10.1.3 Establishment of an incoming call / Initial conditions

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

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

The tables below describe message exchanges which bring the UE in the requested initial states in case of an incoming call.

A state may be taken as initial only when all the states which lead to this initial states have been validated. The order will be U0, U6, U9, U7, U8, U10, U26 etc. as in the following tables.

Table 10.1.3/1: Establishment of an incoming call, procedure 1

Step	Direction		Message	Comments
	UE	SS
1			Mobile terminated establishment of Radio Resource Connection	See TS 34.108 clause 7.1.2 Establishment cause: Terminating Conversational Call.
2	->		PAGING RESPONSE
3	<-		AUTHENTICATION REQUEST
4	->		AUTHENTICATION RESPONSE
5	<-		SECURITY MODE COMMAND
6	->		SECURITY MODE COMPLETE
7	<-		SETUP	U6, (note 1)
8	->		CALL CONFIRMED	U9
A9	->		CONNECT	U8, p = Y, (note 2)
B9	->		ALERTING	U7, p = N, (note 2)
B10	UE			(note 3)
B11	->		CONNECT	U8
12			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3
13	<-		CONNECT ACKNOWLEDGE	U10
NOTE 1: With signal information included in the SETUP message. NOTE 2: The UE is supporting immediate connect (p = Y/N). See ICS/IXIT statement. NOTE 3: If necessary (see ICS/IXIT statement), the UE is made to accept the call in the way described in a ICS/IXIT statement.

Table 10.1.3/2: Establishment of an incoming call, procedure 2

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See TS34.108 clause 7.1.2 Establishment cause: Terminating Conversational Call.
2	->		PAGING RESPONSE
2a	<-		AUTHENTICATION REQUEST
2b	->		AUTHENTICATION RESPONSE
3	<-		SECURITY MODE COMMAND
4	->		SECURITY MODE COMPLETE
5	<-		SETUP	U6, (note 1)
6	->		CALL CONFIRMED	U9
A7	->		CONNECT	U8, p = Y, (note 2)
A8			Radio Bearer Setup Procedure	See TS34.108 clause 7.1.3
B7	->		ALERTING	U7, p = N, (note 2)
B8			Radio Bearer Setup Procedure	See TS34.108 clause 7.1.3
B9	UE			(note 3)
B10	->		CONNECT	U8
11			Void
12			Void
13	<-		CONNECT ACKNOWLEDGE	U10
NOTE 1: With signal information included in the SETUP message. NOTE 2: The UE is supporting immediate connect (p = Y/N). See ICS/IXIT statement. NOTE 3: If necessary (see ICS/IXIT statement), the UE is made to accept the call in the way described in a ICS/IXIT statement.

Table 10.1.3/3: Void

Table 10.1.3/4: Establishment of an incoming call, procedure 4

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See TS 34.108 clause 7.1.2 Establishment cause: Terminating Conversational Call.
2	->		PAGING RESPONSE
2a	<-		AUTHENTICATION REQUEST
2b	->		AUTHENTICATION RESPONSE
3	<-		SECURITY MODE COMMAND
4	->		SECURITY MODE COMPLETE
5	<-		SETUP	U6, (note 1)
6	->		CALL CONFIRMED	U9
7			Radio Bearer Setup Procedure	See TS 34.108 clause 7.1.3
A8	->		CONNECT	U8, p = Y, (note 2)
B8	->		ALERTING	U7, p = N, (note 2)
B9	UE			(note 3)
B10	->		CONNECT	U8
11			Void
12			Void
13	<-		CONNECT ACKNOWLEDGE	U10
NOTE 1: The signal information element is not included in the SETUP message. NOTE 2: The UE is supporting immediate connect (p = Y/N). See ICS/IXIT statement. NOTE 3: If necessary (see ICS/IXIT statement), the UE is made to accept the call in the way described in a ICS/IXIT statement.

10.1.3.1 Incoming call / U0 null state

10.1.3.1.1 Incoming call / U0 null state / SETUP received with a non supported bearer capability

10.1.3.1.1.1 Definition

The call control entity of the UE being in the state, U0, a SETUP message is received with only one bearer capability and this bearer capability is not supported by the UE.

10.1.3.1.1.2 Conformance requirement

