Enhanced UE route selection policy (URSP) rule matching
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.
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.
2. The method of claim 1 , wherein the selecting in (b) involves matching all components of the traffic descriptor with the application.
3. 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.
4. 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.
5. 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.
6. The method of claim 5 , wherein the UE fails to establish the new PDU session.
7. The method of claim 1 , wherein the obtaining in (c) involves evaluating each of the route selection descriptors based on a precedence value.
8. The method of claim 1 , wherein the UE provides information of the suitable PDU session to the application layer upon being obtained successfully.
9. 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.
10. The method of claim 1 , wherein the default URSP rule contains a “match all” traffic descriptor.
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.
12. The UE of claim 11 , wherein the UE selects the non-default URSP by matching all components of the traffic descriptor with the application.
13. 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.
14. 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.
15. 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.
16. The UE of claim 15 , wherein the UE fails to establish the new PDU session.
17. 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.
18. The UE of claim 11 , wherein the UE provides information of the suitable PDU session to the application layer upon being obtained successfully.
19. 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.
20. The UE of claim 11 , wherein the default URSP rule contains a “match all” traffic descriptor.