TW202141955A - Handling method of ip 3 tuple component and user equipment thereof - Google Patents

Abstract

A method for configuring Route Selection Policy (URSP) rules with IP 3 tuples as a traffic descriptor component is proposed. URSP is used by a user equipment (UE) to determine if a detected application can be associated to an established Protocol Data Unit (PDU) session, can be offloaded to non-3GPP access outside a PDU session, or can trigger the establishment of a new PDU session. URSP can be configured by the network to the UE. A new component is introduced which can include three parameters of IP 3 tuple for URSP configuration. Upon receiving the new component for IP 3 tuple component, the UE may discover certain errors and determine corresponding error handling.

Description

Internet protocol 3-tuple component processing method and its user equipment

The embodiments of the present invention generally relate to wireless communication, and, more specifically, to deal with the Internet Protocol (IP) 3-tuple in the fifth generation (5th Generation, 5G) new radio (NR) system (Tuple) The method of the component.

Over the years, wireless communication networks have grown exponentially. The Long-Term Evolution (LTE) system provides high peak data rates, low latency, improved system capacity, and low operating costs brought about by a simple network architecture. The LTE system, also known as the 4th Generation (4G) system, also provides seamless integration with older networks, such as Global System for Mobile Communications (GSM), code division multiple access ( Code Division Multiple Access, CDMA) and Universal Mobile Telecommunications System (UMTS). In the LTE system, the evolved universal terrestrial radio access network (E-UTRAN) includes a plurality of evolved node Bs that communicate with a plurality of mobile stations called user equipment (UE) (Evolved Node-B, eNodeB or eNB). Third Generation Partnership Project ^{(3 rd generation partner project, 3GPP} ) network typically includes a second-generation (2nd Generation, 2G) / third-generation (3rd Generation, 3G) / 4G hybrid systems. The Next Generation Mobile Network (NGMN) board of directors has decided to focus future NGMN activities on defining the end-to-end requirements of the 5G NR system (5GS).

UE strategies used in 5GS include UE Route Selection Policy (URSP) and Access Network Discovery and Selection Policy (ANDSP). The UE policy can be passed to the UE through the Policy Control Function (PCF). PCF is responsible for managing network strategies to manage network behavior. PCF obtains subscription information from Unified Data Management (UDM). PCF connects with Access and Mobility Function (AMF) to manage the mobility context, and connects with the Session Management Function (SMF) to manage the session context. PCF also plays an important role in providing network slicing and roaming modes. The PCF triggers the URSP to enable the UE to determine how to handle an application in the context of an existing or new Protocol Data Unit (PDU) session. The UE policy can also be pre-configured in the UE. Only when the UE does not receive the same type of policy from the PCF, the UE should apply the pre-configured policy.

The PDU session defines the association between the UE and the data network that provides the PDU connection service. Each PDU session is identified by a PDU session identifier (identifier, ID), and includes one or more quality of service (QoS) flows and QoS rules. When the upper layer requests to send information about the PDU session of the application PDU, the UE shall evaluate the URSP rules. The UE finds the traffic descriptor matching the application information in the URSP rule, and finds an established PDU session that matches at least one of the routing descriptors in the URSP rule. If there is no suitable existing PDU session, the UE shall establish a PDU session for at least one of the routing descriptors.

Specifically, for URSP rule configuration, the network can provide IP 3-tuples as traffic descriptor components. An IP 3-tuple consists of three traffic descriptor components: 1) Internet Protocol version 4 (IPv4) remote address type or Internet Protocol version 6 (Internet Protocol version 6, IPv6) remote address/prefix length type; 2) protocol identifier/next header type; and 3) single remote port type or remote port range type. However, a single traffic descriptor can include multiple IP 3-tuples of different traffic descriptor components. The UE may not be able to determine whether the different parameters are in the same or in different IP 3-tuples.

Need to find a solution.

The present invention proposes a method for configuring URSP rules using IP 3-tuples as traffic descriptor components. The UE uses URSP to determine whether the detected application can be associated with an established PDU session, whether it can be offloaded to non-3GPP access outside the PDU session, or whether it can trigger the establishment of a new PDU session. The URSP can be configured to the UE by the network. A new component has been introduced, which includes the three parameters of the IP 3-tuple for URSP configuration. After receiving the new component for the IP 3-tuple parameter, the UE can find some errors and determine the corresponding error handling.

