12.2.1 Normal PS attach

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

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

The normal PS attach procedure is a GMM procedure used by PS UEs of UE operation mode A or C to IMSI attach for PS services only.

12.2.1.1 PS attach / accepted

12.2.1.1.1 Definition

12.2.1.1.2 Conformance requirement

1) If the network accepts the PS attach procedure (signalled by an IMSI) and allocates a P-TMSI, the UE shall acknowledge the P-TMSI and continue communication with the P-TMSI.

2) If the network accepts the PS attach procedure (signalled by P-TMSI) and reallocates a new P-TMSI, the UE shall acknowledge the new P-TMSI and continue communication with the new P-TMSI.

3) If the network accepts the PS attach procedure (signalled by a P-TMSI) from the UE without reallocation of the old P-TMSI, the UE shall continue communication with the old P-TMSI.

Reference

3GPP TS 24.008 clause 4.7.3.1

12.2.1.1.3 Test purpose

To test the behaviour of the UE if the network accepts the PS attach procedure.

The following cases are identified:

1) P-TMSI / P-TMSI signature is allocated;

2) P-TMSI / P-TMSI signature is reallocated;

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

12.2.1.1.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode II.

The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE to prevent repeated CS domain registration and/or IMSI Detach by UEs in operation mode A).

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 an ATTACH REQUEST message with identity IMSI. The SS allocates a P-TMSI and returns ATTACH ACCEPT message with a P-TMSI. The UE acknowledge the P-TMSI by sending ATTACH COMPLETE message. Further communication UE – SS is performed by the new P-TMSI.

2) The UE sends an ATTACH REQUEST message with identity P-TMSI. The SS reallocates a new P-TMSI and returns ATTACH ACCEPT message with the new P-TMSI. The UE acknowledge the P-TMSI by sending ATTACH 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.

3) The UE sends an ATTACH REQUEST message with identity P-TMSI. The SS accepts the P-TMSI and returns ATTACH ACCEPT message without any P-TMSI. Further communication UE – SS is performed by the old P-TMSI.

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, goto step 26.
2	UE			The UE is powered up or switched on and initiates an attach (see ICS).
2a	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
3	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
3a	<-		AUTHENTICATION AND CIPHERING REQUEST
3b	->		AUTHENTICATION AND CIPHERING RESPONSE
3c	SS			The SS starts integrity protection.
4	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
5	->		ATTACH COMPLETE
5a	SS			The SS releases the RRC connection.
6	<-		PAGING TYPE1	Mobile identity = P-TMSI-2 Paging order is for PS services. Paging cause: Terminating interactive call
6a	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".
7	->		SERVICE REQUEST	Service type = "paging response"
7a	SS			The SS starts integrity protection and releases the RRC connection.
8	UE			The UE is switched off or power is removed (see ICS).
8a	SS			SS checks that the IE "Establishment cause" in any received RRC CONNECTION REQUEST message is set to "Detach" (message not sent if power is removed).
9	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
9a	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.
10	UE			The UE is powered up or switched on and initiates an attach (see ICS).
10a	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
11	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-2 Old Routing area identity = RAI-1
11a	<-		AUTHENTICATION AND CIPHERING REQUEST
11b	->		AUTHENTICATION AND CIPHERING RESPONSE
11c	SS			The SS starts integrity protection.
12	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI-1 signature Routing area identity = RAI-1
13	->		ATTACH COMPLETE
14			Void
14b			Void
14c	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 Paging order is for PS services.
14d	SS			SS verifies that the UE transmits an RRC CONNECTION REQUEST message. SS will reject this request. The IE "Establishment cause" is not checked.
15	<-		PAGING TYPE1	Mobile identity = P-TMSI-2 Paging order is for PS services.
16	UE			No response from the UE to the request. This is checked for 10 seconds.
17	UE			The UE is switched off or power is removed (see ICS).
17a	SS			SS checks that the IE "Establishment cause" in any received RRC CONNECTION REQUEST message is set to "Detach" (message not sent if power is removed).
18	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
18a	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	UE			The UE is powered up or switched on and initiates an attach (see ICS).
19a	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
20	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
20a	<-		AUTHENTICATION AND CIPHERING REQUEST
20b	->		AUTHENTICATION AND CIPHERING RESPONSE
20c	SS			The SS starts integrity protection.
21	<-		ATTACH ACCEPT	No new mobile identity assigned. P-TMSI and P-TMSI signature not included. Routing area identity = RAI-1 Attach result = ‘GPRS only attached’
22	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 Paging order is for PS services. Paging cause: Terminating interactive call
22a	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".
22b			Void
22c			Void
23	->		SERVICE REQUEST	Service type = "paging response"
23aa	SS			The SS starts integrity protection and releases the RRC connection.
23a			Void
23b			Void
24	UE			The UE is switched off or power is removed (see ICS).
24a	SS			SS checks that the IE "Establishment cause" in any received RRC CONNECTION REQUEST message is set to "Detach" (message not sent if power is removed).
25	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
25a	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.
26	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 25a.

Specific message contents

None.

12.2.1.1.5 Test requirements

At step 2a, 10a and 19a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Registration".

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

At step 8a, 17a and 24a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Detach".

At step3, 11 and 20, 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.

UE shall perform the following actions depending on the Mobile identity in the ATTACH REQUEST message and on the Mobile identity in the ATTACH ACCEPT message.

Case 1) The Mobile identity in the ATTACH REQUEST message is the IMSI and the Mobile identity in the ATTACH ACCEPT message is the P-TMSI.

At step5, UE shall:

– acknowledge the P-TMSI by sending the ATTACH COMPLETE message.

Case 2) The Mobile identity in the ATTACH REQUEST message is the P-TMSI and the Mobile identity in the ATTACH ACCEPT message is the new P-TMSI.

At step13, UE shall:

– acknowledge the new P-TMSI by sending the ATTACH COMPLETE message.

At step23, UE shall:

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

12.2.1.1a PS attach / accepted / Attach with IMSI

12.2.1.1a.1 Definition

12.2.1.1a.2 Conformance requirement

1) If the MS is configured for "AttachWithIMSI" and the selected PLMN is neither the registered PLMN nor in the list of equivalent PLMNs, the MS shall include the IMSI in the Mobile identity IE in the ATTACH REQUEST message

2) If the network accepts the PS attach procedure (signalled by an IMSI) and allocates a P-TMSI, the UE shall acknowledge the P-TMSI and continue communication with the P-TMSI.

Reference

3GPP TS 24.008 clause 4.7.3.1, 4.4.4.1

12.2.1.1a.3 Test purpose

To test the behaviour of the UE if the network accepts the PS attach procedure.

The following cases are identified:

1) To verify that the Attach with IMSI indicator can be set in the UE

2. To verify that the UE registers with IMSI (not Temporary ID) when registering with a new PLMN if the selected PLMN is neither the registered PLMN nor in the list of equivalent PLMNs

12.2.1.1a.4 Method of test

Initial condition

System Simulator:

Two cells; cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1) and cell B in MCC2/MNC1/LAC2/RAC1 (RAI-6).
Both cells are operating in network operation mode II (in case of UE operation mode A).

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

The PLMN that contains Cell B is not equivalent to the PLMN that contains Cell A.

User Equipment:

The UE has a valid IMSI.

The UE has been registered in the CS domain.

The US is configured for "AttachWithIMSI"

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	“Attach with IMSI is performed when moving to a non-equivalent PLMN” as defined in TS 24.368, clause 5.4.

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

2) The SS changes the serving cell to a cell that belongs to a new PLMN. When the UE selects the new cell it sends an ATTACH REQUEST message with identity IMSI. The SS allocates a P-TMSI and returns ATTACH ACCEPT message with a P-TMSI. The UE acknowledge the P-TMSI by sending ATTACH COMPLETE message. Further communication UE – SS is performed by the new P-TMSI.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1				Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Non-suitable cell ".
2	UE			The UE is set to attach to the PS services only (see ICS). If this is not supported by the UE, goto step 34.
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 = ‘GPRS attach’ Mobile identity = IMSI
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-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-1
10	–>		ATTACH COMPLETE
11	SS			The SS releases the RRC connection.
12	<–		PAGING TYPE1	Mobile identity = P-TMSI-1 Paging order is for PS services. Paging cause: Terminating interactive call
13	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".
14	–>		SERVICE REQUEST	Service type = "paging response"
15	SS			The SS starts integrity protection and releases the RRC connection.
16				void
17				void
18				void
19				void
20	SS			Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the "Non-suitable cell ".
21	UE			Cell B is preferred by the UE.
				The following messages are sent and shall be received on cell B.
22	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
23	–>		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
24	<–		AUTHENTICATION AND CIPHERING REQUEST
25	–>		AUTHENTICATION AND CIPHERING RESPONSE
26	SS			The SS starts integrity protection.
27	<–		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
28	–>		ATTACH COMPLETE
29	SS			The SS releases the RRC connection.
30	<–		PAGING TYPE1	Mobile identity = P-TMSI-2 Paging order is for PS services. Paging cause: Terminating interactive call
31	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".
32	–>		SERVICE REQUEST	Service type = "paging response"
33	SS			The SS starts integrity protection and releases the RRC connection.
34	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 33.
NOTE: The definitions for "Suitable neighbour cell", "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.2.1.1a.5 Test requirements

At step 4 and 22 the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Registration".

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

At step 5, when the UE is powered up or switched on and step 23, UE shall initiate the PS attach procedure with an ATTACH REQUEST message using the IMSI as Mobile Identity.

At step10 and 28 UE shall acknowledge the new P-TMSI by sending the ATTACH COMPLETE message.

12.2.1.1b PS attach / accepted / PSM

12.2.1.1b.1 Definition

12.2.1.1b.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".

…

If the MS supports PSM and requests the use of PSM, then the MS shall include the T3324 value IE with a requested timer value in the ATTACH 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.3.1.1

12.2.1.1b.3 Test purpose

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

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

12.2.1.1b.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode II.

User Equipment:

The UE is configured to use Power Saving Mode

The UE is configured to use a specific value of T3324

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 an ATTACH REQUEST message including the T3324 IE set to 2 minutes.

2) The SS returns an ATTACH ACCEPT message with the T3324 IE set to the same value as provided by the UE. The UE acknowledge by sending ATTACH COMPLETE message.

3) The SS sends a PAGING TYPE1 message to the UE before the T3324 timer expires.

4) The UE acknowledge the paging 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, goto step 17.
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	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
5	–>		ATTACH REQUEST	Attach type = ‘GPRS attach’ T3324 value = 2 minutes
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-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-1 T3324 value = 2 minutes
10	–>		ATTACH COMPLETE
11	SS			The SS releases the RRC connection.
12				The SS shall wait for 1 minute and then execute the following steps before timer T3324 expires
13	<–		PAGING TYPE1	Mobile identity = P-TMSI-1 Paging order is for PS services. Paging cause: Terminating interactive call
14	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".
15	–>		SERVICE REQUEST	Service type = "paging response"
16	SS			The SS starts integrity protection and releases the RRC connection.
17	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 16.

Specific message contents

None.

12.2.1.1b.5 Test requirements

At step 5 UE shall include the T3324 IE set to a configured value.

At step 9 the UE shall accept the PAGING TYPE1 message.

At step 15 UE shall respond to the paging message for PS domain by sending the SERVICE REQUEST message.

12.2.1.1c PS attach / accepted / DCN

12.2.1.1c.1 Definition

12.2.1.1c.2 Conformance requirement

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.

…

If the ATTACH 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 ATTACH 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 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.3.1 and 4.7.1.8a, TS 25.331, clause 8.1.8.2

12.2.1.1c.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.2.1.1c.4 Method of test

Initial condition

System Simulator:

One cell 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 an ATTACH REQUEST message. The Initial Direct Transfer message contains the IE "DCN Identity" set to the provisioned DCN value.

