12.4.1 Normal routing area updating

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

The routing area updating procedure is a GMM procedure used by PS UEs of UE operation mode A or C that are IMSI attached for PS services only.

12.4.1.1a Routing area updating / accepted

12.4.1.1a.1 Definition

12.4.1.1a.2 Conformance requirement

1) If the network accepts the routing area updating procedure and reallocates a P-TMSI, the UE shall acknowledge the new P-TMSI and continue communication with the new P-TMSI.

2) If the network accepts the routing area updating procedure from the UE without reallocation of the old P-TMSI, the UE shall continue communication with the old P-TMSI.

3) The routing area updating procedure shall also be used by a UE which is attached for PS services if a new PLMN is entered.

Reference

3GPP TS 24.008 clause 4.7.5, 4.7.5.1.

12.4.1.1a.3 Test purpose

To test the behaviour of the UE if the network accepts the routing area updating procedure.

The following cases are identified:

1) P-TMSI / P-TMSI signature is reallocated.

2) Old P-TMSI / P-TMSI signature is not changed.

To test the behaviour of the UE if the UE enters the new PLMN.

12.4.1.1a.4 Method of test

Initial condition

System Simulator:

Three cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4), cell C in MCC2/MNC1/LAC1/RAC2 (RAI-7).
All three cells are operating in network operation mode II.
The PLMN contains cell C is equivalent to the PLMN that contains cell A.

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) in all cells.

Sintrasearch and Sintersearch values for cells A, B and C 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 IMSI.

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
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

1) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS reallocates the P-TMSI and returns ROUTING AREA UPDATE ACCEPT message with a new P-TMSI. The UE acknowledge the new P-TMSI by sending ROUTING AREA UPDATE COMPLETE message. Further communication UE – SS is performed by the new P-TMSI. The UE will not answer signalling addressed to the old P-TMSI.

2) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS accepts the P-TMSI and returns ROUTING AREA UPDATE ACCEPT message without any P-TMSI. Further communication UE – SS is performed by the P-TMSI.

3) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS reallocates the P-TMSI and returns ROUTING AREA UPDATE ACCEPT message with a new P-TMSI. The UE acknowledge the new P-TMSI by sending ROUTING AREA UPDATE COMPLETE message.

Expected Sequence

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". Set the cell type of cell C to the "Suitable neighbour cell". (see note)
2	UE			The UE is set to attach to PS services only (see ICS). If that is not supported by the UE, goto step 32.
3	UE			The UE is powered up or switched on and initiates an attach (see ICS).
3a	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1 Equivalent PLMN: MCC = 2, MNC = 1
6	->		ATTACH COMPLETE
6a	SS			The SS releases the RRC connection.
				The following messages are sent and shall be received on cell B.
7	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
7a	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
8	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ P-TMSI-2 signatureOld P-TMSI signature= Routing area identityOld = RAI-1
8a	SS			The SS starts integrity protection.
9	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Mobile identity = P-TMSI-1 P-TMSI-1 signature Routing area identity = RAI-4 Equivalent PLMNs = MCC2,MNC1
10	->		ROUTING AREA UPDATE COMPLETE
11			Void
11b			Void
11c	SS			The SS releases the RRC connection.
11d	<-		PAGING TYPE1	Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = Paging order is for PS services.
11e	SS			SS verifies that the UE transmits an RRC CONNECTION REQUEST message. SS will reject this request. The IE "Establishment cause" is not checked.
12	<-		PAGING TYPE1	Mobile identity = P-TMSI-2 Paging order is for PS services.
13	UE			No response from the UE to the request. This is checked for 10 seconds.
				The following messages are sent and shall be received on cell A.
14	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)
15	UE			Cell A is preferred by the UE.
15a	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
16	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-4
16a	SS			The SS starts integrity protection.
17	<-		ROUTING AREA UPDATE ACCEPT	No new mobile identity assigned. P-TMSI not included. Update result = ‘RA updated’ P-TMSI-1 signature Routing area identity = RAI-1 Equivalent PLMN: MCC = 2, MNC = 1
17a	SS			The SS releases the RRC connection.
18	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 Paging order is for PS services. Paging cause = "Terminating interactive call".
18a	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call"
18b			Void
18c			Void
19	->		SERVICE REQUEST	service type = "paging response"
19aa	SS			The SS starts integrity protection.
19a	SS			The SS releases the RRC connection.
				The following messages are sent and shall be received on cell C.
20	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell C to the "Serving cell". (see note)
21	UE			Cell C is preferred by the UE.
21a	UE		Registration on CS	See TS 34.108 This is applicable only for UE in UE operation mode A.
22	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
23	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-1
24	SS			The SS starts integrity protection.
25	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-3 P-TMSI Signature = P-TMSI-3 signature Routing area identity = RAI-7 Equivalent PLMNs = MCC1,MNC1
26	->		ROUTING AREA UPDATE COMPLETE
27	SS			The SS releases the RRC connection.

28	UE			The UE is switched off or power is removed (see ICS).
29	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Detach".
30	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
31	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.
32	UE			The UE is set to attach to both the PS and non-PS services (see ICS) and the test is repeated from step 3 to step 31.
NOTE: The definitions for "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.1a.5 Test requirements

At step 3a, 7a, 15a and 22 the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Registration".

At step 18a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Terminating Interactive Call".

At step 29 the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Detach".

At step4, 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 step8, UE shall;

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

At step13, when the UE receives the paging message for PS domain with Mobile identity = P-TMSI-2, UE shall:

– not respond to the paging message for PS domain.

At step16, UE shall;

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

At step19, when the UE receives the paging message for PS domain with Mobile identity = P-TMSI-1, UE shall:

– respond to the paging message for PS domain by sending the SERVICE REQUEST message.

At step23, UE shall;

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

12.4.1.1b Routing area updating / accepted / Signalling connection re-establishment

12.4.1.1b.1 Definition

12.4.1.1b.2 Conformance requirement

When the UE receives an indication from the lower layers that the RRC connection has been released with cause "Directed signalling connection re-establishment", then the UE shall enter PMM-IDLE mode and initiate immediately a normal routing area update procedure (the use of normal or combined procedure depends on the network operation mode in the current serving cell) regardless whether the routing area has been changed since the last update or not.

Reference

3GPP TS 24.008 clause 4.7.2.5, 4.7.5.1

12.4.1.1b.3 Test purpose

To test the behaviour of the UE if the UE receives a RRC CONNECTION RELEASE message with cause = "Directed signalling connection re-establishment".

12.4.1.1b.4 Method of test

Initial condition

System Simulator:

One cell(Cell A) in MCC1/MNC1/LAC1/RAC1 (RAI-1) operating in network operation mode II.

User Equipment:

The UE has a valid TMSI, P-TMSI-1 and RAI-1

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
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

a) The UE initiates a Service request procedure in order to establish the PS signalling connection for the upper layer signalling.

b) After the Service request procedure is complete, the SS sends the RRC CONNECTION RELEASE message with cause = "Directed signalling connection re-establishment" to the UE.

c) After the UE release the RRC connection, the UE initiate immediately a normal routing area update procedure.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set in UE operation mode C (see ICS). If that is not supported by the UE, goto step 19.
2	UE			The UE is powered up or switched on and initiates an attach (see ICS).
3	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI1
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	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
7	->		SERVICE REQUEST	Service type = "signalling",
8	<-		AUTHENTICATION AND CIPHERING REQUEST
9	->		AUTHENTICATION AND CIPHERING RESPONSE
10	SS			The SS starts integrity protection.
10a	SS			After reception of Activate PDP Context request SS sends Activate PDP context Reject (with cause 31) so that timer T3380 is stopped in the UE.
10b	SS			A non auto attach UE may optionally send Detach Request. After receiving Detach Request Message, SS does not respond to this and moves to step 11.
11	SS			The SS releases the RRC connection, using Release cause=Directed Signalling Connection Re-establishment
12			Void
13	SS			SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Call re-establishment".
14			Void
15			Void
16	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ (FOR bit not checked) Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-1
16a				The SS starts integrity protection.
17	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-1
18	->		ROUTING AREA UPDATE COMPLETE
18a	SS			If UE transmits Detach Request Message at step 10b, expect to receive the message again at this step.
19				The UE is set in UE Operation mode A (see ICS). And the test is repeated from step 2 to step 18.

Specific message contents

None.

12.4.1.1b.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 step16, UE shall;

– initiate the routing area updating procedure whether the routing area has been changed since the last update or not.

12.4.1.1c Void

12.4.1.1d Routing area updating / accepted / SMS via GPRS supported

12.4.1.1d.1 Definition

Void

12.4.1.1d.2 Conformance requirement

If the network operates in mode II, a GPRS MS that operates in mode A or B and wishes to be or is simultaneously IMSI attached for GPRS and non-GPRS services, shall use the MM specific procedures listed in subclauses 4.3 and 4.4 and the GMM specific procedures listed in subclauses 4.7.3, 4.7.4 and 4.7.5. The applicability of periodic location updating is further specified in subclause 4.4.2 and the periodic routing area updating is specified in subclause 4.7.2.2. If the GPRS MS, which operates in mode A or B, wishes to be IMSI attached for GPRS and "SMS-only service” or is simultaneously IMSI attached for GPRS and non-GPRS services in order to obtain GPRS services and "SMS-only service", then the GPRS MS shall first complete the GMM specific procedure before performing the MM specific procedures. If this GPRS MS receives in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message the Additional network feature support IE indicating "SMS via GPRS supported", then the GPRS MS shall not perform the MM specific procedure until a new ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message indicating "SMS via GPRS not supported" or the GPRS MS does not wish to be IMSI attached only for GPRS and "SMS-only service".

If the authentication procedure is performed by MM and the authentication is rejected by the network (i.e. upon receive of AUTHENTICATION REJECT), the MS shall in addition set the GPRS update status to GU3 ROAMING NOT ALLOWED and shall, if available, delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number stored. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301 [120] for the case when the EPS authentication is not accepted by the network.

If the PS or CS domain is barred because of domain specific access control, a GPRS MS operating in mode A or B in a network that operates in mode II shall use the MM specific procedures or GMM specific procedures, respectively, in the domain which is unbarred. If the MS detects that a domain changes from barred to unbarred, it shall behave as specified in subclauses 4.3.4.4, 4.4.4.9, 4.5.1.2, 4.7.3.1.5, 4.7.4.1.4, 4.7.5.1.5, and 4.7.13.5.

Reference

3GPP TS 24.008 clauses 4.1.1.2.2.

12.4.1.1d.3 Test purpose

To verify that a UE that wishes to be IMSI attached for GPRS and "SMS-only service" or is simultaneously IMSI attached for GPRS and non-GPRS services in order to obtain GPRS services and "SMS-only service" in a network that operates in NMO II, the UE shall first complete the GMM specific procedure before performing the MM specific procedures.

To verify that a UE that receives in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message the Additional network feature support IE indicating "SMS via GPRS supported", then the GPRS MS shall not perform the MM specific procedure.

12.4.1.1d.4 Method of test

Initial conditions

System Simulator:

Two cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4).
Both cells are operating in network operation mode II.

User Equipment:

The UE has a valid IMSI.

The UE is configured to use the SMS-only service

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode A Yes/No
Switch off on button Yes/No
Support of SMS-only service Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

A GPRS attach procedure for GPRS services and "SMS-only service", is performed. The SS respond with the ATTACH ACCEPT message including additional network feature support IE indicating "SMS via GPRS supported”.

The UE sends a ROUTING AREA UPDATE REQUEST message. The SS respond with the ROUTING AREA UPDATE ACCEPT message including additional network feature support IE indicating "SMS via GPRS supported".

No MM messages shall be sent by the UE during this sequence.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The following messages are sent and shall be received on cell A.
1	SS			The SS is set in network operation mode II. 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	UE			The UE is set in UE operation mode A (see ICS).
3	UE			The UE is powered up or switched on and initiates an attach (see ICS).
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity =IMSI
5	<-		AUTHENTICATION AND CIPHERING REQUEST
6	->		AUTHENTICATION AND CIPHERING RESPONSE
7	SS			The SS starts integrity protection.
8	<-		ATTACH ACCEPT	Attach result = ‘GPRS only’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1 Additional network feature support = ‘SMS via GPRS supported’
9	->		ATTACH COMPLETE
9a				SS releases RRC Connection
				The following messages are sent and shall be received on cell B.
