12.2.2 Combined PS attach

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

12.2.2.1 Combined PS attach / PS and non-PS attach accepted

12.2.2.1.1 Definition

12.2.2.1.2 Conformance requirement

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

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

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

4) If the network accepts the combined PS attach procedure and determines that IMSI shall be used in CS operations, the UE shall continue communication with the IMSI for CS operations.

5) If the network accepts the combined PS attach procedure and determines that a TMSI shall be used in CS operations, the UE shall continue communication with the TMSI for CS operations.

Reference

3GPP TS 24.008 clause 4.7.3.2.

12.2.2.1.3 Test purpose

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

The following cases are identified:

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

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

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

4) Mobile terminating CS call is allowed with IMSI;

5) Mobile terminating CS call is allowed with TMSI.

12.2.2.1.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode I. ATT flag is set to 0.

User Equipment:

The UE has a valid IMSI.

Related ICS/IXIT statements

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

Test procedure

1) The UE sends an ATTACH REQUEST message with identity IMSI. The SS allocates a P-TMSI and returns ATTACH ACCEPT message with a P-TMSI. The UE acknowledge the P-TMSI by sending ATTACH COMPLETE message. Further communication UE – SS is performed by the new P-TMSI. For CS calls, the IMSI is used.

2) The UE is CS paged in order to verify that the IMSI is used for CS calls.

3) The UE is PS paged in order to verify that the new P-TMSI is used for PS services.

4) The UE sends an ATTACH REQUEST message with identity P-TMSI. The SS allocates a new P-TMSI and returns ATTACH ACCEPT message with the new P-TMSI and a new TMSI. The UE acknowledge the P-TMSI and the TMSI by sending ATTACH COMPLETE message. Further communication UE – SS is performed by the new P-TMSI. For CS calls, the new TMSI is used. The UE is CS paged in order to verify that the new TMSI is used for CS services.

5) The UE is PS paged in order to verify that the new P-TMSI is used for PS services. The UE will not answer signalling addressed to the old P-TMSI.

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

7) The UE is PS paged in order to verify that the previously used P-TMSI is used for PS services.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

The UE is set in UE operation mode A (see ICS).

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 = ‘Combined GPRS/IMSI attach’

Mobile identity =IMSI

TMSI status = no valid TMSI available

3a

<-

AUTHENTICATION AND CIPHERING REQUEST

3b

->

AUTHENTICATION AND CIPHERING RESPONSE

3c

SS

The SS starts integrity protection.

4

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

MS identity =IMSI

Routing area identity = RAI-1

5

->

ATTACH COMPLETE

5a

SS

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

6

<-

PAGING TYPE1

Mobile identity = IMSI

Paging order is for CS services.

Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling"

7

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating conversational call" or “Low priority signalling”.

8

Void

9

Void

10

->

PAGING RESPONSE

Mobile identity = IMSI

11

SS

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

12

Void

13

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging for PS services

Paging cause = "Terminating interactive call"

13a

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".

13b

Void

13c

Void

14

->

SERVICE REQUEST

service type = "paging response"

14aa

SS

The SS starts integrity protection.

14a

SS

The SS releases the RRC connection.

14b

Void

15

UE

The UE is switched off or power is removed (see ICS).

15a

SS

SS checks that the IE "Establishment cause" in any received RRC CONNECTION REQUEST message is set to "Detach".

16

->

DETACH REQUEST

Message not sent if power is removed.

Detach type = ‘power switched off, combined GPRS / IMSI detach’

16a

SS

If the power was not removed, the SS releases the RRC connection. If no RRC CONNECTION RELEASE COMPLETE message have been received within 1 second then the SS shall consider the UE as switched off .

17

UE

The UE is powered up or switched on and initiates an attach (see ICS).

17a

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".

18

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = P-TMSI-1

TMSI status = no valid TMSI available

Old Routing area identity = RAI-1

18a

<-

AUTHENTICATION AND CIPHERING REQUEST

18b

->

AUTHENTICATION AND CIPHERING RESPONSE

18c

SS

The SS starts integrity protection.

19

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-2

P-TMSI Signature = P-TMSI-2 signature

MS identity = TMSI-1

Routing area identity = RAI-1

20

->

ATTACH COMPLETE

21

Void

21b

Void

21c

SS

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

22

<-

PAGING TYPE 1

Mobile identity = TMSI-1

Paging order is for CS services.

Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling "

23

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating conversational call".

24

Void

25

Void

26

->

PAGING RESPONSE

Mobile identity = TMSI-1

27

SS

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

28

Void

29

<-

PAGING TYPE1

Mobile identity = P-TMSI-2

Paging for PS services

Paging cause = "Terminating interactive call"

29a

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".

29b

Void

29c

Void

30

->

SERVICE REQUEST

service type = "paging response"

30aa

Void

30a

SS

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

30b

Void

31

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging for PS services

Paging cause = "Terminating interactive call"

32

UE

No response from the UE to the request. This is checked for 10 seconds.

33

UE

The UE is switched off or power is removed (see ICS).

33a

SS

SS checks that the IE "Establishment cause" in any received RRC CONNECTION REQUEST message is set to "Detach".

34

->

DETACH REQUEST

Message not sent if power is removed.

Detach type = ‘power switched off, combined GPRS / IMSI detach’

34a

SS

If the power was not removed, the SS releases the RRC connection. If no RRC CONNECTION RELEASE COMPLETE message have been received within 1 second then the SS shall consider the UE as switched off .

35

UE

The UE is powered up or switched on and initiates an attach (see ICS).

35a

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".

36

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = P-TMSI-2

Old Routing area identity = RAI-1
TMSI status = valid TMSI available or IE not present

36a

<-

AUTHENTICATION AND CIPHERING REQUEST

36b

->

AUTHENTICATION AND CIPHERING RESPONSE

36c

SS

The SS starts integrity protection.

37

<-

ATTACH ACCEPT

No new mobile identity assigned.

TMSI and P-TMSI not included.

Attach result = ‘Combined GPRS/IMSI attached’
P-TMSI-3 signature

Routing area identity = RAI-1

37a

SS

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

38

<-

PAGING TYPE1

Mobile identity = P-TMSI-2

Paging for PS services

Paging cause = "Terminating interactive call"

38a

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".

38b

Void

38c

Void

39

->

SERVICE REQUEST

service type = "paging response"

39aa

Void

39a

SS

The SS releases the RRC connection.

39b

Void

Specific message contents

None.

12.2.2.1.5 Test requirements

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

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

Case 1) SS accept the combined PS attach procedure (signalled by an IMSI) and allocates a P-TMSI.

At step5, UE shall

– send the ATTACH COMPLETE message.

At step10, when the UE receives the paging message for CS domain with Mobile identity = IMSI, UE shall;

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

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

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

Case 2) SS accepts the combined PS attach procedure (signalled by P-TMSI) and reallocates a new P-TMSI and TMSI.

At step20, UE shall:

– send the ATTACH COMPLETE message.

At step26, when the UE receives the paging message for CS domain with Mobile identity = TMSI, UE shall;

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

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

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

Case 3) SS accepts the combined PS attach procedure (signalled by a P-TMSI) from the UE without reallocation of the previously used P-TMSI.

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

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

12.2.2.2 Combined PS attach / PS only attach accepted

12.2.2.2.1 Definition

12.2.2.2.2 Conformance requirement

1) If the network accepts the combined PS attach procedure, but GMM cause code ‘IMSI unknown in HLR’ is sent to the UE the User Equipment shall delete the stored TMSI, LAI and CKSN. The User Equipment shall consider USIM invalid for non-PS services until power is switched off or USIM is removed.

2) If the network accepts the combined PS attach procedure, but GMM cause code ‘MSC temporarily not reachable’ or ‘Network failure’ is sent to the UE, an UE operation mode A UE may perform an MM IMSI attach procedure.

Reference

3GPP TS 24.008 clause 4.7.3.2.

12.2.2.2.3 Test purpose

Test purpose 1

To test the behaviour of the UE if the network accepts the PS attach procedure with indication PS only, GMM cause ‘IMSI unknown in HLR’.

Test purpose 2

To test the behaviour of the UE which does not support an automatic MM IMSI attach if the network accepts the PS attach procedure with indication PS only, GMM cause ‘MSC temporarily not reachable’ or ‘Network failure’.

Test purpose 3

To test the behaviour of the UE which supports an automatic MM IMSI attach if the network accepts the PS attach procedure with indication PS only, GMM cause ‘MSC temporarily not reachable’ or ‘Network failure’.

12.2.2.2.4 Method of test

Proc 1: Test procedure 1

Initial condition

System Simulator:

One cell operating in network operation mode I.

User Equipment:

The UE has a valid IMSI.

Related ICS/IXIT statements

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

Test procedure

The UE sends an ATTACH REQUEST message with identity IMSI. The SS allocates a P-TMSI and returns ATTACH ACCEPT message with a P-TMSI. GMM cause ‘IMSI unknown in HLR’ is indicated from SS. Further communication UE – SS is performed by the P-TMSI. CS services are not possible.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

