12.9 Service Request procedure (UMTS Only)

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

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

12.9.1 Service Request Initiated by UE Procedure

12.9.1.1 Definition

12.9.1.2 Conformance requirement

UE shall send the Service Request message to the network in order to establish the PS signalling connection for the upper layer signalling or for the resource reservation for active PDP context(s).

Reference

TS 24.008 clauses 4.7.13

TS 23.060 clauses 6.12.1

12.9.1.3 Test purpose

To test the behaviour of the UE if the UE initiates the CM layer service (e.g. SM or SMS) procedure.

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

Test procedure

a) The UE in PMM-IDLE state sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for the upper layer signalling.

b) After the SS receives the SERVICE REQUEST message, the SS sends a SERVICE REJECT message.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set to attach to PS services only (see ICS). If that is not supported by the UE, goto step 12.
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 ciphering and integrity protection.
4	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-1
5	->		ATTACH COMPLETE
5a	SS			The SS releases the RRC connection.
6	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
6a	SS			The IE "Establishment cause" in the received RRC CONNECTION REQUEST message is not checked.
7	->		SERVICE REQUEST	Service type = "signalling",
8	<-		SERVICE REJECT	Reject cause = "GPRS services not allowed"
9	->		Void
9a	SS			The SS releases the RRC connection.
10	UE			The UE is switched off or power is removed (see ICS).
10a			Void
11			Void
11a			Void
12	UE			The UE is set to attach to both PS and non-PS services (see ICS) and the test is repeated from step 2 to step 11a.

Specific message contents

None.

12.9.1.5 Test requirements

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

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

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

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

At step7, when the UE has any signalling message (e.g. for SM or SMS) that requires security protection, the UE shall:

– send the SERVICE REQUEST message with service type indicated "signalling".

12.9.2 Service Request Initiated by Network Procedure

12.9.2.1 Definition

12.9.2.2 Conformance requirement

When the UE receives a paging request for PS domain from the network in PMM-IDLE mode, the UE shall send the SERVICE REQUEST message to the network.

Reference

TS 24.008 clauses 4.7.13

TS 23.060 clauses 6.12.2

12.9.2.3 Test purpose

To test the behaviour of the UE if the UE receives the paging request for PS domain service from the network.

12.9.2.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode II.

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

Test procedure

a) The UE is in PMM-IDLE state. The SS pages the UE by sending a Paging message to the UE.

b) The UE sends a SERVICE REQUEST message to the SS. Service Type specifies Paging Response. The Service Request is carried over the radio in an RRC Direct Transfer message.

c) After the SS receives the SERVICE REQUEST message from the UE, SS initiates an authentication procedure.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			The UE is set to attach to PS services only (see ICS). If that is not supported by the UE, goto step 12.
2	UE			The UE is powered up or switched in 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 ciphering and integrity protection.
4	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-1
5	->		ATTACH COMPLETE
5a	SS			The SS releases the RRC connection.
6	<-		PAGING TYPE1	Mobile identity = P-TMSI-1 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"
8	<-		AUTHENTICATION AND CIPHERING REQUEST
9	->		AUTHENTICATION AND CIPHERING RESPONSE
9a	SS			SS starts integrity protection and releases the RRC connection.
10	UE			The UE is switched off or power is removed (see ICS).
10a	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).
11	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRSdetach’
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	UE			The UE is set to attach to both PS and non-PS services (see ICS) and the test is repeated from step 2 to step 11a.

Specific message contents

None.

12.9.2.5 Test requirements

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

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

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

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

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

At step 7, when the UE receives a paging request for PS domain from the network in PMM-IDLE mode, the UE shall:

– send the SERVICE REQUEST message with service type indicated "paging response".

12.9.3 Service Request / rejected / Illegal MS

12.9.3.1 Definition

12.9.3.2 Conformance requirement

If the network rejects a service request procedure from the UE with the cause "Illegal MS", the UE shall:

1) set the GPRS update status to GU3 ROAMING NOT ALLOWED and enter state GMM DEREGISTRATED. A UE operating in MS operation A shall in addition to set the update status to U3 ROAMING NOT ALLOWED.

2) delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. A UE operating in MS operation A shall in addition delete any TMSI, LAI and ciphering key sequence number.

3) consider the USIM as invalid for PS service until switched off or the USIM is removed.

Reference

TS 24.008 clauses 4.7.13.4

12.9.3.3 Test purpose

To test the behaviour of the UE if the network rejects the service request procedure with the cause "Illegal MS".

12.9.3.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, RAI-1 and IMSI.

The UE has been registered in the CS domain.

Related ICS/IXIT statements

Support of PS service Yes/No

UE operation mode A Yes/No
UE operation mode C Yes/No

USIM removal possible without powering down Yes/No

Switch off on button Yes/No

Test procedure

a) The UE sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for the upper layer signalling.

b) After the SS receiving the SERVICE REQUEST message, the SS sends a SERVICE REJECT message with the cause value #3(Illegal MS).

c) After the UE receives the SERVICE REJECT message with the cause value #3(Illegal MS), the UE deletes any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.

d) The SS checks that the UE does not initiate an upper-layer signalling until the power of the UE is switched off.

e) The SS checks that the UE does not initiate an upper-layer signalling until the USIM is removed from the UE.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following message 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 is not supported, go to step 38.
2	SS			The SS is set in network operation mode II and activates cell 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	SS			The SS verifies 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 ciphering and integrity protection.
5	<-		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’
6	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
7	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
8	->		SERVICE REQUEST	Service type = "signalling"
9	<-		SERVICE REJECT	Reject cause = "Illegal MS"
9a	SS			The SS releases the RRC connection
10	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
11	SS			The SS verifies that the UE does not attempt to access the network. (SS waits 30 seconds)
12	UE			The UE is switched off.
13			Void
14	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
14a	UE		Registration on CS	See TS 34.108 This is applicable only for UE in UE operation mode A.
14b	SS			The SS verifies 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
15a	<-		AUTHENTICATION AND CIPHERING REQUEST
15b	->		AUTHENTICATION AND CIPHERING RESPONSE
15c	SS			The SS starts ciphering and integrity protection.
16	<-		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
17	->		ATTACH COMPLETE
17a	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
18	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
19	->		SERVICE REQUEST	Service type = "signalling"
20	<-		SERVICE REJECT	Reject cause = "Illegal MS"
20a	SS			The SS releases the RRC connection
21	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
22	SS			The SS verifies that the UE does not attempt to access the network. (SS waits 30 seconds)
23	UE			If possible (see ICS) USIM replacement is performed. Otherwise if possible (see ICS) switch / power off is performed. The UE is then powered up or switched on (see ICS).
24	UE		Registration on CS	See TS 34.108 This is applicable only for UE in UE operation mode A.
25	UE			The UE initiates a PS attach, by MMI or by AT command.
25a	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
26	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
26a	<-		AUTHENTICATION AND CIPHERING REQUEST
26b	->		AUTHENTICATION AND CIPHERING RESPONSE
26c	SS			The SS starts ciphering and integrity protection.
27	<-		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
28	->		ATTACH COMPLETE
28a	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
29	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
30	->		SERVICE REQUEST	Service type = "signalling"
31	<-		SERVICE REJECT	Reject cause = "Illegal MS"
32			VOID
33			VOID
34	SS			The SS releases RRC connection.
35	UE			The UE is switched off or power is removed (see ICS).
36			Void
37			Void
38	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 37.

Specific message contents

None.

12.9.3.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 step11, when the UE receives the SERVICE REJECT message with cause "Illegal MS" UE shall:

not attempt to access the network.

At step15, 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 step22, when the UE receives the SERVICE REJECT message with cause "Illegal MS" UE shall:

not attempt to access the network.

At step26, when the UE gets the USIM replaced, is powered up or switched on, UE shall:

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

At step30, UE shall:

– initiate the service request procedure.

12.9.4 Service Request / rejected / PS services not allowed

12.9.41 Definition

12.9.4.2 Conformance requirement

If the network rejects a service request procedure from the UE with the cause "GPRS services not allowed", the UE shall:

1) set the GPRS update state to GU3 ROAMING NOT ALLOWED.

2) delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.

3) consider the USIM as invalid for PS service until the UE is switched off or until the USIM is removed.

Reference

TS 24.008 clauses 4.7.13.4

12.9.4.3 Test purpose

To test the behaviour of the UE if the network rejects the service request procedure with the cause "GPRS services not allowed in this PLMN".

