7.24b MTSI MO Voice Call / Forking / UE receives two preliminary responses and one final response / 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.24b.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 processed two early dialogs until before completion }

ensure that {

when { one of the early dialog moves to established state and the other early dialog is then indicated to be ready for establishment as well }

then { UE sends ACK for this other dialog and terminates it right away by sending BYE }

}

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

When a final answer is received for one of the early dialogs, the UE proceeds to set up the SIP session. The UE shall not progress any remaining early dialogs to established dialogs. Therefore, upon the reception of a subsequent final 200 (OK) response for an INVITE request (e.g., due to forking), the UE shall:

1) acknowledge the response with an ACK request; and

2) send a BYE request to this dialog in order to terminate it.

7.24b.3 Profile Requirements (Informative)

[GSMA NG.114 V1.0, clause 2.2.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].

Note 1: An early dialog that is maintained is one where a SIP 18x response has been received and the early dialogue has not been terminated (e.g. by receipt of a SIP 199 response) prior to receiving a SIP 2xx response.

Note 2: Multiple early dialogs can occur as a result of forking or for other reasons such as announcements or services.

7.24b.4 Test description

7.24b.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.24b.4.2 Test procedure sequence

Table 7.24b.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 an SDP answer as specified in A.4.1 step 6 (dialog 2)

(step 4 of Annex A.4.1a)

–>

PRACK

–

–

23

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

<–

200 OK

–

–

24

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

<–

180 Ringing

–

–

25

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

–>

PRACK

1

P

26

SS responds to PRACK (dialog 2)
(step 10 of A.4.1a)

<–

200 OK

–

–

27

SS sends 200 OK for dialog 1

(step 11 of Annex A.4.1a)

<–

200 OK

–

–

28

UE sends ACK for dialog 1

(step 12 of Annex A.4.1a)

–>

ACK

–

–

29

SS sends 200 OK for dialog 2

(step 11 of Annex A.4.1a)

<–

200 OK

–

–

–

EXCEPTION: Steps 30 and 31 may occur in any order.
Note: the UE will issue ACK before BYE but, due to network delays, these messages might arrive in reverse order at the SS

–

–

–

–

30

UE sends ACK for dialog 2

(step 12 of Annex A.4.1a)

–>

ACK

2

P

31

UE sends BYE for dialog 2

–>

BYE

2

P

32

SS sends 200 OK for BYE

<–

200 OK

–

–

33-34

SS releases the established call (dialog 1)

(Annex A.8)

–

–

–

–

7.24b.4.3 Specific message contents

Table 7.24b.4.3-1: INVITE (in steps 2-8, table 7.24b.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.24b.4.3-2: 183 Session Progress (step 21, table 7.24b.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.24b.4.3-3: 200 OK (step 29, table 7.24b.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.24b.4.3-4: ACK (step 30, table 7.24b.4.2-1)

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