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 |
|
3GPP TS 31.127 V0.1.10 (2023-02) |
|
|
Technical Specification |
|
|
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; UICC-terminal interaction; non-removable Universal Subscriber Identity Module (nrUSIM) application behavioural test specification; (Release 17) |
|
|
|
 |
|
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. |
|
|
3GPP Postal address 3GPP support office address 650 Route des Lucioles – Sophia Antipolis Valbonne – FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org |
|
Copyright Notification No part may be reproduced except as authorized by written permission. © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). All rights reserved. UMTS™ is a Trade Mark of ETSI registered for the benefit of its members 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM Association |
Contents
Foreword 13
Introduction 14
1 Scope 15
2 References 15
3 Definitions of terms, symbols and abbreviations 17
3.1 Terms 17
3.2 Symbols 17
3.3 Abbreviations 17
3.4 Coding Conventions 17
3.5 Generic procedures for 5G‑NR, E‑UTRAN, NB‑IoT, UTRAN and IMS 17
3.6 Table of optional features 18
3.7 Applicability 19
3.7.1 Applicability to user equipment 19
3.7.2 Supported additional explicit verification methods 20
3.7.3 Applicability of the individual tests 20
3.8 Applicability table 21
4 Test environment 22
4.1.1 General test environment 22
4.1.2 Example – test environment for implicit testing 23
4.1.3 Example – test environment for contents verification 23
4.1.4 Example – test environment for seamless testing 24
4.1.5 Example – test environment for test toolkit events based testing 24
4.1.6 Example – test environment for UEs with ETSI eSSP/iSSP 25
4.2 Requirements to the EUT and the test environment 25
4.2.1 General Requirements 25
4.2.2 Requirements to the UE (EUT) – supported interfaces 25
4.2.3 Supported RATs 26
4.2.4 Initial and final procedure steps 26
4.3 Random value generation 26
4.4 Suitability assessment 27
4.4.1 Suitability assessment in present test procedures 27
4.4.2 Suitability assessment in test descriptions 27
4.4.3 Suitability assessment in the test protocol 27
4.4.4 Justification of additional measures 27
4.5 Definition of default values 27
4.5.1 Definition of the Default UICC 27
4.5.2 Definition of E-UTRAN/EPC UICC 28
4.5.3 Definition of E-UTRAN/EPC ISIM-UICC 28
4.5.4 Definition of ACSGL/OCSGL E-UTRAN/EPC UICC 28
4.5.5 Definition of Non-Access Stratum Configuration UICC 28
4.5.6 Definition of Non-Access Stratum Configuration of EUTRAN/EPC UICC 28
4.5.7 Definition of 5G-NR UICC 28
4.5.8 Definition of default values for EFs commonly used with random value generation 29
4.5.8.1 EFIMSI with 3-digit MNC and random value 29
4.5.8.2 EFIMSI "short", with 3-digit MNC and random value 29
4.5.8.3 EFIMSI "short", with 2-digit MNC and random value 29
4.5.8.4 EFIMSI "long", with 3-digit MNC and random value 29
4.5.8.5 EFIMSI for SUCI calculation tests 29
4.5.8.6 EFIMSI for "change IMSI" tests 30
4.5.8.7 EFRouting_Indicator with 2-digit MNC and random value 30
4.5.8.8 EFLOCI with "short" random TMSI value 30
4.5.8.9 EFLOCI with "long" random TMSI value 30
4.5.8.10 EFEPSLOCI 31
5 Subscription related tests 31
5.1 IMSI/TMSI handling 31
5.1.1 UE identification by short IMSI 31
5.1.1.1 Definition and applicability 31
5.1.1.2 Conformance requirement 31
5.1.1.3 Test purpose 32
5.1.1.4 Method of test 32
5.1.1.4.1 Initial conditions 32
5.1.1.4.2 Procedure 32
5.1.1.5 Acceptance criteria 32
5.1.2 UE identification by short IMSI using a 2-digit MNC 32
5.1.2.1 Definition and applicability 32
5.1.2.2 Conformance requirement 32
5.1.2.3 Test purpose 33
5.1.2.4 Method of test 33
5.1.2.4.1 Initial conditions 33
5.1.2.4.2 Procedure 33
5.1.2.5 Acceptance criteria 33
5.1.3 UE identification by "short" TMSI 33
5.1.3.1 Definition and applicability 33
5.1.3.2 Conformance requirement 33
5.1.3.3 Test purpose 34
5.1.3.4 Method of test 34
5.1.3.4.1 Initial conditions 34
5.1.3.4.2 Procedure 34
5.1.3.5 Acceptance criteria 34
5.1.4 UE identification by "long" TMSI 34
5.1.4.1 Definition and applicability 34
5.1.4.2 Conformance requirement 34
5.1.4.3 Test purpose 35
5.1.4.4 Method of test 35
5.1.4.4.1 Initial conditions 35
5.1.4.4.2 Procedure 35
5.1.4.5 Acceptance criteria 36
5.1.5 UE identification by long IMSI, TMSI updating and key set identifier assignment 36
5.1.5.1 Definition and applicability 36
5.1.5.2 Conformance requirement 36
5.1.5.3 Test purpose 36
5.1.5.4 Method of test 37
5.1.5.4.1 Initial conditions 37
5.1.5.4.2 Procedure 37
5.1.5.5 Acceptance criteria 37
5.1.6 UE identification by short IMSI when accessing E-UTRAN/EPC 38
5.1.6.1 Definition and applicability 38
5.1.6.2 Conformance requirement 38
5.1.6.3 Test purpose 38
5.1.6.4 Method of test 38
5.1.6.4.1 Initial conditions 38
5.1.6.4.2 Procedure 39
5.1.6.4.2.1 Test Procedure A 39
5.1.6.4.2.2 Test Procedure B 39
5.1.6.5 Acceptance criteria 39
5.1.6.5.1 Acceptance criteria for Test Procedure A 39
5.1.6.5.2 Acceptance criteria for Test Procedure B 39
5.1.6.4.3 Common acceptance criteria 40
5.1.7 UE identification by short IMSI using a 2-digit MNC when accessing E-UTRAN/EPC 40
5.1.7.1 Definition and applicability 40
5.1.7.2 Conformance requirement 40
5.1.7.3 Test purpose 40
5.1.7.4 Method of test 40
5.1.7.4.1 Initial conditions 40
5.1.7.4.2 Procedure 41
5.1.7.4.2.1 Test Procedure A 41
5.1.7.4.2.2 Test Procedure B 41
5.1.7.4 Acceptance criteria 41
5.1.8 UE identification after changed IMSI with service "EMM Information" not available 42
5.1.8.1 Definition and applicability 42
5.1.8.2 Conformance requirement 42
5.1.8.3 Test purpose 42
5.1.8.4 Method of test 42
5.1.8.4.1 Initial conditions 42
5.1.8.4.2 Procedure 43
5.1.8.4.2.1 Test Procedure A 43
5.1.8.4.2.2 Test Procedure B 43
5.1.8.5 Acceptance criteria 44
5.1.9 UE identification by GUTI when using USIM with service "EMM Information" not available 44
5.1.10 UE identification by GUTI when using USIM with service "EMM Information" available 46
5.1.10.2 Conformance requirement 46
5.1.10.3 Test purpose 46
5.1.10.4 Method of test 46
5.1.10.4.1 Initial conditions 46
5.1.10.4.2 Procedure 47
5.1.10.4.2.1 Test Procedure A 47
5.1.10.4.2.2 Test Procedure B 47
5.1.10.4.2.3 Common final Test Procedure 48
5.1.10.5 Acceptance criteria 48
5.2 Access Control handling 48
5.2.1 Access Control information handling 48
5.2.1.1 Definition and applicability 48
5.2.1.2 Conformance requirement 48
5.2.1.3 Test purpose 49
5.2.1.4 Method of test 49
5.2.1.4.1 Initial conditions 49
5.2.1.4.2 Coding details 50
5.2.1.4.3 Procedure 50
5.2.1.5 Acceptance criteria 50
5.2.2 Access Control information handling for E-UTRAN/EPC 50
5.2.3 Access Control information handling for NB-IoT 50
5.3 Handling subscription identifier privacy for 5G 50
5.3.1 SUCI calculation by ME using null scheme 50
5.3.1.1 Definition and applicability 50
5.3.1.2 Conformance requirement 50
5.3.1.3 Test purpose 51
5.3.1.4 Method of test 51
5.3.1.4.1 Initial conditions 51
5.3.1.4.2 Procedure 52
5.3.1.5 Acceptance criteria 53
5.3.2 SUCI calculation by ME using Profile B 53
5.3.2.1 Definition and applicability 53
5.3.2.2 Conformance requirement 53
5.3.2.3 Test purpose 54
5.3.2.4 Method of test 54
5.3.2.4.1 Initial conditions 54
5.3.2.4.2 Procedure 54
5.3.2.5 Acceptance criteria 55
5.3.3 UE identification by SUCI during initial registration – SUCI calculation by USIM using profile B 55
5.3.4 UE identification by SUCI in response to IDENTITY REQUEST message 55
5.3.4.1 Definition and applicability 55
5.3.4.2 Conformance requirement 55
5.3.4.3 Test purpose 56
5.3.4.4 Method of test 56
5.3.4.4.1 Initial conditions 56
5.3.4.4.2 Procedure 57
5.3.4.5 Acceptance criteria 58
5.3.5 UE identification by SUCI in response to IDENTITY REQUEST message with T3519 timer expiry 58
5.3.5.1 Definition and applicability 58
5.3.5.2 Conformance requirement 58
5.3.5.3 Test purpose 59
5.3.5.4 Method of test 59
5.3.5.4.1 Initial conditions 59
5.3.5.4.2 Procedure 60
5.3.5.5 Acceptance criteria 61
5.3.6 UE identification by SUCI in response to IDENTITY REQUEST message and AUTHENTICATION REJECT 61
5.3.7 SUCI calculation by the ME using null scheme – missing parameters for subscription identifier privacy support by the USIM 61
5.3.8 UE identification by 5G-GUTI – Last Registered TAI stored on USIM 61
5.3.9 UE identification by 5G-GUTI – Last Registered TAI stored by ME 61
5.3.10 UE identification after SUPI is changed 61
5.3.11 SUCI calculation by ME using Profile A 61
5.3.12 UE identification by SUCI during initial registration – SUCI calculation by USIM using profile A 61
5.3.13 SUCI calculation by ME using null scheme– no Protection Scheme Identifier provisioned in the USIM 61
5.3.14 SUCI calculation by ME using null scheme – no Home Network Public Key for supported protection scheme provisioned in the USIM 62
5.3.15 SUCI calculation by ME using null scheme with the E-UTRAN/EPC UICC 62
5.3.16 SUCI calculation by ME using the lower priority protection scheme when the higher priority protection scheme is not supported by the ME 62
5.3.17 SUCI calculation by ME using Profile B with compressed Home Network Public Key 62
5.4 Unified Access Control information handling for 5G-NR 62
5.4.1 Unified Access Control – Access identity 0, no access identities indicated by USIM 62
5.4.1.1 Definition and applicability 62
5.4.1.2 Conformance requirement 62
5.4.1.3 Test purpose 63
5.4.1.4 Method of test 63
5.4.1.4.1 Initial conditions 63
5.4.1.4.2 Procedure 64
5.4.1.4.3 Acceptance criteria 65
5.4.1.4.4 Tables related to the test case 66
5.4.2 Unified Access Control – Access Identity 1 – MPS indicated by USIM 66
5.4.3 Unified Access Control – Access Identity 1 – no MPS indication by USIM and SUPI not changed 66
5.4.4 Unified Access Control – Access Identity 1 – no MPS indication by USIM and SUPI is changed 66
5.4.5 Unified Access Control – Access Identity 2 – MCS indicated by USIM 67
5.4.6 Unified Access Control – Access Identity 2 – no MCS indication by USIM and SUPI is not changed 67
5.4.7 Unified Access Control – Access Identity 2 – no MCS indication by USIM and SUPI is changed 67
5.4.8 Unified Access Control – Access Identities 11 and 15 indicated by USIM 67
5.4.9 Unified Access Control – Access Identities 12, 13 and 14 indicated by USIM 67
5.4.10 Unified Access Control – Operator-Defined Access Category 67
5.4.11 Unified Access Control – Operator-Defined Access Categories, no change in SUPI 67
5.4.12 Unified Access Control – Operator-Defined Access Categories, SUPI change 67
5.5 Handling of operator controlled features 67
5.5.1 Display of registered 5G PLMN name from USIM 67
5.5.1.1 Definition and applicability 67
5.5.1.2 Conformance requirement 68
5.5.1.3 Test purpose 68
5.5.1.4 Method of tests 68
5.5.1.4.1 Initial conditions 68
5.5.1.4.2 Procedure 70
5.5.1.4.3 Acceptance criteria 71
5.5.2 Display of registered 5G PLMN name from ME 71
5.5.2.1 Definition and applicability 71
5.5.2.2 Conformance requirement 71
5.5.2.3 Test purpose 71
5.5.2.4 Method of tests 72
5.5.2.4.1 Initial conditions 72
5.5.2.4.2 Procedure 74
5.5.1.4.3 Acceptance criteria 74
6 Security related Tests 85
6.1 PIN handling 85
6.1.1 Entry of PIN 85
6.1.1.1 Definition and applicability 85
6.1.1.2 Conformance requirement 85
6.1.1.3 Test purpose 85
6.1.1.4 Method of test 86
6.1.1.4.1 Initial conditions 86
6.1.1.4.2 Procedure 86
6.1.1.5 Acceptance criteria 86
6.1.2 Change of PIN 86
6.1.2.1 Definition and applicability 86
6.1.2.2 Conformance requirement 86
6.1.2.3 Test purpose 86
6.1.2.4 Method of test 87
6.1.2.4.1 Initial conditions 87
6.1.2.4.2 Procedure 87
6.1.2.5 Acceptance criteria 87
6.1.3 Unblock PIN 87
6.1.3.1 Definition and applicability 87
6.1.3.2 Conformance requirement 88
6.1.3.3 Test purpose 88
6.1.3.4 Method of test 88
6.1.3.4.1 Initial conditions 88
6.1.3.4.2 Procedure 88
6.1.3.5 Acceptance criteria 89
6.1.4 Entry of PIN2 90
6.1.4.1 Definition and applicability 90
6.1.4.2 Conformance requirement 90
6.1.4.3 Test purpose 90
6.1.4.4 Method of test 90
6.1.4.4.1 Initial conditions 90
6.1.4.4.2 Procedure 90
6.1.4.5 Acceptance criteria 91
6.1.5 Change of PIN2 91
6.1.5.1 Definition and applicability 91
6.1.5.2 Conformance requirement 91
6.1.5.3 Test purpose 91
6.1.5.4 Method of test 91
6.1.5.4.1 Initial conditions 91
6.1.5.4.2 Procedure 91
6.1.5.5 Acceptance criteria 92
6.1.6 Unblock PIN2 92
6.1.6.1 Definition and applicability 92
6.1.6.2 Conformance requirement 92
6.1.6.3 Test purpose 93
6.1.6.4 Method of test 93
6.1.6.4.1 Initial conditions 93
6.1.6.4.2 Procedure 93
6.1.6.5 Acceptance criteria 94
6.1.7 Replacement of PIN 94
6.1.7.1 Definition and applicability 94
6.1.7.2 Conformance requirement 95
6.1.7.3 Test purpose 95
6.1.7.4 Method of test 95
6.1.7.4.1 Initial conditions 95
6.1.7.4.2 Procedure 95
6.1.7.5 Acceptance criteria 96
6.1.8 Change of Universal PIN 96
6.1.8.1 Definition and applicability 96
6.1.8.2 Conformance requirement 96
6.1.8.3 Test purpose 97
6.1.8.4 Method of test 97
6.1.8.4.1 Initial conditions 97
6.1.8.4.2 Procedure 97
6.1.8.5 Acceptance criteria 97
6.1.9 Unblock Universal PIN 98
6.1.9.1 Definition and applicability 98
6.1.9.2 Conformance requirement 98
6.1.9.3 Test purpose 98
6.1.9.4 Method of test 98
6.1.9.4.1 Initial conditions 98
6.1.9.4.2 Procedure 98
6.1.9.5 Acceptance criteria 99
6.1.10 Entry of PIN on multi-verification capable UICCs 99
6.1.10.1 Definition and applicability 99
6.1.10.2 Conformance requirement 99
6.1.10.4 Method of test 100
6.1.10.4.1 Initial conditions 100
6.1.10.4.2 Procedure 100
6.1.10.5 Acceptance criteria 101
6.1.11 Change of PIN on multi-verification capable UICCs 101
6.1.11.1 Definition and applicability 101
6.1.11.2 Conformance requirement 101
6.1.11.3 Test purpose 101
6.1.11.4 Method of test 101
6.1.11.4.1 Initial conditions 101
6.1.11.4.2 Procedure 102
6.1.11.5 Acceptance criteria 103
6.1.12 Unblock PIN on multi-verification capable UICCs 103
6.1.12.1 Definition and applicability 103
6.1.12.2 Conformance requirement 103
6.1.12.3 Test purpose 103
6.1.12.4 Method of test 103
6.1.12.4.1 Initial conditions 103
6.1.12.4.2 Procedure 104
6.1.12.5 Acceptance criteria 105
6.1.13 Entry of PIN2 on multi-verification capable UICCs 106
6.1.13.1 Definition and applicability 106
6.1.13.2 Conformance requirement 106
6.1.13.3 Test purpose 106
6.1.13.4 Method of test 106
6.1.13.4.1 Initial conditions 106
6.1.13.4.2 Procedure 107
6.1.13.5 Acceptance criteria 108
6.1.14 Change of PIN2 on multi-verification capable UICCs 108
6.1.14.1 Definition and applicability 108
6.1.14.2 Conformance requirement 108
6.1.14.3 Test purpose 108
6.1.14.4 Method of test 108
6.1.14.4.1 Initial conditions 108
6.1.14.4.2 Procedure 109
6.1.14.5 Acceptance criteria 110
6.1.15 Unblock PIN2 on multi-verification capable UICCs 110
6.1.15.1 Definition and applicability 110
6.1.15.2 Conformance requirement 110
6.1.15.3 Test purpose 110
6.1.15.4 Method of test 110
6.1.15.4.1 Initial conditions 110
6.1.15.4.2 Procedure 111
6.1.15.5 Acceptance criteria 112
6.1.16 Replacement of PIN with key reference "07" 113
6.1.16.1 Definition and applicability 113
6.1.16.2 Conformance requirement 113
6.1.16.3 Test purpose 113
6.1.16.4 Method of test 114
6.1.16.4.1 Initial conditions 114
6.1.16.4.2 Procedure 114
6.1.16.5 Acceptance criteria 115
6.2 Fixed Dialling Numbers (FDN) handling 116
6.2.1 Terminal and USIM with FDN enabled, EFADN readable and updateable 116
6.2.2 Terminal and USIM with FDN disabled 116
6.2.3 Enabling, disabling and updating of FDN 116
6.2.4 Terminal and USIM with FDN enabled, EFADN readable and updateable (Rel-4 and onwards) 116
6.3 Void 116
6.4 Advice of charge (AoC) handling 116
6.4.1 AoC not supported by USIM 116
6.4.2 Maximum frequency of ACM updating 116
6.4.3 Call terminated when ACM greater than ACMmax 116
6.4.4 Response codes of increase command of ACM 116
7 PLMN related tests 116
7.1 FPLMN handling 116
7.1.1 Adding FPLMN to the Forbidden PLMN list 116
7.1.2 UE updating forbidden PLMNs 117
7.1.3 UE deleting forbidden PLMNs 117
7.1.4 Adding FPLMN to the forbidden PLMN list when accessing E‑UTRAN 117
7.1.4.1 Definition and applicability 117
7.1.4.2 Conformance requirement 117
7.1.4.3 Test purpose 117
7.1.4.4 Method of test 118
7.1.4.4.1 Initial conditions 118
7.1.4.4.2 Procedure 118
7.1.4.4 Acceptance criteria 119
7.1.5 UE updating forbidden PLMNs when accessing E-UTRAN 120
7.1.6 UE deleting forbidden PLMNs when accessing E-UTRAN 120
7.1.7 Updating the Forbidden PLMN list after receiving non-integrity protected reject message – UTRAN 120
7.1.8 Updating the Forbidden PLMN list after receiving non-integrity protected reject message – EUTRAN 120
7.2 User controlled PLMN selector handling 120
7.2.1 UE updating the User controlled PLMN selector list 120
7.2.2 UE recognizing the priority order of the User controlled PLMN selector list with the same access Technology 120
7.2.3 UE recognizing the priority order of the User controlled PLMN selector list using an ACT Preference 121
7.2.4 Void 121
7.2.5 UE updating the User controlled PLMN selector list for E-UTRAN 121
7.2.6 UE recognizing the priority order of the User controlled PLMN selector list using an ACT preference- UTRAN/E-UTRAN 121
7.2.7 UE recognizing the priority order of the User controlled PLMN selector list using an ACT preference- GSM/E-UTRAN 121
7.2.8 UE recognising the priority order of the User controlled PLMN selector list with the same access technology – E-UTRAN in NB-S1 mode 121
7.2.9 UE recognising the priority order of the User controlled PLMN selector list using the ACT preference – E-UTRAN in WB-S1/EUTRAN in NB-S1 121
7.3 Operator controlled PLMN selector handling 121
7.3.1 UE recognizing the priority order of the Operator controlled PLMN selector list 121
7.3.2 UE recognizing the priority order of the User controlled PLMN selector over the Operator controlled PLMN selector list 121
7.3.3 UE recognizing the priority order of the Operator controlled PLMN selector list when accessing E-UTRAN 122
7.3.4 UE recognizing the priority order of the User controlled PLMN selector over the Operator controlled PLMN selector list – E-UTRAN 122
7.4 Higher priority PLMN search handling 122
7.4.1 UE recognizing the search period of the Higher priority PLMN 122
7.4.2 GSM/UMTS dual mode UEs recognizing the search period of the Higher priority PLMN 122
7.4.3 UE recognizing the search period of the Higher priority PLMN – E‑UTRAN 122
7.4.4 E-UTRAN/EPC capable UEs recognizing the search period of the Higher priority PLMN – GSM/E-UTRAN 122
7.4.5 E-UTRAN/EPC capable UEs recognizing the search period of the Higher priority PLMN – UTRAN/E-UTRAN 122
7.5 Void 123
8 Subscription independent tests 123
8.1 Phone book procedures 123
8.1.1 Recognition of a previously changed phonebook 123
8.1.2 Update of the Phonebook Synchronization Counter (PSC) 123
8.1.3 Phonebook content handling 123
8.1.4 Phonebook selection 123
8.1.5 Local Phonebook handling 123
8.2 Short message handling report 123
8.2.1 Correct storage of a SM on the USIM 123
8.2.2 Correct reading of a SM on the USIM 123
8.2.3 SM memory capacity exceeded handling 123
8.2.4 Correct storage of an SM on the UICC 123
8.2.5 Correct reading of a SM on the USIM if USIM and ISIM are present 124
8.2.6 Correct reading of a SM on the ISIM if USIM and ISIM are present 124
8.2.7 Correct storage of an SM on the UICC 124
8.3 MMS related tests 124
8.3.1 UE recognizing the priority order of MMS Issuer Connectivity Parameters 124
8.3.2 UE recognizing the priority order of MMS User Connectivity Parameters 124
8.3.3 UE recognizing the priority order of MMS Issuer Connectivity Parameters over the MMS User Connectivity Parameters 124
8.3.4 Usage of MMS notification 124
8.4 UICC presence detection 124
8.5 UICC presence detection when connected to E‑UTRAN/EPC 124
9 USIM service handling 125
9.1 Access Point Name Control List handling 125
9.1.1 Access Point Name Control List handling for terminals supporting ACL 125
9.1.2 Network provided APN handling for terminals supporting ACL 125
9.1.3 Access Point Name Control List handling for terminals not supporting ACL 125
9.1.4 Access Point Name Control List handling for terminals supporting ACL connected to E-UTRAN/EPC 125
9.1.5 Void 125
9.1.6 Void 125
9.2 Service Dialling Numbers handling 125
10 CSG list handling 125
10.1 CSG list handling for E-UTRA 125
10.1.1 Automatic CSG selection in E-UTRA with CSG list on USIM, success 125
10.1.3 Manual CSG selection in E-UTRA with CSG list on USIM, success 126
10.1.4 Manual CSG selection in E-UTRA with CSG list on USIM, rejected 126
10.1.5 CSG selection in E-UTRA with no CSG list on USIM, no IMSI change 126
10.1.6 CSG selection in E-UTRA with no CSG list on USIM, with IMSI change 126
10.1.7 Manual CSG selection without display restrictions in E-UTRA with ACSG list and OCSG list on USIM 126
10.1.8 Manual CSG selection with display restrictions in E-UTRA with ACSG list and OCSG list on USIM 126
10.2 CSG list handling for UTRA 126
10.2.1 Manual CSG selection without display restrictions in UTRA with ACSG list and OCSG list on USIM 126
10.2.2 Manual CSG selection with display restrictions in UTRA with ACSG list and OCSG list on USIM 126
10.2.3 Manual CSG selection in UTRA with CSG list on USIM, success 126
11 NAS security context parameter handling 127
11.1 NAS security context parameter handling when service "EMM Information" is available 127
11.2 NAS security context parameter handling when service "EMM Information" is not available, no IMSI change 127
11.3 NAS security context parameter handling when service "EMM Information" is not available, IMSI Changed 127
11.4 EPS NAS Security Context Storage 127
12 Non Access Stratum (NAS) Configuration parameter handling 127
12.1 EFNASCONFIG – NAS signalling priority handling 127
12.2 EFNASCONFIG – NMO I Network Mode of Operation I handling 127
12.3 EFNASCONFIG – Attach with IMSI handling 127
12.4 EFNASCONFIG – Verifying Minimum Periodic Search Timer 127
12.5 EFNASCONFIG – Extended access barring handling 127
12.6 EFNASCONFIG – Verifying Timer T3245 Behaviour 128
12.7 EFNASCONFIG – Override NAS signalling low priority 128
12.8 EFNASCONFIG – Override Extended access barring 128
12.9 EFNASCONFIG – Fast First Higher Priority PLMN Search 128
12.10 EFNASCONFIG – E-UTRA Disabling Allowed for EMM cause #15 128
12.11 EFNASCONFIG – SM_RetryWaitTime 128
12.12 EFNASCONFIG – SM_RetryAtRATChange 128
13 UICC interface during PSM 128
13.1 UICC interface in PSM handling for E-UTRAN – No UICC deactivation in PSM 128
13.2 UICC interface in PSM handling for E-UTRAN – PSM not accepted by E-USS/NB-SS 128
13.3 UICC interface in PSM handling for E-UTRAN – UICC deactivation in PSM 128
13.4 UICC interface in PSM for E-UTRAN – SUSPEND UICC 129
14 UICC interface during eDRX 129
14.1 UICC interface during eDRX for E-UTRAN – eDRX is not supported by the UICC 129
14.2 UICC interface during eDRX for E-UTRAN – eDRX is not accepted by E-USS/NB-SS 129
14.3 UICC interface during eDRX for E-UTRAN – UICC deactivation during eDRX 129
14.4 UICC interface during eDRX for E-UTRAN– SUSPEND UICC 129
15 Authentication procedure and NAS security context handling for 5G 129
15.1 Authentication procedure for EAP-AKA’ 129
15.1.1 Authentication procedure for EAP-AKA’ – Authentication is successful 129
15.1.1.1 Definition and applicability 129
15.1.1.2 Conformance requirement 130
15.1.1.3 Test purpose 130
15.1.1.4 Method of test 131
15.1.1.4.1 Initial conditions 131
15.1.1.4.2 Procedure 132
15.1.1.5 Acceptance criteria 133
15.1.2 Authentication procedure for EAP-AKA’ – Authentication is successful – GSM UICC 133
15.1.3 Authentication procedure for EAP-AKA’ – AUTN fails on the USIM 133
15.1.4 Authentication procedure for EAP-AKA’ – after SUPI is changed 133
15.2 Authentication procedure for 5G AKA 133
15.2.1 Authentication procedure for 5G AKA – Authentication is successful 133
15.2.2 Authentication procedure for 5G AKA – Authentication is successful – GSM UICC 133
15.2.3 Authentication procedure 5G AKA – AUTN fails on the USIM 133
15.2.4 Authentication procedure for 5G AKA – after SUPI is changed 133
16 UE Route Selection Policy (URSP) procedure 134
16.1 Pre-configured URSP rules 134
16.1.1 Support for URSP by USIM 134
16.1.1.1 Definition and applicability 134
16.1.1.2 Conformance requirement 134
16.1.1.3 Test purpose 134
16.1.1.4 Method of test 134
16.1.1.4.1 Initial conditions 134
16.1.1.4.2 Procedure 136
16.1.1.5 Acceptance criteria 136
16.1.2 Support for URSP by ME 137
16.1.2.1 Definition and applicability 137
16.1.2.2 Conformance requirement 137
16.1.2.3 Test purpose 137
16.1.2.4 Method of test 137
16.1.2.4.1 Initial conditions 137
16.1.2.4.2 Procedure 138
16.1.2.5 Acceptance criteria 138
16.1.3 Support of Signalled URSP 138
16.1.3.1 Definition and applicability 138
16.1.3.2 Conformance requirement 138
16.1.3.3 Test purpose 139
16.1.3.4 Method of test 139
16.1.3.4.1 Initial conditions 139
16.1.3.4.2 Procedure 140
16.1.3.5 Acceptance criteria 141
Annex <A>: <Normative annex title> 142
Annex <D> (informative): Index 144
Annex <X> (informative): Change history 145