TECHNICAL FIELD

[0001] This invention relates generally to buffer status reporting and, more specifically, relates to introducing a new trigger for a BSR when a QoS flow remapping is ordered either directly via RRC signaling or indirectly via Reflective QoS.

BACKGROUND

[0002] This section is intended to provide a background or context to the invention disclosed below. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived, implemented or described. Therefore, unless otherwise explicitly indicated herein, what is described in this section is not prior art to the description in this application and is not admitted to be prior art by inclusion in this section.

[0003] Since Rel-8, to assist the scheduler, an eNB can configure UEs to send Buffer Status Reports (BSR) and Power Headroom Reports (PHR) in uplink. BSR indicates the amount of data the UE has available for transmission while PHR provides the eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission. BSR are typically used by the eNB to choose an appropriate transport block size while PHR are typically used to select and appropriate coding scheme (MCS) and number allocated Physical Resource Blocks (PRBs). Among other conditions, in E-UTRA a buffer status report (BSR) is triggered in the UE: if data arrives in the UE buffer which has higher priority than the data already available for transmission; if new data arrives in an empty UE buffer.

[0004] If the UE has no allocation available on the Physical Uplink Shared Channel (PUSCH) for the TTI where the BSR is triggered, a Scheduling Request (SR) is then triggered. The SR is transmitted on the Physical Uplink Control Channel (PUCCH) using dedicated resources which are allocated on a UE basis with a certain periodicity. Details on the triggering of SRs and BSRs can be found in Sections 5.4.4 and 5.4.5 of 3GPP TS 36.321 and 3GPP TS 38.321. Note that BSR report the buffer status of a logical channel group (LCG). Logical channels can be divided in up to 4 different LCGs based on priority of data, etc. Also note that BSRs/SRs can also be triggered based on configurations of periodical BSR.

[0005] One of the goals of NR is to allow a more flexible QoS (Quality of Service) Framework where EPS bearers disappear and flow can be dynamically mapped onto radio bearers by the RAN [see TS 38.300]

[0006] As described in the next several paragraphs, TS 38.300 states that the 5G QoS model is based on QoS Flows (see 3GPP TS 23.501) and supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (non-GBR QoS Flows). At NAS level (see 3GPP TS 23.501), the QoS flow is thus the finest granularity of QoS differentiation in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over NG-U.

[0007] The QoS architecture in NG-RAN, both for NR connected to 5GC and for E- UTRA connected to 5GC, is depicted in the QoS architecture shown in FIG. 1 and described as follows:

• For each UE, 5GC establishes one or more PDU Sessions;

• For each UE, the NG-RAN establishes one or more Data Radio Bearers (DRB) per PDU Session; the NG-RAN maps packets belonging to different PDU sessions to different DRBs; hence, the NG-RAN establishes at least one default DRB for each PDU Session;

• NAS level packet filters in the UE and in the 5GC associate UL and DL packets with QoS Flows;

• AS-level mapping rules in the UE and in the NG-RAN associate UL and DL QoS Flows with DRBs.

[0008] NG-RAN and 5GC ensure quality of service (e.g. reliability and target delay) by mapping packets to appropriate QoS Flows and DRBs. Hence there is a 2-step mapping of IP- flows to QoS flows (NAS) and from QoS flows to DRBs (Access Stratum).

[0009] At NAS level, a QoS flow is characterized by a QoS profile provided by 5GC to NG-RAN and QoS rule(s) provided by 5GC to the UE. The QoS profile is used by NG-RAN to determine the treatment on the radio interface while the QoS rules dictates the mapping between uplink User Plane traffic and QoS flows to the UE. A QoS flow may either be "GBR" or "Non- GBR" depending on its profile. The QoS profile of a QoS flow contains QoS parameters, for instance (see 3GPP TS 23.501):

For each QoS flow:

• A 5G QoS Identifier (5QI);

• An Allocation and Retention Priority (ARP).

In case of a GBR QoS flow only:

• Guaranteed Flow Bit Rate (GFBR) for both uplink and downlink;

• Maximum Flow Bit Rate (MFBR) for both uplink and downlink;

• Maximum Packet Loss Rate for both uplink and downlink.

In case of Non-GBR QoS only:

