7 PLMN related tests
31.1273GPPnon-removable Universal Subscriber Identity Module (nrUSIM) application behavioural test specificationRelease 17TSUICC-terminal interaction
7.1 FPLMN handling
7.1.1 Adding FPLMN to the Forbidden PLMN list
RFU – agreed method to verify the UPDATE command on EF_Keys/EF_KeysPS and EF_FPLMN needed.
7.1.2 UE updating forbidden PLMNs
7.1.2.1 Definition and applicability
A list of forbidden PLMNs stored in the USIM provides storage for at least 4 entries, and is managed by the UE. In automatic PLMN selection mode the UE controls registration attempts to appropriate networks with respect to this list of forbidden PLMNs. As a result of a registration reject with the cause "PLMN not allowed" the UE stores the PLMN which rejected the update request in the USIM.
The registration attempts initiated by the 3G UE depends on UEs capabilities and can be one of the following:
I. registration procedures for UEs supporting CS or
II. registration procedures for UEs supporting PS or
III. registration procedures for UEs supporting CS/PS
7.1.2.2 Conformance requirement
In case of a 2G terminal:
CR 1 After the receipt of a LOCATION UPDATING REJECT message with the cause "PLMN not allowed" the UE shall update the EFFPLMN in the USIM
Reference:
– TS 22.011 [18], clause 3.2.2.4.
– TS 31.102 [19], clauses 5.1.1 and 5.2.7.
In case of a 3G terminal:
CR 1 Depending on which domain the UE will be registered on, one of the following requirements should be fulfilled:
I. After the receipt of a LOCATION UPDATING REJECT message during registration on CS with the cause "PLMN not allowed" the UE shall update the EF FPLMN in the USIM or
II. after receipt of a ATTACH REJECT message during registration on PS with the cause "PLMN not allowed" the Terminal shall update the EF FPLMN in the USIM or
III. after receipt of a LOCATION UPDATING REJECT and/or ATTACH REJECT message during registration on CS/PS with the cause "PLMN not allowed" the Terminal shall update the EF FPLMN in the USIM.
Reference:
– TS 22.011 [18], clause 3.2.2.4.
– TS 31.102 [19], clauses 5.1.1 and 5.2.7.
7.1.2.3 Test purpose
To verify that the UE correctly updates the EFFPLMN, i.e. fill up existing gaps in the elementary file before overwriting any existing entries.
7.1.2.4 Method of test
7.1.2.4.1 Initial conditions
The USS (in case of a Terminal accessing UTRAN)/ SS (in case of a Terminal accessing a GERAN) transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 234/002/0001.
– RAI (MCC/MNC/LAC/RAC): 234/002/0001/05 (only for UTRAN cell)
– Access control: unrestricted.
NOTE: In case of a GERAN no packet system information is transmitted
Ensure that the automatic PLMN selection mode is set and that the UE is using the UICC/USIM configuration defined for this test case in 31.121 [2] and runs an initial activation when executing the test procedure. The UE is switched on.
In case of a Terminal accessing UTRAN "Expected Sequence A" and in case of a Terminal accessing a GERAN "Expected Sequence B" shall be performed.
7.1.2.4.2 Procedure
Expected Sequence A:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE > TT |
|
|||
|
2 |
TT > UE |
RRC CONNECTION SETUP |
|||
|
3 |
UE > TT |
|
|||
|
Depending on which domain the UE is going to be registered on, either Step 4, 5 or 6 will be used. |
|||||
|
4 |
UE > TT |
|
This step is followed if UE is registered on CS domain. The TT performs an authentication and starts NAS integrity protection |
||
|
TT > UE |
|
||||
|
5 |
UE > TT |
ATTACH REQUEST |
This step is followed if UE is registered on PS domain. The TT performs an authentication and starts NAS integrity protection |
||
|
TT > UE |
ATTACH REJECT |
||||
|
6 |
UE > TT |
|
This step is followed if UE is registered on CS/PS domain. The TT performs an authentication and starts NAS integrity protection |
||
|
TT > UE |
|
||||
|
7 |
UE > USIM |
|
CR1 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
8 |
TT > UE |
|
|||
|
9 |
UE > TT |
|
|||
|
10 |
UE |
|
|||
Expected Sequence B:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE > TT |
|
|||
|
2 |
TT > UE |
IMMEDIATE ASSIGNMENT |
|||
|
3 |
UE > TT |
|
|||
|
4 |
TT > UE |
LOCATION UPDATING REJECT (Cause: PLMN Not Allowed) |
|||
|
5 |
UE > USIM |
|
CR1 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
6 |
TT > UE |
|
|||
|
7 |
UE |
The UE is soft powered down. |
7.1.2.5 Acceptance criteria
CR 1 shall be verified in step 7) for Sequence A, and step 5) for Sequence B. Test environments not capable of evaluating the content of EFFPLMN while the common test procedure is executed, may verify the correct update of EFFPLMN by reading out the file at the end of the test execution. All entries generated during test execution shall be available and comply to the EF listings below, else the conformance requirement is not met.
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 001 (MCC MNC)
PLMN2: 234 002
PLMN3: 234 003
PLMN4: 234 004
PLMN5: 234 005
PLMN6: 234 006
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
14 |
00 |
32 |
24 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
54 |
00 |
32 |
64 |
00 |
Or
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 001 (MCC MNC)
PLMN2: 234 003
PLMN3: 234 004
PLMN4: 234 005
PLMN5: 234 006
PLMN6: 234 002
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
14 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
32 |
54 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
64 |
00 |
32 |
24 |
00 |
7.1.3 UE deleting forbidden PLMNs
7.1.3.1 Definition and applicability
In manual PLMN selection mode the UE allows registration attempts to all available PLMNs, including forbidden PLMNs (as indicated by the forbidden PLMN list on the USIM). As a result of a successful registration procedure onto a PLMN which is in the forbidden PLMN list, the forbidden PLMN list is automatically updated by the UE.
The registration attempts initiated by the 3G UE depends on UEs capabilities and can be one of the following:
I. registration procedures for UEs supporting CS or
II. registration procedures for UEs supporting PS or
III. registration procedures for UEs supporting CS/PS
7.1.3.2 Conformance requirement
In case of a 2G terminal:
CR 1 In manual PLMN selection mode the UE shall be able to perform a LOCATION UPDATING attempt to a PLMN which is in the forbidden PLMN list.
Reference:
– TS 22.011 [18], clause 3.2.2.2.
CR 2 After receipt of LOCATION UPDATING ACCEPT the UE shall delete the forbidden PLMN from the forbidden PLMN list.
Reference:
– TS 22.011 [18], clause 3.2.2.4.
In case of a 3G terminal:
CR 1 Depending on which domain the UE will be registered on, one of the following requirements should be fulfilled:
I. In manual PLMN selection mode the UE shall be able to perform a LOCATION UPDATING attempt during registration on CS to a PLMN which is in the forbidden PLMN list or
II. In manual PLMN selection mode the UE shall be able to perform a ATTACH attempt during registration on PS to a PLMN which is in the forbidden PLMN list or
III. In manual PLMN selection mode the UE shall be able to perform a LOCATION UPDATING and/or ATTACH attempt during registration on CS/PS to a PLMN which is in the forbidden PLMN list.
Reference:
– TS 22.011 [18], clause 3.2.2.2.
– TS 31.102 [19], clauses 5.1.1 and 5.2.7.
CR 2 Depending on which domain the UE will be registered on, one of the following requirements should be fulfilled:
I. After receipt of LOCATION UPDATING ACCEPT message during registration on CS the UE shall delete the forbidden PLMN from the forbidden PLMN list OR
II. After receipt of ATTACH ACCEPT message during registration on PS the UE shall delete the forbidden PLMN from the forbidden PLMN list or
III. After receipt of LOCATION UPDATING ACCEPT and/or ATTCH ACCEPT message during registration on CS/PS the UE shall delete the forbidden PLMN from the forbidden PLMN list.
Reference:
– TS 22.011 [18], clause 3.2.2.4.
7.1.3.3 Test purpose
1) To verify that the 2G UE is able to perform a LOCATION UPDATING on a forbidden PLMN in manual PLMN selection mode or to verify that the 3G UE is able to perform
I. LOCATION UPDATING REQUEST during registration on CS on a forbidden PLMN in manual PLMN selection mode or
II. ATTACH REQUEST during registration on PS on a forbidden PLMN in manual PLMN selection mode or
III. LOCATION UPDATING REQUEST and/or ATTACH REQUEST during registration on CS/PS on a forbidden PLMN in manual PLMN selection mode.
2) To verify that the UE after a successful registration attempt deletes the PLMN in the EFFPLMN on the USIM.
7.1.3.4 Method of test
7.1.3.4.1 Initial conditions
The USS (in case of a Terminal accessing UTRAN)/ SS (in case of a Terminal accessing a GERAN) transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 234/005/0001.
– RAI (MCC/MNC/LAC/RAC): 234/005/0001/05 (only for UTRAN cell)
– Access control: unrestricted.
NOTE: In case of a GERAN no packet system information is transmitted
Ensure that the manual PLMN selection mode is set and that the UE is using the UICC/USIM configuration defined for this test case in 31.121 [2] and runs an initial activation when executing the test procedure. The UE is switched on.
In case of a Terminal accessing UTRAN "Expected Sequence A" and in case of a Terminal accessing a GERAN "Expected Sequence B" shall be performed.
7.1.3.4.2 Procedure
Expected Sequence A:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
User > UE |
|
|||
|
2 |
UE > TT |
|
|||
|
3 |
TT > UE |
RRC CONNECTION SETUP |
|||
|
4 |
UE > TT |
|
|||
|
Depending on which domain the UE is going to be registered on, either Steps 5x, 6x or 7x will be used. |
|||||
|
5 |
UE > TT |
|
This step is followed if UE is registered on CS domain. The TT performs an authentication and starts NAS integrity protection |
CR1 |
|
|
5a |
TT > UE |
|
|||
|
5b |
UE > TT |
TMSI REALLOCATION COMPLETE |
CR2 |
||
|
5c |
UE > USIM |
Update EFFPLMN, EFLOCI |
CR3 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
6 |
UE > TT |
ATTACH REQUEST |
This step is followed if UE is registered on PS domain. The TT performs an authentication and starts NAS integrity protection |
CR1 |
|
|
6a |
TT > UE |
ATTACH ACCEPT
|
|||
|
6b |
UE > TT |
|
CR2 |
||
|
6c |
UE > USIM |
|
CR3 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
7 |
UE > TT |
|
This step is followed if UE is registered on CS/PS domain. The TT performs an authentication and starts NAS integrity protection |
CR1 |
|
|
7a |
TT > UE |
|
|||
|
7b |
UE > TT |
|
CR2 |
||
|
7c |
UE > USIM |
|
CR3 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
8 |
TT > UE |
|
|||
|
9 |
UE > TT |
|
|||
|
10 |
UE |
|
|||
Expected Sequence B:
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
User > UE |
|
|||
|
2 |
UE > TT |
|
|||
|
3 |
TT > UE |
IMMEDIATE ASSIGNMENT |
|||
|
4 |
UE > TT |
|
CR1 |
||
|
5 |
TT > UE |
LOCATION UPDATING ACCEPT
|
|||
|
6 |
UE > TT |
|
CR2 |
||
|
7 |
UE > USIM |
|
CR3 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
8 |
TT > UE |
|
|||
|
9 |
UE |
The UE is soft powered down. |
7.1.3.5 Acceptance criteria
CR 1 is met if the UE is sending LOCATION UPDATE REQUEST and/or ATTACH REQUEST in either step 5), 6), 7) of Sequence A, or LOCATION UPDATE REQUEST in step 4) of Sequence B. TT shall provide status information.
CR 2 shall be verified either in step 5b, 6b, 7b of Sequence A, or step 6 in Sequence B.
CR 3 shall be explicitly verified either in step 5c, 6c, 7c of Sequence A, or step 7 in Sequence B. Test environments not capable of evaluating the content of EFFPLMN, EFLOCI, EFPSLOCI while the common test procedure is executed, may verify the correct update of EFFPLMN, EFLOCI, EFPSLOCI by reading out the file at the end of the test execution. All entries generated during test execution shall be available and comply to the EF listings below, else the conformance requirement is not met.
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: empty
PLMN2: empty
PLMN3: empty
PLMN4: empty
PLMN5: empty
PLMN6: empty
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
FF |
FF |
FF |
FF |
FF |
FF |
EFLOCI (Location Information)
Logically:
LAI-MCC: 234
LAI-MNC: 005
TMSI: "12345678"
Coding::
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
12 |
34 |
56 |
78 |
32 |
54 |
00 |
xx |
xx |
xx |
00 |
EFPSLOCI (Location Information)
Logically:
LAI-MCC: 234
LAI-MNC: 005
TMSI: "12345678"
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
12 |
34 |
56 |
78 |
xx |
xx |
xx |
32 |
54 |
00 |
xx |
xx |
|
B13 |
B14 |
|||||||||||
|
xx |
00 |
7.1.4 Adding FPLMN to the forbidden PLMN list when accessing E‑UTRAN
7.1.4.1 Definition and applicability
A list of forbidden PLMNs stored in the USIM and providing storage for at least 4 entries is managed by the UE. In automatic PLMN selection mode the UE controls registration attempts to appropriate networks with respect to this list of forbidden PLMNs. As a result of a registration reject with the cause "PLMN not allowed" the UE stores the PLMN which rejected the update request in the USIM.
7.1.4.2 Conformance requirement
CR 1 In automatic PLMN selection mode the UE shall only attempt an AttachRequest during registration on E‑UTRAN/EPS if it receives a BCCH containing a PLMN (MCC, MNC) that is not indicated in the EFFPLMN in the USIM
Reference:
– TS 22.011 [18], clause 2.3;
– TS 31.102 [19], clauses 5.1.1 and 5.2.7.
CR 2 After receipt of an AttachReject message during registration on E-UTRAN/EPS with the EMM cause "PLMN not allowed" the ME shall update the EFFPLMN in the USIM.
Reference:
– TS 22.011 [18], clause 3.2.2 2;
– TS 31.102 [19], clauses 5.1.1 and 5.2.7
CR 3 After receipt of an AttachReject message during registration on E-UTRAN/EPS with the EMM cause "PLMN not allowed" the ME shall update the EFEPSLOCI in the USIM.
Reference:
– TS 24.301 [21], clause 5.5.1.2.5;
– TS 31.102 [19], clauses 5.1.2 and 4.2.9.1.
CR 4 After receipt of an AttachReject message during registration on E-UTRAN/EPS with the After registration on E‑UTRAN/EPS the USIM shall contain the correct GUTI and TAI received by the UE.
Reference:
– TS 31.102 [19], clauses 5.1.2 and 4.2.9.1;
– TS 21.111 [20], clause 10.1.
7.1.4.3 Test purpose
The purpose of this test is to verify that:
1) in automatic PLMN selection mode the UE does not attempt to access PLMNs stored in EFFPLMN on the USIM;
2) the EFFPLMN is correctly updated by the Terminal after receipt of an AttachReject message with cause "PLMN not allowed" during registration;
3) the EFEPSLOCI has been correctly updated by the Terminal during registration.
7.1.4.4 Method of test
7.1.4.4.1 Initial conditions
The UICC/USIM configuration defined for this test case is installed in the UE.
Ensure that the automatic PLMN selection mode is set and that the UE is using the UICC/USIM configuration defined for this test case and runs an initial activation when executing the test procedure.
7.1.4.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
TT |
Activate the RF output on the BCCH with: |
The UE does not send an AttachRequest message as the PLMN provided by the TT is listed in EFFPLMN |
CR1 |
|
|
2 |
TT |
Stop RF output on the BCCH |
The UE starts a reselection procedure |
||
|
3 |
TT |
Resume the RF output on the BCCH with: |
The UE does not send an AttachRequest message as the PLMN provided by the TT is it is listed in EFFPLMN |
CR1 |
|
|
4 |
TT |
Stop RF output on the BCCH |
The UE starts a reselection procedure |
||
|
5 |
TT |
Resume the RF output on the BCCH with: |
The UE does not send an AttachRequest message as the PLMN provided by the TT is it is listed in EFFPLMN |
CR1 |
|
|
6 |
TT |
Stop RF output on the BCCH |
The UE starts a reselection procedure |
||
|
7 |
TT |
Resume the RF output on the BCCH with: |
The UE does not send an AttachRequest message as the PLMN provided by the TT is it is listed in EFFPLMN |
CR1 |
|
|
8 |
TT |
Stop RF output on the BCCH |
The UE starts a reselection procedure |
||
|
9 |
TT |
Resume the RF output on the BCCH with: |
The UE tries to connect to the PLMN provided by the TT |
CR1 |
|
|
10 |
UE > TT |
Send RRCConnectionRequest / RRCConnectionRequest-NB |
The TT responds with a RRCConnectionSetup / RRCConnectionSetup-NB |
||
|
11 |
UE > TT |
Send RRCConnectionSetupComplete / RRCConnectionSetupComplete-NB |
|||
|
12 |
UE > TT |
Send AttachRequest |
The TT performs an authentication and starts NAS integrity protection |
||
|
13 |
TT > UE |
Send AttachReject message with cause ‘PLMN not allowed’ |
The UE updates EFFPLMN The UE updates EFEPSLOCI |
CR2 CR3 |
A.2/1 OR A.2/2 OR A.2/4 |
|
14 |
TT > UE |
Send RRCConnectionRelease / RRCConnectionRelease-NB |
|||
|
15 |
TT |
Stop RF output on the BCCH |
|||
|
16 |
UE |
Disable signalling on RAN |
|||
|
17 |
TT |
Read out EFEPSLOCI |
EFEPSLOCI content can be verified by the TT |
CR3 |
A.2/1 OR A.2/2 OR A.2/4 |
|
18 |
UE |
Enable signalling on RAN |
The UE starts a reselection procedure |
||
|
19 |
TT |
Resume the RF output on the BCCH with: |
The UE tries to connect to the PLMN provided by the TT |
CR1 |
|
|
20 |
UE > TT |
Send RRCConnectionRequest / RRCConnectionRequest-NB |
The TT responds with a RRCConnectionSetup / RRCConnectionSetup-NB |
||
|
21 |
UE > TT |
Send RRCConnectionSetupComplete / RRCConnectionSetupComplete-NB |
|||
|
22 |
UE > TT |
Send AttachRequest |
The TT performs an authentication and starts NAS integrity protection |
||
|
23 |
TT > UE |
Send AttachAccept message with: |
The UE responds with an AttachComplete message |
CR4 |
|
|
UE |
Update EFEPSLOCI |
CR3 |
A.2/1 OR A.2/2 OR A.2/4 |
||
|
24 |
TT > UE |
Send a RRCConnectionRelease / RRCConnectionRelease-NB |
7.1.4.4 Acceptance criteria
CR 1 is met if the UE is not sending an AttachRequest in steps 1), 3), 5) and 7) but in step 9) and 19) as indicated by correctly interpreted EFFPLMN content. During test execution the TT shall provide status information related to the AttachRequest.
CR 2 shall be verified in step 13). Test environments not capable of evaluating the content of EFFPLMN while the common test procedure is executed, may verify the correct update of EFFPLMN by reading out the file at the end of the test execution. All entries generated during test execution shall be available and comply to the EF listings below, else the conformance requirement is not met.
CR 3 shall be verified in step 17). Test environments not capable of evaluating the content of EFEPSLOCI while the common test procedure is executed, may verify the correct update of EFEPSLOCI by reading out the file at the end of the test execution. All entries generated during test execution shall be available and comply to the EF listings below, else the conformance requirement is not met.
CR 4 is met if the GUTI derived from EFEPSLOCI matches the GUTI generated from the TT in step 13).
EFEPSLOCI (EPS Information)
Logically:
GUTI: as generated from TT in step 13)
Last visited registered TAI: 234/007/0001
EPS update status: updated
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
0B |
F6 |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
74 |
00 |
00 |
01 |
00 |
The EFs of the USIM read after finishing the common test procedure shall contain the following values:
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 002 (MCC MNC)
PLMN2: 234 003
PLMN3: 234 004
PLMN4: 234 005
PLMN5: 234 006
PLMN6: 234 007
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
24 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
32 |
54 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
64 |
00 |
32 |
74 |
00 |
EFEPSLOCI (EPS Information)
Logically:
GUTI: as generated from TT in step 13)
Last visited registered TAI: 234/008/0001
EPS update status: updated
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
0B |
F6 |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
84 |
00 |
00 |
01 |
00 |
7.1.5 UE updating forbidden PLMNs when accessing E-UTRAN
7.1.5.1 Definition and applicability
A list of forbidden PLMNs stored in the USIM provides storage for at least 4 entries, and is managed by the UE. In automatic PLMN selection mode the UE controls registration attempts to appropriate networks with respect to this list of forbidden PLMNs. As a result of a registration reject with the cause "PLMN not allowed" the UE stores the PLMN which rejected the update request in the USIM.
7.1.5.2 Conformance requirement
CR 1 After receipt of an AttachReject message during registration with the cause "PLMN not allowed" the ME shall update the EFFPLMN in the USIM.
Reference:
– TS 22.011 [18], clause 3.2.2 4;
– TS 31.102 [19], clauses 5.1.1 and 5.2.7
7.1.5.3 Test purpose
To verify that the UE correctly updates the EFFPLMN, i.e. fill up existing gaps in the elementary file before overwriting any existing entries.
7.1.5.4 Method of test
7.1.5.4.1 Initial conditions
The defined UICC/USIM configuration defined for this test case shall be used and made available on the UE.
Ensure that the automatic PLMN selection mode is set and that the UE is using the UICC/USIM configuration defined for this test case in 31.121 [2] and runs an initial activation when executing the test procedure. The UE is switched on.
7.1.5.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE > TT |
Send RRCConnectionRequest / RRCConnectionRequest-NB |
The TT responds with a RRCConnectionSetup / RRCConnectionSetup-NB |
||
|
2 |
UE > TT |
Send RRCConnectionSetupComplete / RRCConnectionSetupComplete-NB |
|||
|
3 |
UE > TT |
Send AttachRequest |
The TT performs an authentication and starts NAS integrity protection |
||
|
4 |
TT > UE |
Send AttachReject message with cause ‘PLMN not allowed’ |
The UE updates EFFPLMN |
CR1 |
A.2/1 OR A.2/2 OR A.2/4 |
|
5 |
TT > UE |
Send RRCConnectionRelease / RRCConnectionRelease-NB |
|||
|
6 |
User > UE |
UE is soft powered down |
7.1.5.5 Acceptance criteria
CR 1 shall be verified in step 4 after receiving AttachReject. Test environments not capable of evaluating the content of EFFPLMN while the common test procedure is executed, may verify the correct update of EFFPLMN by reading out the file at the end of the test execution. All entries generated during test execution shall be available and comply to the EF listings below, else the conformance requirement is not met.
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 001 (MCC MNC)
PLMN2: 234 002
PLMN3: 234 003
PLMN4: 234 004
PLMN5: 234 005
PLMN6: 234 006
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
14 |
00 |
32 |
24 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
54 |
00 |
32 |
64 |
00 |
Or
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 001 (MCC MNC)
PLMN2: 234 003
PLMN3: 234 004
PLMN4: 234 005
PLMN5: 234 006
PLMN6: 234 002
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
14 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
32 |
54 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
64 |
00 |
32 |
24 |
00 |
7.1.6 UE deleting forbidden PLMNs when accessing E-UTRAN
7.1.6.1 Definition and applicability
In manual PLMN selection mode the UE allows registration attempts to all available PLMNs, including forbidden PLMNs (as indicated by the forbidden PLMN list on the USIM). As a result of a successful registration procedure onto a PLMN which is in the forbidden PLMN list, the forbidden PLMN list is automatically updated by the UE.
7.1.6.2 Conformance requirement
CR 1 In manual PLMN selection mode the UE shall be able to perform a ATTACH attempt during registration to a PLMN which is in the forbidden PLMN list.
Reference:
– TS 22.011 [18], clause 3.2.2.2;
– TS 31.102 [19], clauses 5.1.1 and 5.2.7.
CR 2 After receipt of AttachAccept message during registration the UE shall delete the forbidden PLMN from the forbidden PLMN list.
Reference:
– TS 22.011 [18], clause 3.2.2.4;
7.1.6.3 Test purpose
1) To verify that the terminal is able to perform an AttachRequest during registration on a forbidden PLMN in manual PLMN selection mode.
2) To verify that the UE after a successful registration attempt deletes the PLMN in the EFFPLMN on the USIM.
7.1.6.4 Method of test
7.1.6.4.1 Initial conditions
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 234/005/0001.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 234/005/0001.
– Access control: unrestricted.
Ensure that the manual PLMN selection mode is set and that the UE is using the UICC/USIM configuration defined for this test case in 31.121 [2] and runs an initial activation when executing the test procedure. The UE is switched on.
7.1.6.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
User > UE |
|
|||
|
2 |
UE > TT |
|
The TT responds with a RRCConnectionSetup / RRCConnectionSetup-NB |
||
|
3 |
UE > TT |
RRCConnectionSetupComplete / RRCConnectionSetupComplete-NB |
|||
|
4 |
UE > TT |
|
The TT performs an authentication and starts NAS integrity protection |
CR1 |
|
|
5 |
TT > UE |
AttachAccept message with:
|
The UE responds with an AttachComplete message |
||
|
6 |
UE > USIM |
|
CR2 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
7 |
TT > UE |
|
|||
|
8 |
UE |
The UE is soft powered down. |
7.1.6.5 Acceptance criteria
CR 1 is met if the UE is sending ATTACH REQUEST in step 4) of Sequence A. TT shall provide status information.
CR 2 shall be explicitly verified in step 6). Test environments not capable of evaluating the content of EFFPLMN , EFEPSLOCI while the common test procedure is executed, may verify the correct update of EFFPLMN , EFEPSLOCI by reading out the file at the end of the test execution. All entries generated during test execution shall be available and comply to the EF listings below, else the conformance requirement is not met.
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: empty
PLMN2: empty
PLMN3: empty
PLMN4: empty
PLMN5: empty
PLMN6: empty
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
FF |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
FF |
FF |
FF |
FF |
FF |
FF |
EFEPSLOCI (EPS Information)
Logically:
GUTI: as generated from TT in step 5)
Last visited registered TAI: 234/005/0001
EPS update status: updated
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
0B |
F6 |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
54 |
00 |
00 |
01 |
00 |
7.1.7 Updating the Forbidden PLMN list after receiving non-integrity protected reject message – UTRAN
7.1.7.1 Definition and applicability
A list of forbidden PLMNs stored in the USIM and providing storage for at least 4 entries is managed by the UE. In automatic PLMN selection mode the UE controls registration attempts to appropriate networks with respect to this list of forbidden PLMNs. As a result of a registration reject with the cause "PLMN not allowed" the UE stores the PLMN which rejected the update request in the USIM.
7.1.7.2 Conformance requirement
CR 1 After receipt of a not integrity-protected LOCATION UPDATING REJECT and/or ATTACH REJECT message during registration on CS/PS with the cause "PLMN not allowed" the Terminal shall update the EFFPLMN in the USIM thereafter that VPLMN will not be accessed by the MS in automatic mode:
– if the MS is not configured to use timer T3245, and the MS maintains a list of PLMN-specific attempt counters and the value of the PLMN-specific attempt counter for that VPLMN is equal to the MS implementation specific maximum value or;
– if the MS is not configured to use timer T3245, and the MS is not maintain a list of PLMN-specific attempt counters
Reference:
– TS 23.122 [41], clause 3.1.
– TS 22.011 [18], clause 3.2.2 2.3;
– TS 31.102 [19], clauses 5.1.1 and 5.2.7.
7.1.7.3 Test purpose
To verify in automatic PLMN selection mode and after receipt of a LOCATION UPDATING REJECT and/or ATTACH REJECT message with cause "PLMN not allowed" during registration that the UE correctly updates EFFPLMN, in the following cases:
– if the UE maintains a list of PLMN-specific attempt counters, and the value of the PLMN-specific attempt counter for that VPLMN is equal to the MS implementation specific maximum value.
– if the UE does not maintain a list of PLMN-specific attempt counters.
To verify that the UE correctly updates the EFFPLMN, i.e. fill up existing gaps in the elementary file before overwriting any existing entries.
7.1.7.4 Method of test
7.1.7.4.1 Initial conditions
The USS transmits on the BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 234/002/0001.
– RAI (MCC/MNC/LAC/RAC): 234/002/0001/05.
– Access control: unrestricted.
Ensure that the automatic PLMN selection mode is set and that the UE is using the UICC/USIM configuration defined for this test case in 31.121 [2] and runs an initial activation when executing the test procedure. The UE is switched on.
7.1.7.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE > TT |
|
Depending on which domain the UE is going to be registered on, UE attempts to perform CS, PS or CS/PS registration. |
||
|
2 |
TT > UE |
|
Not integrity protected |
||
|
3 |
If the UE supports A.1/38, perform step 4) after the expiry of timer T3247, otherwise perform step 5). |
||||
|
4 |
Using the settings declared in table B.1/AER006, repeat step 1) – 3) until the PLMN-specific attempt counters has reached the maximum value for that VPLMN |
||||
|
5 |
UE > USIM |
|
CR1 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
6 |
UE |
|
|||
7.1.7.5 Acceptance criteria
CR 1 shall be verified in step 5). Test environments not capable of evaluating the content of EFFPLMN while the common test procedure is executed, may verify the correct update of EFFPLMN by reading out the file at the end of the test execution. All entries generated during test execution shall be available and comply to the EF listings below, else the conformance requirement is not met.
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 001 (MCC MNC)
PLMN2: 234 002
PLMN3: 234 003
PLMN4: 234 004
PLMN5: 234 005
PLMN6: 234 006
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
14 |
00 |
32 |
24 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
54 |
00 |
32 |
64 |
00 |
Or
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 001 (MCC MNC)
PLMN2: 234 003
PLMN3: 234 004
PLMN4: 234 005
PLMN5: 234 006
PLMN6: 234 002
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
14 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
32 |
54 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
64 |
00 |
32 |
24 |
00 |
7.1.8 Updating the Forbidden PLMN list after receiving non-integrity protected reject message – E-UTRAN
7.1.8.1 Definition and applicability
A list of forbidden PLMNs stored in the USIM and providing storage for at least 4 entries is managed by the UE. In automatic PLMN selection mode the UE controls registration attempts to appropriate networks with respect to this list of forbidden PLMNs. As a result of a registration reject with the cause "PLMN not allowed" the UE stores the PLMN which rejected the update request in the USIM.
7.1.8.2 Conformance requirement
CR 1 After receipt of a not integrity-protected ATTACH REJECT message during registration with the cause "PLMN not allowed" the Terminal shall update the EFFPLMN in the USIM thereafter that VPLMN will not be accessed by the MS in automatic mode:
– if the MS is not configured to use timer T3245, and the MS maintains a list of PLMN-specific attempt counters and the value of the PLMN-specific attempt counter for that VPLMN is equal to the MS implementation specific maximum value or;
– if the MS is not configured to use timer T3245, and the MS is not maintain a list of PLMN-specific attempt counters
Reference:
– TS 23.122 [41], clause 3.1.
– TS 22.011 [18], clause 3.2.2 2.3;
– TS 31.102 [19], clauses 5.1.1 and 5.2.7.
7.1.8.3 Test purpose
To verify in automatic PLMN selection mode and after receipt of ATTACH REJECT message with cause "PLMN not allowed" during registration that the UE correctly updates EFFPLMN, in the following cases:
– if the UE maintains a list of PLMN-specific attempt counters, and the value of the PLMN-specific attempt counter for that VPLMN is equal to the MS implementation specific maximum value;
– if the UE does not maintain a list of PLMN-specific attempt counters.
To verify that the UE correctly updates the EFFPLMN, i.e. fill up existing gaps in the elementary file before overwriting any existing entries.
7.1.8.4 Method of test
7.1.8.4.1 Initial conditions
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 234/002/0001.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 234/002/0001.
– Access control: unrestricted.
Ensure that the automatic PLMN selection mode is set and that the UE is using the UICC/USIM configuration defined for this test case in 31.121 [2] and runs an initial activation when executing the test procedure. The UE is switched on.
7.1.8.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE > TT |
|
TT responds with a RRCConnectionSetup / RRCConnectionSetup-NB |
||
|
2 |
UE > TT |
|
|||
|
3 |
UE > TT |
|
|||
|
4 |
TT > UE |
|
Not integrity protected |
||
|
5 |
TT > UE |
|
|||
|
6 |
If the UE supports A.1/38, perform step 7) after the expiry of timer T3247, otherwise perform step 8). |
||||
|
7 |
Using the settings declared in table B.1/AER006, repeat step 1) – 6) until the PLMN-specific attempt counters has reached the maximum value for that VPLMN |
||||
|
8 |
UE > USIM |
|
CR1 |
A.2/1 OR A.2/2 OR A.2/4 |
|
|
9 |
UE |
|
|||
7.1.8.5 Acceptance criteria
CR 1 shall be verified in step 8). Test environments not capable of evaluating the content of EFFPLMN while the common test procedure is executed, may verify the correct update of EFFPLMN by reading out the file at the end of the test execution. All entries generated during test execution shall be available and comply to the EF listings below, else the conformance requirement is not met.
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 001 (MCC MNC)
PLMN2: 234 002
PLMN3: 234 003
PLMN4: 234 004
PLMN5: 234 005
PLMN6: 234 006
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
14 |
00 |
32 |
24 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
54 |
00 |
32 |
64 |
00 |
Or
EFFPLMN (Forbidden PLMNs)
Logically:
PLMN1: 234 001 (MCC MNC)
PLMN2: 234 003
PLMN3: 234 004
PLMN4: 234 005
PLMN5: 234 006
PLMN6: 234 002
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
B12 |
|
Hex |
32 |
14 |
00 |
32 |
34 |
00 |
32 |
44 |
00 |
32 |
54 |
00 |
|
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||||
|
32 |
64 |
00 |
32 |
24 |
00 |
7.2 User controlled PLMN selector handling
7.2.1 UE updating the User controlled PLMN selector list
RFU – currently no system simulator involved – agreed method to verify the EF_PLMwACT on test case end needed.
7.2.2 UE recognizing the priority order of the User controlled PLMN selector list with the same access Technology
TBD for the first release of the present document. Agreement on alternative verification of EF_LOCI/EF_PSLOCI contents needed.
7.2.3 UE recognizing the priority order of the User controlled PLMN selector list using an ACT Preference
TBD for the first release of the present document. Agreement on alternative verification of EF_LOCI/EF_PSLOCI contents needed.
7.2.4 Void
7.2.5 UE updating the User controlled PLMN selector list for E-UTRAN
RFU – currently no system simulator involved – agreed method to verify the EF_PLMwACT on test case end needed.
7.2.6 UE recognizing the priority order of the User controlled PLMN selector list using an ACT preference – UTRAN/E-UTRAN
TBD for the first release of the present document. Agreement on alternative verification of EF_EPSLOCI contents needed.
7.2.7 UE recognizing the priority order of the User controlled PLMN selector list using an ACT preference – GSM/E-UTRAN
TBD for the first release of the present document. Agreement on alternative verification of EF_EPSLOCI contents needed.
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
TBD for the first release of the present document
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
TBD for the first release of the present document
7.3 Operator controlled PLMN selector handling
7.3.1 UE recognizing the priority order of the Operator controlled PLMN selector list
TBD for the first release of the present document. Agreement on alternative verification of EF_LOCI/EF_PSLOCI contents needed.
7.3.2 UE recognizing the priority order of the User controlled PLMN selector over the Operator controlled PLMN selector list
TBD for the first release of the present document. Agreement on alternative verification of EF_LOCI/EF_PSLOCI contents needed.
7.3.3 UE recognizing the priority order of the Operator controlled PLMN selector list when accessing E-UTRAN
TBD for the first release of the present document. Agreement on alternative verification of EF_LOCI/EF_PSLOCI contents needed.
7.3.4 UE recognizing the priority order of the User controlled PLMN selector over the Operator controlled PLMN selector list – E-UTRAN
TBD for the first release of the present document. Agreement on alternative verification of EF_EPSLOCI contents needed.
7.4 Higher priority PLMN search handling
7.4.1 UE recognizing the search period of the Higher priority PLMN
TBD for the first release of the present document. Agreement on alternative verification of EF_LOCI/EF_PSLOCI contents needed.
7.4.2 GSM/UMTS dual mode UEs recognizing the search period of the Higher priority PLMN
TBD for the first release of the present document. Agreement on alternative verification of EF_LOCI/EF_PSLOCI contents needed.
7.4.3 UE recognizing the search period of the Higher priority PLMN – E‑UTRAN
TBD for the first release of the present document. Agreement on alternative verification of EF_EPSLOCI contents needed.
7.4.4 E-UTRAN/EPC capable UEs recognizing the search period of the Higher priority PLMN – GSM/E-UTRAN
TBD for the first release of the present document. Agreement on alternative verification of EF_EPSLOCI contents needed.
7.4.5 E-UTRAN/EPC capable UEs recognizing the search period of the Higher priority PLMN – UTRAN/E-UTRAN
TBD for the first release of the present document. Agreement on alternative verification of EF_EPSLOCI contents needed.