7.12 MTSI MO Voice Call with preconditions at originating UE and without preconditions at terminating UE / 5GS

34.229-53GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 5: Protocol conformance specification using 5G System (5GS)Release 16TSUser Equipment (UE) conformance specification

7.12.1 Test Purpose (TP)

(1)

with { UE being registered to IMS and configured to use preconditions }

ensure that {

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

then { UE sends INVITE for voice call with preconditions }

}

(2)

with { UE having sent INVITE with preconditions }

ensure that {

when { UE receives 183 Session Progress without preconditions }

then { UE sends PRACK for 183 Session Progress }

}

(3)

with { UE having sent PRACK }

ensure that {

when { UE receives 200 OK for PRACK followed by 180 Ringing followed by 200 OK for INVITE }

then { UE sends ACK }

}

7.12.2 Conformance Requirements

The conformance requirements covered in the present test case are, unless otherwise stated, Rel-15 requirements.

[TS 24.229, clause 5.1.3.1]:

During the session initiation, if the originating UE indicated the support for the precondition mechanism in the initial INVITE request and:

a) the received response with an SDP body includes a Require header field with "precondition" option-tag, the originating UE shall include a Require header field with the "precondition" option-tag:

– in subsequent requests that include an SDP body, that the originating UE sends in the same dialog as the response is received from; and

– in responses with an SDP body to subsequent requests that include an SDP body and include "precondition" option-tag in Supported header field or Require header field received in-dialog; or

b) the received response with an SDP body does not include the "precondition" option-tag in the Require header field,

– in subsequent requests that include an SDP body, the originating UE shall not include a Require or Supported header field with "precondition" option-tag in the same dialog;

– in responses with an SDP body to subsequent requests with an SDP body but without "precondition" option-tag in the Require or Supported header field, the originating UE shall not include a Require or Supported header field with "precondition" option-tag in the same dialog; and

– in responses with an SDP body to subsequent requests with an SDP body and with "precondition" option-tag in the Require or Supported header field, the originating UE shall include a Require header field with "precondition" option-tag in the same dialog.

7.12.3 Test description

7.12.3.1 Pre-test conditions

System Simulator:

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

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:

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

7.12.3.2 Test procedure sequence

Table 7.12.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE is made to attempt an IMS voice call.

–

–

–

–

2

Steps 2-7 of generic procedure specified in Table 4.9.15.2.2-1 of TS 38.508-1 [21] are performed.

–

–

–

–

–

EXCEPTION: In parallel with Step 3, parallel behaviour defined in table 7.12.3.2-2 takes place

–

–

–

–

3

Step 1 of Annex A.4.1 happens

(Check: does the UE send INVITE for voice call with preconditions?)

–>

INVITE

1

P

4

Step 2 of Annex A.4.1 happens

<–

100 Trying

–

–

5

Step 3 of Annex A.4.2 happens

(Note: the SS sends 183 Session Progress without attributes for preconditions in the SDP body.)

<–

183 Session Progress

–

–

6

Step 4 of Annex A.4.2 happens

(Check: does the UE send PRACK?)

–>

PRACK

2

P

7

Step 5 of Annex A.4.2 happens

<–

200 OK

–

–

7A-7C

Steps 10-12 of generic procedure specified in Table 4.9.15.2.2-1 of TS 38.508-1 [21] are performed.

–

–

–

–

8

Step 6 of Annex A.4.2 happens

<–

180 Ringing

–

–

9

Step 7 of Annex A.4.2 happens

<–

200 OK

–

–

10

Step 8 of Annex A.4.2 happens

(Check: does the UE send ACK?)

–>

ACK

3

P

Table 7.12.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

–

7.12.3.3 Specific message contents

None as fully described in Annex A.4.1 and A.4.2.