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

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

13.1.2a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionRelease message with redirection to UTRAN including System Information }

then { UE uses the received System Information and UE sends an RRC CONNECTION REQUEST message in the cell which belongs to the frequency indicated in RRCConnectionRelease message }

}

13.1.2a.2 Conformance requirements

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

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

[TS 25.331, clause 8.1.1.8]

If the UE was redirected from a different RAT:

1> if the UE receives the System Information Container message corresponding to a cell, on which UE is camped after a cell selection procedure triggered by the redirection procedure:

2> the UE may store the System Information Container message into variable SYSTEM INFORMATION CONTAINER and use the stored master information block, scheduling blocks and system information blocks in the variable SYSTEM_INFORMATION_CONTAINER until the variable is cleared, and act as if this system information was scheduled on BCCH of this cell.

13.1.2a.3 Test description

13.1.2a.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.2a.3.1-1;

– Cell 5 is in NMO I.

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

Table 13.1.2a.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) on Cell 1 according to TS 36.508 [18].

13.1.2a.3.2 Test procedure sequence

Table 13.1.2a.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 on Cell 1.

–>

RRCConnectionRequest

3

The SS transmits an RRCConnectionSetup message on Cell 1.

<–

RRCConnectionSetup

4

The UE transmits an EXTENDED SERVICE REQUEST message on Cell 1.

–>

EXTENDED SERVICE REQUEST

5

The SS transmits an RRCConnectionRelease message indicating redirection to cell 5 on Cell 1.

<–

RRCConnectionRelease

6

Check: Does the UE transmit an RRC CONNECTION REQUEST message with an establishment cause indicating ‘ Originating Conversational Call ‘ on Cell 5?

–>

RRC CONNECTION REQUEST

1

P

6A

SS adjusts cell levels according to row T1 of table 13.1.2a.3.1-1.

7

The SS transmits an RRC CONNECTION SETUP message on Cell 5.

<–

RRC CONNECTION SETUP

8

The UE transmits an RRC CONNECTION SETUP COMPLETE message on Cell 5.

–>

RRC CONNECTION SETUP COMPLETE

EXCEPTION: In parallel to step 9, the parallel behaviour in Table 13.1.2a.3.2-2 is taking place.

9

The UE transmits a CM SERVICE REQUEST message on Cell 5.

–>

CM SERVICE REQUEST

10

The SS transmits a SECURITY MODE COMMAND message for the PS domain on Cell 5. (see Note 2)

<–

SECURITY MODE COMMAND

11

The UE transmits a SECURITY MODE COMPLETE message on Cell 5.

–>

SECURITY MODE COMPLETE

12

The SS transmits a ROUTING AREA UPDATE ACCEPT message on Cell 5.

<–

ROUTING AREA UPDATE ACCEPT

12A

The UE transmits a ROUTING AREA UPDATE COMPLETE message.

–>

ROUTING AREA UPDATE COMPLETE

13-21

Steps 8 to 16 of the generic test procedure in TS 34.108 subclause 7.2.3.2 are performed on Cell 5 (the SS performs a SMC procedure and the CS call is set up).

22

The UE releases the PS signalling connection.

–>

SIGNALLING CONNECTION RELEASE INDICATION

The UE is in end state UTRA CS call (U5).

Note 1: The trigger in step 1 is the same as in the generic procedure in 36.508 clause 6.4.3.5.

Note 2: A real network will initiate the security mode command procedure for the CS domain immediately after receiving the CM SERVICE REQUEST, but in this test case it was chosen to complete the procedure for PS domain first in order to avoid the possibility of a security mode command procedure running in parallel with another RRC procedure.

Table 13.1.2a.3.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

13.1.2a.3.3 Specific message contents

Table 13.1.2a.3.3-1: SystemInformationBlockType6 for cell 1 (preamble and all steps, Table 13.1.2a.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)

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

Table 13.1.2a.3.3-2: EXTENDED SERVICE REQUEST (step 4, Table 13.1.2a.3.2-1)

Derivation path: 36.508 Table 4.7.2-14A

Information Element

Value/Remark

Comment

Condition

Service type

‘0000’B

‘mobile originating CS fallback or 1xCS fallback’

