Method and user equipment for wireless communication

Abstract

One aspect of the present disclosure provides a method for wireless communication. A UE can initiate a URSP rule matching procedure in a mobile communication network. The UE can select a URSP rule from one or more URSP rules. In step 602, the UE can match a traffic descriptor of the selected URSP rule with application information. In step 603, the UE can select and evaluate an RSD from an RSD list of the selected URSP rule to match with a PDU session. The RSD can have an RSD component list, which can contain a PDU session pair ID or RSN. In step 604, the UE can ignore the RSD when it is determined that the RSD further contains a preferred access type set to non-3GPP access, or the UE can ignore the RSD when it is determined that the RSD further contains a multi-access preferred type. By utilizing the present disclosure, wireless communication can be better.

Description

Technical Field

[0001] This invention relates to wireless communication, and more particularly to communication for fifth-generation (5G) wireless communication. th Improvement method for User Equipment (UE) Route Selection Policy (URSP) process in redundant Protocol Data Unit (PDU) sessions in 5G (5G System, 5GS). Background Technology

[0002] In recent years, wireless communication networks have experienced exponential growth. Long-Term Evolution (LTE) systems offer high peak data rates, low latency, higher system capacity, and lower operating costs due to a simplified network architecture. LTE systems (also known as fourth-generation)... th Generation 4G systems can also provide seamless integration with legacy wireless networks such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), and Universal Mobile Telecommunications System (UMTS). In LTE systems, the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) includes multiple evolved Node-Bs (eNodeBs or eNBs) communicating with multiple mobile stations (UEs). Third-generation partner project (3GPP) networks typically include second-generation (2G) networks. nd Generation (2G) / Third Generation (3G) rd The hybrid of 3G and 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 (NR) systems (5GS).

[0003] UE policies for 5GS include URSP and Access Network Discovery and Selection Policy (ANDSP). UE policies can be delivered to the UE from a Policy Control Function (PCF). The PCF is responsible for network policies for managing network behavior. The PCF obtains subscription information from a Unified Data Management (UDM). The PCF interfaces with an Access and Mobility Function (AMF) to manage mobility context and with a Session Management Function (SMF) to manage session context. The PCF also plays a vital role in providing network slicing and roaming scenarios. The PCF can trigger URSP to enable the UE to determine how to handle a particular application in the context of an existing or new PDU session. UE policies can also be pre-configured in the UE. The UE can apply pre-configured policies (stored in a Universal Subscriber Identity Module (USIM) or Non-Volatile Random-Access Memory (NVRAM)) when the UE does not receive the same type of policy from the PCF.

[0004] A PDU session can define an association between a UE and a data network offering PDU connectivity service. Each PDU session can be identified by a PDU session Identity (ID) and can include one or more Quality of Service (QoS) flows and QoS rules. When an application is executed, an upper layer can send application information to a URSP entity to match URSP rules (i.e., matching by evaluating Traffic Descriptor (TD)) and use a corresponding Route Selection Descriptor (RSD) to associate with an existing PDU session or establish a new PDU session. If the characteristics of the RSD match the characteristics of an existing PDU session, the UE can attempt to reuse the existing PDU session.

[0005] The concept of a "redundant PDU session" has been introduced for Ultra-Reliable and Low-Latency Communication (URLLC) applications. The 5G Session Management (5GSM) sublayer supports the establishment of redundant PDU sessions. To establish a set of two redundant PDU sessions, the UE can include a PDU session pair ID, a Redundancy Sequence Number (RSN), or both in the PDU session establishment request message for each PDU session in the two redundant PDU sessions. The UE can set the PDU session pair ID, RSN, or both based on the URSP or its local configuration. Furthermore, even if the UE neither provides a PDU session pair ID nor an RSN for each PDU session in the PDU session establishment request message, the SMF can still treat the two PDU sessions as redundant.

[0006] To ensure reliability and low latency, redundant PDU sessions are established via 3GPP access. Furthermore, because Multi-Access (MA) PDU sessions imply data can be transmitted via non-3GPP access, MA PDU sessions are excluded. During upper-layer triggered URSP rule matching, if the routing descriptor contains a "PDU session pair ID type" or "RSN type" routing descriptor component, and the same routing descriptor also contains a "multi-access preference type" descriptor component, the UE's behavior is undefined. Additionally, if the routing descriptor contains a "PDU session pair ID type" or "RSN type" routing descriptor component, and the same routing descriptor also contains a "preferred access type" descriptor component set to "non-3GPP access," the UE's behavior is undefined.

