13.1.2 Call setup from E-UTRAN RRC_IDLE / CS fallback to UTRAN with redirection / MO call

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

13.1.2.1 Test Purpose (TP)

(1)

with { the UE is in E-UTRA RRC_IDLE state }

ensure that {

when { the user initiates a CS voice call }

then { the UE transmits an EXTENDED SERVICE REQUEST message with Service Type IE set to "mobile originating CS fallback or 1xCS fallback" }

}

(2)

with { the UE transmitted an EXTENDED SERVICE REQUEST message with Service Type IE set to "mobile originating CS fallback or 1xCS fallback" }

ensure that {

when { the UE receives an RRCConnectionRelease message with redirection to a UMTS cell which belongs to the LA allocated to the UE during the previous registration procedure in E-UTRAN }

then { UE establishes a connection to the designated UMTS cell, performs a RA update procedure and establishes a CS call }

}

13.1.2.2 Conformance requirements

The conformance requirements covered in the present TC are specified in: TS 24.301 clauses 5.6.1.1 and TS 24.008, clause 4.5.1.1.

[TS 24.301, clause 5.6.1.1]

…

The UE shall invoke the service request procedure when:

…

d) the UE in EMM-IDLE or EMM-CONNECTED mode is configured to use CS fallback and has a mobile originating CS fallback request from the upper layer;

[TS 24.008, clause 4.5.1.1]

…

In order to establish an MM connection, the mobile station proceeds as follows:

…

d) When the MS is IMSI attached for CS services via EMM combined procedures, as described in 3GPP TS 24.301 [120], and the MS is camping on an E-UTRAN cell, the MM sublayer requests EMM to initiate a service request procedure for CS fallback. The MM connection establishment is delayed until the MS changes to a GERAN or UTRAN cell.

If the MS enters a GERAN or UTRAN cell, then the MS shall initiate the MM connection establishment and send a CM SERVICE REQUEST message. If the MS determines that it is in a different location area than the stored location area, the MS shall first initiate a normal location updating procedure or a combined routing area update procedure, depending on Network Mode of Operation. If the location area of the current cell is not available, the MS may initiate a normal location updating procedure directly. The MM connection establishment is delayed until successful completion of the normal location updating or combined routing area update procedure. The MS may perform location area updating procedure instead of combined routing area update procedure in NMO I. If the normal location updating procedure is initiated, the MS shall indicate the "follow-on request pending" in the LOCATION UPDATING REQUEST message.

13.1.2.3 Test description

13.1.2.3.1 Pre-test conditions

System Simulator:

– cell 1 (E-UTRA) and cell 5 (UTRA);

– power levels are constant and as defined in table 13.1.2.3.1-1;

– cell 5 is in NMO 1.

– System information combination 4 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

Table 13.1.2.3.1-1: Cell power levels

	Parameter name	Unit	Cell 1	Cell 5
T0	RS EPRE	dBm/15kHz	-75
	CPICH_Ec	dBm/3.84 MHz		-70
	P-CCPCH	dBm/1.28 MHz		-72
T1	RS EPRE	dBm/15kHz	Non-suitable “Off”
	CPICH_Ec	dBm/3.84 MHz		-70
	P-CCPCH	dBm/1.28 MHz		-72

UE:

None.

Preamble:

– the UE is in state Registered, Idle Mode (state 2) according to TS 36.508 [18].

13.1.2.3.2 Test procedure sequence

Table 13.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	A CS call is initiated (see Note 1)
2	The UE transmits an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
3	The SS transmits an RRCConnectionSetup message	<–	RRCConnectionSetup	–	–
4	Check: Does the UE transmit an EXTENDED SERVICE REQUEST message?	–>	EXTENDED SERVICE REQUEST	1	P
5	Void			–	–
6	Void			–	–
7	Void			–	–
8	The SS transmits an RRCConnectionRelease message indicating redirection to cell 5	<–	RRCConnectionRelease	–	–
9	The UE transmits an RRC CONNECTION REQUEST with an establishment cause indicating ‘ Originating Conversational Call ‘.	–>	RRC CONNECTION REQUEST	–	–
9A	SS adjusts cell levels according to row T1 of table 13.1.2.3.1-1.
10-27	Check: Does steps 2 to 19 of the generic test procedure in TS 36.508 subclause 6.4.3.7.2 are performed?	–	–	2	–
–	The UE is in end state UTRA CS call (U5).	–	–	–	–
Note 1: The request is assumed to be triggered by AT command D. Note 2: Void

Table 13.1.2.3.2-2: Void

13.1.2.3.3 Specific message contents

Table 13.1.2.3.3-1: SystemInformationBlockType6 for cell 1 (preamble and all steps, table 13.1.2.3.2-1)

Derivation path: 36.508 table 4.4.3.3-5
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType6 ::= SEQUENCE {
carrierFreqListUTRA-FDD SEQUENCE (SIZE (1..maxUTRA-FDD-Carrier)) OF SEQUENCE {			FDD
carrierFreq[n]	Same as cell 5
cellReselectionPriority[n]	3	Lower than cell 1 priority (priority = 4)
}
carrierFreqListUTRA-TDD SEQUENCE (SIZE (1..maxUTRA-TDD-Carrier)) OF SEQUENCE {	1 entry		TDD
carrierFreq[n]	Same as cell 5
cellReselectionPriority[n]	3	Lower than cell 1 priority (priority = 4)
}
}

Table 13.1.2.3.3-2: EXTENDED SERVICE REQUEST (step 4, table 13.1.2.3.2-1)

Derivation path: 36.508 table 4.7.2-14A
Information Element	Value/Remark	Comment	Condition
Service type	0000 ‘mobile originating CS fallback or 1xCS fallback’
CSFB response	Not present
EPS bearer context status	Not present or any allowed value

Table 13.1.2.3.3-3: RRCConnectionRelease (step 8, table 13.1.2.3.2-1)

Derivation path: 36.508 table 4.6.1-15
Information Element	Value/Remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
utra-FDD	Downlink UARFCN of cell 5		FDD
utra-TDD	Downlink UARFCN of cell 5		TDD
}
}
}

Table 13.1.2.3.3-4: CM SERVICE REQUEST (step 12, table 13.1.2.3.2-1)

Derivation path: 24.008 table 9.2.11
Information Element	Value/Remark	Comment	Condition
CM service type	0001 ‘Mobile originating call establishment or packet mode connection establishment’
Ciphering key sequence number	Any allowed value
Mobile station classmark	Any allowed value
Mobile identity
TMSI	TMSI-1
Priority	Not present or any allowed value

Table 13.1.2.3.3-5: Void

Table 13.1.2.3.3-6: ATTACH ACCEPT (Preamble)

Derivation Path: 36.508 Table 4.7.2-1
Information Element		Value/remark	Comment	Condition
EPS network feature support		Not present