12.9.4.4 Method of test

Initial condition

System Simulator:

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
UE operation mode C Yes/No

Switch off on button Yes/No

Test procedure

a) The UE sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for the upper layer signalling.

b) After the SS receiving the SERVICE REQUEST message, the SS sends a SERVICE REJECT message with the cause value #7(GPRS services not allowed).

c) After the UE receives the SERVICE REJECT message with the cause value #7(GPRS services not allowed), the UE deletes any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.

d) The SS checks that the UE does not initiate an upper-layer signalling until the UE is switched off.

e) The SS checks that the UE does not initiate an upper-layer signalling until the USIM is removed from the UE.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following message 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 is not supported, go to step 38.
2	SS			The SS is set in network operation mode II and activates cell 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	SS			The SS verifies 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 ciphering and integrity protection.
5	<-		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’
6	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
7	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
8	->		SERVICE REQUEST	Service type = "signalling"
9	<-		SERVICE REJECT	Reject cause = "GPRS services not allowed"
9a	SS			The SS releases the RRC connection
10	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
11	SS			The SS verifies that the UE does not attempt to access the network. (SS wait 30seconds)
12	UE			The UE is switched off.
13			Void
14	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
14a	SS			The SS verifies 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
15a	<-		AUTHENTICATION AND CIPHERING REQUEST
15b	->		AUTHENTICATION AND CIPHERING RESPONSE
15c	SS			The SS starts ciphering and integrity protection.
16	<-		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
17	->		ATTACH COMPLETE
17a	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
18	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
19	->		SERVICE REQUEST	Service type = "signalling"
20	<-		SERVICE REJECT	Reject cause = "GPRS services not allowed"
20a	SS			The SS releases the RRC connection
21	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
22	SS			The SS verifies that the UE does not attempt to access the network. (SS wait 30seconds)
23	UE			The UE gets the USIM replaced, is powered up or switched on.
24			Void
25	UE			The UE initiates a PS attach, by MMI or by AT command.
25a	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
26	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = IMSI
26a	<-		AUTHENTICATION AND CIPHERING REQUEST
26b	->		AUTHENTICATION AND CIPHERING RESPONSE
26c	SS			The SS starts ciphering and integrity protection.
27	<-		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
28	->		ATTACH COMPLETE
28a	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
29	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
30	->		SERVICE REQUEST	Service type = "signalling"
31	<-		SERVICE REJECT	Reject cause = "GPRS services not allowed"
32			VOID
33			VOID
34	SS			The SS releases RRC connection.
35	UE			The UE is switched off or power is removed (see ICS).
36			Void
37			Void
38	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 37.

Specific message contents

12.9.4.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 step11, when the UE receives the SERVICE REJECT message with cause "GPRS services not allowed" UE shall:

not attempt to access the network.

At step15, 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 step22, when the UE receives the SERVICE REJECT message with cause "GPRS services not allowed" UE shall:

not attempt to access the network.

At step26, when the UE gets the USIM replaced, is powered up or switched on, UE shall:

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

At step30, UE shall:

– initiate the service request procedure.

12.9.5 Service Request / rejected / MS identity cannot be derived by the network

12.9.5.1 Definition

12.9.5.2 Conformance requirement

If the network rejects a service request procedure from the UE with the cause "MS identity cannot be derived by the network", the UE shall:

1) set the GPRS update states to GU2 NOT UPDATED.

2) delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number.

3) initiate the PS attach procedure automatically.

Reference

TS 24.008 clauses 4.7.13.4

12.9.5.3 Test purpose

To test the behaviour of the UE if the network rejects the service request procedure with the cause "MS identity cannot be derived by the network".

12.9.5.4 Method of test

Initial condition

System Simulator:

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
UE operation mode C Yes/No

Switch off on button Yes/No

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

Test procedure

a) The UE sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for the upper layer signalling.

b) After the SS receiving the SERVICE REQUEST message, the SS sends a SERVICE REJECT message with the cause value #9 (MS identity cannot be derived by the network).

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following message 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 is not supported, go to step 23.
2	SS			The SS is set in network operation mode II and activates cell 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	SS			The SS verifies 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 ciphering and integrity protection.
5	<-		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’
6	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
7	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
8	->		SERVICE REQUEST	Service type = "signalling"
9	<-		SERVICE REJECT	Reject cause = "MS identity cannot be derived by the network"
9a	SS			The SS releases the RRC connection
10	UE			The UE automatically initiates the PS attach procedure.
10a	SS			The SS verifies 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 ciphering and integrity protection.
12	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature
13	->		ATTACH COMPLETE
13a	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
14	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
15	->		SERVICE REQUEST	Service type = "signalling"
16	<-		SERVICE REJECT	Reject cause = “GPRS services not allowed”
17			VOID
18			VOID	.
19	SS			The SS releases RRC connection.
20	UE			The UE is switched off or power is removed (see ICS).
21			Void
22			Void
23	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 22.

Specific message contents

None.

12.9.5.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 step11, when the UE receives the SERVICE REJECT message with cause "MS identity cannot be derived by the network" UE shall:

– initiate PS attach procedure automatically.

12.9.6 Service Request / rejected / PLMN not allowed

12.9.6.1 Definition

12.9.6.2 Conformance requirement

If the network rejects a service request procedure from the UE with the cause "PLMN not allowed", the UE shall:

1) delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number.

2) set the GPRS update status to GU3 ROAMING NOT ALLOWED.

3) store the PLMN identity in the appropriate forbidden list.

Reference

TS 24.008 clauses 4.7.13.4

12.9.6.3 Test purpose

To test the behaviour of the UE if the network rejects the service request procedure with the cause "PLMN not allowed".

12.9.6.4 Method of test

Initial condition

System Simulator:

Two cells (not simultaneously activated), cell A in MCC1/MNC2/LAC1/RAC1 (RAI-8, Not HPLMN), cell B in MCC2/MNC1/LAC1/RAC1 (RAI-2, Not HPLMN).
All two 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-8.

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

Test procedure

a) The UE sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for the upper layer signalling.

b) After the SS receiving the SERVICE REQUEST message, the SS sends a SERVICE REJECT message with the cause value #11 (PLMN not allowed).

c) The SS checks that the UE does not initiate an upper-layer signalling until the UE is switched off.

d) The SS checks that the UE does not answer a Page from the SS until the power of the UE is switched off.

Expected Sequence

Step	Direction			Message		Comments
	UE	SS
						The following message 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 is not supported, go to step 24.
2	SS					The SS is set in network operation mode II. Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Non-Suitable cell". (see note)
3	UE					The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
3a	SS					The SS verifies 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-8
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS					The SS starts ciphering and integrity protection.
5	<-			ATTACH ACCEPT		No new mobile identity assigned. P-TMSI and P-TMSI signature not included. Routing area identity = RAI-8 Attach result = ‘GPRS only attached’
6	SS					UE is moved to PMM idle. (The SS releases the RRC connection)
7	UE					The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
8	->			SERVICE REQUEST		Service type = "signalling"
9	<-			SERVICE REJECT		Reject cause = "PLMN not allowed"
9a	SS					The SS releases the RRC connection
10	UE					The UE stores the PLMN identity in the "forbidden PLMN list".
11	UE					The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
12	SS					The SS verifies that the UE does not attempt to access the network. (SS wait 30second)
13	<-			PAGING TYPE1		Paging order is for PS service
14	UE					No response from the UE to the request. This is checked for 10 seconds.
						The following messages shall be sent and shall be received on cell B.
15	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)
16	UE					Cell B is preferred by the UE.
16a	UE			Registration on CS	See TS 34.108 This is applicable only for UE in UE operation mode A.
17	UE					The UE initiates an attach automatically, by MMI or by AT command.
17a	SS					The SS verifies 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
18a	<-			AUTHENTICATION AND CIPHERING REQUEST
18b	->			AUTHENTICATION AND CIPHERING RESPONSE
18c	SS					The SS starts ciphering and integrity protection.
19	<-			ATTACH ACCEPT		Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-2 Attach result = ‘GPRS only attached’
20	->			ATTACH COMPLETE
21	UE					The UE is switched off or power is removed (see ICS).
22	->			DETACH REQUEST		Message not sent if power is removed. Detach type = ‘power switched off, GPRSdetach’
23	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.
24	UE					The UE is set to attach to both the PS and non-PS services (see ICS) and the test is repeated from step 2 to step 23.
NOTE: The definitions for "Non-Suitable cell" 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.9.6.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, when the UE receives the SERVICE REJECT message with cause "PLMN not allowed", UE shall:

