Methods for providing qfi coordination between a ran and a 5gc, and related wireless terminals, base stations, and core network nodes

Abstract

Methods of operating a wireless terminal in communication with a base station can be provided. Such methods can include receiving a radio resource control (RRC) message from the base station, where the RRC message includes information about at least one quality of service (QoS) flow being reflective and / or non-reflective. Such methods can also include providing communication of data packets between the wireless terminal and the base station using the non-reflective QoS flow, where the data packets include a data field and a service data application protocol (SDAP) header field having a QoS flow identity (QFI), and where the QFI is used for the data packets based on the information from the RRC message. Methods of operating a base station and a core network node are also provided. Related wireless terminals, base stations, and core network nodes are also discussed.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to communications, and more particularly, to wireless communications and related wireless terminals, base stations, and network nodes. BACKGROUND

[0002] 5G system design supports data connectivity and services such that deployments can use various technologies, e.g., network function virtualization and software-defined networking. 5G systems utilize service-based interaction between control plane (CP) network functions.

[0003] To enable independent scalability, evolution, and flexible deployments (e.g., centralized location or distributed / remote location), the 5G system design has separated user plane (UP) functions from control plane (CP) functions. In addition, this system is designed to be modular such that flexible and efficient network slicing can be implemented.

[0004] The 5G core architecture aims to reduce / minimize dependencies between the access network and the core network (CN) and define a common AN-CN interface to allow various radio access technologies to connect to the core. This can enable 3GPP as well as non-3GPP access technologies to access the 5G core network. [3GPP TS 23.501]

[0005] The 5G system architecture with 3GPP access is discussed below.

[0006] The 5G system can support a service-based architecture where network functions within the control plane (CP), such as the Access and Mobility Management Function (AMF), enable authorized network functions to access services. This representation can also include point-to-point reference points as necessary.

[0007] Figure 1 A reference point representation is presented that illustrates the interaction between network function services described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF). Thus, Figure 1 is a block diagram illustrating elements of the 5G architecture.

[0008] The 5G QoS in the RAN is discussed below.

[0009] 5G QoS includes entities established end-to-end by creating consistent packet forwarding handling between the UE and the peer. Since the 5G core network is responsible for managing packet handling between many network users, the QoS behavior of each UE can be required. Based on a configured or standardized profile that holds QoS information, the network equipment can decide packet handling consistent with the expected network behavior of a particular UE. To architect the end-to-end system, several components are defined in the 5G system, such as PDU session, QFI, and DRB.Figure 2 is a diagram illustrating high level components of a 5G QoS system.

[0010] PDU session is discussed below.

[0011] A 5G PDU session is an association between a UE and a data network offering PDU connectivity service, where packet data units (PDUs) are exchanged between the UE and the data network (DN) (see Figure 1 For reference). The association type can be IP, Ethernet or unstructured. A UE can have multiple simultaneous PDU sessions.

[0012] QoS parameters in PDU session are discussed below.

[0013] Traffic rate of a UE can be controlled per PDU session according to an aggregate maximum bit rate (AMBR). In addition, each UE is associated with a per-UE aggregate maximum bit rate (UE-AMBR). The UE-AMBR limits the aggregate bit rate that all non-GBR QoS flows across the UE can expect to be provided. The UE-AMBR is enforced by the radio access network (RAN). The UE-AMBR information is provided by the AMF or SMF.

[0014] A QoS flow is the finest granularity of QoS differentiation in a PDU session. A QoS flow is unique within a PDU session and each QoS flow is assigned a QoS flow indicator. NAS QoS flows are marked in UPF functionality. User plane traffic with the same QFI within a PDU session receives the same traffic forwarding treatment. QFI is carried in encapsulation header on N3 (and N9) (i.e. without any changes to the e2e packet header). It can be applied to PDUs with different types of payload, i.e. IP packets, unstructured PDUs and Ethernet frames. QFI is associated with 5QI information that provides QoS parameter information for the RAN. Flows within the same PDU session can use the same 5QI. A QoS flow can be configured as a guaranteed bit rate flow or a non-guaranteed bit rate flow.

[0015] A QoS flow is associated with parameters defined in 3GPP TS 23.501. These parameters include 5QI, QoS flow type (GBR or non-GBR), UL and DL GBFR rates and notification control parameters. In addition, Reflective QoS Attribute (RQA) can be carried in a QoS flow.

[0016] Radio protocol architecture is discussed below.

[0017] In the 5G system, the UE has a control plane connection with the gNB and AMF entities. The connection with the AMF entity is defined as a NAS connection and the gNB connection is defined as an RRC connection. These connections can allow the UE to communicate with the 5GC and RAN (gNB).

[0018] The SDAP layer on top of the PDCP layer can be used to provide user plane QoS handling. The responsibilities of the SDAP layer can include marking QFI and mapping QoS flows to DRBs.

[0019] Figure 3 The overall RAN protocol architecture is illustrated, where the SDAP layer is provided according to TS 37.324.

[0020] The DL and UL QoS framework is discussed below.

[0021] Figure 4 Figure 1 is a diagram illustrating an overview of the downlink, DL, QoS framework for New Radio, NR.

[0022] Figure 5 Figure 2 is a diagram illustrating the uplink, UL, QoS framework.

[0023] For more information on the QoS framework and associated issues, the existing QoS framework issues are discussed in the 3GPP contribution for RAN2#100.

[0024] Access Stratum, AS, reflective QoS or AS reflective QFI to DRB mapping is a mechanism that allows the Radio Access Network, RAN, to change the QFI to DRB mapping of a UE without Radio Resource Control, RRC, signaling. This mechanism is described in http: / / www.3gpp.org / ftp / Specs / latest-drafts / 37324-101.zip.

[0025] NAS reflective QoS is described in 3GPP TS 23.501 http: / / www.3gpp.org / ftp / Specs / latest-drafts / 23501-140.zip.

[0026] Reflective QoS is controlled on a per packet basis by using a Reflective QoS Indication, RQI, in the encapsulation header on the N3 reference point along with the QFI along with a Reflective QoS Timer, RQ Timer, value that is either signaled to the UE at PDU session establishment or set to a default value.

[0027] RQA (Reflective QoS Attribute) within the QoS profile of a QoS flow provided by the SMF to the NG-RAN at N2 reference point indicates that some (not necessarily all) traffic carried over this QoS flow is subject to reflective QoS. The RQA indication is given to the NG-RAN at UE context setup in the NG-RAN and at QoS flow setup.

[0028] When the 5GC determines that reflective QoS is used for a specific SDF, the SMF shall include an indication that reflective QoS is used in the corresponding SDF information provided to the UPF via the N4 interface, i.e. reflective QoS is to be applied to this SDF.

[0029] When the UPF receives this indication for a SDF, the UPF shall set the RQI bit in the encapsulation header on the N3 reference point for each DL packet corresponding to this SDF.

[0030] When the (R)AN receives the RQI in a DL packet on the N3 reference point, the (R)AN shall indicate to the UE the QFI, and that the DL packet is subject to reflective QoS.

[0031] Reflective QoS Attribute (RQA) is an optional parameter that can be signaled to the RAN via N2 when reflective QoS control is used, as described in clause 5.7.5.4. The RQA indicates that specific traffic on this QoS flow can be subject to reflective QoS.

[0032] The Radio Access Network (RAN) and the Core Network (CN) can use different sizes of QFI, and these differences can cause problems related to different ranges of values.

[0033] 3GPP standard document TS 37.324 V1.1.0 discloses that the SDAP procedures include QoS flow to DRB mapping configuration and reflective QoS flow to DRB mapping.

[0034] 3GPP draft document R2-1800940 by Intel Corporation entitled "QFI in SDAP header" discusses the use of QFI bits, NAS RQI bits, and AS RQI bits. In one proposal, it is proposed to consider using RRC signaling to configure a mapping of 7-bit QFI to 6-bit values.

[0035] 3GPP draft document R2-1712920 by Ericsson entitled "Problems with existing QoS framework (Phase 3)" discusses problems with AS reflective QFI to DRB mapping.

[0036] Xiaomi’s 3GPP draft document R2-1800230 entitled “Open issues for SDAP” proposes that the gNB indicate to the UE in the RR Reconfiguration message whether a QoS flow is configured with NAS reflective QoS.

[0037] Ericsson’s 3GPP draft document R2-1800698 entitled “SDAP header format” discusses several formats regarding the number of QFI bits, the presence of RQI bits, and reserved bits. SUMMARY

[0038] According to some embodiments of inventive concepts, a method of operating a wireless terminal in communication with a base station can be provided. The method can include receiving a radio resource control, RRC, message from the base station, where the RRC message includes information about at least one quality of service, QoS, flow being reflective and / or non-reflective. The method can also include providing communication of data packets between the wireless terminal and the base station using a non-reflective QoS flow, where the data packets include a data field and a service data application protocol, SDAP, header field having a QoS flow identity, QFI, and where the QFI is used for the data packets based on the information from the RRC message.

[0039] According to some other embodiments of inventive concepts, a method of operating a wireless terminal in communication with a base station can be provided. The method can include providing communication of data packets between the wireless terminal and the base station using a quality of service, QoS, flow. The QoS flow is a reflective QoS flow or a non-reflective QoS flow, the data packets include a data field and a service data application protocol, SDAP, header field, and a format of the SDAP header field is determined based on whether the QoS flow is a reflective QoS flow or a non-reflective QoS flow.