2) The SS returns an ATTACH ACCEPT 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 ATTACH COMPLETE message.

3) The SS sends a PAGING TYPE1 message to the UE.

4) The UE responds to the paging message by sending an Initial Direct Transfer RRC message containing a SERVICE REQUEST message. The Initial Direct Transfer message contains the IE "DCN Identity" set to the value received in the ATTACH 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, goto step 16.
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	SS			SS checks that the IE " DCN Identity " in the received RRC INITIAL DIRECT TRANSFER message is set to the DCN ID provisioned in the UE.
5	–>		ATTACH REQUEST
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-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-1 DCN-ID = “different DCN-ID from the default provisioned in the UE”
10	–>		ATTACH COMPLETE
11	SS			The SS releases the RRC connection.
12	<–		PAGING TYPE1	Mobile identity = P-TMSI-1 Paging order is for PS services. Paging cause: Terminating interactive call
13	SS			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 ATTACH ACCEPT message in step 9.
14	–>		SERVICE REQUEST	Service type = "paging response"
15	SS			The SS starts integrity protection and releases the RRC connection.
16	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 15.

Specific message contents

None.

12.2.1.1c.5 Test requirements

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

At step 9 the UE shall store the value of the DCN-ID IE carried by the ATTACH ACCEPT message.

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

12.2.1.2 PS attach / rejected / IMSI invalid / illegal UE

12.2.1.2.1 Definition

12.2.1.2.2 Conformance requirement

1) If the network rejects a PS attach procedure from the User Equipment with the cause ‘Illegal MS, 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 PS attach procedure from the User Equipment with the cause ‘Illegal MS the User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.

3) If the network rejects a PS attach procedure from the User Equipment with the cause ‘Illegal MS, the User Equipment shall delete the LAI.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.1.2.3 Test purpose

To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause ‘illegal MS.

12.2.1.2.4 Method of test

Initial condition

System Simulator:

Three cells (not simultaneously activated), cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in

MCC1/MNC1/LAC2/RAC1 (RAI-3), 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.

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 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 PS attach with the cause value ‘Illegal MS’. 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). 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.
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 REJECT	GMM cause = ‘Illegal MS’.
				The following messages are sent and shall be received on cell B.
6	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)
7	UE			Cell B is preferred by the UE.
8	UE			No ATTACH REQUEST sent to the SS (SS waits 30 seconds).
9	UE			The UE initiates an attach by MMI or by AT command.
10	UE			No ATTACH REQUEST sent to the SS (SS waits 30 seconds).
				The following messages are sent and shall be received on cell C.
11	SS			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)
12	UE			Cell C is preferred by the UE.
13	UE			No ATTACH REQUEST sent to the SS (SS waits 30 seconds).
14	UE			The UE initiates an attach by MMI or by AT command.
15	UE			No ATTACH REQUEST sent to the SS (SS waits 30 seconds).
16	UE			If possible (see ICS) switch off is performed. Otherwise the power is removed.
17	UE			The UE is powered up or switched on.
18	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A. SS allocates Mobile identity = TMSI-1.
19	UE			The UE initiates an attach (see ICS).
20	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
20a	<-		AUTHENTICATION AND CIPHERING REQUEST
20b	->		AUTHENTICATION AND CIPHERING RESPONSE
20c	SS			The SS starts integrity protection.
21	<-		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
22	->		ATTACH COMPLETE
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.2.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, 10, 13 and 15, UE shall:

– not send the ATTACH REQUEST message to SS, even if there is an instruction of attach request from MMI or from AT command.

At step20, UE shall:

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

12.2.1.3 PS attach / rejected / IMSI invalid / PS services not allowed

12.2.1.3.1 Definition

12.2.1.3.2 Conformance requirement

1) If the network rejects a PS attach procedure from the User Equipment with the cause ‘GPRS services not allowed’, 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 PS attach procedure from the User Equipment with the cause ‘GPRS services not allowed’ the User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.1.3.3 Test purpose

To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause ‘GPRS services not allowed’ (no valid PS-subscription for the IMSI).

12.2.1.3.4 Method of test

Initial condition

System Simulator:

Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (HPLMN, RAI-1) and cell B in MCC2/MNC1/LAC1/RAC1 (RAI-2).
Both 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 both cells.

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 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

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 normal attach with the cause value ‘GPRS services not allowed’. The SS checks that the UE does not perform PS attach in another PLMN.

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 "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 17.
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
3a	SS			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 = P-TMSI-1 Old Routing area identity = RAI-1
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c				The SS starts integrity protection.
5	<-		ATTACH REJECT	GMM cause = ‘GPRS services not allowed’
5a	SS			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 "Non-Suitable cell". Set the cell type of cell B to the "Serving cell". (see note)
7	UE			Cell B is preferred by the UE.
7a	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A.
8	UE			No ATTACH REQUEST sent to the SS (SS waits 30 seconds).
9	UE			If possible (see ICS) USIM removal is performed. Otherwise if possible (see ICS) switch off is performed. Otherwise the power is removed.
10	UE			The UE gets the USIM replaced, is powered up or switched on and initiates an attach (see ICS).
10a	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
11	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
11a	<-		AUTHENTICATION AND CIPHERING REQUEST
11b	->		AUTHENTICATION AND CIPHERING RESPONSE
11c	SS			The SS starts integrity protection.
12	<-		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
13	->		ATTACH COMPLETE
14	UE			The UE is switched off or power is removed (see ICS).
15	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
15a	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 .
16				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)
17	UE			The UE is set in UE operation mode A(see ICS) and the test is repeated from step 3 to step 15.
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.2.1.3.5 Test requirements

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

– not perform a PS attach procedure.

At step11, after the UE is switched on or a USIM is replaced, UE shall:

– perform the PS attach procedure.

12.2.1.4 PS attach / rejected / PLMN not allowed

12.2.1.4.1 Definition

12.2.1.4.2 Conformance requirement

1) If the network rejects a PS attach procedure from the User Equipment with the cause ‘PLMN not allowed’ the User Equipment shall:

1.1 not perform PS attach when switched on in the same routing area or location area (except for the HPLMN).

1.2 not perform PS attach when in the same PLMN and when that PLMN is not selected manually.

1.3 delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.

1.4 store the PLMN in the ‘forbidden PLMN’ list.

2) If the network rejects a PS attach procedure from the User Equipment with the cause ‘PLMN not allowed’ the User Equipment shall perform PS attach when a new PLMN is entered.

3) If the network rejects a PS attach procedure from the User Equipment with the cause ‘PLMN not allowed’ and if after that the PLMN from which this rejection was received, is manually selected, the User Equipment shall perform a PS attach procedure.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.1.4.3 Test purpose

To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause ‘PLMN not allowed’.

12.2.1.4.4 Method of test

Proc 1: Test procedure 1

Initial condition

System Simulator:

Four cells (not simultaneously activated), cell A in MCC1/MNC2/LAC1/RAC1 (RAI-8), cell B in MCC1/MNC2/LAC1/RAC1 (RAI-8), cell C in MCC1/MNC2/LAC2/RAC1 (RAI-9) and cell D in MCC2/MNC1/LAC1/RAC1 (RAI-2).
All four cells are operating in network operation mode II (in case of UE operation mode A). The PLMN of the four cells should NOT be that of the UE Home PLMN.
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 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 P-TMSI-1 and RAI-8. UE is Idle Updated on cell A.

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 PS attach with the cause value ‘PLMN not allowed’. The SS checks that the UE does not perform PS attach if activated in the same routing area or location area and performs PS attach only when a new PLMN is entered.

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". Set the cell type of cell C to the "Non-Suitable cell". Set the cell type of cell D 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-8
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c				The SS starts integrity protection.
5	<-		ATTACH REJECT	GMM cause = ‘PLMN not allowed’
5a				The SS releases the RRC Connection.
6	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
				The following messages are sent and shall be received on cell B.
7	UE			The UE is switched off.
8	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)
9	UE			The UE is powered up or switched on.
10	UE			Cell B is preferred by the UE.
11	UE			No ATTACH REQUEST sent to SS (SS waits 30 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 C to the "Serving cell". (see note)
13	UE			Cell C is preferred by the UE.
14	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
				The following messages are sent and shall be received on cell D.
15	SS			Set the cell type of cell C to the "Non-Suitable cell". Set the cell type of cell D to the "Serving cell". (see note)
16	UE			Cell D is preferred by the UE.
17	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A.
18	UE			The UE initiates an attach automatically, by MMI or by AT command.
19	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
19a	<-		AUTHENTICATION AND CIPHERING REQUEST
19b	->		AUTHENTICATION AND CIPHERING RESPONSE
19c	SS			The SS starts integrity protection.
20	<-		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
21	->		ATTACH COMPLETE
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.

Proc 2: Test procedure 2

Initial condition

System Simulator:

One cell operating in network operation mode II: MCC2/MNC1/LAC1/RAC1 (RAI-2). The PLMN of the cell should NOT be that of the Mobile Station Home PLMN.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE).

User Equipment:

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

Related ICS/IXIT statements

Test procedure

The SS rejects a PS attach with the cause value ‘PLMN not allowed’. The subscribers access rights is changed to allow PS attach. Then the PLMN from which this rejection was received is manually selected and the SS check that a PS attach is performed.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set in UE operation mode C or A (see ICS).
2	UE			The UE is powered up or switched on and initiates an attach (see ICS).
2a			Void
3	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-2
3a	<-		AUTHENTICATION AND CIPHERING REQUEST
3b	->		AUTHENTICATION AND CIPHERING RESPONSE
3c				The SS starts integrity protection.
4	<-		ATTACH REJECT	GMM cause = ‘PLMN not allowed’
4a				The SS releases the RRC Connection.
5	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds)
6	UE			The current PLMN is selected manually.
7			Void
8	UE			The UE initiates a PS attach. If UE does not attach automatically, then UE initiates the attach procedure by MMI or AT command.
9	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
9a	<-		AUTHENTICATION AND CIPHERING REQUEST
9b	->		AUTHENTICATION AND CIPHERING RESPONSE
9c	SS			The SS starts integrity protection.
10	<-		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
11	->		ATTACH COMPLETE

Specific message contents

None.

12.2.1.4.5 Test requirements

Test requirements for test procedure 1

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

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

At step6, UE shall:

– not perform PS attach procedure.

UE shall perform the following actions depending on the PLMN or the routing area or the location area

Case 1) UE is in the same routing area or location area when the power is switched on,

At step11, UE shall:

– not perform PS attach procedure.

Case2) UE is in the same PLMN, and this PLMN is not selected manually

At step14, UE shall:

– not perform PS attach procedure.

Case3) UE is in a new PLMN.

At step19, UE shall:

– perform the PS attach procedure.

Test requirements for test procedure 2

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

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

At step5, UE shall:

– not perform PS attach procedure.

At step9, when the UE is in the new PLMN, and this PLMN is selected manually, UE shall

– perform the PS attach procedure.

12.2.1.5a PS attach / rejected / roaming not allowed in this location area

12.2.1.5a.1 Definition

12.2.1.5a.2 Conformance requirement

1) If the network rejects a PS attach procedure from the User Equipment with the cause ‘roaming not allowed in this location area’ 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 and P-TMSI signature.

1.3 store the LA in the ‘forbidden location areas for roaming’ list.

1.4 perform PS attach when a new location area is entered.

1.5 Periodically search for its HPLMN.

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

3) The UE shall be capable of storing at least 10 entries in the list of ‘Forbidden location areas for roaming’.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.1.5a.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 to attach on that location area. Successful PS attach 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.

Test purpose 3

To test that at least 6 entries can be held in the list of ‘forbidden location areas for roaming’ (the requirement in 3GPP TS 24.008 is to store at least 10 entries. This is not fully tested by the third procedure).

Test purpose 4

