26.7.5 MM connection
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
26.7.5.1 Introduction
[tbd]
26.7.5.2 MM connection / establishment with cipher and repeated FACCH
26.7.5.2.1 Conformance requirement
The Mobile Station 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 SIM and Mobile Identity information element set to the TMSI.
The Mobile Station shall be able to interpret cipher mode setting as acceptance of its CM service request i.e. send a CM message.
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.5.1.1;
The MS shall, when receiving a downlink FACCH block, always attempt to decode it without combining with any previously received FACCH block.
If the current FACCH block is successfully decoded and an identical FACCH block was previously received (successfully decoded and spaced in time from the current FACCH block as specified in sub-clause 10.2), the MS shall not send the LAPDm frame of the current FACCH block to the LAPDm entity.
3GPP TS 44.006 subclause 10.4;
26.7.5.2.2 Test purpose
To verify that the MS can correctly set up an MM connection in an origination and interpret cipher mode setting as acceptance of its CM service request.
To verify that the MS behaves correctly when Repeated FACCH is used by the SS for LAPDm command frames, and additionally where the MS supported repeated FACCH for LAPDm response frames.
26.7.5.2.3 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
- at least one half rate service (TSPC_AddInfo_HalfRate)
- Support of Repeated FACCH (TSPC_Repeated_FACCH)
PIXIT statements:
–
Foreseen final state of the MS
The MS has valid TMSI, CKSN. It is "idle updated".
Test Procedure
A mobile originating CM connection is initiated. After the MS has sent the CM SERVICE REQUEST message to the SS, an authentication procedure and a ciphering mode setting procedure are performed. Then, the MS sends a CM message and the SS clears the call and releases the channel.
For k=2 and k=3, the SS shall activate Repeated FACCH for LAPDm command frames on FACCH.
If the MS supports Repeated FACCH, the SS shall additionally activate Repeated FACCH for LAPDm response frames on FACCH. It is checked by the SS that the MS does not respond to identical FACCH blocks which are repeated.
If the MS does not support Repeated FACCH, the MS may respond to the identical FACCH blocks which are repeated, with a REJ frame.
This test is repeated for:
k=1;
k=2;
k=3 where the MS supports at least one half rate service.
Maximum duration of test
3 minute.
Expected sequence
Step |
Direction |
Message |
Comments |
If the MS supports Repeated FACCH (TSPC_Repeated_FACCH), the SS shall check that the MS does not respond to identical FACCH blocks which are repeated. If the MS does not support Repeated FACCH (TSPC_Repeated_FACCH), the MS may respond to the identical FACCH blocks which are repeated, with a REJ frame. |
|||
1 |
MS |
A MO CM connection is attempted. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
See specific message contents. |
4 |
MS -> SS |
CM SERVICE REQUEST |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
The SS starts deciphering. |
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
The SS starts enciphering. |
A9 |
MS -> SS |
SETUP |
|
A10 |
SS -> MS |
RELEASE COMPLETE |
"Cause" IE: "unassigned number". |
B9 |
MS -> SS |
REGISTER |
|
B10 |
SS -> MS |
RELEASE COMPLETE |
|
C9 |
MS -> SS |
CP-DATA |
|
C10 |
SS -> MS |
CP-ACK |
|
C11 |
SS -> MS |
CP-DATA |
|
C12 |
MS -> SS |
CP-ACK |
|
C13 |
SS -> MS |
RELEASE COMPLETE |
|
14 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
IMMEDIATE ASSIGNMENT
Information Element |
value/remarks |
Channel description |
k=1: SDCCH |
k=2: TCH/F |
|
k=3: TCH/H |
26.7.5.3 MM connection / establishment without cipher
26.7.5.3.1 Conformance requirement
Upon reception of the CM SERVICE ACCEPT message, the MS shall send a CM message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1.
26.7.5.3.2 Test purpose
To verify that the MS can correctly set up an MM connection in an originating CM connection establishment when ciphering mode setting is not required.
26.7.5.3.3 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
–
PIXIT statements:
–
Foreseen final state of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
A mobile originating CM connection is attempted. The MM-connection is established without invoking the ciphering mode setting procedure.
Then, the MS sends a CM message and the SS releases the channel.
Maximum duration of test
one minute.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
A MO CM connection is attempted. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
|
5 |
SS -> MS |
CM SERVICE ACCEPT |
|
A6 |
MS -> SS |
SETUP |
|
B6 |
MS -> SS |
REGISTER |
|
C6 |
MS -> SS |
CP-DATA |
|
C7 |
SS -> MS |
CP-ACK |
|
C8 |
SS -> MS |
CP-DATA |
|
C9 |
MS -> SS |
CP-ACK |
|
10 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.
26.7.5.4 MM connection / establishment rejected
26.7.5.4.1 Conformance requirement
Upon reception of a CM SERVICE REJECT message, the MS shall not send any layer 3 message, start timer T3240 and enter the "wait for network command" state.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.5.1.1.
26.7.5.4.2 Test purpose
To verify that the MS does not send a layer 3 message when the service request is rejected by the SS.
26.7.5.4.3 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
–
PIXIT statements:
–
Foreseen final state of the MS
The MS has a valid TMSI; It is "idle updated".
Test Procedure
A mobile originating CM connection is attempted. After the MS 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 MS does not send a layer 3 message.
Maximum duration of test
1 minute.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
A MO CM connection is attempted |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
|
5 |
SS -> MS |
CM SERVICE REJECT |
"Reject cause" IE: "requested service option not subscribed". |
6 |
SS |
The MS shall not send a layer 3 message. This is checked during 5 s. |
|
7 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.
26.7.5.5 MM connection / establishment rejected cause 4
26.7.5.5.1 Conformance requirement
1) The Mobile Station 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 SIM and Mobile Identity information element set to the TMSI.
2) The Mobile Station, when receiving a CM SERVICE REJECT message with reject cause "IMSI unknown in VLR" shall wait for the network to release the RR connection.
3) The Mobile Station shall then be able to perform a location updating procedure.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.5.1.1.
26.7.5.5.2 Test purpose
To verify that the MS can correctly accept a CM SERVICE REJECT message with reject cause "IMSI unknown in VLR".
26.7.5.5.3 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
–
PIXIT statements:
–
Foreseen final state of the MS
The MS has valid TMSI, CKSN. It is "idle updated".
Test Procedure
A mobile originating CM connection is attempted. After the MS 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 MS shall delete any TMSI, LAI, cipher key and cipher key sequence number. The channel is released. It is checked that the MS performs a normal location updating procedure.
Maximum duration of test
One minute.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
A MO CM connection is attempted. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
|
5 |
SS -> MS |
CM SERVICE REJECT |
"Reject cause" = "IMSI unknown in VLR". |
6 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
7 |
MS -> SS |
CHANNEL REQUEST |
"Establishment cause": Location updating. |
8 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
9 |
MS -> SS |
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). |
10 |
SS -> MS |
AUTHENTICATION REQUEST |
|
11 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
12 |
SS -> MS |
LOCATION UPDATING ACCEPT |
"Mobile identity" = new TMSI. |
13 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
14 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.
26.7.5.6 MM connection / expiry T3230
26.7.5.6.1 Conformance requirement
At T3230 expiry (i.e. no response is given but an RR connection is available) the MM connection establishment shall be aborted.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.2 and 11.2.
26.7.5.6.2 Test purpose
To verify that at T3230 expiry, the MS aborts the MM-connection establishment.
26.7.5.6.3 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
–
PIXIT statements:
–
Foreseen final state of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
A mobile originating CM connection is attempted. After the MS has sent the CM SERVICE REQUEST message to the SS, the SS waits for expiry of timer T3230. It is checked that the MS does not send a layer 3 message but waits for the release of the RR-connection.
Maximum duration of test
1 minute.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
A MO CM connection is attempted. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
|
5 |
SS |
The SS waits for expiry of timer T3230. |
|
6 |
SS -> MS |
CM SERVICE ACCEPT |
|
7 |
MS -> SS |
MM STATUS |
"Reject cause” IE is "message not compatible with the call state or not implemented". |
8 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.
26.7.5.7 MM connection / abortion by the network
26.7.5.7.1 MM connection / abortion by the network / cause #6
26.7.5.7.1.1 Conformance requirement
1) Upon reception of an ABORT message, the MS shall release any ongoing MM connection and enter the "wait for network command" state.
2) If the cause in the ABORT message was cause #6, the Mobile Station shall:
2.1 not perform normal location updating;
2.2 not perform periodic location updating;
2.3 not respond to paging with TMSI;
2.4 reject any request for Mobile Originating call establishment except Emergency call;
2.5 not perform IMSI detach if deactivated.
3) After reception of an ABORT message with cause #6, the Mobile Station, if it supports speech, shall accept a request for an emergency call by sending a Channel Request message with the establishment cause set to "emergency call".
4) After reception of an ABORT message with cause #6, the Mobile Station shall delete the stored LAI, CKSN and TMSI.
Reference(s)
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.3.5.
26.7.5.7.1.2 Test purpose
To check that upon reception of an ABORT message with cause #6 during call establishment:
– the MS does not send any layer 3 message;
– after reception of an ABORT message and after having been deactivated and reactivated, the MS performs location updating using its IMSI as mobile identity and indicates deleted LAI and CKSN;
– the MS 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 MS accepts a request for emergency call.
26.7.5.7.1.3 Method of test
Initial Conditions
System Simulator:
2 cells, default parameters.
Mobile Station:
The MS has a valid TMSI, CKSN and Kc. It is "idle updated" on cell B.
Specific PICS statements:
– On/Off switch (TSPC_Feat_OnOff)
– SIM removable without power down (TSPC_AddInfo_SIMRmv)
– Speech supported for Full rate version 1 (GSM FR) (TSPC_AddInfo_Full_rate_version_1)
PIXIT statements:
–
Foreseen final state of the MS
The MS has a valid TMSI. It is "idle updated" on cell A.
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 MS shall not send any layer 3 message. The SS releases the RR connection.
The SS checks that the MS 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.
Maximum Duration Of Test
10 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
---|---|---|---|
The following messages are sent and shall be received on cell B |
|||
1 |
MS |
A mobile originating CM connection is attempted. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
ABORT |
"reject cause" = #6. |
8 |
SS |
The SS waits for 5 s. |
|
9 |
MS |
The MS shall not send any layer 3 message during that time. |
|
10 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
The following messages are sent and shall be received on cell A. |
|||
11 |
SS |
The RF levels are changed to make the MS reselect cell A. |
|
12 |
MS |
The MS performs cell reselection according to procedure as specified in 3GPP TS 05.08 (this however is not checked until step 22). The MS shall not initiate an RR connection establishment on cell A or on cell B. |
|
13 |
SS |
The SS waits at least 7 minutes for a possible periodic updating. |
|
14 |
MS |
The MS shall not initiate an RR connection establishment on cell A or on cell B. |
|
15 |
SS -> MS |
PAGING REQUEST TYPE 1 |
"Mobile identity" IE contains TMSI. |
16 |
MS |
The MS shall not initiate an RR connection establishment on cell A or on cell B. This is verified during 3 s. |
|
17 |
MS |
A MO CM connection is attempted. |
|
18 |
MS |
The MS shall not initiate an RR connection establishment on cell A or on cell B. This is checked during 3 s. |
|
19 |
MS |
If the MS supports speech (see PICS), an emergency call is attempted. |
|
20 |
MS -> SS |
CHANNEL REQUEST |
"Establishment cause": Emergency call. |
21 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
22 |
MS -> SS |
CM SERVICE REQUEST |
"CM service type": Emergency call establishment. |
23 |
SS -> MS |
CM SERVICE ACCEPT |
|
24 |
MS -> SS |
EMERGENCY SETUP |
|
25 |
SS -> MS |
RELEASE COMPLETE |
"Cause" = unassigned number. |
26 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
27 |
MS |
If possible (see PICS) SIM detachment is performed. Otherwise if possible (see PICS) switch off is performed. Otherwise the power is removed. |
|
28 |
MS |
The MS shall not initiate an RR connection establishment on cell A or on cell B. This is checked during 3 s. |
|
29 |
MS |
Depending on what has been performed in step 29 the MS is brought back to operation. |
|
30 |
MS -> SS |
CHANNEL REQUEST |
"Establishment cause": Location updating. |
31 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
32 |
MS -> SS |
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). |
33 |
SS -> MS |
AUTHENTICATION REQUEST |
"CKSN" = CKSN1. |
34 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
35 |
SS -> MS |
LOCATION UPDATING ACCEPT |
"Mobile Identity" = TMSI. |
36 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
37 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.
26.7.5.7.2 MM connection / abortion by the network / cause not equal to #6
26.7.5.7.2.1 Conformance requirement
Upon reception of an ABORT message, the MS shall release any ongoing MM connection and enter the "wait for network command" state.
Reference(s)
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.3.5.
26.7.5.7.2.2 Test purpose
1. When multiple MM connections are established, the MS releases all MM connections upon reception of an ABORT message, in the case when the two MM connections are established for a mobile terminating call and a non call related supplementary service operation.
2. The TMSI isn’t deleted from MS after reception of ABORT message with cause another than #6.
26.7.5.7.2.3 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
T3212 is set to 6 minutes.
Mobile Station:
The MS is in state U10 of a mobile terminating call.
Specific PICS statements:
–
PIXIT statements:
–
Foreseen final state of the MS
The MS has a valid TMSI. It is "idle updated".
Test procedure
A non call related supplementary service operation is attempted at the MS. Upon reception of the REGISTER message, the SS sends an ABORT message with cause # 17. The SS waits for 5 s. The MS shall not send any layer 3 message. The SS releases the RR connection. The MS shall perform periodic location updating 6 minutes after the CHANNEL RELEASE message. TMSI shall be used as an MS Identity in LOCATION UPDATING REQUEST
Maximum Duration Of Test
15 minutes.
Expected Sequence
This procedure is performed if the MS supports non call related supplementary service operation.
Step |
Direction |
Message |
Comments |
1 |
MS |
A non call related supplementary service operation is attempted at the MS. |
|
2 |
MS -> SS |
CM SERVICE REQUEST |
|
3 |
SS -> MS |
CM SERVICE ACCEPT |
|
4 |
MS -> SS |
REGISTER |
|
5 |
SS -> MS |
ABORT |
"reject cause" = #17. |
6 |
SS |
The SS waits for 5 seconds. The MS shall not send any layer 3 message during that time. |
|
7 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
8 |
MS -> SS |
CHANNEL REQUEST |
"Establishment cause": Location updating This message shall be sent by the MS between 5minutes 45s and 6minutes 15s after step 7. |
9 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
10 |
MS -> SS |
LOCATION UPDATING REQUEST |
"location updating type": periodic updating. Mobile identity IE specifies the TMSI of the MS. |
11 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
12 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.
26.7.5.8 MM connection / follow-on request pending
26.7.5.8.1 MM connection / follow-on request pending / test 1
26.7.5.8.1.1 Conformance requirement
The MS shall not attempt to establish a new MM connection after location updating on the same RR connection if not allowed by the network.
Reference(s)
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.4.4.6.
26.7.5.8.1.2 Test purpose
To check that when the network does not include the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a MS that has a CM application request pending does not attempt to establish a new MM connection on that RR connection.
26.7.5.8.1.3 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".
Mobile Station:
The MS has a valid TMSI and is deactivated.
Specific PICS statements:
–
PIXIT statements:
–
Foreseen final state of the MS
The MS has a valid TMSI. It is "idle updated".
Test procedure
The MS 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 seconds. The MS shall not send any layer 3 message for 8 seconds.
Maximum Duration of Test
60 s.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is activated. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
LOCATION UPDATING REQUEST |
location updating type = IMSI attach. Then the SS waits for 15 s. During this delay a CM connection is attempted. |
5 |
SS -> MS |
LOCATION UPDATING ACCEPT |
follow on proceed IE not included. |
6 |
SS |
The SS wait for at least 8 seconds. |
|
7 |
MS |
The MS shall not send any layer 3 message for 8 seconds after reception of the LOCATION UPDATING ACCEPT message. |
|
8 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.
26.7.5.8.2 MM connection / follow-on request pending / test 2
26.7.5.8.2.1 Conformance requirement
A MS 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)
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.4.4.6.
26.7.5.8.2.2 Test purpose
To check that when the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a MS that supports the follow on request procedure and that has a CM application request pending establishes successfully a new MM connection on that RR connection.
26.7.5.8.2.3 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".
Mobile Station:
The MS has a valid TMSI and is deactivated.
Specific PICS statements:
– follow-on request procedure (TSPC_AddInfo_followOnReq)
PIXIT statements:
–
Foreseen final state of the MS
The MS has a valid TMSI. It is "idle updated".
Test procedure
The MS 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 seconds.
If the MS supports the follow on request procedure:
The MS shall send a CM SERVICE REQUEST. Upon reception of that message, the SS sends a CM SERVICE ACCEPT message. The MS shall send an initial CM message. Upon reception of that message, the SS releases the RR connection.
If the MS does not support the follow on request procedure:
The MS shall not send any layer 3 message for 8 seconds.
Maximum Duration of Test
60 s.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is activated. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
LOCATION UPDATING REQUEST |
Location updating type = IMSI attach. Then the SS waits for 15 s. During this delay a CM connection is attempted. |
5 |
SS -> MS |
LOCATION UPDATING ACCEPT |
follow on proceed IE included. |
If the MS supports the follow on request procedure (see PICS) steps A6 to A8 are performed, otherwise steps B6 to B7 are performed. |
|||
A6 |
MS -> SS |
CM SERVICE REQUEST |
|
A7 |
SS ->MS |
CM SERVICE ACCEPT |
|
A8 |
MS -> SS |
An initial CM message |
|
B6 |
SS |
The SS wait for at least 8 seconds. |
|
B7 |
MS |
The MS shall not send any layer 3 message for 8 seconds after reception of the LOCATION UPDATING ACCEPT message. |
|
9 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.
26.7.5.8.3 MM connection / follow-on request pending / test 3
26.7.5.8.3.1 Conformance requirement
1) The MS shall not set the follow on request bit 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 MS that has no CM application request pending shall not attempt to establish a new MM connection on that RR connection.
3) The MS shall correctly handle a CM connection established by the network on the RR connection that was used for the location updating procedure.
Reference(s)
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.4.4.6.
26.7.5.8.3.2 Test purpose
1) To check that a MS that has no CM application request pending sets the Follow-On-Request bit 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 MS that has no CM application request pending does not attempt to establish a new MM connection on that RR connection.
3) To check that the MS accepts establishment by the network of a new MM connection on the existing RR connection.
26.7.5.8.3.3 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".
Mobile Station:
The MS has a valid TMSI and is deactivated.
Specific PICS statements:
– at least one MO circuit switched basic service (TSPC_AddInfo_MOsvc)
PIXIT statements:
–
Foreseen final state of the MS
The MS has a valid TMSI. It is "idle updated".
Test procedure
The MS is activated. The MS performs location updating. The MS shall set the FOR bit to No follow-on request pending in the LOCATION UPDATING REQUEST message. The SS includes the follow on proceed information element in the LOCATION UPDATING ACCEPT message. The SS waits for 5 s. The MS shall not send any layer 3 message for 5 s. The SS sends a SETUP message to the MS requesting a basic service supported by the MS. The MS shall send either a CALL CONFIRMED message if it supports a service on TCH or a RELEASE COMPLETE with cause #88.
Maximum Duration of Test
20 s.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is activated. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
LOCATION UPDATING REQUEST |
"Location updating type" = IMSI attach. The FOR bit is set to No follow-on request pending. |
5 |
SS -> MS |
LOCATION UPDATING ACCEPT |
follow on proceed IE is included. |
6 |
SS |
The SS wait for 5 s. |
|
7 |
MS |
The MS shall not send any layer 3 message for 5 s after reception of the LOCATION UPDATING ACCEPT message. |
|
8 |
SS -> MS |
SETUP |
|
If the MS supports a basic service on TCH. |
|||
A9 |
MS -> SS |
CALL CONFIRMED |
|
If the MS does not support any basic service on TCH. |
|||
B9 |
MS -> SS |
RELEASE COMPLETE |
cause #88. |
10 |
SS -> MS |
CHANNEL RELEASE |
After the sending of this message, the SS waits for the disconnection of the main signalling link. |
Specific message contents
None.