[0040] According to yet some other embodiments of inventive concepts, a method of operating a base station of a wireless communication network in communication with a wireless terminal can be provided. The method can include receiving information about at least one quality of service, QoS, flow being reflective and / or non-reflective from a core network, CN, node, and transmitting a radio resource control, RRC, message to the wireless terminal based on the information about at least one QoS flow being reflective and / or non-reflective. The method can also include providing communication of data packets between the base station and the wireless terminal using a non-reflective QoS flow, where the data packets include a data field and a service data application protocol, SDAP, header field having a QoS flow identity, QFI, and where the QFI is used for the data packets based on the information from the CN node.

[0041] According to yet some other embodiments of inventive concepts, a method of operating a base station of a wireless communication network in communication with a wireless terminal can be provided. The method can comprise providing communication of data packets between the base station and the wireless terminal using a quality of service, QoS, flow, wherein the QoS flow is a reflective QoS flow or a non-reflective QoS flow, wherein the data packets comprise a data field and a service data application protocol, SDAP, header field, and wherein a format of the SDAP header field is determined based on whether the QoS flow is a reflective QoS flow or a non-reflective QoS flow.

[0042] According to more embodiments of inventive concepts, a method of operating a core network, CN, node of a wireless communication network can be provided. The method can comprise determining, using a 5G quality of service, QoS, indicator, 5QI, having a value greater than a threshold value, that a reflective QoS flow is to be established for a 3GPP access between a base station and a wireless terminal. The method can further comprise transmitting, in response to establishing the reflective QoS flow for the 3GPP access using the 5QI having the value greater than the threshold value, information about the reflective QoS flow to the base station, wherein the information about the reflective QoS flow comprises a QoS flow identity, QFI, and the 5QI having the value greater than the threshold value.

[0043] According to some embodiments disclosed herein, a wireless terminal, UE, operates as follows:

[0044] • receives from the base station (gNB or eNB) a configuration indicating a mapping of non-access stratum, NAS, QoS flow identity, QFI, values to access stratum, AS, QFI values,

[0045] • exchanges data traffic associated to an AS QFI value with a base station, and

[0046] • determines the NAS QFI as follows:

[0047] ° if the AS QFI value is lower than 64, the UE uses the AS QFI value as NAS QFI value,

[0048] ° else, if the AS QFI value is greater than 63, the UE uses a NAS QFI value indicated by the mapping received from the base station.

[0049] According to some embodiments disclosed herein, a base station (gNB or eNB) operates as follows:

[0050] • sends to the UE a configuration indicating a mapping of non-access stratum, NAS, QoS flow identity, QFI, values to access stratum, AS, QFI values,

[0051] • wherein the mapping comprises information for determining the NAS QFI as follows:

[0052] ° If the AS QFI value is lower than 64, use the AS QFI value as NAS QFI value,

[0053] ° Else, if the AS QFI value is greater than 63, use the NAS QFI value indicated by the mapping.

[0054] According to some embodiments disclosed herein, the impact of integrating the radio access network and the 5G core network can be reduced, and / or an increased QFI range can be supported. BRIEF DESCRIPTION OF DRAWINGS

[0055] The accompanying drawings, included to provide a further understanding of the disclosure and

[0056] Accordingly, Figure 1 is a block diagram illustrating elements of a 5G architecture;

[0057] Figure 2 is a diagram illustrating high level components of a 5G QoS system;

[0058] Figure 3 is a diagram illustrating the overall RAN protocol architecture;

[0059] Figure 4 is a diagram illustrating an overview of the downlink, DL, QoS framework for New Radio, NR;

[0060] Figure 5 is a diagram illustrating the uplink, UL, QoS framework;

[0061] Figure 6 is a diagram illustrating a SDAP header with 6-bit QFI according to some embodiments of inventive concepts;

[0062] Figure 7 illustrating a SDAP header with 7-bit QFI according to some embodiments of inventive concepts;

[0063] Figure 8 is a block diagram illustrating elements of a wireless terminal, UE, according to some embodiments of inventive concepts;

[0064] Figure 9 is a block diagram illustrating elements of a base station according to some embodiments of inventive concepts;

[0065] Figure 10 is a block diagram illustrating elements of a core network, CN, node according to some embodiments of inventive concepts;

[0066] Figure 11is a flowchart illustrating operations of a wireless terminal, UE, according to some embodiments of the inventive concept;

[0067] Figure 12 is a flowchart illustrating operations of a base station (gNB or eNB) according to some embodiments of the inventive concept; and

[0068] Figure 13 is a flowchart illustrating operations of a core network, CN, node according to some embodiments of the inventive concept. DETAILED DESCRIPTION

[0069] The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are shown. The inventive concept may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It is clear that components from one embodiment can be considered to be present in / for another embodiment.

[0070] The following description presents various embodiments of the disclosed subject matter. The embodiments are presented to teach examples, and should not be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments can be modified, omitted, or supplemented without departing from the scope of the disclosed subject matter.

[0071] Figure 8 is a block diagram illustrating elements of a wireless terminal, UE, configured to provide wireless communication according to embodiments of the inventive concept. As shown, the wireless terminal, UE, can comprise an antenna 807 and transceiver circuitry 801 (also referred to as a transceiver) comprising a transmitter and a receiver configured to provide uplink and downlink radio communication with a base station of a radio access network. The wireless terminal, UE, can further comprise processor circuitry 803 (also referred to as a processor) coupled to the transceiver circuitry, and memory circuitry 805 (also referred to as a memory) coupled to the processor circuitry. The memory circuitry 805 can comprise computer-readable program code that, when executed by the processor circuitry 803, causes the processor circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processor circuitry 803 can be defined to include the memory, such that a separate memory circuitry is not needed. The wireless terminal, UE, can further comprise an interface (such as a user interface) coupled to the processor 803, and / or the wireless terminal, UE, can be incorporated in a vehicle.

[0072] As discussed herein, the operations of the wireless terminal UE can be performed by the processor 803 and / or the transceiver 801. For example, the processor 803 can control the transceiver 801 to transmit communications over a radio interface through the transceiver 801 to a base station gNB and / or to receive communications over a radio interface through the transceiver 801 from a base station. Moreover, modules can be stored in the memory 805, and these modules can provide instructions so that when the instructions of the modules are executed by the processor 803, the processor 803 performs respective operations (e.g., the operations discussed below with respect to example embodiments).

[0073] Figure 9 is a block diagram illustrating elements of a base station (also referred to as a network node, base station, eNodeB, eNB, gNodeB, gNB, etc.) of a radio access network (RAN) configured to provide cellular communications according to embodiments of inventive concepts. As shown, the base station can include transceiver circuitry 901 (also referred to as a transceiver) that includes a transmitter and a receiver configured to provide uplink and downlink radio communications with wireless terminals. The base station can include network interface circuitry 907 (also referred to as a network interface) configured to provide communications with other nodes of the RAN and / or a local area network (e.g., with other base stations and / or other entities). The base station can also include processor circuitry 903 (also referred to as a processor) coupled to the transceiver circuitry and memory circuitry 905 (also referred to as a memory) coupled to the processor circuitry. The memory circuitry 905 can include computer-readable program code that, when executed by the processor circuitry 903, causes the processor circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processor circuitry 903 can be defined to include the memory such that a separate memory circuitry is not needed.

[0074] As discussed herein, the operations of the base station can be performed by the processor 903, the network interface 907, and / or the transceiver 901. For example, the processor 903 can control the transceiver 901 to transmit communications over a radio interface through the transceiver 901 to one or more wireless terminals UE and / or to receive communications over a radio interface through the transceiver 901 from one or more wireless terminals UE. Similarly, the processor 903 can control the network interface 907 to transmit communications through the network interface 907 to one or more other network nodes / entities and / or to receive communications through the network interface from one or more other network nodes / entities. Moreover, modules can be stored in the memory 905, and these modules can provide instructions so that when the processor 903 executes the instructions of the modules, the processor 903 performs respective operations.

[0075] Figure 10is a block diagram illustrating elements of a core network, CN, node (e.g., an AMF entity / node, an SMF entity / node, a UPF entity / node, or any other control entity / node of a core network CN) configured to support cellular communications according to embodiments of inventive concepts. As shown, the CN node can include network interface circuitry 1007 (also referred to as a network interface) configured to provide communications with other network entities / nodes (e.g., with base stations and / or with another CN node of a RAN and / or CN). The CN node can also include processor circuitry 1003 (also referred to as a processor) coupled to the network interface circuitry 1007, as well as memory circuitry 1005 (also referred to as a memory) coupled to the processor circuitry. The memory circuitry 1005 can include computer-readable program code that, when executed by the processor circuitry 1003, causes the processor circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, the processor circuitry 1003 can be defined to include the memory such that a separate memory circuitry is not needed.

[0076] As discussed herein, the operations of the CN node can be performed by the processor 1003 and / or the network interface 1007. For example, the processor 1003 can control the network interface 1007 to transmit communications through the network interface 1007 to one or more other network nodes / entities, and / or to receive communications through the network interface from one or more other network nodes / entities. Moreover, modules can be stored in the memory 1005, and these modules can provide instructions so that when the processor 1003 executes the instructions of a module, the processor 1003 performs the corresponding operations. As discussed above, Figure 10 The structure of the CN node of FIG. 10 can be used, for example, to implement an Access and Mobility Function, AMF, entity / node, a Session Management Function, SMF, entity / node, a User Plane Function, UPF, entity / node, and / or a control entity / node (also referred to as a controller) to perform its operations as discussed in more detail below. For example, Figure 10 The operations of the CN node of FIG. 10 can be performed by one server, or distributed across multiple network servers having Figure 10 The structure of FIG. 10 can be used, for example, to implement an Access and Mobility Function, AMF, entity / node, a Session Management Function, SMF, entity / node, a User Plane Function, UPF, entity / node, and / or a control entity / node (also referred to as a controller) to perform its operations as discussed in more detail below. For example,