To test that if a cell of the Home PLMN is available then the UE returns to it in preference to any other available cell.

12.2.1.5a.4 Method of test

Proc 1: Test procedure 1

Initial condition

System Simulator:

Three cells (not simultaneously activated), cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN), cell B in

MCC2/MNC1/LAC2/RAC1 (RAI-6, Not HPLMN) and cell C in MCC2/MNC1/LAC1/RAC2 (RAI-7, Not HPLMN).

All three 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.

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-2.

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 SS rejects a PS attach with the cause value ‘Roaming not allowed in this location area’. A new attempt for a PS attach is not possible. Successful PS attach / detach procedures are performed in another location area. A new attempt for a PS attach is performed in the 1^st location area. This attempt shall not succeed, as the LA is on the forbidden list.

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 19.
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.
3a			Void
3b	SS			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 = P-TMSI-1 Old Routing area identity = RAI-2
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c				The SS starts integrity protection.
5	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
6	UE			The SS releases the RRC connection.
6a	SS			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
				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.
9	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A. SS checks Mobile identity = IMSI SS allocates Mobile identity = TMSI-1.
10	UE			The UE initiates an attach automatically, by MMI or by AT command.
10a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
11	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
11a	<-		AUTHENTICATION AND CIPHERING REQUEST
11b	->		AUTHENTICATION AND CIPHERING RESPONSE
11c	SS			The SS starts integrity protection.
12	<-		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
13	->		ATTACH COMPLETE
13a	SS			The SS releases the RRC connection.
14	UE			The UE initiates a PS detach (without power off) by MMI or by AT command .
14a	SS			SS checks that the IE “Establishment cause” in any received RRC CONNECTION REQUEST message is set to “Detach”.
15	->		DETACH REQUEST	Detach type = ‘normal detach, GPRS detach’
16	<-		DETACH ACCEPT
16a	SS			The SS releases the RRC connection.
				The following messages are sent and shall be received on cell C.
17	SS			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)
18	UE			Cell C is preferred by the UE.
19	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds). The UE is switched off or power is removed (see ICS)
20	UE			UE is switched off.
21	SS			Set the cell type of cell C to the "Non-Suitable cell". (see note)
22	UE			The UE is set in UE operation mode A if supported (see ICS) and the test is repeated from step 2 to step 20.
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.

Proc 2: Test procedure 2

Initial condition

System Simulator:

One cell in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN) operating in network operation mode II.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE).

User Equipment:

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

Related ICS/IXIT statements

Test procedure

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

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

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			If UE operation mode C is supported, the UE is set in UE operation mode C (see ICS). If UE operation mode C is not supported, the UE is set in UE operation mode A.
2	UE			The UE is powered up or switched on and initiates an attach (see ICS).
2a			Void
2b	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
3	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-2
3a	<-		AUTHENTICATION AND CIPHERING REQUEST
3b	->		AUTHENTICATION AND CIPHERING RESPONSE
3c				The SS starts integrity protection.
4	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
5	UE			The SS releases the RRC connection.
5a	SS			No ATTACH REQUEST sent to the SS (SS waits 30 seconds).
6	UE			If possible (see ICS) switch off is performed. Otherwise the power is removed.
7	UE			The UE is powered up or switched on and initiates an attach (see ICS).
8
8a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
8b	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A. SS allocates Mobile identity = TMSI-1.
9	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
9a	<-		AUTHENTICATION AND CIPHERING REQUEST
9b	->		AUTHENTICATION AND CIPHERING RESPONSE
9c	SS			The SS starts integrity protection.
10	<-		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
11	->		ATTACH COMPLETE
11a	SS			The SS releases the RRC connection.

Proc 3: Test procedure 3

Initial condition

System Simulator:

Six cells (not simultaneously activated), cell A in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN), cell B in MCC2/MNC1/LAC2/RAC1 (RAI-3, Not HPLMN), cell C in MCC2/MNC1/LAC3/RAC1 (Not HPLMN), cell D in MCC2/MNC1/LAC4/RAC1 (Not HPLMN), cell E in MCC2/MNC1/LAC5/RAC1 (Not HPLMN), cell F in MCC2/MNC1/LAC6/RAC1 (Not HPLMN).
All six 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-2.

Related ICS/IXIT statements

Test procedure

The SS rejects a PS attach with the cause value ‘Roaming not allowed in this location area’. This is done for 6 different location areas. Then the SS checks that the UE does not attempt to perform an attach procedure on the non-allowed location areas.

Different types of UE may use different methods to periodically clear the list of forbidden areas (e.g. every day at 12am) for roaming. If the list is cleared while the test is being run, it may be necessary to re-run the test.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	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". Set the cell type of cell C to the "Non-Suitable cell". Set the cell type of cell D to the "Non-Suitable cell". Set the cell type of cell E to the "Non-Suitable cell". Set the cell type of cell F to the "Non-Suitable cell". (see note)
2	UE			If UE operation mode C is supported, the UE is set in UE operation mode C (see ICS). If UE operation mode C is not supported, the UE is set in UE operation mode A.
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
3b	SS			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 = P-TMSI-1 Old Routing area identity = RAI-2
5	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
6	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds)
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 "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.
9	UE		Registration on CS	See TS 34.108 This is applied only in case of UE operation mode A. Parameter mobile identity is IMSI.
10	UE			The UE initiates an attach automatically, by MMI or by AT command.
10a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
11	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
12	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
13	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
13a	SS			The SS releases the RRC connection.
				The following messages are sent and shall be received on cell C.
14	SS			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)
15	UE			Cell C is preferred by the UE.
16	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A. Parameter mobile identity is IMSI.
17	UE			The UE initiates an attach automatically, by MMI or by AT command.
17a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
18	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
19	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
20	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
				The following messages are sent and shall be received on cell D.
21a	SS			The SS releases the RRC connection.
21	SS			Set the cell type of cell C to the "Non-Suitable cell". Set the cell type of cell D to the "Serving cell". (see note)
22	UE			Cell D is preferred by the UE.
23	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A. Parameter mobile identity is IMSI.
24	UE			The UE initiates an attach automatically, by MMI or by AT command.
24a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
25	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
26	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
27	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
27a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
				The following messages are sent and shall be received on cell E.
28	SS			Set the cell type of cell D to the "Non-Suitable cell". Set the cell type of cell E to the "Serving cell". (see note)
29	UE			Cell E is preferred by the UE.
30	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A. Parameter mobile identity is IMSI.
31	UE			The UE initiates an attach automatically, by MMI or by AT command.
31a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
32	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
33	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
34	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
34a	SS			The SS releases the RRC connection.
				The following messages are sent and shall be received on cell F.
35	SS			Set the cell type of cell E to the "Non-Suitable cell". Set the cell type of cell F to the "Serving cell". (see note)
36	UE			Cell F is preferred by the UE.
37	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A.
38	UE			The UE initiates an attach automatically, by MMI or by AT command.
38a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
39	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
40	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
41	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds)
41a	SS			The SS releases the RRC connection.
				The following messages are sent and shall be received on cell E.
42	SS			Set the cell type of cell E to the "Serving cell". Set the cell type of cell F to the "Non-Suitable cell". (see note)
43	SS			Cell E is preferred by the UE.
44	UE			The UE initiates an attach automatically, by MMI or by AT command.
45	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
				The following messages are sent and shall be received on cell C.
46	SS			Set the cell type of cell C to the "Serving cell". Set the cell type of cell E to the "Non-Suitable cell". (see note)
47	SS			Cell C is preferred by the UE.
48	UE			The UE initiates an attach automatically, by MMI or by AT command.
49	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
				The following messages are sent and shall be received on cell A.
50	SS			Set the cell type of cell A to the "Serving cell". Set the cell type of cell C to the "Non-Suitable cell". (see note)
51	SS			Cell A will be preferred by the UE.
52	UE			The UE initiates an attach automatically, by MMI or by AT command.
53	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
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.

Proc 4: Test procedure4

Initial condition

System Simulator:

Two cells, cell A in MCC2/MNC1/LAC1/RAC1 (not HPLMN, RAI-2) and cell B in MCC1/MNC1/LAC1/RAC1 (HPLMN, RAI-1).
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.

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

Related ICS/IXIT statements

Test procedure

The SS rejects a PS attach with the cause value ‘Roaming not allowed in this location area’. A second cell belonging to the HPLMN is activated. It is checked that the UE returns to its HPLMN.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The following messages are sent and shall be received on cell A.
1	UE			If UE operation mode C is supported, the UE is set in UE operation mode C (see ICS). If UE operation mode C is not supported, the UE is set in UE operation mode 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 "Suitable neighbour 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
3b	SS			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 = P-TMSI-1 Old Routing area identity = RAI-2
5	<-		ATTACH REJECT	GMM cause = ‘Roaming not allowed in this location area’
6	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
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)
8	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A. Parameter mobile identity is IMSI.
9	UE			The UE initiates an attach automatically, by MMI or by AT command.
9a	SS			SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
10	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
10a	<-		AUTHENTICATION AND CIPHERING REQUEST
10b	->		AUTHENTICATION AND CIPHERING RESPONSE
10c	SS			The SS starts integrity protection.
11	<-		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
12	->		ATTACH COMPLETE
12a	->			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.2.1.5a.5 Test requirements

Test requirements for Test procedure1

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 step6, when the UE receives the ATTACH REJECT message with GMM cause = ‘Roaming not allowed in this location area’, UE shall:

– not perform the PS attach procedure.

At step11, when the new location area is entered, UE shall:

– perform the PS attach procedure

At step19, when the rejected location area is entered, UE shall

– not perform PS attach procedure.

Test requirements for Test procedure2

At step3, 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 step5, after the UE receives the ATTACH REJECT message with GMM cause = ‘Roaming not allowed in this location area’, UE shall:

– not perform PS attach procedure.

At step9, when the UE is switched on or USIM is replaced, UE shall:

– perform the PS attach procedure.

Test requirements for Test procedure3

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 step6, 13, 20, 27, 34 and 41, after the UE receives the ATTACH REJECT message with GMM cause = ‘Roaming not allowed in this location area’, UE shall:

– not perform PS attach procedure.

At step11, 18, 25, 32 and 39 , UE shall:

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

At step45, 49 and 53, UE shall:

– not perform PS attach procedure.

Test requirements for Test procedure4

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 step6, when the UE receives the ATTACH REJECT message with GMM cause = ‘Roaming not allowed in this location area’, UE shall:

– not perform PS attach procedure.

At step10, when a new location area is entered, UE shall:

– perform the PS attach procedure.

12.2.1.5b PS attach / rejected / No Suitable Cells In Location Area

12.2.1.5b.1 Definition

12.2.1.5b.2 Conformance requirement

If the network rejects a PS attach procedure from the User Equipment with the cause ‘No Suitable Cells In Location Area’, 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 and P-TMSI signature.

1.3 store the LA in the ‘forbidden location areas for roaming’ list.

1.4 not delete the list of "equivalent PLMNs".

1.5 perform PS attach when a new location area is entered.

Reference

3GPP TS 24.008 clauses 4.7.3.1.

12.2.1.5b.3 Test purpose

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

12.2.1.5b.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/LAC2/RAC1 (RAI-6)

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

Test procedure

The SS rejects a PS attach with the cause value ‘No Suitable Cells In Location Area’. The SS checks that the UE shall search for a suitable cell in a different location area on the equivalent PLMN and shall perform PS attach procedure in that cell.

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 A (see ICS).
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			Void
3a	SS			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 = 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’ Routing area identity = RAI-1 Equivalent PLMNs = MCC2,MNC1
6	<-		DETACH REQUEST	Detach type = re-attach required
7	->		DETACH ACCEPT
8	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) The SS configures power level of each Cell as follows. Cell A > Cell B = Cell C
9			Void
9a	SS			SS shall wait for 1 second to receive the Attach Request in step 10 on the existing RRC Connection. In case ATTACH REQUEST is not received within 1 second then existing RRC Connection is released.
10	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
10a	<-		AUTHENTICATION AND CIPHERING REQUEST
10b	->		AUTHENTICATION AND CIPHERING RESPONSE
10c				The SS starts integrity protection.
11	<-		ATTACH REJECT	GMM cause = ‘No Suitable Cells In Location Area’
12	SS			The SS initiates the RRC connection release.
				The following message are sent and shall be received on cell C.
