9.4.2 Location updating / rejected
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
9.4.2.1 Location updating / rejected / IMSI invalid
9.4.2.1.1 Definition
9.4.2.1.2 Conformance requirement
1) If the network rejects a location updating from the UE with the cause "IMSI unknown in HLR", "Illegal MS" or "Illegal ME" the UE shall:
1.1 not perform normal location updating;
1.2 not perform periodic location updating;
1.3 not respond to paging with IMSI;
1.4 not respond to paging with TMSI;
1.5 reject any request from CM entity for MM connection other than for emergency call;
1.6 not perform IMSI detach if it is switched off or has its power source removed.
2) If the network rejects a location updating from the UE with the cause "IMSI unknown in HLR", "Illegal MS" or "Illegal ME" the UE, if it supports emergency speech call, shall accept a request for an emergency call by sending a RRC CONNECTION Request message with the establishment cause set to "emergency call" and include an IMEI as mobile identity in the CM SERVICE REQUEST message.
3) If the network rejects a location updating from the UE with the cause "IMSI unknown in HLR", "Illegal MS" or "Illegal ME" the UE shall delete the stored LAI, CKSN and TMSI.
Reference(s)
TS 24.008 clause 4.4.4.7.
9.4.2.1.3 Test purpose
To test the behaviour of the UE if the network rejects the location updating of the UE with the cause "IMSI unknown in HLR", "illegal MS" or "Illegal ME".
9.4.2.1.4 Method of test
Initial conditions
– System Simulator:
– two cells: A and B, belonging to different location areas of the same PLMN;
– IMSI attach/detach is allowed in both cells;
– the T3212 time-out value is 1/10 hour in both cells.
– User Equipment:
– the UE has valid TMSI(= TMSI1), CKSN and CK, IK. It is "idle updated" on cell A.
Related ICS/IXIT statement(s)
USIM removal possible while the UE is powered Yes/No.
Switch off on button Yes/No.
Support for emergency speech call Yes/No.
Test Procedure
The SS rejects a normal location updating with the cause value "IMSI unknown in HLR". The RRC CONNECTION is released. The SS checks that the UE has entered the state MM IDLE and the substate NO IMSI, i.e. does not perform normal location updating when a new cell of the same or another PLMN is entered, does not perform periodic updating, does not respond to paging, rejects any requests from CM entities except emergency calls, does not perform IMSI detach if it is switched off or has its power source removed and deletes the stored LAI, CKSN and TMSI.
The test is repeated with cause value "Illegal MS" and with cause value "Illegal ME".
Expected sequence
The sequence is executed for execution counter k = 1, 2, 3.
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell B. |
||||
|
1 |
SS |
Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the "non-suitable cell". (see note) |
||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST is set to "Registration". If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with cause “GPRS services not allowed” when LOCATION UPDATING REJECT is sent with cause “IMSI unknown in HLR”. |
||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "LAI" = a, "Mobile Identity" = TMSI1 |
|
|
5a |
|
AUTHENTICATION REQUEST |
||
|
5b |
|
AUTHENTICATION RESPONSE |
||
|
5c |
The SS starts Integrity protection. Steps 5a to 5c are only applicable when k=2 and k=3 |
|||
|
6 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "IMSI unknown in HLR" for k = 1, "Illegal MS" for k = 2, "Illegal ME" for k = 3. |
|
|
7 |
SS |
The SS releases the RRC Connection. |
||
|
8 |
Void |
|||
|
The following messages are sent and shall be received on cell A. |
||||
|
9 |
SS |
Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "non-suitable cell". (see note) |
||
|
10 |
UE |
The UE performs cell reselection according to procedure as specified in (this however is not checked until step 23). The UE shall not initiate an RRC connection establishment on cell A or on cell B. |
||
|
11 |
SS |
The SS waits at least 7 minutes for a possible periodic updating. |
||
|
12 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. |
||
|
13 |
|
PAGING TYPE 1 |
The UE is paged in cell A. "UE identity" IE contains IMSI. Paging Cause: Terminating Conversational Call. |
|
|
14 |
UE |
The UE shall ignore this message. This is verified during 3 s. |
||
|
15 |
|
PAGING TYPE 1 |
The UE is paged in cell A. "UE identity" IE contains TMSI. Paging Cause: Terminating Conversational Call. |
|
|
16 |
UE |
The UE shall ignore this message. This is verified during 3 s. |
||
|
17 |
UE |
A MO CM connection is attempted. |
||
|
18 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. This is checked during 30 s. |
||
|
19 |
UE |
If the UE supports emergency speech call (see ICS), it is made to perform an emergency call. |
||
|
20 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST is set to "Emergency call". |
||
|
This message is sent in cell A. |
||||
|
21 |
Void |
|||
|
22 |
Void |
|||
|
23 |
|
CM SERVICE REQUEST |
"CM service type": Emergency call establishment. "Mobile identity": type of identity is set to IMEI. |
|
|
24 |
|
CM SERVICE ACCEPT |
||
|
25 |
|
EMERGENCY SETUP |
||
|
26 |
|
RELEASE COMPLETE |
"Cause" = unassigned number. |
|
|
27 |
SS |
The SS releases the RRC connection. |
||
|
28 |
Void |
|||
|
29 |
UE |
If possible (see ICS) USIM detachment is performed. Otherwise if possible (see ICS) switch off is performed. Otherwise the power is removed. |
||
|
30 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. This is checked during 3 s. |
||
|
31 |
UE |
Depending on what has been performed in step 29 the UE is brought back to operation. The subsequent GMM attach should be rejected if received in the PS mode. |
||
|
32 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST is set to "Registration". |
||
|
33 |
Void |
|||
|
34 |
Void |
|||
|
35 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = no key available, "mobile station classmark 1" as given by the ICS, "Mobile Identity" = IMSI, "LAI" = deleted LAI (the MCC and MNC hold the previous values, the LAC is coded FFFE). |
|
|
36 |
|
AUTHENTICATION REQUEST |
Assign a CKSN |
|
|
37 |
|
AUTHENTICATION RESPONSE |
||
|
37a |
SS |
The SS starts integrity protection. |
||
|
38 |
|
LOCATION UPDATING ACCEPT |
"Mobile Identity" = TMSI. |
|
|
39 |
|
TMSI REALLOCATION COMPLETE |
||
|
40 |
SS |
The SS releases the RRC connection. |
||
|
41 |
Void |
|||
|
NOTE: The definitions for "Serving cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Specific message contents
None.
9.4.2.1.5 Test requirement
1) 1.1 At step 10 the UE shall not perform normal location updating.
1.2 At step 12 the UE shall not perform periodic location updating.
1.3 At step 14 the UE shall not respond to paging with IMSI.
1.4 At step 16 the UE shall not respond to paging with TMSI.
1.5 At step 18 the UE shall reject a MO CM connection.
1.6 At step 30 the UE shall not initiate an RRC connection establishment on cell A or on cell B.
2) At step 20 the UE shall accept a request for an emergency call with the establishment cause set to "Emergency call".
3) At step 35 the UE shall send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and the LAI IE set to "deleted LAI" on cell A.
9.4.2.2 Location updating / rejected / PLMN not allowed
9.4.2.2.1 Definition
9.4.2.2.2 Conformance requirement
1) If the network reject a location updating from the UE with the cause "PLMN not allowed" the UE shall:
1.1 not perform periodic updating;
1.2 not perform IMSI detach when switched off;
1.3 not perform IMSI attach when switched on in the same location area;
1.4 not perform normal location updating when in the same PLMN and when that PLMN is not selected manually;
1.5 reject any request from CM entity for MM connection other than for emergency call.
2) If the network rejects a location updating from the UE with the cause "PLMN not allowed" the UE shall:
2.1 perform normal location updating when a new PLMN is entered;
2.2 accept a request for an emergency call, if it supports emergency speech call h, by sending a RRC CONNECTION REQUEST message with the establishment cause set to "emergency call".
3) If the network rejects a location updating from the UE with the cause "PLMN not allowed" and if after that the PLMN from which this rejection was received, is manually selected, the UE shall perform a normal location updating procedure.
4) If the network rejects a location updating from the UE with the cause "PLMN not allowed" the UE shall delete the stored LAI, CKSN and TMSI.
Reference(s)
TS 24.008 clause 4.4.4.7.
9.4.2.2.3 Test purpose
To test the behaviour of the UE if the network rejects the location updating of the UE with the cause "PLMN not allowed".
9.4.2.2.4 Method of test
Proc 1: Test procedure 1: Location updating / rejected / PLMN not allowed / test 1
Initial conditions
– System Simulator:
– one cell: C, belonging to PLMN1;
– two cells: A and B, belonging to different location areas a and b and belonging to PLMN2. PLMN2 is different from HPLMN and from PLMN1;
– IMSI attach/detach is allowed in cells A and B but not in cell C;
– the T3212 time-out value is 1/10 hour in cells A and B.
NB: i) Cell C will be mapped to Cell 1 as found in TS 34.108 clause 6.1.4.1.
ii) Cell A and B will be mapped to Cell 4 and 5 respectively, as found in TS 34.108 clause 6.1.4.1.
– User Equipment:
– the UE has a valid TMSI(= TMSI1) and CKSN(= CKSN1). It is "idle updated" on cell C;
– the UE is in manual mode for PLMN selection.
Related ICS/IXIT statement(s)
USIM removal possible while the UE is powered Yes/No.
Switch off on button Yes/No.
Support for emergency speech call Yes/No.
Test Procedure
The SS rejects a normal location updating with the cause value "PLMN not allowed". The RRC CONNECTION is released. The SS checks that the UE does not perform periodic updating, does not perform IMSI detach, does not perform IMSI attach if activated in the same location area, rejects any request for CM connection establishment other than emergency call, accepts a request for an emergency call, performs normal location updating only when a new PLMN is entered and deletes the stored LAI, CKSN and TMSI.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell B. |
||||
|
1 |
UE |
The UE is switched off (or power is removed). A Detach Request can be received in PS mode. |
||
|
2 |
SS |
Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell C to the "non-suitable cell". (see note) |
||
|
3 |
UE |
The UE is switched on (or power is reapplied). The UE shall offer the new PLMN as available to the user. The PLMN is manually selected. |
||
|
4 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". The subsequent GMM attach should be rejected if received in the PS mode. |
||
|
5 |
Void |
|||
|
6 |
Void |
|||
|
7 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal |
|
|
7a |
|
AUTHENTICATION REQUEST |
||
|
7b |
|
AUTHENTICATION RESPONSE |
||
|
7c |
The SS starts Integrity protection |
|||
|
8 |
|
LOCATION UPDATING REJECT |
"Reject cause" = PLMN not allowed. |
|
|
9 |
SS |
The SS releases the RRC connection. |
||
|
10 |
Void |
|||
|
11 |
SS |
The SS waits for a possible periodic updating for 7 minutes. |
||
|
12 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. |
||
|
13 |
UE |
If possible (see ICS) USIM detachment is performed. Otherwise if possible (see ICS) switch off is performed. Otherwise the power is removed. |
||
|
14 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. This is checked during 3 s. |
||
|
15 |
UE |
Depending on what has been performed in step 13 the UE is brought back to operation. The UE is not made to select PLMN 2. |
||
|
16 |
UE |
The UE shall not initiate an RRC connection establishment. This is checked during 3 s. |
||
|
The following message are sent and shall be received on cell A. |
||||
|
17 |
SS |
Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Suitable neighbour cell". (see note) |
||
|
18 |
UE |
No access to the network shall be registered by the SS within one minute. |
||
|
19 |
UE |
If the UE supports emergency speech call (see ICS) it is made to perform an emergency. |
||
|
20 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Emergency Call". |
||
|
21 |
Void |
|||
|
22 |
Void |
|||
|
23 |
|
CM SERVICE REQUEST |
"CM service type" = Emergency call establishment. "Mobile identity": type of identity is set to IMSI |
|
|
24 |
|
CM SERVICE ACCEPT |
||
|
25 |
|
EMERGENCY SETUP |
||
|
26 |
|
RELEASE COMPLETE |
Cause IE: "unassigned number". |
|
|
27 |
SS |
The SS releases the RRC connection. |
||
|
28 |
Void |
|||
|
29 |
UE |
A MO CM connection is attempted. |
||
|
30 |
UE |
The UE shall not initiate an RRC connection establishment. This is checked during 30 s. |
||
|
The following messages are sent and shall be received on cell C. |
||||
|
31 |
UE |
The UE is switched off. |
||
|
32 |
SS |
Set the cell type of cell C to the "Serving cell". Set the cell type of cell A to the "non-suitable cell". Set the cell type of cell B to the "non-suitable cell". (see note) |
||
|
33 |
UE |
The UE is switched on. If necessary the UE is placed into the automatic mode. |
||
|
34 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST is set to "Registration". |
||
|
35 |
Void |
|||
|
36 |
Void |
|||
|
37 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = no key available, "LAI" = deleted LAI (the MCC and MNC hold the values of PLMN1, the LAC is coded FFFE) "mobile identity" = IMSI. |
|
|
37a |
|
AUTHENTICATION REQUEST |
||
|
37b |
|
AUTHENTICATION RESPONSE |
||
|
37c |
SS |
The SS starts integrity protection. |
||
|
38 |
|
LOCATION UPDATING ACCEPT |
"Mobile identity" = TMSI. |
|
|
39 |
|
TMSI REALLOCATION COMPLETE |
||
|
40 |
SS |
The SS releases the RRC connection. |
||
|
41 |
Void |
|||
|
NOTE: The definitions for "Serving cell", "Suitable neighbour cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Specific message contents:
None.
Proc 2: Test procedure 2: Location updating / rejected / PLMN not allowed / test 2
Initial conditions
– System Simulator:
– one cell C, belonging to PLMN1;
– two cells A and B, belonging to different location areas a and b and belonging to PLMN2. PLMN2 is different from HPLMN;
– IMSI attach/detach is allowed in cells A and B but not in cell C;
– the T3212 time-out value is 1/10 hour in cells A and B.
– User Equipment:
– the UE has a valid TMSI. It is "idle updated" on cell C.
– the UE is in manual mode for PLMN selection.
NB: i) Cell C will be mapped to Cell 1 as found in TS 34.108 clause 6.1.4.1.
ii) Cell A and B will be mapped to Cell 4 and 5 respectively, as found in TS 34.108 clause 6.1.4.1.
Related ICS/IXIT statement(s)
USIM removal possible while UE is powered Yes/No.
Switch off on button Yes/No.
The UE is automatically in automatic mode after switch on Yes/No.
Test Procedure
The SS rejects a normal location updating with the cause value "PLMN not allowed". The RRC CONNECTION is released. Then the PLMN from which this rejection was received is manually selected and the SS checks that a normal location updating is performed.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell B. |
||||
|
1 |
UE |
The UE is switched off (or power is removed). A Detach Request can be received in PS mode. |
||
|
2 |
SS |
Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell C to the "non-suitable cell". (see note) |
||
|
3 |
UE |
The UE is switched on (or power is reapplied). |
||
|
3a |
UE |
The UE shall offer the new PLMN as available to the user. The PLMN is manually selected. |
||
|
4 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". The subsequent GMM attach should be rejected if received in the PS mode. |
||
|
5 |
Void |
|||
|
6 |
Void |
|||
|
7 |
|
LOCATION UPDATING REQUEST |
||
|
7a |
|
AUTHENTICATION REQUEST |
||
|
7b |
|
AUTHENTICATION RESPONSE |
||
|
7c |
The SS starts Integrity Protection |
|||
|
8 |
|
LOCATION UPDATING REJECT |
"Reject cause" = PLMN not allowed. |
|
|
9 |
SS |
Void |
The SS releases the RRC connection. |
|
|
10 |
Void |
|||
|
11 |
UE |
The UE is made to search for PLMNs and the PLMN indicated by the SS is manually selected. |
||
|
12 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
|
13 |
Void |
|||
|
14 |
Void |
|||
|
15 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = no key available, "LAI" = deleted LAI (the MCC and MNC hold the values of PLMN1, the LAC is coded FFFE) "mobile identity" = IMSI. |
|
|
15a |
Void |
|||
|
15b |
|
LOCATION UPDATING REJECT |
"Reject cause" = PLMN not allowed. |
|
|
16 |
SS |
The SS releases the RRC connection. |
||
|
17 |
Void |
|||
|
The following messages are sent and shall be received on cell C. |
||||
|
18 |
UE |
The UE is switched off. |
||
|
19 |
SS |
Set the cell type of cell C to the "Serving cell". Set the cell type of cell A to the "non-suitable cell". Set the cell type of cell B to the "non-suitable cell". (see note) |
||
|
20 |
UE |
The UE is switched on. If necessary, the UE is put into the automatic mode. |
||
|
21 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
|
22 |
Void |
|||
|
23 |
Void |
|||
|
24 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = no key available, "LAI" = deleted LAI (the MCC and MNC hold the values of PLMN1, the LAC is coded FFFE) "mobile identity" = IMSI. |
|
|
24a |
|
AUTHENTICATION REQUEST |
||
|
24b |
|
AUTHENTICATION RESPONSE |
||
|
24c |
SS |
The SS starts integrity protection. |
||
|
25 |
|
LOCATION UPDATING ACCEPT |
"Mobile identity" = TMSI. |
|
|
26 |
|
TMSI REALLOCATION COMPLETE |
||
|
27 |
SS |
The SS releases the RRC connection. |
||
|
28 |
Void |
|||
|
NOTE: The definitions for "Serving cell", "Suitable neighbour cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Specific message contents
None.
9.4.2.2.5 Test requirement
1) 1.1 At step 12 in test 1 the UE shall not perform periodic updating.
1.2 At step 14 in test 1 the UE shall not initiate an RRC connection establishment (IMSI detach).
1.3 At step 16 in test 1 the UE shall not initiate an RRC connection establishment (IMSI attach).
1.4 At step 16 in test 1 the UE shall not perform normal location updating.
1.5 At step 30 in test 1 the UE shall reject a MO CM connection.
2) 2.1 At step 37 in test 1 the UE shall perform normal location updating.
2.2 At step 20 in test 1 the UE shall accept a request for an emergency call with the establishment cause set to "Emergency call".
3) At step 11 in test 2 the UE is made to search for PLMNs and the PLMN indicated by the SS is manually selected, and at step 15 the UE shall perform a normal location updating procedure.
4) At step 37 in test 1 the UE shall send a LOCATION UPDATING REQUEST message with Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and LAI IE set to "deleted LAI" on cell C.
9.4.2.3 Location updating / rejected / location area not allowed
9.4.2.3.1 Definition
9.4.2.3.2 Conformance requirement
1) If the network rejects a location updating from the UE with the cause "Location Area not allowed" the UE shall:
1.1 not perform periodic updating;
1.2 not respond to paging with TMSI;
1.3 reject any request from CM entity for MM connection other than for emergency call;
1.4 not perform IMSI detach.
1.5 not delete the list of "equivalent PLMNs".
2) If the network rejects a location updating from the UE with the cause "Location Area not allowed" the UE shall:
2.1 perform normal location updating when a new location area is entered;
2.2 accept a request for an emergency call, if it supports emergency speech call h, by sending a RRC CONNECTION REQUEST message with the establishment cause set to "emergency call";
2.3 delete the list of forbidden LAs after switch off (power off).
3) If the network rejects a location updating from the UE with the cause "Location Area not allowed" the UE shall delete the stored LAI, CKSN and TMSI.
Reference(s)
TS 24.008 clause 4.4.4.7.
9.4.2.3.3 Test purpose
To test the behaviour of the UE if the network rejects the location updating of the UE with the cause "Location Area not allowed".
To test that the UE deletes the list of forbidden LAs after switch off (power off).
9.4.2.3.4 Method of test
Initial conditions
– System Simulator:
– three cells: A, B and C, belonging to different location areas a, b and c. Cell A and B belongs to PLMN1. Cell C belongs to PLMN2.
– IMSI attach/detach is allowed in both cells;
– the T3212 time-out value is 1/10 hour in both cells;
– Sintersearch values for cells A and B are 20 dB.
NB: i) Cell C will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.1.
– User Equipment:
– the UE has a valid TMSI(= TMSI1) and CKSN(= CKSN1). It is "idle updated" on cell A.
– the UE has a list of "equivalent PLMNs" containing PLMN1 and PLMN2.
Related ICS/IXIT statement(s)
Switch off on button Yes/No.
Support for emergency speech call Yes/No.
Method to clear the list of forbidden location areas periodically.
Test Procedure
The SS rejects a normal location updating with the cause value "Location Area not allowed". The RRC CONNECTION is released. The SS checks that the UE deletes the stored LAI, CKSN and TMSI, does not perform periodic updating, does not respond to paging with TMSI, rejects any requests from CM entities for MM-connections except emergency calls, does not perform IMSI detach, does not delete the list of "equivalent PLMNs", performs normal location updating when a new location area is entered, deletes the list of forbidden LAs when switched off.
Different types of UE may use different methods to periodically clear the list of forbidden location areas (e.g. every day at 12am). If the list is cleared while the test is being run, it may be necessary to re-run the test.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell B. |
||||
|
1 |
SS |
Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the " Suitable neighbour cell ". Set the cell type of cell C to the " Suitable neighbour cell ". (see note). |
||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = CKSN1, "LAI" = a, "Mobile Identity" = TMSI1 |
|
|
5a |
|
AUTHENTICATION REQUEST |
||
|
5b |
|
AUTHENTICATION RESPONSE |
||
|
5c |
The SS starts Integrity Protection |
|||
|
6 |
|
LOCATION UPDATING REJECT |
"Reject cause" = "Location Area not allowed". |
|
|
7 |
SS |
After the sending of this message, the SS waits for the disconnection of the main signalling link. The SS releases the RRC connection. |
||
|
8 |
Void |
|||
|
9 |
SS |
SS waits for a possible location updating for 7 minutes. |
||
|
10 |
UE |
The UE shall not initiate an RRC-connection establishment either on cell A, C or cell B. |
||
|
11 |
|
PAGING TYPE 1 |
The UE is paged in cell B. "UE identity" = TMSI. Paging Cause: Terminating Conversational Call. |
|
|
12 |
UE |
The UE shall ignore this message. This is checked during 30 s. |
||
|
13 |
UE |
A MO CM connection is attempted. |
||
|
14 |
UE |
The UE shall not initiate an RRC connection establishment on cell A, C or cell B. This is checked during 30 s. |
||
|
15 |
UE |
If the UE supports emergency speech call (see ICS), it is made to perform an emergency call. |
||
|
16 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Emergency call". |
||
|
17 |
Void |
|||
|
18 |
Void |
|||
|
19 |
|
CM SERVICE REQUEST |
"CM service type": Emergency call establishment. |
|
|
20 |
|
CM SERVICE ACCEPT |
||
|
21 |
|
EMERGENCY SETUP |
||
|
22 |
|
RELEASE COMPLETE |
Cause: "unassigned number". |
|
|
23 |
SS |
The SS releases the RRC connection. |
||
|
24 |
Void |
|||
|
25 |
UE |
If possible (see ICS) switch off is performed. Otherwise the power is removed. |
||
|
26 |
UE |
The UE shall not initiate an RRC connection establishment on cell A, C or on cell B (check for IMSI detach) This is checked during 3 s. |
||
|
27 |
UE |
The SS sets the cell type of cells A and C to "non-suitable cell". Depending on what has been performed in step 25 the UE is brought back to operation. The subsequent GMM attach should be rejected if received in the PS mode with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
28 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
|
29 |
Void |
|||
|
30 |
Void |
|||
|
31 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = no key available, "LAI" = deleted LAI, "mobile identity" = IMSI (This checks the deletion of the forbidden lists) |
|
|
31a |
|
AUTHENTICATION REQUEST |
||
|
31b |
|
AUTHENTICATION RESPONSE |
||
|
31c |
The SS starts Integrity Protection |
|||
|
32 |
|
LOCATION UPDATING REJECT |
"Reject cause" = "Location Area not allowed". |
|
|
33 |
SS |
The SS releases the RRC connection. |
||
|
34 |
Void |
|||
|
The following messages are sent and shall be received on cell C. |
||||
|
35 |
SS |
Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell C to the "Serving cell". Set the cell type of cell B to the " Suitable neighbour cell ". (see note). |
||
|
36 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
|
37 |
Void |
|||
|
38 |
Void |
|||
|
39 |
|
LOCATION UPDATING REQUEST |
||
|
40 |
|
AUTHENTICATION REQUEST |
||
|
41 |
|
AUTHENTICATION RESPONSE |
||
|
41a |
SS |
The SS starts integrity protection. |
||
|
42 |
|
LOCATION UPDATING ACCEPT |
Mobile identity = TMSI. |
|
|
43 |
|
TMSI REALLOCATION COMPLETE |
||
|
44 |
SS |
The SS releases the RRC connection. |
||
|
45 |
Void |
|||
|
NOTE: The definitions for "Serving cell", "Suitable neighbour cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Specific message contents
None.
9.4.2.3.5 Test requirement
1) 1.1 At step 10 the UE shall not perform periodic updating.
1.2 At step 12 the UE shall not respond to paging with TMSI.
1.3 At step 14 the UE shall not initiate an RRC connection establishment.
1.4 At step 26 the UE shall not initiate an RRC connection establishment (IMSI detach).
1.5 At step 39 the UE shall perform normal location updating on cell C.
2) 2.1 At step 39 the UE shall perform normal location updating.
2.2 At step 16 the UE shall accept a request for an emergency call.
2.3 At step 31 the UE shall send a LOCATION UPDATING REQUEST message on cell B.
3) At step 31 the UE shall send a LOCATION UPDATING REQUEST message with Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and LAI IE set to "deleted LAI" on cell B.
9.4.2.4 Location updating / rejected / roaming not allowed in this location area
9.4.2.4.1 Definition
9.4.2.4.2 Conformance requirement
1) If the network rejects a location updating from the UE with the cause "Roaming not allowed in this location area" the UE shall:
1.1 not perform periodic updating;
1.2 void;
1.3 reject any request from CM entity for MM connection other than for emergency call;
1.4 not perform IMSI detach.
2) If the network rejects a location updating from the UE with the cause "Roaming not allowed in this location area" the UE shall:
2.1 perform normal location updating when a new location area is entered;
2.2 accept a request for an emergency call, if it supports emergency speech call, by sending a RRC CONNECTION Request message with the establishment cause set to "emergency call";
2.3 periodically search for its HPLMN.
3) The UE shall reset the list of "Forbidden location areas for roaming" when it is switched off or has its power source removed or when the USIM is removed.
4) The UE shall contain a list of "forbidden location areas for roaming". The location area identification received on the BCCH that triggered the location updating request shall be added to the suitable list whenever a LOCATION UPDATE REJECT message is received with the cause "Roaming not allowed in this location area". The lists shall accommodate each 10 or more location area identifications.
Reference(s)
TS 24.008 clause 4.4.4.7.
9.4.2.4.3 Test purposes
Test purpose 1
To test that on receipt of a rejection using the Roaming cause code, the UE ceases trying to update on that cell, that this situation continues for at least one periodic location interval period, and that the corresponding list is re-set by switching off the UE or removing its power source.
Test purpose 2
To test that if no cell is available, the UE rejects a request from CM entity other than for emergency calls.
Test purpose 3
To test that at least 6 entries can be held in the list of "forbidden location areas for roaming" (the requirement in is to store at least 10 entries. This is not fully tested by the third procedure).
Test purpose 4
To test that if a cell of the Home PLMN is available then the UE returns to it in preference to any other available cell.
Test purpose 5
To test that if the USIM is removed the list of "forbidden location areas for roaming" is cleared.
9.4.2.4.4 Method of test
Initial conditions
The initial conditions shall be met before each of the different procedures.
– System Simulator:
– for procedures 1, 2, 3 and 5: Two cells A and B, belonging to different location areas of the same PLMN with LAI a and b. The MCC of that PLMN is the same as that of the HPLMN. The MNC of that PLMN is different from that of the HPLMN. For procedure 2, Cell B will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.1 and Qqualmin values for cells A and B are -16 dB (FDD only);
– for procedure 4: three cells A, B, C of the same PLMN which is not the HPLMN with 3 different location area codes. Cells should differ in signal strength by 10 dB with cell A being the strongest and cell C the weakest. There should be a 20 dB range between A and C. A should be set to a level of – 40 dBm;
NB: i) Cell C will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.1.
– IMSI attach/detach is allowed in every cell;
– the T3212 time-out value is 1/10 hour in every cell,
– User Equipment:
– procedures 1, 2, 3 and 5: The UE has valid TMSI, CKSN and CK, IK. It is "idle updated" on cell B;
– procedure 4: The UE has valid TMSI, CKSN and CK, IK. It is "idle updated" on cell A;
– the list of "forbidden location areas for roaming" shall be empty (this may be achieved by either removing the USIM or switching the UE OFF then ON or removing the UE power source depending on ICS).
Related ICS/IXIT statement(s)
USIM removal possible while UE is powered Yes/No.
Switch off on button Yes/No.
Support of emergency speech call Yes/No.
Method to clear the list of location areas for roaming periodically.
The UE is automatically in automatic mode after switch on Yes/No.
9.4.2.4.4.1 Test Procedures
Proc 1: Test procedure 1
– The SS rejects a normal location updating with the cause value "Roaming not allowed in this location area". The RRC CONNECTION is released. The SS checks that the UE does not perform periodic location updating procedure. The UE is turned off and then on. The SS checks that the UE performs location updating on the cell on which its location update request had been rejected (this checks that the LA is not the forbidden list after switch on). This procedure is performed another time but the deletion of the list is checked while removing the USIM (instead of turning off the UE).
Proc 2: Test procedure 2
– The SS rejects a normal location updating with the cause value "Roaming not allowed in this location area". The RRC CONNECTION is released. The SS checks that the UE rejects a request from CM entity but supports an emergency call.
Proc 3: Test procedure 3
– The SS rejects a normal location updating with the cause value "Roaming not allowed in this location area". This is done for 6 different location areas. Then the SS checks that the UE does not attempt to begin a location updating procedure on the non-allowed location areas.
Proc 4: Test procedure 4
– The SS accepts a periodic location updating on a cell not belonging to the HPLMN. Then when the UE attempts to perform a periodic location updating to this cell, the SS rejects this location updating with the cause value "Roaming not allowed in this location area". Three cells are then available, one of them belonging to the HPLMN. It is checked that the UE returns to its HPLMN.
Proc 5: Test procedure 5
If USIM removal is possible while UE is powered:
– The SS rejects a normal location updating with the cause value "Roaming not allowed in this location area". The RRC CONNECTION is released. The SS checks that the UE does not perform periodic location updating procedure. The USIM is removed and inserted in the UE. The SS checks that the UE performs location updating on the cell on which its location update request had been rejected (this checks that the LA is not the forbidden list after switch on).
Different types of UE may use different methods to periodically clear the list of forbidden areas (e.g. every day at 12am) for roaming. If the list is cleared while the test is being run, it may be necessary to re-run the test.
Expected sequence
The following procedure is used during the test:
– change_LAI (x):
– the purpose of this procedure is to change the value of Location Area Identifier of cell x;
– the Location Area Identifier of cell x shall be changed. The code shall be chosen arbitrarily but shall be different from any previously used in this procedure. The code shall have the same MCC as the Home PLMN and shall not have the same MNC as the Home PLMN.
Procedure 1
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell A. |
||||
|
1 |
SS |
Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "non-suitable cell". (see note). |
||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
LOCATION UPDATING REQUEST |
Location Updating Type = normal. |
|
|
5a |
|
AUTHENTICATION REQUEST |
||
|
5b |
|
AUTHENTICATION RESPONSE |
||
|
5c |
The SS starts Integrity Protection |
|||
|
6 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
7 |
SS |
The SS releases the RRC connection |
||
|
8 |
Void |
|||
|
9 |
SS |
The SS waits at least 7 minutes for a possible location updating. |
||
|
10 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. |
||
|
11 |
UE |
If possible (see ICS) the UE is switched off. Otherwise if possible the power is removed. |
||
|
12 |
UE |
Depending on what has been performed in step 11 the UE is brought back to operation and placed in an automatic mode. The subsequent GMM attach should be rejected if received in the PS mode. |
||
|
13 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
|
14 |
Void |
|||
|
15 |
Void |
|||
|
16 |
|
LOCATION UPDATING REQUEST |
Location Updating Type = normal. |
|
|
16a |
SS |
The SS starts integrity protection. |
||
|
17 |
|
LOCATION UPDATING ACCEPT |
"Mobile Identity" not IE included. |
|
|
18 |
SS |
The SS releases the RRC connection. |
||
|
19 |
Void |
|||
|
NOTE: The definitions for "Serving cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Procedure 2
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell A. |
||||
|
1 |
SS |
Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the “Suitable neighbour inter-frequency cell”. (see note). |
||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". This message is sent on cell A. If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
LOCATION UPDATING REQUEST |
||
|
5a |
|
AUTHENTICATION REQUEST |
||
|
5b |
|
AUTHENTICATION RESPONSE |
||
|
5c |
The SS starts Integrity Protection |
|||
|
6 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
7 |
SS |
The SS releases the RRC connection. |
||
|
8 |
SS |
Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the “Suitable neighbour inter-frequency cell”. (see note). |
||
|
The following messages are sent and shall be received on cell B. |
||||
|
9 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
10 |
Void |
|||
|
11 |
Void |
|||
|
12 |
|
LOCATION UPDATING REQUEST |
||
|
12a |
|
AUTHENTICATION REQUEST |
||
|
12b |
|
AUTHENTICATION RESPONSE |
||
|
12c |
The SS starts Integrity Protection |
|||
|
13 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
14 |
SS |
The SS releases the RRC connection. |
||
|
15 |
Void |
|||
|
16 |
SS |
The SS waits for a possible location updating procedure on both cells A and B for 2 minutes. |
||
|
17 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B within 2 minutes after the end of step 15. |
||
|
18 |
Void |
|||
|
19 |
Void |
|||
|
20 |
UE |
A MO CM connection is attempted. |
||
|
21 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. This is checked during 30 s. |
||
|
The following messages are sent and shall be received on cell B. Steps 22 to 31 are performed if the UE supports emergency speech call. |
||||
|
22 |
UE |
An emergency call is attempted. |
||
|
23 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Emergency Call". |
||
|
24 |
Void |
|||
|
25 |
Void |
|||
|
26 |
|
CM SERVICE REQUEST |
"CM service type": Emergency call establishment. |
|
|
27 |
|
CM SERVICE ACCEPT |
||
|
28 |
|
EMERGENCY SETUP |
||
|
29 |
|
RELEASE COMPLETE |
"Cause" = unassigned number. |
|
|
30 |
SS |
The SS releases the RRC connection. |
||
|
31 |
Void |
|||
|
NOTE: The definitions for "Serving cell" and “Suitable neighbour inter-frequency cell” are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Procedure 3
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell A |
||||
|
1 |
SS |
Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Suitable neighbour cell". (see note) |
||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Registration”. If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
LOCATION UPDATING REQUEST |
||
|
6 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
7 |
SS |
The SS releases the RRC connection |
||
|
8 |
Void |
|||
|
The following messages are sent and shall be received on cell B. |
||||
|
9 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Registration”. If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
10 |
Void |
|||
|
11 |
Void |
|||
|
12 |
|
LOCATION UPDATING REQUEST |
||
|
13 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
14 |
SS |
The SS releases the RRC connection |
||
|
15 |
Void |
|||
|
16 |
SS |
Change_LAI (A) within 5 s after step 13. |
||
|
The following messages are sent and shall be received on cell A. |
||||
|
17 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST is set to “Registration”. If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
18 |
Void |
|||
|
19 |
Void |
|||
|
20 |
|
LOCATION UPDATING REQUEST |
||
|
21 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
22 |
SS |
The SS releases the RRC connection |
||
|
23 |
Void |
|||
|
24 |
SS |
Change_LAI (B) within 5 s after step 21. |
||
|
The following messages are sent and shall be received on cell B. |
||||
|
25 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Registration”. If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
26 |
Void |
|||
|
27 |
Void |
|||
|
28 |
|
LOCATION UPDATING REQUEST |
||
|
29 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
30 |
SS |
The SS releases the RRC connection. |
||
|
31 |
Void |
|||
|
32 |
SS |
Change_LAI (A) within 5 s after step 29. |
||
|
The following messages are sent and shall be received on cell A. |
||||
|
33 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Registration”. If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
34 |
Void |
|||
|
35 |
Void |
|||
|
36 |
|
LOCATION UPDATING REQUEST |
||
|
37 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
38 |
SS |
The SS releases the RRC connection |
||
|
39 |
Void |
|||
|
40 |
SS |
Change_LAI (B) within 5 s after step 37. |
||
|
The following messages are sent and shall be received on cell B. |
||||
|
41 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Registration”. If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
42 |
Void |
|||
|
43 |
Void |
|||
|
44 |
|
LOCATION UPDATING REQUEST |
||
|
45 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
46 |
SS |
The SS releases the RRC connection |
||
|
47 |
Void |
|||
|
48 |
SS |
The SS waits for a possible location updating procedure on both cells A and B for 7 minutes. |
||
|
49 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B within 7 minutes after the end of step 47. |
||
|
NOTE: The definitions for "Serving cell" and "Suitable neighbour cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Procedure 4
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell A. |
||||
|
1 |
SS |
The SS waits for a periodic location updating procedure on cell A for T3212 minutes after the initial conditions have been established. |
||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Registration”. |
||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
LOCATION UPDATING REQUEST |
Location Updating Type = periodic. |
|
|
6 |
|
LOCATION UPDATING ACCEPT |
"Mobile Identity" not IE included. |
|
|
7 |
SS |
The SS releases the RRC connection |
||
|
8 |
Void |
|||
|
9 |
SS |
The location area identity of cell C shall be changed to that of a location area in the Home PLMN. |
||
|
10 |
SS |
The SS waits for a periodic location updating procedure on cell A for T3212 minutes. |
||
|
11 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Registration”. This message is sent on cell A within T3212 minutes after the end of step 7. |
||
|
12 |
Void |
|||
|
13 |
Void |
|||
|
14 |
|
LOCATION UPDATING REQUEST |
"Location updating type" = periodic. |
|
|
14a |
|
AUTHENTICATION REQUEST |
||
|
14b |
|
AUTHENTICATION RESPONSE |
||
|
14c |
The SS starts Integrity Protection |
|||
|
15 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
16 |
SS |
The SS releases the RRC connection |
||
|
17 |
Void |
|||
|
The following messages are sent and shall be received on cell C. |
||||
|
18 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Registration”. If PS mode: a ROUTING AREA UPDATE REQUEST should be accepted. |
||
|
19 |
Void |
|||
|
20 |
Void |
|||
|
21 |
|
LOCATION UPDATING REQUEST |
"Location updating type" = normal. |
|
|
21a |
SS |
The SS starts integrity protection. |
||
|
22 |
|
LOCATION UPDATING ACCEPT |
"Mobile Identity" not IE included. |
|
|
23 |
SS |
The SS releases the RRC connection |
||
|
24 |
Void |
|||
Procedure 5
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell A. |
||||
|
1 |
SS |
Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "non-suitable cell". (see note) |
||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
LOCATION UPDATING REQUEST |
||
|
6 |
|
LOCATION UPDATING REJECT |
"Reject cause" IE is "Roaming not allowed in this location area". |
|
|
7 |
The SS releases the RRC connection. |
|||
|
8 |
Void |
|||
|
9 |
SS |
The SS waits at least 7 minutes for a possible location updating. |
||
|
10 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. |
||
|
11 |
UE |
The USIM is removed. |
||
|
12 |
UE |
The USIM is inserted into the ME. The subsequent GMM attach should be rejected if received in the PS mode. |
||
|
13 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
|
14 |
Void |
|||
|
15 |
Void |
|||
|
16 |
|
LOCATION UPDATING REQUEST |
Location Updating Type = normal. |
|
|
16a |
|
AUTHENTICATION REQUEST |
||
|
16b |
|
AUTHENTICATION RESPONSE |
||
|
16c |
SS |
The SS starts integrity protection. |
||
|
17 |
|
LOCATION UPDATING ACCEPT |
"Mobile Identity" not IE included. |
|
|
18 |
SS |
The SS releases the RRC connection. |
||
|
19 |
Void |
|||
|
NOTE: The definitions for "Serving cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Specific message contents
None.
9.4.2.4.5 Test requirement
1) 1.1 At step 10 in Procedure 1 the UE shall not perform periodic updating.
1.2 Void.
1.3 At step 21 in procedure 2 the UE shall not initiate an RRC connection establishment.
1.4 After step 13 in Procedure 5 the UE shall perform location updating (at step 16; not perform IMSI detach).
2) 2.1 After step 9 in Procedure 2 the UE perform normal location updating (at step 12).
2.2 At step 23 in Procedure 2 the UE shall initiate a RRC CONNECTION REQUEST message with the establishment cause set to "Emergency call";
2.3 At step 14 in Procedure 4 the UE shall attempt to location updating with location updating type "periodic" (at step 21: UE returns to HPLMN in preference to any other available cell).
3) After step 12 in Procedure 5 the UE shall perform location updating (at step 16) when the USIM is inserted.
4) At step 49 in Procedure 3 the UE shall not attempt to begin a location updating procedure.
9.4.2.5 Location updating / rejected / No Suitable Cells In Location Area
9.4.2.5.1 Definition
9.4.2.5.2 Conformance requirement
1) If the network rejects a location updating from the UE with the cause " No Suitable Cells In Location Area " the UE shall:
1.1 perform normal location updating at a suitable cell in another location area in the same PLMN,
1.2 not delete the list of "equivalent PLMNs".
Reference(s)
TS 24.008 clause 4.4.4.7.
9.4.2.5.3 Test purpose
To test the behaviour of the UE if the network rejects the location updating of the UE with the cause "No Suitable Cells In Location Area".
9.4.2.5.4 Method of test
Initial conditions
– System Simulator:
– two cells: A and B, belonging to different location areas a and b and belonging to PLMN1;
– one cell: C, belonging to PLMN2;
– one cell: D, belonging to PLMN3;
– IMSI attach/detach is allowed in cells A, B, C and D;
NB: i) Cell C will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.2.
ii) Cell D will be mapped to Cell 7 as found in TS 34.108 clause 6.1.4.2.
– User Equipment:
– the UE has a valid TMSI(= TMSI1) and CKSN(= CKSN1). It is "idle updated" on cell A.
– the UE has a list of "equivalent PLMNs" containing PLMN1 and PLMN2.
Related ICS/IXIT statement(s)
None.
Test Procedure
The SS rejects a normal location updating with the cause value "No Suitable Cells In Location Area". The RRC CONNECTION is released. The SS checks that the UE shall search for a suitable cell in a different location area on the equivalent PLMN, which is equal condition for the UE as same PLMN, and shall perform normal location updating procedure in that cell
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell B. |
||||
|
1 |
SS |
Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the "non-suitable cell". Set the cell type of cell C to the "Suitable neighbour cell". Set the cell type of cell D to the "Suitable neighbour cell". (see note) |
||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". If PS mode: a ROUTING AREA UPDATE REQUEST should be rejected with the same cause as used in the LOCATION UPDATING REJECT. |
||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = CKSN1, "LAI" = a, "mobile station classmark 1" as given by the ICS and "Mobile Identity" = TMSI1. |
|
|
5a |
|
AUTHENTICATION REQUEST |
||
|
5b |
|
AUTHENTICATION RESPONSE |
||
|
5c |
The SS starts Integrity Protection |
|||
|
6 |
|
LOCATION UPDATING REJECT |
"Reject cause" = "No Suitable Cells In Location Area". |
|
|
7 |
SS |
The SS releases the RRC connection. |
||
|
8 |
Void |
|||
|
The following messages are sent and shall be received on cell C. |
||||
|
9 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". The subsequent GMM attach should be rejected if received in the PS mode. |
||
|
10 |
Void |
|||
|
11 |
Void |
|||
|
12 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = CKSN1, "LAI" = a, "mobile station classmark 1" as given by the ICS, "Mobile Identity" = TMSI1. |
|
|
13 |
Void |
|||
|
14 |
Void |
|||
|
15 |
SS |
The SS starts integrity protection. |
||
|
16 |
Void |
|||
|
17 |
|
LOCATION UPDATING ACCEPT |
Mobile identity = TMSI, LAI = c. |
|
|
18 |
|
TMSI REALLOCATION COMPLETE |
||
|
19 |
SS |
The SS releases the RRC connection. |
||
|
20 |
Void |
|||
|
NOTE: The definitions for "Serving cell", "Suitable neighbour cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Specific message contents
None.
9.4.2.5.5 Test requirement
At step 12 the UE shall perform normal location updating on cell C.
9.4.2.6 Location updating / rejected / Not authorized for this CSG
9.4.2.6.1 Definition
9.4.2.6.2 Conformance requirement
1) If the network rejects a location updating procedure from the User Equipment with the cause ‘ Not authorized for this CSG ‘ the User Equipment shall:
1.1 not delete the list of "equivalent PLMNs"
1.2 remove the CSG ID of the cell where the UE has sent the LOCATION UPDATING REQUEST message from the allowed CSG list stored in the UE.
1.3 perform normal location updating at a suitable cell in the same PLMN.
Reference
3GPP TS 24.008 clause 4.4.4.7.
9.4.2.6.3 Test purpose
To verify that the UE removes the CSG ID from the Allowed CSG list and searches for a suitable cell in the same PLMN If the network rejects the location updating of the UE with the cause ‘ Not authorized for this CSG ‘.
9.4.2.6.4 Method of test
Initial conditions
System Simulator:
– Four cells: A, B, C and D, belonging to different location areas a, b, c and d. Cell A, B, C and D belong to PLMN1 and operating in network operation mode II.
– IMSI attach/detach is allowed in all cells;
NB: i) Cell A, B, C and D will be mapped to Cell 1, 2, 3 and 7 respectively as found in TS 34.108 clause 6.1.4.1.
ii) Cell A and D shall also include a CSG ID as CSG 1 for PLMN 1.
iii) Cell C shall also include a CSG ID as CSG 2 for PLMN 1.
User Equipment:
The UE has a valid TMSI(= TMSI1), KSI and CK, IK. It is "idle updated" on cell B.
UE Allowed CSG List contains CSG1 and CSG2 for PLMN 1.
The UE is equipped with a USIM containing default values except for those listed below.
|
USIM field |
PLMN |
CSG ID |
|
EFACSGL |
PLMN 1 |
CSG 1,CSG 2 |
Related ICS/IXIT statement(s)
Switch off on button Yes/No
Test procedure
The SS rejects a normal location updating with the cause value ‘Not authorized for this CSG’. The RRC CONNECTION is released. The SS checks that the UE shall search for a suitable cell in the same PLMN.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
SS |
Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "non-suitable cell". Set the cell type of cell C to the "Suitable neighbour cell". Set the cell type of cell D to the "non-suitable ‘Off’ cell". (see NOTE) |
||
|
The following messages are sent and shall be received on cell A. |
||||
|
2 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
|
3 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "LAI" = b, "Mobile Identity" = TMSI1 |
|
|
3a |
The SS starts integrity protection |
|||
|
4 |
|
LOCATION UPDATING REJECT |
"Reject cause" = “Not authorized for this CSG ". |
|
|
5 |
SS |
The SS releases the RRC connection. |
||
|
5a |
SS |
Set the cell type of cell C to the "Serving cell". Set the cell type of cell A to the "Suitable neighbour cell". |
||
|
The following messages are sent and shall be received on cell C. |
||||
|
6 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration". |
||
|
7 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "LAI" = b, "Mobile Identity" = TMSI1. |
|
|
8 |
SS |
The SS starts integrity protection. |
||
|
9 |
|
LOCATION UPDATING ACCEPT |
Mobile identity = TMSI, LAI =c. |
|
|
10 |
|
TMSI REALLOCATION COMPLETE |
||
|
11 |
SS |
The SS releases the RRC connection. |
||
|
12 |
Set the cell type of cell A to the "non-suitable ‘Off’ cell ". Set the cell type of cell C to the "Suitable neighbour cell". Set the cell type of cell D to the " Serving cell ". |
|||
|
13 |
SS checks that UE does not initiate a RRC Connection on Cell D in 30sec |
|||
|
NOTE: The definitions for "Serving cell", "Suitable neighbour cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
9.4.2.6.5 Test requirements
At step 1, UE Allowed CSG List shall contain CSG 1 and CSG 2.
At step 4, when the UE receives LOCATION UPDATING REJECT, UE shall:
– delete the CSG1 from the Allowed CSG List.
– Allowed CSG List shall contain only CSG 2.
At step 7, the UE shall perform normal location updating on Cell C.