10	SS			Set the cell type of cell A to the " Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
11	UE			Cell B is preferred by the UE.
12	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
12a				SS starts integrity protection
13	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Mobile identity = P-TMSI-1 P-TMSI-1 signature Routing area identity = RAI-4 Equivalent PLMNs = MCC2,MNC1 Additional network feature support = ‘SMS via GPRS supported’
14	->		ROUTING AREA UPDATE COMPLETE
NOTE: The definitions for "Non-Suitable cell", Suitable neighbour cell and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.1d.5 Test requirements

After step 9: No MM messages shall be sent by the UE.

12.4.1.1dm Handling of MBMS context status information in ROUTING AREA UPDATE procedure/ MBMS Multicast Service

12.4.1.1dm.1 Definition

This Test is applicable for all Rel-6 UEs supporting MBMS multicast services.

12.4.1.1dm.2 Conformance requirement

If the MBMS context status information element is included in the ROUTING AREA UPDATE ACCEPT message, then the MS shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are not in SM state PDP-INACTIVE in the MS, but are indicated by the network as being in state PDP-INACTIVE. If no MBMS context status information element is included, then the MS shall deactivate all those MBMS contexts locally which are not in SM state PDP-INACTIVE in the MS.

Reference

3GPP TS 24.008 [4] clause 4.7.5.1.3.

12.4.1.1dm.3 Test purpose

1. To verify that the UE includes correctly the MBMS context status information in the ROUTING AREA UPDATE REQUEST message.

2. To verify that if the MBMS context status information element is included in the ROUTING AREA UPDATE ACCEPT message, then the UE deactivates all those MBMS contexts locally (without peer to peer signalling between the UE and network) which are not in SM state PDP-INACTIVE in the UE, but are indicated by the network as being in state PDP-INACTIVE.

3. To verify that if no MBMS context status information element is included, then the UE deactivates all MBMS contexts locally which are not in SM state PDP-INACTIVE in the MS.

12.4.1.1dm.4 Method of test

Initial condition

System Simulator:

Three MBMS cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4), cell C in MCC2/MNC1/LAC1/RAC2 (RAI-7).
All three cells are operating in network operation mode II.
The PLMN contains cell C is equivalent to the PLMN that contains cell A.

Sintrasearch and Sintersearch values for cells A, B and C are set to 20 dB.

Note: Cell A is mapped to Cell 21, Cell B is mapped to Cell 22 and Cell C is mapped to Cell 24 as found in TS 34.108 [9] clause 6.1.4.3.

User Equipment:

The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN in cell A.

The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

The UE has one PDP context activated, three MBMS contexts activated in SM state MBMS-ACTIVE.

PDP1: trans_id 0 and nsapi 5

MBMS-1 (MBMS-ACTIVE): trans_id 1 and nsapi 128

MBMS-2 (MBMS-ACTIVE): trans_id 2 and nsapi 129

MBMS-3 (MBMS-ACTIVE): trans_id 3 and nsapi 130

Related ICS/IXIT statements

MBMS Multicast service application available on UE Yes/No

UE operation mode A Yes/No
UE operation mode C Yes/No
Switch off on button Yes/No

Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

1) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS verifies the MBMS context status IE and returns a ROUTING AREA UPDATE ACCEPT message with a different MBMS context status IE.

2) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS verifies the MBMS context status IE and returns a ROUTING AREA UPDATE ACCEPT message without an MBMS context status IE.

3) The UE sends a ROUTING AREA UPDATE REQUEST message. The SS verifies the MBMS context status IE is not contained in the message and returns a ROUTING AREA UPDATE ACCEPT message without an MBMS context status IE.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
2				The following messages are sent and shall be received on cell B.
3	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
4			ROUTING AREA UPDATE REQUEST	UE sets nsapi 128 and 129 and 130 as 1 in MBMS context Status IE and all other as 0.
5	SS			The SS starts integrity protection.
6			ROUTING AREA UPDATE ACCEPT	SS sets nsapi 128 as 1 and nsapi 129 and 130 as 0 in MBMS Context Status IE. UE locally deactivates MBMS context with nsapi 129 and nsapi 130.
7			ROUTING AREA UPDATE COMPLETE
8	SS			The SS releases the RRC connection.
9	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)
10				The following messages are sent and shall be received on cell A.
11	UE			Cell A is preferred by the UE.
12	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
13			ROUTING AREA UPDATE REQUEST	UE sets nsapi 128 as 1 in MBMS context Status IE and all other as 0. SS verifies UE deactivated nsapi 129 and 130.
14	SS			The SS starts integrity protection.
15			ROUTING AREA UPDATE ACCEPT	SS does not include PDP context status and MBMS Context Status IE. The UE locally deactivates all MBMS contexts and PDP contexts.
16			ROUTING AREA UPDATE COMPLETE
17	SS			The SS releases the RRC connection.
18	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell C to the "Serving cell". (see note)
19				The following messages are sent and shall be received on cell C.
20	UE			Cell C is preferred by the UE.
21	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
22			ROUTING AREA UPDATE REQUEST	UE does not include PDP context status IE and MBMS Context Status IE. SS verifies UE deactivated nsapi 128 and UE does not include MBMS and PDP context status IEs when no PDP and MBMS context exists.
23				The SS starts integrity protection.
24			ROUTING AREA UPDATE ACCEPT	SS does not include PDP and MBMS Context Status IEs.
25			ROUTING AREA UPDATE COMPLETE
NOTE: The definitions for "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 [9] clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

ROUTING AREA UPDATE REQUEST (step 4)

Information Element	Value/remark
MBMS context status
MBMS context status IEI	35
Length of MBMS context status contents	1
	07 (NSAPI 128 =1, NSAPI 129 = 1, NSAPI 130 = 1)

ROUTING AREA UPDATE ACCEPT (step 6)

Information Element	Value/remark
PDP context status
PDP context status IEI	32
Length of PDP context status contents	1
	2x (NSAPI(5)=1)
MBMS context status
MBMS context status IEI	35
Length of MBMS context status contents	1
	01 (NSAPI 128 =1, NSAPI 129 = 0, NSAPI 130 = 0)

ROUTING AREA UPDATE REQUEST (step 13)

Information Element	Value/remark
MBMS context status
MBMS context status IEI	35
Length of MBMS context status contents	1
	01 (NSAPI 128 =1, NSAPI 129 = 0, NSAPI 130 = 0)

Step 15: The SS does not include PDP Context status IE and MBMS Context Status IE.

Note: Allocate P-TMSI in all ROUTING AREA UPDATE ACCEPT.

12.4.1.1dm.5 Test requirements

At step 4, the UE shall set nsapi 128, 129 and 130 as 1 in the MBMS context Status IE and all others as 0.

At step 13, the UE shall set nsapi 128 as 1 in the MBMS context Status IE and all others as 0.

At step 22, the UE shall not include the PDP context status IE and the MBMS Context Status IE.

12.4.1.1e Routing area updating / accepted / low priority override

12.4.1.1e.1 Definition

Void

12.4.1.1e.2 Conformance requirement

An MS configured for NAS signalling low priority (see 3GPP TS 24.368 [135], 3GPP TS 31.102 [112]) indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured to NAS signalling low priority" except for the following cases in which the MS shall set the low priority indicator to "MS is not configured for NAS signalling low priority":

– the MS is performing an attach for emergency bearer services;

– the MS has a PDN connection for emergency bearer services established and is performing mobility management procedures, or is establishing a PDN connection for emergency bearer services;

– the MS configured for dual priority is requested by the upper layers to establish a PDN connection with the low priority indicator set to "MS is not configured for NAS signalling low priority";

– the MS configured for dual priority is performing EPS session management procedures related to the PDN connection established with low priority indicator set to "MS is not configured for NAS signalling low priority";

– the MS configured for dual priority has a PDN connection established by setting the low priority indicator to "MS is not configured for NAS signalling low priority" and is performing EPS mobility management procedures;

– the MS is accessing the network with access class 11 – 15; or

– the MS is responding to paging.

The network may use the NAS signalling low priority indication for NAS level mobility management congestion control on a per core network node basis and APN based congestion control.

If the NAS signalling low priority indication is provided in an ACTIVATE PDP CONTEXT REQUEST message, the SGSN stores the NAS signalling low priority indication within the default PDP context activated due to this request.

Reference

3GPP TS 24.008 clauses 1.8.

12.4.1.1e.3 Test purpose

To verify that a MS configured for dual priority and has a PDN connection established by setting the low priority indicator to "MS is not configured for NAS signalling low priority", set the low priority indicator to "MS is not configured for NAS signalling low priority" when it is performing mobility management procedures

12.4.1.1e.4 Method of test

Initial condition

System Simulator:

Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4).
Both cells are operating in network operation mode II.

User Equipment:

The UE has a valid P-TMSI-1 and RAI-1. MS is Idle Updated on cell A.

The UE is configured for NAS signalling low priority

The UE is configured for NAS signalling low priority override

The UE is equipped with a USIM containing default values except for those listed below.

USIM field

Value

EF_UST

Service 96 is supported

EF_NASCONFIG

“NAS_SignallingPriority is set to “NAS signalling low priority”.

“Override_NAS_SignallingLowPriority” is set to 1, as defined in TS 24.368, clause 5.3.

“ExtendedAccessBarring is set to 1 which indicate the extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8.

OverrideExtendedAccessBarring is set to 1 which indicate the Override extended access barring is applied for the UE” as defined in TS 24.368, clause 5.10.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode C Yes/No
UE operation mode A Yes/No
Automatic attach procedure when UE identity cannot be derived by the network Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The UE initiates the ATTACH procedure, indicating that it is configured for NAS signalling low priority.

Configure the UE to override NAS signalling low priority and initiate a PDP context procedure.

SS releases the RRC Connection.

When the UE enters a new routing area is performs the Routing Area Update procedure, indicating it is not configured for NAS signalling low priority.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following messages are sent and shall be received on cell A.
1	SS			The SS is set in network operation mode II. 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	–		Void
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4	UE		Registration on CS	See TS 34.108 This step is applied only for UE in UE operation mode A. Parameter mobile identity is TMSI.
5	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity =P-TMSI-1 Old Routing area identity = RAI-1 Device properties = ‘MS is configured for NAS signalling low priority’
6	<-		AUTHENTICATION AND CIPHERING REQUEST
7	->		AUTHENTICATION AND CIPHERING RESPONSE
8	SS			The SS starts integrity protection.
9	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
10	->		ATTACH COMPLETE
10A1	SS			SS releases the RRC connection
10A2	UE			The UE is configured to override NAS signalling low priority and Initiate a PDP context activation
10A3	->		ACTIVATE PDP CONTEXT REQUEST	The UE requests a PDP context activation. Device properties = ‘MS is not configured for NAS signalling low priority’
10A4	<-		ACTIVATE PDP CONTEXT ACCEPT
10A5	SS			SS releases the RRC connection
				The following messages are sent and shall be received on cell B.
11	SS			Set the cell type of cell A to the " Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
12	UE			Cell B is preferred by the UE.
13	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1 Device properties = ‘MS is not configured for NAS signalling low priority’
13A	SS			The SS starts integrity protection
14	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Mobile identity = P-TMSI-1 P-TMSI-1 signature Routing area identity = RAI-4 Equivalent PLMNs = MCC2,MNC1
15	->		ROUTING AREA UPDATE COMPLETE
NOTE: The definitions for "Non-Suitable cell", Suitable neighbour cell and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.1e.5 Test requirements

Step 5: ATTACH REQUEST message contains the Device properties IE set to ‘MS is configured for NAS signalling low priority’.

Step 10A3: ACTIVATE PDP CONTEXT REQUEST message contains the Device properties IE set to ‘MS is not configured for NAS signalling low priority’.

Step 13: ROUTING AREA UPDATE REQUEST message contains the Device properties IE set to ‘MS is not configured for NAS signalling low priority’.

12.4.1.1f Routing area updating / accepted / PSM

12.4.1.1f.1 Definition

