Managing uplink pdu set based handling of traffic

Abstract

To configure a user equipment (UE) for a protocol data unit (PDU) session, the UE receives, at a non-access stratum (NAS) layer from a network, a response to a request to establish or modify a PDU session; receives, at an application layer from the network, uplink PDU Set handling information for the PDU session; and processes uplink packets according to the PDU Set handling information.

Description

MANAGING UPLINK PDU SET BASED HANDLING OF TRAFFICCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63 / 541,848 entitled “Managing Uplink PDU Set based Handling of Traffic,” filed on September 30, 2023. The entire content of the provisional applications is hereby expressly incorporated herein by reference.FIELD OF THE DISCLOSURE

[0002] This disclosure relates generally to wireless communications and, more particularly, to supporting traffic organized into Protocol Data Unit (PDU) sets.BACKGROUND

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] Base stations that operate according to fifth-generation (5G) New Radio (NR) requirements support significantly larger bandwidth than fourth-generation (4G) base stations. In some cases, a base station can transmit to a user device, or a user equipment (UE), data associated with extended Reality (XR), which refers to such technologies as Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), cloud gaming. The technologies generally involve quasi-periodic streaming and are associated with high data rates and low-latency requirements.

[0005] The 3rd Generation Partnership Project recently proposed to study support of XR and media (XRM) to provide 5G system (5GS) support of advanced media services, e.g. High Data Rate Low Latency (HDRLL) services, AR / VR / XR services, and tactile / multi-modality communication services. More specifically, the objectives include enhancements of network exposure to support interaction between 5GS and XRM applications, and enhancements of quality -of-service (QoS) and policy for XR services and media service transmissions.

[0006] When supporting XR communications (or, more generally, a data-intensive service), an application executing on a user equipment (UE) can receive or originate a data burst, which can be understood as multiple units (PDUs) communicated within a relatively short period of time. A data burst can include or more PDU sets. A PDU set in general includes one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. frame(s) or video slice(s) etc. for XR Services). All PDUs in a PDU set correspond to the same Quality- of-Service (QoS) flow.

[0007] To support XRM services for PDU set based handling in a 5GS, the radio access network (RAN) such as the next generation RAN (NG-RAN) must be aware of XRM services the 5G core network (CN) provides. The RAN receives, from the Session Management Function (SFM) over the N2 interface, PDU set QoS parameters in the QoS profde. The RAN further receives, from a User Plane Function (UPF) via the N3 interface, PDU Set information received for the downlink XRM traffic or, from the UE over Uu interface, PDU Set information for the uplink XRM traffic.

[0008] When a Session Management Function (SMF) determines that it should enable PDU set handling for a certain QoS flow, for the downlink traffic, the SMF indicates the QoS profile including PDU set based QoS parameters to the RAN, provisions a QoS rule to the UE in a non- access stratum (NAS) message (PDU Session Establishment / Modification Accept), and instructs the PDU Session Anchor (PSA) UPF in a N4 session to activate PDU set handling for the following two actions: (i) performing PDU Set identification and marking on the media traffic received over the N6 interface, and (ii) adding PDU set information on the GPRS Tunnelling Protocol (GTP-U) header over the N3 interface. For the downlink traffic, the RAN the performs PDU set based QoS handling based on PDU set information in the GTP-U header of a packet and the downlink PDU set based QoS parameters.

[0009] However, it is not clear how the UE, the RAN, and the CN should support PDU set based QoS handling in the uplink direction. For example, it is not clear how the UE and the RAN should coordinate the initiation of PDU set based handling at both ends, or how the UE can provide the required information to the RAN, what this required information includes, or how the RAN can perform PDU set based QoS handling based on the information the UE provides.SUMMARY

[0010] An example embodiment of the techniques of this disclosure is a method implemented in a user equipment (UE) for configuring a protocol data unit (PDU) session. The method comprises receiving, at a non-access stratum (NAS) layer from a network, a response to a request to establish or modify a PDU session; receiving, at an application layer from the network, uplink PDU Set handling information for the PDU session; and processing uplink packets according to the PDU Set handling information.

[0011] Another example embodiment of these techniques is a UE comprising processing hardware and a transceiver, the UE configured to implement the method above.

[0012] Yet another example embodiment of these techniques is a method for configuring a user equipment (UE), the method implemented in a radio access network (RAN) and comprising: configuring the UE with one or more rules for transmitting data in an uplink direction using PDU set based handling; and indicating, to the UE at a protocol layer for controlling radio resources, that the UE is to perform the PDU set based handling.

[0013] Still another example embodiment of these techniques is a method for configuring a UE, the method implemented in a RAN and comprising: determining whether the RAN supports PDU set based handling of uplink traffic from the UE to a core network (CN); in a first instance, in response to determining that the RAN supports PDU set based handling of the uplink traffic, transmitting, to the UE, an indication that the UE is to perform the PDU set based handling; and in a second instance, in response to determining that the RAN does not support PDU set based handling of the uplink traffic, refraining from transmitting, to the UE, the indication that the UE is to perform the PDU set based handling.

[0014] Still another example embodiment of these techniques is a method for configuring a UE, the method implemented in a RAN and comprising: configuring the UE with one or more rule rules for transmitting data in an uplink direction using protocol data unit (PDU) set based handling; and providing, to the UE in a message associated with an application layer, an indication that the UE is to perform the PDU set based handling.

[0015] Another example embodiment of these techniques is a method for processing an uplink packet, the implemented in a UE and comprising: receiving, from a RAN, an indication that theUE is to perform the PDU set based handling of the uplink data; selecting, based on the received indication, a type of marking of the uplink packet for the PDU set based handling; marking the uplink packet according to the selecting type.

[0016] Another example embodiment of these techniques is a device comprising processing hardware and configured to implement one of the methods above.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Fig. 1 A is a block diagram of an example wireless communication system, such as 5GS, that supports PDU set handling in the uplink direction using the techniques of this disclosure;

[0018] Fig. IB is a block diagram that illustrates uplink PDU set based handling at the UE of Fig. 1 A;

[0019] Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1A can communicate with the RAN of Fig. 1 A;

[0020] Fig. 3 is a service-based representation of the 5GS architecture, including the overall non-roaming reference architecture of the policy and charging control framework for the 5GS;

[0021] Fig. 4 is a reference-point based representation of the 5GS architecture, including overall non-roaming reference architecture of the policy and charging control framework for the 5GS;

[0022] Fig. 5 is a high-level messaging diagram of an example scenario in which a UE uses XRM services using PDU set handling;

[0023] Fig. 6 is a messaging diagram of an example scenario in which a RAN configures a UE to for PDU set based handling, and the UE performs uplink PDU set identification and marking according to the RAN configuration;

[0024] Fig. 7A is a messaging diagram of an example scenario in which an SMF transmits, to the UE via an AMF, uplink PDU set based handling information;

[0025] Fig. 7B is a messaging diagram of an example scenario generally similar to that of Fig. 7A, except that here the UE receives uplink PDU Set based handling information from an application layer or the operating system;

[0026] Fig. 7C is a messaging diagram of an example scenario generally similar to that of Fig. 7A, except that here the RAN transmits uplink PDU Set based handling information to the UE using RRC messaging;

[0027] Fig. 7D is a messaging diagram of an example scenario generally similar to that of Fig. 7B, except that here that the network also provides an indication of uplink PDU Set based handling per QoS flow;

[0028] Fig. 7E is a messaging diagram of an example scenario generally similar to that of Fig. 7A, except that here that the network also provides an indication of Uplink PDU Set based handling;

[0029] Fig. 8 is a messaging diagram of an example scenario in which components of a CN configure a UE to initiate PDU set based identification and marking;

[0030] Fig. 9 is a flow diagram of an example method for determining whether to perform PDU set based handling of uplink data in view of whether a NAS message included a protocol description information element, which can be implemented in the UE of Fig. 1A;

[0031] Fig. 10 is a flow diagram of an example method for determining whether to perform PDU set based handling of uplink data view of the protocol description and IP connection information, which can be implemented in the UE of Fig. 1A;

[0032] Fig. 11 is a flow diagram of an example method for determining whether to perform PDU set based handling of uplink data in view of whether an indication of uplink PDU set based handling is set to active, which can be implemented in the UE of Fig. 1A;

[0033] Fig. 12 is a flow diagram of an example method for configuring a UE for uplink PDU set based handling, which can be implemented in the RAN of Fig. 1 A; and

[0034] Fig. 13 is a flow diagram of an example method for receiving configuration for uplink PDU set based handling, which can be implemented in the UE of Fig. 1A.DETAILED DESCRIPTION OF THE DRAWINGSOverview

[0035] A UE receives uplink PDU Set handling information from the network (e.g., from a CN node via the RAN) and performs PDU Set identification and marking of PDU Sets using the uplink PDU Set handling information. In some implementations, the UE also receives an indication of whether the RAN (e.g., an NG-RAN or another suitable RAN) and / or the CN support PDU set based handling and, based on the indication, determines whether the UE should mark uplink traffic headers to indicate a PDU set. Depending on the implementation or scenario, the RAN and / or the CN provide the uplink PDU Set handling information, an indication of support of PDU set handling, or both via a NAS message, a radio resource control (RRC) message, or an application-layer message.

[0036] As discussed in more detail below, according to a certain approach, the network provides uplink PDU Set based handling information to the UE. The upper layer at the UE provides a media SDF to the lower layers, and the lower layers apply the uplink PDU Set based handling information to implement (i) PDU Set identification and (ii) marking. In some implementations, the UE performs PDU Set identification and marking using the PDU Set based handling information, as discussed above, and marks an IP header or IP payload, a Packet Data Convergence Protocol (PDCP) header or PDCP payload, a MAC header or MAC payload, etc. The UE receives, from the network, a QoS rule including a packet filter and maps an IP flow to a QoS flow using packets filters.