The UE is set in UE operation mode A.

2

UE

The UE is powered up or switched on and initiates an attach (see ICS).

3

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =IMSI

TMSI status = no valid TMSI available

3a

<-

AUTHENTICATION AND CIPHERING REQUEST

3b

->

AUTHENTICATION AND CIPHERING RESPONSE

3c

SS

The SS starts integrity protection.

4

<-

ATTACH ACCEPT

Attach result = ‘GPRS only attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

GMM cause = ‘IMSI unknown in HLR’

Routing area identity = RAI-1

5

->

ATTACH COMPLETE

6

<-

PAGING TYPE1

Mobile identity = IMSI

Paging order is for CS services.

7

UE

The UE shall not initiate an RRC connection. This is checked during 3 seconds.

Proc 2: Test procedure 2

Initial condition

System Simulator:

One cell operating in network operation mode I. T3212 and T3302 is set to 6 minutes.

User Equipment:

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

Related ICS/IXIT statements

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

Test procedure

The UE sends an ATTACH REQUEST message. The SS allocates a P-TMSI and returns ATTACH ACCEPT message with a P-TMSI. GMM cause ‘MSC temporarily not reachable’ or ‘Network failure’ is indicated from SS. The cause code is arbitrarily chosen. The UE sends a ROUTING AREA UPDATE REQUEST message. The SS returns a ROUTING AREA UPDATE ACCEPT message. GMM cause ‘MSC temporarily not reachable’ or ‘Network failure’ is indicated from SS. The cause code is arbitrarily chosen. The ROUTING AREA UPDATE procedure is repeated four times. An UE operation mode A UE may then perform an MM IMSI attach procedure (according to the ICS statement). Further communication UE – SS is performed by the P-TMSI. The existence of a signalling channel is verified by a request for mobile identity.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

The UE is set in UE operation mode A and no automatic MM IMSI attach procedure is indicated (see ICS).

2

UE

The UE is powered up or switched on and initiates an attach (see ICS).

3

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1
TMSI status = valid TMSI available or IE is omitted

3a

<-

AUTHENTICATION AND CIPHERING REQUEST

3b

->

AUTHENTICATION AND CIPHERING RESPONSE

3c

SS

The SS starts integrity protection.

4

<-

ATTACH ACCEPT

Attach result = ‘GPRS only attached’

Allocated P-TMSI = P-TMSI-2

P-TMSI Signature = P-TMSI-2 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

5

->

ATTACH COMPLETE

6

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA / LA updating with IMSI attach’

Old P-TMSI signature =P-TMSI-2 signature

Old Routing area identity = RAI-1

7

<-

ROUTING AREA UPDATE ACCEPT

No new mobile identity assigned.

P-TMSI not included.

Update result = ‘RA updated’

P-TMSI-3 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

8

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA / LA updating with IMSI attach’

Old P-TMSI signature =P-TMSI-3 signature

Old Routing area identity = RAI-1

9

<-

ROUTING AREA UPDATE ACCEPT

No new mobile identity assigned.

P-TMSI not included.

Update result = ‘RA updated’
P-TMSI-4 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

10

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA / LA updating with IMSI attach’

Old P-TMSI signature =P-TMSI-4 signature

Old Routing area identity = RAI-1

11

SS

The SS verifies that the time between the previous routing area update accept and routing area update request is T3311.

12

<-

ROUTING AREA UPDATE ACCEPT

No new mobile identity assigned.

P-TMSI not included.

Update result = ‘RA updated’
P-TMSI-5 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

13

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA / LA updating with IMSI attach’

Old P-TMSI signature =P-TMSI-5 signature

Old Routing area identity = RAI-1

14

<-

ROUTING AREA UPDATE ACCEPT

No new mobile identity assigned.

P-TMSI not included.

Update result = ‘RA updated’
P-TMSI-6 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

15-20

(void)

Proc 3: Test procedure 3

Initial condition

System Simulator:

One cell operating in network operation mode I. T3212 and T3302 is set to 6 minutes.

User Equipment:

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

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode A Yes/No
Switch off on button Yes/No

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

Test procedure

The UE sends an ATTACH REQUEST message. The SS allocates a P-TMSI and returns ATTACH ACCEPT message with a P-TMSI. GMM cause ‘MSC temporarily not reachable’ or ‘Network failure’ is indicated from SS. The cause code is arbitrarily chosen. The UE sends a ROUTING AREA UPDATE REQUEST message. The SS returns a ROUTING AREA UPDATE ACCEPT message. GMM cause ‘MSC temporarily not reachable’ or ‘Network failure’ is indicated from SS. The cause code is arbitrarily chosen. The ROUTING AREA UPDATE procedure is repeated four times. An UE operation mode A UE may then perform an MM IMSI attach procedure (according to the ICS statement). Further communication UE – SS is performed by the P-TMSI. The existence of a signalling channel is verified by a request for mobile identity.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

Automatic MM IMSI attach procedure is indicated (see ICS).

2

UE

The UE is powered up or switched on and initiates an attach (see ICS).

3

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1
TMSI status = valid TMSI available or IE is omitted

3a

<-

AUTHENTICATION AND CIPHERING REQUEST

3b

->

AUTHENTICATION AND CIPHERING RESPONSE

3c

SS

The SS starts integrity protection.

4

<-

ATTACH ACCEPT

No new mobile identity assigned.

P-TMSI not included.

Attach result = ‘GPRS only attached’
P-TMSI-2 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

5

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA / LA updating with IMSI attach’

Old P-TMSI signature =P-TMSI-2 signature

Old Routing area identity = RAI-1

6

<-

ROUTING AREA UPDATE ACCEPT

No new mobile identity assigned.

P-TMSI not included.

Update result = ‘RA updated’
P-TMSI-3 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

7

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA / LA updating with IMSI attach’

Old P-TMSI signature =P-TMSI-3 signature

Old Routing area identity = RAI-1

8

<-

ROUTING AREA UPDATE ACCEPT

No new mobile identity assigned.

P-TMSI not included.

Update result = ‘RA updated’
P-TMSI-4 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

9

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA / LA updating with IMSI attach’

Old P-TMSI signature =P-TMSI-4 signature

Old Routing area identity = RAI-1

10

SS

The SS verifies that the time between the previous routing area update accept and routing area update request is T3311.

11

<-

ROUTING AREA UPDATE ACCEPT

No new mobile identity assigned.

P-TMSI not included.

Update result = ‘RA updated’
P-TMSI-5 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

12

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA / LA updating with IMSI attach’

Old P-TMSI signature =P-TMSI-5 signature

Old Routing area identity = RAI-1

TMSI status = no valid TMSI available

13

SS

The SS verifies that the time between the previous routing area update accept and routing area update request is T3311.

14

<-

ROUTING AREA UPDATE ACCEPT

No new mobile identity assigned.

P No new mobile identity assigned.

P-TMSI not included.

Update result = ‘RA updated’
P-TMSI-6 signature

Routing area identity = RAI-1

GMM cause = ‘MSC temporarily not reachable’ or ‘Network failure’ (arbitrarily chosen)

15

UE

An automatic MM IMSI attach procedure is initiated.

16

UE

Registration on CS

Optional step.

See TS 34.108

This is applied only for UE in UE operation mode A.

Parameter mobile identity is TMSI

Steps 17 – 23 are only performed if the UE has performed the Registration Procedure in step 16.

17

<-

PAGING TYPE1

Mobile identity = TMSI-1

Paging order is for CS services.

18

->

RRC CONNECTION REQUEST

19

<-

RRC CONNECTION SETUP

20

->

RRC CONNECTION SETUP COMPLETE

21

->

PAGING RESPONSE

Mobile identity = TMSI-1

22

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

23

->

RRC CONNECTION RELEASE COMPLETE

Specific message contents

None.

12.2.2.2.5 Test requirements

Test requirements for Test porpose1

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

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

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

– not respond to the paging message for CS domain.

Test requirements for Test porpose2

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

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

At step6, 8, 10 and 13, when the routing area updating attempt counter is less than 5 and the stored RAI is equal to the RAI of the current serving cell, UE shall:

– perform the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach".

Test requirements for Test porpose3

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

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

At step5, 7, 9 and 11, when the routing area updating attempt counter is less than 5 and the stored RAI is equal to the RAI of the current serving cell, UE shall:

– perform the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach".

At step16, UE shall:

– perform MM location updating procedure.

At step21, UE shall:

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

12.2.2.3 Combined PS attach / PS attach while IMSI attach

12.2.2.3.1 Definition

12.2.2.3.2 Conformance requirement

If the PS UE is already attached for non-PS services by the MM specific attach procedure, but wants to perform an attach for PS services, the combined PS attach procedure is performed.

Reference

3GPP TS 24.008 clause 4.7.3.2.

12.2.2.3.3 Test purpose

To test the behaviour of the UE if PS attach performed while IMSI attached.

12.2.2.3.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode I. ATT flag is set.

User Equipment:

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