[0077] Currently, RAN 2 has agreed to use 6-bit QFI, while assuming 5GC uses 7-bit QFI. This can create a problem of value range (6-bit max 64 values and 7-bit max 128 values).

[0078] At the AH meeting in January 2018, RAN2 agreements were reached on the following.

[0079] Agreements

[0080] => Independent AS and NAS reflective QoS are supported.

[0081] => From RAN2 perspective, it is sufficient to support up to 64 reflective flows per UE per PDU session, so the QFI in SDAP is 6 bits.

[0082] => Ask SA2 / CT1 if they want to use more than 64 reflective flows per UE per PDU session each time. Indicate RAN2 agreement and strong need to have 6-bit SDAP.

[0083] The question will be included in the SA2 LS from the main session.

[0084] For future study FFS if the final QFI in CT1 / SA2 is more than 6 bits, a mechanism to remap NAS QFI to AS QFI can be needed.

[0085] According to some embodiments of the invention concept, the impact on the RAN and / or 5GC can be reduced / minimized while supporting an increase / max range of QFI.

[0086] 6-bit indication of QFI in SDAP header is one format that can be implemented. In addition, explicit bits can be used for NAS reflective QoS as well as AS reflective QoS. From the perspective of codepoints needed for full QoS mapping of 5QI, the QFI value should be at least 7 bits. However, this assumption can not be met. Therefore, alternative solutions should be explored.

[0087] Observation 1 - While 7 bits can be needed, only 6-bit QFI can be available.

[0088] Two main approaches can be seen on this topic. One is to limit the impact of QFI to the RAN (i.e., have local QFI in the RAN). The other option is to push the impact of 6-bit QFI to the 5GC and have 6-bit QFI limit for the whole system. It is worth noting that even if the RAN tries to absorb the impact of this change, the SMF can still need to comply with the limit of 64 QFIs configured per PDU session. In general, having an additional mapping layer on the RAN in QFI will unbind the NAS and AS QFIs, resulting in the 5GC can potentially have support for 8-bit QFIs. On the other hand, 2-level mapping can require the RAN to need to have QFI handling on a per-packet basis (assuming multiple QFIs mapped per DRB).

[0089] Observation 2 - Regarding the 3GPP access case, there can be two main approaches, RAN adapted to CN or CN adapted to RAN.

[0090] An additional impact of 6-bit QFI on 5GC is that the QFI value can no longer be bound to a 5QI value in 5GC. With 7-bit QFI, it would already be possible to indicate the 5QI value directly with the QFI value. For values above 63, this can no longer be possible. One option would then be to re-group the 5QI table so that all standardized 5QIs are below 64, but this can impact NR-LTE interworking and can require operator adaptation. Another option is to always signal both QFI and 5QI when the 5QI is above 64.

[0091] Observation 3 - Having 6-bit QFI values on 5GC would prevent 5QI from being used as QFI for 5QI above 64.

[0092] Option 1 : 7-bit QFI can be used in 5GC, mapped to 6-bit in RAN.

[0093] One approach is to use 7-bit QFI in 5GC, then the gNB would map it to a 6-bit AS-QFI value local to the RAN. This approach can require that the RAN always RRC configures the UE so that there is a mapping from NAS QFI to RAN QFI. Additional impact of this option is that the NAS reflective QoS behavior is slightly modified as the RAN is required to send the NAS-QFI to AS-QFI mapping to the UE whenever a new QFI appears on the system. Otherwise, the UE would not be able to resolve the AS-QFI from the NAS-QFI in uplink, UL traffic.

[0094] One benefit of this approach is that if QFI values are extended in the RAN in the future, there would be no 5GC impact other than the SMF.

[0095] UE RRC: UE (per DRB) is configured with mapping from NAS-QFI to AS-QFI.

[0096] DL: UE receives AS-QFI and maps it to NAS-QFI

[0097] UL: UE uses NAS-QFI at NAS level and marks NAS-QFI on RAN. (SDAP is responsible for mapping NAS-QFI to AS-QFI)

[0098] RAN RRC: RAN configures UE with NAS-QFI to AS-QFI mapping

[0099] DL: Mapping of AS-QFI to NAS-QFI

[0100] UL: RAN resolves AS-QFI to NAS-QFI for UPF.

[0101] 5GC SMF: Enforce limit of 64 QFIs per PDU session

[0102] UPF: Mark QFI in N3 (NG-U) header

[0103] Summary of Option 1: RAN uses 6-bit QFI, 5GC uses 7-bit QFI. RAN always maps NAS-QFI to local AS-QFI. SMF limits the maximum number of QFIs to 64.

[0104] Option 2: 7-bit QFI can be used in 5GC, mapped to 6-bit in RAN when needed.

[0105] In an alternative option, where 6-bit QFI is used in RAN and 7-bit QFI is used in 5GC, there is a one-to-one mapping of NAS-QFI to AS-QFI for values below or equal to 63. For values above 63, RAN will signal the NAS-QFI to AS-QFI mapping. SMF will need to limit the maximum number of QFI values to 64.

[0106] UE RRC: For NAS QFI values above 63, UE (per DRB) is configured with the mapping from NAS-QFI to AS-QFI. UE enables the mapping functionality of QFI based on RAN signaling.

[0107] DL: For QFI <= 63, NAS-QFI == AS QFI. For QFI > 63, UE receives AS-QFI and maps it to NAS-QFI

[0108] UL: For QFI <= 63, NAS-QFI == AS QFI. For QFI > 63, UE uses NAS-QFI on NAS level and marks AS-QFI on RAN based on SDAP mapping. (SDAP is responsible for mapping NAS-QFI to AS-QFI)

[0109] RAN RRC: QFI > 63, RAN configures UE with NAS-QFI to AS-QFI mapping.

[0110] DL: Mapping of AS-QFI to NAS-QFI

[0111] UL: RAN resolves AS-QFI to NAS-QFI for UPF.

[0112] 5GC SMF: Enforce limit of 64 QFIs per PDU session

[0113] UPF: Mark QFI in N3 (NG-U) header

[0114] Summary of Option 2: RAN uses 6-bit QFI, 5GC uses 7-bit QFI. RAN uses the same QFI as 5GC for values below or equal to 63, and explicit mapping for values above 64. SMF limits the maximum number of QFIs to 64

[0115] Option 3: For 3GPP access, QFI can be limited to 6 bits in the CN.

[0116] An alternative approach is to have 6-bit QFI for 3GPP access. This option has the most impact on 5GC. In addition, this restriction can potentially be implemented only on 3GPP access, i.e. non-3GPP access can still use higher values, and use the standardized 5QI values above 63 as QFI. With this approach, SMF limits the maximum QFI value to 64 for 3GPP access, and UPF marks QFI up to 64. For 5QI values above 64, both 5QI and dynamic QFI are signaled.

[0117] UE NAS-QFI == AS QFI

[0118] RAN NAS-QFI == AS QFI

[0119] 5GC SMF: Implement the limit of 64 QFIs per PDU session

[0120] UPF: For 3GPP access, mark 6-bit QFI on N3.

[0121] It is up to SA2 to decide if this option is feasible.

[0122] Summary of Option 3: RAN uses 6-bit QFI, 5GC uses 7-bit QFI. RAN uses the same QFI as 5GC for values below or equal to 63, and explicit mapping for values above 64. SMF limits the maximum number of QFIs to 64

[0123] Option 4: QFI can be limited to 6 bits in 5GC when needed.

[0124] Another alternative is to implement QFI restriction only when needed. When considering the SDAP header format, it has 1 bit for NAS-RQI. The NAS-RQI bit can only be used for QoS flows configured via N2 signaling for reflective QoS (i.e. it is completely dependent on 5GC configuration, regardless of space on RAN2 header). Thus, there can be options for 6-bit QFI and 7-bit QFI. For QoS flows that NAS flow can be subject to reflective QoS, 6-bit QFI will be used and otherwise 7-bit QFI is used. This increases the air overhead efficiency as we do not empty bit carry them when there is RQA (Reflective QoS parameter) for specific QoS flow. This approach will allow RAN to support 64 reflective QoS flows per PDU session or up to 128 non-reflective QoS flows per PDU session and implementation will be possible via existing specification mechanisms.

[0125] As NAS reflective QoS support can be optional for UE implementation, a UE that does not implement reflective QoS will only use 7-bit QFI format with 128 possible values. No additional processing can be needed.

[0126] UE NAS-QFI == AS QFI

[0127] RAN NAS-QFI == AS QFI

[0128] When RQA is configured, RAN sends RRC indication to UE.

[0129] RRC indication contains per QFI configuration or per DRB configuration regardless of RQI used in the header.

[0130] 5GC SMF implements the limit of 64 reflective QoS flows and 128 QFIs per PDU session.

[0131] 5GC implements the following limit: For QFI > 63, reflective QoS is not used in 3GPP access.

[0132] Option 4 can require implementation from gNB:

[0133] - Each QoS flow is configured individually, whether they contain QoS flow or not

[0134] o This option can require gNB not to mix QFI with or without reflective QoS parameter.

[0135] - Alternatively, 6-bit or 7-bit QFI is configured per DRB.

[0136] o UE knows from DRB configuration whether SDAP is 6-bit or 7-bit.

[0137] Option 4: RAN uses 6-bit QFI format with reflective QoS flows and 7-bit format with non-reflective QoS flows. 5GC does not use reflective QoS with values above 63 in the 5QI table.

[0138] Benefits of Option 4: Option 4 allows for 128 QFIs which can be needed in the future.

