8.38 Communication Waiting and cancelling 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.38.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 receives CANCEL for incoming voice call }

then { UE responds with 200 OK and 487 Request Terminated responses }

}

8.38.2 Conformance Requirements

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

[TS 24.615 clause 1]:

The Communication Waiting (CW) service enables a user to be informed, that very limited resources are available for an incoming communication. The user then has the choice of accepting, rejecting or ignoring the waiting call (as per basic call procedures).

[TS 24.615 clause 4.2.1]:

When a communication arrives at the destination user, the UE validates the status of the user. If the user is already involved in one or more communications, the terminal notifies the served user of a communication waiting situation.

[TS 24.615 clause 4.5.5.3.2]:

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

[TS 24.615 clause 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.

8.38.3 Test description

8.38.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, registered to IMS and has set up an MO call with preconditions, by executing the generic test procedure in Table 4.9.15.2.2-1 of TS 38.508-1 [21].

8.38.3.2 Test procedure sequence

Table 8.38.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-7

MT Voice call setup takes place according to steps 1-7 of Annex A.5.1

8

Step 8 of Annex A.5.1 happens

–>

180 Ringing

1

P

9

Conditional Step: if UE sent 180 Ringing reliably, Step 9 of Annex A.5.1 happens

<–

PRACK

10

Conditional Step: if UE sent 180 Ringing reliably, Step 10 of Annex A.5.1 happens

–>

200 OK

11

SS sends CANCEL request to terminate INVITE transaction

<–

CANCEL

12

UE acknowledges CANCEL with 200 OK

–>

200 OK

13

The UE responds to INVITE with a 487 Request Terminated final response after transaction was terminated.

–>

487 Request Terminated

2

P

14

SS acknowledges the receipt of 487 Request Terminated

<–

ACK

15

The UE is made to release the call

16-17

UE releases the original MO call
(Annex A.7)

8.38.3.3 Specific message contents

Table 8.38.3.3-1: INVITE (Step 1, table 8.38.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.38.3.3-2: UPDATE (Step 6, table 8.38.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.38.3.3-3: 180 Ringing (step 8, table 8.38.3.2-1)

Derivation path: Step 8 of Annex A.5.1

Header/param

Cond

Value/remark

Rel

Reference

Alert-Info

<urn:alert:service:call-waiting>

RFC 7462 [39]

Table 8.38.3.3-4: CANCEL (step 11, table 8.38.3.2-1)

Derivation path: TS 34.229-1 [2], Table in subclause A.2.15

Table 8.38.3.3-5: 200 OK (step 12, table 8.38.3.2-1)

Derivation path: TS 34.229-1 [2], Table in subclause A.3.1 applying conditions A5 and A11

Table 8.38.3.3-6: 487 Request Terminated (step 13, table 8.38.3.2-1)

Derivation path: TS 34.229-1 [2], Table in subclause A.2.16

Table 8.38.3.3-7: ACK (step 14, table 8.38.3.2-1)

Derivation path: TS 34.229-1 [2], Table in subclause A.2.7 applying conditions A2 and A4