In one embodiment, the UE receives non-access-stratum (NAS) messages in the mobile communication network. The NAS message carries the URSP rule configuration. The UE determines the IP 3-tuple component from the traffic descriptor (TD) included in the URSP rule. When the UE detects an IP 3-tuple component of an IP 3-tuple error, the UE performs corresponding error handling. When the UE does not detect an IP 3-tuple error, the UE processes the URSP rule. In an example, the IP 3-tuple component includes at least one of a destination IP address field, a destination port field, and a protocol identifier field.

The method for processing IP 3-tuple components proposed in the present invention enables the UE to use the IP 3-tuple components correctly and avoids UE behavior errors.

Other embodiments and advantages are described in the detailed description below. The summary is not intended to define the invention. The present invention is limited by the scope of patent application for invention.

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

Figure 1 depicts an exemplary 5G network 100 according to novel aspects, which supports the processing of IP 3-tuple parameters for URSP configuration. The 5G network 100 includes UE 101, base station gNB 102, AMF 103, SMF 104, PCF 105, and UDM 106. In the example in Figure 1, the UE 101 and its serving base station gNB 102 are part of a radio access network (RAN) 120. In the access layer (Access Stratum, AS), as shown by arrow 130, the RAN 120 provides radio access to the UE 101 via a radio access technology (RAT), for example, 5G NR. At the NAS layer, AMF 103 communicates with gNB 102 and SMF 104 to perform access and mobile management of wireless access devices in 5G network 100. The UE 101 is configured with a radio frequency (RF) transceiver or multiple RF transceivers to perform different application services through different RATs/CNs. UE 101 can be a smart phone, a wearable device, an Internet of Thing (IoT) device, a tablet computer, etc.

UE strategies for 5GS include URSP and ANDSP. The UE strategy can be passed to the UE through the PCF. PCF is responsible for managing network strategies to manage network behavior. PCF obtains subscription information from UDM. PCF connects with AMF to manage the action context, and connects with SMF to manage the session context. PCF also plays an important role in providing network slicing and roaming modes. PCF triggers URSP, enabling the UE to determine how to handle an application in the context of an existing or new PDU session. The UE policy can also be pre-configured in the UE. Only when the UE does not receive the same type of policy from the PCF, the UE should apply the pre-configured policy.

The PDU session defines the association between the UE and the data network that provides the PDU connection service. Each PDU session is identified by a PDU session ID and includes one or more QoS flows and QoS rules. When the upper layer requests to send information about the PDU session of the application PDU, the UE shall evaluate the URSP rules. The UE finds the traffic descriptor matching the application information in the URSP rule, and finds an established PDU session that matches at least one of the routing descriptors in the URSP rule. If there is no suitable existing PDU session, the UE shall establish a PDU session for at least one of the routing descriptors.

In the example in Figure 1, when the UE 101 starts the application 140, the upper layer of the UE triggers the URSP rule evaluation. Specifically, the UE 101 evaluates the URSP rules (except the default URSP rules) that have traffic descriptors matching the application information according to the ascending order of the priority value. If the UE 101 finds a non-default URSP rule (141) with a traffic descriptor (142) that matches the application information, and at least one of the routing descriptors (143) that matches the non-default URSP rule has been created For the PDU session, the UE 101 provides the upper layer with information about the PDU session that matches the routing descriptor with the lowest priority value. Otherwise, the UE 101 selects the routing descriptor with the next smallest priority value that has not yet been evaluated. If there is no matching PDU session, the UE NAS layer shall try to establish a PDU session 144 using the local configuration of the UE. If the PDU session is successfully established (step 145), the UE NAS layer should provide the information of the successfully established PDU session to the upper layer.

For URSP rule configuration, the network can provide IP 3-tuples as traffic descriptor components. An IP 3-tuple consists of three traffic descriptor components: 1) IPv4 remote address type or IPv6 remote address/prefix length type; 2) protocol identifier/next header type; and 3) single remote port Type or remote port range type. However, a single traffic descriptor can include multiple IP 3-tuples of different traffic descriptor components. The UE may not be able to determine whether the different parameters are in the same or in different IP 3-tuples. According to a novel aspect, a new component is introduced that includes three parameters of the IP 3-tuple for URSP configuration. The UE 101 needs to indicate through NAS signaling (for example, 5G session management (5G session management, 5GSM) procedures) whether it supports "IP 3-tuple components" as UE capabilities. After receiving the new component of the IP 3-tuple parameter for URSP configuration, the UE can find some errors and determine the corresponding error handling.

