7.8 MTSI MT Voice Call without preconditions at originating UE and with 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.8.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE receives INVITE for voice call without precondition option-tag in Require or Supported header }

then { UE completes setup of voice call without preconditions }

}

7.8.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.4.1]

If an initial INVITE request is received the terminating UE shall check whether the terminating UE requires local resource reservation.

NOTE 1: The terminating UE can decide if local resource reservation is required based on e.g. application requirements, current access network capabilities, local configuration, etc.

During the session initiation, if local resource reservation is required at the terminating UE and the terminating UE supports the precondition mechanism, and:

a) the received INVITE request includes the "precondition" option-tag in the Supported header field or Require header field and the precondition mechanism is enabled as specified in subclause 5.1.5A, the terminating UE shall use the precondition mechanism and shall include a Require header field with the "precondition" option-tag:

– in responses to that INVITE request if those responses include an SDP body;

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

– in subsequent requests that include an SDP body, that it sends towards the originating UE during the session initiation;

b) the received INVITE request includes the "precondition" option-tag in the Supported header field, and the precondition mechanism is disabled as specified in subclause 5.1.5A, the terminating UE shall not use the precondition mechanism:

c) the received INVITE request includes the "precondition" option-tag in the Require header field, and the precondition mechanism is disabled as specified in subclause 5.1.5A, the terminating UE shall reject the INVITE request with a 420 (Bad Extension) response; and

d) the received INVITE request does not include the "precondition" option-tag in the Supported header field or Require header field, the terminating UE shall not use the precondition mechanism.

7.8.3 Test description

7.8.3.1 Pre-test conditions

System Simulator:

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

UE:

– UE contains either ISIM and USIM applications or only USIM application on UICC.

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

– UE is configured to use preconditions.

Preamble:

– The UE is in test state 1N-A (TS 38.508-1 [21]) and registered to IMS.

– The UE has registered to IMS and set up an MO voice call, by executing the generic test procedure in Annex A.2 up to the last step and thereafter executing the generic test procedure in Annex A.4.1. The SS then ends the MO voice call by sending BYE.

7.8.3.2 Test procedure sequence

Table 7.8.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-8

Steps 1-8 of generic procedure specified in Table 4.9.16.2.2-1 of TS 38.508-1 [21] are performed.

–

–

–

–

9-13

Steps 1-5 of Annex A.5.2 happens

–

–

–

–

13A-13C

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

–

–

–

–

14-16

Steps 6-8 of Annex A.5.2 happen.

–

–

–

–

18

Step 10 of Annex A.5.2 happens

<–

ACK

–

–

7.8.3.3 Specific message contents

None as fully described in annex A.5.2.