13	UE		Registration on CS	See TS 34.108
14	UE			The UE initiates an attach automatically, by MMI or by AT command.
14a				SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
15	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
16	<-		AUTHENTICATION AND CIPHERING REQUEST
17	->		AUTHENTICATION AND CIPHERING RESPONSE
18	SS			The SS starts integrity protection.
19	<-		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
20	->		ATTACH COMPLETE
20a	SS			The SS releases the RRC connection.
NOTE: The definitions for "Suitable neighbour cell", "Non-suitable cell" and "Serving cell" are specified in TS 34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.2.1.5b.5 Test requirements

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 step15, when the UE enters a suitable cell in a different location area on the equivalent PLMN, UE shall:

– perform the PS attach procedure.

12.2.1.5c PS attach / rejected / Location area not allowed

12.2.1.5c.1 Definition

12.2.1.5c.2 Conformance requirement

1) If the network rejects a PS attach procedure from the User Equipment with the cause ‘Location area not allowed’ the User Equipment shall:

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

1.2 set the PS update status to GU3 ROAMING NOT ALLOWED.

1.3 reset the attach attempt counter.

1.4 store the LAI in the list of "forbidden location areas for regional provision of service".

1. perform a cell selection.
2. not delete the list of "equivalent PLMNs".

2) If the network rejects a PS attach procedure from the User Equipment with the cause ‘Location area not allowed’ and if the User Equipment is IMSI attached via MM procedures the User Equipment shall:

2.1 set the update status to U3 ROAMING NOT ALLOWED.

2.2 delete any TMSI, LAI and ciphering key sequence number.

2.3 reset the location update attempt counter.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.1.5c.3 Test purpose

To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause ‘Location area not allowed’.

12.2.1.5c.4 Method of test

Initial condition

System Simulator:

Three cells cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell C in MCC2/MNC1/LAC2/RAC1 (RAI-6).
All three cells are operating in network operation mode II (in case of UE operation mode A).

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

Related ICS/IXIT statements

Test procedure

The SS rejects a PS attach with the cause value ‘Location area not allowed’. The SS checks that the UE does not perform MM IMSI attach while in the same location area and performs PS attach when a new equivalent PLMN is entered.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			The following messages are sent and shall be received on cell A.
1	UE			If UE operation mode A is supported, If UE operation mode C is supported, the UE is set in UE operation mode A (see ICS). If UE operation mode A is not supported, the UE is set in UE operation mode C.
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		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A.
3a	SS			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 = P-TMSI-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’ Routing area identity = RAI-1 Equivalent PLMNs = MCC2,MNC1
6	<-		DETACH REQUEST	Detach type = re-attach required
7	->		DETACH ACCEPT
8	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 " Suitable neighbour cell ". Set the cell type of cell C to the " Suitable neighbour cell " (see note) The SS configures power level of each Cell as follows. Cell A > Cell B > Cell C
9			Void
10	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1
11	<-		ATTACH REJECT	GMM cause = ‘Location area not allowed’
11a	SS			The SS releases the RRC connection.
12	UE			The UE performs cell selection.
				The following messages are sent and shall be received on cell C.
12a	UE		Registration on CS	See TS 34.108. This is applied only for UE in UE operation mode A.
12b	UE			SS checks that the IE “Establishment cause” in any received RRC CONNECTION REQUEST message is set to “Registration”
13	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
14	<-		AUTHENTICATION AND CIPHERING REQUEST
15	->		AUTHENTICATION AND CIPHERING RESPONSE
16	SS			The SS starts integrity protection.
17	<-		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
18	->		ATTACH COMPLETE
19	UE			No MM IMSI attach request sent to SS (SS waits 30 seconds).
19a	SS			The SS releases the RRC connection.
NOTE: The definitions for "Suitable neighbour cell", "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.2.1.5c.5 Test requirements

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

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

At step12, UE shall:

– perform cell selection.

At step13, UE shall:

– perform PS attach procedure with Mobile identity = IMSI.

At step19, UE shall:

– not perform MM IMSI attach

12.2.1.5d PS attach / rejected / PS services not allowed in this PLMN

12.2.1.5d.1 Definition

12.2.1.5d.2 Conformance requirement

If the network rejects a PS attach procedure from the User Equipment with the cause ‘GPRS services not allowed in this PLMN’ the User Equipment shall:

The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall change to state GMM-DEREGISTERED.

The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list. A GPRS MS operating in MS operation mode C shall perform a PLMN selection instead of a cell selection.

A GPRS MS operating in MS operation mode A or B in network operation mode II or III, is still IMSI attached for CS services in the network.

As an implementation option, a GPRS MS operating in operation mode A or B may perform the following additional action. If no RR connection exists the MS may perform the action immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS may only perform the action when the RR connection is subsequently released:

– The MS may perform a PLMN selection according to 3GPP TS 23.122 [14].

The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause is:

– On the "User Controlled PLMN Selector with Access Technology " list or,

– On the "Operator Controlled PLMN Selector with Access Technology " list or,

– A PLMN identified as equivalent to any PLMN, with the same MCC, contained in the lists above

….

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.3.1 and 4.7.3.1.3.

12.2.1.5d.3 Test purpose

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

12.2.1.5d.4 Method of test

Initial condition

System Simulator:

Three cells cell A with 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/RAC2 (RAI-7).
All three cells are operating in network operation mode II (in case of UE operation mode A).

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

Related ICS/IXIT statements

Test procedure

The SS rejects a PS attach with the cause value ‘GPRS services not allowed in this PLMN’. The SS checks that the UE performs PS attach with attach type = GPRS attach when a new equivalent PLMN is entered.

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 A OR 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.
4	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A. Mobile identity = TMSI-1
5	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1
5a	<-		AUTHENTICATION AND CIPHERING REQUEST
5b	->		AUTHENTICATION AND CIPHERING RESPONSE
5c	SS			The SS starts integrity protection.
6	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 Routing area identity = RAI-8 Equivalent PLMNs = MCC2,MNC1
6a	->		ATTACH COMPLETE
7	<-		DETACH REQUEST	Detach type = re-attach required
8	->		DETACH ACCEPT
9	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 " Suitable neighbour cell ". Set the cell type of cell C to the " Non-suitable cell " (see note)
9a	SS			SS shall wait for 1 second to receive the Attach Request in step 10 on the existing RRC Connection. In case ATTACH REQUEST is not received within 1 second then existing RRC Connection is released.
10	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1
10a	<-		AUTHENTICATION AND CIPHERING REQUEST
10b	->		AUTHENTICATION AND CIPHERING RESPONSE
10c				The SS starts integrity protection.
11	<-		ATTACH REJECT	GMM cause = ‘GPRS services not allowed in this PLMN’
A12	UE			If the UE is in UE Operation Mode C Set the cell type of cell A to the " Suitable neighbour cell ". Set the cell type of cell B to the " Suitable neighbour cell ". Set the cell type of cell C to the " Serving cell " The UE performs PLMN selection.
B12	UE			If the UE is in Operation Mode A The UE initiates an attach automatically, by MMI or by AT command.
B12a	UE			No ATTACH REQUEST sent to SS (SS waits 30 seconds).
				The following messages are sent and shall be received on cell A. This verifies that a UE in operation mode A is still IMSI attached for CS services in cell A
B12a.1	<-		PAGING TYPE1	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"
B12a.2	->		RRC CONNECTION REQUEST
B12a.3	<-		RRC CONNECTION SETUP
B12a.4	->		RRC CONNECTION SETUP COMPLETE
B12a.5	->		PAGING RESPONSE
B12a.6	SS			The SS releases the RRC connection
B12b	SS			The SS is set in network operation mode II. Set the cell type of cell A to the " Suitable neighbour cell ". 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)
				The following messages are sent and shall be received on cell C.
B12c			Registration on CS	Only performed if UE is set to operation mode A.
13	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
14	<-		AUTHENTICATION AND CIPHERING REQUEST
15	->		AUTHENTICATION AND CIPHERING RESPONSE
16	SS			The SS starts integrity protection.
17	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-7 Equivalent PLMNs = MCC1,MNC2
18	->		ATTACH COMPLETE
				A Rel-11 or higher Operation Mode A UE supporting S1 mode may optionally initiate the RAU procedure in Steps 18a-18c within 10s. RRC Connection is released if the inactivity period is more than 2s
18a	->		ROUTING AREA UPDATING REQUEST	P-TMSI-2 signature Routing area identity = RAI-7
18aa	SS			The SS shall start integrity protection if RRC Connection is re-established to perform Step 18a.
18b	<-		ROUTING AREA UPDATING ACCEPT	Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-7 Equivalent PLMNs = MCC1, MNC2
18c	->		ROUTING AREA UPDATING COMPLETE
19			Void
NOTE: The definitions for "Suitable neighbour cell", "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.2.1.5d.5 Test requirements

At step5 and 10, when the UE is powered on or switched on, UE shall:

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

At step A12, UE shall:

– perform PLMN selection, only if the UE is in UE Operation Mode C.

At step13, UE shall:

– in case of operation mode C, perform PS attach procedure with Mobile identity = IMSI to the equivalent cell.

– in case of operation mode A, perform PS attach procedure and CS registration procedure (at step B12c)

At step B12a.1 UE shall:

– respond the Paging for CS domain service on cell A.

12.2.1.5e PS attach / rejected / Not authorized for this CSG

12.2.1.5e.1 Definition

12.2.1.5e.2 Conformance requirement

1. If the network rejects a PS attach procedure from the User Equipment with the cause ‘Not authorized for this CSG’, the User Equipment shall:

1.1 not perform PS attach when no suitable cell is entered.

1.2 delete the CSG ID of the cell, where the UE has sent the ATTACH REQUEST message, from the allowed CSG ID list stored in the UE.

1.3 not delete the list of "equivalent PLMNs".

1.4 perform PS attach when a new suitable cell is entered.

Reference

3GPP TS 24.008 clause 4.7.3.1

12.2.1.5e.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.2.1.5e.4 Method of test

Initial conditions:

System Simulator:

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

2)/CSG2.

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

Both Cell A and Cell B belong to PLMN 1.

NB: i) Cell A and B will be mapped to Cell 1 and 4 respectively as found in TS 34.108 clause 6.1.4.1a.

User Equipment:

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

The UE has been registered on the PLMN 1 in the CS domain.

UE Allowed CSG List contains CSG1and CSG2

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 PS attach with the cause value ‘ Not authorized for this CSG ‘. The SS checks that the UE shall search for a suitable cell on the same PLMN and shall perform PS attach procedure in that cell.

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 A OR The UE is set in UE operation mode C (see ICS).
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". (See note)
2a	UE				The UE is powered up or switched on and initiates an attach (see ICS).
3		UE		Registration on CS		See TS 34.108 This is applied only for UE in UE operation mode A.
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 = ‘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’ Routing area identity = RAI-1
10		<-		DETACH REQUEST		Detach type = re-attach required
11		->		DETACH ACCEPT
12		SS				Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Suitable neighbour cell". The SS configures power level of each Cell as follows. Cell A > Cell B
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 = P-TMSI-1 Old Routing area identity = RAI-1
13A		<–		AUTHENTICATION AND CIPHERING REQUEST
13B		–>		AUTHENTICATION AND CIPHERING RESPONSE
13C						The SS starts Integrity Protection
14		<-		ATTACH REJECT		GMM cause = ‘ Not authorized for this CSG ‘
15		SS				The SS initiates the RRC connection release.
						The following message are sent and shall be received on cell B.