[0007] Solutions need to be found to prevent the UE from: (1) establishing redundant PDU sessions over non-3GPP access, or (2) establishing redundant MA PDU sessions (the network cannot properly handle URLLC application packets sent over non-3GPP access, so sending such packets over non-3GPP can encounter unexpected results). Otherwise, the UE and the network either (1) need to handle redundant PDU sessions established over non-3GPP access, or handle redundant MA PDU sessions established with non-3GPP access legs, or (2) cannot establish redundant PDU sessions or cannot establish redundant MA PDU sessions over non-3GPP access; time is wasted due to network rejections, so user experience is degraded when the user uses an application that relies on redundant PDU sessions. SUMMARY

[0008] The present disclosure proposes a method for URSP rule matching for redundant PDU sessions. When an application is executed, an upper layer of a UE can send application information to a URSP entity for matching URSP rules. The UE can select and evaluate a RSD from a RSD list of a selected URSP rule to match a PDU session. If a "PDU session pair ID type" or "RSN type" routing selection descriptor component exists in one RSD, but a "Multiple access preferred type" descriptor component or a "Preferred access type" descriptor component set to "non-3GPP access" also exists in the same RSD, the UE can ignore the RSD since the RSD is not valid for redundant PDU sessions.

[0009] A method for wireless communication includes initiating, by a user equipment, a user equipment routing selection policy rule matching procedure in a mobile communication network, wherein the user equipment selects a user equipment routing selection policy rule from one or more user equipment routing selection policy rules; matching a traffic descriptor of the selected user equipment routing selection policy rule with application information; selecting and evaluating a routing selection descriptor from a routing selection descriptor list of the selected user equipment routing selection policy rule to match a protocol data unit session, wherein the routing selection descriptor has a routing selection descriptor component list including a protocol data unit session pair identification or a redundant sequence number; and ignoring the routing selection descriptor when it is determined that a preferred access type set to non-third generation partnership project access also exists in the routing selection descriptor, or ignoring the routing selection descriptor when it is determined that a multiple access preferred type also exists in the routing selection descriptor.

[0010] A user equipment for wireless communication, comprising: upper layer processing circuitry to initiate a user equipment route selection policy rule matching procedure in a mobile communication network, wherein the user equipment selects a user equipment route selection policy rule from one or more user equipment route selection policy rules; user equipment route selection policy processing circuitry to match a traffic descriptor of the selected user equipment route selection policy rule with application information, wherein the user equipment selects and evaluates a route selection descriptor from a list of route selection descriptors of the selected user equipment route selection policy rule to match with a protocol data unit session; and control circuitry to determine that the route selection descriptor has a list of route selection descriptor components that includes a protocol data unit session pair identification or a redundant sequence number, wherein the user equipment ignores the route selection descriptor when it is determined that the route selection descriptor further includes a preferred access type set to non-3rd generation partnership project access or the user equipment ignores the route selection descriptor when it is determined that the route selection descriptor further includes a multiple access preferred type.

[0011] By utilizing the present application, wireless communication can be better performed.

[0012] Other embodiments and advantages will be described in the following detailed description of the application. This summary is not intended to define the application. The application is defined by the claims. BRIEF DESCRIPTION OF DRAWINGS

[0013] The accompanying drawings illustrate embodiments of the application, wherein like numbers refer to like components.

[0014] Figure 1 An exemplary 5G network can be illustrated that utilizes improvements in URSP handling according to novel aspects of redundant PDU session in 5G NR systems.

[0015] Figure 2 A simplified block diagram of a UE and base station according to embodiments of the application can be illustrated.

[0016] Figure 3 The contents of URSP rules as defined by 3GPP specifications and parameters for improved URSP rule matching can be illustrated.

[0017] Figure 4 Examples of URSP rule matching for an application can be illustrated where RSDs of selected URSP rules are ignored to support redundant PDU sessions.

[0018] Figure 5 A timing diagram illustrating improved URSP rule matching between a UE and network for redundant PDU sessions according to novel aspects of the application can be illustrated.

[0019] Figure 6 is a flowchart of an improved URSP rule matching method according to the novel aspect of the present application. DETAILED DESCRIPTION

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