[0037] In some implementations, the session management function (SMF) in the CN transmits to the UE, in a NAS message such as a PDU Session Establishment Accept message or a PDU Session Modification Accept message, the uplink PDU Set based handling information discussed above. In one such implementation, the UE receives Protocol Description in a certain information element (IE) or extended Protocol Configuration Options (ePCO) IE and interprets the Protocol Description as an implicit indication to perform Set based handing for all the QoS flows in the PDU session. In an alternative implementation, the UE receives, in a certain IE or ePCO IE of a PDU Session Establishment / Modification Accept message, a listing of respective Protocol Descriptions for QoS flows. For example, the IE includes a listing of tuples (QoS flow ID (QFI) #x, protocol description #x), (QFI #y, protocol description #y), etc. In this manner, theCN and the UE can activate PDU Set based handling for particular QoS flows, rather than for all QoS flows in the PDU session.

[0038] In some implementations, the SMF in the CN transmits to the UE, in a NAS message such as a PDU Session Establishment Accept message or a PDU Session Modification Accept message, a QoS rule or QoS flow description with a special-purpose, dedicated IE in the authorized QoS rule ,a special-purpose, dedicated IE in the authorized QoS flow description, or special-purpose, dedicated QoS parameter in an authorized QoS flow description, or a specialpurpose, dedicated 5QI value in an authorized QoS flow description,

[0039] In some implementations, an application server transmits to the application client at the UE, the uplink PDU Set based handling information discussed above. The application server transmits the uplink PDU Set based handling information at an application layer, e.g., as an application-layer within a NAS message. The UE can receive a PDU Session Establishment Accept message or a PDU Session Modification Accept message and, in response to determining that the UE received Uplink PDU Set based handling information (e.g., a protocol description and IP connection information), the lower layers can perform PDU Set based handling of PDUs.

[0040] In some implementations, the RAN transmits uplink PDU Set based handling information to the UE, e.g., in an RRC Reconfiguration message. Further, the network further can transmit, to the UE, an indication of whether the RAN and / or the CN supports uplink PDU Set based handling.

[0041] In some implementations, the network provides uplink PDU Set based handling information on a per-QoS-flow basis.

[0042] In some of the scenarios of this disclosure, when the UE receives uplink PDU Set based handling information and an indication of uplink PDU Set based handling, the UE can initiate PDU Set based handling for the QoS flows of the PDU Session based on its corresponding Protocol Description, if the indication of uplink PDU Set based handling is set to “active.” The indication of uplink PDU Set based handling can be included in a PDU Session Establishment / modification Accept message or in an RRC reconfiguration message.

[0043] In another implementation, the UE receives a PDU Session Establishment / Modifi cation Accept message including uplink PDU Set based handlinginformation and Indication of uplink PDU Set based handling from SMF, and the uplink PDU Set based handling information is provided by the PCF in PCC rule, and the indication of uplink PDU Set based handling is provided by the RAN in an N2 SM message.

[0044] As another example, the UE receives PDU Session Establishment / Modification Accept message including Uplink PDU Set based handling information from the SMF, and receives an RRC reconfiguration message including an indication of uplink PDU Set based handling from RAN, where the Uplink PDU Set based handling information is provided by the PCF in a PCC rule to the SMF. The indication of uplink PDU Set based handling is provided by the RAN if the RAN supports uplink PDU Set based handling and receives an N2 SM message including QoS profile with PDU Set based QoS parameters from the SMF.

[0045] In another implementation, the UE receives a PDU Session Establishment / Modification Accept message including uplink PDU Set based handling information in a QoS rule IE or QoS rule description IE and an indication of uplink PDU Set based handling from SMF, where the uplink PDU Set based handling information is provided by the PCF in a PCC rule. The indication of uplink PDU Set based handling is provided by the RAN in an N2 SM message to the SMF.

[0046] In another implementation, the UE receives a PDU Session Establishment / Modification Accept message from the SMF, including uplink PDU Set based handling information in a QoS rule IE or QoS rule descriptions IE, and receives an RRC reconfiguration message including an indication of Uplink PDU Set based handling from the RAN, where the uplink PDU Set based handling information is provided by the PCF in a PCC rule to the SMF. The indication of uplink PDU Set based handling is provided by the RAN if the RAN supports uplink PDU Set based handling and receives an N2 SM message including QoS profile with PDU Set based QoS parameters from the SMF.

[0047] As another example, the UE receives a PDU Session Establishment / Modification Accept message from the SMF, including uplink PDU Set based handling information in a QoS rule IE or QoS rule descriptions IE, and receives an RRC reconfiguration message including an indication of Uplink PDU Set based handling from the RAN, where the uplink PDU Set based handling information is provided by the PCF in a PCC rule to the SMF. The indication of Uplink PDU Set based handling is provided by the RAN if the RAN supports uplink PDU Set basedhandling and receives an N2 SM message including QoS profde with PDU Set based QoS parameters from the SMF.

[0048] As another example, the UE receives uplink PDU Set based handling information (e g. Protocol Description) from the upper layer(s) or the OS. The UE receives a PDU Session Establishment / Modification Accept message including an indication of Uplink PDU Set based handling from the SMF, where the uplink PDU Set based handling information is transmitted in an application layer message from the application server to the application client at the UE. The indication of Uplink PDU Set based handling is provided by the RAN in an N2 SM message to the SMF.

[0049] As another example, the UE receives uplink PDU Set based handling information (e.g. Protocol Description) from the upper layer(s) or the OS, and the RRC reconfiguration message including an indication of Uplink PDU Set based handling from RAN, where the uplink PDU Set based handling information is transmitted in an application layer message from the application server to the application client at the UE. The indication of uplink PDU Set based handling is provided by the RAN in an N2 SM message to the SMF if the RAN supports uplink PDU Set based handling and receives an N2 SM message including a QoS profile with the PDU Set based QoS parameters from the SMF.

[0050] As another example, the UE receives an RRC reconfiguration message including uplink PDU Set based handling information from the RAN and PDU Session Establishment / Modification request message including an indication of Uplink PDU Set based handling from the SMF, where the Uplink PDU Set based handling information is provided by the SMF according to the following options: (i) via an N2 SM message, e.g. N2 PDU Session Request message, to NG-RAN during PDU Session Establishment / Modification request procedure, or (ii) via a GTP-U header marked by the UPF when activating PDU Set based handling at the UPF. The indication of Uplink PDU Set based handling is provided by the RAN in N2 SM message to the SMF.

[0051] As another example, the UE receives an RRC reconfiguration message including uplink PDU Set based handling information and an indication of Uplink PDU Set based handling from the RAN, where the uplink PDU Set based handling information is provided by the SMF according to the following options: (i) via an N2 SM message, e.g. N2 PDU Session Requestmessage, to the RAN during PDU Session Establishment / Modification request procedure, or (ii) via a GTP-U header marked by the UPF when activating PDU Set based handling at the UPF. The indication of Uplink PDU Set based handling is provided by the RAN if the RAN supports uplink PDU Set based handling and receives N2 SM message including QoS profile with PDU Set based QoS parameters from the SMF.

[0052] In some implementations, the Protocol Description is provided by the upper layer per IP flow which is mapped to one QoS flow. When the RAN or SMF sends the Indication of Uplink PDU Set based handling (one indication) in the RRC reconfiguration message or NAS message, the UE performs uplink PDU Set identification and marking for one or more QoS flow that has available information of Protocol description for the corresponding IP flow.

[0053] According to this approach, the following enhancements are possible: the UE receives Uplink PDU Set based Handling information, e.g. Protocol Description, from upper layers or OS, and the NAS message including Indication of Uplink PDU Set based handling per QoS flow from SMF. The Uplink PDU Set based handling information (e.g. Protocol Description) is transmitted in application layer message from application server to application client at the UE. the Indication of Uplink PDU Set based handling per QoS flow is provided by the RAN in N2 SM message to SMF. Based on this, the SMF initiates PDU Session modification procedure as indicated in TS23.502 clause 4.3.3, to send PDU Session modification command message to the UE, whereby the message includes updated QoS rules of one or more QoS flows. The Indication of Uplink PDU Set based handling is added for the QoS flow that is with PDU Set based QoS parameters. That is, the Indication of Uplink PDU Set based handling for the QoS flow is for notifying the UE that uplink PDU Set based handling for the QoS flow is supported in RAN.

[0054] The UE activates uplink PDU Set identification and marking for an QoS flow if the protocol description is available for an IP flow and uplink PDU Set Information marking Indicator is set active or included in the QoS rule of the corresponding QoS flow for the IP flow. For example, if the Protocol description of the IP flow is available but the uplink PDU Set Information marking Indicator is set as inactive or not included in the QoS rule of the corresponding QoS flow for the IP flow, the UE does not activate uplink PDU Set identification and marking for the QoS flow. The UE enables uplink PDU Set based identification and markingfor one or more QoS flow(s) if the QoS rule of the QoS flow includes uplink PDU Set Information marking Indicator and if the Protocol Description is available for the QoS flow.

[0055] When receiving PDU Set based QoS parameters for an QoS flow included in the QoS profde from the SMF, the RAN can determine whether to activate uplink PDU Set based handling for the QoS flow and provide the Indication of Uplink PDU Set based handling per QoS flow based on RAN capability and the radio resources. If one or more QoS flows can be activated for uplink PDU Set based handling, the RAN provides a list of QFIs N2 SM message that are supported for uplink PDU set based handling in N2 PDU Session Response message (N2 SM message) to the AMF and then in Nsmf_PDUSession_UpdateSMContext message (N2 SM message) to SMF.

[0056] Based on the Indication of Uplink PDU Set based handling per QoS flow in the N2 SM message sent from the RAN, the SMF determines whether to perform PDU session modification procedure to update one or more QoS rule by including uplink PDU Set Information marking Indicator in the QoS rule of the QoS flow that needs to activate Uplink PDU set based handling.Example system and protocol stack

[0057] Referring first to Fig. 1 A, an example wireless communication system 100 can implement one or more of the techniques of this disclosure for supporting PDU set based handling of traffic, particularly the uplink traffic from a UE. The example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110, such as a fifth generation (5G) core (5GC). The base stations 104 and 106 can operate in a RAN 105 connected to the CN 110. The RAN 105 in some implementations supports XRM services capabilities for PDU Set handling. In other implementations, however, the RAN 105 does not support XRM services capabilities for PDU Set handling. The CN 110 can also be implemented as a sixth generation (6G) core or another suitable core network.

[0058] The base station 104 covers a cell 124, and the base station 106 covers a cell 126. If the base station 104 is a gNB, the cell 124 is an NR cell. If the base station 124 is an ng-eNB, the cell 124 is an evolved universal terrestrial radio access (E-UTRA) cell. Similarly, if the base station 106 is a gNB, the cell 126 is an NR cell, and if the base station 126 is an ng-eNB, the cell126 is an E-UTRA cell. The cells 124 and 126 can be in the same Radio Access Network Notification Areas (RNA) or different RNAs. The cells 124 and 126 can partially overlap, so that the UE 102A or 102B can select, reselect or hands over from one of the cells 124 and 126 to the other. In general, the RAN 105 can include any number of base stations, and each of the base stations can cover one, two, three, or any other suitable number of cells. The UE 102 can support at least a 5G NR (or simply, “NR”) air interface to communicate with the base stations 104 and 106. Each of the base stations 104, 106 can connect to the CN 110 via an interface (e.g., SI or NG interface). The base stations 104 and 106 also can be interconnected via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes.

[0059] Several NFs that make up the CN 110 are discussed below with reference to Figs. 3 and 4. One or more of the NFs of the CN 110 implement the PDU set controller 134 which determines how and when to provide information related to uplink PDU set based handling to the UE 102.

[0060] While not shown in Fig. 1A to avoid clutter, the CN 110 may include processing hardware, which may include one or more general -purpose processors (e.g., CPUs) and a non- transitory computer-readable memory storing instructions that the one or more general-purpose processors execute. Additionally or alternatively, the processing hardware can include specialpurpose processing units. The processing hardware may be configured to implement the techniques of this disclosure for enabling 5GS support of advanced media services.

[0061] The base stations 104 and 106 are equipped with one or more processors 120 that can include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer- readable memory storing instructions that the one or more general-purpose processors execute (not shown). Additionally or alternatively, the processing hardware can include special-purpose processing units.

[0062] The UE 102 is equipped with one or more processors 140 that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. The UE 102 also includes a transceiver 142 to communicate with the RAN 105 over a radio interface. Further, the UE 102 includes an operating system (OS) 141 an application 143 operating in upper layers 145 and a PDU Set controller 144 operating inlower layers 144. The components 141, 143, 144, 145, and 146 can be implemented as sets of instructions stored in a memory and executable on the processors 140..

[0063] Next, Fig. IB illustrates processing 1 0 of uplink PDUs according to uplink PDU set handling information. The UE 102 can receive, from the CN 110 via the RAN 105 (see Fig. 1A), a QoS rule 151 that includes QoS flow information 152 and one or more packet filters 154. The CN 110 via the RAN 105 can be referred to collectively as “the network.” According to the scheme of Fig. IB, the network instructs the UE 102 to perform PDU Set based handling of uplink data for at least one QoS flow. The techniques the network can implement to provide the UE 102 with uplink PDU Set based handling information are discussed in more detail below.

[0064] The lower layers 146 of the UE 102 can receive, from the upper layers 145, a media service data flow (SDF) to which the UE 102 can apply uplink PDU Set handling. In particular, the PDUs 162A, ... 162N can form an IP flow 160, and the UE 102 maps the IP flow 160 to a QoS flow 172A with QFI = 1, using the one or more packet filters 154. In the example scheme of Fig. IB, the one or more packet filters 154 map another IP flow and / or media SDF to a QoS flow 172B with QFI = 2, to which uplink PDU Set based handling does not apply. For the QoS flow 172A, however, the UE 102 can perform 170 PDU Set identification, following by performing 171 PDU Set marking. More particularly, the UE 102 marks the PDUs in the QoS flow 172A with provide in-band uplink PDU Set information. The UE 102 then maps each of the QoS flows 172A and 172B to one or more data radio bearers (DRBs) such as DRBs 182A and 182B.

[0065] Fig. 2 illustrates, in a simplified manner, an example protocol stack 200 according to which the UE 102 can communicate with an eNB / ng-eNB or a gNB (e.g., one or more of the base stations 104, 106). In the example stack 200, a physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA REC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to a EUTRA PDCP sublayer 208 and, in some cases, to an NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR REC sublayer 206B in turn provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 in turn can provide data transfer services to Service Data Adaptation Protocol(SDAP) 212 or a radio resource control (RRC) sublayer (not shown in Fig. 2). The UE 102, in some implementations, supports both the EUTRA and the NR stack as shown in Fig. 2, to support handover between EUTRA and NR base stations and / or to support DC over EUTRA and NR interfaces. Further, as illustrated in Fig. 2, the UE 102 can support layering of NR PDCP 210 over EUTRA RLC 206A, and SDAP sublayer 212 over the NR PDCP sublayer 210.

[0066] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets (e.g., from an Internet Protocol (IP) layer, layered directly or indirectly over the PDCP layer 208 or 210) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206A or 206B) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as “packets.”

