6.4 Generic procedures

36.5083GPPCommon test environments for User Equipment (UE) conformance testingEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Release 17TS

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

This clause describes UE test states which can be used in the initial condition of many test cases defined in TS 36.523-1 [18] in addition to the states already specified in clause 4.5 of this specification.

6.4.1 Initial UE states and setup procedures

6.4.1.1 Initial UE states and setup procedures

Figure 6.4.1.1-1: Initial UE states

In order that the UE can set up a call or session in E-UTRAN, there are a number of setup procedures to be undertaken in a hierarchical sequence to move between known states. The sequences are shown in figure 6.4.1.1-1 and the status of the relevant protocols in the UE in the different states are given in table 6.4.1.1-1. State 3 is defined in clause 4.5.1.

Table 6.4.1.1-1: Protocol state for each initial UE state

		RRC	ECM	EMM	ESM
State 5	Dedicated RB established	RRC_CONNECTED	ECM_CONNECTED	EMM-REGISTERED	1 default EPS bearer context active N dedicated EPS bearer context(s) active
State 5A	DC MCG/SCG Dedicated RB established	RRC_CONNECTED	ECM_CONNECTED	EMM-REGISTERED	1 default EPS bearer context active on the PCell 1 dedicated EPS bearer context(s) active on the PCell 1 dedicated EPS bearer context(s) active on the PSCell
State 5B	DC Split Dedicated RB established	RRC_CONNECTED	ECM_CONNECTED	EMM-REGISTERED	1 default EPS bearer context active on the PCell 1 dedicated EPS bearer context(s) active as a Split DRB on the PCell and the PSCell with UL transmission of PDCP SDUs on PSCell
State 6	Loopback Activated	RRC_CONNECTED	ECM_CONNECTED	EMM-REGISTERED	1 default EPS bearer context active N dedicated EPS bearer context(s) active
State 6A	DC MCG/SCG DRB Loopback Activated	RRC_CONNECTED	ECM_CONNECTED	EMM-REGISTERED	1 default EPS bearer context active 1 dedicated EPS bearer context(s) active on the PCell 1 dedicated EPS bearer context(s) active on the PSCell
State 6B	DC Split DRB Loopback Activated	RRC_CONNECTED	ECM_CONNECTED	EMM-REGISTERED	1 default EPS bearer context active 1 dedicated EPS bearer context(s) active as a Split DRB on the PCell and the PSCell with UL transmission of PDCP SDUs on PSCell

6.4.1.2 Dedicated Bearer Establishment (to state 5)

6.4.1.2.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Generic RB established (State 3).

6.4.1.2.2 Definition of system information messages

The default system information messages are used.

6.4.1.2.3 Procedure

The establishment of dedicated radio bearer connection is assumed to always be mobile terminated.

Table 6.4.1.2.3-1: Procedure for dedicated bearer establishment

Step	Procedure	Message Sequence
		U – S	Message
1	The SS configures new data radio bearer(s) and the associated dedicated EPS bearer context(s).	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer(s), associated with the dedicated EPS bearer context(s) in the NAS message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

6.4.1.2.4 Specific message contents

All specific message contents shall be referred to clause 4.6 and 4.7.

6.4.1.2A DC MCG/SCG Dedicated Bearer Establishment (to state 5A)

6.4.1.2A.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Generic RB established (State 3).

6.4.1.2A.2 Definition of system information messages

The default system information messages are used.

6.4.1.2A.3 Procedure

The establishment of MCG/SCG dedicated radio bearer connection is assumed to always be mobile terminated.

Table 6.4.1.2A.3-1: Procedure for MCG/SCG dedicated bearer establishment

Step	Procedure	Message Sequence
		U – S	Message
1	The SS configures new MCG data radio bearer and the associated dedicated EPS bearer context.	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new MCG data radio bearer, associated with the dedicated EPS bearer context in the NAS message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
4	The SS adds a PSCell and configures new SCG data radio bearer and the associated dedicated EPS bearer context.	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
5	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new SCG data radio bearer(s), associated with the dedicated EPS bearer context in the NAS message.	–>	RRC: RRCConnectionReconfigurationComplete
6	The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

6.4.1.2A.4 Specific message contents

All specific message contents shall be referred to clause 4.6 and 4.7 with the following exceptions:

Table 6.4.1.2A.4-1: RRCConnectionReconfiguration (Step 1, Table 6.4.1.2A.3-1)

Derivation Path: 36.508, Table 4.6.1-8 using conditions AM-DRB-ADD(1)

Table 6.4.1.2A.4-2: RRCConnectionReconfiguration (Step 4, Table 6.4.1.2A.3-1)

Derivation Path: 36.508, Table 4.6.1-8 using conditions PSCell_Add_SCG_DRB

6.4.1.2B DC Split Dedicated Bearer Establishment (to state 5B)

6.4.1.2B.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Generic RB established (State 3).

6.4.1.2B.2 Definition of system information messages

The default system information messages are used.

6.4.1.2B.3 Procedure

The establishment of split dedicated radio bearer connection is assumed to always be mobile terminated.

Table 6.4.1.2B.3-1: Procedure for Dual Connectivity Split dedicated bearer establishment

Step	Procedure	Message Sequence
		U – S	Message
1	The SS configures new MCG data radio bearer and the associated dedicated EPS bearer context.	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new MCG data radio bearer, associated with the dedicated EPS bearer context in the NAS message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
4	The SS adds a PSCell and configures a split data radio bearer with UL transmission of PDCP SDUs on the PSCel.	<–	RRC: RRCConnectionReconfiguration
5	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the split data radio bearer	–>	RRC: RRCConnectionReconfigurationComplete
6	Void	–	–

6.4.1.2B.4 Specific message contents

All specific message contents shall be referred to clause 4.6 and 4.7 with the following exceptions:

Table 6.4.1.2B.4-1: RRCConnectionReconfiguration (Step 1, Table 6.4.1.2A.3-1)

Derivation Path: 36.508, Table 4.6.1-8 using conditions AM-DRB-ADD(1)

Table 6.4.1.2B.4-2: RRCConnectionReconfiguration (Step 4, Table 6.4.1.2A.3-1)

Derivation Path: 36.508, Table 4.6.1-8 using conditions PSCell_Add_Split_DRB

6.4.1.3 Loopback Activation (to state 6)

6.4.1.3.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in Dedicated Radio Bearer Established (State 5).

6.4.1.3.2 Definition of system information messages

The default system information messages are used.

6.4.1.3.3 Procedure

Table 6.4.1.3.3-1: Procedure for loopback activation

Step	Procedure	Message Sequence
		U – S	Message
1	The SS transmits an ACTIVATE RB TEST MODE message to activate UE radio bearer test mode procedure.	<–	RRC: DLInformationTransfer TC: ACTIVATE RB TEST MODE
2	The UE transmits an ACTIVATE RB TEST MODE COMPLETE message.	–>	RRC: ULInformationTransfer TC: ACTIVATE RB TEST MODE COMPLETE
3	The SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode.	<–	RRC: DLInformationTransfer TC: CLOSE UE TEST LOOP
4	The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated (State 6).	–>	RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE

6.4.1.3.4 Specific message contents

All specific message contents shall be referred to clause 4.6, 4.7 and 4.7A.

6.4.1.3A DC MCG/SCG DRB Loopback Activation (to state 6A)

6.4.1.3A.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in DC MCG/SCG Dedicated Radio Bearer Established (State 5A).

6.4.1.3A.2 Definition of system information messages

The default system information messages are used.

6.4.1.3A.3 Procedure

Same procedure as in sub-clause 6.4.1.3.3.

6.4.1.3A.4 Specific message contents

All specific message contents shall be referred to clause 4.6, 4.7 and 4.7A.

6.4.1.3B DC Split DRB Loopback Activation (to state 6B)

6.4.1.3B.1 Initial conditions

System Simulator:

– Parameters are set to the default parameters for the basic single cell environment, as defined in subclause 4.4, unless otherwise specified in the test case.

User Equipment:

– The UE shall be in DC Split Dedicated Radio Bearer Established (State 5B).

6.4.1.3B.2 Definition of system information messages

The default system information messages are used.

6.4.1.3B.3 Procedure

Same procedure as in sub-clause 6.4.1.3.3.

6.4.1.3B.4 Specific message contents

All specific message contents shall be referred to clause 4.6, 4.7 and 4.7A.

6.4.2 Test procedures

6.4.2.1 Introduction

This section defines test procedures which can be used within test procedure sequences for test steps where checking the UE state is needed.

For each test procedure,

– at the start of the test procedure,

– the System Simulator condition and the value of system information messages are the ones applicable in the test case referring to this test procedure, as they are after the execution of the test step immediately preceding the test step where the test procedure is used;

– the initial UE condition is one indicated in the test case referring to this procedure, as it is after the execution of the test step immediately preceding the test step where the test procedure is used.