[0139] Regarding Option 4, there will be two options for the SDAP header:

[0140] Figure 6 SDAP header with 6-bit QFI is illustrated.

[0141] Figure 7 SDAP header with 7-bit QFI is illustrated.

[0142] The following table summarizes the different options based on the effort needed from each entity. While Option 3 is attractive from RAN2 perspective, SA2 can not accept it. Therefore, Option 4 can provide a trade-off in terms of complexity and implementation effort.

[0143] Table 1 Comparison of options. Low is good, high is bad.

[0144] UE RAN CN Option 1 High High Low Option 2 High High Low Option 3 Medium Medium Low Option 4 Low Low Low

[0145] This following section of the disclosure provides additional information on how the options can be implemented according to some embodiments of the inventive concept.

[0146] RAN trigger conditions:

[0147] Options 1 and 2:

[0148] - Upon receiving DL traffic or configuring QoS flows from N3 interface

[0149] - gNB always maps QFI to local QFI and sends NAS-QFI to AS-QFI mapping in RRC RadioBearerConfig (Sdap-config) to UE

[0150] - Upon receiving traffic from higher layers, UE must

[0151] o Map NAS-QFI to AS-QFI based on mapping sent on Sdap-config

[0152] - gNB maintains mapping (e.g. bitmap) on QoS flow values used per PDU session.

[0153] - Upon receiving DL traffic or configuring QoS flows from N3 interface

[0154] o When a new QoS flow is configured,

[0155] • If QoS flow value > 63

[0156] • Find available QFI value

[0157] • Send indication to UE that NAS-QFI and AS-QFI are different. This information can be sent to the UE in Radio bearer Config (Sdap Config).

[0158] -

[0159] Option 3:

[0160] - 5GC needs to have a table per PDU session of QFI values (e.g. UPF). This table contains information about the mapped QFIs. When a QFI is put into use, it is written to the table.

[0161] - 5GC SMF

[0162] o Limit the maximum number of QFIs per PDU session to 64.

[0163] - 5GC UPF: If QFI is larger than value 63

[0164] o Find free QFI value from QFI value table

[0165] o Signal the QFI value to gNB and UE. Also signal the associated QoS parameters.

[0166] o Always mark 6-bit QFI in N3 header.

[0167] Option 4

[0168] - When gNB receives RQA parameters from N2 interface

[0169] o gNB sends in RRC RadioBearerConfig information that it is a reflective QoS flow

[0170] o gNB makes this decision based on the presence of RQA parameters associated with the QFI

[0171] - Use 6-bit QFI for QFIs for which RQA parameters have been received via N2 configuration.

[0172] - UE:

[0173] o DL: UE checks DRB configuration, if DRB contains reflective QFI and reads the QFI value (6-bit or 7-bit value) accordingly

[0174] o The UL UE checks if the QFI is reflective (or by checking the individual QFI configuration or if the QFI is associated with a reflective DRB).

[0175] • Based on this lookup, the UE associates a 6-bit or 7-bit QFI to the SDAP header.

[0176] - gNB: upon reception of DL traffic from N3 interface

