10.1.2 Establishment of an outgoing call

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

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

Initial conditions

As a minimum requirement the UE is updated and has been given a TMSI, a ciphering key and cipher key sequence number, and the layer 2, RRC 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 UE in the requested initial states.

A state may be taken as initial only when all the states which lead to this initial states 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 UE is brought again in the initial state starting with U0 at each new test performed.

Table 10.1.2/1: Establishment of an outgoing call, procedure 1 (late assignment)

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			Mobile Originated establishment of Radio Resource Connection	Establishment cause: Originating Conversational Call
2			Void
3			Void
4	->		CM SERVICE REQUEST	U0.1
5	<-		AUTHENTICATION REQUEST
6	->		AUTHENTICATION RESPONSE
7	<-		SECURITY MODE COMMAND
8	->		SECURITY MODE COMPLETE
9	->		SETUP	U1
10	<-		CALL PROCEEDING	U3
11	<-		ALERTING	U4
12			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3
13	<-		CONNECT
14	->		CONNECT ACKNOWLEDGE	U10
A15	<-		DISCONNECT	U12 (note 1)
B15	<-		DISCONNECT	U12 (note 2)
B16	->		RELEASE	U19
C15				MMI action, terminate call
C16	->		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 10.1.2/2: Void

Table 10.1.2/3: Establishment of an outgoing call, procedure 3

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			Mobile Originated establishment of Radio Resource ConnectionVoid	Establishment cause: Originating Conversational Call
2			Void
3			Void
4	->		CM SERVICE REQUEST	U0.1
4a	<-		AUTHENTICATION REQUEST
4b	->		AUTHENTICATION RESPONSE
5	<-		SECURITY MODE COMMAND
6	->		SECURITY MODE COMPLETE
7	->		SETUP	U1
8			Void
9			Void
10	<-		CALL PROCEEDING	U3
11			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3
12	<-		ALERTING	U4
13	<-		CONNECT
14	->		CONNECT ACKNOWLEDGE	U10
A15	<-		DISCONNECT	U12 (note 1)
B15	<-		DISCONNECT	U12 (note 2)
B16	->		RELEASE	U19
C15				MMI action, terminate call
C16	->		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 10.1.2/4: Establishment of an outgoing call, procedure 4

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			Mobile Originated establishment of Radio Resource Connection	Establishment cause: Originating Conversational Call
2			Void
3			Void
4	->		CM SERVICE REQUEST	U0.1
5	<-		IDENTITY REQUEST
6	->		IDENTITY RESPONSE
6a	<-		AUTHENTICATION REQUEST
6b	->		AUTHENTICATION RESPONSE
7	<-		SECURITY MODE COMMAND
8	->		SECURITY MODE COMPLETE
9	->		SETUP	U1
10			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3 (note 1)
11	<-		CALL PROCEEDING	U3
12	<-		ALERTING	U4
13	<-		CONNECT
14	->		CONNECT ACKNOWLEDGE	U10
A15	<-		DISCONNECT	U12 (note 2)
B15	<-		DISCONNECT	U12 (note 3)
B16	->		RELEASE	U19
C15				MMI action, terminate call
C16	->		DISCONNECT	U11
NOTE 1: Assigned channel is appropriate for the chosen bearer capability (see 10.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.

10.1.2.1 Outgoing call / U0 null state

10.1.2.1.1 Outgoing call / U0 null state / MM connection requested

10.1.2.1.1.1 Definition

The call control entity of the User Equipment requests the MM-sublayer to establish a mobile originating MM-connection.

10.1.2.1.1.2 Conformance requirement

If no RR connection exists, the MM sublayer requests the RR sublayer to establish an RR connection and enters MM sublayer state WAIT FOR RR CONNECTION (MM CONNECTION). This request contains an establishment cause and a CM SERVICE REQUEST message.

References

TS 24.008 clause 5.2.1.1 and clause 4.5.1.1

10.1.2.1.1.3 Test purpose

To verify that upon initiation of an outgoing basic call by user the UE 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” or “ Emergency call establishment ".

10.1.2.1.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	->			UE initiates outgoing call
2			Void
3			Void
4	->		CM SERVICE REQUEST	SS shall verify the CM service type requested by the UE
5	<-			The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.1.1.5 Test requirements

After step 2 the UE 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" or "Emergency call establishment".

10.1.2.2 Outgoing call / U0.1 MM connection pending

10.1.2.2.1 Outgoing call / U0.1 MM connection pending / CM service rejected

10.1.2.2.1.1 Definition

A request for MM connection is rejected by the SS.

10.1.2.2.1.2 Conformance requirement

If a CM SERVICE REJECT message is received by the UE, timer T3230 shall be stopped, the requesting CM sublayer entity informed. Then the UE shall proceed as follows:

– If the cause value is not #4 or #6 the MM sublayer returns to the previous state (the state where the request was received). Other MM connections shall not be affected by the CM SERVICE REJECT message.

– If cause value #4 is received, the UE aborts any MM connection, deletes any TMSI, LAI and ciphering key sequence number in the SIM, changes the update status to NOT UPDATED (and stores it in the SIM according to clause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. If subsequently the RR connection is released or aborted, this will force the UE to initiate a normal location updating). Whether the CM request shall be memorized during the location updating procedure, is a choice of implementation.

– If cause value #6 is received, the UE aborts any MM connection, deletes any TMSI, LAI and ciphering key sequence number in the SIM, changes the update status to ROAMING NOT ALLOWED (and stores it in the SIM according to clause 4.1.2.2), and enters the MM sublayer state WAIT FOR NETWORK COMMAND. The UE shall consider the SIM as invalid for non-GPRS services until switch-off or the SIM is removed.

References

TS 24.008, clause 4.5.1.1.

10.1.2.2.1.3 Test purpose

To verify that a CC entity of the UE in CC-state U0.1, "MM-connection pending", upon the UE receiving a CM SERVICE REJECT message, returns to CC state U0, "Null".

10.1.2.2.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U0.1 by using table 10.1.2/1.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE 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. The SS performs authentication and starts integrity. Then the SS will check the state of the UE by using STATUS ENQUIRY with all the relevant transaction identifiers.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		CM SERVICE REJECT
1a	<-		AUTHENTICATION REQUEST
1b	->		AUTHENTICATION RESPONSE
1c				SS starts integrity
2	<-		STATUS ENQUIRY
3	->		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	<-			The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.2.1.5 Test requirements

After step 2 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value).

10.1.2.2.2 Outgoing call / U0.1 MM connection pending / CM service accepted

10.1.2.2.2.1 Definition

A CM request is accepted for the MM-connection by the SS.

10.1.2.2.2.2 Conformance requirement

Having entered the "MM connection pending" state, upon MM connection establishment, the call control entity of the UE sends a setup message to its peer entity. This setup message is

– a SETUP message, if the call to be established is a basic call.

It then enters the "call initiated" state.

References

TS 24.008 clause 5.2.1.

10.1.2.2.2.3 Test purpose

To verify that a CC entity of the UE in CC-state U0.1, "MM connection pending", after completion of the security mode control procedure, sends a SETUP message specifying the Called party BCD number that was entered into the UE and then enters CC state U1, "Call initiated".

10.1.2.2.2.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U0.1 by using table 10.1.2/1.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. When the UE is requesting a MM-connection, the SS performs authentication and starts integrity. The UE 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
	UE	SS
1	<-		Void
1a	<-		AUTHENTICATION REQUEST
1b	->		AUTHENTICATION RESPONSE
1c				SS starts integrity
2	->		SETUP	with called party BCD number.
3	<-		STATUS ENQUIRY
4	->		STATUS	cause shall be #30 (response to enq.) and state U1 call initiated.

Specific message contents:

None.

10.1.2.2.2.5 Test requirements

After step 1 the UE shall send a SETUP message specifying the Called party BCD number that was entered into the UE and then enter CC state U1, "Call initiated".

10.1.2.2.3 Outgoing call / U0.1 MM connection pending / lower layer failure

10.1.2.2.3.1 Definition

The call control entity of the UE being in the state, U0.1, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated.

10.1.2.2.3.2 Conformance requirement

1. RR connection failure or IMSI deactivation

If an RR connection failure occurs or the IMSI is deactivated during the establishment of an MM connection, the MM connection establishment is aborted, timers T3230 is stopped, and an indication is given to the CM entity that requested the MM connection establishment. This shall be treated as a rejection for establishment of the new MM connection, and the MM sublayer shall release all active MM connections.

2. In CELL_DCH State, after receiving N313 consecutive "out of sync" indications from layer 1 for the established DPCCH physical channel in FDD, and the DPCH associated with mapped DCCHs in TDD, the UE shall:

1> start timer T313;

1> upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state:

2> stop and reset timer T313.

1> if T313 expires:

2> consider it as a "Radio link failure".

