Data packet handling in a wireless communication network

Abstract

Various aspects of the present disclosure relate to a UE for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine that an uplink data packet is part of a data flow of a QoS flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmit the uplink data packet based at least in part on the QoS parameter.

Description

DATA PACKET HANDLING IN A WIRELESS COMMUNICATIONNETWORKTECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to the field of managing (e.g., processing, transmitting, receiving, obtaining, outputting) data packets. In particular, this document defines a user equipment (UE), a processor and methods thereof.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise known as network equipment (NE), supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an examplestep that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] A wireless communication system (also referred to as a wireless communication network or simply a wireless network), such as, a 5G system (5GS) or a 6G system (6GS), may support higher throughput (e.g., bitrate), as well as greater network flexibility compared to other wireless communication systems, such as a 4G system. For example, in a 5GS, service providers can relocate (e.g., transfer, migrate, move) functions, applications, services, or the like between different networks, clouds, or the like environments. Furthermore, 5GS allows service providers to respond to changing demands and to implement different deployment strategies without interrupting services.

[0005] The main Quality of Service (QoS) model in 5GS is based on QoS flows. The QoS flow is the finest granularity of QoS differentiation in 5GS. Each QoS flow is associated with a type. The type may indicate that a guaranteed flow bit rate is required (e.g., a Guaranteed Bit Rate (GBR) QoS flow). Alternatively, the type may indicate that guaranteed flow bit rate is not required (e.g., non-GBR QoS flow). For a Packet Data Unit (PDU) Session, there may be at least a default QoS flow established during a PDU Session establishment and such default QoS flow may be a non-GBR QoS flow. Additionally, a dedicated QoS flow may be established within (e.g., for) the PDU Session, for example, for a data flow, such as a Service Data Flow (SDF).

[0006] An SDF may represent traffic (e.g., data) for an application session that may be characterized (e.g., defined, identified) by specific packet header parameters (e.g., a source Internet Protocol (IP) address, a destination IP address, a part number, a device identifier or an Ethernet addresses, etc.). An SDF filter may include a set of one or more packet flow header parameter values or ranges that may be used to identify one or more of packet flows (e.g., IP or Ethernet packet flows) constituting the SDF. For example, if a customer uses (e.g., utilizes, engages with) multiple different application servers for an offered application service, then the network may detect that downlink (DL) packets having a source IPaddress / prefix from one of the application servers is associated with the customer and can be identified as one or more SDFs. The network can assign one or more separate QoS flows to these SDFs. The terms SDF, data flow, traffic flow, sub-QoS flow, service flow, IP flow and / or application flow may be used interchangeably hereinafter.

[0007] There is provided a user equipment, UE, for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine that an uplink data packet is part of a data flow of a quality of service, QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmit the uplink data packet based at least in part on the QoS parameter.

[0008] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: determine that an uplink data packet is part of a data flow of a quality of service, QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmit the uplink data packet based at least in part on the QoS parameter.

[0009] There is a further provided a method performed by a user equipment, UE, the method comprising: determining that an uplink data packet is part of a data flow of a quality of service, QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmitting the uplink data packet based at least in part on the QoS parameter.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0011] Figure 2 illustrates an example of a framework for a QoS model in accordance with aspects of the present disclosure.

[0012] Figure 3 illustrates an example of a process flow for QoS establishment in accordance with aspects of the present disclosure.

[0013] Figure 4 illustrates a signalling diagram in accordance with aspects of the present disclosure.

[0014] Figure 5 illustrates an example of a framework for classifying data flow for a QoS model in accordance with aspects of the present disclosure.

[0015] Figure 6 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0016] Figure 7 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0017] Figure 8 illustrates an example of a NE in accordance with aspects of the present disclosure.

[0018] Figure 9 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0019] A QoS flow may include one or more data flows, where each data flow may be associated with a latency requirement (e.g., time sensitivity, time criticality) based on a data type associated with the data flow (i.e., a type of data provided by the data flow). Examples of data type may include, but is not limited to, audio streaming, video streaming, Simple Mail Transfer Protocol (SMTP) traffic for email exchange, Transmission Control Protocol (TCP) traffic for email exchange, or non-streaming Hypertext Transfer Protocol (HTTP) traffic (e.g., mapped on a same non-GBR QoS flow), or a combination thereof.

[0020] Some wireless communication systems may establish (e.g., setup) and maintain separate QoS flows for different data flows. For example, in some cases, separate QoS flows may be established and maintained for different data flows that have different traffic characteristics, resulting in a higher number of QoS flows. Traffic characteristics may include periodicity, data rate, maximum data burst volume changes. Additionally, QoS flow-related procedures, such as a QoS flow establishment procedure, a QoS flow modification procedure, and / or a QoS flow release procedure result in a PDU session modification procedure. The PDU session modification procedure may include N2 SessionManagement (SM) signalling (e.g., between a RAN node, such as a base station, and a Session Management Function (SMF)), N1 SM signalling (e.g., between a UE and an SMF), and N4 signalling (e.g., between an SMF and one or more User Plane Functions (UPFs)). Accordingly, establishment and maintenance (e.g., modification, release) of separate QoS flows for different data flows yields increased signalling overhead.

[0021] Examples described herein generally relate to data traffic differentiation for different SDFs associated with a same QoS flow. The data traffic differentiation may be referred to as flexible data traffic differentiation or adaptive data traffic differentiation hereinafter. The QoS flow may be a non-GBR QoS flow.

[0022] Aspects of the present disclosure are described in the context of a wireless communications system.

[0023] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LIE- A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0024] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a networkelement, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.

[0025] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0026] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0027] A UE 104 may be able to support wireless communication directly with otherUEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0028] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0029] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0030] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0031] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0032] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0033] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0034] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0035] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0036] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0037] Figure 2 illustrates an example of a framework for a QoS model 200 in accordance with aspects of the present disclosure.

[0038] The QoS model 200 may include a PDU session 260, which may be established (e.g., setup) between a UE 210 and an anchor UPF 225, which may be examples of corresponding UE and NE as described herein. The anchor UPF 225 may be a designated node that "anchors" a user’s data session. The UPF 225 may be configured to, capable of, or operable to assign an IP address and IP configuration for the UE 210, and provide (e.g., output, transmit, forward) one or more of the IP address and IP configuration to the UE 210. For example, the UPF 225 may assign and provide the IP address and the IP configuration to the UE 210 based on (e.g., using, according to) the PDU session 260.

[0039] The PDU session 260 comprises at least one QoS flow 264 between the UE 210 and the UPF 225. The at least one QoS flow 264 may comprise a default QoS flow 264. The default QoS flow may be automatically assigned to a user session when the UE 210 connects to the network. In some examples, there can be one or more additional QoS flows for specific data flows. The PDU session 260 comprises an N3 tunnel 262 between the (R)AN 215 (or RAN node) and the anchor UPF 225. The N3 tunnel 262 may be a General Packet Radio Service (GPRS) Tunneling Protocol - User plane (GTP-U) tunnel. The N3 tunnel 262 may be a single N3 tunnel 262 for the PDU session 260.

[0040] The UE 210 and a (R)AN node 215 may configured to, capable of, or operable to establish a first DRB 266. For example, the UE 210 and the (R)AN node 215 may establish the first DRB 266 over a radio link (e.g., communication link, communication channel). The (R)AN node 215 may be an example of corresponding NE as describedherein with reference to Figure 1. One or more QoS flows can be mapped to a single DRB. For example, the (R)AN node 215 may be configured to, capable of, or operable to map the QoS flow 264 to the first DRB 266.

[0041] The UPF 225 may be configured to, capable of, or operable to perform packet detection and mapping to the QoS flow 264. Additionally, the UPF 225 may configured to, capable of, or operable to perform N3 marking (e.g., including one or more indications in an N3 tunnel header). The N3 marking may relate to information for the network to apply a QoS.

[0042] In the example of Figure 2, a first application server 252 and a second application server 254 may each be configured to, capable of, or operable to provide an application data flow to a first application 256 and a second application 258 associated with the UE 210 (e.g., stored at the UE 210, executing at the UE 210, or both), respectively via the QoS flow 264.

[0043] Figure 3 illustrates an example of a process flow 300 for QoS establishment in accordance with aspects of the present disclosure. In the example of Figure 3, the process flow 300 may be for establishing (e.g., setting up) a QoS flow. The process flow 300 may implement aspects (e.g., embodiments, features) of the wireless communication system 100, or may be implemented by aspects of the wireless communication system 100. For example, the process flow 300 may illustrate operations between a UE 310, a RAN 315, an SMF 320, an AMF 322, a UPF 325, a Policy Control Function (PCF) 330, and an Application Function (AF) 340, which may be examples corresponding UE and NE described herein. In the following description of the process flow 30, the operations between the one or more of the UE 310, the RAN 315, the SMF 320, the AMF 322, the UPF 325, the PCF 330, and the AF 340 may be transmitted and / or received in a different order than the example order shown, or the operations performed by the one or more of the UE 310, the RAN 315, the SMF 320, the AMF 322, the UPF 325, the PCF 330, and the AF 340 may be performed in different orders or at different times than the example order shown. Some operations may also be omitted from the process flow 300, and other operations may be added to the process flow 300.

[0044] In the example of Figure 3, in response to (e.g., if, based on) the SMF 320 and / or the PCF 330 determining or identifying (e.g., based on received information) that a specific data flow requires a QoS flow different from a default QoS flow, the SMF 320 and / or the PCF 330 may trigger a QoS establishment procedure, for example, to establish a dedicated QoS flow for the specific data flow. The terms SDF, data flow, traffic flow, subQoS flow, service flow, IP flow and / or application flow may be used interchangeably herein.