• Reflective QoS Attribute (RQA): the RQA, when included, indicates that some (not necessarily all) traffic carried on this QoS flow is subject to reflective quality of service (RQoS) at NAS.

[0010] In addition, an Aggregate Maximum Bit Rate is associated to each PDU session (Session- AMBR) and to each UE (UE-AMBR). The Session-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows for a specific PDU Session. The UE-AMBR limits the aggregate bit rate that can be expected to be provided across all Non- GBR QoS Flows of a UE.

[0011] The 5QI is associated to QoS characteristics giving guidelines for setting node specific parameters for each QoS Flow. Standardized or pre-configured 5G QoS characteristics are derived from the 5QI value and are not explicitly signaled. Signaled QoS characteristics are included as part of the QoS profile. The QoS characteristics consist for instance of (see 3GPP TS 23.501 [3]):

• Resource Type (GBR, delay critical GBR or Non-GBR);

• Priority level;

• Packet Delay Budget;

• Packet Error Rate;

• Averaging window;

• Maximum Data Burst Volume.

[0012] At Access Stratum level, the data radio bearer (DRB) defines the packet treatment on the radio interface (Uu). A DRB serves packets with the same packet forwarding treatment. The QoS flow to DRB mapping by NG-RAN is based on QFI and the associated QoS profiles (i.e. QoS parameters and QoS characteristics). Separate DRBs may be established for QoS flows requiring different packet forwarding treatment, or several QoS Flows belonging to the same PDU session can be multiplexed in the same DRB.

[0013] In the uplink, the NG-RAN may control the mapping of QoS Flows to DRB in two different ways:

• Reflective mapping: for each DRB, the UE monitors the QFI(s) of the downlink packets and applies the same mapping in the uplink; that is, for a DRB, the UE maps the uplink packets belonging to the QoS flows(s) corresponding to the QFI(s) and PDU Session observed in the downlink packets for that DRB. To enable this reflective mapping, the NG-RAN marks downlink packets over Uu with QFI.

• Explicit Configuration: besides the reflective mapping, the NG-RAN may configure by RRC an uplink "QoS Flow to DRB mapping".

The UE shall always apply the latest update of the mapping rules regardless of whether it is performed via reflecting mapping or explicit configuration.

[0014] In the downlink, the QFI is signaled by NG-RAN over Uu for the purpose of RQoS and if neither NG-RAN nor the NAS (as indicated by the RQA) intend to use reflective mapping for the QoS flow(s) carried in a DRB, no QFI is signaled for that DRB over Uu. In the uplink, NG-RAN can configure the UE to signal QFI over Uu.

[0015] For each PDU session, a default DRB is configured. If an incoming UL packet matches neither an RRC configured nor a reflective "QoS Flow ID to DRB mapping", the UE shall map that packet to the default DRB of the PDU session.

[0016] Within each PDU session, it is up to NG-RAN how to map multiple QoS flows to a DRB. The NG-RAN may map a GBR flow and a non-GBR flow, or more than one GBR flow to the same DRB, but mechanisms to optimize these cases are not within the scope of standardization. The timing of establishing non-default DRB(s) between NG-RAN and UE for QoS flow configured during establishing a PDU session can be different from the time when the PDU session is established. As TS 38.300 concludes, it is up to NG-RAN when non-default DRBs are established. [0017] When a QoS flow is relocated from one DRB to another, in-order delivery necessitates buffering of fresh data on the new DRB for as long as data remains on the initial one. Such buffering can either take place at the receiver or at the transmitter [R2-1800539] In the uplink, it is possible to avoid involving the UE if buffering takes place in the receiver.

However, without an end marker provided by the UE, the network needs to rely on a timer. Such timer would potentially delay re-ordering and make QoS flow re -mapping un-necessarily inefficient [R2- 1802504] Therefore, 3GPP TSG RAN WG2 has agreed to introduce an end- marker in the uplink.

[0018] The current invention moves beyond current techniques and instrumentation.

[0019] Abbreviations that may be found in the specification and/or the figures are either defined in the text and/or defined as follows:

[0020] 3 GPP third generation partnership project;

[0021] 5G fifth generation;

[0022] 5GC 5G Core network;

