Method and apparatus for handling support for augmented reality and media services in 5GS

Abstract

Methods and apparatus in a wireless communication system are directed to establishing augmented reality and / or media XRM service traffic between a user equipment (UE) (102) and a data network. A core network, CN, element (110) of the system receives (311), from a radio access network, RAN, node (104), single network slice selection assistance information, S-NSSAI, or XRM capabilities for XRM services of the UE (102). The CN element (110) sends (315) a Quality of Service, QoS, parameter based on a Packet Data Unit, PDU, to a Radio Access Network, RAN, node (104), and activates (317), at a User Plane Function, UPF, (166), a PDU set based handling corresponding to the PDU set QoS parameter for a PDU set based QoS flow of a PDU session associated with a network slice corresponding to the selected S-NSSAI.

Description

Technical Field

[0001] This document generally describes methods and apparatus operating in wireless communication systems, such as (but not limited to) those described in 5G standardization documents, known as 3rd Generation Partnership Project (3GPP) communication systems. Background Art

[0002] This background description is provided for the purpose of generally presenting the background and technical problems of the present disclosure. The work of the presently named inventors (to the extent that it is described in this background section) and aspects of the specification that otherwise may not be considered prior art at the time of filing are neither explicitly nor implicitly admitted to be prior art to the present disclosure.

[0003] 5G networks are configured to support a wide variety of services with highly variable quality of service (QoS) requirements. This flexibility makes 5G networks suitable for a wide range of extended reality (XR) and / or media (XRM) services. Currently, for XRM data traffic between user equipment (UE) and core network (CN) elements, the session management function (SMF) hosted by the CN element determines whether to enable PDU set-based handling based on policy and charging control (PCC) rules containing QoS parameters based on packet data unit (PDU) sets.

[0004] However, it is unclear how to configure QoS for a PDU set based on the UE's XRM service capabilities and subscriptions, as current 5G networks only check whether an application function (AF) is authorized to request QoS for the XRM service when it receives a request from the AF to create a QoS flow with QoS requirements based on a PDU set. Furthermore, it is unclear how to configure QoS for a PDU set when the network is divided into multiple network slices that provide different service types, such as enhanced mobile broadband, ultra-reliable low-latency communications, massive Internet of Things (IoT), voice, high-performance machine-type communications, high data rate and low-latency communications, etc.

[0005] Furthermore, when some radio access network (RAN) nodes support PDU set-based QoS handling for XRM services while some other RAN nodes do not, it is unclear how to handle QoS configuration for UEs. For this heterogeneous RAN node deployment, the AF can continue to request PDU set-based QoS requirements from the CN, the application server (AS) can continue to send XRM service data to the 5G network, and various functions of the CN (e.g., access and mobility management function (AMF), SMF) will continue to manage PDU set-based QoS flows based on the AF request and implement corresponding configurations for PDU set handling, even though the serving RAN node may not support PDU set-based QoS handling for XRM services, resulting in unnecessary signaling overhead for PDU set handling and waste of energy and computing power. Summary of the Invention

[0006] According to an embodiment, when the UE initiates a registration request process with a CN element, the UE sends a registration request message including the UE's XRM service capabilities. The UE may also send a PDU session establishment or modification request message to the SMF hosted by the CN element, which includes single network slice selection assistance information (S-NSSAI) for XRM services. The S-NSSAI helps the CN element select a network function that suits the UE's requirements for XRM services. The CN element then configures the UE, the RAN node, and the PDU session anchor PSA user plane function UPF for end-to-end XRM services.

[0007] In another embodiment, the CN's Access and Mobility Management Function (AMF) is informed about the RAN node's XRM service capabilities for PDU set-based handling to configure the required QoS for the XRM service. In a variant of this embodiment, the AF subscribes to the event exposure of the RAN node's XRM service capabilities for PDU set-based QoS handling so that the AF adjusts its XRM service requirements and the AS adjusts its XRM data traffic based on the availability of these services at the RAN node.

[0008] In yet another embodiment, the UE indicates its XRM service capabilities during the PDU session establishment or modification procedure rather than the registration procedure. Alternatively, the UE does not indicate its XRM service capabilities in any of these procedures, and the AMF sends one or more S-NSSAIs to the UE independently of the UE XRM service capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more embodiments and, together with the description, explain these embodiments.

[0010] Figure 1is a block diagram of a wireless communication system in which UE and CN elements perform methods according to various embodiments.

[0011] Figure 2A is a signal diagram illustrating a modified registration request procedure according to an embodiment, in which the UE provides XRM service capabilities to the CN element.

[0012] Figure 2B is a diagram showing a method for Figure 2A Flowchart of the UE behavior of the process shown in .

[0013] Figure 2C is a diagram showing a method for Figure 2B The process of AMF behavior is shown in the flowchart.

[0014] Figure 3A is a signal diagram illustrating a PDU establishment or modification procedure using S-NSSAI to establish an XRM service according to an embodiment.

[0015] Figures 3B to 3D is a diagram showing a method for Figure 3A Flowchart of the SMF, AMF and UE behaviour of the process shown in .

[0016] Figure 4 is a signal diagram showing how the PCF configures XRM service authorization for the UE according to an embodiment.

[0017] Figure 5 is a signal diagram illustrating AMF notification of XRM service capability of a RAN node for PDU set based handling according to an embodiment.

[0018] Figure 6 is a signal diagram showing how the AMF according to an embodiment obtains the XRM service capability of a RAN node for PDU set based handling based on the existing non-UE associated Next Generation Application Protocol (NGAP) procedure.

[0019] Figure 7 is a signal diagram showing how the AMF obtains the XRM service capability of the RAN node for PDU set based handling based on the new non-UE associated NGAP procedure according to an embodiment.

[0020] Figure 8 is a signal diagram illustrating how the AMF obtains the XRM service capability of the RAN node for PDU set based handling based on an indication sent with a new non-UE associated NGAP procedure according to an embodiment.

[0021] Figure 9is a signal diagram illustrating a scenario in which the AMF requests the RAN node's XRM service capability for PDU set based handling based on a new UE-associated NGAP procedure according to an embodiment.

[0022] Figure 10 is a signal diagram showing how the AMF obtains the XRM service capability of the RAN node for PDU set based handling based on the new UE-associated NGAP procedure according to an embodiment.

[0023] Figure 11 2 is a signal diagram showing how a RAN node informs the AMF of the NG-RAN node's XRM service capability for PDU set based handling based on a PDU Session Request according to an embodiment.

[0024] Figure 12 2 is a signal diagram showing how the AF exposes subscription events to the AMF of the CN according to an embodiment.

[0025] Figure 13 2 is a signal diagram showing how the AMF or SMF becomes aware of the XRM service capability of the NG-RAN node for PDU set based handling by using a new event identifier according to an embodiment.

[0026] Figure 14 2 is a signal diagram illustrating that a UE uses a subscribed XRM service based on an initial context setup request message received from an AMF according to an embodiment.

[0027] Figure 15 is a signal diagram showing that the PDU session establishment or modification procedure according to an embodiment is modified so that the SMF provides an XRM service indication to the RAN node. DETAILED DESCRIPTION

