9.5 MM connection
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
9.5.1 Introduction
[tbd]
9.5.2 MM connection / establishment in security mode
9.5.2.1 Definition
9.5.2.2 Conformance requirement
1) The UE shall be able to correctly set up an MM connection in a Mobile Originating CM connection attempt and send a CM SERVICE REQUEST message with CKSN information element as stored in the USIM and Mobile Identity information element set to the TMSI.
2) The UE shall be able to interpret security mode setting as acceptance of its CM service request i.e. send a CM message.
References
TS 24.008 clause 4.5.1.1.
9.5.2.3 Test purpose
To verify that the UE can correctly set up an MM connection in an origination and interpret security mode setting as acceptance of its CM service request.
9.5.2.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE has a valid TMSI. It is "idle updated".
Related ICS/IXIT statements
None.
Test Procedure
A mobile originating CM connection is initiated. After the UE has sent the CM SERVICE REQUEST message to the SS, an authentication procedure and a security mode setting procedure are performed. Then, the UE sends a CM message and the SS clears the call and releases the RRC CONNECTION.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
A MO CM connection is attempted. |
||
|
2 |
Void |
|||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
CM SERVICE REQUEST |
||
|
6 |
|
AUTHENTICATION REQUEST |
||
|
7 |
|
AUTHENTICATION RESPONSE |
||
|
8 |
SS |
The SS starts ciphering and integrity protection. |
||
|
9 |
Void |
|||
|
A10 |
|
SETUP |
The SS expects a SETUP message from the UE, when a call is attempted |
|
|
A11 |
|
RELEASE COMPLETE |
"Cause" IE: "unassigned number". |
|
|
B10 |
|
REGISTER |
The SS expects a REGISTER message from the UE, when a Non call related Supplementary service is attempted |
|
|
B11 |
|
RELEASE COMPLETE |
||
|
C10 |
|
CP-DATA |
The SS expects a CP-DATA message from the UE, when SMS is attempted |
|
|
C11 |
|
CP-ACK |
||
|
C12 |
|
CP-DATA |
||
|
C13 |
|
CP-ACK |
||
|
14 |
SS |
The SS releases the RRC connection. |
||
|
15 |
Void |
|||
|
Note: Only one set of messages are applicable at step A10, B10 or C10 based on the type of CS call that is being made |
||||
Specific message contents
None.
9.5.2.5 Test requirement
At step 5 the UE shall send the CM SERVICE REQUEST message to the SS.
At step A10 or B10 or C10 the UE shall send a CM message and the SS shall release the RRC connection (step 14).
9.5.3 Void
9.5.4 MM connection / establishment rejected
9.5.4.1 Definition
9.5.4.2 Conformance requirement
If a CM SERVICE REJECT message is received by the mobile station, timer T3230 shall be stopped, the requesting CM sublayer entity informed. Then the mobile station shall proceed as follows:
– If the cause value is not #4 or #6 the MM sublayer returns to the previous state (the state where the request was received). Other MM connections shall not be affected by the CM SERVICE REJECT message.
References
TS 24.008 clause 4.5.1.1.
9.5.4.3 Test purpose
To verify that the UE stops timer T3230, informs the requesting CM sublayer entity and returns to the previous state.
9.5.4.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE has a valid TMSI. It is "idle updated".
Related ICS/IXIT statements
None.
Test Procedure
A mobile originating CM connection is attempted. After the UE has sent the CM SERVICE REQUEST message to the SS, the SS responds with a CM SERVICE REJECT message with reject cause "requested service option not subscribed". It is checked that the UE does not send a layer 3 message via the rejected MM connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
A MO CM connection is attempted |
||
|
2 |
Void |
|||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
CM SERVICE REQUEST |
A mobile originating CM connection is attempted |
|
|
6 |
|
CM SERVICE REJECT |
"Reject cause" IE: "requested service option not subscribed". |
|
|
7 |
SS |
The UE shall not send a layer 3 message. This is checked during 5 s. Note: During this period, a new mobile originating CM connection should not be attempted, since then UE would send a new CM SERVICE REQUEST. |
||
|
8 |
SS |
SS releases the RRC connection. |
||
Specific message contents
None.
9.5.4.5 Test requirement
The UE shall attempt MO CM connection (step 1).
At step 5 the UE shall send a CM SERVICE REQUEST.
After step 6 the UE shall not send a layer 3 message.
9.5.5 MM connection / establishment rejected cause 4
9.5.5.1 Definition
9.5.5.2 Conformance requirement
The CM SERVICE REQUEST message contains the:
– mobile identity according to clause 10.5.1.4;
– mobile station classmark 2;
– ciphering key sequence number; and
– CM service type identifying the requested type of transaction (e.g. mobile originating call establishment, emergency call establishment, short message service, supplementary service activation, location services)
…
If a CM SERVICE REJECT message is received by the mobile station, timer T3230 shall be stopped, the requesting CM sublayer entity informed. Then the mobile station shall proceed as follows:
…
– If cause value #4 is received, the mobile station aborts any MM connection, deletes any TMSI, LAI and ciphering key sequence number in the SIM, changes the update status to NOT UPDATED (and stores it in the SIM according to clause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. If subsequently the RR connection is released or aborted, this will force the mobile station to initiate a normal location updating). Whether the CM request shall be memorized during the location updating procedure, is a choice of implementation.
References
TS 24.008 clause 4.5.1.1.
9.5.5.3 Test purpose
To verify that the UE can correctly set up an MM connection in a Mobile Originating CM connection attempt and send a CM SERVICE REQUEST message with CKSN information element as stored in the USIM and Mobile Identity information element set to TMSI.
To verify that the UE, when receiving a CM SERVICE REJECT message with reject cause "IMSI unknown in VLR" shall wait for the network to release the RRC connection.
To verify that the UE shall then perform a normal location updating procedure.
9.5.5.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE has a valid TMSI. It is "idle updated".
Related ICS/IXIT statements
None.
Test Procedure
A mobile originating CM connection is attempted. After the UE has sent the CM SERVICE REQUEST message to the SS, the SS responds with a CM SERVICE REJECT message with reject cause "IMSI unknown in VLR". On receipt of this message, the UE shall delete any TMSI, LAI, cipher key and cipher key sequence number. The RRC CONNECTION is released. It is checked that the UE performs a normal location updating procedure.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
A MO CM connection is attempted. |
||
|
2 |
Void |
|||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
CM SERVICE REQUEST |
CKSN = initial value, Mobile identity = TMSI. |
|
|
6 |
|
CM SERVICE REJECT |
"Reject cause" = "IMSI unknown in VLR". |
|
|
7 |
SS |
SS releases the RRC connection. |
||
|
8 |
Void |
|||
|
9 |
SS |
SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to: "Registration". |
||
|
10 |
Void |
|||
|
11 |
Void |
|||
|
12 |
|
LOCATION UPDATING REQUEST |
"Ciphering key sequence number" = "No key is available". "Mobile identity" = IMSI. "Location area identification" = deleted LAI (the MCC and MNC hold the previous values, the LAC is coded FFFE). |
|
|
13 |
|
AUTHENTICATION REQUEST |
||
|
14 |
|
AUTHENTICATION RESPONSE |
||
|
14a |
|
SECURITY MODE COMMAND |
||
|
14b |
|
SECURITY MODE COMPLETE |
||
|
15 |
|
LOCATION UPDATING ACCEPT |
"Mobile identity" = new TMSI. |
|
|
16 |
|
TMSI REALLOCATION COMPLETE |
||
|
17 |
SS |
SS releases the RRC connection. |
||
|
18 |
Void |
|||
Specific message contents
None.
9.5.5.5 Test requirement
1) The UE shall attempt MO CM connection (at step 1) and at step 5 the UE shall send a CM SERVICE REQUEST message with CKSN information element as stored in the USIM and Mobile Identity information element set to the TMSI.
2) At step 6 the SS should send a CM SERVICE REJECT message with reject cause "IMSI unknown in VLR", and at step 9 the UE shall initiate RRC connection establishment with establishment cause set to "Registration".
3) At step 12 the UE send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and the Location Updating type set to "deleted LAI".
9.5.6 MM connection / expiry T3230
9.5.6.1 Definition
9.5.6.2 Conformance requirement
At T3230 expiry (i.e. no response is given but an RRC connection is available) the MM connection establishment shall be aborted.
References
TS 24.008 clauses 4.5.1.2 and 11.2.
9.5.6.3 Test purpose
To verify that at T3230 expiry, the UE aborts the MM-connection establishment.
9.5.6.4 Method of test
Initial conditions
– System Simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE has a valid TMSI. It is "idle updated".
Related ICS/IXIT statements
None.
Test Procedure
A mobile originating CM connection is attempted. After the UE has sent the CM SERVICE REQUEST message to the SS, the SS waits for expiry of timer T3230. It is checked that the UE send a MM STATUS message and waits for the release of the RRC-connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
A MO CM connection is attempted. |
||
|
2 |
|
RRC CONNECTION REQUEST |
||
|
3 |
|
RRC CONNECTION SETUP |
||
|
4 |
|
RRC CONNECTION SETUP COMPLETE |
||
|
5 |
|
CM SERVICE REQUEST |
||
|
6 |
SS |
The SS waits for expiry of timer T3230. |
||
|
7 |
|
CM SERVICE ACCEPT |
||
|
8 |
|
MM STATUS |
"Reject cause" IE is "message type not compatible with protocol state". |
|
|
9 |
|
RRC CONNECTION RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
|
|
10 |
|
RRC CONNECTION RELEASE COMPLETE |
||
Specific message contents
None.
9.5.6.5 Test requirement
The UE shall attempt MO CM connection (step 1).
At step 8 the UE shall send a MM STATUS message.
9.5.7 MM connection / abortion by the network
9.5.7.1 MM connection / abortion by the network / cause #6
9.5.7.1.1 Definition
9.5.7.1.2 Conformance requirement
At the receipt of the ABORT message the mobile station shall abort any MM connection establishment or call re-establishment procedure and release all MM connections (if any). If cause value #6 is received the mobile station shall delete any TMSI, LAI and ciphering key sequence number stored in the SIM, set the update status to ROAMING NOT ALLOWED (and store it in the SIM according to clause 4.1.2.2) and consider the SIM invalid until switch off or the SIM is removed. As a consequence the mobile station enters state MM IDLE, substate NO IMSI after the release of the RR connection.
The mobile station shall then wait for the network to release the RR connection – see clause 4.5.3.1.
Reference(s)
TS 24.008 clause 4.3.5.2.
9.5.7.1.3 Test purpose
To check that upon reception of an ABORT message with cause #6 during call establishment:
– the UE does not send any layer 3 message;
– after reception of an ABORT message and after having been deactivated and reactivated, the UE performs location updating using its IMSI as mobile identity and indicates deleted LAI and CKSN;
– the UE does not perform location updating, does not answer to paging with TMSI, rejects any request for mobile originating call except emergency call, does not perform IMSI detach;
– the UE accepts a request for emergency call.
9.5.7.1.4 Method of test
Initial Conditions
– System Simulator:
– 2 cells, default parameters.
– User Equipment:
– the UE has a valid TMSI, CKSN and CK, IK. It is "idle updated" on cell B.
Related ICS/IXIT Statement(s)
USIM removal possible while UE is powered Yes/No.
Switch off on button Yes/No.
Support of emergency speech call Yes/No.
Test procedure
A mobile originating CM connection is attempted. Upon reception of the AUTHENTICATION RESPONSE message, the SS sends an ABORT message with cause #6. The SS waits for 5 s. The UE shall not send any layer 3 message. The SS releases the RRC connection.
The SS checks that the UE has entered the state MM IDLE substate NO IMSI, i.e. does not perform normal location updating, does not perform periodic updating, does not respond to paging, rejects any requests from CM entities except emergency calls and does not perform IMSI detach if deactivated.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
The following messages are sent and shall be received on cell B |
||||
|
1 |
UE |
A mobile originating CM connection is attempted. |
||
|
2 |
Void |
|||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
CM SERVICE REQUEST |
CKSN = initial value, Mobile identity = TMSI |
|
|
6 |
|
AUTHENTICATION REQUEST |
||
|
7 |
|
AUTHENTICATION RESPONSE |
||
|
8 |
|
ABORT |
"reject cause" = #6. |
|
|
9 |
SS |
The SS waits for 5 s. |
||
|
10 |
UE |
The UE shall not send any layer 3 message during that time. |
||
|
11 |
SS |
SS releases the RRC connection. |
||
|
12 |
Void |
|||
|
The following messages are sent and shall be received on cell A. |
||||
|
13 |
SS |
Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "non-suitable cell". (see note) If PS mode: a routing area updating procedure should be rejected with cause “GPRS services not allowed”. |
||
|
14 |
UE |
The UE performs cell reselection according to procedure as specified in (this however is not checked until step 27). The UE shall not initiate an RRC connection establishment on cell A or on cell B. |
||
|
15 |
SS |
The SS waits at least 7 minutes for a possible periodic updating. |
||
|
16 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. |
||
|
17 |
|
PAGING TYPE 1 |
"UE identity" IE contains TMSI. Paging Cause: Terminating Conversational Call. |
|
|
18 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. This is verified during 3 s. |
||
|
19 |
UE |
A MO CM connection is attempted. |
||
|
20 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. This is checked during 30 s. |
||
|
21 |
UE |
If the UE supports emergency speech call (see ICS), an emergency call is attempted. |
||
|
22 |
SS |
SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to: "Emergency call". |
||
|
23 |
Void |
|||
|
24 |
Void |
|||
|
25 |
|
CM SERVICE REQUEST |
"CM service type": Emergency call establishment. CKSN = No key is available, Mobile identity = IMEI |
|
|
26 |
|
CM SERVICE ACCEPT |
||
|
27 |
|
EMERGENCY SETUP |
||
|
28 |
|
RELEASE COMPLETE |
"Cause" = unassigned number. |
|
|
29 |
SS |
SS releases the RRC connection. |
||
|
30 |
Void |
|||
|
31 |
UE |
If possible (see ICS) USIM detachment is performed. Otherwise if possible (see ICS) switch off is performed. Otherwise the power is removed. A Detach Request can be received in PS mode. |
||
|
32 |
UE |
The UE shall not initiate an RRC connection establishment on cell A or on cell B. This is checked during 3 s. |
||
|
33 |
UE |
Depending on what has been performed in step 31 the UE is brought back to operation. The subsequent GMM attach should be rejected if received in the PS mode. |
||
|
34 |
SS |
SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to: "Registration". |
||
|
35 |
Void |
|||
|
36 |
Void |
|||
|
37 |
|
LOCATION UPDATING REQUEST |
"location updating type" = normal, "CKSN" = no key available, "Mobile Identity" = IMSI, "LAI" = deleted LAI (the MCC and MNC hold the previous values, the LAC is coded FFFE). |
|
|
38 |
|
AUTHENTICATION REQUEST |
"CKSN" = CKSN1. |
|
|
39 |
|
AUTHENTICATION RESPONSE |
||
|
39a |
SS |
The SS starts integrity protection |
||
|
40 |
|
LOCATION UPDATING ACCEPT |
"Mobile Identity" = TMSI. |
|
|
41 |
|
TMSI REALLOCATION COMPLETE |
||
|
42 |
SS |
SS releases the RRC connection. |
||
|
43 |
Void |
|||
|
NOTE: The definitions for "Serving cell" and "non-suitable cell" are specified in TS 34.108 clause 6.1 "Reference Radio Conditions for signalling test cases only". |
||||
Specific message contents
None.
9.5.7.1.5 Test requirement
1) At step 10 the UE shall not send any layer 3 message.
2)
2.1 At step 14 the UE shall not initiate an RRC connection establishment (not perform normal location updating).
2.2 At step 16 the UE shall not initiate an RRC connection establishment.(not perform periodic location updating).
2.3 At step 18 the UE shall not initiate an RRC connection establishment (not respond to paging with TMSI).
2.4 At step 20 the UE shall not initiate an RRC connection establishment (reject any request for Mobile Originating call establishment).
2.5 At step 32 the UE shall not initiate an RRC connection establishment.(not perform IMSI detach).
3) At step 22 the UE shall initiate RRC connection establishment with the establishment cause set to "emergency call".
4) At step 37 the UE send a LOCATION UPDATING REQUEST message with the Mobile Identity IE set to its IMSI, CKSN IE set to "no key is available" and the Location Updating type set to "deleted LAI".
9.5.7.2 MM connection / abortion by the network / cause not equal to #6
9.5.7.2.1 Definition
9.5.7.2.2 Conformance requirement
At the receipt of the ABORT message the mobile station shall abort any MM connection establishment or call re-establishment procedure and release all MM connections (if any). If cause value #6 is received the mobile station shall delete any TMSI, LAI and ciphering key sequence number stored in the USIM, set the update status to ROAMING NOT ALLOWED (and store it in the USIM according to TS 24.008 clause 4.1.2.2) and consider the USIM invalid until switch off or the USIM is removed. As a consequence the mobile station enters state MM IDLE, substate NO IMSI after the release of the RR connection.
The mobile station shall then wait for the network to release the RR connection – see TS 24.008 clause 4.5.3.1.
Reference(s)
TS 24.008 clause 4.3.5.
9.5.7.2.3 Test purpose
To check that when multiple MM connections are established, the UE releases all MM connections upon reception of an ABORT message, in the case when the two MM connections are established for a mobile originating call and a non call related supplementary service operation.
To check that the TMSI is not deleted from UE after reception of ABORT message with cause another than #6.
9.5.7.2.4 Method of test
Initial Conditions
– System Simulator:
– 1 cell, default parameters.
– T3212 is set to 6 minutes.
– User Equipment:
– the UE is in state U10 of a mobile originating call.
Related ICS/IXIT Statement(s)
The UE supports a non call related supplementary service operation during an active call Yes/No.
Test procedure
A non call related supplementary service operation is attempted at the UE. Upon reception of the REGISTER message, the SS sends an ABORT message with cause # 17. The SS waits for 5 s. The UE shall not send any layer 3 message. The SS releases the RRC connection. The UE shall perform periodic location updating 6 minutes after the SS releases the RRC connection. TMSI shall be used as Mobile Identity in LOCATION UPDATING REQUEST message.
Expected Sequence
This procedure is performed if the UE supports non call related supplementary service operation.
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
A non call related supplementary service operation is attempted at the UE. |
||
|
2 |
Void |
|||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
CM SERVICE REQUEST |
The SS verifies that the IE " CM service type" in the received CM SERVICE REQUEST is set to "Supplementary service activation". |
|
|
6 |
|
CM SERVICE ACCEPT |
||
|
7 |
|
REGISTER |
||
|
8 |
|
ABORT |
"reject cause" = #17. |
|
|
9 |
SS |
The SS waits for 5 seconds. The UE shall not send any layer 3 message during that time. |
||
|
9a |
Void |
|||
|
10 |
Void |
|||
|
11 |
SS |
The UE indicates the signalling connection release. The SS releases the RRC connection. |
||
|
12 |
Void |
|||
|
13 |
SS |
The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST is set to "Registration". This message shall be sent by the UE between 5 minutes 45s and 6 minutes 15s after step 11. |
||
|
14 |
|
LOCATION UPDATING REQUEST |
"Location updating type" = periodic updating, "Mobile Identity" = TMSI |
|
|
15 |
|
LOCATION UPDATING ACCEPT |
"Mobile identity" = TMSI. |
|
|
16 |
SS |
The SS releases the RRC connection. |
||
Specific message contents
None.
9.5.7.2.5 Test requirement
After step 8 the UE shall release all MM connections.
After step 12 the UE shall perform periodic location updating with TMSI used as Mobile Identity.
9.5.8 MM connection / follow-on request pending
9.5.8.1 MM connection / follow-on request pending / test 1
9.5.8.1.1 Definition
9.5.8.1.2 Conformance requirement
The UE shall not attempt to establish a new MM connection after location updating on the same RRC connection if not allowed by the network.
Reference(s)
TS 24.008 clause 4.4.4.6.
9.5.8.1.3 Test purpose
To check that when the network does not include the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE that has a CM application request pending does not attempt to establish a new MM connection on that RRC connection.
9.5.8.1.4 Method of test
Initial Conditions
– System Simulator:
– 1 cell, ATT flag is set to "MSs in the cell shall apply IMSI attach and detach procedure".
– User Equipment:
– the UE has a valid TMSI and is deactivated.
Related ICS/IXIT Statement(s)
None.
Test procedure
The UE is activated and a CM connection is attempted during the location updating procedure. The SS does not include the follow on proceed information element in the LOCATION UPDATING ACCEPT message. The SS waits for at least 8 s. The UE shall not send any layer 3 message for 8 s.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
The UE is activated. |
||
|
2 |
|
RRC CONNECTION REQUEST |
"Establishment cause": Registration. |
|
|
3 |
|
RRC CONNECTION SETUP |
||
|
4 |
|
RRC CONNECTION SETUP COMPLETE |
||
|
5 |
|
LOCATION UPDATING REQUEST |
location updating type = IMSI attach. Then the SS waits for 15 s. During this delay a CM connection is attempted. |
|
|
6 |
|
LOCATION UPDATING ACCEPT |
follow on proceed IE not included. |
|
|
7 |
SS |
The SS wait for at least 8 s. |
||
|
8 |
UE |
The UE shall not send any layer 3 message for 8 s after reception of the LOCATION UPDATING ACCEPT message. |
||
|
9 |
|
RRC CONNECTION RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
|
|
10 |
|
RRC CONNECTION RELEASE COMPLETE |
||
Specific message contents
None.
9.5.8.1.5 Test requirement
After step 8 the UE shall not send any layer 3 messages.
9.5.8.2 MM connection / follow-on request pending / test 2
9.5.8.2.1 Definition
9.5.8.2.2 Conformance requirement
A UE supporting the follow-on request procedure and having a CM connection request pending shall correctly establish an MM connection following a location update when allowed by the network.
Reference(s)
TS 24.008 clause 4.4.4.6.
9.5.8.2.3 Test purpose
To check that when the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE that supports the follow on request procedure and that has a CM application request pending establishes successfully a new MM connection on that RRC connection.
9.5.8.2.4 Method of test
Initial Conditions
– System Simulator:
– 1 cell, ATT flag is set to "MSs in the cell shall apply IMSI attach and detach procedure".
– User Equipment:
– the UE has a valid TMSI and is deactivated.
Related ICS/IXIT Statement(s)
UE supports the follow on request procedure Yes/No.
Test procedure
The UE is activated and a CM connection is attempted during the location updating procedure. The SS includes the follow on proceed information element in the LOCATION UPDATING ACCEPT message. The SS waits for at least 8 s.
If the UE supports the follow on request procedure:
– the UE shall send a CM SERVICE REQUEST. Upon reception of that message, the SS sends a CM SERVICE ACCEPT message. The UE shall send an initial CM message. Upon reception of that message, the SS releases the RRC connection.
If the UE does not support the follow on request procedure:
– the UE shall not send any layer 3 message for 8 s.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
The UE is activated. |
||
|
2 |
|
RRC CONNECTION REQUEST |
"Establishment cause": Registration. |
|
|
3 |
|
RRC CONNECTION SETUP |
||
|
4 |
|
RRC CONNECTION SETUP COMPLETE |
||
|
5 |
|
LOCATION UPDATING REQUEST |
Location updating type = IMSI attach. Then the SS waits for 15 s. During this delay a CM connection is attempted. |
|
|
6 |
|
LOCATION UPDATING ACCEPT |
follow on proceed IE included. |
|
|
If the UE supports the follow on request procedure (see ICS) steps A7 to A9 are performed, otherwise steps B7 to B8 are performed. |
||||
|
A7 |
|
CM SERVICE REQUEST |
||
|
A8 |
|
CM SERVICE ACCEPT |
||
|
A9 |
|
An initial CM message |
||
|
B7 |
SS |
The SS wait for at least 8 s. |
||
|
B8 |
UE |
The UE shall not send any layer 3 message for 8 s after reception of the LOCATION UPDATING ACCEPT message. |
||
|
10 |
|
RRC CONNECTION RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
|
|
11 |
|
RRC CONNECTION RELEASE COMPLETE |
||
Specific message contents
None.
9.5.8.2.5 Test requirement
After step 6:
The UE shall send a CM SERVICE REQUEST if the UE supports the follow on request procedure.
The UE shall not send any layer 3 message if the UE does not support the follow on request procedure.
9.5.8.3 MM connection / follow-on request pending / test 3
9.5.8.3.1 Definition
9.5.8.3.2 Conformance requirement
1) The UE shall not set the follow on proceed IE in a LOCATION UPDATING REQUEST message if no MM connection request is pending.
2) When the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE that has no CM application request pending shall not attempt to establish a new MM connection on that RRC connection.
3) The UE shall correctly handle a CM connection established by the network on the RRC connection that was used for the location updating procedure.
Reference(s)
TS 24.008 clause 4.4.4.6.
9.5.8.3.3 Test purpose
1) To check that a UE that has no CM application request pending sets the follow on proceed IE to No follow-on request pending in a LOCATION UPDATING REQUEST message.
2) To check that when the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE that has no CM application request pending does not attempt to establish a new MM connection on that RRC connection.
3) To check that the UE accepts establishment by the network of a new MM connection on the existing RRC connection.
9.5.8.3.4 Method of test
Initial Conditions
– System Simulator:
– 1 cell, ATT flag is set to "MSs in the cell shall apply IMSI attach and detach procedure".
– User Equipment:
– the UE has a valid TMSI and is deactivated.
Related ICS/IXIT Statement(s)
Supported services on TCH.
Test procedure
The UE is activated. The UE performs location updating. The UE shall set the follow on proceed IE to No follow-on request pending in the LOCATION UPDATING REQUEST message. The SS includes the follow on proceed IE in the LOCATION UPDATING ACCEPT message. The SS waits for 5 s. The UE shall not send any layer 3 message for 5 s. The SS sends a SETUP message to the UE requesting a basic service supported by the UE. The UE shall send either a CALL CONFIRMED message if it supports a service on TCH or a RELEASE COMPLETE with cause #88.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
The UE is activated. |
||
|
2 |
|
RRC CONNECTION REQUEST |
"Establishment cause": Registration. |
|
|
3 |
|
RRC CONNECTION SETUP |
||
|
4 |
|
RRC CONNECTION SETUP COMPLETE |
||
|
5 |
|
LOCATION UPDATING REQUEST |
"Location updating type" = IMSI attach. The FOR bit is set to No follow-on request pending. |
|
|
6 |
|
LOCATION UPDATING ACCEPT |
follow on proceed IE is included. |
|
|
7 |
SS |
The SS wait for 5 s. |
||
|
8 |
UE |
The UE shall not send any layer 3 message for 5 s after reception of the LOCATION UPDATING ACCEPT message. |
||
|
9 |
|
SETUP |
||
|
If the UE supports a basic service on TCH. |
||||
|
A10 |
|
CALL CONFIRMED |
||
|
If the UE does not support any basic service on TCH. |
||||
|
B10 |
|
RELEASE COMPLETE |
cause #88. |
|
|
11 |
|
RRC CONNECTION RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
|
|
12 |
|
RRC CONNECTION RELEASE COMPLETE |
||
Specific message contents
None.
9.5.8.3.5 Test requirement
At step 8 the UE shall not send any layer 3 message.
After step 9:
The UE shall send CALL CONFIRMED message if the UE supports a basic service on TCH.
The UE shall send RELEASE COMPLETE message if the UE does not support a basic service on TCH.
9.5.9 MM connection / abnormal cases / CS domain barred because of domain specific access control
9.5.9.1 Definition
This test is applicable for Rel-5 UEs supporting DSAC and Rel-6 or later UEs.
9.5.9.2 Conformance requirement
TS 24.008 clause 4.1.1.2.2
If the PS or CS domain is barred because of domain specific access control, a GPRS MS operating in mode A or B in a network that operates in mode II or III shall use the MM specific procedures or GMM specific procedures, respectively, in the domain which is unbarred. If the MS detects that a domain changes from barred to unbarred, it shall behave as specified in subclauses 4.4.4.9, 4.5.1.2, 4.7.3.1.5, 4.7.5.1.5, and 4.7.13.5.
TS 24.008 clause 4.5.1.2
e) Access barred because of CS domain specific access control
The MM connection establishment shall not be initiated. The MS stays in the current serving cell and applies normal cell reselection process. The MM connection establishment may be initiated by CM layer if it is still necessary, i.e. when access is granted or because of a cell change.
Reference
3GPP TS 24.008 clause 4.1.1.2.2 , 4.5.1.2
9.5.9.3 Test purpose
To test the behaviour of the UE if the CS domain is changed from unbarred to barred because of domain specific access control in a network that operates mode II.
9.5.9.4 Method of test
Initial condition
An access class x (0-15) is arbitrarily chosen. The USIM is programmed with this access class x. The UE is informed that the CS domain specific access class x is barred.
System Simulator:
One cell operating in network operation mode II.
CS domain specific access class x is barred .
User Equipment:
The UE has a valid TMSI and is in idle state .
Related ICS/IXIT statements
Support of DSAC Yes/No.
Test procedure
- The CS domain specific access class x is barred: a Mobile Originating CM connection is attempted, but: the MM connection establishment shall not be initiated.
- The SS informs the UE by paging that the CS domain specific access class x is not barred: a Mobile Originating CM connection is attempted and the MM connection establishment is initiated, the UE sends a CM SERVICE REQUEST message. Then the UE sends a CM message and the SS clears the call and releases the RRC connection.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
UE |
An MO CM connection is attempted. |
||
|
2 |
UE |
Check that no CM service request is sent as CS domain specific access class x is barred . |
||
|
3 |
SS |
The SS informs the UE by paging that the CS domain changes from barred to unbarred. |
||
|
4 |
UE |
An MO CM connection is attempted. |
||
|
5 |
SS |
The IE "Establishment cause" in the received RRC CONNECTION REQUEST is not checked. |
||
|
6 |
|
CM SERVICE REQUEST |
||
|
7 |
|
AUTHENTICATION REQUEST |
||
|
8 |
|
AUTHENTICATION RESPONSE |
||
|
9 |
SS |
The SS starts ciphering and integrity protection. |
||
|
A10 |
|
SETUP |
The SS expects a SETUP message from the UE, when a call is attempted |
|
|
A11 |
|
RELEASE COMPLETE |
"Cause" IE: "unassigned number". |
|
|
B10 |
|
REGISTER |
The SS expects a REGISTER message from the UE, when a Non call related Supplementary service is attempted |
|
|
B11 |
|
RELEASE COMPLETE |
||
|
C10 |
|
CP-DATA |
The SS expects a CP-DATA message from the UE, when SMS is attempted |
|
|
C11 |
|
CP-ACK |
||
|
C12 |
|
CP-DATA |
||
|
C13 |
|
CP-ACK |
||
|
12 |
SS |
The SS releases the RRC connection. |
||
|
Note: Only one set of messages are applicable at step A10, B10 or C10 based on the type of CS call that is being made. |
||||
Specific message contents
None.
9.5.9.5 Test requirements
At step 2, the CS domain specific access class x is barred , the UE shall:
– not send a CM SERVICE REQUEST message.
At step 6, the CS domain specific access class x is not barred, the UE shall:
– send a CM SERVICE REQUEST message.