[0023] AMF Access and Mobility management Function;

[0024] BSR Buffer Status Report;

[0025] CU Central Unit;

[0026] DU Distributed Unit;

[0027] eNB (or eNodeB) evolved Node B (e.g., an LTE base station);

[0028] gNB (or gNodeB) base station for 5G/NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC;

[0029] EN-DC E-UTRA-NR dual connectivity;

[0030] en-gNB or En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as secondary node in EN-DC;

[0031] E-UTRA evolved Universal Terrestrial Radio Access, i.e., the LTE radio access technology;

[0032] I/F Interface;

[0033] LTE Long Term Evolution; [0034] MAC Medium Access Control;

[0035] MME Mobility Management Entity;

[0036] NCE Network Control Element;

[0037] ng orNG New Generation;

[0038] ng-eNB orNG-eNB new generation eNB;

[0039] NR New Radio;

[0040] N/W or NW Network;

[0041] PDCP Packet Data Convergence Protocol;

[0042] PHY Physical layer;

[0043] QoS Quality of Service;

[0044] RAN Radio Access Network;

[0045] Rel Release;

[0046] RLC Radio Link Control;

[0047] RRH Remote Radio Head;

[0048] RRC Radio Resource Control;

[0049] RU Radio Unit;

[0050] Rx Receiver;

[0051] SDAP Service Data Adaptation Protocol;

[0052] SGW Serving Gateway;

[0053] SMF Session Management Function;

[0054] SR Scheduling Request;

[0055] TS Technical Specification;

[0056] Tx transmitter;

[0057] UE User Equipment (e.g., a wireless, typically mobile device);

[0058] UPF User Plane Function.

BRIEF SUMMARY

[0059] Herein a new BSR trigger is introduced such that, when a QoS flow remapping is ordered either directly via RRC signaling or indirectly via Reflective QoS, a BSR is triggered in all cell groups. Alternatively, the trigger could be restricted to the cell group(s) handling the old bearer and the new one, or just to the cell group handing the old bearer.

[0060] An example of an embodiment of the current invention is a method that comprises communicating, by a RAN with a UE connected to the at least one cell, data on a first bearer within a cell served by the RAN; sending a Quality of Service flow remapping order to the UE to move data to a second bearer, triggering the UE to produce a Buffer Status Report; receiving the BSR indicating the UE’s buffer at QoS flow remapping; determining the second bearer to schedule remaining data based on the BSR unless the BSR indicates that data remains in the first bearer, where in response to data remaining in the first bearer: allocating grants to the UE to transmit on the first bearer; and receiving an end marker from the UE once no data remains for the QoS flow on the first bearer. An example of another embodiment of the current invention is a computer program product embodied on a non-transitory computer-readable medium in which a computer program is stored that, when being executed by a computer, is configured to provide instructions to control or carry out this method.

[0061] An example of another embodiment of the current invention, which can be referred to as item 6, is a method that comprises communicating, by a UE connected to at least one serving cell of a RAN, data of at least one QoS flow on a first bearer; receiving a remapping order from the RAN of a QoS flow from a first bearer to a second bearer, wherein the remapping triggers the UE to produce a Buffer Status Report; and transmitting the BSR to the RAN indicating the UE's buffer at QoS flow remapping. An example of another embodiment of the current invention is a computer program product embodied on a non-transitory computer- readable medium in which a computer program is stored that, when being executed by a computer, is configured to provide instructions to control or carry out this method.

[0062] An example of another embodiment of the current invention, which can be referred to as item 7, is an apparatus, that comprises at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following: communicating with a UE connected to the at least one cell, data on a first bearer within a cell served by the apparatus; sending a Quality of Service flow remapping order to the UE to move data to a second bearer, triggering the UE to produce a Buffer Status Report;

receiving the BSR indicating the UE’s buffer at QoS flow remapping; determining the second bearer to schedule remaining data based on the BSR unless the BSR indicates that data remains in the first bearer, where in response to data remaining in the first bearer: allocating grants to the UE to transmit on the first bearer; and receiving an end marker from the UE once no data remains for the QoS flow on the first bearer.

