4 Conferencing overview

24.1473GPPConferencing using the IP Multimedia (IM) Core Network (CN) subsystemRelease 17Stage 3TS

The basic services for the IP Multimedia core network Subsystem (IMS), as defined in 3GPP TS 24.229 [5], allow a user to initiate, modify and terminate media sessions based on the Session Initiation Protocol, as defined in RFC 3261 [7]. Although these basic mechanisms already allow multi party calls, more sophisticated services for communication between multiple parties can be made available by the network.

The conferencing service provides the means for a user to create, manage, terminate, join and leave conferences. It also provides the network with the ability to give information about these conferences to the involved parties.

The network operator or the user may apply membership and media policies to a conference. The functionality for conference policy control (with a respective standardised protocol) is felt to be essential for a complete IMS conferencing service but is not specified in this version of IMS conferencing and is for further study.

Conferencing applies to any kind of media stream by which users may want to communicate, this includes e.g. audio and video media streams as well as instant message based conferences or gaming. Floor control, as part of the conferencing service offers control of shared conference resources at the MRFP using BFCP.

The framework for SIP conferences is specified in RFC 4353 [8].

The architecture for the 3GPP conference service is specified in 3GPP TS 23.228 [6] and 3GPP TS 23.218 [3].

The present document specifies the usage of SIP, SDP and BFCP to realize 3GPP conference service based on the protocols specified by the IETF defined conference service as per RFCs listed in clause 2. However, since the IETF conference service has various scenarios and features as described in RFC 4353 [8], 3GPP conference service is a subset of the above IETF defined conference service.

Loosely coupled conferencing is outside the scope of this release of the IMS conferencing service.

The following figure depicts the functional split for SIP based conferences between the AS, the MRFC and the MRFP.

Figure 4.1: Functional split between the AS, MRFC and MRFP

The conference policy, conference notification server and top-level focus as specified in RFC 4353 [8] subclause 6 are located in the AS.

The MRFC has a conference policy and focus as specified in RFC 4353 [8] subclause 6.3.

The mixer and floor control server are located in the MRFP.