When the network is providing a basic service at the called side, the UE shall check that the basic service(s) offered by the network in the Bearer Capability information element(s) match(es) the basic services that the UE is able to support. If a mismatch is detected, then the UE shall proceed as follows:

– if the SETUP message contained two bearer capability information elements for only one of which a mismatch is detected, the UE shall either:

– under the conditions specified in 3GPP TS 27.001 (e.g. TS 61 and TS 62), accept the SETUP message with a CALL CONFIRMED message containing the, possibly negotiated, bearer capability information element for which no mismatch is detected, or

– reject the call using cause No. 88 "incompatible destination".

– otherwise the UE shall reject the offered call using a RELEASE COMPLETE message with cause No. 88 "incompatible destination".

References

TS 24.008 clause 5.2.2.2 and annex B.3.2

10.1.3.1.1.3 Test purpose

To verify that a CC entity of the UE, upon receipt of SETUP containing one bearer capability and this bearer capability is not supported, returns a RELEASE COMPLETE with correct cause value to its peer entity, and returns to the idle mode. To verify that the CC-entities relating to the seven mobile terminating transaction identifiers are then in the state U0, "Null".

10.1.3.1.1.4 Method of test

Related ICS/IXIT statements

– supported MT 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

A mobile terminated call is initiated. The UE receives a SETUP message that contains a bearer capability not supported by the UE. The UE returns a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity is still in the state U0 with all the relevant transaction identifiers.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			Mobile terminated establishment of Radio Resource Connection	SS sends paging, See TS34.108
2	->		PAGING RESPONSE
3	<-		AUTHENTICATION REQUEST
4	->		AUTHENTICATION RESPONSE
5	<-			The SS starts integrity protection.
6			Void
7	<-		SETUP	(note 1)
8	->		RELEASE COMPLETE	(note 2)
9	<-		STATUS ENQUIRY
10	->		RELEASE COMPLETE	Cause #81 (invalid TI value).
11	SS			Repeat steps 9‑10 to cover all the transaction identifiers from 000… 110.

Specific message contents:

NOTE 1: With one bearer capability and that bearer capability is not supported by the UE.

NOTE 2: With cause #88 incompatible destination.

10.1.3.1.1.5 Test requirements

After step 7 the UE shall return a RELEASE COMPLETE message with cause value #88 (incompatible destination) and return to the idle mode.

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

10.1.3.2 Incoming call / U6 call present

10.1.3.2.1 Incoming call / U6 call present / automatic call rejection

10.1.3.2.1.1 Definition

Although the state U6 is transient, the ability to refuse a call (automatically) in this state is tested, if it is implemented at the UE.

10.1.3.2.1.2 Conformance requirement

If the mobile user wishes to refuse the call, a RELEASE COMPLETE message shall be sent with the cause #21 "call rejected".

References

TS 24.008 clause 5.2.2.3.1

10.1.3.2.1.3 Test purpose

To verify that a CC entity of the UE in CC-state U6, "Call Present", shall upon receipt of a rejection indication of the incoming call from the user, shall send RELEASE COMPLETE with the appropriate cause value to its peer entity and enter the CC-state U0, "Null". The CC entities relating to the seven mobile terminating transaction identifiers are then in state U0, "Null".

10.1.3.2.1.4 Method of test

Related ICS/IXIT statements

– supported teleservices;

– the UE supports an ability to refuse a call after receipt of a SETUP message.

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 U6 by using table 10.1.3/2.

Test procedure

A teleservice is selected that is supported by the UE; if the UE supports speech, the selected teleservice is speech. If necessary, the UE is configured for that teleservice. Then a mobile terminated call is initiated. The call control entire of the UE is brought to the state U6 (Note: The state U6 is not checked, since it is not stable). The UE is made to refuse the call (the refusal may require some preliminary preparations in order to achieve refusal at this point). The UE shall send a RELEASE COMPLETE message and enter a call control state U0. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				the UE is made to refuse the call
2	->		RELEASE COMPLETE	(note)
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:

NOTE: With cause value #21 call rejected.

10.1.3.2.1.5 Test requirements

After step 1 the UE shall return a RELEASE COMPLETE message with cause value #21 (call rejected) and return to the idle mode.

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.3.3 Incoming call / U9 mobile terminating call confirmed

