26.8.1 Circuit switched Call Control (CC) state machine verification
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
26.8.1.1 General on CC state machine verification
The principle of checking the call control functions consists in the validation of each call control identified state.
State U0 as an initial state is not verified in the tests of 26.8.1.2 (establishment of an outgoing call).
State U0.1 is never verified.
The steps to be followed within each performed test are:
– bring the MS into the required state;
– trigger the tested event;
– check the MS response and new state.
In subclauses 26.8.1.2 and 26.8.1.3 different tables are defined to bring the MS into the required initial state. The exact table to be chosen is specified individually in subclause "Initial conditions" of "Method of test" for each test case.
For each test, unless otherwise specified, a circuit switched basic service among those supported by the MS but excluding the emergency call teleservice shall be chosen arbitrarily, and the test shall be performed according to that basic service. If the only circuit switched basic service supported by the mobile is emergency call, then the incoming call tests shall not be performed and the other call control tests shall be performed with the EMERGENCY SETUP message replacing the SETUP message.
The initial states are to be checked through STATUS ENQUIRY messages sent by the SS, when feasible. This is not explicitly stated in the tables of expected sequences of signalling messages. The checking of final states are explicitly included into the expected sequences of signalling messages.
The following postamble may be used by the SS to bring MS back to idle mode in those test cases, in which it is not already included into expected sequence of signalling messages:
Table 26.8.1.1/1: A postamble to bring the MS back to idle mode.
Step |
Direction |
Message |
Comments |
n |
SS -> MS |
CHANNEL RELEASE |
|
n+1 |
MS |
the MS shall release the main signalling link (DISC/UA) |
The postamble has not been included into the all of the tests in order to leave an option to concatenate the procedures in the future by using a final state of a test case as an initial state to another one.
For the special case of U0, the state is checked by sending STATUS ENQUIRY message with all possible values of transaction identifier (seven values) as U0 is the only state in which for every TI the MS will answer with release complete with cause #81. If U0 is to be verified when no RR connection exists, first a mobile terminating radio connection must be established.
The MS responses are either call management messages received by the SS or lower layers functions activated within the MS or MMI actions (e.g. the buzzing of an alerting tone).
A time-out within the MS is triggered by the SS when it does not answer back an MS expected response.
The test sequences may be split in 3 main groups:
– establishment and release of an outgoing call;
– establishment and release of an incoming call;
– in-call functions.
Remark on verification of transient states:
Some call control states of the mobile station may be transient, depending on implementation, configuration of the MS and previous messages (see annex 3, subclause 3.1.6).
If a test starts in a transient state, then the test is executed without verification of the starting state.
26.8.1.2 Establishment of an outgoing call
Initial conditions
As a minimum requirement the MS is updated and has been given a TMSI, a ciphering key and cipher key sequence number, and the layer 2, RR and MM functionalities have been verified.
There are as many CM initial conditions as states to be checked.
The tables below describe message exchanges which bring the MS in the requested initial states.
A state may be taken as initial only when all the states which lead to this initial state have been validated. The order followed in the test procedure will be U0, U0.1, U1, U3, U4, U10, U12, U19, U11 as seen in the table underneath.
The MS is brought again in the initial state starting with U0 at each new test performed.
Table 26.8.1.2/1: Establishment of an outgoing call, procedure 1 (late assignment)
Step |
Direction |
Message |
Comments/actions/next state |
1 |
MS -> SS |
CHANNEL REQUEST |
initiate outgoing call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH, U0 |
3 |
MS -> SS |
CM SERVICE REQUEST |
U0.1 |
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
U1 |
7 |
SS -> MS |
CALL PROCEEDING |
U3 |
8 |
SS -> MS |
ALERTING |
U4 |
9 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
10 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
11 |
SS -> MS |
CONNECT |
|
12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
U10 |
A13 |
SS -> MS |
DISCONNECT |
U12 (note 1) |
B13 |
SS -> MS |
DISCONNECT |
U12 (note 2) |
B14 |
MS -> SS |
RELEASE |
U19 |
C13 |
MMI action, terminate call |
||
C14 |
MS -> SS |
DISCONNECT |
U11 |
NOTE 1: The Progress Indicator IE with progress description #8 "in band information or appropriate pattern now available" is included. NOTE 2: The Progress Indication IE is not included. |
Table 26.8.1.2/2: Establishment of an outgoing call, procedure 2
Step |
Direction |
Message |
Comments/actions/next state |
1 |
MS -> SS |
CHANNEL REQUEST |
initiate outgoing call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
TCH, U0 |
3 |
MS -> SS |
CM SERVICE REQUEST |
U0.1 |
4 |
SS -> MS |
CHANNEL MODE MODIFY |
(note 1) |
5 |
MS -> SS |
CHANNEL MODE MODIFY ACKNOWLEDGE |
|
6 |
SS -> MS |
CIPHERING MODE COMMAND |
|
7 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
8 |
MS -> SS |
SETUP |
U1 |
9 |
SS -> MS |
CALL PROCEEDING |
U3 |
10 |
SS -> SS |
ALERTING |
U4 |
11 |
SS -> MS |
CONNECT |
|
12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
U10 |
A13 |
SS -> MS |
DISCONNECT |
U12 (note 2) |
B13 |
SS -> MS |
DISCONNECT |
U12 (note 3) |
B14 |
MS -> SS |
RELEASE |
U19 |
C13 |
MMI action, terminate call |
||
C14 |
MS -> SS |
DISCONNECT |
U11 |
NOTE 1: Assigned channel is appropriate for the chosen bearer capability (see subclause 26.8.1). NOTE 2: The Progress Indicator IE with progress description #8 "in band information or appropriate pattern now available’ is included. NOTE 3: The Progress Indicator IE is not included. |
Table 26.8.1.2/3: Establishment of an outgoing call, procedure 3
Step |
Direction |
Message |
Comments/actions/next state |
1 |
MS -> SS |
CHANNEL REQUEST |
initiate outgoing call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH, U0 |
3 |
MS -> SS |
CM SERVICE REQUEST |
U0.1 |
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
U1 |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CALL PROCEEDING |
U3 |
10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> MS |
ALERTING |
U4 |
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
U10 |
A15 |
SS -> MS |
DISCONNECT |
U12 (note 1) |
B15 |
SS -> MS |
DISCONNECT |
U12 (note 2) |
B16 |
MS -> SS |
RELEASE |
U19 |
C15 |
MMI action, terminate call |
||
C16 |
MS -> SS |
DISCONNECT |
U11 |
NOTE 1: The Progress Indicator IE with progress description #8 "in band information or appropriate pattern now available" is included. NOTE 2: The Progress indicator IE is not included. |
Table 26.8.1.2/4: Establishment of an outgoing call, procedure 4
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
initiate outgoing call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
TCH, U0 |
3 |
MS -> SS |
CM SERVICE REQUEST |
U0.1 |
4 |
SS -> MS |
IDENTITY REQUEST |
|
5 |
MS -> SS |
IDENTITY RESPONSE |
|
6 |
SS -> MS |
CIPHERING MODE COMMAND |
|
7 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
8 |
MS -> SS |
SETUP |
U1 |
9 |
SS -> MS |
CHANNEL MODE MODIFY |
(note 1) |
10 |
MS -> SS |
CHANNEL MODE MODIFY ACKNOWLEDGE |
|
11 |
SS -> MS |
CALL PROCEEDING |
U3 |
12 |
SS -> MS |
ALERTING |
U4 |
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
U10 |
A15 |
SS -> MS |
DISCONNECT |
U12 (note 2) |
B15 |
SS -> MS |
DISCONNECT |
U12 (note 3) |
B16 |
MS -> SS |
RELEASE |
U19 |
C15 |
MMI action, terminate call |
||
C16 |
MS -> SS |
DISCONNECT |
U11 |
NOTE 1: Assigned channel is appropriate for the chosen bearer capability (see subclause 26.8.1). NOTE 2: The Progress Indicator IE with progress description #8 "in band information or appropriate pattern now available" is included. NOTE 3: The Progress Indicator IE is not included. |
26.8.1.2.1 Outgoing call / U0 null state
26.8.1.2.1.1 Outgoing call / U0 null state / MM connection requested
26.8.1.2.1.1.1 Definition
The call control entity of the Mobile Station requests the MM-sublayer to establish a mobile originating MM-connection. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.1.1.2 Conformance requirement
1) Upon initiation of an outgoing basic call by user the MS shall initiate establishment of an MM connection, using as first MM message a CM SERVICE REQUEST message with CM service type "Mobile originating call establishment or packet mode connection establishment".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.1.1, 4.5.1.1 and 3.3.1.1.
26.8.1.2.1.1.3 Test purpose
To verify that upon initiation of an outgoing basic call by user the MS initiates establishment of an MM connection, using as first MM message a CM SERVICE REQUEST message with CM service type "Mobile originating call establishment or packet mode connection establishment".
26.8.1.2.1.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
U0, null.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. When the SS receives CM SERVICE REQUEST, the contents of it shall be checked.
Maximum duration of test
30 s.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
initiate outgoing call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
TCH |
3 |
MS -> SS |
CM SERVICE REQUEST |
verify the type of call which is asked for "basic" or "emergency by the MS |
4 |
SS -> MS |
CHANNEL RELEASE |
|
5 |
MS |
the MS shall release the main signalling link (DISC/UA) |
Specific message contents:
None.
26.8.1.2.2 Outgoing call / U0.1 MM connection pending
26.8.1.2.2.1 Outgoing call / U0.1 MM connection pending / CM service rejected
26.8.1.2.2.1.1 Definition
A request for MM connection is rejected by the SS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.2.1.2 Conformance requirement
Upon receiving indication of an MM-connection establishment being rejected, CC entity should inform upper layer of this rejection.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 4.5.1.1, 3GPP TS 04.07 / 3GPP TS 24.007, subclause 6.2.2.
26.8.1.2.2.1.3 Test purpose
To verify that a CC entity of the MS in CC-state U0.1, "MM-connection pending", upon the MS receiving a CM SERVICE REJECT message, returns to CC state U0, "Null".
26.8.1.2.2.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U0.1 by using table 26.8.1.2/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. When the SS receives CM SERVICE REQUEST, the contents of it shall be checked. The SS rejects it by CM SERVICE REJECT. Then the SS will check the state of the MS by using STATUS ENQUIRY with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CM SERVICE REJECT |
|
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
RELEASE COMPLETE |
cause shall be 81# (invalid TI value) |
4 |
SS |
repeat steps 2‑3 to cover all the transaction identifiers from 000 …110 |
|
5 |
SS -> MS |
CHANNEL RELEASE |
|
6 |
MS |
the MS shall release the main signalling link (DISC/UA) |
Specific message contents:
None.
26.8.1.2.2.2 Outgoing call / U0.1 MM connection pending / CM service accepted
26.8.1.2.2.2.1 Definition
A CM request is accepted for the MM-connection by the SS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.2.2.2 Conformance requirement
A CC entity of the MS in CC-state U0.1, "MM-connection pending", upon the MS receiving a CM SERVICE ACCEPT message, shall send a SETUP message specifying the Called party BCD number that was entered into the MS and then enter CC state U1, "Call initiated".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 4.5.1.1 and 5.2.1.1.
26.8.1.2.2.2.3 Test purpose
To verify that a CC entity of the MS in CC-state U0.1, "MM-connection pending", upon the MS receiving a CM SERVICE ACCEPT message, sends a SETUP message specifying the Called party BCD number that was entered into the MS and then enters CC state U1, "Call initiated".
26.8.1.2.2.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U0.1 by using table 26.8.1.2/1.
Foreseen final state of the MS
U1, call initiated.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. When the MS is requesting a MM-connection, the SS will indicate acceptance by sending a CM SERVICE ACCEPT message. The MS shall respond with SETUP. Then the SS will check the state of the call control entity by STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CM SERVICE ACCEPT |
|
2 |
MS -> SS |
SETUP |
with called party BCD number. |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause shall be 30# (response to enq.) and state U1 call initiated. |
Specific message contents:
None.
26.8.1.2.2.3 Outgoing call / U0.1 MM connection pending / lower layer failure
26.8.1.2.2.3.1 Definition
The call control entity of the MS being in the state, U0.1, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.2.3.2 Conformance requirement
1) Upon a lower layer failure the MS releases the MM connection in progress and returns to idle mode. In that state no call exists and the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 4.5.1.2, 5.2.1.1, 5.5.3.2 and 8.3.
26.8.1.2.2.3.3 Test purpose
To verify that after the MS with a CC entity in state U0.1, "MM-connection pending", has detected a lower layer failure and has returned to idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
26.8.1.2.2.3.4 Method of test
Specific PICS statements
– Support of UTRAN Radio Access Technology (TSPC_Type_UTRAN)
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U0.1 by using table 26.8.1.2/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. When the MS has sent a CM SERVICE REQUEST message, the SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure. |
|
2 |
SS |
If PICS statement “Support of UTRAN Radio Access Technology” is ‘NO’, then the SS waits 20 s for the MS to return to listening to paging. If PICS statement “Support of UTRAN Radio Access Technology” is ‘YES’, then the SS waits 50 s for the MS to return to listening to paging. |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause shall be 81# (invalid TI value). |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000 …110. |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.3 Outgoing call / U1 call initiated
26.8.1.2.3.1 Outgoing call / U1 call initiated / receiving CALL PROCEEDING
26.8.1.2.3.1.1 Definition
The call control entity of the MS being in the state, U1, a CALL PROCEEDING message is sent by the SS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.3.1.2 Conformance requirement
1) A CC entity of the MS in CC-state U1, "Call initiated", upon receipt of a CALL PROCEEDING message, shall enter CC state U3, "Mobile originating call proceeding".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.1.1, 5.2.1.2 and 5.2.1.3.
26.8.1.2.3.1.3 Test purpose
To verify that a CC entity of the MS in CC-state U1, "Call initiated", upon receipt of a CALL PROCEEDING message, enters CC state U3, "Mobile originating call proceeding".
26.8.1.2.3.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/2.
Foreseen final state of the MS
U3, Mobile originating call proceeding.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U1. The SS sends a CALL PROCEEDING message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U3.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CALL PROCEEDING |
tone generation not mandatory |
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
STATUS |
cause 30#, state U3 |
Specific message contents:
None.
26.8.1.2.3.2 Outgoing call / U1 call initiated / rejecting with RELEASE COMPLETE
26.8.1.2.3.2.1 Definition
The call control entity of the MS being in the state, U1, the call is rejected by a RELEASE COMPLETE message sent by the SS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.3.2.2 Conformance requirement
1) A CC entity of the MS in CC-state U1, "Call initiated", upon receipt of a RELEASE COMPLETE message with valid cause value, shall enter CC state U0, "Null".
2) On returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers shall be in state U0, "Null".
3) On releasing the MM-connection, the MS shall wait for MM layer release initiated by the network.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.4.2 and 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.5.3.2.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.4.4.3 and 4.5.3,
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.13.1
26.8.1.2.3.2.3 Test purpose
1) To verify that a CC entity of the MS in CC-state U1, "Call initiated", upon receipt of a RELEASE COMPLETE message with valid cause value, enters CC state U0, "Null".
2) To verify that in returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
3) To verify that in releasing the MM-connection, the MS shall wait for MM layer release initiated by SS.
26.8.1.2.3.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/2.
Foreseen final state of the MS
U0, null.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U1. The SS sends a RELEASE COMPLETE message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE COMPLETE |
See specific message content below. |
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
4 |
SS |
repeat steps 2‑3 to cover all the transaction identifiers from 000…110 |
|
5 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
RELEASE COMPLETE
1) With a valid cause value among:
related to numbering,
#1 unallocated number
#3 no route to destination
#22 number changed
#28 invalid number format
related to bearer capabilities,
#8 operator determined barring
#57 bearer capability not authorized
#58 bearer capability not presently available
#63 service or option not available
#65 bearer service not implemented
#34 no circuit/channel available (call queuing).
26.8.1.2.3.3 Outgoing call / U1 call initiated / T303 expiry
26.8.1.2.3.3.1 Definition
The call control entity of the MS being in the state, U1, if no response is then received from the SS, timer T303 expires at the MS side. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.3.3.2 Conformance requirement
1) A CC entity of the MS in CC-state U1, "Call initiated", upon expiry of T303 shall send a DISCONNECT message to its peer entity and enter state U11, "Disconnect request".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.1.1 and 5.4.
26.8.1.2.3.3.3 Test purpose
1) To verify that a CC entity of the MS in CC-state U1, "Call initiated", upon expiry of T303 (accuracy ±20 % between reception of CM SERVICE REQUEST and DISCONNECT by SS) sends a DISCONNECT message to its peer entity and enters state U11, "Disconnect request".
26.8.1.2.3.3.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/2.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
1 minute.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U1. When T303 expires at the MS, the MS shall send DISCONNECT. The SS checks by using the status enquiry procedure that the CC entity has entered the state U11, disconnect request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS waits for T303 expiry. |
|
2 |
MS -> SS |
DISCONNECT |
Shall be transmitted between 24 s and 36 s after the CM SERVICE REQUEST. |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, status U11 |
Specific message contents:
None.
26.8.1.2.3.4 Outgoing call / U1 call initiated / lower layer failure
26.8.1.2.3.4.1 Definition
The call control entity of the MS being in the state, U1, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.3.4.2 Conformance requirement
Upon a lower layer failure MM informs the relevant CM entities that the MM connection has been interrupted. As call re-establishment is not allowed, the CC entity must perform a local release. The MS returns to idle mode. In that state no call exists, and the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 4.5.2.3, 5.2.1.1 and 5.5.3.2.
26.8.1.2.3.4.3 Test purpose
To verify that after the MS with a CC entity in state U1 "Call initiated", has detected a lower layer failure and has returned to idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
26.8.1.2.3.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/4.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The MS is brought to the state U1. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure. |
|
2 |
SS |
SS waits 20 s for the MS to return to listening to paging. |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value). |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000…110. |
|
10 |
SS -> MS |
CHANNEL RELEASE |
|
11 |
MS |
the MS shall release the main signalling link (DISC/UA). |
Specific message contents:
None.
26.8.1.2.3.5 Outgoing call / U1 call initiated / receiving ALERTING
26.8.1.2.3.5.1 Definition
The call control entity of the MS being in the state, U1, an ALERTING message is sent to the MS as a indication that a call is being alerted at a called end. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.3.5.2 Conformance requirement
1) A CC entity of the MS in CC-state U1, "Call initiated", upon receipt of an ALERTING message, shall enter CC state U4, "Call delivered".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.1.1.
26.8.1.2.3.5.3 Test purpose
To verify that a CC entity of the MS in CC-state U1, "Call initiated", upon receipt of an ALERTING message, enters CC state U4, "Call delivered".
26.8.1.2.3.5.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/4.
Foreseen final state of the MS
U4, call delivered.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U1. The SS sends an ALERTING message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U4, call delivered.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
ALERTING |
|
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
STATUS |
cause 30#, state U4 |
Specific message contents:
None.
26.8.1.2.3.6 Outgoing call / U1 call initiated / entering state U10
26.8.1.2.3.6.1 Definition
The call control entity of the MS being in the state, U1, a CONNECT message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.3.6.2 Conformance requirement
1) A CC entity of the MS in CC-state U1, "Call initiated", upon receipt of a CONNECT message, shall send a CONNECT ACKNOWLEDGE message to its peer entity and enter CC state U10, "Active".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.1.1 and 5.2.1.6.
26.8.1.2.3.6.3 Test purpose
To verify that a CC entity of the MS in CC-state U1, "Call initiated", upon receipt of a CONNECT message, sends a CONNECT ACKNOWLEDGE message to its peer entity and enters CC state U10, "Active".
26.8.1.2.3.6.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/4.
Foreseen final state of the MS
U10, call active.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U1. The SS sends a CONNECT message to the MS. The MS shall respond by sending a CONNECT ACKNOWLEDGE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U10, active.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CONNECT |
|
2 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
None.
26.8.1.2.3.7 Outgoing call / U1 call initiated / unknown message received
26.8.1.2.3.7.1 Definition
The call control entity of the MS being in the state, U1, an unknown message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.3.7.2 Conformance requirement
1) A CC entity of the MS in CC-state U1, "Call initiated", upon receipt of a message with message type not defined for the protocol discriminator from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 8.4.
26.8.1.2.3.7.3 Test purpose
To verify that a CC entity of the MS in CC-state U1, "Call initiated", upon receipt of a message with message type not defined for the protocol discriminator unknown message from its peer entity returns a STATUS message.
26.8.1.2.3.7.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/1.
Foreseen final state of the MS
U1, call initiated.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U1. The SS sends a message with message type not defined for the protocol discriminator to the MS. The MS shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
unknown message |
message type not defined for PD |
2 |
MS -> SS |
STATUS |
cause 97#, state U1 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U1 |
Specific message contents:
None.
26.8.1.2.4 Outgoing call / U3 MS originating call proceeding
26.8.1.2.4.1 Outgoing call / U3 MS originating call proceeding / ALERTING received
26.8.1.2.4.1.1 Definition
The call control entity of the MS being in the state, U3, an ALERTING message is sent to the MS as a indication that a call is being alerted at a called end. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.1.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a ALERTING message shall enter CC-state U4, "Call Delivered".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.5.
26.8.1.2.4.1.3 Test purpose
To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a ALERTING message enters CC-state U4, "Call Delivered".
26.8.1.2.4.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/2.
Foreseen final state of the MS
U4, call delivered.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends an ALERTING message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U4, call delivered.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
ALERTING |
|
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
STATUS |
cause 30#, state U4 |
Specific message contents:
None.
26.8.1.2.4.2 Outgoing call / U3 MS originating call proceeding / CONNECT received
26.8.1.2.4.2.1 Definition
The call control entity of the MS being in the state, U3, a CONNECT message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.2.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a CONNECT message shall return a "CONNECT ACKNOWLEDGE" message to its peer entity and enter the CC state U10, "Active".
2) The MS shall then stop any locally generated indication.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.6.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.6.
26.8.1.2.4.2.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a CONNECT message returns a "CONNECT ACKNOWLEDGE" message to its peer entity and enters the CC state U10, "Active".
2) To verify that the MS stops locally generated indication, if any.
26.8.1.2.4.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/2.
Foreseen final state of the MS
U10, active.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends a CONNECT message to the MS. The MS shall respond by sending a CONNECT ACKNOWLEDGE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U10, active.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CONNECT |
the MS shall stop tone generation, if any |
2 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
None.
26.8.1.2.4.3 Outgoing call / U3 MS originating call proceeding / PROGRESS received without in band information
26.8.1.2.4.3.1 Definition
The call control entity of the MS being in the state, U3, a PROGRESS message is received by the MS. The PROGRESS message does not contain indication of in-band information availability. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.3.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a PROGRESS message with valid Progress Indicator values shall stay in CC-state U3.
2) After receipt of the PROGRESS message timer T310 shall be stopped.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 11.3.
26.8.1.2.4.3.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a PROGRESS message with valid Progress Indicator values stays in CC-state U3.
2) To verify that after receipt of the PROGRESS message timer T310 is stopped.
26.8.1.2.4.3.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/2.
Foreseen final state of the MS
U3, mobile originating call proceeding.
Maximum duration of test
1 min.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends a PROGRESS message not containing indication of in-band information availability to the MS. The SS checks that the MS has stopped T310, i.e. at T310 time-out no DISCONNECT message is sent by the MS. Then the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PROGRESS |
(note) |
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
STATUS |
cause 30#, state U3 |
4 |
SS |
SS waits at least 45 s and checks no DISCONNECT is sent by the MS |
|
5 |
SS -> MS |
STATUS ENQUIRY |
|
6 |
MS -> SS |
STATUS |
cause 30#, state U3 |
NOTE: Tested with a valid Progress Indicator value among:
#4 call has returned to PLMN/ISDN;
#32 call is end-to-end PLMN/ISDN; or
any value in the set #(21‑127).
Specific message contents:
None.
26.8.1.2.4.4 Outgoing call / U3 MS originating call proceeding / PROGRESS with in band information
26.8.1.2.4.4.1 Definition
The call control entity of the MS being in the state, U3, a PROGRESS message indicating availability of in band information is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.4.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a PROGRESS message indicating in-band announcement shall through-connect the traffic channel for speech, if TCH is in a speech mode. If TCH is not in speech mode, the MS shall not through-connect the TCH.
2) After receipt of the PROGRESS message, T310 shall be stopped.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3,
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.1.3, 5.2.1.4, 5.2.1.9, 5.5.1 and 11.3.
26.8.1.2.4.4.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a PROGRESS message indicating in-band announcement through-connects the traffic channel for speech, if TCH is in speech mode. If TCH is not in a speech mode, the MS does not through-connect the TCH.
2) To verify that after receipt of the PROGRESS message, T310 is stopped.
26.8.1.2.4.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/2.
Foreseen final state of the MS
U3, mobile originating call proceeding.
Maximum duration of test
1 minute.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends a PROGRESS message containing indication of in-band information availability to the MS. The SS checks that if channel mode is speech, the TCH shall be through connected. If channel mode is not speech, the TCH shall not be through connected. Also the SS checks that the MS has stopped T310, i.e. at T310 time-out no DISCONNECT message is sent by the MS. Then the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PROGRESS |
the MS shall stop all the CC timers (note), if channel mode is speech, the TCH shall be through connected. If channel mode is not speech, the TCH shall not be through connected. |
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
STATUS |
cause 30#, state U3 |
4 |
SS |
SS waits at least 45 s and checks no DISCONNECT is sent by the MS. |
|
5 |
SS -> MS |
STATUS ENQUIRY |
|
6 |
MS -> SS |
STATUS |
cause 30#, state U3 |
7 |
SS |
If the channel mode is speech the SS will check that the user connection for speech is attached (both downlink and uplink). |
Specific message contents:
NOTE: Tested with a valid Progress Indicator value among:
#1 call is not end to end PLMN/ISDN;
#2 destination address is non PLMN/ISDN;
#3 originating address is non PLMN/ISDN;
#8 in band information or appropriate pattern now available; or
any value in the set #(6‑20).
26.8.1.2.4.5 Outgoing call / U3 MS originating call proceeding / DISCONNECT with in band tones
26.8.1.2.4.5.1 Definition
The call control entity of the MS being in the state, U3, a DISCONNECT message indicating availability of in band information is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.5.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a DISCONNECT with progress indicator #8, shall through-connect the speech channel to make in-band announcements available, if traffic channel is in speech mode. If TCH is not in speech mode, the MS shall send a RELEASE message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.1.4 and 5.4.4.
26.8.1.2.4.5.3 Test purpose
To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a DISCONNECT with progress indicator #8 through-connects the speech channel to make in-band announcements available, if traffic channel is in speech mode. If TCH is not in speech mode, the MS sends a RELEASE message.
26.8.1.2.4.5.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/2.
Foreseen final state of the MS
U12, disconnect indication if TCH is speech mode.
U19, release request if TCH is not speech mode.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends a DISCONNECT message containing indication of in-band information availability to the MS. The SS checks that if channel mode is speech, the TCH shall be through connected and the MS enters state U12, disconnect indication. If channel mode is not speech, the TCH shall not be through connected and the MS shall enter state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
(note) |
TCH in speech mode: |
|||
B2 |
SS |
the SS will check that the audio path for in band tones is attached. |
|
B3 |
SS -> MS |
STATUS ENQUIRY |
|
B4 |
MS -> SS |
STATUS |
cause 30#, state U12 |
TCH is not in speech mode: |
|||
C2 |
MS -> SS |
RELEASE |
|
C3 |
SS -> MS |
STATUS ENQUIRY |
|
C4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
NOTE: the Progress Indicator value:
#8 in band information or appropriate pattern now available.
26.8.1.2.4.6 Outgoing call / U3 MS originating call proceeding / DISCONNECT without in band tones
26.8.1.2.4.6.1 Definition
The call control entity of the MS being in the state, U3, a DISCONNECT message is received by the MS. The DISCONNECT message does not contain indication of in-band information availability. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.6.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a DISCONNECT without progress indicator shall return a RELEASE message and enter the CC-state U19, "Release Request"
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
26.8.1.2.4.6.3 Test purpose
To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a DISCONNECT without progress indicator returns a RELEASE message and enters the CC-state U19, "Release Request".
26.8.1.2.4.6.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/2.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends a DISCONNECT message not containing indication of in-band information availability to the MS. The MS shall respond with a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity of the MS has entered the state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
|
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
None.
26.8.1.2.4.7 Outgoing call / U3 MS originating call proceeding / RELEASE received
26.8.1.2.4.7.1 Definition
The call control entity of the MS being in the state, U3, a RELEASE message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.7.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".
2) The MS on returning to the idle mode shall release the MM-connection and the CC-entities relating to the seven mobile originating transaction identifiers shall be in CC-state U0, "Null".
3) On releasing the MM-connection, the MS shall wait for MM layer release initiated by the network.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.2 and 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3 and 5.5.3.2.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.4.4.3 and 4.5.3,
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.13.1
26.8.1.2.4.7.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".
2) To verify that the MS on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile originating transaction identifiers are in CC-state U0, "Null".
3) To verify that in releasing the MM-connection, the MS shall wait for MM layer release initiated by SS.
26.8.1.2.4.7.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/2.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 minute 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends a RELEASE message to the MS. The MS shall respond with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
with cause "Normal, unspecified" |
2 |
MS -> SS |
RELEASE COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.4.8 Outgoing call / U3 MS originating call proceeding / termination requested by the user
26.8.1.2.4.8.1 Definition
The call control entity of the MS being in the state, U3, the user requests to terminate the call. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.8.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon request by the user to terminate will send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
References
3GPP TS 04.07 / 3GPP TS 24.007 subclause 6.2.2,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.3.
26.8.1.2.4.8.3 Test purpose
To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", upon request by the user to terminate will send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
26.8.1.2.4.8.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator: 1 cell, default parameters.
Mobile Station: The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/3.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The user requests termination of the call. The MS shall send a DISCONNECT message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U11, disconnect request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MMI action, terminate call |
||
2 |
MS -> SS |
DISCONNECT |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
None.
26.8.1.2.4.9 Outgoing call / U3 MS originating call proceeding / traffic channel allocation
26.8.1.2.4.9.1 Definition
The call control entity of the MS being in the state, U3, a traffic channel assignment procedure is performed. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.9.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", when allocated a traffic channel by the network performing the assignment procedure, shall perform a layer 2 establishment on the FACCH without changing the state of the call in progress.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.9.
26.8.1.2.4.9.3 Test purpose
To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding", when allocated a traffic channel by the network performing the assignment procedure, performs a layer 2 establishment on the FACCH without changing the state of the call in progress.
26.8.1.2.4.9.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/3.
Foreseen final state of the MS
U3, mobile originating call proceeding.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends an ASSIGNMENT COMMAND for traffic channel to the MS. The MS shall establish layer 2 link on the newly allocated channel and respond with an ASSIGNMENT COMPLETE message. The SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
ASSIGNMENT COMMAND |
(TCH) the MS shall perform L2 establishment on the FACCH |
2 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U3 |
Specific message contents:
None.
26.8.1.2.4.10 Outgoing call / U3 MS originating call proceeding / timer T310 time-out
26.8.1.2.4.10.1 Definition
The call control entity of the MS being in the state, U3, if no response is then received from the SS, timer T310 expires at the MS side. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.10.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding" shall, upon expiry of timer T310, and not before, initiate call release by sending DISCONNECT and enter the CC-state U11, "Disconnect Request".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.1.3./Abnormal case, 5.4.3 and 11.3.
26.8.1.2.4.10.3 Test purpose
To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding" will, upon expiry of timer T310 (accuracy minus 2 %, plus 50 %), initiate call release by sending DISCONNECT and enter the CC-state U11, "Disconnect Request".
26.8.1.2.4.10.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/3.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
1 minute.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The T310 expires at the MS and the MS shall send DISCONNECT. The SS checks timer T310 accuracy and that the CC entity has entered the state U11, disconnect request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
the SS waits for T310 time-out |
|
2 |
MS -> SS |
DISCONNECT |
check the timer T310 accuracy (minus 2 % to plus 50 %) |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
None.
26.8.1.2.4.11 Outgoing call / U3 MS originating call proceeding / lower layer failure
26.8.1.2.4.11.1 Definition
The call control entity of the MS being in the state, U3, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.11.2 Conformance requirement
1) If a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding" has detected a lower layer failure and has returned to idle mode, the CC entities relating to the seven mobile originating transaction identifiers shall be in state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.5.2.3, 4.5.3 and 5.5.3.2.
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.13.2.1.
26.8.1.2.4.11.3 Test purpose
To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding" having detected a lower layer failure and having returned to idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
26.8.1.2.4.11.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/4.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 minute 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The MS is brought to the state U3. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure |
|
2 |
SS |
SS waits 20 s for the MS to return to listening to paging |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
9 |
SS |
repeat steps 18‑19 to cover all the transaction identifiers from 000…110 |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.4.12 Outgoing call / U3 MS originating call proceeding / unknown message received
26.8.1.2.4.12.1 Definition
The call control entity of the MS being in the state, U3, an unknown message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.4.12.2 Conformance requirement
1) A CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding" having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 8.5.
26.8.1.2.4.12.3 Test purpose
To verify that a CC-entity of the MS in CC-state U3, "Mobile Originating Call Proceeding" having received an unknown message from its peer entity returns a STATUS message.
26.8.1.2.4.12.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/1.
Foreseen final state of the MS
U3, mobile originating call proceeding.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U3. The SS sends a message with message type not defined for the protocol discriminator to the MS. The MS shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
unknown message |
message type not defined for PD |
2 |
MS -> SS |
STATUS |
cause 97#, state U3 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U3 |
Specific message contents:
None.
26.8.1.2.4.13 Outgoing call / U3 MS originating call proceeding / Internal alerting indication
26.8.1.2.4.13.1 Definition
The call control entity of the MS being in the state, U3, an ALERTING message is sent to the MS when the user connection is not attached to the radio path. This test is applicable for any equipment supporting mobile originated circuit switched basic service for telephony.
26.8.1.2.4.13.2 Conformance requirement
1) When the call control entity of the MS in the "mobile originating call proceeding" state receives an ALERTING message then it shall enter "call delivered" state and, for speech calls, if the user connection is not attached to the radio path, the MS shall internally generate an alerting indication.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.5.
26.8.1.2.4.13.3 Test purpose
When the call control entity of the MS in the "mobile originating call proceeding" state receives an ALERTING message then it enters "call delivered" state and, for speech calls, if the user connection is not attached to the radio path, the MS generates internally an alerting indication.
26.8.1.2.4.13.4 Method of test
Specific PICS statements
–
PIXIT statements
– way to give internally generated alerting indication for outgoing calls
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U3 by using table 26.8.1.2/1.
Foreseen final state of the MS
U4, call delivered.
Maximum duration of test
30 s.
Test procedure
The SS sends an ALERTING message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U4, call delivered. Also it is checked that the MS generates internally alerting indication to the user in the way described in the PIXIT statements.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
ALERTING |
the MS shall generate an alerting indication to the user in the way described in the PIXIT statements |
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
STATUS |
cause 30#, state U4 |
Specific message contents:
None.
26.8.1.2.5 Outgoing call / U4 call delivered
26.8.1.2.5.1 Outgoing call / U4 call delivered / CONNECT received
26.8.1.2.5.1.1 Definition
The call control entity of the MS being in the state, U4, a CONNECT message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.5.1.2 Conformance requirement
1) A CC-entity of the MS in CC-state U4, "Call Delivered", upon receipt of the CONNECT message shall return a CONNECT ACKNOWLEDGE to its peer entity and enter the CC-state U10, "Active".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.6.
26.8.1.2.5.1.3 Test purpose
To verify that a CC-entity of the MS in CC-state U4, "Call Delivered", upon receipt of the CONNECT message returns a CONNECT ACKNOWLEDGE to its peer entity and enters the CC-state U10, "Active".
26.8.1.2.5.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U4 by using table 26.8.1.2/3.
Foreseen final state of the MS
U10, active.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The SS sends a CONNECT message to the MS. The MS shall respond by sending a CONNECT ACKNOWLEDGE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U10, active.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CONNECT |
|
2 |
MS -> SS |
CONNECT ACKNOWLEDGE |
MS stops alerting, if applicable |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
None.
26.8.1.2.5.2 Outgoing call / U4 call delivered / termination requested by the user
26.8.1.2.5.2.1 Definition
The call control entity of the MS being in the state, U4, the user requests to terminate the call. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.5.2.2 Conformance requirement
1) A CC-entity of the MS in CC-state U4, "Call Delivered", upon request by the user to terminate shall send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
References
3GPP TS 04.07 / 3GPP TS 24.007 subclause 6.2.2.
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.3.
26.8.1.2.5.2.3 Test purpose
To verify that a CC-entity of the MS in CC-state U4, "Call Delivered", upon request by the user to terminate will send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
26.8.1.2.5.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U4 by using table 26.8.1.2/3.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The user requests termination of the call. The MS shall send a DISCONNECT message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U11, disconnect request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MMI action, terminate call |
||
2 |
MS -> SS |
DISCONNECT |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
None.
26.8.1.2.5.3 Outgoing call / U4 call delivered / DISCONNECT with in band tones
26.8.1.2.5.3.1 Definition
The call control entity of the MS being in the state, U4, a DISCONNECT message indicating availability of in band information is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.5.3.2 Conformance requirement
1) A CC-entity of the MS in CC-state U4, "Call Delivered" shall, upon receipt of a DISCONNECT with a progress indicator indicating in-band information, shall through-connect the speech channel to make in-band announcements available, if traffic channel is in speech mode. If TCH is not in speech mode, the MS shall send a RELEASE message.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3,
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.4.1, 5.5.1 and 5.2.1.9.
26.8.1.2.5.3.3 Test purpose
To verify that a CC-entity of the MS in CC-state U4, "Call Delivered", upon receipt of a DISCONNECT with a progress indicator indicating in-band information, through-connects the speech channel to make in-band announcements available, if traffic channel is in speech mode. If TCH is not in speech mode, the MS shall send a RELEASE message.
26.8.1.2.5.3.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U4 by using table 26.8.1.2/2.
Foreseen final state of the MS
U12, disconnect indication.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The SS sends a DISCONNECT message containing indication of in-band information availability to the MS. The SS checks that if channel mode is MO telephony, the TCH shall be through connected and the MS enters state U12, disconnect indication. If channel mode is not speech, the TCH shall not be through connected and the MS shall enter state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
(note) |
TCH in speech mode: |
|||
A2 |
SS |
the SS will check that the audio path for in band tones is attached. |
|
A3 |
SS -> MS |
STATUS ENQUIRY |
|
A4 |
MS -> SS |
STATUS |
cause 30#, state U12 |
TCH is not in speech mode: |
|||
B2 |
MS -> SS |
RELEASE |
|
B3 |
SS -> MS |
STATUS ENQUIRY |
|
B4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
NOTE: the Progress Indicator, Progress Description:
#8 in band information or appropriate pattern now available.
26.8.1.2.5.4 Outgoing call / U4 call delivered / DISCONNECT without in band tones
26.8.1.2.5.4.1 Definition
The call control entity of the MS being in the state, U4, a DISCONNECT message is received by the MS. The DISCONNECT message does not contain indication of in-band information availability. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.5.4.2 Conformance requirement
1) A CC-entity of the MS in CC-state U4, "Call Delivered", upon receipt of a DISCONNECT without progress indicator, shall return a RELEASE message and enter the CC-state U19, "Release Request".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
26.8.1.2.5.4.3 Test purpose
To verify that a CC-entity of the MS in CC-state U4, "Call Delivered", upon receipt of a DISCONNECT without progress indicator, returns a RELEASE message and enters the CC-state U19, "Release Request".
26.8.1.2.5.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U4 by using table 26.8.1.2/2.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The SS sends a DISCONNECT message not containing indication of in-band information availability to the MS. The MS shall respond with a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity of the MS has entered the state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
|
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
None.
26.8.1.2.5.5 Outgoing call / U4 call delivered / RELEASE received
26.8.1.2.5.5.1 Definition
The call control entity of the MS being in the state, U4, a RELEASE message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.5.5.2 Conformance requirement
1) A CC-entity of the MS in CC-state U4, "Call Delivered", upon receipt of the RELEASE message shall respond with the RELEASE COMPLETE message and enter the CC-state U0, "Null".
2) The MS on returning to idle mode shall release the MM-connection and the CC-entities relating to the seven mobile originating transaction identifiers shall be in CC-state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.2 and 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3 and 5.5.3.2.
26.8.1.2.5.5.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U4, "Call Delivered", upon receipt of the RELEASE message will respond with the RELEASE COMPLETE message and enter the CC-state U0, "Null".
2) To verify that the MS on returning the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile originating transaction identifiers are in CC-state U0, "Null".
26.8.1.2.5.5.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U4 by using table 26.8.1.2/2.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The SS sends a RELEASE message to the MS. The MS shall respond with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
with cause "Normal, unspecified" |
2 |
MS -> SS |
RELEASE COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.5.6 Outgoing call / U4 call delivered / lower layer failure
26.8.1.2.5.6.1 Definition
The call control entity of the MS being in the state, U4, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.5.6.2 Conformance requirement
1) When CC-entity of the MS in CC-state U4, "Call Delivered" has detected a lower layer failure and has returned to idle mode, the CC-entities relating to the seven mobile originating transaction identifiers shall be in CC-state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.2.3, 4.5.3 and 5.5.3.2,
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.13.2.1.
26.8.1.2.5.6.3 Test purpose
To verify that a CC-entity of the MS in CC-state U4, "Call Delivered" having detected a lower layer failure and has returned to idle mode, the CC-entities relating to the seven mobile originating transaction identifiers are in CC-state U0, "Null".
26.8.1.2.5.6.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U4 by using table 26.8.1.2/2.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 minute 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The MS is brought to the state U4. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure |
|
2 |
SS |
SS waits 20 s for the MS to return to listening to paging |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000…110 |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.5.7 Outgoing call / U4 call delivered / traffic channel allocation
26.8.1.2.5.7.1 Definition
The call control entity of the MS being in the state, U4, a traffic channel assignment procedure is performed. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.5.7.2 Conformance requirement
1) A CC-entity of the MS in CC-state U4, "Call Delivered", when allocated a traffic channel by the network performing the assignment procedure, shall perform a layer 2 establishment on the FACCH without changing the state of the call in progress.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.9.
26.8.1.2.5.7.3 Test purpose
To verify that a CC-entity of the MS in CC-state U4, "Call Delivered", when allocated a traffic channel by the network performing the assignment procedure, shall perform a layer 2 establishment on the FACCH without changing the state of the call in progress.
26.8.1.2.5.7.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U4 by using table 26.8.1.2/1.
Foreseen final state of the MS
U4, call delivered.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The SS sends an ASSIGNMENT COMMAND for traffic channel to the MS. The MS shall establish layer 2 link on the newly allocated channel and respond with an ASSIGNMENT COMPLETE message. The SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH, the MS shall perform L2 establishment on the FACCH |
2 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U4 |
Specific message contents:
None.
26.8.1.2.5.8 Outgoing call / U4 call delivered / unknown message received
26.8.1.2.5.8.1 Definition
The call control entity of the MS being in the state, U4, an unknown message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.5.8.2 Conformance requirement
1) A CC-entity of the MS in CC-state U4, "Call Delivered", having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 8.4.
26.8.1.2.5.8.3 Test purpose
To verify that a CC-entity of the MS in CC-state U4, "Call Delivered", having received an unknown message from its peer entity returns a STATUS message.
26.8.1.2.5.8.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U4 by using table 26.8.1.2/4.
Foreseen final state of the MS
U4, call delivered.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The SS sends a message with message type not defined for the protocol discriminator to the MS. The MS shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
unknown message |
message type not defined for PD |
2 |
MS -> SS |
STATUS |
cause 97#, state U4 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U4 |
Specific message contents:
None.
26.8.1.2.6 U10 call active
26.8.1.2.6.1 U10 call active / termination requested by the user
26.8.1.2.6.1.1 Definition
The call control entity of the MS being in the state, U10, the user requests to terminate the call. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.6.1.2 Conformance requirement
1) A CC-entity of the MS in CC-state U10, "Call Active", upon request by the user to terminate shall send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
References
3GPP TS 04.07 / 3GPP TS 24.007 subclause 6.2.2,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.3.
26.8.1.2.6.1.3 Test purpose
To verify that the a CC-entity of the MS in CC-state U10, "Call Active", upon request by the user to terminate will send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
26.8.1.2.6.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U10 by using table 26.8.1.2/1.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U10. The user requests termination of the call. The MS shall send a DISCONNECT message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U11, disconnect request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MMI action, terminate call |
||
2 |
MS -> SS |
DISCONNECT |
U11 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
None.
26.8.1.2.6.2 U10 call active / RELEASE received
26.8.1.2.6.2.1 Definition
The call control entity of the MS being in the state, U10, a RELEASE message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.6.2.2 Conformance requirement
1) A CC-entity of the MS in CC-state U10, "Call Active", upon receipt of the RELEASE shall respond with the RELEASE COMPLETE message and enter the CC-state U0, "Null"
2) When the MS returns to the idle mode it shall release the MM-connection and the CC-entities relating to the seven mobile originating transaction identifiers shall be in CC-state U0, "Null"
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.2 and 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3 and 5.5.3.2.
26.8.1.2.6.2.3 Test purpose
1) To verify that the a CC-entity of the MS in CC-state U10, "Call Active", upon receive of the RELEASE will respond with the RELEASE COMPLETE message and enter the CC-state U0, "Null".
2) To verify that the MS on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile originating transaction identifiers are in CC-state U0, "Null".
26.8.1.2.6.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U10 by using table 26.8.1.2/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U10. The SS sends a RELEASE message to the MS. The MS shall respond with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
with cause "Normal, unspecified" |
2 |
MS -> SS |
RELEASE COMPLETE |
the MS starts T3240 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA) |
Specific message contents:
None.
26.8.1.2.6.3 U10 call active / DISCONNECT with in band tones
26.8.1.2.6.3.1 Definition
The call control entity of the MS being in the state, U10, a DISCONNECT message indicating availability of in band information is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.6.3.2 Conformance requirement
1) A CC-entity of the MS in CC-state U10, "Call Active", upon receipt of a DISCONNECT message with a Progress Indicator indicating in-band information, shall through-connect the speech channel to make in-band announcements available, if traffic channel is in speech mode. If TCH is not in speech mode, the MS shall send a RELEASE message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.4.1 and 5.5.1.
26.8.1.2.6.3.3 Test purpose
To verify that a CC-entity of the MS in CC-state U10, "Call Active", upon receipt of a DISCONNECT message with a Progress Indicator indicating in-band information, through-connects the speech channel to make in-band announcements available, if traffic channel is in speech mode. If TCH is not in speech mode, the MS sends a RELEASE message.
26.8.1.2.6.3.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U10 by using table 26.8.1.2/2.
Foreseen final state of the MS
U12, disconnect indication.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U10. The SS sends a DISCONNECT message containing indication of in-band information availability to the MS. The SS checks that if channel mode is speech, the TCH shall be through connected and the MS enters state U12, disconnect indication. If channel mode is not speech, the TCH shall not be through connected and the MS enters state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
(note) |
TCH in speech mode: |
|||
A2 |
SS |
the SS will check that the audio path for in band tones is attached. |
|
A3 |
SS -> MS |
STATUS ENQUIRY |
|
A4 |
MS -> SS |
STATUS |
cause 30#, state U12 |
TCH is not in speech mode: |
|||
B2 |
MS -> SS |
RELEASE |
|
B3 |
SS -> MS |
STATUS ENQUIRY |
|
B4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
NOTE: the Progress Indicator, Progress Description:
#8 in band information or appropriate pattern now available.
26.8.1.2.6.4 U10 call active / DISCONNECT without in band tones
26.8.1.2.6.4.1 Definition
The call control entity of the MS being in the state, U10, a DISCONNECT message is received by the MS. The DISCONNECT message does not contain indication of in-band information availability. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.6.4.2 Conformance requirement
1) A CC-entity of the MS in CC-state U10, "Call Active", upon receipt of a DISCONNECT message without progress indicator, shall return a RELEASE message and enter the CC-state U19, "Release Request".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
26.8.1.2.6.4.3 Test purpose
To verify that the a CC-entity of the MS in CC-state U10, "Call Active", upon receipt of a DISCONNECT message without progress indicator, returns a RELEASE message and enters the CC-state U19, "Release Request".
26.8.1.2.6.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U10 by using table 26.8.1.2/2.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U10. The SS sends a DISCONNECT message not containing indication of in-band information availability to the MS. The MS shall respond with a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity of the MS has entered the state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
|
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
None.
26.8.1.2.6.5 U10 call active / RELEASE COMPLETE received
26.8.1.2.6.5.1 Definition
The call control entity of the MS being in the state, U10, the call is cleared by a RELEASE COMPLETE message sent by the SS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.6.5.2 Conformance requirement
1) A CC entity of the MS in CC-state U10, "active", upon receipt of a RELEASE COMPLETE message with valid cause value, shall enter CC state U0, "Null".
2) On returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers shall be in state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.4.2 and 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.4.4.3.
26.8.1.2.6.5.3 Test purpose
1) To verify that a CC entity of the MS in CC-state U10, "Call active" upon receipt of a RELEASE COMPLETE message with valid cause value, enters CC state U0, "Null".
2) To verify that in returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
26.8.1.2.6.5.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U10 by using table 26.8.1.2/2.
Foreseen final state of the MS
U0, null.
Maximum duration of test
30 s.
Test procedure
The SS sends a RELEASE COMPLETE message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE COMPLETE |
note 1 |
2 |
SS -> MS |
STATUS ENQUIRY |
note 2 |
3 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value), |
4 |
SS |
repeat steps 2‑3 to cover all the transaction identifiers from 000…110 |
|
5 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
NOTE 1: With the cause value chosen arbitrarily.
NOTE 2: TI flag has the value indicating the MS as a originator of the call.
26.8.1.2.6.6 U10 call active / SETUP received
26.8.1.2.6.6.1 Definition
If the MS does not react correctly when receiving a SETUP message on a new Transaction Identifier during an active call, the active call may be lost.
This test is applicable for all MS supporting at least one mobile originated circuit switched basic service.
26.8.1.2.6.6.2 Conformance requirement
1) A Mobile Station that has a call established when receiving a SETUP message shall respond either with a CALL CONFIRMED message or a RELEASE COMPLETE message, both with cause #17 "user busy".
2) The call control state of the existing transaction shall not be affected by the incoming SETUP message.
Reference(s):
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.3.1.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.1.1.
26.8.1.2.6.6.3 Test purpose
1) To verify that a Mobile Station that has a call established and receives a SETUP message answers either with a CALL CONFIRMED message with cause "user busy" if it supports call waiting, or with a RELEASE COMPLETE message with cause "user busy" otherwise.
2) To verify that after having sent this message, the MS is still in state U10 for the established call.
26.8.1.2.6.6.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is idle updated with valid TMSI and CKSN.
The MS is brought into the state U10 by using table 26.8.1.2/14.
Specific PICS statements
– support of call waiting (TSPC_Serv_SS_CW)
PIXIT statements
–
Foreseen final state of the MS
U10, call active.
Maximum duration of test
30 s.
Test Procedure
The MS has a mobile originated call in the U10 state.
The SS sends a SETUP message to the MS (with signal IE indicating "call waiting tone on").
If the MS does not support call waiting it shall answer by a RELEASE COMPLETE message.
If the MS supports call waiting it shall answer by a CALL CONFIRMED message followed by an ALERTING. The second transaction is then released by the SS with a RELEASE COMPLETE message.
In both cases the SS checks by using the status enquiry procedure that the CC entity of the MS is still in state U10, active call for the original call.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
SETUP |
this message establishes a second transaction The TI value shall be the same as the one that is in use for the MO call. The TI flag shall have the value specified for an MT call. |
if the MS does not support call waiting |
|||
A2 |
MS -> SS |
RELEASE COMPLETE |
with cause user busy" with the TI of the second transaction |
if the MS supports call waiting |
|||
B2 |
MS -> SS |
CALL CONFIRMED |
with cause user busy" with the TI of the second transaction |
B3 |
MS -> SS |
ALERTING |
with the TI of the second transaction |
B4 |
SS -> MS |
RELEASE COMPLETE |
with the TI of the second transaction |
5 |
SS -> MS |
STATUS ENQUIRY |
with the TI of the original transaction |
6 |
MS -> SS |
STATUS |
cause 30#, state U10 with the TI of the original transaction |
NOTE: The Transaction Identifier of the second transaction shall be different from the one of the already established transaction.
Specific message contents
SETUP message contains a Signal IE with value "call waiting tone on" (H’07).
26.8.1.2.6.7 U10 call active / RELEASE received with Normal call clearing
26.8.1.2.6.7.1 Definition
The call control entity of the MS being in the state, U10, a RELEASE message is received by the MS with cause value 16 “normal call clearing”. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.6.7.2 Conformance requirement
1) A CC-entity of the MS in CC-state U10, "Call Active", upon receipt of the RELEASE shall respond with the RELEASE COMPLETE message and enter the CC-state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 sub clauses 4.5.3, 5.4.2 and 5.4.3.
26.8.1.2.6.7.3 Test purpose
1) To verify that the a CC-entity of the MS in CC-state U10, "Call Active", upon receipt of the RELEASE will respond with the RELEASE COMPLETE message and enter the CC-state U0, "Null".
26.8.1.2.6.7.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U10 by using table 26.8.1.2/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U10. The SS sends a RELEASE message to the MS. The MS shall respond with a RELEASE COMPLETE message.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
with cause "Normal call clearing" |
2 |
MS -> SS |
RELEASE COMPLETE |
the MS starts T3240 |
3 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA) |
Specific message contents:
None
26.8.1.2.7 U11 disconnect request
26.8.1.2.7.1 U11 disconnect request / clear collision
26.8.1.2.7.1.1 Definition
The call control entity of the MS being in the state, U11, a DISCONNECT message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.7.1.2 Conformance requirement
1) A CC-entity of the MS in CC-state U11, "Disconnect Request", upon receipt of a DISCONNECT message, shall return to its peer entity the RELEASE message and enter the CC-state U19, "Release Request".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.5.
26.8.1.2.7.1.3 Test purpose
To verify that the a CC-entity of the MS in CC-state U11, "Disconnect Request", upon receipt of a DISCONNECT message, returns to its peer entity the RELEASE message and enters the CC-state U19, "Release Request".
26.8.1.2.7.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U11 by using table 26.8.1.2/3.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U11. The SS sends a DISCONNECT message to the MS. The MS shall respond with a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity of the MS has entered the state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
|
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
None.
26.8.1.2.7.2 U11 disconnect request / RELEASE received
26.8.1.2.7.2.1 Definition
The call control entity of the MS being in the state, U11, a RELEASE message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.7.2.2 Conformance requirement
1) A CC-entity of the MS in CC-state U11, "Disconnect Request", upon receipt of the RELEASE message shall return RELEASE COMPLETE and enter the CC-state U0, "Null".
2) On returning to the idle mode the MS shall release the MM-connection and the CC-entities relating to the seven mobile originating transaction identifiers shall be in CC-state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.3.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3, 5.5.3.2 and 8.3.
26.8.1.2.7.2.3 Test purpose
1) To verify that the a CC-entity of the MS in CC-state U11, "Disconnect Request", upon receipt of the RELEASE message shall return RELEASE COMPLETE and enter the CC-state U0, "Null".
2) To verify that the MS on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile originating transaction identifiers are in CC-state U0, "Null".
26.8.1.2.7.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U11 by using table 26.8.1.2/3.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U11. The SS sends a RELEASE message to the MS. The MS shall respond with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
|
2 |
MS -> SS |
RELEASE COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.7.3 U11 disconnect request / timer T305 time-out
26.8.1.2.7.3.1 Definition
The call control entity of the MS being in the state, U11, if no response is then received from the SS, timer T305 expires at the MS side. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.7.3.2 Conformance requirement
1) A CC-entity of the MS in CC-state U11, "Disconnect Request" shall on expiry of T305, proceed with the connection release procedure by sending the RELEASE message to its peer entity and shall enter the CC-state U19, "Release Request".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.3 and 11.3.
26.8.1.2.7.3.3 Test purpose
To verify that the CC-entity of the MS in CC-state U11, "Disconnect Request" shall on expiry of T305 (accuracy ±10 %), proceed with the connection release procedure by sending the RELEASE message to its peer entity and enters the CC-state U19, "Release Request".
26.8.1.2.7.3.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U11 by using table 26.8.1.2/3.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
1 minute.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U11. Then T305 expires at the MS and the MS shall send a RELEASE message. The SS checks timer T305 accuracy and that the CC entity has entered the state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS waits until T305 expires at the MS |
|
2 |
MS -> SS |
RELEASE |
SS checks the time between DISCONNECT and RELEASE (note), (T305 ± 10 %) |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
NOTE: With the same cause value as originally contained in the DISCONNECT message. An additional cause information element (#102 recovery on timer expiry) may be included.
26.8.1.2.7.4 U11 disconnect request / lower layer failure
26.8.1.2.7.4.1 Definition
The call control entity of the MS being in the state, U11, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.7.4.2 Conformance requirement
1) A CC-entity of the MS in CC-state U11, "Disconnect Request" having detected a lower layer failure shall return to the idle mode. The CC entities relating to the seven mobile originating transaction identifiers shall be in state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.2.3, 4.5.3, 5.5.3.2 and 8.3.
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.13.2.1.
26.8.1.2.7.4.3 Test purpose
To verify that the a CC-entity of the MS in CC-state U11, "Disconnect Request" having detected a lower layer failure returns to the idle mode. The CC entities relating to the seven mobile originating transaction identifiers are thus in state U0, "Null".
26.8.1.2.7.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U11 by using table 26.8.1.2/4.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 minute 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The MS is brought to the state U11. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure |
|
2 |
SS |
SS waits 20 s for the MS to return to listening to paging |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000…110 |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.7.5 U11 disconnect request / unknown message received
26.8.1.2.7.5.1 Definition
The call control entity of the MS being in the state, U11, an unknown message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.7.5.2 Conformance requirement
1) A CC-entity of the MS in CC-state U11, "disconnect request", having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 8.4.
26.8.1.2.7.5.3 Test purpose
To verify that a CC-entity of the MS in CC-state U11, "disconnect request", having received an unknown message from its peer entity returns a STATUS message.
26.8.1.2.7.5.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U11 by using table 26.8.1.2/4.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U11. The SS sends a message with message type not defined for the protocol discriminator to the MS. The MS shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
unknown message |
message type not defined for PD |
2 |
MS -> SS |
STATUS |
cause 97#, state U11 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
None.
26.8.1.2.8 U12 disconnect indication
26.8.1.2.8.1 U12 disconnect indication / call releasing requested by the user
26.8.1.2.8.1.1 Definition
The call control entity of the MS being in the state, U12, the user requests to terminate the call. This test is applicable only for mobile stations supporting bearer capability for speech.
26.8.1.2.8.1.2 Conformance requirement
1) A CC-entity of the MS in CC-state U12, "Disconnect Indication" being in network initiated call release phase, shall, upon receiving a call release request from the user send a RELEASE to its peer entity and enter CC-state U19, "Release Request".
References
3GPP TS 04.07 / 3GPP TS 24.007 subclause 6.2.2,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
26.8.1.2.8.1.3 Test purpose
To verify that a CC-entity of the MS in CC-state U12, "Disconnect Indication" being in network initiated call release phase, shall, upon receiving a call release request from the user sends a RELEASE to its peer entity and enters CC-state U19, "Release Request"
26.8.1.2.8.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U12 by using Option A of table 26.8.1.2/1.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U12. The user requests termination of the call. The MS shall send a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MMI action, "on hook" |
||
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
None.
26.8.1.2.8.2 U12 disconnect indication / RELEASE received
26.8.1.2.8.2.1 Definition
The call control entity of the MS being in the state, U12, a RELEASE message is received by the MS. This test is applicable only for mobile stations supporting bearer capability for speech.
26.8.1.2.8.2.2 Conformance requirement
1) A CC-entity of the MS in CC-state U12, "Disconnect Indication", upon receipt of a RELEASE message shall return to its peer entity the RELEASE COMPLETE message and enter the CC-state U0, "Null".
2) On returning to the idle mode the MS shall release the MM-connection and the CC-entities relating to the seven mobile originating transaction identifiers shall be in CC-state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.2.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3, 5.5.3.2 and 8.3.
26.8.1.2.8.2.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U12, "Disconnect Indication", upon receipt of a RELEASE message returns to its peer entity the RELEASE COMPLETE message and enters the CC-state U0, "Null".
2) To verify that the MS on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile originating transaction identifiers are in CC-state U0, "Null".
26.8.1.2.8.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U12 by using Option A of table 26.8.1.2/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U12. The SS sends a RELEASE message to the MS. The MS shall respond with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
|
2 |
MS -> SS |
RELEASE COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.8.3 U12 disconnect indication / lower layer failure
26.8.1.2.8.3.1 Definition
The call control entity of the MS being in the state, U12, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable only for mobile stations supporting bearer capability for speech.
26.8.1.2.8.3.2 Conformance requirement
1) A CC-entity of the MS in CC-state U12, "Disconnect Indication" having detected a lower layer failure shall return to idle mode. The CC-entities relating to the seven mobile originating transaction identifiers shall be in state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3.2, 4.5.3, 5.5.3.2, 3.4.13.2.1 and 8.3.
26.8.1.2.8.3.3 Test purpose
To verify that a CC-entity of the MS in CC-state U12, "Disconnect Indication" having detected a lower layer failure returns to idle mode. The CC-entities relating to the seven mobile originating transaction identifiers are thus in state U0, "Null".
26.8.1.2.8.3.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U12 by using Option A of table 26.8.1.2/2.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 minute 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The MS is brought to the state U12. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure |
|
2 |
SS |
SS waits 20 s for the MS to return to listening to paging |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000…110 |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.8.4 U12 disconnect indication / unknown message received
26.8.1.2.8.4.1 Definition
The call control entity of the MS being in the state, U12, an unknown message is received by the MS. This test is applicable only for mobile stations supporting bearer capability for speech.
26.8.1.2.8.4.2 Conformance requirement
A CC-entity of the MS in CC-state U12, "Disconnect Indication" having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 8.4.
26.8.1.2.8.4.3 Test purpose
To verify that a CC-entity of the MS in CC-state U12, "Disconnect Indication" having received an unknown message from its peer entity returns a STATUS message.
26.8.1.2.8.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U12 by using Option A of table 26.8.1.2/3.
Foreseen final state of the MS
U12, disconnect indication.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U12. The SS sends a message with message type not defined for the protocol discriminator to the MS. The MS shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
unknown message |
message type not defined for PD |
2 |
MS -> SS |
STATUS |
cause 97#, state U12 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U12 |
Specific message contents:
None.
26.8.1.2.9 Outgoing call / U19 release request
26.8.1.2.9.1 Outgoing call / U19 release request / timer T308 time-out
26.8.1.2.9.1.1 Definition
The call control entity of the MS being in the state, U19, if no response is then received from the SS, timer T308 expires at the MS side. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.9.1.2 Conformance requirement
1) A CC-entity of the MS in CC-state U19, "Release Request" will, upon the first expiry of timer T308 send the RELEASE message to its peer entity and remain in the CC-state U19.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.4.3.1 and 11.3.
26.8.1.2.9.1.3 Test purpose
To verify that a CC-entity of the MS in CC-state U19, "Release Request" will, upon the first expiry of timer T308 (accuracy ± 10 %) send the RELEASE message to its peer entity and remain in the CC-state U19.
26.8.1.2.9.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U19 by using table 26.8.1.2/4.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
1 min.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U19. When T308 expires at the MS, the MS shall send a RELEASE message. The SS checks timer T308 accuracy and that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS waits until T308 at the MS |
|
2 |
MS -> SS |
RELEASE |
SS checks the time between the two RELEASE messages (T308 ± 10 %) |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
None.
26.8.1.2.9.2 Outgoing call / U19 release request / 2nd timer T308 time-out
26.8.1.2.9.2.1 Definition
The call control entity of the MS being in the state, U19, if no response is then received after timer T308 has expired two times in success at the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.9.2.2 Conformance requirement
1) A CC-entity of the MS in CC-state U19, "Release Request", upon the 2nd expiry of the timer T308, shall enter the CC-state U0, "Null".
2) Subsequently the MS shall proceed with releasing the MM-connection and enter the idle mode with the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.4.3.1 and 11.3.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3 and 5.5.3.2.
26.8.1.2.9.2.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U19, "Release Request", upon the 2nd expiry of the timer T308, enters the CC-state U0, "Null".
2) To verify that subsequently the MS proceeds with releasing the MM-connection and enters the idle mode with the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null".
26.8.1.2.9.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U19 by using table 26.8.1.2/4.
Foreseen final state of the MS
U0, null.
Maximum duration of test
2 min 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U19. The SS allows T308 expiry at the MS, and the MS shall repeat sending the RELEASE message and start timer T308 again. The SS allows again T308 expiry at the MS. The MS shall abort the RR-connection (DISC/UA). The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS waits until T308 expiry at the MS |
|
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
5 |
SS |
SS waits until the second T308 expiry at the MS |
|
6 |
SS |
SS waits T3240 expiry at the MS |
|
7 |
MS |
the main signalling link shall be released by the MS (L2: DISC/UA). |
|
8 |
SS |
SS waits 10 s for the MS to return to listening to paging |
|
9 |
SS -> MS |
PAGING REQUEST |
|
10 |
MS -> SS |
CHANNEL REQUEST |
|
11 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
12 |
MS -> SS |
PAGING RESPONSE |
|
13 |
SS -> MS |
STATUS ENQUIRY |
|
14 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
15 |
SS |
repeat steps 13‑14 to cover all the transaction identifiers from 000…110 |
|
16 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.9.3 Outgoing call / U19 release request / RELEASE received
26.8.1.2.9.3.1 Definition
The call control entity of the MS being in the state, U19, a RELEASE message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.9.3.2 Conformance requirement
1) A CC-entity of the MS in CC-state U19, "Release Request", upon receipt of a RELEASE, shall release the MM-connection and enter the CC-state U0, "Null" with the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.5, 11.3 and 5.5.3.2.
26.8.1.2.9.3.3 Test purpose
To verify that a CC-entity of the MS in CC-state U19, "Release Request", upon receipt of a RELEASE, shall release the MM-connection and enters the CC-state U0, "Null" with the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null".
26.8.1.2.9.3.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U19 by using table 26.8.1.2/4.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U19. The SS sends a RELEASE message to the MS. The MS shall release the MM-connection. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
(note) |
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
4 |
SS |
repeat steps 2‑3 to cover all the transaction identifiers from 000…110 |
|
5 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
NOTE: With the same cause number as originally contained in DISC and optional cause #102 recovery on timer expiry.
26.8.1.2.9.4 Outgoing call / U19 release request / RELEASE COMPLETE received
26.8.1.2.9.4.1 Definition
The call control entity of the MS being in the state, U19, a RELEASE COMPLETE message is received by the MS. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.9.4.2 Conformance requirement
1) A CC-entity of the MS in CC-state U19, "Release Request", upon receipt of a RELEASE COMPLETE, shall release the MM-connection and enter the CC-state U0, "Null" with the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.4.3, 4.5.3 and 8.3.
26.8.1.2.9.4.3 Test purpose
To verify that a CC-entity of the MS in CC-state U19, "Release Request", upon receipt of a RELEASE COMPLETE, shall release the MM-connection and enters the CC-state U0, "Null" with the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null".
26.8.1.2.9.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U19 by using table 26.8.1.2/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U19. The SS sends a RELEASE COMPLETE message to the MS. The MS shall release the MM-connection. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE COMPLETE |
|
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
4 |
SS |
repeat steps 2‑3 to cover all the transaction identifiers from 000…110 |
|
5 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.2.9.5 Outgoing call / U19 release request / lower layer failure
26.8.1.2.9.5.1 Definition
The call control entity of the MS being in the state, U19, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
26.8.1.2.9.5.2 Conformance requirement
A CC-entity of the MS in CC-state U19, "Release Request", having detected a lower layer failure, shall return to the idle mode, the CC entities relating to the seven mobile originating transaction identifiers shall be in state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.2.3, 4.5.3, 5.5.3.2 and 8.3.
26.8.1.2.9.5.3 Test purpose
To verify that a CC-entity of the MS in CC-state U19, "Release Request", having detected a lower layer failure, returns to the idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
26.8.1.2.9.5.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U19 by using table 26.8.1.2/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The MS is brought to the state U19. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure |
|
2 |
SS |
SS waits 20 s for the MS to return to listening to paging |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000…110 |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.3 Establishment of an incoming call / Initial conditions
The tables below describe message exchanges which bring the MS in the requested initial states in case of an incoming call.
A state may be taken as initial only when all the states which lead to this initial states have been validated. The order will be U0, U6, U9, U7, U8, U10, U26 etc. as in the following tables.
Table 26.8.1.3/1: Establishment of an incoming call, procedure 1
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
U0, SDCCH |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
9 |
SS -> MS |
SETUP |
U6, (note 1) |
10 |
MS -> SS |
CALL CONFIRMED |
U9 |
A11 |
MS -> SS |
CONNECT |
U8, p = Y, (note 2) |
B11 |
MS -> SS |
ALERTING |
U7, p = N, (note 2) |
B12 |
MS |
(note 3) |
|
B13 |
MS -> SS |
CONNECT |
U8 |
14 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
15 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
16 |
SS -> MS |
CONNECT ACKNOWLEDGE |
U10 |
NOTE 1: With signal information included in the SETUP message. NOTE 2: The MS is supporting immediate connect (p = Y/N). See PICS/PIXIT statement. NOTE 3: If necessary (see PICS/PIXIT statement), the MS is made to accept the call in the way described in a PICS/PIXIT statement. |
Table 26.8.1.3/2: Establishment of an incoming call, procedure 2
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
U0, SDCCH |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
CIPHERING MODE COMMAND |
|
6 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
7 |
SS -> MS |
SETUP |
U6, (note 1) |
8 |
MS -> SS |
CALL CONFIRMED |
U9 |
A9 |
MS -> SS |
CONNECT |
U8, p = Y, (note 2) |
A10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
A11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
B9 |
MS -> SS |
ALERTING |
U7, p = N, (note 2) |
B10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
B11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
B12 |
MS |
(note 3) |
|
B13 |
MS -> SS |
CONNECT |
U8 |
14 |
SS -> MS |
AUTHENTICATION REQUEST |
|
15 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
16 |
SS -> MS |
CONNECT ACKNOWLEDGE |
U10 |
NOTE 1: With signal information included in the SETUP message. NOTE 2: The MS is supporting immediate connect (p = Y/N). See PICS/PIXIT statement. NOTE 3: If necessary (see PICS/PIXIT statement), the MS is made to accept the call in the way described in a PICS/PIXIT statement. |
Table 26.8.1.3/3: Establishment of an incoming call, procedure 3
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
U0, TCH |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
9 |
SS -> MS |
CHANNEL MODE MODIFY |
(note 1) |
10 |
MS -> SS |
CHANNEL MODE MODIFY ACKNOWLEDGE |
|
11 |
SS -> MS |
SETUP |
U6, (note 2) |
12 |
MS -> SS |
CALL CONFIRMED |
U9 |
A13 |
MS -> SS |
CONNECT |
U8, p = Y, (note 3) |
B13 |
MS -> SS |
ALERTING |
U7, p = N, (note 3) |
B14 |
MS |
(note 4) |
|
B15 |
MS -> SS |
CONNECT |
U8 |
16 |
SS -> MS |
CONNECT ACKNOWLEDGE |
U10 |
NOTE 1: Assigned channel is appropriate for the chosen mobile originated circuit switched basic service. NOTE 2: With signal information included in the SETUP message. NOTE 3: The MS is supporting immediate connect (p = Y/N). See PICS/PIXIT statement. NOTE 4: If necessary (see PICS/PIXIT statement), the MS is made to accept the call in the way described in a PICS/PIXIT statement. |
Table 26.8.1.3/4: Establishment of an incoming call, procedure 4
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
U0, SDCCH |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
CIPHERING MODE COMMAND |
|
6 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
7 |
SS -> MS |
SETUP |
U6, (note 1) |
8 |
MS -> SS |
CALL CONFIRMED |
U9 |
9 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
10 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
A11 |
MS -> SS |
CONNECT |
U8, p = Y, (note 2) |
B11 |
MS -> SS |
ALERTING |
U7, p = N, (note 2) |
B12 |
MS |
(note 3) |
|
B13 |
MS -> SS |
CONNECT |
U8 |
14 |
SS -> MS |
AUTHENTICATION REQUEST |
|
15 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
16 |
SS -> MS |
CONNECT ACKNOWLEDGE |
U10 |
NOTE 1: The signal information element is not included in the SETUP message. NOTE 2: The MS is supporting immediate connect (p = Y/N). See PICS/PIXIT statement. NOTE 3: If necessary (see PICS/PIXIT statement), the MS is made to accept the call in the way described in a PICS/PIXIT statement. |
26.8.1.3.1 Incoming call / U0 null state
26.8.1.3.1.1 Incoming call / U0 null state / SETUP received with a non supported bearer capability
26.8.1.3.1.1.1 Definition
The call control entity of the MS being in the state, U0, a SETUP message is received with only one bearer capability and this bearer capability is not supported by the MS. This test is applicable for all equipment.
26.8.1.3.1.1.2 Conformance requirement
1) A CC entity of the MS, upon receipt of SETUP containing one bearer capability and this bearer capability is not supported, shall return a RELEASE COMPLETE with correct cause value to its peer entity and return to the idle mode. The CC-entities relating to the seven mobile terminating transaction identifiers shall be in the state U0,"Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.2.2 and annex B.
26.8.1.3.1.1.3 Test purpose
To verify that a CC entity of the MS, upon receipt of SETUP containing one bearer capability and this bearer capability is not supported, returns a RELEASE COMPLETE with correct cause value to its peer entity, and returns to the idle mode. To verify that the CC-entities relating to the seven mobile terminating transaction identifiers are then in the state U0,"Null".
26.8.1.3.1.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
U0, null.
Maximum duration of test
30 s.
Test procedure
A mobile terminated call is initiated. The MS receives a SETUP message that contains a bearer capability not supported by the MS. The MS returns a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity is still in the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST |
SS sends paging |
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
(SDCCH) |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
9 |
SS -> MS |
SETUP |
(note 1) |
10 |
MS -> SS |
RELEASE COMPLETE |
(note 2) |
11 |
SS -> MS |
STATUS ENQUIRY |
|
12 |
MS ->SS |
RELEASE COMPLETE |
Cause #81 (invalid TI value). |
13 |
SS |
Repeat steps 11‑12 to cover all the transaction identifiers from 000… 110. |
Specific message contents:
NOTE 1: With one bearer capability and that bearer capability is not supported by the MS.
NOTE 2: With cause #88 incompatible destination.
26.8.1.3.2 Incoming call / U6 call present
26.8.1.3.2.1 Incoming call / U6 call present / automatic call rejection
26.8.1.3.2.1.1 Definition
Although the state U6 is transient, the ability to refuse a call (automatically) in this state is tested, if it is implemented at the MS. The test is applicable for those equipments described above supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.2.1.2 Conformance requirement
1) A CC entity of the MS in CC-state U6, "Call Present", upon receipt of a rejection indication of the incoming call from the user, send RELEASE COMPLETE with the appropriate cause value to its peer entity and enter the CC-state U0, "Null". The CC entities relating to the seven mobile terminating transaction identifiers shall be in state U0, "Null".
References
3GPP TS 04.07 / 3GPP TS 24.007 subclause 6.2.2,
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.2.3.1, 5.5.3.2 and 8.3.
26.8.1.3.2.1.3 Test purpose
To verify that a CC entity of the MS in CC-state U6, "Call Present", shall upon receipt of a rejection indication of the incoming call from the user, shall send RELEASE COMPLETE with the appropriate cause value to its peer entity and enter the CC-state U0, "Null". The CC entities relating to the seven mobile terminating transaction identifiers are then in state U0, "Null".
26.8.1.3.2.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U6 by using table 26.8.1.3/2.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
A teleservice is selected that is supported by the MS; if the MS supports speech, the selected teleservice is speech. If necessary, the MS is configured for that teleservice. Then a mobile terminated call is initiated. The call control entire of the MS is brought to the state U6 (Note: The state U6 is not checked, since it is not stable). The MS is made to refuse the call (the refusal may require some preliminary preparations in order to achieve refusal at this point). The MS shall send a RELEASE COMPLETE message and enter a call control state U0. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
the MS is made to refuse the call |
||
2 |
MS -> SS |
RELEASE COMPLETE |
(note) |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
NOTE: With cause value #21 call rejected.
26.8.1.3.3 Incoming call / U9 mobile terminating call confirmed
26.8.1.3.3.1 Incoming call / U9 mobile terminating call confirmed / alerting or immediate connecting
26.8.1.3.3.1.1 Definition
The call control entity of the MS having entered the state, U9, with signal information received in the preceding SETUP message, the subsequent behaviour of the MS is tested. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.3.1.2 Conformance requirement
1) A CC entity in CC-state U9, "MS Terminating Call Confirmed", (if signalled by the network in previous SETUP message that it may alert) shall either send a ALERTING message to its peer entity and enter state U7, or send a CONNECT message to its peer entity and enter U8.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.2.3.2
26.8.1.3.3.1.3 Test purpose
To verify that a CC entity in CC-state U9, "MS Terminating Call Confirmed", (if signalled by the network in previous SETUP message that it may alert) will either send a ALERTING message to its peer entity and enter state U7, or send a CONNECT message to its peer entity and enter U8.
26.8.1.3.3.1.4 Method of test
Specific PICS statements
– Support of immediate connect (TSPC_AddInfo_ImmConn)
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U9 by using table 26.8.1.3/2.
Foreseen final state of the MS
– U8, connect request, if the MS supports immediate connect for the selected basic service;
– otherwise U7, call received.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U9 by using a SETUP message containing signalling information element. (The state U9 is not a stable state in this case, and consequently it is not checked as an initial state.) If the MS supports immediate connect for the selected basic service (p = Y), it sends a CONNECT message and enters the state U8, connect request. Otherwise (p = N) the MS sends an ALERTING message and enters the state U7, call receiving. The SS checks by using the status enquiry procedure that the CC entity has entered its state as described.
Expected sequence
Step |
Direction |
Message |
Comments |
A1 |
MS -> SS |
CONNECT |
p = Y |
A2 |
SS -> MS |
STATUS ENQUIRY |
|
A3 |
MS -> SS |
STATUS |
cause 30#, state U8 |
B1 |
MS -> SS |
ALERTING |
p = N |
B2 |
SS -> MS |
STATUS ENQUIRY |
|
B3 |
MS -> SS |
STATUS |
cause 30#, state U7 |
Specific message contents:
None.
26.8.1.3.3.2 Incoming call / U9 mobile terminating call confirmed / TCH assignment
26.8.1.3.3.2.1 Definition
The call control entity of the MS being in the state, U9, an assignment procedure is performed for traffic channel. This test is applicable for any equipment supporting at least one MT circuit switched basic service, for which immediate connect is not used.
26.8.1.3.3.2.2 Conformance requirement
1) A CC-entity of the MS in CC-state U9, "MS Terminating Call Confirmed", when allocated a traffic channel by the network performing the assignment procedure, shall perform a layer 2 establishment on the FACCH, send a ALERTING message and enter state U7.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 3.4.3, 5.2.2.7 and 5.2.2.3.2.
26.8.1.3.3.2.3 Test purpose
To verify that a CC-entity of the MS in CC-state U9, "MS Terminating Call Confirmed", when allocated a traffic channel by the network performing the assignment procedure, performs a layer 2 establishment on the FACCH, sends a ALERTING message and enters state U7.
26.8.1.3.3.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U9 by using table 26.8.1.3/4.
Foreseen final state of the MS
U9, mobile terminating call confirmed.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U9 (by using a SETUP message not containing the signal information element). The SS sends an ASSIGNMENT COMMAND for traffic channel to the MS. The MS shall establish layer 2 link on the newly allocated channel and respond with an ASSIGNMENT COMPLETE message. The MS sends an ALERTING message and enters state U7, call received. The SS verifies by using the status enquiry procedure that the MS has entered the correct state.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH, an appropriate non-signalling mode |
2 |
MS |
the MS shall establish L2 link |
|
3 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
4 |
MS -> SS |
ALERTING |
|
5 |
SS -> MS |
STATUS ENQUIRY |
|
6 |
MS -> SS |
STATUS |
cause 30#, state U7 |
Specific message contents:
None.
26.8.1.3.3.3 Void
26.8.1.3.3.4 Incoming call / U9 mobile terminating call confirmed / DISCONNECT received
26.8.1.3.3.4.1 Definition
The call control entity of the MS being in the state, U9, a DISCONNECT message is received by the MS. This test is applicable for any equipment supporting at least one MT circuit switched basic service, for which immediate connect is not used.
26.8.1.3.3.4.2 Conformance requirement
1) A CC-entity of the MS in CC-state U9, "MS Terminating Call Confirmed", upon receipt of a DISCONNECT shall return a RELEASE message and enter the CC-state U19, "Release Request".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
26.8.1.3.3.4.3 Test purpose
To verify that a CC-entity of the MS in CC-state U9, "MS Terminating Call Confirmed", upon receipt of a DISCONNECT returns a RELEASE message and enters the CC-state U19, "Release Request".
26.8.1.3.3.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U9 by using table 26.8.1.3/4.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U9. The SS sends a DISCONNECT message to the MS. The MS responds by sending a RELEASE message and enters state U19, release request. The SS verifies by using the status enquiry procedure that the MS has entered the correct state.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
|
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
None.
26.8.1.3.3.5 Incoming call / U9 mobile terminating call confirmed / RELEASE received
26.8.1.3.3.5.1 Definition
The call control entity of the MS being in the state, U9, a RELEASE message is received by the MS. This test is applicable for any equipment supporting at least one MT circuit switched basic service, for which immediate connect is not used.
26.8.1.3.3.5.2 Conformance requirement
1) A CC-entity of the MS in CC-state U9, "MS Terminating Call Confirmed", upon receipt of a RELEASE shall return a RELEASE COMPLETE and enter the CC-state U0, "Null".
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
2) On returning to the idle mode the MS shall release the MM-connection and the CC-entities relating to the seven mobile terminating transaction identifiers shall be in CC-state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3, 5.5.3.2 and 8.3.
26.8.1.3.3.5.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U9, "MS Terminating Call Confirmed", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".
2) To verify that the MS on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile terminating transaction identifiers are in CC-state U0, "Null".
26.8.1.3.3.5.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U9 by using table 26.8.1.3/4.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U9. The SS sends a RELEASE message to the MS. The MS responds by sending a RELEASE COMPLETE message and enters state U0, null. The SS verifies by using the status enquiry procedure that the MS has entered the correct state with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
with cause "Normal, unspecified" |
2 |
MS -> SS |
RELEASE COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.3.3.6 Incoming call / U9 mobile terminating call confirmed / lower layer failure
26.8.1.3.3.6.1 Definition
The call control entity of the MS being in the state, U9, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one MT circuit switched basic service, for which immediate connect is not used.
26.8.1.3.3.6.2 Conformance requirement
1) A CC entity of the MS in CC-state U9, "MS Terminating Call Confirmed", having detected a lower layer failure shall return to idle mode with the CC entities relating to the seven mobile terminating transaction identifiers in CC-state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.2.3, 4.5.3, 5.5.3.2 and 8.3.
26.8.1.3.3.6.3 Test purpose
To verify that a CC entity of the MS in CC-state U9, "MS Terminating Call Confirmed", having detected a lower layer failure returns to idle mode with the CC entities relating to the seven mobile terminating transaction identifiers in CC-state U0, "Null".
26.8.1.3.3.6.4 Method of test
Specific PICS statements
– Support of UTRAN Radio Access Technology (TSPC_Type_UTRAN)
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U9 by using table 26.8.1.3/4.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The MS is brought to the state U9. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure |
|
2 |
SS |
If PICS statement “Support of UTRAN Radio Access Technology” is ‘NO’, then the SS waits 20 s for the MS to return to listening to paging. If PICS statement “Support of UTRAN Radio Access Technology” is ‘YES’, then the SS waits 50 s for the MS to return to listening to paging. |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000…110 |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.3.3.7 Incoming call / U9 mobile terminating call confirmed / unknown message received
26.8.1.3.3.7.1 Definition
The call control entity of the MS being in the state, U9, an unknown message is received by the MS. This test is applicable for any equipment supporting at least MT circuit switched basic service, for which immediate connect is not used.
26.8.1.3.3.7.2 Conformance requirement
1) A CC-entity of the MS in CC-state U9, "MS Terminating Call Confirmed" having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 8.4.
26.8.1.3.3.7.3 Test purpose
To verify that a CC-entity of the MS in CC-state U9, "MS Terminating Call Confirmed" having received an unknown message from its peer entity returns a STATUS message.
26.8.1.3.3.7.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U9 by using table 26.8.1.3/4.
Foreseen final state of the MS
U9, mobile terminating call proceeding.
Maximum duration of test
30 s.
Test procedure
A MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U9. The SS sends a message with message type not defined for the protocol discriminator to the MS. The MS shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
unknown message |
message type not defined for PD |
2 |
MS -> SS |
STATUS |
cause 97#, state U9 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U9 |
Specific message contents:
None.
26.8.1.3.4 Incoming call / U7 call received
26.8.1.3.4.1 Incoming call / U7 call received / call accepted
26.8.1.3.4.1.1 Definition
The call control entity of the MS being in the state, U7, a user accepts the incoming call. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service for which immediate connect is not used.
26.8.1.3.4.1.2 Conformance requirement
1) A CC entity of a MS in CC-state U7, "Call Received", upon a user accepting the incoming call, shall send a CONNECT message to its peer entity and enter the CC-state U8, "Connect Request".
References
3GPP TS 04.07 / 3GPP TS 24.007 subclause 6.2.2,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.2.5.
26.8.1.3.4.1.3 Test purpose
To verify that a CC entity of a MS in CC-state U7, "Call Received", upon a user accepting the incoming call, shall send a CONNECT message to its peer entity and enter the CC-state U8, "Connect Request"
26.8.1.3.4.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U7 by using table 26.8.1.3/3.
Foreseen final state of the MS
U8, connect request.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U7. The user accepts the incoming call. The MS sends a CONNECT message. The SS checks by using the status enquiry procedure that the CC entity has entered state U8, connect request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
the MS is made to accept the call by the user |
||
2 |
MS -> SS |
CONNECT |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U8 |
Specific message contents:
None.
26.8.1.3.4.2 Incoming call / U7 call received / termination requested by the user
26.8.1.3.4.2.1 Definition
The call control entity of the MS being in the state, U7, a user requests to terminate incoming call. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service for which immediate connect is not used.
26.8.1.3.4.2.2 Conformance requirement
1) A CC entity of a MS in CC-state U7, "Call Received", upon request by the user to terminate shall send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
References
3GPP TS 04.07 / 3GPP TS 24.007 subclause 6.2.2,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.3.
26.8.1.3.4.2.3 Test purpose
To verify that a CC entity of a MS in CC-state U7, "Call Received", upon request by the user to terminate will send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
26.8.1.3.4.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U7 by using table 26.8.1.3/3.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U7. The user initiates clearing the incoming call. The MS sends a DISCONNECT message. The SS checks by using the status enquiry procedure that the CC entity has entered state U11, disconnect request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
the MS is made to terminate/reject the call |
||
2 |
MS -> SS |
DISCONNECT |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
None.
26.8.1.3.4.3 Incoming call / U7 call received / DISCONNECT received
26.8.1.3.4.3.1 Definition
The call control entity of the MS being in the state, U7, a DISCONNECT message is received by the MS. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service for which immediate connect is not used.
26.8.1.3.4.3.2 Conformance requirement
1) A CC entity of a MS in CC-state U7, "Call Received", upon receipt of a DISCONNECT with a progress indicator indicating in-band information from network, if a TCH was not assigned, shall return a RELEASE message and enter the CC-state U19, "Release Request".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
26.8.1.3.4.3.3 Test purpose
To verify that a CC entity of a MS in CC-state U7, "Call Received", upon receipt of a DISCONNECT with a progress indicator indicating in-band information from network, if a TCH was not assigned, returns a RELEASE message and enters the CC-state U19, "Release Request".
26.8.1.3.4.3.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U7 by using table 26.8.1.3/1.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U7. The SS sends a DISCONNECT message. The MS responds with a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity has entered state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
(note) |
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
NOTE: With a progress indicator indicating in-band information; Progress Indicator, Progress Description #8.
26.8.1.3.4.4 Incoming call / U7 call received / RELEASE received
26.8.1.3.4.4.1 Definition
The call control entity of the MS being in the state, U7, a RELEASE message is received by the MS. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service for which immediate connect is not used.
26.8.1.3.4.4.2 Conformance requirement
1) A CC entity of a MS in CC-state U7, "Call Received", upon receipt of a RELEASE shall return a RELEASE COMPLETE and enter the CC-state U0, "Null".
2) On returning to the idle mode the MS shall release the MM-connection and the CC-entities relating to the seven mobile terminating transaction identifiers shall be in CC-state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3 and 5.5.3.2.
26.8.1.3.4.4.3 Test purpose
1) To verify that a CC entity of a MS in CC-state U7, "Call Received", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".
2) To verify that the MS on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile terminating transaction identifiers are in CC-state U0, "Null".
26.8.1.3.4.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U7 by using table 26.8.1.3/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U7. The SS sends a RELEASE message. The MS responds with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered state U0, null, with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
with cause "Normal, unspecified" |
2 |
MS -> SS |
RELEASE COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.3.4.5 Incoming call / U7 call received / lower layer failure
26.8.1.3.4.5.1 Definition
The call control entity of the MS being in the state, U7, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service for which immediate connect is not used.
26.8.1.3.4.5.2 Conformance requirement
1) A CC entity of a MS in CC-state U7, "Call Received", having detected a lower layer failure shall return to idle mode with the CC entities relating to the seven mobile terminating transaction identifiers in CC-state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.2.3, 4.5.3, 5.5.3.2 and 8.3.
26.8.1.3.4.5.3 Test purpose
To verify that a CC entity of a MS in CC-state U7, "Call Received", having detected a lower layer failure returns to idle mode with the CC entities relating to the seven mobile terminating transaction identifiers in CC-state U0, "Null".
26.8.1.3.4.5.4 Method of test
Specific PICS statements
– Support of UTRAN Radio Access Technology
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U7 by using table 26.8.1.3/2.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The MS is brought to the state U7. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure |
|
2 |
SS |
If PICS statement “Support of UTRAN Radio Access Technology” is ‘NO’, then the SS waits 20 s for the MS to return to listening to paging. If PICS statement “Support of UTRAN Radio Access Technology” is ‘YES’, then the SS waits 50 s for the MS to return to listening to paging. |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000…110 |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.3.4.6 Incoming call / U7 call received / unknown message received
26.8.1.3.4.6.1 Definition
The call control entity of the MS being in the state, U7, an unknown message is received by the MS. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service for which immediate connect is not used.
26.8.1.3.4.6.2 Conformance requirement
1) A CC entity of a MS in CC-state U7, "Call Received", having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 8.4.
26.8.1.3.4.6.3 Test purpose
To verify that a CC entity of a MS in CC-state U7, "Call Received", having received an unknown message from its peer entity returns a STATUS message.
26.8.1.3.4.6.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U7 by using table 26.8.1.3/3.
Foreseen final state of the MS
U7, call received.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U7. The SS sends a message with message type not defined for the protocol discriminator to the MS. The MS shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
unknown message |
message type not defined for PD |
2 |
MS -> SS |
STATUS |
cause 97#, state U7 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U7 |
Specific message contents:
None.
26.8.1.3.4.7 Incoming call / U7 call received / TCH assignment
26.8.1.3.4.7.1 Definition
The call control entity of the MS being in the state, U7, an assignment procedure is performed for traffic channel. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service for which immediate connect is not used.
26.8.1.3.4.7.2 Conformance requirement
1) A CC entity of a MS in CC-state U7, "Call Received", when allocated a traffic channel by the network performing the assignment procedure, shall perform a layer 2 establishment on the FACCH without changing the state of the call in progress.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.2.7.
26.8.1.3.4.7.3 Test purpose
To verify that a CC entity of a MS in CC-state U7, "Call Received", when allocated a traffic channel by the network performing the assignment procedure, shall perform a layer 2 establishment on the FACCH without changing the state of the call in progress.
26.8.1.3.4.7.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U7 by using table 26.8.1.3/1.
Foreseen final state of the MS
U7, call received.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U7. The SS sends an ASSIGNMENT COMMAND for traffic channel to the MS. The MS shall establish layer 2 link on the newly allocated channel and respond with an ASSIGNMENT COMPLETE message. The SS verifies by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
2 |
MS |
the MS shall establish L2 link |
|
3 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
4 |
SS -> MS |
STATUS ENQUIRY |
|
5 |
MS -> SS |
STATUS |
cause 30#, state U7 |
Specific message contents:
None.
26.8.1.3.4.8 Incoming call / U7 call received / RELEASE COMPLETE received
26.8.1.3.4.8.1 Definition
The call control entity of the MS being in the state, U7, the call is cleared by a RELEASE COMPLETE message sent by the SS. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service, for which immediate connect is not used.
26.8.1.3.4.8.2 Conformance requirement
1) A CC entity of the MS in CC-state U7, "call received", upon receipt of a RELEASE COMPLETE message with valid cause value, shall enter CC state U0, "Null".
2) On returning to idle mode, the CC entities relating to the seven mobile terminating transaction identifiers shall be in state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.4.2 and 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.4.4.3.
26.8.1.3.4.8.3 Test purpose
1) To verify that a CC entity of the MS in CC-state U7, "Call received", upon receipt of a RELEASE COMPLETE message with valid cause value, enters CC state U0, "Null".
2) To verify that in returning to idle mode, the CC entities relating to the seven mobile terminating transaction identifiers are in state U0, "Null".
26.8.1.3.4.8.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U7 by using table 26.8.1.3/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS and for which the MS does not use immediate connection; if the MS supports MT telephony without immediate connection, the selected service is telephony. If necessary, the MS is configured for that basic service. The a mobile terminated call is initiated. the CC entity of the MS is brought to U7. The SS sends a RELEASE COMPLETE message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE COMPLETE |
note 1 |
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value), note 2 |
4 |
SS |
repeat steps 2‑3 to cover all the transaction identifiers from 000…110 |
|
5 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
NOTE 1: With the cause value chosen arbitrarily.
NOTE 2: TI flag has the value indicating the SS as a originator of the call.
26.8.1.3.5 Incoming call / U8 connect request
26.8.1.3.5.1 Incoming call / U8 connect request / CONNECT acknowledged
26.8.1.3.5.1.1 Definition
The call control entity of the MS being in the state, U8, a CONNECT ACKNOWLEDGE message is received by the MS. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.1.2 Conformance requirement
A CC entity of a MS in CC-state U8, "Connect Request", upon receipt of CONNECT ACKNOWLEDGE shall enter the CC-state U10, "Call Active".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.2.6.
26.8.1.3.5.1.3 Test purpose
To verify that a CC entity of a MS in CC-state U8, "Connect Request", upon receipt of CONNECT ACKNOWLEDGE shall enter the CC-state U10, "Call Active".
26.8.1.3.5.1.4 Method of test
Specific PICS statements
– Support of immediate connect (TSPC_AddInfo_ImmConn)
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U8 by using table 26.8.1.3/2.
Foreseen final state of the MS
U10, active.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U8 (if the MS uses immediate connection for the selected basic service then p = Y, otherwise p = N). The SS sends a CONNECT ACKNOWLEDGE message. The SS checks by using the status enquiry procedure that the CC entity of the MS has entered state U10, active.
Expected sequence
Step |
Direction |
Message |
Comments |
A1 |
SS -> MS |
ASSIGNMENT COMMAND |
p = Y |
A2 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
3 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
4 |
SS -> MS |
STATUS ENQUIRY |
|
5 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
None.
26.8.1.3.5.2 Incoming call / U8 connect request / timer T313 time-out
26.8.1.3.5.2.1 Definition
The call control entity of the MS being in the state, U8, if no response is then received from the SS, timer T313 expires at the MS side. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.2.2 Conformance requirement
A CC entity of a MS in CC-state U8, "Connect Request", having waited for a reasonable length of time (e.g. expiry of timer T313) without receiving the appropriate protocol message to complete the incoming call, shall initiate the clearing of that incoming call by sending the CC message DISCONNECT and enter the CC-state U11, "Disconnect Request".
If an MS disconnects too early then, in the case of very late assignment of a traffic channel, systematic waste of radio resources may occur.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.2.6 and 5.4.3.
26.8.1.3.5.2.3 Test purpose
To verify that a CC entity of a MS in CC-state U8, "Connect Request", having waited for a reasonable length of time (e.g. expiry of timer T313) without receiving the appropriate protocol message to complete the incoming call, shall initiate the clearing of that incoming call by sending the CC message DISCONNECT and enter the CC-state U11, "Disconnect Request"
26.8.1.3.5.2.4 Method of test
Specific PICS statements
– Support of immediate connect (TSPC_AddInfo_ImmConn)
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U8 by using table 26.8.1.3/2.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
45 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U8 (if the MS uses immediate connection for the selected basic service then p = Y, otherwise p = N). The T313 expires at the MS and the MS sends a DISCONNECT message and enters state U11, disconnect request. The SS checks by using the status enquiry procedure that the MS has entered the correct state.
Expected sequence
Step |
Direction |
Message |
Comments |
A1 |
SS -> MS |
ASSIGNMENT COMMAND |
p = Y |
A2 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
3 |
MS -> SS |
DISCONNECT |
Shall not be sent before 15 s after entry into state U8. But, shall be sent before 1,1 * T313 after entry into state U8. |
4 |
SS -> MS |
STATUS ENQUIRY |
|
5 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
None.
26.8.1.3.5.3 Incoming call / U8 connect request / termination requested by the user
26.8.1.3.5.3.1 Definition
The call control entity of the MS being in the state, U8, the user requests for releasing of the call. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.3.2 Conformance requirement
1) A CC entity of a MS in CC-state U8, "Connect Request", upon request by the user to terminate shall send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
References
3GPP TS 04.07 / 3GPP TS 24.007 subclause 6.2.2,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.3
26.8.1.3.5.3.3 Test purpose
To verify that a CC entity of a MS in CC-state U8, "Connect Request", upon request by the user to terminate will send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".
26.8.1.3.5.3.4 Method of test
Specific PICS statements
– MT circuit switched basic services for which immediate connect is not used.
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U8 by using table 26.8.1.3/2.
Foreseen final state of the MS
U11, disconnect request.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U8 (if the MS uses immediate connection for the selected basic service then p = Y, otherwise p = N). Then the user requests termination of the call. The MS sends a DISCONNECT message and enters state U11, disconnect request. The SS verifies by using the status enquiry procedure that the MS has entered the correct state.
Expected sequence
Step |
Direction |
Message |
Comments |
A1 |
SS -> MS |
ASSIGNMENT COMMAND |
p = Y |
A2 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
3 |
the user requests to clear the call |
||
4 |
MS -> SS |
DISCONNECT |
|
5 |
SS -> MS |
STATUS ENQUIRY |
|
6 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
None.
26.8.1.3.5.4 Incoming call / U8 connect request / DISCONNECT received with in-band information
26.8.1.3.5.4.1 Definition
The call control entity of the MS being in the state, U8, a DISCONNECT message indicating availability of in band information is received by the MS. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.4.2 Conformance requirement
A CC entity of a MS in CC-state U8, "Connect Request", upon receipt of a DISCONNECT with progress indicator #8 shall enter CC-state U12, if the traffic channel is in speech mode. If the TCH is not in speech mode, the MS shall send a RELEASE message and enter CC-state U19.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.4 and 5.5.1.
26.8.1.3.5.4.3 Test purpose
To verify that a CC entity of a MS in CC-state U8, "Connect Request", upon receipt of a DISCONNECT with progress indicator #8 enters CC-state U12, if the traffic channel is in speech mode, and that the MS sends a RELEASE message and enters CC-state U19 if the TCH is not in speech mode.
26.8.1.3.5.4.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN. The MS is brought into the state U8 by using table 26.8.1.3/3.
Foreseen final state of the MS
U12, disconnect indication or U19 depending on the bearer capabilities.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U8. The SS sends a DISCONNECT message containing indication of in-band information availability to the MS. If channel mode is speech, the MS enters state U12, disconnect indication. If channel mode is not speech, the MS sends a RELEASE message and enters state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
(note) |
TCH in speech mode: |
|||
A2 |
SS -> MS |
STATUS ENQUIRY |
|
A3 |
MS -> SS |
STATUS |
cause 30#, state U12 |
TCH is not in speech mode: |
|||
B2 |
MS -> SS |
RELEASE |
|
B3 |
SS -> MS |
STATUS ENQUIRY |
|
B4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
NOTE: With a progress indicator indicating in-band information; Progress Indicator, Progress description #8.
26.8.1.3.5.5 Incoming call / U8 connect request / DISCONNECT received without in-band information
26.8.1.3.5.5.1 Definition
The call control entity of the MS being in the state, U8, a DISCONNECT message is received by the MS. The DISCONNECT message does not contain indication of in-band information availability. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.5.2 Conformance requirement
1) A CC entity of a MS in CC-state U8, "Connect Request", upon receipt of a DISCONNECT without progress indicator, shall return a RELEASE message and enter the CC-state U19, "Release Request".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.4 and 5.4.4.2.
26.8.1.3.5.5.3 Test purpose
To verify that a CC entity of a MS in CC-state U8, "Connect Request", upon receipt of a DISCONNECT without progress indicator, returns a RELEASE message and enters the CC-state U19, "Release Request".
26.8.1.3.5.5.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U8 by using table 26.8.1.3/3.
Foreseen final state of the MS
U19, release request.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U8. The SS sends a DISCONNECT message not containing indication of in-band information availability to the MS. The MS shall respond with a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity of the MS has entered the state U19, release request.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
DISCONNECT |
(note) |
2 |
MS -> SS |
RELEASE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U19 |
Specific message contents:
NOTE: Without a progress indicator indicating in-band information.
26.8.1.3.5.6 Incoming call / U8 connect request / RELEASE received
26.8.1.3.5.6.1 Definition
The call control entity of the MS being in the state, U8, a RELEASE message is received by the MS. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.6.2 Conformance requirement
1) A CC entity of a MS in CC-state U8, "Connect Request", upon receipt of a RELEASE shall return a RELEASE COMPLETE and enter the CC-state U0, "Null".
2) On returning to the idle mode the MS shall release the MM-connection and the CC-entities relating to the seven mobile terminating transaction identifiers shall be in CC-state U0, "Null".
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.3 and 5.5.3.2.
26.8.1.3.5.6.3 Test purpose
1) To verify that a CC entity of a MS in CC-state U8, "Connect Request", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".
2) To verify that the MS on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile terminating transaction identifiers are in CC-state U0, "Null".
26.8.1.3.5.6.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U8 by using table 26.8.1.3/3.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U8. The SS sends a RELEASE message. The MS responds with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered state U0, null, with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
RELEASE |
with cause "Normal, unspecified" |
2 |
MS -> SS |
RELEASE COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
5 |
SS |
repeat steps 3‑4 to cover all the transaction identifiers from 000…110 |
|
6 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.3.5.7 Incoming call / U8 connect request / lower layer failure
26.8.1.3.5.7.1 Definition
The call control entity of the MS being in the state, U8, a lower layer failure is accomplished at the MS and consequently, communication at layer 3 level with the peer entity is terminated. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.7.2 Conformance requirement
1) A CC entity of a MS in CC-state U8, "Connect Request", having detected a lower layer failure shall return to idle mode with the CC entities relating to the seven mobile terminating transaction identifiers in CC-state U0, "Null".
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.2.3, 4.5.3 and 5.5.3.2.
26.8.1.3.5.7.3 Test purpose
To verify that a CC entity of a MS in CC-state U8, "Connect Request", having detected a lower layer failure returns to idle mode with the CC entities relating to the seven mobile terminating transaction identifiers in CC-state U0, "Null".
26.8.1.3.5.7.4 Method of test
Specific PICS statements
– Support of UTRAN Radio Access Technology (TSPC_Type_UTRAN)
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U8 by using table 26.8.1.3/1.
Foreseen final state of the MS
U0, null.
Maximum duration of test
1 min 30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The MS is brought to the state U8. The SS generates a lower layer failure at the MS. The SS waits long enough to enable the MS to return to idle state listening to paging, and then pages MS to create RR-connection. Finally, the SS will check the state of the MS by using STATUS ENQUIRY with the relevant transaction identifiers.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS |
SS generates lower layer failure |
|
2 |
SS |
If PICS statement “Support of UTRAN Radio Access Technology” is ‘NO’, then the SS waits 20 s for the MS to return to listening to paging. If PICS statement “Support of UTRAN Radio Access Technology” is ‘YES’, then the SS waits 50 s for the MS to return to listening to paging. |
|
3 |
SS -> MS |
PAGING REQUEST |
|
4 |
MS -> SS |
CHANNEL REQUEST |
|
5 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
PAGING RESPONSE |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
RELEASE COMPLETE |
cause 81# (invalid TI value) |
9 |
SS |
repeat steps 7‑8 to cover all the transaction identifiers from 000…110 |
|
10 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA). |
Specific message contents:
None.
26.8.1.3.5.8 Incoming call / U8 connect request / TCH assignment
26.8.1.3.5.8.1 Definition
The call control entity of the MS being in the state, U8, an assignment procedure is performed for traffic channel. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.8.2 Conformance requirement
1) A CC entity of a MS in CC-state U8, "Connect Request", when allocated a traffic channel by the network performing the assignment procedure, shall perform a layer 2 establishment on the FACCH without changing the state of the call in progress.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.2.7.
26.8.1.3.5.8.3 Test purpose
To verify that a CC entity of a MS in CC-state U8, "Connect Request", when allocated a traffic channel by the network performing the assignment procedure, shall perform a layer 2 establishment on the FACCH without changing the state of the call in progress.
26.8.1.3.5.8.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U8 by using table 26.8.1.3/1.
Foreseen final state of the MS
U8, connect request.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U8. The SS sends an ASSIGNMENT COMMAND for traffic channel to the MS. The MS shall establish layer 2 link on the newly allocated channel and respond with an ASSIGNMENT COMPLETE message. The SS verifies by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
2 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U8 |
Specific message contents:
None.
26.8.1.3.5.9 Incoming call / U8 connect request / unknown message received
26.8.1.3.5.9.1 Definition
The call control entity of the MS being in the state, U8, an unknown message is received by the MS. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.3.5.9.2 Conformance requirement
1) A CC entity of a MS in CC-state U8, "Connect Request", having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclause 8.4.
26.8.1.3.5.9.3 Test purpose
To verify that a CC entity of a MS in CC-state U8, "Connect Request", having received an unknown message from its peer entity returns a STATUS message.
26.8.1.3.5.9.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U8 by using table 26.8.1.3/1.
Foreseen final state of the MS
U8, connect request.
Maximum duration of test
30 s.
Test procedure
An MT circuit switched basic service is selected that is supported by the MS; if the MS supports MT telephony, the selected basic service is telephony. If necessary the MS is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the MS is brought to the state U8. The SS sends a message with message type not defined for the protocol discriminator to the MS. The MS shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
unknown message |
message type not defined for PD |
2 |
MS -> SS |
STATUS |
cause 97#, state U8 |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U8 |
Specific message contents:
None.
26.8.1.4 In call functions
26.8.1.4.1 In-call functions / DTMF information transfer
26.8.1.4.1.1 In-call functions / DTMF information transfer / basic procedures
26.8.1.4.1.1.1 Definition
Dual Tone Multi Frequency (DTMF) is an inband one out of four plus one out of four signalling system primarily used from terminal instruments in telecommunication networks.
The support of DTMF is only permitted when a bearer capability for speech is in use or during the speech phase of alternate speech/data and alternate speech/facsimile teleservices.
26.8.1.4.1.1.2 Conformance requirement
1) An MS supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone, shall send a START DTMF message on the correct DCCH.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.3.
2) An MS supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone (the corresponding IA5 character being selected from among the ones supported), shall send a START DTMF message specifying the correct IA5 character in the "keypad information" field of the keypad facility information element.
2.1 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.3.
26.8.1.4.1.1.3 Test purpose
1) To verify that an MS supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone, sends a START DTMF message on the correct DCCH.
2) To verify that an MS supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone (the corresponding IA5 character being selected from among the ones supported), sends a START DTMF message specifying the correct IA5 character in the "keypad information" field of the keypad facility information element.
26.8.1.4.1.1.4 Method of test
Specific PICS statements
–
PIXIT statements
– supported character set (e.g. 0‑9, #, *, A, B, C, D);
– if and how DTMF tone is indicated to the user.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
1 min.
Test procedure
The MS being in the call active state, a user causes a DTMF tone to be generated e.g. by depression of a key in the MS. A DTMF digit corresponding to the digit indicated by the user is sent in a START DTMF message by the MS. The SS will return a START DTMF ACKNOWLEDGE message to the MS. This acknowledgement may be used in the MS to generate an indication as a feedback for a successful transmission. Then the user indicates that the DTMF sending should cease e.g. by releasing the key. The MS will send a STOP DTMF message to the network which is acknowledged with STOP DTMF ACKNOWLEDGE by the SS.
The sequence described above is repeated for each of the applicable characters 0‑9, #, *, A, B, C, and D.
Then a case of rejecting a DTMF tone is tested and the state of the MS is verified.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
START DTMF |
the user causes DTMF tone to be generated |
SS |
the SS will verify that the transmitted information corresponds to the digit pressed |
||
2 |
SS -> MS |
START DTMF ACKNOWLEDGE |
possible indication of a DTMF tone depending the PIXIT statements |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U10 |
5 |
MS -> SS |
STOP DTMF |
|
6 |
SS -> MS |
STOP DTMF ACKNOWLEDGE |
the DTMF tone indication shall be stopped |
7 |
the steps 1‑6 shall be repeated for each of the applicable characters 0‑9, #, *, A, B, C, D. |
||
8 |
SS -> MS |
STATUS ENQUIRY |
|
9 |
MS -> SS |
STATUS |
cause 30#, state U10 |
10 |
MS -> SS |
START DTMF |
|
11 |
SS -> MS |
START DTMF REJECT |
|
12 |
SS -> MS |
STATUS ENQUIRY |
|
13 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
None.
26.8.1.4.2 In-call functions / user notification
User notification procedure allows the network to notify a MS of any call-related event during the "active" state of a call. It also may allow a MS to notify the remote user of any appropriate call-related event during the "active" state of a call by sending a NOTIFY message containing a notification indicator to the network. No state change occurs at any of the interface sides during this procedure.
26.8.1.4.2.1 In-call functions / User notification / MS terminated
26.8.1.4.2.1.1 Definition
This is a case for testing user notification procedure terminated by the mobile station. The test is applicable for those equipments supporting at least one circuit switched basic service.
26.8.1.4.2.1.2 Conformance requirement
1) A CC entity of a MS in CC-state U10, "active", upon receiving of a NOTIFY message shall remain in the active state.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.1.
26.8.1.4.2.1.3 Test purpose
To verify that a CC entity of a MS in CC-state U10, "active", upon receiving of a NOTIFY message remains in the active state.
26.8.1.4.2.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The MS being in the call active state, the SS will send a NOTIFY message to the MS. The state of the MS is checked after that.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
NOTIFY |
|
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
None.
26.8.1.4.3 In-call functions / channel changes
The two following test cases are for testing some elementary radio resource level procedures during an active state of a call to ensure call maintenance also during physical channel changes.
26.8.1.4.3.1 In-call functions / channel changes / a successful channel change in active state/ Handover and Assignment Command
26.8.1.4.3.1.1 Definition
This is a case to test a change of a physical channel during active state of a call. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.4.3.1.2 Conformance requirement
1) The MS being in the call active state after having successful completed a channel assignment or a handover command, shall remain in the call active state.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.2,
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.6.1
26.8.1.4.3.1.3 Test purpose
To verify that the MS being in the call active state after having successful completed a channel assignment or having completed a handover command remains in the call active state.
26.8.1.4.3.1.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The SS initiates a call to the Mobile Station, using an arbitrarily chosen MT circuit switched basic service (see clause 10 for generic call set up procedures).
The MS being in the call active state, the SS initiated channel assignment procedure causing an intracell change of channel by sending ASSIGNMENT COMMAND message to the MS. The MS performs channel assignment procedure and after the main signalling link is successfully established, the MS returns an ASSIGNMENT COMPLETE message. The state of the MS is then checked.
The SS then initiates a Finely Synchronized handover intra cell procedure. On the successful completion of this procedure the state of the MS is checked.
Expected sequence
Step |
Direction |
Message |
Comments |
0 |
Generic call set up procedure defined in subclauses 10.1 and 10.3, depending on choice of Bearer Capability. |
||
1 |
SS -> MS |
ASSIGNMENT COMMAND |
|
2 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U10 |
5 |
SS -> MS |
HANDOVER COMMAND |
See Specific message contents. |
6 |
MS -> SS |
HANDOVER ACCESS |
|
7 |
MS -> SS |
HANDOVER ACCESS |
|
8 |
MS -> SS |
HANDOVER ACCESS |
|
9 |
MS -> SS |
HANDOVER ACCESS |
Before completion of the 4 access bursts on the new DCCH, additional access bursts may also be sent on the SACCH |
10 |
MS -> SS |
HANDOVER COMPLETE |
|
11 |
SS -> MS |
STATUS ENQUIRY |
|
12 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
ASSIGNMENT COMMAND
Information Element |
value/remark |
Channel Description |
|
As used in Assignment Command when setting up the call, except: |
|
– Timeslot Number |
Arbitrary value, but different to originally used. |
HANDOVER COMMAND
Information Element |
value/remark |
Cell Description |
|
– Network Colour Code |
1 |
– Base Station Colour Code |
5 |
– BCCH Carrier Number |
GSM 450 – ARFCN 263 GSM 480 – ARFCN 310 P-GSM 900 – ARFCN 20 DCS 1 800 – ARFCN 590 PCS 1 900 – ARFCN 650 GSM 710 – ARFCN 457 GSM 750 – ARFCN 457 T-GSM 810 – ARFCN 457 GSM 850 – ARFCN 147 |
Channel Description |
|
As used in Assignment Command when setting up the call, except: |
|
– Timeslot Number |
Arbitrary value, but different to originally used. |
Synchronization Indication |
|
– Report Observed Time Difference |
Shall not be included. |
– Synchronization Indication |
"Synchronized". |
– Normal Cell Indication |
Ignore out of range timing advance. |
STATUS
Information Element |
value/remark |
cause |
#30, statue U10. |
26.8.1.4.3.2 In-call functions / channel changes / an unsuccessful channel change in active mode/ Handover and Assignment Command
26.8.1.4.3.2.1 Definition
This is a case to test an unsuccessful change of a physical channel during active state of a call. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
26.8.1.4.3.2.2 Conformance requirement
1) The MS, when returning to the old channel after handover or Assignment failure and having established the link, shall remain in the call active state.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.
26.8.1.4.3.2.3 Test purpose
To verify that the MS, when returning to the old channel after handover or Assignment failure and correctly establishing the link, will remain in the call active state.
26.8.1.4.3.2.4 Method of test
Specific PICS statements
–
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
30 s.
Test procedure
The SS initiates a call to the Mobile Station, using an arbitrarily chosen circuit switched basic service (see clause 10 for generic call set up procedures).
The MS being in the call active state, the SS initiates non synchronized handover procedure to cell B. The MS begins to send access bursts on the new DCCH (and optionally the SACCH). The SS activates the SACCH, but does not send a PHYSICAL INFORMATION MESSAGE, thus causing timer T3124 to time-out. Then the MS shall return back to the old channel and re-establish the signalling link on cell A and send a HANDOVER FAILURE message. The state of the MS is then checked.
The SS sends an Assignment command message allocating a hopping TCH/F, but does not activate the assigned channel. The MS shall attempt try to activate the new channel (this is not verified) and shall then reactivate the "old" channel and trigger the establishment of the main signalling link on the old channel. The MS shall send an ASSIGNMENT FAILURE message. The state of the MS is then checked.
Expected sequence
Step |
Direction |
Message |
Comments |
0 |
Generic call set up procedure defined in subclauses 10.1 and 10.3, depending on choice of Bearer Capability. |
||
1 |
SS -> MS |
HANDOVER COMMAND |
|
2 |
MS -> SS |
HANDOVER ACCESS |
Several messages are sent, all with the handover reference sent in the HANDOVER COMMAND message. |
3 |
MS -> SS |
HANDOVER FAILURE |
|
4 |
SS -> MS |
STATUS ENQUIRY |
|
5 |
MS -> SS |
STATUS |
cause 30#, state U10 |
6 |
SS -> MS |
ASSIGNMENT COMMAND |
Channel type = TCH/F, hopping. The MS attempts and fails to establish a signalling link on the new channel. |
7 |
The MS re-establishes the signalling link on the "old" channel. |
||
8 |
MS -> SS |
ASSIGNMENT FAILURE |
RR cause value = "protocol error unspecified" |
9 |
SS -> MS |
STATUS ENQUIRY |
|
10 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
ASSIGNMENT FAILURE
Information Element |
value/remark |
RR cause |
"protocol error unspecified" |
HANDOVER FAILURE
Information Element |
value/remark |
RR cause |
Not checked, as tested elsewhere. |
STATUS
Information Element |
value/remark |
cause |
#30, statue U10. |
26.8.1.4.4 In-call functions / MS terminated in-call modification
26.8.1.4.4.1 In-call functions / MS terminated in-call modification / modify when new mode is not supported
26.8.1.4.4.1.1 Definition
This is to test a special case of a in-call modification procedure, in which the new mode is not supported (and consequently not one of those negotiated and agreed during the establishment phase of the call). This test is applicable for any equipment supporting at least one circuit switched basic service.
26.8.1.4.4.1.2 Conformance requirement
1) In the case that the MS supports the network originated in-call modification procedure, the MS after having received a MODIFY message with a new mode which is not the actual one and cannot be supported by the MS shall reject it by sending a MODIFY REJECT message or a STATUS message.
2) In the case that the MS does not support the network originated in-call modification procedure, the MS shall, when receiving a MODIFY message, treat the message as unknown and respond with a STATUS message.
References
1) 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.3.4.3.4.2 and 5.3.4.4.
2) 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.
26.8.1.4.4.1.3 Test purpose
1) To verify that an MS supporting the network originated in-call modification procedure, after having received a MODIFY message with a new mode which is not the actual one and cannot be supported by the MS, rejects it by sending a MODIFY REJECT.
2) To verify that an MS not supporting the network originated in-call modification procedure, after having received a MODIFY message, responds with a STATUS message.
26.8.1.4.4.1.4 Method of test
Specific PICS statements
– the MS supports the network originated in-call modification procedure (p = Yes/No) (TSPC_AddInfo_InCallMod)
PIXIT statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The MS being in the call active state, the SS initiates in-call modification procedure by sending a MODIFY message with new mode different from actual mode and one of those not supported by the MS. The MS either returns a MODIFY REJECT message with the old bearer capability or a STATUS message with reject cause #97, depending on the PICS statement. The state of the MS is then checked.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
MODIFY |
with new mode different from actual one |
2a |
MS -> SS |
MODIFY REJECT |
with the old call mode included OR, p = Yes |
2b |
MS -> SS |
STATUS |
cause #97, state U10, p = No |
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
None.
26.8.1.4.5 In-call functions / MS originated in-call modification
26.8.1.4.5.1 In-call functions / MS originated in-call modification / a successful case of modifying
26.8.1.4.5.1.1 Definition
This test is to test a successful case of in-call modification, which is triggered by the calling tone identification (CNG) received by the MS. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech/Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech/Group 3 fax).
26.8.1.4.5.1.2 Conformance requirement
1) The procedure shall be initiated by the MS in the "active" state of the call. It shall send a MODIFY message including the new mode to be changed to; and enter the "mobile originating modify" state. The new mode given in the MODIFY message shall be one of those already negotiated and agreed during the establishment phase of the call. The MS shall stop sending Bm-channel information according to the old mode and enter the state U26 "Mobile Originating Modify".
2) Upon receipt of the MODIFY COMPLETE message the MS shall start sending channel information according to the new call mode and enter the "active" state.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.1.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.2.
26.8.1.4.5.1.3 Test purpose
1) To verify that the procedure is initiated by the MS in the "active" state of the call. It sends a MODIFY message including the new mode to be changed to; and enters the "mobile originating modify" state. The new mode given in the MODIFY message is one of those already negotiated and agreed during the establishment phase of the call. The MODIFY originating side stops sending Bm-channel information.
2) To verify that upon receipt of the MODIFY COMPLETE message the MS starts sending channel information according to the new call mode and enters the "active" state.
26.8.1.4.5.1.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modificationInitial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with the new mode to the SS and the state of the MS is checked. The channel mode is modified with the CHANNEL MODE MODIFY message including the appropriate channel mode for the new service. The SS then returns a MODIFY COMPLETE message. The state of the MS is then checked.
NOTE: ICM can be initiated by manual intervention at the MS.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is made to initiate a dual mode call |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
4 |
MS -> SS |
CM SERVICE REQUEST |
|
5 |
SS -> MS |
CIPHERING MODE COMMAND |
|
6 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
7 |
MS -> SS |
SETUP |
as specified in specific message contents |
8 |
SS -> MS |
AUTHENTICATION REQUEST |
|
9 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
10 |
SS -> MS |
CALL PROCEEDING |
as specified in specific message contents |
11 |
SS -> MS |
ASSIGNMENT COMMAND |
channel mode: see subclause 10.4 |
12 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
13 |
SS -> MS |
ALERTING |
|
14 |
SS -> MS |
CONNECT |
|
15 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
16 |
MS -> SS |
MODIFY |
as specified in specific message contents |
17 |
SS -> MS |
STATUS ENQUIRY |
|
18 |
MS -> SS |
STATUS |
cause 30#, state U26 |
19 |
SS -> MS |
CHANNEL MODE MODIFY |
as specified in specific message contents |
20 |
MS -> SS |
CHANNEL MODE MODIFY ACKNOWLEDGE |
|
21 |
SS -> MS |
MODIFY COMPLETE |
contains the new mode as bearer capability |
22 |
SS |
allow at least 2 s for the MS to adapt for the new mode |
|
23 |
SS -> MS |
STATUS ENQUIRY |
|
24 |
MS -> SS |
STATUS |
cause 30#, state U10 |
25 |
SS |
verify that the MS starts sending Bm channel information according to the new mode |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.2 In-call functions / MS originated in-call modification / modify rejected
26.8.1.4.5.2.1 Definition
This is to test a special case of a in-call modification procedure, in which the in-call modification is rejected. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech/Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech/Group 3 fax).
26.8.1.4.5.2.2 Conformance requirement
1) Upon receipt of the MODIFY REJECT message with the old bearer capability the MS shall: resume sending Bm-channel information according to the present call mode; resume interpreting received Bm-channel information according to the present call mode; and enter the "active" state.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.4.1.
26.8.1.4.5.2.3 Test purpose
To verify that upon receipt of the MODIFY REJECT message with the old bearer capability the MS resumes sending Bm-channel information according to the present call mode; resumes interpreting received Bm-channel information according to the present call mode; and enters the "active" state.
26.8.1.4.5.2.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modification
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with new mode to the SS. The SS returns a MODIFY REJECT message. The state of the MS is then checked.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
MMI action to initiate a dual mode call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
3 |
MS -> SS |
CM SERVICE REQUEST |
|
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
as specified in specific message contents |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CALL PROCEEDING |
agreeing bearer capabilities for dual mode call |
10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> SS |
ALERTING |
|
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
15 |
MS -> SS |
MODIFY |
MMI action to change the mode |
16 |
SS -> MS |
MODIFY REJECT |
with cause #58 bearer capability not available and with old bearer capabilities |
17 |
SS -> MS |
STATUS ENQUIRY |
|
18 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.3 In-call functions / MS originated in-call modification / an abnormal case of acceptance
26.8.1.4.5.3.1 Definition
This is to test a special case of a in-call modification procedure, in which the in-call modification is accepted incorrectly. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech/Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech/Group 3 fax).
26.8.1.4.5.3.2 Conformance requirement
1) Upon receipt of the MODIFY COMPLETE message indicating a call mode which does not correspond to the requested one the MS shall discard it and take no action.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.4.
26.8.1.4.5.3.3 Test purpose
To verify that upon receipt of the MODIFY COMPLETE message indicating a call mode which does not correspond to the requested one the MS discards it and takes no action.
26.8.1.4.5.3.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modification
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
CC-state U26 "Mobile Originating Modify".
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with new mode to the SS. The SS returns a MODIFY COMPLETE message specifying a mode that does not correspond to the requested one. It will be verified then that the MS shall not take any action and the state of the MS will be checked.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
MMI action to initiate a dual mode call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
3 |
MS -> SS |
CM SERVICE REQUEST |
|
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
as specified in specific message contents |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CALL PROCEEDING |
agreeing bearer capabilities for dual mode call |
10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> SS |
ALERTING |
|
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
15 |
MS -> SS |
MODIFY |
MMI action to change the mode |
16 |
SS -> MS |
MODIFY COMPLETE |
with a mode that does not correspond to the requested one |
17 |
SS -> MS |
STATUS ENQUIRY |
|
18 |
MS -> SS |
STATUS |
cause 30#, state U26 |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.4 In-call functions / MS originated in-call modification / an abnormal case of rejection
26.8.1.4.5.4.1 Definition
This is to test a special case of a in-call modification procedure, in which the in-call modification is rejected incorrectly. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech/Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech/Group 3 fax).
26.8.1.4.5.4.2 Conformance requirement
1) Upon receipt of the MODIFY REJECT message indicating a call mode which does not correspond to the actual one the MS shall discard it and take no action.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.4.
26.8.1.4.5.4.3 Test purpose
To verify that upon receipt of the MODIFY REJECT message indicating a call mode which does not correspond to the actual one the MS discards it and takes no action.
26.8.1.4.5.4.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modification
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
CC-state U26 "Mobile Originating Modify".
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with new mode to the SS. The SS returns a MODIFY REJECT message specifying a mode that does not correspond to the actual one. The state of the MS is then checked.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
MMI action to initiate a dual mode call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
3 |
MS -> SS |
CM SERVICE REQUEST |
|
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
as specified in specific message contents |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CALL PROCEEDING |
agreeing bearer capabilities for dual mode call |
10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> SS |
ALERTING |
|
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
15 |
MS -> SS |
MODIFY |
MMI action to change the mode |
16 |
SS -> MS |
MODIFY REJECT |
with a mode that does not correspond to the actual one |
17 |
SS -> MS |
STATUS ENQUIRY |
|
18 |
MS -> SS |
STATUS |
cause 30#, state U26 |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.5 In-call functions / MS originated in-call modification / time-out of timer T323
26.8.1.4.5.5.1 Definition
This is to test a special case of a in-call modification procedure, in which timer T323 expires in state U26, mobile originating modify. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech/Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech/Group 3 fax).
26.8.1.4.5.5.2 Conformance requirement
1) Upon expiration of T323 the MS shall initiate the procedures for call clearing with cause #102 "recovery on timer expiry".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.4.3.
26.8.1.4.5.5.3 Test purpose
To verify that upon expiration of T323 (accuracy ± 10 %) the MS shall initiate the procedures for call clearing with cause #102 "recovery on timer expiry".
26.8.1.4.5.5.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modification
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
CC-state U11 "disconnect request".
Maximum duration of test
1 minute.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with new mode to the SS. The SS does not respond until timer T323 expires at the MS. The MS is expected to respond with a DISCONNECT message. The SS checks timer T323 accuracy between emission of MODIFY and reception of DISCONNECT messages, the state of the MS and a cause value from the DISCONNECT message.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
MMI action to initiate a dual mode call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
3 |
MS -> SS |
CM SERVICE REQUEST |
|
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
as specified in specific message contents |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CALL PROCEEDING |
agreeing bearer capabilities for dual mode call |
10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> MS |
ALERTING |
|
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
15 |
MS -> SS |
MODIFY |
MMI action to change the mode |
16 |
SS |
the SS waits for the timer T323 expiry |
|
17 |
MS -> SS |
DISCONNECT |
cause value #102, the SS checks timer T323 accuracy (± 10 %) between MODIFY and DISCONNECT messages |
18 |
SS -> MS |
STATUS ENQUIRY |
|
19 |
MS -> SS |
STATUS |
cause 30#, state U11 |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.6 In-call functions / MS originated in-call modification / a successful channel change in state mobile originating modify
26.8.1.4.5.6.1 Definition
This is to test a special case of a in-call modification procedure, in which a change of a physical channel occurs in state U26, mobile originating modify. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech/Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech/Group 3 fax).
26.8.1.4.5.6.2 Conformance requirement
1) A CC-entity of the MS in CC-state U26, "Mobile Originating Modify", after successful completion of a channel assignment procedure or channel mode modify procedure shall remain in the call state U26.
2) Upon receipt of the MODIFY COMPLETE message the MS shall start sending channel information according to the new call mode and enter the "active" state.
References
1) 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.2,
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.6.1.
2) 3GPP TS 04.08, subclause 5.3.4.3.2.
26.8.1.4.5.6.3 Test purpose
1) To verify that a CC-entity of the MS in CC-state U26, "Mobile Originating Modify", after successful completion of a channel assignment procedure remains in the call state U26.
2) To verify that upon receipt of the MODIFY COMPLETE message the MS starts sending channel information according to the new call mode and enters the "active" state.
26.8.1.4.5.6.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modification
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
CC-state U10, active.
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with a new mode to the SS. The SS does not respond immediately, but performs channel assignment procedure including the appropriate channel mode for the new service. The state of the MS is then checked. The SS then returns a MODIFY COMPLETE message. The state of the MS is checked finally.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
MMI action to initiate a dual mode call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
3 |
MS -> SS |
CM SERVICE REQUEST |
|
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
as specified in specific message contents |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CALL PROCEEDING |
agreeing bearer capabilities for dual mode call |
10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> MS |
ALERTING |
|
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
15 |
MS -> SS |
MODIFY |
MMI action to change the mode |
16 |
SS -> MS |
ASSIGNMENT COMMAND |
channel mode implied by the MODIFY message |
17 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
18 |
SS -> MS |
STATUS ENQUIRY |
|
19 |
MS -> SS |
STATUS |
cause 30#, state U26 |
20 |
SS -> MS |
MODIFY COMPLETE |
|
21 |
SS -> MS |
STATUS ENQUIRY |
|
22 |
MS -> SS |
STATUS |
cause 30#, state U10 |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.7 In-call functions / MS originated in-call modification / an unsuccessful channel change in state mobile originating modify
26.8.1.4.5.7.1 Definition
This is to test a special case of a in-call modification procedure, in which an unsuccessful change of a physical channel occurs in state U26, mobile originating modify. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech/Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech/Group 3 fax).
26.8.1.4.5.7.2 Conformance requirement
1) A CC-entity of the MS in CC-state U26, "Mobile Originating Modify", when returning to the old channel after handover failure and having established the link, shall remain in the call state U26.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.2.
26.8.1.4.5.7.3 Test purpose
To verify that a CC-entity of the MS in CC-state U26, "Mobile Originating Modify", when returning to the old channel after handover failure and having established the link, remains in the call state U26.
26.8.1.4.5.7.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modification
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
CC-state U26, mobile originating modify.
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with a new mode to the SS. The SS initiates handover procedure. When the MS tries to establish the main signalling link, it is prohibited by the SS. Then the MS shall return back to the old channel and re-establish correctly the link. The state of the MS is then checked.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
MMI action to initiate a dual mode call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
3 |
MS -> SS |
CM SERVICE REQUEST |
|
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
as specified in specific message contents |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CALL PROCEEDING |
agreeing bearer capabilities for dual mode call |
10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> SS |
ALERTING |
|
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
15 |
MS -> SS |
MODIFY |
MMI action to change the mode |
16 |
SS -> MS |
HANDOVER COMMAND |
|
17 |
MS -> SS |
HANDOVER ACCESS |
the SS does not respond |
18 |
MS -> SS |
HANDOVER FAILURE |
after the MS has re-established the main signalling link in the old channel |
19 |
SS -> MS |
STATUS ENQUIRY |
|
20 |
MS -> SS |
STATUS |
cause 30#, state U26 |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.8 In-call functions / MS originated in-call modification / unknown message received
26.8.1.4.5.8.1 Definition
This is to test a special case of a in-call modification procedure, in which an unknown message is received in state U26, mobile originating modify. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech/Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech/Group 3 fax).
26.8.1.4.5.8.2 Conformance requirement
A CC entity of a MS in CC-state U26, "Mobile Originating Modify", having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 8.4.
26.8.1.4.5.8.3 Test purpose
To verify that a CC entity of a MS in CC-state U26, "Mobile Originating Modify", having received an unknown message from its peer entity returns a STATUS message.
26.8.1.4.5.8.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modification
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
CC-state U26, mobile originating modify.
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with a new mode to the SS. The SS sends a message with message type not defined for the protocol discriminator. The state of the MS is then checked.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
CHANNEL REQUEST |
MMI action to initiate a dual mode call |
2 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
3 |
MS -> SS |
CM SERVICE REQUEST |
|
4 |
SS -> MS |
CIPHERING MODE COMMAND |
|
5 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
6 |
MS -> SS |
SETUP |
as specified in specific message contents |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CALL PROCEEDING |
agreeing bearer capabilities for dual mode call |
10 |
SS -> MS |
ASSIGNMENT COMMAND |
TCH |
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> SS |
ALERTING |
|
13 |
SS -> MS |
CONNECT |
|
14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
15 |
MS -> SS |
MODIFY |
MMI action to change the mode |
16 |
SS -> MS |
unknown message |
message type not defined for PD |
17 |
MS -> SS |
STATUS |
cause 97#, state U26 |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.9 In-call functions / MS originated in-call modification / a release complete received
26.8.1.4.5.9.1 Definition
The call control entity of the MS being in the state, U26, the call is cleared by a RELEASE COMPLETE message sent by the SS. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 – Alternate Speech / Data, BS81 – Speech followed by Data, Teleservice 61 – Alternate Speech / Group 3 fax).
26.8.1.4.5.9.2 Conformance requirement
1) A CC entity of the MS in CC-state U26, "mobile originating modify", upon receipt of a RELEASE COMPLETE message with valid cause value, shall enter CC state U0, "Null".
2) On returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers shall be in state U0, "Null".
Reference(s)
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.2 and 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.3.
26.8.1.4.5.9.3 Test purpose
1) To verify that a CC entity of the MS in CC-state U26, "mobile originating modify", upon receipt of a RELEASE COMPLETE message with valid cause value, enters CC state U0, "Null".
2) To verify that on returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
26.8.1.4.5.9.4 Method of test
Specific PICS statements
–
PIXIT statements
– a way to activate a dual mode call
– a way to activate in-call modification
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Maximum duration of test
30 s.
Test Procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with the new mode to the SS and the state of the MS is checked. The SS sends a RELEASE COMPLETE message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
NOTE: ICM can be initiated by manual intervention at the MS.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is made to initiate a dual mode call |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
SDCCH |
4 |
MS -> SS |
CM SERVICE REQUEST |
|
5 |
SS -> MS |
CIPHERING MODE COMMAND |
|
6 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
7 |
MS -> SS |
SETUP |
as specified in specific message contents |
8 |
SS -> MS |
AUTHENTICATION REQUEST |
|
9 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
10 |
SS -> MS |
CALL PROCEEDING |
as specified in specific message contents |
11 |
SS -> MS |
ASSIGNMENT COMMAND |
channel mode: see subclause 10.4 |
12 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
13 |
SS -> MS |
ALERTING |
|
14 |
SS -> MS |
CONNECT |
|
15 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
16 |
MS -> SS |
MODIFY |
as specified in specific message contents |
17 |
SS -> MS |
STATUS ENQUIRY |
|
18 |
MS -> SS |
STATUS |
cause #30, state U26 |
19 |
SS -> MS |
RELEASE COMPLETE |
|
20 |
SS -> MS |
STATUS ENQUIRY |
|
21 |
MS -> SS |
RELEASE COMPLETE |
cause #81 (invalid TI value) |
22 |
SS |
repeat steps 20 – 21 to cover all the transaction identifiers from 000 … 110 |
|
23 |
SS -> MS |
CHANNEL RELEASE |
the main signalling link shall be released by the MS (L2: DISC/UA) |
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
26.8.1.4.5.10 In-call functions/MS originated in-call modification/contents of some of the messages
The following messages are used for testing in-call modification procedures, test cases 26.8.1.4.5.*, as default messages for those ones defined below. If any other values are defined in the expected sequence of the actual test cases, those values take precedence over the ones defined hereafter.
SETUP (MS to SS)
Information element |
Value/remark |
BC Repeat indicator |
|
Repeat indication |
Sequential, if BS81 is being tested, otherwise circular for successive selection |
Bearer capability 1 |
Appropriate for the teleservice/Bearer Service selected as an initial call mode |
Bearer capability 2 |
Appropriate for the teleservice/Bearer Service to be selected as a new call mode |
Facility |
Omitted |
Calling party subaddress |
Omitted |
Called party BCD number |
As entered |
Called party subaddress |
Omitted |
LLC repeat indicator |
The same repeat indication as the one for BC. Present if and only if LLC I and LLC II are present |
Low layer compatibility I |
See note |
Low layer compatibility II |
See note |
HLC repeat indicator |
The same repeat indication as the one for BC. Present if and only if HLC i and HLC ii are present. |
High layer compatibility i |
See note |
High layer compatibility ii |
See note |
User-user |
Omitted |
SS version |
Omitted |
CLIR suppression |
Omitted |
CC Capabilities |
present, but contents not checked |
NOTE: HLC/LLC may or may not be present. The contents of HLC/LLC are not verified. If LLC I is present then LLC II shall be present. If HLC i is present then HLC ii shall be present. |
CALL PROCEEDING
If the MS offers a choice in a SETUP message with respect to its bearer capabilities (this choice is restricted to the connection element), the bearer capabilities 1 and 2 and BC repeat indicator must all be present in this message. Otherwise, all three IEs are omitted.
Information element |
Value/remark |
Repeat Indicator |
See above |
Repeat indication |
As received in the SETUP message |
Bearer Capability 1 |
Same as in subclause 10.4 |
Bearer Capability 2 |
Same as in subclause 10.4 |
Facility |
Omitted |
Progress indicator |
Omitted |
MODIFY
Information element |
Value/remark |
Bearer capability |
If the bearer capability IEs were present in the CALL PROCEEDING message, then as it was specified in the bearer capability 2 of the CALL PROCEEDING message. Otherwise as in the bearer capability 2 of the SETUP message. |
Reverse Call Setup Direction |
Presence and value not checked |
Low layer compatibility |
See note |
High layer compatibility |
See note |
NOTE: HLC (LLC) shall be included if the HLC (LLC) was included in the SETUP message. The contents of LLC/HLC are not verified. |
MODIFY COMPLETE
Information element |
Value/remark |
Bearer capability |
If the bearer capability IEs were present in the CALL PROCEEDING message, then as it was specified in the bearer capability 2 of the CALL PROCEEDING message. Otherwise as in the bearer capability 2 of the SETUP message. |
Reverse Call Setup Direction |
Same as in MODIFY |
Low layer compatibility |
See note |
High layer compatibility |
See note |
NOTE: HLC (LLC) shall be included if the HLC (LLC) was included in the SETUP message. The contents of LLC/HLC are not verified. |
MODIFY REJECT
Information element |
Value/remark |
Bearer capability |
If the bearer capability IEs were present in the CALL PROCEEDING message, then as it was specified in the bearer capability 1 of the CALL PROCEEDING message. Otherwise as in the bearer capability 1 of the SETUP message. |
Cause |
#58 "bearer capability not presently available". |
Low layer compatibility |
See note |
High layer compatibility |
See note |
NOTE: HLC (LLC) shall be included if the HLC (LLC) was included in the SETUP message. The contents of LLC/HLC are not verified. |
CHANNEL MODE MODIFY
Information element |
Value/remark |
Channel description |
describes non-hopping Bm+ACCHs or Lm+ACCHs as appropriate for the test |
Channel Mode |
appropriate for the BC in the MODIFY |
CHANNEL MODE MODIFY ACKNOWLEDGE
Information element |
Value/remark |
Channel description |
as sent by the SS in the corresponding CHANNEL MODE MODIFY message |
Channel mode |
as sent by the SS in the corresponding CHANNEL MODE MODIFY message |