[0177] o Implementation option 1: copy the 7-bit QFI from the N3 header, if the MSB 7th bit is "1" -> high value range in use. Use 7-bit SDAP header for this. For example, QFI = 010 0000, MSB == 0 -> QFI < 64. Use 6-bit QFI on the SDAP header. This can also be done with a bit mask (if (QFI & b'100 0000 > 0) QFI > 64)

[0178] o Implementation option 2: read the 7-bit QFI value, copy the 7-bit QFI value if the RQA parameter is associated with the QoS flow, otherwise copy only the 6-bit (UPF ensures that the value < 64).

[0179] o The gNB can implement the QFI to DRB mapping in a way that non-reflective and reflective QoS flows are mapped into separate DRBs.

[0180] - 5GC UPF:

[0181] o Always mark the 7-bit QFI on the SDAP header.

[0182] - 5GC SMF: limit the maximum number of reflective QoS flows to 64,

[0183] - Reflective QoS with 5QI values larger than 63 are not used.

[0184] The inter-gNB handover is discussed below.

[0185] - In case the gNB maintains the NAS-QFI to AS-QFI mapping (options 1, 2), this mapping needs to be transferred from the source gNB to the target gNB via Xn signaling.

[0186] - In case the gNB maintains information about the reflectivity of a QFI (e.g. list of QFI values associated with a QFI and if the QFI is reflective) at QFI level or at DRB level. This information needs to be carried from the source to the target gNB via Xn signaling.

[0187] o In option 4, this allows the target gNB to know whether to configure 6-bit or 7-bit QFI for DL and expect 6-bit or 7-bit QFI for UL.

[0188] - Similar procedures apply for E-UTRA and NR handover.

[0189] The normative implementation of Option 4 is discussed below.

[0190] SDAP implementation (based on Release 3GPP TS 37.324 V1.3.0 (2018-01)

[0191] SDAP procedures

[0192] SDAP entity handling

[0193] SDAP entity establishment

[0194] When the RRC [3] requests SDAP entity establishment for a PDU session, the UE shall:

[0195] - establish the SDAP entity for the PDU session;

[0196] - associate the SDAP entity with the default DRB.

[0197] SDAP entity release

[0198] When the RRC [3] requests SDAP entity release for a PDU session, the UE shall:

[0199] - release the SDAP entity for the PDU session.

[0200] Data transfer

[0201] Uplink

[0202] Upon receiving an SDAP SDU for a QoS flow from upper layers, the transmitting SDAP entity shall:

[0203] - if there is no stored QoS flow to DRB mapping rule for the QoS flow, as specified in subclause 5.3, then:

[0204] - map the SDAP SDU to the default DRB;

[0205] - else:

[0206] - map the SDAP SDU to a DRB according to the stored QoS flow to DRB mapping rule;

[0207] - if the DRB to which the SDAP SDU is mapped is configured by RRC [3] with the presence of SDAP header,

[0208] - if the RRC configures the QoS flow DRB with reflective QoS

[0209] - construct an SDAP PDU as specified in sub-clause 6.2.2.2-1;

[0210] - else:

[0211] - construct an SDAP PDU as specified in sub-clause 6.2.2.2-2;

[0212] - else:

[0213] - construct an SDAP PDU as specified in sub-clause 6.2.2.1;

[0214] - deliver the constructed SDAP PDU to lower layers.

[0215] Downlink

[0216] Upon receiving an SDAP PDU for a QoS flow from lower layers, the receiving SDAP entity shall:

[0217] - if the DRB from which the SDAP PDU is received is configured by RRC [3] with the presence of SDAP header:

[0218] - perform reflective QoS flow to DRB mapping as specified in sub-clause 5.3.2;

[0219] - perform RQI handling as specified in sub-clause 5.4;

[0220] - if RRC configures the QoS flow DRB with reflective QoS

[0221] - retrieve the SDAP SDU from the SDAP PDU as specified in sub-clause 6.2.2.2-1;

[0222] - else:

[0223] - retrieve the SDAP SDU from the SDAP PDU as specified in sub-clause 6.2.2.2-2;

[0224] - else:

[0225] - retrieve the SDAP SDU from the SDAP PDU as specified in sub-clause 6.2.2.1;

[0226] - deliver the retrieved SDAP SDU to upper layers.

[0227] QoS flow to DRB mapping

[0228] Configuration

[0229] When the RRC [3] configures UL QoS flow to DRB mapping rules for the SDAP entity, the SDAP entity shall:

[0230] - store the UL QoS flow to DRB mapping rules.

[0231] Reflective mapping

[0232] For each received DL SDAP PDU with RDI set to 1, the SDAP entity shall:

[0233] - process the QFI field in the SDAP header and store the QoS flow to DRB mapping of the DL SDAP PDU as UL QoS flow to DRB mapping rule.

[0234] DRB release

[0235] When a DRB is released, the SDAP entity shall:

[0236] - remove all QoS flow to DRB mappings associated with the released DRB.

[0237] RQI handling

[0238] For each received DL SDAP PDU with RQI set to 1, the SDAP entity shall:

[0239] - inform the NAS layer that the RQI bit is set to 1.

[0240] Data PDU with SDAP header

[0241] Figure 6 Figure illustrating the format of a SDAP data PDU for downlink, DL, where the SDAP header is configured with RDI, RQI and 6-bit QFI.

[0242] Figure 7 Figure illustrating the format of a SDAP data PDU for downlink, DL, where the SDAP header is configured with RDI and 7-bit QFI.

[0243] Figure 11 Figure illustrating operations of a wireless terminal, UE, (e.g., operations of the wireless terminal processor 803), Figure 12 Figure illustrating operations of a base station (e.g., operations of the base station processor 903), and Figure 13 Figure illustrating operations of a core network, CN, node (e.g., operations of the processor 1003). With respect to some embodiments of the invention concept, Figure 11 , 12 and / or the various operations of Figures 1 1, 12, and / or 13 can be optional. For example, with respect to example embodiment 1, Figure 11Operations 1101, 1105, 1107, 1109, 1111, 1113, and 1117 can be optional; regarding example embodiment 15, Figure 11 Operations 1101, 1103, 1105, 1107, 1109, 1111, and 1113, as well as 1115 or 1117, may be optional; regarding example embodiment 27, Figure 12 Operations 1201, 1205, 1207, 1209, 1211, 1213, and 1217 can be optional; regarding example embodiment 41, Figure 12 Operations 1201, 1203, 1204, 1205, 1207, 1209, 1211, and 1213, as well as 1215 or 1217, may be optional; and with respect to Example Embodiment 54, operations 1301, 1309, and 1311 may be optional.

[0244] As mentioned above, Figure 11 The diagram illustrates the operation of a wireless terminal (UE). According to... Figure 11 In some embodiments illustrated, at blocks 1101 and 1103, processor 803 can receive Radio Resource Control (RRC) messages from a base station via transceiver 801. The RRC message may include information about whether at least one Quality of Service (QoS) flow is reflective and / or non-reflective. For example, information from the RRC message may identify a first Data Radio Bearer (DRB) as a DRB for a non-reflective QoS flow, and information from the RRC message may identify a second DRB as a DRB for a reflective QoS flow.

[0245] In blocks 1105 and 1107, processor 803 can establish a first DRB for non-reflective QoS flows between the wireless terminal and the base station, and a second DRB for reflective QoS flows between the wireless terminal and the base station, based on information from the RRC message. According to some embodiments, the information for the first and second DRBs can be provided in a single RRC message. According to some other embodiments, the information for the first and second DRBs can be provided in different RRC messages.

[0246] If a data packet needs to be transmitted via transceiver 801 in box 1111, processor 803 can determine in box 1113 whether a non-reflective DRB or a reflective DRB should be used to transmit the data packet.

[0247] For example, in block 1115, processor 803 can use a non-reflective QoS stream on a first DRB to provide communication of a first data packet between a wireless terminal and a base station via transceiver 801, wherein the first data packet includes a first data field and a first Service Data Application Protocol (SDAP) header field with a QoS Stream Identity (QFI), and wherein an information QFI based on an RRC message is used for the data packet.

[0248] In block 1117, processor 803 may use a reflected QoS stream on a second DRB to provide communication of a second data packet between the wireless terminal and the base station, wherein the second data packet includes a second data field and a second SDAP header field with a QFI, the QFI being used for the second data packet based on information from the RRC message, and wherein the length of the QFI in the second SDAP header field is less than the length of the QFI in the first SDAP header field.

[0249] The QFI in the first SDAP header field can be a 7-bit QFI, while the QFI in the second SDAP header field can be a 6-bit QFI.

[0250] The first SDAP header field may include the QFI and the Reflected QoS to DRB Mapping Indicator (RDI) of the first SDAP header field, but without the Reflected QoS Indicator (RQI), and the second SDAP header field may include the QFI, the RQI, and the RDI of the second SDAP header field.

[0251] Furthermore, the format of the first SDAP header field can be determined based on the fact that the first QoS flow of the first DRB is a non-reflective QoS flow, and the format of the second SDAP header field can be determined based on the fact that the second QoS flow of the second DRB is a reflective QoS flow.

[0252] As mentioned above, Figure 12 The diagram illustrates the operation of a base station. (Based on...) Figure 11 In some embodiments illustrated in the diagram, at blocks 1201 and 1203, processor 903 can receive (via network interface 907) information from a core network (CN) node regarding whether at least one Quality of Service (QoS) flow is reflective and / or non-reflective. The information from the CN node can identify one QoS flow as a non-reflective QoS flow and another as a reflective QoS flow. For example, information from the CN node can identify a first Data Radio Bearer (DRB) as a DRB for a non-reflective QoS flow, and information from an RRC message can identify a second DRB as a DRB for a reflective QoS flow.

[0253] In block 1204, processor 903 may transmit Radio Resource Control (RRC) messages to the wireless terminal via transceiver 901 based on information regarding whether at least one Quality of Service (QoS) flow is reflective and / or non-reflective. For example, the RRC message may include information regarding a first DRB being a DRB for non-reflective QoS flows and a second DRB being a DRB for reflective QoS flows.

[0254] At block 1205, 1207, and / or 1209, the processor 903 can establish a first DRB between the base station and the wireless terminal for a non-reflective QoS flow, and the processor 903 can establish a second DRB between the base station and the wireless terminal for a reflective QoS flow.

[0255] If a data packet is to be communicated through the transceiver 901 at block 1211, the processor 903 can determine whether a non-reflective DRB or a reflective DRB should be used to communicate the data packet at block 1213.

[0256] For example, at block 1215, the processor 903 can provide communication of a first data packet between the base station and the wireless terminal through the transceiver 901 using the non-reflective QoS flow on the first DRB, where the first data packet includes a first data field and a first service data application protocol, SDAP, header field having a QoS flow identity, QFI, and where the QFI is used for the data packet based on information from a CN node.

[0257] At block 1217, the processor 903 can provide communication of a second data packet between the base station and the wireless terminal through the transceiver 901 using the reflective QoS flow on the second DRB, where the second data packet includes a second data field and a second SDAP header field having a QFI, the QFI is used for the second data packet based on information from a CN node, and where a length of the QFI of the second SDAP header field is less than a length of the QFI of the first SDAP header field.

[0258] The QFI of the first SDAP header field can be a 7-bit QFI, and the QFI of the second SDAP header field can be a 6-bit QFI.

[0259] The first SDAP header field can include the QFI of the first SDAP header field and a reflective QoS to DRB mapping indication, RDI, without a reflective QoS indicator, RQI, and the second SDAP header field can include the QFI of the second SDAP header field, an RQI of the second SDAP header field, and the RDI.

[0260] The format of the first SDAP header field can be determined based on the non- reflective QoS flow being a non-reflective QoS flow, and the format of the second SDAP header field can be determined based on the reflective QoS flow being a reflective QoS flow.

[0261] For example, responsive to the corresponding QoS flow being a non-reflective QoS flow, the first SDAP header field (corresponding to a non-reflective QoS flow) can have a format that includes a QoS flow identity QFI and a reflective QoS flow to DRB mapping indication RDI. The QFI of the first SDAP header field can be a 7-bit QFI, the RDI of the first SDAP can be a 1-bit RDI, and the first SDAP header field can be provided with the QFI and the RDI without a reflective QoS indicator RQI.

[0262] Responsive to the QoS flow being a reflective QoS flow, the second SDAP header field (corresponding to a reflective QoS flow) can have a format that includes a QoS flow identity QFI, a reflective QoS indicator RQI, and a 1-bit reflective QoS flow to DRB mapping indication RDI.

[0263] As described above, Figure 13 The operation of a base station is illustrated. If a QoS flow is to be established at block 1301, the processor 1003 can determine whether the QoS flow is non-reflective or reflective at block 1303.

[0264] For a reflective QoS flow, the processor 1003 can determine whether a 5G QoS indicator 5QI has a value greater than a threshold at block 1305.

[0265] Responsive to determining at blocks 1303 and 1305 that a reflective quality of service QoS flow is to be established for 3GPP access between the base station (gNB or eNB) and the wireless terminal (UE) using a 5G QoS indicator 5QI having a value greater than a threshold, the processor 1003 can transmit information about the reflective QoS flow to the base station through the network interface 1007 at block 1307, where the information about the reflective QoS flow includes a QoS flow identity QFI and the 5QI having a value greater than the threshold. In this case, the QFI can be a 6-bit QFI, and the 5QI can have a value greater than 64.

[0266] Responsive to determining at blocks 1303 and 1305 that a reflective QoS flow is to be established for 3GPP access between the base station and the wireless terminal using a 5QI having a value less than a threshold, the processor 1003 can transmit information about a second reflective QoS flow to the base station through the network interface 1007 at block 1309, where the information about the second reflective QoS flow includes a second QFI mapped to a second 5QI having a value less than the threshold without separately including the second 5QI. In this case, the second QFI can be a 6-bit QFI, and the 5QI can have a value less than 63.

[0267] In response to determining at block 1303 that a non-reflective QoS flow is to be established for 3GPP access between the base station and a wireless terminal (UE), processor 1003 can transmit information about the non-reflective QoS flow to the base station at block 1311 via network interface 1007, where the information about the non-reflective QoS flow includes a second QFI that is mapped to a second 5QI having a value that is greater than a threshold, without separately including the second 5QI.

[0268] Example embodiments of inventive concepts are discussed below.

[0269] 1. A method of operating a wireless terminal (UE) in communication with a base station gNB, the method comprising:

[0270] receiving (1103) a radio resource control, RRC, message from the base station, where the RRC message includes information that at least one quality of service, QoS, flow is reflective and / or non-reflective; and

[0271] providing (1115) communication of data packets between the wireless terminal and the base station using a non-reflective QoS flow, where the data packets include a data field and a service data application protocol, SDAP, header field having a QoS flow identity, QFI, and where the QFI is used for the data packets based on information from the RRC message.

[0272] 2. The method of embodiment 1, where the data packets are first data packets, the data field is a first data field, and the SDAP header field is a first SDAP header field, the method further comprising:

[0273] providing (1117) communication of second data packets between the wireless terminal and the base station using a reflective QoS flow, where the second data packets include a second data field and a second SDAP header field having a QFI, the QFI is used for the second data packets based on information from the RRC message, and where a length of the QFI of the second SDAP header field is less than a length of the QFI of the first SDAP header field.

[0274] 3. The method of embodiment 2, where the information from the RRC message identifies the reflective QoS flow as being a reflective QoS flow.

[0275] 4. The method of any of embodiments 2-3, further comprising:

[0276] establishing (1107) a first data radio bearer, DRB, between the wireless terminal and the base station; and

[0277] establishing (1107) a second DRB between the wireless terminal and the base station.

[0278] wherein providing communication of the first data packet comprises providing communication of the first data packet using the non-reflective QoS flow on the first DRB;

[0279] wherein providing communication of the second data packet comprises providing communication of the second data packet using the reflective QoS flow on the second DRB.

[0280] 5. The method of embodiment 4, wherein information from the RRC message identifies the first DRB as a DRB for a non-reflective QoS flow, and / or wherein information from the RRC message identifies the second DRB as a DRB for a reflective QoS flow.

[0281] 6. The method of any of embodiments 2-5, wherein the QFI of the second SDAP header field is a 6-bit QFI.

[0282] 7. The method of any of embodiments 2-6, wherein the first SDAP header field comprises a QFI and a reflective QoS to DRB mapping indication RDI of the first SDAP header field, without a reflective QoS indicator RQI, and wherein the second SDAP header field comprises a QFI of the second SDAP header field, an RQI and an RDI of the second SDAP header field.

[0283] 8. The method of embodiment 1, further comprising:

[0284] establishing (1107) a data radio bearer, DRB, between the wireless terminal and the base station;

[0285] wherein providing communication of the data packet comprises providing communication of the data packet using the non-reflective QoS flow on the DRB.

[0286] 9. The method of embodiment 8, wherein information from the RRC message identifies the DRB as a DRB for a non-reflective QoS flow.

[0287] 10. The method of any of embodiments 1-9, wherein information from the RRC message identifies the non-reflective QoS flow as being a non-reflective QoS flow.

[0288] 11. The method of any of embodiments 1-10, wherein providing communication comprises transmitting the data packet from the wireless terminal to the base station on the non-reflective QoS flow.

[0289] 12. The method of any of embodiments 1-10, wherein providing communication comprises receiving the data packet at the wireless terminal from the base station on the non-reflective QoS flow.

[0290] 13. The method of any of embodiments 1-12, wherein the QFI of the SDAP header field is a 7-bit QFI.

[0291] 14. The method of any of embodiments 1-13, wherein the SDAP header field is provided with the QFI and has a reflective QoS flow to DRB mapping indication, RDI, but no reflective QoS indicator, RQI.

[0292] 15. A method of operating a wireless terminal (UE) in communication with a base station, gNB, the method comprising:

[0293] providing (1115, 1117) communication of data packets between the wireless terminal and the base station using a quality of service, QoS, flow, wherein the QoS flow is a reflective QoS flow or a non-reflective QoS flow, wherein the data packets include a data field and a service data application protocol, SDAP, header field, and wherein a format of the SDAP header field is determined based on whether the QoS flow is a reflective QoS flow or a non-reflective QoS flow.

[0294] 16. The method of embodiment 15, wherein the QoS flow is a non-reflective QoS flow, and wherein responsive to the QoS flow being a non-reflective QoS flow, the SDAP header field has a format that includes a QoS flow identity, QFI, and a reflective QoS flow to DRB mapping indication, RDI.

[0295] 17. The method of embodiment 16, wherein the QFI is a 7-bit QFI and the RDI is a 1-bit RDI.

[0296] 18. The method of any of embodiments 16-17, wherein the SDAP header field is provided with the QFI and the RDI but no reflective QoS indicator, RQI.

[0297] 19. The method of embodiment 15, wherein the QoS flow is a reflective QoS flow, and wherein responsive to the QoS flow being a reflective QoS flow, the SDAP header field has a format that includes a QoS flow identity, QFI, a reflective QoS indicator, RQI, and a reflective QoS flow to DRB mapping indication, RDI.

[0298] 20. The method of embodiment 19, wherein the data packet is a first data packet, the QoS flow is a first QoS flow, the data field is a first data field, and the SDAP header field is a first SDAP header field, the method further comprising:

[0299] providing (1115) communication of second data packets between the wireless terminal and the base station using a second quality of service, QoS, flow, wherein the second QoS flow is a non-reflective QoS flow, wherein the second data packets comprise a second data field and a second SDAP header field, and wherein, responsive to the QoS flow being a non-reflective QoS flow, the second SDAP header field has a format comprising a QoS flow identity, QFI, and a reflective QoS flow to DRB mapping indication, RDI, and wherein the QFI of the second SDAP header field is longer than the QFI of the first SDAP header field.

[0300] 21. The method of embodiment 20, further comprising:

[0301] establishing (1107) a first data radio bearer, DRB, between the wireless terminal and the base station; and

[0302] establishing (1107) a second DRB between the wireless terminal and the base station;

[0303] wherein providing communication of the first data packets comprises providing communication of the first data packets using the first QoS flow on the first DRB;

[0304] wherein providing communication of the second data packets comprises providing communication of the second data packets using the second QoS flow on the second DRB.

[0305] 22. The method of any of embodiments 15-21, further comprising:

[0306] receiving (1103) a radio resource control, RRC, message from the base station, wherein the RRC message comprises information about at least one QoS flow being reflective and / or non-reflective, wherein using the information from the RRC message, a format of the header field is determined based on the QoS flow being a reflective QoS flow or a non-reflective QoS flow.

[0307] 23. The method of any of embodiments 15-22, wherein providing communication comprises transmitting the data packets from the wireless terminal to the base station over the QoS flow.

[0308] 24. The method of any of embodiments 15-22, wherein providing communication comprises receiving the data packets at the wireless terminal from the base station over the QoS flow.

[0309] 25. A wireless terminal (UE), wherein the wireless terminal is adapted to perform operations according to any of embodiments 1-24.

[0310] 26. A wireless terminal (UE), comprising:

[0311] a transceiver (801) configured to provide wireless communication in a wireless communication network; and

[0312] a processor (803) coupled with the transceiver, wherein the processor is configured to provide wireless communication with the wireless communication network through the transceiver, wherein the processor is further configured to perform the operations of any of embodiments 1-24.

[0313] 27. A method of operating a base station gNB of a wireless communication network in communication with a wireless terminal (UE), the method comprising:

[0314] receiving (1203) information from a core network, CN, node that at least one quality of service, QoS, flow is reflective and / or non-reflective;

[0315] transmitting (1204) a radio resource control, RRC, message to the wireless terminal based on the information that at least one QoS flow is reflective and / or non-reflective; and

[0316] providing (1215) communication of data packets between the base station and the wireless terminal using a non-reflective QoS flow, wherein the data packets include a data field and a service data application protocol, SDAP, header field having a QoS flow identity, QFI, and wherein the QFI is used for the data packets based on information from the CN node.

[0317] 28. The method of embodiment 27, wherein the data packets are first data packets, the data field is a first data field, and the SDAP header is a first SDAP header, the method further comprising:

[0318] providing (1217) communication of second data packets between the base station and the wireless terminal using a reflective QoS flow, wherein the second data packets include a second data field and a second SDAP header field having a QFI, the QFI is used for the second data packets based on information from the CN node, and wherein a length of the QFI of the second SDAP header field is less than a length of the QFI of the first SDAP header field.

[0319] 29. The method of embodiment 28, wherein the information from the CN node identifies the reflective QoS flow as a reflective QoS flow.

[0320] 30. The method of any of embodiments 28-29, further comprising:

[0321] establishing (1207) a first data radio bearer, DRB, between the base station and the wireless terminal; and

[0322] establishing (1207) a second DRB between the base station and the wireless terminal;

[0323] wherein providing communication of the first data packet comprises providing communication of the first data packet using the non-reflective QoS flow on the first DRB;

[0324] wherein providing communication of the second data packet comprises providing communication of the second data packet using the reflective QoS flow on the second DRB.

[0325] 31. The method of embodiment 30, wherein the information from the CN node identifies the first DRB as a DRB for a non-reflective QoS flow, and / or wherein the information from the RRC message identifies the second DRB as a DRB for a reflective QoS flow.

[0326] 32. The method of any of embodiments 28-31, wherein the QFI of the second SDAP header field is a 6-bit QFI.

[0327] 33. The method of any of embodiments 28-32, wherein the first SDAP header field comprises a QFI of the first SDAP header field and a reflective QoS to DRB mapping indication RDI without a reflective QoS indicator RQI, and wherein the second SDAP header field comprises a QFI of the second SDAP header field, an RQI of the second SDAP header field, and an RDI.

[0328] 34. The method of embodiment 27, further comprising:

[0329] establishing (1207) a data radio bearer, DRB, between the base station and the wireless terminal;

[0330] wherein providing communication of the data packet comprises providing communication of the data packet using the non-reflective QoS flow on the DRB.

[0331] 35. The method of any of embodiments 27-34, wherein the information from the CN node identifies the non-reflective QoS flow as being a non-reflective QoS flow.

[0332] 36. The method of any of embodiments 27-35, wherein providing communication comprises transmitting the data packet from the base station to the wireless terminal on the non-reflective QoS flow.

[0333] 37. The method of any of embodiments 27-36, wherein providing communication comprises receiving the data packet at the base station from the wireless terminal on the non-reflective QoS flow.

[0334] 38. The method of any of embodiments 27-37, wherein the information from the CN node comprises a reflective QoS attribute, RQA.

[0335] 39. The method of any of embodiments 27-38, wherein the QFI of the SDAP header field is a 7-bit QFI.

[0336] 40. The method of any of embodiments 27-39, wherein the SDAP header field is provided with the QFI and has a reflective QoS flow to DRB mapping indication, RDI, but no reflective QoS indicator, RQI.

[0337] 41. A method of operating a base station, gNB, of a wireless communication network in communication with a wireless terminal (UE), the method comprising:

[0338] providing (1215, 1217) communication of data packets between the base station and the wireless terminal using a quality of service, QoS, flow, wherein the QoS flow is a reflective QoS flow or a non-reflective QoS flow, wherein the data packets comprise a data field and a service data application protocol, SDAP, header field, and wherein a format of the SDAP header field is determined based on whether the QoS flow is a reflective QoS flow or a non-reflective QoS flow.

[0339] 42. The method of embodiment 41, wherein the QoS flow is a non-reflective QoS flow, and wherein, in response to the QoS flow being a non-reflective QoS flow, the SDAP header field has a format comprising a QoS flow identity, QFI, and a reflective QoS flow to DRB mapping indication, RDI.

[0340] 43. The method of embodiment 42, wherein the QFI is a 7-bit QFI and the RDI is a 1-bit RDI.

[0341] 44. The method of any of embodiments 42-43, wherein the SDAP header field is provided with the QFI and the RDI, but no reflective QoS indicator, RQI.

[0342] 45. The method of embodiment 41, wherein the QoS flow is a reflective QoS flow, and wherein, in response to the QoS flow being a reflective QoS flow, the SDAP header field has a format comprising a QoS flow identity, QFI, a reflective QoS indicator, RQI, and a 1-bit reflective QoS flow to DRB mapping indication, RDI.

[0343] 46. The method of embodiment 45, wherein the data packet is a first data packet, the QoS flow is a first QoS flow, the data field is a first data field, and the header field is a first header field, the method further comprising:

[0344] providing (1215) communication of a second data packet between the base station and the wireless terminal using a second quality of service, QoS, flow, wherein the second QoS flow is a non-reflective QoS flow, wherein the second data packet comprises a second data field and a second SDAP header field, and wherein the second SDAP header field has a format comprising a QoS flow identity, QFI, and a reflective QoS flow to DRB mapping indication, RDI, in response to the QoS flow being a non-reflective QoS flow.

[0345] 47. The method of embodiment 46, further comprising:

[0346] establishing (1207) a first data radio bearer, DRB, between the base station and the wireless terminal; and

[0347] establishing (1207) a second DRB between the base station and the wireless terminal;

[0348] wherein providing communication of the first data packet comprises providing communication of the first data packet using the first QoS flow on the first DRB;

[0349] wherein providing communication of the second data packet comprises providing communication of the second data packet using the second QoS flow on the second DRB.

[0350] 48. The method of any of embodiments 41-47, further comprising:

[0351] transmitting (1204) a radio resource control, RRC, message from the base station to the wireless terminal, wherein the RRC message comprises information that at least one QoS flow is reflective and / or non-reflective.

[0352] 49. The method of any of embodiments 41-48, wherein providing communication comprises transmitting the data packet from the base station to the wireless terminal over the QoS flow.

[0353] 50. The method of any of embodiments 41-48, wherein providing communication comprises receiving the data packet from the wireless terminal at the base station over the QoS flow.

[0354] 51. The method of any of embodiments 51-50, further comprising:

[0355] receiving (1203) information from a core network, CN, node about at least one quality of service, QoS, flow being reflective and / or non-reflective, wherein a format of the SDAP header field is determined based on the QoS flow being a reflective QoS flow or a non-reflective QoS flow using the information from the CN node.

[0356] 52. A base station, gNB, wherein the base station is adapted to perform operations according to any of embodiments 27-51.

[0357] 53. A base station, gNB, comprising:

[0358] a transceiver (901) configured to provide wireless communication with wireless terminals;

[0359] a network interface (907) configured to provide communication with other nodes of a wireless communication network; and

[0360] a processor (903) coupled with the transceiver and the network interface, wherein the processor is configured to provide wireless communication with the wireless communication network through the transceiver, wherein the processor is configured to provide network communication with other nodes of the wireless communication network through the network interface, and wherein the processor is further configured to perform operations according to any of embodiments 27-51.

[0361] 54. A method of operating a core network, CN, node of a wireless communication network, the method comprising:

[0362] determining (1303, 1305) that a reflective quality of service, QoS, flow is to be established for 3GPP access between a base station, gNB, and a wireless terminal (UE) using a 5G QoS indicator, 5QI, having a value greater than a threshold; and

[0363] in response to establishing the reflective QoS flow for the 3GPP access using the 5QI having the value greater than the threshold, transmitting (1307) information about the reflective QoS flow to the base station, wherein the information about the reflective QoS flow includes a QoS flow identity, QFI, and the 5QI having the value greater than the threshold.

[0364] 55. The method of embodiment 54, wherein the QFI is a 6-bit QFI, and wherein the 5QI has a value greater than 64.

[0365] 56. The method of any of embodiments 54-55, wherein the reflective QoS flow is a first reflective QoS flow, the QFI is a first QFI, and wherein the 5QI is a first 5QI, the method further comprising:

[0366] determining (1303, 1305) that a second reflective Quality of Service, QoS, flow is to be established for the 3GPP access between the base station and the wireless terminal using a second 5QI having a value less than the threshold; and

[0367] transmitting (1309), to the base station, information about the second reflective QoS flow in response to establishing the second reflective QoS flow for the 3GPP access using the second 5QI having the value less than the threshold, wherein the information about the second reflective QoS flow includes a second QFI mapped to the second 5QI having the value less than the threshold without separately including the second 5QI.

[0368] 57. The method of embodiment 56, wherein the second QFI is a 6-bit QFI, and wherein the 5QI has a value greater than 63.

[0369] 58. The method of embodiment 54, wherein the QFI is a first QFI, and wherein the 5QI having a value greater than the threshold is a first 5QI, the method further comprising:

[0370] determining (1303) that a non-reflective QoS flow is to be established for the 3GPP access between the base station and the wireless terminal (UE) using a second 5QI having a value greater than the threshold; and

[0371] transmitting (1311), to the base station, information about the non-reflective QoS flow in response to establishing the non-reflective QoS flow for the 3GPP access, wherein the information about the non-reflective QoS flow includes a second QFI mapped to the second 5QI having the value greater than the threshold without separately including the second 5QI.

[0372] 59. The method of embodiment 58, wherein the second QFI is longer than the first QFI.

[0373] 60. The method of any of embodiments 58-59, wherein the second QFI is a 7-bit QFI, and wherein the 5QI has a value greater than 64.

[0374] 61. A core network, CN, node, wherein the CN node is adapted to perform the operations of any of embodiments 54-60.

[0375] 62. A core network, CN, node, comprising:

[0376] a network interface (1007) configured to provide communication with other nodes of a wireless communication network; and

[0377] a processor (1003) coupled with the network interface, wherein the processor is configured to provide network communications with other nodes of the wireless communication network through the network interface, and wherein the processor is further configured to perform the operations of any of embodiments 54-60.

[0378] Explanations for acronyms / initialisms used herein are provided below.

[0379] Abbreviation Explanation

[0380] 5GC 5G core network

[0381] 5CN 5G core network

[0382] 5G-AN 5G access network

[0383] 5GS 5G system

[0384] 5QI 5G QoS indicator

[0385] AF application function

[0386] AMF access and mobility management function

[0387] AMF access and mobility management function

[0388] AS access stratum

[0389] CP control plane

[0390] DL downlink

[0391] DN data network

[0392] DNN data network name

[0393] GFBR guaranteed flow bit rate

[0394] gNB NR Node B

[0395] MFBR maximum flow bit rate

[0396] NAS network access identifier

[0397] NCGI NR cell global identifier

[0398] NCR neighbor cell relation

[0399] NEF network exposure function

[0400] NF network function

[0401] NG-RAN NG radio access network

[0402] NR New Radio

[0403] NRF Network Repository Function

[0404] PCF Policy Control Function

[0405] PEI Permanent Equipment Identifier

[0406] PFDF Packet Flow Description Function

[0407] QFI QoS Flow Identity

[0408] QoE Quality of Experience

[0409] RLAU RAN-based Location Area Update

[0410] RNA RAN Notification Area

[0411] SA NR Stand-Alone NR

[0412] SBA Service-Based Architecture

[0413] SBI Service-Based Interface 5G

[0414] SDAP Service Data Adaptation Protocol

[0415] SDSF Structured Data Storage Function

[0416] SMF Session Management Function

[0417] SUPI Subscriber Permanent Identifier

[0418] UDSF Unstructured Data Storage Function

[0419] UL Uplink

[0420] UL CL Uplink Classifier

[0421] UPF User Plane Function

[0422] Xn-C Xn Control Plane

[0423] Xn-U Xn User Plane

[0424] CN Core Network (e.g., 5CN)

[0425] Embodiments herein are described in the context of 3GPP NR radio technology (3GPP TS 38.300 V15.0.0 (2017-12)). It should be appreciated that the problems and solutions described herein can be equally applicable to wireless access networks and user equipment (UE) implementing other access technologies and standards. Where embodiments can be suitable, NR is used as an example technology, and thus the use of NR in the description can be useful for understanding the problems and solutions to solving such problems. For example, some embodiments can also be applicable to 3GPP LTE, or 3GPP LTE and NR integration, also known as non-standalone NR, or EN-DC (EUTRA-NR - Dual Connectivity).

[0426] Information about reference documents 1 and 2 is provided below.

[0427] 1. 3GPP TS 23.501 V15.0.0 (2017-12), Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)

[0428] 2. 3GPP TS 37.324 V1.2.0 (2018-03), Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification (Release 15)

[0429] 3. 3GPP TS 38.300 V15.0.0 (2017-12), Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15)

[0430] Further definitions and embodiments are discussed below.

[0431] In the above-description of various embodiments of the present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0432] When an element is referred to as being "connected", "coupled", "responsive", or "in communication" to another element, it can be directly connected, coupled, responsive, or in communication to the other element or intervening elements can be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or "directly in communication" to another element, there are no intervening elements present. By way of example, an element A can be said to be "connected" or "coupled" to an element B if it is possible, and advantageous, for an element A to trigger an action by an element B directly or after a mere presence of an intervening element or a mere passage of time. Likewise, an element A can be said to be "indirectly connected", "indirectly coupled", "indirectly responsive", or "indirectly in communication" to an element B if there are one or more intervening elements present. It will be appreciated that for the sake of clarity, not all elements in the drawings can be labeled in order to not obscure one or more embodiments of the present inventive concepts. Like numbers indicate like elements in all drawings. In addition, the term "coupled" as used herein is intended to include any type of coupling, whether that is direct or indirect, mechanical, electrical, magnetic, hydraulic, or otherwise. In addition, the terms "component", "system", "platform", "interface", and the like as used herein are intended to refer to a computer-related entity, either hardware, software, or both. As an example, a component can be a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instructions supporting one or more processes or execution threads, a computer system, or one or more computers. By way of illustration, both an application running on a computer device and the computer device itself can be a component. One or more components can reside within a process and / or thread of execution and a component can be localized, static, and / or dynamic. As another example, a platform can be an operating system (OS) execution environment on a computer device and / or an application runtime environment dedicated to making programs highly executable. As used herein, the term "exemplary" merely means "serving as an example", "example" and not "preferred" or "advantageous over other examples". Thus, the example is merely one implementation and does not imply that any one feature or combination of features is necessary or necessary to one or more implementations or that the example is preferred over or superior to other examples. As used herein, the term "if" can be construed to mean "when" or "upon" or "in response to the happening of" or "in response to the condition of" provided that the condition is contrary. As used herein, the terminology or description used for a potential future event or action can be construed to mean that the potential future event or action is likely to occur or is likely to be performed. As used herein, the term "about" means approximately, roughly, around, or in the immediate vicinity of a numeric value (e.g., within 10% of the value). As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0433] It will be understood that, although the terms first, second, third, etc. can be used herein to describe various elements / operations, these elements / operations should not be limited by these terms. These terms are only used to distinguish one element / operation from another element / operation. Thus, a first element / operation in some embodiments can be termed a second element / operation in other embodiments without departing from the teachings of the present inventive concepts. Throughout the specification, the same reference numerals or the same reference designators will be understood to refer to the same or similar elements in various embodiments.