16				Void
17		UE				The UE initiates an attach automatically, by MMI or by AT command.
18						SS checks that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Registration”.
19		->		ATTACH REQUEST		Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1
20		<-		AUTHENTICATION AND CIPHERING REQUEST
21		->		AUTHENTICATION AND CIPHERING RESPONSE
22		SS				The SS starts integrity protection.
23		<-		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
24		->		ATTACH COMPLETE
25		SS				The SS releases the RRC connection.
26		UE				The UE is switched Off or Power is removed. (See ICS)
27		SS				The SS checks that the IE “Establishment Cause” in any received RRC CONNECTION REQUEST is set to “Detach” (Message not sent if power is removed).
28		–>		DETACH REQUEST		Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
29						Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Non Suitable neighbour cell". The SS configures power level of each Cell as follows. Cell A > Cell B
30						The UE is powered up or switched ON.
31						SS Checks that the does not initiate a RRC CONNECTION REQ on Cell A
NOTE: The definitions for "Suitable neighbour cell", "Non-suitable cell" and "Serving cell" are specified in TS 34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

12.2.1.5e.5 Test requirements

At step5, 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 step14, after the UE receives ATTACH REJECT, UE shall:

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

At step19, when the UE camps on a suitable cell in on the same PLMN, UE shall:

perform the PS attach procedure.

At step23, after the UE receives ATTACH ACCEPT:

UE Allowed CSG List shall contain only CSG2.

12.2.1.6 PS attach / abnormal cases / access barred due to access class control

12.2.1.6.1 Definition

12.2.1.6.2 Conformance requirement

1) The UE shall not perform PS attach procedure, but stays in the current serving cell and applies normal cell reselection process.

2) The User Equipment shall perform the PS attach procedure when:

2.1 Access is granted.

2.2 Cell is changed.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.1.6.3 Test purpose

Test purpose1

To test the behaviour of the UE in case of access class control (access is granted).

Test purpose2

To test the behaviour of the UE in case of access class control (Cell is changed).

12.2.1.6.4 Method of test

Proc 1: Test procedure1

Initial condition

An access class x (0-15) is arbitrarily chosen. The USIM is programmed with this access class x. Communication with User Equipments using access class x is initially indicated to be barred.

System Simulator:

One cell operating in network operation mode II.
Access class x barred.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE).

User Equipment:

The UE has a valid 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 SS indicates access class x barred. A PS attach procedure is not performed.

The SS indicates that access class x is not barred. A PS attach procedure is performed.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The USIM is programmed with access class x.
2	UE			The UE is set in UE operation mode C (see ICS). If UE operation mode C not supported, goto step 12.
3	UE			The UE is powered up or switched on and attempts to initiate an attach (see ICS).
4	UE			No ATTACH REQUEST sent to SS, as access class x is barred (SS waits 30 seconds).
5	SS			The access class x is not barred anymore.
6	UE			The UE initiates a PS attach either automatically or manually (see ICS).
7	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
7a	<-		AUTHENTICATION AND CIPHERING REQUEST
7b	->		AUTHENTICATION AND CIPHERING RESPONSE
7c	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	UE			The UE is switched off or power is removed (see ICS).
11	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRS detach’
11a	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.
12	SS			The SS is set in network operation mode II.
13	UE			The UE is set in UE operation mode A(see ICS) and the test is repeated from step 3 to step 11.

Proc 2: Test procedure2

Initial condition

An access class x (0-15) is arbitrarily chosen. The USIM is programmed with this access class x. Communication with User Equipments using access class x is indicated to be barred on cell A.

System Simulator:

Two cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) has access class x barred, cell B in MCC1/MNC1/LAC1/RAC1 (RAI-1) has access class x not barred.
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

Switch off on button Yes/No

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

Test procedure

The SS indicates access class x barred. A PS attach procedure is not performed.

A cell change is performed into a cell where access class x is not barred. A PS attach procedure is performed.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The USIM is programmed with access class x.
	SS			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 "Suitable neighbour cell". (see note)
3	UE			The UE is set in UE operation mode C (see ICS).
4	UE			The UE is powered up or switched on and attempts to initiate an attach (see ICS).
5	UE			No ATTACH REQUEST sent to SS, as access class x is barred (SS waits 30 seconds).
				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			The UE initiates an attach either automatically or manually (see ICS).
8	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
8a	<-		AUTHENTICATION AND CIPHERING REQUEST
8b	->		AUTHENTICATION AND CIPHERING RESPONSE
8c	SS			The SS starts integrity protection.
9	<-		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
10	->		ATTACH 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.2.1.6.5 Test requirements

Test requirements for Test procedure1

At step4, when the UE access class x is barred, UE shall:

– not perform a PS attach procedure.

At step7, when the UE access class x is granted, UE shall:

initiate the PS attach procedure.

Test requirements for Test procedure2

At step5, when the UE access class x is barred, UE shall:

– not perform a PS attach procedure.

At step8, when the serving cell is changed, UE shall:

– initiate the PS attach procedure.

12.2.1.7 PS attach / abnormal cases / change of routing area

12.2.1.7.1 Definition

12.2.1.7.2 Conformance requirement

If a cell change into a new routing area occurs before an ATTACH ACCEPT or ATTACH REJECT message has been received, the GPRS attach procedure shall be aborted and re-initiated immediately.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.1.7.3 Test purpose

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

12.2.1.7.4 Method of test

Initial condition

System Simulator:

One cell with MCC1/MNC1/LAC1/RAC1 (RAI-1)
The cell is 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).

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)

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. The ATTACH ACCEPT message is delayed from the SS. The UE receive a new routing area code. The UE shall re-initiate a PS attach 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).
2	SS			The SS is set in network operation mode II. Set the cell type of cell A to the "Serving 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	SS			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 = P-TMSI-1 Old Routing area identity = RAI-1
5	SS			No response to the ATTACH REQUEST message is given by the SS.
6			Void
6a	<-		UTRAN MOBILITY INFORMATION	The SS conveys updated CN system information for the PS domain to the UE in connected mode, including a new routing area code. Note: SS transmits the updated system information with the new RAI information in SIB1
6b	->		UTRAN MOBILITY INFORMATION CONFIRM
7	UE			The UE automatically re-initiates the attach.
8	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
8a	<-		AUTHENTICATION AND CIPHERING REQUEST
8b	->		AUTHENTICATION AND CIPHERING RESPONSE
8c	SS			The SS starts integrity protection.
9	<-		ATTACH ACCEPT	No new mobile identity assigned. P-TMSI and P-TMSI signature not included. Attach result = ‘GPRS only attached’ Routing area identity = RAI-4
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

UTRAN MOBILITY INFORMATION (step 6a)

The contents of the UTRAN MOBILITY INFORMATION message in this test case is identical to the default message in TS 34.108, with the following exceptions.

Information Element	Value/remark
New U-RNTI	Not Present
New C-RNTI	Not Present
UE Timers and constants in connected mode	Not Present
CN information info
– PLMN identity	Not Present
– CN common GSM-MAP NAS system information	Not Present
– CN domain related information
– CN domain identity	CS domain
– CN domain specific GSM-MAP NAS system info
– T3212	Infinity
– ATT	0
– CN domain specific DRX cycle length coefficient	7
– CN domain related information
– CN domain identity	PS domain
– CN domain specific GSM-MAP NAS system info
– RAC	RAC-2
– NMO	1 (Network Mode of Operation II)
– CN domain specific DRX cycle length coefficient	7

12.2.1.7.5 Test requirements

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 step8, as the UE has received a new RAI in the UTRAN MOBILITY INFORMATION message before the ATTACH ACCEPT message or the ATTACH REJECT message is received by the UE, the UE shall:

– abort the PS attach procedure and re-initiate the PS attach procedure immediately with new information elements.

12.2.1.8 PS attach / abnormal cases / power off

12.2.1.8.1 Definition

12.2.1.8.2 Conformance requirement

When power is switched off before ATTACH ACCEPT message is received by the UE, the UE shall abort the PS attach procedure and perform a PS detach procedure.

Reference

3GPP TS 24.008 clause 4.7.3.

12.2.1.8.3 Test purpose

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

12.2.1.8.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.

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 is switched off after initiating an attach procedure. A PS detach is automatically performed by the UE before power is switched off.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set in UE operation mode C (see ICS). If UE operation mode C not supported, goto step 7.
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-TMSI-1 Routing area identity = RAI-1
4	SS			No response to the ATTACH REQUEST message is given by the SS.
5	UE			The UE is powered off and initiates a PS detach (with power off) by
6	->		DETACH REQUEST	Detach type = ‘power switched off, GPRS detach’
7	UE			The UE is set in UE operation mode A (see ICS) and the test is repeated from step 2 to step 6.

Specific message contents

None.

12.2.1.8.5 Test requirements

At step3, 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 step6, when power is switched off before ATTACH ACCEPT message is received, UE shall:

– abort the PS attach procedure and perform the PS detach procedure.

12.2.1.9 PS attach / abnormal cases / PS detach procedure collision

12.2.1.9.1 Definition

12.2.1.9.2 Conformance requirement

1) When a DETACH REQUEST message is received by the UE (any cause except re-attach) while waiting for an ATTACH ACCEPT message, the UE shall terminate the PS attach procedure and continue with the PS detach procedure.

2) When a DETACH REQUEST message is received by the UE (cause re-attach) while waiting for an ATTACH ACCEPT message, the UE shall ignore the PS detach procedure and continue with the PS attach procedure.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.1.9.3 Test purpose

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

12.2.1.9.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode II.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE).

User Equipment:

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

The UE has been registered in the CS domain.

Related ICS/IXIT statements

Test procedure

The UE initiates a PS attach procedure. The SS does not answer the PS attach procedure, but initiates a PS detach procedure (any cause except re-attach). The UE shall terminate the PS attach procedure and continue with the PS detach procedure.

The UE initiates a PS attach procedure. The SS does not answer the PS attach procedure, but initiates a PS detach procedure (cause re-attach). The UE shall ignore the PS detach procedure and continue with the PS attach.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set in UE operation mode C (see ICS).
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-TMSI-1 Old Routing area identity = RAI-1
4	SS			The SS ignores the ATTACH REQUEST message and initiates a detach procedure.
5	<-		DETACH REQUEST	Detach type = ‘re-attach not required’
6	->		DETACH ACCEPT
7	UE			The UE initiates the attach procedure by MMI or AT command.
8	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
9	SS			The SS ignores the ATTACH REQUEST message and initiates a detach procedure.
10	<-		DETACH REQUEST	Detach type = ‘re-attach required’
11	UE			The UE ignores the DETACH REQUEST message and continue with the attach procedure.
12	<-		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
13	->		ATTACH COMPLETE

Specific message contents

None.

12.2.1.9.5 Test requirements

At step3, 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.

UE shall perform the following actions depending on the Detach type in the DETACH REQUEST message.

Case1) Detach type = ‘re-attach not required’ GMM cause is not re-attach

At step6, when the DETACH REQUEST message is received by the UE while waiting for an ATTACH ACCEPT message, UE shall:

– terminate the PS attach procedure and continue with the PS detach procedure.

Case2) Detach type = ‘re-attach required’

At step11, when the DETACH REQUEST message is received by the UE while waiting for an ATTACH ACCEPT message, UE shall:

– ignore the PS detach procedure and continue with the PS attach procedure.

12.2.1.10 PS attach / abnormal cases / Failure due to non-integrity protection

12.2.1.10.1 Definition

12.2.1.10.2 Conformance requirement

Except the messages listed below, no layer 3 signalling messages shall be processed by the receiving MM and GMM entities or forwarded to the CM entities, unless the security mode control procedure is activated for that domain.

– GMM messages:

– AUTHENTICATION & CIPHERING REQUEST

– AUTHENTICATION & CIPHERING REJECT

– IDENTITY REQUEST

– ATTACH REJECT

– ROUTING AREA UPDATE ACCEPT (at periodic routing area update with no change of routing area or temporary identity)

– ROUTING AREA UPDATE REJECT

– SERVICE REJECT

– DETACH ACCEPT (for non power-off)

Reference(s):

3GPP TS 24.008 clause 4.1.1.1.1

12.2.1.10.3 Test purpose

To verify that the UE ignores NAS signalling messages when the security mode procedure is not activated.

12.2.1.10.4 Method of test

Initial Conditions

System Simulator:

User Equipment:

The UE has a valid IMSI.

If the UE is in UE operation mode A, then the UE has been registered in the CS domain.

Related ICS 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

Test procedure

The attach procedure is initiated. Upon reception of ATTACH REQUEST message from the UE, the SS responds with an ATTACH ACCEPT message without the integrity protection. The UE shall ignore this message and re-transmit ATTACH REQUEST message at expiry of timer T3310.

This time the SS starts the authentication procedure and initiates the integrity protection. After receiving ATTACH ACCEPT message, the UE shall respond to ATTACH COMPLETE message.

Expected Sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
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 procedure (see ICS).
3	SS			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
5	<-		AUTHENTICATION AND CIPHERING REQUEST	Request authentication. Set PS-CKSN
6	->		AUTHENTICATION AND CIPHERING RESPONSE	RES
7	SS			The SS does not initiate the security mode procedure.
8	<-		ATTACH ACCEPT
9	UE			The UE ignores ATTACH ACCEPT message.
10	SS			The SS waits until the UE sends a new ATTACH REQUEST message in step 11.
11	->		ATTACH REQUEST	The UE re-transmits the message. The SS verifies that this ATTACH REQUEST message is sent by the UE after the expiry of T3310 (15 sec). The period of time to check is either between the ATTACH REQUEST messages or between the RRC CONNECTION REQUEST message and the second ATTACH REQUEST message. Attach type = ‘GPRS attach’ Mobile identity = IMSI
12	<-		AUTHENTICATION AND CIPHERING REQUEST	Request authentication. Set PS-CKSN
13	->		AUTHENTICATION AND CIPHERING RESPONSE	RES
14	SS			The SS starts integrity protection.
15	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI
16	->		ATTACH COMPLETE

Specific Message Contents

None.

12.2.1.10.5 Test requirements

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

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

At step9, UE shall;

– ignore the first ATTACH ACCEPT message.

At step11, UE shall;

– re-transmit ATTACH REQUEST message after expiry of timer T3310.

At step16, UE shall;

– respond to ATTACH COMPLETE message after the UE receives the second ATTACH ACCEPT message.

12.2.1.11 PS attach / accepted / follow-on request pending indicator set

12.2.1.11.1 Definition and applicability

UE which supports follow-on request procedure.

12.2.1.11.2 Conformance requirement

1) In UMTS, if the MS wishes to prolong the established PS signalling connection after the GPRS attach procedure, it may set a follow-on request pending indicator on.

2) In UMTS, the network should prolong the PS signalling connection if the mobile station has indicated a follow-on request pending in ATTACH REQUEST. The network may also prolong the PS signalling connection without any indication from the mobile terminal.

Reference

3GPP TS 24.008 clause 4.7.3.1.1 and 4.7.3.1.3

12.2.1.11.3 Test purpose

To test the behaviour of the UE if the follow-on request pending indicator can be set on during the attach procedure.

The following cases are identified:

1) follow-on request pending indicator may be set to indicate further signalling messages from the UE

2) follow-on request pending indicator not set, no further signalling messages expected from the UE

12.2.1.11.4 Method of test

Initial condition

System Simulator:

1 cell, operating in network operation mode II.

The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (to prevent repeated CS domain registration and/or IMSI Detach by UEs in operation mode A).

User Equipment:

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

The UE has been registered in the CS domain.

Related ICS/IXIT statements

Support of PS service Yes/No

Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No
Method of context activation

Support of Follow On Proceed Yes/No

Test procedure

1) The UE is attached, then the Detach Request is originated from the UE indicating "GPRS detach without switching off". The SS responds with a Detach Accept after completing the security mode procedures. A PDP context activation is then requested by the user. The PS attach (ATTACH REQUEST) is then indirectly caused by a requested PDP context activation. UE shall set the Follow-ON Request bit to 1 in the ATTACH REQUEST message. The SS returns the ATTACH ACCEPT message to the UE. Now session management can proceed with PDP context activation. On receipt of the ACTIVATE PDP CONTEXT REQUEST message an ACTIVATE PDP CONTEXT ACCEPT is returned by the SS with the same requested QoS to finish the PC call establishment. The SS releases the RRC connection and the UE is switched off.

2) The UE is switched on and initiates PS attach (ATTACH REQUEST). UE shall set the Follow-ON Request bit to 0 in the ATTACH REQUEST message. The SS returns the ATTACH ACCEPT message to the UE. The SS verifies UE does not sent any messages on the PS Signalling Connection for 10 seconds. SS releases the RRC connection.

Expected Sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
0	UE			Detach is performed by the UE using MMI or AT Commands
1	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Detach".
2			DETACH REQUEST
3	SS			The SS starts integrity protection.
4			DETACH ACCEPT	SS sends Detach Accept message.
5	SS			The SS releases the RRC connection.
6	UE			Initiate a context activation
7	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
8			ATTACH REQUEST	The UE requests attach. UE shall set the FOR bit to 1
9	SS			The SS starts integrity protection.
10			ATTACH ACCEPT	The SS accepts attach Negotiated Ready timer value IE should not be included Force to standby IE set to “Force to standby not indicated”
11			ACTIVATE PDP CONTEXT REQUEST	The UE requests a PDP context activation, enters the state PDP-ACTIVE-PENDING and starts timer T3380
12	SS			The SS establishes the RAB.
13			ACTIVATE PDP CONTEXT ACCEPT	The SS accepts the PDP context activation.
14	SS			The SS releases the RRC connection due to inactivity (no user data transferred)
15	UE			The UE is switched off or power is removed (see ICS).
16	SS			SS checks that the IE "Establishment cause" in any received RRC CONNECTION REQUEST message is set to "Detach" (message not sent if power is removed).
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	UE			The UE is powered up or switched on and initiates an attach (see ICS).
20	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
21	->		ATTACH REQUEST	The UE requests attach. The UE shall set the FOR bit to 0.
22			AUTHENTICATION AND CIPHERING REQUEST
23			AUTHENTICATION AND CIPHERING RESPONSE
24	SS			The SS starts integrity protection.
25	<-		ATTACH ACCEPT	The SS accepts attach Negotiated Ready timer value IE should not be included Force to standby IE set to “Force to standby not indicated”
26				The SS does not respond and waits for the time of 5 seconds. No further messages are expected from the UE on the current PS Signalling Connection.
27	SS			The SS releases the RRC connection

Specific message contents

None.

12.2.1.11.5 Test requirements

At step 8 the UE shall send an ATTACH REQUEST with FOR bit set to 1

At step 21 the UE shall send an ATTACH REQUEST with FOR bit set to 0.

12.2.1.12 PS attach / abnormal cases / access barred due to domain specific access restriction for PS domain

12.2.1.12.1 Definition

This test case is applicable for Rel-5 UEs supporting DSAC and Rel-6 or later UEs.

12.2.1.12.2 Conformance requirement

TS24.008 4.1.1.2.2

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 or III 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.4.4.9, 4.5.1.2, 4.7.3.1.5, 4.7.5.1.5, and 4.7.13.5.

TS24.008 4.7.3.1.5

a) Access barred because of common access class control or PS domain specific access control

The GPRS attach procedure shall not be started. The MS stays in the current serving cell and applies normal cell reselection process. The GPRS attach procedure is started as soon as possible, i.e. when access is granted or because of a cell change.

Reference

3GPP TS 24.008 clause 4.1.1.2.2, 4.7.3.1.5

12.2.1.12.3 Test purpose

Test purpose

To test the behaviour of the UE in case of domain specific access control for PS domain.

12.2.1.12.4 Method of test

Initial condition

An access class x (0-15) is arbitrarily chosen. The USIM is programmed with this access class x.
The SS informs the UE that the PS domain specific access class x is barred in the cell.

System Simulator:

One cell operating in network operation mode II.
PS domain specific access class x is barred.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE).

User Equipment:

The UE has a valid 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 Support of DSAC Yes/No

Test procedure

The SS indicates that PS domain access class x is barred. A PS attach procedure is not performed.
The SS indicates that PS domain access class x is not barred. A PS attach procedure is performed.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The USIM is programmed with access class x.
2	UE			The UE is set in UE operation mode A or C (see ICS).
3	UE			The UE is powered up or switched on and attempts to initiate an attach (see ICS).
4	UE			No ATTACH REQUEST sent to the SS as PS domain access class x is barred. The SS waits 30 seconds.
5	SS			PS domain access class x is not barred anymore.
6	UE			The UE initiates a PS attach. If UE does not attach automatically, then UE initiates the attach procedure by MMI or AT command.”
7	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
8	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
9	<-		AUTHENTICATION AND CIPHERING REQUEST
10	->		AUTHENTICATION AND CIPHERING RESPONSE
11	SS			The SS starts an integrity protection.
12	<-		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
13	->		ATTACH COMPLETE
14	SS			The SS releases the RRC connection.

Specific message contents

None.

12.2.1.12.5 Test requirements

At step4, when the SS indicates that PS domain specific access class x is barred, the UE shall:

– not perform a PS attach procedure.

At step7, when the SS indicates that PS domain specific access class x is not barred, the UE shall:

– initiate the PS attach procedure.

12.2.1.13 NITZ / GMM/ Time zone, Time and DST Handling

12.2.1.13.1 Definition

To check that the UE correctly handles time zone, time and DST.

12.2.1.13.2 Conformance requirement

The feature Network Identities and Timezone shall make it possible for a serving PLMN to transfer its current identity, universal time, DST and LTZ to MSs, and for the MS to store and use this information. Each one of these elements is optional. The feature significantly enhances roaming as it enables the accurate indication of network identities that are either newer than the ME or have changed their name since the ME was manufactured or sold. Additionally time and timezone information can be utilised by MEs as desired.

When using the default character set (see 3GPP TS 23.038 [3]), the serving PLMN shall make both a "short" and a "long" name available to the MS. As an alternative or, in addition, to the default character set, the serving PLMN can make a name available in UCS2. The MS shall be free to choose one of these names depending upon its own characteristics and/or limitations, such as those of its display.

NOTE: Guidance is sought, particularly from non-European operators, as to whether long and short name is required in UCS2 format.

The Network Operator may change the network identity at any time. However the change of network identity need not force immediate transfer of information to the MS.

As a network option, it shall be possible to send universal time (UT) by the network. Time information shall include: Year, Month, Day, Hour, Minute, Second, Timezone and DST. The expected accuracy of the time information is in the order of minutes.

NOTE: Universal time indicates the time at which this information element (see 3GPP TS 24.008 [2]) may have been sent by the network. Thus it can be assumed that the accuracy of the time information when it arrives at the MS is usually within a couple minutes.

The serving PLMN shall make Local Time Zone (LTZ) available to the MS as an offset from Universal Time in units of 15 minutes.

When the LTZ is compensated for DST (summertime), the serving PLMN shall provide a DST parameter to indicate this. The adjustment for DST can be +1h or +2h.

The TP-Service‑Centre‑Time‑Stamp field is given in semi‑octet representation, and represents the local time in the following way:

	Year:	Month:	Day:	Hour:	Minute:	Second:	Time Zone
Digits: (Semi-octets)	2	2	2	2	2	2	2