[0045] At step 371, the AF 340 may determine and output (e.g., transmit) one or more QoS requirements for a data flow associated with a specific service to the PCF 330. The one or more QoS requirements for the data flow associated with a specific service may be traffic requirements for an IP flow (5-tuple). The traffic requirements may comprise at least one of a packet delay or a data rate. In some examples, the specific service may be at least one of: video streaming, audio streaming, multimedia call (e.g., video call). The AF 340 may provide information for identifying the data flow (e.g. 5-tuple of IP packets or an application identifier) and classify (e.g., assign, define) the data flow characteristics (e.g., one or more traffic QoS requirements, such as a packet delay, a packet error rate, or a priority). In some examples, this provisioning of identification and classification information may be referred to as AF-requested QoS influence on the data flow. The data flow identification and associated QoS characteristics may be pre-configured, for example, in the PCF 330 or a Unified Data Repository (UDR).

[0046] At step 372, the PCF 330 may determine (e.g., derive) one or more Policy Control and Charging (PCC) rules for the data flow (e.g., an SDF), where a PCC rule may include (e.g., identify) the specific QoS requirements for the data flow. The PCC rule may comprise a QoS rule. The QoS rule may comprise traffic classification information, information for mapping to the QoS flow, or QoS parameters. The PCC rule may include the data flow identification and corresponding QoS characteristics. The data flow identification may comprise a traffic detection filter, such as an IP packet filter (e.g., a 5- Tuple containing a source IP address, a source port, a destination IP address, a destination port, and / or a transport protocol). A 5-tuple may uniquely identify a User Datagram Protocol (UDP) session or a Transmission Control Protocol (TCP) session. Thecorresponding QoS characteristic may be a pre-defined 5G QoS Identifier (5 QI) or a QoS Flow Identifier (QFI), which may be associated with or specific to a network operator. The PCF 330 may provide (e.g., transmit, signal) the one or more PCC rules to the SMF 320. Additionally, or alternatively, the PCF 330 may provide (e.g., transmit, signal) one or more QoS rules to the SMF 320. One or more of the PCC rules or the QoS rules may comprise QoS requirements for 5-tuple. The QoS requirements may be PDU set related QoS requirements.

[0047] In some examples, the one or more PCC rules may be pre-configured at the SMF 320 and can be activated or deactivated by the PCF 330.

[0048] At step 373, the SMF 320 may determine a QoS profile of the QoS flow (e.g., one or more of a Packet Delay Budget (PDB) or a Packet Error Rate (PER)). The SMF 320 may establish the dedicated QoS flow according to the one or more PCC rules. The SMF 320 may provide (e.g., transmit, signal) to the UPF 325 one or more N4 rules, including configuration information. The configuration may be for routing packets of the data flow to a QoS flow. The one or more N4 rules may include traffic detection rules (e.g., Packet Detection Rules (PDRs)) and packet handling policies that includes at least one of: a QoS Enforcement rule (QER), a Forwarding Action Rule (FAR), or a Usage Report Rule (URR).

[0049] Additionally, the SMF 320 may provide (e.g., transmit, signal, output) the QoS profile including the QoS requirements to the RAN 315. For example, the SMF 320 may output the QoS profile including the QoS requirements to the RAN 315 in an N2 SM container via the AMF 322.

[0050] At step 374, the UPF 325 may process (e.g., inspect, analyse) data packets received (e.g., obtained) from a first application 356 and a second application 358, and determine whether the data packets are associated with (e.g., belong) a QoS flow. The UPF 325 may route incoming DL packets (e.g., DL data packets) from the first application 356 and the second application 358 to a corresponding QoS flow. For example, the UPF 325 may route a first set of DL data packets received from the first application 356 to a first QoS flow and route a second set of DL data packet received from the second application 358 to a second QoS flow. The UPF 325 uses the PDRs, which are received in the N4 rules from the SMF 320, in order to determine the forwarding of the DL packets to acorresponding QoS flow. Each QoS flow may be associated with a QFI. The UPF 325 may include the QFI in each DL packet. The DL packet may be a PDU. The QFI may be included in a tunnel encapsulation header (e.g., a GTP-U packet header) used for a PDU session. For example, the first QoS flow may be identified by QFI-1 and the second QoS flow may be identified by QFI -2 in a GTP-U header of a corresponding DL packet. In some examples, there is a single GTP-U tunnel for the PDU session between the UPF 325 and the RAN 315.

[0051] At step 375, the RAN 315 may identify one or more DL data packets associated with (e.g., belonging to) a QoS flow, for example, based at least in part on a GTP-U marking, and handle the DL data packets according to QoS requirements of the QoS profile provided directly by the SMF 320, or via the AMF 322, at step 373. GTP-U marking may include information in a header of a GTP-U data packet corresponding to the QOS requirement of the QoS profile. The RAN 315 may establish two DRBs for each of the QoS flows, as shown in Figure 3, “DRB QoS flow 1” and “DRB QoS flow 2”. The RAN 315 may determine (or select) a DRB configuration based at least in part on one or more QoS characteristics for the QoS flow. The RAN 315 may decide the DRB configuration. A QoS characteristic may be a QoS parameter. For example, if a PER is less than or equal to a threshold a different Modulation and Coding Scheme (MSC) or different Radio Link Control (RLC) retransmissions may be configured for a corresponding DRB compared to a DRB that is associated with a PER that is greater than the threshold. By way of example, if a PER is low (e.g., 10'6) a different MSC or different RLC retransmissions may be configured for the DRB compared to a DRB for which the PER is high (e.g., 10'3).

[0052] Each QoS flow may be associated with a resource type. For example, the resource type may be at least one of: a non-GBR QoS flow, a GBR QoS flow, or a Delay- critical GBR QoS flow. In some examples, QoS characteristics, such as for 5G may contribute to setting node specific parameters for each QoS Flow (e.g., for 3GPP radio access link layer protocol configurations). For non-GBR QoS flows, the QoS characteristics may comprise at least one of: a default Priority Level (PL), PDB, or PER. In contrast to the non-GBR QoS flow, for a GBR QoS flow the QoS characteristics may comprise at least one of: one or more parameters from non-GBR flows; a Guaranteed Flow Bit Rate (GFBR)(e.g., for uplink (UL) and / or DL), a Maximum Flow Bit Rate (MFBR) (e.g., for uplink (UL) and / or DL), or a Maximum Burst Data Volume (MBDV).

[0053] The following parameters may apply for a PDU session level (or a network slice level): a session Aggregated Maximum Bit Rate (AMBR) (e.g., applicable to non-GBR QoS flows), a per UE Aggregate Maximum Bit Rate (UE-AMBR) (e.g., applicable to non- GBR QoS flows), and a per UE per Slice MBR (UE-Slice-MBR) (e.g., applicable to GBR and non-GBR QoS flows).

[0054] The AMF 322 may output (e.g., transmit, signal) the one or more QoS rules to the UE 310, for example, via the RAN 315 using an N1 SM container. The AMF 322 may output (e.g., transmit, signal) the QoS profile to the RAN 315 using an N2 SM container.

[0055] Table 1 is a table of “Standardized 5QI to QoS characteristics mapping” as described in clause 5.7.4 in 3GPP TS 23.501, vl8.3.0. Specifically for non-GBR QoS flows identified by 5QI 6, 7, 8, 9 or 10, as shown in Table 1 various traffic types or SDFs may be transmitted in the same QoS flow.Table 1 Standardized 5QI to QoS characteristics mapping

[0056] Different data flows like streaming (video or audio; in UL or DL), SMTP / TCP traffic for email exchange, or non-streaming HTTP traffic are mapped on the same non- GBR QoS flow. Such a non-GBR QoS flow may have a 5QI=6 / 7 and can be a part of the so called “Internet” PDU Session. The following use cases may apply:• For data upload e.g., as part of UL data transmission for Artificial Intelligence (Al) model training, a TCP packet may be dropped by the UE’s UL buffer (due to queue overflow). A TCP retransmission may apply and the data upload is received correctly at the end. The TCP re-transmission is not time critical for the sending and receiving application.• For a video calling application or video uplink streaming application, a Real-Time Transport Protocol (RTP) / QUICK packet may be dropped at the UE, wherein the reason may be due to UL transmission queue overflow, or due to reached maximum UL data rate limit like UE / Session AMBR. An RTP re-transmission may occur on the application layer, but the re-transmitted packet will be received at the receiver after an increase delay (e.g. more than 300ms) and the received retransmitted packet may not be valid / needed anymore.

[0057] Therefore, some data flows in the QoS flow may be more time critical for the application layer than other data flows.

[0058] One target for a more flexible QoS model in future communication systems is to avoid setting up and maintaining separate QoS flows for different data flows having minor difference in the traffic characteristics. If a separate QoS flow is setup for each traffic / data flow, it would result in high number of QoS flows. Each QoS flow setup, modification and release procedures may result in a PDU Session modification procedure. The PDU Session modification procedure may comprise N2 SM signalling (between RNA and SMF), N1 SM signalling (between UE and SMF) and N4 signalling to one or more UPFs. In other words, the setup and maintenance of many QoS flows tends to result in increased signalling to setup and release the QoS flows.

[0059] Examples described herein generally relate to a flexible (or adaptive) uplink traffic differentiation (e.g., for different data flows) within the same QoS flow (e.g. non- GBR QoS flow).

[0060] In the past, the wireless communication network establishes a new QoS flow for each data flow having a different QoS characteristic compared to an existing QoS flow. However, in case of multiple data flows, the establishment of multiple QoS flows tends to result in increased C-plane signalling. For example, a PDU Session may comprise 10-15 different data flows user over a default PDU Session.

[0061] Examples described herein generally relate to differentiated handling of uplink data flows inside a QoS flow. Differentiated handling of specific data flows inside the QoS flow may comprise the following functionalities on a single QoS flow:• identifying uplink packets belonging to a specific traffic / data flow inside the QoS flow; and• applying one or more QoS characteristics on the radio link transmission which are different from the QoS characteristics of the remaining traffic of the QoS flow.