Figure 2 depicts a simplified block diagram of a wireless device (eg, UE 201 and network entity 211) according to an embodiment of the present invention. The network entity 211 may be a base station combined with MME or AMF. The UE 201 has a memory 202, a processor 203, and an RF transceiver 204. The RF transceiver 204 is coupled to the antenna 205, receives RF signals from the antenna 205, converts them into baseband signals, and sends them to the processor 203. The RF transceiver 204 also converts the baseband signals received from the processor 203, converts them into RF signals, and sends them to the antenna 205. The processor 203 processes the received baseband signal and calls different functional modules and circuits to execute the functions in the UE 201. The memory 202 stores program instructions and data 210 for the processor to control the operation of the UE 201. Suitable processors include, for example, special purpose processors, digital signal processors (digital signal processors, DSP), multiple microprocessors, one or more microprocessors related to DSP cores, controllers, and microcontrollers Controllers, application specific integrated circuits (ASIC), field programmable gate array (FPGA) circuits, and other types of integrated circuits (IC) and/or state machines. The processor associated with the software can be used to implement and configure the features of the UE 201.

The UE 201 also includes a set of functional modules and control circuits that perform the functional tasks of the UE 201. The protocol stack 260 includes the NAS layer that communicates with the AMF/SMF/MME entity connected to the core network, the Radio Resource Control (RRC) layer for upper-layer configuration and control, and the Packet Data Convergence protocol (Packet Data Convergence). Protocol, PDCP)/Radio Link Control (Radio Link Control, RLC) layer, Media Access Control (MAC) layer and Physical (PHY) layer. The system module and circuit 270 can be implemented and configured by hardware, firmware, software, and any combination thereof. When the processor executes the functional modules and circuits through the program instructions in the memory, they cooperate with each other to enable the UE 201 to execute the implementation modes and functional tasks and features in the network. In one example, the system module and circuit 270 includes a URSP rule processing circuit 271, a PDU session processing circuit 272, and a configuration and control circuit 273 that performs URSP rule configuration and evaluation. Specifically, the PDU session processing circuit 271 matches an existing PDU session or establishes a new PDU session for the application. The URSP rule processing circuit 272 updates the URSP configuration including the IP 3-tuple components and executes the corresponding URSP rule selection. The configuration and control circuit 273 receives the URSP configuration from the network, determines whether there is an IP 3-tuple error, and performs corresponding error processing.

Similarly, the network entity 211 has an antenna 215, which transmits and receives radio signals. The RF transceiver 214 is coupled to the antenna 215, receives RF signals from the antenna 215, converts them into baseband signals, and sends them 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 signal and calls different functional modules to execute the functions in the network entity 211. The memory 212 stores program instructions and data 220 to control the operation of the network entity 211. In the example in FIG. 2, the network entity 211 also includes a protocol stack 280 and a set of control function modules and circuits 290. The PDU session processing circuit 291 handles the PDU session establishment and modification process. The policy control module 292 configures a policy rule including an IP 3-tuple component for the URSP rule for the UE. The configuration and control circuit 293 provides different parameters to configure and control related functions of the UE, including mobility management and session management.

Figure 3 illustrates an example of the content of the URSP rules, including the traffic descriptor with IP 3-tuple defined in the 3GPP specification. As shown in Table 300, each URSP rule is composed of the following parts: 1) The priority value of the URSP rule, which is used to identify the priority of the URSP rule in all existing URSP rules; 2) the traffic descriptor; 3) one or more Multiple routing descriptors. The traffic descriptor includes: 1) a fully matched traffic descriptor; or 2) at least one of the following components: A) one or more application identifiers; B) one or more IP descriptors; C) one Or more domain descriptors, namely the Fully Qualified Domain Name (FQDN) of the destination; D) one or more non-IP descriptors, namely the destination information of non-IP traffic; E) one or More data network names (Data Network Name, DNN); F) One or more connection properties. Each routing descriptor includes the priority value of the routing descriptor, and optionally includes one or more of the following: A) Session and Service Continuity (SSC) mode; B) One or more Single Network Slice Selection Assistance Information (S-NSSAI); C) one or more DNNs; D) a PDU session type; E) non-seamless non-3GPP offload instructions; F) preferred storage Take the type; G) multiple access preferences; H) routing selection verification criteria (Route Selection Validation Criteria, RSVC).