Periods in time where neither "in sync" nor "out of sync" is reported by layer 1 do not affect the evaluation of the number of consecutive (resp. successive) "in sync" or "out of sync" indications.

When a radio link failure occurs, the UE shall:

1> clear the dedicated physical channel configuration;

1> perform actions as specified for the ongoing procedure;

1> if no procedure is ongoing or no actions are specified for the ongoing procedure:

2> perform a cell update procedure according to subclause 8.3.1 using the cause "radio link failure".

2. In addition, the cell update procedure also serves the following purposes:

…

– to act on a radio link failure in the CELL_DCH state;

References

TS 24.008, clause 4.5.1.2 a), TS 25.331 clause 8.5.6 and 8.3.1.1.

10.1.2.2.3.3 Test purpose

To verify that the UE with a CC entity in state U0.1, "MM connection pending", aborts MM connection establishment, stops timer T3230 and returns to idle mode in case an RR connection failure occurs.

10.1.2.2.3.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U0.1 by using table 10.1.2/1.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. When the UE has sent a CM SERVICE REQUEST message, the SS release the DPCH configuration to generate a lower layer failure at the UE. The SS waits long enough to enable the UE to perform cell update procedure. The SS sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS checks that the UE does not initiate RRC connection establishment during 60 s.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS release the DPCH configuration to generate lower layer failure (radio link failure)
2	->		CELL UPDATE	CCCH
3	<-		RRC CONNECTION RELEASE	CCCH
4	SS			For a period of 60 s the SS checks that the UE does not initiate RRC connection establishment (since it should not re- attempt MM connection establishment).

Specific message contents:

None.

10.1.2.2.3.5 Test requirements

After step 4 the UE shall not initiate RRC connection establishment during 60 s.

10.1.2.3 Outgoing call / U1 call initiated

10.1.2.3.1 Outgoing call / U1 call initiated / receiving CALL PROCEEDING

10.1.2.3.1.1 Definition

The call control entity of the UE being in the state, U1, a CALL PROCEEDING message is sent by the SS.

10.1.2.3.1.2 Conformance requirement

Having entered the "call initiated" state, when the call control entity of the UE receives a CALL PROCEEDING message, it shall enter the "mobile originating call proceeding" state.

References

TS 24.008, clauses 5.2.1.1, 5.2.1.2 and 5.2.1.3.

10.1.2.3.1.3 Test purpose

To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of a CALL PROCEEDING message, enters CC state U3, "Mobile originating call proceeding".

10.1.2.3.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U1 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		CALL PROCEEDING	tone generation not mandatory
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U3

Specific message contents:

None.

10.1.2.3.1.5 Test requirements

After step 1 the UE shall enter CC state U3, "Mobile originating call proceeding".

10.1.2.3.2 Outgoing call / U1 call initiated / rejecting with RELEASE COMPLETE

10.1.2.3.2.1 Definition

The call control entity of the UE being in the state, U1, the call is rejected by a RELEASE COMPLETE message sent by the SS.

10.1.2.3.2.2 Conformance requirement

A call control entity of the UE in any call control state shall, upon receipt of a RELEASE COMPLETE message from its peer entity in the network: stop all running call control timers ; release the MM connection; and return to the "null" state.

References

TS 24.008, clause 5.4.4.1.3.

10.1.2.3.2.3 Test purpose

1) To verify that a CC entity of the UE 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".

10.1.2.3.2.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U1 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		RELEASE COMPLETE	This test case does not require a specific cause value. E.g. value #47, resources unavailable, is a suitable value
2	<-		STATUS ENQUIRY
3	->		RELEASE COMPLETE	cause #81 (invalid TI value)
4	SS			repeat steps 2‑3 to cover all the transaction identifiers from 000…110
5	<-			The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.3.2.5 Test requirements

After step 2 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value).

10.1.2.3.3 Outgoing call / U1 call initiated / T303 expiry

10.1.2.3.3.1 Definition

The call control entity of the UE being in the state, U1, if no response is then received from the SS, timer T303 expires at the UE side.

10.1.2.3.3.2 Conformance requirement

If timer T303 elapses in the "call initiated" state before any of the CALL PROCEEDING, ALERTING, CONNECT or RELEASE COMPLETE messages has been received, the clearing procedure described in TS 24.008 clause 5.4 is performed.

References

TS 24.008, clause 5.2.1.1 and clause 5.4.

10.1.2.3.3.3 Test purpose

1) To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon expiry of T303 sends a DISCONNECT message to its peer entity and enters state U11, "Disconnect request".

10.1.2.3.3.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U1 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS waits for T303 expiry.
2	->		DISCONNECT	Shall be transmitted 30 s after the CM SERVICE REQUEST, check the timer T303 accuracy, see TS34.108 clause 4.2.3.
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, status U11

Specific message contents:

None.

10.1.2.3.3.5 Test requirements

After step 1 upon expiry of timer T303 the UE shall send a DISCONNECT message and enter state U11, "Disconnect request".

10.1.2.3.4 Outgoing call / U1 call initiated / lower layer failure

10.1.2.3.4.1 Definition

The call control entity of the UE being in the state, U1, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated.

10.1.2.3.4.2 Conformance requirement

The MM sublayer shall indicate to all CM entities associated with active MM connections that the MM connection is interrupted, the subsequent action of the MM sublayer (call re-establishment, see TS 24.008 clause 4.5.1.6, or local release) will then depend on the decisions by the CM entities.

References

TS 24.008, clause 4.5.2.3 and 5.2.1.1, TS 25.331 clause 8.3.1 and clause 8.5.6.

10.1.2.3.4.3 Test purpose

To verify that after the UE with a CC entity in state U1 "Call initiated", has detected a lower layer failure and has returned to idle mode, the CC entity is in state U0, "Null".

10.1.2.3.4.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U1 by using table 10.1.2/4.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The UE is brought to the state U1. The SS modifies the scrambling code of downlink transmission (DL DPCH) to generate a lower layer failure at the UE. The SS waits long enough to enable the UE to perform cell update procedure. The SS sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS re-modifies the scrambling code of downlink transmission (DL DPCH) to the original one and waits 60 s. The SS will check that the UE will not send any message during 60 s.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS modifies the scrambling code of DPCH for generating lower layer failure
2	->		CELL UPDATE	CCCH
3	<-		RRC CONNECTION RELEASE	CCCH
4	SS			SS re-modifies the scrambling code of DPCH to the original one.
5	SS			SS waits 60 s.
				UE shall send no message on DCCH

Specific message contents:

None.

10.1.2.3.4.5 Test requirements

After step 4 the UE shall not send any message to the SS during 60 s.

10.1.2.3.5 Outgoing call / U1 call initiated / receiving ALERTING

10.1.2.3.5.1 Definition

The call control entity of the UE being in the state, U1, an ALERTING message is sent to the UE as an indication that a call is being alerted at a called end.

10.1.2.3.5.2 Conformance requirement

When the call control entity of the UE in the "call initiated" state or "mobile originating call proceeding" state receives an ALERTING message then, the call control entity of the UE shall stop timer T303 and T310 (if running) and shall enter the "call delivered" state.

References

TS 24.008, clause 5.2.1.1 and clause 5.2.1.5.

10.1.2.3.5.3 Test purpose

To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of an ALERTING message, enters CC state U4, "Call delivered".

10.1.2.3.5.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U1 by using table 10.1.2/4.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		ALERTING
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U4

Specific message contents:

None.

10.1.2.3.5.5 Test requirements

After step 1 the UE shall enter CC state U4, "Call delivered".

10.1.2.3.6 Outgoing call / U1 call initiated / entering state U10

10.1.2.3.6.1 Definition

The call control entity of the UE being in the state, U1, a CONNECT message is received by the UE.

10.1.2.3.6.2 Conformance requirement

The call control entity of the UE in the "call initiated" state, in the "mobile originating call proceeding" state or in the "call delivered" state, shall, upon receipt of a CONNECT message:

– attach the user connection;

– return a CONNECT ACKNOWLEDGE message;

– stop any locally generated alerting indication (if applied);

– stop timer T303 and T310 (if running);

– enter the "active" state.

References

TS 24.008, clause 5.2.1.1 and clause 5.2.1.6.

10.1.2.3.6.3 Test purpose

To verify that a CC entity of the UE 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".

10.1.2.3.6.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U1 by using table 10.1.2/4.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		CONNECT
2	->		CONNECT ACKNOWLEDGE
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U10

Specific message contents:

None.

10.1.2.3.6.5 Test requirements

After step 1 the UE shall send a CONNECT ACKNOWLEDGE message and shall enter CC state U10, "Active".

10.1.2.3.7 Outgoing call / U1 call initiated / unknown message received

10.1.2.3.7.1 Definition

The call control entity of the UE being in the state, U1, an unknown message is received by the UE.

