12.7 Identification procedure
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
The purpose of this procedure is to check that the UE gives its identity as requested by the network. If this procedure does not work, it will not be possible for the network to rely on the identity claimed by the UE.
12.7.1 General Identification
12.7.1.1 Definition
12.7.1.2 Conformance requirement
1) When requested by the network the User Equipment shall send its IMSI.
2) When requested by the network the User Equipment shall send its IMEI as stored in the Mobile Equipment.
3) When requested by the network the User Equipment shall send its IMEISV as stored in the Mobile Equipment.
Reference
3GPP TS 24.008 clauses 4.7.8
12.7.1.3 Test purpose
To verify that the UE sends identity information as requested by the system. The following identities can be requested: IMSI, IMEI and IMEISV.
12.7.1.4 Method of test
Initial condition
System Simulator:
One cell operating in network mode II.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE to prevent repeated CS domain registration and/or IMSI Detach by UEs in operation mode A).
User Equipment:
The UE has a valid IMSI.
If the UE is in UE operation mode A, then the UE has been registered in the CS domain
Related ICS/IXIT statements
Support of PS service Yes/No
UE operation mode A Yes/No
UE operation mode C Yes/No(only if mode A not supported)
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No
Test procedure
The SS requests identity information from the UE:
– IMSI
– IMEI
– IMEISV
Expected Sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
SS |
The UE is set to attach to PS services only (see ICS). If that is not supported by the UE, goto step 14. |
||
2 |
UE |
The UE is powered up or switched on and initiates an attach (see ICS). |
||
2a |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
3 |
-> |
ATTACH REQUEST |
Attach type = ‘GPRS attach’ Mobile identity = IMSI |
|
4 |
Void |
|||
5 |
<- |
AUTHENTICATION AND CIPHERING REQUEST |
||
5a |
-> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
5b |
SS |
The SS starts ciphering and integrity protection. |
||
6 |
<- |
IDENTITY REQUEST |
Identity type = IMSI |
|
7 |
-> |
IDENTITY RESPONSE |
Mobile identity = IMSI |
|
8 |
<- |
IDENTITY REQUEST |
Identity type = IMEI |
|
9 |
-> |
IDENTITY RESPONSE |
Mobile identity = IMEI |
|
10 |
<- |
IDENTITY REQUEST |
Identity type = IMEISV |
|
11 |
-> |
IDENTITY RESPONSE |
Mobile identity = IMEISV |
|
11a |
<- |
ATTACH ACCEPT |
Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-1 |
|
11b |
-> |
ATTACH COMPLETE |
||
11c |
SS |
The SS releases the RRC connection. |
||
12 |
UE |
The UE is switched off or power is removed (see ICS). |
||
12a |
SS |
SS checks that the IE "Establishment cause" in any received RRC CONNECTION REQUEST message is set to "Detach" (message not received if power is removed). |
||
13 |
-> |
DETACH REQUEST |
Message not sent if power is removed. Detach type = ‘power switched off, GPRSdetach’ |
|
13a |
SS |
The SS releases the RRC connection. If no RRC CONNECTION RELEASE COMPLETE message have been received within 1 second then the SS shall consider the UE as switched off. |
||
14 |
UE |
The UE is set to attach to both PS and non-PS services (see ICS) and the test is repeated from step 2 to step 13a. |
Specific message contents
None.
12.7.1.5 Test requirements
At step 2a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Registration".
At step 12a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Detach".
At step3, when the UE is powered on or switched on, UE shall:
– initiate the PS attach procedure with information elements specified in the above Expected Sequence.
At step7, when the SS requests an IMSI with the IDENTITY REQUEST message, UE shall:
– send the IDENTITY RESPONSE message with the Mobile identity = IMSI.
At step9, when the SS requests an IMEI with the IDENTITY REQUEST message, UE shall:
– send the IDENTITY RESPONSE message with the Mobile identity = IMEI.
At step11, when the SS requests an IMEISV with the IDENTITY REQUEST message, UE shall:
– send the IDENTITY RESPONSE message with the Mobile identity = IMEISV.