User equipment routing selection policy rule matching method and related user equipment

Abstract

A UE Routing Selection Policy (URSP) rule matching method and user equipment regarding S-NSSAI and PDU session type is proposed. When executing an application, the UE finds the RSD of the matching URSP rule, and the association of the application with an existing PDU session should have some exceptions. In one example, regarding S-NSSAI, if there is only one allowed S-NSSAI or the UE knows the default S-NSSAI, the UE can associate the PDU session with the application of an existing PDU session established through the S-NSSAI provided by the UE, but the RSD does not contain any S-NSSAI. In another example, regarding PDU session type, the PDU session type IPv4v6 in the RSD can match the PDU session type IPv4 or IPv6 of an existing PDU session that is established when the UE requests IPv4v6 during PDU session establishment.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority under 35 U.S.C. §119 to U.S. Provisional Application No. 63 / 200,228, filed on February 23, 2021, entitled “URSP Handling for S-NSSAI and PDU Types,” the subject matter of which is incorporated herein by reference. Technical Field

[0003] The disclosed embodiments relate generally to wireless communications, and more particularly to a method for processing UE route selection policy (URSP) regarding single-network slice selection assistance information (S-NSSAI) and protocol data unit (PDU) types in a 5G new radio (NR) system. Background Art

[0004] Wireless communication networks have grown exponentially over the years. Long-Term Evolution (LTE) systems offer high peak data rates, low latency, improved system capacity, and low operating costs due to simplified network architecture. LTE systems, also known as 4G systems, also provide seamless integration with older wireless networks such as GSM, CDMA, and Universal Mobile Telecommunication System (UMTS). In LTE systems, the evolved universal terrestrial radio access network (E-UTRAN) includes multiple evolved Node-Bs (eNode / eNB) that communicate with multiple mobile stations called user equipment (UE). The 3rd generation partner project (3GPP) network typically includes a mix of 2G / 3G / 4G systems. The Next Generation Mobile Network (NGMN) committee has decided to focus future NGMN activities on defining the end-to-end requirements for 5G New Radio Systems (5G NR systems, 5GS).

[0005] The UE policy of 5GS includes URSP and access network discovery and selection policy (ANDSP). UE policy can be passed to the UE from the Policy Control Function (PCF). PCF is responsible for managing network policies for network behavior. PCF obtains subscription information from the Unified Data Management (UDM). PCF interfaces with the Access and Mobility Function (AMF) to manage mobile context and the Session Management Function (SMF) to manage session context. PCF also plays a vital role in providing patterns for network slicing and roaming. The PCF triggers the URSP, enabling the UE to determine how a certain application should be handled in the context of an existing or new (PDU) session. UE policies can also be pre-configured in the UE. The UE should apply a pre-configured policy only if it has not received a policy of the same type from the PCF.

[0006] A PDU session defines the association between a UE and a data network that provides PDU connection services. Each PDU session is identified by a PDU session ID and includes one or more QoS flows and QoS rules. When an application is executed, the upper layer sends the application information to the URSP entity to match the URSP rules (i.e., by evaluating the traffic descriptor (TD)) and establishes a PDU session using the corresponding route selection descriptor (RSD). The UE attempts to reuse an existing PDU session. Otherwise, duplicate PDU sessions may occur; or the network may reject the PDU session establishment request, which results in signaling overhead; or the UE may select the next RSD or URSP that may not be the most suitable for the application.

[0007] Seek solutions. Summary of the Invention

[0008] A URSP rule matching method regarding S-NSSAI and PDU session type and related user equipment are proposed. When executing an application, the UE upper layer sends application information to the URSP entity for matching the URSP rule. The UE finds an RSD that matches the URSP rule, and the UE attempts to reuse an existing PDU session, for example, there are certain exceptions to the association of the application with the existing PDU session. In one example, regarding S-NSSAI, if there is only one allowed S-NSSAI or the UE knows the default S-NSSAI, the UE can associate the PDU session with the application of the existing PDU session established through the S-NSSAI provided by the UE, but the RSD does not contain any S-NSSAI. In another example, regarding the PDU session type, the PDU session type IPv4v6 in the RSD can match the PDU session type IPv4 or PDU session type IPv6 of an existing PDU session, which is established when the UE requests IPv4v6 during PDU session establishment.