[0062] Examples described herein tend to avoid to establishment of a separate QoS flow for each data flow, as this tends to result in increased signalling and many different QoS flows maintenance. Examples described herein may differentiate a specific data flow (mapping to one or more SDFs) and apply different handling of the data flow in the RAN. This tends to achieve higher application experience and user experience.

[0063] The QoS characteristics may be identified by the QoS parameters such as priority level (PL), PDB or packet error rate (PER). For example, a QoS flow may be setup with QFI / 5QI = 6. For this QoS flow, the default parameter values may be PL = 60, PDB = 300ms and PER = 10'6which may apply to all data flows. However, there may be one or more specific data flow(s) for which a higher priority for transmission is required in certain conditions. Such data flows may be identified by the UE and signalled to the SMF, or the CN (e.g., SMF or PCF) may identify such data flows. The data flows may be identified by a Packet Filter Set (PFS) used in signalling from / to the UE to / from SMF over N1 SM for UL packet identification. In the signalling from the SMF to the RAN, a data flow packet filter (or Packet Detection Rule (PDR)) can be used on N2 interface. The identification of the data flows and the corresponding action based on QoS characteristics (e.g. higher PL value) can be performed in the UE or SMF / PCF. For UL packet handling, either the UE may provide the UL packet filter to the SMF or SMF / PCF may identify the specific data flows which may require differentiated packet handling (e.g., resulting from the flow QoS characteristics) in the UL and / or in the DL. The flow QoS characteristics information may be at least one of:• A new parameter to be included in the N3 tunnel packet header (e.g., a packet marking parameter) having a scalar value (e.g. from 1 to 16). Each scalar value may be associated with a one or more QoS characteristics or parameter. The scalarvalues may be different from the values of the QFI or 5QI of a QoS flow. Each scalar value may be a Data Flow Identifier (DFI) or a Data Flow Category (DFC).• A standardized (or existing) QoS parameter having a value different from the value of the 5 QI of the QoS flow. In one example, the PL parameter of a specific data flow may be different from the PL of the QoS flow. For example, a QoS flow with QFI / 5QI = 6, the PL = 60, whereas the PL for a data flow corresponding to SDF1 may be 40 and the PL for or a data flow corresponding to SDF2 may be 50.

[0064] The UE may use the provided parameter and includes it in the N3 tunnel packet header. In one example of considering the differentiated flow identifier parameter, the following may apply:

[0065] Example 1 : For SDF1 of a video streaming (e.g. 3rd party App video call) traffic, the SMF may determine a DFI = 2 which translates into one or more QoS parameters corresponding to PL = 40 and / or PER =10'4. The PDB is the PDB of the QoS flow (e.g. PDB = 300ms).

[0066] Example 2: For SDF2 of an audio streaming (e.g. Spotify streaming) traffic, the SMF may determine a DFI = 3 which translates into one or more QoS parameters corresponding to PL = 50 and / or PER =10'3. The PDB is the PDB of the QoS flow (e.g. PDB = 300ms).

[0067] In examples described herein, the network (e.g. SMF) receives a notification that the UL traffic for a QoS flow may suffer of a congestion situation. The SMF (and / or with PCF) determines a policy that a certain data flow (or SDF) has to be handled with QoS characteristics different from the QoS characteristics of the current / established QoS flow. The certain data flow is identified by packet filter information (e.g. PFS for UL packets and or PDR for DL packets) and data flow QoS handling information (or QoS enforcement / action information) different from the default QoS characteristics of the QoS flow. The SMF may receive assistance information that the UL traffic for a QoS flow may suffer of a congestion situation in one of the following ways:• a notification sent by the UE including at least one of: data flow identification, QoS characteristics, and congestion information in the UL transmission. This notification can be transmitted in a PDU Session modification request;• a notification from the RAN including information that congestion in the UL transmission may occur (e.g. based on UL buffer status report from UE that buffer overflow may happen or based on UL data rate limitation); and• The SMF determines that the certain data flow (e.g., SDF) is transmitted over the QoS flow with lower QoS characteristics because currently there are sufficient network resources (e.g. in the current serving cell) so that the actual achieved QoS parameters / characteristics are higher than the QoS flow QoS characteristics.

[0068] The SMF may determine to apply:• UE-based solution: the SMF configures the RAN (e.g. via the N2 SM protocol) with at least one of the following information: a list of one or more data flows identified by a PDR and for each data flow, and one or more QoS parameters having values different from the default QFI / 5QI values of the QoS low.• RAN-based solution: the SMF configures the UPF (e.g. via the N4 interface) with information for differentiated data flow (e.g., SDF) identification information and corresponding data flow (e.g., SDF) packet handling information. In addition, the SMF may provide to the (Radio) Access Network ((R)AN) corresponding information, e.g. how many differentiated data flows are configured for this QoS flow, and for each differentiated data flow the data flow packet handling information. The data flow packet handling information may include the mapping information between the DFI (or DFC) parameter and QoS parameters value (such as indicated in Example 1 or Example 2 above).

[0069] The UE may be arranged to perform at least one of the following functions:• The UE may determine a congestion situation in the UL transmission based on UL buffer status report from UE that buffer overflow may happen or based on UL data rate limitation.• The UE transmits a notification to the SMF including at least one of: data flow identification, QoS characteristics, and congestion information in the UL transmission. This notification can be transmitted in a PDU Session modification request.• The UE receives a QoS rule information from the SMF indicating that for a QoS flow one or more data flows may be handled with different QoS characteristics. The UE may apply internal differentiated handling of the UL packets in the UL queue or scheduling mechanism or the UE may request.• The UE may receive and process the SDAP enhancements to support the mapping of DRB to both QFI and DFI.

[0070] The (R)AN may be arranged to perform at least one of the following functions:• receiving information about one or more data flows (e.g. identified by a packet filter in RAN-based solution or by DFI in UPF-based solution) and associated with QoS parameters different from the QoS parameters of the QoS flow;• for the RAN-based solution, the (R)AN may receive a DL flow packet filter (e.g. PDR) and a QoS characteristic. The (R)AN inspects the DL data packets to determine which packets belong to the data flow identified by the DL flow packet filter (e.g. PDR);• for the UE-based solution, the (R)AN may receive (e.g. via Medium Access Control (MAC) request for UL resources) packet handling information which may include a Data Flow Identifier (DFI) parameter (or DFI);• the (R)AN may setup more than one DRBs associated with the QoS flow, wherein a DRB can be associated with a data flow (e.g. identified by a DFI). In other words, the DRB is associated with a QFI and a DFI. This association may be sent to the UE. The Service Data Adaptation Protocol (SDAP) in the RAN and in the UE may support the mapping of the DRB to both QFI and DFI. For example, the (R)AN may setup a DRB1 for the QoS flow with the default QoS parameters, DRB2 for the differentiated SDF-1 with DFI=2 and DRB3 for the differentiated SDF-2 with DFI = 3; and• The (R)AN may use a single DRB for the transmission of all data flows of the QoS flow, however, the RAN may apply a scheduling mechanism to handle packets of the differentiated data flow(s) in a different way corresponding to the QoS characteristics of the data flows (e.g. higher / lower PL, or higher / lower DRB, or lower / higher PER).

[0071] Examples described herein generally relate to 5GS. Thus, the names of the interfaces, protocols, functions and entities used in the examples described herein are in relation to 5GS. It will be understood that the examples described herein are also applicable to any future communication system, e.g. 6G System (6GS). It will also be understood that a future communication system may use different names for the same or similar interfaces, protocols, functions and entities described herein. Thus, adapting the examples described herein for future communication systems may comprise translating the names of the interfaces, protocols, functions and entities. For example, the N2 interface may be translated to a general interface between the (R)AN and the Core Network (CN) control plane, the N3 interface may be translated to a general interface between the (R)AN and the CN user plane, the N4 interface may be translated to a general interface between the Session management entity in the control plane and the user plane entity, etc. Furthermore, an SMF or UPF from 5GS may be correspondingly mapped to 6G-SMF or 6G-UPF in 6GS.

[0072] The SMF or UPF may implement a Charging Trigger Function (CTF) functionality which generates charging events to be sent to the Charging Function (CHF). The charging events may be enhanced with a new charging record identifying that differentiated traffic handling within the QoS flow is applied in the uplink direction and the corresponding data amount of the data flows for which the differentiated traffic handling applied. The CTF may use the Nchf services exposed by the CHF to send the charging event to the CHF.

[0073] Figure 4 illustrates a signalling diagram 400 for configuring differentiated data flow handling within a QoS flow in uplink in accordance with aspects of the present disclosure. The signalling diagram 400 may show the signalling flow for the procedure.

[0074] The signalling diagram 400 illustrates the signals and messages between a UE 410, a (R)AN 415, an SMF 420, a UPF 425, a PCF 430, a Unified Data Management(UDM) / Unified Data Repository (UDR) 435, an AF 440 and an Application Server (AS) 445.

[0075] The AF 440 may be an entity which is authorized to communicate with the 5GC control plane by using exposed Application Programming Interfaces (APIs). The AS 445 is the media or context server which sends and receives the service / application data to / from the application in the UE 410 via the user plane. The AF 440 and AS 445 may be the same physical node implementing different functionality to interface with the 5GC control plane and with the 5GC user plane.

[0076] The signalling diagram 400 starts with step 471, in which the UE 410 may send a PDU Session establishment request to establish a new PDU session or PDU Session modification request to modify an existing PDU Session. This request may be included in the N1 Session Management (SM) container to the session management function (SMF).

[0077] There are several alternative how the network control plane (e.g. SMF 420 and / or PCF 430) may determine to enable the differentiated packet handling within the QoS flow. One alternative “Alt-1” is presented in steps 472a and 472b:

[0078] In step 472a, the SMF 420 may request the Session Management (SM) subscription data from the data subscription data repository (e.g. UDM / UDR 435). The “session” may be identified by a Data Network Name (DNN) or Network Slice Identifier (S-NSSAI).

[0079] In step 472b, for the requested session, the UDM / UDR 435 may store information indicating that differentiated data flow handling within the (default) QoS flow of the PDU Session may or should be enabled. In other words, differentiated traffic handling is enabled for the PDU Session. The UDM / UDR 435 sends a reply which may include an indication of enabled differentiated packet handling.

[0080] The UDM / UDR 435 may also indicate the type of SM subscription (e.g. for gold type session or subscriber) and based on this the SMF 420 / PCF 430 may determine to activate / enable the differentiated traffic handling with a QoS flow.

[0081] Another alternative for the network control plane (e.g. SMF 420 and / or PCF 430) to determine to enable the differentiated packet handling within the QoS flow is presented in alternative “Alt-2” as steps 373a to 373e:

[0082] In step 473a, the 5GS / 6GS may expose a service / network API to the AF 440 wherein the API may be used by an authorised AF to request for specific service requirements (e.g. QoS requirements). The AF 440, which is associated with an application server transmitting service data, can request the communication network to handle the service data flow (or the service packets) with specific QoS requirements. For example, the AF 440 may perform provisioning of traffic characteristics for 1) the UE 410 or group of UEs or 2) for the traffic associated with the application (e.g. identified by data flow identification). The AF 440 sends a request to the UDM / UDR 435 which may include data flow information and QoS / QoE requirements.

[0083] The AF 440 may send this information to a Network Exposure Function (NEF). The NEF may store this information at the UDR as application subscription data, or as UE subscription data. The AF 440 sends to the NEF a request to reserve resources using Nnef AF Request QoS Create request message, e.g. including among other parameters at least one of the following: a Generic Public Subscription Identifier (GPSI) or External Group ID, AF Identifier, Flow description(s) (e.g. data flow packet filters) or External Application Identifier, QoS reference or individual QoS parameters, Alternative Service Requirements, and DNN, S-NSSAI. Specifically, the parameters for the data flow identification and the QoS / QoE requirements may be relevant for examples described herein.

[0084] In step 473b, the SMF 420 may send a policy association establishment request to the PCF 430, e.g. including the UE ID e.g. Subscription Permanent Identifier (SUPI)), DNN, S-NSSAI and other parameters.

[0085] In step 473c, the PCF 430 may request SM subscription data from the UDR 435. The PCF 430 may request subscription data associated with the SUPI, or policy data or application data from the UDR 435 by using the signalling keys SUPI, DNN, or S-NSSAI.

[0086] In step 473d, the UDR 435 sends a reply message which may include a new indication that the differentiated packet handling within the QoS flow is enabled for the UE 410 or for the specific PDU Session.

[0087] In step 473e, the PCF 430 creates one or more PCC rules for the PDU Session and sends them to the SMF 420, which is considered as a policy association establishment reply message to step 373b. The PCC rule may contain at least one of: Flow Description information (e.g. a set of service data flow filters or 5-tuples), a QoS requirement, and an indication for enabled differentiated packet data flow handling within a QoS flow. The reply message may comprise at least one of: a data flow filter, QoS requirements, and an indication on differentiated packet handling.

[0088] In step 473f, the SMF 420 may complete the PDU Session establishment procedure by setting up a default QoS flow for any traffic associated with the PDU Session. The SMF 420 may determine to allocate the traffic of all data flow flows on the default QoS flow if the network is underloaded. For example, if the network is underloaded and the data / service flows with higher QoS characteristics can be successfully transmitted over a QoS flow with lower QoS characteristics. In other words, the SMF 420 may determine to not set up a separate QoS flow for the SDF-1 but transmit the SDF-1 on the QoS flow with lower QoS characteristics based on the current available network resources.

[0089] Step 473g, shows another alternative for the network control plane (e.g. SMF 420 and / or PCF 430) to determine to enable the differentiated packet handling within the QoS flow; which is labelled as “Alt-3”. In Alt-3, the AF 440 may send a request for QoS handling for the UE 410 or group of UEs. The request may include at least one of the parameters: a data flow description information and the traffic characteristics information (e.g., the QoS or QoE requirements). The AF 440 may send such a request to the PCF 430 and the PCF 430 may create a PCC rule which is sent to the UE 410. The AF 440 may also send such a request to the SMF 420. The request is sent from the AF 440 to the SMF 420 may comprise at least one of data flow information and QoS / QoE requirements.

[0090] In step 474, the SMF 420 may store in the PDU Session (or SM) context as per QoS flow information at least one of: an indication that differentiated data flow handlingfor the QoS flow is enabled; identification information (e.g. packet filter) of one or more data flows and 3) the QoS characteristics / parameters applicable for each data flow.

[0091] If the QoS traffic characteristics of one or more data flows (e.g. SDF-1 and SDF-2) are different from the default QFI / 5QI (e.g., the default QoS characteristics) assigned to the current (default) QoS flow of the PDU Session, the SMF can decide to establish the default QoS only. Such decision in the SMF 420 may be determined based on at least one of:• the traffic characteristics of the different data flows being similar. For example, if the SDF-1 has requirement of PDB 250ms and the current QoS flow has a PDB of 300ms, the SMF 420 can decide to not establish a separate QoS flow for SDF-1, but the SDF-1 traffic is transmitted over the current QoS flow with PDB = 300ms; and• the SMF 420 being aware that currently the network is underloaded, or the load conditions in the cell where the UE 410 is located are low, so that the data packets of the QoS flow will experience better QoS characteristics than the QFI parameters of the QoS flow. For example, the PDB of the assigned QFI is 300ms (e.g. as in case of 5QI = 6), but the actual packet delay is less than 100ms because the cell load is low. So, even if the QoS characteristics of the SDF-1 indicate that the PDB should be 100ms, the SMF 420 may decide to not establish a separate QoS flow for SDF-1, but the SDF-1 traffic is transmitted over the current QoS flow with PDB = 300ms.

[0092] In step 475, the storing of the SM context that differentiated data flow handling for the QoS flow does not necessarily mean that the SMF 420 will activate the differentiated data flow handling in the user plane. The SMF 420 may first determine to let the data flow to be transmitted over the existing (e.g. default) QoS flow. Later, upon certain conditions, the SMF 420 may determine to handle the data flow in differentiated way.

[0093] For example, the SMF 420 may rely on an event or condition detected in the network. The possible events may be based on at least one of:• the RAN 415 condition, which can be e.g. signalled from RAN 415 to SMF 420; as described in step 475a.• the network conditions (including both RAN 415 and CN), e.g. SMF 420 subscribes for analytics with Network Data Analytics Function (NWDAF). For example, the SMF 420 may subscribe for network performance analytics for certain service experience (e.g. video or audio streaming service experience). The NWDAF may create the analytics based on information from the AF 440 or AS 445. When the QoE or service analytics indicate that the service does not meet the application requirements, or is close to not meet the application requirements, the SMF 420 may determine to activate the differentiated data flow handling as described in steps 476 or 477.• determining at UPF 425 / RAN 415 that the DL data rate limit (e.g. AMBR for the UE 410, or DL Session AMBR or slice Maximum Bit Rate (MBR)) is about to be reached. For example, if the current aggregated data rate is above 80% of the data rate limit. Thus, there is a high probability of dropping a DL packet at the UPF 425 or RAN 415. Upon such determination, the RAN 415 or UPF 425 may inform the SMF 420. The SMF 420 may determine to activate the differentiated packet handling as described in step 475c in order to avoid dropping of more critical data flows. For example, assigning a higher QoS characteristic (e.g. PL or PDB) to a more time critical packets for voice / video streaming application may result in avoiding packet dropping of this traffic but dropping packets of other traffic (e.g. background file download). The user may not notice the increased file download time but may notice an interruption of the voice / video streaming.

[0094] In step 475a, the UE 410 may implement internal means to detect whether an existing data flow may become congested (e.g. in the UL transmission direction). The UE 410 may send a notification to the SMF 420 indicating that one or more data flows (e.g. identified by packet data filters, or application identifier) may become congested and / or indicating the traffic QoS requirements for the data flow. The UE 410 may also trigger this notification in case of changed traffic QoS characteristics as required from the application layer. For example, the change of traffic QoS characteristics may occur due to changed resolution of a video call or video streaming. The notification may be a PDU Sessionmodification request which may comprise at least one of: an data flow description, QoS requirements, and congestion indication.

[0095] For example, the UE 410 may send a PDU Session modification request message to the SMF 420 including at least the data flow description (e.g. packet filter or data flow description), traffic QoS requirements or characteristics, and a congestion indication.

[0096] In one option, the UE 410 may also indicate its capability to apply differentiated packet handling of different traffic data flows within a QoS flow. This indication may be used by the SMF 420 to determine to apply the UE-based solution as per steps 476, 477 and 478.

[0097] In step 475b, UE 410 reports UL buffer status report to the RAN node 415 as part of the MAC reports sent to the RAN node 415.

[0098] In step 475c, the RAN 415 may determine that the UL data transmission for the QoS flow or the PDU Session may become congested. For example, the RAN node 415 may have received the UL buffer status reports as per step 475b. If the UE 410 indicates that maximum UL buffer is about to reach a specific threshold level and packets may be dropped, or the packets delay budget for a packet in the buffer may expire, the RAN 415 may determine a congestion or load situation in the UL transmission. In another example, the RAN 415 may determine that the Session AMBR, UE AMBR or Slice MBR in the UL is about to be reached.

[0099] If the SMF 420 stores in the SM context an information that specific data flows may require QoS characteristics different from the QoS flow characteristics (and the specific data flows are transmitted via the QoS flow), the SMF 420 may send a request to the (R)AN 415 to subscribe for notification when the packets (e.g., UL packets) of the QoS flow may potentially experience congestion, e.g., the packets may be dropped from the UL queue (or a potential queue threshold is reached) for one or more of the currently established QoS flows of the PDU Session. The potential buffer / queue overflow for the QoS flow may happen due to a cell load. Another example of notification event can be thatthe data rate limit (e.g. AMBR or MBR) reaches a certain threshold, wherein the SMF 420 may also indicate the threshold, e.g. 90%.

[0100] In step 475d, the (R)AN 415 may send an N2 SM Notification to the SMF 420 indicating a certain for load condition in the UL. The load condition in the UL may indicate UL congestion. There may be multiple meanings of the indication sent to the SMF 420. For example, the indication may indicate congestion in the RAN 415. In another example, the indication may indicate the status of a specific QoS flow, e.g., that packets of a QoS flow identified by a QFI, e.g. non-GBR flow, are about to be dropped or were already dropped. The RAN 415 may also indicate congestion in UL data transmission, and may further indicate the reason for congestion (e.g., UL buffer status report reached a threshold, Session AMBR, UE AMBR or Slice MBR in the UL is about to be reached).

[0101] In step 475e, the UPF 425 may determine that the UL data rate limit (e.g. AMBR for the UE for the UL, or UL Session AMBR or Slice MBR for the UL) is about to be reached., as described in step 475. The SMF 420 may have subscribed with UPF 425 for notifications and may have indicated the threshold level for sending a notification, e.g., the threshold may be 90% of the maximum data limit. The UPF 425 sends a notification to the SMF 420 indicating the reached threshold level. The notification may indicate UL congestion.

[0102] In step 475f, if the SMF 420 doesn’t know the data flow(s) (e.g., SDF) requirements as described in step 473, the SMF 420 may request UPF 425 to report information about the current data flows in the QoS flow. The UPF 425 may report one or more packet filters or protocol details (e.g., TCP or User Datagram Protocol (UDP) port numbers) and the SMF 420 may determine one or more data flows with specific traffic requirements. For example, the SMF 420 may request for data analytics (e.g., from the NWD AF) or consult with other data based to provide the traffic characteristics for data flows identified by the UPF 425. The SMF 420 determines that there are data flow(s) with specific traffic characteristics (e.g. UL video streaming) and the SMF 420 determines to prioritise such data flow(s).

[0103] Based on input as described above, the SMF 420 may determine to handle the specific data flow in a differentiated way and the SMF 420 may perform at least one of the following procedures:A. based on a trigger event from step 475 / 475a, the SMF 420 may determine to set up a new QoS flow for the traffic with different QoS characteristics. The SMF 420 may not set up a new QoS for the data flow from the start of the data flow, but the SMF 420 triggers the new QoS flow establishment based on certain network conditions;B. the SMF 420 may activate the differentiated data flow handling in the user plane within the existing QoS flow and decide to apply the RAN-based solution; andC. the SMF 420 may activate the differentiated data flow handling in the user plane within the existing QoS flow and decide to apply the UPF -based solution.

[0104] The determination whether to apply option B) and C) may be based on the capabilities of the (R)AN node 415 serving the UE 410 or PDU Session. For example, if the (R)AN 415 does not support packet inspection, the SMF 420 may determine to apply the UPF -based solution.

[0105] The SMF 420 may learn the (R)AN node 415 capabilities either during step 475a, step 476a, step 477a, or during step PDU Session establishment procedure when the (R)AN 415 replies to the establishment of the default QoS flow (e.g. before step 474).

[0106] The steps 476 - 478 show one possible solution denoted as UE-based solution and the details are as follows:

[0107] In step 476, if the SMF 420 determines to apply the UE-based solution, the SMF 420 may derive a (sub-QoS) data flow packet handling information which may comprise at least a data flow identifier (DFI, or data packet filter) and corresponding QoS characteristics of the (sub-QoS) data flow. For example, the DFI is a scalar value which isassociated with corresponding QoS parameters different from the QoS parameters of the default 5 QI.

[0108] For example, the SMF 420 may send a PDU Session modification request or (in case of step 475a the SMF 420 has received PDU Session modification request) a PDU Session modification reply to the UE 410. The message to the UE 410 may include at least one of: the QoS flow information including the identification of sub-QoS flows (e.g. with packet data flow filters) and the corresponding QoS characteristics. The PDU Session modification request / reply may comprise a QoS rule including PFS(s) with associated QoS parameter.

[0109] In step 477, the UE 410 receives and stores in the PDU Session context the information about sub-QoS flows and the corresponding QoS traffic characteristics. The UE 410 may apply strategies about differentiated queueing mechanisms (e.g., in the UL buffer for the QoS flow) to consider the QoS traffic characteristics of the different data flows. For example, the UE 410 may transmit the packets of a specific data flow with higher priority compared to the packets of the rest of the data flows.

[0110] In step 478, the UE 410 may indicate in the signalling to the RAN node 415 (e.g., using MAC layer signalling in a MAC request) that UL resources are required for packets with higher priority. For example, the UE 410 may use the UL Buffer Status Report (BSR) for the signalling and indicate that there are packets with higher DFI which are about to expire. In another example, the UE 410 may request UL resources and indicate that the resources are for higher DFI packets. The RAN 415 may schedule UL resources for data transmission. The UE 410 may send such indication as part of an enhanced UL buffer status report and optionally the UE 410 may include the DFI of the data flow. The BSR may include a DFI value.

[0111] Steps 479a and 479b show one possible solution denoted as (R)AN-based solution and the details are as follows:

[0112] In step 479a, if the SMF 420 determines to apply the RAN-based solution, the SMF 420 may derive a (sub-QoS) data flow packet handling information which may comprise at least a data flow identifier (DFI, or data flow category, DFC) parameter, theassociated packet filter and the QoS characteristics of the (sub-QoS) data flow. For example, the DFI is a scalar value which is associated with corresponding QoS parameters different from the QoS parameters of the default 5QI.

[0113] Optionally a DFI = 0 associated with default 5QI may be assigned; DFI = 1 associated with PL = 60, PDB = 200ms (and wherein the remaining QoS parameters of the default 5QI apply); DFI = 2 associated with PL = 50 (and wherein the remaining QoS parameters of the default 5 QI apply).

[0114] The SMF 420 may send to the (R)AN 415 a N2 SM information container (e.g., via the AMF) to inform the RAN 415 that one or more data flows within the QoS flow may need differentiated handling. The N2 SM information container may comprise a QoS flow modification request with the following additional information for the QoS flow: a list of one or more DFIs, the associated data flow packet filter and the associated QoS parameters applicable for the (sub-QoS) data flow. This information is associated with the QoS flow, e.g., with the QFI. The N2 SM notification may comprise at least one of: a QFI, and a list of PDRs with associated DFI or QoS parameters. The N1 SM container may comprise a PDU Session modification request comprising a QoS rule that may include a PFS and DFI.

[0115] The SMF 420 may send to the UE 410 a N1 SM information container (e.g., PDU Session modification request message) to inform the UE 410 that one or more data flows (e.g., sub-QoS flows) within the QoS flow may need differentiated handling. The N1 SM information container may comprise at least one of: a list of one or more DFIs, the associated data flow packet filter and the associated DFIs.

[0116] The (R)AN 415 may send a reply containing a result indication of the request. For example, the result indication may be positive, meaning that the (R)AN 415 acknowledges the reception and handling of the request; or the result indication can be negative, meaning that the (R)AN 415 rejects the request. If the result indication is negative, the SMF 420 may decide to either apply the UPF based solution or to establish a new QoS flow for the data flow.

[0117] For example for a non-GBR QoS flow, the QFI for the (default) QoS flow may be a 5QI = 6 with the QoS parameters PL = 60, PDB = 300ms, PER = 10'6, and a specificdata flow of SDF-1 for video streaming for which the SMF 420 may assign the QoS parameters PL = 50, PDB = 100ms and PER =10'4. The SMF 420 sends a N2 SM message with a new QoS profile for the (default) QoS flow and a new container information to identify the SDF-1 (e.g., called “sub-QoS flow” information) including the packet data flow filter of SDF-1 (e.g., 3-tuple or 5-tuple of IP header information) and the QoS parameters for SDF-1.

[0118] In step 479b, the RAN 415 receives and stores “sub-QoS flow” information associated with the QFI of the QoS flow, wherein this can be stored in the UE’s 410 access stratum context, specifically in the PDU Session context. Based on the QoS parameters of the sub-QoS flow, the (R)AN 415 applies different strategies to transmit the DL packets of the (default) QoS flow and the DL packets of the sub-QoS flow identified by the DFI (or the sub-QoF flow packet filter). Based on the QoS parameters of the sub-QoS flow, the RAN 415 determines whether to establish a new DRB corresponding to the QoS parameters of the sub-QoS flow, or whether to use an enhanced scheduling / queueing mechanism inside the single DRB for the QoS flow. The RAN 415 may configure a new DRB for each DFI within the same QoS flow. The new DRB may be associated with a QFI and a DFI.

[0119] The RAN node 415 may apply (deep) packed inspection of the DL packets of the QoS flow by applying the sub-QoS flow filter (e.g. PDR) received from the SMF 420. By this, the RAN 415 determines the DL traffic corresponding to the sub-QoS flow packet filter.

[0120] The (R)AN 415 may setup more than one DRBs associated with the QoS flow, wherein each DRB is associated with one or more sub-QoS data flows (e.g. identified by a DFIs). In other words, the DRB is associated with QFI and DFI; and this association may be sent to the UE 410 correspondingly. In this case the Service Data Adaptation Protocol (SDAP) in the RAN 415 and in the UE 410 may be enhanced to support the mapping of DRB to both QFI and DFI. For example, the (R)AN 415 may setup a DRB1 for the QoS flow with the default QoS parameters using QFI = 6 and DFI=0, DRB2 for the differentiated SDF-1 with DFI=2 and DRB3 for the differentiated SDF-2 with DFI = 3. The RAN 415 may assign a DFI value to the sub-QoS flows and use this DFI value for each sub-QoS flow in the signalling with the UE 410 in the SDAP layer. For example, the RAN415 assigns the following associations: DRB1 maps to the set [QFI=6 and DFI=0], DRB2 maps to the set [QFI=6, DFI=2], and DRB2 maps to the set [QFI=6, DFI=3],

[0121] Alternatively, the (R)AN 415 may continue to use a single DRB associated with the QoS flow, but the RAN 415 applies enhanced scheduling / queueing mechanism for the DRB. The enhanced scheduling / queueing mechanism means that the incoming packets in the DL buffer for the QoS flow are marked with different priorities and e.g. the packets belonging to the sub-QoS flow (e.g., the packets of the SDF-1) are treated with higher priority than the rest of the packets of the QoS flow. For example, when the DL packets enter the buffer, a timestamp and the PDB is associated with the packet. When the packet is about to expire in the buffer (e.g., due to delay reaching 80% of the PDB), the RAN 415 may schedule the packet may jump the queue and be schedule for sooner transmission.

[0122] If the reflective QoS indication is set up in the DRB transmission, the UE 410 determines to apply the same DRB for the UL data packets.

[0123] Examples described herein tend to enable one or more data flows with different QoS traffic characteristics to be transmitted over the same QoS flow using differentiated packet handling on the radio link. Especially in situations where many data flows with various QoS characteristics are to be transmitted, this tends to avoid setting up many QoS flows. Instead, differentiated packet handling is performed on a single QoS flow. The examples tend to enable a single QoS characteristic to be modified for a data flow. Furthermore, examples tend to offer a more fine granular handling of data flows instead of establishing new QoS flows for each data flow.

[0124] Examples described herein may be applied to public networks, e.g., a Public Land Mobile Network (PLMN), or to private networks, e.g., Non-Public Network (NPN) or a Standalone NPN (SNPN).

[0125] Examples described herein generally relate to differentiated packet handling within a single QoS flow in the DL. Examples described herein may also be applied to multiple QoS flows in a PDU Session. In the case of multiple QoS flows, the SMF / PCF may determine to apply the differentiated packet handling for data flows in each QoS flow separately.

[0126] Figure 5 illustrates a diagram for data flow classification and user plane marking for a QoS model 500 in accordance with aspects of the present disclosure.

[0127] The diagram for the QoS model 500 illustrates a PDU Session 560 setup between a UE 510 and an anchor UPF 525. The PDU Session 560 is used to assign an IP address and IP configuration to the UE 510. The PDU Session 560 comprises at least one QoS flow 564 between the UPF 525 and UE 510. The at least one QoS flow 564 may comprise a default QoS flow 564. There can be also additional QoS flows established for specific service flows or application flows. The PDU Session 560 comprises the N3 tunnel 562 between the anchor UPF 525 and the (R)AN 515 (or RAN node). The N3 tunnel 562 may be a GTP-U tunnel. The N3 tunnel 562 is a single N3 tunnel 562 for the PDU Session 560. Over a radio link, a first DRB 566 and a second DRB 567 is setup between the (R)AN node 515 and the UE 510. One or more QoS flows can be mapped to a single DRB.

[0128] A first App server 552 and a second App server 554 each provide an App data flow to a first App 556 and a second App 558 at the UE 510, respectively via the QoS flow 564.

[0129] The diagram for the QoS model 500 is an enhanced QoS model in the user plane to flow diagram for the QoS model 200 described above in relation to Figure 2. The term “enhanced” may mean that the traffic of a QoS flow is differentiated and 1) either mapped to different DRBs or 2) a different scheduling mechanism is applied in the RAN 515. The main difference to the flow diagram for the QoS model 200 is the use of two DRBs (first DRB 566 or the second DRB 567) within the same QoS flow 564. The RAN 515 maps the QoS flow 564 and DFI to the first DRB 566 or the second DRB 567; which corresponds to the RAN-based solution described herein. The UPF 525 performs packet detection and mapping to the QoS flow 564 and corresponding DFIs. The DFIs are represented by a continuous arrow between the UPF 525 and the UE 510. One of the DFIs corresponds to the data flow from the first App server 552 and the other DFI corresponds to the data flow from the second App server 554 The UPF 525 performs N3 tunnel marking for the QoS flow and the DFI. This corresponds to the UPF -based solution described herein.

[0130] Figure 6 illustrates an example of a UE 600 in accordance with aspects of the present disclosure. The UE 600 may include a processor 602, a memory 604, a controller606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0131] The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0132] The processor 602 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604 to cause the UE 600 to perform various functions of the present disclosure.

[0133] The memory 604 may include volatile or non-volatile memory. The memory 604 may store computer-readable, computer-executable code including instructions when executed by the processor 602 cause the UE 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 604 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0134] In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to cause the UE 600 to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604). For example, the processor 602 may support wireless communication at theUE 600 in accordance with examples as disclosed herein. The UE 600 may be configured to support a means for determining that an uplink data packet is part of a data flow of a QoS flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmitting the uplink data packet based at least in part on the QoS parameter.

[0135] The controller 606 may manage input and output signals for the UE 600. The controller 606 may also manage peripherals not integrated into the UE 600. In some implementations, the controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 606 may be implemented as part of the processor 602.

[0136] In some implementations, the UE 600 may include at least one transceiver 608. In some other implementations, the UE 600 may have more than one transceiver 608. The transceiver 608 may represent a wireless transceiver. The transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0137] A receiver chain 610 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 610 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 610 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 610 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0138] A transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 may also include at least one poweramplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0139] Figure 7 illustrates an example of a processor 700 in accordance with aspects of the present disclosure. The processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein. The processor 700 may optionally include at least one memory 704, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 706. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0140] The processor 700 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 700) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0141] The controller 702 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. For example, the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various componentsof the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0142] The controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction(s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein. The controller 702 may be configured to track memory address of instructions associated with the memory 704. The controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 702 may be configured to manage flow of data within the processor 700. The controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 700.

[0143] The memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700). In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700).

[0144] The memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 702 and / or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions. For example, the processor 700 and / or the controller 702 may be coupled with or to the memory 704, the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein. In some examples, the processor700 may include multiple processors and the memory 704 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0145] The one or more ALUs 706 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 706 may reside within or on a processor chipset (e.g., the processor 700). In some other implementations, the one or more ALUs 706 may reside external to the processor chipset (e.g., the processor 700). One or more ALUs 706 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 706 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 706 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 706 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 706 to handle conditional operations, comparisons, and bitwise operations.

[0146] The processor 700 may support wireless communication in accordance with examples as disclosed herein. The processor 700 may be configured to support a means for determining that an uplink data packet is part of a data flow of a QoS flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmitting the uplink data packet based at least in part on the QoS parameter.

[0147] Figure 8 illustrates an example of a NE 800 in accordance with aspects of the present disclosure. The NE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0148] The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0149] The processor 802 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 802 may be configured to operate the memory 804. In some other implementations, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in the memory 804 to cause the NE 800 to perform various functions of the present disclosure.

[0150] The memory 804 may include volatile or non-volatile memory. The memory 804 may store computer-readable, computer-executable code including instructions when executed by the processor 802 cause the NE 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 804 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0151] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to cause the NE 800 to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). For example, the processor 802 may support wireless communication at the NE 800 in accordance with examples as disclosed herein.

[0152] The controller 806 may manage input and output signals for the NE 800. The controller 806 may also manage peripherals not integrated into the NE 800. In some implementations, the controller 806 may utilize an operating system such as iOS®,ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 806 may be implemented as part of the processor 802.

[0153] In some implementations, the NE 800 may include at least one transceiver 808. In some other implementations, the NE 800 may have more than one transceiver 808. The transceiver 808 may represent a wireless transceiver. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0154] A receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 810 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 810 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 810 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 810 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0155] A transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0156] Figure 9 illustrates a flowchart of a method 900 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0157] At 902, the method 900 may include determining that an uplink data packet is part of a data flow of a QoS flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a UE as described with reference to Figure 6.

[0158] At 904, the method 900 may include transmitting the uplink data packet based at least in part on the QoS parameter. The operations of 904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 904 may be performed by a UE as described with reference to Figure 6.

[0159] It should be noted that the method 900 described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0160] There is provided a user equipment, UE, for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine that an uplink data packet is part of a data flow of a quality of service, QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmit the uplink data packet based at least in part on the QoS parameter.

[0161] Such a UE tends to improve handling of uplink data packets with different QoS parameters over a single QoS flow. The UE tends to negate the need to establish separate QoS flows for each data flow. The UE therefore tends to reduce the signalling overhead.

[0162] The configuration information may be for handling the uplink data packet. The configuration information may be data flow packet handling information. The configuration information may comprise at least one of identification information of a data flow. The configuration information may comprise an uplink packet filter. The configuration information may comprise a DFI. The configuration information may comprise a packet filter and corresponding DFI. The packet filter may be an uplink packet filter. The packet filter may be a data packet filter. The configuration information may comprise a QoSparameter applicable to the data flow. The configuration information may comprise at least one QoS parameter. The configuration information may comprise an indication of the data flow and a corresponding QoS parameter. The QoS parameter may correspond to a Priority Level (PL). The QoS parameter may correspond to a Packet Delay Budget (PDB). The QoS parameter may correspond to a Packet Error Rate (PER). The QoS parameter may correspond to a Quality of Experience (QoE). The data flow may be a Service Data Flow (SDF). The QoS parameter may be a QoS characteristic. The configuration information may comprise an indication of the QoS parameter.

[0163] The uplink data packet may comprise at least source and target packet address (but may also include further 5-tuple parameters). Such information may be compared with the identification information of a data flow (e.g. uplink packet filter and corresponding DFI) and if there is a match, the UE may determine that the uplink data packet belongs to the data flow.

[0164] The at least one processor coupled with the at least one memory may be further configured to cause the UE to: queue the uplink data packet for transmission according to one or more criteria, wherein the one or more criteria may comprise at least one of: a number of uplink data packets queued for transmission satisfying a threshold value, and a priority of the uplink data packet or the data flow, or a combination thereof, wherein the uplink data packet is transmitted based at least in part on the QoS parameter and the uplink data packet being queued for transmission.

[0165] Queuing the uplink data packet for transmission may comprise applying a queuing strategy. The queuing strategy may be an internal uplink queuing strategy. The queuing strategy may be a differentiated queuing mechanism. The internal uplink queuing strategy may be a strategy about differentiated queuing mechanism. Applying the queuing strategy may comprise applying the queuing strategy in an uplink buffer for the QoS flow. The queuing strategy may consider the QoS traffic characteristics of different data flows. Queuing the uplink data packet for transmission according to the number of uplink data packets queued for transmission satisfying the threshold value may comprise dropping one or more of the uplink data packets from a queue.

[0166] The at least one processor coupled with the at least one memory being configured to cause the UE to queue the uplink data packet for transmission according to one or more criteria may comprise the at least one processor coupled with the at least one memory being further configured to cause the UE to: queue the uplink data packet in a buffer associated with the QoS flow. Queuing the uplink data packet in a buffer associated with the QoS flow may comprise queuing the uplink data packet in a buffer of the QoS flow. Queuing the uplink data packet in a buffer associated with the QoS flow may comprise queuing the uplink data packet in a buffer relating to the QoS flow. Queuing the uplink data packet in a buffer associated with the QoS flow may comprise queuing the uplink data packet in a buffer for the QoS flow. Queuing the uplink data packet in a buffer associated with the QoS flow may comprise queuing the uplink data packet in a buffer in the QoS flow. Queuing the uplink data packet in a buffer associated with the QoS flow may comprise queuing the uplink data packet in a buffer provided for the QoS flow. Queuing the uplink data packet may comprise queuing the uplink data packet using a differentiated queuing mechanism. The uplink data packet may be queued in the buffer associated with the QoS flow

[0167] The at least one processor coupled with the at least one memory may be further configured to cause the UE to: transmit, to a first network entity, a request message for one or more resources for transmission of the uplink data packet, wherein the request message may comprise a buffer status report, BSR, or a random access channel, RACH, message, wherein the at least one processor coupled with the at least one memory being configured to cause the UE to transmit the uplink data packet may further comprise the at least one processor coupled with the at least one memory being further configured to cause the UE to: transmit the uplink data packet based at least in part on the QoS parameter and the one or more requested resources for transmission of the uplink data packet.

[0168] The request for uplink resources may be Medium Access Control (MAC) layer signalling. The request for uplink resources may be an uplink buffer status report. The request for uplink resources may comprise the indication of the QoS parameter for handling the uplink data packet. The first network entity may be a radio access network, RAN.

[0169] The at least one processor coupled with the at least one memory may be further configured to cause the UE to output, to a second network entity, a first request message comprising an indication of the data flow; and obtain, from the second network entity, a second response message comprising the configuration information.

[0170] The second network entity may be a Session Management Function (SMF). The first request message may be a PDU session modification request message. The first request message may further comprise a description of the data flow. The description of the data flow may be a data flow description. The description of the data flow may comprise a packet filter. The description of the data flow may comprise an SDF description. The first request message may further comprise a congestion indication. The packet filter may be associated with the QoS Parameter in the data flow. The second response message may be a PDU session modification reply message. The second response message may comprise at least one of: QoS flow information including the identification of sub-QoS flows (e.g. with packet data flow filters) and the corresponding QoS characteristics

[0171] The uplink data packet may comprise the indication of the data flow. The method may further comprise inspecting the uplink data packet for the indication of the data flow. The data flow may be identified by the indication of the data flow. The indication of the data flow may comprise an identifier for the data flow. The identifier for the data flow may be a DFI. The data flow may be identified by a DFI. The indication of the data flow may be the DFI. The identifier for the data flow may be a packet filter. The data flow may be a sub-QoS flow. The identifier for the data flow may be a Packet Detection Rule (PDR). The PDR may be a traffic detection rule.

[0172] The at least one processor coupled with the at least one memory being configured to cause the UE to determine that the uplink data packet is part of the data flow may comprise the at least one processor coupled with the at least one memory being further configured to cause the UE to associate the indication of the data flow with the data flow.

[0173] The indication of the data flow may be a data flow identifier, DFI. The DFI may map to one of a plurality of scalar values. Each of the plurality of scalar values may correspond to a QoS parameter. The DFI may be a data flow category. The DFI may be a differentiated flow identifier. The indication of the data flow may be a packet filter. Thepacket filter may be a data flow packet filter. The second network entity may be a session management function, SMF. The QoS flow may be a non-guaranteed bit rate, non-GBR, QoS flow.

[0174] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: determine that an uplink data packet is part of a data flow of a quality of service, QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmit the uplink data packet based at least in part on the QoS parameter.

[0175] Such a processor tends to improve handling of uplink data packets with different QoS parameters over a single QoS flow. The processor tends to negate the need to establish separate QoS flows for each data flow. The processor therefore tends to reduce the signalling overhead.

[0176] There is a further provided a method performed by a user equipment, UE, the method comprising: determining that an uplink data packet is part of a data flow of a quality of service, QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmitting the uplink data packet based at least in part on the QoS parameter.

[0177] Such a method tends to improve handling of uplink data packets with different QoS parameters over a single QoS flow. The method tends to negate the need to establish separate QoS flows for each data flow. The method therefore tends to reduce the signalling overhead.

[0178] The method may further comprise queuing the uplink data packet for transmission according to one or more criteria. The one or more criteria may comprise at least one of: a number of uplink data packets queued for transmission satisfying a threshold value, and a priority of the uplink data packet or the data flow, or a combination thereof. The uplink data packet may be transmitted based at least in part on the QoS parameter and the uplink data packet being queued for transmission.

[0179] Queuing the uplink data packet for transmission according to one or more criteria may comprise queuing the uplink data packet in a buffer associated with the QoS flow. Queuing the uplink data packet may comprise queuing the uplink data packet using a differentiated queuing mechanism. The uplink data packet may be queued in the buffer associated with the QoS flow

[0180] The method may further comprise: transmitting, to a first network entity, a request message for one or more resources for transmission of the uplink data packet. The request message may comprise a buffer status report, BSR, or a random access channel, RACH, message. Transmitting the uplink data packet may comprise transmitting the uplink data packet based at least in part on the QoS parameter and the one or more requested resources for transmission of the uplink data packet. The first network entity may be a radio access network, RAN.

[0181] The method may further comprise: outputting, to a second network entity, a first request message comprising an indication of the data flow; and obtaining, from the second network entity, a second response message comprising the configuration information. Determining that the uplink data packet is part of the data flow may comprise associating the indication of the data flow with the data flow. The indication of the data flow may be a data flow identifier, DFI. The indication of the data flow may be a packet filter. The second network entity may be a session management function, SMF. The QoS flow may be a nonguaranteed bit rate, non-GBR, QoS flow.

[0182] There is further provided a method performed by a second network entity, the method comprising: receiving, from a user equipment, UE, a first request message comprising an indication of a data flow. Such a method tends to improve handling of uplink data packets with different QoS parameters over a single QoS flow. The method tends to negate the need to establish separate QoS flows for each data flow. The method therefore tends to reduce the signalling overhead.

[0183] The method may further comprise determining to enable differentiated data flow handling. Differentiated data flow handling may comprise differentiated data flow handling for the QoS flow. Differentiated data flow handling may comprise handling the uplink data packet in the data flow of the QoS flow according to the QoS parameter. Differentiated dataflow handling may comprise handling the uplink data packet in the data flow of the QoS flow differently to a second uplink data packet in a second data flow in the QoS flow.

[0184] Determining to enable differentiated data flow handling may comprise receiving, from the UE, the first request message comprising the indication of the data flow. The first request message may indicate that the data flow is congested. Determining to enable differentiated data flow handling may comprise receiving, from the first network entity, a third notification comprising an indication of a load condition in the data flow. The third notification may be a N2 SM Notification. Determining to enable differentiated data flow handling may comprise receiving, from the third network entity, a fourth notification comprising an indication that the data flow has exceeded a data rate limit. The third network entity may be a User Plane Function (UPF). The fourth notification may be an N4 notification.

[0185] The method may further comprise transmitting, to the UE, a second response message comprising configuration information. The second response message may be a PDU session modification reply message. The second response message may comprise a first configuration message. The first configuration message may be configuration information to the UE.

[0186] The method may further comprise transmitting, to the third network entity, a request for an indication of one or more second data flow(s) in the QoS flow. The one or more second data flow(s) may comprise the data flow. The one or more second data flow(s) may comprise different QoS parameters. The one or more second data flow(s) may comprise different traffic requirements. The method may further comprise transmitting, to a Network Data Analytics Function (NWDAF), a request for data analytics for the one or more second data flow(s). The method may further comprise determining a priority for each of the one or more second data flow(s).