Related ICS/IXIT statements

Support of PS service Yes/No

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

Test procedure

The UE is forced to register for CS services but not to PS services. The SS verifies that the UE does not respond to paging messages for PS domain. Then the UE is triggered to perform the PS attach procedure and the SS verifies that it responds to PS paging messages.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

The UE is set in UE operation mode A (see ICS) and configured not to perform an automatic PS attach at switch on.

2

UE

The UE is powered up or switched on. No PS attach is performed (see ICS).

3

Registration on CS

See TS 34.108

Location updating type = IMSI attach.

The SS allocates TMSI-1

4

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS services.

5

UE

No response from the UE to the request. This is checked for 10 seconds.

6

UE

The UE is triggered to perform a PS attach.

7

->

ATTACH REQUEST

Attach type = ‘GPRS attach while IMSI attached’ or ‘Combined GPRS/IMSI attach’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

7a

<-

AUTHENTICATION AND CIPHERING REQUEST

7b

->

AUTHENTICATION AND CIPHERING RESPONSE

7c

SS

The SS starts integrity protection.

8

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

No new mobile identity assigned. TMSI and P-TMSI not included
P-TMSI-2 signature

Routing area identity = RAI-1

9

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS services.

10

->

RRC CONNECTION REQUEST

11

<-

RRC CONNECTION SETUP

12

->

RRC CONNECTION SETUP COMPLETE

13

->

SERVICE REQUEST

service type = "paging response"

14

<-

RRC CONNECTION RELEASE

15

->

RRC CONNECTION RELEASE COMPLETE

Specific message contents

None.

12.2.2.3.5 Test requirements

UE is already attached for non-PS service with the MM specific attach procedure.

At step5, UE shall:

– not respond to the paging message for PS domain.

At step7, when the UE is requested to attach for PS services, UE shall:

– perform the combined PS attach procedure.

At step13, UE shall:

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

12.2.2.3a Combined PS attach / NMO-I enabled in UE

12.2.2.3a.1 Definition

12.2.2.3a.2 Conformance requirement

1) The network operation mode (mode I, II, or III) shall be indicated as system information to MSs. Additional system information can indicate that MSs configured to use the extended NMO I system information (see TS 24.368 [111]) shall use NMO I, regardless of what NMO is indicated by system information for other MSs. If this additional system information is absent, MSs configured to use the extended NMO I system information shall use the system information that represents the network operation mode for other MSs. From these indications, the MS determines which mode applies to it. That mode shall be used when using the procedures described in other clauses of this specification.

2) If the parameter "NMO_I_Behaviour" in the NAS configuration Management Object or USIM is set to the value of "1", the bit 2 "NMO I" of system information is applied.

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

Reference

3GPP TS 24.008 clauses 4.7.3.2 and 4.1.1.4.2. 3GPP TS 23.060 clause 5.3.13.2

12.2.2.3a.3 Test purpose

To verify that if "Network mode of operation I" is set in the UE, the UE performs a combined attach when the extended NMO-I system information is broadcast from the network.

12.2.2.3a.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode II. ATT flag is set to 0.

The SIB1 IE "CN domain specific GSM-MAP NAS system information" for the PS Domain has the bit in the “NMO I, Network Mode of Operation I” set to “1”.

User Equipment:

The UE has a valid IMSI.

The UE has the parameter "NMO_I_Behaviour" set to “1”.

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

USIM field

Value

EFUST

Service 96 is supported.

EFNASCONFIG

"NMO I, Network Mode of Operation I" indication is used as defined in TS 24.368, clause 5.6.

Related ICS/IXIT statements

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

Test procedure

1) The UE reads the SIB1 IE "CN domain specific GSM-MAP NAS system information" and uses the value of the “NMO I, Network Mode of Operation I” bit.

2) The UE sends an ATTACH REQUEST message with identity IMSI. The SS allocates a P-TMSI and returns ATTACH ACCEPT message with a P-TMSI. The UE acknowledge the P-TMSI by sending ATTACH COMPLETE message. Further communication UE – SS is performed by the new P-TMSI. For CS calls, the IMSI is used.

2) The UE is CS paged in order to verify that the IMSI is used for CS calls.

3) The UE is PS paged in order to verify that the new P-TMSI is used for PS services.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

The UE is set in UE operation mode A (see ICS).

2

UE

The UE is powered up or switched on and initiates an attach (see ICS).

3

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".

4

–>

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =IMSI

TMSI status = no valid TMSI available

5

<–

AUTHENTICATION AND CIPHERING REQUEST

6

–>

AUTHENTICATION AND CIPHERING RESPONSE

7

SS

The SS starts integrity protection.

8

<–

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

MS identity =IMSI

Routing area identity = RAI-1

9

–>

ATTACH COMPLETE

10

SS

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

11

<–

PAGING TYPE1

Mobile identity = IMSI

Paging order is for CS services.

Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling"

12

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating conversational call" or “Low priority signalling”.

13

–>

PAGING RESPONSE

Mobile identity = IMSI

14

SS

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

15

<–

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging for PS services

Paging cause = "Terminating interactive call"

16

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".

17

–>

SERVICE REQUEST

service type = "paging response"

18

SS

The SS releases the RRC connection

Specific message contents

None.

12.2.2.3a.5 Test requirements

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

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

At step 9, UE shall

– send the ATTACH COMPLETE message.

At step13, when the UE receives the paging message for CS domain with Mobile identity = IMSI, UE shall;

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

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

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

12.2.2.3b

12.2.2.3c Combined PS attach / congestion / GPRS services only

12.2.2.3c.1 Definition

12.2.2.3c.2 Conformance requirement

# 22 (Congestion)

The MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, shall stop timer T3310 if still running, and shall enter state MM-IDLE. The MS shall set the routing area updating attempt counter to 5 and shall start the timer T3302.

Reference

3GPP TS 24.008 clause 4.7.3.2.3.2.

12.2.2.3c.3 Test purpose

To verify that when the MS receives ATTACH ACCEPT with GMM cause congestion then the MS stops combined attach procedure, starts timer T3302 and initiates the combined RAU procedure again when Timer T3302 expires.

12.2.2.3c.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode I. ATT flag is set to 0.

User Equipment:

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

Related ICS/IXIT statements

Support of PS service Yes/No

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

Test procedure

  1. UE initiate a combined attach procedure, and receive a Attach Accept with Attach result = ‘ GPRS only attached ‘ and GMM cause= ‘congestion’.
  2. After T3302 expired, the UE initiate a combined RAU procedure.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

The UE is set in UE operation mode A (see ICS).

2

UE

The UE is powered up or switched on and initiates an attach (see ICS).

3

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".

4

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = PTMSI

5

<-

AUTHENTICATION AND CIPHERING REQUEST

6

->

AUTHENTICATION AND CIPHERING RESPONSE

7

SS

The SS starts integrity protection.

8

<-

ATTACH ACCEPT

Attach result = ‘ GPRS only attached ‘

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

Routing area identity = RAI-1

GMM cause= ‘congestion’

T3302= 3min

9

->

ATTACH COMPLETE

10

SS

The SS releases the RRC connection.

11

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".

12

->

ROUTING AREA UPDATE REQUEST

Update type = ‘Combined RA/LA updating with IMSI attach’

Mobile Identity = P-TMSI-1

13

SS

The SS verifies that the time between the last attach procedure and the RAU procedure is 3 minutes

14

<-

AUTHENTICATION AND CIPHERING REQUEST

15

->

AUTHENTICATION AND CIPHERING RESPONSE

16

SS

The SS starts integrity protection.

17

ROUTING AREA UPDATE ACCEPT

Update result = ‘Combined RA/LA updated’

Mobile Identity = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

Routing area identity = RAI-1

18

->

ROUTING AREA UPDATE COMPLETE

19

SS

The SS releases the RRC connection.

Specific message contents

None.

12.2.2.3c.5 Test requirements

At step 12, when the timer T3302 is expired, UE shall:

– Initiate the combine RAU procedure with Update type = ‘Combined RA/LA updating with IMSI attach’.

12.2.2.4 Combined PS attach / rejected / IMSI invalid / illegal ME

12.2.2.4.1 Definition

12.2.2.4.2 Conformance requirement

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

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

Reference

3GPP TS 24.008 clause 4.7.3.2

12.2.2.4.3 Test purpose

To test the behaviour of the UE if the network rejects the combined PS attach procedure of the UE with the cause ‘Illegal ME’.

12.2.2.4.4 Method of test

Initial condition

System Simulator:

Three cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) and 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 I.

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

User Equipment:

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

Related ICS/IXIT statements

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

Test procedure

The SS rejects a PS attach with the cause value ‘Illegal ME’. The SS checks that the UE does not perform PS attach in the same or another PLMN. CS services are not possible as the USIM is blocked for CS services. PS services are not possible as the USIM is blocked for PS services.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

The following messages are sent and shall be received on cell A.

1

SS

Set the cell type of cell A to the "Serving cell".

Set the cell type of cell B to the "Non-Suitable cell".