[0063] An example of another embodiment of the current invention, which can be referred to as item 12, is an apparatus that comprises at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following: communicating, via at least one serving cell of a RAN, data of at least one QoS flow on a first bearer; receiving a remapping order from the RAN of a QoS flow from a first bearer to a second bearer, wherein the remapping triggers the apparatus to produce a Buffer Status Report; and transmitting the BSR to the RAN indicating the apparatus’s buffer at QoS flow remapping.

[0064] An example of another embodiment of the current invention, which can be referred to as item 19, is an apparatus that comprises means for communicating with a UE connected to the at least one cell, data on a first bearer within a cell served by the apparatus; means for sending a Quality of Service flow remapping order to the UE to move data to a second bearer, triggering the UE to produce a Buffer Status Report; means for receiving the BSR indicating the UE’s buffer at QoS flow remapping; means for determining the second bearer to schedule remaining data based on the BSR unless the BSR indicates that data remains in the first bearer, where in response to data remaining in the first bearer further that comprises means for allocating grants to the UE to transmit on the first bearer; and means for receiving an end marker from the UE once no data remains for the QoS flow on the first bearer.

[0065] An example of another embodiment of the current invention, which can be referred to as item 20, is an apparatus that comprises means for communicating, via at least one serving cell of a RAN, data of at least one QoS flow on a first bearer; means for receiving a remapping order from the RAN of a QoS flow from a first bearer to a second bearer, wherein the remapping triggers the apparatus to produce a Buffer Status Report; and means for transmitting the BSR to the RAN indicating the apparatus’s buffer at QoS flow remapping.

[0066] This section is intended to include examples and is not intended to be limiting. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] In the attached Drawing Figures:

[0068] FIG. 1 is a block diagram of exemplary QoS architecture in NG-RAN.

[0069] FIG. 2 is a block diagram of one possible and non-limiting exemplary system in which the exemplary embodiments may be practiced;

[0070] FIG. 3 is a logic flow diagram for a RAN concerning a trigger for a BSR when a QoS flow remapping is ordered and illustrates the operation of an exemplary method or methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments; and

[0071] FIGS. 4 is logic flow diagrams for a UE concerning a trigger for a BSR when a QoS flow remapping is ordered and illustrate the operation of exemplary methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments.

DETAIFED DESCRIPTION OF THE DRAWINGS

[0072] The word“exemplary” is used herein to mean“serving as an example, instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described in this Detailed Description are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims.

[0073] The exemplary embodiments describe techniques for the new BSR trigger is introduced herein. In response to a QoS flow remapping being ordered, either directly via RRC signaling or indirectly via Reflective QoS, a BSR is triggered in all cell groups. The trigger could be restricted to the cell group(s) handling the old bearer and the new one, alternatively, or also just to the cell group handing the old bearer.

[0074] Additional description of these techniques is presented after a system into which the exemplary embodiments may be used is described.

[0075] Turning to FIG. 2, this figure shows a block diagram of one possible and non limiting exemplary system in which the exemplary embodiments may be practiced. A user equipment (UE) 1 10, radio access network (RAN) node 170, and network control element(s) (NCE(s)) 190 are illustrated. In FIG. 2, a user equipment (EGE) 110 is in wireless communication with a wireless network 100. A EGE is a wireless, typically mobile device that can access a wireless network. The EGE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127.

[0076] Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123.

[0077] The EGE 110 includes a YYY module 140, comprising one of or both parts 140-1 and/or 140-2, which may be implemented in a number of ways. The YYY module 140 may be implemented in hardware as YYY module 140-1, such as being implemented as part of the one or more processors 120. The YYY module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the YYY module 140 may be implemented as YYY module 140-2, which is implemented as computer program code 123 and is executed by the one or more processors 120.

[0078] For instance, the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The EGE 1 10 communicates with RAN node 170 via a wireless link 11 1.