[0187] The method may further comprise receiving the configuration information. The method may further comprise transmitting, to a first network entity, a second configuration message comprising the configuration information. The second configuration message may use N2 SM signalling. The second configuration message may be configuration informationto the first network entity. The second configuration message may be configuration information to the RAN.

[0188] In some examples described herein, the SMF may be arranged to receive (e.g. from PCF, UDM) and store in the SM context that one or more indications that differentiated SDF handling is enabled or allowed for a QoS flow; the SDF identification information (e.g. packet filter) and required QoS characteristics or QoE information; determine to activate differentiated handling of the UL data flow packets, wherein the handling is different from the handling of the other packets of the QoS flow; for UE-based solution, the SMF may be further arranged to send a configuration information to the UE (e.g. PDU Session modification reply / request) including data flow identification information (e.g. packet filter, PDR, DFI) and associated differentiated flow handling parameter; for RAN-based solution, the SMF may be further arranged to send a configuration information to the (R)AN (e.g. using N2 SM signalling) including data flow identification information (e.g. packet filter, PDR), DFI and associated QoS characteristics.

[0189] In some examples described herein, the RAN may be arranged to receive a first message including one or more data flows (e.g. identified by a data flow packet filter), data flow identifier (DFI) and associated QoS characteristics different from the QoS characteristics of the QoS flow, setup a separate data radio bearer (DRB) to the UE for the one or more data flows within the QoS flow; and transmit a configuration message to the UE to setup an association of the DRBs and the combination of data flows identifier and QoS flow identifier. The configuration message may be an SDAP message containing an association of the DRB to both QFI and DFI.

[0190] There is further provided a method of a first network function (e.g. SMF) in a communication network, the method comprising the following steps: receiving and storing one or more indications that differentiated (sub-)data flow handling is enabled or allowed for a QoS flow, the data flow identification information (e.g. packet filter) and associated required QoS (or QoE) information for the data flow; determining to activate differentiated handling of the data flow packets from the handling of the other packets of the QoS flow in the uplink direction, which includes at least one of: (for UE-based solution); sending a N1 SM information to the UE including data flow identification information (e.g. data flowpacket filter, PDR, and / or DFI) and associated differentiated flow handling parameter, (for RAN-based solution); and sending a configuration information to the (R)AN (e.g. using N2 SM signalling) including data flow identification information (e.g. data flow packet filter, PDR, and / or DFI) and associated QoS characteristics.

[0191] Determining to enable the differentiated data flow handling for the QoS flow may be based on at least one of the following trigger events: an indication from the UE for congestion situation of the uplink transmission for a data flow, and optionally the data flow QoS characteristics; an N2 SM notification from the (R)AN about a certain condition for the uplink transmission of the QoS flow (e.g. UL buffer / queue overflow); an N4 notification from the UPF UL that a data rate limit (e.g. AMBR for the UE for the UL, or UL Session AMBR or Slice MBR for the UL) is about to be reached.

[0192] If the SMF doesn’t know information about the current data flows within theQoS flow, the SMF may request the UPF to provide information about the current (sub- )data flows within the QoS flow. The SMF may interact with the NWDAF to request analytics about the (sub-)data flow QoS characteristics.

[0193] The SMF may determine the QoS characteristics of the (sub-)data flows within the QoS flow. The QoS flow may be a non-GBR QoS flow.

[0194] There is further provided a method of a radio terminal (e.g. UE) in a communication network, the method comprising the following steps: receiving a first message including a list of one or more data flows identification information (e.g. data flow packet filter and / or DFIs) and associated QoS characteristics different from the QoS characteristics of the QoS flow; performing uplink data packets inspection to determine which packets belong to the data flow identified by the (uplink) data flow packet filter; determining whether to apply one of: internal uplink queuing strategy to transmit the packets of the data flow with higher priority; or transmit signalling (e.g. MAC layer buffer status report or RACH request for UL transmission) to the RAN node and indicate the uplink resources for the data flow are required.

[0195] Prior to receiving the first message, the UE may have transmitted a request message (e.g. to the SMF) to indicate at least one of: one or more data flows (e.g. identifiedby packet data filters, or application identifier) may become congested and / or indicating the traffic QoS requirements for the data flow.

[0196] The first message may be transmitted from an SMF and the first message may be a PDU Session establishment request or PDU Session establishment reply. The QoS flow may be a non-GBR QoS flow.

[0197] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0198] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0199] The following abbreviations are relevant in the field addressed by this document: 5GC / 5GS - 5th Generation Core network / 5th Generation System, 5QI - 5G QoS Identifier, AAA - Authentication, Authorization, and Accounting, AF - Application Function, AMBR - Aggregated maximum bitrate, AMF - Access and Mobility Management Function, AN - Access network, API - Application Programming Interface, AS - Application Server, BS - Base Station, CN - Core network, EC - Energy Consumption, ECF - Energy Consumption function, eNB - Evolved Node-B, EPC / EPS - Evolved packet core / Evolved packet system, GBR - Guaranteed Bitrate, gNB - 5G Node- B, ID - Identity, IE - Information Element, LTE - Long Term Evolution, NAS - Non Access Stratum, MM - Mobility Management, MO - Mobile Originated, MRU - Mobility Registration Update, MT - Mobile Terminated, NEF - Network Exposure Function, NF - Network Function, NPN - Non-Public Network, NR - New Radio, NRF - Network Repository Function, NS - Network Slice, NWDAF - Network Data Analytics Function, 0AM - Operations, Administration and Management, PCF - Policy Control Function, PDR - Packet Detection Rule, PDU - Protocol Data Unit, PLMN - Public Land Mobile Network, HPLMN - Home Public Land Mobile Network, VPLMN - Visited Public Land MobileNetwork, QFI - QoS Flow ID, QoS - Quality of Service, QoE - Quality of Experience, RAN - Radio Access Network, RAT - Radio Access Technology / Type, SDAP - Service Data Adaptation Protocol, S-NSSAI - Single Network Slice Selection Assistance Information, SM - Session Management, SMF - Session Management Function, SNPN - Standalone Non-Public Network, SUPI - Subscription Permanent Identifier, TA - Tracking area, TRP - Transmit-Receive Points, UDM - Unified Data Management, UDR - Unified Data Repository, UE - User Equipment, UMTS - Universal Mobile Telecommunication System, UPF - User Plane Function, USIM - Universal Subscriber Identity Module, (E)- UTRAN - (Evolved) Universal Terrestrial Radio Access Network.

Claims

CLAIMSWhat is claimed is:

1. A user equipment, UE, for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: determine that an uplink data packet is part of a data flow of a quality of service, QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmit the uplink data packet based at least in part on the QoS parameter.

2. The UE of claim 1, wherein the at least one processor coupled with the at least one memory is further configured to cause the UE to: queue the uplink data packet for transmission according to one or more criteria, wherein the one or more criteria comprises at least one of: a number of uplink data packets queued for transmission satisfying a threshold value, and a priority of the uplink data packet or the data flow, or a combination thereof, wherein the uplink data packet is transmitted based at least in part on the QoS parameter and the uplink data packet being queued for transmission.

3. The UE of claim 2, wherein the at least one processor coupled with the at least one memory being configured to cause the UE to queue the uplink data packet for transmission according to one or more criteria comprises the at least one processor coupled with the at least one memory being further configured to cause the UE to: queue the uplink data packet in a buffer associated with the QoS flow.

4. The UE of claim any one of claims 1 to 3, wherein the at least one processor coupled with the at least one memory is further configured to cause the UE to: transmit, to a first network entity, a request message for one or more resources for transmission of the uplink data packet, wherein the request message comprises a buffer status report, BSR, or a random access channel, RACH, message, wherein the at least oneprocessor coupled with the at least one memory being configured to cause the UE to transmit the uplink data packet further comprises the at least one processor coupled with the at least one memory being further configured to cause the UE to: transmit the uplink data packet based at least in part on the QoS parameter and the one or more requested resources for transmission of the uplink data packet.

5. The UE of claim 4, wherein the first network entity is a radio access network, RAN.

6. The UE of any one of claims 1 to 5, wherein the at least one processor coupled with the at least one memory is further configured to cause the UE to output, to a second network entity, a first request message comprising an indication of the data flow; and obtain, from the second network entity, a second response message comprising the configuration information.

7. The UE of claim 6, wherein the at least one processor coupled with the at least one memory being configured to cause the UE to determine that the uplink data packet is part of the data flow comprises the at least one processor coupled with the at least one memory being further configured to cause the UE to associate the indication of the data flow with the data flow.

8. The UE of any one of claims 6 or 7, wherein the indication of the data flow is a data flow identifier, DFI.

9. The UE of any one of claims 6 or 7, wherein the indication of the data flow is a packet filter.

10. The UE of any one of claims 6 to 9, wherein the second network entity is a session management function, SME11. The UE of any one of claims 1 to 10, wherein the QoS flow is a non-guaranteed bit rate, non-GBR, QoS flow.

12. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: determine that an uplink data packet is part of a data flow of a quality of service, QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmit the uplink data packet based at least in part on the QoS parameter.

13. A method performed by a user equipment, UE, the method comprising: determining that an uplink data packet is part of a data flow of a quality of service,QoS, flow based at least in part on configuration information, wherein the configuration information comprises a QoS parameter; and transmitting the uplink data packet based at least in part on the QoS parameter.

14. The method of claim 13, further comprising: queuing the uplink data packet for transmission according to one or more criteria, wherein the one or more criteria comprises at least one of: a number of uplink data packets queued for transmission satisfying a threshold value, and a priority of the uplink data packet or the data flow, or a combination thereof, wherein the uplink data packet is transmitted based at least in part on the QoS parameter and the uplink data packet being queued for transmission.

15. The method of claim 14, wherein queuing the uplink data packet for transmission according to one or more criteria comprises queuing the uplink data packet in a buffer associated with the QoS flow.

Images