11.1.1a MO MMTEL enhanced voice service call setup from NR RRC_IDLE / EPS Fallback with redirection / Single registration mode with N26 interface / Success

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

11.1.1a.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_IDLE state }

ensure that {

when { UE is being made to initiate a voice call }

then { UE requests the establishment of a voice call by transmitting an RRCSetupRequest message with establishmentCause set to ‘mo-VoiceCall’ and a SERVICE REQUEST message with Service type set to ‘data’ }

}

(2)

with { UE being in NR RRC_CONNECTED state after having requested a voice call establishment and the MO IMS voice session establishment has been initiated }

ensure that {

when { UE receives an RRCRelease message which includes redirectedCarrierInfo indicating redirection to E-UTRA }

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

}

11.1.1a.2 Conformance requirements

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

[TS 38.331, clause 5.3.3.3]

The UE shall set the contents of RRCSetupRequest message as follows:

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCSetupRequest message to lower layers for transmission.

[TS 24.501, clause 5.6.1.2]

For cases d) and e) in subclause 5.6.1.1, the Uplink data status IE shall be included in the SERVICE REQUEST message to indicate the PDU session(s) the UE has pending user data to be sent. If the UE is not a UE configured for high priority access in selected PLMN:

b) otherwise, the service type IE in the SERVICE REQUEST message shall be set to "data".

[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.1a.3 Test Description

11.1.1a.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.1a.3.1-1/2.

Table 11.1.1a.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.1a.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 contains either ISIM and USIM applications or only USIM application on UICC.

– The UE is configured to register for IMS after switch on.

– 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/5GC), 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.1a.3.2 Test procedure sequence

Table 11.1.1a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt an IMS voice call.

2

Check: Does the UE send NR RRCSetupRequest with EstablishmentCause set to ‘mo-VoiceCall’?

–>

NR RRC: RRCSetupRequest

1

P

3

SS transmits an NR RRCSetup message

<–

NR RRC: RRCSetup

4

Check: Does the UE transmit an NR RRCSetupComplete message to confirm the successful completion of the connection establishment including initiation of 5GSM procedure by including the SERVICE REQUEST message with Service Type set to ‘data’?

–>

NR RRC: RRCSetupComplete 5GSM: SERVICE REQUEST

1

P

5

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

6-9

Steps 5-8 of expected sequence from Table 4.5.4.2-3 as defined in TS 38.508-1 [4] are performed.

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

SS transmits RRCRelease message indicating redirection to E-UTRA Cell 1.

<–

NR RRC: RRCRelease

16-21

UE performs generic procedure as defined in TS 38.508-1 [4], Table 4.9.7.2.2-1 Steps 1-6 for N1 to S1 Inter mode change with condition ‘connected without release’ & ‘mapped 5G security context’.

22-25

Generic Test Procedure as defined in Steps 5-8 of TS 36.508-1 [4] Table 4.5A.6.3-1 is performed to establish radio bearer corresponding to IMS PDN.

26

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 table 6.6.2-1: Reference dedicated EPS bearer contexts.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

EXCEPTION: In parallel to the events described in steps 27-28 the steps specified in table 11.1.1.3.2-2 will take place.

27

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the establishment of the new data radio bearer, associated with the dedicated EPS bearer.

–>

RRC: RRCConnectionReconfigurationComplete

28

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

–>

RRC: ULInformationTransfer

NAS:ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

29

UE is triggered by MMI to release the call.

30-33

Follow the Test Steps 2-5 as defined in TS 34.229-1 [35] subclause C.32 for Generic test procedure for MO release of IMS call followed by EPS Bearer Deactivation.

34

SS transmits RRCConnectionRelease message indicating redirection to NR Cell 1.

<–

RRC: RRCConnectionRelease

35

Generic Test procedure for Tracking area updating / Inter-system change from S1 mode to N1 mode in 5GMM/EMM-IDLE mode with connected without release is present as mentioned in TS 38.508-1 [4] Table 4.9.9.2.2-1 is performed with condition ‘’Mapped EPS security context.

38

Generic Procedure as defined in TS 38.508-1 [4] Table 4.9.6.3-1A to switch off the UE in NR RRC_CONNECTED mode with T3540 started is performed.

Table 11.1.1a.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.

2

P

11.1.1a.3.3 Specific message contents

Table 11.1.1a.3.3-1: RRCSetupRequest (step 2, table 11.1.1a.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.6.1-23

Information Element

Value/remark

Comment

Condition

RRCSetupRequest ::= SEQUENCE {

rrcSetupRequest SEQUENCE {

establishmentCause

mo-VoiceCall

}

}

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

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

Information Element

Value/Remark

Comment

Condition

Service type

‘0001’B

data

Uplink data status

Present

PSI bit corresponding to IMS PDN needs to be set

Table 11.1.1a.3.3-3: RRCRelease (step 15, table 11.1.1a.3.2-1)

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

Information Element

Value/Remark

Comment

Condition

RRCRelease ::= SEQUENCE {

criticalExtensions CHOICE {

rrcRelease SEQUENCE {

redirectedCarrierInfo CHOICE {

eutra SEQUENCE {

eutraFrequency

Downlink EARFCN of EUTRA cell 1

cnType

epc

}

}

}

}

}

Table 11.1.1a.3.3-4: RRCConnectionRelease (step 34, table 11.1.1a.3.2-1)

Derivation path: TS 36.508 [4] Table 4.6.1-15

Information Element

Value/Remark

Comment

Condition

RRCConnectionRelease ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionRelease-r8 SEQUENCE {

redirectedCarrierInfo SEQUENCE {

nr-r15 SEQUENCE {

carrierFreq-r15

Downlink NR SSB ARFCN of cell NR Cell 1

TS 38.508-1 [4] cl.6.2.3.1

subcarrierSpacingSSB-r15

}

}

}

}

}