[0434] The terms "comprise(s)," "comprising," "include(s)," "including," "have(s)," "having," or "contain(s)," "containing," as used herein, are open-ended, and include one or more of the features, integers, elements, steps, components, or functions described herein, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. In addition, as used herein, the common abbreviation "e.g." (which is derived from the Latin phrase "exempli gratia") can be used to introduce one or more general examples, and should be interpreted in the same manner as the term "for example" or similar language. The common abbreviation "i.e." (which is derived from the Latin phrase "id est") can be used as an abbreviation for the phrase "that is," or similar language, to introduce one or more specific examples or features.

[0435] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. Alternatively, computer program

[0436] These computer program instructions can also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions / acts specified in the flowchart and / or block diagram block or blocks. Accordingly, embodiments of the present inventive concept can be embodied in hardware and / or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which can collectively be referred to as "circuitry," "a module" or variants thereof.

[0437] It should also be noted that in some alternative implementations, the functions / acts noted in the blocks can occur out of the order noted in the flowcharts. For example, two blocks shown in succession can in fact be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality / acts involved. Also, the functionality of a given block can be separated into multiple blocks and / or the functionality of two or more blocks can be combined into a single block, and / or a combination of these. Finally, while shown as being carried out at a single location in some of the flowcharts, the functionality / acts noted in the blocks can be carried out at different locations and / or by different parties than shown in the flowcharts. For example, the functionality / acts noted in the blocks can be carried out at a web server, a mobile device, a personal computer, etc. and / or by the user, an application provider, a service provider, etc.

[0438] Many modifications and variations of the embodiments described herein are possible and are intended to be within the scope of the present inventive concept. Accordingly, the subject matter of the above disclosure has been shown and described with particularities of certain examples. It is not intended to be limited to or by these examples. The disclosure is intended to cover all alternatives, modifications and equivalents which can be included within the spirit and scope of the present inventive concept. Therefore, the scope of the present inventive concept is to be determined as encompassing all such modifications, permutations, substitutions and equivalents within the spirit and scope of the inventive concept. To the extent not otherwise specified, the scope of the inventive concept includes such modifications, enhancements and other embodiments thereto within the purview of the patent statutes and judgments of equivalent specifications. Accordingly, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same or similar results could be substituted for the specific embodiments shown.

Claims

1. A method of operating a wireless terminal, UE, in communication with a base station, gNB, the method comprising: receiving (1103) a radio resource control, RRC, message from the base station, wherein the RRC message includes information that each of a plurality of quality of service, QoS, flows is reflective or non-reflective, and identifies a first data radio bearer, DRB, as a DRB for non-reflective QoS flows, and / or identifies a second DRB as a DRB for reflective QoS flows, and receiving (1115) a first data packet from the base station using a non-reflective QoS flow, wherein the first data packet includes a first data field and a first service data application protocol, SDAP, header field having a QoS flow identity, QFI, characterized in that the first SDAP header field includes the QFI and a reflective QoS to DRB mapping indication, RDI, of the first SDAP header field, wherein if the value of the RDI is set to 1, the UE processes the QFI field in the SDAP header and stores the QoS flow to DRB mapping of the data field as a QoS flow to DRB mapping rule for UL.