[0028] The methods and apparatus described in this section embody techniques related to XRM services in wireless communication systems. The description of embodiments in this section refers to the accompanying drawings. The same reference numerals in different drawings identify the same or similar elements. The detailed description does not preclude other embodiments within the scope of the appended claims, for example, applying one or more of the methods to further RAN elements that may not be RAN nodes. The embodiments are not limited to the described configurations but may extend to other arrangements.

[0029] Reference throughout this section to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments.

[0030] Currently, the 5G system (5GS) lacks established procedures for some aspects of the interaction between the system (e.g., UE, RAN nodes, various functions of CN elements) and XRM applications, such as configuring QoS for UEs using XRM services when multiple network slices are available. Various working groups in 3GPP have been tasked with developing procedures for the 5G system to support advanced media services such as High Data Rate Low Latency (HDRLL) services, AR / VR / XR services, and tactile / multimodal communication services. The goals of these groups include, among other things, enhancing network exposure to support interaction between 5GS and XRM applications, and enhancing QoS and policies for XRM service delivery.

[0031] As part of these developments, a PDU set is defined as comprising one or more PDUs that carry an application layer payload associated with an information unit such as a video frame or video slice. QoS flows can be enabled with PDU set-based QoS handling. All PDUs in a PDU set are sent using the same QoS parameters in the QoS flow. PDU set QoS parameters (e.g., PDU set delay budget, PDU set error rate, etc.) are used to support PDU set-based QoS handling in RAN nodes. At least one PDU set QoS parameter should be sent to the RAN node to enable PDU set-based QoS handling.

[0032] PDU set-based QoS treatment by the RAN node is determined by: PDU set QoS parameters (as specified in 3GPP Technical Specification (TS) 23.501, which are included in the QoS profile of the QoS flow); and PDU set information in the GTP-U header (GTP-U is the protocol used for user plane data transmission in 5G) provided by the PDU Session Anchor (PSA) User Plane Function (UPF). Note that the PSA UPF is typically the last UPF in the UPF chain that connects the UE to the data network (DN). The SMF instructs this UPF to perform PDU set identification and marking and may provide the UPF with a protocol description indicating the headers (e.g., Real-time Transport Protocol (RTP) / Secure RTP (SRTP)) and payload types (e.g., H.264) used by the service data flow of the media flow from the application server. Based on instructions from the SMF, for each downlink (DL) PDU received on the N6 interface for which PDU set based QoS treatment should be performed, the PSA UPF applies rules for PDU set identification and provides PDU set information, which is made available to the RAN node in the GTP-U header.

[0033] To support XRM services with PDU set-based QoS handling in 5G systems, RAN nodes need to be aware of the XRM services provided by CN elements, and vice versa. The RAN node can be configured to handle PDU sets based on the PDU set QoS parameters in the QoS profile if the SMF provides this information to the RAN node over the N2 interface. In addition, for downlink XRM traffic, the RAN node needs to receive PDU set information from the UPF over the N3 interface; for uplink XRM traffic, it needs to receive this information from the UE over the Uu interface.

[0034] The 5G Core (5GC) handles QoS provisioning based on the XRM service capabilities of the UE and RAN nodes for PDU set based handling (also known as "PDU set based QoS handling", which can be expressed as a PDU set based handling support indication). In order to support end-to-end PDU set based QoS provisioning for XRM services (between UE and DN, through PSA UPF), the 5GC needs to ensure that PDU set handling for XRM services is enabled for UEs that support the XRM service capability and are subscribed to the XRM service for PDU set handling. Currently, when an AF request is received to create a QoS flow with PDU set based QoS requirements for a target UE, the 5GC only checks whether the AF is authorized to request QoS for the XRM service. Therefore, a mechanism is needed to enable PDU set based handling for XRM services for a UE based on the UE's XRM service capability and subscription.

[0035] Furthermore, in early deployments of RAN nodes supporting PDU set-based handling for XRM services, a network may have RANs with and without XRM service capabilities for PDU set-based handling. If a RAN node does not support the XRM service capability for PDU set-based handling, the RAN node will not perform PDU set-based QoS handling for radio resource management based on the PDU set-based QoS parameters and PDU set information for the QoS flow of the XRM service for the target UE.

[0036] For this scenario where the network has RANs with and without XRM service capabilities for PDU set based handling, the end-to-end QoS configuration for the XRM service becomes uncertain because the AF can continue to request PDU set based QoS requirements from the 5GC, the AS can continue to send XRM service data to the 5G network, and the 5GC continues to manage PDU set based QoS flows based on the AF request and implement the corresponding configuration for PDU set based handling.

[0037] For example, in the downlink (DL), based on instructions from the SMF, the PSA UPF can continue to perform deep packet inspection on the PDUs to perform PDU set identification and marking, as well as implement QoS for PDUs and PDU sets. If the RAN node does not support the corresponding PDU set-based QoS parameters for the QoS flow, then the RAN node becomes a broken link for managing the end-to-end QoS of the QoS flow of the XRM service.

[0038] In another example, in the uplink (UL), based on instructions from the SMF, the UE may continue to perform PDU set identification and marking for PDUs from the XRM application on the UE, as well as implement QoS flow mapping for PDUs and PDU sets. If the RAN node does not support the corresponding PDU set-based QoS parameters for the QoS flow, then the RAN node becomes a broken link for managing the end-to-end QoS of the QoS flow of the XRM service. Therefore, in both examples, the network experiences unnecessary signaling overhead for PDU set-based handling, as well as waste of energy and computing power.

[0039] Various solutions to the above-mentioned problems for 5GC will now be discussed with reference to the accompanying drawings. The following embodiments assume that the RAN node may or may not support the XRM service capability for PDU set-based handling, the UE may or may not support the XRM service capability for PDU set-based handling, and that XRM is an XR and media service.

[0040] Before discussing these various solutions, Figure 1 As shown, a possible 5GS 100 is presented. The 5GS 100 includes a UE 102, a first base station (BS) 104, a second BS 106, and a CN element 110. In this specification, the term base station is used as a generic name for a radio access network node. BSs 104 and 106 can operate in a RAN 105 connected to the CN element 110. For example, the CN element 110 can be implemented as an evolved packet core (EPC) 111 (i.e., a non-5G system) or a 5G core (5GC) 160. In another example, the CN element 110 can also be implemented as a sixth generation (6G) core.

[0041] In this example, first BS 104 covers first cell 124 and second cell 125, and second BS 106 covers cell 126. If first BS 104 is a gNB, cells 124 and 125 are NR cells. If first BS 104 is an ng-eNB or eNB, cells 124 and 125 are Evolved Universal Terrestrial Radio Access (E-UTRA) cells. The same is true for second BS 106. Cells 124, 125, and 126 can be located in the same Radio Access Network Notification Area (RNA) or in different RNAs. In general, RAN 105 can include any number of BSs, and each of the BSs can cover one, two, three, or any other suitable number of cells. UE 102 can support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with BSs 104 and 106. Each of the BSs 104 and 106 may be connected to the CN element 110 via an interface (e.g., an S1 or Ng interface, i.e., a CN-based interface). The BSs 104 and 106 may also be interconnected via an interface (e.g., an X2 or Xn interface) for interconnecting RAN nodes (i.e., a RAN node-to-RAN node interface).