The Time Zone indicates the difference, expressed in quarters of an hour, between the local time and GMT. In the first of the two semi‑octets, the first bit (bit 3 of the seventh octet of the TP‑Service‑Centre‑Time‑Stamp field) represents the algebraic sign of this difference (0: positive, 1: negative).

The Service‑Centre‑Time‑Stamp, and any other times coded in this format that are defined in the present document, represent the time local to the sending entity.

If the MS has knowledge of the local time zone, then any time received (e.g. Service‑Centre‑Time‑Stamp) at the MS may be displayed in the local time rather than the time local to the sending entity. Messages shall be stored as received without change to any time contained therein.

The Time Zone code enables the receiver to calculate the equivalent time in GMT from the other semi‑octets in the Service‑Centre‑Time‑Stamp, or indicate the time zone (GMT, GMT+1H etc.), or perform other similar calculations as required by the implementation. The value contained in the Time Zone field must take into account daylight saving time, such that when the sending entity changes from regular (winter) time to daylight saving (summer) time, there is a change to the value in the Time Zone field, for example in the UK the winter setting is 00000000 and the summer setting is 01000000.

If the MS receives a non‑integer value in the SCTS, it shall assume that the digit is set to 0 but shall store the entire field exactly as received.

If the local time zone has been adjusted for Daylight Saving Time, the network shall indicate this by including the IE Network Daylight Saving Time.

References

3GPP TS 22.042 sub clause 4

3GPP TS 23.040 sub clause 9.2.3.11

3GPP TS 24.008 sub clause 9.4.19.4

12.2.1.13.3 Test purpose