CSFB response

Not present

EPS bearer context status

Not present or any allowed value

Table 13.1.2a.3.3-3: RRCConnectionRelease (step 5, Table 13.1.2a.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

}

nonCriticalExtension SEQUENCE {

cellInfoList-r9 CHOICE {

utra-FDD-r9 SEQUENCE {

1 entry

FDD

physCellId-r9[1]

PhysicalCellIdentity of Cell 5

utra-BCCH-Container-r9[1]

SYSTEM INFORMATION CONTAINER

}

utra-TDD-r9 SEQUENCE {

1 entry

TDD

physCellId-r9[1]

PhysicalCellIdentity of Cell 5

utra-BCCH-Container-r9[1]

SYSTEM INFORMATION CONTAINER

}

}

}

}

}

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

Table 13.1.2a.3.3-4: SYSTEM INFORMATION CONTAINER (Table 13.1.2a.3.3-3)

Derivation path: 25.331 clause 11.2

Information Element

Value/Remark

Comment

Condition

mib

See Table 13.1.2a.3.3-5

sysInfoTypeSB1

See 34.108 6.1.0a

sysInfoTypeSB2

Not present

sysInfoType1

See 34.108 6.1.0b

sysInfoType3

See 34.108 6.1.0b

sysInfoType5

See 34.108 6.1.0b

sysInfoType7

See 34.108 6.1.0b

sysInfoType11

See 34.108 6.1.0b

sysInfoType11bis

Not present

sysInfoType12

See 34.108 6.1.0b

Table 13.1.2a.3.3-5: Master Information Block (Table 13.1.2a.3.3-4)

Derivation Path: 34.108 clause 6.1.0a.3

Information Element

Value/remark

Comment

Condition

– MIB value tag

1

Table 13.1.2a.3.3-6: System Information Block type 3 for Cell 5 (preamble and all steps, Table 13.1.2a.3.2-1)

Derivation path: 34.108 clause 6.1.0b

Information Element

Value/Remark

Comment

Condition

Access Class Barred List

– Access Class Barred0

barred

– Access Class Barred1

barred

– Access Class Barred2

barred

– Access Class Barred3

barred

– Access Class Barred4

barred

– Access Class Barred5

barred

– Access Class Barred6

barred

– Access Class Barred7

barred

– Access Class Barred8

barred

– Access Class Barred9

barred

– Access Class Barred10

barred

– Access Class Barred11

barred

– Access Class Barred12

barred

– Access Class Barred13

barred

– Access Class Barred14

barred

– Access Class Barred15

barred

NOTE 1: To confirm that the UE uses System Information included in RRCConnectionRelease message, the parameters of System Information included in RRCConnectionRelease message is intentionally different from the target cell.

Table 13.1.2a.3.3-6A: System Information Block type 3 for Cell 5 (postamble)

Derivation path: 34.108 clause 6.1.0b

NOTE 2: Following the last test step, default contents of System Information Block type 3 should be applied for cell 5, to allow the UE to complete the postamble procedure.

Table 13.1.2a.3.3-7: Master Information Block for Cell 5 (preamble and all steps, Table 13.1.2a.3.2-1)

Derivation Path: 34.108 clause 6.1.0a.3

Information Element

Value/remark

Comment

Condition

– MIB value tag

2

Table 13.1.2a.3.3-8: CM SERVICE REQUEST (step 9, Table 13.1.2a.3.2-1)

Derivation path: 24.008 Table 9.2.11

Information Element

Value/Remark

Comment

Condition

CM service type

‘0001’B

‘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.2a.3.3-9: ROUTING AREA UPDATE ACCEPT (step 12, Table 13.1.2a.3.2-1)

Derivation path: 24.008 Table 9.4.15

Information Element

Value/Remark

Comment

Condition

P-TMSI signature

Not present

Allocated P-TMSI

efb1ee97

TMSI is an arbitrary value chosen different from M-TMSI in the preamble

Table 13.1.2a.3.3-10: ATTACH ACCEPT (Preamble)

Derivation Path: 36.508 Table 4.7.2-1

Information Element

Value/remark

Comment

Condition

EPS network feature support

Not present