[0042] Among other components, EPC 111 may also include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. Generally speaking, SGW 112 is configured to transmit user plane packets related to audio calls, video calls, Internet traffic, etc., and MME 114 is configured to manage authentication, registration, paging, and other related functions. PGW 116 provides connectivity from the UE to one or more external packet data networks, such as the Internet network and / or the Internet Protocol (IP) Multimedia Subsystem (IMS) network. 5GC 160 includes a user plane function (UPF) 162, an access and mobility management function (AMF) 164, and / or a session management function (SMF) 166. Each of these functions can be hosted by a corresponding processor or a general-purpose processor. Among other functions, UPF 162 is configured to transport user plane packets associated with audio calls, video calls, Internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging, and other related functions, and SMF 166 is configured to manage PDU sessions. CN element 110 may also include processing hardware 140, processor 142, receiver 144, transmitter 146, and storage medium 148, which are similar to components 130, 132, 134, 136, and 138 of first BS 102, respectively. These components are discussed in more detail below.

[0043] Because the cells 124, 125, and 126 may partially overlap, the UE 102 may select, reselect, or switch from one of the cells 124, 125, and 126 to another. In order to directly exchange messages or information (e.g., related to a handover process), the first BS 104 and the second BS 106 may support an X2 or Xn interface, i.e., a dedicated protocol for exchanging messages between BSs without involving the CN element 110. In addition, the BS is connected to the CN element 110 via an Ng interface, which may be connected to any suitable number of BSs supporting NR cells and / or EUTRA cells.

[0044] The first BS 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory storing instructions executed by the one or more general-purpose processors. Additionally or alternatively, the processing hardware 130 may include a dedicated processing unit. In an example implementation, the processing hardware 130 includes a processor 132 to process data to be transmitted by the first BS 104 in the downlink (DL) direction, or to process data received by the BS 104 in the uplink (UP) direction. The processing hardware 130 may also include a transmitter 136 configured to transmit data on the DL. The processing hardware may further include a receiver 134 configured to receive data in the uplink direction. The processing hardware 130 may also include a storage medium 138 for storing instructions executed by the processor 132. The second BS 106 may include similar components.

[0045] The UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions that can be executed on the one or more general-purpose processors, and / or dedicated processing units. The processing hardware 150 may include a processor 152 to process data to be transmitted by the UE 102 on the UP, or to process data received by the UE 102 on the DL. The processing hardware 150 may also include a transmitter 156 configured to transmit data on the DL. The processing hardware may further include a receiver 154 configured to receive data on the UP. The processing hardware 150 may also include a storage medium 158 for storing instructions executed by the processor 152.

[0046] According to an embodiment, the UE uses a registration procedure to obtain one or more network slices that support XRM services. More specifically, the AMF of the CN element authorizes the UE to use the XRM service based on the UE's XRM service capabilities and / or the UE's subscription. For example, the UE's subscription includes a specific network slice described by a single network selection assistance information (S-NSSAI) for XRM services with specific PDU set-based QoS requirements. The S-NSSAI is defined in 3GPP Technical Specification (TS) 23.501 and includes a slice / service type (SST), which refers to the expected network slice behavior in terms of features and services, and a slice differentiator (SD), which is optional information that supplements the SST to distinguish among multiple network slices of the same SST. The S-NSSAI can have a standard value (e.g., the S-NSSAI only includes an SST with a standardized SST value and no SD) or a non-standard value (i.e., such S-NSSAI includes both an SST and an SD set (e.g., HDLLC)), or only an SST without a standardized SST value and no SD). For example, an SST value may be associated with a QoS requirement requiring, for example, high data rate and low latency communications.

[0047] The Policy Control Function (PCF) implemented by the CN element supports Policy Control and Charging (PCC) rules to enable PDU set based QoS parameters based on XRM service authorization and RAN node support for XRM service for PDU set based handling. If the UE is capable of XRM service, the UE enables PDU set handling for PDU set QoS flows based on the authorization of the XRM service configured by the PCF. In this regard, the UE may obtain information of the subscribed and / or authorized S-NSSAI for the XRM service from the CN element as part of the registration request process. When the XRM application is invoked at the UE, the UE may send a PDU Session Establishment / Modification Request message that includes the Data Network Name (DNN) and the specific S-NSSAI (subscribed network slice) for the XRM service. These features will be related to Figure 2A Discuss in more detail.

[0048] The modified registration process 260 (the conventional registration process is described in 3GPP TS 23.502) is as follows Figure 2A As shown, the UE behavior regarding the registration process 260 is as follows Figure 2B As shown, and the AMF behavior regarding the registration process 260 is as follows Figure 2C As shown. Figure 2AAs shown, the conventional registration procedure is modified so that the UE includes the UE's XRM service capability in the registration request message 200, which may be part of the 5G Mobility Management (5GMM) capability. The UE's XRM service capability indicates whether the UE 102 supports the XRM service capability for PDU set-based QoS treatment, for example, whether the UE 102 is authorized to use the XRM service for UL, or whether the UE 102 is authorized to use the XRM service for DL, or whether the UE 102 is authorized to use the XRM service. Note that in this document, the term "XRM service capability" indicates whether there is support for "PDU set-based QoS treatment".

[0049] During the UE modified registration process 260, the AMF 164 uses, for example, the Nudm_SDM service defined in 3GPP TS 23.502 to obtain 201 UE XRM service subscription data from the UDM 168 as part of the user subscription data. For example, the XRM service subscription data includes one or more network slices for the XRM service defined by the S-NSSAI. The AMF determines whether the UE is authorized to use the XRM service based on the UE's XRM service capabilities and the XRM service authorization included in the subscription data received from the UDM. If the UE is authorized for the XRM service, the AMF stores the authorized UE XRM service capabilities. If the UE 102 is authorized to use the XRM service, the AMF 164 discovers the PCF 169 via the Network Function Repository Function (NRF) to associate the UE 102 with the PCF 169 and sends the authorized UE XRM service capabilities for XRM service operation to the PCF 169.

[0050] These features are now about Figure 2A for discussion. The UE 102 sends 200 a Registration Request message including the UE's XRM service capabilities as part of the 5GMM Capability IE to the AMF 164. The AMF 164 requests 201 the UE's subscription from the UDM 168 by indicating the UE's Subscription Persistent Identifier (SUPI) and the UE XRM service capabilities. The AMF 164 then obtains XRM service subscription data as part of the user subscription data, which includes the S-NSSAI for the XRM service, for example using the Nudm_SDM service. The AMF 164 determines whether the UE is authorized to use the XRM service based on the UE's XRM service capabilities and the XRM service authorization included in the subscription data received from the UDM. If the UE is authorized for the XRM service, the AMF stores the authorized XRM service capabilities.

[0051] If the UE 102 is authorized for XRM services, the AMF 164 performs 203a / 203b PCF 169 selection and establishes the UE's access and mobility (AM) policy association with the PCF. The PCF-UE 169 registers 203c its address and instance for the UE to the Binding Support Function (BSF) 170. The BSF is used to bind application function requests to a specific PCF. The SMF 166 can use this information to select the same PCF 169 for the PDU session for the XRM service. The AMF 164 then sends 204 a Registration Accept message to the UE, which includes information about the authorized network slices for the XRM service (one or more S-NSSAIs). The UE stores 205 the received S-NSSAI for the XRM service, and the UE activates 206 the XRM application and sends a PDU Session Establishment / Modification Request procedure 208 indicating the desired DNN and selected S-NSSAI for the XRM service.

