4.9.24 Test procedure for IMS MO Video call establishment in 5GC

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

4.9.24.1 Scope

The purpose of this procedure is to establish an IMS MO Video call.

4.9.24.2 Procedure description

4.9.24.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.24.2.2 Procedure sequence

Table 4.9.24.2.2-1: IMS MO video call establishment in 5GC

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt an IMS Video call

2

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

–>

NR RRC: RRCSetupRequest

P

3

SS transmit an RRCSetup message.

<–

NR RRC: RRCSetup

4

Check: Does the UE transmit an RRCSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message?

–>

NR RRC: RRCSetupComplete
5GMM: SERVICE REQUEST

P

5

The SS transmits a SecurityModeCommand message to activate AS security.

<–

NR RRC: SecurityModeCommand

6

Check: Does the UE transmit a SecurityModeComplete message and establish the initial security configuration?

–>

NR RRC: SecurityModeComplete

P

7

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

<–

NR RRC: RRCReconfiguration
5GMM: SERVICE ACCEPT

EXCEPTION: In parallel to step 8 below, the steps specified in Table 4.9.24.2.2-2 take place.

8

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

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

9a1-9a4

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

9b1-9b4

ELSE steps 2-5 of Annex A.15.2 of TS 34.229-5 [47] take place.

10

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

<–

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 13b8 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.15.1 of TS 34.229-5 [47] take place.

13b1-13b3

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

Table 4.9.24.2.2-2: Parallel Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

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

1a1

IF the UE is configured to use preconditions, THEN step 1 of Annex A.15.1 of TS 34.229-5 [47] takes place.

1b1

ELSE step 1 of Annex A.15.2 of TS 34.229-5 [47] takes place

4.9.24.3 Specific message contents

Table 4.9.24.3-1: RRCSetupRequest (step 2, Table 4.9.24.2.2-1)

Derivation Path: TS 38.508-1 [21], Table 4.6.1-23.

Information Element

Value/remark

Comment

Condition

RRCSetupRequest ::= SEQUENCE {

rrcSetupRequest SEQUENCE {

establishmentCause

mo-VideoCall

}

}

Table 4.9.24.3-2: SERVICE REQUEST (step 4, Table 4.9.24.2.2-1)

Derivation Path: TS 38.508-1 [21], Table 4.7.1-16

Information Element

Value/remark

Comment

Condition

Service type

Service type value

‘0001’B

data

Table 4.9.24.3-3: PDU SESSION MODIFICATION COMMAND (step 10, Table 4.9.24.2.2-1)

Derivation Path: TS 38.508-1 [21], Table 4.7.2-9.

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 TS 38.508-1, Table 4.8.2.1-7 using conditions IMS_VOICE and IMS_VIDEO.

Authorized QoS flow descriptions

Reference QoS flow #5 and QoS flow #6 as defined in TS 38.508-1, Table 4.8.2.3-5 & Table 4.8.2.3-6 respectively.

Mapped EPS bearer contexts

Not Present

Mapped EPS bearer contexts

Interworking_with_EPS

Mapped EPS bearer context

EPS bearer identity

The same value as the one specified in the Reference QoS flow referred to from the Reference QoS rule indicated in the IE Authorized QoS rules

Operation code

‘001’B

Create new EPS bearer

E bit

‘1’B

Parameters list is included

Number of EPS parameters

’0010’B

2 parameters

Mapped EPS QoS parameters

See reference dedicated EPS bearer context #3 and #4 in TS 36.508 table 6.6.2-1

Traffic Flow Template

See reference dedicated EPS bearer context #3 and #4 in TS 36.508 table 6.6.2-1

Condition

Explanation

Interworking_with_EPS

If the UE has indicated support of S1, then the SS shall include this IE to provide details for the interworking with EPS being supported for a PDU session. This requirement is set up for the purpose of facilitating the test description. It is not mandatory for the Network to support Mapped EPS bearer contexts.

Table 4.9.24.3-4: RRCReconfiguration (step 10, Table 4.9.24.2.2-1)

Derivation Path: TS 38.508-1 [21], Table 4.8.1-1D