[0021] Figure 1 An exemplary 5G network 100 that utilizes the improvements in redundant PDU session in 5G NR system to support URSP processing according to the novel aspect can be illustrated. The 5G NR network 100 can include a UE 101, a base station gNB 102, an AMF 103, an SMF 104, a PCF 105, and a UDM 106. In Figure 1 In an example, the UE 101 and its serving base station gNB 102 can belong to a part of a Radio Access Network (RAN) 120. In the Access Stratum (AS), the RAN 120 can provide radio access for the UE 101 via a Radio Access Technology (RAT). In the Non-Access Stratum (NAS), the AMF 103 can communicate with the gNB 102 and the 5GC to perform access and mobility management for the wireless access devices in the 5G network 100. The UE 101 can be equipped with one or more Radio Frequency (RF) transceivers for different application services through different RATs / core networks. The UE 101 can be a smartphone, a wearable device, an Internet of Things (IoT) device, a tablet, and the like.

[0022] A 5GS network can be a packet-switched (PS) Internet Protocol (IP) network. This means that the network can deliver data traffic in the form of IP packets and provide users with an Always-On IP connection. When a UE joins a 5GS network, the UE can be allocated a Packet Data Network (PDN) address (i.e., an address that can be used on a PDN) to connect to a PDN. In 4G, the EPS can define a default EPS bearer to provide the Always-On IP connection. In 5G, a Protocol Data Unit (PDU) session establishment procedure can be a parallel procedure to the PDN connection procedure in 4G. A PDU session (such as 130) can define an association between a UE and a data network that provides PDU connectivity services. Each PDU session can be identified by a PDU session ID, and can include multiple QoS flows and QoS rules.

[0023] UE policies for 5GS can include URSP and ANDSP. UE policies can be delivered to the UE from a PCF. The PCF can be responsible for network policies for managing network behavior. The PCF can obtain subscription information from a UDM. The PCF can interact with an AMF to manage mobility context and with an SMF to manage session context. The PCF also plays a vital role in providing network slicing and roaming solutions. The PCF can provide URSP to enable the UE to determine how to handle a particular application in the context of an existing or new PDU session. UE policies can also be pre-configured in the UE (stored in USIM or NVRAM). The UE can apply the pre-configured policies when the UE does not receive the same type of policy from the PCF.

[0024] When the UE 101 starts an application 140, the UE upper layers can trigger URSP rule matching. The UE 101 can evaluate URSP rules (except for the default URSP rule) in order of precedence value by matching traffic descriptors with application information. If the UE 101 finds a traffic descriptor (141) in a non-default URSP rule (142) that matches the application information and an established PDU session matches at least one RSD (143) of the URSP rule, the UE can provide information related to the PDU session matched by the matching RSD with the lowest precedence value to the upper layers. Otherwise, the UE can select the next RSD with the lowest precedence value that has not been evaluated. If no matching non-default URSP rule is found, but a local configuration of the UE for the application is available, the UE 101 can associate the application with a PDU session accordingly.

[0025] If there is no matching PDU session, the UE's NAS layer can attempt to establish a PDU session 144. If the PDU session establishment is successful (145), the UE's NAS layer can provide the information of the successfully established PDU session to the upper layer. Otherwise, if no matching non-default URSP rule is found, and the UE's local configuration for this application is not available or the PDU session establishment based on the UE's local configuration fails (146), the UE 101 can associate the application with a PDU session according to the default URSP rule (150) with "match-all" traffic descriptor or associate with non-seamless non-3GPP offload. If the association is not successful, the UE 101 can inform the upper layer.

[0026] The concept of "redundant PDU session" can be introduced for URLLC applications. The 5GSM sublayer can support the establishment of redundant PDU sessions. To establish a set of two redundant PDU sessions, the UE can include the PDU session pair ID, RSN, or both in the PDU session establishment request message for each PDU session in the two redundant PDU sessions. The UE can set the PDU session pair ID, RSN, or both according to the URSP or UE local configuration. To ensure reliability and low latency, the corresponding redundant PDU sessions can be established over 3GPP access. Therefore, MA PDU sessions are excluded from redundant PDU sessions since MA PDU sessions mean that data can be transmitted over non-3GPP access.