[0052] Now about Figure 2B Public Figure 2A 10. Behavior of the UE 102 during the procedure shown. The UE sends 200 the UE's XRM service capabilities in the registration request procedure, which may be part of "5GMM capabilities" because the UE's XRM service capabilities indicate at least one of the following: (1) the UE is authorized to use XRM services for UL, (2) the UE is authorized to use XRM services for DL, or (3) the UE is authorized to use XRM services. The UE receives 204 a registration accept message including one or more subscribed / authorized S-NSSAIs associated with one or more XRM services. The UE stores 205 the received S-NSSAIs for the XRM services. The UE activates 206 the XRM application. Upon activation, the UE checks 217 the stored S-NSSAIs for the XRM services and determines the S-NSSAI for the XRM application. If the stored S-NSSAI is selected for the XRM application, the UE sends 208a a PDU Session Establishment / Modify Request message to the SMF via the AMF, which includes the DNN for the XRM services and the selected S-NSSAI. Then, the XRM application enables PDU set-based handling. If no S-NSSAI is selected for the XRM application, the UE sends 208b a PDU Session Establishment / Modification Request message, which includes the DNN and a default S-NSSAI, which can be a default for the XRM service or a default for all services. In this case, PDU set-based handling is not enabled.

[0053] Now about Figure 2C Public Figure 2ABehavior of the AMF 164 during the procedure shown. The AMF receives 200 a Registration Request message from the UE including the UE's XRM service capabilities. The AMF 164 stores 209 the UE's XRM service capabilities for XRM service operation and requests 201 the UE's subscription and authorization for the XRM service from the UDM 168. If the UE is authorized for XRM services, the AMF 164 performs 202 PCF selection for the UE (PCF-UE) and establishes the UE's Access and Mobility (AM) policy association with the PCF. For simplicity, it is assumed that the PCF is the same as the PCF of the PDU Session (PCF-PS) selected later by the SMF. The AMF 164 sends 204 a Registration Accept message to the UE including information of the authorized network slices for the XRM service (one or more S-NSSAIs).

[0054] In order to use the subscribed XRM services, the UE and CN elements perform PDU session establishment or modification procedures. Figure 3A The modified PDU session establishment procedure 208 is discussed. The UE 102 sends 310a / b a PDU session establishment request message to the AMF 164 via the RAN node 104, including the DNN and the selected S-NSSAI for the XRM service. The AMF 164 selects 311 an SMF 166 capable of PDU set-based handling based on the stored XRM service capabilities of the UE, the DNN, and the S-NSSAI. The AMF 164 sends 312a to the SMF 166, for example, using an Nsmf_PDUSession_CreateSMContext request message including the DNN and S-NSSAI. The SMF 166 checks 313 with the UDM 168 that the UE is subscribed to and authorized for the S-NSSAI for the XRM service. The SMF 166 responds 312b to the AMF to create the PDU session. If the UE does not have authorization and subscription for the S-NSSAI, the SMF sends a PDU Session Establishment or Modification Reject message including a cause value to the UE and the process stops.

[0055] The SMF 166 selects 314a the PCF 169 for this PDU Session (for simplicity, assumed to be the same as the PCF for the UE), and if the PCF determines to enable PDU set-based handling for the QoS flow of the PDU Session associated with the DNN and S-NSSAI, then the request 314b includes the PCC rules for the PDU set-based QoS parameters for the subscribed XRM service. The SMF then sends an N2 message including the following: • N2 SM information 315a, which includes a QoS profile with UL / DL PDU-set based QoS parameters for UL / DL PDU-set based QoS flows; and • N1 NAS message 315b, 315c, which includes a PDU Session Establishment / Modification Accept message, which includes one or more QoS flow information: QoS rules and protocol descriptions of PDU set-based QoS flows for the PDU session (represented by standardized values ​​or included in a container).

[0056] If the RAN node 104 supports PDU set-based QoS handling, it sends 316a / b of the RAN node's XRM service capability for PDU set-based handling to the SMF 166 via the AMF 164. Based on this indication, the SMF 166 determines 317 to enable PDU set-based handling and instructs the PSA UPF 169 in an N4 message including PDU set-based QoS parameters and a protocol description indicating a header (e.g., Real-time Transport Protocol (RTP) / Secure RTP (SRTP)) for PDU set-based identification and marking. Alternatively, the SMF initiates a PDU Session Modification procedure to update the PSA UPF 169 and / or the UE. The SMF 166 sends 318a / b a PDU Session Establishment / Modification Response message to the UE 102 via the AMF 64.

[0057] With this message, UE 102 may do the following: • For DL ​​XRM traffic, it maps Data Radio Bearers (DRBs) to QoS flows based on PDU sets and forwards them to the XRM application, • For UL XRM traffic, it determines whether PDU set based handling (including UL PDU set identification and / or marking) is enabled for XRM traffic received from the XRM application and maps the QoS flows to DRBs.

[0058] Now about Figure 3B Discussion on Figure 3A . The SMF 166 receives 310a / b a PDU SESSION SETUP REQUEST message from the UE 102 via the AMF 164, including a DNN and a specific S-NSSAI for the XRM service. The SMF 166 selects 314a the PCF 169 for the PDU session and requests PCC rules including PDU set-based QoS parameters for the subscribed XRM service. If the PCF determines to activate PDU set-based handling with a PDU set-based QoS flow for the PDU session, the SMF 166 receives 314b a PCC rule including PDU set-based QoS parameters for the subscribed S-NSSAI for the XRM service. The SMF 166 then sends 315 an N2 message to the RAN node 104. The N2 message includes: • N2 SM information containing the QoS profile with UL / DL PDU-set based QoS parameters, and • N1 information, which contains a NAS message including QoS rules with QoS flows and packet filters for XRM services, which can be further delivered to the UE.

[0059] The SMF 166 determines 317 to activate PDU set-based handling and initiates a PDU session modification request procedure that instructs the PSA UPF to activate PDU set-based handling via an N4 message. The N4 message may include PDU set-based QoS parameters and a protocol description indicating a header (e.g., Real-time Transport Protocol (RTP) / Secure RTP (SRTP)) for PDU set-based identification and marking.

[0060] Now about Figure 3C Discussion on Figure 3A 3. The AMF 164 behavior of the modified PDU Session Establishment 208 shown in FIG. The AMF 164 receives 310 a / b a PDU Session Establishment / Modify Request message from the UE, including the DNN and S-NSSAI for the XRM service. The AMF 164 then selects 311 the SMF 166 and sends 312 a / b to the SMF 166, including the DNN and S-NSSAI for the XRM service for the UE. The AMF 164 passes 315 an N2 message from the SMF 166 to the RAN node 104. The N2 message includes N2 information with a QoS profile including UL and / or DL ​​PDU set-based QoS parameters to the RAN node 104. The N2 message further includes N1 information with a NAS message to the UE, the NAS message including QoS rules, including information and packet filters for the QoS flow for the XRM service. The AMF 164 further delivers 317 the RAN node’s XRM service capability for PDU set based handling from the RAN node 104 to the SMF 166 , and also delivers 318 a PDU Session Establishment / Modification Response message from the SMF 166 to the RAN node 104 and the UE 102 .