Void

12.4.1.1f.2 Conformance requirement

An MS supporting PSM may request the network to assign a value for T3324 by including a requested timer value in:

– the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message (in A/Gb mode and Iu mode ); or

– the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message (in S1 mode).

The value of timer T3324 can be sent by the network to the MS in:

– the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message (in A/Gb mode and Iu mode ); and

– the ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message (in S1 mode).

…

The network accepts the use of PSM by providing a specific value for timer T3324 when accepting the attach or routing area updating procedure. The MS may use PSM only if the network has provided the T3324 value IE during the last attach or routing area updating procedure with a value different from "deactivated".

…

Periodic routing area updating is used to periodically notify the availability of the MS to the network. The value of the update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "periodic updating". The procedure is controlled in the MS by timer T3312. When timer T3312 expires, the periodic routing area updating procedure is started. Start and reset of timer T3312 is described in subclause 4.7.2.2.

The normal routing area updating procedure is initiated:

– when the MS detects a change of the routing area in state GMM-REGISTERED;

– when the MS determines that GPRS resumption shall be performed;

– when the MS needs to update the network with the new MS Radio Access Capability IE;

– when the MS needs to update the network with the new DRX parameter IE;

– in Iu mode, to re-synchronize the PMM mode of MS and network after RRC connection release with cause "Directed signalling connection re-establishment", see subclause 4.7.2.5;

– in Iu mode, to re-synchronize the PMM mode of MS and network after inter-system change not due to PS handover from PMM-CONNECTED mode in Iu mode to A/Gb mode or S1 mode, if the MS performs an inter – system change back to Iu mode without sending a ROUTING AREA UPDATE REQUEST message while in A/Gb mode or a TRACKING AREA UPDATE REQUEST message while in S1 mode;

– in Iu mode and A/Gb mode, after intersystem change from S1 mode, and the GMM receives an indication of "RRC connection failure" from lower layers due to lower layer failure while in S1 mode. In this case, if the TIN indicates "RAT-related TMSI", the MS shall set the TIN to "GUTI" before initiating the routing area updating procedure;

– in A/Gb mode, after intersystem change from S1 mode if the TIN indicates "RAT-related TMSI", but the MS is required to perform routing area updating for IMS voice termination as specified in annex P.4;

– when the MS enters GMM-REGISTERED.NORMAL-SERVICE and the TIN indicates "GUTI";

– when the MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the Allowed CSG list; or in the Operator CSG list;

– when the MS supports SRVCC and changes the mobile station classmark 2, mobile station classmark 3 or the supported codecs;

– when the MS changes the MS network capability information;

– when the UE’s usage setting or the voice domain preference for E-UTRAN change in the MS;

– when the MS activates mobility management for IMS voice termination as specified in annex P.2 and the TIN indicates "RAT-related TMSI";

– upon reception of a paging indication, using P-TMSI, even if the timer T3346 is running and the MS is in state GMM-REGISTERED.ATTEMPTING-TO-UPDATE;

– in A/Gb mode, after intersystem change from S1 mode via cell change order procedure not due to CS fallback, if the TIN indicates "RAT-related TMSI"; in this case the MS shall set the TIN to "GUTI" before initiating the routing area updating procedure;

– in A/Gb mode, after Inter RAT handover from S1 mode or Iu mode;

– when the UE needs to request the use of PSM or needs to stop the use of PSM; or

– when a change in the PSM usage conditions at the MS requires a different timer T3312 value or different timer T3324 value.

NOTE: A change in the PSM usage conditions at the MS can include e.g. a change in the MS configuration, a change in requirements from upper layers or the battery running low at the MS.

…

If the MS supports PSM and requests the use of PSM, the MS shall include the T3324 value IE with a requested timer value in the ROUTING AREA UPDATE REQUEST message. When the MS includes the T3324 value IE and the MS indicates support for extended periodic timer value in the MS network feature support IE, it may also include the T3312 extended value IE to request a particular T3312 value to be allocated.

Reference

3GPP TS 24.008 clause 4.7.2.8, 4.7.2.9, 4.7.5.1

12.4.1.1f.3 Test purpose

1. To verify that the UE indicates PSM by providing a T3324 value IE during the RAU procedure

2. To verify that an UE accepts the value for timer T3324 provided by the network

3. To verify that the UE, upon expiry of the timer T3324 deactivate the AS layer and activate PSM by entering the state GMM-REGISTERED.NO-CELL-AVAILABLE

4. To verify that the UE can deactivate PSM

12.4.1.1f.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode II.

User Equipment:

The UE has a valid P-TMSI-1 and RAI-1. MS is Idle Updated on cell A.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode A Yes/No
UE operation mode C Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No
Support of Power Saving Mode Yes/No

Test procedure

1) The UE sends a ROUTING AREA UPDATE REQUEST message indicating activation of Power Save Mode by including the T3324 timer set to 2 minutes. The SS acknowledge the PSM request by including the T3324 timer set to 2 minutes in the ROUTING AREA UPDATE ACCEPT message.

2) When timer T3324 expires the UE enters state GMM-REGISTERED.NO-CELL-AVAILABLE. The SS sends a PAGING TYPE1 message that is not acknowledge by the UE.

3) The UE deactivates PSM by sending a ROUTING AREA UPDATE REQUEST message indicating a new value of the T3324 timer set to 4 minutes. The SS acknowledge the new timer value by including the T3324 timer set to 4 minutes in the ROUTING AREA UPDATE ACCEPT message.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set to attach to the PS services only (see ICS). If this is not supported by the UE, go to step 20.
2	UE			The UE is powered up or switched on and initiates an attach (see ICS).
3	UE		Registration on CS	This step is applied only for UE in UE operation mode A. See TS 34.108 SS allocates Mobile identity = TMSI-1.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity =P-TMSI-1 Old Routing area identity = RAI-1
5	<-		AUTHENTICATION AND CIPHERING REQUEST
6	->		AUTHENTICATION AND CIPHERING RESPONSE
7	SS			The SS starts integrity protection.
8	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
9	->		ATTACH COMPLETE
10				The UE requests PSM by MMI or by AT command.
11	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity T3324 value = 2 minutes
12	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ No new mobile identity assigned. P-TMSI not included. Routing area identity = RAI-1 T3324 value = 2 minutes
13	->		ROUTING AREA UPDATE COMPLETE
				When the T3324 timer expires the following message is sent.
14	<-		PAGING TYPE1	Mobile identity = P-TMSI-2 Paging order is for PS services.
15	UE			Check: No response from the UE to the request. This is checked for 10 seconds.
16				The UE requests to deactivate PSM by requesting to use a new value for timer T3324. This can be initiated by MMI or AT command.
17	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1 T3324 value = 4 minutes
18	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ No new mobile identity assigned. P-TMSI not included. Update result = ‘RA updated’ Routing area identity = RAI-1 T3324 value = 4 minutes
19	->		ROUTING AREA UPDATE COMPLETE
20	UE			The UE is set to attach to both the PS and non-PS services (see ICS) and the test is repeated from step 2 to step 19.

Specific message contents

None.

12.4.1.1f.5 Test requirements

At step 11 UE shall include the T3324 IE set to a 2 minutes.

At step 15, when the UE receives the paging message for PS domain, UE shall not respond to the paging message for PS domain.

At step 17 UE shall include the T3324 IE set to 4 minutes.

12.4.1.1g Routing area updating / accepted / DCN

12.4.1.1g.1 Definition

12.4.1.1g.2 Conformance requirement

If the ROUTING AREA UPDATE ACCEPT message contains the DCN-ID IE, then the MS shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301 [120], annex C.

In a shared network or in a multi-operator core network (MOCN) with common GERAN, if the ROUTING AREA UPDATE ACCEPT message contains the DCN-ID IE and the PLMN identity of the CN operator IE, the MS shall store the included DCN-ID value with the PLMN identity indicated in the PLMN identity of the CN operator IE, and the included DCN-ID value with the PLMN identity indicated in the RAI in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301 [120], annex C.

…

The network shall initiate the P-TMSI reallocation procedure by sending a P-TMSI REALLOCATION COMMAND message to the MS and shall start the timer T3350.

The P-TMSI REALLOCATION COMMAND message shall contain a new combination of P-TMSI, RAI and optionally a P-TMSI signature or a DCN-ID or both allocated by the network.

The network may suspend the transmission of user data during the P-TMSI reallocation procedure.

…

Upon receipt of the P-TMSI REALLOCATION COMMAND message, the MS shall store the routing area identifier (RAI) and the P-TMSI. Furthermore, the MS shall send a P-TMSI REALLOCATION COMPLETE message to the network.

If a P-TMSI signature is present in the P-TMSI REALLOCATION COMMAND message, the MS shall store the new P-TMSI signature and shall if available delete the old P-TMSI signature. If no P-TMSI signature is present in the P-TMSI REALLOCATION COMMAND message, the old P-TMSI signature, if available, shall be kept.

If the P-TMSI REALLOCATION COMMAND message contains the DCN-ID IE, then the MS shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301 [120], annex C.

…

When an ATTACH REQUEST message, or a ROUTING AREA UPDATE REQUEST message after a routing area change, is sent to establish a PS signalling connection, the MS NAS also provides the lower layers with the DCN-ID according to the following rules:

a) if a DCN-ID for the PLMN code of the selected PLMN is available in the MS, this DCN-ID the MS NAS shall provide this DCN-ID to the lower layers; or

b) if no DCN-ID for the PLMN code of the selected PLMN is available but a Default_DCN_ID value is available in the MS, as specified in 3GPP TS 24.368 [135] or in USIM file NAS_CONFIG as specified in 3GPP TS 31.102 [112], the Default_DCN_ID value MS NAS shall provide the Default_DCN_ID value to the lower layers.

…

The UE shall, in the INITIAL DIRECT TRANSFER message:

1> set the IE "NAS message" as received from upper layers; and

1> set the IE "CN domain identity" as indicated by the upper layers; and

1> set the IE "Intra Domain NAS Node Selector" as follows:

2> derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and

2> provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:

1. base the routing parameter for IDNNS on TMSI (CS domain) or on PTMSI (PS domain) according to the TMSI/PTMSI provided by upper layers, where the PTMSI may be mapped from a valid GUTI;

2. base the routing parameter for IDNNS on IMSI when no TMSI/PTMSI is provided by upper layers;

3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.

1> if the UE, on the existing RRC connection, has received a dedicated RRC message containing the IE "Primary PLMN Identity" in the IE "CN Information Info":

2> set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the latest PLMN information received via dedicated RRC signalling. If NAS has indicated the PLMN towards which a signalling connection is requested, and this PLMN is not in agreement with the latest PLMN information received via dedicated RRC signalling, then the initial direct transfer procedure shall be aborted, and NAS shall be informed.

1> if the UE, on the existing RRC connection, has not received a dedicated RRC message containing the IE "CN Information Info" , and if the IE "Multiple PLMN List" was broadcast in the cell where the current RRC connection was established:

2> set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the PLMN chosen by higher layers [5, 25] amongst the PLMNs in the IE "Multiple PLMN List" broadcast in the cell where the RRC connection was established.

1> if the IE "Activated service list" within variable MBMS_ACTIVATED_SERVICES includes one or more MBMS services with the IE "Service type" set to "Multicast" and;

1> if the IE "CN domain identity" as indicated by the upper layers is set to "CS domain" and;

1> if the variable ESTABLISHED_SIGNALLING_CONNECTIONS does not include the CN domain identity ‘PS domain’:

2> include the IE "MBMS joined information";

2> include the IE "P-TMSI" within the IE "MBMS joined information" if a valid PTMSI is available.

1> if the UE is in CELL_FACH state and the IE "CN domain identity" as indicated by the upper layers is set to "CS domain":

2> if the value of the variable ESTABLISHMENT_CAUSE is set to "Originating Conversational Call" or "Emergency Call":

3> set the value of the IE "CS Call type" to "speech", "video" or "other" according to the call being initiated.

1> if the variable ESTABLISHMENT_CAUSE is initialised:

2> set the IE "Establishment cause" to the value of the variable ESTABLISHMENT_CAUSE;

2> clear the variable ESTABLISHMENT_CAUSE.