10.1.2.3.7.2 Conformance requirement

If a UE receives an RR, MM or CC message with message type not defined for the PD or not implemented by the receiver in acknowledged mode, it shall return a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause # 97 "message type non-existent or not implemented".

References

TS 24.008 clause 8.4.

10.1.2.3.7.3 Test purpose

To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of a message with message type not defined for the protocol discriminator from its peer entity returns a STATUS message.

10.1.2.3.7.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U1 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		unknown message	message type not defined for PD
2	->		STATUS	cause #97, state U1
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U1

Specific message contents:

None.

10.1.2.3.7.5 Test requirements

After step 1 and step 3 the UE shall return a STATUS message with "Call state" set to state U1, "Call initiated".

10.1.2.4 Outgoing call / U3 Mobile originating call proceeding

10.1.2.4.1 Outgoing call / U3 Mobile originating call proceeding / ALERTING received

10.1.2.4.1.1 Definition

The call control entity of the UE being in the state, U3, an ALERTING message is sent to the UE as an indication that a call is being alerted at a called end.

10.1.2.4.1.2 Conformance requirement

References

TS 24.008 clause 5.2.1.5.

10.1.2.4.1.3 Test purpose

To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a ALERTING message enters CC-state U4, "Call Delivered".

10.1.2.4.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		ALERTING
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U4

Specific message contents:

None.

10.1.2.4.1.5 Test requirements

After step 1 the UE shall enter CC-state U4, "Call Delivered".

10.1.2.4.2 Outgoing call / U3 Mobile originating call proceeding / CONNECT received

10.1.2.4.2.1 Definition

The call control entity of the UE being in the state, U3, a CONNECT message is received by the UE.

10.1.2.4.2.2 Conformance requirement

The call control entity of the UE in the "call initiated" state, in the "mobile originating call proceeding" state or in the "call delivered" state, shall, upon receipt of a CONNECT message:

– attach the user connection;

– return a CONNECT ACKNOWLEDGE message;

– stop any locally generated alerting indication (if applied);

– stop timer T303 and T310 (if running);

– enter the "active" state.

References

TS 24.008 clause 5.2.1.6.

10.1.2.4.2.3 Test purpose

1) To verify that a CC-entity of the UE 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 UE stops locally generated alerting indication, if any.

10.1.2.4.2.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The CC entity of the UE is brought to the state U3. The SS sends a RADIO BEARER SETUP for traffic channel to the UE. The UE shall respond with a RADIO BEARER SETUP COMPLETE message. The SS sends a CONNECT message to the UE. The UE 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
	UE	SS
1			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3
2	<-		CONNECT	the UE shall stop locally generated alerting indication, if any
3	->		CONNECT ACKNOWLEDGE
4	<-		STATUS ENQUIRY
5	->		STATUS	cause #30, state U10

Specific message contents:

None.

10.1.2.4.2.5 Test requirements

After step 1 the UE shall return a "CONNECT ACKNOWLEDGE" message and enter the CC state U10, "Active".

The UE shall stop locally generated alerting indication.

10.1.2.4.3 Outgoing call / U3 Mobile originating call proceeding / PROGRESS received without in band information

10.1.2.4.3.1 Definition

The call control entity of the UE being in the state, U3, a PROGRESS message is received by the UE. The PROGRESS message does not contain indication of in-band information availability.

10.1.2.4.3.2 Conformance requirement

1) In order to inform the UE that the call is progressing in the PLMN/ISDN environment the network may send a progress indicator information element to the calling UE either:

a) in an appropriate call control message, if a state change is required (e.g., ALERTING or CONNECT); or

b) in the PROGRESS message, if no state change is appropriate.

This progress indicator information element shall contain progress description value #32 "Call is end-to-end ISDN/PLMN".

2) At any time during the establishment or release of a call and during an active call the network may send a PROGRESS message to the UE.

On receipt of a PROGRESS message during the establishment or release of a call the UE shall stop all call control timers related to that call.

References

Conformance requirement 1: TS 24.008 clause 5.2.1.4.2

Conformance requirement 2: TS 24.008 clause 5.5.6

10.1.2.4.3.3 Test purpose

1) To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding", upon receipt of a PROGRESS message with valid cause values stays in CC-state U3.

2) To verify that after receipt of the PROGRESS message timer T310 is stopped.

10.1.2.4.3.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		PROGRESS	(note)
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U3
4	SS			SS waits at least 45 s and checks no DISCONNECT is sent by the UE
5	<-		STATUS ENQUIRY
6	->		STATUS	cause #30, state U3

NOTE: Tested with a valid Progress Indicator, Progress description value among:

– #32 call is end-to-end PLMN/ISDN.

Specific message contents:

None.

10.1.2.4.3.5 Test requirements

After step 1 the UE shall stay in CC-state U3.

After step 3 SS waits at least 45 s and checks no DISCONNECT is sent by the UE.

10.1.2.4.4 Outgoing call / U3 Mobile originating call proceeding / PROGRESS with in band information

10.1.2.4.4.1 Definition

The call control entity of the UE being in the state, U3, a PROGRESS message indicating availability of in band information is received by the UE.

10.1.2.4.4.2 Conformance requirement

1) When the network wants to make the UE attach the user connection (e.g. in order to provide in-band tones/announcement) before the UE has reached the "active" state of a call, the network may include a progress indicator IE indicating user attachment in a suitable CC message:

– Either it includes the IE in a SETUP, CALL PROCEEDING, ALERTING, or CONNECT message that is send during call establishment

– it sends a PROGRESS message containing the IE.

On reception of a SETUP, CALL PROCEEDING, ALERTING, CONNECT, or PROGRESS message the UE shall proceed as specified elsewhere in TS 24.008 clause 5; if the progress indicator IE indicated user attachment and a speech mode traffic channel is appropriate for the call the UE shall in addition: attach the user connection for speech as soon as an appropriate channel in speech mode is available.

2) At any time during the establishment or release of a call and during an active call the network may send a PROGRESS message to the UE.

On receipt of a PROGRESS message during the establishment or release of a call the UE shall stop all call control timers related to that call.

References

Conformance requirement 1: TS 24.008 clause 5.5.1

Conformance requirement 2: TS 24.008 clause 5.5.6

10.1.2.4.4.3 Test purpose

1) To verify that a CC-entity of the UE 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 DTCH is in speech mode. If DTCH is not in a speech mode, the UE does not through-connect the DTCH.

2) To verify that after receipt of the PROGRESS message, T310 is stopped.

10.1.2.4.4.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The CC entity of the UE is brought to the state U3. The SS sends a RADIO BEARER SETUP for traffic channel to the UE. The UE shall respond with a RADIO BEARER SETUP COMPLETE message. The SS sends a PROGRESS message containing indication of in-band information availability to the UE. The SS checks that if channel mode is speech, the DTCH shall be through connected. If channel mode is not speech, the DTCH shall not be through connected. Also the SS checks that the UE has stopped T310, i.e. at T310 time-out no DISCONNECT message is sent by the UE. 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
	UE	SS
1			Radio Bearer Setup Procedure	See TS34.108 clause 7.1.3
2	<-		PROGRESS	(note) the UE shall stop all the CC timers , if channel mode is speech, the DTCH shall be through connected. If channel mode is not speech, the DTCH shall not be through connected.
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U3
5	SS			SS waits at least 45 s and checks no DISCONNECT is sent by the UE.
6	<-		STATUS ENQUIRY
7	->		STATUS	cause #30, state U3
8	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, Progress description 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.

10.1.2.4.4.5 Test requirements

After step 2 the UE shall through-connect the traffic channel for speech, if DTCH is in a speech mode. If DTCH is not in speech mode, the UE shall not through-connect the DTCH.

After step 4 the SS waits at least 45 s and checks no DISCONNECT is sent by the UE.

After step 7 the SS checks that the user connection for speech is attached (both downlink and uplink), if the channel mode is speech.

10.1.2.4.5 Outgoing call / U3 Mobile originating call proceeding / DISCONNECT with in band tones

10.1.2.4.5.1 Definition

The call control entity of the UE being in the state, U3, a DISCONNECT message indicating availability of in band information is received by the UE.

10.1.2.4.5.2 Conformance requirement

The call control entity of the UE in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon receipt of a DISCONNECT message with progress indicator #8:

i) if an appropriate speech traffic channel is not connected, continue clearing as defined in TS24.008 clause 5.4.4.1.2.1 without connecting to the in-band tone/announcement;

ii) if an appropriate speech traffic channel is connected, attach the user connection for speech if it is not yet attached and enter the "disconnect indication" state. In that state, if upper layers request the clearing of the call, the call control entity of the UE shall proceed as defined in TS24.008 clause 5.4.4.1.2.1.

….

