16 UE Route Selection Policy (URSP) procedure
31.1273GPPnon-removable Universal Subscriber Identity Module (nrUSIM) application behavioural test specificationRelease 17TSUICC-terminal interaction
16.1 Pre-configured URSP rules
16.1.1 Support for URSP by USIM
16.1.1.1 Definition and applicability
As specified in 3GPP TS 24.526 [38], if the UE has no signalled URSP, and the UE has pre-configured URSPs configured in both the USIM and the ME, then the UE shall use the pre-configured URSP in the USIM.
As specified in 3GPP TS 31.102 [4], the EFURSP in the USIM contains UE Route Selection Policies per PLMN and shall be considered by the ME if EFUST service n° 132 "Support for URSP by USIM" is available.
16.1.1.2 Conformance requirement
CR 1 The UE shall support the URSP procedure;
Reference:
– TS 31.102 [19], clause 5.2.34
– TS 24.526 [38], clause 4.2.2.2
– TS 23.503 [40], clause 6.6.2.1
– TS 23.501 [39], clause 5.15.5.2 and 5.15.5.3
CR 2 The URSP rules shall be read from USIM if service n°132 is "available";
Reference:
– TS 31.102 [19], clause 4.4.11.12 and 5.2.3.34
CR 3 The ME shall use URSP rules stored on the USIM rather than any pre-configured USRP rules stored in the ME if service n°132 is "available".
Reference:
– TS 31.102 [19], clause 5.1.1 and 5.2.34
3) The ME shall use the URSP rules from USIM instead of any pre-configured USRP rules in ME if service n°132 is "available".
Reference:
– 3GPP TS 24.526 [38], and 5.2;
– 3GPP TS 23.501 [39], clause 5.15.5.2 and 5.15.5.3,
– 3GPP TS 23.003 [34], clause 9A,
16.1.1.3 Test purpose
The purpose of this test is to verify that:
1) To verify that the ME reads the URSP rules from USIM if service n°132 is "available".
2) To verify that the ME uses the matching URSP rule from USIM to set the PDU session establishment parameters if service n°132 is "available".
16.1.1.4 Method of test
16.1.1.4.1 Initial conditions
The NG-SS parameters of the system simulator are:
– Mobile Country Code (MCC) = 246;
– Mobile Network Code (MNC) = 081;
– Tracking Area Code (TAC) = 000001;
– NG-SS Cell Id = 0001 (36 bits).
The Allowed S-NSSAI list is configured in NG-SS as ’01 01 01 01′, ’01 01 01 02′ and ’01 01 01 03′.
The ME is pre-configured with the following URSP rules:
USRP rules for one PLMN only
– PLMN: 246 081
Rule Precedence =1
Traffic descriptor:
– DNN=TestGp.rs
Route Selection Descriptor:
– Precedence=1
– Network Slice Selection, S-NSSAI: 01 01 01 02 (ST: MBB, SD: 010102)
– SSC Mode Selection: SSC Mode 1
– Access Type preference: 3GPP access
Rule Precedence = <lowest priority>
Traffic Descriptor: *
Route Selection Descriptor:
– Precedence = 1
– Network Slice Selection, S-NSSAI: 01 01 01 01 (ST: MBB, SD: 010101)
– SSC Mode Selection: SSC Mode 1
– DNN Selection: internet
The default 5G-NR UICC is used (with the following additions) and the UICC is installed into the ME.
EFUST (USIM Service Table)
Logically:
– User controlled PLMN selector available
– Fixed dialling numbers available
– The GSM Access available
– The Group Identifier level 1 and level 2 not available
– Service n 33 (Packed Switched Domain) shall be set to ‘1’
– Enabled Services Table available
– EPS Mobility Management Information available
– Allowed CSG Lists and corresponding indications available
– 5GS Mobility Management Information available
– 5G Security Parameters available
– Subscription identifier privacy support available
– SUCI calculation by USIM not available
– Support for URSP by USIM
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Binary: |
xxxx xx1x |
xxxx xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
xxxx xxxx |
xxxx xxxx |
xxxx xxxx |
|
B9 |
B10 |
B11 |
B16 |
B17 |
||||
|
xxxx xxxx |
xxxx xxxx |
xx11 xxxx |
….. |
xxx0 111x |
xxxx 1xxx |
EFURSP (URSP)
Logically:
URSP rules for one PLMN only
– PLMN: 246 081
Rule Precedence = 0
Traffic descriptor:
– DNN = TestGp.rs
Route Selection Descriptor:
– Precedence = 0
– Network Slice Selection, S-NSSAI: ’01 01 01 03′ (ST: MBB, SD: 010103)
|
Coding: |
80 |
22 |
42 |
16 |
80 |
1E |
00 |
1C |
|
00 |
00 |
0C |
88 |
0A |
06 |
54 |
65 |
|
|
73 |
74 |
47 |
70 |
02 |
72 |
73 |
00 |
|
|
0B |
00 |
09 |
00 |
00 |
06 |
02 |
04 |
|
|
01 |
01 |
01 |
03 |
16.1.1.4.2 Procedure
a) The UE is switched on.
b) The UE is successful authenticated to PLMN 246 081 and the NG-SS indicates Allowed S-NSSAI list as ’01 01 01 01′, ’01 01 01 02′ and ’01 01 01 03′.
c) No URSP rules are provisioned by the PCF.
d) The UE tries to connect to DNN=TestGp.rs
e) After reception of the PDU SESSION ESTABLISHMENT REQUEST, the NG-SS sends PDU SESSION ESTABLISHMENT ACCEPT message.
16.1.1.5 Acceptance criteria
1) After step a) the UE shall read EFUST and EFURSP.
2) After step d) the UE sends PDU SESSION ESTABLISHMENT REQUEST to the network via UL NAS TRANSPORT with:
DNN: TestGp.rs
S-NSSAI: ’01 01 01 03′
16.1.2 Support for URSP by ME
16.1.2.1 Definition and applicability
If the UE has no signalled URSP and the UE has only pre-configured URSPs configured in the ME, then the UE shall use the pre-configured URSP in the ME.
The pre-configured URSP can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME.
16.1.2.2 Conformance requirement
1) The UE shall support the URSP procedure.
2) The ME shall use the pre-configured URSP rules in the ME if there is no signalled URSP and UE has only pre-configured URSP in the ME.
3) The URSP can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME.
Reference:
– 3GPP TS 24.526 [50], clause 4.2.2.2 and 5.2;
– 3GPP TS 23.503 [52], clause 6.6.2.
16.1.2.3 Test purpose
1) To verify that the ME uses the matching URSP rule from ME to set the PDU session establishment parameters if there is no signalled URSP and there is no pre-configured URSP in the USIM.
16.1.2.4 Method of test
16.1.2.4.1 Initial conditions
The NG-SS parameters of the system simulator are:
– Mobile Country Code (MCC) = 244;
– Mobile Network Code (MNC) = 083;
– Tracking Area Code (TAC) = 000001;
– NG-SS Cell Id = 0001 (36 bits).
The Allowed S-NSSAI list is configured in NG-SS to include S-NSSAIs (’01 01 01 01’, ’01 01 01 01’), and (’01 01 01 02’, ’01 01 01 02’).
The ME is pre-configured with the following URSP rules:
USRP rules for one PLMN only
– PLMN: 244 083
Rule Precedence = 1
Traffic descriptor:
– DNN = TestGp.rs
Route Selection Descriptor:
– Precedence = 1
– Network Slice Selection, S-NSSAI: 01 01 01 02 (ST: MBB, SD: 010102)
– SSC Mode Selection: SSC Mode 1
– Access Type preference: 3GPP access
Rule Precedence = <lowest priority>
Traffic Descriptor: *
Route Selection Descriptor:
– Precedence =1
– Network Slice Selection, S-NSSAI: 01 01 01 01 (ST: MBB, SD: 010101)
– SSC Mode Selection: SSC Mode 1
– DNN Selection: internet
The default 5G-NR UICC is used and the UICC is installed into the ME.
16.1.2.4.2 Procedure
a) The UE is switched on.
b) The UE successfully registers to PLMN 244 083 and the NG-SS indicates Allowed S-NSSAI list as ’01 01 01 01′ and ’01 01 01 02′.
c) No URSP rules are provisioned by the PCF.
d) The UE tries to connect to DNN: TestGp.rs.
e) After reception of the PDU SESSION ESTABLISHMENT REQUEST, the NG-SS sends PDU SESSION ESTABLISHMENT ACCEPT.
16.1.2.5 Acceptance criteria
1) After step a) the UE shall read EFUST.
2) After step d) the UE sends PDU SESSION ESTABLISHMENT REQUEST to the network via UL NAS TRANSPORT with
DNN: TestGp.rs
S-NSSAI: ’01 01 01 02′
16.1.3 Support of Signalled URSP
16.1.3.1 Definition and applicability
The HPLMN pre-configured URSP in the ME and the HPLMN signalled URSP shall be stored in a non-volatile memory in the ME together with the SUPI from the USIM.
If the UE has both pre-configured URSP(s) and signalled URSP, the UE shall only use the signalled URSP. For a UE not operating in SNPN access mode, if the UE has no signalled URSP, and the UE has pre-configured URSPs configured in both the USIM and the ME, then the UE shall use the pre-configured URSP in the USIM. The HPLMN pre-configured URSP in the ME shall be stored until a new URSP is configured by HPLMN or the USIM is removed.
16.1.3.2 Conformance requirement
1) The UE shall support the URSP procedure.
2) If the UE has both pre-configured URSP(s) and signalled URSP, the UE shall only use the signalled URSP.
Reference:
– 3GPP TS 24.526 [50], clause 4.2.2.2 and 5.2;
– 3GPP TS 23.503 [52], clause 6.6.2.
16.1.3.3 Test purpose
1) To verify that the ME uses signalled URSP when provided rather than pre-configured URSP in the USIM or the ME.
16.1.3.4 Method of test
16.1.3.4.1 Initial conditions
The NG-SS is configured with the following parameters:
– Mobile Country Code (MCC) = 246;
– Mobile Network Code (MNC) = 081;
– Tracking Area Code (TAC) = 000001;
– NG-SS Cell Id = 0001 (36 bits).
The Allowed S-NSSAI list is configured in NG-SS as ’01 01 01 01′, ’01 01 01 02′ and ’01 01 01 03′.
The ME is pre-configured with the following URSP rules:
USRP rules for one PLMN only
– PLMN: 246 081
Rule Precedence =1
Traffic descriptor:
– DNN=TestGp.rs
Route Selection Descriptor:
– Precedence=1
– Network Slice Selection, S-NSSAI: 01 01 01 01 (ST:MBB, SD: 010101)
– SSC Mode Selection: SSC Mode 1
– Access Type preference: 3GPP access
The default 5G-NR UICC is used with the following exceptions:
EFUST (USIM Service Table)
Logically:
– User controlled PLMN selector available
– Fixed dialling numbers available
– The GSM Access available
– The Group Identifier level 1 and level 2 not available
– Service n 33 (Packed Switched Domain) shall be set to ‘1’
– Enabled Services Table available
– EPS Mobility Management Information available
– Allowed CSG Lists and corresponding indications available
– 5GS Mobility Management Information available
– 5G Security Parameters available
– Subscription identifier privacy support available
– SUCI calculation by USIM not available
– Support for URSP by USIM available
Coding:
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Binary: |
xxxx xx1x |
xxxx xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
xxxx xxxx |
xxxx xxxx |
xxxx xxxx |
|
B9 |
B10 |
B11 |
B16 |
B17 |
||||
|
xxxx xxxx |
xxxx xxxx |
xx11 xxxx |
….. |
xxx0 111x |
xxxx 1xxx |
EFURSP (URSP)
Logically:
URSP rules for one PLMN only
– PLMN: 246 081
Rule Precedence = 0
Traffic descriptor:
– DNN=TestGp.rs
Route Selection Descriptor:
– Precedence=0
– Network Slice Selection, S-NSSAI: ’01 01 01 02′ (ST: MBB, SD: 010102)
Coding:
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex: |
80 |
22 |
42 |
16 |
80 |
1E |
00 |
1C |
00 |
00 |
0C |
88 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
B19 |
B20 |
B21 |
B22 |
B23 |
B24 |
|
|
0A |
06 |
54 |
65 |
73 |
74 |
47 |
70 |
02 |
72 |
73 |
00 |
|
|
B25 |
B26 |
B27 |
B28 |
B29 |
B30 |
B31 |
B32 |
B33 |
B34 |
B35 |
B36 |
|
|
0B |
00 |
09 |
00 |
00 |
06 |
02 |
04 |
01 |
01 |
01 |
02 |
16.1.3.4.2 Procedure
a) The UE is switched on;
b) The UE successfully registers to PLMN 246 081 and the NG-SS indicates Allowed S-NSSAI list as ’01 01 01 01′, ’01 01 01 02′ and ’01 01 01 03′;
c) No URSP rules are provisioned by the PCF;
d) The UE tries to connect to DNN=TestGp.rs:
e) After reception of the PDU SESSION ESTABLISHMENT REQUEST, the NG-SS sends PDU SESSION ESTABLISHMENT ACCEPT.
f) The NG-SS releases the PDU Session;
g) The NG-SS sends MANAGE UE POLICY COMMAND to the UE to update the URSP rule for DNN: "TestGp.rs"
Traffic Descriptor: DNN: ‘TestGp.rs’
Route Selection Descriptor: S-NSSAI: ’01 01 01 03′
h) The UE tries to connect to DNN: TestGp.rs
i) After reception of the PDU SESSION ESTABLISHMENT REQUEST, the NG-SS sends PDU SESSION ESTABLISHMENT ACCEPT.
16.1.3.5 Acceptance criteria
1) After step a) the UE shall read EFUST and EFURSP.
2) After step d) the UE sends PDU SESSION ESTABLISHMENT REQUEST to the network via UL NAS TRANSPORT with
DNN: TestGp.rs
S-NSSAI: ’01 01 01 02′
3) After step g) the UE sends MANAGE UE POLICY COMPLETE to the NG-SS
4) After step h) the UE sends PDU SESSION ESTABLISHMENT REQUEST to the network via UL NAS TRANSPORT with
DNN: TestGp.rs
S-NSSAI: ’01 01 01 03′
Annex <A>:
<Normative annex title>
Annex <D> (informative):
Index
Use style "Heading 8" in TSs and "Heading 9" in TRs. Do not use "informative" in the title in TRs.
The Index is optional. If it exists, it shall immediately precede the Changes history annex.
Generate the index using MS Word’s index field feature.
Annex <X> (informative):
Change history
Use style "Heading 8" in TSs and "Heading 9" in TRs. Do not use "informative" in the title in TRs.
This is the last annex for TS/TSs which details the change history using the following table.
This table is to be used for recording progress during the WG drafting process till TSG approval of this TS/TR.
For TRs under change control, use one line per approved Change Request
Date: use format YYYY-MM
CR: four digits, leading zeros as necessary
Rev: blank, or number (max two digits)
Cat: use one of the letters A, B, C, D, F
Subject/Comment: for TSs under change control, include full text of the subject field of the Change Request cover
New vers: use format [n]n.[n]n.[n]n
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |