Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.379  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   4…   7…   7.4…   10…   10.5…   10.6…   10.6.2.2.18…   10.6.2.2.34…   10.6.2.3…   10.6.2.3.2…   10.6.2.4…   10.6.2.5…   10.6.2.6…   10.6.2.7…   10.6.2.9…   10.6.2.10…   10.6.3…   10.7…   10.7.2.2   10.7.2.3…   10.7.3…   10.7.4…   10.7.5…   10.7.6…   10.9…   10.9.1.3…   10.9.2…   10.10…   10.14…   A…   A.4…   B…

 

10.9  Floor control

10.9.1  Floor control for on-network MCPTT service

10.9.1.1  General

The procedure is for providing a floor control to MCPTT UE in an on-network case and applies for both private call and group call. Floor control is performed by using floor control information flows between the floor participant and the floor control server.

10.9.1.2  Information flows for floor control for on-network

10.9.1.2.1  General
When the floor control server receives a floor request from the floor participant, it decides whether to give a grant or not based on, e.g., the session status (i.e., whether the grant is given to another user or not), user profile, priority. The result is informed to the requesting floor participant. When the floor participant receives a floor granted message, it can send voice media over the uplink bearer established beforehand. The floor revoked message can be used as part of override. The floor queue status request can be used to know current position in the queue for floor.
Some floor control information flows can also piggyback call control information flows to provide efficient call setup and clearing:
  • Call setup request is optionally carried in floor request (uplink) or floor taken (downlink, can be broadcast); and
  • Call release request is optionally carried in floor release (uplink) or floor idle (downlink, can be broadcast).