1> include the IE "DCN Identity" if a DCN value [91] was received from upper layers;

1> calculate the START according to subclause 8.5.9 for the CN domain as set in the IE "CN Domain Identity"; and

1> include the calculated START value for that CN domain in the IE "START".

Reference

3GPP TS 24.008, clauses 4.7.5.1, 4.7.6 and 4.7.1.8a, TS 25.331, clause 8.1.8.2

12.4.1.1g.3 Test purpose

1. To verify that the UE uses the pre-provisioned default DCN-ID

2. To verify that the UE accepts a PLMN specific DCN Identity provided by the network.

3. To verify that the UE uses the PLM specific DCN Identity provided by the network.

12.4.1.1g.4 Method of test

Initial condition

System Simulator:

Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4).
Both cells are operating in network operation mode II.

User Equipment:

The UE is equipped with a USIM containing default values except for those listed below.

USIM field	Value
EF_UST	Service 96 is supported.
EF_NASCONFIG	“Default_DCN_ID value” provisioned with the value 0, as defined in TS 24.368, clause 5.10e.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode A Yes/No
UE operation mode C Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

1) The UE sends an Initial Direct Transfer RRC message containing a ROUTING AREA UPDATE REQUEST message. The Initial Direct Transfer message contains the IE "DCN Identity" set to the provisioned DCN value.

2) The SS sends an P-TMSI REALLOCATION COMMAND message with the DCN-ID IE set to a different DCN-ID from the default value provisioned in the UE. The UE acknowledge by sending an P-TMSI REALLOCATION COMPLETE message.

3) The SS changes the radio conditions to force the UE to move to cell B.

4) The UE sends an Initial Direct Transfer RRC message containing a ROUTING AREA UPDATE REQUEST message. The Initial Direct Transfer message contains the IE "DCN Identity" set to the value received in the P-TMSI REALLOCATION COMMAND message.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set to attach to the PS services only (see ICS). If this is not supported by the UE, go to step 24.
				The following messages are sent and shall be received on cell A.
2	SS			The SS is set in network operation mode II. 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)
3	UE			The UE is powered up or switched on and initiates an attach (see ICS).
4	UE		Registration on CS	This step is applied only for UE in UE operation mode A. See TS 34.108 SS allocates Mobile identity = TMSI-1.
5	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity =P-TMSI-1 Old Routing area identity = RAI-1
6	<-		AUTHENTICATION AND CIPHERING REQUEST
7	->		AUTHENTICATION AND CIPHERING RESPONSE
8	SS			The SS starts integrity protection.
9	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
10	->		ATTACH COMPLETE
11				The SS releases the RRC connection.
				The following messages are sent and shall be received on cell B.
11A				Set the cell type of cell A to the " Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
12	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1 SS checks that the IE " DCN Identity " in the received RRC INITIAL DIRECT TRANSFER message is set to the default DCN ID provisioned in the UE
13	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ No new mobile identity assigned. P-TMSI not included. Routing area identity = RAI-4
14			Void
15	<-		P-TMSI REALLOCATION COMMAND	Allocated P-TMSI = P-TMSI-3 P-TMSI Signature = P-TMSI-3 signature Routing area identity = RAI-4 DCN-ID = “different DCN-ID from the default provisioned in the UE”
16	->		P-TMSI REALLOCATION COMPLETE
17	SS			The SS releases the RRC connection.
				The following messages are sent and shall be received on cell A.
18	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)
19	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-3 signature Old Routing area identity = RAI-4 SS checks that the IE " DCN Identity " in the received RRC INITIAL DIRECT TRANSFER message is set to the DCN ID received by the UE in the P-TMSI REALLOCATION COMMAND message in step 15.
20				The SS starts integrity protection
21	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Mobile identity = P-TMSI-1 P-TMSI-1 signature Routing area identity = RAI-1 Equivalent PLMNs = MCC2,MNC1
22	->		ROUTING AREA UPDATE COMPLETE
23	SS			The SS releases the RRC connection.
24	UE			The UE is set to attach to both the PS and non-PS services (see ICS) and the test is repeated from step 2 to step 23.
NOTE: The definitions for "Non-Suitable cell", Suitable neighbour cell and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.1g.5 Test requirements

At step 12 UE shall include the DCN Identity IE set to the pre-configured value in the INITIAL DIRECT TRANSFER RRC message.

At step 15 the UE shall store the value of the DCN-ID IE carried by the P-TMSI REALLOCATION COMMAND message.

At step 19 UE shall include the DCN Identity IE, set to the value received in step 15, in the INITIAL DIRECT TRANSFER RRC message.

12.4.1.2 Routing area updating / rejected / IMSI invalid / illegal ME

12.4.1.2.1 Definition

12.4.1.2.2 Conformance requirement

1) If the network rejects a routing area updating procedure from the User Equipment with the cause ‘Illegal ME’, the User Equipment shall consider USIM invalid for PS services until power is switched off or USIM is removed.

2) If the network rejects a routing area updating procedure from the User Equipment with the cause ‘Illegal ME’, the User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.

Reference

3GPP TS 24.008 clause 4.7.5.1.

12.4.1.2.3 Test purpose

To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause ‘Illegal ME’.

12.4.1.2.4 Method of test

Initial condition

System Simulator:

Three cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4), cell C in MCC2/MNC1/LAC1/RAC1 (RAI-2).
All three cells are operating in network operation mode II (in case of UE operation mode A)
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) in all cells.

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 P-TMSI-1 and RAI-1.

The UE has been registered in the CS domain.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode C Yes/No
UE operation mode A Yes/No (only if mode C not supported)
USIM removal possible without powering down Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The SS rejects a routing area updating with the cause value ‘Illegal ME’. The SS checks that the UE does not perform PS attach in the same or another PLMN.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following messages are sent and shall be received on cell A.
1	UE			The UE is set in UE operation mode C (see ICS).
2	SS			The SS is set in network operation mode II. 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 "Non-Suitable cell". (see note)
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
3a			Void
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	No new mobile identity assigned. P-TMSI and P-TMSI signature not included. Attach result = ‘GPRS only attached’ Routing area identity = RAI-1
5a				The SS releases the RRC connection.
				The following messages are sent and shall be received on cell B.
6	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
7	UE			Cell B is preferred by the UE.
8	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old Routing area identity = RAI-1
8a				The SS starts integrity protection.
9	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Illegal ME’
10	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 PAGING TYPE1 (used for NW-mode II). Paging order is for PS services.
11	UE			No response from the UE to the request. This is checked for 10 seconds.
				The following messages are sent and shall be received on cell C.
12	SS			Set the cell type of cell B to the "Non-Suitable cell". Set the cell type of cell A to the “Non-Suitable cell”. Set the cell type of cell C to the "Serving cell". (see note)
13	UE			Cell C is preferred by the UE.
14	UE			No ATTACH REQUEST sent to the SS (SS waits 30 seconds).
15	UE			If possible (see ICS) USIM removal is performed. Otherwise if possible (see ICS) switch off is performed. Otherwise the power is removed.
16	UE			The UE gets the USIM replaced, is powered up or switched on and initiates an attach (see ICS).
16a				Step 16b is only performed by UE in operation mode A
16b	UE		Registration on CS	See TS 34.108 SS allocates Mobile identity = TMSI-1.
17	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
17a	<-		AUTHENTICATION AND CIPHERING REQUEST
17b	->		AUTHENTICATION AND CIPHERING RESPONSE
17c	SS			The SS starts integrity protection.
18	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-2
19	->		ATTACH COMPLETE



NOTE: The definitions for "Non-Suitable cell", "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.2.5 Test requirements

At step4, 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 step8, UE shall;

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

At step11, after the routing area updating procedure is rejected with GMM cause = ‘Illegal ME’, UE shall;

– not respond to the paging message for PS domain.

At step14, UE shall,

– not initiate PS attach procedure.

At step17, after the UE is powered up or USIM is replaced, UE shall;

– initiate the PS attach procedure.

12.4.1.3 Routing area updating / rejected / UE identity cannot be derived by the network

12.4.1.3.1 Definition

12.4.1.3.2 Conformance requirement

If the network rejects a routing area updating procedure from the User Equipment with the cause ‘MS identity cannot be derived by the network’, the User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.

Depending on the manufacturer the UE may or may not perform a PS attach procedure.

Reference

3GPP TS 24.008 clause 4.7.5.1.

12.4.1.3.3 Test purpose

To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause ‘MS identity cannot be derived by the network’.

12.4.1.3.4 Method of test

Initial condition

System Simulator:

Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4).
Both cells are operating in network operation mode II (in case of UE operation mode A).
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) in both cells.

User Equipment:

The UE has a valid P-TMSI-1 and RAI-1.

The UE has been registered in the CS domain.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode C Yes/No
UE operation mode A Yes/No (only if mode C not supported)
Automatic attach procedure when UE identity cannot be derived by the network Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The SS rejects a normal routing area updating with the cause value ‘MS identity cannot be derived by the network’. The UE detach locally. A new PS attach may be performed.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following messages are sent and shall be received on cell A.
1	SS			The SS is set in network operation mode II. 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	UE			The UE is set in UE operation mode C (see ICS).
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity =P-TMSI-1 Old Routing area identity = RAI-1
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
6	->		ATTACH COMPLETE
6a				The SS releases the RRC connection
				The following messages are sent and shall be received on cell B.
7	SS			Set the cell type of cell A to the " Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
8	UE			Cell B is preferred by the UE.
9	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
9a				The SS starts integrity protection.
10	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘MS identity cannot be derived by the network’
11	UE			If an automatic attach procedure by the UE is not possible when the UE identity cannot be derived by the network (see ICS) goto step 19.
12			Void
12a	SS			SS shall wait for 1 second to receive the Attach Request in step 13 on the existing RRC Connection. In case ATTACH REQUEST is not received within 1 second then existing RRC Connection is released.
13	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
13a	<-		AUTHENTICATION AND CIPHERING REQUEST
13b	->		AUTHENTICATION AND CIPHERING RESPONSE
13c	SS			The SS starts integrity protection.
14	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-4
15	->		ATTACH COMPLETE
16	UE			The UE is switched off or power is removed (see ICS).
17	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
18	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.
19	<-		PAGING TYPE1	Mobile identity = P-TMSI-2 PAGING TYPE1 (used for NW-mode II). Paging order is for PS services.
20	UE			No response from the UE to the request, as the UE has detached locally. This is checked for 10 seconds.
NOTE: The definitions for "Non-Suitable cell", Suitable neighbour cell and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.3.5 Test requirements

At step4, 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 step9, UE shall;

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

UE shall perform the following actions depending on the implementation of the UE.

Case 1) UE supports an Automatic PS attach procedure.

At step13, UE shall;

– initiate the PS attach procedure.

Case 2) UE does not support an Automatic PS attach procedure.

At step20, when the UE receives the paging message for PS domain, UE shall:

– not respond to the paging message for PS domain.

12.4.1.4a Routing area updating / rejected / location area not allowed

12.4.1.4a.1 Definition

12.4.1.4a.2 Conformance requirement

1) If the network rejects a routing area updating procedure from the User Equipment with the cause ‘location area not allowed’ the User Equipment shall:

1.1 not perform PS attach when in the same location area.

1.2 delete the stored RAI, PS-CKSN, P-TMSI, P-TMSI signature and TMSI, LAI and ciphering key sequence number.

1.3 store the LA in the ‘forbidden location areas for regional provision of service’.

1.4 not delete the list of "equivalent PLMNs".

1.5 perform a cell selection.

2) If the network rejects a routing area updating procedure from the User Equipment with the cause ‘location area not allowed’ the User Equipment:

2.1 may perform routing area update when a new location area is entered.

2.2 shall delete the list of forbidden LAs after switch off (power off).

Reference

3GPP TS 24.008 clauses 4.7.5.1.

12.4.1.4a.3 Test purpose

To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause ‘Location Area not allowed’.

To test that the UE deletes the list of forbidden LAs when power is switched off.

12.4.1.4a.4 Method of test

Initial condition

System Simulator:

Four cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) , cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4), cell C in MCC1/MNC1/LAC2/RAC1 (RAI-3), cell D in MCC2/MNC1/LAC2/RAC1(RAI-6).
All four cells are 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) in all cells.