[0027] In one novel aspect, as shown in 160, an improved URSP rule matching method that supports redundant PDU sessions is proposed. During the URSP rule matching procedure triggered by the upper layer, if there is a "PDU session pair ID type" or "RSN type" routing descriptor component in one RSD, and there is also a "multiple access preferred type" descriptor component in the same RSD, the UE can ignore this RSD. In addition, if there is a "PDU session pair ID type" or "RSN type" routing descriptor component in one RSD, and there is also a "preferred access type" descriptor component set to "non-3GPP access" in the same RSD, the UE can ignore this RSD. Then, the UE can select the RSD with the next lowest priority that has not been evaluated from the selected URSP rule.

[0028] Figure 2A simplified block diagram of a wireless device, such as UE 201 and network entity 211, in accordance with embodiments of the application can be illustrated. Network entity 211 can be a base station combined with a Mobility Management Entity (MME) or an AMF. Network entity 211 can have an antenna 215 to transmit and receive radio signals. An RF transceiver module 214 coupled with the antenna 215 can receive RF signals from the antenna 215, convert the RF signals to baseband signals and send to a processor 213. The RF transceiver module 214 can also convert baseband signals received from the processor 213, convert the baseband signals to RF signals, and send out the antenna 215. The processor 213 processes the received baseband signals and invokes different functional modules to perform features in the base station 211. A storage medium 212 can store program instructions and data 220 to control the operation of the base station 211. In Figure 2 In an example, network entity 211 can also include a protocol stack 280 and a set of control functional modules and circuits 290. PDU session handling circuit 231 can handle PDU session establishment and modification procedures. Policy control module 232 can configure policy rules for UEs. Configuration and control circuit 233 can provide different parameters to configure and control related functions of UEs, including mobility management and session management.

[0029] Similarly, UE 201 can have a storage medium 202, a processor 203 and an RF transceiver module 204. The RF transceiver module 204 can be coupled with an antenna 205 to receive RF signals from the antenna 205, convert the RF signals to baseband signals, and send the baseband signals to the processor 203. The RF transceiver module 204 can also convert baseband signals received from the processor 203, convert the baseband signals to RF signals, and send out the antenna 205. The processor 203 can process the received baseband signals and invoke different functional modules and circuits to perform features in the UE 201. The storage medium 202 can store data and program instructions 210 executable by the processor to control the operation of the UE 201. Suitable processors can include, for example, a general purpose processor, a Digital Signal Processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGA) circuits, and other types of integrated circuits (ICs) and / or state machines. The processor associated with software can be used to implement and configure the features of the UE 201.

[0030] The UE 201 can also include a set of functional means and circuitry for performing the functions tasks of the UE 201. The protocol stack 260 can include application and other upper layers to manage different applications, where a NAS layer can communicate with an AMF entity connected to a core network, a Radio Resource Control (RRC) layer can be used for upper layer configuration and control, a Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer. The system modules and circuitry 270 can be implemented and configured through software, firmware, hardware, and / or combinations thereof. The functional modules and circuitry described above can cooperate with each other to allow the UE 201 to perform embodiments and functional tasks and features in the network when executed by the processor through program instructions contained in the storage medium. In one example, an upper layer entity can request information of a PDU session to send PDUs of an application through the PDU session. The system modules and circuitry 270 can include a PDU session handling circuitry 221 to perform PDU session establishment and modification procedures with the network, a URSP rule matching circuitry 222 to perform URSP rule matching, and a configuration and control circuitry 223 to handle configuration and control parameters for mobility management and session management.

[0031] Figure 3The content of URSP rules as defined in 3GPP specifications and parameters for improved URSP rule matching can be exemplified. A URSP can be defined as a set of one or more URSP rules. As shown in Table 300, each URSP rule can include: 1) a priority value of the URSP rule, for identifying the priority of the URSP rule among all existing URSP rules; 2) a traffic descriptor; and 3) one or more routing selection descriptors. The traffic descriptor can include: 1) a “full match” traffic descriptor; 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, protocol used above IP; c) one or more non-IP descriptors, i.e., destination information for non-IP traffic; D) one or more Data Network Names (DNNs); e) one or more connection capabilities; and F) one or more domain descriptors, i.e., destination Fully Qualified Domain Name (FQDN).

