11.1.1 MO MMTEL voice 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.1.1 Test Purpose (TP)

(1)

with { UE supporting both S1 mode and N1 mode and operating in single-registration mode and the Network having indicated "interworking without N26 interface not supported" and the UE in NR RRC_IDLE state }

ensure that {

when { User initiates an MMTEL call and the UE completes Access control and checking in 5GMM-IDLE mode }

then { UE requests the establishment of an MMTEL 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 an MMTEL 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 MMTEL call setup in EPS }

}

11.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 4.5.4.1, 5.6.1.2 and TS 38.331: clauses 5.3.3.2, 5.3.3.3. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 4.5.4.1]

When the UE is in 5GMM-IDLE mode, upon receiving a request from the upper layers for an access attempt, the NAS shall categorize the access attempt into access identities and an access category following subclause 4.5.2, table 4.5.2.1 and table 4.5.2.2, and subclause 4.5.3, and provide the applicable access identities and the access category to the lower layers for the purpose of access control checking. In this request to the lower layer the NAS can also provide to the lower layer the RRC establishment cause determined as specified in subclause 4.5.6 of this specification.

NOTE 1: The access barring check is performed by the lower layers.

NOTE 2: As an implementation option, the NAS can provide the RRC establishment cause to the lower layers after being informed by the lower layers that the access attempt is allowed.

If the UE has uplink user data pending for one or more PDU sessions when it builds a REGISTRATION REQUEST or SERVICE REQUEST message as initial NAS message, the UE shall indicate the respective PDU sessions in the Uplink data status IE as specified in subclause 5.5.1.3.2 and 5.6.1.2, regardless of the access category for which the access barring check is performed.

NOTE 3: The UE indicates pending user data for all the respective PDU sessions, even if barring timers are running for some of the corresponding access categories.

If the lower layers indicate that the access attempt is allowed, the NAS shall initiate the procedure to send the initial NAS message for the access attempt.

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

a) if there exists an emergency PDU session which is indicated in the Uplink data status IE the service type IE in the SERVICE REQUEST message shall be set to "emergency services"; or

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

[TS 38.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE and it has acquired essential system information as described in 5.2.2.1.

The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure.

Upon initiation of the procedure, the UE shall:

1> if the upper layers provide an Access Category and one or more Access Identities upon requesting establishment of an RRC connection:

2> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers;

[TS 38.331, clause 5.3.3.3]

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

1> set the ue-Identity as follows:

2> if upper layers provide a 5G-S-TMSI:

3> set the ue-Identity to ng-5G-S-TMSI-Part1;

2> else:

3> draw a 39-bit random value in the range 0..239-1 and set the ue-Identity to this value;

NOTE 1: Upper layers provide the 5G-S-TMSI if the UE is registered in the TA of the current cell.

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.

11.1.1.3 Test Description

11.1.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 is configured according to TS 38.508-1 [4] Table 4.4.2-3 and is connected to 5GC.

– E-UTRA Cell 1 is configured to TS 36.508 [7] Table 4.4.2-2 and is connected to EPC.

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

– N26 interface is configured.

– Power levels are constant and as defined in Tables 11.1.1.3.1-1/2.

Table 11.1.1.3.1-1: Time instances of cell power level and parameter changes for conducted test environment

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.1.3.1-2: Time instances of cell power level and parameter changes for OTA test environment

Parameter name

Unit

NR Cell 1

E-UTRA Cell 1

Remark

T0

SS/PBCH SSS EPRE

dBm/SCS

-82

–

RS EPRE

dBm/15kHz

–

-96

UE:

The UE is configured to use IMS 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.1.3.2 Test procedure sequence

Table 11.1.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

Void

–

–

–

–

1

Make the UE attempt an MTSI MO Speech Call (Note 1).

–

–

–

–

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

4A

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

–

–

–

–

5-8

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

–

–

–

–

9-13

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

–

–

–

–

14

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

<–

NR RRC: RRCRelease

–

–

15-20

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

–

–

–

–

21-24

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.

–

–

–

–

–

EXCEPTION: Steps 25a1-25a2 describe a step sequence depending on UE implementation.

–

–

–

–

25a1-25a2

The UE may perform steps 1-2 according to TS 34.229-1 subclause C.46 to perform IMS re-registration on EUTRAN.

–

–

–

–

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.

–

–

–

–

36-37

IF UE performed IMS re-registration over E-UTRAN in Steps 25a1-25a2,

THEN the UE may perform IMS re-registration on NR Cell1 as per Annex A.12 of TS 34.229-5 [41]

–

–

–

–

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.

–

–

–

–

Note 1: UE is configured such that Access Control check passes for MO MMTEL Voice call.

Table 11.1.1.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-5

Steps 1 to 5 of the Generic test procedure for setting up MTSI MO speech call – EPS fallback according TS 34.229-5 [41] subclause A.9.2 take place.

–

–

–

–

6

Step 6 of the Generic test procedure for setting up MTSI MO speech call – EPS fallback according TS 34.229-5 [41] subclause A.9.2 takes place.

–

–

2

P

11.1.1.3.3 Specific message contents

Table 11.1.1.3.3-1: RRCSetupRequest (step 2, table 11.1.1.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.1.3.3-2: SERVICE REQUEST (step 4, table 11.1.1.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.1.3.3-3: RRCRelease (step 14, table 11.1.1.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.1.3.3-4: RRCConnectionRelease (step 34, table 11.1.1.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

}

}

}

}

}