13.1.9 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with CCO without NACC / 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.9.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state having requested CS call setup }

ensure that {
when { UE receives a MobilityFromEUTRACommand message including a cs-FallbackIndicator set to ‘true‘, a targetRAT-Type set to ‘geran‘ and purpose set to ‘cellChangeOrder‘ and no ‘networkControlOrder’ }

then { UE acquires networkControlOrder and establishes the connection to the target cell indicated in the CellChangeOrder }

}

13.1.9.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 23.272, clauses 6.4 and 6.3, and, TS 36.331, clause 5.4.3.3, 5.3.9.2, 5.3.12 and B.1.

[TS 23.272, clause 6.4]

Mobile Originating call in Idle Mode procedure is specified by reusing the Mobile Originating Call in Active mode procedure with Extended Service Request (CS Fallback Indicator) to the MME. The UE is transited to ECM-CONNECTED mode by following the applicable procedures specified in TS 23.401 [2].

[TS 23.272, clause 6.3]

Figure 6.3-1: CS Call Request in E-UTRAN, Call in GERAN/UTRAN without PS HO

1a. The UE sends an Extended Service Request (CS Fallback Indicator) to the MME. Extended Service Request message is encapsulated in RRC and S1‑AP messages. CS Fallback Indicator indicates MME to perform CS Fallback. The UE only transmits this request if it is attached to CS domain (with a combined EPS/IMSI Attach) and can not initiate an IMS voice session (because e.g. the UE is not IMS registered or IMS voice services are not supported by the serving IP‑CAN, home PLMN or UE).

…

2. The eNodeB may optionally solicit a measurement report from the UE to determine the target GERAN cell to which the redirection procedure will be performed.

3a. If the UE and network support inter-RAT cell change order to GERAN and the target cell is GERAN: The eNodeB triggers an inter‑RAT cell change order (optionally with NACC) to a GERAN neighbour cell by sending an RRC message to the UE. The inter-RAT cell change order may contain a CS Fallback Indicator which indicates to UE that the cell change order is triggered due to a CS fallback request. If the inter-RAT cell change order contains a CS Fallback Indicator and the UE fails to establish connection to the target RAT, then the UE considers that CS fallback has failed. Service Request procedure is considered to be successfully completed when cell change order procedure is completed successfully.

…

NOTE 2: Service Request procedure supervision timer shall be sufficiently long considering the optional measurement reporting at step 2.

…

6. The UE moves to the new cell in GERAN/UTRAN and establishes a radio signalling connection.

…

9. The UE continues with the MO call setup procedure. An ICS UE (as defined in TS 23.292 [25]) shall not use Gm (TS 23.292 [25]) procedures to establish the call.

NOTE 3: For an ICS user, in order to receive a consistent service experience the ICS UE needs to add ICS Service Control Signalling Path once the call is established, as described in TS 23.292 [25].

…

If the UE remains on UTRAN/GERAN after the CS voice call is terminated the UE performs normal mobility management procedures as defined in TS 23.060 [3] and TS 24.008 [21], i.e. if the UE is not registered in the current RA/LA, the UE performs combined RA/LA update procedure when the target system operates in NMO I, or separate LA update and RA update procedures when the target system operates in NMO II/III. Also for NMO I if the UE performed only RA update due to the CS call the UE performs a combined RA/LA update (see TS 23.060 [3], clause 6.3.1) which creates the Gs association.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover‘:

…

1> else if the MobilityFromEUTRACommand message includes the purpose set to ‘cellChangeOrder‘:

2> start timer T304 with the timer value set to t304, as included in the MobilityFromEUTRACommand message;

2> if the targetRAT-Type is set to ‘geran‘:

3> if networkControlOrder is included in the MobilityFromEUTRACommand message:

4> apply the value as specified in TS 44.060 [36];

3> else:

4> acquire networkControlOrder and apply the value as specified in TS 44.060 [36];

3> use the contents of systemInformation, if provided, as the system information to begin access on the target GERAN cell;

NOTE 2: The systemInformation is constructed in the same way as in 2G to 2G NACC, i.e. the PSI messages are encoded as such, whereas the SI messages exclude 2 octets of headers, see TS 44.060[36].

2> establish the connection to the target cell indicated in the CellChangeOrder;

NOTE 3: The criteria for success or failure of the cell change order to GERAN are specified in TS 44.060[36].

[TS 36.331, clause 5.3.9.2]

Upon successfully completing the handover or the cell change order, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

1> stop timer T304, if running;