For example, as shown in block 301, the IP descriptor of the traffic descriptor may include an IP 3-tuple, the IP 3-tuple including the destination IP address, the number of destination ports, and the protocol used on the IP. If a single traffic descriptor can include different traffic descriptor components of multiple IP 3-tuples, the UE cannot determine whether the different parameters are in the same or different IP 3-tuples. According to a novel aspect, a new component is introduced that includes at least one of the three parameters of the IP 3-tuple (IP address, number of ports, and protocol). For example, the components of the IP 3-tuple may include "IP 3-tuple ID" to identify each individual IP 3-tuple parameter, so that the UE can compose IP 3-tuple parameters based on the IP 3-tuple ID. In a preferred embodiment, a new component can be introduced to include the three parameters of the IP 3-tuple for URSP configuration.

Figure 4 depicts an embodiment of a new component for IP 3-tuple configuration in accordance with the novel aspect of the invention. In the embodiment in Figure 4, the network provides a new component 400 for configuring traffic descriptors during URSP configuration through NAS signaling. The new component 400 includes the TD component type ID (for example, =IP 3-tuple component type), optionally followed by the length of the IP 3-tuple component, and then each individual traffic descriptor, for example, IP 3 1 to 3 traffic descriptor components of the tuple. For example, the first parameter is the TD component type ID=IP/PORT/PROTOCOL (IP/port/protocol), and the next parameter is the content of the TD component.

In order to properly receive the new component carrying the IP 3-tuple for URSP configuration, the UE needs to indicate whether it supports the "IP 3-tuple component" through NAS signaling (for example, the 5GSM procedure). In one embodiment, the UE indicates the UE performance in the UE policy flag IE included in the UE STATE INDICATION message sent to the network. The UE can find various errors and determine the corresponding treatment. Possible errors include: 1) There is more than one IP component ((IPv4 remote address type or IPv6 remote address/prefix length type), or more than one port component (single remote port type or remote port range type); 2) IP There are no fields in the 3-tuple component; and 3) Other syntax/semantic errors. The handling of the above errors includes: 1) UE ignores the IP 3-tuple component; 2) UE ignores the corresponding URSP rule; 3) UE refuses to transmit IP 3-tuple NAS signaling from the network with appropriate error reasons (for example , It can be the 5GSM reason of the new specific reason, or the existing 5GSM reason); and 4) The UE accepts the NAS signaling of the IP 3-tuple and has an appropriate error reason (for example, it can be the 5GSM reason of the new specific reason, or the existing 5GSM reason). 5GSM reason).

Figure 5 depicts another embodiment of a new component for IP 3-tuple configuration in accordance with the novel aspect of the invention. In the embodiment in Figure 5, the network provides a new component 500 for configuring traffic descriptors during URSP configuration through NAS signaling. The new component 500 includes the TD component type ID (for example, =IP 3-tuple component type), optionally followed by the length of the IP 3-tuple component, and then each individual traffic descriptor, for example, to pre Define the 3 traffic descriptor components of the IP 3-tuple arranged in a fixed order. For example, the IP component is followed by the content of the IP component, the port component is followed by the content of the port component, and the protocol component is followed by the content of the protocol component.

Similar to the implementation in Figure 4, in the implementation in Figure 5, the UE may find various errors and determine the corresponding processing. Possible errors include: 1) There is more than one IP component ((IPv4 remote address type or IPv6 remote address/prefix length type), or more than one port component (single remote port type or remote port range type); 2) IP There are no components in the 3-tuple component; and 3) Other syntax/semantic errors. The handling of the above errors includes: 1) UE ignores the IP 3-tuple component; 2) UE ignores the corresponding URSP rule; 3) UE refuses to transmit IP 3-tuple NAS signaling from the network with appropriate error reasons (for example , It can be the 5GSM reason of the new specific reason, or the existing 5GSM reason); and 4) The UE accepts the NAS signaling of the IP 3-tuple and has an appropriate error reason (for example, it can be the 5GSM reason of the new specific reason, or the existing 5GSM reason). 5GSM reason).

