12.5 P-TMSI reallocation
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
12.5.1 Definition
12.5.2 Conformance requirement
1) A User Equipment shall acknowledge a new P-TMSI when explicitly allocated.
2) The P-TMSI shall be updated on the USIM when the User Equipment is correctly deactivated in accordance with the manufacturer’s instructions.
3) A User Equipment shall use the given P-TMSI in further communication with the network.
Reference
3GPP TS 24.008 clause 4.7.6.
12.5.3 Test purpose
To verify that the UE is able to receive and acknowledge a new P-TMSI by means of an explicit P-TMSI reallocation procedure.
To verify that the UE has stored the P-TMSI in a non-volatile memory.
The implicit reallocation procedure is tested in the attach procedure.
12.5.4 Method of test
Initial condition
System Simulator:
– One cell operating in network operation 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).
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
An explicit P-TMSI reallocation procedure is performed (P-TMSI reallocation command sent from the SS and acknowledged from the UE by P-TMSI reallocation complete). The UE is PS detached and switched off. Its power supply is interrupted for 10 seconds. The power supply is resumed and then the UE is switched on. A PS attach procedure is performed with the given P-TMSI as identity.
Expected Sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The UE is set in UE operation mode A (see ICS). If UE operation mode A not supported set the UE in operation mode C. |
||
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 |
|
3a |
<- |
AUTHENTICATION AND CIPHERING REQUEST |
||
3b |
-> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
3c |
SS |
The SS starts integrity protection. |
||
4 |
<- |
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 |
|
5 |
-> |
ATTACH COMPLETE |
||
6 |
<- |
P-TMSI REALLOCATION COMMAND |
Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature |
|
7 |
-> |
P-TMSI REALLOCATION COMPLETE |
||
8 |
UE |
The UE is switched off or power is removed (see ICS). |
||
8a |
SS |
SS checks that the IE "Establishment cause" in any received RRC CONNECTION REQUEST message is set to "Detach". |
||
9 |
-> |
DETACH REQUEST |
Message not sent if power is removed. Detach type = ‘power switched off, GPRSdetach’ |
|
9a |
SS |
If the power was not removed, 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 . |
||
10 |
UE |
Ensure the power is removed from the UE for at least 10 seconds |
||
11 |
UE |
The UE is powered up or switched on and initiates an attach (see ICS). |
||
11a |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
12 |
-> |
ATTACH REQUEST |
Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-2 Old Routing area identity = RAI-1 |
|
12a |
<- |
AUTHENTICATION AND CIPHERING REQUEST |
||
12b |
-> |
AUTHENTICATION AND CIPHERING RESPONSE |
||
12c |
SS |
The SS starts integrity protection. |
||
13 |
<- |
ATTACH ACCEPT |
No new mobile identity assigned. P-TMSI not included. Attach result = ‘GPRS only attached’ |
|
13a |
SS |
The SS releases the RRC connection and waits 5s to allow the UE to read system information. |
||
14 |
<- |
PAGING TYPE1 |
Mobile identity = P-TMSI-2 Paging cause = "Terminating interactive call". |
|
15 |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call". |
||
16 |
Void |
|||
17 |
Void |
|||
18 |
-> |
SERVICE REQUEST |
service type = "paging response" |
|
18a |
SS |
The SS starts integrity protection. |
||
19 |
SS |
The SS releases the RRC connection. |
||
20 |
Void |
Specific message contents
None.
12.5.5 Test requirements
At step3, when the UE is powered up or switched on, UE shall:
– initiate the PS attach procedure with the information elements specified in the above Expected Sequence.
At step7, when the UE receives P-TMSI REALLOCATION COMMAND message from SS, UE shall:
– acknowledge the new P-TMSI by sending P-TMSI REALLOCATION COMPLETE message.
At step12, when the UE is powered up or switched on, UE shall:
– initiate the PS attach procedure with the information elements specified in the above Expected Sequence.
At step18, when the UE receives the paging message for PS domain with Mobile identity = P-TMSI-2, UE shall:
– respond to the paging message for PS domain by sending the SERVICE REQUEST message.