Set the cell type of cell C to the "Non-Suitable cell".

(see note)

2

UE

The UE is set in UE operation mode A (see ICS).

3

UE

The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.

4

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or ‘GPRS attach while IMSI attached’

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

TMSI status = valid TMSI available or IE is omitted

5

<-

ATTACH REJECT

GMM cause ‘Illegal ME’.

6

UE

PAGING TYPE1

Mobile identity = TMSI-1Paging order is for CS services.

7

UE

The UE shall not initiate an RRC connection. This is checked during 3 seconds.

8

<-

PAGING TYPE1

Mobile identity = IMSI Paging order is for CS services

9

UE

The UE shall not initiate an RRC connection. This is checked during 3 seconds.

10

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS services.

11

UE

No response from the UE to the request. This is checked for 10 seconds.

The following messages are sent and shall be received on cell B.

12

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)

13

UE

Cell B is preferred by the UE.

14

UE

No ATTACH REQUEST sent to the SS
(SS waits 30 seconds).

15

<-

PAGING TYPE1

Mobile identity = IMSI Paging order is for CS services

16

UE

The UE shall not initiate an RRC connection. This is checked during 3 seconds.

The following messages are sent and shall be received on cell C.

17

SS

Set the cell type of cell B to the "Non-Suitable cell".

Set the cell type of cell C to the "Serving cell".

(see note)

18

UE

Cell C is preferred by the UE.

19

UE

No ATTACH REQUEST sent to the SS
(SS waits 30 seconds).

20

<-

PAGING TYPE1

Mobile identity = IMSI Paging order is for PS services

21

UE

No response from the UE to the request. This is checked for 10 seconds.

22

UE

If possible (see ICS) USIM removal is performed. Otherwise if possible (see ICS) switch off is performed. Otherwise the power is removed.

23

UE

The UE gets the USIM replaced, is powered up or switched on and initiates an attach (see ICS).

24

UE

Step 25 is only performed for non-auto attach UE.

A location updating procedure is initiated.

25

UE

Registration on CS

See TS34.108

Parameter Mobile identity is IMSI.

26

UE

UE initiates an attach automatically (see ICS), by MMI or AT commands.

27

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or ‘GPRS attach while IMSI attached’

Mobile identity = IMSI
TMSI status = no valid TMSI available

27a

<-

AUTHENTICATION AND CIPHERING REQUEST

27b

->

AUTHENTICATION AND CIPHERING RESPONSE

27c

SS

The SS starts integrity protection.

28

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signatureMS identity = TMSI-1

Routing area identity = RAI-2

29

->

ATTACH COMPLETE

30

<-

PAGING TYPE1

Mobile identity = TMSI-1

Paging order is for CS services.

31

->

RRC CONNECTION REQUEST

32

<-

RRC CONNECTION SETUP

33

->

RRC CONNECTION SETUP COMPLETE

34

->

PAGING RESPONSE

Mobile identity = TMSI-2

35

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

36

->

RRC CONNECTION RELEASE COMPLETE

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

Specific message contents

None.

12.2.2.4.5 Test requirements

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

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

At step7, 9 and 16, when the UE receives the paging message for CS domain, UE shall,

– not respond to the paging message for CS domain.

At step11 and 21, when the UE receives the paging message for PS domain, UE shall,

– not respond to the paging message for PS domain.

At step27, when the USIM is replaced, UE shall:

– perform the combined PS attach procedure.

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

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

12.2.2.5 Combined PS attach / rejected / PS services and non-PS services not allowed

12.2.2.5.1 Definition

12.2.2.5.2 Conformance requirement

1) If the network rejects a combined PS attach procedure from the User Equipment with the cause ‘GPRS services and non-GPRS services not allowed’, the User Equipment shall consider USIM invalid for PS and non-PS services until power is switched off or USIM is removed.

2) If the network rejects a combined PS attach procedure from the User Equipment with the cause ‘GPRS services and non-GPRS services not allowed’, the User Equipment shall delete the stored TMSI, LAI, CSKN, RAI, PS-CKSN, P-TMSI and P-TMSI signature.

Reference

3GPP TS 24.008 clause 4.7.3.2.

12.2.2.5.3 Test purpose

To test the behaviour of the UE if the network rejects the combined PS attach procedure of the UE with the cause ‘GPRS services and non-GPRS services not allowed’.

12.2.2.5.4 Method of test

Initial condition

System Simulator:

– Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) and cell B in MCC2/MNC1/LAC1/RAC1 (RAI-2).
Both cells are operating in network operation mode I.

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

Related ICS/IXIT statements

– Support of PS service Yes/No
UE operation mode A Yes/No
Switch off on button Yes/No

USIM removal possible without powering down Yes/No
Automatic PS attach procedure at switch on or power on Yes/No

Test procedure

The SS rejects a PS attach with the cause value ‘GPRS services and non-GPRS services not allowed’. The SS checks that the UE does not perform PS attach in the same or another PLMN. CS services are not possible as the USIM is blocked for CS services. PS services are not possible as the USIM is blocked for PS services.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

The following messages are sent and shall be received on cell A.

1

SS

Set the cell type of cell A to the "Serving cell".

Set the cell type of cell B to the "Non-Suitable cell".

(see note)

2

UE

The UE is set in UE operation mode A (see ICS).

3

UE

The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.

3a

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".

4

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or ‘GPRS attach while IMSI attached’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

4a

<-

AUTHENTICATION AND CIPHERING REQUEST

4b

->

AUTHENTICATION AND CIPHERING RESPONSE

4c

SS

The SS starts integrity protection.

5

<-

ATTACH REJECT

GMM cause ‘GPRS services and non-GPRS services not allowed’

5a

SS

The SS releases the RRC connection. A Rel-8 UE supporting E-UTRA and CS voice emergency call may send ‘signallingConnectionReleaseIndication’.

6

UE

The SS verifies that the UE does not attempt to access the network.
(SS waits 30 seconds).

7

<-

PAGING TYPE1

Mobile identity = IMSI

Paging order is for CS services.

8

UE

The UE shall not initiate an RRC connection. This is checked during 3 seconds.

9

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS Paging.

10

UE

No response from the UE to the request.

This is checked for 10 seconds

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

(void)

13

UE

The SS verifies that the UE does not attempt to access the network.
(SS waits 30 seconds).

14

<-

PAGING TYPE1

Mobile identity = IMSI

Paging order is for CS services.

Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling"

15

UE

The UE shall not initiate an RRC connection. This is checked during 3 seconds.

16

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS services.

Paging cause = "Terminating interactive call"

17

UE

No response from the UE to the request. This is checked for 10seconds.

18

UE

If possible (see ICS) USIM removal is

performed. Otherwise if possible (see ICS)

switch off is performed. Otherwise the power is

removed.

19

UE

The UE gets the USIM replaced, is powered up

or switched on and initiates an attach (see ICS).

20

Void

21

SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".

22

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or ‘GPRS attach while IMSI attached’

Mobile identity = IMSI
TMSI status = no valid TMSI available

22a

<-

AUTHENTICATION AND CIPHERING REQUEST

22b

->

AUTHENTICATION AND CIPHERING RESPONSE

22c

SS

The SS starts integrity protection.

23

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI-1 signature

MS identity = TMSI-1

Routing area identity = RAI-2

24

->

ATTACH COMPLETE

24a

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

25

<-

PAGING TYPE1

Mobile identity = TMSI-1

Paging order is for CS services.

Paging cause = "Terminating conversational call [UE supports CS call establishment] or Terminating Low Priority Signalling"

26

->SS

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating conversational call" or “Low priority signalling”.

27

<-

Void

28

->

Void

29

->

PAGING RESPONSE

Mobile identity = TMSI-1

30

SS<-

The SS releases the RRC connection and waits 5s to allow the UE to read system information.

31

Void

32

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging is for PS services.

Paging cause = "Terminating interactive call"

33

->

RRC CONNECTION REQUEST

SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating interactive call".

34

Void

35

Void

36

->

SERVICE REQUEST

Service type = "paging response"

37

SS

The SS starts integrity protection.

38

SS

The SS releases the RRC connection.

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

Specific message contents

None.

12.2.2.5.5 Test requirements

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

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

At step8 and 15, when the UE receives the paging message for CS domain, UE shall:

– not respond to the paging message for CS domain.

At step10 and 17, when the UE receives the paging message for PS domain, UE shall:

– not respond to the paging message for PS domain.

At step22, when the UE is powered up or switched on or a USIM is replaced, UE shall:

– initiate the combined PS attach procedure.

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

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

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

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

12.2.2.6 Combined PS attach / rejected / PS services not allowed

12.2.2.6.1 Definition

12.2.2.6.2 Conformance requirement

1) If the network rejects a combined PS attach procedure from the User Equipment with the cause ‘GPRS services not allowed’, the User Equipment shall consider USIM invalid for PS services until power is switched off or USIM is removed.