2. The method of claim 1, further comprising: receiving (1117) a second data packet from the base station using a reflective QoS flow, wherein the second data packet includes a second data field and a second SDAP header field having a QFI and a RDI and a reflective QoS indicator, RQI, wherein the length of the QFI of the second SDAP header field is less than the length of the QFI of the first SDAP header field, wherein the presence of the RQI indicates to the UE that the second data packet is subject to reflective QoS flow handling.

3. The method of claim 2, further comprising: establishing (1107) the first data radio bearer, DRB, between the wireless terminal and the base station; and establishing (1107) the second DRB between the wireless terminal and the base station; wherein providing the communication of the first data packet comprises providing the communication of the first data packet using the non-reflective QoS flow on the first DRB; wherein providing the communication of the second data packet comprises providing the communication of the second data packet using the reflective QoS flow on the second DRB.

4. The method of claim 3, wherein the information from the RRC message identifies the first DRB as a DRB for non-reflective QoS flows, and / or wherein the information from the RRC message identifies the second DRB as a DRB for reflective QoS flows.

5. The method of any of claims 2-4, wherein the QFI of the second SDAP header field is a 6-bit QFI.

6. The method of claim 1, further comprising: providing the communication of the data packet comprises providing the communication of the data packet using the non-reflective QoS flow on the first DRB.

7. A wireless terminal, UE, wherein the wireless terminal is adapted to perform operations according to any of claims 1-6. ​ 8. A method of operating a base station, gNB, of a wireless communication network in communication with a wireless terminal, UE, the method comprising: receiving (1203) information from a core network, CN, node regarding a plurality of Quality of Service, QoS, flows being respectively reflective or non-reflective; transmitting (1204) a Radio Resource Control, RRC, message to the wireless terminal indicating the information received from the CN and identifying a first Data Radio Bearer, DRB, as a DRB for non-reflective QoS flows and / or a second DRB as a DRB for reflective QoS flows, and sending (1215) a first data packet to the wireless terminal using a non-reflective QoS flow, wherein the first data packet comprises a data field and a first Service Data Application Protocol, SDAP, header field having a QoS Flow Identity, QFI, and wherein the QFI is used for the first data packet based on the information from the CN node, characterized in that the first SDAP header field comprises a Reflective QoS to DRB Mapping Indication, RDI, wherein if the value of the RDI is set to 1, the UE shall store the QoS flow to DRB mapping of the data field as a QoS flow to DRB mapping rule for UL.

9. The method of claim 8, further comprising: providing (1217) communication of a second data packet between the base station and the wireless terminal using a reflective QoS flow, wherein the second data packet comprises a second data field and a second SDAP header field having a QFI, the QFI being used for the second data packet based on the information from the CN node.

10. The method of claim 9, wherein the second SDAP header field further comprises an RDI and a Reflective QoS Indicator, RQI, wherein a length of the QFI of the second SDAP header field is less than a length of the QFI of the first SDAP header field, wherein a presence of the RQI indicates to the UE that the second data packet is subject to reflective QoS flow handling.

11. The method of any of claims 8-10, further comprising: establishing (1207) a first Data Radio Bearer, DRB, between the base station and the wireless terminal; and establishing (1207) a second DRB between the base station and the wireless terminal; wherein providing communication of the first data packet comprises providing communication of the first data packet using the non-reflective QoS flow on the first DRB; wherein providing communication of the second data packet comprises providing communication of the second data packet using the reflective QoS flow on the second DRB.

12. The method of claim 10, wherein the information from the CN node identifies the first DRB as a DRB for non-reflective QoS flows and / or wherein the information from the RRC message identifies the second DRB as a DRB for reflective QoS flows. ​ 13. The method of any of claims 9-12, wherein the QFI of the second SDAP header field is a 6-bit QFI.

14. The method of any of claims 9-13, wherein the second SDAP header field includes the QFI of the second SDAP header field, an RQI and an RDI of the second SDAP header field.

15. The method of claim 8, further comprising: establishing (1207) a data radio bearer, DRB, between the base station and the wireless terminal; wherein providing communication of the data packets comprises providing communication of the data packets using the non-reflective QoS flow on the DRB.

16. A base station, gNB, wherein the base station is adapted to perform operations according to any of claims 8-15.

17. A computer program product having stored thereon computer program instructions that, when executed by a processor, cause the processor to carry out the method of any of claims 1-6 and 8-15.

18. A tangible computer-readable medium having stored thereon computer program instructions that, when executed by a processor, cause the processor to carry out the method of any of claims 1-6 and 8-15.

Images