[0032] Each RSD can include a priority value of the RSD, and 1) a PDU session type, optionally, and one or more of: A) a Session and Service Continuity (SSC) mode; B) one or more Single Network Slice Selection Assistance Information (S-NSSAIs); C) one or more DNNs; D) a PDU session type; E) a preferred access type; F) a multi-access preference; G) a time window; H) location criteria; I) a PDU session pair ID; and J) an RSN; or 2) a non-seamless non-3GPP offload indication. Only one URSP rule in a URSP can be a default URSP rule, which can contain a “full match” traffic descriptor. If a default URSP rule and one or more non-default URSP rules are included in a URSP, the non-default URSP rules can have a lower priority value (i.e., higher priority) than the default URSP rule.

[0033] The UE can use the URSP to determine whether a detected application can be associated with an established PDU session, can be offloaded to non-3GPP access outside of the PDU session, or can trigger establishment of a new PDU session. The URSP rules can include a traffic descriptor, where the traffic descriptor can define a matching criterion and one or more RSD components associated with a priority value for one or more of: a SSC mode selection policy for associating a matching application with a SSC mode, a network slice selection policy for associating a matching application with a S-NSSAI, a DNN selection policy for associating a matching application with a DNN, a PDU session type policy for associating a matching application with a PDU session type, a time window, a location criterion, a preferred access type for indicating a preferred access (3GPP or non-3GPP) when the UE needs to establish a new PDU session for a matching application, a multiple access preferred type for MA PDU, a PDU session pair ID for a redundant PDU session, an RSN, and a non-seamless offload policy for determining that a matching application can be non-seamlessly offloaded to non-3GPP access (i.e., outside of a PDU session).

[0034] In one novel aspect, when a URSP rule is matched with an application, the UE can match the application information with the traffic descriptor of the selected URSP rule. Then, as shown in 311, the UE can select the RSD and determine whether the RSD contains a "PDU session pair ID type" or "RSN type" routing selection descriptor component or both. If so, the UE can know that the RSD is intended to be associated with a redundant PDU session. The UE can also determine whether the "multiple access preferred type" descriptor component is also contained in the same RSD or the "preferred access type" is set to "non-3GPP access" (as shown in 312). If so, because a redundant PDU session is introduced for URLLC to be established through 3GPP access to ensure reliability and low latency, the above RSD is not suitable for a redundant PDU session. The RSD contains conflicting parameters, therefore, the UE can ignore the RSD when it performs URSP rule matching.

[0035] Figure 4An example of URSP rule matching for an application can be illustrated, where the RSDs of selected URSP rules are ignored and skipped to support redundant PDU sessions. When the UE initiates an application, the upper layer of the UE can trigger URSP rule matching. The UE can evaluate URSP rules (excluding the default URSP rules) by matching service descriptors with application information in order of priority. If the UE finds a service descriptor that matches the application information in a non-default URSP rule, and an established PDU session matches at least one RSD of that URSP rule, the UE can provide information about the PDU session matched by the lowest priority RSD to the upper layer. Otherwise, the UE can select an RSD with the next lowest priority that has not yet been evaluated. If no match is found, the UE can evaluate the next URSP rule by matching service descriptors with application information in order of priority.

[0036] like Figure 4 As shown, a UE can be configured with multiple URSP rules, including URSP rule 1, ..., URSP rule N, URSP rule N+1, ... and so on. Each URSP rule can contain a service descriptor TD and a list of RSDs. For example, URSP rule N+1 may include TD, RSD1, and RSD2. If the UE finds a TD in URSP rule N+1 that matches the application information, the UE can select an RSD with the next lowest priority value (e.g., RSD1) for URSP rule matching. The UE can then determine the RSD components and parameters in RSD1 and attempt to match it with an existing PDU session or (if no existing PDU session is found) create a new PDU session. In a novel aspect, the UE can also check for any conflicting RSD components for redundant PDU sessions. First, the UE can determine whether RSD1 contains a "PDU session pair ID type" or "RSN type" routing descriptor component, or both. If so, the UE knows that RSD1 is intended to be associated with a redundant PDU session. The UE can also determine whether the same RSD1 contains a "Multi-access Preferred Type" descriptor component or a "Preferred Access Type" descriptor component set to "Non-3GPP Access". If so, the UE knows that RSD1 is not suitable for redundant PDU sessions. Therefore, RSD1 contains conflicting parameters, and the UE can ignore RSD1 when performing URSP rule matching. Then, the UE selects the RSD with the next lowest priority value (e.g., RSD2) for URSP rule matching.