2) If the network rejects a combined PS attach procedure from the User Equipment with the cause ‘GPRS services not allowed’ the User Equipment shall delete the stored RAI, PS-CKSN, P-TMSI and P-TMSI signature.

3) A PS class AUE shall perform an MM IMSI attach procedure.

Reference

3GPP TS 24.008 clause 4.7.3.2

12.2.2.6.3 Test purpose

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

12.2.2.6.4 Method of test

Initial condition

System Simulator:

Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1) and cell B in MCC2/MNC1/LAC1/RAC1 (RAI-2).
Both cells are operating in network operation mode I.
ATT flag set to 1

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

Related ICS/IXIT statements

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

Test procedure

The SS rejects a normal attach with the cause value ‘GPRS services not allowed’. The SS checks that the UE does not perform PS attach. PS services are not possible. An UE operation mode A UE shall perform an MM IMSI attach.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

The following messages are sent and shall be received on cell A.

1

SS

Set the cell type of cell A to the "Serving cell".

Set the cell type of cell B to the "Non-Suitable cell".

(see note)

2

UE

The UE is powered up or switched on.

2a

UE

Registration on CS

See TS 34.108

This step is applied only for non-auto attach UE.

Location Update Procedure initiated from the UE. Parameter mobile identity is TMSI-1.

2b

UE

UE initiates an attach automatically (see ICS), via MMI or AT commands.

3

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or ‘GPRS attach while IMSI attached’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

4

<-

ATTACH REJECT

GMM cause ‘GPRS services not allowed’

5

UE

An automatic MM IMSI attach procedure is initiated.

6

UE

Registration on CS

See TS 34.108

Location updating type = IMSI attach.

The SS allocates TMSI-2.

7

<-

PAGING TYPE1

Mobile identity = TMSI-2

Paging order is for CS services.

8

->

RRC CONNECTION REQUEST

9

<-

RRC CONNECTION SETUP

10

->

RRC CONNECTION SETUP COMPLETE

11

->

PAGING RESPONSE

Mobile identity = TMSI-2

12

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

13

->

RRC CONNECTION RELEASE COMPLETE

The following messages are sent and shall be received on cell B.

14

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)

15

UE

Cell B is preferred by the UE.

16

UE

A location updating procedure is initiated.

17

UE

Registration on CS

See TS 34.108

Location updating type = normal.

The SS allocates TMSI-1.

18

<-

PAGING TYPE1

Mobile identity = TMSI-1

Paging order is for CS services.

19

->

RRC CONNECTION REQUEST

20

<-

RRC CONNECTION SETUP

21

->

RRC CONNECTION SETUP COMPLETE

22

->

PAGING RESPONSE

Mobile identity = TMSI-1

23

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

24

->

RRC CONNECTION RELEASE COMPLETE

25

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging is for PS services

26

UE

No response from the UE to the request. This is checked for 10seconds.

27

UE

If possible (see ICS) switch off is performed. Otherwise the power is removed.

27a

UE

If switch off is performed then UE performs IMSI detach procedure.

28

UE

The UE is powered up or switched.

28a

UE

Registration on CS

See TS 34.108

This step is applied only for non-auto attach UE.

Location Update Procedure initiated from the UE. Parameter mobile identity is TMSI-1.

28b

UE

UE initiates an attach automatically (see ICS), via MMI or AT commands.

29

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or ‘GPRS attach while IMSI attached’

Mobile identity = IMSI

29a

<-

AUTHENTICATION AND CIPHERING REQUEST

29b

->

AUTHENTICATION AND CIPHERING RESPONSE

29c

SS

The SS starts integrity protection.

30

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

MS identity = TMSI-2

Routing area identity = RAI-2

31

->

ATTACH COMPLETE

32

<-

PAGING TYPE1

Mobile identity = TMSI-2

Paging order is for CS services.

33

->

RRC CONNECTION REQUEST

34

<-

RRC CONNECTION SETUP

35

->

RRC CONNECTION SETUP COMPLETE

36

->

PAGING RESPONSE

Mobile identity = TMSI-2

37

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

38

->

RRC CONNECTION RELEASE COMPLETE

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

Specific message contents

None.

12.2.2.6.5 Test requirements

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

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

At step6, if the UE is PS class A, UE shall:

– perform the MM IMSI attach procedure.

At step11, 22 and 36, when the UE receives the paging message for CS domain, UE shall:

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

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

– not respond to the paging message for PS domain.

At step29, UE shall:

– perform the PS attach procedure.

12.2.2.7a Combined PS attach / rejected / location area not allowed

12.2.2.7a.1 Definition

12.2.2.7a.2 Conformance requirement

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

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

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

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

1.4 not delete the list of "equivalent PLMNs".

1.5 perform a cell selection.

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

2.1 perform combined PS attach when a new location area is entered.

2.2 delete the list of forbidden LAs when power is switched off.

Reference

3GPP TS 24.008 clauses 4.7.3.2.

12.2.2.7a.3 Test purpose

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

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

12.2.2.7a.4 Method of test

Initial condition

System Simulator:

Three cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4), cell C in MCC2/MNC1/LAC2/RAC1 (RAI-6).
All cells are operating in network operation mode I.

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

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

User Equipment:

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

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode A Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No
PS attach attempted automatically by outstanding request Yes/No

Test procedure

The SS rejects a combined PS attach with the cause value ‘Location Area not allowed’. The SS checks that the UE does not perform combined PS attach while in the location area, performs PS attach when a new location area is entered and deletes the list of forbidden LAs when switched off. CS services are not possible unless an IMSI attach procedure is performed.

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

Expected Sequence

Step

Direction

Message

Comments

UE

SS

SS

The following messages are sent and shall be received on cell 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 A (see ICS).

3

UE

The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.

3a

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/ IMSI attach’ or

"GPRS Attach while IMSI attached"

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

3b

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

MS identity = TMSI-1

Routing area identity = RAI-1

Equivalent PLMNs = MCC2,MNC1

3c

<-

DETACH REQUEST

Detach type = re-attach required

3d

->

DETACH ACCEPT

4

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or

"GPRS Attach while IMSI attached"

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

5

<-

ATTACH REJECT

GMM cause ‘Location Area not allowed’

6

UE

No LOCATION UPDATING REQ with type ‘IMSI attach’ is sent to the SS
(SS waits 30 seconds).

7

<-

PAGING TYPE1

Mobile identity = TMSI

Paging order is for CS services.

8

UE

The UE shall not initiate an RRC connection. This is checked during 3 seconds.

9

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS services.

10

->

No response from the UE to the request.

This is checked for 10 seconds

The following messages are sent and shall be received on cell B.

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)

11a

UE

The UE performs cell selection.

12

UE

Cell B is preferred by the UE.

13

UE

No ATTACH REQUEST or LOCATION UPDATING REQ is sent to SS
(SS waits 60 seconds)

15

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS services.

16

UE

No response from the UE to the request. This is checked for 10seconds.

17

UE

The UE initiates an attach by MMI or AT command.

18

No attach is performed by the UE. This is checked for 10 seconds.

The following messages are sent and shall be received on cell C.

19

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)

19a

UE

The UE performs cell selection

20

UE

Cell C is preferred by the UE.

Step 20a and 20b are only performed by an UE which will not initiate a PS attach automatically (see ICS)

20a conditional

UE

Registration on CS

Parameter Mobile identity is IMSI.

See TS 34.108

20b conditional

UE

UE initiates an attach via MMI or AT commands.

21

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/ IMSI attach’

Mobile identity = IMSI
TMSI status = no valid TMSI available

21a

<-

AUTHENTICATION AND CIPHERING REQUEST

21b

->

AUTHENTICATION AND CIPHERING RESPONSE

21c

SS

The SS starts integrity protection.

22

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI1

P-TMSI Signature = P-TMSI-1 signature

MS identity = TMSI-1

Routing area identity = RAI-6

Equivalent PLMNs = MCC1,MNC1

23

->

ATTACH COMPLETE

24

<-

PAGING TYPE1

Mobile identity = TMSI-1

Paging order is for CS services.

25

->

RRC CONNECTION REQUEST

26

<-

RRC CONNECTION SETUP

27

->

RRC CONNECTION SETUP COMPLETE

28

->

PAGING RESPONSE

Mobile identity = TMSI-1

29

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

30

->

RRC CONNECTION RELEASE COMPLETE

31

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS services.

32

->

RRC CONNECTION REQUEST

33

<-

RRC CONNECTION SETUP

34

->

RRC CONNECTION SETUP COMPLETE

35

->

SERVICE REQUEST

Service type = "paging response"

36

<-

RRC CONNECTION RELEASE

37

->

RRC CONNECTION RELEASE COMPLETE

38

UE

The UE is switched off or power is removed (see ICS).

39

->

DETACH REQUEST

Message not sent if power is removed.

Detach type = ‘power switched off, combined GPRS / IMSI detach’

39a

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.

The following messages are sent and shall be received on cell B.

40

UE

Set the cell type of cell B to the "Serving cell".

Set the cell type of cell C to the "Non-Suitable cell".

(see note)

Cell B is preferred by the UE.