The PLMN contains Cell D is equivalent to the PLMN that contains Cell C.

NB: i) Cell D will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.1.

User Equipment:

The UE has a valid IMSI.

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
USIM removal possible without powering down Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The SS rejects a routing area updating with the cause value ‘Location Area not allowed’. The SS checks that the UE does not perform PS attach while in the location area, performs PS attach when a new location area is entered and 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
	SS			The following messages are sent and shall be received on cell C.
1	SS			Set the cell type of cell A to the "Non-Suitable cell". Set the cell type of cell B to the "Non-Suitable cell". Set the cell type of cell C to the "Serving cell". Set the cell type of cell D to the "Non-Suitable cell". (see note)
2	UE			The UE is set in UE operation mode C (see ICS). If UE operation mode C not supported, goto step 33.
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell C is preferred by the UE.
3a			Void
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-3 Equivalent PLMNs = MCC2,MNC1
6	->		ATTACH COMPLETE
6a	SS			The SS releases the RRC connection.
				The following messages are sent and shall be received on cell B.
7	SS			Set the cell type of cell B to the "Serving cell". Set the cell type of cell C to the "Non-Suitable cell". (see note)
8	SS			Cell B is preferred by the UE.
8a				The following step is only performed for UE Operation Mode A.
8b	UE		Registration on CS	See TS34.108 Parameter mobile identity is IMSI, Equivalent PLMNs = MCC2,MNC1
9	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ P-TMSI-1 signatureOld P-TMSI signature= Routing area identityOld = RAI-3
9a				The SS starts integrity protection.
10	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Location Area not allowed’
10a	SS			The SS releases the RRC connection.
11	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 PAGING TYPE1 (used for NW-mode II). Paging order is for PS services.
12	UE			No response from the UE to the request. This is checked for 10 seconds.
				The following messages are sent and shall be received on cell A.
13	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)
13a	UE			The UE performs cell selection.
14	UE			Cell A is preferred by the UE.
15	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds)
16	SS			Set the cell type of cell A to the "Non-Suitable cell". Set the cell type of cell D to the "Serving cell". (see note)
16a	UE			The UE performs cell selection.
17	UE			Cell D is preferred by the UE.
				The following messages are sent and shall be received on cell D.
17a				The following step is only performed for UE Operation Mode A.
17b	UE		Registration on CS	See TS34.108 Parameter mobile identity is IMSI
	UE			The UE initiates a PS attach. If UE does not attach automatically, then UE initiates the attach procedure by MMI or AT command.
18	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
18a	<-		AUTHENTICATION AND CIPHERING REQUEST
18b	->		AUTHENTICATION AND CIPHERING RESPONSE
18c	SS			The SS starts integrity protection.
19	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-6 Equivalent PLMNs = MCC1,MNC1
20	->		ATTACH COMPLETE
20a	SS			The SS releases the RRC connection.
21	UE			If possible (see ICS) USIM removal is performed, go to Step 21a, 21b. Otherwise if possible (see ICS) switch off is performed, go to Step22. Otherwise the power is removed, go to Step22.
21a	->		DETACH REQUEST	Type of detach" = “GPRS detach”, "Power off" = Any value
21b	<-		DETACH ACCEPT	Message not sent if power off detach is performed in step 21a. Go to Step22a
22	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
22a	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.
23	UE			The UE gets the USIM replaced, is powered up or switched on and initiates an attach (see ICS).
24	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-2 Old Routing area identity = RAI-6
24a	<-		AUTHENTICATION AND CIPHERING REQUEST
24b	->		AUTHENTICATION AND CIPHERING RESPONSE
24c	SS			The SS starts integrity protection.
25	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-6 Equivalent PLMNs = MCC1,MNC1
26	->		ATTACH COMPLETE
26a	SS			The SS releases the RRC connection.
	SS			The following messages are sent and shall be received on cell A.
27				Set the cell type of cell A to the "Serving cell". Set the cell type of cell D to the "Non-Suitable cell". (see note)
28				Cell A is preferred by the UE.
28a				The following step is only performed for UE Operation Mode A.
28b	UE		Registration on CS	See TS34.108 Parameter mobile identity is IMSI Equivalent PLMNs = MCC2,MNC1
29	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-6
29a	SS			The SS starts integrity protection.
30	<-		ROUTING AREA UPDATE ACCEPT	No new mobile identity assigned. P-TMSI and P-TMSI signature not included. Update result = ‘RA updated’ Routing area identity = RAI-1 Equivalent PLMNs = MCC2,MNC1
30a	SS			The SS releases the RRC connection.
31	UE			The UE is switched off or power is removed (see ICS).
32	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
32a	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.
33	SS			The SS is set in network operation mode II.
34	UE			The UE is set in UE operation mode A (see ICS), cell A is switched off and the test is repeated from step 3 to step 32.
NOTE: The definitions for "Non-Suitable cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.4a.5 Test requirements

At step4, 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 step9, UE shall:

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

At step12, when the UE receives the paging message for PS domain, UE shall:

– not respond to the paging message for PS domain.

At step12 and 15, when in the same location area, UE shall

– not perform PS attach procedure.

At step18, when a new location area is entered, UE shall

– perform the PS attach procedure.

At step24, when the USIM is replaced , UE shall;

– perform the PS attach procedure.

At step29, UE shall;

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

12.4.1.4b Routing area updating / rejected / No Suitable Cells In Location Area

12.4.1.4b.1 Definition

12.4.1.4b.2 Conformance requirement

If the network rejects a routing area updating procedure from the User Equipment with the cause ‘No Suitable Cells In Location Area’, the User Equipment shall:

1.1 store the LA identity in the ‘forbidden location areas for roaming’.

1.2 search for a suitable cell in a different location area on the same PLMN.

1.3 not delete equivalent PLMNs list.

1.4 not delete the MM and GMM contexts

Reference

3GPP TS 24.008 clauses 4.7.5.1.

12.4.1.4b.3 Test purpose

To test the behaviour of the UE if the network rejects the routing area updating procedure with the cause ‘No Suitable Cells In Location Area’.

12.4.1.4b.4 Method of test

Initial condition

System Simulator:

Three cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC2/RAC1 (RAI-3), cell C in MCC1/MNC1/LAC1/RAC2 (RAI-4),

Cell B will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.2.

Cell C will be mapped to Cell 7 as found in TS 34.108 clause 6.1.4.2.

Qqualmin value for cells A and C is -16

All three cells are 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) in all cells.

User Equipment:

The UE has 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
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The SS rejects a routing area updating with the cause value ‘No Suitable Cells In Location Area’. The SS checks that the UE shall perform Routing Area Update procedure when the UE enters a suitable cell in a different location area on the same PLMN.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The UE is set in UE operation mode A or C (see ICS). The following messages are sent and shall be received on cell C.
1	SS			Set the cell type of cell A to the "Non-Suitable cell". Set the cell type of cell B to the "Non-Suitable cell". Set the cell type of cell C to the "Serving cell". (see note)
2	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell C is preferred by the UE.
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-4
5	->		ATTACH COMPLETE
5a				The SS releases the RRC connection
6	SS			Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Suitable neighbour cell". Set the cell type of cell C to the "Suitable neighbour cell". (see note)
				Cell A is preferred by the UE.
7	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-4 Mobile identity = P-TMSI-1
7a				The SS starts integrity protection.
8	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘No Suitable Cells In Location Area’
				The following message are sent and shall be received on cell B.
9	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-4 Mobile identity = P-TMSI-1 The UE shall initiate a location area updating procedure between steps 8 and 12.
10	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-3
11	->		ROUTING AREA UPDATE COMPLETE
NOTE: The definitions for "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.4b.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, UE shall;

– initiate the routing area updating procedure.

At step9, when the UE enters a suitable cell in a different location area on the same PLMN, UE shall:

– perform the routing area updating procedure.

12.4.1.4c Routing area updating / rejected / PS services not allowed in this PLMN

12.4.1.4c.1 Definition

12.4.1.4c.2 Conformance requirement

If the network rejects a routing area updating procedure from the User Equipment with the cause ‘GPRS services not allowed in this PLMN’, the User Equipment shall:

– delete any RAI, P-TMSI, P-TMSI signature, and PS ciphering key sequence number stored.

– shall set the PS update status to GU3 ROAMING NOT ALLOWED.

– store the PLMN identity in the "forbidden PLMNs for GPRS service" list.

– not delete the equivalent PLMN list.

UE shall perform the following actions depending on the update type, UE operation mode and network operation mode.

1) UE is in UE operation mode C

UE shall perform a PLMN selection instead of a cell selection.

2) UE is in UE operation mode A, update type = periodic updating and Network is in network operation mode I

UE shall set the timer T3212 to its initial value and restart it, if it is not already running.

3) UE is in UE operation mode A and Network is in network operation mode II.

UE shall be still IMSI attached for CS services in the network.

…

R99 to Rel-10:

The network may also send a list of "equivalent PLMNs" in the ATTACH ACCEPT message. Each entry of the list contains a PLMN code (MCC+MNC). The mobile station shall store the list, as provided by the network, and if the GPRS attach procedure is not for emergency bearer services, any PLMN code that is already in the "forbidden PLMN" list shall be removed from the "equivalent PLMNs" list before it is stored by the mobile station. In addition the mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list.

Rel-11:

The network may also send a list of "equivalent PLMNs" in the ATTACH ACCEPT message. Each entry of the list contains a PLMN code (MCC+MNC). The mobile station shall store the list, as provided by the network, and if the GPRS attach procedure is not for emergency bearer services, any PLMN code that is already in the "forbidden PLMN" list or in the list of "forbidden PLMNs for GPRS service" shall be removed from the "equivalent PLMNs" list before it is stored by the mobile station. In addition the mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list.

Reference

3GPP TS 24.008 clauses 4.7.5.1.4 #14 and 4.7.3.1.3.

12.4.1.4c.3 Test purpose

To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause ‘GPRS services not allowed in this PLMN’.

12.4.1.4c.4 Method of test

Proc 1: Test procedure 1

Initial condition

System Simulator:

Three cells, cell A in MCC1/MNC2/LAC1/RAC1 (RAI-8, Not HPLMN), cell B in MCC1/MNC2/LAC1/RAC2 (RAI-10, Not HPLMN), cell C in MCC2/MNC1/LAC1/RAC1 (RAI-2).
All three cells are 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) in all cells.

The PLMN contains Cell C is equivalent to the PLMN that contains Cell A.

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 P-TMSI-1, RAI-8.

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
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure: The SS rejects a routing area updating with the cause value ‘GPRS services not allowed in this PLMN’. The SS checks that the UE performs PLMN selection.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following messages are sent and shall be received on cell A.
1	UE			The UE is set in UE operation mode C (see ICS). If UE operation mode C not supported, goto step 20.
2	SS			The SS is set in network operation mode II. 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 "Non-Suitable cell". (see note)
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-8
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	No new mobile identity assigned. P-TMSI and P-TMSI signature not included. Attach result = ‘GPRS only attached’ Routing area identity = RAI-8 Equivalent PLMNs = MCC2,MNC1
5a				The SS releases the RRC connection
				The following messages are sent and shall be received on cell B.
6	SS			Set the cell type of cell A to the " Suitable neighbour cell ". Set the cell type of cell B to the "Serving cell". (see note)
7	UE			Cell B is preferred by the UE.
8	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old Routing area identity = RAI-8
8a	SS			The SS starts integrity protection.
9	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘GPRS services not allowed in this PLMN’
10	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 PAGING TYPE1 (used for NW-mode II). Paging order is for PS services.
11	UE			No response from the UE to the request. This is checked for 10 seconds.
12	SS			Set the cell type of cell B to the "Non-Suitable cell". Set the cell type of cell A to the "Serving cell". (see note)
12a				The following step 13 is only performed for UE operation mode C.
13	UE			The UE performs PLMN selection.
14	UE			No ATTACH REQUEST or LOCATION UPDATE REQUEST sent to the SS (SS waits 30 seconds).
15	SS			Set the cell type of cell A to the "Non-Suitable cell". Set the cell type of cell C to the "Serving cell". (see note)
16				The following step is only performed for UE operation mode A.
16a	UE		Registration on CS	See TS34.108 Parameter mobile identity is IMSI
17	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
17a	<-		AUTHENTICATION AND CIPHERING REQUEST
17b	->		AUTHENTICATION AND CIPHERING RESPONSE
17c	SS			The SS starts integrity protection.
18	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-2 Equivalent PLMNs = MCC1,MNC2
19	->		ATTACH COMPLETE
				A Rel-11 or higher Operation Mode A UE supporting S1 mode may optionally initiate the RAU procedure in Steps 19a-19c within 10s. RRC Connection is released if the inactivity period is more than 2s