10.1.3.3.1 Incoming call / U9 mobile terminating call confirmed / alerting or immediate connecting

10.1.3.3.1.1 Definition

The call control entity of the UE having entered the state, U9, with signal information received in the preceding SETUP message, the subsequent behaviour of the UE is tested.

10.1.3.3.1.2 Conformance requirement

1) The call control entity of the UE having entered the "mobile terminating call confirmed" state, if the call is accepted at the called user side, the UE proceeds as described in TS 24.008 clause 5.2.2.5. Otherwise, if the signal information element was present in the SETUP message user alerting is initiated at the UE side; if the signal information element was not present in the SETUP message, user alerting is initiated when an appropriate channel is available.

Here, initiation of user alerting means:

– the generation of an appropriate tone or indication at the UE; and

– sending of an ALERTING message by the call control entity of the MS to its peer entity in the network and entering the "call received" state.

2) In the "mobile terminating call confirmed" state or the "call received" state, the call control entity in the UE indicates acceptance of a mobile terminating call by:

– sending a CONNECT message to its peer entity in the network;

– starting Timer T313; and

– entering the "connect request" state.

References

Conformance requirement 1: TS 24.008 clause 5.2.2.3.2

Conformance requirement 2: TS 24.008 clause 5.2.2.5.

10.1.3.3.1.3 Test purpose

To verify that a CC entity in CC-state U9, "Mobile Terminating Call Confirmed", (if signalled by the network in previous SETUP message that it may alert) will either send a ALERTING message to its peer entity and enter state U7, or send a CONNECT message to its peer entity and enter U8.

10.1.3.3.1.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U9 by using table 10.1.3/2.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U9 by using a SETUP message containing signalling information element. (The state U9 is not a stable state in this case, and consequently it is not checked as an initial state.) If the UE supports immediate connect for the selected basic service (p = Y), it sends a CONNECT message and enters the state U8, connect request. Otherwise (p = N) the UE sends an ALERTING message and enters the state U7, call received. The SS checks by using the status enquiry procedure that the CC entity has entered its state as described.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
A1	->		CONNECT	p = Y
A2	<-		STATUS ENQUIRY
A3	->		STATUS	cause #30, state U8
B1	->		ALERTING	p = N
B2	<-		STATUS ENQUIRY
B3	->		STATUS	cause #30, state U7

Specific message contents:

None.

10.1.3.3.1.5 Test requirements

At step A1 the UE shall send a CONNECT message and enter U8 if the network has signalled in previous SETUP message that UE may not alert.

At step B1 the UE shall send an ALERTING message and enter state U7 if the network has signalled in previous SETUP message that UE may alert.

10.1.3.3.2 Incoming call / U9 mobile terminating call confirmed / DTCH assignment

10.1.3.3.2.1 Definition

The call control entity of the UE being in the state, U9, a radio bearer establishment procedure is performed for traffic channel.

10.1.3.3.2.2 Conformance requirement

1) It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile terminating call establishment phase.

Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control timer, but may have some secondary effects (see e.g. TS 24.008 clause 5.2.2.3.2).

2) The call control entity of the UE having entered the "mobile terminating call confirmed" state, if the call is accepted at the called user side, the UE proceeds as described in TS24.008 clause 5.2.2.5. Otherwise, if the signal information element was present in the SETUP message user alerting is initiated at the UE side; if the signal information element was not present in the SETUP message, user alerting is initiated when an appropriate channel is available.

Here, initiation of user alerting means:

– the generation of an appropriate tone or indication at the UE; and

– sending of an ALERTING message by the call control entity of the MS to its peer entity in the network and entering the "call received" state.

References

Conformance requirement 1: TS 24.008 clause 5.2.2.7

Conformance requirement 2: TS 24.008 clause 5.2.2.3.2.

10.1.3.3.2.3 Test purpose

To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", when a traffic channel is allocated by the network performing the radio bearer establishment procedure, shall sends an ALERTING message and enters state U7.

10.1.3.3.2.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U9 by using table 10.1.3/4.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U9 (by using a SETUP message not containing the signal information element). 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 UE sends an ALERTING message and enters state U7, call received. The SS verifies by using the status enquiry procedure that the UE has entered the correct state.

Expected sequence

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

Specific message contents:

None.

10.1.3.3.2.5 Test requirements

After step 1 the UE shall send an ALERTING message and enter state U7.

10.1.3.3.3 Void

10.1.3.3.4 Incoming call / U9 mobile terminating call confirmed / DISCONNECT received

10.1.3.3.4.1 Definition

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

10.1.3.3.4.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.3.3.4.3 Test purpose

To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", upon receipt of a DISCONNECT returns a RELEASE message and enters the CC-state U19, "Release Request".

10.1.3.3.4.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U9 by using table 10.1.3/4.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U9. The SS sends a DISCONNECT message to the UE. The UE responds by sending a RELEASE message and enters state U19, release request. The SS verifies by using the status enquiry procedure that the UE has entered the correct state.

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.3.3.4.5 Test requirements

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

10.1.3.3.5 Incoming call / U9 mobile terminating call confirmed / RELEASE received

10.1.3.3.5.1 Definition

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

10.1.3.3.5.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.3.3.5.3 Test purpose

1) To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".

2) To verify that the UE on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile terminating transaction identifiers are in CC-state U0, "Null".

10.1.3.3.5.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U9 by using table 10.1.3/4.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U9. The SS sends a RELEASE message to the UE. The UE responds by sending a RELEASE COMPLETE message and enters state U0, null. The SS verifies by using the status enquiry procedure that the UE has entered the correct state with the relevant transaction identifiers.

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.3.3.5.5 Test requirements

After step 1 the UE shall return 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.3.3.6 Incoming call / U9 mobile terminating call confirmed / lower layer failure

10.1.3.3.6.1 Definition

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

10.1.3.3.6.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 clause 4.5.3, TS 25.331 clause 8.3.1 and clause 8.5.6.

10.1.3.3.6.3 Test purpose

To verify that a CC entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", having detected a lower layer failure returns to idle mode, the CC entity is in state U0, "Null".

10.1.3.3.6.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U9 by using table 10.1.3/4.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The UE is brought to the state U9. 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.3.3.6.5 Test requirements

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

10.1.3.3.7 Incoming call / U9 mobile terminating call confirmed / unknown message received

10.1.3.3.7.1 Definition

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

10.1.3.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.3.3.7.3 Test purpose

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

10.1.3.3.7.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U9 by using table 10.1.3/4.

Test procedure

A MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U9. The SS sends a message with message type not defined for the protocol discriminator to the UE. The UE shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.

Expected sequence

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

Specific message contents:

None.

10.1.3.3.7.5 Test requirements

After step 1 the UE shall return a STATUS message.

10.1.3.4 Incoming call / U7 call received

10.1.3.4.1 Incoming call / U7 call received / call accepted

10.1.3.4.1.1 Definition

The call control entity of the UE being in the state, U7, a user accepts the incoming call.

10.1.3.4.1.2 Conformance requirement

In the "mobile terminating call confirmed" state or the "call received" state, the call control entity in the UE indicates acceptance of a mobile terminating call by:

– sending a CONNECT message to its peer entity in the network;

– starting Timer T313; and

– entering the "connect request" state.

References

TS 24.008 clause 5.2.2.5.

10.1.3.4.1.3 Test purpose

To verify that a CC entity of a UE in CC-state U7, "Call Received", upon a user accepting the incoming call, shall send a CONNECT message to its peer entity and enter the CC-state U8, "Connect Request".

10.1.3.4.1.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U7 by using table 10.1.3/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				the UE is made to accept the call by the user
2	->		CONNECT
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U8

Specific message contents:

None.

10.1.3.4.1.5 Test requirements

After step 1 a UE shall send a CONNECT message and enter the CC-state U8, "Connect Request".

10.1.3.4.2 Incoming call / U7 call received / termination requested by the user

10.1.3.4.2.1 Definition

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

10.1.3.4.2.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.3.4.2.3 Test purpose

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

10.1.3.4.2.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U7 by using table 10.1.3/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1				the UE is made to terminate/reject the call
2	->		DISCONNECT
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U11

Specific message contents:

None.

10.1.3.4.2.5 Test requirements

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

10.1.3.4.3 Incoming call / U7 call received / DISCONNECT received

10.1.3.4.3.1 Definition

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

10.1.3.4.3.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 TS 24.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 TS 24.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 clause 5.4.4.1.1.1 and 5.4.4.2.1.1.

10.1.3.4.3.3 Test purpose

To verify that a CC entity of a UE in CC-state U7, "Call Received", upon receipt of a DISCONNECT with a progress indicator indicating in-band information from network, if a DTCH was not assigned, returns a RELEASE message and enters the CC-state U19, "Release Request".

10.1.3.4.3.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U7 by using table 10.1.3/1.

Test procedure

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		DISCONNECT	(note)
2	->		RELEASE
3	<-		STATUS ENQUIRY
4	->		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.3.4.3.5 Test requirements

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

10.1.3.4.4 Incoming call / U7 call received / RELEASE received

10.1.3.4.4.1 Definition

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

10.1.3.4.4.2 Conformance requirement

References

TS 24.008 clause 5.4.3.3

10.1.3.4.4.3 Test purpose

1) To verify that a CC entity of a UE in CC-state U7, "Call Received", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".

2) To verify that the UE on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile terminating transaction identifiers are in CC-state U0, "Null".

10.1.3.4.4.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U7 by using table 10.1.3/1.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U7. The SS sends a RELEASE message. The UE responds with a RELEASE COMPLETE message. The SS checks by using the status enquiry procedure that the CC entity has entered state U0, null, with the relevant transaction identifiers.

Expected sequence

Step	Direction		Message	Comments
	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.3.4.4.5 Test requirements

After step 1 a UE shall return 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.3.4.5 Incoming call / U7 call received / lower layer failure

10.1.3.4.5.1 Definition

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

10.1.3.4.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.3.4.5.3 Test purpose

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

10.1.3.4.5.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U7 by using table 10.1.3/2.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The UE is brought to the state U7. 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.3.4.5.5 Test requirements

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

10.1.3.4.6 Incoming call / U7 call received / unknown message received

10.1.3.4.6.1 Definition

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

10.1.3.4.6.2 Conformance requirement

References

TS 24.008 clause 8.4.

10.1.3.4.6.3 Test purpose

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

10.1.3.4.6.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U7 by using table 10.1.3/1.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U7. The SS sends a message with message type not defined for the protocol discriminator to the UE. The UE shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.

Expected sequence

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

Specific message contents:

None.

10.1.3.4.6.5 Test requirements

After step 1 a UE shall return a STATUS message.

10.1.3.4.7 Incoming call / U7 call received / DTCH assignment

10.1.3.4.7.1 Definition

The call control entity of the UE being in the state, U7, a radio bearer establishment procedure is performed for traffic channel.

10.1.3.4.7.2 Conformance requirement

It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile terminating call establishment phase.

Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control timer, but may have some secondary effects (see e.g. TS 24.008 clause 5.2.2.3.2).

References

TS 24.008 clause 5.2.2.7.

10.1.3.4.7.3 Test purpose

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

10.1.3.4.7.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U7 by using table 10.1.3/1.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE and for which the UE does not use immediate connection; if the UE supports MT telephony without immediate connection, the selected basic service is telephony. If necessary, the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U7. 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 verifies 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 TS 34.108 clause 7.1.3
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U7

Specific message contents:

None.

10.1.3.4.7.5 Test requirements

After step 1 the CC state U7, "Call Received", shall remain unchanged.

10.1.3.4.8 Incoming call / U7 call received / RELEASE COMPLETE received

10.1.3.4.8.1 Definition

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

10.1.3.4.8.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.3.4.8.3 Test purpose

1) To verify that a CC entity of the UE in CC-state U7, "Call received", upon receipt of a RELEASE COMPLETE message with valid cause value, enters CC state U0, "Null".

2) To verify that in returning to idle mode, the CC entities relating to the seven mobile terminating transaction identifiers are in state U0, "Null".

10.1.3.4.8.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U7 by using table 10.1.3/1.

Test procedure

Expected sequence

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

Specific message contents:

NOTE 1: With the cause value chosen arbitrarily.

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

10.1.3.4.8.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.3.5 Incoming call / U8 connect request

10.1.3.5.1 Incoming call / U8 connect request / CONNECT acknowledged

10.1.3.5.1.1 Definition

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

10.1.3.5.1.2 Conformance requirement

