8.37 Communication Waiting and answering the voice call / 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

8.37.1 Test Purpose (TP)

(1)

with { UE being registered to IMS and having initiated an MO voice call with preconditions }

ensure that {

when { UE receives INVITE for MT voice call with preconditions }

then { UE continues voice call initiation until 180 Ringing (including conditional PRACK/200 OK) }

}

(2)

with { UE having continued initiation of incoming voice call until 180 Ringing }

ensure that {

when { UE is being made to terminate the MO voice call }

then { UE sends BYE for the MO voice call }

}

(3)

with { UE having terminated the MO voice call }

ensure that {

when { UE is being made to accept the incoming MT voice call }

then { UE sends 200 OK for INVITE }

}

8.37.2 Conformance Requirements

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

[TS 24.615 subclause 4.5.5.3.2]:

Upon receipt of an INVITE request containing:

– a Content-Type header field set to "application/vnd.3gpp.cw+xml";

– a MIME body according to subclause 4.4.1 with the with the <communication-waiting-indication> element contained in the <ims-cw> root element; and

– if the maximum number of waiting communications is not reached (i.e. UDUB condition has not occurred), the UE shall:

– provide a CW indication to the user;

– send a 180 (Ringing) response to the INVITE request according to the provisional response procedures described in 3GPP TS 24.229 [2];

– optionally, if the INVITE includes an Expires header field, use the value of this header field to provide the time to expiry information of the communication waiting to the user; and

– optionally start timer TUE-CW;

NOTE 1: The timer TUE-CW is used in order to limit the duration of the CW condition at the UE. For terminals that can provide an indication to the user that a CW condition is occurring without disturbing the active communication, this timer is not needed.

NOTE 2: RFC 5621 [9] describes conditions under which a 415 (Unsupported Media Type) response is returned.

The UE may insert an Alert-Info header field set to "<urn:alert:service:call-waiting>" according to RFC 7462 [131] in the 180 (Ringing) response, according to the provisional response procedures described in 3GPP TS 24.229 [2].

[TS 24.615 subclause 4.5.5.3.3]:

Case A

If user B accepts the waiting communication and holds (per procedures in 3GPP TS 24.610 [5]) or releases (per procedures in 3GPP TS 24.229 [2]) the active communication and timer TUE-CW has not expired, user B’s UE shall:

– stop timer TUE-CW (if it has been started);

– stop providing the CW indication to User B; and

– apply the procedures for answering the waiting communication to User B as described in 3GPP TS 24.229 [2].

Case B

If TUE-CW was started and expires, user B’s UE shall:

– stop providing the CW indication to User B; and

– send a 480 (Temporarily Unavailable) response towards User C, optionally including a Reason header field set to cause 19, in accordance with RFC 6432 [130].

[TS 24.615 subclause 4.5.5.3.4]:

If user B’s UE receives a CANCEL request or BYE request from User C during a CW condition, user B’s UE shall:

– stop timer TUE-CW (if necessary);

– stop providing the CW indication to User B; and

– apply the terminating UE procedures upon receipt of CANCEL or BYE as described in 3GPP TS 24.229 [2].

If user B’s UE receives a CANCEL request or BYE request from User A and during a CW condition, user B’s UE shall:

– stop timer TUE-CW (if necessary);

– stop providing the CW indication to User B;

– apply the terminating UE procedures upon receipt of CANCEL request or BYE request as described in 3GPP TS 24.229 [2]; and

– optionally apply the procedure for accepting the waiting communication as described in 3GPP TS 24.229 [2].

8.37.3 Test description

8.37.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 has registered to IMS and set up the 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 A.4.1.

8.37.3.2 Test procedure sequence

Table 8.37.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-7

Steps 1-7 of A.5.1 are executed.

–

–

–

–

8

Check: Does the UE responds to INVITE with 180 Ringing with an Alert-Info header field set to "<urn:alert:service:call-waiting>"

–>

180 Ringing

1

P

9

(Conditional) The SS shall send PRACK only if the 180 response contains 100rel option tag within the Require header.

<–

PRACK

–

–

10

(Conditional) The UE acknowledges the PRACK with 200 OK.

–>

200 OK

–

–

11

The UE is made to end the MO call

–

–

–

–

12

Check: Does the UE send a BYE to terminate its previous session?

(step 1 in Annex A.7)

–>

BYE

2

P

13

The SS responds to the BYE request with a valid 200 OK response.

(step 2 in Annex A.7)

<–

200 OK

–

–

14

UE is made to accept the incoming call

–

–

–

–

15

Check: Does the UE responds to INVITE with a 200 OK final response after the user answers the call.

–>

200 OK

3

P

16

The SS acknowledges the receipt of 200 OK for INVITE.

<–

ACK

–

–

8.37.3.3 Specific message content

Table 8.37.3.3-1: INVITE (Step 1, table 8.37.3.2-1)

Derivation Path: Annex A.5.1, Step 1

Header/param

Cond

Value/remark

Rel

Reference

Message-body

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

RFC 4566 [38]

Table 8.37.3.3-2: UPDATE (Step 6, table 8.37.3.2-1)

Derivation Path: Annex A.5.1, step 6

Header/param

Cond

Value/remark

Rel

Reference

Message-body

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

RFC 4566 [38]

Table 8.37.3.3-3: 180 Ringing (Step 8, table 8.37.3.2-1)

Derivation Path: TS 34.229-1 [2], Annex A.2.6, Conditions A2 and A14.

Header/param

Cond

Value/remark

Rel

Reference

Alert-Info

<urn:alert:service:call-waiting>

Table 8.37.3.3-4: PRACK (Step 9, table 8.37.3.2-1)

Derivation Path: TS 34.229-1 [2], Annex A.2.4, Condition A3

Header/param

Cond

Value/remark

Rel

Reference

Content-Length

value

0

Message-body

not present

Table 8.37.3.3-5: 200 OK (Step 10, table 8.37.3.2-1)

Derivation Path: TS 34.229-1 [2], Annex A.3.1, Conditions A2, A11 and A20.

Table 8.37.3.3-6: 200 OK (Step 15, table 8.37.3.2-1)

Derivation Path: TS 34.229-1 [2], Annex A.3.1, Conditions A1, A10 and A19.

Table 8.37.3.3-7: ACK (Step 16, table 8.37.3.2-1)

Derivation Path: TS 34.229-1 [2], Annex A.2.7, Condition A2.