– at the end of the test procedure,

– the System Simulator condition after the test procedure execution is complete is the same as before it is started (this should not be changed by the test procedure).

6.4.2.2 Test procedure to check RRC_IDLE state

This procedure aims at checking whether the UE is in RRC_IDLE on a certain cell of a test case or not.

Table 6.4.2.2-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message/PDU/SDU
0	The SS waits 1 second.	–	–	–	–
1	The SS sends RRC Paging message with UE S-TMSI on the cell(s) specified in the test case.	<–	RRC: Paging (PCCH)	–	–
2	Check: Does the UE send an RRCConnectionRequest message on the cell specified in the test case ?	–>	RRC: RRCConnectionRequest		P
3	The SS transmits a RRCConnectionSetup message	<–	RRC: RRCConnectionSetup	–	–
4	The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.	–>	RRC: RRCConnectionSetup Complete NAS: SERVICE REQUEST	–	–
5 – 6	Void	–	–	–	–
7	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand	–	–
8	The UE transmits a SecurityModeComplete message.	–>	RRC: SecurityModeComplete	–	–
9	The SS transmits a RRCConnectionReconfiguration message to establish the default bearer with condition SRB2-DRB(1, 0) according to 4.8.2.2.1.1,	<–	RRC: RRCConnectionReconfiguration	–	–
10	The UE transmits an RRCConnectionReconfiguration complete message.	–>	RRC: RRCConnectionReconfigurationComplete	–	–
11	The SS release the RRC connection.	<–	RRC: RRCConnectionRelease	–	–

6.4.2.3 Test procedure to check RRC_CONNECTED state

Table 6.4.2.3-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message/PDU/SDU
1	The SS sends UECapabilityEnquiry message to the UE.	<–	UECapabilityEnquiry	–	–
2	Check: Does the UE send a UECapabilityInformation message?	–>	UECapabilityInformation		P

6.4.2.4 Test procedure Paging (for NAS testing)

This procedure aims at checking whether the UE is in registered with a certain S-TMSI.

For the PS domain this procedure is identical to the procedure in 6.4.2.2 except that the S-TMSI as indicated in step 1 is the one explicitly specified in the test step calling this procedure.

For the CS domain the test procedure is FFS (i.e. it shall be avoided to make use of CS paging in the test case design).

6.4.2.5 Test procedure for no response to paging (for NAS testing)

This procedure aims at checking that the UE ignores paging messages with a specified identity.

The procedure is defined in table 6.4.2.5-1.

Table 6.4.2.5-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS waits 1 second.	–	–	–	–
1	The SS transmits a paging message using the UE identity and the CN domain which are both specified in the referring test step, and on the cell which is specified in the referring test step.	<–	Paging	–	–
2	Check: Does the UE send an RRCConnectionRequest message on the cell where the paging was transmitted within the next 3s?	–>	RRCConnectionRequest		F

6.4.2.6 Test procedure to check that a dedicated EPS bearer context is active (for NAS testing)

This procedure aims at checking that a dedicated EPS bearer context is active.

The procedure is defined in table 6.4.2.6-1.

Table 6.4.2.6-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS modifies existing data radio bearer(s) and the associated EPS bearer context(s) with Bearer QoS update.	<–	RRC: RRCConnectionReconfiguration NAS: MODIFY EPS BEARER CONTEXT REQUEST	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the modification of the existing data radio bearer(s), associated with the EPS bearer context(s) in the NAS message.	–>	RRC: RRCConnectionReconfigurationComplete	–	–
3	Check: Does the UE transmit a MODIFY EPS BEARER CONTEXT ACCEPT message?	–>	RRC: ULInformationTransfer NAS: MODIFY EPS BEARER CONTEXT ACCEPT		P

6.4.2.7 Test procedure to check that UE is camped on a new E-UTRAN cell

This procedure aims at checking whether the UE is camping on a new E-UTRAN cell with different TAI of a test case or not.

The procedure is defined in table 6.4.2.7-1.

Table 6.4.2.7-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits an RRCConnectionRequest message on the cell specified in the test case.	–>	RRC: RRCConnectionRequest	–	–
2	SS transmit an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup	–	–
3	The UE transmits an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.	–>	RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST	–	–
4	SS responds with TRACKING AREA UPDATE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT	–	–
5	Check: Does the UE send a TRACKING AREA UPDATE COMPLETE on the cell specified in the test case?	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE	–	P
6	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease	–	–

NOTE 1: The periodic tracking area updating timer T3412 is deactivated by default during the attach procedure (TS 36.508 clause 4.7.2).

NOTE 2: The SS does not initiate authentication and NAS SECURITY MODE COMMAND are not performed (reuse of keys allocated during the attach procedure).

6.4.2.7A Test procedure to check that UE is camped on E-UTRAN cell upon mobility from another RAT

This procedure aims at checking whether the UE is camping on a E-UTRAN cell upon mobility from another RAT after Inter RAT reselection.

The procedure if PDP context was established before inter RAT reselection, is defined in table 6.4.2.7A-1.

Table 6.4.2.7A-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a RRCConnectionRequest message on the cell specified in the test case.	–>	RRC: RRCConnectionRequest	–	–
2	SS transmit an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup	–	–
3	The UE transmits a RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.	–>	RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST	–	–
4	The SS transmits a NAS SECURITY MODE COMMAND message to activate NAS security (mapped security context) (Note 1).	<–	RRC: DLInformationTransfer NAS: SECURITY MODE COMMAND	–	–
5	The UE transmits a NAS SECURITY MODE COMPLETE message and establishes the initial security configuration.	–>	RRC: ULInformationTransfer NAS: SECURITY MODE COMPLETE	–	–
6	SS responds with TRACKING AREA UPDATE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT	–	–
7	Check: Does the UE send a TRACKING AREA UPDATE COMPLETE on the cell specified in the test case?	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE	–	P
8	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease	–	–
Note 1: Step 4 and 5 are executed only when UE and SS does not have a native security context.

The procedure if PDP context was not established before inter RAT reselection, is defined in table 6.4.2.7A-2.

Table 6.4.2.7A-2: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	EXCEPTION: For Rel-8 and Rel-9 steps 1 to 6 are optional and depend on UE implementation. A Rel-10 UE directly starts attach procedure from step 6.	–	–	–	–
1	The UE transmits a RRCConnectionRequest message on the cell specified in the test case.	–>	RRC: RRCConnectionRequest	–	–
2	SS transmit an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup	–	–
3	The UE transmits a RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.	–>	RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST	–	–
4	The SS transmits a TRACKING AREA UPDATE REJECT message with cause #40 (No EPS bearer context activated) to force attach the UE	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE REJECT
–	EXCEPTION: Step 5 describes the behaviour that depends on UE behaviour (Note 1).	–	–	–	–
5	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease	–	–
–	EXCEPTION: Step 6 describes a behaviour which depends on the UE capability	–	–	–	–
6	IF NOT pc_Auto_PDN_Connectivity, the user initiates an attach by MMI or by AT command. (Note 2)	–	–	–	–
7-22	Steps 2 to 17 of the generic UE Registration procedure (4.5.2.3-1) are executed to successfully complete the Attach procedure.	–	–	–	–
Note 1: SS waits for 1.5 second to receive the Attach Request on the existing RRC Connection. In case Attach Request is not received within 1.5 second, existing RRC Connection is released. Note 2: The request is assumed to be triggered by AT command AT+CGDCONT=1,"IP" followed by AT+CGACT=1

6.4.2.7A.1 Specific message contents

Table 6.4.2.7A.1-1: TRACKING AREA UPDATE REQUEST (Step 3, table 6.4.2.7A-1, 6.4.2.7A-2)

Derivation Path: 36.508 clause 4.7.2
Information Element	Value/remark	Comment	Condition
EPS update type
EPS update type Value	‘000’B	TA updating	TA_only
	‘001’B or ‘010’B	Combined TA/LA updating or combined TA/LA updating with IMSI attach	No_LAU_CombinedRAU_GERAN_UTRA
	‘010’B	Combined TA/LA updating with IMSI attach	LAU_CombinedRAU_GERAN_UTRA
"Active" flag	Any allowed value
NAS key set identifier
NAS key set identifier	The valid NAS key set identifier of the UE
TSC	‘0’B	native security context (for KSI_ASME)	Native_Secuirty_Context
	‘1’B	mapped security context (for KSI_SGSN)	Mapped_Secuirty_Context
GPRS ciphering key sequence number	Not present or any allowed value
Old P-TMSI signature	Any allowed value
Additional GUTI	Not present or any allowed value
Nonce_UE	Not present or any allowed value
UE radio capability information update needed	Not present or any allowed value
EPS bearer context status	Not present or (octet 3 = (‘00100000’B or ‘01100000’B) and octet 4 = ‘00000000’B)		Bearer_Established
	Not present or (octet 3 = ‘00000000’B and octet 4 = ‘00000000’B)		No_Bearer_Established

