Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.503  Word version:  18.5.0

Top   Top   Up   Prev   Next
0…   4…   5…   6…   6.1.2…   6.1.2.4…   6.1.3…   6.1.3.6…   6.1.3.18…   6.1.3.21…   6.1.4…   6.2…   6.2.2…   6.3…   6.4…   6.6…   A…   C   D… 
A URSP rules example  B Deployment option to support of BSF and DRA coexistence due to network migration 
...

 

A  URSP rules example  p. 163

As an example, the URSP rules provisioned in the UE may include the following rules:
Example URSP rules Comments
Rule Precedence =1
Traffic Descriptor: Application descriptor=App1		Route Selection Descriptor Precedence=1
Network Slice Selection: S-NSSAI-a
SSC Mode Selection: SSC Mode 3
DNN Selection: internet
Access Type preference: 3GPP access		 This URSP rule associates the traffic of application "App1" with S-NSSAI-a, SSC Mode 3, 3GPP access and the "internet" DNN.
It enforces the following routing policy:
The traffic of App1 should be transferred on a PDU Session supporting S-NSSAI-a, SSC Mode 3 and DNN=internet over 3GPP access. If this PDU Session is not established, the UE shall attempt to establish a PDU Session with S-NSSAI-a, SSC Mode 3 and the "internet" DNN over 3GPP access.
Rule Precedence =2
Traffic Descriptor: Application descriptor=App2		 Route Selection Descriptor Precedence =1
Network Slice Selection: S-NSSAI-a
Access Type preference: Non-3GPP access		 This URSP rule associates the traffic of application "App2" with S-NSSAI-a and Non-3GPP access.
It enforces the following routing policy: The traffic of application App2 should be transferred on.
a PDU Session supporting S-NSSAI-a using a Non-3GPP access. If this PDU Session is not established, the UE shall attempt to establish a PDU Session with S-NSSAI-a over Access Type=non-3GPP access.
If the PDU Session cannot be established, the traffic of App2 shall be directly offloaded to WLAN, if the UE is connected to a WLAN with SSID-a (based on the 2nd RSD)
Route Selection Descriptor Precedence =2
Non-seamless Offload indication: Permitted (WLAN SSID-a)
Rule Precedence =3
Traffic Descriptor: DNN=DNN_1		Route Selection Descriptor Precedence =1
Network Slice Selection: S-NSSAI-a
Access Type preference: Non-3GPP access		This URSP rule associates the traffic of applications that are configured to use DNN_1 with DNN_1, S-NSSAI-a over Non-3GPP access.
It enforces the following routing policy: The traffic of application(s) that are configured to use DNN_1 should be transferred on a PDU Session supporting S-NSSAI-a over Non-3GPP access. If this PDU Session is not established, the UE shall attempt to establish the PDU Session with S-NSSAI-a over Non-3GPP access.
Rule Precedence =4
Traffic Descriptor:
Application descriptor=App1
Connection Capabilities="internet", "supl" 		Route Selection Descriptor Precedence =1
Network Slice Selection: S-NSSAI-a
DNN Selection: DNN_1
Access Type preference: Non-3GPP access		 This URSP rule associates the application "App1" and the Connection Capabilities "internet" and "supl" with DNN_1, S-NSSAI-a over Non-3GPP access.
It enforces the following routing policy without UE reporting the URSP rule enforcement as specified in clause 6.6.2.4: When the "App1" requests a network connection with Connection Capability "internet" or "supl", the UE establishes (if not already established) a PDU Session with DNN_1 and S-NSSAI-a over Non-3GPP access. After that, the UE routes the traffic of "App1" over this PDU Session.
Rule Precedence =5
Traffic Descriptor:
Application descriptor=App3
Connection Capabilities="ims" 		Route Selection Descriptor Precedence =1
Network Slice Selection: S-NSSAI-c
DNN Selection: DNN_1
Access Type preference: Multi-Access 		This URSP rule associates the application "App3" and the Connection Capability "ims" with DNN_1, S-NSSAI-c and multi-access connectivity.
It enforces the following routing policy without UE reporting the URSP rule enforcement as specified in clause 6.6.2.4:
When the "App3" requests a network connection with Connection Capability "ims", the UE establishes (if not already established) a MA PDU Session with DNN_1 and S-NSSAI-c. After that, the UE routes the traffic of "App3" over this MA PDU Session by using the received ATSSS rules
Rule Precedence =6
Traffic Descriptor: Application descriptor=App1		Route Selection Descriptor Precedence =1
DNN Selection: DNN_1
Network Slice Selection: S-NSSAI-a
Access Type preference: Multi Access		This URSP rule associates App 1 with DNN_1, S-NSSAI-a with Multi Access connectivity.
It enforces the following routing policy:
The traffic of Application 1 should be transferred on a PDU Session supporting S-NSSAI-a and DNN_1 according to the received ATSSS rules. After that the UE routes the traffic of any other application according to the ATSSS rule with match all packet filters if available.
Rule Precedence =7
Traffic Descriptor: Connection Capabilities="Real time interactive" 		Route Selection Descriptor Precedence =1
Network Slice Selection: S-NSSAI-d
Access Type preference: 3GPP-Access		 This URSP rule associates the Connection Capability "Real time interactive" with S-NSSAI-d and 3GPP-access connectivity.
It enforces the following routing policy and:
When any application requests a network connection with Connection Capability "Real time interactive", the UE establishes (if not already established) a PDU Session with S-NSSAI-d over 3GPP access. After that, the UE routes the traffic from the requesting application over this PDU Session.
Rule Precedence =8
Traffic Descriptor:
Connection Capabilities="Real time interactive"
Indication for reporting of URSP enforcement = "Y"
UE supports reporting of URSP rule enforcement conditions (see clause 6.6.2.4) 		Route Selection Descriptor Precedence =1
Network Slice Selection: S-NSSAI-d
Access Type preference: 3GPP-Access 		Since indication for reporting of URSP enforcement is included, if UE reporting of URSP rule enforcement conditions are met (see clause 6.6.2.4), same as in example with Rule Precedence=7, with the difference that the UE enforces the routing policy and additionally, the UE reports the URSP rule enforcement as specified in clause 6.6.2.4. Otherwise, same as in example with Rule Precedence=7.
Rule Precedence =9
Traffic Descriptor:
PIN ID=PIN1 		Route Selection Descriptor Precedence =1
DNN Selection: DNN_p1
Network Slice Selection: S-NSSAI-p1
Access Type preference: 3GPP access 		This URSP rule associates PIN 1 with DNN_p1, S-NSSAI-p1 with 3GPP Access connectivity.
It enforces the following routing policy:
The traffic of PIN 1 should be transferred on a PDU Session supporting S-NSSAI-p1 and DNN_p1 over 3GPP access. If this PDU Session is not established, the UE shall attempt to establish a PDU Session with S-NSSAI-p1 and DNN_p1 over 3GPP access.
Rule Precedence =10
Traffic Descriptor:
IP descriptor=IP Address of PIN Server of PIN1 		Route Selection Descriptor Precedence =1
DNN Selection: DNN_p2
Network Slice Selection: S-NSSAI-p2
Access Type preference: 3GPP access 		This URSP rule associates traffic towards the PIN Server of PIN 1 with DNN_p2, S-NSSAI-p2 with 3GPP Access connectivity.
It enforces the following routing policy:
The traffic that targets the PIN 1 Server should be transferred on a PDU Session supporting S-NSSAI-p2 and DNN_p2 over 3GPP access. If this PDU Session is not established, the UE shall attempt to establish a PDU Session with S-NSSAI-p2 and DNN_p2 over 3GPP access.
In a deployment, DNN_p1 and DNN_p2 may be configured to the same value. Also, S-NSSAI-p1 and S-NSSAI-p2 may be configured to the same value.
Rule Precedence = lowest priority
Traffic Descriptor: *		Route Selection Descriptor Precedence =1
Network Slice Selection: S-NSSAI-b
SSC Mode Selection: SSC Mode 3
DNN Selection: internet		 This URSP rule associates all traffic not matching any prior rule a PDU Session with S-NSSAI-b, SSC Mode 3 and the "internet" DNN.
It enforces the following routing policy:
All traffic not matching any prior rule should be transferred on a PDU Session supporting S-NSSAI-b, SSC Mode 3 and DNN=internet with no access network preference.
Up

B  Deployment option to support of BSF and DRA coexistence due to network migration  p. 168

During the network migration, DRA and BSF may coexist in operator's network. The DRA can be a consumer of Nbsf services and the BSF can provide binding functionality for different subscribers. When the AF using Rx, such as P-CSCF, sends Rx request to the DRA, if the DRA has no binding information for the subscriber, based on configuration or via NRF, it selects the BSF. Then the DRA can query the BSF by invoking Nbsf_Management discovery service operation, to get the relevant PCF address, based on which the DRA routes the Rx request to the selected PCF.
Up

Up   Top   ToC