Up
10.9.1.2.2  Floor requestWord‑p. 171
Table 10.9.1.2.2-1 describes the information flow floor request, from the floor participant to the floor control server and from the floor control server to the floor control server, which is used to request the floor for media transfer. This information flow is sent in unicast to the floor control server.
Information Element Status Description
MCPTT IDMRequester identity
Functional aliasOFunctional alias of the requester
Floor priorityMPriority of the request
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Location InformationOLocation information
Up
10.9.1.2.3  Floor granted
Table 10.9.1.2.3-1 describes the information flow floor granted, from the floor control server to the floor participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate that a request for floor is granted and media transfer is possible. This information flow is sent in unicast (to the granted floor participant).
Information Element Status Description
MCPTT IDMGranted party identity
Functional aliasOFunctional alias of the requester
DurationMThe time for which the granted party is allowed to transmit
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement requiredOIndicates if acknowledgement from the floor participant is required
Up
10.9.1.2.4  Floor rejected
Table 10.9.1.2.4-1 describes the information flow floor rejected, from the floor control server to the floor participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate that a request for the floor is rejected. This information flow is sent in unicast (to the refused floor participant).
Information Element Status Description
MCPTT ID (see NOTE)ORejected party identity
Functional alias (see NOTE)OFunctional alias of the requester
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Rejection causeOIndicates the cause for floor rejection
Acknowledgement requiredOIndicates if acknowledgement from the floor participant is required
Up
10.9.1.2.5  Floor request cancelWord‑p. 172
Table 10.9.1.2.5-1 describes the information flow floor request cancel, from the floor participant to the floor control server, which is used to request cancelling the floor request from the floor request queue. This information flow is sent in unicast to the floor control server.
Information Element Status Description
MCPTT IDMIdentity for the requester
Functional aliasOFunctional alias for the requester
List of MCPTT IDsMTarget identity (Identities) whose floor request is to be cancelled
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Up
10.9.1.2.6  Floor request cancel response
Table 10.9.1.2.6-1 describes the information flow floor request cancel response, from the floor control server to the floor control participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate the response for the floor request cancellation. This information flow is sent in unicast.
Information Element Status Description
MCPTT IDMIdentity of party that initiated the cancellation request
Functional aliasOFunctional alias of the requester
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement requiredOIndicates if acknowledgement from the floor participant is required
Up
10.9.1.2.7  Floor request cancel notify
Table 10.9.1.2.7-1 describes the information flow floor request cancel notify, from the floor control server to the floor control participant, which is used to indicate the floor request is cancelled by the administrator/floor control server. This information flow is sent in unicast or broadcast.
Information Element Status Description
MCPTT IDMIdentity of the administrator
Functional aliasOFunctional alias of the administrator
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement requiredOIndicates if acknowledgement from the floor participant is required
Up
10.9.1.2.8  Floor idle
Table 10.9.1.2.8-1 describes the information flow floor idle, from the floor control server to the floor participant, which is used to indicate that a session is in idle status, i.e. the floor is not granted to any party. This information flows is sent in unicast or broadcast.
Information Element Status Description
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement requiredOIndicates if acknowledgement from the floor participant is required
Up
10.9.1.2.9  Floor releaseWord‑p. 173
Table 10.9.1.2.9-1 describes the information flow floor release, from the floor participant to the floor control server, which is used to indicate the media transfer is completed and floor is released. This information flow is sent in unicast to the floor control server.
Information Element Status Description
MCPTT IDMIdentity of party that initiated the cancellation request
Functional aliasOFunctional alias of the requester
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Up
10.9.1.2.9a  Multi-talker floor release |R15|
Table 10.9.1.2.9a-1 describes the information elements of floor release for multi-talker control, from the floor control server to the floor participants, which is used to indicate the media transfer is completed and floor is released. This information flow is sent in unicast from the floor control server.
Information Element Status Description
MCPTT ID (NOTE)MIdentity of participant releasing the floor
List of functional aliases (NOTE)OFunctional alias(es) of participant releasing the floor
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Up
10.9.1.2.10  Floor taken
Table 10.9.1.2.10-1 describes the information flow floor taken, from the floor control server to the floor participant, which is used to indicate the floor is granted to another MCPTT user. This information flows is sent in unicast or broadcast.
Information Element Status Description
MCPTT IDMIdentity for the granted party
Functional aliasOFunctional alias for the granted party
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Permission to request the floorOIndicates whether receiving parties are allowed to request the floor or not (e.g. broadcast call)
Acknowledgement requiredOIndicates if acknowledgement from the floor participant is required
Location InformationOLocation information
Up
10.9.1.2.10a  Multi-talker floor taken |R15|Word‑p. 174
Table 10.9.1.2.10a-1 describes the information elements of floor taken for multi-talker control, from the floor control server to the floor participant, which is used to indicate when the floor is simultaneously granted to multiple MCPTT users. The multi-talker floor taken is sent in unicast or broadcast.
Information Element Status Description
List of MCPTT IDs (NOTE)MIdentity (identities) of the granted participant(s)
List of functional aliases (NOTE)OFunctional alias(es) of the granted participant(s)
List of source identifiers (NOTE)OIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement requiredOIndicates if acknowledgement from the floor participant is required
Up
10.9.1.2.11  Floor revoked
Table 10.9.1.2.11-1 describes the information flow floor revoked, from the floor control server to the floor participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate the floor is revoked from its current holder (the floor participant who was granted the floor). This information flows is sent in unicast (to the revoked floor participant).
Information Element Status Description
MCPTT IDMRevoked party identity
Functional aliasOFunctional alias of the requester
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement requiredOIndicates if acknowledgement from the floor participant is required
Up
10.9.1.2.12  Floor acknowledgement
Table 10.9.1.2.12-1 describes the information flow floor acknowledgement, from the floor participant to the floor control server, which is used to provide an acknowledgement if the acknowledgement is required in the received floor control message.
Information Element Status Description
MCPTT IDMIdentity of the sender
Functional aliasOFunctional alias of the sender
Up
10.9.1.2.13  Queue position request
Table 10.9.1.2.13-1 describes the information flow queue position request, from the floor participant to the floor control server and from the floor control server to the floor control server or MC gateway server, which is used to request the position in the floor request queue. The MCPTT server and the MCPTT client support queuing of the floor control requests shall support this information flow. This information flow is sent in unicast to the floor control server.
Information Element Status Description
MCPTT IDMIdentity of party whose floor position is requested
Functional aliasOFunctional alias of the requester
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Up
10.9.1.2.14  Queue position infoWord‑p. 175
Table 10.9.1.2.14-1 describes the information flow queue position info, from the floor control server to the floor participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate the floor request is queued and the queue position to the floor requesting UE. The MCPTT server and the MCPTT client support queuing of the floor control requests shall support this information flow. This information flows is sent in unicast (to the queued floor participant).
Information Element Status Description
MCPTT IDMIdentity of party whose floor position is provided
Functional aliasOFunctional alias of the requester
Queue position infoMPosition of the queued floor request in the queue
Source identifierOIdentifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Acknowledgement required O Indicates if acknowledgement from the floor participant is required
Up
10.9.1.2.15  Unicast media stop request |R15|
Table 10.9.1.2.15-1 describes the information flow unicast media stop request from the floor participant to the floor control server, which is used by the floor participant to indicate that the unicast media flow of the designated communication does not need to be sent to the MCPTT client.
Information Element Status Description
MCPTT IDMIdentity of the requester
Functional aliasOFunctional alias for the requester
Source identifierOIdentifies the communication whose media flow is to be stopped, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Up
10.9.1.2.16  Unicast media resume request |R15|
Table 10.9.1.2.16-1 describes the information flow unicast media resume request from the floor participant to the floor control server, which is used by the floor participant to request that the unicast media flow of the designated communication is to be sent to the MCPTT client.
Information Element Status Description
MCPTT IDMIdentity of the requester
Functional aliasOFunctional alias of the requester
Source identifierOIdentifies the communication whose media flow is to be resumed, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Up

Up   Top   ToC