8 Protocol for floor control for conferencing

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

8.1 Introduction

Support of floor control is optional for participants and MRFP.

8.2 Functional entities

8.2.1 User Equipment (UE)

A UE may support the floor participant (see subclause 8.3.1) or floor chair role (see subclause 8.3.2). A floor chair may, but need not, be a floor participant.

8.2.2 Media Resource Function Processor (MRFP)

An MRFP may support the floor control server role (see subclause 8.3.3), the floor chair role (see subclause 8.3.2), or the floor participant role (see subclause 8.3.1).

8.3 Role

8.3.1 Floor participant

The floor participant shall support general client operations and floor participant operations as described in RFC 4582 [28].

BFCP messages shall be sent on any IP-CAN transport used for media in accordance with subclause 9.2.2 of 3GPP TS.24.229 [5].

8.3.2 Floor chair

The floor chair shall support client operations and floor chair operations as described in RFC 4582 [28].

BFCP messages shall be sent on any IP-CAN transport used for media in accordance with subclause 9.2.2 of 3GPP TS.24.229 [5].

8.3.3 Floor control server

The floor control server shall support floor control server operations as described in RFC 4582 [28].

NOTE: It is out of scope of this version of the document how the floor control server discovers the floor control policy of the conference, and how the floor control server manipulates the media policy of the conference due to changes in the status of any floor.

Annex A (informative):
Example signalling flows of conferencing operation