The UE uses URSP to determine whether the detected application can be associated with an established PDU session, whether it can be offloaded to non-3GPP access outside the PDU session, or whether it can trigger the establishment of a new PDU session. URSP rules include a traffic descriptor specifying matching conditions and one or more routing descriptors. Each routing descriptor includes one or more of the following: SSC mode selection strategy for associating matching applications with SSC modes, network slicing selection strategies for associating matching applications with S-NSSAI, and matching applications with DNNs The DNN selection strategy, the PDU session type strategy that associates the matching application with the PDU session type, the non-seamless uninstallation strategy used to determine that the matching application should be non-seamlessly uninstalled to non-3GPP access, and when the UE needs to be matched The application indicates the access type preference of the preferred access (3GPP or non-3GPP or multiple access) when establishing a PDU session.

Figure 6 depicts the sequence flow between the UE and the network for URSP configuration and corresponding rule evaluation according to the novel aspect of the present invention. In step 611, the UE 601 registers with the 5GS through the network 602. In step 612, the UE 601 indicates through NAS signaling whether it supports the "IP 3-tuple component" (for example, the UE status indication process). In step 621, the network 602 (via the PCF) provides the UE 601 with URSP configuration or update (for example, via a management UE policy command message). URSP may include a set of URSP rules, including a preset URSP rule. In step 622, the UE 601 updates the URSP rule including the IP 3-tuple and performs error handling. For example, if the UE 601 detects any semantic or syntax error, in step 623, the UE 601 sends a management UE policy completion (MANAGE UE POLICY COMPLETE) or a management UE policy command rejection (MANAGE UE POLICY COMMAND REJECT) with an appropriate error reason. ) Message to accept or reject the URSP configuration. The UE can also accept URSP configuration, but ignore specific URSP rules with IP 3-tuple errors. If no errors are found, the UE 601 processes/updates the URSP rules. In step 631, the UE 601 and the network 602 establish one or more PDU sessions, and each PDU session has information including the service NSSAI, DNN, and PDU session ID.

In step 641, the UE 601 starts the application. In order to determine the association between the application and the PDU session or non-seamless non-3GPP offloading, the upper layer of the UE performs URSP rule evaluation in step 642. The UE 601 tries all non-default URSP rules in the ascending order of the priority values of the URSP rules. Specifically, in step 643, the UE 601 selects a URSP rule with a traffic descriptor matching the application information, and then, in step 644, the UE 601 finds at least one of the routing descriptors of the selected URSP rule For a matching existing PDU session, the preferred access type and multiple access preferences are not considered or considered. If there is no matching PDU session, the UE NAS layer can try to establish a new PDU session (step 651).

Figure 7 is a flowchart of the method of IP 3-tuple configuration and error handling according to the novel aspect of the present invention. In step 701, the UE receives the NAS message in the mobile communication network. The NAS message carries the URSP rule configuration. In step 702, the UE determines the IP 3-tuple component from the TD included in the URSP rule. In step 703, when the UE detects an IP 3-tuple component of the IP 3-tuple error, the UE performs corresponding error processing. In step 704, when the UE does not detect an IP 3-tuple error, the UE processes the URSP rule. In an example, the IP 3-tuple component includes at least one of a destination IP address field, a destination port field, and a protocol identifier field.

Although the present invention has been described in conjunction with certain specific embodiments for instructional purposes, the present invention is not limited thereto. Therefore, various modifications, adaptations and combinations of various features of the described embodiments can be implemented without departing from the scope of the present invention described in the scope of the patent application.

100: 5G network 101,201,601:UE 102: gNB 103: AMF 104: SMF 105: PCF 106: UDM 120: RAN 130: Arrow 140: Application 141: Non-preset URSP rules 142: Traffic Descriptor 143: routing descriptor 144: PDU session 145,611,612,621,622,623,631,641,642,643,644,651: steps 202, 212: memory 203,213: Processor 204,214: RF transceiver 205,215: Antenna 210, 220: Program instructions and data 211: Network entity 260,280: Protocol stack 270: System modules and circuits 271: URSP rule processing circuit 272, 291: PDU session processing circuit 273, 293: configuration and control circuits 292: Strategy Control Module 300: table 301: box 400,500: New components 600: Network

