8.29 MT Video Call Hold without announcement / 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.29.1 Test Purpose (TP)

(1)

with { UE being registered to IMS and configured to use preconditions and having set up an MO video call }

ensure that {

when { UE receives re-INVITE including call hold instructions }

then { UE may send 100 Trying and sends 200 OK for re-INVITE }

}

(2)

with { UE having responded to re-INVITE for call hold }

ensure that {

when { UE receives ACK followed by re-INVITE including call resume instructions }

then { UE may send 100 Trying and sends 200 OK for re-INVITE }

}

(3)

with { UE having concluded the call resume procedure }

ensure that {

when { UE is being made to release the call }

then { UE sends BYE }

}

8.29.2 Conformance Requirements

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

[TS 24.610 clause 4.5.2.9]:

3GPP TS 24.229 [1] shall apply.

[TS 26.114 clause 7.3.1]:

RTCP packets should be sent for all types of multimedia sessions to enable synchronization with other RTP transported media, remote end-point aliveness information, monitoring of the transmission quality, and carriage of feedback messages such as TMMBR for video and RTCP APP for speech. The RR value should be set greater than zero to enable RTCP packets to be sent when media is put on hold and during active RTP media transmission, including real-time text sessions which may have infrequent RTP media transmissions.

[TS 24.229 clause 6.1.1]:

If the media line in the SDP message body indicates the usage of RTP/RTCP, and if the UE is configured to request an RTCP bandwidth level for the session is different than the default RTCP bandwidth as specified in RFC 3556 [56], then in addition to the "AS" bandwidth modifier in the media-level "b=" line, the UE shall include two media-level "b=" lines, one with the "RS" bandwidth modifier and the other with the "RR" bandwidth modifier as described in RFC 3556 [56] to specify the required bandwidth allocation for RTCP. The bandwidth-value in the b=RS: and b=RR: lines may include transport overhead as described in subclause 6.1 of RFC 3890 [152].

For other media streams the "b=" media descriptor may be included. The value or absence of the "b=" parameter will affect the assigned QoS which is defined in or 3GPP 29.213 [13C].

NOTE 3: In a two-party session where both participants are active, the RTCP receiver reports are not sent, therefore, the RR bandwidth modifier will typically get the value of zero.

8.29.3 Test description

8.29.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 Video 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.15.1.

8.29.3.2 Test procedure sequence

Table 8.29.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS sends INVITE with a SDP offer to hold the video call.

(Step 1 of Annex A.28)

<–

INVITE

2

Optional: The UE responds with a 100 Trying provisional response.

(Step 2 of Annex A.28)

–>

100 Trying

3

Check: Does the UE respond to INVITE with 200 OK to indicate that the UE is no more expecting to receive any media?

(Step 3 of Annex A.28)

–>

200 OK

1

P

4

The SS acknowledges the receipt of 200 OK for INVITE.

(Step 4of Annex A.28)

<–

ACK

5

SS sends INVITE with a SDP offer to resume the call

(Step 1 of Annex A.28)

<–

INVITE

6

Optional: The UE responds with a 100 Trying provisional response.

(Step 2 of Annex A.28)

–>

100 Trying

7

Check: Does the UE respond to INVITE with 200 OK to indicate that the UE resumes sending media (call resume)?

(Step 3 of Annex A.28)

–>

200 OK

2

P

8

The SS acknowledges the receipt of 200 OK for INVITE.

(Step 4 of Annex A.28)

<–

ACK

9

UE is made to release the call

10

Check: Does the UE send BYE to release the call?

(Step 1 of Annex A.7)

–>

BYE

3

P

11

The SS sends 200 OK for BYE.

(Step 2 of Annex A.7)

<–

200 OK

8.29.3.3 Specific message contents

None as fully described in Annex A.28 and A.7