[0061] Now about Figure 3D Discussion on Figure 3A3. The RAN node 102 behavior of the modified PDU session establishment 208 shown in FIG. The RAN node sends 310a / b a PDU session establishment / modification request message including the DNN and S-NSSAI for the XRM service to the CN element 110. The RAN node 104 receives 315b a PDU session establishment / modification accept message including the QoS flow information for the PDU session from the CN element, and sends 315c an access network (AN) resource setup for the PDU session establishment / modification procedure for the XRM service to the UE. The RAN node 104 also sends 316a a PDU session response indicating RAN support for the XRM service to the AMF. The RAN node 104 passes a PDU session establishment / modification response message from the AMF 164 to the UE 102, instructing the UE 102 to establish a PDU set-based QoS flow with the XRM application.

[0062] Figures 3A to 3D The embodiments shown may be modified as follows. In a variation of those embodiments, the UE is not (as described above with respect to Figures 2A to 2C The UE's XRM service capabilities are indicated in the Registration Request message 200 as discussed above, and the AMF (independent of the UE's XRM service capabilities) sends 204 one or more S-NSSAIs in the Registration Accept message. Figure 3A The PDU session establishment / modification request message shown in step 310a / b indicates the UE's XRM service capability, which may be part of the 5GSM capability.

[0063] For this embodiment, the UE 102 sends 310a / b PDU Session Establishment Request message to the AMF 164, which includes the DNN for the XRM service and the selected S-NSSAI, as well as a different Figure 3A , the UE's XRM service capability, which may be part of the 5GMM capability. The AMF 164 selects 311 an SMF capable of PDU set based handling based on the received UE's XRM service capability, DNN and S-NSSAI. The AMF 164 sends 312a an Nsmf_PDUSession_CreateSMContext request message including, for example, the DNN and S-NSSAI and the UE's XRM service capability to the SMF 166. Based on the UE's XRM service capability, DNN and S-NSSAI, the SMF checks 313 with the UDM the UE's subscription and authorization for the DNN and S-NSSAI for the XRM service. The remaining steps are similar to those regarding Figure 3A The steps described.

[0064] Can be further modified Figures 3A to 3DThe embodiment shown in , makes UE 102 not in the registration request message (see Figure 2A , step 200) or PDU session establishment / modification process (see Figure 3A , step 310a / b) indicates the XRM service capability of the UE, and the AMF 164 (independent of the XRM service capability of the UE) sends one or more S-NSSAIs in the Registration Accept message. More specifically, with respect to Figure 3B , UE 102 sends 310a / b a PDU Session Establishment Request message including the DNN and the selected S-NSSAI to SMF 166 via AMF 164. AMF 164 selects 311 an appropriate SMF based on the DNN and the selected S-NSSAI. AMF 164 sends 312a an Nsmf_PDUSession_CreateSMContext Request message including the DNN and the selected S-NSSAI to the SMF, for example. Based on the DNN and the selected S-NSSAI, the SMF checks 313 with the UDM the UE's subscription and authorization for the DNN and the selected S-NSSAI. Then, the SMF is executed without any modification. Figure 3A The remaining steps 312b to 318b are performed.

[0065] Next, various additional embodiments are discussed, and each such embodiment may be combined with Figures 2A to 3DAccording to an embodiment, PCF 169 is configured to query a RAN node's XRM service capability for PDU set-based handling and subscribe to AMF 164 notifications of the RAN node's XRM service capability for PDU set-based handling when the serving RAN node for a UE changes. For this embodiment, a new event identity (ID) is introduced for exposing new events: the RAN node's XRM service capability for PDU set-based handling, or a change in the RAN node's XRM service capability for PDU set-based handling for a UE's serving RAN node. For this embodiment, AMF 164 sends a notification to PCF 169, for example, in an EventExposure_Notify message. If the serving RAN node is capable of PDU set handling for XRM services, the PCF provides rule updates for new / existing PDU sessions to all affected SMFs based on the supported RAN node's XRM service capability for PDU set-based handling, or provides PCC rules for new PDU sessions and / or new QoS flows to SMF 166. In addition to the QoS parameters for PDU handling, if PDU set-based handling is activated and the RAN node's XRM service capability for PDU set-based handling is supported, the PCC rules may also contain PDU set QoS parameters and PDU set information. Although the above description relates to event-based subscriptions for the XRM service capability for PDU set-based handling, the description can be applied to any other event-based subscriptions, i.e., non-XRM service capabilities.

[0066] For the XRM service capability for PDU set based handling, the SMF 166 performs QoS flow binding based on the PCC rules from the PCF and configures the UPF for PDU set identification and marking according to the PDU session establishment procedure, PDU session modification procedure, and AF session with required QoS procedure and / or AF session with required QoS update procedure as disclosed in 3GPP TS 23.502. Figure 2A In step 203b, the PCF configures authorization of the XRM service to the UE 102 by including one or more of the following: (1) whether the UE is authorized to use the XRM service for UL, (2) whether the UE is authorized to use the XRM service for DL, or (3) whether the UE is authorized to use the XRM service.

[0067] To use XRM service authorization, the UE performs the following: • Instruct upper layers to perform PDU set-based handling of UL traffic received from the XRM application, and / or • Map one or more DRBs to a PDU set QoS flow for XRM traffic received from the 5G network.

[0068] Now about Figure 4 The above features are discussed in more detail. Figure 4 The PCF 169 is shown configuring the UE 102 using the UE Configuration Update procedure, which is Figure 2A The registration procedure 260 shown is then performed. The PCF decides 420 to update the UE policy and therefore subscribes 420a to the AMF 164 to be informed about the UE policy. The PCF then sends 421 a message, such as a Namf_Communication_N1N2MessageTransfer message including the UE's XRM service authorization, to the UE's AM policy hosted by the AMF 164. An optional network-triggered service request may be sent 422 to the UE 102. Based on the UE Configuration Update procedure for transparent UE policy delivery, the AMF delivers 423 the UE's AM policy to the UE 102 via a DL NAS transport message. The UE 102 informs 424 the AMF of the result of the UE policy delivery and the AMF confirms 425 the result to the PCF.

[0069] Figure 5 The messages exchanged between the AMF, RAN node, and PCF to implement the configuration of a UE with XRM service authorization are shown in greater detail. An AF session is established 530 based on a QoS procedure or an AF session with a required QoS update procedure. A PDU Session Establishment procedure or a PDU Session Modification procedure 208 is then initiated. The PCF 169 queries 531 the AMF 164 for the RAN node's XRM service capabilities for PDU set-based handling and subscribes to AMF notifications for new event IDs of the RAN node's XRM service capabilities for PDU set-based handling when the UE's serving RAN node changes. The RAN node 104 provides 532 its XRM service capabilities for PDU set-based handling to the AMF. The AMF sends 533 a notification to the PCF, for example, in a Namf_EventExposure_Notify message, which includes the RAN node's XRM service capabilities for PDU set-based handling. Thus, the PCF is informed by the AMF of the RAN node's XRM service capabilities for PDU set-based handling.