Condition	Explanation
TA_only	See the definition below table 4.7.2-24.
combined_TA_LA	See the definition below table 4.7.2-24.
Native_Secuirty_Context	UE has performed AKA on the EUTRA Cell
Mapped_Secuirty_Context	UE has performed AKA on the UTRA/GERAN Cell
No_LAU_CombinedRAU_GERAN_UTRA	UE has not performed location area update procedure or a combined routing area update procedure in A/Gb or Iu mode
LAU_CombinedRAU_GERAN_UTRA	UE has performed location area update procedure or a combined routing area update procedure in A/Gb or Iu mode
Bearer_Established	Bearer is Established when UE earlier camped at UTRAN/GERAN cell or UE previously successfully camped in EUTRA cell.
No_Bearer_Established	Bearer is not Established when UE earlier camped at UTRAN/GERAN cell and UE did not previously camped in EUTRA cell.

This message is sent integrity protected when a valid security context exists and without integrity protection otherwise.

6.4.2.7B Test procedure to check that UE is camped on a new E-UTRAN cell / UP CIoT

This procedure aims at checking whether the UE is camping on a new E-UTRAN cell with different TAI of a test case or not.

The procedure is defined in table 6.4.2.7B-1.

Table 6.4.2.7B-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits an RRCConnectionResumeRequest message on the cell specified in the test case.	–>	RRC: RRCConnectionResumeRequest	–	–
2	SS transmit an RRCConnectionResume message.	<–	RRC: RRCConnectionResume	–	–
3	The UE transmits an RRCConnectionResumeComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.	–>	RRC: RRCConnectionResumeComplete NAS: TRACKING AREA UPDATE REQUEST	–	–
4	SS responds with TRACKING AREA UPDATE ACCEPT message.	<–	RRC: DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT	–	–
5	Check: Does the UE send a TRACKING AREA UPDATE COMPLETE on the cell specified in the test case?	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE	–	P
6	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease	–	–

Table 6.4.2.7B-2: RRCConnectionRelease (Step 6)

Derivation Path: 36.331 clause 6.2.2
Information Element	Value/remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
releaseCause	other
redirectedCarrierInfo	Not present
idleModeMobilityControlInfo	Not present
nonCriticalExtension SEQUENCE {}	Not present
}
}
}
}

6.4.2.8 Test procedure to check that UE is camped on a new UTRAN cell

This procedure aims at checking whether the UE is camping on a new UTRAN cell of a test case or not.

The procedure is defined in table 6.4.2.8-1.

Table 6.4.2.8-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a RRC CONNECTION REQUEST message on the cell specified in the test case.	–>	RRC: RRC CONNECTION REQUEST	–	–
2	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC: RRC CONNECTION SETUP	–	–
3	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC: RRC CONNECTION SETUP COMPLETE	–	–
4	The UE transmits a ROUTING AREA UPDATE REQUEST message.	–>	RRC: INITIAL DIRECT TRANSFER NAS: ROUTING AREA UPDATE REQUEST	–	–
5	The SS transmits a SECURITY MODE COMMAND message.	<–	RRC: SECURITY MODE COMMAND	–	–
6	The UE transmits a SECURITY MODE COMPLETE message.	–>	RRC: SECURITY MODE COMPLETE	–	–
7	The SS transmits a ROUTING AREA UPDATE ACCEPT message.	<–	RRC: DOWNLINK DIRECT TRANSFER NAS: ROUTING AREA UPDATE ACCEPT	–	–
8	The UE transmits a ROUTING AREA UPDATE COMPLETE message.	–>	RRC: UPLINK DIRECT TRANSFER NAS: ROUTING AREA UPDATE COMPLETE	–	–
9	The SS transmits a RRC CONNECTION RELEASE message.	<–	RRC: RRC CONNECTION RELEASE	–	–
10	Check: Does the UE transmit an RRC CONNECTION RELEASE COMPLETE message on the cell specified in the test?	–>	RRC: RRC CONNECTION RELEASE COMPLETE	–	P

NOTE: The TS 34.108 [5] and TS 34.123-1 [7] use Network Mode of Operation I as default, for this reason a combined MM/GMM procedure is performed.

6.4.2.9 Test procedure to check that UE is camped on a new GERAN cell

This procedure aims at checking whether the UE is camping on a new GERAN cell of a test case or not.

The procedure is defined in table 6.4.2.9-1.

Table 6.4.2.9-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE send a CHANNEL REQUEST message on the cell(s) specified in the test case?	–>	CHANNEL REQUEST	–	–
2	An uplink TBF is established in order to allow the UE to transmit a ROUTING AREA UPDATE REQUEST message signalling.	–	–	–	–
3	The UE transmits a ROUTING AREA UPDATE REQUEST message.	–>	ROUTING AREA UPDATING REQUEST	–	–
4	A downlink TBF is established by the SS in order to transmit the AUTHENTICATION AND CIPHERING REQUEST message	–	–	–	–
5	The SS transmits an AUTHENTICATION AND CIPHERING REQUEST message.	<–	AUTHENTICATION AND CIPHERING REQUEST	–	–
6	An uplink TBF is established in order to allow the UE to transmit an AUTHENTICATION AND CIPHERING RESPONSE message	–	–	–	–
7	The UE transmits an AUTHENTICATION AND CIPHERING RESPONSE message.	–>	AUTHENTICATION AND CIPHERING RESPONSE	–	–
8	A downlink TBF is established by the SS in order to transmit the ROUTING AREA UPDATE ACCEPT message	–	–	–	–
9	The SS transmits a ROUTING AREA UPDATE ACCEPT message.	<–	ROUTING AREA UPDATING ACCEPT	–	–
10	An uplink TBF is established in order to allow the UE to transmit a ROUTING AREA UPDATE COMPLETE message			–	–
11	The UE transmits a ROUTING AREA UPDATE COMPLETE message.	–>	ROUTING AREA UPDATING COMPLETE	–	P

NOTE: The TS 51.010-1 [25] uses Network Mode of Operation I as default, for this reason a combined MM/GMM procedure is performed.

6.4.2.10 Test procedure to check that UE performs tracking area updating procedure without ISR and security reconfiguration after successful completion of handover from UTRA

This procedure aims at checking whether the UE performs tracking area updating procedure where ISR is not activated and security reconfiguration after successful completion of handover from UTRA.

The procedure is defined in table 6.4.2.10-1.

Table 6.4.2.10-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits an ULInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE REQUEST message.	–>	RRC: ULInformationTransfer NAS: TRACKING AREA UPDATE REQUEST	–	–
2	The SS transmits a DLInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE ACCEPT message.	<–	RRC:DLInformationTransfer NAS: TRACKING AREA UPDATE ACCEPT	–	–
3	The UE transmits an ULInformationTransfer message on the cell specified in the test case. This message includes a TRACKING AREA UPDATE COMPLETE message.	–>	RRC:ULInformationTransfer NAS: TRACKING AREA UPDATE COMPLETE	–	–
–	EXCEPTION: Steps 4a1 to 4a2 describe behaviour that depends on the IE included in TRACKING AREA UPDATE REQUEST in step 1.	–	–	–	–
4a1	IF TRACKING AREA UPDATE REQUEST transmitted in step 1 does not contain a valid KSI_ASME THEN the SS transmits a DLInformationTransfer message on the cell specified in the test case. This message includes an AUTHENTICATION REQUEST message.	<–	RRC:DLInformationTransfer NAS: AUTHENTICATION REQUEST	–	–
4a2	The UE transmits an ULInformationTransfer message on the cell specified in the test case. This message includes an AUTHENTICATION RESPONSE message.	–>	RRC:ULInformationTransfer NAS: AUTHENTICATION RESPONSE	–	–
5	The SS transmits a DLInformationTransfer message on the cell specified in the test case. This message includes a SECURITY MODE COMMAND message to take the native EPS security context into use.	<–	RRC:DLInformationTransfer NAS: SECURITY MODE COMMAND	–	–
6	The UE transmits an ULInformationTransfer message on the cell specified in the test case. This message includes a SECURITY MODE COMPLETE message.	–>	RRC:ULInformationTransfer NAS: SECURITY MODE COMPLETE	–	–
7	The SS transmits an RRCConnectionReconfiguration message to perform intra cell handover and security reconfiguration on the cell specified in the test case.	<–	RRC:RRCConnectionReconfiguration	–	–
8	Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on the cell specified in the test case?	–>	RRC:RRCConnectionReconfigurationComplete	–	P

Table 6.4.2.10-2: Message TRACKING AREA UPDATE REQUEST (step 1, Table 6.4.2.10-1)