The drawings describe the embodiments of the present invention, in which the same numbers refer to the same parts. Figure 1 depicts an exemplary 5G network based on the novel aspect, which supports the processing of IP 3-tuple parameters for URSP configuration. Figure 2 depicts a simplified block diagram of a wireless device according to an embodiment of the present invention. Figure 3 illustrates an example of the content of the URSP rules, including the traffic descriptor with IP 3-tuple defined in the 3GPP specification. Figure 4 depicts an embodiment of a new component for IP 3-tuple configuration in accordance with the novel aspect of the invention. Figure 5 depicts another embodiment of a new component for IP 3-tuple configuration in accordance with the novel aspect of the invention. Figure 6 depicts the sequence flow between the UE and the network for URSP configuration and corresponding rule evaluation according to the novel aspect of the present invention. Figure 7 is a flowchart of the method of IP 3-tuple configuration and error handling according to the novel aspect of the present invention.

100: 5G NR network

101: UE

102: gNB/eNB

103: AMF/SMF/MME

104:5GC/EPC

105: PDN GW

106: IMS server

120: RAN

130: Arrow

Claims (11)

A method for processing Internet protocol 3-tuple components, including: A user equipment receives a non-access layer message in a mobile communication network, and the non-access layer message carries a user equipment routing policy rule configuration; Determining an Internet Protocol 3-tuple component from a traffic descriptor included in the user equipment routing policy rule; When the user equipment detects an Internet Protocol 3-tuple error in one of the Internet Protocol 3-tuple components, execute a corresponding error processing; and When the user equipment does not detect the Internet Protocol 3-tuple error, process the user equipment routing policy rule. The method for processing an Internet Protocol 3-tuple component as described in claim 1, wherein the Internet Protocol 3-tuple component includes a destination Internet Protocol address field, a destination port field, and At least one of the agreement identifier fields. The method for processing an Internet Protocol 3-tuple component according to claim 1, wherein the traffic descriptor includes a traffic descriptor component type identifier indicating an Internet Protocol 3-tuple component type. The method for processing an Internet Protocol 3-tuple component according to claim 3, wherein the traffic descriptor further includes one or one indicating an Internet Protocol component type, a port component type, or a protocol component type. More traffic descriptor component type identifiers are followed by the content of the corresponding traffic descriptor component. The processing method of the Internet Protocol 3-tuple component as described in claim 1, wherein, when there is more than one Internet Protocol address field, more than one port field, or more than one protocol field, the use The device detects the Internet Protocol 3-tuple error. The method for processing an Internet Protocol 3-tuple component as described in claim 1, wherein when there is no field in the Internet Protocol 3-tuple component, the user equipment detects the Internet Network protocol 3-tuple error. The method for processing an Internet Protocol 3-tuple component according to claim 1, wherein, when there are other syntax or semantic errors in the Internet Protocol 3-tuple component, the user equipment detects the Internet protocol 3-tuple error. The method for processing an Internet Protocol 3-tuple component according to claim 1, wherein the corresponding error processing includes the user equipment ignoring the user equipment routing policy rule. The method for processing an Internet Protocol 3-tuple component according to claim 1, wherein the corresponding error processing includes the user equipment rejecting the non-access layer message or the user equipment sending a message with a One of the appropriate reasons for the error is the fifth-generation session management status message. The method for processing an Internet Protocol 3-tuple component according to claim 1, wherein the corresponding error processing includes that the user equipment accepts the non-access layer message and the user equipment also sends A fifth-generation session management status message is one of the appropriate causes of error. A user equipment for processing Internet protocol 3-tuple components, including: A radio frequency transceiver, receiving a non-access layer message in a mobile communication network, the non-access layer message carrying a user equipment routing policy rule configuration; A user equipment routing policy rule processing circuit, which determines an Internet protocol 3-tuple component from a traffic descriptor included in the user equipment routing policy rule; A configuration and control circuit, when the user equipment detects an Internet Protocol 3-tuple error in one of the Internet Protocol 3-tuple components, executes a corresponding error processing; and when the user equipment When the Internet Protocol 3-tuple error is not detected, the user equipment routing policy rule is processed.

Images