[0070] The PCF determines 534 based on the supported RAN node's XRM service capability for PDU set-based handling to provide / update PCC rules with updated policy information to all affected SMFs via, for example, an Npcf_SMPolicyControl_UpdateNotify request for new / existing PDU sessions. If the RAN node supports the XRM service capability for PDU set-based handling, the PCF configures the SMF 166 with PCC rules with PDU set QoS parameters and indicates the header (e.g., Real-time Transport Protocol (RTP) / Secure RTP (SRTP)).

[0071] The PCF 169 notifies the NEF 535 of the subscribed policy authorization of the RAN node's XRM service capability for PDU set-based handling, and the NEF sends 536 an Nnef_AFsessionWithQoS_Notify message to the AF, for example, with the event reported by the PCF. The SMF 166 performs 317 QoS flow binding based on the PCC rules and configures the UPF for PDU set identification and marking via the N4 interface. The SMF then updates 318a the RAN node 104 with the QoS profile for the PDU session and updates 318b the UE 102 with the QoS rules during the PDU session establishment / modification process.

[0072] The AMF can use various mechanisms to learn about the XRM service capabilities of RAN nodes for PDU set-based handling. Traditionally, the RAN Configuration Update procedure is used to update application-level configuration data required for proper interoperation between the RAN node and the AMF. This procedure uses non-UE-related signaling. This procedure is modified as follows to take into account the RAN node XRM service capabilities.

[0073] According to the embodiment describing Option A, the RAN node reports its XRM service capability for PDU set-based handling to the AMF according to the non-UE-associated N2 procedure. This procedure is used to inform the AMF whether the XRM service capability is activated at the RAN node. In other words, a RAN node capable of performing XRM service for PDU set-based handling can enable or disable its XRM service capability for all its served UEs on a per-RAN node basis, which can be based on local configuration or overload control.

[0074] For example, Figure 6 An existing non-UE associated N2 procedure is shown, which is the RAN Configuration Update procedure as described in 3GPP TS 38.413 and includes the RAN node 104 sending 640 a RAN Configuration Update to the AMF 164, and receiving 642 a RAN Configuration Update Confirmation. Figure 7A modified procedure is shown that relies on non-UE-associated N2 messages and is used to convey the capabilities of a RAN node, such as XRM service capabilities. The non-UE-associated N2 procedure is used by the AMF to request 744 the XRM service capabilities of the RAN node, and the RAN node responds 746 with its XRM service capabilities. Figure 8 The use of a new non-UE associated N2 message is shown, which is specifically used to convey 847 the capabilities of the RAN node to the AMF, such as the XRM service capability for PDU set based handling.

[0075] According to another embodiment describing Option B, the RAN node reports its XRM service capability for PDU set-based handling to the AMF based on the UE-associated N2 procedure. This procedure is used to inform the AMF whether the XRM service capability is activated. In other words, a RAN node capable of performing XRM service for PDU set-based handling can enable or disable its XRM service capability on a per-UE basis based on local configuration or overload control.

[0076] For example, Figure 9 As shown, the UE-associated N2 procedure is used by the AMF to request 944 the XRM service capabilities of the RAN node, and the RAN node responds 946 with its XRM service capabilities. Figure 10 A new UE-associated N2 message is shown, which is specifically used to convey 1047 the XRM service capabilities of the RAN node for PDU set based handling to the AMF, e.g., an XRM service capability indication.

[0077] According to the description Figure 11 In yet another embodiment of Option C shown, the RAN node Figure 3A The N2 message of the PDU session establishment / modification procedure 208 indicates 1110 the XRM service capability of its RAN node for PDU set-based handling (corresponding to step 310).

[0078] The XRM service capability of the RAN node for PDU set based handling can also be provided to the AF, as now described with respect to Figure 12As discussed above, the AF 174 may receive the XRM service capabilities of the RAN node 104 via the NEF 172 or directly from the PCF 169. The AF may subscribe to AMF or PCF notifications of the RAN node's XRM service capabilities for PDU set-based handling when the UE's serving RAN node changes. A new event ID is introduced for exposing the following new events: the RAN node's XRM service capabilities for PDU set-based handling, or a change in the RAN node's XRM service capabilities for PDU set-based handling for the UE's serving RAN node. Using this event subscription, the AMF sends a notification to the PCF or NEF, for example, in an EventExposure_Notify message.

[0079] More specifically, AF 174 requests an event exposure including one or more of the following parameters: target UE ID, event ID, event reporting criteria, and validity criteria. When the UE's serving RAN node changes, an event ID is set for the RAN node's XRM service capability for PDU-set-based handling. The event reporting criteria can be: 1) always report when the serving RAN node changes, or 2) report only when the RAN node's XRM service capability for PDU-set-based handling changes in conjunction with the serving RAN node change.

[0080] The target UE ID can be a Universal Public Subscription Identifier (GPSI) representing an individual UE or a list of UEs, or an external group identifier representing a group of UEs. The NEF maps the GPSI in the target UE ID to a SUPI, or maps the external group identifier to an internal group identifier, based on information received from the UDM.

[0081] The validity criteria include validity conditions for the AF request, such as time window, target geographical area, as the NEF maps the geographical area in the spatial validity condition to the area of ​​validity determined by the local configuration, by referring to a predefined area represented by a tracking area list, cell list or (R)AN node identifier list, which can be the area of ​​interest (AOI) of the network function such as AMF, SMF, PCF.

[0082] The NEF 172 requests 1252a-1252b or 1252c-1252f event exposure service operations from the AMF 164 or PCF 169, for example using an Npcf_EventExposure_Subscribe message or a Namf_EventExposure_Subscribe message, which includes the target UE ID, the event ID of the RAN node's XRM service capability for PDU set based handling, event reporting criteria and validity criteria.

[0083] The NEF 172 responds 1253 to the AF 174, for example, in an Nnef_EventExposure_Subscribe Response message or a Namf_EventExposure_Subscribe Response message, based on the information collected from the AMF 164 and / or PCF 169. The AMF 164 obtains 1254 the RAN node's XRM service capabilities for PDU-set-based handling via an N2 message from the RAN node 104. The PCF and / or AMF sends 1255a or 1255b to 1255c notifications to the NEF in Npcf_EventExposure_Notify or Namf_EventExposure_Notify messages, respectively, which include the RAN node's XRM service capabilities for PDU-set-based handling. The NEF 172 sends 1256 to the AF 174, for example, an Nnef_EventExposure_Notify message including the RAN node's XRM service capabilities for PDU-set-based handling. The AF 174 determines 1257 whether to create, modify, activate or deactivate PDU set based QoS for the XRM service via, for example, the Nnef_AFsessionWithQoS_Create request procedure for a new or existing AF session for the required QoS.

[0084] In one embodiment, the SMF subscribes to the AMF notification of the RAN node's XRM service capability for PDU set-based handling when the UE's serving RAN node changes. For this embodiment, a new event ID is introduced to expose the following new events: the RAN node's XRM service capability for PDU set-based handling, or the RAN node's XRM service capability for PDU set-based handling changes. When a new event occurs, the AMF sends a notification to the SMF, for example, in an EventExposure_Notify message.

