8.31 Creating and leaving a conference / 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.31.1 Test Purpose (TP)

(1)

with { UE being registered to IMS }

ensure that {

when { UE is made to start a conference call }

then { UE sends INVITE to the conference factory and completes the conference call initiation and subscribes to conference event }

}

(2)

with { Conference call going on }

ensure that {

when { UE is made to leave the call }

then { UE sends BYE and processes notification for conf event if any }

}

8.31.2 Conformance Requirements

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

[TS 24.147, clause 5.3.1.3.1]:

A conference can be created by means of SIP, as described in subclause 5.3.1.3.2 or subclause 5.3.1.3.3.

NOTE: Additionally, creation of a conference can be provided by other means.

The conference participant shall make use of the procedures for session establishment as described in subclauses 5.1.2A and 5.1.3 of 3GPP TS 24.229 [5] when creating conferences by means of SIP.

[TS 24.147, clause 5.3.1.3.2]:

Upon a request to create a conference with a conference factory URI, the conference participant shall:

1) generate an initial INVITE request in accordance with subclause 5.1.3.1 of 3GPP TS 24.229 [5]; and

2) set the request URI of the INVITE request to the conference factory URI.

On receiving a 200 (OK) response to the INVITE request with the "isfocus" feature parameter indicated in Contact header, the conference participant shall store the content of the received Contact header as the conference URI. In addition to this, the conference participant may subscribe to the conference event package as described in RFC 4575 [11] by using the stored conference URI.

NOTE 1: A conference participant can decide not to subscribe to the conference event package for conferences with a large number of attendees, due to, e.g. the signalling traffic caused by the notifications about users joining or leaving the conference.

NOTE 2: A conference can also be created with a conference URI. The procedures for this case at the conference participant are identical to those for joining a conference, as described in subclause 5.3.1.4.1. It is not assumed that the conference participant is aware that the conference gets created in this case.

NOTE 3: The UE can discover the conference factory URI from the Management Object as defined in 3GPP TS 24.166 [38]. Further discovery mechanisms for the conference factory URI are outside the scope of the present document.

8.31.3 Test description

8.31.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.

Preamble:

– The UE is in test state 1N-A (TS 38.508-1) and registered to IMS.

8.31.3.2 Test procedure sequence

Table 8.31.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt an IMS Conference call

–

–

–

–

2

Check: Does the UE send INVITE with the first SDP offer?

(Step 1 of annex A.19)

–>

INVITE

1

P

3-14

UE and SS continue the procedures of conference call. (Steps 2-13 of annex A.19)

–

–

–

–

EXCEPTION: steps 11 – 14 (conference event subscription) describe optional behaviour depending on UE configuration. The SS shall wait up to 3s for the SUBSCRIBE of step 11

–

–

–

–

15

The UE is made to leave the conference

–

–

–

–

16

The UE leaves the conference with BYE

(Step 1 of annex A.27)

–>

BYE

2

P

17-19

The SS and UE continue to finish the procedures of leaving a conference.

(Steps 2-4 of annex A.27)

–

–

–

–

8.31.3.3 Specific message contents

None as fully specified in annex A.19 and A.27.