[TS 36.331, clause 5.3.12]

Upon leaving RRC_CONNECTED, the UE shall:

1> reset MAC;

1> stop all timers that are running except T320;

1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established RBs;

1> indicate the release of the RRC connection to upper layers together with the release cause;

[TS 36.331, clause B.1]

This annex contains the definitions of the bits in field featureGroupIndicators.

In this release of the protocol, the UE shall include the field featureGroupIndicators in the IE UE-EUTRA-Capability. All the functionalities defined within the field featureGroupIndicators defined in Table B.1-1 are mandatory for the UE, if the related capability (frequency band, RAT or SR-VCC) is also supported. For a specific indicator, if all functionalities for a feature group listed in Table B.1-1 have been implemented and tested, the UE shall set the indicator as one (1), else (i.e. if any one of the functionalities in a feature group listed in Table B.1-1, which have not been implemented or tested), the UE shall set the indicator as zero (0).

…

Table B.1-1: Definitions of feature group indicators

Index of indicator (bit number)

Definition

(description of the supported functionality, if indicator set to one)

Notes

…

10

– EUTRA RRC_CONNECTED to GERAN (Packet_) Idle by Cell Change Order

– EUTRA RRC_CONNECTED to GERAN (Packet_) Idle by Cell Change Order with NACC (Network Assisted Cell Change)

…

13.1.9.3 Test description

13.1.9.3.1 Pre-test conditions

System Simulator:

– Cell 1 serving cell

– Cell 24 suitable neighbour cell

– The parameters settings and power levels for Cell 1 and Cell 24 are selected according to [18], [5] so that camping on Cell 1 is guaranteed and no cell re-selection to Cell 24 can take place (GERAN priority is lower than serving and S Cell 1 > Thresh Cell 1,low).

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

UE:

None.

Preamble:

– The UE is in state Registered, Idle Mode (state 2) on Cell 1 according to [18].

13.1.9.3.2 Test procedure sequence

Table 13.1.9.3.2-0: instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 24

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

-115

–

The power levels are such that reselection back to cell 1 should not occur

Table 13.1.9.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause the UE to originate CS call. (see Note 1)

–

–

–

–

2

Generic test procedure ‘UE triggered CS call’ as described in 36.508, clause 6.4.3.5 is performed.

–

–

–

3

The SS transmits a SecurityModeCommand message on Cell 1.

<–

SecurityModeCommand

–

–

4

The UE transmits a SecurityModeComplete message on Cell 1.

–>

SecurityModeComplete

–

–

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1.

<–

RRCConnectionReconfiguration

–

–

6

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

–

–

7

The SS transmits a MobilityFromEUTRACommand message on Cell 1 including a cs-FallbackIndicator set to ‘true‘, a targetRAT-Type set to ‘geran‘, purpose set to ‘cellChangeOrder‘ and no ‘networkControlOrder’

<–

MobilityFromEUTRACommand

–

–

8

Void

–

–

–

–

8A

The UE transmits a CHANNEL REQUEST message on Cell24.

–>

CHANNEL REQUEST

–

–

8B

The SS changes cell 1 power level according to the row “T1”

9-39

Check: Does the steps 2 to 32 of the generic test procedure described in TS36.508 subclause 6.4.3.8.2 are performed on Cell24?

–

–

1

–

–

At the end of this test procedure sequence, the UE is in end state GERAN idle (G1) according to TS 36.508.

–

–

–

–

Note 1: See generic procedure in 36.508 clause 6.4.3.5 for the trigger.

13.1.9.3.3 Specific message contents

Table 13.1.4.3.3-1: RRCConnectionReconfiguration (step 5, Table 13.1.9.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(1, 0)

Table 13.1.9.3.3-2: MobilityFromEUTRACommand (step 7, Table 13.1.9.3.2-1)

Derivation Path: 36.508, Table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

cs-FallbackIndicator

true

purpose CHOICE{

cellChangeOrder SEQUENCE {

t304

ms8000

targetRAT-Type CHOICE{

geran SEQUENCE {

physCellId

TS 36.508, 6.3.1.4

carrierFreq

TS 36.508, 6.3.1.4

networkControlOrder

Not present

systemInformation

Not present

}

}

}

}

}

}

}

}

Table 13.1.9.3.3-8: Void

Table 13.1.9.3.3-9: ATTACH ACCEPT (Preamble)

Derivation Path: 36.508 Table 4.7.2-1

Information Element

Value/remark

Comment

Condition

EPS network feature support

Not present