[0085] More specifically, regarding Figure 13, establishing / modifying 208 a PDU session as follows. An AF session is established 530 based on the required QoS procedure or the AF session with the required QoS update procedure. The NEF 172 subscribes to the policy authorization for the RAN node's XRM service capability for PDU set-based handling from the PCF. The PDU session establishment / modification procedure 208 is initiated. The SMF 166 performs 1358 an SM policy association and modification procedure with the PCF 169 to obtain PCC rules, which may include PDU set QoS parameters and a protocol description indicating the header (e.g., Real-time Transport Protocol (RTP) / Secure RTP (SRTP)), if applicable. The SMF 166 queries 1331 the RAN node's XRM service capability for PDU set-based handling from the AMF 164 and subscribes to AMF notifications of the RAN node's XRM service capability for PDU set-based handling when the UE's serving RAN node changes. The RAN node 104 indicates 532 its XRM service capabilities for PDU set based handling to the AMF 164. The AMF 164 sends 1333 a notification to the SMF 166, for example in a Namf_EventExposure_Notify message, which includes the RAN node's XRM service capabilities for PDU set based handling.

[0086] The SMF 166 performs 534 an SM policy association and modification procedure with the PCF 169 to obtain PCC rules, which may include PDU set-based QoS parameters and PDU set information, if applicable. The PCF 169 notifies 535 the NEF 172 of the subscribed policy authorization for the RAN node's XRM service capabilities, and the NEF sends 536 an Nnef_AFsessionWithQoS_Notify message to the AF with the event reported by the PCF. The SMF 166 performs 317 QoS flow binding for the service data flow of the XRM service based on the RAN node's XRM service capabilities for PDU set-based handling and the PCC rules. If the RAN node supports the XRM service capabilities for PDU set-based handling, the SMF configures the UPF via the N4 interface for PDU set identification and marking.

[0087] Finally, the SMF 166 updates 318 the a / b RAN node with the QoS profile for the QoS flow of the PDU session in an N2 message and updates the UE with the QoS rules in an N1 PDU Session Accept message.

[0088] In a different embodiment, the XRM capability of the RAN node for PDU set based handling may be provided to the SMF via the AMF per PDU session, as now described with respect to Figure 14The AMF may configure the RAN node with the XRM service authorization via the Initial Context Setup Request message associated with the Registration Request procedure 1460, which is Figure 2A A modification of the process 260 shown. The XRM service authorization may include one or more of the following: the UE is authorized to use the XRM service for the UL; the UE is authorized to use the XRM service for the DL; or the UE is authorized to use the XRM service. The RAN node capable of performing XRM services may perform PDU set-based handling due to the XRM service authorization and information received from the SMF via the N2 message and the GTP-U header received from the UPF via the N3 interface.

[0089] The RAN node may also inform the UE about its XRM service. In one embodiment, after the RAN node receives the XRM service authorization, if the RAN node supports and enables its XRM service capability, it includes the XRM service indication in an RRC message such as RRCReconfiguration, which is sent to the UE in the registration process 1460. This embodiment can be applied to at least two situations: • Case 1: The RRCReconfiguration message may be sent in the Registration Request process 1460, and • Case 2: When the RAN node enables or disables the XRM service capability for the UE, the RAN node may initiate an RRCReconfiguration message.

[0090] When there is an XRM service indication, the UE performs the following steps: • Instructs upper layers to perform PDU set handling on UL XRM traffic received from the XRM application, and • Map one or more DRBs to a PDU set QoS flow for DL ​​XRM traffic received from the 5G network.

[0091] Figure 14Message flows for this embodiment are shown. The UE 102 sends 1400a / b a Registration Request message to the AMF 164 including the UE's XRM service capabilities as part of the 5GMM Capability IE. The AMF 164 obtains 1472 the UE's XRM service subscription data from the UDM 168 as part of the user subscription data using, for example, the Nudm_SDM service. The AMF determines whether the UE is authorized to use XRM services based on the UE's XRM service capabilities and the XRM service authorization included in the subscription data received from the UDM. If the UE is authorized for XRM services, the AMF stores the authorized UE XRM service capabilities. If the UE is authorized for XRM services, the AMF 164 performs 1474 PCF selection. The AMF 164 sends 1478a / b a Registration Accept message to the UE by configuring 1478a the RAN node 104 with the XRM service authorization via the Initial Context Setup Request message. If the RAN node supports the XRM service capability for PDU set-based handling, the RAN node includes 1478b XRM service authorization in the RRC message sent to the UE using, for example, an RRCConnectionReconfiguration message. The AMF 164 further establishes 1476 the UE Access and Mobility (AM) policy associated with the PCF 169.

[0092] In one embodiment, if the RAN node UE context stores UE authorization for XRM services, the RAN node indicates its XRM service capabilities to the SMF via the AMF, for example in the PDU session establishment or modification procedure 208, as now described with respect to Figure 15 As discussed. The PCF provides the SMF with PCC rules including PDU set QoS parameters and PDU set information based on the UE's XRM service authorization. The SMF performs QoS flow binding based on the RAN node's XRM service capabilities for PDU set-based handling and PCC rules, and configures the UPF for PDU set-based handling and marking.

[0093] For example, during the PDU session establishment procedure 208, an XRM service indication may be provided to the AMF, for example in the message Namf_Communication_N1N2MessageTransfer, based on the following two options: • In option 1, the Namf_Communication_N1N2MessageTransfer message includes the XRM service indication, PDU session ID, N2 SM information, and N1 SM container and Nsmf_PDUSession_SMContextStatusNotify. • In option 2, the Nsmf_PDUSession_SMContextStatusNotify message includes an XRM service indication that provides the SMF-derived, CN-assisted RAN parameter adjustment service. The AMF stores the SMF-derived, CN-assisted RAN parameter adjustment in the associated PDU Session Context for this UE.

[0094] For the PDU session establishment procedure 208, the RAN node capable of XRM service can perform PDU set-based handling of QoS flows in the PDU session based on the XRM service authorization and information received from the SMF via the N2 message and the GTP-U header received from the UPF via the N3 interface.

[0095] about Figure 15 The message flows associated with this embodiment are discussed in more detail. The RAN node's XRM service capabilities for PDU set-based handling may be exposed to the SMF via the AMF. The UE performs the Registration Request procedure 260 / 1460, and the AMF 164 may configure the RAN node with an XRM service authorization via an Initial Context Setup Request message, and the RAN node may store the XRM service authorization in the UE context. If the RAN node supports and enables its RAN node XRM service capabilities, the RAN node receiving the XRM service authorization may include an XRM service indication in an RRC message sent to the UE, such as an RRCReconfiguration message.

[0096] As part of the PDU session establishment 208, the UE sends 1510a a PDU Session Establishment Request message to the SMF 166 via the AMF 164, and the RAN node 104 indicates 1510b its XRM service capabilities to the AMF 164 in an N2 message based on the XRM service authorization configured in 260 / 1460. The AMF 164 sends 1512a, for example, an Nsmf_PDUSession_CreateSMContext Request message including the XRM service capabilities of the RAN node to the SMF 166, and receives 1512b, for example, an Nsmf_PDUSession_CreateSMContext Response message from the SMF. The SMF 166 performs 1514b an SM policy association and modification procedure with the PCF 169 to obtain PCC rules, which may include QoS parameters based on the PDU set and a protocol description indicating the header (e.g., Real-time Transport Protocol (RTP) / Secure RTP (SRTP)), if applicable. The SMF 166 also performs 1514a QoS flow binding based on the received PCC rules and configures the UPF for PDU set identification and marking via the N4 interface. The SMF 166 sends an N4 Session Establishment / Modification Request to the UPF, and the UPF acknowledges by sending an N4 Session Establishment / Modification Response.