[0009] According to the user equipment routing policy rule matching method and user equipment provided by the present invention, when there are one or more PDU sessions that meet certain conditions / exceptions, the appropriate RSD can be matched to the upper-layer information about the PDU session, avoiding the establishment of repeated and redundant PDU sessions and avoiding unnecessary exception processing, even if certain parameters of the PDU session do not completely match the RSD of the matching URSP rule.

[0010] Other embodiments and advantages are described in the detailed description that follows. This summary is not intended to define the invention. The invention is defined by the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, wherein like numerals represent like components, illustrate embodiments of the present invention.

[0012] Figure 1 An exemplary 5G network supporting URSP processing for S-NSSAI and PDU session types in a 5G NR system is illustrated in accordance with one novel aspect.

[0013] Figure 2 A simplified block diagram of a UE and a base station according to an embodiment of the present invention is shown.

[0014] Figure 3 The contents of the URSP rules defined in the 3GPP specification are shown.

[0015] Figure 4 Different layers within a UE are shown for supporting URSP processing with respect to S-NSSAI and PDU types according to one novel aspect of the present invention.

[0016] Figure 5 A sequence flow between a UE and a network for URSP processing with respect to S-NSSAI and PDU types according to one novel aspect of the present invention is shown.

[0017] Figure 6 is a flowchart of a method for enhancing URSP rule matching exceptions on PDU session type according to one novel aspect of the present invention.

[0018] Figure 7 is a flowchart of a method for enhancing URSP rule matching exceptions on S-NSSAI according to one novel aspect of the present invention. DETAILED DESCRIPTION

[0019] Reference will now be made in detail to some embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

[0020] Figure 1 An exemplary 5G network 100 is illustrated that supports enhanced URSP processing for S-NSSAI and PDU session types in a 5G NR system according to one novel aspect. The 5G NR network 100 includes a user equipment UE 101, a base station gNB 102, an access and mobility management function (AMF) 103, a session management function (SMF) 104, a policy control function (PCF) 105, and a unified data management (UDM) 106. Figure 1 In the example shown in Figure 1, UE 101 and its serving base station, gNB 102, are part of a radio access network (RAN) 120. In the access stratum (AS) layer, RAN 120 provides radio access for UE 101 via a radio access technology (RAT). In the non-access stratum (NAS) layer, AMF 103 communicates with gNB 102 and 5GC 104 to manage access and mobility for radio access devices in 5G network 100. UE 101 can be equipped with a radio frequency (RF) transceiver or multiple RF transceivers to provide different application services over different RATs / CNs. UE 101 can be a smartphone, wearable device, Internet of Things (IoT) device, tablet, etc.

[0021] The 5GS network is a packet-switched (PS) Internet Protocol (IP) network. This means that the network transmits all data traffic in the form of IP packets and provides users with always-on IP connectivity. When a UE joins a 5GS network, a packet data network (PDN) address (i.e., an address that can be used on a PDN) is assigned to the UE to connect to the PDN. In 4G, EPS defines a default EPS bearer to provide always-on IP connectivity. In 5G, the PDU session establishment process is a parallel process to the PDN connection process in 4G. A PDU session (e.g., 130) defines an association between a UE and a data network that provides PDU connection services. Each PDU session is identified by a PDU session ID and may include multiple QoS flows and QoS rules.

[0022] The UE policy of 5GS includes URSP and access network discovery and selection policy (ANDSP). UE policy can be passed to the UE from the PCF. PCF is responsible for managing network policy for network behavior. PCF obtains subscription information from Unified Data Management (UDM). PCF interfaces with AMF to manage mobile context and with SMF to manage session context. PCF also plays a vital role in providing network slicing and roaming solutions. PCF triggers URSP, enabling the UE to determine how a certain application should be handled in the context of an existing or new PDU session. UE policies can also be pre-configured in the UE. The UE should apply a pre-configured policy only if it has not received a policy of the same type from the PCF.