The call control entity of the MS in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon receipt of a DISCONNECT message with progress indicator #8 and, either not containing an Allowed Actions IE or containing an Allowed Actions IE indicating "CCBS activation is not possible":

i) if an appropriate speech traffic channel is not connected,

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

– not connect to the in-band tone/announcement;

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

References

TS 24.008 and clause 5.4.4.1.1.1 and 5.4.4.2.1.1.

10.1.2.4.5.3 Test purpose

To verify that a CC-entity of the UE 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 DTCH is not in speech mode, the UE sends a RELEASE message.

10.1.2.4.5.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The CC entity of the UE is brought to the state U3. The SS sends a RADIO BEARER SETUP for traffic channel to the UE. The UE shall respond with a RADIO BEARER SETUP COMPLETE message. The SS sends a DISCONNECT message containing indication of in-band information availability to the UE. The SS checks that if channel mode is speech, the DTCH shall be through connected and the UE enters state U12, disconnect indication. If channel mode is not speech, the DTCH shall not be through connected and the UE shall enter state U19, release request.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3
2	<-		DISCONNECT	(note)
				DTCH in speech mode:
A3	SS			the SS will check that the audio path for in band tones is attached.
A4	<-		STATUS ENQUIRY
A5	->		STATUS	cause #30, state U12
				DTCH is not in speech mode:
B3	->		RELEASE
B4	<-		STATUS ENQUIRY
B5	->		STATUS	cause #30, state U19

Specific message contents:

NOTE: the Progress Indicator, Progress description value:

– #8 in band information or appropriate pattern now available.

10.1.2.4.5.5 Test requirements

After step 2 the UE shall through-connect the speech channel to make in-band announcements available, if traffic channel is in speech mode. If DTCH is not in speech mode, the UE shall send a RELEASE message.

10.1.2.4.6 Outgoing call / U3 Mobile originating call proceeding / DISCONNECT without in band tones

10.1.2.4.6.1 Definition

The call control entity of the UE being in the state, U3, a DISCONNECT message is received by the UE. The DISCONNECT message does not contain indication of in-band information availability.

10.1.2.4.6.2 Conformance requirement

The call control entity of the UE in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon the receipt of a DISCONNECT message without progress indicator information element or with progress indicator different from #8:

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

…

The call control entity of the mobile station in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon the receipt of a DISCONNECT message either without progress indicator information element or with progress indicator different from #8, and, either without the Allowed Actions IE or with the Allowed Actions IE indicating that "CCBS is not possible":

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state. References

TS 24.008 clause 5.4.4.1.2.1 and 5.4.4.2.3.1

10.1.2.4.6.3 Test purpose

To verify that a CC-entity of the UE 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".

10.1.2.4.6.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		DISCONNECT	without progress indicator
2	->		RELEASE
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U19

Specific message contents:

None.

10.1.2.4.6.5 Test requirements

After step 1 the UE shall send a RELEASE message and enter the CC-state U19, "Release Request".

10.1.2.4.7 Outgoing call / U3 Mobile originating call proceeding / RELEASE received

10.1.2.4.7.1 Definition

The call control entity of the UE being in the state, U3, a RELEASE message is received by the UE.

10.1.2.4.7.2 Conformance requirement

The call control entity of the UE in any state except the "null" state and the "release request" state, shall, upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; release the MM connection; and return to the "null" state.

References

TS 24.008 clause 5.4.3.3

10.1.2.4.7.3 Test purpose

1) To verify that a CC-entity of the UE 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 UE 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".

10.1.2.4.7.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		RELEASE	with cause "Normal, unspecified"
2	->		RELEASE COMPLETE
3	<-		STATUS ENQUIRY
4	->		RELEASE COMPLETE	cause #81 (invalid TI value)
5	SS			repeat steps 3‑4 to cover all the transaction identifiers from 000…110
6	<-			The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.4.7.5 Test requirements

After step 1 the UE shall send a RELEASE COMPLETE message.

After step 3 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value).

10.1.2.4.8 Outgoing call / U3 Mobile originating call proceeding / termination requested by the user

10.1.2.4.8.1 Definition

The call control entity of the UE being in the state, U3, the user requests to terminate the call.

10.1.2.4.8.2 Conformance requirement

Apart from the exceptions identified in TS 24.008 clause 5.4.2, the call control entity of the UE shall initiate clearing by: stopping all running call control timers, sending a DISCONNECT message; starting timer T305; and entering the "disconnect request" state.

References

TS 24.008 clause 5.4.3.1

10.1.2.4.8.3 Test purpose

To verify that a CC-entity of the UE 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".

10.1.2.4.8.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator: 1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				MMI action, terminate call
2	->		DISCONNECT
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U11

Specific message contents:

None.

10.1.2.4.8.5 Test requirements

After step 1 the UE shall send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".

10.1.2.4.9 Outgoing call / U3 Mobile originating call proceeding / traffic channel allocation

10.1.2.4.9.1 Definition

The call control entity of the UE being in the state, U3, a radio bearer establishment procedure is performed.

10.1.2.4.9.2 Conformance requirement

It is a network dependent decision when to initiate the assignment of an appropriate traffic channel during the mobile originating call establishment phase. Initiation of a suitable RR procedure to assign an appropriate traffic channel does neither change the state of a call control entity nor affect any call control timer.

References

TS 24.008 clause 5.2.1.9.

10.1.2.4.9.3 Test purpose

To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding", when a traffic channel is allocated by the network performing the radio bearer establishment procedure, stays in CC-state U3.

10.1.2.4.9.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U3

Specific message contents:

None.

10.1.2.4.9.5 Test requirements

After step 1 the CC state U3, "Mobile Originating Call Proceeding", shall remain unchanged.

10.1.2.4.10 Outgoing call / U3 Mobile originating call proceeding / timer T310 time-out

10.1.2.4.10.1 Definition

The call control entity of the UE being in the state, U3, if no response is then received from the SS, timer T310 expires at the UE side.

10.1.2.4.10.2 Conformance requirement

1) If timer T310 elapses before any of the ALERTING, CONNECT or DISCONNECT messages has been received, the UE shall perform the clearing procedure described in TS 24.008 clause 5.4.

2) Apart from the exceptions identified in TS 24.008 clause 5.4.2, the call control entity of the UE shall initiate clearing by: stopping all running call control timers, sending a DISCONNECT message; starting timer T305; and entering the "disconnect request" state.

References

Conformance requirement 1: TS 24.008 clause 5.2.1.3./Abnormal case

Conformance requirement 2: TS 24.008 clause 5.4.3.1.

10.1.2.4.10.3 Test purpose

To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding" will, upon expiry of timer T310, initiate call release by sending DISCONNECT and enter the CC-state U11, "Disconnect Request".

10.1.2.4.10.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			the SS waits for T310 time-out
2	->		DISCONNECT	check the timer T310 accuracy, see TS34.108 clause 4.2.3
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U11

Specific message contents:

None.

10.1.2.4.10.5 Test requirements

After step 1 upon expiry of timer T310 the UE shall initiate call release by sending a DISCONNECT message and enter the CC-state U11, "Disconnect Request".

10.1.2.4.11 Outgoing call / U3 Mobile originating call proceeding / lower layer failure

10.1.2.4.11.1 Definition

The call control entity of the UE being in the state, U3, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated.

10.1.2.4.11.2 Conformance requirement

….

The re-establishment procedure allows a MS to resume a connection in progress after a radio link failure, possibly in a new cell and possibly in a new location area. The conditions in which to attempt call re-establishment or not depend on the call control state, see clause 5.5.4 and, whether or not a cell allowing call re-establishment has been found (as described in GSM 05.08). MM connections are identified by their protocol discriminators and transaction identifiers: these shall not be changed during call re-establishment.

The re-establishment takes place when a lower layer failure occurs and at least one MM connection is active (i.e.. the mobile station’s MM sublayer is either in state 6 "MM CONNECTION ACTIVE" or state 20 "WAIT FOR ADDITIONAL OUTGOING MM CONNECTION").

.…

When a MM connection is active, an indication may be given by the MM sublayer to the call control entity to announce that the current MM connection has been interrupted but might be re-established on request of call control.

Depending whether call re-establishment is allowed or not and on its actual state, call control shall decide to either request re-establishment or to release the MM connection.

a) Re-establishment not required

If the call is in the call establishment or call clearing phase, i.e. any state other than the "active" state or the "mobile originating modify" state, call control shall release the MM connection

….

In CELL_DCH State, after receiving N313 consecutive "out of sync" indications from layer 1 for the established DPCCH physical channel in FDD, and the DPCH associated with mapped DCCHs in TDD, the UE shall:

1> start timer T313;

1> upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state:

2> stop and reset timer T313.

1> if T313 expires:

2> consider it as a "Radio link failure".

Periods in time where neither "in sync" nor "out of sync" is reported by layer 1 do not affect the evaluation of the number of consecutive (resp. successive) "in sync" or "out of sync" indications.