[0037] Note that if the UE does not skip RSD1, the UE can attempt to establish a redundant PDU session over non-3GPP access. If the establishment is successful, the redundant PDU session cannot transmit duplicate packets over non-3GPP access because 5GS does not support it. If the establishment fails, the UE can continue to retry, wasting time and resources. Similarly, the UE can attempt to establish a redundant PDU session using the M APDU session. If the establishment is successful, the redundant PDU session cannot transmit duplicate packets over non-3GPP access because 5GS does not support it. If the establishment fails, the UE can continue to retry, wasting time and resources.

[0038] Figure 5 A timing diagram of improved URSP rule matching between a UE and a network for a redundant PDU session according to the novel aspects of the present application can be illustrated. In step 510, the network 502 can provide a URSP configuration or update to the UE 501 (via a PCF). The URSP can include a set of URSP rules, including a default URSP rule. In step 511, the UE 501 can send a PDU session establishment request message to establish a PDU session with a list of UE requested parameters. In step 512, the stored PDU session parameters can be assigned by the network via a PDU session establishment accept message. In step 513, the upper layer of the UE 501 can request PDU session information, such as triggered by the launch of an application. It can also be said that the upper layer of the UE can request information of a PDU session that is used to send PDU of an application. To determine the association between the application and the PDU session or non-seamless non-3GPP offload, the UE upper layer can perform URSP rule matching in step 514.

[0039] At step 520, the UE 501 can try all non-default URSP rules in order of priority value. Specifically, at step 521, the UE 501 can select a matching URSP rule, and then can find an existing PDU session that matches at least one RSD of the selected URSP rule, or can establish a new PDU session that matches at least one RSD of the selected URSP rule. If there is no matching PDU session, the UE’s NAS layer can attempt to establish a new PDU session. For example, at step 522, the UE 501 can send a PDU session establishment request to the network. At step 523, the network can send a PDU session establishment accept to the UE 501, and the PDU session establishment is successful. Otherwise, the network can send a PDU session establishment reject to the UE 501, and the PDU session establishment fails. After step 520, if all non-default URSP rules fail to match the application, at step 531, the UE 501 can try the default URSP rule, which can include a “full match” traffic descriptor. If the association still fails, the UE 501 can notify the upper layer of the failure.

[0040] At step 521, the UE 501 can also check for any conflicting RSD components for redundant PDU sessions. The UE can first determine whether the RSD1 contains a “PDU session pair ID type” or “RSN type” routing descriptor component or both. If so, the UE can know that the RSD1 is intended to be associated with a redundant PDU session. The UE can also determine whether the same RSD1 also contains a “multi-access preference type” descriptor component or contains a “preferred access type” set to “non-3GPP access.” If so, the UE can know that the RSD1 is not suitable for a redundant PDU session. Thus, the RSD1 contains conflicting parameters, and the UE can ignore the RSD1 when performing URSP rule matching.

[0041] Figure 6is a flow chart of the improved URSP rule matching method according to the novel aspect of the present application. In step 601, the UE can initiate a URSP rule matching procedure in a mobile communication network. The UE can select a URSP rule from one or more URSP rules. In step 602, the UE can match the traffic descriptor of the selected URSP rule with the application information. In step 603, the UE can select and evaluate an RSD from the RSD list of the selected URSP rule to match with a PDU session. The RSD can have an RSD component list, which can contain a PDU session pair ID or RSN. In step 604, the UE can ignore the RSD when it is determined that the RSD further contains a preferred access type set as non-3GPP access, or the UE can ignore the RSD when it is determined that the RSD further contains a multi-access preferred type.

[0042] The above-described embodiments of the present application are merely intended to guide the practice of the present application, and are not intended to limit the present application. Accordingly, various modifications, adjustments and combinations of the above-described embodiments can be made without departing from the scope of the present application as set forth in the claims.

Claims

