[go: up one dir, main page]

WO2018196243A1 - 缓存状态的上报方法及装置 - Google Patents

缓存状态的上报方法及装置 Download PDF

Info

Publication number
WO2018196243A1
WO2018196243A1 PCT/CN2017/099532 CN2017099532W WO2018196243A1 WO 2018196243 A1 WO2018196243 A1 WO 2018196243A1 CN 2017099532 W CN2017099532 W CN 2017099532W WO 2018196243 A1 WO2018196243 A1 WO 2018196243A1
Authority
WO
WIPO (PCT)
Prior art keywords
logical channel
entity
sdap
drb
bsr
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/099532
Other languages
English (en)
French (fr)
Inventor
江小威
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to EP17907455.4A priority Critical patent/EP3606148B1/en
Priority to US16/499,239 priority patent/US11012887B2/en
Priority to CN201780001386.XA priority patent/CN109121467B/zh
Publication of WO2018196243A1 publication Critical patent/WO2018196243A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present application relates to communication technologies, and in particular, to a method and an apparatus for reporting a buffer status.
  • the user equipment In the Long Term Evolution (LTE), the user equipment (UE) needs to report the buffer status of the logical channel, and the buffer status of the logical channel includes a packet data convergence protocol (referred to as a packet data convergence protocol).
  • PDCP packet data convergence protocol
  • the 5G new radio (NR) user plane introduces a new protocol layer above the existing PDCP layer.
  • a bearer contains configurations of PDCP entities, RLC entities, and logical channels, so they are treated as a whole.
  • the service entity in the newly introduced protocol layer does not have a unique relationship with a bearer.
  • the service entity is not part of the bearer, and its mapping relationship can be dynamically configured.
  • how to report the buffer status of the logical channel or logical channel group is an urgent technical problem to be solved.
  • the embodiments of the present disclosure provide a method and a device for reporting a buffer status, which are used to report a buffer status problem of a logical channel or a logical channel group after introducing a new protocol layer.
  • a method for reporting a buffer status comprising:
  • the determined logical channel or the logical channel group corresponds to the DRB mapped by the service data adaptation protocol SDAP entity, reporting, to the base station, the SDAP entity that is mapped to the determined logical channel or the logical channel group The cached BSR.
  • the method further includes:
  • the BSR is triggered
  • the BSR is reported to the base station.
  • the BSR is triggered, including:
  • the BSR is triggered after detecting that the DRB mapped by the SDAP entity changes.
  • the triggering the BSR includes:
  • the determined logical channel or the BSR of the logical channel group is triggered.
  • the triggering the BSR includes:
  • the determined logical channel or the BSR of the logical channel group is triggered.
  • the method further includes:
  • the SDAP entity indicates the transmittable data volume of the SDAP entity to the MAC entity mapped by the determined logical channel, including:
  • the SDAP entity indicates, according to the transmittable data volume indication rule of the PDCP entity corresponding to the DRB, the transmittable data volume of the SDAP entity to the MAC entity mapped by the determined logical channel.
  • the SDAP entity indicates the amount of transmittable data to the MAC entity mapped by the determined logical channel, including:
  • the PDCP entity uses the transmittable data amount of the SDAP entity as part of its own transmittable data, and then indicates the MAC entity mapped to the determined logical channel according to the transmittable data volume indication rule of the PDCP entity. The amount of data that can be transmitted by the PDCP entity.
  • the SDAP entity indicates, according to the transmittable data volume indication rule of the PDCP entity corresponding to the DRB, the transmittable data volume of the SDAP entity to the MAC entity mapped by the determined logical channel, including :
  • the SDAP entity regards the transmittable data volume of the PDCP entity as belonging to the first logical channel included in the DRB, and indicates to the MAC entity corresponding to the first logical channel
  • the SDAP entity The MAC entity corresponding to the first logical channel indicates the amount of transmittable data of the SDAP entity;
  • the SDAP entity regards the transmittable data volume of the PDCP entity as belonging to the second logical channel included in the DRB, and indicates to the MAC entity corresponding to the second logical channel
  • the SDAP entity The MAC entity corresponding to the second logical channel indicates the amount of transmittable data of the SDAP entity;
  • the SDAP entity simultaneously indicates the transmittable data amount of the SDAP entity to the MAC entity corresponding to the first logical channel and the MAC entity corresponding to the second logical channel.
  • the transmittable data amount of the SDAP entity includes at least one of a SDAP Service Data Unit SDU, a SDAP Packet Data Unit PDU, and a SDAP Control PDU.
  • a buffer status reporting apparatus comprising:
  • a determining module configured to determine a logical channel or a logical channel group that satisfies a buffer status report BSR trigger condition
  • the first reporting module is configured to: if the logical channel or the logical channel group determined by the determining module is corresponding to the DRB mapped by the service data adaptation protocol SDAP entity, reporting, to the base station, the mapping to the determining The logical channel or the buffered BSR of the SDAP entity of the logical channel group.
  • the apparatus further includes:
  • the detecting triggering module is configured to trigger the BSR if it detects that the DRB mapped by the SDAP entity changes;
  • the second reporting module is configured to report the BSR triggered by the detection trigger module to the base station.
  • the detection trigger module is configured to:
  • the BSR is triggered after detecting that the DRB mapped by the SDAP entity changes.
  • the detection trigger module includes:
  • Determining a sub-module configured to determine a logical channel or a logical channel group corresponding to the DRB before and after the change;
  • a triggering submodule configured to trigger the logical channel or the logical channel group determined by the determining submodule BSR.
  • the detection trigger module includes:
  • Determining a sub-module configured to determine a logical channel or a logical channel group corresponding to the DRB before and after the change;
  • the triggering submodule is configured to trigger the BSR of the logical channel or the logical channel group determined by the determining submodule.
  • the apparatus further includes:
  • the indication module is configured to: when the first reporting module reports to the base station, a BSR that is mapped to the determined logical channel or the buffered SDAP entity of the logical channel group, is mapped to the determined logical channel
  • the medium access control MAC entity indicates the amount of transmittable data of the SDAP entity.
  • the indication module comprises:
  • the first indication submodule is configured to indicate, according to the transmittable data volume indication rule of the PDCP entity corresponding to the DRB, the transmittable data amount of the SDAP entity to the MAC entity mapped by the determined logical channel.
  • the indication module comprises:
  • a second indication submodule configured to indicate, to a PDCP entity corresponding to the DRB, a transmittable data amount of the SDAP entity
  • a third indicator sub-module configured to use the transmittable data volume of the SDAP entity indicated by the second indication sub-module as a part of self-transportable data, and then indicate a rule according to the transmittable data volume of the PDCP entity
  • the determined MAC entity mapped by the logical channel indicates the amount of transmittable data of the PDCP entity.
  • the first indicator submodule includes:
  • a first indication unit configured to: if the PDCP entity considers the transmittable data volume of the PDCP entity to belong to a first logical channel included in the DRB, and indicates to the MAC entity corresponding to the first logical channel Transmitting, to the MAC entity corresponding to the first logical channel, the amount of transmittable data of the SDAP entity; or
  • a second indication unit configured to: if the PDCP entity considers the transmittable data volume of the PDCP entity to belong to a second logical channel included in the DRB, and indicates to the MAC entity corresponding to the second logical channel Transmitting, to the MAC entity corresponding to the second logical channel, the amount of transmittable data of the SDAP entity; or
  • a third indication unit configured to: if the PDCP entity considers the transmittable data volume of the PDCP entity to belong to both the first logical channel and the second logical channel included in the DRB, and simultaneously indicate to the first a logical letter
  • the MAC entity corresponding to the track and the MAC entity corresponding to the second logical channel simultaneously indicate the transmittable data of the SDAP entity to the MAC entity corresponding to the first logical channel and the MAC entity corresponding to the second logical channel. the amount.
  • the transmittable data amount of the SDAP entity includes at least one of a SDAP Service Data Unit SDU, a SDAP Packet Data Unit PDU, and a SDAP Control PDU.
  • a user equipment including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the determined logical channel or the logical channel group corresponds to the DRB mapped by the service data adaptation protocol SDAP entity, reporting, to the base station, the SDAP entity that is mapped to the determined logical channel or the logical channel group The cached BSR.
  • 1 is a protocol stack architecture and a data flow diagram after adding an SDAP layer according to an exemplary embodiment of the present application
  • FIG. 2 is a flowchart of a method for reporting a buffer status according to an exemplary embodiment of the present application
  • FIG. 3 is a flowchart of determining a DRB of a SDAP entity mapping according to an exemplary embodiment of the present application
  • FIG. 4A is a flowchart of another method for reporting a buffer status according to an exemplary embodiment of the present application.
  • FIG. 4B is a flowchart of another method for reporting a buffer status according to an exemplary embodiment of the present application.
  • FIG. 5 is a block diagram of a buffer status reporting apparatus according to an exemplary embodiment of the present application.
  • FIG. 6 is a block diagram of another buffer status reporting apparatus according to an exemplary embodiment of the present application.
  • FIG. 7A is a block diagram of another reporting device of a buffer state according to an exemplary embodiment of the present application.
  • FIG. 7B is a block diagram of another buffer status reporting apparatus according to an exemplary embodiment of the present application.
  • FIG. 7C is a block diagram of another buffer status reporting apparatus according to an exemplary embodiment of the present application.
  • FIG. 7D is a block diagram of another buffer status reporting apparatus according to an exemplary embodiment of the present application.
  • FIG. 7E is a block diagram of another buffer status reporting apparatus according to an exemplary embodiment of the present application.
  • FIG. 8 is a block diagram of a reporting apparatus suitable for a cache state, according to an exemplary embodiment.
  • the newly introduced protocol layer is called a Service Data Adaptation Protocol (SDAP) layer, where the SDAP layer is located on the upper layer of the PDCP layer, and is responsible for the upper layer.
  • SDAP Service Data Adaptation Protocol
  • the QoS flow is mapped to a data bearer (DRB), and the packet data unit (PDU) of the SDAP layer is a service data unit (SDU) of the PDCP layer, and the protocol stack structure and data flow diagram after the SDAP layer is added.
  • DRB data bearer
  • PDU packet data unit
  • SDU service data unit
  • the SDAP layer may include multiple PDU sessions, each PDU session corresponding to one SDAP entity, and the SDAP entity refers to a logical body that processes the PDU session service.
  • the mapping relationship between the uplink data of the PDU session and the DRB has the following states: The status of the PDU session is mapped to the DRB. Map to the default DRB.
  • a SDAP entity contains multiple QoS flows, and different QoS flows may be mapped to the same or different DRBs.
  • One DRB corresponds to one PDCP configuration, one or more RLC configurations, and one or more logical channels Configuration.
  • the standard protocol supports one DRB corresponding to two RLC configurations and two logical channel configurations (one logical channel corresponds to one RLC, and the two correspond one-to-one).
  • the two RLCs or logical channels may correspond to the same Media Access Control (MAC) entity, or two different MAC entities: a primary cell group (MCG) MAC or a secondary cell group. Referred to as (SCG) MAC.
  • MCG primary cell group
  • SCG secondary cell group
  • mapping between the SDAP entity and the DRB is not determined by the mapping between the SDAP entity and the DRB. Therefore, the mapping between the SDAP and the DRB is required to be performed by the UE.
  • the following describes the implementation process of the present application in detail with reference to specific embodiments. description.
  • FIG. 2 is a flowchart of a method for reporting a buffer status according to an exemplary embodiment of the present application. The method embodiment is described from the UE side. As shown in FIG. 2, the method for reporting the buffer status includes:
  • step S201 a logical channel or a logical channel group that satisfies a buffer status report (BSR) trigger condition is determined.
  • BSR buffer status report
  • the UE may have multiple logical channels or logical channel groups, and when some or some logical channels or logical channel groups satisfy the BSR trigger condition, determine the identifier of the logical channel or logical channel group that satisfies the BSR trigger condition. information.
  • step S202 if the determined logical channel or logical channel group corresponds to the DRB mapped by the SDAP entity, the BSR including the cache of the SDAP entity mapped to the determined logical channel or logical channel group is reported to the base station.
  • the UE reports to the base station a BSR including a cache of the SDAP entity mapped to the determined logical channel or logical channel group, that is, the UE
  • the reported BSR includes the sum of the buffer states of the RLC entity, the PDCP entity, and the SDAP entity mapped to the determined logical channel or logical channel group.
  • the BSR reported by the UE to the base station does not include the cached BSR of the SDAP entity.
  • the method may further include: determining a DRB of the SDAP entity mapping.
  • the DRB of the SDAP entity mapping can be determined by the following steps:
  • step S301 radio resource control (RRC) configuration information delivered by the base station is received.
  • RRC radio resource control
  • the RRC configuration information may include configuration information of the SDAP layer, and the configuration information of the SDAP layer may include, but is not limited to, a DRB mapped by the QoS flow.
  • step S302 configuration is performed according to the received RRC configuration information, and the DRB mapped by each SDAP entity is determined.
  • the mapping of the QoS flow to the DRB is a SDAP entity. Therefore, the DRB mapped by the SDAP entity can be determined according to the DRB mapped by the QoS flow. For example, if SDAP entity 1 maps QoS flow to DRB1 and SDAP entity 2 maps QoS flow to DRB2, it can be determined that the DRB mapped by SDAP entity 1 is DRB1, and the DRB mapped by SDAP entity 2 is DRB2.
  • reporting to the base station includes mapping to the determined logical channel or logic.
  • the buffered BSR of the SDAP entity of the channel group thereby solving the problem of reporting the buffer status of the logical channel or logical channel group after introducing a new protocol layer.
  • FIG. 4A is a flowchart of another method for reporting a cache state according to an exemplary embodiment of the present application. As shown in FIG. 4A, the method may further include:
  • step S401 if it is detected that the DRB mapped by the SDAP entity changes, the BSR is triggered.
  • triggering the BSR of the affected logical channel or logical channel group that is, first determining the logical channel corresponding to the DRB before and after the change or The logical channel group then triggers the BSR of the determined logical channel or logical channel group.
  • the UE may change the DRB mapped by the SDAP entity by receiving the update configuration information.
  • the update configuration information may indicate that one or some of the SDAP entities update the mapped DRB.
  • the base station remaps the downlink QoS flow to a new DRB, it indicates that the uplink QoS flow is also re-established. Map to this new DRB.
  • the BSR is triggered after detecting that the DRB mapped by the SDAP entity changes. Because if the SDAP entity has cached data, when the SDAP entity is remapped from one DRB to another, the cache state of the logical channel or logical channel group corresponding to the original DRB and the new DRB changes. In this case, the change is first determined. The logical channel or logical channel group corresponding to the DRBs before and after, and then triggers the BSR of the determined logical channel or logical channel group.
  • step S402 the BSR is reported to the base station.
  • the BSR can be reported to the base station.
  • the BSR is triggered when the DRB mapped by the SDAP entity is detected to be changed, and The triggered BSR is reported, which solves the problem of reporting the buffer status of the logical channel or logical channel group when the DRB of the SDAP entity mapping changes.
  • FIG. 4B is a flowchart of another method for reporting a cache state according to an exemplary embodiment of the present application. As shown in FIG. 4B, when performing step S202, the method may further include:
  • step S203 the SDAP entity indicates the transmittable data amount of the SDAP entity to the MAC entity mapped by the determined logical channel.
  • the data available for transmission of the SDAP entity may include at least one of the following: a) a SDAP SDU if it has not been processed by the SDAP layer; b) a SDAP PDU, if the SDAP SDU has been processed to generate a PDU; c) SDAP Control PDU (if the standard has a Control PDU).
  • the amount of transmittable data of the SDAP entity can be indicated to the MAC entity mapped by the determined logical channel in two ways:
  • the SDAP entity indicates the transmittable data amount of the SDAP entity to the MAC entity mapped by the determined logical channel according to the transmittable data volume indication rule of the PDCP entity corresponding to the DRB.
  • the PDCP entity of the DRB When the PDCP entity of the DRB indicates the transmittable data size to the MAC layer, it indicates the transmittable data size corresponding to each logical channel of the DRB (depending on the MAC entity to which the logical channel belongs, indicating to the corresponding MAC entity).
  • the indication manner that the PDCP layer indicates that the data can be transmitted to the MAC includes (depending on the specific scenario, different indication modes are used, and is not deployed here): 1. All transmittable data is counted into a designated logical channel, and the MAC corresponding to the logical channel is indicated. (If the DRB is configured with two logical channels, the designated logical channel indicates the amount of transmittable data, and the other logical channel indicates 0) 2. All transmittable data is simultaneously recorded in two logical channels, indicating to the two logical channels. The MAC entity corresponding to the channel indicates the amount of data that can be transmitted for both logical channels.
  • Scenario 1 If the PDCP entity regards the transmittable data volume of the PDCP entity as belonging to the first logical channel included in the DRB and indicates the MAC entity corresponding to the first logical channel, the SDAP entity sends the MAC entity corresponding to the first logical channel. Indicates the amount of transmittable data for the SDAP entity.
  • the DRB contains one logical channel, it is assumed to be called an A logical channel; if the DRB contains two logical channels, it is assumed to be referred to as an A logical channel and a B logical channel, respectively.
  • the PDCP entity regards the transmittable data amount as belonging to the logical channel A and indicates to the MAC entity corresponding to the logical channel A (indicating that the amount of data belonging to the logical channel B corresponding to the MAC entity of the logical channel B is 0)
  • the SDAP entity also The amount of transmittable data is regarded as belonging to logical channel A, and is indicated to the MAC entity corresponding to logical channel A, that is, it is assumed that the PDCP entity indicates only the transmittable data to the MCG.
  • the SDAP entity also indicates that the transmittable data is only indicated to the MCG MAC.
  • the PDCP entity regards the amount of transmittable data as belonging to the logical channel B, and indicates to the MAC entity corresponding to the logical channel B (the amount of data belonging to the logical channel A indicated to the corresponding entity of the logical channel A is 0)
  • the SDAP entity also treats the amount of transmittable data as logical channel B and indicates to the MAC entity corresponding to logical channel B.
  • the PDCP entity considers the transmittable data amount of the PDCP entity to belong to both the first logical channel and the second logical channel included in the DRB, and simultaneously indicates that the MAC entity corresponding to the first logical channel corresponds to the second logical channel.
  • the MAC entity indicates that the SDAP entity simultaneously indicates the transmittable data amount of the SDAP entity to the MAC entity corresponding to the first logical channel and the MAC entity corresponding to the second logical channel.
  • the SDAP entity regards the amount of transmittable data as belonging to both logical channels A and B, and simultaneously indicates to the corresponding MAC entities of logical channels A and B (the amount of data belonging to logical channels A and B is the same, If the PDCP layer can transmit data, the SDAP entity also considers the amount of transmittable data to belong to both logical channels A and B, and simultaneously indicates the MAC entities corresponding to logical channels A and B.
  • the SDAP entity can be correspondingly indicated according to different indication manners used by the PDCP entity, and the applicable scenarios are many, and the implementation manner is simple.
  • the SDAP entity indicates the transmittable data volume of the SDAP entity to the PDCP entity corresponding to the DRB, and the PDCP entity uses the transmittable data volume of the SDAP entity as part of the transmittable data, and then according to the transmittable data volume of the PDCP entity.
  • the indication rule indicates to the MAC entity mapped by the determined logical channel the amount of transmittable data of the PDCP entity.
  • the embodiment can indicate the transmittable data volume of the SDAP entity to the MAC entity mapped by the determined logical channel in two ways, and the implementation manner is flexible and diverse.
  • the MAC entity mapped by the SDAP entity to the determined logical channel indicates the transmittable data amount of the SDAP entity, for reporting the BSR.
  • the present disclosure also provides an embodiment of the reporting device of the cache state.
  • FIG. 5 is a block diagram of a buffer status reporting apparatus according to an exemplary embodiment. As shown in FIG. 5, the buffer status reporting apparatus includes a determining module 51 and a first reporting module 52.
  • the determination module 51 is configured to determine a logical channel or logical channel group that satisfies the buffer status report BSR trigger condition.
  • the UE may have multiple logical channels or logical channel groups, and when some or some logical channels or logical channel groups satisfy the BSR trigger condition, determine the identifier of the logical channel or logical channel group that satisfies the BSR trigger condition. information.
  • the first reporting module 52 is configured to report to the base station that the logical channel or the logical channel group determined by the determining module 51 corresponds to the DRB mapped by the service data adaptation protocol SDAP entity, and includes reporting to the determined logical channel or logical channel group.
  • the cached BSR of the SDAP entity is configured to report to the base station that the logical channel or the logical channel group determined by the determining module 51 corresponds to the DRB mapped by the service data adaptation protocol SDAP entity, and includes reporting to the determined logical channel or logical channel group.
  • the UE reports to the base station a BSR including a cache of the SDAP entity mapped to the determined logical channel or logical channel group, that is, the UE
  • the reported BSR includes the sum of the buffer states of the RLC entity, the PDCP entity, and the SDAP entity mapped to the determined logical channel or logical channel group.
  • the BSR reported by the UE to the base station does not include the cached BSR of the SDAP entity.
  • the first reporting module 52 can also determine the DRB mapped by the SDAP entity. For the implementation manner, refer to the embodiment shown in FIG. 3.
  • the device shown in FIG. 5 is used to implement the method flow shown in FIG. 2, and the related content descriptions are the same, and are not described herein.
  • reporting to the base station includes mapping to the determined logical channel or logic.
  • the buffered BSR of the SDAP entity of the channel group thereby solving the problem of reporting the buffer status of the logical channel or logical channel group after introducing a new protocol layer.
  • FIG. 6 is a block diagram of another reporting device of a cache state according to an exemplary embodiment. As shown in FIG. 6, on the basis of the foregoing embodiment shown in FIG. 5, the device may include: a detection trigger module 53 and The second reporting module 54.
  • the detection triggering module 53 is configured to trigger the BSR if it detects that the DRB mapped by the SDAP entity changes.
  • triggering the BSR of the affected logical channel or logical channel group that is, first determining the logical channel corresponding to the DRB before and after the change or The logical channel group then triggers the BSR of the determined logical channel or logical channel group.
  • the second reporting module 54 is configured to report the BSR triggered by the detection trigger module 53 to the base station.
  • the detection triggering module 53 can be configured to: if it is determined that the SDAP entity has cached data, trigger the BSR after detecting that the DRB mapped by the SDAP entity changes. Because if the SDAP entity has cached data, when the SDAP entity is remapped from one DRB to another, the cache state of the logical channel or logical channel group corresponding to the original DRB and the new DRB changes. In this case, the change is first determined. The logical channel or logical channel group corresponding to the DRBs before and after, and then triggers the BSR of the determined logical channel or logical channel group.
  • the BSR when detecting that the DRB mapped by the SDAP entity changes, the BSR is triggered, and the triggered BSR is reported, thereby solving the problem of reporting the buffer status of the logical channel or the logical channel group when the DRB of the SDAP entity is changed.
  • FIG. 7A is a block diagram of another reporting device of a cache state according to an exemplary embodiment.
  • the detecting trigger module 53 may include: determining a submodule. 531 and trigger sub-module 532.
  • the determining sub-module 531 is configured to determine a logical channel or a logical channel group corresponding to the DRB before and after the change occurs.
  • the trigger sub-module 532 is configured to trigger a BSR of the logical channel or logical channel group determined by the determining sub-module 531.
  • the BSR is triggered when the DRB corresponding to the logical channel or the logical channel group is triggered by the logical channel or the logical channel group corresponding to the DRB before and after the change, and then the BSR is changed.
  • FIG. 7B is a block diagram of another reporting device of a cache state according to an exemplary embodiment. As shown in FIG. 7B, the device may further include an indication module 55.
  • the indication module 55 is configured to indicate to the media access control MAC entity mapped to the determined logical channel when the first reporting module 52 reports to the base station a buffered BSR including a SDAP entity mapped to the determined logical channel or logical channel group. The amount of data that can be transferred by the SDAP entity.
  • the data available for transmission of the SDAP entity may include the following At least one: a) the SDAP SDU if it has not been processed by the SDAP layer; b) the SDAP PDU if the SDAP SDU has been processed to generate the PDU; c) the SDAP Control PDU (if the standard has a Control PDU).
  • the indication module 55 is located at the SDAP layer, ie the SDAP entity indicates the amount of transmittable data of the SDAP entity to the Media Access Control MAC entity mapped by the determined logical channel.
  • the MAC entity mapped by the SDAP entity to the determined logical channel indicates the transmittable data amount of the SDAP entity, for reporting the BSR.
  • FIG. 7C is a block diagram of another reporting device of a cache state according to an exemplary embodiment.
  • the indication module 55 may include: a first indicator. Module 551.
  • the first indicator sub-module 551 is configured to indicate the transmittable data amount of the SDAP entity to the MAC entity mapped by the determined logical channel according to the transmittable data volume indication rule of the PDCP entity corresponding to the DRB.
  • the transmittable data volume of the SDAP entity may be indicated to the MAC entity mapped by the determined logical channel according to the transmittable data volume indication rule of the PDCP entity corresponding to the DRB, and the implementation manner is simple.
  • FIG. 7D is a block diagram of another buffer status reporting apparatus according to an exemplary embodiment.
  • the indication module 55 may include: a second indicator. Module 552 and third indicator sub-module 553.
  • the second indication sub-module 552 is configured to indicate to the PDCP entity corresponding to the DRB the amount of transmittable data of the SDAP entity.
  • the second indicator submodule 552 is located at the SDAP layer.
  • the third indicator sub-module 553 is configured to use the transmittable data amount of the SDAP entity indicated by the second indication sub-module 552 as part of its own transmittable data, and then to the determined logical channel according to the transmittable data amount indication rule of the PDCP entity.
  • the mapped MAC entity indicates the amount of transmittable data of the PDCP entity.
  • the third indicator submodule 553 is located at the PDCP layer.
  • the transmittable data volume of the SDAP entity indicated by the second indication submodule is used as a part of the transmittable data, and then according to the PDCP entity.
  • the transmission data volume indication rule indicates the amount of transmittable data of the PDCP entity to the MAC entity mapped by the determined logical channel, and the implementation manner is simple.
  • FIG. 7E is a block diagram of another reporting device of a cache state according to an exemplary embodiment.
  • the first indicator submodule 551 may include: An indicating unit 5511.
  • the first indication unit 5511 is configured to correspond to the first logical channel if the PDCP entity regards the transmittable data volume of the PDCP entity as belonging to the first logical channel included in the DRB and indicates the MAC entity corresponding to the first logical channel.
  • the MAC entity indicates the amount of transmittable data of the SDAP entity.
  • the DRB contains one logical channel, it is assumed to be called an A logical channel; if the DRB contains two logical channels, it is assumed to be referred to as an A logical channel and a B logical channel, respectively.
  • the PDCP entity regards the transmittable data amount as belonging to the logical channel A and indicates to the MAC entity corresponding to the logical channel A (indicating that the amount of data belonging to the logical channel B corresponding to the MAC entity of the logical channel B is 0)
  • the SDAP entity also Considering the amount of transmittable data as belonging to logical channel A and indicating to the MAC entity corresponding to logical channel A, that is, assuming that the PDCP entity indicates only the transmittable data to the MCG MAC, the SDAP entity also indicates that the transmittable data is only indicated to the MCG MAC. .
  • the second indication unit 5512 is configured to correspond to the second logical channel if the PDCP entity regards the transmittable data volume of the PDCP entity as belonging to the second logical channel included in the DRB and indicates the MAC entity corresponding to the second logical channel.
  • the MAC entity indicates the amount of transmittable data of the SDAP entity.
  • the PDCP entity regards the amount of transmittable data as belonging to the logical channel B, and indicates to the MAC entity corresponding to the logical channel B (the amount of data belonging to the logical channel A indicated to the corresponding entity of the logical channel A is 0)
  • the SDAP entity also treats the amount of transmittable data as logical channel B and indicates to the MAC entity corresponding to logical channel B.
  • the third indication unit 5513 is configured to: if the PDCP entity regards the transmittable data amount of the PDCP entity as belonging to the first logical channel and the second logical channel included in the DRB, and simultaneously indicate to the MAC entity corresponding to the first logical channel and The MAC entity corresponding to the second logical channel indicates the transmittable data amount of the SDAP entity to the MAC entity corresponding to the first logical channel and the MAC entity corresponding to the second logical channel.
  • the SDAP entity regards the amount of transmittable data as belonging to both logical channels A and B, and simultaneously indicates to the corresponding MAC entities of logical channels A and B (the amount of data belonging to logical channels A and B is the same, If the PDCP layer can transmit data, the SDAP entity also considers the amount of transmittable data to belong to both logical channels A and B, and simultaneously indicates the MAC entities corresponding to logical channels A and B.
  • the SDAP entity can be instructed according to different indication manners used by the PDCP entity, and the applicable scenarios are simple, and the implementation manner is simple.
  • FIG. 8 is a block diagram of a reporting apparatus suitable for a cache state, according to an exemplary embodiment.
  • device 800 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • device 800 can include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, And a communication component 816.
  • Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 802 can include one or more processors 820 to execute instructions to perform all or part of the steps of the above described methods.
  • processing component 802 can include one or more modules to facilitate interaction between component 802 and other components.
  • processing component 802 can include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operation at device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 804 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Electrically erasable programmable read only memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 806 provides power to various components of device 800.
  • Power component 806 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 800.
  • the multimedia component 808 includes a screen between the device 800 and the user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the device 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 810 is configured to output and/or input an audio signal.
  • audio component 810 includes a microphone (MIC) that is in operation mode, such as call mode, recording mode, and voice recognition mode, The wind is configured to receive an external audio signal.
  • the received audio signal may be further stored in memory 804 or transmitted via communication component 816.
  • the audio component 810 also includes a speaker for outputting an audio signal.
  • the I/O interface 812 provides an interface between the processing component 802 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 814 includes one or more sensors for providing device 800 with a status assessment of various aspects.
  • sensor component 814 can detect an open/closed state of device 800, a relative positioning of components, such as a display and a keypad of device 800, and sensor component 814 can also detect a change in position of device 800 or a component of device 800, the user The presence or absence of contact with device 800, device 800 orientation or acceleration/deceleration and temperature variation of device 800.
  • Sensor assembly 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 814 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices.
  • the device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • communication component 816 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • device 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 804 comprising instructions executable by processor 820 of apparatus 800 to perform the above method.
  • the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
  • the device embodiment since it basically corresponds to the method embodiment, Part of the description of the example can be.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种缓存状态的上报方法及装置，其中，缓存状态的上报方法包括：确定满足BSR触发条件的逻辑信道或逻辑信道组；若确定的逻辑信道或逻辑信道组与SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR。本申请实施例，通过确定满足BSR触发条件的逻辑信道或逻辑信道组，并在确定的逻辑信道或逻辑信道组与SDAP实体所映射的DRB对应时，向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR，从而解决了在引入新的协议层之后上报逻辑信道或逻辑信道组的缓存状态问题。

Description

缓存状态的上报方法及装置 技术领域
本申请涉及通信技术，尤其涉及一种缓存状态的上报方法及装置。
背景技术
在长期演进(Long Term Evolution，简称LTE)中，用户设备(UE)需要上报逻辑信道的缓存状态，而逻辑信道的缓存状态包括映射到该逻辑信道的数据包汇聚协议(packet data convergence protocol，简称PDCP)实体和无线链路控制(radio link control，简称RLC)实体的缓存状态。
随着通信技术的发展，出现了第五代移动通信技术(5th Generation，简称5G)。5G新空口(new radio，NR)用户面在现有的PDCP层之上引入了一个新的协议层。在LTE中，一个承载包含了PDCP实体、RLC实体与逻辑信道的配置，所以它们被当作一个整体。但是新引入的协议层中的业务实体却与某个承载并没有唯一的确定关系，该业务实体不是承载的一部分，其映射关系可以动态配置。那么，在PDCP层之上引入了一个新的协议层之后，如何上报逻辑信道或逻辑信道组的缓存状态是一个急需解决的技术问题。
发明内容
为克服相关技术中存在的问题，本公开实施例提供一种缓存状态的上报方法及装置，用以在引入新的协议层之后上报逻辑信道或逻辑信道组的缓存状态问题。
根据本公开实施例的第一方面，提供一种缓存状态的上报方法，所述方法包括：
确定满足缓存状态报告BSR触发条件的逻辑信道或逻辑信道组；
若确定的所述逻辑信道或所述逻辑信道组与业务数据适配协议SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR。
在一实施例中，所述方法还包括：
若检测到SDAP实体所映射的DRB发生变化，则触发所述BSR；
向基站上报所述BSR。
在一实施例中，所述若检测到SDAP实体所映射的DRB发生变化，则触发所述BSR，包括：
若确定所述SDAP实体有缓存数据，则在检测到所述SDAP实体所映射的DRB发生变化后，触发所述BSR。
在一实施例中，所述触发所述BSR，包括：
确定发生变化前后的DRB对应的逻辑信道或逻辑信道组；
触发所确定的所述逻辑信道或所述逻辑信道组的BSR。
在一实施例中，所述触发所述BSR，包括：
确定发生变化前后的DRB对应的逻辑信道或逻辑信道组；
触发所确定的所述逻辑信道或所述逻辑信道组的BSR。
在一实施例中，所述方法还包括：
在所述向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR时，所述SDAP实体向确定的所述逻辑信道所映射的媒体接入控制MAC实体指示所述SDAP实体的可传输数据量。
在一实施例中，所述SDAP实体向确定的所述逻辑信道所映射的MAC实体指示所述SDAP实体的可传输数据量，包括：
所述SDAP实体按照所述DRB所对应的PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述SDAP实体的可传输数据量。
在一实施例中，所述SDAP实体向确定的所述逻辑信道所映射的MAC实体指示可传输数据量，包括：
所述SDAP实体向所述DRB所对应的PDCP实体指示所述SDAP实体的可传输数据量；
所述PDCP实体将所述SDAP实体的可传输数据量作为自己可传输数据的一部分，然后按照所述PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述PDCP实体的可传输数据量。
在一实施例中，所述SDAP实体按照所述DRB所对应的PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述SDAP实体的可传输数据量，包括：
若所述PDCP实体将所述PDCP实体的可传输数据量视为属于所述DRB所包含的第一逻辑信道，且指示给所述第一逻辑信道对应的MAC实体，则所述SDAP实体向所述第一逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量；或者
若所述PDCP实体将所述PDCP实体的可传输数据量视为属于所述DRB所包含的第二逻辑信道，且指示给所述第二逻辑信道对应的MAC实体，则所述SDAP实体向所述第二逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量；或者
若所述PDCP实体将所述PDCP实体的可传输数据量视为同时属于所述DRB所包含的第一逻辑信道和第二逻辑信道，且同时指示给所述第一逻辑信道对应的MAC实体和所述第二逻辑信道对应的MAC实体，则所述SDAP实体同时向所述第一逻辑信道对应的MAC实体和所述第二逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量。
在一实施例中，所述SDAP实体的可传输数据量包括SDAP服务数据单元SDU、SDAP包数据单元PDU和SDAP控制PDU中的至少一项。
根据本公开实施例的第二方面，提供一种缓存状态的上报装置，所述装置包括：
确定模块，被配置为确定满足缓存状态报告BSR触发条件的逻辑信道或逻辑信道组；
第一上报模块，被配置为若所述确定模块确定的所述逻辑信道或所述逻辑信道组与业务数据适配协议SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR。
在一实施例中，所述装置还包括：
检测触发模块，被配置为若检测到SDAP实体所映射的DRB发生变化，则触发所述BSR；
第二上报模块，被配置为向基站上报所述检测触发模块触发的所述BSR。
在一实施例中，所述检测触发模块，被配置为：
若确定所述SDAP实体有缓存数据，则在检测到所述SDAP实体所映射的DRB发生变化后，触发所述BSR。
在一实施例中，所述检测触发模块包括：
确定子模块，被配置为确定发生变化前后的DRB对应的逻辑信道或逻辑信道组；
触发子模块，被配置为触发所述确定子模块所确定的所述逻辑信道或所述逻辑信道组 的BSR。
在一实施例中，所述检测触发模块包括：
确定子模块，被配置为确定发生变化前后的DRB对应的逻辑信道或逻辑信道组；
触发子模块，被配置为触发所述确定子模块所确定的所述逻辑信道或所述逻辑信道组的BSR。
在一实施例中，所述装置还包括：
指示模块，被配置为在所述第一上报模块向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR时，向确定的所述逻辑信道所映射的媒体接入控制MAC实体指示所述SDAP实体的可传输数据量。
在一实施例中，所述指示模块包括：
第一指示子模块，被配置为按照所述DRB所对应的PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述SDAP实体的可传输数据量。
在一实施例中，所述指示模块包括：
第二指示子模块，被配置为向所述DRB所对应的PDCP实体指示所述SDAP实体的可传输数据量；
第三指示子模块，被配置为将所述第二指示子模块指示的所述SDAP实体的可传输数据量作为自己可传输数据的一部分，然后按照所述PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述PDCP实体的可传输数据量。
在一实施例中，所述第一指示子模块包括：
第一指示单元，被配置为若所述PDCP实体将所述PDCP实体的可传输数据量视为属于所述DRB所包含的第一逻辑信道，且指示给所述第一逻辑信道对应的MAC实体，则向所述第一逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量；或者
第二指示单元，被配置为若所述PDCP实体将所述PDCP实体的可传输数据量视为属于所述DRB所包含的第二逻辑信道，且指示给所述第二逻辑信道对应的MAC实体，则向所述第二逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量；或者
第三指示单元，被配置为若所述PDCP实体将所述PDCP实体的可传输数据量视为同时属于所述DRB所包含的第一逻辑信道和第二逻辑信道，且同时指示给所述第一逻辑信 道对应的MAC实体和所述第二逻辑信道对应的MAC实体，则同时向所述第一逻辑信道对应的MAC实体和所述第二逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量。
在一实施例中，所述SDAP实体的可传输数据量包括SDAP服务数据单元SDU、SDAP包数据单元PDU和SDAP控制PDU中的至少一项。
根据本公开实施例的第三方面，提供一种用户设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
确定满足缓存状态报告BSR触发条件的逻辑信道或逻辑信道组；
若确定的所述逻辑信道或所述逻辑信道组与业务数据适配协议SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR。
本公开的实施例提供的技术方案可以包括以下有益效果：
通过确定满足BSR触发条件的逻辑信道或逻辑信道组，并在确定的逻辑信道或所述逻辑信道组与SDAP实体所映射的DRB对应时，向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR，从而解决了在引入新的协议层之后上报逻辑信道或逻辑信道组的缓存状态问题。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一示例性实施例示出的一种增加SDAP层后的协议栈架构及数据流图；
图2是本申请一示例性实施例示出的一种缓存状态的上报方法流程图；
图3是本申请一示例性实施例示出的一种确定SDAP实体映射的DRB的流程图；
图4A是本申请一示例性实施例示出的另一种缓存状态的上报方法流程图；
图4B是本申请一示例性实施例示出的另一种缓存状态的上报方法流程图；
图5是本申请一示例性实施例示出的一种缓存状态的上报装置的框图；
图6是本申请一示例性实施例示出的另一种缓存状态的上报装置的框图；
图7A是本申请一示例性实施例示出的另一种缓存状态的上报装置的框图；
图7B是本申请一示例性实施例示出的另一种缓存状态的上报装置的框图；
图7C是本申请一示例性实施例示出的另一种缓存状态的上报装置的框图；
图7D是本申请一示例性实施例示出的另一种缓存状态的上报装置的框图；
图7E是本申请一示例性实施例示出的另一种缓存状态的上报装置的框图；
图8是根据一示例性实施例示出的一种适用于缓存状态的上报装置的框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
在本申请实施例中，为描述方便，将新引入的协议层称为业务数据适配协议(Service data adaptation protocol，SDAP)层，其中，SDAP层位于PDCP层的上一层，负责将上层的业务质量流(QoS flow)映射到某个数据承载(DRB)上，SDAP层的包数据单元(PDU)是PDCP层的服务数据单元(SDU)，增加SDAP层后的协议栈架构及数据流图如图1所示。SDAP层可以包括多个PDU会话(session)，每个PDU session与一个SDAP实体对应，SDAP实体是指处理PDU session业务的逻辑主体，PDU session的上行数据与DRB间的映射关系有以下几种状态：状态1，PDU session的上行数据映射到某一个DRB；状态2，网络配置了反射(reflective)QoS，即PDU session的上行数据和下行数据映射到同一个DRB；状态3，PDU session的上行数据映射到默认DRB。
一个SDAP实体中包含多个QoS flow，不同的QoS flow可能映射到同一个或不同的DRB。一个DRB对应一个PDCP配置、一个或多个RLC配置，以及一个或多个逻辑信道 配置。目前标准协议支持一个DRB最多对应2个RLC配置和2个逻辑信道配置(一个逻辑信道对应一个RLC，二者一一对应)。两个RLC或逻辑信道可以对应到同一个媒体接入控制(Media Access Control，简称MAC)实体，或两个不同MAC实体：主小区组(master cell group，简称MCG)MAC或(secondary cell group，简称(SCG)MAC。
由于SDAP实体与DRB没有唯一确定的映射关系，因此，UE在上报逻辑信道或逻辑信道组的缓存状态时需要根据SDAP与DRB的映射关系来完成，下面结合具体实施例对本申请的实现过程进行详细描述。
图2是本申请一示例性实施例示出的一种缓存状态的上报方法流程图，该方法实施例从UE侧进行描述，如图2所示，该缓存状态的上报方法包括：
在步骤S201中，确定满足缓存状态报告(BSR)触发条件的逻辑信道或逻辑信道组。
在该实施例中，UE可以有多个逻辑信道或逻辑信道组，当某个或某些逻辑信道或逻辑信道组满足BSR触发条件时，确定满足BSR触发条件的逻辑信道或逻辑信道组的标识信息。
在步骤S202中，若确定的逻辑信道或逻辑信道组与SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR。
由于SDAP实体与DRB没有唯一确定的映射关系，因此，在确定满足BSR触发条件的逻辑信道或逻辑信道组后，需要检查满足BSR触发条件的逻辑信道或逻辑信道组是否与SDAP实体所映射的DRB对应，若满足BSR触发条件的逻辑信道或逻辑信道组与SDAP实体所映射的DRB对应，则UE向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR，也即UE上报的BSR包括映射到确定的逻辑信道或逻辑信道组的RLC实体、PDCP实体和SDAP实体的缓存状态之和。
而如果满足BSR触发条件的逻辑信道或逻辑信道组与SDAP实体所映射的DRB不对应，则UE向基站上报的BSR不包括SDAP实体的缓存的BSR。
另外，在执行步骤S202之前，该方法还可以包括：确定SDAP实体映射的DRB。如图3所示，可以通过以下步骤确定SDAP实体映射的DRB：
在步骤S301中，接收基站下发的无线资源控制(RRC)配置信息。
其中，该RRC配置信息可以包括SDAP层的配置信息，该SDAP层的配置信息可以包括但不局限于QoS flow所映射的DRB等。
在步骤S302中，根据接收的RRC配置信息进行配置，并确定每个SDAP实体映射的DRB。
其中，将QoS flow映射到DRB的是SDAP实体，因此，可以根据QoS flow所映射的DRB来确定SDAP实体映射的DRB。例如，假设SDAP实体1将QoS flow映射到DRB1，SDAP实体2将QoS flow映射到DRB2，则可以确定SDAP实体1映射的DRB是DRB1，SDAP实体2映射的DRB是DRB2。
上述实施例，通过确定满足BSR触发条件的逻辑信道或逻辑信道组，并在确定的逻辑信道或逻辑信道组与SDAP实体所映射的DRB对应时，向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR，从而解决了在引入新的协议层之后上报逻辑信道或逻辑信道组的缓存状态问题。
图4A是本申请一示例性实施例示出的另一种缓存状态的上报方法流程图，如图4A所示，该方法还可以包括：
在步骤S401中，若检测到SDAP实体所映射的DRB发生变化，则触发BSR。
在该实施例中，如果变化的DRB影响了对应逻辑信道或逻辑信道组的缓存状态，则触发所影响的逻辑信道或逻辑信道组的BSR，即首先确定发生变化前后的DRB对应的逻辑信道或逻辑信道组，然后触发所确定的逻辑信道或逻辑信道组的BSR。
其中，UE可以通过接收更新配置信息的方式来更改SDAP实体映射的DRB。例如，更新配置信息中可以指示某个或某些SDAP实体更新映射的DRB，又例如，对于reflective QoS，如果基站将下行的QoS flow重新映射到一个新的DRB，则表明上行的QoS flow也重新映射到这个新的DRB。
优选地，如果确定SDAP实体有缓存数据，则在检测到该SDAP实体所映射的DRB发生变化后，触发BSR。因为如果SDAP实体有缓存数据，则该SDAP实体由一个DRB重新映射到另一个DRB时，原先DRB与新DRB对应的逻辑信道或逻辑信道组的缓存状态都会发生变化，此时，首先确定发生变化前后的DRB对应的逻辑信道或逻辑信道组，然后触发所确定的逻辑信道或逻辑信道组的BSR。
在步骤S402中，向基站上报BSR。
在触发BSR之后，可以向基站上报BSR。
上述实施例，通过在检测到SDAP实体所映射的DRB发生变化时，触发BSR，并 上报触发的BSR，从而解决了SDAP实体映射的DRB发生变化时逻辑信道或逻辑信道组的缓存状态上报问题。
图4B是本申请一示例性实施例示出的另一种缓存状态的上报方法流程图，如图4B所示，在执行步骤S202时，该方法还可以包括：
在步骤S203中，SDAP实体向确定的逻辑信道所映射的MAC实体指示SDAP实体的可传输数据量。
其中，SDAP实体的可传输数据量(data available for transmission)可以包括以下至少一项：a)SDAP SDU，如果其还未被SDAP层处理；b)SDAP PDU，如果SDAP SDU已经被处理生成PDU；c)SDAP控制PDU(如果标准制定了控制PDU)。
在该实施例中，可以通过两种方式向确定的逻辑信道所映射的MAC实体指示SDAP实体的可传输数据量：
第一种方式，SDAP实体按照DRB所对应的PDCP实体的可传输数据量指示规则向确定的逻辑信道所映射的MAC实体指示SDAP实体的可传输数据量。
一个DRB的PDCP实体在向MAC层指示可传输数据大小时，分别指示该DRB的各个逻辑信道对应的可传输数据大小(视逻辑信道所属的MAC实体，指示给对应的MAC实体)。PDCP层指示可传输数据给MAC的指示方式包括(视具体场景采用不同指示方式，此处不展开)：1.全部可传输数据计入指定的一个逻辑信道，并指示给该逻辑信道对应的MAC(如果DRB配置了两个逻辑信道，则对该指定逻辑信道指示可传输数据量，对另一个逻辑信道指示0)2.全部可传输数据同时都记入两个逻辑信道，指示给两个逻辑信道对应的MAC实体，对两个逻辑信道均指示可传输数据量。
对于第一种方式，可以包括以下三种情形：
情形1)若PDCP实体将PDCP实体的可传输数据量视为属于DRB所包含的第一逻辑信道，且指示给第一逻辑信道对应的MAC实体，则SDAP实体向第一逻辑信道对应的MAC实体指示SDAP实体的可传输数据量。
例如，若该DRB包含一个逻辑信道，假设称为A逻辑信道；若该DRB包含两个逻辑信道，假设分别称为A逻辑信道和B逻辑信道。若PDCP实体将可传输数据量视为属于逻辑信道A，并指示给逻辑信道A所对应MAC实体(指示给逻辑信道B对应MAC实体的属于逻辑信道B的数据量为0)，则SDAP实体也将可传输数据量视为属于逻辑信道A，并指示给逻辑信道A所对应MAC实体，即假设PDCP实体将可传输数据仅指示给MCG  MAC，则SDAP实体也将可传输数据仅指示给MCG MAC。
情形2)若PDCP实体将PDCP实体的可传输数据量视为属于DRB所包含的第二逻辑信道，且指示给第二逻辑信道对应的MAC实体，则SDAP实体向第二逻辑信道对应的MAC实体指示SDAP实体的可传输数据量。
继续上例进行描述，假设PDCP实体将可传输数据量视为属于逻辑信道B，并指示给逻辑信道B所对应MAC实体(指示给逻辑信道A对应实体的属于逻辑信道A的数据量为0)，则SDAP实体也将可传输数据量视为逻辑信道B，并指示给逻辑信道B所对应MAC实体。
情形3)若PDCP实体将PDCP实体的可传输数据量视为同时属于DRB所包含的第一逻辑信道和第二逻辑信道，且同时指示给第一逻辑信道对应的MAC实体和第二逻辑信道对应的MAC实体，则SDAP实体同时向第一逻辑信道对应的MAC实体和第二逻辑信道对应的MAC实体指示SDAP实体的可传输数据量。
继续上例进行描述，假设若PDCP实体将可传输数据量视为同时属于逻辑信道A和B，并同时指示给逻辑信道A和B所对应MAC实体(属于逻辑信道A和B的数据量相同，均为PDCP层可传输数据量)，则SDAP实体也将可传输数据量视为同时属于逻辑信道A和B，并同时指示给逻辑信道A和B所对应MAC实体。
由此可见，该实施例中，SDAP实体可以根据PDCP实体所采用的不同指示方式进行相应地指示，可应用场景多，实现方式简单。
第二种方式，SDAP实体向DRB所对应的PDCP实体指示SDAP实体的可传输数据量，PDCP实体将SDAP实体的可传输数据量作为自己可传输数据的一部分，然后按照PDCP实体的可传输数据量指示规则向确定的逻辑信道所映射的MAC实体指示PDCP实体的可传输数据量。
由此可见，该实施例可以通过两种方式向确定的逻辑信道所映射的MAC实体指示SDAP实体的可传输数据量，实现方式灵活多样。
上述实施例，通过SDAP实体向确定的逻辑信道所映射的MAC实体指示SDAP实体的可传输数据量，以用于上报BSR。与前述缓存状态的上报方法实施例相对应，本公开还提供了缓存状态的上报装置实施例。
图5是根据一示例性实施例示出的一种缓存状态的上报装置的框图，如图5所示，缓存状态的上报装置包括确定模块51和第一上报模块52。
确定模块51被配置为确定满足缓存状态报告BSR触发条件的逻辑信道或逻辑信道组。
在该实施例中，UE可以有多个逻辑信道或逻辑信道组，当某个或某些逻辑信道或逻辑信道组满足BSR触发条件时，确定满足BSR触发条件的逻辑信道或逻辑信道组的标识信息。
第一上报模块52被配置为若确定模块51确定的逻辑信道或逻辑信道组与业务数据适配协议SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR。
由于SDAP实体与DRB没有唯一确定的映射关系，因此，在确定满足BSR触发条件的逻辑信道或逻辑信道组后，需要检查满足BSR触发条件的逻辑信道或逻辑信道组是否与SDAP实体所映射的DRB对应，若满足BSR触发条件的逻辑信道或逻辑信道组与SDAP实体所映射的DRB对应，则UE向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR，也即UE上报的BSR包括映射到确定的逻辑信道或逻辑信道组的RLC实体、PDCP实体和SDAP实体的缓存状态之和。
而如果满足BSR触发条件的逻辑信道或逻辑信道组与SDAP实体所映射的DRB不对应，则UE向基站上报的BSR不包括SDAP实体的缓存的BSR。
另外，第一上报模块52还可以确定SDAP实体映射的DRB，实现方式可参见图3所示实施例。
如图5所示的装置用于实现上述如图2所示的方法流程，涉及到的相关内容描述相同，此处不赘述。
上述实施例，通过确定满足BSR触发条件的逻辑信道或逻辑信道组，并在确定的逻辑信道或逻辑信道组与SDAP实体所映射的DRB对应时，向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR，从而解决了在引入新的协议层之后上报逻辑信道或逻辑信道组的缓存状态问题。
图6是根据一示例性实施例示出的另一种缓存状态的上报装置的框图，如图6所示，在上述图5所示实施例的基础上，该装置可以包括：检测触发模块53和第二上报模块54。
检测触发模块53被配置为若检测到SDAP实体所映射的DRB发生变化，则触发BSR。
在该实施例中，如果变化的DRB影响了对应逻辑信道或逻辑信道组的缓存状态，则触发所影响的逻辑信道或逻辑信道组的BSR，即首先确定发生变化前后的DRB对应的逻辑信道或逻辑信道组，然后触发所确定的逻辑信道或逻辑信道组的BSR。
第二上报模块54被配置为向基站上报检测触发模块53触发的BSR。
在一优选实施例中，检测触发模块53可以被配置为：若确定SDAP实体有缓存数据，则在检测到SDAP实体所映射的DRB发生变化后，触发BSR。因为如果SDAP实体有缓存数据，则该SDAP实体由一个DRB重新映射到另一个DRB时，原先DRB与新DRB对应的逻辑信道或逻辑信道组的缓存状态都会发生变化，此时，首先确定发生变化前后的DRB对应的逻辑信道或逻辑信道组，然后触发所确定的逻辑信道或逻辑信道组的BSR。
上述实施例，通过在检测到SDAP实体所映射的DRB发生变化时，触发BSR，并上报触发的BSR，从而解决了SDAP实体映射的DRB发生变化时逻辑信道或逻辑信道组的缓存状态上报问题。
图7A是根据一示例性实施例示出的另一种缓存状态的上报装置的框图，如图7A所示，在上述图6所示实施例的基础上，检测触发模块53可以包括：确定子模块531和触发子模块532。
确定子模块531被配置为确定发生变化前后的DRB对应的逻辑信道或逻辑信道组。
触发子模块532被配置为触发确定子模块531所确定的逻辑信道或逻辑信道组的BSR。
上述实施例，通过确定发生变化前后的DRB对应的逻辑信道或逻辑信道组，然后触发所确定的逻辑信道或逻辑信道组的BSR，从而实现SDAP实体所映射的DRB发生变化时触发BSR。
图7B是根据一示例性实施例示出的另一种缓存状态的上报装置的框图，如图7B所示，在上述图5所示实施例的基础上，该装置还可以包括：指示模块55。
指示模块55被配置为在第一上报模块52向基站上报包括映射到确定的逻辑信道或逻辑信道组的SDAP实体的缓存的BSR时，向确定的逻辑信道所映射的媒体接入控制MAC实体指示SDAP实体的可传输数据量。
其中，SDAP实体的可传输数据量(data available for transmission)可以包括以下 至少一项：a)SDAP SDU，如果其还未被SDAP层处理；b)SDAP PDU，如果SDAP SDU已经被处理生成PDU；c)SDAP控制PDU(如果标准制定了控制PDU)。
在该实施例中，指示模块55位于SDAP层，即SDAP实体向确定的逻辑信道所映射的媒体接入控制MAC实体指示SDAP实体的可传输数据量。
上述实施例，通过SDAP实体向确定的逻辑信道所映射的MAC实体指示SDAP实体的可传输数据量，以用于上报BSR。
图7C是根据一示例性实施例示出的另一种缓存状态的上报装置的框图，如图7C所示，在上述图7B所示实施例的基础上，指示模块55可以包括：第一指示子模块551。
第一指示子模块551被配置为按照DRB所对应的PDCP实体的可传输数据量指示规则向确定的逻辑信道所映射的MAC实体指示SDAP实体的可传输数据量。
上述实施例，可以按照DRB所对应的PDCP实体的可传输数据量指示规则向确定的逻辑信道所映射的MAC实体指示SDAP实体的可传输数据量，实现方式简单。
图7D是根据一示例性实施例示出的另一种缓存状态的上报装置的框图，如图7D所示，在上述图7B所示实施例的基础上，指示模块55可以包括：第二指示子模块552和第三指示子模块553。
第二指示子模块552被配置为向DRB所对应的PDCP实体指示SDAP实体的可传输数据量。
其中，第二指示子模块552位于SDAP层。
第三指示子模块553被配置为将第二指示子模块552指示的SDAP实体的可传输数据量作为自己可传输数据的一部分，然后按照PDCP实体的可传输数据量指示规则向确定的逻辑信道所映射的MAC实体指示PDCP实体的可传输数据量。
其中，第三指示子模块553位于PDCP层。
上述实施例，通过向DRB所对应的PDCP实体指示SDAP实体的可传输数据量，将第二指示子模块指示的SDAP实体的可传输数据量作为自己可传输数据的一部分，然后按照PDCP实体的可传输数据量指示规则向确定的逻辑信道所映射的MAC实体指示PDCP实体的可传输数据量，实现方式简单。
图7E是根据一示例性实施例示出的另一种缓存状态的上报装置的框图，如图7E所示，在上述图7C所示实施例的基础上，第一指示子模块551可以包括：第一指示单元 5511、第二指示单元5512或者第三指示单元5513。
第一指示单元5511被配置为若PDCP实体将PDCP实体的可传输数据量视为属于DRB所包含的第一逻辑信道，且指示给第一逻辑信道对应的MAC实体，则向第一逻辑信道对应的MAC实体指示SDAP实体的可传输数据量。
例如，若该DRB包含一个逻辑信道，假设称为A逻辑信道；若该DRB包含两个逻辑信道，假设分别称为A逻辑信道和B逻辑信道。若PDCP实体将可传输数据量视为属于逻辑信道A，并指示给逻辑信道A所对应MAC实体(指示给逻辑信道B对应MAC实体的属于逻辑信道B的数据量为0)，则SDAP实体也将可传输数据量视为属于逻辑信道A，并指示给逻辑信道A所对应MAC实体，即假设PDCP实体将可传输数据仅指示给MCG MAC，则SDAP实体也将可传输数据仅指示给MCG MAC。
第二指示单元5512被配置为若PDCP实体将PDCP实体的可传输数据量视为属于DRB所包含的第二逻辑信道，且指示给第二逻辑信道对应的MAC实体，则向第二逻辑信道对应的MAC实体指示SDAP实体的可传输数据量。
继续上例进行描述，假设PDCP实体将可传输数据量视为属于逻辑信道B，并指示给逻辑信道B所对应MAC实体(指示给逻辑信道A对应实体的属于逻辑信道A的数据量为0)，则SDAP实体也将可传输数据量视为逻辑信道B，并指示给逻辑信道B所对应MAC实体。
第三指示单元5513被配置为若PDCP实体将PDCP实体的可传输数据量视为同时属于DRB所包含的第一逻辑信道和第二逻辑信道，且同时指示给第一逻辑信道对应的MAC实体和第二逻辑信道对应的MAC实体，则同时向第一逻辑信道对应的MAC实体和第二逻辑信道对应的MAC实体指示SDAP实体的可传输数据量。
继续上例进行描述，假设若PDCP实体将可传输数据量视为同时属于逻辑信道A和B，并同时指示给逻辑信道A和B所对应MAC实体(属于逻辑信道A和B的数据量相同，均为PDCP层可传输数据量)，则SDAP实体也将可传输数据量视为同时属于逻辑信道A和B，并同时指示给逻辑信道A和B所对应MAC实体。
上述实施例中，SDAP实体可以根据PDCP实体所采用的不同指示方式进行相应地指示，可应用场景多，实现方式简单。
关于上述实施例中的装置，其中各个模块、子模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
图8是根据一示例性实施例示出的一种适用于缓存状态的上报装置的框图。例如，装置800可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图8，装置800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制装置800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理元件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理部件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在设备800的操作。这些数据的示例包括用于在装置800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为装置800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为装置800生成、管理和分配电力相关联的组件。
多媒体组件808包括在装置800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当设备800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当装置800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦 克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为装置800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如组件为装置800的显示器和小键盘，传感器组件814还可以检测装置800或装置800一个组件的位置改变，用户与装置800接触的存在或不存在，装置800方位或加速/减速和装置800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于装置800和其他设备之间有线或无线方式的通信。装置800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信部件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信部件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由装置800的处理器820执行以完成上述方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实 施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本发明实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (22)

  1. 一种缓存状态的上报方法，其特征在于，所述方法包括：
    确定满足缓存状态报告BSR触发条件的逻辑信道或逻辑信道组；
    若确定的所述逻辑信道或所述逻辑信道组与业务数据适配协议SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    若检测到SDAP实体所映射的DRB发生变化，则触发所述BSR；
    向基站上报所述BSR。
  3. 根据权利要求2所述的方法，其特征在于，所述若检测到SDAP实体所映射的DRB发生变化，则触发所述BSR，包括：
    若确定所述SDAP实体有缓存数据，则在检测到所述SDAP实体所映射的DRB发生变化后，触发所述BSR。
  4. 根据权利要求2所述的方法，其特征在于，所述触发所述BSR，包括：
    确定发生变化前后的DRB对应的逻辑信道或逻辑信道组；
    触发所确定的所述逻辑信道或所述逻辑信道组的BSR。
  5. 根据权利要求3所述的方法，其特征在于，所述触发所述BSR，包括：
    确定发生变化前后的DRB对应的逻辑信道或逻辑信道组；
    触发所确定的所述逻辑信道或所述逻辑信道组的BSR。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR时，所述SDAP实体向确定的所述逻辑信道所映射的媒体接入控制MAC实体指示所述SDAP实体的可传输数据量。
  7. 根据权利要求6所述的方法，其特征在于，所述SDAP实体向确定的所述逻辑信道所映射的MAC实体指示所述SDAP实体的可传输数据量，包括：
    所述SDAP实体按照所述DRB所对应的PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述SDAP实体的可传输数据量。
  8. 根据权利要求6所述的方法，其特征在于，所述SDAP实体向确定的所述逻辑信道所映射的MAC实体指示可传输数据量，包括：
    所述SDAP实体向所述DRB所对应的PDCP实体指示所述SDAP实体的可传输数据量；
    所述PDCP实体将所述SDAP实体的可传输数据量作为自己可传输数据的一部分，然后按照所述PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述PDCP实体的可传输数据量。
  9. 根据权利要求7所述的方法，其特征在于，所述SDAP实体按照所述DRB所对应的PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述SDAP实体的可传输数据量，包括：
    若所述PDCP实体将所述PDCP实体的可传输数据量视为属于所述DRB所包含的第一逻辑信道，且指示给所述第一逻辑信道对应的MAC实体，则所述SDAP实体向所述第一逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量；或者
    若所述PDCP实体将所述PDCP实体的可传输数据量视为属于所述DRB所包含的第二逻辑信道，且指示给所述第二逻辑信道对应的MAC实体，则所述SDAP实体向所述第二逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量；或者
    若所述PDCP实体将所述PDCP实体的可传输数据量视为同时属于所述DRB所包含的第一逻辑信道和第二逻辑信道，且同时指示给所述第一逻辑信道对应的MAC实体和所述第二逻辑信道对应的MAC实体，则所述SDAP实体同时向所述第一逻辑信道对应的MAC实体和所述第二逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量。
  10. 根据权利要求6-9任一项所述的方法，其特征在于，所述SDAP实体的可传输数据量包括SDAP服务数据单元SDU、SDAP包数据单元PDU和SDAP控制PDU中的至少一项。
  11. 一种缓存状态的上报装置，其特征在于，所述装置包括：
    确定模块，被配置为确定满足缓存状态报告BSR触发条件的逻辑信道或逻辑信道组；
    第一上报模块，被配置为若所述确定模块确定的所述逻辑信道或所述逻辑信道组与业务数据适配协议SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR。
  12. 根据权利要求11所述的装置，其特征在于，所述装置还包括：
    检测触发模块，被配置为若检测到SDAP实体所映射的DRB发生变化，则触发所述BSR；
    第二上报模块，被配置为向基站上报所述检测触发模块触发的所述BSR。
  13. 根据权利要求12所述的装置，其特征在于，所述检测触发模块，被配置为：
    若确定所述SDAP实体有缓存数据，则在检测到所述SDAP实体所映射的DRB发生变化后，触发所述BSR。
  14. 根据权利要求12所述的装置，其特征在于，所述检测触发模块包括：
    确定子模块，被配置为确定发生变化前后的DRB对应的逻辑信道或逻辑信道组；
    触发子模块，被配置为触发所述确定子模块所确定的所述逻辑信道或所述逻辑信道组的BSR。
  15. 根据权利要求13所述的装置，其特征在于，所述检测触发模块包括：
    确定子模块，被配置为确定发生变化前后的DRB对应的逻辑信道或逻辑信道组；
    触发子模块，被配置为触发所述确定子模块所确定的所述逻辑信道或所述逻辑信道组的BSR。
  16. 根据权利要求11所述的装置，其特征在于，所述装置还包括：
    指示模块，被配置为在所述第一上报模块向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR时，向确定的所述逻辑信道所映射的媒体接入控制MAC实体指示所述SDAP实体的可传输数据量。
  17. 根据权利要求16所述的装置，其特征在于，所述指示模块包括：
    第一指示子模块，被配置为按照所述DRB所对应的PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述SDAP实体的可传输数据量。
  18. 根据权利要求16所述的装置，其特征在于，所述指示模块包括：
    第二指示子模块，被配置为向所述DRB所对应的PDCP实体指示所述SDAP实体的可传输数据量；
    第三指示子模块，被配置为将所述第二指示子模块指示的所述SDAP实体的可传输数据量作为自己可传输数据的一部分，然后按照所述PDCP实体的可传输数据量指示规则向确定的所述逻辑信道所映射的MAC实体指示所述PDCP实体的可传输数据量。
  19. 根据权利要求17所述的装置，其特征在于，所述第一指示子模块包括：
    第一指示单元，被配置为若所述PDCP实体将所述PDCP实体的可传输数据量视为属于所述DRB所包含的第一逻辑信道，且指示给所述第一逻辑信道对应的MAC实体，则向所述第一逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量；或者
    第二指示单元，被配置为若所述PDCP实体将所述PDCP实体的可传输数据量视 为属于所述DRB所包含的第二逻辑信道，且指示给所述第二逻辑信道对应的MAC实体，则向所述第二逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量；或者
    第三指示单元，被配置为若所述PDCP实体将所述PDCP实体的可传输数据量视为同时属于所述DRB所包含的第一逻辑信道和第二逻辑信道，且同时指示给所述第一逻辑信道对应的MAC实体和所述第二逻辑信道对应的MAC实体，则同时向所述第一逻辑信道对应的MAC实体和所述第二逻辑信道对应的MAC实体指示所述SDAP实体的可传输数据量。
  20. 根据权利要求16-19任一项所述的装置，其特征在于，所述SDAP实体的可传输数据量包括SDAP服务数据单元SDU、SDAP包数据单元PDU和SDAP控制PDU中的至少一项。
  21. 一种用户设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    确定满足缓存状态报告BSR触发条件的逻辑信道或逻辑信道组；
    若确定的所述逻辑信道或所述逻辑信道组与业务数据适配协议SDAP实体所映射的DRB对应，则向基站上报包括映射到确定的所述逻辑信道或所述逻辑信道组的SDAP实体的缓存的BSR。
  22. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现权利要求1所述方法的步骤。