When a radio link failure occurs, the UE shall:

1> clear the dedicated physical channel configuration;

1> perform actions as specified for the ongoing procedure;

1> if no procedure is ongoing or no actions are specified for the ongoing procedure:

2> perform a cell update procedure according to subclause 8.3.1 using the cause "radio link failure".

In addition, the cell update procedure also serves the following purposes:

…

– to act on a radio link failure in the CELL_DCH state;

References

TS 24.008 clause 4.5.2.3, 4.5.1.6, and 5.5.4, TS 25.331 clause 8.5.6 and 8.3.1.1.

10.1.2.4.11.3 Test purpose

To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding" having detected a lower layer failure and having returned to idle mode, the CC entity is in state U0, "Null".

10.1.2.4.11.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/4.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS releases the DPCH configuration to generate lower layer failure(radio link failure)
2	->		CELL UPDATE	CCCH
3	<-		RRC CONNECTION RELEASE	CCCH
4	SS			For a period of 60 s the SS checks that the UE does not initiate RRC connection establishment (since it should not re- attempt MM connection establishment)

Specific message contents:

None.

10.1.2.4.11.5 Test requirements

After step 4 the UE shall not initiate RRC Connection Establishment for 60 s.

10.1.2.4.12 Outgoing call / U3 Mobile originating call proceeding / unknown message received

10.1.2.4.12.1 Definition

The call control entity of the UE being in the state, U3, an unknown message is received by the UE.

10.1.2.4.12.2 Conformance requirement

References

TS 24.008 clause 8.4.

10.1.2.4.12.3 Test purpose

To verify that a CC-entity of the UE in CC-state U3, "Mobile Originating Call Proceeding" having received an unknown message from its peer entity returns a STATUS message.

10.1.2.4.12.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		unknown message	message type not defined for PD
2	->		STATUS	cause #97, state U3
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U3

Specific message contents:

None.

10.1.2.4.12.5 Test requirements

After step 1 the UE shall return a STATUS message.

10.1.2.4.13 Outgoing call / U3 Mobile originating call proceeding / Internal alerting indication

10.1.2.4.13.1 Definition

The call control entity of the UE being in the state, U3, an ALERTING message is sent to the UE when the user connection is not attached to the radio path.

10.1.2.4.13.2 Conformance requirement

– an alerting indication should be given to the user. If the UE has not attached the user connection then the UE shall internally generate an alerting indication. If the UE has attached the user connection then the network is responsible for generating the alerting indication and the UE need not generate one.

References

TS 24.008 clause 5.2.1.5.

10.1.2.4.13.3 Test purpose

When the call control entity of the UE 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 UE generates internally an alerting indication.

10.1.2.4.13.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

– way to give internally generated alerting indication for outgoing calls.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U3 by using table 10.1.2/1.

Test procedure

The SS sends an ALERTING message to the UE. 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 UE generates internally alerting indication to the user in the way described in the ICS/IXIT statements.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		ALERTING	the UE shall generate an alerting indication to the user in the way described in the ICS/IXIT statements
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U4

Specific message contents:

None.

10.1.2.4.13.5 Test requirements

After step 1 the UE shall enter "Call Delivered" state and, for speech calls, if the user connection is not attached to the radio path, the UE shall internally generate an alerting indication.

10.1.2.5 Outgoing call / U4 call delivered

10.1.2.5.1 Outgoing call / U4 call delivered / CONNECT received

10.1.2.5.1.1 Definition

The call control entity of the UE being in the state, U4, a CONNECT message is received by the UE.

10.1.2.5.1.2 Conformance requirement

The call control entity of the UE in the "call initiated" state, in the "mobile originating call proceeding" state or in the "call delivered" state, shall, upon receipt of a CONNECT message:

– attach the user connection;

– return a CONNECT ACKNOWLEDGE message;

– stop any locally generated alerting indication (if applied);

– stop timer T303 and T310 (if running);

– enter the "active" state.

References

TS 24.008 clause 5.2.1.6.

10.1.2.5.1.3 Test purpose

To verify that a CC-entity of the UE 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".

10.1.2.5.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U4 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		CONNECT
2	->		CONNECT ACKNOWLEDGE	UE stops locally generated alerting indication, if applicable
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U10

Specific message contents:

None.

10.1.2.5.1.5 Test requirements

After step 1 the UE shall return a CONNECT ACKNOWLEDGE message and enter the CC state U10, "Active".

10.1.2.5.2 Outgoing call / U4 call delivered / termination requested by the user

10.1.2.5.2.1 Definition

The call control entity of the UE being in the state, U4, the user requests to terminate the call.

10.1.2.5.2.2 Conformance requirement

References

TS 24.008 clause 5.4.3.1

10.1.2.5.2.3 Test purpose

To verify that a CC-entity of the UE 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".

10.1.2.5.2.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U4 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				MMI action, terminate call
2	->		DISCONNECT
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U11

Specific message contents:

None.

10.1.2.5.2.5 Test requirements

After step 1 the UE shall send a DISCONNECT message and enter the CC state U11, "Disconnect Request".

10.1.2.5.3 Outgoing call / U4 call delivered / DISCONNECT with in band tones

10.1.2.5.3.1 Definition

The call control entity of the UE being in the state, U4, a DISCONNECT message indicating availability of in band information is received by the UE.

10.1.2.5.3.2 Conformance requirement

i) if an appropriate speech traffic channel is not connected, continue clearing as defined in TS 24.008 clause 5.4.4.1.2.1 without connecting to the in-band tone/announcement;

….

i) if an appropriate speech traffic channel is not connected,

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

– not connect to the in-band tone/announcement;

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

References

TS 24.008 clause 5.4.4.1.1.1 and 5.4.4.2.1.1.

10.1.2.5.3.3 Test purpose

To verify that a CC-entity of the UE 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 DTCH is not in speech mode, the UE shall send a RELEASE message.

10.1.2.5.3.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U4 by using table10.1.2/3.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The CC entity of the UE is brought to the state U4. The SS sends a DISCONNECT message containing indication of in-band information availability to the UE. The SS checks that if channel mode is MO telephony, the DTCH shall be through connected and the UE enters state U12, disconnect indication. If channel mode is not speech, the DTCH shall not be through connected and the UE shall enter state U19, release request.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		DISCONNECT	(note)
				DTCH in speech mode:
A2	SS			the SS will check that the audio path for in band tones is attached.
A3	<-		STATUS ENQUIRY
A4	->		STATUS	cause #30, state U12
				DTCH is not in speech mode:
B2	->		RELEASE
B3	<-		STATUS ENQUIRY
B4	->		STATUS	cause #30, state U19

Specific message contents:

NOTE: the Progress Indicator, Progress Description value:

– #8 in band information or appropriate pattern now available.

10.1.2.5.3.5 Test requirements

After step 1 the UE shall through-connect the speech channel to make in-band announcements available, if traffic channel is in speech mode. If DTCH is not in speech mode, the UE shall send a RELEASE message.

10.1.2.5.4 Outgoing call / U4 call delivered / DISCONNECT without in band tones

10.1.2.5.4.1 Definition

The call control entity of the UE being in the state, U4, a DISCONNECT message is received by the UE. The DISCONNECT message does not contain indication of in-band information availability.

10.1.2.5.4.2 Conformance requirement

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

…..

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

References

TS 24.008 clause 5.4.4.1.2.1 and 5.4.4.2.3.1.

10.1.2.5.4.3 Test purpose

To verify that a CC-entity of the UE 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".

10.1.2.5.4.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U4 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		DISCONNECT	without progress indicator
2	->		RELEASE
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U19

Specific message contents:

None.

10.1.2.5.4.5 Test requirements

After step 1 the UE shall return a RELEASE message and enter the CC-state U19, "Release Request".

10.1.2.5.5 Outgoing call / U4 call delivered / RELEASE received

10.1.2.5.5.1 Definition

The call control entity of the UE being in the state, U4, a RELEASE message is received by the UE.

10.1.2.5.5.2 Conformance requirement

References

TS 24.008 clause 5.4.3.3.

10.1.2.5.5.3 Test purpose

1) To verify that a CC-entity of the UE 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".

10.1.2.5.5.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U4 by using table10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		RELEASE	with cause "Normal, unspecified"
2	->		RELEASE COMPLETE
3	<-		STATUS ENQUIRY
4	->		RELEASE COMPLETE	cause #81 (invalid TI value)
5			Void
6	<-			The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.5.5.5 Test requirements

After step 1 the UE shall respond with the RELEASE COMPLETE message.

10.1.2.5.6 Outgoing call / U4 call delivered / lower layer failure

10.1.2.5.6.1 Definition

The call control entity of the UE being in the state, U4, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated.

10.1.2.5.6.2 Conformance requirement

