11.1.3a MO MMTEL enhanced voice service call setup from NR RRC_CONNECTED / EPS Fallback with handover / Single registration mode with N26 interface / Success

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

11.1.3a.1 Test Purpose (TP)

(1)

with { UE supporting both S1 mode and N1 mode and configured to use preconditions and configured to use the EVS default configuration and the UE is in NR RRC_CONNECTED state }

ensure that {

when { User initiates a MMTEL call, the MO IMS voice call has been initiated and the UE receives a MobilityFromNRCommand message which includes targetRAT-Type set to eutra an RRCRelease message which includes redirectedCarrierInfo indicating redirection to E-UTRA }

then { UE performs a handover to the E-UTRA including a TAU procedure, and, successfully completes the voice call setup in EPS using EVS}

}

11.1.3a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 clause 5.4.3.3, 5.4.3.4 and TS 26.114 clause 5.2.1.1.

[TS 38.331, clause 5.4.3.3]

The UE shall:

1> if T390 is running:

2> stop timer T390 for all access categories;

2> perform the actions as specified in 5.3.14.4;

1> if the targetRAT-Type is set to eutra:

2> consider inter-RAT mobility as initiated towards E-UTRA;

2> forward the nas-SecurityParamFromNR to the upper layers, if included;

1> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT.

[TS 38.331, clause 5.4.3.4]

Upon successfully completing the handover, at the source side the UE shall:

1> reset MAC;

1> stop all timers that are running;

1> release ran-NotificationAreaInfo, if stored;

1> release the AS security context including the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key, if stored;

1> release all radio resources, including release of the RLC entity and the MAC configuration;

1> if the E-UTRA RRCConnectionReconfiguration message included in the received MobilityFromNRCommand does not include fullConfig:

2> maintain source RAT configuration of PDCP and SDAP for applicable RBs which is used for target RAT RBs;

1> else:

2> release the associated PDCP entity and SDAP entity for all established RBs;

1> indicate the release of the RRC connection to upper layers together with the release cause ‘other’.

[TS 26.114, clause 5.2.1.1]

MTSI clients in terminals offering speech communication shall support narrowband, wideband and super-wideband communication.

…

MTSI clients in terminals offering super-wideband or fullband speech communication shall support:

– EVS codec …

11.1.3a.3 Test Description

11.1.3a.3.1 Pre-test conditions

System Simulator:

– NR Cell 1, E-UTRA Cell 1.

– System information for the NR Cell 1 in accordance with combination NR-6 in TS 38.508-1 [4] sub-clause 4.4.3.1.2, and, for the E-UTRA Cell 1 in accordance with system information combination 31 as defined in TS 36.508 [7], subclause 4.4.3.1.1.

– Power levels are constant and as defined in Tables 11.1.3a.3.1-1/2.

Table 11.1.3a.3.1-1: Time instances of cell power level and parameter changes for FR1

Parameter name

Unit

NR Cell 1

E-UTRA Cell 1

Remark

T0

SS/PBCH SSS EPRE

dBm/SCS

-88

RS EPRE

dBm/15kHz

-85

Table 11.1.3a.3.1-2: Time instances of cell power level and parameter changes for FR2

Parameter name

Unit

NR Cell 1

E-UTRA Cell 1

Remark

T0

SS/PBCH SSS EPRE

dBm/SCS

-82

–

RS EPRE

dBm/15kHz

–

-85

UE:

– The UE is configured to use preconditions.

Preamble:

– With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state RRC_IDLE using generic procedure parameters Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On) in accordance with the procedure described in TS 38.508-1 [4], clause 4.5.2. 4G GUTI and eKSI are assigned and security context established.

– the UE is switched-off.

– With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state 1N-A, RRC_IDLE Connectivity (NR), in accordance with the procedure described in TS 38.508-1 [4], Table 4.5.2.2-2. 5G-GUTI and ngKSI are assigned and security context established.

11.1.3a.3.2 Test procedure sequence

Table 11.1.3a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

–

The following messages are to be observed on NR Cell 1 unless explicitly stated otherwise.

–

–

–

–

1

The SS transmits a Paging message.

<–

NR RRC: Paging

–

–

2

The UE transmits an RRCSetupRequest message.

–>

NR RRC: RRCSetupRequest

–

–

3-7

Steps 3 to 8 of the NR RRC_CONNECTED procedure in TS 38.508-1 [4] Table 4.5.4.2-3 are executed to successfully complete the service request procedure.

–

–

–

–

8

Set the power levels according to “T0” as per Table 11.1.3a.3.1-1/2.

–

–

–

–

9

Make the UE attempt an IMS voice call.

–

–

–

–

10-14

Steps 1-5 of expected sequence from A.4.1a as defined in TS 34.229-5 [41] are performed for initiating an MTSI MO speech call.

–

–

–

–

15

The SS transmits a MobilityFromNRCommand message which includes targetRAT-Type set to eutra according to 38.508-1 [4] Table 4.6.1-8.

<–