PCT/CN2017/099532 2017-04-25 2017-08-29 缓存状态的上报方法及装置 Ceased WO2018196243A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP17907455.4A EP3606148B1 (en) 2017-04-25 2017-08-29 Method and device for reporting buffer state
US16/499,239 US11012887B2 (en) 2017-04-25 2017-08-29 Method and device for reporting buffer state
CN201780001386.XA CN109121467B (zh) 2017-04-25 2017-08-29 缓存状态的上报方法及装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2017/081793 2017-04-25
PCT/CN2017/081793 WO2018195752A1 (zh) 2017-04-25 2017-04-25 缓存状态的上报方法及装置

Publications (1)

Publication Number Publication Date
WO2018196243A1 true WO2018196243A1 (zh) 2018-11-01

Family

ID=60461759

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2017/081793 Ceased WO2018195752A1 (zh) 2017-04-25 2017-04-25 缓存状态的上报方法及装置
PCT/CN2017/099532 Ceased WO2018196243A1 (zh) 2017-04-25 2017-08-29 缓存状态的上报方法及装置

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/081793 Ceased WO2018195752A1 (zh) 2017-04-25 2017-04-25 缓存状态的上报方法及装置

Country Status (4)

Country Link
US (1) US11012887B2 (zh)
EP (1) EP3606148B1 (zh)
CN (2) CN107439037A (zh)
WO (2) WO2018195752A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600203A (zh) * 2018-11-29 2019-04-09 西安电子科技大学 一种sdap pdu中携带重映射节点包序列号的方法

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632889B (zh) * 2017-03-24 2024-06-14 中兴通讯股份有限公司 一种缓冲区状态报告的触发方法、装置、终端
US20180324631A1 (en) * 2017-05-05 2018-11-08 Mediatek Inc. Using sdap headers for handling of as/nas reflective qos and to ensure in-sequence packet delivery during remapping in 5g communication systems
WO2018226024A1 (ko) * 2017-06-05 2018-12-13 삼성전자 주식회사 차세대 이동통신 시스템에서 pdcp 장치 및 sdap 장치를 설정하는 방법 및 장치
KR102359746B1 (ko) * 2017-06-05 2022-02-10 삼성전자 주식회사 차세대 이동통신 시스템에서 인액티브 모드 단말이 데이터를 전송하는 방법 및 장치
KR102394123B1 (ko) * 2017-06-16 2022-05-04 삼성전자 주식회사 차세대 이동 통신 시스템에서 복수 개의 스케쥴링 요청을 전송하는 방법 및 장치
CN109548194B (zh) * 2017-08-17 2021-07-16 维沃移动通信有限公司 一种数据处理方法、发送端和接收端
WO2019139376A1 (en) * 2018-01-10 2019-07-18 Samsung Electronics Co., Ltd. Method and apparatus for wireless communication in wireless communication system
CN110072253B (zh) * 2018-01-22 2020-12-18 华为技术有限公司 通信方法、装置和系统
JP7100135B6 (ja) 2018-02-06 2022-09-30 オッポ広東移動通信有限公司 データ伝送制御方法および関連製品
CN109863733B (zh) * 2018-02-08 2020-05-08 Oppo广东移动通信有限公司 动态指示qfi的方法和用户设备
CN111526542A (zh) 2018-02-13 2020-08-11 Oppo广东移动通信有限公司 一种QoS流的重映射方法及装置、计算机存储介质
EP3625987B1 (en) * 2018-02-14 2021-07-07 LG Electronics Inc. Method and apparatus for modifying mapping rule
US20190349805A1 (en) * 2018-05-11 2019-11-14 Mediatek Inc. User equipments and methods for handling an update on quality of service (qos) flow to data radio bearer (drb) mapping
WO2020029414A1 (zh) * 2018-08-07 2020-02-13 Oppo广东移动通信有限公司 无线通信方法、通信设备、芯片和通信系统
CN110972337B (zh) * 2018-09-29 2021-09-14 中国移动通信有限公司研究院 数据传输方法、装置、系统、sdap实体及存储介质
KR20210113591A (ko) * 2019-01-14 2021-09-16 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 데이터 흐름 처리 방법, 기기 및 저장 매체
CN115551000A (zh) * 2021-06-30 2022-12-30 展讯通信（上海）有限公司 触觉数据的传输方法及相关产品
CN116418894A (zh) * 2022-01-10 2023-07-11 联发科技（新加坡）私人有限公司 业务处理方法和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102369778A (zh) * 2009-04-03 2012-03-07 松下电器产业株式会社 移动通信系统中的缓冲状态报告
CN104349342A (zh) * 2013-08-01 2015-02-11 中兴通讯股份有限公司 业务管理方法和装置
CN104363598A (zh) * 2014-11-25 2015-02-18 电信科学技术研究院 一种drb映射方法及装置
WO2017034232A1 (en) * 2015-08-21 2017-03-02 Lg Electronics Inc. Method for triggering a bsr for sidelink data in a d2d communication system and device therefor

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8265640B2 (en) * 2008-05-07 2012-09-11 Qualcomm Incorporated BSR prohibit timer
US9264930B2 (en) * 2012-11-07 2016-02-16 Qualcomm Incorporated Buffer status reporting and logical channel prioritization in multiflow operation
WO2015062085A1 (en) * 2013-11-01 2015-05-07 Nokia Technologies Oy Method and apparatus for handling buffer status reporting and scheduling request with dual connectivity

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102369778A (zh) * 2009-04-03 2012-03-07 松下电器产业株式会社 移动通信系统中的缓冲状态报告
CN104349342A (zh) * 2013-08-01 2015-02-11 中兴通讯股份有限公司 业务管理方法和装置
CN104363598A (zh) * 2014-11-25 2015-02-18 电信科学技术研究院 一种drb映射方法及装置
WO2017034232A1 (en) * 2015-08-21 2017-03-02 Lg Electronics Inc. Method for triggering a bsr for sidelink data in a d2d communication system and device therefor

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3GPP TS 37.324 specification v1.1.1", 3GPP TSG-RAN WG2 MEETING #100 R2-1713458, 22 November 2017 (2017-11-22), XP055528910 *
See also references of EP3606148A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600203A (zh) * 2018-11-29 2019-04-09 西安电子科技大学 一种sdap pdu中携带重映射节点包序列号的方法
CN109600203B (zh) * 2018-11-29 2021-09-14 西安电子科技大学 一种sdap pdu中携带重映射节点包序列号的方法