References

TS 24.008 clause 4.5.2.3 and clause 4.5.3, TS 25.331 clause 8.3.1 and clause 8.5.6.

10.1.2.5.6.3 Test purpose

To verify that a CC-entity of the UE in CC-state U4, "Call Delivered" having detected a lower layer failure and has returned to idle mode, the CC-entity is in CC-state U0, "Null".

10.1.2.5.6.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U4 by using table 10.1.2/3.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The UE is brought to the state U4. The SS modifies the scrambling code of downlink transmission (DL DPCH) to generate a lower layer failure at the UE. The SS waits long enough to perform cell update procedure. The SS sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS re-modifies the scrambling code of downlink transmission (DL DPCH) to the original one and waits 60 s. The SS will check that the UE will not send any message during 60 s.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS modifies the scrambling code of DPCH for generating lower layer failure
2	->		CELL UPDATE	CCCH
3	<-		RRC CONNECTION RELEASE	CCCH
4	SS			SS re-modifies the scrambling code of DPCH to the original one.
5	SS			SS waits 60 s.
				UE shall send no message on the DCCH

Specific message contents:

None.

10.1.2.5.6.5 Test requirements

After step 4 the UE shall not send any message to the SS during 60 s.

10.1.2.5.7 Outgoing call / U4 call delivered / traffic channel allocation

10.1.2.5.7.1 Definition

The call control entity of the UE being in the state, U4, a radio bearer establishment procedure is performed.

10.1.2.5.7.2 Conformance requirement

References

TS 24.008 clause 5.2.1.9.

10.1.2.5.7.3 Test purpose

To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", when a traffic channel is allocated by the network performing the radio bearer establishment procedure, stays in CC-state U4.

10.1.2.5.7.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U4 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U4

Specific message contents:

None.

10.1.2.5.7.5 Test requirements

After step 1 the CC state U4, "Call delivered", shall remain unchanged.

10.1.2.5.8 Outgoing call / U4 call delivered / unknown message received

10.1.2.5.8.1 Definition

The call control entity of the UE being in the state, U4, an unknown message is received by the UE.

10.1.2.5.8.2 Conformance requirement

References

TS 24.008 clause 8.4.

10.1.2.5.8.3 Test purpose

To verify that a CC-entity of the UE in CC-state U4, "Call Delivered", having received an unknown message from its peer entity returns a STATUS message.

10.1.2.5.8.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U4 by using table 10.1.2/4.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		unknown message	message type not defined for PD
2	->		STATUS	cause #97, state U4
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U4

Specific message contents:

None.

10.1.2.5.8.5 Test requirements

After step 1 the UE shall return a STATUS message.

10.1.2.6 U10 active

10.1.2.6.1 U10 active / termination requested by the user

10.1.2.6.1.1 Definition

The call control entity of the UE being in the state, U10, the user requests to terminate the call.

10.1.2.6.1.2 Conformance requirement

References

TS 24.008 clause 5.4.3.1

10.1.2.6.1.3 Test purpose

To verify that the a CC-entity of the UE in CC-state U10, "Active", upon request by the user to terminate will send a DISCONNECT message and enter the CC-state U11, "Disconnect Request".

10.1.2.6.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U10 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				MMI action, terminate call
2	->		DISCONNECT
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U11

Specific message contents:

None.

10.1.2.6.1.5 Test requirements

After step 1 the UE shall send a DISCONNECT message and enter the CC state U11, "Disconnect Request".

10.1.2.6.2 U10 active / RELEASE received

10.1.2.6.2.1 Definition

The call control entity of the UE being in the state, U10, a RELEASE message is received by the UE.

10.1.2.6.2.2 Conformance requirement

References

TS 24.008 clause 5.4.3.3.

10.1.2.6.2.3 Test purpose

1) To verify that the a CC-entity of the UE in CC-state U10, "Active", upon receive of the RELEASE will respond with the RELEASE COMPLETE message and enter the CC-state U0, "Null"

10.1.2.6.2.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U10 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		RELEASE	with cause "Normal, unspecified"
2	->		RELEASE COMPLETE	the UE starts T3240
3	<-		STATUS ENQUIRY
4	->		RELEASE COMPLETE	cause #81 (invalid TI value)
5			Void
6	<-			The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.6.2.5 Test requirements

After step 1 the UE shall return a RELEASE COMPLETE message.

10.1.2.6.3 U10 active / DISCONNECT with in band tones

10.1.2.6.3.1 Definition

The call control entity of the UE being in the state, U10, a DISCONNECT message indicating availability of in band information is received by the UE.

10.1.2.6.3.2 Conformance requirement

i) if an appropriate speech traffic channel is not connected, continue clearing as defined in TS 24.008 clause 5.4.4.1.2.1 without connecting to the in-band tone/announcement;

…

i) if an appropriate speech traffic channel is not connected,

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

– not connect to the in-band tone/announcement;

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

References

TS 24.008 clause 5.4.4.1.1.1 and clause 5.4.4.2.1.1

10.1.2.6.3.3 Test purpose

To verify that a CC-entity of the UE in CC-state U10, "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 DTCH is not in speech mode, the UE sends a RELEASE message.

10.1.2.6.3.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U10 by using table 10.1.2/1.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The CC entity of the UE is brought to the state U10. The SS sends a DISCONNECT message containing indication of in-band information availability to the UE. The SS checks that if channel mode is speech, the DTCH shall be through connected and the UE enters state U12, disconnect indication. If channel mode is not speech, the DTCH shall not be through connected and the UE enters state U19, release request.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		DISCONNECT	(note)
				DTCH in speech mode:
A2	SS			the SS will check that the audio path for in band tones is attached.
A3	<-		STATUS ENQUIRY
A4	->		STATUS	cause #30, state U12
				DTCH is not in speech mode:
B2	->		RELEASE
B3	<-		STATUS ENQUIRY
B4	->		STATUS	cause #30, state U19

Specific message contents:

NOTE: the Progress Indicator, Progress Description value:

#8 in band information or appropriate pattern now available.

10.1.2.6.3.5 Test requirements

10.1.2.6.4 U10 active / DISCONNECT without in band tones

10.1.2.6.4.1 Definition

The call control entity of the UE being in the state, U10, a DISCONNECT message is received by the UE. The DISCONNECT message does not contain indication of in-band information availability.

10.1.2.6.4.2 Conformance requirement

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

….

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

References

TS 24.008 clause 5.4.4.1.2.1 and 5.4.4.2.3.1.

10.1.2.6.4.3 Test purpose

To verify that the a CC-entity of the UE in CC-state U10, "Active", upon receipt of a DISCONNECT message without progress indicator, returns a RELEASE message and enters the CC-state U19, "Release Request".

10.1.2.6.4.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U10 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		DISCONNECT	without progress indicator
2	->		RELEASE
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U19

Specific message contents:

None.

10.1.2.6.4.5 Test requirements

After step 1 the UE shall return a RELEASE message and enter the CC-state U19, "Release Request".

10.1.2.6.5 U10 active / RELEASE COMPLETE received

10.1.2.6.5.1 Definition

The call control entity of the UE being in the state, U10, the call is cleared by a RELEASE COMPLETE message sent by the SS.

10.1.2.6.5.2 Conformance requirement

1) A call control entity shall accept an incoming RELEASE COMPLETE message used to initiate the call clearing even though the cause information element is not included.

2) A call control entity of the UE in any call control state shall, upon receipt of a RELEASE COMPLETE message from its peer entity in the network: stop all running call control timers ; release the MM connection; and return to the "null" state.

References

Conformance requirement 1: TS 24.008 clause 5.4.2.

Conformance requirement 2: TS 24.008 clause 5.4.4.1.3.

10.1.2.6.5.3 Test purpose

1) To verify that a CC entity of the UE in CC-state U10, "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".

10.1.2.6.5.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U10 by using table 10.1.2/1.

Test procedure

The SS sends a RELEASE COMPLETE message to the UE. 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
	UE	SS
1	<-		RELEASE COMPLETE	note 1
2	<-		STATUS ENQUIRY	note 2
3	->		RELEASE COMPLETE	cause #81 (invalid TI value),
4	SS			repeat steps 2‑3 to cover all the transaction identifiers from 000…110
5	<-			The SS releases the RRC connection.

Specific message contents:

NOTE 1: With the cause value chosen arbitrarily or cause value not included.

NOTE 2: TI flag has the value indicating the UE as an originator of the call.

10.1.2.6.5.5 Test requirements

After step 2 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value).

10.1.2.6.6 U10 active / SETUP received

10.1.2.6.6.1 Definition

If the UE does not react correctly when receiving a SETUP message on a new Transaction Identifier during an active call, the active call may be lost.

10.1.2.6.6.2 Conformance requirement

