7.24a MTSI MO Voice Call / Forking / UE receives two preliminary responses and one early dialog termination / 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.24a.1 Test Purpose (TP)

(1)

with { UE being registered to IMS and configured to use preconditions and to not use GRUU and to not suppress forking }

ensure that {

when { UE is made to start a voice call, processes the call setup until before completion, and then receives another early dialog indication }

then { UE processes the second early dialog until before completion }

}

(2)

with { UE having proceeded two early dialogs }

ensure that {

when { UE receives 199 Early Dialog Terminated for the first dialog, followed by 200 OK for the second dialog }

then { UE sends ACK on the second dialog and maintains it }

}

7.24a.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]:

Upon receiving a 199 (Early Dialog Terminated) provisional response to an established early dialog the UE shall release resources specifically related to that early dialog.

7.24a.3 Profile Requirements (Informative)

[GSMA NG.114 V1.0, clause 2.3.7]:

It is also possible that the network or the terminating UE will need to release an early dialog using the 199 (Early Dialog Terminated) response defined in IETF RFC 6228 [85]. To support this, the originating UE must include the "199" option tag in the Supported header field in the initial INVITE request and must understand a 199 (Early Dialog Terminated) response code and act as specified in section 5.1.3.1 of 3GPP TS 24.229 [8].

7.24a.4 Test description

7.24a.4.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.

– UE is configured to not use GRUU.

– UE is configured to not suppress forking via the no-fork directive.

Preamble:

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

7.24a.4.2 Test procedure sequence

Table 7.24a.4.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE is made to start a voice call.

–

–

–

–

2-8

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

–

–

–

–

9-12

UE continues call setup (dialog 1)

(steps 2-5 of Annex A.4.1a)

–

–

–

–

13

SS triggers resource reservation: Step 10 of generic procedure specified in Table 4.9.15.2.2-1 of TS 38.508-1 [21] is performed.

–

–

–

–

–

EXCEPTION: In parallel to steps 14 and 15 below, step 16 occurs.

–

–

–

–

14-15

SS triggers resource reservation: Steps 11-12 of generic procedure specified in Table 4.9.15.2.2-1 of TS 38.508-1 [21] are performed.

–

–

–

–

16-20

UE continues call setup (dialog 1)

(steps 6-10 of A.4.1a)

–

–

–

–

21

SS sends 183 Session Progress with a different to-tag
(dialog 2)

(step 3 of Annex A.4.1a)

<–

183 Session Progress

–

–

22

UE sends PRACK, including SDP answer as specified in A.4.1a step 6 (dialog 2)

(step 4 of Annex A.4.1a)

–>

PRACK

1

P

23

SS responds to PRACK (step 5 of Annex A.4.1a)

<–

200 OK

–

–

24

SS sends 180 Ringing reliably (step 8 of A.4.1a)

<–

180 Ringing

–

–

25

UE acknowledges reception of 180 Ringing (step 9 of A.4.1a)

–>

PRACK

–

–

26

SS responds to PRACK

<–

200 OK

–

–

27

SS sends 199 Early Dialog Terminated (dialog 1)

<–

199 Early Dialog Terminated

–

–

28

SS sends 200 OK for INVITE (dialog 2)

<–

200 OK

–

–

29

UE sends ACK (dialog 2)

–>

ACK

2

P

UE maintains dialog 2 by not sending BYE

–

–

2

F

30-31

SS waits 5 seconds and releases the call (dialog 2)
(Annex A.8)

–

–

–

–

7.24a.4.3 Specific message contents

Table 7.24a.4.3-1: INVITE (in steps 2-8, table 7.24a.4.2-1)

Derivation Path: Annex A.4.1a, Step 1

Header/param

Cond

Value/remark

Rel

Reference

Supported

option-tag

199

RFC 6228 [49]

Table 7.24a.4.3-2: 183 Session Progress (step 21, table 7.24a.4.2-1)

Derivation Path: Annex A.4.1a, Step 3

Header/param

Cond

Value/remark

Rel

Reference

To

RFC 3261 [6]

addr-spec

same value as received in INVITE message

tag

any value different from the one used for dialog 1

Contact

RFC 3261 [6]

addr-spec

px_IMS_CalleeContactUri2

Message-body

o=- 1111111112 1111111111 IN (addrtype) (unicast-address for SS)

RFC 4566 [38]

Table 7.24a.4.3-3: 199 Early Dialog Terminated (step 27, table 7.24a.4.2-1)

Derivation Path: TS 34.229-1 [2], Annex A.2.26

Table 7.24a.4.3-4: 200 OK (step 28, table 7.24a.4.2-1)

Derivation Path: Annex A.4.1a, step 11, with same to tag as used in step 21 of Test procedure sequence

Table 7.24a.4.3-5: ACK (step 29, table 7.24a.4.2-1)

Derivation Path: Annex A.4.1a, step 12, with same to tag as used in step 21 of Test procedure sequence