Derivation Path: 36.508 clause 4.7.2-27
Information Element	Value/remark	Comment	Condition
NAS key set identifier
NAS key set identifier	The valid NAS key set identifier of the UE	mapped security context (for KSI_SGSN)
TSC	1
Non-current native NAS key set identifier
NAS key set identifier	The valid NAS key set identifier of the UE	native security context (for KSI_ASME)
TSC	0
Old P-TMSI signature	any allowed value
Additional GUTI	any allowed value

Table 6.4.2.10-3: RRCConnectionReconfiguration (step 7, Table 6.4.2.10-1)

Derivation Path: 36.508, Table 4.6.1-8

Table 6.4.2.10-4: SecurityConfigHO (IE in RRCConnectionReconfiguration, Table 6.4.2.10-3)

Derivation Path: 36.508, Table 4.6.4-1
Information Element	Value/remark	Comment	Condition
SecurityConfigHO ::= SEQUENCE {
handoverType CHOICE {
intraLTE SEQUENCE {
keyChangeIndicator	TRUE
nextHopChainingCount	0
}
}
}

6.4.3 Reference test procedures for TTCN development

This clause describes reference test procedures for the purpose of TTCN development.

6.4.3.1 UE triggered establishment of a dedicated EPS bearer context

Table 6.4.3.1-1: Test procedure sequence

St	Procedure	Message Sequence
		U – S	Message
1	Cause the UE to request bearer resource allocation of dedicated EPS bearer associated with first PDN connectivity. (see Note 1)	–	–
–	EXCEPTION: Steps 2a1 to 2a7 describe behaviour that depends on RRC state; the "lower case letter" identifies a step sequence that takes place if the UE is in RRC_IDLE state.	–	–
2a1	IF the UE is in RRC_IDLE state THEN the UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
2a2	The SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
2a3	The UE transmits an RRCConnectionSetupComplete including the SERVICE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST
2a4	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand
2a5	The UE transmits a SecurityModeComplete message and establishes the initial security configuration.	–>	RRC: SecurityModeComplete
2a6	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context. The RRCConnectionReconfiguration message is using condition SRB2-DRB(n, m) where n and m are the number of DRBs associated with existing EPS bearer contexts and configured respectively with RLC-AM and RLC-UM.	<–	RRC: RRCConnectionReconfiguration
2a7	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ULInformationTransfer message including the BEARER RESOURCE ALLOCATION REQUEST message.	–>	RRC: ULInformationTransfer NAS: BEARER RESOURCE ALLOCATION REQUEST
4	The SS transmits an RRCConnectionReconfiguration message including the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message to establish the dedicated EPS bearer context.	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST
5	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
6	The UE transmits an ULInformationTransfer message including the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT
Note 1: The request is assumed to be triggered by AT command +CGDSCONT, and +CGACT (activated). Note 2: If UE sends IP related data this shall be handled by the SS.

6.4.3.2 UE triggered establishment of a default EPS bearer context associated with an additional PDN

Table 6.4.3.2-1: Test procedure sequence

St	Procedure	Message Sequence
		U – S	Message
1	Cause the UE to request connectivity to an additional PDN. (see Note 1)	–	–
–	EXCEPTION: Steps 2a1 to 2a7 describe behaviour that depends on RRC state; the "lower case letter" identifies a step sequence that takes place if the UE is in RRC_IDLE state.	–	–
2a1	IF the UE is in RRC_IDLE state THEN the UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
2a2	The SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
2a3	The UE transmits an RRCConnectionSetupComplete including the SERVICE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST
2a4	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand
2a5	The UE transmits a SecurityModeComplete message and establishes the initial security configuration.	–>	RRC: SecurityModeComplete
2a6	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context. The RRCConnectionReconfiguration message is using condition SRB2-DRB(n, m) where n and m are the number of DRBs associated with existing EPS bearer contexts and configured respectively with RLC-AM and RLC-UM.	<–	RRC: RRCConnectionReconfiguration
2a7	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ULInformationTransfer message including the PDN CONNECTIVITY REQUEST message.	–>	RRC: ULInformationTransfer NAS: PDN CONNECTIVITY REQUEST
4	The SS transmits an RRCConnectionReconfiguration message including the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to establish the default EPS bearer context.	<–	RRC: RRCConnectionReconfiguration NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST
5	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
–	EXCEPTION: In parallel to the event described in step 6 below, the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.	–	–
6	The UE transmits an ULInformationTransfer message including the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message.	–>	RRC: ULInformationTransfer NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT
Note 1: The request is assumed to be triggered by AT command +CGDCONT and +CGACT (activated). Note 2: If UE sends IP related data this shall be handled by the SS.