1) A busy UE which satisfies the compatibility requirements indicated in the SETUP message shall respond either with a CALL CONFIRMED message if the call setup is allowed to continue or a RELEASE COMPLETE message if the call setup is not allowed to continue, both with cause #17 "user busy".

References:

TS 24.008 clause 5.2.2.3.1.

10.1.2.6.6.3 Test purpose

1) To verify that a User Equipment 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 UE is still in state U10 for the established call.

10.1.2.6.6.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

– support of call waiting Y/N.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is idle updated with valid TMSI and CKSN.

The UE is brought into the state U10 by using table 10.1.2/1.

Test Procedure

The UE has a mobile originated call in the U10 state. When UE sends a SETUP message and SS receives it in the first call establishment, SS sends a CALL PROCEEDING message without Network Call Control Capabilities IE.

The SS sends a SETUP message to the UE (with signal IE indicating "call waiting tone on" and without Network Call Control Capabilities IE).

If the UE does not support call waiting it shall answer by a RELEASE COMPLETE message.

If the UE 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 UE is still in state U10, active call for the original call.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		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 UE does not support call waiting
A2	->		RELEASE COMPLETE	with cause "user busy" with the TI of the second transaction
				if the UE supports call waiting
B2	->		CALL CONFIRMED	with cause "user busy" with the TI of the second transaction
B3	->		ALERTING	with the TI of the second transaction
B4	<-		RELEASE COMPLETE	with the TI of the second transaction
5	<-		STATUS ENQUIRY	with the TI of the original transaction
6	->		STATUS	cause #30, state U10 with the TI of the original transaction

Specific message contents

SETUP message contains a Signal IE with value "call waiting tone on" (H’07).

10.1.2.6.6.5 Test requirements

After step 1 a UE that has a call established shall answer 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.

After step A2 or B4 the UE shall be in state U10 for the established call.

10.1.2.7 U11 disconnect request

10.1.2.7.1 U11 disconnect request / clear collision

10.1.2.7.1.1 Definition

The call control entity of the UE being in the state, U11, a DISCONNECT message is received by the UE.

10.1.2.7.1.2 Conformance requirement

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

….

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

References

TS 24.008 clause 5.4.4.1.2.1 and 5.4.4.2.3.1.

10.1.2.7.1.3 Test purpose

To verify that the a CC-entity of the UE 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".

10.1.2.7.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U11 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		DISCONNECT
2	->		RELEASE
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U19

Specific message contents:

None.

10.1.2.7.1.5 Test requirements

After step 1 the UE shall return the RELEASE message.

After step 3 the UE shall return a STATUS message with "Call state" set to state U19, "Release Request".

10.1.2.7.2 U11 disconnect request / RELEASE received

10.1.2.7.2.1 Definition

The call control entity of the UE being in the state, U11, a RELEASE message is received by the UE.

10.1.2.7.2.2 Conformance requirement

References

TS 24.008 clause 5.4.3.3

10.1.2.7.2.3 Test purpose

1) To verify that the a CC-entity of the UE in CC-state U11, "Disconnect Request", upon receipt of the RELEASE message shall return RELEASE COMPLETE and enter the CC-state U0, "Null".

10.1.2.7.2.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U11 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		RELEASE
2	->		RELEASE COMPLETE
3	<-		STATUS ENQUIRY
4	->		RELEASE COMPLETE	cause #81 (invalid TI value)
5			Void
6				The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.7.2.5 Test requirements

After step 1 the UE shall return the RELEASE COMPLETE.

10.1.2.7.3 U11 disconnect request / timer T305 time-out

10.1.2.7.3.1 Definition

The call control entity of the UE being in the state, U11, if no response is then received from the SS, timer T305 expires at the UE side.

10.1.2.7.3.2 Conformance requirement

The call control entity of the UE in the "disconnect request" state, shall upon expiry of timer T305: send a RELEASE message to the network with the cause number originally contained in the DISCONNECT message and optionally, a second cause information element with cause #102 "recovery on timer expiry", start timer T308, and enter the "release request" state.

References

TS 24.008 clause 5.4.3.5.

10.1.2.7.3.3 Test purpose

To verify that the CC-entity of the UE 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 enters the CC-state U19, "Release Request".

10.1.2.7.3.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U11 by using table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS waits until T305 expires at the UE
2	->		RELEASE	SS checks the time between DISCONNECT and RELEASE (note), check the timer T305 accuracy, see TS34.108 clause 4.2.3
3	<-		STATUS ENQUIRY
4	->		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.

10.1.2.7.3.5 Test requirements

After step 1 upon expiry of timer T305 the UE shall proceed with the connection release procedure by sending the RELEASE message and enter the CC-state U19, "Release Request".

10.1.2.7.4 U11 disconnect request / lower layer failure

10.1.2.7.4.1 Definition

The call control entity of the UE being in the state, U11, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated.

10.1.2.7.4.2 Conformance requirement

References

TS 24.008 clause 4.5.2.3 and 4.5.3, TS 25.331 clause 8.3.1 and clause 8.5.6.

10.1.2.7.4.3 Test purpose

To verify that the a CC-entity of the UE in CC-state U11, "Disconnect Request" having detected a lower layer failure returns to the idle mode. The CC entity is thus in state U0, "Null".

10.1.2.7.4.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U11 by using table 10.1.2/4.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The UE is brought to the state U11. The SS modifies the scrambling code of downlink transmission (DL DPCH) to generate a lower layer failure at the UE. The SS waits long enough to enable the UE to perform cell update procedure. The SS sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS re-modifies the scrambling code of downlink transmission (DL DPCH) to the original one and waits 60 s. The SS will check that the UE will not send any message during 60 s.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS modifies the scrambling code of DPCH for generating lower layer failure
2	->		CELL UPDATE	CCCH
3	<-		RRC CONNECTION RELEASE	CCCH
4	SS			SS re-modifies the scrambling code of DPCH to the original one.
5	SS			SS waits 60 s.

Specific message contents:

None.

10.1.2.7.4.5 Test requirements

After step 4 the UE shall not send any message to the SS during 60 s.

10.1.2.7.5 U11 disconnect request / unknown message received

10.1.2.7.5.1 Definition

The call control entity of the UE being in the state, U11, an unknown message is received by the UE.

10.1.2.7.5.2 Conformance requirement

References

TS 24.008 clause 8.4.

10.1.2.7.5.3 Test purpose

To verify that a CC-entity of the UE in CC-state U11, "Disconnect Request", having received an unknown message from its peer entity returns a STATUS message.

10.1.2.7.5.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U11 by using table 10.1.2/4.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		unknown message	message type not defined for PD
2	->		STATUS	cause #97, state U11
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U11

Specific message contents:

None.

10.1.2.7.5.5 Test requirements

After step 1 the UE shall return a STATUS message.

10.1.2.8 U12 disconnect indication

10.1.2.8.1 U12 disconnect indication / call releasing requested by the user

10.1.2.8.1.1 Definition

The call control entity of the UE being in the state, U12, the user requests to terminate the call.

10.1.2.8.1.2 Conformance requirement

Response from the upper layers:

i) If the upper layers request the clearing of the call, the call control entity of the UE shall:

– stop all running call control timers;

– send a RELEASE message;

– start timer T308; and

– enter the "release request" state.

References

TS 24.008 clause 5.4.4.2.2.1

10.1.2.8.1.3 Test purpose

To verify that a CC-entity of the UE 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"

10.1.2.8.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U12 by using Option A of table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				MMI action, "on hook"
2	->		RELEASE
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U19

Specific message contents:

None.

10.1.2.8.1.5 Test requirements

After step 1 the UE being in network initiated call release phase, shall send a RELEASE message and enter CC-state U19, "Release Request".

10.1.2.8.2 U12 disconnect indication / RELEASE received

10.1.2.8.2.1 Definition

The call control entity of the UE being in the state, U12, a RELEASE message is received by the UE.

10.1.2.8.2.2 Conformance requirement

References

TS 24.008 clause 5.4.3.3

10.1.2.8.2.3 Test purpose

1) To verify that a CC-entity of the UE 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 UE 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".

10.1.2.8.2.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U12 by using Option A of table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		RELEASE
2	->		RELEASE COMPLETE
3	<-		STATUS ENQUIRY
4	->		RELEASE COMPLETE	cause #81 (invalid TI value)
5	SS			repeat steps 3‑4 to cover all the transaction identifiers from 000…110
6	<-			The SS releases the RRC connection

Specific message contents:

None.

10.1.2.8.2.5 Test requirements

After step 1 the UE shall return the RELEASE COMPLETE message.

After step 3 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value).

10.1.2.8.3 U12 disconnect indication / lower layer failure

10.1.2.8.3.1 Definition

The call control entity of the UE being in the state, U12, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated.

10.1.2.8.3.2 Conformance requirement

References