[0079] The RAN node 170 is a base station that provides access by wireless devices such as the EGE 1 10 to the wireless network 100. The RAN node 170 may be, for instance, a base station for 5G, also called New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or an ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the EGE, and connected via the NG interface to a 5GC (e.g., the NCE(s) 190). The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the ETE, and connected via the NG interface to the 5GC. The NG-RAN node may include multiple gNBs, which may also include a central unit (CET) (gNB- CU) 196 and distributed unit(s) (DETs) (gNB-DETs), ofwhich DET 195 is shown. Note that the DET may include or be coupled to and control a radio unit (RET). The gNB-CET is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en- gNB that controls the operation of one or more gNB-DETs. The gNB-CET terminates the Fl interface connected with the gNB-DET. The Fl interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CET 196 and the gNB-DET 195. The gNB-DET is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CET. One gNB-CET supports one or multiple cells. One cell is supported by only one gNB-DET. The gNB-DET terminates the Fl interface 198 connected with the gNB-CET. Note that the DET 195 is considered to include the transceiver 160, e.g., as part of an RET, but some examples of this may have the transceiver 160 as part of a separate RET, e.g., under control of and connected to the DET 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station.

[0080] The RAN node 170 (which in the shown embodiment could be substituted for a gNB or NR/5G Node B but possibly an evolved NodeB for FTE, long term evolution, but could be any similar access point to a wireless network) that provides access by wireless devices such as the EGE 1 10 to the wireless network 100, includes one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CET 196 may include the processor(s) 152, memories 155, and network interfaces 161. Note that the DET 195 may also contain its own memory/memories and processor(s), and/or other hardware, but these are not shown.

[0081] The RAN node 170 includes a ZZZ module 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways. The ZZZ module 150 may be implemented in hardware as ZZZ module 150-1, such as being implemented as part of the one or more processors 152. The ZZZ module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the ZZZ module 150 may be implemented as ZZZ module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152.

[0082] For instance, the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein. Note that the functionality of the ZZZ module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.

[0083] The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more RANs 170 communicate using link 176. The link 176 may be wired or wireless or both and may implement, e.g., an Xn interface for 5G, an XI interface for LTE, or other suitable interface for other standards.

[0084] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like.

[0085] For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH/DU, and the one or more buses 157 could be implemented in part as, e.g., fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit (CU), gNB-CU) of the RAN node 170 to the RRH/DU 195. Reference 198 also indicates those suitable network link(s).

[0086] It is noted that description herein indicates that“cells” perform functions, but it should be clear that the base station that forms the cell will perform the functions. The cell makes up part of a base station. That is, there can be multiple cells per base station. For instance, there could be three cells for a single carrier frequency and associated bandwidth, each cell covering one -third of a 360 degree area so that the single base station’s coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and a base station may use multiple carriers. So if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells.

[0087] The wireless network 100 may include a network control element (NCE) (or elements, NCE(s)) 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a further network, such as a telephone network and/or a data communications network (e.g., the Internet). Such core network functionality for 5G may include access and mobility management fimction(s) (AMF(S)) and/or user plane functions (UPF(s)) and/or session management fimction(s) (SMF(s)). Such core network functionality for LTE may include MME (Mobility Management Entity)/SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the NCE(s) 190, and note that both 5G and LTE functions might be supported. The RAN node 170 is coupled via a link 131 to the NCE 190. The link 131 may be implemented as, e.g., an NG interface for 5G, or an S l interface for LTE, or other suitable interface for other standards. The NCE 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the NCE 190 to perform one or more operations.

[0088] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software -based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.

[0089] The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, and other functions as described herein.

[0090] In general, the various embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.

[0091] Having thus introduced one suitable but non-limiting technical context for the practice of the exemplary embodiments of this invention, the exemplary embodiments will now be described with greater specificity.

[0092] As noted above, exemplary embodiments herein describe techniques for a new BSR trigger. In response to a QoS flow remapping being ordered, either directly via RRC signaling or indirectly via Reflective QoS, a BSR is triggered in all cell groups. The trigger could be restricted to the cell group(s) handling the old bearer and the new one, alternatively, or also just to the cell group handing the old bearer.

[0093] With such a trigger, the scheduler in the RAN (gNB) quickly gets an up-to-date picture of the UE’s buffer at QoS flow relocation. When receiving the BSR, the gNB knows whether it needs to schedule the old bearer for remaining data or not. This reduces latency, since, if there is no data remaining, then the gNB knows it can proceed with the data on the new bearer without having to rely on a start marker in the new bearer and/or end marker on the old bearer. This also reduces latency since, if there is data remaining, by allocating grants to the UE to transmit that old bearer, the end marker can reach the gNB quickly.