[0023] When the UE 101 starts the application 140, the UE upper layer triggers URSP rule matching. The UE 101 evaluates the URSP rules except the default URSP rule in ascending order of their priority values ​​by matching the traffic descriptors of the application information. If the UE 101 finds that the traffic descriptor (141) in the non-default URSP rule (142) matches the application information and the established PDU session matches at least one of the routing descriptors (143) of the URSP rule, the UE then provides information about matching the routing descriptor with the lowest priority value to the upper layer. Otherwise, the UE selects the routing descriptor with the next lowest priority value that has not been evaluated. If no non-default matching URSP rule is found and if the UE local configuration of the application is available, the UE 101 should perform the association of the application with the PDU session accordingly. If there is no matching PDU session, the UE NAS layer should try to establish the PDU session 144 using the UE local configuration. If the PDU session establishment is successful (145), the UE NAS layer should provide information about the successfully established PDU session to the upper layer. Otherwise, if no non-default matching URSP rule is found and the UE local configuration for the application is not available or the PDU session establishment based on the UE local configuration for the application fails (146), then the UE 101 shall perform association of the application with the PDU session or with the non-seamless non-3GPP offload according to the default URSP rule with the "all match" traffic descriptor (150). If the association is unsuccessful, the UE 101 notifies the upper layers.

[0024] UE 101 attempts to reuse an existing PDU session (160) when an application is executed and the upper layer sends application information to the URSP entity to match the URSP rules. Otherwise, duplicate PDU sessions may occur; or the network may reject the PDU session establishment request, which results in signaling overhead; or the UE may select the next RSD or URSP, which may not be the best fit for the application. In a novel aspect, when an application is executed, the UE finds an RSD that matches the URSP rules, and the association of the application with the existing PDU session should have certain exceptions. Generally speaking, the existing PDU session should have parameters that match the RSD that matches the URSP rules; however, in exceptional cases, the PDU session can be associated with the application even if there is no exact match. In one example, with respect to S-NSSAI, if there is only one allowed S-NSSAI or the UE knows the default S-NSSAI, the UE can associate the PDU session with the application of the existing PDU session established with the S-NSSAI provided by the UE, but the RSD does not contain any S-NSSAI (other parameters are the same). In another example, regarding the PDU session type, the PDU session type IPv4v6 in the RSD may match the PDU session type IPv4 or PDU session type IPv6 of a PDU session established when the UE requests IPv4v6 during PDU session establishment.

[0025] Figure 2 A simplified block diagram of a wireless device (e.g., UE 201 and network entity 211) according to an embodiment of the present invention is shown. The network entity 211 can be a base station combined with an MME or an AMF. The network entity 211 has an antenna 215 for transmitting and receiving radio signals. A radio frequency (RF) transceiver module 214 coupled to the antenna receives RF signals from the antenna 215, converts them into baseband signals, and sends the baseband signals to the processor 213. The RF transceiver 214 also converts the baseband signals received from the processor 213, converts them into RF signals, and sends them to the antenna 215. The processor 213 processes the received baseband signals and calls different functional modules to perform functions in the base station 211. The memory 212 includes volatile computer-readable storage media and non-volatile computer-readable storage media, storing program instructions and data 220 to control the operation of the base station 211. In Figure 2 In the example shown, network entity 211 also includes a protocol stack 280 and a set of control function modules and circuits 290. PDU session processing circuitry 231 handles PDU session establishment and modification. Policy control circuitry 232 configures policy rules for the UE. Configuration and control circuitry 233 provides various parameters to configure and control UE-related functions, including mobility management and session management.

[0026] Similarly, UE 201 has a memory 202, a processor 203, and an RF transceiver module 204. RF transceiver 204 is coupled to antenna 205, receives RF signals from antenna 205, converts them into baseband signals, and transmits the baseband signals to processor 203. RF transceiver 204 also converts baseband signals received from processor 203, converts them into RF signals, and transmits them to antenna 205. Processor 203 processes the received baseband signals and invokes various functional modules and circuits to perform functions in UE 201. Memory 202 includes volatile computer-readable storage media and non-volatile computer-readable storage media, and stores data and program instructions 210 to be executed by the processor to control the operation of UE 201. Suitable processors include, for example, a dedicated processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a file programmable gate array (FPGA) circuit, and other types of integrated circuits (ICs) and / or state machines. The processor, in association with software, may be used to implement and configure features of the UE 201.

[0027] UE 201 also includes a set of functional modules and control circuits to perform the functional tasks of UE 201. The protocol stack 260 includes an application layer and other upper layers to manage different applications, a NAS layer to communicate with the AMF entity connected to the core network, a Radio Resource Control (RRC) layer for high-level configuration and control, a Packet Data Convergence Protocol / Radio Link Control (PDCP / RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer. The system modules and circuits 270 can be implemented and configured by software, firmware, hardware, and / or a combination thereof. The functional modules and circuits cooperate with each other when executed by the processor through program instructions contained in the memory to allow UE 201 to perform embodiments and functional tasks and features in the network. In one example, an upper layer entity requests information of a PDU session through which PDUs of an application are sent, and the system module and circuit 270 includes a PDU session processing circuit 221 that performs PDU session establishment and modification procedures with a network, a URSP rule matching circuit 222 that performs URSP rule matching, and a configuration and control circuit 223 that processes configuration and control parameters for mobility management and session management.

[0028] Figure 3The diagram illustrates the contents of the URSP rules defined in the 3GPP specification. A URSP is defined as a set of one or more URSP rules. As shown in Table 300, each URSP rule consists of the following components: 1) a priority value for the URSP rule, which identifies the priority of the URSP rule among all existing URSP rules; 2) a traffic descriptor; and 3) one or more routing descriptors. The traffic descriptor includes 1) matching all traffic descriptors; or 2) at least one of the following components: A) one or more application identifiers; b) one or more IP 3-tuples, i.e., destination IP address, destination port number, and protocol used on IP; c) one or more non-IP descriptors, i.e., destination information for non-IP traffic; D) one or more DNNs; e) one or more connection capabilities; and F) one or more domain descriptors, i.e., one or more target FQDNs. Each routing descriptor includes a routing descriptor priority value and 1) a PDU session type, and optionally one or more of the following: A) SSC mode; B) one or more S-NSSAIs; C) one or more DNNs; D) preferred access type; E) multiple access preference; or 2) a non-seamless non-3GPP offload indication. Only one URSP rule in a URSP can be the default URSP rule, and the default URSP rule should include matching all traffic descriptors. If a URSP includes a default URSP rule and one or more non-default URSP rules, any non-default URSP rule should have a lower priority value (i.e., a higher priority) than the default URSP rule.

[0029] Figure 4 The diagram illustrates different layers within a UE for supporting URSP processing regarding S-NSSAI and PDU types according to a novel aspect of the present invention. The UE uses the URSP to determine whether a detected application can be associated with an established PDU session, whether it can be offloaded to a non-3GPP access outside of a PDU session, or whether the establishment of a new PDU session can be triggered. The URSP rule includes a traffic descriptor that specifies matching criteria and one or more of the following components: an SSC mode selection policy that associates the matching application with an SSC mode, a network slice selection policy that associates the matching application with an S-NSSAI, a DNN selection policy that associates the matching application with a DNN, a PDU session type policy that associates the matching application with a PDU session type, a non-seamless offload policy that determines that the matching application should be non-seamlessly offloaded to a non-3GPP access (i.e., output of a PDU session), and an access type preference that indicates the preferred access (3GPP or non-3GPP) when the UE needs to establish a new PDU session for the matching application.

[0030] In order to send the PDUs of the application, the upper layer requests information about the PDU session through which the PDUs of the application are sent (e.g., PDU address). When the upper layer requests information about the PDU session through which the application PDUs are sent, if non-seamless non-3GPP offload is requested due to the request for UE local configuration, information about non-3GPP access outside the PDU session should be provided to the upper layer without evaluating the URSP rules. Otherwise, the UE should proceed in the following order.

[0031] In the first step (410), the UE shall evaluate the URSP rules (if any) other than the default URSP rule through the traffic descriptor, which is matched to the application information in ascending order of the priority value of the URSP. If the traffic descriptor contains more than one traffic descriptor component type, each of a different type, all of them shall be matched. If the traffic descriptor contains multiple traffic descriptor components of the same traffic descriptor component type, at least one traffic descriptor component of the same traffic descriptor component type shall match the application information. When no corresponding information from the application is available for any given component in the traffic descriptor or the corresponding information from the application does not match any value in the traffic descriptor component, the URSP rule is determined to be not applicable. If the UE finds a traffic descriptor in the non-default URSP rule that matches the application information, the UE shall provide non-3GPP access information other than the PDU session to the upper layer, and if certain conditions are met, the UE shall provide information about the PDU session that matches the routing descriptor with the lowest priority value to the upper layer.

[0032] In the second step (420), if no non-default matching URSP rule is found and if the UE local configuration of the application is available, the UE will perform the association of the application with the PDU session accordingly. If there is no matching PDU session, the UE NAS layer will attempt to establish the PDU session using the UE local configuration. If the PDU session is successfully established, the UE NAS layer will provide the upper layer with information of the successfully established PDU session (e.g., PDU address). Otherwise, the UE enters the third step (430), if no non-default matching URSP rule is found and the UE local configuration of the application is not available or the PDU session establishment based on the UE local configuration of the application is unsuccessful, the UE shall perform the association of the application with the PDU session or with the non-seamless non-3GPP offload according to the default URSP rule through the "match-all" traffic descriptor (if any). If the association is unsuccessful, the UE will notify the upper layer of the failure.

[0033] During the first step (410) of the URSP rule evaluation, if the UE finds a traffic descriptor in a non-default URSP rule that matches the application information, and if at least one routing descriptor of the URSP rule contains a non-seamless non-3GPP offload indication and information about non-3GPP access outside the PDU session is available, the UE shall provide information about non-3GPP access outside the PDU session to the upper layer. In addition, if the UE finds a traffic descriptor in the non-default URSP rule that matches the application information, and if there are one or more PDU sessions that meet certain exceptions or conditions, the UE shall provide information about the PDU session that matches the routing descriptor with the lowest priority value to the upper layer. Here, when the PDU session parameters are the same as the RSD descriptor components, the PDU session matches the RSD.

[0034] The first exception / condition is that one or more PDU sessions match at least one of the routing descriptors of the URSP rule, except for the preferred access type and the multiple access preference, if any, wherein a routing descriptor with PDU session type IPv4v6 also matches PDU session type IPv4 if the network sent a 5GSM cause value #50 “PDU session type IPv4 only allowed” in the PDU SESSION ESTABLISHMENT ACCEPT message, and a routing descriptor with PDU session type IPv4v6 also matches PDU session type IPv6 if the network sent a 5GSM cause value #51 “PDU session type IPv6 only allowed” in the PDU SESSION ESTABLISHMENT ACCEPT message, and if the UE requested PDU session type IPv4v6 but did not send a 5GSM cause value #52 “PDU session type IPv6 only allowed” in the PDU SESSION ESTABLISHMENT ACCEPT message. ACCEPT message is set to IPv4 or IPv6, then the routing descriptor with PDU session type IPv4v6 also matches the PDU session type IPv6 or IPv4.

[0035] The second exception / condition is: one or more PDU sessions are established without requesting a URSP rule whose matching routing descriptor does not provide any parameters of the routing descriptor components, except for A) preferred access type; B) multiple access preference; C) DNN, if one or more DNNs are included in the traffic descriptor and the DNN provided by the application is the same as the DNN requested by the UE during PDU session establishment; and D) S-NSSAI, if the UE has only one S-NSSAI among the allowed NSSAIs. In other words, the matching RSD includes a set of RSD descriptor components, and the existing PDU session was established with a set of parameters requested by the UE. The requested set of parameters is a subset of the set of RSD descriptor components of the matching RSD, with the exceptions of A), B), C), and D). For example, under exception D), if the existing PDU session was established with an S-NSSAI and a set of parameters provided by the UE. If an application matches a URSP rule where the application's RSD only includes a set of parameters (without an S-NSSAI), then the application should be associated with the existing PDU session.

[0036] Figure 5The diagram illustrates a sequence flow for URSP rule matching between a UE and a network according to a novel aspect of the present invention. In step 510, the network 502 (via the PCF) provides a URSP configuration or update to the UE 501. The URSP includes a set of URSP rules, including a default URSP rule. In step 511, the UE 501 and the network 502 establish one or more PDU sessions, each of which includes information such as a service NSSAI, a DNN, and a PDU session ID. In step 512, the upper layers of the UE 501 request PDU session information, for example, triggered by launching an application. In other words, the UE's upper layers request information about the PDU session over which the application's PDUs are sent. To determine the association between the application and the PDU session or non-seamless non-3GPP offload, the UE's upper layers proceed with URSP rule matching in step 513. In step 520, the UE 501 attempts all non-default URSP rules in ascending order of priority. Specifically, in step 521, UE 501 selects a matching URSP rule and then either locates an existing PDU session or establishes a new PDU session that matches at least one of the routing descriptors of the selected URSP rule. If no matching PDU session exists, the UE NAS layer attempts to establish a new PDU session. For example, in step 522, UE 501 sends a PDU session establishment request to the network. In step 523, the network sends a PDU session establishment accept to UE 501, and the PDU session establishment is successful. Otherwise, the network sends a PDU session establishment reject to UE 501, and the PDU session is not established. After step 520, if all non-default URSP rules fail to match the application, in step 531, UE 501 attempts the default URSP rule, which includes matching all traffic descriptors. If the association is still unsuccessful, UE 501 notifies the upper layer of the failure.

[0037] In step 521, the UE 501 attempts to reuse an existing PDU Session. For example, the association of an application with an existing PDU Session should be based on a match between the PDU Session and the RSD / URSP, but with some exceptions. Otherwise, duplicate PDU Sessions may occur; or the network may reject the PDU Session establishment request, which causes signaling overhead; or the UE may select the next RSD or URSP, which may not be the most suitable for the application. Specifically, if the UE 501 finds a traffic descriptor that matches the application information in a non-default URSP rule, and if there are one or more PDU Sessions that meet certain conditions / exceptions, the UE should provide information about the PDU Session that matches the RSD with the lowest priority value to the upper layer, even if some parameters of the PDU Session do not completely match the RSD of the matching URSP rule.

[0038] In one embodiment, there may be exceptions to the PDU type based on the application's requirement to associate with an existing PDU session. This is because the network can also change the PDU session type = IPv4v6 request to IPv4 or IPv6 without indicating a 5GSM reason (i.e., #50 "PDU session type IPv4 only allowed" or #51 "PDU session type IPv6 only allowed"). For example, it is possible that: 1) when the UE requests to establish an IPv4v6 PDU session, there is no indication of IPv4 PDU session establishment #50 / #51; 2) when the UE requests to establish an IPv4v6 PDU session, there is no indication of IPv6 PDU session establishment #50 / #51; 3) when the UE initially requests to establish a single IPv4v6 PDU session, an IPv4 PDU session and another IPv6 PDU session are established, but there is no indication #50#51. Therefore, the exception handling for URSP PDU Session Association shall include that if the UE requests PDU Session Type IPv4v6 but the selected PDU Session Type is set by the network to IPv4 or IPv6 in the PDU Session Setup Accept message, then a Routing Descriptor with PDU Session Type IPv4v6 also matches PDU Session Type IPv6 or IPv4.

[0039] In another embodiment, the UE has only one S-NSSAI among the allowed NSSAIs, or the UE knows the default S-NSSAI. It is assumed that there is an existing PDU Session established with an S-NSSAI and a set of parameters provided by the UE. If a new application is executed and the new application matches a URSP rule where the RSD only includes a set of parameters without the S-NSSAI, for example, the other parameters are exactly the same as the set of parameters provided for the established PDU Session (i.e., the only difference is that the S-NSSAI was provided when the original PDU Session was established), then the application should associate with the existing PDU Session (i.e., without checking whether the S-NSSAI was provided) as long as the other parameters are the same.

[0040] Figure 66 is a flowchart of a method for enhancing URSP rule matching with exceptions on PDU session type according to a novel aspect of the present invention. In step 601, the UE receives a request for PDU session information of the UE in a mobile communication network from an upper layer. For example, the upper layer requests information of a PDU session through which the PDU of an application is sent. In step 602, the UE selects a URSP rule from one or more configured URSP rules. The traffic descriptor of the selected URSP rule matches the application. In step 603, the UE obtains a PDU session matching the RSD from the RSD list of the selected URSP rule. The RSD has a first PDU session type, and the PDU session has a second PDU session type different from the first PDU session type. In step 604, the UE associates the PDU session with the application and provides the PDU session information to the upper layer.