TS 24.008 clause 4.5.2.3 and clause 4.5.3, TS 25.331 clause 8.3.1 and clause 8.5.6.

10.1.2.8.3.3 Test purpose

To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication" having detected a lower layer failure returns to idle mode. The CC-entity is thus in state U0, "Null".

10.1.2.8.3.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U12 by using Option A of table 10.1.2/3.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The UE is brought to the state U12. The SS modifies the scrambling code of downlink transmission (DL DPCH) to generate a lower layer failure at the UE. The SS waits long enough to enable the UE to perform cell update procedure. The SS sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS re-modifies the scrambling code of downlink transmission (DL DPCH) to the original one and waits 60 s. The SS will check that the UE will not send any message during 60 s.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS modifies the scrambling code of DPCH for generating lower layer failure
2	->		CELL UPDATE	CCCH
3	<-		RRC CONNECTION RELEASE	CCCH
4	SS			SS re-modifies the scrambling code of DPCH to the original one.
5	SS			SS waits 60 s.
				UE shall send no message on the DCCH

Specific message contents:

None.

10.1.2.8.3.5 Test requirements

After step 4 the UE shall not send any message to the SS during 60 s.

10.1.2.8.4 U12 disconnect indication / unknown message received

10.1.2.8.4.1 Definition

The call control entity of the UE being in the state, U12, an unknown message is received by the UE.

10.1.2.8.4.2 Conformance requirement

References

TS 24.008 clause 8.4.

10.1.2.8.4.3 Test purpose

To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication" having received an unknown message from its peer entity returns a STATUS message.

10.1.2.8.4.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U12 by using Option A of table 10.1.2/3.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		unknown message	message type not defined for PD
2	->		STATUS	cause #97, state U12
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U12

Specific message contents:

None.

10.1.2.8.4.5 Test requirements

After step 1 the UE shall return a STATUS message.

10.1.2.9 Outgoing call / U19 release request

10.1.2.9.1 Outgoing call / U19 release request / timer T308 time-out

10.1.2.9.1.1 Definition

The call control entity of the UE being in the state, U19, if no response is then received from the SS, timer T308 expires at the UE side.

10.1.2.9.1.2 Conformance requirement

The call control entity of the UE in the "release request" state shall at first expiry of timer T308 retransmit the RELEASE message and restart timer T308.

References

TS 24.008 clause 5.4.4.1.3.1.

10.1.2.9.1.3 Test purpose

To verify that a CC-entity of the UE 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.

10.1.2.9.1.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U19 by using table 10.1.2/4.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS waits until T308 at the UE
2	->		RELEASE	SS checks the time between the two RELEASE messages check the timer T308 accuracy, see TS34.108 clause 4.2.3
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U19

Specific message contents:

None.

10.1.2.9.1.5 Test requirements

After step 1 upon the first expiry of timer T308 the UE shall send the RELEASE message and remain in the CC-state U19.

10.1.2.9.2 Outgoing call / U19 release request / 2nd timer T308 time-out

10.1.2.9.2.1 Definition

The call control entity of the UE being in the state, U19, if no response is then received after timer T308 has expired two times in success at the UE.

10.1.2.9.2.2 Conformance requirement

At second expiry of timer T308, the call control entity of the UE shall: release the MM connection; and return to the "null" state.

References

TS 24.008 clause 5.4.4.1.3.1.

10.1.2.9.2.3 Test purpose

1) To verify that a CC-entity of the UE 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 UE 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".

10.1.2.9.2.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U19 by using table 10.1.2/4.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The CC entity of the UE is brought to the state U19. The SS allows T308 expiry at the UE, and the UE shall repeat sending the RELEASE message and start timer T308 again. The SS allows again T308 expiry at the UE. The UE shall abort the RRC connection. The SS waits long enough to enable the UE to return to idle state listening to paging, and then pages UE to create RRC connection. The SS performs authentication and starts integrity. Finally, the SS will check the state of the UE by using STATUS ENQUIRY with the relevant transaction identifiers.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	SS			SS waits until T308 expiry at the UE
2	->		RELEASE
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U19
5	SS			SS waits until the second T308 expiry at the UE
6	SS			SS waits T3240 expiry at the UE
7	UE			The SS releases the RRC connection
8	SS			SS waits 10 s for the UE to return to listening to paging
9			Mobile terminated establishment of Radio Resource Connection	See TS34.108
9a	->		PAGING RESPONSE
9b	<-		AUTHENTICATION REQUEST
9c	->		AUTHENTICATION RESPONSE
9d				SS starts integrity
10	<-		STATUS ENQUIRY
11	->		RELEASE COMPLETE	cause #81 (invalid TI value)
12	SS			repeat steps 10‑11 to cover all the transaction identifiers from 000…110
13				The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.9.2.5 Test requirements

After step 5 upon the 2nd expiry of the timer T308 the UE shall enter the CC-state U0, "Null".

After step 10 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value).

10.1.2.9.3 Outgoing call / U19 release request / RELEASE received

10.1.2.9.3.1 Definition

The call control entity of the UE being in the state, U19, a RELEASE message is received by the UE.

10.1.2.9.3.2 Conformance requirement

Clear collision can also occur when both sides simultaneously transfer RELEASE messages related to the same call. The entity receiving such a RELEASE message whilst within the "release request" state shall: stop timer T308; release the MM connection; and enter the "null" state (without sending a RELEASE COMPLETE message).

References

TS 24.008 clause 5.4.4.2.5.1

10.1.2.9.3.3 Test purpose

To verify that a CC-entity of the UE 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".

10.1.2.9.3.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U19 by using table 10.1.2/4.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		RELEASE
2	<-		STATUS ENQUIRY
3	->		RELEASE COMPLETE	cause #81 (invalid TI value)
4	SS			repeat steps 2‑3 to cover all the transaction identifiers from 000…110
5	<-			The SS releases the RRC connection

Specific message contents:

None.

10.1.2.9.3.5 Test requirements

After step 2 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value).

10.1.2.9.4 Outgoing call / U19 release request / RELEASE COMPLETE received

10.1.2.9.4.1 Definition

The call control entity of the UE being in the state, U19, a RELEASE COMPLETE message is received by the UE.

10.1.2.9.4.2 Conformance requirement

1) A call control entity shall accept an incoming RELEASE COMPLETE message used to initiate the call clearing even though the cause information element is not included.

References

Conformance requirement 1: TS 24.008 clause 5.4.2

Conformance requirement 2: TS 24.008 clause 5.4.4.1.3

10.1.2.9.4.3 Test purpose

To verify that a CC-entity of the UE 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".

10.1.2.9.4.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U19 by using table 10.1.2/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		RELEASE COMPLETE
2	<-		STATUS ENQUIRY
3	->		RELEASE COMPLETE	cause #81 (invalid TI value)
4	SS			repeat steps 2‑3 to cover all the transaction identifiers from 000…110
5	<-			The SS releases the RRC connection.

Specific message contents:

None.

10.1.2.9.4.5 Test requirements

After step 2 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value).

10.1.2.9.5 Outgoing call / U19 release request / lower layer failure

10.1.2.9.5.1 Definition

The call control entity of the UE being in the state, U19, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated.

10.1.2.9.5.2 Conformance requirement

References

TS 24.008 clause 4.5.2.3 and clause 4.5.3, TS 25.331 clause 8.3.1 and clause 8.5.6.

10.1.2.9.5.3 Test purpose

To verify that a CC-entity of the UE in CC-state U19, "Release Request", having detected a lower layer failure, returns to the idle mode, the CC entity is in state U0, "Null".

10.1.2.9.5.4 Method of test

Related ICS/IXIT statements

– supported MO circuit switched basic services.

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is in MM-state "idle, updated" with valid TMSI and CKSN.

The UE is brought into the state U19 by using table 10.1.2/1.

Test procedure

An MO circuit switched basic service is selected that is supported by the UE; if the UE supports MO telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then, the UE is made to initiate a call. The UE is brought to the state U19. The SS modifies the scrambling code of downlink transmission (DL DPCH) to generate a lower layer failure at the UE. The SS waits long enough to enable the UE to perform cell update procedure. The SS sends RRC CONNECTION RELEASE message as a response to the CELL UPDATE message from the UE. The SS re-modifies the scrambling code of downlink transmission (DL DPCH) to the original one and waits 60 s. The SS will check that the UE will not send any message during 60 s.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	SS			SS modifies the scrambling code of DPCH for generating lower layer failure
2	->		CELL UPDATE	CCCH
3	<-		RRC CONNECTION RELEASE	CCCH
4	SS			SS re-modifies the scrambling code of DPCH to the original one.
5	SS			SS waits 60 s.
				UE shall send no message on the DCCH

Specific message contents:

None.

10.1.2.9.5.5 Test requirements

After step 4 CC the UE shall not send any message to the SS during 60 s.