Also Published As

Publication number Publication date
US20210112442A1 (en) 2021-04-15
WO2018195752A1 (zh) 2018-11-01
EP3606148A4 (en) 2020-02-26
US11012887B2 (en) 2021-05-18
EP3606148B1 (en) 2025-10-01
CN109121467B (zh) 2022-02-01
CN107439037A (zh) 2017-12-05
CN109121467A (zh) 2019-01-01
EP3606148A1 (en) 2020-02-05

Similar Documents

Publication Publication Date Title
WO2018196243A1 (zh) 缓存状态的上报方法及装置
US11133913B2 (en) Method and device for turning off and turning on packet data convergence protocol packet replication function
CN108496385B (zh) 信息上报方法及装置和基于带宽部分的操作方法及装置
US11343704B2 (en) Method and apparatus for assigning identifier, base station and user equipment
WO2019080008A1 (zh) 增补上行载波配置方法及装置和调度资源分配方法及装置
WO2018000336A1 (zh) Rrc连接建立方法及设备
WO2018176231A1 (zh) 数据传输方法及装置、数据接收方法及装置、电子设备
WO2018076820A1 (zh) 一种无线链路失败的处理方法和装置
WO2018129940A1 (zh) 用户设备的状态控制方法、装置、用户设备和基站
WO2018232602A1 (zh) 功能配置方法及装置、消息发送方法及装置和用户设备
US20210144712A1 (en) Method and apparatus for reporting buffer status report
CN108702763B (zh) 前导码和调度请求的发送方法及装置
WO2019033399A1 (zh) 反射业务质量配置的方法及装置和信息发送方法及装置
WO2019127438A9 (zh) 随机接入失败处理方法和装置
WO2018232559A1 (zh) 数据处理方法及装置、用户设备和计算机可读存储介质
WO2018196102A1 (zh) 信息传递方法、装置及计算机可读存储介质
WO2018201439A1 (zh) 随机接入方法及装置、用户设备和计算机可读存储介质
US11665586B2 (en) Method and apparatus for data transmission, electronic device and computer readable storage medium
CN110800245B (zh) 波束失败请求发送方法、装置和电子设备
WO2019153246A1 (zh) 触发保持方法和触发保持装置
US11438924B2 (en) Message sending methods and apparatuses, and resource allocating methods and apparatuses
WO2019140692A1 (zh) 信息配置方法及装置、接收功率的确定方法及装置和基站
WO2018086097A1 (zh) 通信方法及装置
CN110268779B (zh) 直连链路数据发送和直连链路资源配置方法以及装置
WO2019113757A1 (zh) 确定用户设备移动速度的方法及装置、基站和用户设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17907455

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017907455

Country of ref document: EP

Effective date: 20191023

WWG Wipo information: grant in national office

Ref document number: 2017907455

Country of ref document: EP