– not perform a PS attach procedure in the same PLMN.

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

– not respond to the paging message for PS domain.

At step18, UE shall:

– perform PS attach procedure.

12.9.7a Service Request / rejected / No PDP context activated

12.9.7a.1 Definition

12.9.7a.2 Conformance requirement

If the network rejects a service request procedure with the cause "No PDP context activated":

– The UE shall deactivate locally all active PDP contexts and the UE shall enter the state GMM-REGISTERED.NORMAL-SERVICE. The UE may also activate PDP context(s) to replace any previously active PDP contexts.

NOTE: In some cases, user interaction may be required and then the UE cannot activate the PDP context(s) automatically.

Reference

TS 24.008 clauses 4.7.13.4

12.9.7a.3 Test purpose

To test the behaviour of the UE if the network rejects the service request procedure with the cause "No PDP context activated".

12.9.7a.4 Method of test

Initial condition

System Simulator:

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
UE operation mode C Yes/No

Switch off on button Yes/No

Method of context activation

Support of automatic PS attach procedure at switch on Yes/No

Test procedure

a) The UE sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for the upper layer signalling.

b) After the SS receiving the SERVICE REQUEST message, the SS sends a SERVICE REJECT message with the cause value #40 (No PDP context activated).

c) After the UE receives the SERVICE REJECT message, the UE shall deactivate locally all active PDP contexts. The UE may optionally activate PDP context(s) to replace any previously active PDP contexts or the UE in manual mode may perform a detach procedure.

d) If the UE not automatically activates the PDP context (to replace the previously active PDP context) then a PS call is initiated by MMI or by AT command. The UE shall send a SERVICE REQUEST with Service type = "signalling".

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following message are sent and shall be received on cell A.
1				The UE is set in UE operation mode C (see ICS). If UE operation mode C is not supported, go to step 26.
2				The SS is set in network operation mode II and activates cell A.
3				The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4	->		ATTACH REQUEST
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts ciphering and integrity protection.
5	<-		ATTACH ACCEPT
6	->		ATTACH COMPLETE
6a	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
7	UE			The UE initiates a PS call, by MMI or by AT command.
8	->		SERVICE REQUEST	Service type = "signalling"
9	<-		AUTHENTICATION AND CIPHERING REQUEST
10	->		AUTHENTICATION AND CIPHERING RESPONSE
11	SS			The SS initiates a security mode control procedure.
12	UE			After a PS call is established, the UE suspends transmission of the user data.
13	SS			The SS initiates a Radio Bearer release procedure.
14	UE			The UE resumes the transmission of the user data.
15	->		SERVICE REQUEST	Service type = "data"
16	<-		SERVICE REJECT	Reject cause = "No PDP context activated"
17	UE			The UE shall deactivate locally all active PDP contexts. The UE may optionally activate PDP context(s) to replace any previously active PDP contexts or the UE in manual mode may perform a detach procedure.
AA17	->		ACTIVATE PDP CONTEXT REQUEST
AA18	->		ACTIVATE PDP CONTEXT REJECT	SS can reject the activation of PDP context with cause value “#31 activation rejected, unspecified”. The UE in manual mode may perform a detach procedure, in this case step A17 will be followed else step 17a.
A17			DETACH REQUEST	This step is performed only when UE is in manual attach mode: The UE may (optionally) send a Detach Request (only Note 1).
A18			DETACH ACCEPT	This step is performed only when UE is in manual attach mode: SS responds with DETACH ACCEPT message as a Detach Request was transmitted by the UE.
17a	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
A17a				This step is performed only when UE is in manual attach mode: The UE initiates the attach procedure by MMI or AT command (only Note 1). The attach procedure is performed only if steps A17 and A18 have been performed.
18	UE			The UE initiates a PS call, automatically, by MMI or by AT command.
19	->		SERVICE REQUEST	Service type = "signalling"
20	<-		AUTHENTICATION AND CIPHERING REQUEST
21	->		AUTHENTICATION AND CIPHERING RESPONSE
22	SS			SS initiates a security procedure by sending SECURITY MODE COMMAND message.
23	UE			The UE is switched off or power is removed (see ICS).
24	UE			The UE initiates Detach request, by MMI or by AT command.
25	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRSdetach’
26	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.
27	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 25.
Note 1: Support of automatic PS attach procedure at switch on – no

Specific message contents

None.

12.9.7a.5 Test requirements

At step4, when the UE is powered on or switched on, the UE shall initiate the PS attach procedure.

At step15, the UE shall initiates a Service request procedure by sending a SERVICE REQUEST message with Service type = "data".

At step19, the UE shall initiates a Service request procedure by sending a SERVICE REQUEST message with Service type = "signalling".

12.9.7b Service Request / rejected / No Suitable Cells In Location Area

12.9.7b.1 Definition

12.9.7b.2 Conformance requirement

If the network rejects a service request procedure from the UE with the cause "No Suitable Cells In Location Area", the UE shall:

1) set the GPRS update status to GU3 ROAMING NOT ALLOWED and shall change to state GMM-REGISTERED.LIMITED-SERVICE.

2) store the LAI in the list of ‘forbidden location areas for roaming’.

If no RRC connection exists, the UE shall perform the following additional actions immediately. If the UE is operating in operation mode A and an RRC connection exists, the UE shall perform these actions when the RRC connection is subsequently released:

1) if the UE is IMSI attached, the UE shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE.

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

Reference

TS 24.008 clauses 4.7.13.4

12.9.7b.3 Test purpose

To test the behaviour of the UE if the network rejects the service request procedure with the cause "No Suitable Cells In Location Area".

12.9.7b.4 Method of test

Initial condition

System Simulator:

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

All three cells are operating in network operation mode II.

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

User Equipment:

The UE has valid IMSI.

Related ICS/IXIT statements

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

Test procedure

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

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	SS			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) The SS configures power level of each Cell as follows. Cell A > Cell B = Cell C
1	UE			The UE is set in UE operation mode C (see ICS). If UE operation mode C is not supported, goto step 15.
2	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
2a	UE		Registration on CS	See TS 34.108 This is applicable only for UE in UE operation mode A.
2b	SS			The SS verifies 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 ciphering and integrity protection.
4	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature MS identity = TMSI-1 Routing area identity = RAI-1
5	->		ATTACH COMPLETE
6	SS			The SS initiates the RRC connection release.
7	UE			The UE initiates a PS call, by MMI or by AT command.
8	->		SERVICE REQUEST	Service type = ‘signalling’
9	<-		SERVICE REJECT	Reject cause = ‘No Suitable Cells In Location Area’
9a	SS			The SS releases the RRC connection
9aa	SS			Set the cell type of cell B to the "Serving cell". Set the cell type of cell C to the "Serving cell". Set the cell type of cell A to the "Suitable neighbour cell". The following message are sent and shall be received on cell B.
9b	UE		Registration on CS	See TS 34.108 This is applicable only for UE in UE operation mode A.
9c	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
10	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Mobile identity = P-TMSI-1 Old routing area identity = RAI-1 Follow-on request pending = 0 or 1
10a	<-		AUTHENTICATION AND CIPHERING REQUEST
10b	->		AUTHENTICATION AND CIPHERING RESPONSE
10c	SS			The SS starts ciphering and integrity protection.
11	<-		ROUTING AREA UPDATE ACCEPT	Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-3 Update result = ‘RA updated’ Follow-on proceed is set to the opposite value as provided in ROUTING AREA UPDATE REQUEST in step 10.
12	->		ROUTING AREA UPDATE COMPLETE
12a	->		ACTIVATE PDP CONTEXT REQUEST	In case Follow-on request pending is set 1 in step 10, the UE sends an Activate PDP context request.
12b	SS			If the UE transmitted an Activate PDP context request message in step 12a then the SS establishes the RAB.
12c	<-		ACTIVATE PDP CONTEXT ACCEPT	If the UE transmitted an Activate PDP context request message in step 12a then the SS responds with an Activate PDP context accept message
13	UE			The UE is switched off or power is removed (see ICS).
13a			IMSI DETACH INDICATION	Message not sent if power is removed This is applicable only for UE in UE operation mode A.
14	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRSdetach’
14a	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.
15	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 14.
NOTE: The definitions for “Non-Suitable cell”, "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1 in the relevant to the RAT of the cells "Reference Radio Conditions" subclauses.

