Content for  TS 23.333  Word version:  17.1.0

The set of data to establish a BFCP connection shall be exchanged in accordance with RFC 4583. A Floor control connection, which requires a BFCP/TCP protocol termination property, shall be established between the UE and the Floor Control Server, located in the MRFP. The MRFC shall initiate the "Configure BFCP Termination" procedure as specified in clause 8.44 to indicate to the MRFP the remote Floor control Client connection address and request the local Floor control Client connection address. The MRFP shall return the local Floor control Client connection address to the MRFC. The Floor control connection may be initiated by the UE or the MRFP (FCS).

• It is a prerequisite that the conference is configured using "Configure Conference for Floor Control" procedure as described in clause 6.2.13.2.2, which is used to set the common data of the conference for Floor control.

The combined sequence is shown in Figure 6.2.13.2.1.1.

The "Configure Conference For Floor Control" procedure, specified in Clause 8.45 shall be used to set up a conference and to modify FCS properties such as the Floor Control Policy. The procedure defines common data for all BFCP users, these properties are defined on Context level. The common data include:

• Floor-Resource Associations, which indicates the correlation between Floor ID and media properties for the MRFP to identify the Floor(s) when receiving BFCP requests and notifying the MRFC of decisions to change the floor permissions for a given user (termination).
• Conference Identifier, which indicates the Conference Identifier for the BFCP client to identify the conference when sending BFCP requests.

Floor Control Policy. This consists of:

• The Floor control algorithm to be used in granting the Floor, either:
• The FCFS algorithm or
• The chair-controlled algorithm.
• The maximum number of users who can hold the Floor at the same time.

Figure 6.2.13.2.2.1 shows the message sequence chart example for configuring a conference for Floor control.

If the Floor Control Policy indicates that the conference is Chair-controlled, the MRFC shall indicate to the MRFP which termination represents the Floor Chair and which Floor(s) the Floor Chair controls using the "Designate Floor Chair" procedure as specified in clause 8.46. The MRFC may also change the Floor Chair as needed using the "Designate Floor Chair" procedure as specified in clause 8.46. It is a prerequisite that the conference is configured and the termination configured for BFCP using "Configure Conference for Floor Control" and "Configure BFCP Termination" procedures respectively. Figure 6.2.13.2.3.1 shows the message sequence chart example for designating Floor Chair.

The MRFC shall request the MRFP to notify the decision of Floor request using the "Floor Decision Request" procedure as specified in clause 8.47. The MRFP shall then notify the MRFC the outcome of the Floor Request, when the FCS has made the decision to change the status to "Granted", "Released" or "Revoked" (The status is defined as REQUEST-STATUS in RFC 4582), using the "Report Floor Status Decision" procedure as specified in clause 8.48. The Floor Request Decision information is used by the MRFC to decide how to set the media properties of the associated Termination/Stream on the MRFP. The MRFP shall indicate the Floor Identity or Identities to which the Floor decision is associated. The MRFP sends one notification per Floor decision for a given termination and only one notification per termination shall be outstanding at any time. Figure 6.2.13.2.4.1 shows the message sequence chart example for requesting and reporting Floor Request decisions.

The MRFC modifies media properties associated with the Floor Request Decision received from the MRFP using the "Modify Media" procedure defined in Clause 8.59; this will be either adding permissions if the "status" was granted or removing the permissions if the "status" was revoked or released. The MRFC shall indicate to the MRFP when it has successfully modified the media properties based on the provided Floor Request Decisions notification using the "Confirm Media Update" procedure as specified in clause 8.49. The MRFP shall then modify the Floor status of the associated Client. Figure 6.2.13.2.5.1 shows the message sequence chart example for modifying the media and confirming media update based on Floor Request status.