[0067] On a control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide signaling radio bearers (SRBs) or RRC sublayer (not shown in Fig. 2) to exchange RRC messages or non-access-stratum (NAS) messages, for example. On a user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide data radio bearers (DRBs) to support data exchange. Data exchanged on the NR PDCP sublayer 210 can be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.

[0068] Fig. 3 is a service-based representation 300 of the 5GS architecture, which the system of Fig. 1A can implement. In the representation 300, the overall non-roaming reference architecture of the policy and charging control (PCC) framework for the 5GS includes components illustrated using solid lines, and the other components are illustrated using dashed lines. According to this representation, network functions enable other authorized network functions to access their services. The components that are outside the PCC framework include a Network Slicing Selection Function (NSSF) 302, a Network Repository Function (NRF) 306, a Unified Data Management (UDM) 308, an Edge Application Server Discovery Function (EASDF) 310, a Network Slice Specific Authentication and Authorization Function (NSAAF) 312, an Authentication Server Function (AUSF) 314, a Service Communication Proxy (SCP) 316, and a Network Slice Admission Control Function (NSACF) 318. The non-PCC architecture further includes the UE 102, the RAN 105, and a data network (DN) 330. An application server (AS) 190 operates in the DN 330.

[0069] The PCC framework in the architecture 300 includes a Unified Data Repository (UDR) 352, a Network Exposure Function (NEF) 354, a network data analytics function (NWDAF) 356, an Application Function (AF) 357, a Policy Control Function (PCF) 360, a Charging Function (CHF) 362, an Access & Mobility Management Function (AMF) 364, a Session Management Function (SMF) 366, and a User Plane Function (UPF) 370.

[0070] In an example implementation, the AF 358 includes a user consent controller 112A, and the NEF 354 includes a user consent controller 112B. The CN 110 in various implementations can include only the user consent controller 112A, only the user consent controller 112B, or both. The user consent controllers 112A and 112B collectively can be referred to as the user consent control logic 112 of the CN 110.

[0071] Fig. 4 is a reference-point based representation 400 of the 5GS architecture. In Fig. 4, the non-roaming reference architecture of the PCC framework for the 5GS is illustrated as blocks and connections with solid lines, and components and connections outside the PCC framework are illustrated using dashed lines.

[0072] Several example techniques for assisting application with selection of UEs in view of user consent are discussed next. Generally speaking, events in Figs. 5-11 that are similar are labeled with similar reference numbers (e.g., event 640 of Figs. 6A and 6B is similar to event 540 of Fig. 5), with differences discussed below where appropriate. With the exception of the differences shown in the figures and discussed below, any of the alternative implementations discussed with respect to a particular event (e.g., for messaging and processing) may apply to events labeled with similar reference numbers in other figures.

[0073] Referring to a scenario 500 of Fig. 5, during the registration procedure, the AMF determines 501 whether the UE 102 is authorized to use XRM services based on the XRM Service Capability of the UE and the XRM Service Authorization included in the subscription data received from UDM as specified in TS 23.501 clause 5.7.

[0074] After successful registration, the UE requests 511 for PDU Session Establishment procedure and the RAN capable of XRM services can perform PDU Set handling for the QoS flows in a PDU session based on the XRM service authorization and information received fromthe SMF via N2 message and GTP-U header via N3 interface from the UPF. The PDU Session Establishment Procedure can be implemented as described in TS23.502 clause 4.3.2.2.

[0075] The UE or network initiate 521 PDU Session Modification Procedure for the existing PDU Session. The PDU Session Modification Procedure can be implemented as described in TS23.502 clause 4.3.3.2 and 4.3.3.3.

[0076] The UE may repeat procedure 511 for multiple PDU sessions which are associated with the same or different data network names (DNNs) and Single - Network Slice Selection Assistance Information (S-NSSAI).

[0077] When the PLMN provides homogeneous RAN support of PDU set based handling, the procedure 500 can be applied with the following enhancement for supporting PDU set based QoS: PCF: provides PCC rules for an application service flow as defined in clause 6.1.3.27.4 of TS 23.503 that includes PDU Set QoS parameters (PSER, PSDB and PSIHI) and Protocol Description.

[0078] The SMF determines a QoS Profile for the QoS flow, which is based on received PCC rules or pre-configuration. The PSA UPF performs the following: (i) identifies PDUs that belong to PDU Sets based on Protocol Description based on received PDR (Packet Detection Rule), (ii) marks the GTP-U header for PDU Set information as described in TS23.501 clause 5.37.5.2, (iii) and performs PDU set based parameters based on received QER (QoS Enforcement Rule).

[0079] The network instructs the UE with uplink PDU Set based handling information to perform PDU set based handling including PDU Set identification and marking on the uplink media service data flow received from upper layer to provide the RAN with in-band uplink PDU Set information.