NR RRC: MobilityFromNRCommand

–

–

–

The following messages are to be observed on E-UTRA Cell 1 unless explicitly stated otherwise.

–

–

–

–

16

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message to confirm the successful completion of handover?

–>

RRC: RRCConnectionReconfigurationComplete

1

P

17

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

1

P

18-21

Steps 4a1-6 of the generic test procedure in TS 38.508-1 [4] Table 4.9.7.2.2-1 for N1 to S1 Inter mode change with condition ‘connected without release’ & ‘mapped 5G security context’ are performed to make sure successfully camped on E-UTRAN cell upon mobility from NR.

–

–

–

–

22

The SS configures a new RLC-UM data radio bearer with condition DRB (0,1), associated with the dedicated EPS bearer context. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message. EPS bearer context #4 (QCI 1) according to TS 36.508 [7] Table 6.6.2-1: Reference dedicated EPS bearer contexts.

Reference dedicated EPS bearer contexts is to establish the dedicated EPS bearer context on IMS PDN.

<–

RRC: RRCConnectionReconfiguration

NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

–

–

EXCEPTION: In parallel to the events described in steps 23-24 the steps specified in table 11.1.3a.3.2-2 will take place.

–

–

–

–

23

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRC: RRCConnectionReconfigurationComplete

–

–

24

The UE transmits an ULInformationTransfer message including the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

–

–

24A

The SS waits 1 second for call duration.

–

–

–

–

25

Release IMS Call as specified in the generic procedure in TS 34.229-1 [35] subclause C.32.

–

–

–

–

Table 11.1.3a.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-6

Steps 6-11 of expected sequence from A.4.1a as defined in TS 34.229-5 [41] are performed for initiating an MTSI MO speech call.

–

–

–

–

7

Step 12 of expected sequence from A.4.1a as defined in TS 34.229-5 [41] is performed for initiating an MTSI MO speech call.

–

–

1

P

11.1.3a.3.3 Specific message contents

Table 11.1.3a.3.3-1: REGISTRATION REQUEST (preamble, Table 11.1.3a.3.2-1)

Derivation path: TS 38.508-1 [4] Table 4.7.1-6

Information Element

Value/remark

Comment

Condition

5GMM capability

S1 mode

‘1’B

S1 mode supported

S1 UE network capability

Present but contents not checked

Table 11.1.3a.3.3-2: REGISTRATION ACCEPT (preamble, Table 11.1.3a.3.2-1)

Derivation path: TS 38.508-1 [4] Table 4.7.1-7

Information Element

Value/remark

Comment

Condition

5GS network feature support

IMS- VoPS-3GPP

‘1’B

IMS voice over PS session supported over 3GPP access

IWK N26

‘0’B

Interworking without N26 interface not supported

Table 11.1.3a.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (preamble for PDU Session for PS data, Table 11.1.3a.3.2-1)

Derivation path: TS 38.508-1 [4] Table 4.7.2-2, condition Interworking_with_EPS

Table 11.1.3a.3.3-4: PDU SESSION ESTABLISHMENT ACCEPT (preamble for IMS PDU Session, Table 11.1.3a.3.2-1)

Derivation path: TS 38.508-1 [4] Table 4.7.2-2, condition Interworking_with_EPS, IMS_DNN_ Requested

Table 11.1.3a.3.3-5: MobilityFromNRCommand (step 15, Table 11.1.3a.3.2-1)

Derivation path: TS 38.508-1 [4] Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

MobilityFromNRCommand::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier

criticalExtensions CHOICE {

mobilityFromNRCommand SEQUENCE {

targetRAT-Type

eutra

targetRAT-MessageContainer

RRCConnectionReconfig uration

nas-SecurityParamFromNR

8 LSB of the downlink NAS COUNT

}

}

}

}

Table 11.1.3a.3.3-6: RRCConnectionReconfiguration (Table 11.1.3a.3.3-5)

Derivation path: TS 36.508-1 [4], Table 4.6.1-8 condition HO-TO-EUTRA(n,0)

Table 11.1.3a.3.3-7: MobilityControlInfo (Table 11.1.3a.3.3-6)

Derivation path: TS 36.508 [7], Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of E-UTRA Cell 1

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for E-UTRA Cell 1

}

carrierFreq

Not present

Band > 64

carrierBandwidth SEQUENCE {

dl-Bandwidth

Downlink system bandwidth under test.

ul-Bandwidth

Uplink Bandwidth under test.

FDD

ul-Bandwidth

Not present

TDD

}

additionalSpectrumEmission

1

HO-to-EUTRA

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for E-UTRA Cell 1

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

Band > 64

If band > 64 is selected

Table 11.1.3a.3.3-8: TRACKING AREA UPDATE REQUEST (step 17, Table 11.1.3a.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.9.7.2.3-1.

Information Element

Value/remark

Comment

Condition

EPS update type

"Active" flag

AnyValue

EPS bearer context status

Not checked

EBI corresponding to active PDU Sessions need to be set to 1