[0094] Although an end marker helps to identify when there is no more data for that QoS flow on the old bearer, it does not help the gNB to know how much data needs to be scheduled to reach that point: the amount that needs to be scheduled at the time of QoS flow relocation is useful to know as it gives a guarantee to the gNB that after scheduling that amount, an end marker would pop-up. The latency gain over gNB always scheduling the UE until either the end- marker packet or a padding BSR is received comes from the fact that by knowing how much data is left, the gNB can be aggressive in scheduling. If it has no idea, it would be more conservative to avoid overallocation

[0095] Even if there is no data buffered, the BSR can always reflect at least the end- marker packet that the UE shall always send.

[0096] Without this invention, the“tail” of the remapped QoS flow that is served on the previous DRB will not be expedited but will undergo a delay that is characteristic to that DRB. Without the remapping, that DRB would still have been kept scheduled in the uplink based on some prior info at the scheduler.

[0097] Consider a default bearer with background (low priority data). Some traffic pops up that requires handling with higher priority (e.g. picture upload). Reflective QoS is used to relocate the flow to a DRB with higher priority. In-order delivery requirement will stall the traffic for as long as the end-marker is missing. The current invention solves this problem. If one assumes that the default DRB is good enough, and the gNB can just wait for the end marker to come, then the need to relocate the flow in the first place would be questionable. If a flow is relocated, it is fair to assume that all packets from that flow need to be prioritized.

[0098] However, there is no way for the network to prioritize the tail of the remapped flow in uplink. It can only assign UL grants to the UE, which the UE will use as specified by LCP, where the default bearer may have a low priority. In NR, there exist LCP restrictions which allow the gNB to grant resources to the default bearer.

[0099] Besides, in the general case (CU-DU split), based only on receiving BSR due to this proposed trigger, the network scheduler/MAC will not know that a flow was remapped and therefore that scheduling the UE needs to be expedited. In such scenarios, the indication could be conveyed in the BSR or via the Fl interface.

[00100] FIG. 3 is a logic flow diagram for a RAN concerning a trigger for a BSR when a QoS flow remapping is ordered. This figure further illustrates the operation of an exemplary method or methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments. For instance, the ZZZ module 150 may include multiples ones of the blocks in FIG. 3, where each included block is an interconnected means for performing the function in the block. The blocks in FIG. 3 are assumed to be performed by a base station such as RAN node 170, e.g., under control of the ZZZ module 150 at least in part.

[00101] The method 300 comprises the following steps. In step 302, a RAN communicates data on a first bearer within a cell served by the RAN with a UE connected to at least one cell of the RAN. In step 304, the RAN sends a Quality of Service flow remapping order to the FTE to move data to a second bearer, triggering the UE to produce a Buffer Status Report. In step 306, the RAN receives the BSR indicating the UE’s buffer at QoS flow remapping. In step 308, the RAN determines the second bearer to schedule remaining data based on the BSR unless the BSR indicates that data remains in the first bearer. Finally, in step 310, the RAN, in response to data remaining in the first bearer, allocates grants to the UE to transmit on the first bearer. Thereafter, the RAN receives an end marker from the UE once no data remains for the QoS flow on the first bearer.

[00102] FIG. 4 is a logic flow diagram for a UE concerning a trigger for a BSR when a QoS flow remapping is ordered. This figure further illustrates the operation of an exemplary method or methods, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with exemplary embodiments. For instance, the YYY module 150 may include multiples ones of the blocks in FIG. 4, where each included block is an interconnected means for performing the function in the block. The blocks in FIG. 4 are assumed to be performed by the UE 110, e.g., under control of the YYY module 140 at least in part. [00103] The method 400 comprises the following steps. In step 402, UE, connected to at least one serving cell of a RAN, communicates data of at least one QoS flow on a first bearer. In step 404, the UE receives a remapping order from the RAN of a QoS flow from a first bearer to a second bearer, where the remapping triggers the UE to produce a Buffer Status Report. Finally, in step 406, UE transmits the BSR to the RAN indicating the UE's buffer at QoS flow remapping.