[0080] According to one implementation, the RAN 105 performs PDU set based QoS handling for radio resources management based on the following information: (i) uplink PDU Set information received from the UE over air interface, and (ii) QoS profile containing uplink PDU set based QoS parameters.

[0081] The uplink PDU Set Information can include one or more of: (i) a PDU Set Sequence Number, (ii) an Indication of End PDU of the PDU Set, (iii) PDU Sequence Number within aPDU Set, (iv) PDU Set Size in bytes, and (v) PDU Set Importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow.

[0082] Generally speaking, the network (e.g., the CN 110 and / or the RAN 105) provides the UE 102 with Uplink PDU set based Handling information, so that the UE 102 can perform PDU set based handling, including PDU Set identification and marking, on the uplink media SDF from an upper layer, so as to provide in-band uplink PDU Set information to the RAN 105.

[0083] The RAN 105 can perform PDU Set based QoS handling for radio resources management using the following information: (i) uplink PDU Set information received from the UE 102 over the air / radio interface, and (ii) the QoS profile containing uplink PDU Set based QoS parameters.

[0084] The uplink PDU Set information can include one or more of the following: (i) PDU Set Sequence Number, (ii) an indication of End PDU of the PDU Set, (iii) a PDU Sequence Number within a PDU Set, (iv) a PDU Set size in bytes, (v) an indication of PDU Set importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow.

[0085] In some implementations, the UE 102 marks uplink packets with uplink PDU Set information, after receiving uplink PDUs from an upper layer and performing PDU Set identification on the uplink PDUs. The To this end, the UE 102 can use PDU Set based handling information.

[0086] For example, the UE 102 can mark (include) uplink PDU Set Information for an uplink packet in an unencrypted IP packet, e g. in the IP header or the IP payload. As another example, the UE 102 can mark uplink PDU Set Information for an uplink PDCP packet, e.g. in the PDCP header or the PDCP payload, with a PDCP header indication of the marked PDCP payload. As yet another example, the UE 102 can mark PDU Set information for an uplink MAC packet, e.g. in the MAC header or the MAC payload, with a PDCP header indication of the marked MAC payload.

[0087] In some implementations, the UE 102 supports an application programming interface (API) for sending and receiving uplink PDU Set information across different layers, e.g. from the RRC layer to the NAS layer or vice versa. The API thus can allow an inter-layers message exchange for the uplink PDU Set based handling information. \Transmitting uplink PDU Set handling information

[0088] Now referring to Fig. 6, in a scenario 600, uplink PDU Set handling information enables uplink PDU Set based handling at the UE 102 and the RAN 105.

[0089] The RAN 105 can receive 602, from the CN 110 (e.g., the SMF 366) a QoS profde including PDU Set based QoS parameters. In response, the RAN 105 enables 602 uplink PDU Set based handling based on the QoS profile. The RAN 105 then transmits 640 a QoS rule (see, e.g., the QoS rule 154 of Fig. IB) including QoS flow information and one or more packet filters, or multiple QoS rules. The RAN 105 also transmits 640 Uplink PDU Set based handling information, so as to instruct the UE 102 to perform PDU Set based handling (PDU Set identification and marking) on the uplink media SDF from an upper layer.

[0090] As discussed with reference to Fig. IB above, the UE 102 maps 657 an IP flow to the corresponding QoS flow, which the UE 102 and network nodes can identify based on the QFI, using packet filters included in the QoS rule(s) the UE 102 receives 640 from the network. The UE 102 can perform 658, using the uplink PDU Set based handling information and the one or more QoS rules, PDU Set identification and marking on the uplink PDUs received from the upper layer, to provide in-band uplink PDU Set information. The UE 102 then can map 659 the PDU Set based QoS flow to one or more DRB(s) and transmit 675 the PDUs over the one or more DRBs to the RAN 105. To this end, the UE 102 can rely on the RRC message (not shown) including radio bearer configuration information.

[0091] The RAN 105 performs 676 PDU Set based handling for radio resource management based on the QoS profiles for the corresponding QoS flows and the uplink PDU Set information (which the UE 102 included, as a part of the maring, in the PDUs that belong the PDU set based QoS flow).

[0092] In some implementations consistent with the techniques discussed above, the UE 102 receives 640 the uplink PDU Set based handling information in a NAS message such as a PDU Session Establishment Accept message or a PDU Session Modification Accept message. The NAS message can originate at the SMF 366 and travel via the AMF 364, for example. The SMF 366 can include the uplink PDU Set based handling in a special-purpose, dedicated IE or ePCO IE.

[0093] According to one such approach, the Protocol Description field operates as an implicit trigger indication for uplink PDU Set based handling. The Protocol Description includes indications of a transport protocol (e.g. RTP, SRTP), transport protocol header extensions, payload type and format (e.g. H.264, H.265), and format parameters (e.g. H.264 profile level and packetization mode) which the SDF can use. When the UE 102 receives the uplink PDU Set based Handling information, the UE 102 can initiate PDU Set based handling based on the Protocol Description for all the QoS flows of the PDU Session. This implementation is further discussed with reference to Fig. 9.

[0094] In another implementation, the Protocol Description operates as an implicit trigger indication per QoS flow granularity. Here, a special-purpose, dedicated IE or ePCO IE contains a listing of tuples (QFI #x, protocol description #x), (QFI #y, protocol description #y), etc. to identify QoS flows that require PDU Set based QoS handling (in other words, those QoS flows that are associated with PDU Set based QoS parameters).

[0095] Similar to the example above, the Protocol Description can indicate a transport protocol (e.g. RTP, SRTP), transport protocol header extensions, payload type and format (e.g. H.264, H.265), and format parameters (e.g. H.264 profile level and packetization mode) used by the SDF. A QFI identifies a QoS flow that requires PDU set based QoS handling and thus corresponds to the PDU Set based QoS parameters included in the QoS profile which the RAN 105 enforces.

[0096] When the UE 102 receives the uplink PDU Set based handling information, the UE 102 can initiate PDU Set based handling for each indicated QoS flow of the PDU session, based on the corresponding Protocol Descriptions. For example, when the NAS message the UE 102 received 640 includes Uplink PDU Set based handling information, the UE 102 performs uplink PDU Set identification and marking based on the Protocol Description of the PDU set based QoS flow. Referring back to Fig. IB, for example, the QoS flows 172A and 172B can belong to the same PDU session, but only the QoS flow 172A requires uplink PDU Set based handling.

[0097] In some implementations, the network transfers the special-purpose, dedicated IE in QoS rule or QoS flow description include in a NAS message.

[0098] For example, the network includes the uplink PDU Set based handling information in a QoS rule or QoS flow description for a QoS flow identified by QFI for a PDU Session. The QoSrule or QoS flow description in this case includes a Protocol Description which indicates the transport protocol (e.g. RTP, SRTP), transport protocol header extensions, the payload type and format (e g. H.264, H.265), and format parameters (e g. H.264 profile level and packetization mode) used by the SDF.

[0099] One such option is including a new IE (e.g., a special-purpose, dedicated IE) in the Authorized QoS rule. Thus, within a certain PDU session, a QoS flow that includes uplink PDU Set based handling information in the Authorized QoS rule requires uplink PDU set based handling, whereas a QoS flow that does not include uplink PDU Set based handling information in the Authorized QoS rule does not require uplink PDU set based handling. As a more particular example, the description of an Authorized QoS rule can be expanded to include, in addition to the QRI, the length of QoS rule, the rule operation code, the DQR bit, the number of packet filers, the packet filter list, the packet filter precedence, the new IE discussed above, followed by the QFI The precise positioning of the new IE within the Authorized QoS rule description can vary according to the embodiment.

[0100] Another option is including a new IE (e.g., a special-purpose, dedicated IE) in the Authorized QoS flow descriptions. Thus, within a certain PDU session, the QoS flow description that includes uplink PDU Set based handling information in the Authorized QoS rule description requires uplink PDU set based handling, whereas a QoS flow that does not include uplink PDU Set based handling information in the Authorized QoS rule description does not require uplink PDU set based handling. As a more particular example, the Authorized QoS flow description can be expanded to include, in addition to the QFI, the operation code (create, modify, delete), the QoS parameters (5QI, GFBR / MFBR uplink / downlink, avg. window, EPS bearer ID), the RQ timer value, the new IE discussed above.

[0101] Yet another option is including a new QoS parameter (e.g., a special-purpose, dedicated parameter) in the Authorized QoS flow description. For example, the Authorized QoS flow description can include, in addition to the currently defined parameters, a new parameter IE that includes the QFI, the operation code (create, modify, delete), the QoS parameters (5QI, GFBR / MFBR uplink / downlink, avg. window, EPS bearer ID, the new parameter related to uplink PDU Set based handling), and the RQ timer value.

[0102] Still another option is including the uplink PDU Set based handling information in a 5QI IE, with a new (special -purpose, dedicated) 5QI value is associated with some specific uplink PDU set based handling information, e.g. Protocol Description represented by a standardized value.

[0103] Fig. 7A is a messaging diagram of an example scenario 700A in which an SMF transmits, to the UE via an AMF, uplink PDU set based handling information. The UE 102 sends 710 a PDU Session Establishment request message to the AMF 364 operating in the CN 110. The AMF 364 then selects the SMF 366 and then sends 714, to the selected SMF 366, an Nsmf PDUSession CreateSMContext message to create an SM context for the PDU session.

[0104] Based on PCC rules from PCF 360, the SMF 366 determines 720 to enable uplink and / or downlink PDU Set based handling. The SMF 366 instructs 722 UPF to perform downlink PDU Set based handling by configuring an N4 session.

[0105] The SMF 366 sends 724A an Namf_Communication_NlN2MessageTransfer to the AMF 364, so to provide an N2 SM message including a QoS profile to the RAN 105, and to provide an N1 SM container including a NAS message (QoS rules, Uplink PDU set based handling info) to the UE 102.

[0106] The AMF 364 sends 730A, to the RAN 105, an N2 PDU Session Request message. The N2 PDU Session Request message can include the N2 SM message with the QoS profile (received 724A from the SMF 366) and the NAS message including QoS rules and Uplink PDU set based handling information. Next, the RAN 105 sends 740A, to the UE 102, an RRC reconfiguration message including the NAS message. The UE 102 responds 742 to the RAN 105 with an RRC reconfiguration complete message. Further, in response to receiving 730 A the N2 PDU Session Request message, the RAN 105 sends 732 an N2 PDU Session Response message to the AMF 364, to confirm the radio resources setup.

[0107] The AMF 364 sends 760, to the SMF 366, an Nsmf_PDUSession_UpdateSMContext message, to update the SM context of the PDU session. The UE 102 in this scenario determines 751 whether to perform PDU Set based handling based on the received 740A NAS message containing the uplink PDU set based handling information.

[0108] In another implementation, the application server 190 transmits the uplink PDU Set based handling information to the application 143 of the UE 102. The uplink PDU Set based handling information can include a Protocol Description and IP connection information. The Protocol Description indicates the transport protocol (e.g. RTP, SRTP), the transport protocol header extensions, the payload type and payload format (e.g. H.264, H.265), and format parameters (e.g. H.264 profde level and packetization mode) used by the SDF. The IP connection information corresponds to a specific IP flow, which devices can identify based on one or multiple units of information such as IP 5 tuples, which can include the source IP address, the source port number, the destination IP address, the destination port number, and the protocol type (e.g. TCP, UDP, QUIC). When the UE 102 receives the uplink PDU Set based handling information from one of the upper layers 145 or the OS 141, the UE 102 can initiate PDU Set based handling based on the Protocol Description for the IP flows. Example implementation of this technique is illustrated in Fig. 10.

[0109] Referring to Fig. 7B, an example scenario 700B is generally similar to the scenario 700A, except that here the UE 102 the receives uplink PDU Set based handling information from an application layer or the operating system. After the events 710, 714, 720, and 722 discussed above, the SMF 366 sends 724B, to the AMF 364, an Namf_Communication_NlN2MessageTransfer message to provide (i) an N2 SM message including the QoS profile to the RAN 105, and (ii) an N1 SM container containing an NAS message, which in turn includes QoS rules for the UE 102.

[0110] The AMF 364 sends, to the RAN 105, 730B an N2 PDU Session Request message, which can include the N2 SM message with the QoS profile and the NAS message including the QoS rules, similar to event 730A. In some implementations, the AMF 364 transmits 730B such information as a PDU Session Establishment / Modification Accept with the QoS rules and the QFIs. The RAN 105 sends 740B, to the UE 102, an RRC reconfiguration message including the NAS message in the NAS container. The UE 102 responds 742 to the RAN 105 with an RRC reconfiguration complete message.[0U1] The UE 102 receives 752 uplink PDU Set based handling information from the upper application layer or the OS and determines 751 whether to perform PDU set based handling based on the received Uplink PDU set based handling information.

[0112] Next, Fig. 7C illustrates an example scenario 700C generally similar to that of Fig. 7A, except that here the RAN transmits uplink PDU Set based handling information to the UE using RRC messaging. More particularly, the RAN can transmit, to the UE, the uplink PDU Set based handling information in an RRC reconfiguration message. Similar to the examples above, the Protocol Description includes indications of a transport protocol (e.g. RTP, SRTP), transport protocol header extensions, payload type and format (e.g. H.264, H.265), and format parameters (e.g. H.264 profile level and packetization mode) which the SDF can use.

[0113] For example, the RRC reconfiguration message can include the uplink PDU Set based handling information a dedicated, special-purpose IE, which can be a new IE defined in the relevant 3 GPP standard(s) to support the scenario 700C. When the UE receives the uplink PDU Set based handling information in the RRC reconfiguration message, the UE 102 can initiate the PDU Set based handling based on the Protocol Description for all of the QoS flows of the PDU Session.

[0114] As a further example, the network can include the uplink PDU Set based handling information per a DRB configuration, that provides the mapping between DRB(s) and QFI(s) in the RRC reconfiguration message. When the UE receives the uplink PDU Set based handling information in the DRB configuration, the UE can initiate PDU Set based handling based on the Protocol Description for those QoS flows that require PDU Set based handling.

[0115] As one option, the SMF provides the uplink PDU Set based handling information to the RAN via an N2 SM message, e.g. N2 PDU Session Request message, during the PDU Session Establishment / Modification request procedure. As another option, the SMF provides the uplink PDU Set based handling information to the RAN via a GTP-U header marked by the UPF, when activating PDU Set based handling at UPF.

[0116] As illustrated in Fig. 7C, the UE 102 sends 710 a PDU Session Establishment request message, and the AMF 364 selects an SMF and sends 714, to the SMF 366, an Nsmf_PDUSession_CreateSMContext message to create am SM context for the PDU session. Based on the PCC rules received from the PCF, the SMF 366 determines 720 to enable uplink / downlink PDU Set based handling. The SMF 266 instructs 722 the UPF 370 to perform the downlink PDU Set based handling by configuring N4 session.

[0117] The SMF 366 sends 724C, to the AMF 364, anNamf_Communication_NlN2MessageTransfer message to provide (i) an N2 SM message including a QoS profile and the uplink PDU Set based handling information, to the RAN 105, and (ii) an N1 SM container containing a NAS message including the QoS rules, to the UE 102 (via the AMF 364). Alternatively, the SMF 366 instructs the UPF 370 to mark uplink PDU Set based handling information in the GTP-U header to deliver the uplink PDU Set based Handling informaion.

[0118] The AMF 364 sends 730C, to the RAN 105, an N2 PDU Session Request message including the N2 SM message (which in turn includes the QoS profile and the uplink PDU Set based handling information). The N2 PDU Session Request message also include a NAS message with the QoS rules. The RAN 105 sends 740C, to the UE 102, an RRC reconfiguration message, including uplink PDU Set based handling information, e.g., a Protocol Description. The UE 102 responds 742 to the RAN 105 in an RRC reconfiguration complete message.

[0119] Based on the uplink PDU Set based handling information such as the Protocol Description, received 740C in the RRC reconfiguration message , the UE 102 determines 751 whether to perform uplink PDU Set based handling, such as uplink PDU Set identification and marking.Providing an indication of network support of uplink PDU Set based handling

[0120] In some implementations, the network provides a UE with an explicit trigger indication for network support of uplink PDU Set based handling. More particularly, the network can indicate to the UE whether the RAN and / or the CN functions such as the PCF, the SMF, or the UPF support uplink PDU Set based handling, for a certain QoS flow.

[0121] Referring to the implementations discussed above with reference to Figs. 7A-C, when the UE receives uplink PDU Set based Handling information and an indication of uplink PDU Set based handling, the UE can initiate PDU Set based handling. In some implementations, the UE initiates PDU Set based handling for the QoS flows of the PDU Session based on the corresponding Protocol Description, if the indication of uplink PDU Set based handling is set to “active” or “supported,” for example.

[0122] In some implementations, the network transmits the indication of uplink PDU Set based handling in a PDU Session Establishment / modification Accept message. In another implementation, the network transmits the indication of uplink PDU Set based handling in an RRC reconfiguration message.

[0123] For example, in some of the implementations where the SMF transmits the uplink PDU Set based handling information using a NAS message, the UE can receive, from the SMF, a PDU Session Establishment / Modification Accept message including uplink PDU Set based handling information along with an indication of uplink PDU Set based handling from SMF. More specifically, the PCF can provide the uplink PDU Set based handling information in a PCC rule, and the RAN can provide the indication of uplink PDU Set based handling in an N2 SM message.

[0124] As another example, in other implementations where the SMF transmits the uplink PDU Set based handling information using a NAS message, the UE can receive, from the SMF, a PDU Session Establishment / Modification Accept message including uplink PDU Set based handling information from SMF, and receive, from the RAN, an RRC reconfiguration message including the indication of uplink PDU Set based handling. The PCF can provide the uplink PDU Set based handling information to the SMF in a PCC rule. The RAN can provide the indication of uplink PDU Set based handling, if (i) the RAN supports uplink PDU Set based handling and (ii) has received, from the SMF, an N2 SM message including a QoS profile with PDU Set based QoS parameters.

[0125] In those implementations where the network includes the PDU Set based handling information in a QoS rule or QoS flow description for a QoS flow, identified by a QFI for the PDU Session, the UE can receive, from the SMF, (i) a PDU Session Establishment / Modification Accept message including uplink PDU Set based handling information (in a QoS rule IE or a QoS rule descriptions IE) and (ii) and an indication of uplink PDU Set based handling. More specifically, the PCF can include the uplink PDU Set based handling information in a PCC rule, and the RAN sends, to the SMF in an N2 SM message, the indication of uplink PDU Set based handling.

[0126] In some implementations where the network includes the PDU Set based handling information in a QoS rule or QoS flow description for a QoS flow, the UE receives, from theSMF, a PDU Session Establishment / Modification Accept message including the uplink PDU Set based handling information in a QoS rule IE or a QoS rule descriptions IE, and receives, from the RAN, an RRC reconfiguration message including the indication uplink PDU Set based handling. According to this approach, the PCF provides the uplink PDU Set based handling information to the SMF in a PCC rule. The RAN provides the indication of Uplink PDU Set based handling to the UE if (i) the RAN supports uplink PDU Set based handling and (ii) has received, from the SMF, an N2 SM message including a QoS profile with PDU Set based QoS parameters.

[0127] Further, as discussed above with reference to Fig. 7B, for example, an application client at the UE in some implementations receives uplink PDU Set based handling information from an application server, at the application layer.

[0128] In some of these implementations, the UE receives the uplink PDU Set based handling information (e.g. a Protocol Description) from the upper layer(s) or the OS, and receives, from the SMF, a PDU Session Establishment / Modification Accept message including the indication of Uplink PDU Set based handling. According to this approach, the application server transmits, to the application client at the UE and in an application layer message, the uplink PDU Set based handling information. The RAN provides to the SMF, in an N2 SM message, the indication of uplink PDU Set based handling.

[0129] In other implementations based on the application-layer signaling, the UE receives the uplink PDU Set based handling information (e.g. a Protocol Description) from the upper layer(s) or the OS and receives, from the RAN, an RRC reconfiguration message including an indication of uplink PDU Set based handling. Here, the application server transmits the uplink PDU Set based handling information in an application layer message to application client at the UE, and the RAN provides the indication of Uplink PDU Set based handling if (i) the RAN supports uplink PDU Set based handling and (ii) has received, from the SMF, an N2 SM message including a QoS profile with PDU Set based QoS parameters.

[0130] As discussed above with reference to Fig. 7C, for example, a UE can receive an RRC message with uplink PDU Set based handling information. In some of these implements, the UE receives, from the RAN, an RRC reconfiguration message including uplink PDU Set based handling information from NG-RAN and receives, from the SMF, a PDU SessionEstablishment / Modification request message including an indication of uplink PDU Set based handling. The SMF can provide the uplink PDU Set based handling information to the RAN via an N2 SM message, such as an N2 PDU Session Request message, during the PDU Session Establishment / Modification request procedure. Alternatively, the SMF can provide the uplink PDU Set based handling information via a GTP-U header, which the UPF marks when activating PDU Set based handling at the UPF. The RAN can provide the SMF with the indication of uplink PDU Set based handling in an N2 SM message.

[0131] As another example, the UE can receive, from the RAN, (i) an RRC reconfiguration message including the uplink PDU Set based handling information and (ii) the indication of uplink PDU Set based handling. Similar to the example above, the SMF can provide the uplink PDU Set based handling information to the RAN via an N2 SM message, such as an N2 PDU Session Request message, during the PDU Session Establishment / Modification request procedure; or, alternatively, the SMF can provide the uplink PDU Set based handling information via a GTP-U header, which the UPF marks when activating PDU Set based handling at the UPF. The RAN provides the Indication of uplink PDU Set based handling if (i) the RAN supports uplink PDU Set based handling and (ii) has received, from the SMF, an N2 SM message including QoS profile with PDU Set based QoS parameters.

[0132] In some of the examples above, the network provides a Protocol Description in an upper layer, per an IP flow, which is mapped to one QoS flow. When the RAN or the SMF sends the indication of uplink PDU Set based handling in an RRC reconfiguration message or a NAS message, as a single indication, the UE performs the uplink PDU Set identification and marking for one or more QoS flows that has available information correspond to the Protocol Description for the corresponding IP flow. The techniques can be further enhanced according to one of the approaches outlined below.

[0133] According to one approach, the UE receives uplink PDU Set based handling information, such as the Protocol Description, from the upper layers or the OS, and receives, from the SMF, a NAS message including an indication of uplink PDU Set based handling per QoS flow. In particular, the application server transmits the uplink PDU Set based handling information such as the Protocol Description) to application client at the UE. The RAN provides, to the SMF and in an N2 SM message, an indication of uplink PDU Set based handlingper QoS flow. Based on this information, the SMF can initiate a PDU Session modification procedure as described in TS 23.502 clause 4.3.3, for example, to send a PDU Session modification command message to the UE. The message can include updated QoS rules for one or more QoS flows. The SMF can add an indication of uplink PDU Set based handling for the QoS flow that has PDU Set based QoS parameters. In other words, the indication of uplink PDU Set based handling for a QoS flow notifies the UE the RAN supports uplink PDU Set based handling for the QoS flow.