In the "connect request" state, the call control entity of the UE shall, upon receipt of a CONNECT ACKNOWLEDGE message: stop timer T313 and enter the "active" state.

References

TS 24.008 clause 5.2.2.6.

10.1.3.5.1.3 Test purpose

To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon receipt of CONNECT ACKNOWLEDGE shall enter the CC-state U10, " Active".

10.1.3.5.1.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U8 by using table 10.1.3/2.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U8 (if the UE uses immediate connection for the selected basic service then p = Y, otherwise p = N). The SS sends a CONNECT ACKNOWLEDGE message. The SS checks by using the status enquiry procedure that the CC entity of the UE has entered state U10, active.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
A1			Radio Bearer Setup Procedure	p = Y, See TS34.108
2	<-		CONNECT ACKNOWLEDGE
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U10

Specific message contents:

None.

10.1.3.5.1.5 Test requirements

After step 2 a UE shall enter the CC-state U10, "Active".

10.1.3.5.2 Incoming call / U8 connect request / timer T313 time-out

10.1.3.5.2.1 Definition

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

10.1.3.5.2.2 Conformance requirement

1) When timer T313 expires prior to the receipt of a CONNECT ACKNOWLEDGE message, the UE shall initiate clearing in accordance with clause 5.4.3.

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.2.6

Conformance requirement 2: TS 24.008 clause 5.4.3.1

10.1.3.5.2.3 Test purpose

To verify that a CC entity of a UE in CC-state U8, "Connect Request", having waited for a reasonable length of time (e.g. expiry of timer T313) without receiving the appropriate protocol message to complete the incoming call, shall initiate the clearing of that incoming call by sending the CC message DISCONNECT and enter the CC-state U11, "Disconnect Request".

10.1.3.5.2.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U8 by using table 10.1.3/2.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U8 (if the UE uses immediate connection for the selected basic service then p = Y, otherwise p = N). The T313 expires at the UE and the UE sends a DISCONNECT message and enters state U11, disconnect request. The SS checks by using the status enquiry procedure that the UE has entered the correct state.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
A1			Radio Bearer Setup Procedure	p = Y, See TS34.108
2	->		DISCONNECT	Shall not be sent before 15 s after entry into state U8. But, shall be sent before 1,1 * T313 after entry into state U8.
3	<-		STATUS ENQUIRY
4	->		STATUS	cause #30, state U11

Specific message contents:

None.

10.1.3.5.2.5 Test requirements

After step A1 a UE shall initiate the clearing of that incoming call by sending a DISCONNECT message and enter the CC-state U11, "Disconnect Request".

10.1.3.5.3 Incoming call / U8 connect request / termination requested by the user

10.1.3.5.3.1 Definition

The call control entity of the UE being in the state, U8, the user requests for releasing of the call.

10.1.3.5.3.2 Conformance requirement

References

TS 24.008 clause 5.4.3.1

10.1.3.5.3.3 Test purpose

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

10.1.3.5.3.4 Method of test

Related ICS/IXIT statements

– supported MT circuit switched basic services;

– MT circuit switched basic services for which immediate connect is not used.

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 U8 by using table 10.1.3/2.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U8 (if the UE uses immediate connection for the selected basic service then p = Y, otherwise p = N). Then the user requests termination of the call. The UE sends a DISCONNECT message and enters state U11, disconnect request. The SS verifies by using the status enquiry procedure that the UE has entered the correct state.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
A1			Radio Bearer Setup Procedure	p = Y, See TS34.108
2				the user requests to clear the call
3	->		DISCONNECT
4	<-		STATUS ENQUIRY
5	->		STATUS	cause #30, state U11

Specific message contents:

None.

10.1.3.5.3.5 Test requirements

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

10.1.3.5.4 Incoming call / U8 connect request / DISCONNECT received with in-band information

10.1.3.5.4.1 Definition

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

10.1.3.5.4.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.3.5.4.3 Test purpose

To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon receipt of a DISCONNECT with progress indicator #8 enters CC-state U12, if the traffic channel is in speech mode, and that the UE sends a RELEASE message and enters CC-state U19 if the DTCH is not in speech mode.

10.1.3.5.4.4 Method of test

Related ICS/IXIT statements