Specific message contents

None.

12.9.7b.5 Test requirements

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

– perform the routing area updating procedure.

12.9.7c Service Request / rejected / Roaming not allowed in this location area

12.9.7c.1 Definition

12.9.7c.2 Conformance requirement

If the network rejects a service request procedure from the UE with the cause "Roaming not allowed in this location area", the UE shall:

1) set the PS update status to GU3 ROAMING NOT ALLOWED

2) store the LAI in the list of "forbidden location areas for roaming".

3) perform a PLMN selection.

Reference

TS 24.008 clauses 4.7.13.4

12.9.7c.3 Test purpose

To test the behaviour of the UE if the network rejects the service request procedure with the cause "Roaming not allowed in this location area".

12.9.7c.4 Method of test

Initial condition

System Simulator:

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

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

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

Test procedure

The SS rejects a Service request with the cause value ‘Roaming not allowed in this location area’. The SS checks that the UE shall not perform PS attach procedure when the UE enters a different location area.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
	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". Set the cell type of cell C 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 is not supported, go to step 19.
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			The SS verifies 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 ciphering and integrity protection.
5	<-		ATTACH ACCEPT	No new mobile identity assigned. P-TMSI and P-TMSI signature not included. Attach result = ‘GPRS only attached’ Routing area identity = RAI-1
6	SS			The SS initiates the RRC connection release.
7	UE			The UE initiates a PS call, by MMI or by AT command.
8	->		SERVICE REQUEST	Service type = "signalling"
9	<-		SERVICE REJECT	Reject cause = "roaming not allowed in this location area"
9a	SS			The SS releases the RRC connection.
10	UE			The UE performs PLMN selection.
11	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)
12	SS			The SS verifies that the UE does not attempt to access the network. (SS waits 30 seconds).
13	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)
				The following messages are sent and shall be received on cell C.
13a	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
13a.1	UE		Registration on CS	See TS 34.108 This is applied only for UE in UE operation mode A.
14	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Mobile identity = P-TMSI-1 Old routing area identity = RAI-1 Follow-on request pending = 0 or 1
14a	<-		AUTHENTICATION AND CIPHERING REQUEST
14b	->		AUTHENTICATION AND CIPHERING RESPONSE
14c	SS			The SS starts integrity protection.
15	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature MS identity = TMSI-2 Routing area identity = RAI-2 Follow-on proceed is set to the opposite value as provided in ROUTING AREA UPDATE REQUEST in step 14.
16	->		ROUTING AREA UPDATE COMPLETE
16a	->		ACTIVATE PDP CONTEXT REQUEST	In case Follow-on request pending is set 1 in step 14, the UE sends an Activate PDP context request.
16b	SS			If the UE transmitted an Activate PDP context request message in step 16a then the SS establishes the RAB.
16c	<-		ACTIVATE PDP CONTEXT ACCEPT	If the UE transmitted an Activate PDP context request message in step 16a then the SS responds with an Activate PDP context accept message
17	UE			The UE is switched off or power is removed (see ICS).
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 set to attach to both the PS and non-PS services (see ICS) and the test is repeated from step 3 to step 18.
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.9.7c.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 step12, when the UE enters a same location area, UE shall:

– not initiate the PS attach procedure.

At step14, when the UE enters a different location area, UE shall:

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

12.9.7d Service Request / rejected / Not authorized for this CSG

12.9.7d.1 Definition

12.9.7d.2 Conformance requirement

If the network rejects a service request procedure from the UE with the cause " Not authorized for this CSG ":

– The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it ) and shall change to state GMM-REGISTERED.LIMITED-SERVICE.

– The MS shall remove from the list of allowed CSG IDs stored in the MS, the CSG ID of the cell where the MS sent the SERVICE REQUEST message.

– The MS shall start timer T3340.

– The MS shall search for a suitable cell in the same PLMN.

– If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state and EPS update status for the case when the service request procedure is rejected with this cause value.

Reference

3GPP TS 24.008 clause 4.7.13

12.9.7d.3 Test purpose

To test the behaviour of the UE if the network rejects the service request procedure with the cause " Not authorized for this CSG ".

12.9.7d.4 Method of test

Initial conditions:

System Simulator:

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

CSG 2.

Both Cell A and Cell B belong to PLMN1.

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

User Equipment:

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

UE Allowed CSG List contains CSG1 and CSG2.

UE is registered on PLMN1.

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

USIM field	PLMN	CSG ID
EFACSGL	PLMN 1	CSG 1,CSG 2

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

Related ICS/IXIT statements

Support of PS service Yes/No

UE operation mode A Yes/No

UE operation mode C Yes/No

Switch off on button Yes/No

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

Test procedure

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

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following messages are sent and shall be received on cell A.
1	UE			The UE is set in UE operation mode C OR The UE is set in UE operation mode A(see ICS). If UE operation mode C is not supported, goto step 27.
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)
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.
5	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
6	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
7	<-		AUTHENTICATION AND CIPHERING REQUEST
8	->		AUTHENTICATION AND CIPHERING RESPONSE
9	SS			The SS starts integrity protection.
10	<-		ATTACH ACCEPT	Attach result =’Combined GPRS/IMSI attached’ Routing area identity = RAI-1
11	SS			The SS initiates the RRC connection release.
12	UE			The UE initiates a PS call, by MMI or by AT command.
13	->		SERVICE REQUEST	Service type = ‘signalling’
13a	<-		AUTHENTICATION AND CIPHERING REQUEST
13b	->		AUTHENTICATION AND CIPHERING RESPONSE
13c	SS			The SS starts integrity protection.
13d	SS			This is an optional Step applicable only if the UE sends a ACTIVATE PDP Context REQ, otherwise go to Step 14. After reception of Activate PDP Context request SS sends Activate PDP context Reject (with cause 26 (Network failure).
14	<-		SERVICE REJECT	Reject cause = ‘ Not authorized for this CSG ‘
15	SS			The SS releases the RRC connection
16	SS			Set the cell type of cell A to the " Non-suitable cell ". Set the cell type of cell B to the " Serving cell ". The following message are sent and shall be received on cell B.
17	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
18	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’ Old P-TMSI signature=P-TMSI-1 signature Mobile identity = P-TMSI-1 Old routing area identity = RAI-1
19	<-		AUTHENTICATION AND CIPHERING REQUEST
20	->		AUTHENTICATION AND JCIPHERING RESPONSE
21	SS			The SS starts ciphering and integrity protection.
22	<-		ROUTING AREA UPDATE ACCEPT	Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-2 Update result = ‘RA updated’
23	->		ROUTING AREA UPDATE COMPLETE
24	UE			The UE is switched off.(see ICS).
25	UE			The UE initiates Detach request, by MMI or by AT command.
26	->		DETACH REQUEST	Message not sent if power is removed. Detach type = ‘power switched off, GPRSdetach’
27	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.
27a				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
27b				The UE is powered up or switched ON.
27c				SS Checks that the does not initiate a RRC CONNECTION REQ on Cell A
28	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 25.
NOTE: The definitions for "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.9.7d.5 Test requirements

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 step14, when the UE receives SERVICE REJECT, UE shall:

– delete the CSG1 in the CSG List.

– UE Allowed CSG List shall contain only CSG2.

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

– perform the routing area updating procedure.

12.9.8 Service Request / Abnormal cases / Access barred due to access class control

12.9.8.1 Definition

12.9.8.2 Conformance requirement

If the UE access class X is barred, the UE shall:

1) not start Service Request procedure.

2) stay in the current serving cell.

3) apply normal cell reselection process.

If the UE access class X is granted or serving cell is changed, the UE may:

1) start Service Request procedure.

Reference

TS 24.008 clauses 4.7.13.5.

12.9.8.3 Test purpose

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

12.9.8.4 Method of test

Initial condition

A random access class X (0-15) is selected. The USIM is programmed with this access class X.

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

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 initiates access class X barred. A service request procedure is not performed.