[0134] The UE can activate uplink PDU Set identification and marking for the QoS flow if (i) the protocol description is available for the IP flow and (ii) the indication for uplink PDU Set information marking (or indication of uplink PDU Set based handling) is set to “active,” or if the QoS rule of the corresponding QoS flow for the IP flow includes this indicator. For example, if the Protocol description of the IP flow is available, but the uplink PDU Set information marking indicator is set to “inactive” or is not present in the QoS rule of the corresponding QoS flow for the IP flow, the UE does not activate uplink PDU Set identification and marking for the QoS flow. On the other hand, the UE enables uplink PDU Set based identification and marking for one or more QoS flow(s) if the QoS rule of the QoS flow includes uplink PDU Set information marking indicator, and if the Protocol Description is available for the QoS flow.

[0135] The RAN can determine, after receiving, from the SMF, PDU Set based QoS parameters for an QoS flow included in the QoS profile, whether to activate uplink PDU Set based handling for the QoS flow and provide an indication of Uplink PDU Set based handling per QoS flow based on NG-RAN capability and the radio resources. If one or more QoS flows can be activated for uplink PDU Set based handling, the RAN can provide the AMF with a list of QFIs that are supported for uplink PDU set based handling. To this end, the RAN can send an N2 SM message, e.g., as an N2 PDU Session Response message including the N2 SM message. The RAN can also send, to the SMF, an Nsmf_PDUSession_UpdateSMContext message including an N2 SM message.

[0136] Based on the indication of uplink PDU Set based handling indicated per QoS flow in the N2 SM message from the NG-RAN, the SMF can determine whether to perform PDU session modification procedure to update one or more QoS rules. To update a QoS rule, the SMFcan include an uplink PDU Set Information marking indicator in the QoS rule of the QoS flow that requires activation of uplink PDU set based handling.

[0137] As discussed above, the network can use Authorized QoS rule with a special-purpose IE that can be referred as an uplink PDU Set Information marking indicator, for example, to indicate whether the network supports, and accordingly whether UE should perform, uplink PDU Set information marking for a QoS flow identified by a QFI. As one alternative, the network can use Authorized QoS flow description with a special-purpose IE (e g., an uplink PDU Set Information marking indicator) to provide this indication. As another alternative, the network can use a special-purpose, dedicated QoS parameter in a listing of QoS parameters included in an Authorized QoS flow description.

[0138] Now referring to Fig. 7D, a scenario 700D is generally similar to that of Fig. 7B, but here the RAN provides an indication of uplink PDU Set based handling per QoS flow, to the AMF, which then updates the SMF and the UE accordingly. After events 710, 714, 720, and 722 discussed above, the SMF 366 sends 724, to the AMF 364, an Namf_Communication_NlN2MessageTransfer, to provide (i) an N2 SM message including a QoS profile to the RAN 105 and (ii) an N1 SM container containing a NAS message including the QoS rules to the AMF 364. The AMF 364 sends 730D, to the RAN 105, an N2 PDU Session Request message, which can include the N2 SM message with the QoS profile and a NAS message with the QoS rules. The RAN 105 sends 740D, to the UE 103, an RRC reconfiguration message including the NAS message in the NAS container. The UE responds 742 to the RAN 105 with an RRC reconfiguration complete message.

[0139] In response to receiving 742 the RRC reconfiguration complete message, the RAN 105 sends 732D, to the AMF 364, an N2 PDU Session Response message including an indication of uplink PDU Set based handling per QoS flow, to confirm the setup of the radio resources. More specifically, based on the RAN capability and the radio resources, the RAN 105 can determine whether to activate uplink PDU Set based handling for the QoS flow that includes PDU Set based QoS parameters. If the RAN 105 determines to enable the uplink PDU Set based handling for the UE, the RAN 105 can provide the indication of uplink PDU Set based handling per QoS flow.

[0140] The AMF 364 then sends 760D, to the SMF 366, an Nsmf PDUSession UpdateSMContext message including the indication of Uplink PDU Set based handling per QoS flow. The indication of Uplink PDU Set based handling per QoS flow can be an element in an N2 SM message. The SMF can update the PDU session SM context based on the receiving 760D of the Nsmf_PDUSession_UpdateSMContext message.

[0141] With continued reference to Fig. 7D, based on indication of Uplink PDU Set based handling per QoS flow in the N2 SM message, the SMF 366 initiates 761 a PDU session modification procedure to update one or more QoS rules of the QoS flows at the UE 102. To this end, the SMF 266 can send a PDU Session Modification command message. The QoS rule in this case includes an uplink PDU Set Information marking indicator for the QoS flow that requires activation of uplink PDU set based handling.

[0142] The UE 102 receives 752 the uplink PDU Set based handling information from an upper application layer or the OS. The UE determines 75 ID to perform uplink PDU Set identification and marking if (i) the uplink PDU Set based handling information is available and (ii) the QoS rule includes the uplink PDU Set information marking indicator for the QoS flow. In some implementations, the UE 102 determines to not activate uplink PDU Set identification and marking based on the additional information at the UE 102, e.g. the computing power, battery power, UE preference settings, etc.

[0143] Fig. 7E is a messaging diagram of an example scenario generally similar to that of Fig. 7A, except that here that the UE receives uplink PDU Set based handling information in a message related to PDU session management.

[0144] Similar to the scenarios above, initially the UE 102 sends 702 a PDU Session Establishment request message to the AMF in the core network; the AMF 364 selects the SMF 366 and sends 710, to the SMF 366, Nsmf_PDUSession_CreateSMContext message to create a PDU session SM context; the SMF 366 determines 720 to enable uplink / downlink PDU Set based handlin based on PCC rules from PCF 360; and the SMF 366 instructs the UPF 360 to perform downlink PDU Set based handling by configuring an N4 session.

[0145] The SMF 366 sends 724E, to the AMF 364, an Namf_Communication_NlN2MessageTransfer message to provide (i) the RAN 105 with an N2SM message including a QoS profile and an indication of uplink PDU Set based handling to the NG-RAN and (ii) the AMF 364 with an N1 SM container containing a NAS message including QoS rules as well as uplink PDU Set based handling information, for the UE 102. The CN 110 can use NAS message in this implementation similar to the examples above.

[0146] The AMF 364 sends 730E, to the RAN 105, an N2 PDU Session Request message including the N2 SM message with the QoS profile and the NAS message with the uplink PDU Set based handling information.