[0097] SMF 166 queries 1515a the AMF 164 for the RAN node's XRM service capabilities for PDU-set-based handling and subscribes 531 to AMF notifications for event exposure of the RAN node's XRM service capabilities for PDU-set-based handling when the UE's serving RAN node changes. Alternatively, SMF 166 directly queries the RAN node for its XRM service capabilities for PDU-set-based handling, for example, via the AMF using a Namf_N2InfoSubscribe message. In response, the RAN node sends the XRM service capabilities to the SMF via the AMF in a Namf_N2InfoNotify message. SMF 166 updates 1515c the RAN node with the QoS profile for the PDU session in the N2 PDU Session Request message and updates 1515d the UE with the QoS rules in the N1 PDU Session Accept Establishment message. The AMF 164 obtains 532 the XRM service capabilities of the RAN node from the RAN node 104 and sends 533 a notification to the SMF, for example in a Namf_EventExposure_Notify message including the XRM service capabilities of the RAN node. The SMF 166 performs 317 QoS flow binding and configures the UPF via the N4 interface to enable PDU set identification and marking.

[0098] The numerical adjectives "first," "second," and "third" do not imply any order (they are not ordinal numbers) but are labels used to distinguish different instances of similar elements. References to the singular (e.g., "a" or "an," "the") shall include the plural unless expressly indicated otherwise.

[0099] As used herein, a phrase referring to "at least one of" or "one or more of" a list of items refers to any combination of those items, including individual members. For example, "at least one of: a, b, or c" is intended to encompass the following possibilities: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c.

[0100] Although the features and elements of the present embodiments are described in particular combinations in the embodiments, each feature or element can be used alone without the other features and elements in the embodiments, or in various combinations with or without the other features and elements disclosed herein. The method or flow chart can be implemented as a computer program, software, or firmware tangibly embodied in a computer-readable storage medium for execution by a specially programmed computer or processor.

Claims

1. A wireless communication method for establishing an extended reality and / or media XRM service, performed by a core network CN element (110), the method comprising: Receiving (311) single network slice selection assistance information S-NSSAI or XRM capabilities for the XRM service of the UE (102) from a user equipment UE (102); Sending (315) a quality of service (QoS) parameter based on a packet data unit (PDU) set to a RAN access network (RAN) node (104); as well as A PDU set based handling corresponding to the PDU set QoS parameters is activated (317) at the user plane function UPF (166) for a PDU set based QoS flow of the PDU session associated with the network slice corresponding to the selected S-NSSAI.

2. The method of claim 1, wherein the sending further comprises: A QoS rule including QoS flow information related to the XRM service is sent to the UE.

3. The method according to any one of claims 1 or 2, further comprising, before the sending: selecting a Policy Control Function (PCF) for the PDU Session associated with the selected S-NSSAI, and A policy and charging control (PCC) rule including the PDU set-based QoS parameter is received from the PCF.

4. The method according to any one of claims 1 to 3, wherein the sending further comprises: Instruct the PSA UPF at the session management function SMF of the CN element to activate PDU set identification and marking for the PDU set-based QoS flow served by the PDU session associated with the selected S-NSSAI.

5. The method according to any one of claims 1 to 4, further comprising: receiving, at the authentication and mobility management (AMF) of the CN element, the UE XRM capability in one of: a registration request message, a PDU session establishment request message, or a PDU session modification request message; as well as One or more subscribed and / or authorized S-NSSAIs associated with the UE XRM capability are sent to the UE.

6. The method according to any one of claims 1 to 4, further comprising: receiving, at the authentication and mobility management (AMF) of the CN element, from the UE one of the following: a registration request message, a PDU session establishment request message, or a PDU session modification request message, none of which includes the UE XRM capability; as well as One or more subscribed and / or authorized S-NSSAIs are sent to the UE independent of the UE XRM capabilities.

7. The method according to any one of claims 1 to 6, further comprising: The XRM service capability of the RAN node for PDU set-based QoS handling is received at a session management function (SMF) or an access and mobility management function (AMF) performed by the CN element.

8. The method of any one of claims 1 to 7, further comprising: Receive the UE XRM service capability through the registration process, receiving a PDU session establishment request message or a PDU session modification request including the selected S-NSSAI, and Establish or modify the PDU session associated with the selected S-NSSAI.

9. A method as described in any one of claims 1 to 8, wherein the S-NSSAI includes a slice service type SST, the SST indicating a specific service associated with the network slice; and optionally includes a slice differentiator SD, the SD distinguishing different network slices; and for the XRM service, the SST is set to high data rate and low latency communication.

10. A wireless communication method for establishing an extended reality and / or media XRM service, performed by a user equipment UE (102), the method comprising: receiving (204) one or more subscribed and / or authorized single network slice selection assistance information S-NSSAI associated with UE XRM capabilities from a core network CN element (110); Activate (206) the XRM application; as well as A PDU session establishment or modification request message including an S-NSSAI selected from the one or more subscribed and / or authorized S-NSSAIs is sent (208) to the CN element (110) for the XRM application.

11. The method of claim 10, further comprising: PDU set based handling is enabled for the XRM application based on the selected S-NSSAI.

12. A method as described in any one of claims 10 or 11, wherein the selected S-NSSAI includes a slice service type SST, the SST indicating a specific service associated with the network slice; and optionally includes a slice differentiator SD, the SD distinguishing different network slices; and for the XRM service, the SST is set to high data rate and low latency communication.

13. A wireless communication method performed by a Radio Access Network (RAN) node (104) for providing PDU set-based Quality of Service (QoS) handling for extended reality and / or media (XRM) services, the method comprising: Sending (310a / b) single network slice selection assistance information S-NSSAI for the XRM service of the user equipment UE (102) to a core network CN element (110); receiving (315b) a packet data unit (PDU) session establishment or modification message from said CN element (110) including QoS flow information for said XRM service; as well as A PDU session response is sent (316a) to the CN element (110) indicating support for the XRM service.

14. The method of claim 13, further comprising: The QoS rules in the PDU session related message are forwarded from the CN element to the UE for instructing the UE to use the established PDU set based QoS flow for the XRM application in the uplink direction.

15. The method according to any one of claims 13 or 14, wherein the S-NSSAI is independent of UE XRM capabilities.

16. The method of any one of claims 13 to 15, further comprising: When the RAN node UE context stores the UE authorization for the XRM service, the RAN node XRM service capability is sent to the CN element through the PDU session establishment or modification procedure.

17. A wireless communication device (102, 104, 110) comprising a transceiver (134, 136, 146, 148, 154, 156), a processor (132, 146, 152), and a computer-readable storage medium (138, 148, 158) storing executable instructions for the processor to use the transceiver to perform any of the methods of claims 1-16.

Images