The SS initiates that access class X is not barred. A service request procedure is performed.

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 is not supported, go to step 15.
1a	UE			The UE is powered up or switched on and attempt to initiate an ATTACH. (see ICS)
2			Void
3			Void
4			Void
4a	SS			The SS verifies 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
5a	<-		AUTHENTICATION AND CIPHERING REQUEST
5b	->		AUTHENTICATION AND CIPHERING RESPONSE
5c	SS			The SS starts ciphering and integrity protection.
6	<-		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
7	->		ATTACH COMPLETE
7a	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
7b	SS			The access class x is barred in cell A
8	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
8a	UE			No SERVICE REQUEST sent to SS, as access class x is barred. SS waits 30 seconds
8b	SS			The access class x is not barred any more
8c	UE			In manual attach mode UE may send a Detach Request (Note 1). If the SS receives a Detach Request the test execution continues from step 14.
8d	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
9	->		SERVICE REQUEST	Service Type = "signalling".
10	<-		SERVICE REJECT	GMM cause = ‘GPRS services not allowed’
11			VOID
11a	SS			The SS releases the RRC connection.
12	UE			The UE is switched off or power is removed (see ICS).
13			Void
14			Void
15	UE			The UE is set to attach to both the PS and non-PS services (see ICS) and the test is repeated from step 1a to step 12.
Note 1: Support of automatic PS attach procedure at switch on – no

Specific message contents

None.

12.9.8.5 Test requirements

At step 8a, when the UE access class x is barred, UE shall:

– not perform Service Request procedure.

At step9, UE shall:

– perform Service Request procedure.

12.9.9 Service Request / Abnormal cases / Routing area update procedure is triggered

12.9.9.1 Definition

12.9.9.2 Conformance requirement

If a cell change into a new routing area occurs and the necessity of routing area update procedure is determined before the security mode control procedure is completed, the UE shall:

– abort Service request procedure.

– start routing area update procedure immediately.

Reference

TS 24.008 clause 4.7.13.5

12.9.9.3 Test purpose

To test the behaviour of the UE in case of collision between Routing area update procedure and Service request procedure.

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

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 A Yes/No
UE operation mode C Yes/No

Switch off on button Yes/No

Test procedure

a) The UE sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for the upper layer signalling in cell A.

b) The SS conveys change of routing area code to the UE.

c) The UE aborts Service request procedure and performs Routing area updating procedure.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following messages are sent and shall be received on cell A.
1	UE			The UE is set in UE operation mode C (see ICS). If UE operation mode C is not supported, go to step 22.
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.
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 ciphering and integrity protection.
5	<-		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’
5a			Void
6	SS			UE is moved to PMM Idle. The SS releases the RRC connection.
6a	UE			The UE initiates upper-layer signalling, e.g., Activate PDP Context request, by MMI or by AT command.
7	->		SERVICE REQUEST	Service type = "signalling"
8	<-		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
8a	->		UTRAN MOBILITY INFORMATION CONFIRM
9	UE			The UE aborts Service request procedure.

10	->		ROUTING AREA UPDATE REQUEST	Update type = ‘RA updating’
10a			AUTHENTICATION AND CIPHERING REQUEST
10b			AUTHENTICATION AND CIPHERING RESPONSE
10c	SS			The SS starts ciphering and integrity protection.
11	<-		ROUTING AREA UPDATE ACCEPT	Update result = ‘RA updated’ Allocated P-TMSI = P-TMSI-1 P-TMSI Signature = P-TMSI-1 signature Routing area identity = RAI-4
12	->		ROUTING AREA UPDATE COMPLETE
12a				If the UE initiates a PDP Context, this is rejected and if the UE is in manual GPRS Attach Mode, the UE may perform a detach procedure at this point. If the UE initiates a Service Request, this is rejected with reject cause of 07 – “GPRS Services not Allowed”.
13			Void
14			Void
15			Void
16			Void
17			Void
18			Void
19	UE			The UE is switched off or power is removed (see ICS).
20	->		DETACH REQUEST	Message not sent if power is removed or if the UE in manual GPRS Attach Mode has already detached. Detach type = ‘power switched off, GPRSdetach’
21	SS			The SS releases the RRC connection. If no RRC CONNECTION RELEASE COMPLETE message has been received within 1 second then the SS shall consider the UE as switched off.
22	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 21.
NOTE: The definitions for "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 8)

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.9.9.5 Test requirements

At step 4, the UE shall send an ATTACH REQUEST message

At step 7, the UE shall send a SERVICE REQUEST message with Service type = "signalling".

At step 8, as the UE has received a new RAI in the UTRAN MOBILITY INFORMATION message before the SERVICE ACCEPT message or the SERVICE REJECT message is received, the UE shall abort service request procedure.

At step 10, the UE shall send a ROUTING AREA UPDATE REQUEST message.

12.9.10 Service Request / Abnormal cases / Power off

12.9.10.1 Definition

12.9.10.2 Conformance requirement

When the UE in GMM-SERVICE-REQUEST-INITIATED state is switched off, UE shall:

– perform PS detach procedure.

Reference

TS 24.008 clauses 4.7.13.5

12.9.10.3 Test purpose

To test the behaviour of the UE in case of collision between Service request procedure and "powered off".

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

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

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following message 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 is not supported, go to step 11.
2	SS			The SS is set in network operation mode II and activates cell A.
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts ciphering and integrity protection.
5	<-		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’
6	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
7	->		SERVICE REQUEST	Service type = "signalling"
8	UE			The UE is powered off and initiates a PS detach (with power off) by MMI or by AT command.
9	->		DETACH REQUEST	Detach type = ‘power switched off, GPRSdetach’
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 set to attach to both the PS and non-PS services (see ICS) and the test is repeated from step 2 to step 10.

Specific message contents

None.

12.9.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 step7, UE shall:

– perform the service request procedure

At step9, when the UE is switched off during the Service Request procedure, UE shall;

– abort the Service request procedure.

– perform the PS detach procedure.

12.9.11 Service Request / Abnormal cases / Service request procedure collision

12.9.11.1 Definition

12.9.11.2 Conformance requirement

Abnormal cases in the MS

The following abnormal cases can be identified:

– Procedure collision

If the MS receives a DETACH REQUEST message from the network in state GMM-SERVICE-REQUEST-INITIATED, the GPRS detach procedure shall be progressed and the Service request procedure shall be aborted. If the cause IE, in the DETACH REQUEST message, indicated a "reattach request", the GPRS attach procedure shall be performed.

Reference

TS 24.008 clauses 4.7.13.5

12.9.11.3 Test purpose

To test the behaviour of the UE in case of collision between Service request procedure and PS detach procedure.

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

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

a) The UE sends a SERVICE REQUEST message to the SS in order to establish the PS signalling connection for the upper layer signalling.

b) The SS does not respond to the SERVICE REQUEST for data. Instead it sends a DETACH REQUEST message to the UE, with the Detach type IE set to value "re-attach required".

c) After the UE receives the DETACH REQUEST message, the repeats the attach procedure.

d) The UE is switched off or power is removed. If the UE is switched off it sends a DETACH REQUEST.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
				The following message 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 is not supported, go to step 17.
2	SS			The SS is set in network operation mode II and activates cell A.
3	UE			The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.
4	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
4a	<-		AUTHENTICATION AND CIPHERING REQUEST
4b	->		AUTHENTICATION AND CIPHERING RESPONSE
4c	SS			The SS starts ciphering and integrity protection.
5	<-		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’
6	SS			UE is moved to PMM idle. (The SS releases the RRC connection)
7a	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
7b	->		SERVICE REQUEST	Service type ="signalling"
7c	SS			The SS starts ciphering and integrity protection.
7d	SS			The SS initiates a Radio Bearer release procedure.
7e	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
8	->		SERVICE REQUEST	Service type = "data"
9	SS			The SS does not respond to SERVICE REQUEST message.
10	<-		DETACH REQUEST	Detach type = "re-attach required"
10a	->		DETACH ACCEPT
11	->		ATTACH REQUEST	Attach type = ‘GPRS attach’ Mobile identity = P-TMSI-1 Old Routing area identity = RAI-1
11a	<-		AUTHENTICATION AND CIPHERING REQUEST
11b	->		AUTHENTICATION AND CIPHERING RESPONSE
11c	SS			The SS starts ciphering and integrity protection.
12	<-		ATTACH ACCEPT	Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1 Attach result = ‘GPRS only attached’
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, GPRSdetach’
16	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.
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.9.11.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 step11, when the UE receives a DETACH REQUEST message from the network before the Service request procedure completes, UE shall;

– repeat the attach procedure.

retry the Service request procedure

At step 19 if the UE is switched off, UE shall:

– perform the PS detach procedure.

12.9.12 Service Request / RAB re-establishment / UE initiated / Single PDP context

12.9.12.1 Definition

12.9.12.2 Conformance requirement

The following procedures shall be performed in the MS when radio coverage is lost:

– For a PDP context using background or interactive traffic class, the PDP context is preserved even if RRC re-establishment procedures have failed.

– For a PDP context using streaming or conversational traffic class, the PDP context is preserved, but the maximum bit rate is downgraded to 0 kbit/s (for both uplink and downlink) when the RRC re-establishment procedure has failed. After coverage is regained and if the MS did not deactivate the PDP Context locally the MS should start MS-initiated PDP Context Modification procedure or the PDP Context Deactivation procedure. The MS shall use the PDP Context Modification procedure to re-activate the PDP context and re-establish the RAB.

The following procedures shall be performed in the MS when the RRC layer indicate to higher layer that a RAB has been released and the RAB release was not initiated due to a PDP Context Deactivation Procedure:

– For a PDP context using background or interactive traffic class, the PDP context is be preserved with no modifications.

– For a PDP context using streaming or conversational traffic class, the PDP context is preserved, but the maximum bit rate is downgraded to 0 kbit/s (for both uplink and downlink).

At this point or at a later stage, the MS may start a PDP Context Deactivation procedure or PDP Context Modification procedure. The MS shall use the PDP Context Modification procedure to re-activate the PDP context and re-establish the RAB.

The procedure for re-establishment of RABs allows the SGSN to re-establish RABs for active PDP contexts that don’t have an associated RAB.

The MS initiates the re-establishment of RABs by using the Service Request (Service Type = Data) message.

The criteria to invoke the Service request procedure are when;

b) the MS, either in PMM-IDLE or PMM-CONNECTED mode, has pending user data to be sent and no radio access bearer is established for the corresponding PDP context. The procedure is initiated by an indication from the lower layers (see 3GPP TS 24.007). In this case, the service type shall be set to "data".

After completion of a Service request procedure, the pending service is resumed and uses then the connection established by the procedure. If the service type is indicating "data", then the radio access bearers for all activated PDP contexts are re-established by the network, except for those activated PDP contexts having maximum bit rate value set to 0 kbit/s for both uplink and downlink. The re-establishment of radio access bearers for those PDP contexts is specified in subclause 6.1.3.3 of 3GPP TS 24.008.

Reference

TS 23.060 clause 9.2.3.4-5, 9.2.5.2

TS 24.008 clause 4.7.13

12.9.12.3 Test purpose

To verify that the UE initiates a Service request procedure due to uplink data transmission with one preserved PDP context with traffic class "Background class" after normal RRC connection release as well as when radio coverage is lost.

To verify that the radio access bearer can be re-established for the preserved PDP context, initiated by the UE.

12.9.12.4 Method of test

Initial condition

System Simulator:

One cell, default parameters.

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 is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Related ICS/IXIT statements

Support of PS service Yes/No

Test procedure

a) A PDP context with traffic class "Background class" is activated including the radio access bearer.

b) The SS releases the RRC connection, but keeps the PDP context.

c) Due to transmission of uplink data, the UE initiates an RRC connection establishment and sends a SERVICE REQUEST.

d) The SS performs security mode control procedure and establishes the RAB for the active PDP context using a Radio bearer establishment procedure and the same QoS as previously, without the need for PDP context modification.

e) The SS configured the cell as a non-suitable "Off" cell for 4 minutes, making the UE to release the RAB and enter idle mode due to that radio coverage is lost.

f) The SS configures the cell as a serving cell.

g) Due to transmission of uplink data, the UE initiates an RRC connection establishment and sends a SERVICE REQUEST.

h) The SS performs security mode control procedure and establishes the RAB for the active PDP context using a Radio bearer establishment procedure and the same QoS as previously, without the need for PDP context modification.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a PDP context activation
2			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context with traffic class "Background class"
3	SS			The SS starts ciphering and integrity protection and establishes the radio access bearer.
4			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context
5	SS			The SS releases the RRC connection
6	UE			The UE initiates transmission of uplink data, by MMI or by AT command.
7	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Originating Background Call".
8			SERVICE REQUEST	Service type = "data"
9	SS			The SS starts ciphering and integrity protection.
10	SS			The SS establishes the radio access bearer for the active PDP context, using the same QoS that was used at activation.
11	SS			The SS configures the cell as a non-suitable "Off" cell and waits for 4 minutes, making the UE to release the RAB and enter idle mode.
12	SS			The SS configures the cell as a serving cell.
13	UE			The UE initiates transmission of uplink data, by MMI or by AT command.
14	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Originating Background Call".
15			SERVICE REQUEST	Service type = "data"
16	SS			The SS starts ciphering and integrity protection.
17	SS			The SS establishes the radio access bearer for the active PDP context, using the same QoS that was used at activation.

Specific message contents

None.

12.9.12.5 Test requirements

After steps 7 and 14, UE shall:

– transmit a SERVICE REQUEST message with service type "data"

12.9.13 Service Request / RAB re-establishment / UE initiated / multiple PDP contexts

12.9.13.1 Definition

12.9.13.2 Conformance requirement

– For a PDP context using background or interactive traffic class, the PDP context is be preserved with no modifications.

– For a PDP context using streaming or conversational traffic class, the PDP context is preserved, but the maximum bit rate is downgraded to 0 kbit/s (for both uplink and downlink).

The procedure for re-establishment of RABs allows the SGSN to re-establish RABs for active PDP contexts that don’t have an associated RAB.

The MS initiates the re-establishment of RABs by using the Service Request (Service Type = Data) message.

The criteria to invoke the Service request procedure are when;

Reference

TS 23.060 clause 9.2.3.4-5, 9.2.5.2

TS 24.008 clause 4.7.13

12.9.13.3 Test purpose

To verify that the UE initiates a Service request procedure due to uplink data transmission with two PDP contexts with different traffic classes are activated, when one is of traffic class "background class" and the other is of traffic class "interactive class", after normal RRC connection release.

To verify that the radio access bearers can be re-established with a single radio bearer establishment procedure for the preserved PDP contexts, when initiated by the UE.

12.9.13.4 Method of test

Initial condition

System Simulator:

One cell, default parameters.

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 is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Related ICS/IXIT statements

Support of PS service Yes/No

Secondary PDP context activation procedure Yes/no

Test procedure

a) Two PDP contexts with different Traffic Classes are activated including the radio access bearers.

b) The SS releases the RRC connection, but keeps the two PDP contexts.

c) Due to transmission of uplink data, the UE initiates an RRC connection establishment and sends a SERVICE REQUEST.

d) The SS performs security mode control procedure and establishes the RABs for the two active PDP contexts using a single Radio bearer establishment procedure and the same QoS as previously, without the need for PDP context modification.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a PDP context activation
2			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context with traffic class "Background class"
3	SS			The SS establishes the radio access bearer.
4			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context
5	UE			Initiate a secondary PDP context activation
6			ACTIVATE SECONDARY PDP CONTEXT REQUEST	Request a Secondary PDP context activation with traffic class "Interactive class"
7	SS			The SS establishes the radio access bearer.
8			ACTIVATE SECONDARY PDP CONTEXT ACCEPT	Accept the Secondary PDP context activation
9	SS			The SS releases the RRC connection.
10	UE			The UE initiates transmission of uplink data, by MMI or by AT command.
11	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Originating Interactive Call", which is the most demanding traffic class among the active PDP contexts.
12			SERVICE REQUEST	Service type = "data"
13	SS			The SS starts ciphering and integrity protection.
14	SS			The SS establishes the radio access bearers simultaneously for the two active PDP contexts, using the same QoS that was used at activation.

Specific message contents

None.

12.9.13.5 Test requirements

After step 11, UE shall:

– transmit a SERVICE REQUEST message with service type "data".

12.9.14 Service Request / RAB re-establishment / Network initiated / single PDP context

12.9.14.1 Definition

12.9.14.2 Conformance requirement

– For a PDP context using background or interactive traffic class, the PDP context is be preserved with no modifications.

– For a PDP context using streaming or conversational traffic class, the PDP context is preserved, but the maximum bit rate is downgraded to 0 kbit/s (for both uplink and downlink).

The procedure for re-establishment of RABs allows the SGSN to re-establish RABs for active PDP contexts that don’t have an associated RAB.

When RABs for an MS that has no RRC connection needs to be re-established, the CN must first page the MS.

The criteria to invoke the Service request procedure are when;

c) the MS receives a paging request for PS domain from the network in PMM-IDLE mode. In this case, the service type shall be set to "paging response".

Reference

