5.1 IMSI / TMSI handling
31.1213GPPRelease 16TSUICC-terminal interfaceUniversal Subscriber Identity Module (USIM) application test specification
5.1.1 UE identification by short IMSI
5.1.1.1 Definition and applicability
The IMSI is used for unique identification of the UE by UTRAN/ a GERAN. The IMSI is stored in the USIM and read during the UICC-Terminal initialisation procedure.
5.1.1.2 Conformance requirement
After successful completion of the RRC Connection Establishment procedure (in case of Terminals accessing UTRAN) respectively after receipt of an IMMEDIATE ASSIGNMENT message (in case of a Terminal accessing a GERAN) the UE shall send PAGING RESPONSE/ ATTACH REQUEST containing the IMSI of the USIM, which is less than the maximum length.
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– TS 24.008 [16], clause 10.5.1.4 and 4.7.9.1.2;
– ETSI TS 102 221 [5], clause 14.1.1.
5.1.1.3 Test purpose
1) To verify that the Terminal uses the IMSI of the USIM.
2) To verify that the Terminal can handle an IMSI of less than the maximum length.
3) To verify that the READ EFIMSI command is performed correctly by the terminal
5.1.1.4 Method of test
5.1.1.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): 246/081/0001.
– RAI (MCC/MNC/LAC/RAC): 246/081/0001/05. (only for UTRAN cell)
– Access control: unrestricted.
The default UICC is installed into the Terminal and the UE is powered on. In case PS is supported and active the ME performs a GPRS attach procedure, this will be accepted by the USS.
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.
5.1.1.4.2 Procedure
Expected Sequence A:
a) The USS sends PAGING TYPE 1 in the CS domain if supported by the ME or where CS is not supported by the ME, in PS domain to the UE using the IMSI stored in the USIM.
b) After receipt of a RRC CONNECTION REQUEST from the UE, the USS sends RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS.
c) After receipt of a PAGING RESPONSE in case paging in CS domain or an ATTACH REQUEST in case of PS domain from the UE, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
Expected Sequence B:
a) The SS sends PAGING REQUEST to the UE using the IMSI stored in the USIM.
b) After receipt of a CHANNEL REQUEST from the UE, the SS sends IMMEDIATE ASSIGNMENT to the UE.
c) After receipt of a PAGING RESPONSE from the UE, the SS sends CHANNEL RELEASE to the UE.
5.1.1.5 Acceptance criteria
After step b) the UE shall send PAGING RESPONSE or ATTACH REQUEST to the USS/SS containing the IMSI stored in the USIM.
5.1.2 UE identification by short IMSI using a 2 digit MNC
5.1.2.1 Definition and applicability
In some networks the IMSI identifying the UTRAN/ GERAN can be consistence of a 2 digit MNC. The IMSI is stored in the USIM and read during the UICC-Terminal initialisation procedure.
5.1.2.2 Conformance requirement
After successful completion of the RRC Connection Establishment procedure (in case of Terminals accessing UTRAN) respectively after receipt of an IMMEDIATE ASSIGNMENT message (in case of a Terminal accessing a GERAN) the UE shall send PAGING RESPONSE/ ATTACH REQUEST containing the IMSI of the USIM.
Reference:
– TS 31.102 [4], clause 4.2.18;
– TS 24.008 [16], clause 10.5.1.4 and 4.7.9.1.2.
5.1.2.3 Test purpose
1) To verify that the Terminal can handle an IMSI consistence of a 2 digit MNC.
5.1.2.4 Method of test
5.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): 246/81/0001.
– RAI (MCC/MNC/LAC/RAC): 246/81/0001/05. (only for UTRAN cell)
– Access control: unrestricted.
The default UICC is used with the following exception:
EFLOCI (Location Information)
Logically: LAI-MCC: 246
LAI-MNC: 81
LAI-LAC: 0001
TMSI: "FF .. FF"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
FF |
FF |
FF |
FF |
42 |
F6 |
18 |
00 |
01 |
FF |
00 |
EFIMSI (IMSI)
Logically: 246813579
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
|
Hex |
05 |
29 |
64 |
18 |
53 |
97 |
FF |
FF |
FF |
EFAD (Administrative Data)
Logically: Normal operation
OFM to be deactivated by the Terminal
MNC: 2 digit
|
Coding: |
B1 |
B2 |
B3 |
B4 |
|
Hex |
00 |
00 |
00 |
02 |
The UICC is installed into the Terminal and the UE is powered on. In case PS is supported and active the ME performs a GPRS attach procedure, this will be accepted by the USS.
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.
5.1.2.4.2 Procedure
Expected Sequence A:
a) The USS sends PAGING TYPE 1 in the CS domain if supported by the ME or where CS is not supported by the ME, in PS domain to the UE using the IMSI stored in the USIM.
b) After receipt of a RRC CONNECTION REQUEST from the UE, the USS sends RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS.
c) After receipt of a PAGING RESPONSE in the case of paging in CS domain or an ATTACH REQUEST in the case of PS domain from the UE, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
Expected Sequence B:
a) The SS sends PAGING REQUEST to the UE using the IMSI stored in the USIM.
b) After receipt of a CHANNEL REQUEST from the UE, the SS sends IMMEDIATE ASSIGNMENT to the UE.
c) After receipt of a PAGING RESPONSE from the UE, the SS sends CHANNEL RELEASE to the UE.
5.1.2.5 Acceptance criteria
After step b) the UE shall send PAGING RESPONSE or ATTACH REQUEST to the USS/SS containing the IMSI stored in the USIM.
5.1.3 UE identification by "short" TMSI
5.1.3.1 Definition and applicability
The TMSI is temporarily used for identification of the UE by UTRAN/ a GERAN. It will have been previously assigned by the network. The TMSI is stored in the USIM by the Terminal and read during the USIM-Terminal initialisation procedure.
NOTE: According to TS 23.003 [14], clause 2.4, a TMSI always consists of 8 digits (4 bytes). With this tests the handling of a TMSI with leading zeros will be tested. The term "short" TMSI is used in order to distinguish between the tests as defined in clauses 5.1.3 and 5.1.4.
5.1.3.2 Conformance requirement
After successful completion of the RRC Connection Establishment procedure (in case of Terminals accessing UTRAN) respectively after receipt of an IMMEDIATE ASSIGNMENT message (in case of a Terminal accessing a GERAN) the UE shall send PAGING RESPONSE containing the TMSI of the USIM. According to clause 10.3.1.17 in TS 25.331 [20] the TMSI has a fixed length of 32 bit (8 digits) when used inside the PAGING TYPE 1/ PAGING REQUEST message.
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– TS 24.008 [16], clause 10.5.1.4.
– TS 25.331 [20], clause 10.3.1.17
5.1.3.3 Test purpose
1) To verify that the Terminal uses the TMSI stored in the USIM.
2) To verify that the Terminal can handle a TMSI of less than maximum length.
5.1.3.4 Method of test
5.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): 246/081/0001.
– Access control: unrestricted.
The default UICC is used with the following exception:
EFLOCI (Location Information)
Logically: LAI-MCC: 246
LAI-MNC: 081
LAI-LAC: 0001
TMSI: "00002143"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
00 |
00 |
21 |
43 |
42 |
16 |
80 |
00 |
01 |
FF |
00 |
The UICC is installed into the Terminal and the UE is powered 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.
5.1.3.4.2 Procedure
Expected Sequence A:
a) The USS sends PAGING TYPE 1 to the UE using the TMSI stored in the USIM matching the required length of 8 digits.
b) After receipt of a RRC CONNECTION REQUEST from the UE, the USS sends RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS.
c) After receipt of a PAGING RESPONSE from the UE, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
Expected Sequence B:
a) The SS sends PAGING REQUEST to the UE using the TMSI stored in the USIM matching the required length of 8 digits.
b) After receipt of a CHANNEL REQUEST from the UE, the SS sends IMMEDIATE ASSIGNMENT to the UE.
c) After receipt of a PAGING RESPONSE from the UE, the SS sends CHANNEL RELEASE to the UE.
5.1.3.5 Acceptance criteria
After step b) the UE shall send PAGING RESPONSE to the USS/SS containing the TMSI stored in the USIM.
5.1.4 UE identification by "long" TMSI
5.1.4.1 Definition and applicability
The TMSI is temporarily used for identification of the UE by UTRAN/ a GERAN. It will have been previously assigned by the network. The TMSI is stored in the USIM by the Terminal and read during the USIM-Terminal initialisation procedure.
NOTE: According to TS 23.003 [14], clause 2.4, a TMSI always consists of 8 digits (4 bytes). With this tests the handling of a new assigned TMSI will be tested. The term "long" TMSI is used in order to distinguish between the tests as defined in clauses 5.1.3 and 5.1.4.
5.1.4.2 Conformance requirement
After successful completion of the RRC Connection Establishment procedure (in case of Terminals accessing UTRAN) respectively after receipt of an IMMEDIATE ASSIGNMENT message (in case of a Terminal accessing a GERAN) the UE shall send PAGING RESPONSE containing the correct TMSI stored in the USIM.
According to clause 10.3.1.17 in TS 25.331 [20] the TMSI has a fixed length of 32 bit (8 digits) when used inside the PAGING TYPE 1/PAGING REQUEST message.
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– TS 24.008 [16], clause 10.5.1.4.
– TS 25.331 [20], clause 10.3.1.17
5.1.4.3 Test purpose
1) To verify that the Terminal uses the TMSI stored in the USIM.
2) To verify that the Terminal can handle a TMSI of maximum length.
3) To verify that the Terminal does not respond to page requests containing a previous TMSI.
5.1.4.4 Method of test
5.1.4.4.1 Initial conditions
Prior to this test, the Terminal shall have been operated with a USIM containing TMSI "2143". This may be achieved by executing the previous test (5.1.3) prior to this test. Only under this condition will test purpose 3) be verified.
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): 246/081/0001.
– Access control: unrestricted.
The default UICC is used with the following exception:
EFLOCI (Location Information)
Logically: LAI-MCC: 246
LAI-MNC: 081
LAI-LAC: 0001
TMSI: "21430000"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
21 |
43 |
00 |
00 |
42 |
16 |
80 |
00 |
01 |
FF |
00 |
The UICC is installed into the Terminal and the UE is powered 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.
5.1.4.4.2 Procedure
Expected Sequence A:
a) The USS sends PAGING TYPE 1 to the UE using the TMSI "00002143".
b) The USS sends PAGING TYPE 1 to the UE using the TMSI stored in the USIM.
c) After receipt of a RRC CONNECTION REQUEST from the UE, the USS sends RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS.
d) After receipt of a PAGING RESPONSE from the UE, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
Expected Sequence B:
a) The SS sends PAGING REQUEST to the UE using the TMSI "00002143".
b) The SS sends PAGING REQUEST to the UE using the TMSI stored in the USIM.
c) After receipt of a CHANNEL REQUEST from the UE, the SS sends IMMEDIATE ASSIGNMENT to the UE.
d) After receipt of a PAGING RESPONSE from the UE, the SS sends CHANNEL RELEASE to the UE.
5.1.4.5 Acceptance criteria
1) After step a) the UE shall not respond to the PAGING TYPE 1 respectively to the PAGING REQUEST.
2) After step c) the UE shall send PAGING RESPONSE to the USS/ SS containing the TMSI stored in the USIM.
5.1.5 UE identification by long IMSI, TMSI updating and key set identifier assignment
5.1.5.1 Definition and applicability
The IMSI and TMSI are used for identification of the UE by UTRAN/ a GERAN. They are read from the USIM during the USIM-Terminal initialisation procedure. Within the authentication procedure the UTRAN sends a key set identifier respectively a GERAN sends a ciphering key sequence number to the UE. In addition the network may allocate a new TMSI to the UE. Key set identifier and TMSI are stored in the USIM after UTRAN call termination and/or at a 3G session termination. Ciphering key sequence number and TMSI are stored in the USIM after GERAN call termination and/or at a 3G session termination.
NOTE: According to TS 24.008 [16] the term KSI may be used instead of the term ciphering key sequence number which is used inside the MM message AUTHENTICATION REQUEST.
5.1.5.2 Conformance requirement
1) After successful completion of the RRC Connection Establishment procedure (in case of Terminals accessing UTRAN) respectively after receipt of an IMMEDIATE ASSIGNMENT message (in case of a Terminal accessing a GERAN) the UE shall send PAGING RESPONSE containing the correct IMSI stored in the USIM.
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– TS 24.008 [16], clause 10.5.1.4.
2) After call termination the USIM shall contain the key set identifier (ciphering key sequence number) and TMSI received by the UE during the authentication and TMSI reallocation procedures.
Reference:
– TS 31.102 [4], clauses 5.1.2, 5.2.5 and 5.2.6;
– TS 21.111 [19], clause 10.1.
– TS 24.008 [16], clause 4.3.2.4.
3) After call termination the Terminal shall have updated EFLOCI.
Reference:
– ETSI TS 102 221 [5], clause 14.1.2.
5.1.5.3 Test purpose
1) To verify that the Terminal uses the IMSI stored in the USIM.
2) To verify that the Terminal does not respond to page requests containing a previous IMSI.
3) To verify that the Terminal can handle an IMSI of maximum length.
4) To verify that the Terminal correctly updates the key set identifier respectively the ciphering key sequence number at call termination.
5) To verify that the Terminal correctly updates the TMSI at call termination.
6) To verify that the UPDATE EFLOCI command is performed correctly by the terminal
5.1.5.4 Method of test
5.1.5.4.1 Initial conditions
Prior to this test, the Terminal shall have been operated with a USIM containing IMSI "2460813579". This may be achieved by executing the previous test (5.1.4) prior to this test. Only under this condition will test purpose 2) be verified.
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): 246/081/0001.
– Access control: unrestricted.
The default UICC is used with the following exception:
EFIMSI (IMSI)
Logically: 246081111111111
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
|
Hex |
08 |
29 |
64 |
80 |
11 |
11 |
11 |
11 |
11 |
EFKc (GSM Ciphering Key Kc)
Logically: Ciphering key Kc: xx
Ciphering key sequence number n: 01
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
|
Hex |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
xx |
01 |
The UICC is installed into the Terminal and the UE is powered 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.
5.1.5.4.2 Procedure
Expected Sequence A:
a) The USS sends PAGING TYPE 1 to the UE using the IMSI "2460813579".
b) The USS sends PAGING TYPE 1 to the UE using the IMSI stored in the USIM.
c) After receipt of a RRC CONNECTION REQUEST from the UE, the USS sends RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS.
d) After receipt of a PAGING RESPONSE from the UE, the USS sends AUTHENTICATION REQUEST to the UE containing Key Set Identifier KSI (ciphering key sequence number) set to binary 010.
e) After receipt of AUTHENTICATION RESPONSE from the UE and subsequent completion of the security procedure on RRC, the USS sends TMSI REALLOCATION COMMAND to the UE containing TMSI "32547698".
f) Within 5 s after receipt of TMSI REALLOCATION COMPLETE from the UE, the USS sends RRC CONNECTION RELEASE to the UE.
g) To allow examination of the values in the USIM after connection termination the UE shall not be soft powered down. If the test is performed with a USIM simulator, the simulation is stopped. If the test is performed with a USIM, the UICC is removed without soft powering down the UE. If this is not possible, the power supply of the Terminal is removed and then the UICC removed.
Expected sequence B:
a) The SS sends PAGING REQUEST to the UE using the IMSI "2460813579".
b) The SS sends PAGING REQUEST to the UE using the IMSI stored in the USIM.
c) After receipt of a CHANNEL REQUEST from the UE, the SS sends IMMEDIATE ASSIGNMENT to the UE.
d) After receipt of a PAGING RESPONSE from the UE, the SS sends AUTHENTICATION REQUEST to the UE containing ciphering key sequence number set to binary 010.
e) After receipt of AUTHENTICATION RESPONSE from the UE, the SS sends TMSI REALLOCATION COMMAND to the UE containing TMSI "32547698".
f) Within 5 s after receipt of TMSI REALLOCATION COMPLETE from the UE, the SS sends CHANNEL RELEASE to the UE.
g) To allow examination of the values in the USIM after connection termination the UE shall not be soft powered down. If the test is performed with a USIM simulator, the simulation is stopped. If the test is performed with a USIM, the UICC is removed without soft powering down the UE. If this is not possible, the power supply of the Terminal is removed and then the UICC removed.
5.1.5.5 Acceptance criteria
1) After step a) the UE shall not respond to the PAGING TYPE 1/ PAGING REQUEST.
2) After step c) the UE shall send PAGING RESPONSE to the USS/SS containing the IMSI stored in the USIM.
3) After step e) the UE shall send TMSI REALLOCATION COMPLETE to the USS/SS.
4) After step g) the USIM shall contain the following values:
EFLOCI (Location Information)
Logically: LAI-MCC: 246
LAI-MNC: 081
TMSI: "32547698"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
32 |
54 |
76 |
98 |
42 |
16 |
80 |
xx |
xx |
xx |
00 |
In case of a Terminal accessing UTRAN:
EFKeys (Ciphering and Integrity Keys)
Logically: Key Set Identifier KSI: 02
Ciphering Keys CK: xx (result of the authentication algorithm)
Integrity Keys IK: xx (result of the authentication algorithm)
|
Coding: |
B1 |
B2 |
B3 |
… |
B16 |
B17 |
B18 |
… |
B31 |
B32 |
B33 |
|
Hex |
02 |
xx |
xx |
… |
xx |
xx |
xx |
… |
xx |
xx |
xx |
In case of a Terminal accessing a GERAN:
EFKc (GSM Ciphering Key Kc)
Logically: Ciphering key Kc: xx (result of the authentication algorithm)
Ciphering key sequence number n: 02
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
|
Hex |
xx |
xx |
xx |
xx |
Xx |
xx |
xx |
xx |
02 |
5.1.6 UE identification by short IMSI when accessing E-UTRAN/EPC
5.1.6.1 Definition and applicability
Paging for EPS services using IMSI is an abnormal procedure used for error recovery in the network. The IMSI is used for unique identification of the UE by an E-UTRAN/EPC if there is no GUTI available. The IMSI is stored in the USIM and read during the UICC-Terminal initialisation procedure.
5.1.6.2 Conformance requirement
Only after reception of a Paging message containing the IMSI stored in the USIM the UE shall send the RRCConnectionRequest message.
For NB-IoT, the paging message shall include a CN domain indicator set to "PS". If the paging message includes a UE Paging Identity set to the UE’s IMSI, the paging procedure is performed according to clause 5.6.2.2.2 [26].
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– ETSI TS 102 221 [5], clause 14.1.1;
– TS 24.301 [26], clause 5.6.2.2.2, 5.6.2.4.
5.1.6.3 Test purpose
1) To verify that the Terminal uses the IMSI of the USIM.
2) To verify that the Terminal can handle an IMSI of less than the maximum length.
3) To verify that the READ EFIMSI command is performed correctly by the terminal.
4) To verify that the terminal does not respond to a Paging message containing an IMSI not stored in the USIM.
5.1.6.4 Method of test
5.1.6.4.1 Initial conditions
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The default E-UTRAN UICC is installed into the Terminal and the UE is powered on.
5.1.6.4.2 Procedure
a) The UE performs Attach procedure to E-USS/NB-SS.
b) The E-USS/NB-SS sends Paging/Paging-NB to the UE using the IMSI 24608122222.
c) The E-USS/NB-SS sends Paging/Paging-NB to the UE using the IMSI stored in the USIM.
d) After receipt of a RRCConnectionRequest/RRCConnectionRequest-NB message from the UE, the E-USS/NB-SS sends RRCConnectionSetup/RRCConnectionSetup-NB message to the UE, followed by RRCConnectionSetupComplete/RRCConnectionSetupComplete-NB sent by the UE to the E-USS/NB-SS.
e) After the EPS attach procedure the E-USS/NB-SS sends RRCConnectionRelease/RRCConnectionRelease-NB to the UE.
5.1.6.5 Acceptance criteria
1) After step b) the UE shall not send RRCConnectionRequest/RRCConnectionRequest-NB to the E-USS/NB-SS.
2) After step c) the UE shall send RRCConnectionRequest/RRCConnectionRequest-NB to the E-USS/NB-SS.
3) After step d) the UE performs the EPS attach procedure.
5.1.7 UE identification by short IMSI using a 2 digit MNC when accessing E-UTRAN/EPC
5.1.7.1 Definition and applicability
In some networks the IMSI identifying the E-UTRAN/EPC can be consistence of a 2 digit MNC. Paging for EPS services using IMSI is an abnormal procedure used for error recovery in the network. The IMSI is used for unique identification of the UE by an E-UTRAN/EPC if there is no GUTI available. The IMSI is stored in the USIM and read during the UICC-Terminal initialisation procedure.
5.1.7.2 Conformance requirement
Only after reception of a Paging message containing the IMSI stored in the USIM the UE shall send the RRCConnectionRequest message.
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– ETSI TS 102 221 [5], clause 14.1.1;
– TS 24.301 [26], clause 5.6.2.2.2, 5.6.2.4.
5.1.7.3 Test purpose
1) To verify that the Terminal uses the IMSI of the USIM.
2) To verify that the Terminal can handle an IMSI consistence of a 2 digit MNC.
3) To verify that the READ EFIMSI command is performed correctly by the terminal.
4) To verify that the terminal does not respond to a Paging message containing an IMSI not stored in the USIM.
5.1.7.4 Method of test
5.1.7.4.1 Initial conditions
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/81/0001.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/81/0001.
– Access control: unrestricted.
The default UICC is used with the following exception:
EFIMSI (IMSI)
Logically: 246813579
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
|
Hex |
05 |
29 |
64 |
18 |
53 |
97 |
FF |
FF |
FF |
EFAD (Administrative Data)
Logically: Normal operation
OFM to be deactivated by the Terminal
MNC: 2 digit
|
Coding: |
B1 |
B2 |
B3 |
B4 |
|
Hex |
00 |
00 |
00 |
02 |
The UICC is installed into the Terminal and the UE is powered on.
5.1.7.4.2 Procedure
a) The UE performs Attach procedure to E-USS/NB-SS.
b) The E-USS/NB-SS sends Paging/Paging-NB to the UE using the IMSI 24608122222.
c) The E-USS/NB-SS sends Paging/Paging-NB to the UE using the IMSI stored in the USIM.
d) After receipt of a RRCConnectionRequest/RRCConnectionRequest-NB message from the UE, the E-USS/NB-SS sends RRCConnectionSetup/RRCConnectionSetup-NB message to the UE, followed by RRCConnectionSetupComplete/RRCConnectionSetupComplete-NB sent by the UE to the E-USS/NB-SS.
e) After the EPS attach procedure the E-USS/NB-SS sends RRCConnectionRelease/RRCConnectionRelease-NB to the UE.
5.1.7.5 Acceptance criteria
1) After step b) the UE shall not send RRCConnectionRequest/RRCConnectionRequest-NB to the E-USS/NB-SS.
2) After step c) the UE shall send RRCConnectionRequest/RRCConnectionRequest-NB to the E-USS/NB-SS.
3) After step d) the UE performs the EPS attach procedure.
5.1.8 UE identification after changed IMSI with service "EMM Information" not available
5.1.8.1 Definition and applicability
The attach procedure is used to attach for packet services in EPS. With a successful attach procedure, a context is established for the UE in the MME, and a default bearer is established between the UE and the PDN GW, thus enabling always-on IP connectivity to the UE. The network may also initiate the activation of dedicated bearers as part of the attach procedure.For NB-IoT terminals the establishment of the PDN connection is optional.
5.1.8.2 Conformance requirement
The following EMM parameters shall be stored on the USIM if the corresponding file is present:
– GUTI;
– last visited registered TAI;
– EPS update status.
If the corresponding file is not present on the USIM, these EMM parameters except allowed CSG list are stored in a non-volatile memory in the ME together with the IMSI from the USIM. These EMM parameters can only be used if the IMSI from the USIM matches the IMSI stored in the non-volatile memory; else the UE shall delete the EMM parameters.
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– TS 24.301 [26], clause 5.5.1.2.1, 5.5.1.2.2, 5.5.1.2.4 and Annex C.
5.1.8.3 Test purpose
1) To verify that UE deletes existing EMM parameters from the UE’s non-volatile memory in case a different IMSI is activated.
2) To verify that UE includes the IMSI stored in the USIM during the attach procedure.
5.1.8.4 Method of test
5.1.8.4.1 Initial conditions
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The default UICC (without the service "EMM Information") is installed into the Terminal and the UE is powered on.
5.1.8.4.2 Procedure
a) The UE is switched on.
b) The UE requests RRC Connection and therefore performs EPS Attach procedure to the E-USS/NB-SS. The E-USS/NB-SS sends AttachAccept with the following values:
GUTI: "24608100010266345678"
TAI (MCC/MNC/TAC): 246/081/0001
c) The UE send AttachComplete.
d) The E-USS/NB-SS requests the release of the RRC Connection.
e) The UE is switched off.
f) A new UICC with the following configuration is activated:
The default UICC with the following exception: The IMSI is set to "246081222233333".
g) The Terminal is switched on.
h) The UE requests RRC Connection and therefore performs EPS Attach procedure to the E-USS/NB-SS.
5.1.8.5 Acceptance criteria
1) After step a) the UE shall read EFUST.
2) During step h) the UE shall include the IMSI "246081222233333", but no GUTI nor TAI in the AttachRequest message.
5.1.9 UE identification by GUTI when using USIM with service "EMM Information" not available
The attach procedure is used to attach for packet services in EPS. With a successful attach procedure, a context is established for the UE in the MME, and a default bearer is established between the UE and the PDN GW, thus enabling always-on IP connectivity to the UE. The network may also initiate the activation of dedicated bearers as part of the attach procedure. For NB-IoT terminals the establishment of the PDN connection is optional.
5.1.9.2 Conformance requirement
The following EMM parameters shall be stored on the USIM if the corresponding file is present:
– GUTI;
– last visited registered TAI;
– EPS update status.
If the corresponding file is not present on the USIM, these EMM parameters except allowed CSG list are stored in a non-volatile memory in the ME together with the IMSI from the USIM. These EMM parameters can only be used if the IMSI from the USIM matches the IMSI stored in the non-volatile memory; else the UE shall delete the EMM parameters.
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– TS 24.301 [26], clause 5.5.1.2.1, 5.5.1.2.2, 5.5.1.2.4 and Annex C.
5.1.9.3 Test purpose
1) To verify that UE stores the GUTI and the TAI in the UE’s non-volatile memory.
2) To verify that the UE uses the GUTI and the TAI from the UE’s non-volatile memory during the attach procedure if the IMSI stored in the USIM has not changed.
5.1.9.4 Method of test
5.1.9.4.1 Initial conditions
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The default UICC (without the service "EMM Information") is installed into the Terminal and the UE is powered on.
5.1.9.4.2 Procedure
a) The UE is switched on.
b) The UE requests RRC Connection and therefore performs EPS Attach procedure to the E-USS/NB-SS. The E-USS/NB-SS sends AttachAccept with the following values:
GUTI: "24608100010266345699"
TAI (MCC/MNC/TAC): 246/081/0001
c) The UE send AttachComplete.
d) The E-USS/NB-SS requests the release of the RRC Connection.
e) The UE is switched off.
f) The default UICC remains in use.
g) The Terminal is switched on.
h) The UE requests RRC Connection and therefore performs EPS Attach procedure to the E-USS/NB-SS.
5.1.9.5 Acceptance criteria
1) After step a) the UE shall read EFUST.
2) During step h) the UE shall include the GUTI "24608100010266345699" and the TAI 246/081/0001 in the AttachRequest message.
5.1.10 UE identification by GUTI when using USIM with service "EMM Information" available
5.1.10.1 Definition and applicability
The attach procedure is used to attach for packet services in EPS. With a successful attach procedure, a context is established for the UE in the MME, and a default bearer is established between the UE and the PDN GW, thus enabling always-on IP connectivity to the UE. The network may also initiate the activation of dedicated bearers as part of the attach procedure. For NB-IoT terminals the establishment of the PDN connection is optional.
5.1.10.2 Conformance requirement
The following EMM parameters shall be stored on the USIM if the corresponding file is present:
– GUTI;
– last visited registered TAI;
– EPS update status.
The presence and format of corresponding files on the USIM is specified in 3GPP TS 31.102 [4].
Reference:
– TS 31.102 [4], clauses 5.1.1 and 5.2.2;
– TS 24.301 [26], clause 5.5.1.2.1, 5.5.1.2.2, 5.5.1.2.4 and Annex C.
5.1.10.3 Test purpose
1) To verify that UE includes the GUTI and TAI stored in EFEPSLOCI in the AttachRequest message.
2) To verify that the EMM parameters GUTI, Last Registered TAI sent in the AttachAccept message and the related EPS Update Status are correctly stored on the USIM if the corresponding file is present.
5.1.10.4 Method of test
5.1.10.4.1 Initial conditions
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0002.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0002.
– Access control: unrestricted.
The default E-UTRAN UICC is is used with the following exceptions:
EFEPSNSC (EPS NAS Security Context)
Logically: Key Set Identifier KSIASME: ’01’
ASME Key (KSIASME): 32 byte key, any value
Uplink NAS count: ’00’
Downlink NAS count: ’01’
Identifiers of selected NAS
integrity and encryption algorithm: ’01’
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
… |
B39 |
|
Hex |
A0 |
34 |
80 |
01 |
01 |
81 |
20 |
xx |
… |
xx |
|
B40 |
B41 |
B42 |
B43 |
B44 |
B45 |
B46 |
B47 |
B48 |
B49 |
|
|
82 |
04 |
00 |
00 |
00 |
00 |
83 |
04 |
00 |
00 |
|
|
B50 |
B51 |
B52 |
B53 |
B54 |
||||||
|
00 |
01 |
84 |
01 |
01 |
5.1.10.4.2 Procedure
a) The UE is switched on.
b) The UE requests RRC Connection and therefore performs EPS Attach procedure to the E-USS/NB-SS. The E-USS/NB-SS sends AttachAccept with the following values:
GUTI: "24608100010266436587"
TAI (MCC/MNC/TAC): 246/081/0002
c) The UE send AttachComplete.
d) The E-USS/NB-SS requests the release of the RRC Connection.
5.1.10.5 Acceptance criteria
1) After step a) the UE shall read EFUST and EFEPSLOCI.
2) During step b) the UE shall include the GUTI and the Last visited registered TAI contained in EFEPSLOCI when sending the AttachRequest message.
3) After step b) EFEPSLOCI shall contain:
Logically: GUTI: 24608100010266436587
Last visited registered TAI: 246/081/0002
EPS update status: updated
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex: |
0B |
F6 |
42 |
16 |
80 |
00 |
01 |
02 |
66 |
43 |
65 |
|
B12 |
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||
|
87 |
42 |
16 |
80 |
00 |
02 |
00 |