4.9.16 Test procedure for IMS MT speech call establishment in 5GC

38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification

4.9.16.1 Scope

The purpose of this procedure is to establish an IMS MT speech call.

4.9.16.2 Procedure description

4.9.16.2.1 Initial conditions

System Simulator:

– 1 NR Cell connected to 5GC, default parameters.

User Equipment:

– The UE is in state 1N-A and registered to the IMS.

4.9.16.2.2 Procedure sequence

Table 4.9.16.2.2-1: IMS MT speech call establishment in 5GC

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a Paging message.

<–

NR RRC: Paging

2

Check: Does the UE transmit an RRCSetupRequest message with ‘establishmentCause’ set to ‘mt-Access’?

–>

NR RRC: RRCSetupRequest

P

3

The SS transmits an RRCSetup message.

<–

NR RRC: RRCSetup

4

Check: Does the UE transmit an RRCSetupComplete message and a SERVICE REQUEST message?

–>

NR RRC: RRCSetupComplete

5GMM: SERVICE REQUEST

P

5

The SS transmits a SecurityModeCommand message.

<–

NR RRC: SecurityModeCommand

6

The UE transmits a SecurityModeComplete message.

–>

NR RRC: SecurityModeComplete

7

The SS transmits an RRCReconfiguration message and a SERVICE ACCEPT message to establish SRB2 and DRB(s).

The RRCReconfiguration message is configured using RRCReconfiguration-SRB2-DRB(n, m) where n and m are the number of DRB(s) configured with RLC-AM and RLC-UM respectively.

<–

NR RRC: RRCReconfiguration

5GMM: SERVICE ACCEPT

8

Check: Does the UE transmit an RRCReconfigurationComplete message?

–>

NR RRC: RRCReconfigurationComplete

P

EXCEPTION: Steps 9a1 to 9b5 describe behaviour that depends on UE configuration; the “lower case letter” identifies a step sequence that takes place if such configuration was conducted.

9a1-9a5

IF the UE is configured to use preconditions THEN steps 1-5 of Annex A.5.1 of TS 34.229-5 [47] take place.

9b1-9b5

ELSE steps 1-5 of Annex A.5.2 of TS 34.229-5 [47] take place.

10

The SS transmits an RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND message.

<–

NR RRC: RRCReconfiguration
5GMM: DL NAS TRANSPORT
5GSM: PDU SESSION MODIFICATION COMMAND

EXCEPTION: Depending upon UE implementation, steps 11 and 12 can occur in any order

11

The UE transmits an RRCReconfigurationComplete message

–>

NR RRC: RRCReconfigurationComplete

12

Check: Does the UE transmit a ULInformationTransfer message, an UL NAS TRANSPORT message and an PDU SESSION MODIFICATION COMPLETE message?

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION MODIFICATION COMPLETE

P

EXCEPTION: Steps 13a1 to 13b7 describe behaviour that depends on UE configuration; the “lower case letter” identifies a step sequence that takes place if such configuration was conducted.

13a1-13a7

IF the UE is configured to use preconditions THEN steps 6-12 of Annex A.5.1 of TS 34.229-5 [47] take place.

13b1-13b5

ELSE steps 6-10 of Annex A.5.2 of TS 34.229-5 [47] take place.

4.9.16.3 Specific message contents

Table 4.9.16.3-1: RRCSetupRequest (step 2, Table 4.9.16.2.2-1)

Derivation Path: Table 4.6.1-23

Information Element

Value/remark

Comment

Condition

RRCSetupRequest ::= SEQUENCE {

rrcSetupRequest SEQUENCE {

establishmentCause

mt-Access

}

}

Table 4.9.16.3-2: SERVICE REQUEST (step 4, Table 4.9.16.2.2-1)

Derivation Path: Table 4.7.1-16

Information Element

Value/remark

Comment

Condition

Service type

Service type value

’0010’B

Mobile Terminated Services

Table 4.9.16.3-3: PDU SESSION MODIFICATION COMMAND (step 10, Table 4.9.16.2.2-1)

Derivation Path: Table 4.7.2-2

Information Element

Value/remark

Comment

Condition

PDU session ID

Same value as sent in PDU SESSION ESTABLISHMENT REQUEST message.

Authorized QoS rules

Reference QoS rule #7 as defined in Table 4.8.2.1-7 using condition IMS_VOICE.

Authorized QoS flow descriptions

Reference QoS flow #5 as defined in Table 4.8.2.3-5.

Table 4.9.16.3-4: RRCReconfiguration (step 10, Table 4.9.16.2.2-1)

Derivation Path: Table 4.8.1-1C