1. A method for wireless communication, comprising: In a mobile communication network, a user equipment (UE) initiates a UE routing policy rule matching process, wherein the UE selects a UE routing policy rule from one or more UE routing policy rules. Match the service descriptor of the selected user equipment routing policy rule with the application information; A route selection descriptor is selected and evaluated from the list of route selection descriptors in the selected user equipment routing policy rule to match a protocol data unit session, wherein the route selection descriptor has a list of route selection descriptor components, the list of route selection descriptor components containing protocol data unit session pair identifiers or redundant sequence numbers; Determine whether the routing descriptor component list still contains a preferred access type that is set to non-Generation 3 Partner Program access, or whether the routing descriptor component list still contains a multiple access preferred type; as well as When it is determined that the routing descriptor component list contains Protocol Data Unit session pair identifiers or redundant sequence numbers, but also contains the preferred access type set to non-Generation 3 Partner Program access, the routing descriptor is ignored, or... When it is determined that the routing descriptor component list contains Protocol Data Unit Session Pair Identifiers or Redundant Sequence Numbers, but also contains Multiple Access Preferred Types, the routing descriptor is ignored.

2. The method for wireless communication as described in claim 1, characterized in that, The user equipment routing selection policy rule matching process is initiated by the upper layer of the user equipment and triggered by the protocol data unit that needs to send the application.

3. The method for wireless communication as described in claim 1, characterized in that, Each user equipment routing policy rule includes a priority value, a service descriptor, and a list of routing descriptors.

4. The method for wireless communication as described in claim 1, characterized in that, The service descriptor includes at least one of the following: Application identifier, Internet protocol tuple, non-Internet protocol descriptor, data network name, connectivity, and domain descriptor.

5. The method for wireless communication as described in claim 1, characterized in that, Each route selection descriptor in the list of route selection descriptors is associated with a priority value, which indicates the priority for matching.

6. The method for wireless communication as described in claim 1, characterized in that, The user equipment skips the routing descriptor and selects another routing descriptor with the lowest priority value from the list of routing descriptors that has not yet been evaluated.

7. The method for wireless communication as described in claim 6, characterized in that, When there are no other route selection descriptors in the list that have not been evaluated, the user equipment skips the selected user equipment route selection policy rule.

8. A user equipment for wireless communication, comprising: The upper-layer processing circuit initiates a user equipment routing policy rule matching process in the mobile communication network, wherein the user equipment selects a user equipment routing policy rule from one or more user equipment routing policy rules; The user equipment routing policy processing circuit matches the service descriptors of the selected user equipment routing policy rules with application information. Specifically, the user equipment selects and evaluates routing descriptors from the list of routing descriptors in the selected user equipment routing policy rules to match them with protocol data unit sessions. The control circuit determines that the routing descriptor has a routing descriptor component list, wherein the routing descriptor component list contains protocol data unit session pair identifiers or redundant sequence numbers. The control circuit also determines whether the routing descriptor component list still contains a preferred access type set to non-Generation 3 Partner Program access, or whether the routing descriptor component list still contains a multiple access preferred type. Wherein, when it is determined that the routing descriptor component list contains Protocol Data Unit session pair identifiers or redundant sequence numbers, but also contains the preferred access type set to non-Generation 3 Partner Program access, the user equipment ignores the routing descriptor, or When it is determined that the routing descriptor component list contains Protocol Data Unit Session Pair Identifiers or Redundant Sequence Numbers, but also contains Multiple Access Preferred Types, the user equipment ignores the routing descriptor.

9. The user equipment as claimed in claim 8, characterized in that, The user equipment routing selection policy rule matching process is initiated by the upper layer of the user equipment and triggered by the protocol data unit that needs to send the application.

10. The user equipment as claimed in claim 8, characterized in that, Each user equipment routing policy rule includes a priority value, a service descriptor, and a list of routing descriptors.

11. The user equipment as claimed in claim 8, characterized in that, The service descriptor includes at least one of the following: Application identifier, Internet protocol tuple, non-Internet protocol descriptor, data network name, connectivity, and domain descriptor.

12. The user equipment as claimed in claim 8, characterized in that, Each route selection descriptor in the list of route selection descriptors is associated with a priority value, which indicates the priority for matching.

13. The user equipment as claimed in claim 8, characterized in that, The user equipment skips the routing descriptor and selects another routing descriptor with the lowest priority value from the list of routing descriptors that has not yet been evaluated.

14. The user equipment as claimed in claim 13, characterized in that, When there are no other route selection descriptors in the list that have not been evaluated, the user equipment skips the selected user equipment route selection policy rule.

15. A storage medium storing program instructions that, when executed by a user equipment, cause the user equipment to perform the steps of the method for wireless communication according to any one of claims 1-7.

Images