41

UE

The UE is powered up or switched on and initiates an attach (see ICS).

42

Step 43 is only performed for non-auto attach UE.

43

UE

Registration on CS

See TS 34.108

44

UE

UE initiates an attach automatically (see ICS), by MMI or AT commands.

45

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or "GPRS Attach while IMSI attached"

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-6

45a

<-

AUTHENTICATION AND CIPHERING REQUEST

45b

->

AUTHENTICATION AND CIPHERING RESPONSE

45c

SS

The SS starts integrity protection.

46

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-2

P-TMSI Signature = P-TMSI-2 signature

MS identity = TMSI-2

Routing area identity = RAI-4

Equivalent PLMNs = MCC2,MNC1

47

->

ATTACH COMPLETE

48

<-

PAGING TYPE1

Mobile identity = TMSI-2

Paging order is for CS services.

49

->

RRC CONNECTION REQUEST

50

<-

RRC CONNECTION SETUP

51

->

RRC CONNECTION SETUP COMPLETE

52

->

PAGING RESPONSE

Mobile identity = TMSI-2

53

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

54

->

RRC CONNECTION RELEASE COMPLETE

55

<-

PAGING TYPE1

Mobile identity = P-TMSI-2

Paging order is for PS services.

56

->

RRC CONNECTION REQUEST

57

<-

RRC CONNECTION SETUP

58

->

RRC CONNECTION SETUP COMPLETE

59

->

SERVICE REQUEST

service type = "paging response"

60

<-

RRC CONNECTION RELEASE

61

->

RRC CONNECTION RELEASE COMPLETE

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

Specific message contents

None.

12.2.2.7a.5 Test requirements

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

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

At step6, when the UE receives the ATTACH REJECT message with GMM cause = ‘Location Area not allowed’, UE shall:

– not initiate MM location updating procedure.

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

– not respond to the paging message for CS domain.

At step10 and 16, when the UE receives the paging message for PS domain, UE shall:

– not respond to the paging message for PS domain.

At step13 and 18, when the UE is in the same location area, UE shall:

– not perform PS attach procedure.

At step21, when the UE enters a new location area, UE shall

– perform the combined PS attach procedure.

At step28 and 52, when the UE receives the paging message for CS domain, UE shall:

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

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

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

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

– perform the combined PS attach procedure.

12.2.2.7b Combined PS attach / rejected / No Suitable Cells In Location Area

12.2.2.7b.1 Definition

12.2.2.7b.2 Conformance requirement

1) If the network rejects a combined PS attach procedure from the User Equipment with the cause ‘No Suitable Cells In Location Area’, the User Equipment shall:

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

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

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

1.4 not delete the list of "equivalent PLMNs".

2) If the network rejects a combined PS attach procedure from the User Equipment with the cause ‘No Suitable Cells In Location Area’, the User Equipment shall:

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

Reference

3GPP TS 24.008 clauses 4.7.3.2.

12.2.2.7b.3 Test purpose

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

12.2.2.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)

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

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

User Equipment:

The UE has valid TMSI, P-TMSI and RAI

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

Related ICS/IXIT statements

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

Test procedure

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

Expected Sequence

Step

Direction

Message

Comments

UE

SS

The following message 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 A (see ICS).

3

UE

The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.

4

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

5

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-2 signature

MS identity = TMSI-1

Routing area identity = RAI-1

Equivalent PLMNs = MCC2,MNC1

6

<-

DETACH REQUEST

Detach type = re-attach required

7

->

DETACH ACCEPT

8

SS

Set the cell type of cell A to the "Serving cell".

Set the cell type of cell B to the "Suitable neighbour cell".

Set the cell type of cell C to the "Suitable neighbour cell".

(see note)

The SS configures power level of each Cell as follows.

Cell A > Cell B = Cell C

9

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

10

<-

ATTACH REJECT

GMM cause = ‘No Suitable Cells In Location Area’

11

SS

The SS initiates the RRC connection release.

The following message are sent and shall be received on cell B.

12

UE

The UE initiates an attach automatically, by MMI or by AT command.

13

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = IMSI
TMSI status = no valid TMSI available

14

<-

AUTHENTICATION AND CIPHERING REQUEST

15

->

AUTHENTICATION AND CIPHERING RESPONSE

16

SS

The SS starts integrity protection.

17

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-2

P-TMSI Signature = P-TMSI-2 signature

MS identity = TMSI-2

Routing area identity = RAI-3

Equivalent PLMNs = MCC2,MNC1

18

->

ATTACH COMPLETE

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

Specific message contents

None.

12.2.2.7b.5 Test requirements

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

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

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

– initiate the combined PS attach procedure.

12.2.2.7c Combined PS attach / rejected / Roaming not allowed in this location area

12.2.2.7c.1 Definition

12.2.2.7c.2 Conformance requirement

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

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

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

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

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

1.5 perform a PLMN selection.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.2.7c.3 Test purpose

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

12.2.2.7c.4 Method of test

Initial condition

System Simulator:

Three cells cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4) , cell C in MCC1/MNC1/LAC2/RAC2 (RAI-12)
All three cells are operating in network operation mode I.

User Equipment:

The UE has valid TMSI, P-TMSI and RAI.

Related ICS/IXIT statements

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

Test procedure

The SS rejects a PS attach with the cause value ‘Roaming not allowed in this location area’. The SS checks that the UE performs PLMN selection.

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 A (see ICS).

3

UE

The UE is powered up or switched on and initiates an attach (see ICS). Cell A is preferred by the UE.

4

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’ or

"GPRS Attach while IMSI attached"

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

5

<-

ATTACH REJECT

GMM cause = ‘Roaming not allowed in this location area’

6

UE

No LOCATION UPDATING REQ and ATTACH REQ with type ‘IMSI attach’ is sent to the SS
(SS waits 30 seconds).

7

<-

PAGING TYPE1

Mobile identity = TMSI

Paging order is for CS services.

8

UE

The UE shall not initiate an RRC connection. This is checked during 3 seconds.

9

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

Paging order is for PS services.

10

->

No response from the UE to the request.

This is checked for 10 seconds

11

UE

UE performs PLMN selection.

The following messages are sent and shall be received on cell B.

12

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)

13

UE

Cell B is preferred by the UE.

14

UE

No LOCATION UPDATING REQ is sent to SS
(SS waits 60 seconds)

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 integrity protection.

16

<-

ATTACH ACCEPT

Attach result = ‘GPRS only attached’

Allocated P-TMSI = P-TMSI-2

P-TMSI Signature = P-TMSI-2 signature

Routing area identity = RAI-4

17

->

ATTACH COMPLETE

The following messages are sent and shall be received on cell C.

18

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)

19

UE

Cell C is preferred by the UE.

20

UE

Registration on CS

Parameter Mobile identity is IMSI.

See TS 34.108

21

UE

UE initiates an attach automatically (see ICS) via MMI or AT commands.

22

<-

PAGING TYPE1

Mobile identity = TMSI-1

Paging order is for CS services.

23

->

RRC CONNECTION REQUEST

24

<-

RRC CONNECTION SETUP

25

->

RRC CONNECTION SETUP COMPLETE

26

->

PAGING RESPONSE

Mobile identity = TMSI-1

27

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

28

->

RRC CONNECTION RELEASE COMPLETE

29

<-

PAGING TYPE1

Mobile identity = P-TMSI-2

Paging order is for PS services.

30

->

RRC CONNECTION REQUEST

31

<-

RRC CONNECTION SETUP

32

->

RRC CONNECTION SETUP COMPLETE

33

->

SERVICE REQUEST

Service type = "paging response"

34

<-

RRC CONNECTION RELEASE

35

->

RRC CONNECTION RELEASE COMPLETE

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

Specific message contents

None.

12.2.2.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 step6, UE shall:

– not perform MM IMSI attach and PS attach.

At step8, UE shall:

– not respond to paging for CS domain service.

At step10, UE shall:

– not respond to paging for PS domain service.

At step15, UE shall:

– perform PS attach procedure.

At step20, UE shall:

– perform MM IMSI attach procedure.

12.2.2.7d Combined PS attach / rejected / PS services not allowed in this PLMN

12.2.2.7d.1 Definition

12.2.2.7d.2 Conformance requirement

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

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

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

1.3 store the PLMN identity in the "forbidden PLMNs for PS service" list.

2) If the UE is in UE operation mode A the User Equipment shall:

2.1 perform IMSI attach for non-GPRS services by use of the MM IMSI attach procedure.

Reference

3GPP TS 24.008 clause 4.7.3.1.

12.2.2.7d.3 Test purpose

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

12.2.2.7d.4 Method of test

Initial condition

System Simulator:

Two cells cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC2/MNC1/LAC1/RAC1 (RAI-2).
All two cells are operating in network operation mode I.

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

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

Related ICS/IXIT statements

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

Test procedure

The SS rejects a PS attach with the cause value ‘GPRS services not allowed in this PLMN’. The SS checks that the UE does not perform PS attach and performs an IMSI attach for non-PS services by use of the MM IMSI attach procedure when in the same cell.