[0147] The RAN 105 determines to enable uplink PDU Set based handling and sends 740E, to the UE 102, an RRC reconfiguration message including the indication of uplink PDU Set based handling, as well as the NAS message including the QoS rules and the uplink PDU Set based handling information such as the Protocol Description. The UE 102 responds 742 with an RRC reconfiguration complete message.

[0148] The RAN 105 then sends 732, to the AMF 364, an N2 PDU Session Response message to confirm the setup of radio resources. The AFM 364 sends 760, to the SMF 366, an Nsmf_PDUSession_UpdateSMContext message, to update the PDU session SM context.

[0149] Based on the received indication of uplink PDU Set based handling in the RRC reconfiguration message and the NAS message containing the uplink PDU Set based handling information, the UE 102 determines to perform uplink PDU Set based handling, e.g. uplink PDU Set identification and marking.

[0150] Next, Fig. 8 illustrates an example scenario 800 in which the network instructs the UE to initiate uplink PDU set identification and marking.

[0151] The UE sends 802, to the AMF 364, a PDU Session Establishment Request message, which can include a PDU Session ID, a DNN, and S-NSSAI (such that the specific DNN and S- NSSAI are associated with XRM services). The AMF 364 performs 804 an SMF selection based on the DNN and S-NSSAI. If the DNN and S-NSSAI are associated with applications requiring PDU Set based QoS, the AMF 364 selects a specific SMF capable of PDU Set handling. The AMF 364 then sends 810, to the SMF 366, a Nsmf_PDU Session_CreateSMContext Request message including the PDU Session ID, the DNN, and the S-NSSAI.

[0152] The SMF 366 retrieves 812 UE subscription for the XRM based on the DNN and the S-NSSAI. SMF 366 responds 814 to the AMF 364 with an Nsmf_PDUSession CreateSMContext Response message. The SMF 366 performs 815 a PDU Session authentication and / or authorization with the data network (DN), using the user credential information the UE 102 provided for this DN.

[0153] The SMF 366 then performs 831 UPF selection and determines whether to activate PDU Set identification and marking at the PSA UPF 370 for the PDU session with the specific DNN and S-NSSAI, based on the PCC policies the PCF 360 provided. If needed, the SMF 366 can contact 832 the PCF 360 to retrieve and / or update the PCC policies. If the relevant PCC policies require PDU Set handling, the SMF 366 instructs the PSA UPF 370 to activate PDU Set identification and marking for the PDU Session associated with the DNN and the S-NSSAI.

[0154] If the SMF 366 determines to enable PDU Set handling for the PDU Session of the UE 102, the SMF 366 includes 834, in an Namf_Communication_NlN2MessageTransfer message for the AMF 364, an N1 SM container that includes (i) a NAS message with QoS rules and uplink PDU Set based handling information and (ii) an N2 SM message including the QoS profile that contains uplink PDU Set QoS parameters, to enable the PDU Set based handling at the RAN 105. The AMF 364 836 forwards, to the RAN 105, the N1 SM container with the NAS message and the N2 SM message, in an N2 PDU Session request.

[0155] In some implementations, similar to the examples above, the uplink PDU Set based handling information can include a Protocol Description. In some implementations, similar to some of the examples above, the RAN 105 includes an indication of uplink PDU Set handling in the RRC message, when the RAN 105 enables the uplink PDU Set handling. In some implementations similar to those discussed above, the SMF 366 includes an indication of uplink PDU Set handling in the NAS message, if the RAN indicates its support for uplink PDU Set handling.

[0156] With continued reference to Fig. 8, the RAN 105 performs 840 an RRC Reconfiguration procedure, which can include a PDU Session Establishment Accept message for the AN-specific resource setup at the UE 102. The RAN 105 indicates 832 to the AMF 364, in an N2 PDU Session Response message, whether the RAN 105 accepts or rejects the PDU Set based QoS parameters for the QoS flows of the PDU Session. The N2 PDU Session Responsemessage can include the PDU Session ID, a cause value (in the event of rejection), and a list of accepted and / or rejected QFI(s). Each QFI identifies the corresponding QoS Flow.

[0157] The AMF 364 sends 860, to the SMF 366, an Nsmf_PDUSession_Update_SMContext Request including the PDU Session ID, the cause value, and the list of accepted / rejected QFI(s) to the SMF. The SMF 3646 may modify 865 the N4 session for the accepted and / or rejected QoS flows of the PDU Session at the UPF 370. For example, based on the cause value, the SMF 366 may determine to deactivate the PDU Set handling for the PDU Session at the UPF 370, or deactivate PDU Set identification and marking only for the rejected QoS flows. If the RAN 105 rejects certain QoS flows, the SMF 366 can instruct the UPF 370 to release the rejected QoS flows but maintain PDU Set handling for the accepted QoS flows. There may be a requirement for an additional signaling overhead in order to request QoS parameters without PDU Set handling at the RAN 105.

[0158] The SMF 366 sends 892 an Nsmf_PDUSession_UpdateSMContext Response message to the AMF 364, which then sends 894 a PDU SessionEstablishment Response message to the UE 102.

[0159] Referring to Fig. 9, an example method 900 for determining whether to perform PDU set based handling of uplink data, in view of whether a NAS message includes a protocol description information element, can be implemented in the UE 102 of another suitable UE. At block 940, the UE receives PDU Session Establishment / Modification Accept message (e.g., events 640, 740A, 740B, 740C, 740D, 740E, 840). At block 953, the UE determines whether the NAS message includes a Protocol Description. If yes, the flow proceeds to block 951, where the UE enables uplink PDU Set based handling to identify the IP packets of the IP flows indicated in IP connection information and mark the PDU based on Protocol Description (e.g., events 657, 658, 659, 751). Otherwise, at block 954, the UE does not enable uplink PDU Set handling.

[0160] Fig. 10 illustrates example method 1000 for determining whether to perform PDU set based handling of uplink data view of the protocol description and IP connection information, which can be implemented in the UE 102 or another suitable UE.

[0161] At block 1040, the UE receives a PDU Session Establishment / Modification Accept message (e.g., events 640, 740A, 740B, 740C, 740D, 740E, 840). The application server thenprovides uplink PDU Set Handling information to the UE via the application layer. At block 1055, the UE determines whether the lower layers received uplink PDU Set based handling information from the upper layer(s) and / or the OS. If yes, the flow proceeds to block 1051, where the UE enables uplink PDU Set based handling to identify the IP packets of the IP flows indicated in IP connection information and mark the PDUs based on Protocol Description (e.g., events 657, 658, 659, 751). Otherwise, the flow proceeds to block 1054, where the UE does not enable uplink PDU Set handling.

[0162] Referring to Fig. 11, an example method 1100 for determining whether to perform PDU set based handling of uplink data also can be implemented in the UE 102 or another suitable UE. At block 1140, the UE receives, from the RAN, PDU Set based handling information. At block 1 141, the UE receives, from the RAN, an indication of uplink PDU set based handling. At block 1156, the determines whether the indication is set to “active” (or otherwise indicates support of uplink PDU Set based handling. If yes, the flow proceeds to block 1151, where the UE enables uplink PDU Set based handling to identify the IP packets of the IP flows indicated in IP connection information and mark the PDU based on Protocol Description. Otherwise, at block 1154, the UE does not enable uplink PDU Set handling.

[0163] Next, Fig. 12 illustrates an example method 1200 for configuring a UE for uplink PDU set based handling, which can be implemented in the RAN 105 or another suitable RAN. At block 1280, the RAN determines downlink PDU set capability of the RAN. At block 1281, the RAT determines uplink PDU set capability of the RAN. Then, at block 1240A, the RAN provides downlink PDU Set based handling information to the UE. At block 1240B, the RAN provides uplink PDU Set based handling information to the UE.

[0164] Finally, Fig. 13 is a flow diagram of an example method for receiving configuration for uplink PDU set based handling, which can be implemented in the UE 102 or another similar UE. At block 1340B, the UE receives, from the RAN, uplink PDU Set based handling information. At block 1390, the UE selects a marking type for an uplink packet in view of the uplink PDU set handling information. At block 1391, the UE marks the uplink packet according to the selected marking type. At block 1392, the UE transmits the uplink packet to the RAN.

[0165] The following list of examples reflects a variety of the embodiments explicitly contemplated by the present disclosure:

[0166] Example 1. A method for configuring a UE, the method implemented in a RAN and comprising: configuring the UE with one or more rules for transmitting data in an uplink direction using PDU set based handling; and indicating, to the UE at a protocol layer for controlling radio resources, that the UE is to perform the PDU set based handling.

[0167] Example 2. The method of example 1, wherein the configuring comprises transmitting the one or more rules.

[0168] Example 2.1. The method of example 1, wherein the transmitting is the indicating.

[0169] Example 3. The method of example 1, wherein the configuring of the UE with the one or more rules includes transmitting a first message; and the indicating to the UE includes transmitting a second message.

[0170] Example 4. The method of example 3, wherein the first message is a Non-access Stratum (NAS) layer message.

[0171] Example 5. The method any of examples 1-5, except for 2.1, wherein the protocol layer for controlling the radio resources is a Radio Resource Control (RRC) message, and the indication is included in an RRC IE dedicated to conveying PDU set handling information.

[0172] Example 6. The method of example 5, wherein the RRC IE is dedicated to conveying the PDU set handling information for the uplink direction.

[0173] Example 7. The method of any of the preceding examples, wherein the indicating coneys a protocol description for a service data flow, for performing the PDU set based handling based on the protocol description, for all Quality-of-Service (QoS) flows in a PDU session.

[0174] Example 8. The method of any of examples 1-6, except for 2.1, wherein the indicating conveys a protocol description for a service data flow and an indication of a QoS flow for which the UE is to perform the PDU set based handling.

[0175] Example 9. The method of example 8, wherein the indication of the QoS flow includes a QFI.

[0176] Example 10. The method of example 8, wherein the indication includes a plurality of QoS flow, protocol description tuples.

[0177] Example 11.The method of any of examples 1-6, except for 2.1, wherein he indication is set to one of active status or inactive status.

[0178] Example 12. The method of any of the preceding examples, further comprising receiving, from the UE, an uplink packet including PDU set marking; and processing the uplink packet based on the marking.

[0179] Example 13. The method of example 12, wherein the PDU set marking includes uplink PDU set information that includes one or more of (i) a PDU set sequence number, (ii) an indication of an end PDU in a PDU set, (iii) a PDU sequence number within the PDU set, (iv) a size of the PDU set, and (v) an importance indicator for the PDU set.

[0180] Example 14. The method of example 12 or 13, wherein the PDU set marking is included in an IP header of the uplink packet.

[0181] Example 15. The method of example 14, wherein the uplink packet is unencrypted.

[0182] Example 16. The method of example 12 or 13, wherein the PDU set marking is included in a PDCP) header of the uplink packet.

[0183] Example 17. The method of example 12 or 13, wherein the PDU set marking is included in a Medium Access Control (MAC) header of the uplink packet.

[0184] Example 18. The method of example 12 or 13, wherein the PDU set marking is included in a payload of the uplink packet, the payload associated with one of an IP layer, a PDCP layer, or a MAC layer.

[0185] Example 19. The method of any of the preceding examples, further comprising determining that the RAN supports PDU set based handling; wherein the indicating to the UE is in response to the determining that the RAN supports PDU set based handling for a PDU session.

[0186] Example 20. The method of example 19, wherein the determining that the RAN supports PDU set based handling includes determining that the RAN supports PDU set based handling for uplink traffic.

[0187] Example 21. The method of any of examples 1-18, further comprising: receiving, from a core network (CN), uplink PDU set based handling information; wherein the indicating to the UE is based on the uplink PDU set based handling information.

[0188] Example 22. The method of example 21, wherein the uplink PDU Set based handling information is received in an N2 SM message.

[0189] Example 23. The method of example 21, wherein the uplink PDU Set based handling information is received in a GPRS Tunnelling Protocol U (GPT-U) header.

[0190] Example 24. A radio access network (RAN) comprising processing hardware and configured to implement a method of any of the preceding examples.

[0191] Example 25. A method implemented in a radio access network (RAN) comprising: configuring a UE with a first rule for transmitting first uplink data in a first QoS flow using protocol data unit (PDU) set based handling; configuring the UE with a second rule for transmitting second uplink data in a second QoS flow using PDU set based handling; and indicating, to the UE, that the UE is to perform the PDU set based handling.

[0192] Example 26. The method of example 25, wherein the configuring comprises transmitting the one or more rules.

[0193] Example 27. The method of example 25, wherein the transmitting is the indicating.

[0194] Example 28. The method of example 25, wherein the configuring of the UE with the one or more rules includes transmitting a first message; and the indicating to the UE includes transmitting a second message.

[0195] Example 29. The method of example 28, wherein the first message is a Non-access Stratum (NAS) layer message.

[0196] Example 30. The method any of examples 25, 26, 28, or 29, wherein the protocol layer for controlling the radio resources is a Radio Resource Control (RRC) message, and the indication is included in an RRC information element (IE) dedicated to conveying PDU set handling information.

[0197] Example 31. The method of example 30, wherein the RRC IE is dedicated to conveying the PDU set handling information for the uplink direction.

[0198] Example 32. The method of any of examples 25-31, wherein the indicating coneys a protocol description for a service data flow, for performing the PDU set based handling based on the protocol description, for all Quality-of-Service (QoS) flows in a PDU session.

[0199] Example 33. The method of any of examples 25, 26, or 28-32, wherein: the indicating conveys a protocol description for a service data flow and an indication of a QoS flow for which the UE is to perform the PDU set based handling.

[0200] Example 34. The method of example 33, wherein the indication of the QoS flow includes a QFI).

[0201] Example 35. The method of example 34, wherein the indication includes a plurality of QoS flow, protocol description tuples.

[0202] Example 36. The method of any of examples 25, 26, or 28-35, wherein the indication is set to one of active status or inactive status.

[0203] Example 37. The method of any of examples 25, 26, or 28-36, further comprising receiving, from the UE, an uplink packet including PDU set marking; and processing the uplink packet based on the marking.

[0204] Example 38. The method of example 37, wherein the PDU set marking includes uplink PDU set information that includes one or more of: (i) a PDU set sequence number, (ii) an indication of an end PDU in a PDU set, (iii) a PDU sequence number within the PDU set, (iv) a size of the PDU set, and (v) an importance indicator for the PDU set.

[0205] Example 39. The method of example 37 or 38, wherein the PDU set marking is included in an Internet Protocol (IP) header of the uplink packet.

[0206] Example 40. The method of example 39, wherein the uplink packet is unencrypted.

[0207] Example 41. The method of example 37 or 38, wherein the PDU set marking is included in a Data Convergence Protocol (PDCP) header of the uplink packet.

[0208] Example 42. The method of example 37 or 38, wherein the PDU set marking is included in a MAC header of the uplink packet.

[0209] Example 43. The method of example 37 or 38, wherein: the PDU set marking is included in a payload of the uplink packet, the payload associated with one of an IP layer, a PDCP layer, or a MAC layer.

[0210] Example 44. The method of any of the preceding examples, further comprising: determining that the RAN supports PDU set based handling; wherein the indicating to the UE is in response to the determining that the RAN supports PDU set based handling for a PDU session.

[0211] Example 45. The method of example 44, wherein the determining that the RAN supports PDU set based handling includes: determining that the RAN supports PDU set based handling for uplink traffic.

[0212] Example 46. The method of any of examples 25-43, further comprising: receiving, from a core network (CN), uplink PDU set based handling information; wherein the indicating to the UE is based on the uplink PDU set based handling information.

[0213] Example 47. The method of example 46, wherein the uplink PDU Set based handling information is received in an N2 SM message.

[0214] Example 48. The method of example 46, wherein the uplink PDU Set based handling information is received in a GPRS Tunnelling Protocol U (GPT-U) header.

[0215] Example 49. A RAN comprising processing hardware and configured to implement a method of any of examples 25-48.

[0216] Example 50. A method for configuring a UE, the method implemented in a RAN and comprising: determining whether the RAN supports PDU set based handling of uplink traffic from the UE to a CN; in a first instance, in response to determining that the RAN supports PDU set based handling of the uplink traffic, transmitting, to the UE, an indication that the UE is to perform the PDU set based handling; and in a second instance, in response to determining that the RAN does not support PDU set based handling of the uplink traffic, refraining from transmitting, to the UE, the indication that the UE is to perform the PDU set based handling.

[0217] Example 51. A method for configuring a UE the method implemented in a RAN and comprising: configuring the UE with one or more rules for transmitting data in an uplink direction using protocol data unit (PDU) set based handling; and providing, to the UE in a message at an application layer, an indication that the UE is to perform the PDU set based handling.

[0218] Example 52. A method for processing an uplink packet, the implemented in a UE and comprising: receiving, from a RAN, an indication that the UE is to perform the PDU set basedhandling of the uplink packet; selecting, based on the received indication, a type of marking of the uplink packet for the PDU set based handling; marking the uplink packet according to the selecting type.

[0219] Example 53. The method of example 52, wherein the selected type of marking is marking the uplink packet in an IP header.

[0220] Example 54. The method of example 52, wherein the selected type of marking is marking the uplink packet in a PDCP header.

[0221] Example 55. The method of example 52, wherein the selected type of marking is marking the uplink packet in a MAC header.

[0222] The following description may be applied to the description above.

[0223] A user device in which the techniques of this disclosure can be implemented (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0224] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may can be software modules (e.g., code stored on non- transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0225] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more specialpurpose processors.

[0226] As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-ex elusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present)

Claims

CLAIMS:

1. A method implemented in a user equipment (UE) for configuring a protocol data unit (PDU) session, the method comprising: receiving, at a non-access stratum (NAS) layer from a network, a response to a request to establish or modify a PDU session; receiving, at an application layer from the network, uplink PDU Set handling information for the PDU session; and processing uplink packets according to the PDU Set handling information.

2. The method of claim 1, wherein the response received at the NAS layer includes one of:(i) a PDU Session Establishment Accept message or(ii) a PDU Session Modification Accept message.

3. The method of claim 1 or 2, wherein: the uplink PDU Set handling information is received by an application client executing on the UE.

4. The method of any of the preceding claims, wherein the uplink PDU Set handling information is included in a message associated with the application layer.

5. The method of any of the preceding claims wherein the uplink PDU Set handling information includes: a protocol description, an Internet Protocol (IP) connection information6. The method of claim 5, wherein: the IP connection information corresponds to an IP flow; and the processing of the uplink packets according to the PDU Set handling information includes performing PDU set handling based on the protocol description for the IP flow.

7. The method of claim 6, wherein the performing of the PDU set handling includes: marking PDUs based on the protocol description.

8. The method of claim 6, wherein the performing of the PDU set handling includes: identifying IP packets of the IP flow based on the IP connection information.

9. The method of any of claims 5-8, wherein the protocol description indicates one or more transport-layer parameters for a service data flow (SDF).

10. The method of any of claims 5-9, wherein the IP connection information indicates (i) a source IP address, (ii) a source port number, (iii) a destination IP address, a (iv) destination port number, and (v) protocol type.

11. The method of any of the preceding claims, further comprising: receiving, from a radio access network (RAN), an indication that the RAN supports PDU Set handling information.

12. The method of claim 11, wherein: the indication that the RAN supports the PDU Set handling information is received in a Radio Resource Control (RRC) Reconfiguration message.

13. The method of any of the preceding claims, wherein: the processing of the uplink packets is in response to receiving the uplink PDU Set handling information from an upper layer at the UE.

14. The method of any of claims 1-12, wherein: the processing of the uplink packets is in response to receiving the uplink PDU Set handling information from an operating system (OS) at the UE.

15. A user equipment (UE) comprising processing hardware and a transceiver, the UE configured to implement a method of any of the preceding claims.

Images