19a	->		ROUTING AREA UPDATING REQUEST	P-TMSI-1 signature Routing area identity = RAI-2
19aa	SS			The SS shall start integrity protection if RRC Connection is re-established to perform Step 19a.
19b	<-		ROUTING AREA UPDATING ACCEPT	Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-2 Equivalent PLMNs = MCC1, MNC2
19c	->		ROUTING AREA UPDATING COMPLETE
20				The UE is set in UE operation mode A (see ICS) and the test is repeated from step 2 to step 19c.
NOTE: The definitions for "Non-Suitable cell", "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions " subclauses.

Specific message contents

None.

Proc 2: Test procedure2

Initial condition

System Simulator:

One cells, cell A in MCC1/MNC2/LAC1/RAC1 (RAI-8, Not HPLMN) operating in network operation mode I.

T3212 is set to 6 minutes.

User Equipment:

The UE has a valid P-TMSI-1 and RAI-8.

The UE is in UE operation mode A or C.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode A Yes/No
UE operation mode C Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The UE initiates a PS attach procedure with identity P-TMSI. The SS reallocates the P-TMSI and returns ATTACH ACCEPT message with a new P-TMSI and timer T3312. The UE acknowledge the new P-TMSI by sending ATTACH COMPLETE message. A routing area updating procedure is performed at T3312 timeout. The SS rejects a routing area updating with the cause value ‘GPRS services not allowed in this PLMN’. The UE sets the timer T3212 to its initial value and restart it, if it is not already running.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set in UE operation mode A or C (see ICS).
2	UE			The UE is powered up or switched on and initiates an attach (see ICS).
3	->		ATTACH REQUEST	Attach type = ‘Combined GPRS/IMSI attach’ (UE operation mode A) or ‘GPRS attach’ (UE operation mode C) Mobile identity = P-TMSI-1 Old Routing area identity = RAI-8
3a	<-		AUTHENTICATION AND CIPHERING REQUEST
3b	->		AUTHENTICATION AND CIPHERING RESPONSE
3c	SS			The SS starts integrity protection.
4	<-		ATTACH ACCEPT	Attach result = ‘Combined GPRS/IMSI attached’ (UE operation mode A) or ‘GPRS attach’ (UE operation mode C) Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-8 Periodic RA Update Timer (T3312) = 6 minutes
5	->		ATTACH COMPLETE
5a	SS			The SS releases the RRC connection.
5b	SS			The SS verifies that the time between the attach and the periodic RA updating is T3312
6	->		ROUTING AREA UPDATE REQUEST	Update type = ‘Periodic updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-8
6a	<-		AUTHENTICATION AND CIPHERING REQUEST
6b	->		AUTHENTICATION AND CIPHERING RESPONSE
6c	SS			The SS starts integrity protection.
7	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘GPRS services not allowed in this PLMN’
8	UE		Registration on CS	This step is only performed for UE in operation mode A. See TS 34.108 Location Update Procedure is initiated from the UE when T3212 is expired.
9	->		void
10	<-		void
NOTE: The definitions for "Non-Suitable cell", "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions " subclauses.

Specific message contents

None.

12.4.1.4c.5 Test requirements

Test requirement for Test procedure1

At step4, 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 step8, UE shall;

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

At step11, after the routing area updating procedure is rejected with GMM cause = ‘GPRS services not allowed in this PLMN’, UE shall;

– not respond to the paging message for PS domain.

At step13, UE shall,

– initiate PLMN selection.

At step14, UE shall,

– not start registration procedure on CS or PS domain.

At step17, UE shall;

– initiate the PS attach procedure.

Test requirement for Test procedure 2

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 step6, UE shall;

– initiate the routing area updating procedure with the information elements specified in the above Expected Sequence.

At step7, after the routing area updating procedure is rejected with GMM cause = ‘GPRS services not allowed in this PLMN’, UE shall;

– set the timer T3212 to its initial value and restart it.

At step8, UE shall,

– initiate the periodic location area updating procedure when the timer T3212 is expired.

12.4.1.4d Routing area updating / rejected / Roaming not allowed in this location area

12.4.1.4d.1 Definition

12.4.1.4d.2 Conformance requirement

1) If the network rejects a routing area updating procedure from the User Equipment with the cause ‘roaming not allowed in this location area’ the User Equipment:

1.1 shall not perform PS attach when in the same location area.

1.2 shall store the LA in the ‘forbidden location areas for roaming’.

1.3 shall perform a routing area updating when entering into a new location area if the LAI or the PLMN identity is not contained in any of the lists "forbidden LAs for roaming", "forbidden LAs for regional provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs" and the current status is different from "IDLE NO IMSI".

2) The User Equipment shall erase the list of ‘Forbidden location areas for roaming’ when switched off or when the USIM is removed.

References

3GPP TS 24.008 clause 4.7.5.1.4.

3GPP TS 23.122 clause 4.5.2.

3GPP TS 24.008 clause 4.4.1.

12.4.1.4d.3 Test purpose

Test purpose 1

To test that on receipt of a rejection using the ‘Roaming not allowed in this location area’ cause code, the UE ceases trying a routing area updating procedure on that location area. Successful routing area updating procedure is possible in other location areas.

Test purpose 2

To test that if the UE is switched off or the USIM is removed the list of ‘forbidden location areas for roaming’ is cleared.

12.4.1.4d.4 Method of test

Proc 1: Test procedure 1

Initial condition

System Simulator:

Two cells, cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2), cell B in MCC2/MNC1/LAC2/RAC1 (RAI-6).
Both cells are operating in network operation mode II.

NB: i) Cell B will be mapped to Cell 4 as found in TS 34.108 clause 6.1.4.1.

User Equipment:

The UE has a valid IMSI.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode A Yes/No
UE operation mode C Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No
UE supports CS call establishment Yes/No

Test procedure

The SS rejects a routing area updating with the cause value ‘Roaming not allowed in this location area’. A new attempt for a PS attach is not possible. Successful PS attach procedure is performed in another location area. The UE is moved back to the 1^st location area. A routing area updating shall not be performed, as the LA is on the forbidden list.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The UE is set in UE operation mode A or C (see ICS). 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	UE			The UE is powered up or switched on and initiates an attach (see ICS).
3	UE		Registration on CS	This step is only performed for UE in operation mode A. See TS34.108 SS allocates Mobile identity = TMSI-1.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach Mobile identity =IMSI
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-2
6	->		ATTACH COMPLETE
6a				The SS releases the RRC connection
				The following messages are sent and shall be received on cell B.
7	SS			Set the cell type of cell A to the " Non-suitable cell ". Set the cell type of cell B to the "Serving cell". (see note)
8	UE			Cell B is preferred by the UE.
8a	UE		Registration on CS	This step is only performed for UE in operation mode A. See TS 34.108 Location Update Procedure initiated from the UE.
9	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-2
9a	SS			The SS starts integrity protection.
10	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Roaming not allowed in this location area’
10a				The SS releases the RRC connection.
11	UE			The UE initiates an attach by MMI or by AT command.
12	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
13	<-		PAGING TYPE1	Mobile identity = P-TMSI-2 Paging order is for PS services.
14	UE			No response from the UE to the request. This is checked for 10 seconds.
15	<-		PAGING TYPE1	Steps 15 to 16 are only performed for UE in operation mode A. Mobile identity = TMSI-1 Paging order is for CS services. Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling"
16	UE			The UE shall not initiate an RRC connection. This is checked during 3 seconds.
				The following messages 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			Cell A is preferred by the UE.
19	UE		Registration on CS	This step is only performed for UE in operation mode A. See TS 34.108 Location Update Procedure initiated from the UE. SS allocates Mobile identity = TMSI-1.
20			Void
21	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Mobile identity = P-TMSI-2
21a	<-		AUTHENTICATION AND CIPHERING REQUEST
21b	->		AUTHENTICATION AND CIPHERING RESPONSE
21c	SS			The SS starts integrity protection.
22	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-2
23	->		ROUTING AREA UPDATE COMPLETE
24	<-		PAGING TYPE1	Steps 24 to 29 are only performed for UE in operation mode A. Mobile identity = TMSI-1 Paging order is for CS services. Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling"
25			Void
26			Void
27			Void
28	->		PAGING RESPONSE	Mobile identity = TMSI-1
29	SS			The SS releases the RRC connection.
30			Void
31	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 Paging order is for PS services.
32			Void
33			Void
34			Void
35	->		SERVICE REQUEST	service type = "paging response"
36	SS			The SS releases the RRC connection.
37			Void
				The following messages are sent and shall be received on cell B.
38	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
39	UE			No ROUTING AREA UPDATE REQUEST sent to SS (SS waits 30 seconds).
40	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 Paging order is for PS services.
41	UE			No response from the UE to the request. This is checked for 10 seconds.
NOTE: The definitions for “Non Suitable cell”, "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Proc 2: Test procedure 2

Initial condition

System Simulator:

Two cells, cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2), cell B in MCC2/MNC1/LAC2/RAC1 (RAI-6).
Both cells are operating in network operation mode II.

User Equipment:

The UE has a valid IMSI. UE is Idle Updated on cell A.

Related ICS/IXIT statements

Test procedure

The SS rejects a routing area updating with the cause value ‘Roaming not allowed in this location area’. The UE is switched off for 10 seconds and switched on again. The SS checks that a PS attach is possible on the cell on which the previous routing area updating had been rejected.