[00104] Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein is that the current invention solves the problem of an in-order delivery requirement that would stall traffic for as long as the end-marker is missing.

[00105] As used in this application, the term“circuitry” may refer to one or more or all of the following:

[00106] (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

[00107] (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal

processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

[00108] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[00109] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. [00110] Embodiments herein may be implemented in software (executed by one or more processors), hardware (e.g., an application specific integrated circuit), or a combination of software and hardware. For example, in an embodiment, the software (e.g., application logic, an instruction set) is maintained on any one of various conventional computer-readable media. In the context of this document, a“computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with one example of a computer described and depicted, as in FIG. 1 for example. A computer- readable medium may comprise a computer-readable storage medium (e.g., memories 125, 155, 171 or other device) that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[00111] The current architecture in FTE networks is fully distributed in the radio and fully centralized in the core network. The low latency requires bringing the content close to the radio which leads to local break out and multi -access edge computing (MEC). 5G may use edge cloud and local cloud architecture. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services and augmented reality. In radio communications, using edge cloud may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent. Some other technology advancements probably to be used are Software -Defined Networking (SDN), Big Data, and all-IP, which may change the way networks are being constructed and managed.

[00112] One possible manner to carry out embodiments described herein is with an edge cloud using a distributed computing system. An exemplary embodiment comprises a radio node connected to a server. Exemplary embodiments implementing the system allow the edge cloud server and the radio node as stand-alone apparatuses communicating with each other via a radio path or via a wired connection or they may be located in a same entity communicating via a wired connection.

[00113] Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.

[00114] If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined.

[00115] An example of an embodiment of the current invention, which can be referred to as item 1 , is a method that comprises communicating, by a RAN with a UE connected to the at least one cell, data on a first bearer within a cell served by the RAN; sending a Quality of Service flow remapping order to the UE to move data to a second bearer, triggering the UE to produce a Buffer Status Report; receiving the BSR indicating the UE’s buffer at QoS flow remapping; determining the second bearer to schedule remaining data based on the BSR unless the BSR indicates that data remains in the first bearer, where in response to data remaining in the first bearer: allocating grants to the UE to transmit on the first bearer; and receiving an end marker from the UE once no data remains for the QoS flow on the first bearer.

[00116] An example of another embodiment of the current invention, which can be referred to as item 2, is the method of item 1, wherein the order is direct via Radio Resource Control signaling.

[00117] An example of another embodiment of the current invention, which can be referred to as item 3, is the method of item 1, wherein the order is indirect via Reflective QoS, wherein a Radio Resource Control is triggered in all cell groups.

[00118] An example of another embodiment of the current invention, which can be referred to as item 4, is the method of item 1 , wherein the trigger is restricted to cell group(s) handling bearer 1.

[00119] An example of another embodiment of the current invention, which can be referred to as item 5, is the method of item 4, wherein the trigger is further restricted to cell group(s) handling bearer 2.

[00120] An example of another embodiment of the current invention, which can be referred to as item 6, is a method that comprises communicating, by a UE connected to at least one serving cell of a RAN, data of at least one QoS flow on a first bearer; receiving a remapping order from the RAN of a QoS flow from a first bearer to a second bearer, wherein the remapping triggers the UE to produce a Buffer Status Report; and transmitting the BSR to the RAN indicating the UE's buffer at QoS flow remapping.

[00121] An example of another embodiment of the current invention, which can be referred to as item 7, is an apparatus, that comprises at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following: communicating with a UE connected to the at least one cell, data on a first bearer within a cell served by the apparatus; sending a Quality of Service flow remapping order to the UE to move data to a second bearer, triggering the UE to produce a Buffer Status Report;

receiving the BSR indicating the UE’s buffer at QoS flow remapping; determining the second bearer to schedule remaining data based on the BSR unless the BSR indicates that data remains in the first bearer, where in response to data remaining in the first bearer: allocating grants to the UE to transmit on the first bearer; and receiving an end marker from the UE once no data remains for the QoS flow on the first bearer.

[00122] An example of another embodiment of the current invention, which can be referred to as item 8, is the apparatus of item 7, wherein the order is direct via Radio Resource Control signaling.

[00123] An example of another embodiment of the current invention, which can be referred to as item 9, is the apparatus of item 7, wherein the order is indirect via Reflective QoS, wherein a Radio Resource Control is triggered in all cell groups.

[00124] An example of another embodiment of the current invention, which can be referred to as item 10, is the apparatus of item 7, wherein the trigger is restricted to cell group(s) handling bearer 1.

[00125] An example of another embodiment of the current invention, which can be referred to as item 1 1 , is the apparatus of item 10, wherein the trigger is further restricted to cell group(s) handling bearer 2.

[00126] An example of another embodiment of the current invention, which can be referred to as item 12, is an apparatus that comprises at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following: communicating, via at least one serving cell of a RAN, data of at least one QoS flow on a first bearer; receiving a remapping order from the RAN of a QoS flow from a first bearer to a second bearer, wherein the remapping triggers the apparatus to produce a Buffer Status Report; and transmitting the BSR to the RAN indicating the apparatus’s buffer at QoS flow remapping.

[00127] An example of another embodiment of the current invention, which can be referred to as item 13, is a computer program that comprises code for controlling or performing: communicating, by a RAN with a UE connected to the at least one cell, data on a first bearer within a cell served by the RAN; sending a Quality of Service flow remapping order to the UE to move data to a second bearer, triggering the UE to produce a Buffer Status Report; receiving the BSR indicating the UE’s buffer at QoS flow remapping; determining the second bearer to schedule remaining data based on the BSR unless the BSR indicates that data remains in the first bearer, where in response to data remaining in the first bearer: allocating grants to the UE to transmit on the first bearer; and receiving an end marker from the UE once no data remains for the QoS flow on the first bearer.

[00128] An example of another embodiment of the current invention, which can be referred to as item 14, is a computer program product that comprises a computer-readable medium bearing computer program code of item 13 embodied therein for use with a computer.

[00129] An example of another embodiment of the current invention, which can be referred to as item 15, is a computer program product embodied on a non-transitory computer- readable medium in which a computer program is stored that, when being executed by a computer, is configured to provide instructions to control or carry out the method of any of items 1 - 5.

[00130] An example of another embodiment of the current invention, which can be referred to as item 16, is a computer program that comprises code for controlling or performing: communicating, by a UE connected to at least one serving cell of a RAN, data of at least one QoS flow on a first bearer; receiving a remapping order from the RAN of a QoS flow from a first bearer to a second bearer, wherein the remapping triggers the UE to produce a Buffer Status Report; and transmitting the BSR to the RAN indicating the UE's buffer at QoS flow remapping.

[00131] An example of another embodiment of the current invention, which can be referred to as item 17, is a computer program product comprising a computer-readable medium bearing computer program code of item 16 embodied therein for use with a computer.

[00132] An example of another embodiment of the current invention, which can be referred to as item 18, is a computer program product embodied on a non-transitory computer- readable medium in which a computer program is stored that, when being executed by a computer, is configured to provide instructions to control or carry out the method of items 6.

[00133] An example of another embodiment of the current invention, which can be referred to as item 19, is an apparatus that comprises means for communicating with a UE connected to the at least one cell, data on a first bearer within a cell served by the apparatus; means for sending a Quality of Service flow remapping order to the UE to move data to a second bearer, triggering the UE to produce a Buffer Status Report; means for receiving the BSR indicating the UE’s buffer at QoS flow remapping; means for determining the second bearer to schedule remaining data based on the BSR unless the BSR indicates that data remains in the first bearer, where in response to data remaining in the first bearer further that comprises means for allocating grants to the UE to transmit on the first bearer; and means for receiving an end marker from the UE once no data remains for the QoS flow on the first bearer.

[00134] An example of another embodiment of the current invention, which can be referred to as item 20, is an apparatus that comprises means for communicating, via at least one serving cell of a RAN, data of at least one QoS flow on a first bearer; means for receiving a remapping order from the RAN of a QoS flow from a first bearer to a second bearer, wherein the remapping triggers the apparatus to produce a Buffer Status Report; and means for transmitting the BSR to the RAN indicating the apparatus’s buffer at QoS flow remapping.

[00135] Although various aspects are set out above, other aspects comprise other combinations of features from the described embodiments, and not solely the combinations described above. [00136] It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention.