# US 2021/0243664 A1 · Enhanced UE Route Selection Policy (URSP) Rule Matching

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0243664 A1
- Document ID: US20210243664A1
- Status: Published application
- Kind: A1
- Application number: 17/236,974
- Filed: 2021-04-21
- Published: 2021-08-05
- Earliest claimed: 2019-08-08
- Assignees: Mediatek Inc.
- Applicants: Mediatek Inc.
- Inventors: Chien-Chun Huang-Fu; Meng-Ting Tsai
- Web page: https://patentgrep.com/patent/US20210243664A1

## CPC

- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04L 45/85: Selection among different networks
- H04W 8/183: {Processing at user equipment or user record carrier}
- H04W 76/11: Allocation or use of connection identifiers
- H04W 76/20: Manipulation of established connections
- H04W 76/22: Manipulation of transport tunnels
- H04L 45/306: {Route determination based on the nature of the carried application}
- H04L 47/20: Traffic policing
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L 67/148: Migration or transfer of sessions
- H04W 28/0215: {based on user or device properties, e.g. MTC-capable devices (services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51)}
- H04W 28/0252: {per individual bearer or channel (dynamic wireless traffic scheduling H04W72/12)}
- H04W 28/04: Error control
- H04W 28/12: using signalling between network elements
- H04W 28/24: Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
- H04W 40/02: Communication route or path selection, e.g. power-based or shortest path routing
- H04W 48/12: using downlink control channel
- H04W 48/18: Selecting a network or a communication service
- H04W 68/02: Arrangements for increasing efficiency of notification or paging channel
- H04W 76/27: Transitions between radio resource control [RRC] states
- H04W 84/042: {Public Land Mobile systems, e.g. cellular systems}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for UE route selection policy (URSP) rule matching is proposed. URSP is used by a UE to determine if a detected application can be associated to an established PDU session, can be offload to non-3GPP access outside a PDU session, or can trigger the establishment of a new PDU session. The UE first finds a non-default URSP rule with a matching traffic descriptor to the application. When the UE fails to find existing PDU session or setup new PDU session with any or the route selection descriptors of the non-default URSP rule, the UE moves to another non-default URSP rule, if any, and try the matching. If all non-default URSP rules cannot be matched with the application, then the UE tries the default URSP rule, which includes a match-all traffic descriptor.

## Claims

### Claim 1

A method of User Equipment (UE) Route Selection Policy (URSP) rule matching, comprising:
(a) starting an application by a user equipment (UE) in a mobile communication network;
(b) selecting a non-default URSP rule from one or more configured non-default URSP rules by matching a traffic descriptor of the non-default URSP rule with the application;
(c) obtaining a suitable protocol data unit (PDU) session based on a list of route selection descriptors of the non-default URSP rule; and
(d) selecting a default URSP rule only when all non-default URSP rules configured for the UE do not match the application, otherwise indicating a failure when the application matches at least one non-default URSP rule but fails to associate with any PDU session after evaluating all non-default URSP rules.

### Claim 2 (depends on 1)

The method of claim 1, wherein the selecting in (b) involves matching all components of the traffic descriptor with the application.

### Claim 3 (depends on 1)

The method of claim 1, wherein each configured URSP rule has a precedence value, and wherein the selecting in (b) is in an order based on the precedence value.

### Claim 4 (depends on 1)

The method of claim 1, wherein the obtaining in (c) involves finding an existing PDU session that matches a route selection descriptor from the list.

### Claim 5 (depends on 1)

The method of claim 1, wherein the obtaining in (c) involves establishing a new PDU session that matches a route selection descriptor from the list.

### Claim 6 (depends on 5)

The method of claim 5, wherein the UE fails to establish the new PDU session.

### Claim 7 (depends on 1)

The method of claim 1, wherein the obtaining in (c) involves evaluating each of the route selection descriptors based on a precedence value.

### Claim 8 (depends on 1)

The method of claim 1, wherein the UE provides information of the suitable PDU session to the application layer upon being obtained successfully.

### Claim 9 (depends on 1)

The method of claim 1, wherein the UE goes back to (b) to select a second non-default URSP rule when the obtaining of the suitable PDU session in (c) failed for the non-default URSP rule.

### Claim 10 (depends on 1)

The method of claim 1, wherein the default URSP rule contains a “match all” traffic descriptor.

### Claim 11

A User Equipment (UE), comprising:
an application layer handling circuit that starts an application in a mobile communication network, wherein the application triggers UE Route Selection Policy (URSP) rule matching for the application;
a URSP rule matching circuit that selects a non-default URSP rule from one or more configured non-default URSP rules by matching a traffic descriptor of the non-default URSP rule with the application;
a protocol data unit (PDU) session handling circuit that obtains a suitable PDU session based on a list of route selection descriptors of the non-default URSP rule; and
a control circuit that configures a list of URSP rules, wherein the UE selects a default URSP rule only when the UE fails to match all non-default URSP rules configured for the UE, otherwise the UE indicates a failure when the application matches at least one non-default URSP rule but fails to associate with any PDU session after evaluating all non-default URSP rules.

### Claim 12 (depends on 11)

The UE of claim 11, wherein the UE selects the non-default URSP by matching all components of the traffic descriptor with the application.

### Claim 13 (depends on 11)

The UE of claim 11, wherein each configured URSP rule has a precedence value, and wherein the UE selects from the one or more configured non-default URSP rules in an order based on the precedence value.

### Claim 14 (depends on 11)

The UE of claim 11, wherein the UE obtains the suitable PDU session by finding an existing PDU session that matches a route selection descriptor from the list.

### Claim 15 (depends on 11)

The UE of claim 11, wherein the UE obtains the suitable PDU session by establishing a new PDU session that matches a route selection descriptor from the list.

### Claim 16 (depends on 15)

The UE of claim 15, wherein the UE fails to establish the new PDU session.

### Claim 17 (depends on 11)

The UE of claim 11, wherein the UE obtains the suitable PDU session by evaluating each of the route selection descriptors based on a precedence value.

### Claim 18 (depends on 11)

The UE of claim 11, wherein the UE provides information of the suitable PDU session to the application layer upon being obtained successfully.

### Claim 19 (depends on 11)

The UE of claim 11, wherein the UE select a second non-default URSP rule when the obtaining of the suitable PDU session failed for the non-default URSP rule.

### Claim 20 (depends on 11)

The UE of claim 11, wherein the default URSP rule contains a “match all” traffic descriptor.