If USIM removal is possible without switching off:
The SS rejects a routing area updating with the cause value ‘Roaming not allowed in this location area’. The USIM is removed and inserted in the UE. The SS checks that a PS attach procedure and routing area updating procedure is possible on the cell on which the routing area updating had previously been rejected.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The UE is set in UE operation mode A or C (see ICS). 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	UE			The UE is powered up or switched on and initiates an attach (see ICS.
3	UE		Registration on CS	This step is only performed for UE in operation mode A. See TS34.108 SS allocates Mobile identity = TMSI-1.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach Mobile identity =IMSI
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-2
6	->		ATTACH COMPLETE
6a				The SS releases the RRC connection
				The following messages are sent and shall be received on cell B.
7	SS			Set the cell type of cell A to the "Non-suitable cell". Set the cell type of cell B to the "Serving cell". (see note)
8	UE			Cell B is preferred by the UE.
8a	UE		Registration on CS	This step is only performed for UE in operation mode A. See TS 34.108 Location Update Procedure initiated from the UE. SS allocates Mobile identity = TMSI-2
9	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-2
9a	SS			The SS starts integrity protection.
10	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Roaming not allowed in this location area’
10a				The SS releases the RRC connection.
11	UE			The UE initiates an attach by MMI or by AT command.
12	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
13	<-		PAGING TYPE1	Mobile identity = P-TMSI-2 Paging order is for PS services.
14	UE			No response from the UE to the request. This is checked for 10 seconds.
15	<-		PAGING TYPE1	Steps 15 to 16 are only performed for UE in operation mode A. Mobile identity = TMSI-2 Paging order is for CS services. Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling"
16	UE			The UE shall not initiate an RRC connection. This is checked during 3 seconds.
17	UE			If possible (see ICS) USIM removal is performed. Otherwise if possible (see ICS) switch off is performed. Otherwise the power is removed.
18	UE			The UE gets the USIM replaced, is powered up or switched on.
19	UE		Registration on CS	This step is only performed for UE in operation mode A. See TS 34.108 Location Update Procedure initiated from the UE. SS allocates Mobile identity = TMSI-1
20	UE			The UE initiates an attach automatically (see ICS) by MMI or AT command.
21	->		ATTACH REQUEST	Attach type = ‘GPRS attach ‘ Mobile identity =P-TMSI-2
22a	<-		AUTHENTICATION AND CIPHERING REQUEST
22b	->		AUTHENTICATION AND CIPHERING RESPONSE
22c	SS			The SS starts integrity protection.
22	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-6
23	->		ATTACH COMPLETE
24	<-		PAGING TYPE1	Steps 24 to 29 are only performed for UE in operation mode A. Mobile identity = TMSI-1 Paging order is for CS services. Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling"
25			Void
26			Void
27			Void
28	->		PAGING RESPONSE	Mobile identity = TMSI-1
29	SS			The SS releases the RRC connection.
30			Void
31	<-		PAGING TYPE1	Mobile identity = P-TMSI-1
32			Void
33			Void
34			Void
35	->		SERVICE REQUEST	service type = "paging response"
36	SS			The SS releases the RRC connection.
37			Void
NOTE: The definitions for “Non-Suitable cell”, "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.4d.5 Test requirements

Test requirements for Test procedure 1

At step4, when the UE is powered up or switched on, UE shall:

– initiate the PS attach procedure with information elements specified in the above Expected Sequence.

At step9, when the RF level of the attached cell is lower than the RF level of the new cell, UE shall:

– initiate the routing area update procedure with the information elements specified above Expected Sequence

At step12, when the SS rejects the routing area update procedure with GMM cause = ‘Roaming not allowed in this location area’, UE shall:

not initiate a PS attach procedure.

At step14, when the UE receives the paging message for PS domain, UE shall;

– not respond to the paging message for PS domain.

At step16, when the UE receives the paging message for CS domain, UE shall:

not respond to the paging message for CS domain.

At step21, UE shall:

initiate the routing area update procedure.

At step28, when the UE receives the paging message for CS domain, UE shall;

– respond to the paging message for CS domain by sending the PAGING RESPONSE message.

At step35, when the UE receives the paging message for PS domain, UE shall:

respond to the paging message for PS domain by sending the SERVICE REQUEST message.

At step41, when the UE receives the paging message for PS domain, UE shall;

– not respond to the paging message for PS domain.

Test requirements for Test procedure 2

At step4, when the UE is powered up or switched on, UE shall:

– initiate the PS attach procedure with information elements specified in the above Expected Sequence.

At step9, UE shall:

initiate the routing area update procedure with the information elements specified above Expected Sequence.

At step14, when the UE receives the paging message for PS domain, UE shall;

– not respond to the paging message for PS domain.

At step16, when the UE receives the paging message for CS domain, UE shall:

not respond to the paging message for CS domain.

At step21, UE shall:

– initiate the PS attach procedure.

At step28, when the UE receives the paging message for CS domain, UE shall;

– respond to the paging message for CS domain by sending the PAGING RESPONSE message.

At step35, when the UE receives the paging message for PS domain, UE shall:

– respond to the paging message for PS domain by sending the SERVICE REQUEST message.

12.4.1.4e Routing area updating / rejected / Not authorized for this CSG

12.4.1.4e.1 Definition

12.4.1.4e.2 Conformance requirement

(1) If the network rejects a routing area updating procedure from the User Equipment with the cause ‘ Not authorized for this CSG ‘ the User Equipment shall:

1.1 delete the CSG ID of the cell, where the UE has sent the TRACKING AREA UPDATE REQUEST message, from the allowed CSG ID list stored in the UE.

1.2 not delete the list of "equivalent PLMNs".

1.3 search for a suitable cell in the same PLMN.

Reference

3GPP TS 24.008 clause 4.7.5

12.4.1.4e.3 Test purpose

To verify UE to remove the CSG ID from the Allowed CSG list and search for a suitable cell in the same PLMN when #25 is received.

12.4.1.4e.4 Method of test

Initial conditions:

System Simulator:

Four cells, cell A and cell D in MCC1/MNC1/LAC1/RAC1 (RAI-1)/CSG1, cell B in MCC1/MNC1/LAC2/RAC1 (RAI-3)/CSG2, cell C in MCC1/MNC1/LAC1/RAC2 (RAI-4),

Cell A, Cell B, Cell C and Cell D belong to PLMN1.

All four cells are operating in network operation mode II(in case of UE operation mode A).

User Equipment:

The UE has a valid P-TMSI-1, RAI-1.

UE Allowed CSG List contains CSG1 and CSG2.

UE is registered on PLMN1.

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

The UE is previously registered on PLMN1, before switched off.

Related ICS/IXIT statements

Support of PS service Yes/No

UE operation mode C Yes/No

UE operation mode A Yes/No(only if mode C not supported)

Switch off on button Yes/No

Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The SS rejects a routing area updating with the cause value ‘ Not authorized for this CSG ‘. The SS checks that the UE shall perform Routing Area Update procedure when the UE enters a suitable cell in a different location area on the same PLMN.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The following message are sent and shall be received on cell C.
1	SS			Set the cell type of cell A to the "Non-Suitable cell". Set the cell type of cell B to the "Non-Suitable cell". Set the cell type of cell C to the "Serving cell". Set the cell type of cell D to the "non-suitable ‘Off’ cell". (see note)
2	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell C is preferred by the UE.
2a	UE		Registration on CS	See TS34.108 SS allocates Mobile identity = TMSI-1.
3	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
4	<-		AUTHENTICATION AND CIPHERING REQUEST
5	->		AUTHENTICATION AND CIPHERING RESPONSE
6	SS			The SS starts integrity protection.
7	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-4
8	->		ATTACH COMPLETE
9	SS			Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Suitable neighbour cell". Set the cell type of cell C to the " Non-Suitable cell". (see note)
				Cell A is preferred by the UE.
10	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-4 Mobile identity = P-TMSI-1
10a				The SS starts Integrity Protection
11	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘ Not authorized for this CSG ‘
				The following message are sent and shall be received on cell B.
11a	SS			Set the cell type of cell B to the "Serving cell". (see note) Set the cell type of cell A to the "Suitable neighbour cell".
11b	UE		Registration on CS	See TS 34.108 Location Update Procedure initiated from the UE.
12	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-4 Mobile identity = P-TMSI-1
13	<-		AUTHENTICATION AND CIPHERING REQUEST
14	->		AUTHENTICATION AND CIPHERING RESPONSE
15	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-3
16	->		ROUTING AREA UPDATE COMPLETE
17				SS releases rrc connection
17a				The UE is switched OFF, and performs a DETACH on Cell B
18				Set the cell type of cell A to the "non-suitable ‘Off’ cell". Set the cell type of cell B to the " non-suitable neighbour cell". Set the cell type of cell D to the "Serving cell".
18a				The UE is Switched ON
19				SS checks that the UE does not initiate a RRC Connection on Cell D in 30sec
NOTE: The definitions for "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions " subclauses.

12.4.1.4e.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 step10, UE shall;

initiate the routing area updating procedure.

At step11, UE shall;

delete the CSG1 in the Allowed CSG List;
UE Allowed CSG List shall contain only CSG2.

At step12, when the UE camps on a suitable cell in a different location area on the same PLMN, UE shall:

– perform the routing area updating procedure.

At step19, the UE does not try to camp on to CSG 1 (Cell D).

12.4.1.4f Routing area updating / rejected / Congestion

12.4.1.4f.1 Definition

12.4.1.4f.2 Conformance requirement

If the routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT message to the MS. An MS that receives a ROUTING AREA UPDATE REJECT message, stops timer T3330, and for all causes except #12, #14, #15, #22 and #25 deletes the list of "equivalent PLMNs". If a ROUTING AREA UPDATE REJECT message is received, the MS shall stop any ongoing transmission of user data.

If the routing area update request is rejected due to general NAS level mobility management congestion control, the network shall set the GMM cause value to #22 "congestion" and assign a back-off timer T3346.

The MS shall then take different actions depending on the received reject cause value:

…

#22 (Congestion);

If the T3346 value IE is present in the ROUTING AREA UPDATE REJECT message and the value indicates that this timer is neither zero nor deactivated, the MS shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the MS for this case is specified in subclause 4.7.5.1.5.

The MS shall abort the routing area updating procedure, reset the routing area updating attempt counter and set the GPRS update status to GU2 NOT UPDATED. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE.

The MS shall stop timer T3346 if it is running.

If the ROUTING AREA UPDATE REJECT message is integrity protected, the MS shall start timer T3346 with the value provided in the T3346 value IE.

If the ROUTING AREA UPDATE REJECT message is not integrity protected, the MS shall start timer T3346 with a random value from the default range specified in table 11.3a.

The MS stays in the current serving cell and applies the normal cell reselection process. The routing area updating procedure is started, if still necessary, when timer T3346 expires or is stopped.

If the update type is "periodic updating", a GPRS MS operating in MS operation mode A or B in network operation mode I is still IMSI attached for CS services in the network.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, and tracking area updating attempt counter as specified in 3GPP TS 24.301 [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value.

Reference

3GPP TS 24.008 clause 4.7.5.1.4

12.4.1.4f.3 Test purpose

To test the behaviour of the UE if the network rejects the routing area updating procedure of the UE with the cause ‘Congestion’ and includes the network back-off timer T3346.

12.4.1.4f.4 Method of test

Initial condition

System Simulator:

User Equipment:

The MS has a valid P-TMSI-1 and RAI-1. MS is Idle Updated on cell A.

Related ICS/IXIT statements

Test procedure

The SS rejects a normal routing area updating with the cause value ‘Congestion’ and the back-off timer T3346 included. When timer T3346 expires the UE performs a successful routing area updating procedure.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following messages are sent and shall be received on cell A.
1	SS			In case of UE operation mode A the SS is set in network operation mode II. 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	UE			The UE is set in UE operation mode C (see ICS).
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4			Void
5	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity =P-TMSI-1 Old Routing area identity = RAI-1
6	<-		AUTHENTICATION AND CIPHERING REQUEST
7	->		AUTHENTICATION AND CIPHERING RESPONSE
8	SS			The SS starts integrity protection.
9	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
10	->		ATTACH COMPLETE
				The following messages are sent and shall be received on cell B.
11	SS			Set the cell type of cell A to the " Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
12	UE			Cell B is preferred by the UE.
13	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
13A	SS			The SS starts integrity protection.
14	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Congestion’ T3346 value = 5 minutes
15	SS			The SS verifies that the MS does not initiate the routing area update procedure before timer T3346 has expired
16	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
17	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Mobile identity = P-TMSI-1 P-TMSI-1 signature Routing area identity = RAI-4
18	->		ROUTING AREA UPDATE COMPLETE
NOTE: The definitions for "Non-Suitable cell", Suitable neighbour cell and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.4f.5 Test requirements

At step15, when the UE receives the routing are update reject with the T3346 timer, UE shall:

– not initiate any routing updating procedure until the timer T3346 has expired.

At step 16, UE shall;

– after expiry of timer T3346, initiate the routing area updating procedure with the information elements specified in the above Expected Sequence

12.4.1.5 Routing area updating / abnormal cases / attempt counter check / miscellaneous reject causes

12.4.1.5.1 Definition

12.4.1.5.2 Conformance requirement

When a routing area updating procedure is rejected with the attempt counter less than five, the UE shall repeat the routing area updating procedure after T3311 timeout.

When a T3311 timeout has occurred during a routing area updating procedure with the attempt counter five, the UE shall start timer T3302.

When the T3302 expire, a new routing area updating procedure shall be initiated.

Reference

3GPP TS 24.008 clause 4.7.5.1.

12.4.1.5.3 Test purpose

To test the behaviour of the UE with respect to the attempt counter.

12.4.1.5.4 Method of test

Initial condition

System Simulator:

Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4). The ATT-flag shall indicate that the MS should use IMSI attach/detach procedures.
Both cells are operating in network operation mode II (in case of UE operation mode A).

User Equipment:

The UE has a valid P-TMSI-1 and RAI-1.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode C Yes/No
UE operation mode A Yes/No (only if mode C not supported)
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The UE initiates a routing area updating procedure (attempt counter zero).

The SS rejects the routing area updating procedure with a GMM cause ‘congestion’ code.

The UE initiates a new routing area updating procedure (attempt counter one) after T3311 expires.

The SS rejects the routing area updating procedure with a GMM cause ‘congestion’ code.

The UE initiates a new routing area updating procedure (attempt counter two) after T3311 expires.

The SS rejects the routing area updating procedure with a GMM cause ‘congestion’ code.

The UE initiates a new routing area updating procedure (attempt counter three) after T3311 expires.

The SS rejects the routing area updating procedure with a GMM cause ‘congestion’ code.

The UE initiates a new routing area updating procedure (attempt counter four) after T3311 expires.

The SS rejects the routing area updating procedure with a GMM cause ‘congestion’ code.

The UE initiates a new routing area updating procedure with attempt counter five (after T3311 expires).

The SS rejects the routing area updating procedure with a GMM cause ‘congestion’ code.

The UE shall not perform a new successful routing area updating procedure after T3311 seconds.

The UE initiates a routing area updating procedure with attempt counter zero after T3302 expires with the stored P-TMSI, P-TMSI signature, PS CKSN and RAI.

T3302; set to 12 minutes.

T3311; set to 15 seconds.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The following messages are sent and shall be received on cell A.
1	UE			The UE is set in UE operation mode C (see ICS).
2	SS			The SS is set in network operation mode II. 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)
2a			Void
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
3a	UE		Registration on CS	See TS 34.108 This step is applied only for UE in UE operation mode A. Parameter mobile identity is TMSI.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	No new mobile identity assigned. P-TMSI not included. Attach result = ‘GPRS only attached’ P-TMSI-2 signature Routing area identity = RAI-1
				The following messages are sent and shall be received on cell B.