Table 6.4.3.2-2: Message PDN CONNECTIVITY REQUEST (step 3, Table 6.4.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	UE assigns a particular PTI not yet used between 1 and 254
ESM information transfer flag	Not present	This IE is only used during an attach procedure.
Access point name	APN-1(New PDN name)	The requested PDN is different from default PDN

6.4.3.3 UE triggered modification of an EPS bearer context

Table 6.4.3.3-1: Test procedure sequence

St	Procedure	Message Sequence
		U – S	Message
1	Cause the UE to request bearer resource modification of EPS bearer associated with first PDN connectivity. (see Note 1)	–	–
–	EXCEPTION: Steps 2a1 to 2a7 describe behaviour that depends on RRC state; the "lower case letter" identifies a step sequence that takes place if the UE is in RRC_IDLE state.	–	–
2a1	IF the UE is in RRC_IDLE state THEN the UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
2a2	The SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
2a3	The UE transmits an RRCConnectionSetupComplete including the SERVICE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST
2a4	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand
2a5	The UE transmits a SecurityModeComplete message and establishes the initial security configuration.	–>	RRC: SecurityModeComplete
2a6	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context. The RRCConnectionReconfiguration message is using condition SRB2-DRB(n, m) where n and m are the number of DRBs associated with existing EPS bearer contexts and configured respectively with RLC-AM and RLC-UM.	<–	RRC: RRCConnectionReconfiguration
2a7	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ULInformationTransfer message including the BEARER RESOURCE MODIFICATION REQUEST message.	–>	RRC: ULInformationTransfer NAS: BEARER RESOURCE MODIFICATION REQUEST
4	The SS transmits an RRCConnectionReconfiguration message including the MODIFY EPS BEARER CONTEXT REQUEST message to modify the EPS bearer context.	<–	RRC: RRCConnectionReconfiguration NAS: MODIFY EPS BEARER CONTEXT REQUEST
5	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
6	Check: Does the UE transmit an ULInformationTransfer message including the MODIFY EPS BEARER CONTEXT ACCEPT message?	–>	RRC: ULInformationTransfer NAS: MODIFY EPS BEARER CONTEXT ACCEPT
Note 1: The request is assumed to be triggered by AT command +CGCMOD. Note 2: If UE sends IP related data this shall be handled by the SS.

6.4.3.4 UE triggered deletion of an EPS bearer context

Table 6.4.3.4-1: Test procedure sequence

St	Procedure	Message Sequence
		U – S	Message
1	Cause the UE to request bearer resource release of dedicated EPS bearer associated with first PDN connectivity. (see Note 1)	–	–
–	EXCEPTION: Steps 2a1 to 2a7 describe behaviour that depends on RRC state; the "lower case letter" identifies a step sequence that takes place if the UE is in RRC_IDLE state.	–	–
2a1	IF the UE is in RRC_IDLE state THEN the UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
2a2	The SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
2a3	The UE transmits an RRCConnectionSetupComplete including the SERVICE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST
2a4	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand
2a5	The UE transmits a SecurityModeComplete message and establishes the initial security configuration.	–>	RRC: SecurityModeComplete
2a6	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context. The RRCConnectionReconfiguration message is using condition SRB2-DRB(n, m) where n and m are the number of DRBs associated with existing EPS bearer contexts and configured respectively with RLC-AM and RLC-UM.	<–	RRC: RRCConnectionReconfiguration
2a7	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ULInformationTransfer message including the BEARER RESOURCE MODIFICATION REQUEST message.	–>	RRC: ULInformationTransfer NAS: BEARER RESOURCE MODIFICATION REQUEST
4	The SS transmits an RRCConnectionReconfiguration message including the DEACTIVATE EPS BEARER CONTEXT REQUEST message to delete EPS bearer context.	<–	RRC: RRCConnectionReconfiguration NAS: DEACTIVATE EPS BEARER CONTEXT REQUEST
5	The UE transmits an RRCConnectionReconfigurationComplete message	–>	RRC: RRCConnectionReconfigurationComplete
6	The UE transmits an ULInformationTransfer message including the DEACTIVATE EPS BEARER CONTEXT ACCEPT message.	–>	RRC: ULInformationTransfer NAS: DEACTIVATE EPS BEARER CONTEXT ACCEPT
Note 1: The request is assumed to be triggered by AT command +CGACT (deactivated). Note 2: If UE sends IP related data this shall be handled by the SS.

6.4.3.5 UE triggered CS call

Table 6.4.3.5-1: Test procedure sequence

St	Procedure	Message Sequence
		U – S	Message
1	Cause the UE to originate CS call. (see Note 1)	–	–
–	EXCEPTION: Steps 2a1 to 2b1 describe behaviour that depends on RRC state; the "lower case letter" identifies a step sequence that takes place depending on RRC state.	–	–
2a1	IF the UE is in RRC_IDLE state THEN the UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
2a2	The SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
2a3	The UE transmits an RRCConnectionSetupComplete including the EXTENDED SERVICE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: EXTENDED SERVICE REQUEST
2b1	ELSE The UE transmits an ULInformationTransfer message including the EXTENDED SERVICE REQUEST message.	–>	RRC: ULInformationTransfer NAS: EXTENDED SERVICE REQUEST
Note 1: The request is assumed to be triggered by AT command D.

6.4.3.6 UE triggered MO SMS over SGs

Table 6.4.3.6-1: Test procedure sequence

St	Procedure	Message Sequence
		U – S	Message
1	Cause the UE to originate SMS message. (see Note 1)	–	–
–	EXCEPTION: Steps 2a1 to 2a7 describe behaviour that depends on RRC state; the "lower case letter" identifies a step sequence that takes place if the UE is in RRC_IDLE state.	–	–
2a1	IF the UE is in RRC_IDLE state THEN the UE transmits an RRCConnectionRequest message.	–>	RRC: RRCConnectionRequest
2a2	The SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup
2a3	The UE transmits an RRCConnectionSetupComplete including the SERVICE REQUEST message.	–>	RRC: RRCConnectionSetupComplete NAS: SERVICE REQUEST
2a4	The SS transmits a SecurityModeCommand message to activate AS security.	<–	RRC: SecurityModeCommand
2a5	The UE transmits a SecurityModeComplete message and establishes the initial security configuration.	–>	RRC: SecurityModeComplete
2a6	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context. The RRCConnectionReconfiguration message is using condition SRB2-DRB(n, m) where n and m are the number of DRBs associated with existing EPS bearer contexts and configured respectively with RLC-AM and RLC-UM.	<–	RRC: RRCConnectionReconfiguration
2a7	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
3	The UE transmits an ULInformationTransfer message including the UPLINK NAS TRANSPORT message to send the SMS message.	–>	RRC: ULInformationTransfer NAS: UPLINK NAS TRANSPORT
4	The SS transmits a DLInformationTransfer message including the DOWNLINK NAS TRANSPORT message to acknowledge receipt of the SMS message.	<–	RRC: DLInformationTransfer NAS: DOWNLINK NAS TRANSPORT
5	The SS transmits a DLInformationTransfer message including the DOWNLINK NAS TRANSPORT message to send the delivery report.	<–	RRC: DLInformationTransfer NAS: DOWNLINK NAS TRANSPORT
6	The UE transmits an ULInformationTransfer message including the UPLINK NAS TRANSPORT message to acknowledge receipt of the delivery report.	–>	RRC: ULInformationTransfer NAS: UPLINK NAS TRANSPORT
Note 1: The request is assumed to be triggered by AT command +CMGW and +CMSS.

6.4.3.7 CS fallback to UTRAN procedures (LAI of UTRAN cell same as the LAI received in combined Attach procedure in EUTRA cell)

All procedures specified in this clause are referred to the UTRA target cell where the UE has been redirected or handed over from the EUTRA cell after a CS call requested. The default message contents are found in TS 34.108 [5], clause 9.

The procedures in 6.4.3.7.1 – 6.4.3.7.4 are applied if the UE supports (EUTRA) RRC connection release with redirection and Multi Cell System Information to UTRAN. The procedures in 6.4.3.7.5 – 6.4.3.7.7 are applied if the UE supports PS HO from EUTRA to UTRAN.

6.4.3.7.1 CS fallback to UTRAN with redirection / MT call (PS bearers not established)

Table 6.4.3.7.1-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits an RRC CONNECTION REQUEST message.	–>	RRC CONNECTION REQUEST	–	–
2	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
3	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
–	EXCEPTION: In parallel to the events described in step 4 to 15 the step specified in Table 6.4.3.7.1-2 takes place.	–	–	–	–
4	Check: Does the UE transmit a PAGING RESPONSE message?	–>	PAGING RESPONSE	–	P
5-15	Steps 7 to 17 of the generic test procedure in TS 34.108 [5] subclause 7.2.3.1.3 are performed using the UTRA reference radio bearer parameters and combination "UTRA Speech" according to subclause 4.8.3 and Table 4.8.3-1. NOTE: Mobile terminating CS call is established.	–	–	–	–
16	The SS transmits a SECURITY MODE COMMAND message for the PS domain. See Note 1.	<–	SECURITY MODE COMMAND	–	–
17	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
18	The SS transmits a ROUTING AREA UPDATE ACCEPT message.	<–	ROUTING AREA UPDATE ACCEPT	–	–
19	The UE transmits a ROUTING AREA UPDATE COMPLETE message.	–>	ROUTING AREA UPDATE COMPLETE	–	–
Note 1: A real network will initiate the security mode command procedure for the PS domain immediately after receiving the ROUTING AREA UPDATE REQUEST, but in this test procedure it was chosen to complete the procedure for CS domain first, in order to avoid the possibility of a security mode command procedure running in parallel with another RRC procedure.

Table 6.4.3.7.1-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a ROUTING AREA UPDATE REQUEST message.	–>	ROUTING AREA UPDATE REQUEST	–	–

6.4.3.7.2 CS fallback to UTRAN with redirection / MO call (PS bearers not established)

Table 6.4.3.7.2-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits an RRC CONNECTION REQUEST message.	–>	RRC CONNECTION REQUEST	–	–
2	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
3	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
–	EXCEPTION: In parallel to the events described in step 4 to 15 the step specified in Table 6.4.3.7.2-2 takes place.	–	–	–	–
4	Check: Does the UE transmit a CM SERVICE REQUEST message?	–>	CM SERVICE REQUEST	–	P
5-15	Steps 6 to 16 of the generic test procedure in TS 34.108 [5] subclause 7.2.3.2.3 are performed using the UTRA reference radio bearer parameters and combination "UTRA Speech" according to subclause 4.8.3 and Table 4.8.3-1. NOTE: Mobile originating CS call is established.	–	–	–	–
16	The SS transmits a SECURITY MODE COMMAND message for the PS domain. See Note 1.	<–	SECURITY MODE COMMAND	–	–
17	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
18	The SS transmits a ROUTING AREA UPDATE ACCEPT message.	<–	ROUTING AREA UPDATE ACCEPT	–	–
19	The UE transmits a ROUTING AREA UPDATE COMPLETE message.	–>	ROUTING AREA UPDATE COMPLETE	–	–
Note 1: A real network will initiate the security mode command procedure for the PS domain immediately after receiving the ROUTING AREA UPDATE REQUEST, but in this test procedure it was chosen to complete the procedure for CS domain first, in order to avoid the possibility of a security mode command procedure running in parallel with another RRC procedure.

Table 6.4.3.7.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a ROUTING AREA UPDATE REQUEST message.	–>	ROUTING AREA UPDATE REQUEST	–	–

6.4.3.7.3 CS fallback to UTRAN with redirection / MT call (PS bearer established)

Table 6.4.3.7.3-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1-19	Steps 1-19 of table 6.4.3.7.1-1. NOTE: Mobile terminating CS call is established and Routing Area Update procedure is performed			–	–
20	Check: Does the UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	–	P
21	SS transmits a RADIO BEARER SETUP message, using the UTRA reference radio bearer parameters and combination "UTRA PS RB + Speech" according to subclause 4.8.3 and Table 4.8.3-1. NOTE: Mobile originating packet switched session is established.	<–	RADIO BEARER SETUP	–	–
22	The UE transmits a RADIO BEARER SETUP COMPLETE message	–>	RADIO BEARER SETUP COMPLETE	–	–

6.4.3.7.4 CS fallback to UTRAN with redirection / MO call (PS bearer established)

Table 6.4.3.7.4-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1-19	Steps 1-19 of table 6.4.3.7.2-1. NOTE: Mobile originating CS call is set up and Routing Area Update procedure is performed	–	–	–	–
20	Check: Does the UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	–	P
21	SS transmits a RADIO BEARER SETUP message, using the UTRA reference radio bearer parameters and combination "UTRA PS RB + Speech" according to subclause 4.8.3 and Table 4.8.3-1. NOTE: Mobile originating packet switched session is established.	<–	RADIO BEARER SETUP	–	–
22	The UE transmits a RADIO BEARER SETUP COMPLETE message	–>	RADIO BEARER SETUP COMPLETE	–	–

6.4.3.7.5 CS fallback to UTRAN with Handover / MT call

Table 6.4.3.7.5-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message?	–>	HANDOVER TO UTRAN COMPLETE	–	P
–	EXCEPTION: In parallel to the events described in step 2a1 to 9 the steps specified in table 6.4.3.7.5-2 takes place.	–	–	–	–
–	Exception: Steps 2a1 to 2a10 and 2b1 to 2b9 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. Note: One sequence of steps 2a1 to 2a10 or 2b1 to 2b9 are executed	–	–	–	–
2a1	IF the UE does not determine the LAI of the new UTRAN cell, THEN Check: Does the UE transmit a LOCATION UPDATING REQUEST message?	–>	LOCATION UPDATING REQUEST	–	P
2a2	The SS transmits AUTHENTICATION REQUEST	<–	AUTHENTICATION REQUEST	–	–
2a3	The UE transmits AUTHENTICATION RESPONSE	–>	AUTHENTICATION RESPONSE	–	–
2a4	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
2a5	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2a6	The SS transmits a LOCATION UPDATING ACCEPT message.	<–	LOCATION UPDATING ACCEPT	–	–
2a7	The SS transmits a SECURITY MODE COMMAND message for the PS domain.	<–	SECURITY MODE COMMAND	–	–
2a8	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2a9	The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
2a10	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
	Exception: Steps 2b1 to 2b4 takes place if pc_UMI_ProcNeeded_DuringCSFB
2b1	The SS transmits a SECURITY MODE COMMAND message for the PS domain.	<–	SECURITY MODE COMMAND	–	–
2b2	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2b3	The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
2b4	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
2b5	Check: Does the UE transmit a PAGING RESPONSE?	–>	PAGING RESPONSE	–	P
2b6	The SS transmits AUTHENTICATION REQUEST	<–	AUTHENTICATION REQUEST	–	–
2b7	The UE transmits AUTHENTICATION RESPONSE	–>	AUTHENTICATION RESPONSE	–	–
2b8	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
2b9	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
3-9	Steps 11 to 17 of the generic test procedure in TS 34.108 subclause 7.2.3.1.3 are performed using the UTRA reference radio bearer parameters and combination "UTRA PS RB + Speech" according to subclause 4.8.3 and Table 4.8.3-1. NOTE: Mobile terminating CS call is established.	–	–	–	–
10	The SS transmits a ROUTING AREA UPDATE ACCEPT.	<–	ROUTING AREA UPDATE ACCEPT	–	–
11	The UE sends ROUTING AREA UPDATE COMPLETE.	–>	ROUTING AREA UPDATE COMPLETE	–	–

Table 6.4.3.7.5-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a ROUTING AREA UPDATE REQUEST message.	–>	ROUTING AREA UPDATE REQUEST	–	–

6.4.3.7.5.1 Specific message contents

Table 6.4.3.7.5.1-1: Void

Table 6.4.3.7.5.1-2: LOCATION UPDATING ACCEPT (step 2a6 of table 6.4.3.7.5-1)

Derivation Path: TS 36.508 Table 4.7B.2-5
Information Element	Value/remark	Comment	Condition
Mobile identity	Not present

6.4.3.7.6 CS fallback to UTRAN with Handover / MO call

Table 6.4.3.7.6-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message?	–>	HANDOVER TO UTRAN COMPLETE	–	P
–	EXCEPTION: In parallel to the events described in step 2a1 to 9 the steps specified in table 6.4.3.7.6-2 takes place.	–	–	–	–
–	Exception: Steps 2a1 to 2a12 and 2b1 to 2b9 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. Note: One sequence of steps 2a1 to 2a12 or 2b1 to 2b9 are executed	–	–	–	–
2a1	IF the UE does not determine the LAI of the new UTRAN cell, THEN Check: Does the UE transmit a LOCATION UPDATING REQUEST message?	–>	LOCATION UPDATING REQUEST	–	P
2a2	The SS transmits AUTHENTICATION REQUEST	<–	AUTHENTICATION REQUEST	–	–
2a3	The UE transmits AUTHENTICATION RESPONSE	–>	AUTHENTICATION RESPONSE	–	–
2a4	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
2a5	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2a6	The SS transmits a LOCATION UPDATING ACCEPT message.	<–	LOCATION UPDATING ACCEPT	–	–
2a7	Check: Does the UE transmit a CM SERVICE REQUEST?	–>	CM SERVICE REQUEST	–	P
2a8	The SS transmits a SECURITY MODE COMMAND message for the PS domain.	<–	SECURITY MODE COMMAND	–	–
2a9	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2a10	The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
2a11	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
2a12	The SS transmits a CM SERVICE ACCEPT message.	<–	CM SERVICE ACCEPT	–	–
	Exception: Steps 2b1 to 2b4 takes place if pc_UMI_ProcNeeded_DuringCSFB
2b1	The SS transmits a SECURITY MODE COMMAND message for the PS domain.	<–	SECURITY MODE COMMAND	–	–
2b2	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2b3	The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
2b4	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
2b5	Check: Does the UE transmit a CM SERVICE REQUEST?	–>	CM SERVICE REQUEST	–	P
2b6	The SS transmits AUTHENTICATION REQUEST	<–	AUTHENTICATION REQUEST	–	–
2b7	The UE transmits AUTHENTICATION RESPONSE	–>	AUTHENTICATION RESPONSE	–	–
2b8	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
2b9	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
3	The UE transmits a SETUP message.	–>	SETUP	–	–
4-9	Steps 11 to 16 of the generic test procedure in TS 34.108 subclause 7.2.3.2.3 are performed using the UTRA reference radio bearer parameters and combination "UTRA PS RB + Speech" according to subclause 4.8.3 and Table 4.8.3-1. NOTE: Mobile originating CS call is established.	–	–	–	–
10	The SS transmits a ROUTING AREA UPDATE ACCEPT.	<–	ROUTING AREA UPDATE ACCEPT	–	–
11	The UE sends ROUTING AREA UPDATE COMPLETE.	–>	ROUTING AREA UPDATE COMPLETE	–	–

Table 6.4.3.7.6-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a ROUTING AREA UPDATE REQUEST message.	–>	ROUTING AREA UPDATE REQUEST	–	–

6.4.3.7.6.1 Specific message contents

None.

Table 6.4.3.7.6.1-1: LOCATION UPDATING ACCEPT (step 2a6 of table 6.4.3.7.6-1)

Derivation Path: TS 36.508 Table 4.7B.2-5
Information Element	Value/remark	Comment	Condition
Mobile identity	Not present

6.4.3.7.7 CS fallback to UTRAN with Handover / emergency call

Table 6.4.3.7.7-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message?	–>	HANDOVER TO UTRAN COMPLETE	–	P
–	EXCEPTION: In parallel to the events described in step 2a1 to 9 the steps specified in table 6.4.3.7.7-2 takes place.	–	–	–	–
–	Exception: Steps 2a1 to 2a12 and 2b1 to 2b9 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. Note: One sequence of steps 2a1 to 2a12 or 2b1 to 2b9 are executed	–	–	–	–
2a1	IF the UE does not determine the LAI of the new UTRAN cell, THEN Check: Does the UE transmit a LOCATION UPDATING REQUEST message?	–>	LOCATION UPDATING REQUEST	–	P
2a2	The SS transmits AUTHENTICATION REQUEST	<–	AUTHENTICATION REQUEST	–	–
2a3	The UE transmits AUTHENTICATION RESPONSE	–>	AUTHENTICATION RESPONSE	–	–
2a4	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
2a5	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2a6	The SS transmits a LOCATION UPDATING ACCEPT message.	<–	LOCATION UPDATING ACCEPT	–	–
2a7	Check: Does the UE transmit a CM SERVICE REQUEST?	–>	CM SERVICE REQUEST	–	P
2a8	The SS transmits a SECURITY MODE COMMAND message for the PS domain.	<–	SECURITY MODE COMMAND	–	–
2a9	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2a10	The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
2a11	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
2a12	The SS transmits a CM SERVICE ACCEPT message.	<–	CM SERVICE ACCEPT	–	–
	Exception: Steps 2b1 to 2b4 takes place if pc_UMI_ProcNeeded_DuringCSFB
2b1	The SS transmits a SECURITY MODE COMMAND message for the PS domain.	<–	SECURITY MODE COMMAND	–	–
2b2	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2b3	The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
2b4	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
2b5	Check: Does the UE transmit a CM SERVICE REQUEST?	–>	CM SERVICE REQUEST	–	P
2b6	The SS transmits AUTHENTICATION REQUEST	<–	AUTHENTICATION REQUEST	–	–
2b7	The UE transmits AUTHENTICATION RESPONSE	–>	AUTHENTICATION RESPONSE	–	–
2b8	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
2b9	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
3	The UE transmits an EMERGENCY SETUP message.	–>	EMERGENCY SETUP	–	–
4-9	Steps 12 to 17 of the test procedure in TS 34.123-1 [7] subclause 13.2.1.1 are performed using the UTRA reference radio bearer parameters and combination "UTRA PS RB + Speech" according to subclause 4.8.3 and Table 4.8.3-1. NOTE: Emergency call is established..	–	–	–	–
10	The SS transmits a ROUTING AREA UPDATE ACCEPT.	<–	ROUTING AREA UPDATE ACCEPT	–	–
11	The UE sends ROUTING AREA UPDATE COMPLETE.	–>	ROUTING AREA UPDATE COMPLETE	–	–

Table 6.4.3.7.7-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a ROUTING AREA UPDATE REQUEST message.	–>	ROUTING AREA UPDATE REQUEST	–	–

6.4.3.7.7.1 Specific message contents

UTRAN MOBILITY INFORMATION (step 2a10 & 2b1 of table 6.4.3.7.7-1): same as Table 6.4.3.7.5.1-1

Table 6.4.3.7.7.1-1: LOCATION UPDATING ACCEPT (step 2a6 of table 6.4.3.7.7-1)

Derivation Path: TS 36.508 Table 4.7B.2-5
Information Element	Value/remark	Comment	Condition
Mobile identity	Not present

6.4.3.8 CS fallback to GERAN procedures (LAI of GERAN cell same as the LAI received in combined Attach procedure in EUTRA cell)

All procedures specified in this clause are referred to the GERAN target cell where the UE has been redirected or handed over from the EUTRA cell after a CS call requested. The default message contents are found in TS 34.108 [5], clause 9.

The procedures in 6.4.3.8.1 – 6.4.3.8.4 are applied if the UE supports (EUTRA) RRC connection release with redirection or Cell Change order and Multi Cell System Information to GERAN.

6.4.3.8.1 CS fallback to GERAN with redirection or CCO / MT call (DTM not supported)

Table 6.4.3.8.1-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a CHANNEL REQUEST message.	–>	CHANNEL REQUEST	–	–
2	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
3	Void	–	–	–	–
–	EXCEPTION: In parallel to the events described in step 4 to 19 the steps specified in table 6.4.3.8.1-2 takes place	–	–	–	–
4	Check: Does the UE transmit a PAGING RESPONSE message?	–>	PAGING RESPONSE	–	P
4A	The UE transmits a Classmark Change message	–>	CLASSMARK CHANGE	–	–
–	EXCEPTION: Step 4B describes behaviour that depends on the UE capability.	–	–	–	–
4B	IF pc_UTRA then the UE transmits a Utran Classmark message	–>	UTRAN CLASSMARK CHANGE	–	–
5-19	Steps 5 to 19 of the generic test procedure in TS 51.010-1 sub clause 10.3.3 are performed NOTE: Mobile terminating CS call is established.	–	–	–	–
20	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
21	The UE transmits RELEASE..	–>	RELEASE	–	–
22	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
23	The SS transmits CHANNEL RELEASE, with GPRS Resumption Field set to 1	<–	CHANNEL RELEASE	–	–
24-34	Steps 1 to 11 of the generic test procedure in sub clause 6.4.2.9 are performed.	–	–	–	–

Table 6.4.3.8.1-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a GPRS SUSPENSION REQUEST message.	–>	GPRS SUSPENSION REQUEST	–	–

6.4.3.8.2 CS fallback to GERAN with redirection or CCO / MO call (DTM not supported)

Table 6.4.3.8.2-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a CHANNEL REQUEST message.	–>	CHANNEL REQUEST	–	–
2	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
3	Void	–	–	–	–
–	EXCEPTION: In parallel to the events described in step 4 to 17 the steps specified in table 6.4.3.8.2-2 takes place	–	–	–	–
4	Check: Does the UE transmit a CM SERVICE REQUEST message?	–>	CM SERVICE REQUEST	–	P
4A	The UE transmits a Classmark Change message	–>	CLASSMARK CHANGE	–	–
–	EXCEPTION: Step 4B describes behaviour that depends on the UE capability.	–	–	–	–
4B	IF pc_UTRA then the UE transmits a Utran Classmark message	–>	UTRAN CLASSMARK CHANGE	–	–
5-17	Steps 5 to 17 of the generic test procedure in TS 51.010-1 sub clause 10.2.3 are performed NOTE: Mobile originating CS call is established.	–	–	–	–
18	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
19	The UE transmits RELEASE..	–>	RELEASE	–	–
20	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
21	The SS transmits CHANNEL RELEASE, with GPRS Resumption Field set to 1	<–	CHANNEL RELEASE	–	–
22-32	Steps 1 to 11 of the generic test procedure in sub clause 6.4.2.9 are performed.	–	–	–	–

Table 6.4.3.8.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a GPRS SUSPENSION REQUEST message.	–>	GPRS SUSPENSION REQUEST	–	–

6.4.3.8.3 CS fallback to GERAN with PS Handover / MT call (EDTM not supported)

Same as test procedure sequence in 36.523-1 [18] clause 13.1.11.3.2 from steps 11 to end.

6.4.3.8.4 CS fallback to GERAN with PS Handover / MO call (EDTM not supported)

Same as test procedure sequence in 36.523-1 [18] clause 13.1.12.3.2 from steps 4 to end.

6.4.3.8.5 CS fallback to GERAN with PS Handover / MT call (EDTM supported)

Same as test procedure sequence in 36.523-1 [18] clause 13.1.13.3.2 from steps 7 to end.

6.4.3.9 SRVCC Handover to UTRA

The procedure specified in this clause are referred to the UTRA target cell where the UE has been SRVCC handed over from the EUTRA cell. The default message contents are found in TS 34.108 [5], clause 9.

Table 6.4.3.9-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message?	–>	HANDOVER TO UTRAN COMPLETE	–	P
–	EXCEPTION: In parallel to the events described in step 2 to 7 the steps specified in table 6.4.3.9-2 takes place.	–	–	–	–
2	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
3	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
4	The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
5	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
6	The SS transmits a TMSI REALLOCATION COMMAND message.	<–	TMSI REALLOCATION COMMAND	–	–
7	The UE transmits a TMSI REALLOCATION COMPLETE message.	–>	TMSI REALLOCATION COMPLETE	–	–
8	The SS transmits a ROUTING AREA UPDATE ACCEPT.	<–	ROUTING AREA UPDATE ACCEPT	–	–
9	The UE sends ROUTING AREA UPDATE COMPLETE.	–>	ROUTING AREA UPDATE COMPLETE	–	–

Table 6.4.3.9-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a ROUTING AREA UPDATE REQUEST message.	–>	ROUTING AREA UPDATE REQUEST	–	–

6.4.3.9.1 Specific message contents

Table 6.4.3.9.1-1: SECURITY MODE COMMAND (step 2, Table 8.4.1.2.3.2-1)

Derivation Path: 34.108 clause 9.1.1 (SECURITY MODE COMMAND message)
Information Element	Condition	Value/remark
Ciphering mode info		Not Present

6.4.3.10 Offload to WLAN

The procedure specified in this clause is referred to the WLAN target AP where the UE has been offloaded from the EUTRA cell.

Table 6.4.3.10-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE associates with the WLAN AP and obtains the local IP address if it has not already done. Note 1	–	–	–	–
–	EXCEPTION: Step 2 is optional, and is executed if initiated by UE	–	–	–	–
2	UE performs a dynamic selection of ePDG using DNS query	–	–	–	–
3	UE initiates Authentication and Authorization (EAP-AKA) using CHAP as defined in 33.402 [55] clause 6.5.3	–	–	–	–
4-9	Check: The UE establishes IPsec tunnel using the IKEv2 protocol as defined in 3GPP TS 33.402 [55] clause 8.2.2, Figure 8.2.2-1; Procedure as defined in 23.402 [41] clause 8.2.3 steps 4-9	–	–	–	P
	Exception: Steps 10a1 to 10a3 takes place if UE is in RRC Connected state. Note 2			–	–
10a1-10a3	The generic test procedure in TS 36.508 subclause 4.5A.15.3 is executed.	–	–	–	P
–	EXCEPTION: Steps 11a1 to 11a2b1 describes a transaction that depends on offload of IMS PDN.
11a1	IF IMS PDN is offloaded SS starts timer Timer_1 = 10 s (Note 3)
–	EXCEPTION: Steps 11a2a1 to 11a2a2 describe a transaction that depends on offload of IMS PDN and UE implementation
11a2a1-11a2a2	IF initiated by the UE, Re-Registration procedure according to TS 34.229-1 [43] sub clause C.XX takes place on WLAN AP.
11a2b1	The SS waits for Timer_1 expiry
Note 1: If the UE has not already associated with WLAN AP it may take long time (up to 60 seconds) to associate with WLAN AP as it may need to scan, authenticate, obtain IP address etc. Note 2: If UE is in RRC Idle state then as per 24.301[28] clause 6.4.2.2, the offloaded PDN is implicitly released. Note 3: A guarding time of [10] sec is suggested within which the procedure is expected to start. If the timer expires then the test procedure, from which the Procedure for IMS Re-Registration is called, shall advance to the next specified step.

6.4.3.10.1 Specific message contents

None

6.4.3.11 Offload from WLAN

The procedure specified in this clause is referred to the EUTRA cell where the UE has been previously offloaded from the EUTRA cell and now the Offload from WLAN AP back to EUTRA cell happens.

Table 6.4.3.11-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
	Exception: Steps 1 to 9 are executed if the UE is in RRC Idle state in EUTRA cell.			–	–
1	Check: Does UE transmit an RRCConnectionRequest message with establishmentCause set to ‘mo-Data’ followed by a SERVICE REQUEST message?	–>	SERVICE REQUEST	–
2-9	The SS establishes SRB2 and DRB associated with non offloaded default EPS bearer context by executing steps 3-10a7 in the generic test procedure in TS 36.508 subclause 4.5.3.3	–	–	–	–
10	Check: Does the UE establish additional PDN connection for offloaded PDN by executing the generic test procedure in TS 36.508 subclause 4.5A.16.3.	–	–	–	P
11	Network initiated IPsec tunnel disconnection procedures defined by the IKEv2 protocol in IETF RFC 5996 [57] is executed on WLAN AP	–	–	–	–

6.4.3.11.1 Specific message contents

None

6.4.3.12 Check UE does not offload to WLAN

The procedure specified in this clause is referred to the WLANAP.

Table 6.4.3.12-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	Exception: In parallel to step 1 parallel behaviour in table 6.4.3.12-2 may be optionally executed.	–	–	–	–
1	Check: IF UE initiates Authentication and Authorization (EAP-AKA) using CHAP as defined in 33.402 [55] clause 6.5.3 in the next 60 seconds	–	–	–	F

Table 6.4.3.12-2: Parallel Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE associates with the WLAN AP and obtains the local IP address if it has not already done	–	–	–	–

6.4.3.12.1 Specific message contents

None

6.4.3.13 Check UE does not Offload to E-UTRAN

The procedure specified in this clause are referred to the EUTRA cell.

Table 6.4.3.13-1: Test procedure sequence

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
	Exception: Steps 1a to 1b describe behaviour that depends on the state; the "lower case letter" identifies a step sequence that take place. IF UE is in ‘Idle’ state step 1a takes and if in ‘Connected’ state step 1b takes			–	–
1a	Check: Does UE transmit an RRCConnectionRequest in the next 15 seconds	–>	RRCConnectionRequest	–	F
1b	Check: Does the UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN. In the next 15 seconds	–>	RRC: ULInformationTransfer NAS: PDN CONNECTIVITY REQUEST	–	F

6.4.3.14 Procedure for UE initiated detach at non-switch-off

The purpose of this procedure is to allow a UE to perform UE initiated detaching.

Table 6.4.3.14-1: Procedure for optional UE initiated detaching

Step	Procedure	Message Sequence
		U – S	Message
1	The UE transmits a DETACH REQUEST message with the Detach type IE indicating “EPS detach” to regain normal service.	–>	DETACH REQUEST	–	–
2	The SS responds the DETACH ACCEPT message.	<–	DETACH ACCEPT	–	–

6.4.3.13.1 Specific message contents

None

6.4.3A Test case postambles

6.4.3A.1 Introduction

In order to make test cases perfectly reproducible, the UE under test is switched off after the test procedure sequence of a test case is complete. In order to make it possible to run a number of test cases without any manual operation, it is important that the SS can properly handle any possible signalling from the UE between the end of the test procedure sequence and until the UE is off.

After the last verdict of a test procedure sequence is assigned, it is necessary to:

– terminate any ongoing signalling procedure,

– switch off the UE.

Usually, this can be performed by completing necessary TAU/LAU/RAU procedures, completing any ongoing voice call (CS or IMS), and switching off the UE with a detach procedure.

6.4.3A.2 Reference end states

Test procedures in TS 36.523-1 may only partially terminate ongoing signalling procedures, provided they indicate a reference end state at the end of the test procedure sequence, so that a matching procedure in TS 36.523-3 can be executed to switch off the UE.

Reference end states definitions include the necessary pieces of information to predict UE behaviour during the postambles.

If any extra information was stored in the UE or the USIM due to the test procedure sequence, it should be removed explicitly by the test procedure sequence, before the UE can be left in a reference end state.

Table 6.4.3A.2-1: Reference end states

Name	Description	Optional information
E-UTRA idle (E1)	The UE: – is camped on an E-UTRA cell, and RRC idle and – registered for EPS services and EPS update status is "updated" and – is registered for non-EPS services and update status is updated (if CS fallback or SMS over SGs is supported) and – has one or more default EPS bearer context are active, zero or more dedicated EPS bearer contexts are active.	The test case may indicate that the UE is not registered for non-EPS services, though the UE supports CS fallback or SMS over SGs.
E-UTRA connected (E2)	Same as E-UTRA idle, except that: – the UE is RRC connected and – DRBs for all active EPS bearer contexts are established.	Same as for E-UTRA idle.
E-UTRA connected, T3440 started (E2_T3440)	Same as E-UTRA idle, except that: – the UE is RRC connected and – Timer T3440 is started in UE.	Same as for E-UTRA idle
E-UTRA test mode (E3)	Same as E-UTRA connected and – test mode is active and – test loop is closed.	Same as for E-UTRA idle
E-UTRA deregistered (E4)	The UE is: – camped on an E-UTRA cell, and idle and – not registered of EPS services and – not registered for non-EPS services.
E-UTRA manual selection (E5)	Same as E-UTRA idle, except that: – the UE is in manual PLMN selection mode	Same as for E-UTRA idle
UTRA idle (U1)	The UE is: – camped on a UTRA cell, RRC idle and – IMSI attached and update status is "updated" (if the UE supports CS domain) and – GPRS attached, GPRS update state is "updated", and zero or one or several PDP context(s) with interactive or background QoS are active.	The test case may indicate that the UE is not IMSI attached though the UE supports CS domain
UTRA connected (U2)	Same as UTRA idle, except that: – the UE is in CELL_DCH state and – a RAB associated with the active PDP context is established.	The test case may indicate that the UE is not IMSI attached though the UE supports CS domain.
UTRA handover (U3)	The UE: – was E-UTRA connected and – has completed a handover to UMTS and – hasn’t yet sent or received any NAS signalling on the target UTRAN cell.	Same as for UTRA connected
UTRA CS fallback (U4)	The UE: – was E-UTRA idle or E-UTRA connected and – has transmitted an EXTENDED SERVICE REQUEST message due to MO or MT CS fallback call and – either the UE has completed a handover to UMTS or the UE has been redirected to UMTS and has established the RRC connection to a UTRA cell, and the target UTRA cell has activated security and RABs for all previously active EPS bearer contexts were established and – the UE hasn’t yet sent or received any NAS signalling on the target UTRAN cell
UTRA CS call (U5)	The UE was in UTRAN CS fallback and the UE has completed LAU/RAU procedure if necessary and has established a CS call or the UE was in E-UTRAN connected and the UE has completed LAU/RAU procedure if necessary and has performed a handover to UTRAN with SRVCC.
UTRA deregistered (U6)	The UE is: – camped on a UTRA cell, and idle and – not registered GPRS/non-GPRS services
GERAN idle (G1)	The UE: – is camped on an GERAN cell, in idle mode and GPRS idle state and – is registered for PS services and GPRS update status is "updated" and zero or one or several PDP context(s) with interactive or background QoS are active. – is IMSI attached (if CS domain is supported)
GERAN PS handover (G2)	The UE: – was E-UTRA connected and – has performed a PS handover procedure to a GERAN cell and – hasn’t yet sent or received any NAS signalling on the target GERAN cell.
GERAN CS fallback (G3)	The UE: – was E-UTRA idle or E-UTRA connected and – has transmitted an EXTENDED SERVICE REQUEST message due to MO or MT CS fallback call and – either the UE has completed a PS handover to GERAN or a CCO to GERAN or the UE has been redirected to GERAN and has entered dedicated mode, and if DTM is supported, – the UE hasn’t yet sent or received any NAS signalling on the target GERAN cell
GERAN CS call (G4)	The UE was in GERAN CS fallback and the UE has established a CS call or the UE was in E-UTRAN connected and has performed a handover to GERAN with SRVCC.
GERAN deregistered (G5)	The UE is: – camped on a GERAN cell, and idle and – not registered GPRS/non-GPRS services
1xRTT state 1 (1×1)	FFS
…	…
HRPD state 1 (H1)	FFS
…	…