– supported MT 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 U8 by using table 10.1.3/4.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U8. The SS sends a DISCONNECT message containing indication of in-band information availability to the UE. If channel mode is speech, the UE enters state U12, disconnect indication. If channel mode is not speech, the UE sends a RELEASE message and enters state U19, release request.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	<-		DISCONNECT	(note)
				DTCH in speech mode:
A2	<-		STATUS ENQUIRY
A3	->		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.3.5.4.5 Test requirements

After step 1 a UE shall enter CC-state U12, if the traffic channel is in speech mode. If the DTCH is not in speech mode, the UE shall send a RELEASE message and enter CC-state U19.

10.1.3.5.5 Incoming call / U8 connect request / DISCONNECT received without in-band information

10.1.3.5.5.1 Definition

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

10.1.3.5.5.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.3.5.5.3 Test purpose

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

10.1.3.5.5.4 Method of test

Related ICS/IXIT statements

– supported MT 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 U8 by using table 10.1.3/4.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U8. The SS sends a DISCONNECT message not containing indication of in-band information availability to the UE. The UE shall respond with a RELEASE message. The SS checks by using the status enquiry procedure that the CC entity of the UE has entered the state U19, release request.

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.3.5.5.5 Test requirements

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

10.1.3.5.6 Incoming call / U8 connect request / RELEASE received

10.1.3.5.6.1 Definition

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

10.1.3.5.6.2 Conformance requirement

References

TS 24.008 clause 5.4.3.3

10.1.3.5.6.3 Test purpose

1) To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter the CC-state U0, "Null".

2) To verify that the UE on returning to the idle mode releases the MM-connection and that the CC-entities relating to the seven mobile terminating transaction identifiers are in CC-state U0, "Null".

10.1.3.5.6.4 Method of test

Related ICS/IXIT statements

– supported MT 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 U8 by using table 10.1.3/1.

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.3.5.6.5 Test requirements

After step 1 a UE shall return 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.3.5.7 Incoming call / U8 connect request / lower layer failure

10.1.3.5.7.1 Definition

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

10.1.3.5.7.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.3.5.7.3 Test purpose

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

10.1.3.5.7.4 Method of test

Related ICS/IXIT statements

– supported MT 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 U8 by using table 10.1.3/1.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated call is initiated. The UE is brought to the state U8. 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.3.5.7.5 Test requirements

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

10.1.3.5.8 Incoming call / U8 connect request / DTCH assignment

10.1.3.5.8.1 Definition

The call control entity of the UE being in the state, U8, a radio bearer establishment procedure is performed for traffic channel.

10.1.3.5.8.2 Conformance requirement

It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile terminating call establishment phase.

Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control timer, but may have some secondary effects (see e.g. TS 24.008 clause 5.2.2.3.2

References

TS 24.008 clause 5.2.2.7.

10.1.3.5.8.3 Test purpose

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

10.1.3.5.8.4 Method of test

Related ICS/IXIT statements

– supported MT 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 U8 by using table 10.1.3/1.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U8. 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 verifies 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 TS 34.108 clause 7.1.3
2	<-		STATUS ENQUIRY
3	->		STATUS	cause #30, state U8

Specific message contents:

None.

10.1.3.5.8.5 Test requirements

After step 1 the CC-state U8, "Connect Request", shall remain unchanged.

10.1.3.5.9 Incoming call / U8 connect request / unknown message received

10.1.3.5.9.1 Definition

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

10.1.3.5.9.2 Conformance requirement

References

TS 24.008 clause 8.4.

10.1.3.5.9.3 Test purpose

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

10.1.3.5.9.4 Method of test

Related ICS/IXIT statements

– supported MT 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 U8 by using table 10.1.3/1.

Test procedure

An MT circuit switched basic service is selected that is supported by the UE; if the UE supports MT telephony, the selected basic service is telephony. If necessary the UE is configured for that basic service. Then a mobile terminated call is initiated. The CC entity of the UE is brought to the state U8. The SS sends a message with message type not defined for the protocol discriminator to the UE. The UE shall respond with a STATUS message, and finally the SS checks by using the status enquiry procedure that the state of the CC entity has remained unchanged.

Expected sequence

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

Specific message contents:

None.

10.1.3.5.9.5 Test requirements

After step 1 a UE shall return a STATUS message.