TS 23.060 clause 9.2.3.4-5, 9.2.5.2

TS 24.008 clause 4.7.13

12.9.14.3 Test purpose

To verify that the radio access bearers can be re-established for the preserved PDP context with traffic class "Background class", when initiated from the network, after normal RRC connection release.

12.9.14.4 Method of test

System Simulator:

One cell, default parameters.

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 is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Related ICS/IXIT statements

Support of PS service Yes/No

Test procedure

a) A PDP context with traffic class "Background class" is activated including the radio access bearer.

b) The SS releases the RRC connection, but keeps the PDP context.

c) The SS initiates paging of the UE.

d) As response to the paging, the UE initiates an RRC connection establishment and sends a SERVICE REQUEST.

e) The SS performs security mode control procedure and establishes the RAB for the active PDP context using the same QoS as previously, without the need for PDP context modification.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a PDP context activation
2			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context with traffic class "Background class"
3	SS			The SS starts ciphering and integrity protection and establishes the radio access bearer.
4			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context
5	SS			The SS releases the RRC connection.
6	SS			The SS waits for 5 s to ensure the UE is in service.
7			PAGING TYPE 1	The SS initiates paging of the UE using the paging cause "Terminating Background Call"’
8	SS			The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to the same value as the paging cause.
9			SERVICE REQUEST	Service type = "Paging response"
10	SS			The SS starts ciphering and integrity protection.
11	SS			The SS establishes the radio access bearer for the active PDP context, using the same QoS that was used at activation.

Specific message contents

None.

12.9.14.5 Test requirements

After step 8, UE shall:

– transmit a SERVICE REQUEST with service type "Paging response"

12.9.15 Service Request / abnormal cases / access barred due to domain specific access restriction for PS domain

12.9.15.1 Definition

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

12.9.15.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.13.5

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

The Service request procedure shall not be started. The MS stays in the current serving cell and applies normal cell reselection process. The Service request procedure may be started by CM layer if it is still necessary, i.e. when access is granted or because of a cell change.

Reference

TS 24.008 clauses 4.1.1.2.2, 4.7.13.5.

12.9.15.3 Test purpose

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

12.9.15.4 Method of test

Initial condition

A PS domain specific access class X (0-15) is arbitrary selected. The USIM is programmed with this access class X.

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

Support of PS service Yes/No
UE operation mode C Yes/No
UE operation mode A Yes/No
UE supports CS call establishment 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 PS attach procedure is performed.

The SS initiates PS domain specific access class X is barred. A service request procedure is not performed.

The SS initiates PS domain specific access class X is not barred. A service request 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). (The UE is set in UE operation mode A in case of the UE supporting both UE operation mode A and C.)
3	UE			The UE is powered up or switched on and attempt to initiate an ATTACH. (see ICS)
4	SS			The 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 an integrity protection.
9	<-		ATTACH ACCEPT	Attach result = ‘GPRS only attached’ Allocated P-TMSI = P-TMSI-2 P-TMSI Signature = P-TMSI-2 signature Routing area identity = RAI-1
10	->		ATTACH COMPLETE
11	SS			The SS releases the RRC connection
12	SS			PS domain specific access class X is barred in cell
13	UE			The UE initiates an upper-layer signalling for PS domain, e.g., Active PDP Context request, by MMI or by AT command.
14	UE			No SERVICE REQUEST sent to the SS as PS domain access class x is barred. The SS waits 30 seconds
15	UE			Step15, 16 and 17 are applied only for UE in UE operation mode A and supports CS call establishment (see ICS). The UE initiates an upper-layer signalling for CS domain, e.g., CM service request, by MMI or by AT command.
16	UE			A CS call is initiated by the UE.
17				UE sends CM Service Request with CM Service Type= ‘Mobile originating call establishment’ SS send CM Service Reject with Reject Cause=’Congestion’ The SS releases the RRC Connection.
18	SS			The access class x is not barred any more
18a	UE			If UE automatically initiates a Service request goto step 20. If UE does not initiate a Service Request, go to Step 19.
19	UE			The UE initiates an upper-layer signalling, e.g., Active PDP Context request, by MMI or by AT command.
20	SS			The IE "Establishment cause" in the received RRC CONNECTION REQUEST message is not checked.
21	->		SERVICE REQUEST	Service Type = "signalling".
22	<-		SERVICE REJECT	GMM cause = ‘GPRS services not allowed’
23	SS			The SS releases the RRC connection.

Specific message contents

None.

12.9.15.5 Test requirements

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

– not perform Service Request procedure.

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

– perform Service Request procedure.

12.9.16 MBMS SERVICE REQUEST / counting / MBMS Selected Service

12.9.16.1 Definition

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

12.9.16.2 Conformance requirement

The purpose of this procedure is to transfer the PMM mode from PMM-IDLE to PMM-CONNECTED mode, and/or to assign radio access bearer in case of PDP contexts are activated without radio access bearer assigned. In latter case, the PMM mode may be PMM-IDLE mode or may alternatively be the PMM-CONNECTED mode if the MS requires radio access bearer re-establishment. This procedure is used for;

……

– counting the number of mobile stations in a cell which are interested in a specific MBMS service.

…

For counting the number of mobile stations in PMM-IDLE mode interested in a specific MBMS service, the trigger is given from the network by the MBMS notification procedure [8].

Service type can take either of the following values; ……, "MBMS multicast service reception" or "MBMS broadcast service reception". Each of the values shall be selected according to the criteria to initiate the Service request procedure.

If the UE is triggered to send a Service Request message for both MBMS multicast service and MBMS broadcast service simultaneously, the UE shall include a Service Type indicating "MBMS multicast service reception".

…….

The criteria to invoke the Service request procedure are when;

…….

d) the MS is in PMM-IDLE or PMM_CONNECTED mode, receives an MBMS notification for an MBMS multicast service for which the MS has activated an MBMS context or for an MBMS broadcast service which has been selected for reception locally by upper layers in the MS, and is prompted by the contents of the notification to establish a PS signalling connection. In this case, the service type shall be set to "MBMS multicast service reception" or "MBMS broadcast service reception", respectively.

…….

If one of the above criteria to invoke the Service request procedure is fulfilled, then the Service request procedure may only be initiated by the MS when the following conditions are fulfilled:

– its GPRS update status is GU1 UPDATED; and

– no GMM specific procedure is ongoing

Reference

3GPP TS 24.008 clauses 4.7.13

3GPP TS 25.331 clauses 8.6.9.6

3GPP TS 23.246 clauses 8.16

12.9.16.3 Test purpose

To test the behaviour of the UE that, when MBMS Modified services Information is sent with “MBMS required UE action” IE set to “Acquire counting info”, then UE initiates a Service Request procedure.

12.9.16.4 Method of test

Initial condition

System Simulator:

One MBMS cell operating in network operation mode I.

User Equipment:

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

The UE is interested in the selected service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

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

MBMS Broadcast service application available on UE Yes/No

Test procedure

a) The UE in PMM IDLE mode sends a SERVICE REQUEST to the SS, in response to the ‘modified services information’ indicating ‘counting’ to enable MBMS reception

b) After the SS receives the SERVICE REQUEST message, the SS sends a SERVICE REJECT message.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS initiates counting procedure by sending MBMS Modified services Information with “MBMS required UE action” IE set to “Acquire counting info”
1a	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "mbms_Reception".
1b	UE			The UE after completing the RRC Connection Setup procedure shall initiate the MBMS MODIFICATION REQUEST procedure. This message may be received at any point after RRC CONNECTION SETUP COMPLETE and before step 4.
2	->		SERVICE REQUEST	Service Type indicating ‘MBMS Broadcast Service Reception’’.
3	<-		SERVICE REJECT	The SS does not start security procedures, but rejects the Service request with reject cause value other than #3, #6, #7, #9, #10, #11, #12, #13, #15, and #40.
4	SS			The SS releases the RRC Connection. The UE is switched off or power is removed (see ICS)

Specific message contents

In step 1, MBMS Modified services Information sent by SS with “MBMS required UE action” IE set to “Acquire counting info”.

12.9.16.5 Test requirements

1. At step 2, the UE initiates a service request procedure with the ‘Service type’ set to ‘MBMS Broadcast Service Reception’.

12.9.16m MBMS SERVICE REQUEST / counting / MBMS Multicast Service

12.9.16m.1 Definition

This test is applicable for all UEs that support MBMS multicast services.

12.9.16m.2 Conformance requirement