After the cell is changed to equivalent PLMN, the UE shall perform PS attach procedure.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

SS

The following messages are sent and shall be received on cell A.

1

UE

The UE is set in UE operation mode A (see ICS).

2

SS

The SS is set in network operation mode I.

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

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

6

<-

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

Equivalent PLMNs = MCC2,MNC1

7

<-

DETACH REQUEST

Detach type = re-attach required

8

->

DETACH ACCEPT

9

UE

Registration on CS

See TS 34.108

This is applied only for UE in UE operation mode A.

10

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

11

<-

ATTACH REJECT

GMM cause = ‘GPRS services not allowed in this PLMN’

12

UE

No ATTACH REQUEST sent to the SS
(SS waits 30 seconds).

13

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)

The following messages are sent and shall be received on cell B.

14

->

ATTACH REQUEST

Attach type = ‘GPRS attach’

Mobile identity = IMSI

15

<-

AUTHENTICATION AND CIPHERING REQUEST

16

->

AUTHENTICATION AND CIPHERING RESPONSE

17

SS

The SS starts integrity protection.

18

<-

ATTACH ACCEPT

Attach result = ‘GPRS only attached’

Allocated P-TMSI = P-TMSI-2

P-TMSI Signature = P-TMSI-2 signature

Routing area identity = RAI-2

Equivalent PLMNs = MCC1,MNC1

19

->

ATTACH COMPLETE

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

Specific message contents

None.

12.2.2.7d.5 Test requirements

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

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

At step4 and 9, UE shall:

– perform MM IMSI attach.

At step12, UE shall:

– not perform PS attach procedure.

At step14, UE shall:

– perform PS attach procedure.

12.2.2.7e Combined PS attach / rejected / Not authorized for this CSG

12.2.2.7e.1 Definition

12.2.2.7e.2 Conformance requirement

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

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

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

1.3 not delete the list of "equivalent PLMNs".

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

Reference

3GPP TS 24.008 clause 4.7.3.2

12.2.2.7e.3 Test purpose

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

12.2.2.7e.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 PLMN 1.

Both cells are operating in network operation mode I.

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

User Equipment:

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

UE Allowed CSG List contains CSG1 and CSG2.

UE is registered on PLMN 1.

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

USIM field

PLMN

CSG ID

EFACSGL

PLMN 1

CSG 1,CSG 2

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

Switch off on button Yes/No

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

Test procedure

The SS rejects a combined PS attach with the cause value ‘ Not authorized for this CSG ‘. The SS checks that the UE shall search for a suitable cell on the same PLMN and shall perform combined PS attach procedure in that cell.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

The following messages are sent and shall be received on cell A.

1

UE

The UE is set in UE operation mode A (see ICS).

2

SS

Set the cell type of cell A to the "Serving cell".

Set the cell type of cell B to the "Non-suitable cell".

(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 = ‘ Combined GPRS/IMSI attach ‘

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

5

<-

AUTHENTICATION AND CIPHERING REQUEST

6

->

AUTHENTICATION AND CIPHERING RESPONSE

7

SS

The SS starts integrity protection.

8

<-

ATTACH ACCEPT

Attach result =’Combined GPRS/IMSI attached’

Routing area identity = RAI-1

9

<-

DETACH REQUEST

Detach type = re-attach required

10

->

DETACH ACCEPT

11

SS

Set the cell type of cell A to the "Serving cell".

Set the cell type of cell B to the "Suitable neighbour cell".

The SS configures power level of each Cell as follows.

Cell A > Cell B

11a

SS

SS shall wait for 1 second to receive the Attach Request in step 12 on the existing RRC Connection. In case ATTACH REQUEST is not received within 1 second then existing RRC Connection is released.

12

->

ATTACH REQUEST

Attach type =’ Combined GPRS/IMSI attach ‘

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

12A

<–

AUTHENTICATION AND CIPHERING REQUEST

12B

–>

AUTHENTICATION AND CIPHERING RESPONSE

12C

The SS starts Integrity Protection

13

<-

ATTACH REJECT

GMM cause = ‘ Not authorized for this CSG ‘

14

SS

The SS initiates the RRC connection release.

The following message are sent and shall be received on cell B.

15

UE

The UE initiates an attach automatically, by MMI or by AT command.

16

->

ATTACH REQUEST

Attach type =’ Combined GPRS/IMSI attach ‘

Mobile identity = P-TMSI-1

17

<-

AUTHENTICATION AND CIPHERING REQUEST

18

->

AUTHENTICATION AND CIPHERING RESPONSE

19

SS

The SS starts integrity protection.

20

<-

ATTACH ACCEPT

Attach result =’Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

Routing area identity = RAI-2

21

->

ATTACH COMPLETE

22

SS

The SS releases the RRC connection.

23

UE

The UE is switched Off or Power is removed. (See ICS)

24

SS

The SS checks that the IE “Establishment Cause” in any received RRC CONNECTION REQUEST is set to “Detach” (Message not sent if power is removed).

25

–>

DETACH REQUEST

Message not sent if power is removed.

Detach type = ‘power switched off, GPRS detach’

26

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

27

The UE is powered up or switched ON.

28

SS Checks that the does not initiate a RRC CONNECTION REQ on Cell A

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

12.2.2.7e.5 Test requirements

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

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

At step13, when the UE receives ATTACH REJECT, UE shall:

– delete the CSG1 in the CSG List.

– UE Allowed CSG List shall contain only CSG2.

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

– perform the PS attach procedure.

At step20, after the UE receives ATTACH ACCEPT:

– UE Allowed CSG List shall contain only CSG2.

12.2.2.8 Combined PS attach / abnormal cases / attempt counter check / miscellaneous reject causes

12.2.2.8.1 Definition

12.2.2.8.2 Conformance requirement

1) When a combined PS attach procedure is rejected with the attempt counter less than five, the User Equipment shall repeat the combined PS attach procedure after T3311 timeout.

2) When a combined PS attach procedure is rejected with the attempt counter five, the User Equipment shall delete the stored TMSI, LAI, CKSN, P-TMSI, P-TMSI signature, PS CKSN and RAI and start T3302.

3) When the T3302 expire, a new combined PS attach procedure shall be initiated.

GMM cause codes that can be selected are:

‘IMSI unknown in HLR’4

‘MS identity cannot be derived by the network’

‘Network failure’

‘Congestion’

‘retry upon entry into a new cell’

‘Semantically incorrect message’

‘Invalid mandatory information’

‘Message type non-existent or not implemented’

‘Message type not compatible with the protocol state’

‘Information element non-existent or not implemented’

‘Conditional IE error’

‘Message not compatible with the protocol state’

‘Protocol error, unspecified’

Reference

3GPP TS 24.008 clause 4.7.3.2.

12.2.2.8.3 Test purpose

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

12.2.2.8.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode I.

User Equipment:

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

Related ICS/IXIT statements

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

Switch off on button Yes/No

Test procedure

The UE initiates a combined PS attach procedure (attempt counter zero).

The SS rejects the attach with an arbitrarily chosen cause code.

The UE initiates a new combined PS attach procedure (attempt counter one) after T3311 expires.

The SS rejects the attach with an arbitrarily chosen cause code.

The UE initiates a new combined PS attach procedure (attempt counter two) after T3311 expires.

The SS rejects the attach with an arbitrarily chosen cause code.

The UE initiates a new combined PS attach procedure (attempt counter three) after T3311 expires.

The SS rejects the attach with an arbitrarily chosen cause code.

The UE initiates a new combined PS attach procedure (attempt counter four) after T3311 expires.

The SS rejects the attach with an arbitrarily chosen cause code.

The UE shall not perform a new successful attach procedure after 15 seconds.

The UE initiates a combined PS attach procedure with attempt counter zero after T3302 expires without P-TMSI, P-TMSI signature, PS CKSN and RAI.

T3302; set to 10 minutes.

T3311; 15 seconds.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

The UE is set in UE operation mode A (see ICS).

2

UE

The UE is powered up or switched on and initiates an attach (see ICS).

3

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

4

<-

ATTACH REJECT

Arbitrary chosen GMM cause

T3302 with value 10 min.

5

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

6

SS

The SS verifies that the time between the attach reject and attach request is T3311

7

<-

ATTACH REJECT

Arbitrarily chosen GMM cause

T3302 with value 10 min.

8

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

9

SS

The SS verifies that the time between the attach reject and attach request is T3311

10

<-

ATTACH REJECT

Arbitrarily chosen GMM cause

T3302 with value 10 min.

11

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

12

SS

The SS verifies that the time between the attach reject and attach request is T3311

13

<-

ATTACH REJECT

Arbitrarily chosen GMM cause

T3302 with value 10 min.

14

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity =P-TMSI-1

Old Routing area identity = RAI-1

15

SS

The SS verifies that the time between the attach reject and attach request is T3311

16

<-

ATTACH REJECT

Arbitrarily chosen GMM cause

T3302 with value 10 min.

17