[0041] Figure 7 7 is a flowchart of a method for enhancing URSP rule matching exceptions on S-NSSAI according to a novel aspect of the present invention. In step 701, the UE receives a request from an upper layer for PDU session information of the UE in a mobile communication network. For example, the upper layer requests information of a PDU session through which the PDU of an application is sent. In step 702, the UE selects a URSP rule from one or more configured URSP rules. The traffic descriptor of the selected URSP rule matches the application. In step 703, the UE obtains a PDU session that matches the RSD from the RSD list of the selected URSP rule. The PDU session is established using a set of requested parameters that are a subset of a set of RSD descriptor components of the matching RSD, but with exception conditions regarding the S-NSSAI. In step 704, the UE associates the PDU session with the application and provides the PDU session information to the upper layer.

[0042] Although the present invention has been described in conjunction with certain specific embodiments for guiding purposes, it is not limited thereto. Therefore, various modifications, amendments and combinations of the various features of the described embodiments may be implemented without departing from the scope of the invention as set forth in the claims.

Claims

1. A method for matching user equipment routing policy rules, comprising: receiving, in a mobile communication network, a request from an upper layer for protocol data unit session information of a user equipment; selecting a user equipment routing policy rule from one or more configured user equipment routing policy rules, wherein a traffic descriptor of the selected user equipment routing policy rule matches an application; obtaining a protocol data unit session matching a routing descriptor from a routing descriptor list of the selected user equipment routing policy rule, wherein the routing descriptor has a first protocol data unit session type set to IPv4v6, and wherein the protocol data unit session has a second protocol data unit session type set to IPv6 or IPv4 in a protocol data unit session setup accept message from the network; as well as The protocol data unit session is associated with the application, and the protocol data unit session information is provided to the upper layer.

2. A method for matching user equipment routing policy rules, comprising: receiving, in a mobile communication network, a request from an upper layer for protocol data unit session information of a user equipment; selecting a user equipment routing policy rule from one or more configured user equipment routing policy rules, wherein a traffic descriptor of the selected user equipment routing policy rule matches an application; obtaining, from a routing descriptor list of the selected user equipment routing policy rule, a protocol data unit session matching a routing descriptor, wherein the user equipment has only one allowed single network slice selection assistance information in an allowed network slice selection assistance information list, the protocol data unit session being established using the allowed single network slice selection assistance information, and wherein the matching routing descriptor does not have the single network slice selection assistance information; as well as The protocol data unit session is associated with the application, and the protocol data unit session information is provided to the upper layer.

3. The method according to claim 2, characterized in that The set of routing descriptor components of the matching routing descriptor is identical to the set of requested parameters of the protocol data unit session minus the single network slice selection assistance information.

4. A user equipment for user equipment routing selection policy rule matching, comprising: an upper layer entity for requesting protocol data unit session information, wherein the upper layer entity triggers a user equipment routing policy rule match of the application; a user equipment routing policy rule matching circuit for selecting a user equipment routing policy rule from one or more configured user equipment routing policy rules, wherein a traffic descriptor of the selected user equipment routing policy rule matches the application; a protocol data unit session processing circuit configured to obtain a protocol data unit session matching a routing descriptor from a routing descriptor list of the selected user equipment routing policy rule, wherein the routing descriptor has a first protocol data unit session type set to IPv4v6, and wherein the protocol data unit session has a second protocol data unit session type set to IPv6 or IPv4 in a protocol data unit session setup accept message from the network; as well as The control circuit is configured to associate the protocol data unit session with the application and provide the protocol data unit session information to the upper layer.

5. A user equipment for user equipment routing selection policy rule matching, comprising: A processor is coupled to a memory, wherein the memory stores data and program instructions, and when the data and program instructions are executed by the processor of the user equipment, the user equipment executes the method as described in any one of claims 1 to 3 above.

6. A non-volatile computer-readable storage medium storing data and program instructions, which, when executed by a processor of a user equipment matching a user equipment routing policy rule, causes the user equipment to execute the method according to any one of claims 1 to 3.

Images