Same conformance requirement as in clause 12.9.16.2

12.9.16m.3 Test purpose

Same test purpose as in clause 12.9.16.3.

12.9.16m.4 Method of test

Initial condition

System Simulator:

Same as in clause 12.9.16.4.

User Equipment:

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

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

Related ICS/IXIT statements

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

MBMS Multicast service application available on UE Yes/No.

Test procedure

Same test procedure as in clause 12.9.16.4.

Expected Sequence

Same expected sequence as in clause 12.9.16.4 except that expected sequence step 1b is not applicable and the Service Type in SERVICE REQUEST message in step 2 indicates ‘MBMS Multicast Service Reception’.

Specific message contents

Same specific messages contents as in clause 12.9.16.4

12.9.16m.5 Test requirements

1. At step 2, the UE initiates a service request procedure with the ‘Service type’ set to ‘MBMS Multicast Service Reception’ and ‘MBMS Context Status’ set appropriately.

12.9.17 MBMS SERVICE REQUEST / point to point RBs / MBMS Selected Service

12.9.17.1 Definition

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

12.9.17.2 Conformance requirement

…….

– requesting the establishment of a point-to-point Radio Bearer for receiving a MBMS service.

……

For establishing a point-to-point radio bearer to allow MBMS service, the trigger is given from the RRC determining this need from the MBMS control parameters broadcasted by the network [8].

Service type can take either of the following values; …… "MBMS multicast service reception" or "MBMS broadcast service reception". Each of the values shall be selected according to the criteria to initiate the Service request procedure.

The criteria to invoke the Service request procedure are when;

……..

e) the MS in PMM-IDLE or PMM_CONNECTED mode, determines from the broadcast MBMS control parameters that there is a need to establish a point-to-point Radio Bearer to enable MBMS reception. In this case, the service type shall be set to "MBMS multicast service reception" or "MBMS broadcast service reception", respectively.

If one of the above criteria to invoke the Service request procedure is fulfilled, then the Service request procedure may only be initiated by the MS when the following conditions are fulfilled:

– its GPRS update status is GU1 UPDATED; and

– no GMM specific procedure is ongoing.

Reference

3GPP TS 24.008 clauses 4.7.13

3GPP TS 25.331 clauses 8.6.9.6

3GPP TS 23.246 clauses 8.16

12.9.17.3 Test purpose

To test the behaviour of the UE that, when MBMS Modified services Information is sent with “MBMS required UE action” IE set to “Request PTP RB”, then UE initiates a Service Request procedure.

12.9.17.4 Method of test

Initial condition

System Simulator:

One MBMS cell operating in network operation mode I.

User Equipment:

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

The UE is interested in the selected service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

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

MBMS Broadcast service application available on UE Yes/No

Test procedure

a) The UE in PMM IDLE mode sends a SERVICE REQUEST to the SS, in response to the ‘modified services information’ indicating ‘Request PTP RB’ to enable MBMS reception

b) RABs are established after Security procedure.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS initiates PTPRB setup procedure by sending MBMS Modified services Information with “MBMS required UE action” IE set to “Request PTP RB”
1a	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “Request PTP RB” .
1b	UE			The UE after completing the RRC Connection Setup procedure shall initiate the MBMS MODIFICATION REQUEST procedure. This message may be received at any point after RRC CONNECTION SETUP COMPLETE and before step 3.
2	->		SERVICE REQUEST	Service Type = ‘MBMS Broadcast Service Reception’.
3	SS			The SS start security procedures. After completion of Security procedure SS establishes the RAB

Specific message contents

In step 1, MBMS Modified services Information sent by SS with “MBMS required UE action” IE set to “Request PTP RB”.

12.9.17.5 Test requirements

1. At step 2, the UE initiates a service request procedure with the ‘Service type’ set to ‘MBMS Broadcast Service Reception’.

12.9.17m MBMS SERVICE REQUEST / point to point RBs / MBMS Multicast Service

12.9.17m.1 Definition

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

12.9.17m.2 Conformance requirement

Same conformance requirement as in clause 12.9.17.2

12.9.17m.3 Test purpose

Same test purpose as in clause 12.9.17.3.

12.9.17m.4 Method of test

Initial condition

System Simulator:

Same as in clause 12.9.17.4.

User Equipment:

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

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

Related ICS/IXIT statements

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

MBMS Multicast service application available on UE Yes/No.

Test procedure

Same test procedure as in clause 12.9.17.4 except that expected sequence step 1b is not applicable and the Service Type in SERVICE REQUEST message in step 2 indicates ‘MBMS Multicast Service Reception’.

Specific message contents

Same specific messages contents as in clause 12.9.17.4

12.9.17m.5 Test requirements

1. At step 2, the UE initiates a service request procedure with the ‘Service type’ set to ‘MBMS Multicast Service Reception’ and ‘MBMS Context Status’ set appropriately.

12.9.18m Handling of MBMS context status information in SERVICE REQUEST and SERVICE ACCEPT messages / MBMS Multicast Service

12.9.18m.1 Definition

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

12.9.18m.2 Conformance requirement

…

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

Reference

3GPP TS 24.008 clauses 4.7.13.

12.9.18m.3 Test purpose

1. To verify that the UE includes correct MBMS context status information in SERVICE REQUEST message

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

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

12.9.18m.4 Method of test

Initial condition

System Simulator:

1 MBMS cell, default parameters.

User Equipment:

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

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

The UE has PDP context activated and two MBMS contexts activated.

PDP one trans_id 0 and nsapi 5

MBMS one trans_id 1 and nsapi 128 and

MBMS two trans_id 2 and nsapi 129.

For Both the MBMS associated PDP is with nsapi 5

Related ICS/IXIT statements

MBMS Multicast service application available on UE Yes/No

Test procedure

a) The UE initiates RAB Reestablishment for Dormant PDP which in turn triggers a Service request procedure in order to move to state PMM_CONNECTED for the RAB reestablishment.

b) Service procedure completes at completion of security procedure.

c) SS shall not release RRC connection and SS shall not establish the RAB.

d) UE initiates Service Request Procedure which completes with Service Accept this time.

Expected Sequence

	UE	SS
1	UE			The UE initiates transmission of uplink data, by MMI or by AT command.
2	->		SERVICE REQUEST	Service type = "data", UE sets nsapi 128 and 129 as 1 in MBMS context Status IE and all other as 0.
3	<-		AUTHENTICATION AND CIPHERING REQUEST
4	->		AUTHENTICATION AND CIPHERING RESPONSE
5	SS			The SS starts integrity protection.
6	SS			SS shall not release RRC connection and SS shall not establish the RAB
7	UE			The UE initiates transmission of uplink data, by MMI or by AT command.
8	->		SERVICE REQUEST	Service type = "data", UE sets nsapi 128 and 129 as 1 in MBMS context Status IE and all other as 0.
9	<-		SERVICE ACCEPT	SS sets nsapi 129 as 0 in MBMS Context Status IE. UE locally deactivates MBMS context with extended_nsapi 129
10	SS			SS shall not release RRC connection and SS shall not establish the RAB
11	UE			The UE initiates transmission of uplink data, by MMI or by AT command, after time T3319.
12	->		SERVICE REQUEST	Service type = "data", UE sets nsapi 128 1 in MBMS context Status IE and all other as 0.This verifies UE deactivated MBMS Context with nsapi 129
13	<-		SERVICE ACCEPT	SS does not include MBMS Context Status IE. UE locally deactivates all MBMS contexts.
14				UE may deactivate associated PDP with MBMS contexts as all the associated MBMS contexts are deactivated.
15	SS			SS shall not release RRC connection and SS shall not establish the RAB
16	UE			The UE initiates transmission of uplink data, by MMI or by AT command, after time T3319.
17	->		SERVICE REQUEST	UE does not include MBMS Context Status IE. This verifies UE deactivated nsapi 128 and UE does not include MBMS context status IE when no MBMS context exists.
18	<-		SERVICE ACCEPT

Specific message contents

Step 9: SS sets nsapi 129 as 0 in MBMS Context Status IE.

Step 13: SS does not include MBMS Context Status IE.

12.9.18m.5 Test requirements

At step 8, UE sets nsapi 128 and 129 as 1 in MBMS context Status IE and all other as 0 in the service request message.

At step 12, UE sets nsapi 128 as 1 in MBMS context Status IE and all other as 0 in the service request message.

At step 17, UE does not include MBMS Context Status IE in the service request message.