To verify that a UE supporting any of the NITZ Time related feature (Local Time Zone, Universal Time and DST IE (and thus GMM Information) is able to handle them properly.

12.2.1.13.4 Method of test

Related ICS/IXIT statements

Support of FDD Yes/No.

Support of PS bearer service Yes/No.

– Support of Switch on off button Yes/No.

– Support of Automatic GPRS attach procedure at switch on or power on Yes/No.

– Support of NITZ DST Yes/No.

– Support of NITZ Universal Time for PLMN Yes/No.

– Support of NITZ Local Time Zone for PLMN Yes/No.

Initial conditions

System Simulator:

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

User Equipment:

– The UE is "idle updated" on cell A.

– The UE is switched off with a valid USIM inserted.

Test procedure

Following the GPRS attachment on Cell A, SS sends its local time and date (on GMT+1, Winter Time) using the GMM INFORMATION Message to the UE. The test operator verifies then the parameters and/or the time and date stored in the MS.

The UE is then moved to Cell B, and after a ROUTING AREA UPDATE procedure, the time is changed to “Summer Time” with the DST IE using a GMM INFORMATION Message. The test operator verifies then the parameters and/or the time and date stored in the UE and switches Off the UE

The UE is then moved to Cell A, and after a ROUTING AREA UPDATE procedure the Time Zone is then changed, no DST present (GMT+2, Winter Time), using GMM INFORMATION message. The operator verifies then the parameters and/or the time stored on the UE.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	UE			Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Non Suitable neighbour cell". The UE is powered up or switched on and initiates an attach (see PICS). The following messages are sent and shall be received on cell A
2	->		ATTACH REQUEST
3	SS			The SS starts integrity protection.
4	<-		ATTACH ACCEPT	Attach result = Attach type in step 2 Mobile identity = P-TMSI-2 P-TMSI-2 signature Routing area identity = RAI-1
5	->		ATTACH COMPLETE
6	<-		GMM INFORMATION	Universal Time IE is included: “< Current Year >/12/31 04:15:00” for Local Time “+ 1 hour” for Timezone No DST or Local Time Zone IE included See specific message content
7	SS			The SS releases the RRC connection
8	UE			Operator Action: The use of the supported Fields is checked: Universal Time: Year: < Current Year > Month: December Day: 31^st Hour: 5 Hours Minute: 15 Minutes Timezone: GMT+1 Local Time Zone: Not sent DST: Daylight Saving Time not in use (i.e. winter time) (See Note)
9	SS			Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the "Suitable neighbour cell". The following messages are sent and shall be received on cell B
10	->		ROUTING AREA UPDATING REQUEST	P-TMSI-2 signature Routing area identity = RAI-1
11	SS			The SS starts integrity protection.
12	<-		ROUTING AREA UPDATING ACCEPT	Update result = Update type in step 10 Mobile identity = P-TMSI-1 P-TMSI-1 signature Routing area identity = RAI-4
13	->		ROUTING AREA UPDATING COMPLETE
14	<-		GMM INFORMATION	Local Time Zone IE and DST IE are included: “+ 2 hours” for Timezone (including DST) “+ 1 hour” for DST See specific message content
15	SS			The SS releases the RRC connection
16	UE			Operator Action: The use of the supported Fields is checked: Universal Time Year: < Current Year > Month: December Day: 31^st Hour: 6 Hours Minutes: 15 Minutes Timezone: GMT+2 Local Time Zone Timezone: GMT+2 (DST included) DST: Daylight Saving Time in use (i.e. “summer time”) (See Note)
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". The following messages are sent and shall be received on cell A
18	->		ROUTING AREA UPDATING REQUEST	P-TMSI-1 signature Routing area identity = RAI-4
19	SS			The SS starts integrity protection.
20	<-		ROUTING AREA UPDATING ACCEPT	Update result = Update type in step 18 Mobile identity = P-TMSI-2 P-TMSI-2 signature Routing area identity = RAI-1
21	->		ROUTING AREA UPDATING COMPLETE
22	<-		GMM INFORMATION	Only Local Time Zone IE is included: “+ 2 hours” for Timezone No DST IE included See specific message content
23	SS			The SS releases the RRC connection
24	UE			Operator Action: The use of the supported Fields is checked: Universal Time: Year: < Current Year > Month: December Day: 31^st Hour: 6 Hours Minutes: 15 Minutes Timezone: GMT+2 Local Time Zone: Timezone: GMT+2 DST: Daylight Saving Time not in use (i.e. winter time) (See Note)
Note: In step 6, 16 and 24 the “minute” is not so relevant and can be higher than “15” depending on operator’s action time. The check of Timezone and DST is done implicitly by checking the time only in case UE does not support the display of these two fields. Current Year is derived by the SS Steps 9-16 resp. 17-24 are only performed if the UE supports pc_LocalTimeZone. In Steps 8, 16, 24 Local Time Zone is checked. DST is to be checked only if the UE supports pc_DaylightSavingTime.

Specific message contents:

GMM Information on step 6:

Information element	Value/remark
Universal Time IE	47
Year	< Current Year >
Month	21 – December
Day	13 – 31
Hour	40 – 4 hours
Minute	51 – 15 Minutes
Second	00 – 0 second
Time Zone	40 – GMT+1 (415 minutes+ 015 minutes DST)

GMM Information on step 14:

Information element	Value/remark
Local Time Zone IE	46
Time Zone	80 – GMT+1+1(415 minutes+ 415 minutes DST)
Daylight Saving Time IE	49
Length of DST Content	1
Value	1 – + 1 hour (summer time)

GMM Information on step 22:

Information element	Value/remark
Local Time Zone IE	46
Time Zone	80 – GMT+2 (815 minutes+ 015 minutes DST)

12.2.1.13.5 Test requirements

In step 6, 16 and 24 the UE populates the supported fields with the correct values.

12.2.1.14 NITZ / GMM/ NITZ Parameters Storage and Deletion

12.2.1.14.1 Definition

To check that the UE correctly stores and deletes NITZ parameters.

12.2.1.14.2 Conformance requirement

Switching off the MS should not cause the updated name of the network(s) to be deleted.

References

3GPP TS 22.042 sub clause 4 and 6.2

12.2.1.14.3 Test purpose

To verify that a UE supporting any of the NITZ Name related feature (Short or Full PLMN name and thus GMM Information) is able to handle the names properly and does not erase the PLMN name sent using NITZ procedure at switch off.

12.2.1.14.4 Method of test

Related ICS/IXIT statements

Support of FDD Yes/No.

Support of PS bearer service Yes/No.

– Support of Switch on off button Yes/No.

– Support of Automatic GPRS attach procedure at switch on or power on Yes/No.

– Support of NITZ Full name for PLMN Yes/No.

– Support of NITZ Short name for PLMN Yes/No.

Initial conditions

System Simulator:

One cell operating in network operation mode I.

User Equipment:

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

USIM field	Value
EF_UST	Services 19 and 51 are not supported

The UE is "idle updated" on cell A.The UE is switched off.

Test procedure

Following the GPRS attachment, SS sends a Short and a Full Name for the PLMN using the GMM INFORMATION Message to the UE. The operator verifies then the parameters stored in the UE.

The UE is then switched Off. The UE is re-attached after switching on, and the operator verifies then that the names are still stored/used in the MS.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	UE			Set the cell type of cell A to the "Serving cell". The UE is powered up or switched on and initiates an attach (see PICS). The following messages are sent and shall be received on cell A
2	->		ATTACH REQUEST
3	SS			The SS starts integrity protection.
4	<-		ATTACH ACCEPT	Attach result = Attach type in step 2 Mobile identity = P-TMSI-2 P-TMSI-2 signature Routing area identity = RAI-1
5	->		ATTACH COMPLETE
6	<-		GMM INFORMATION	Full Name for Network and Short Name for Network IE are included: “NITZDeletionPLMN” for Full Name “NITZPLMN” for Short Name See specific message content
7	UE			Operator Action: Verify that the names are stored and handled correctly according to Specific PICS Statements: “NITZDeletionPLMN” for Full name, “NITZPLMN” for Short name
8	UE			The UE is switched off or power is removed (see PICS).
9	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, combined GPRS / IMSI detach’
10	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.
11	UE			The UE is powered up or switched on and initiates an attach (see ICS).
12	->		ATTACH REQUEST
13	SS			The SS starts integrity protection.
14	<-		ATTACH ACCEPT	No new mobile identity assigned. P-TMSI and P-TMSI signature not included. Attach result = Attach type in step 12
15	SS			The SS releases the RRC connection
16	UE			Operator Action: Verify that the same names are still stored and handled correctly according to Specific PICS Statements: “NITZDeletionPLMN” for Full name, “NITZPLMN” for Short name

Specific message contents:

GMM Information, step 5:

Information element	Value/remark
Full Name IE	43
Length	0F (15 octets)
Ext	1 – – – – – – – (Spare Bit)
Coding scheme	– 0 0 0 – – – – (Cell Broadcast data coding scheme, GSM default alphabet, language unspecified)
Add CI	– – – – 0 – – – (Initials Country not included)
Spare Bit in final Octet	– – – – – 0 0 0 ( No info about number of spare bits)
Text String	CE 24 55 4B 2 C B3 CB F4 F4 DB 0D 65 36 9 D
	(“NITZDeletionPLMN“)
Short Name IE	45
Length	08 (8 octets)
Ext	1 x x x x x x x (Spare Bit)
Coding scheme	x 0 0 0 x x x x (Cell Broadcast data coding scheme, GSM default alphabet, language unspecified)
Add CI	x x x x 0 x x x (Initials Country not included)
Spare Bit in final Octet	x x x x x 0 0 0 (No info about number of spare bits )
Text String	CE 24 55 0B 65 36 9D
	(“NITZPLMN”)

12.2.1.14.5 Test requirements

In step 7 the UE populates the supported fields with the correct values.

In step 16 the UE still contains the supported fields with the values as received in step 7.

12.2.1.15 NITZ / GMM/ / MM and GMM Signalling

12.2.1.15.1 Definition

To check that the UE correctly stores NITZ parameters and displays the latest received NITZ parameters.

12.2.1.15.2 Conformance requirement

When using the default character set (see TS 23.038 [4]), the serving PLMN shall make both a "short" and a "long" name available to the MS. As an alternative or, in addition, to the default character set, the serving PLMN can make a name available in UCS2. The MS shall be free to choose one of these names depending upon its own characteristics and/or limitations, such as those of its display.

It is expected that the MS will display the most up to date information transferred to it.

References

3GPP TS 22.042 sub clause 4 and 6.2

12.2.1.15.3 Test purpose

To verify that a UE supporting NITZ (any of the Fields) is able to handle both MM INFORMATION and GMM INFORMATION messages and those parameters set in the latest message override the previous ones.

12.2.1.15.4 Method of test

Related ICS/IXIT statements

Support of FDD Yes/No.

Support of PS bearer service Yes/No.

– Support of Switch on off button Yes/No.

– Support of Automatic GPRS attach procedure at switch on or power on Yes/No.

– Support of NITZ DST Yes/No.

– Support of NITZ Universal Time for PLMN Yes/No.

– Support of NITZ Local Time Zone for PLMN Yes/No.

– Support of NITZ Full name for PLMN Yes/No.

– Support of NITZ Short name for PLMN Yes/No.

Initial conditions

System Simulator:

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

User Equipment:

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

USIM field	Value
EF_UST	Services 19 and 51 are not supported

The UE is "idle updated" on cell A.

The UE is switched off.

Test procedure

Following its GPRS Attachment procedure, the UE receives from SS, through the GMM INFORMATION a complete set of NITZ parameters (PLMN long name, short name, and Universal time with local time adjustment). The operator verifies then the names used and the time and date stored in the UE (according to specific PICS Statements).

The UE is then paged on its paging group with its IMSI. SS verifies that the UE sends a PAGING RESPONSE. SS sends back a MM INFORMATION message changing the NITZ PLMN names (short and full names) and the local time information.

The operator verifies then that the new NITZ names are used and the time information changed (if supported).

The serving cell is then lowered and the UE triggers a ROUTING AREA UPDATE procedure on the second cell. Following this procedure, SS sends some new NITZ PLMN names (full and short) using the GMM INFORMATION message.

The operator verifies then that the new NITZ names are used, if supported, and, if possible, that the time information is not changed.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	UE			Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Non Suitable neighbour cell". The following messages are sent and shall be received on cell A The UE is powered up or switched on and initiates an attach (see PICS). The following messages are sent and shall be received on cell A
2	->		ATTACH REQUEST
3	SS			The SS starts integrity protection.
4	<-		ATTACH ACCEPT	Attach result = Attach type in step 2 Mobile identity = P-TMSI-2 P-TMSI-2 signature Routing area identity = RAI-1
5	->		ATTACH COMPLETE
6	<-		GMM INFORMATION	Full Name for Network, Short Name for Network and Universal Time IE are included: “NITZ GMM PLMN” for Full Name “GMM PLMN” for Short Name “< Current Year >/12/31 04:15:00” for Local Time “+ 1 hour” for Timezone No DST or Local Time Zone IE included See specific message content
7	SS			The SS releases the RRC connection
8	UE			Operator Action: Verify that the names and time are stored and handled correctly according to specific PICS Statements: “NITZ GMM PLMN” for Full name, “GMM PLMN” for Short name The use of the supported Fields is checked: Universal Time: Year: < Current Year > Month: December Day: 31^st Hour: 5 Hours Minute: 15 Minutes Timezone: GMT+1 Local Time Zone: Not Sent DST: Daylight Saving Time not in use (i.e. “winter time” See Note
9			Mobile terminated establishment of Radio Resource Connection	See TS 34.108 clause 7.1.2 "Initial UE identity" = TMSI1. Establishment Cause: Terminating Conversation Call.
10			PAGING RESPONSE	"Mobile identity" =TMSI1
11			AUTHENTICATION REQUEST
12			AUTHENTICATION RESPONSE
13	SS			The SS starts CS domain integrity protection.
14	<-		MM INFORMATION	Full Name for Network, Short Name for Network, Local Time Zone and DST IE are included: “NITZ MM PLMN” for Full Name “MM PLMN” for Short Name “+ 2 hours” for Timezone (including DST) “+ 1 hour” for DST See specific message content
15	SS			The SS releases the RRC connection
16				Operator Action: Verify that the names and time are stored and handled correctly according to specific PICS Statements: “NITZ MM PLMN” for Full name, “MM PLMN” for Short name The use of the supported Fields is checked: Universal Time: Year: < Current Year > Month: December Day: 31^st Hour: 6 Hours Minute: 15 Minutes Timezone: GMT+2 Local Time Zone: Timezone: GMT+2 (including DST) DST: Daylight Saving Time in use (i.e. “summer time”) See Note
17	SS			Set the cell type of cell B to the "Serving cell". Set the cell type of cell A to the "Suitable neighbour cell". The following messages are sent and shall be received on cell B
18	->		ROUTING AREA UPDATING REQUEST	P-TMSI-2 signature Routing area identity = RAI-1
19	SS			The SS starts integrity protection.
20	<-		ROUTING AREA UPDATING ACCEPT	Update result = Update type in step 18 Mobile identity = P-TMSI-1 P-TMSI-1 signature Routing area identity = RAI-4
21	->		ROUTING AREA UPDATING COMPLETE
22	<-		GMM INFORMATION	Full Name for Network and Short Name for Network IE are included: “NITZ GMM PLMN” for Full Name “GMM PLMN” for Short Name See specific message content
23	SS			The SS releases the RRC connection
24	UE			Operator Action: Verify that the names and time are stored and handled correctly according to specific PICS Statements: “NITZ GMM PLMN” for Full name, “GMM PLMN” for Short name if possible, verify that no change is done on the time information
Note: In step 8, 16 and 24 the “minute” is not so relevant and can be higher than “15” depending on operator’s action time. The check of Timezone and DST is done implicitly by checking the time only in case UE does not support the display of these two fields. Current Year is derived by the SS. In steps 9-16 Local Time Zone Information is included only if the UE supports pc_LocalTimeZone. In Steps 8, 16 Local Time Zone is checked. DST is to be checked only if the UE supports pc_DaylightSavingTime.

Specific message contents:

GMM Information, Step 6:

Information element	Value/remark
Full Name IE	43
Length	0D (13 octets)
Ext	1 x x x x x x x (Spare Bit)
Coding scheme	x 0 0 0 x x x x (Cell Broadcast data coding scheme, GSM default alphabet, language unspecified)
Add CI	x x x x 0 x x x (Initials Country not included)
Spare Bit in final Octet	x x x x x 1 0 1 (Bit 4 to 8 of last Octet are set to ‘0’)
Text String	CE 24 55 0B 3A 36 9B 20 28 B3 E9 04
	(“NITZ GMM PLMN“)
Short Name IE	45
Length	08 (8 octets)
Ext	1 x x x x x x x (Spare Bit)
Coding scheme	x 0 0 0 x x x x (Cell Broadcast data coding scheme, GSM default alphabet, language unspecified)
Add CI	x x x x 0 x x x (Initials Country not included)
Spare Bit in final Octet	x x x x x 0 0 0 (“no information about the number of spare bits in last octet”)
Text String	C7 66 13 04 65 36 9D (“GMM PLMN“)
Universal Time IE	47
Year	< Current Year >
Month	21 – December
Day	13 – 31
Hour	40 – 4 hours
Minute	51 – 15 Minutes
Second	00 – 0 second
Time Zone	40 – GMT+1 (415 minutes+ 015 minutes DST)
Note:The bit values of x

MM Information, Step 14:

Information element	Value/remark
Full Name IE	43
Length	0C (12 octets)
Ext	1 x x x x x x x (Spare Bit)
Coding scheme	x 0 0 0 x x x x (Cell Broadcast data coding scheme, GSM default alphabet, language unspecified)
Add CI	x x x x 0 x x x (Initials Country not included)
Spare Bit in final Octet	x x x x x 1 0 0 (Bit 5 to 8 of last Octet are set to ‘0’)
Text String	CE 24 55 0B 6A 36 41 50 66 D3 09
	(“NITZ MM PLMN“)
Short Name IE	45
Length	08 (8 octets)
Ext	1 x x x x x x x (Spare Bit)
Coding scheme	x 0 0 0 x x x x (Cell Broadcast data coding scheme, GSM default alphabet, language unspecified)
Add CI	x x x x 0 x x x (Initials Country not included)
Spare Bit in final Octet	x x x x x 1 1 1 (Bit 2 to 8 of last Octet are set to ‘0’)
Text String	CD 26 08 CA 6C 3A 01 (“MM PLMN“)
Local Time Zone IE	46
Time Zone	80 – GMT+1+1(415 minutes+ 415 minutes DST)
Daylight Saving Time IE	49
Length of DST Content	1
Value	1 – + 1 hour (summer time)

GMM Information, Step 22:

Information element	Value/remark
Full Name IE	43
Length	0D (13 octets)
Ext	1 x x x x x x x (Spare Bit)
Coding scheme	x 0 0 0 x x x x (Cell Broadcast data coding scheme, GSM default alphabet, language unspecified)
Add CI	x x x x 0 x x x (Initials Country not included)
Spare Bit in final Octet	x x x x x 1 0 1 (Bit 4 to 8 of last Octet are set to ‘0’)
Text String	CE 24 55 0B 3A 36 9B 20 28 B3 E9 04
	(“NITZ GMM PLMN“)
Short Name IE	45
Length	08 (8 octets)
Ext	1 x x x x x x x (Spare Bit)
Coding scheme	x 0 0 0 x x x x (Cell Broadcast data coding scheme, GSM default alphabet, language unspecified)
Add CI	x x x x 0 x x x (Initials Country not included)
Spare Bit in final Octet	x x x x x 0 0 0 (“no information about the number of spare bits in last octet”)
Text String	C7 66 13 04 65 36 9D (“GMM PLMN“)

12.2.1.15.5 Test requirements

In step 8, 16 and 24 the UE populates the supported fields with the correct received values.

12.2.1.16 PS attach / EAB active

12.2.1.16.1 Definition

Test to verify that the UE does not perform PS attach if the network broadcast EAB and EAB is enabled in the UE.

12.2.1.16.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.2.1.16.3 Test purpose

To verify that the UE does not perform PS attach if the network broadcast EAB and EAB is enabled in the UE

12.2.1.16.4 Method of test

Initial conditions:

– System Simulator:

– One cell operating in network operation mode II.

– The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE to prevent repeated CS domain registration and/or IMSI Detach by UEs in operation mode A).

– User Equipment:

– The UE has a valid IMSI.

– The UE has been registered in the CS domain (In case of UE Operation Mode A).

– 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.2.1.16–1.

Table 12.2.1.16-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

The SS indicates access class x barred in EAB information.

The UE is powered up or switched on.

UE will not initiate a PS attach procedure.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	SS			SS set class x barred in EAB information. SS transmits system information, with IE "EAB Parameters For All" in SIB21. SIB_REP of SIB21 is 5.12s and access class x is present in IE “common EAB information”.
2	UE		Void
3	UE			The UE is powered up or switched on.
4	UE			The UE shall not initiate a PS attach procedure as access class x is barred. (SS waits 30 seconds).
5	SS			SS modifies system information and stops transmitting SYSTEM INFORMATION BLOCK TYPE 21.
6	UE			The UE shall transmit a RRC CONNECTION REQUEST message to initiate a PS attach procedure. And the RRC Connection is established.
7	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
8	<-		AUTHENTICATION AND CIPHERING REQUEST
9	->		AUTHENTICATION AND CIPHERING RESPONSE
10	SS			The SS starts integrity protection.
11	<-		ATTACH ACCEPT
12	->		ATTACH COMPLETE
13	SS			The SS releases the RRC connection.

Specific message contents

None.

12.2.1.16.5 Test requirement

At step 4, The UE shall not initiate a PS attach procedure as access class x is barred in EAB information.

At step 6, The UE shall transmit a RRC CONNECTION REQUESTmessage on cell B to initiate a PS attach procedure.