10.1.1 General on CC state machine verification

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

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

The principle of checking the call control functions consists in the validation of each call control identified state.

State U0 as an initial state is not verified in the tests of 10.1.2 (establishment of an outgoing call).

State U0.1 is never verified.

The steps to be followed within each performed test are:

– bring the UE into the required state;

– trigger the tested event;

– check the UE response and new state.

In clauses 10.1.2 and 10.1.3 different tables are defined to bring the UE into the required initial state. The exact table to be chosen is specified individually in clause "Initial conditions" of "Method of test" for each test case.

For each test, unless otherwise specified, a circuit switched basic service among those supported by the UE but excluding the emergency call teleservice shall be chosen arbitrarily, and the test shall be performed according to that basic service. If the only circuit switched basic service supported by the mobile is emergency call, then the incoming call tests shall not be performed and the other call control tests shall be performed with the EMERGENCY SETUP message replacing the SETUP message.

The initial states are to be checked through STATUS ENQUIRY messages sent by the SS, when feasible. This is not explicitly stated in the tables of expected sequences of signalling messages. The checking of final states are explicitly included into the expected sequences of signalling messages.

The following postamble may be used by the SS to bring UE back to idle mode in those test cases, in which it is not already included into expected sequence of signalling messages:

Table 10.1.1/1: A postamble to bring the UE back to idle mode.

Step	Direction		Message	Comments
	UE	SS
N	<–		RRC CONNECTION RELEASE
n+1	–>		RRC CONNECTION RELEASE COMPLETE
n+2	UE			the UE releases the RRC connection

The postamble has not been included into the all of the tests in order to leave an option to concatenate the procedures in the future by using a final state of a test case as an initial state to another one.

For the special case of U0, the state is checked by sending STATUS ENQUIRY message with all possible values of transaction identifier (seven values) as U0 is the only state in which for every TI the UE will answer with release complete with cause #81. If U0 is to be verified when no RRC connection exists, first a mobile terminating radio connection must be established.

The UE responses are either call management messages received by the SS or lower layers functions activated within the UE or MMI actions (e.g. the buzzing of an alerting tone).

A time-out within the UE is triggered by the SS when it does not answer back an UE expected response.

The test sequences may be split in 3 main groups:

– establishment and release of an outgoing call;

– establishment and release of an incoming call;

– in-call functions.

Some test cases use Basic Generic Procedures, "Mobile terminated establishment of Radio Resource Connection" and "Radio Bearer Setup Procedure" defined in TS34.108 clause 7.

General tolerance value on protocol timers defined in TS34.108 is used in some test cases if no specific tolerance on timer is defined in a test case.

Remark on verification of transient states

Some call control states of the user equipment may be transient, depending on implementation, configuration of the UE and previous messages.

If a test starts in a transient state, then the test is executed without verification of the starting state.