6	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
7	SS			Cell B is preferred by the UE.
8	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
9	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Congestion’
10	SS			The SS verifies that the time between the routing area updating requests is 15 seconds
11	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
12	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Congestion’
13	SS			The SS verifies that the time between the routing area updating requests is 15 seconds
14	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
15	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Congestion’
16	SS			The SS verifies that the time between the routing area updating requests is 15 seconds
17	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
18	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Congestion’
19	SS			The SS verifies that the time between the routing area updating requests is 15 seconds
20	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
21	<-		ROUTING AREA UPDATE REJECT	GMM cause = ‘Congestion’
22	SS			The SS verifies that the UE does not attempt to attach for 12 minutes .
23	SS			The SS shall release the PS signalling connection.
23a			Void
24	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
24a				The SS starts integrity protection.
25	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-3 signature Routing area identity = RAI-4
26	->		ROUTING AREA UPDATE COMPLETE
NOTE: The definitions for "Non-Suitable cell", "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.5.5 Test requirements

At step4, 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 step8, UE shall:

– perform the routing area updating procedure.

UE shall perform the following actions depending on the conditions described below.

Case 1) At step11, 14, 17 and 20, a routing area updating procedure is rejected from SS with the attempt counter less than five,

UE shall:

– repeat the routing area updating procedure after T3311 timeout

Case2) At step22 a routing area updating procedure is rejected from SS with the attempt counter five

At step22, UE shall:

– not initiate a routing area updating procedure.

Case3) At step24, the T3302 expires

UE shall:

– initiate the new routing area updating procedure

12.4.1.6 Routing area updating / abnormal cases / change of cell into new routing area

12.4.1.6.1 Definition

12.4.1.6.2 Conformance requirement

When a change of cell into a new routing area is performed before the routing area updating procedure is finished, the UE shall abort the routing area updating procedure and re-initiate it in the new routing area.

Reference

3GPP TS 24.008 clause 4.7.5.1.

12.4.1.6.3 Test purpose

To test the behaviour of the UE in case of procedure collision.

12.4.1.6.4 Method of test

Initial condition

System Simulator:

Three cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4) and cell C In MCC1/MNC1/LAC1/RAC3 (RAI-5).
All cells are operating in network operation mode II (in case of UE operation mode A).
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) in all cells.

User Equipment:

The UE has a valid P-TMSI-1 and RAI-1.

The UE has been registered in the CS domain.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode C Yes/No
UE operation mode A Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The UE initiates a routing area updating procedure. The ROUTING AREA UPDATE ACCEPT message is delayed from the SS. The UE performs a cell update into a new routing area. The UE shall re-initiate a routing area updating procedure in the new routing area.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The following messages are sent and shall be received on cell A.
1	UE			The UE is set in UE operation mode C (see ICS). If UE operation mode C not supported, goto step 18.
2	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 "Non-Suitable cell". (see note)
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
6	->		ATTACH COMPLETE
				The following messages are sent and shall be received on cell B.
7	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
8	SS			Cell B is preferred by the UE.
9	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
10	SS			No response to the ROUTING AREA UPDATE REQUEST message is given by the SS
				The following messages are sent and shall be received on cell C.
11	SS			Set the cell type of cell B to the "Suitable neighbour cell". Set the cell type of cell C to the "Serving cell". (see note)
12	SS			Cell C is preferred by the UE.
13	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-2 signature Old Routing area identity = RAI-1
14	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-3 signature Routing area identity = RAI-5
15	->		ROUTING AREA UPDATE COMPLETE
16	UE			The UE is switched off or power is removed (see ICS).
17	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
17a	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.
18	SS			The SS is set in network operation mode II.
19	UE			The UE is set in UE operation mode A (see ICS). Set the cell type of cell C to the "Non-Suitable cell". The test is repeated from step 2 to step 17.
NOTE: The definitions for "Non-Suitable cell", "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions " subclauses.

Specific message contents

None.

12.4.1.6.5 Test requirements

At step4, 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 step9, UE shall:

– initiate the routing area update procedure.

At step13, when change of cell into a new routing area is performed before the routing area updating procedure is finished, UE shall:

– abort the routing area updating procedure.

– re-initiate new routing area updating procedure in the new routing area.

12.4.1.7 Void

12.4.1.8 Routing area updating / abnormal cases / P-TMSI reallocation procedure collision

12.4.1.8.1 Definition

12.4.1.8.2 Conformance requirement

When a P-TMSI reallocation COMMAND message is received by the UE while waiting for a ROUTING AREA UPDATE ACCEPT message, the UE shall ignore the P-TMSI reallocation procedure and continue with the routing area updating procedure.

Reference

3GPP TS 24.008 clause 4.7.5.1.

12.4.1.8.3 Test purpose

To test the behaviour of the UE in case of procedure collision.

12.4.1.8.4 Method of test

Initial condition

System Simulator:

Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) and cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4).
Both cells are operating in network operation mode II (in case of UE operation mode A).
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) in both cells.

User Equipment:

The UE has a valid IMSI.

The UE has been registered in the CS domain.

Related ICS/IXIT statements

Test procedure

The UE initiates a routing area updating procedure. The SS does not answer the routing area updating procedure, but initiates a P-TMSI reallocation procedure. The UE shall ignore the P-TMSI reallocation procedure and continue with the routing area updating procedure.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The following messages are sent and shall be received on cell A.
1	UE			The UE is set in UE operation mode C (see ICS).
2	SS			The SS is set in network operation mode II. 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)
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4	->		ATTACH REQUEST	Attach result = ‘GPRS only attached’ Mobile identity = IMSI
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts integrity protection.
5	<-		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
6	->		ATTACH COMPLETE
				The following messages are sent and shall be received on cell B.
7	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
8	SS			Cell B is preferred by the UE.
9	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Old Routing area identity = RAI-1
10	<-		P-TMSI REALLOCATION COMMAND	Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-1
11	UE			The UE ignores the P-TMSI reallocation command.
12	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-4
13	->		ROUTING AREA UPDATE COMPLETE
NOTE: The definitions for "Non-Suitable cell", "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.8.5 Test requirements

At step4, 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 step9, UE shall:

– initiate the routing area updating procedure.

At step11, when a P-TMSI REALLOCATION COMMAND message is received from SS while waiting for a ROUTING AREA UPDATE ACCEPT message, UE shall:

– ignore the P-TMSI reallocation procedure.

– continue with the routing area updating procedure.

12.4.1.9 Routing area updating / EAB active

12.4.1.9.1 Definition

Test to verify that the UE does not perform Routing area updating if the network broadcast EAB and EAB is enabled in the UE.

12.4.1.9.2 Conformance requirement

– For generic location updating, GPRS attach and routing area updating procedures the mobile station shall evaluate the control information for:

– common access control (as specified in 3GPP TS 44.018 [84], 3GPP TS 44.060 [76], and 3GPP TS 25.331 [23c]);

– domain specific access control (as specified in 3GPP TS 44.018 [84] and 3GPP TS 25.331 [23c]);

– specific control information for location registration (as specified in 3GPP TS 25.331 [23c]; see "Paging Permission with Access Control"); and

– EAB as specified for A/Gb mode in 3GPP TS 44.018 [84], and for Iu mode in 3GPP TS 25.331 [23c].

References

TS 24.008, 4.1.1.5

12.4.1.9.3 Test purpose

To verify that the UE does not perform Routing area updating if the network broadcast EAB and EAB is enabled in the UE

12.4.1.9.4 Method of test

Initial conditions:

– System Simulator:

– Two cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4),

– All 2 cells are 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 to prevent repeated CS domain registration and/or IMSI Detach by UEs in operation mode A) in all cells.

– Sintrasearch and Sintersearch values for cells A and B are 20 dB.

– User Equipment:

– The UE has a valid IMSI.

– The UE has been registered in the CS domain.

– An access class x (0-9) is arbitrarily chosen. The USIM is programmed with this access class x.

– The UE is equipped with a USIM containing values shown in Table 12.4.1.9–1.

Table 12.4.1.9-1: USIM Configuration

USIM field	Value
EF_UST	Service 96 is supported
EF_NASCONFIG	“ExtendedAccessBarring is set to 1 which indicate the extended access barring is applied for the UE” as defined in TS 24.368, clause 5.6
EF_NASCONFIG	“NAS_SignallingPriority is set to “NAS signalling low priority” as defined in TS 24.368, clause 5.3

Related ICS/IXIT statement(s)

– Support of PS service Yes/No

– UE operation mode A Yes/No

– UE operation mode C Yes/No

– Switch off on button Yes/No

– Automatic PS attach procedure at switch on or power on Yes/No

Test Procedure

A combined PS attach procedure is performed on Cell A.

The SS indicates access class x barred in EAB information.

Made the UE reselect to Cell B.

UE will not initiate a Routing area updating procedure.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
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	UE			The UE is set in UE operation mode A (see ICS).
3	UE			The UE is powered up or switched on and initiates an attach (see ICS).
4	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
5	->		ATTACH REQUEST	Attach type = ‘Combined GPRS/IMSI attach’ Mobile identity =IMSI TMSI status = no valid TMSI available
6	<-		AUTHENTICATION AND CIPHERING REQUEST
7	->		AUTHENTICATION AND CIPHERING RESPONSE
8	SS			The SS starts integrity protection.
9	<-		ATTACH ACCEPT	Attach result = ‘Combined GPRS/IMSI attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
10	->		ATTACH COMPLETE
11	SS			The SS releases the RRC connection.
12	SS			Set the cell type of cell A to the "Suitable neighbour cell". Set the cell type of cell B to the "Serving cell". (see note)
13	SS			SS transmits SYSTEM INFORMATION BLOCK TYPE 21 on cell B. SIB_REP=5.12s and access class x is present in IE “common EAB information”.
14	UE			The UE shall not initiate a Routing area updating procedure as access class x is barred. (SS waits 3 minutes).
15	SS			SS updates system information and stops transmitting SYSTEM INFORMATION BLOCK TYPE 21.
16	UE			The UE shall transmit a RRC CONNECTION REQUEST message on cell B to initiate a Routing area updating procedure. And the RRC Connection is established
17	->		ROUTING AREA UPDATE REQUEST
18	SS			The SS starts integrity protection.
19	<-		ROUTING AREA UPDATE ACCEPT
20	->		ROUTING AREA UPDATE COMPLETE
21	SS			The SS releases the RRC connection.
NOTE: The definitions for "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.4.1.9.5 Test requirement

At step 14, The UE shall not initiate a Routing area updating procedure as access class x is barred in EAB information.

At step 16, The UE shall transmit a RRC CONNECTION REQUEST message on cell B to initiate a Routing area updating procedure.