(optional step)

UE

Registration on CS

See TS 34.108

This is applied only for UE in UE operation mode A. Location Update Procedure may be initiated from the UE.

Parameter mobile identity is IMSI.

20

<-

PAGING TYPE1

Paging order is for PS services.

Mobile identity = P-TMSI-1

21

UE

No response from the UE to the request. This is checked for 10seconds.

21a

Void

22

SS

The SS verifies that the UE does not attempt to attach for T3302 .

23

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

‘GPRS attach while IMSI attached’

Mobile identity = IMSI
TMSI status = no valid TMSI available

23a

<-

AUTHENTICATION AND CIPHERING REQUEST

23b

->

AUTHENTICATION AND CIPHERING RESPONSE

23c

SS

The SS starts integrity protection.

24

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Mobile identity P-TMSI-1

P-TMSI signature

Mobile identity = TMSI-1

Routing area identity = RAI-1

25

->

ATTACH COMPLETE

26

<-

PAGING TYPE1

Mobile identity = TMSI-1

Paging order is for CS services

27

->

RRC CONNECTION REQUEST

28

<-

RRC CONNECTION SETUP

29

->

RRC CONNECTION SETUP COMPLETE

30

->

PAGING RESPONSE

Mobile identity = TMSI-1

31

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

32

->

RRC CONNECTION RELEASE COMPLETE

33

<-

PAGING TYPE1

Mobile identity = P-TMSI-1

33a

->

RRC CONNECTION REQUEST

33b

<-

RRC CONNECTION SETUP

33c

->

RRC CONNECTION SETUP COMPLETE

34

->

SERVICE REQUEST

Service type = "paging response"

34a

<-

RRC CONNECTION RELEASE

34b

->

RRC CONNECTION RELEASE COMPLETE

Specific message contents

None.

12.2.2.8.5 Test requirements

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

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

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

Case1) A combined PS attach procedure is rejected with the attempt counter less than five

At step 5, 8, 11 and 14, when the timer T3311 timeout has occurred, UE shall:

– repeat the combined PS attach procedure.

Case2) A combined PS attach procedure is rejected with the attempt counter five

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

– not respond to the paging message for PS domain.

Case3) The T3302 expires

At step23, UE shall:

    • re-initiate the new combined PS attach procedure.

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

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

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

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

12.2.2.9 Combined PS attach / abnormal cases / PS detach procedure collision

12.2.2.9.1 Definition

12.2.2.9.2 Conformance requirement

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

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

Reference

3GPP TS 24.008 clause 4.7.3.2.

12.2.2.9.3 Test purpose

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

12.2.2.9.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode I.

User Equipment:

The UE has valid TMSI, P-TMSI and RAI. UE is Idle Updated.

Related ICS/IXIT statements

Support of PS service Yes/No
UE operation mode A Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at switch on or power on Yes/No
Re-attach automatically when the network commands a detach with no cause value Yes/No

Test procedure

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

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

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

UE

The UE is set in UE operation mode A (see ICS).

2

UE

The UE is powered up or switched on and initiates an attach (see ICS).

3

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

4

SS

The SS ignores the ATTACH REQUEST message and initiates a detach procedure.

5

<-

DETACH REQUEST

Detach type = ‘re-attach not required’

6

->

DETACH ACCEPT

7

(void)

8

(void)

9

UE

The UE is attached by MMI or AT command if the UE does not re-attach automatically upon receiving a network initiated detach with no cause value, (see IXIT).

10

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = P-TMSI-1

Old Routing area identity = RAI-1

11

SS

The SS ignores the ATTACH REQUEST message and initiates a detach procedure.

12

<-

DETACH REQUEST

Detach type = ‘re-attach required’

13

UE

The UE ignores the DETACH REQUEST message and continue with the attach procedure

14

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-2

P-TMSI Signature = P-TMSI-2 signature

MS identity = TMSI-2

Routing area identity = RAI-1

15

->

ATTACH COMPLETE

16

<-

PAGING TYPE1

Mobile identity = TMSI-2

Paging order is for CS services.

17

->

RRC CONNECTION REQUEST

18

<-

RRC CONNECTION SETUP

19

->

RRC CONNECTION SETUP COMPLETE

20

->

PAGING RESPONSE

Mobile identity = TMSI-2

21

<-

RRC CONNECTION RELEASE

After sending of this message, the SS waits for disconnection of the CS signalling link.

22

->

RRC CONNECTION RELEASE COMPLETE

23

<-

PAGING TYPE1

Paging order is for PS services.

Mobile identity = P-TMSI-2

23a

->

RRC CONNECTION REQUEST

23b

<-

RRC CONNECTION SETUP

23c

->

RRC CONNECTION SETUP COMPLETE

24

->

SERVICE REQUEST

Service type = "paging response"

24a

<-

RRC CONNECTION RELEASE

24b

->

RRC CONNECTION RELEASE COMPLETE

Specific message contents

None.

12.2.2.9.5 Test requirements

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

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

UE shall perform the following actions depending on the Detach type described below.

Case1) Detach type is not re-attach

At step6, UE shall:

– respond to DETACH REQUEST message by sending DETACH ACCEPT message.

Case2) Detach type is re-attach

At step13, UE shall:

– ignore the PS detach procedure.

At step15, UE shall:

– send the ATTACH COMPLETE message.

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

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

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

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

12.2.2.10 Combined PS attach / abnormal cases / access barred due to paging permission with access control

12.2.2.10.1 Definition

This test case is applicable for Rel-8 or later UEs.

12.2.2.10.2 Conformance requirement

TS 24.008 4.1.1.5

– For location updating and routing area updating the mobile station shall evaluate the control information for common access control (as specified in 3GPP TS 44.018 [84], 3GPP TS 44.060 [76], and 3GPP TS 25.331 [23c]), domain specific access control (as specified in 3GPP TS 25.331 [23c]), and the specific control information for location registration (as specified in 3GPP TS 25.331 [23c]; see "Paging Permission with Access Control").

TS 24.008 4.7.3.1.5

a) Access barred because of access class control

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

Reference

3GPP TS 24.008 clause 4.1.1.5, 4.7.3.1.5

12.2.2.10.3 Test purpose

Test purpose

To test the behaviour of the UE in case of paging permission with access control.

The following cases are identified:

1) To verify that, when a combined attach procedure is triggered and SIB3 indicates that the “Location/Registration Restriction Indicator” is set to “All” and all access classes in “Location/Registration Access Class Barred List” are set to barred, the UE does not attempt to make any attach procedure.

2) To verify that, when a combined attach procedure is triggered and SIB3 indicates that “Location/Registration Restriction Indicator” is set to “All” and restriction status is set to "no restriction”, the UE performs a combined attach procedure.

12.2.2.10.4 Method of test

Initial condition

System Simulator:

One cell operating in network operation mode I.
“Location/Registration Restriction Indicator ” IE in SIB3 is set to “All”.
All access classes in “Location/Registration Access Class Barred List ” IE in SIB3 are set to barred.

User Equipment:

The UE is equipped with a USIM programmed with access class x arbitrarily chosen (0-9).
The UE has a valid IMSI.

Related ICS/IXIT statements

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

Test procedure

The UE is switched on. The UE shall not perform any attach procedure as SS indicates in SIB3 that “Location/Registration Restriction Indicator” is set to “All” and all access classes in the “Location/Registration Access Class Barred List ” are set to barred.

The SS changes the restriction status in SIB3 to indicate no restriction. The UE is triggered to perform a combined attach procedure. The SS checks that UE performs a combined attach procedure.

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

Void

2

UE

The UE is powered up or switched on and attempts to initiate an attach (see ICS).

3

UE

The SS checks for 120 seconds that the UE does not transmit any ATTACH REQUEST

4

SS

The SS change the restriction status in SIB3 to no restriction

5

UE

The UE is triggered to perform a combined attach procedure either automatically or manually (see ICS).

6

SS

The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".

7

->

ATTACH REQUEST

Attach type = ‘Combined GPRS/IMSI attach’

Mobile identity = IMSI

TMSI status = no valid TMSI available

8

<-

AUTHENTICATION AND CIPHERING REQUEST

9

->

AUTHENTICATION AND CIPHERING RESPONSE

10

SS

The SS starts an integrity protection.

11

<-

ATTACH ACCEPT

Attach result = ‘Combined GPRS/IMSI attached’

Allocated P-TMSI = P-TMSI-1

P-TMSI Signature = P-TMSI-1 signature

Routing area identity = RAI-1

MS identity = TMSI-1

12

->

ATTACH COMPLETE

13

SS

The SS releases the RRC connection.

Note 1: The UE shall not initiate any combined attach procedure as “Location/Registration Restriction Indicator” IE in SIB3 is set to “All” and all access classes in Location/Registration Access Class Barred List in SIB3 are set to barred.

Specific message contents

None.

12.2.2.10.5 Test requirements

1) At step 3 the UE shall not transmit any ATTACH REQUEST message.

2) At step 7 the UE shall transmit an ATTACH REQUEST message.