hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2.2 Floor request
|
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.
Table 10.9.1.2.2-1: Floor request
Information element
Status
Description
MCPTT ID
M
Requester identity
Functional alias
O
Functional alias of the requester
Floor priority
M
Priority of the request
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Location Information
O
Location information
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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).
Table 10.9.1.2.3-1: Floor granted
Information element
Status
Description
MCPTT ID
M
Granted party identity
Functional alias
O
Functional alias of the requester
Duration
M
The time for which the granted party is allowed to transmit
Source identifier
O
Identifies 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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).
Table 10.9.1.2.4-1: Floor rejected
Information element
Status
Description
MCPTT ID (see NOTE)
O
Rejected party identity
Functional alias (see NOTE)
O
Functional alias of the requester
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Rejection cause
O
Indicates the cause for floor rejection
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
NOTE: MCPTT ID is present, and functional alias may be present, in messages between the floor control servers in different MCPTT systems, and between floor control server and MC gateway server.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2.5 Floor request cancel
|
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.
Table 10.9.1.2.5-1: Floor request cancel
Information element
Status
Description
MCPTT ID
M
Identity for the requester
Functional alias
O
Functional alias for the requester
List of MCPTT IDs (see NOTE)
O
Target identity (identities) whose floor request is to be cancelled
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
NOTE: If this information element is not present all the entries in the floor request queue are cancelled.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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.
Table 10.9.1.2.6-1: Floor request cancel response
Information element
Status
Description
MCPTT ID
M
Identity of party that initiated the cancellation request
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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.
Table 10.9.1.2.7-1: Floor request cancel notify
Information element
Status
Description
MCPTT ID
M
Identity of the administrator
Functional alias
O
Functional alias of the administrator
Source identifier
O
Identifies 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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.
Table 10.9.1.2.8-1: Floor idle
Information element
Status
Description
Source identifier
O
Identifies 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2.9 Floor release
|
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.
Table 10.9.1.2.9-1: Floor release
Information element
Status
Description
MCPTT ID
M
Identity of party that initiated the cancellation request
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
10.9.1.2.9a Multi-talker floor release
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.
Table 10.9.1.2.9a-1: Multi-talker floor release
MCPTT ID (see NOTE)
M
Identity of participant releasing the floor
List of functional aliases (see NOTE)
O
Functional alias(es) of participant releasing the floor
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
NOTE: One or more functional aliases may be associated with the MCPTT ID.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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.
Table 10.9.1.2.10-1: Floor taken
Information element
Status
Description
MCPTT ID
M
Identity for the granted party
Functional alias
O
Functional alias for the granted party
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
Permission to request the floor
O
Indicates whether receiving parties are allowed to request the floor or not (e.g. broadcast call).
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
Location Information
O
Location information
10.9.1.2.10a Multi-talker floor taken
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.
Table 10.9.1.2.10a-1: Multi-talker floor taken
Information element
Status
Description
List of MCPTT IDs (see NOTE)
M
Identity (identities) of the granted participant(s)
List of functional aliases (see NOTE)
O
Functional alias(es) of the granted participant(s)
List of source identifiers (see NOTE)
O
Identifies 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
NOTE: One or more functional aliases and one source identifier may be associated with an MCPTT ID.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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).
Table 10.9.1.2.11-1: Floor revoked
Information element
Status
Description
MCPTT ID
M
Revoked party identity
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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.
NOTE: The floor acknowledgement flow can be sent by the floor participant after each floor control information flow that includes an indication that an acknowledgement is required. The procedures defined in subclauses 10.9.1.3 to 10.9.1.5 do not explicitly illustrates all scenarios when floor acknowledgement can be used.
Table 10.9.1.2.12-1: Floor acknowledgement
Information element
Status
Description
MCPTT ID
M
Identity of the sender.
Functional alias
O
Functional alias of the sender.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
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.
Table 10.9.1.2.13-1: Queue position request
Information element
Status
Description
MCPTT ID
M
Identity of party whose floor position is requested
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2.14 Queue position info
|
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 and optionally to the authorized user. 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 queued floor participant and optionally to the authorized user).
Table 10.9.1.2.14-1: Queue position info
Information element
Status
Description
MCPTT ID
M
Identity of party whose floor position is provided
Functional alias
O
Functional alias of the requester
Queue position info
M
Position of the queued floor request in the queue
Source identifier
O
Identifies 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2.15 Unicast media stop request
|
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.
Table 10.9.1.2.15-1: Unicast media stop request
Information element
Status
Description
MCPTT ID
M
Identity of the requester
Functional alias
O
Functional alias for the requester
Source identifier
O
Identifies 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2.16 Unicast media resume request
|
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.
Table 10.9.1.2.16-1: Unicast media resume request
Information element
Status
Description
MCPTT ID
M
Identity of the requester
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies 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
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.2.17 floor revoke request
|
Table 10.9.1.2.17-1 describes the information flow floor revoke request, from an authorized floor participant user to floor control server, which is used to revoke the floor from its current holder (the floor participant who was granted the floor).
Table 10.9.1.2.17-1: Floor revoke request
Information element
Status
Description
MCPTT ID
M
The identity of the user who requests to revoke the floor from another talker
MCPTT ID
M
Revoked party identity
Functional alias
O
Functional alias of the requester
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.3 Floor control with a single floor control server
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.3.1 Floor request, floor granted and floor taken during an MCPTT session
|
Figure 10.9.1.3.1-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participant and the floor control server. Only three UEs involved in the session are shown for the simplicity.
Pre-condition:
1. MCPTT session is established between MCPTT clients (client A, client B and client C) and MCPTT server.
2. The user at MCPTT client C is an authorized user (e.g., dispatcher) allowed to remove a floor request of other MCPTT users from the floor queue and can receive notifications about another user when their floor request is queued, when their queued floor request is rejected and when their queued floor request is removed from the queue.
Figure 10.9.1.3.1-1: Floor request, floor granted, floor taken during an MCPTT session
1. The floor control is established between the floor participants and floor control server. It is assumed that the floor is now in idle status.
2. Floor participant A wants to send voice media over the session.
3. Floor participant A sends a floor request message to floor control server which includes floor priority and other information as necessary.
4. Floor control server makes the determination on what action (grant, deny, or queue) to take on the request based on criteria (e.g., floor priority, participant type) and determines to accept the floor request from floor participant A. The floor control server may limit the time a user talks (hold the floor) as allowed by the configuration.
5a. Floor control server responds with a floor granted message to floor participant A including the maximum floor granted duration e.g., if no other floor participant has the permission for transmission.
5b. Floor control server sends a floor taken message to the other floor participant (floor participant B) including information about who is granted the floor.
5c. Floor participant A sends a floor acknowledgement if indicated to do so by the floor granted message.
5d. Floor participant B sends a floor acknowledgement if indicated to do so by the floor taken message.
5e. Floor control server sends a floor taken message to the other floor participant (floor participant C) including information about who is granted the floor.
5f. Floor participant C sends a floor acknowledgement if indicated to do so by the floor taken message.
6a. The floor granted shall cause the user of UE A where the floor participant A is located to be notified.
6b. The receipt of the floor taken may be used to inform the user of UE B where the floor participant B is located.
6c. The receipt of the floor taken may be used to inform the user of UE C where the floor participant C is located.
7. Floor participant A starts sending voice media over the session established beforehand.
NOTE 1: Voice media can continue to be sent while steps 8 through 11 occur.
8. Suppose there are one or more users requesting to talk at this time, the floor request(s) are queued as decided by floor control server e.g., based on floor priority.
9. Floor participant B sends a floor request message.
10. Floor control server queues the request of floor participant B.
11a. Floor control server sends queue position info to floor participant B.
11b. Floor participant B sends a floor acknowledgement if indicated to do so by the queue position info message.
12. Floor control server may send the queue position info to floor participant C who is an authorized user to indicate floor participant user B's floor request is queued.
13. Floor participant C sends a floor acknowledgement if indicated to do so by the queue position info message.
NOTE 2: If the floor participant user B's queued floor request is rejected after de-queue from the floor control queue then the floor control server may send the queue position info to floor participant C who is an authorized user. The floor queue position info message should indicate that floor participant user B's queued floor request is no longer queued.
10.9.1.3.1a Floor request, floor granted and multi-talker floor taken during an MCPTT session enhanced with multi-talker control
Figure 10.9.1.3.1a-1 shows the high level procedure that allows several participants to talk simultaneously in a MCPTT session already established between the floor participant and the floor control server. Three UEs involved in the session are shown for simplicity.
Pre-conditions:
1. The MCPTT group is configured to support multi-talker control and audio mixing by the network is applied.
2. MCPTT session is established between MCPTT clients (client A, client B and client C) and MCPTT server.
3. Participants and A and B have the permission to talk to all other participants and the floor is granted to floor participant B.
Figure 10.9.1.3.1a-1: Floor request, floor granted and multi-talker floor taken during an MCPTT session
1. Floor participant B is talking and is sending the voice media.
2. Floor participant A wants to send voice media over the session.
3. Floor participant A sends a floor request message to the floor control server which includes the necessary information, e.g. floor priority.
4. Based on applicable criteria (e.g. floor priority, participant type, allowance to transmit, maximum number of simultaneous talkers) floor control server determines what action (grant, deny, or queue) shall be applied to the request. In this case, the floor request from floor participant A will be accepted. Simultaneous floor requests to transmit are handled in a sequential order. Based on the group configuration repository data, the floor control server may limit the time a floor participant is allowed to talk.
5a. Floor control server responds with a floor granted message to floor participant A.
5b. Floor control server sends a multi-talker floor taken message to floor participant B.
5c. Floor control server sends a multi-talker floor taken message to floor participant C.
5d. Floor control server may send a multi-talker floor taken message to floor participant A.
6a. The floor granted shall cause the user of UE A, where the floor participant A is located, to be notified.
6b. The multi-talker floor taken shall inform the user of UE B, that the floors are granted to other floor participants, but the floor is not revoked.
6c. The multi-talker floor taken shall inform the user of UE C floor participants list the floor are currently granted to.
7. Floor participant A starts sending voice media over the session established beforehand, i.e. participants A and B receive and transmit voice media; participant C only receives voice media.
NOTE: Floor control is independent from whether audio mixing is performed by the MCPTT server or by the UE.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.3.2 Floor override
|
10.9.1.3.2.1 Floor override using floor revoked (also floor rejected) during an MCPTT session
Figure 10.9.1.3.2.1-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participant (with floor granted to floor participant B) and the floor control server (with an override based on priority). Only two UEs involved in the session are shown for the simplicity.
Figure 10.9.1.3.2.1-1: Floor override using floor revoked (also floor rejected) during an MCPTT session
1. It is assumed that floor participant B has been given floor and is transmitting voice media.
2. Floor participant A having a priority which is relatively higher than that of floor participant B wants to send voice media over the session.
3. Floor participant A sends a floor request message to the floor control server.
4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the priority information that is received in the floor request message. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission from floor participant B.
5. The user of floor participant B may be notified that the floor is revoked.
6. The Floor control server sends a floor granted message to floor participant A, while sending a floor taken message to floor participant B with information of who is granted the floor.
7. The user of floor participant A may be notified that he is granted the floor. Similarly, the user of floor participant B may be notified who is granted the floor.
8. Floor participant A starts sending voice media over the session established beforehand.
9. Now floor participant B may want the floor to start sending voice media.
10. Floor participant B sends a floor request message to floor control server which may include priority information.
11. Floor control server determines whether to accept the floor request from floor participant B based on arbitration result e.g., according to the priority information that is received in the floor request message.
12. The floor control server responds with a floor rejected message to floor participant B.
13. Floor participant B may be notified that he is rejected.
10.9.1.3.2.2 Floor override without using floor revoked during an MCPTT session
Figure 10.9.1.3.2.2-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participants (with floor granted to floor participant B) and the floor control server (with an override based on priority and configured to permit the transmission of the overridden floor participant B to continue). Only two UEs involved in the session are shown for the simplicity.
Pre-conditions
- The floor control server has been configured to support override.
- The override supported in this case permits both the overridden floor participant and the overriding floor participant to be transmitting.
Figure 10.9.1.3.2.2-1: Floor override (overridden continues to transmit) during an MCPTT session
1. It is assumed that floor participant B has been given the floor and is transmitting voice media.
2. Floor participant A having a floor priority which is relatively higher than that of floor participant B wants to send voice media over the session.
3. Floor participant A sends a floor request message to the floor control server.
4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the floor priority information that is received in the floor request message.
5a. Floor control server responds with a floor granted message to floor participant A.
5b. Floor control server sends a floor taken message to the other floor participants (including floor participant B). Floor participant B continues transmitting the (overridden) voice media transmission.
NOTE 1: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn who the newly granted talker (overriding) is.
6a. The floor granted causes the user of floor participant A to be notified.
6b. The user of floor participant B is notified of the status that the floor is now taken by floor participant A.
7. Floor participant A (overriding) starts sending voice media over the session established beforehand.
NOTE 2: Floor participant B is still sending voice (overridden). The list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration.
10.9.1.3.2.3 Floor override using floor revoked (also floor rejected) during an MCPTT session enhanced with multi-talker control
Figure 10.9.1.3.2.3-1 shows the high-level procedure that the floor control allows several participants to talk simultaneously in a MCPTT session already established between the floor participant (with floor granted to floor participant B) and the floor control server. Only two UEs involved in the session are shown for the simplicity.
Pre-conditions:
1. The MCPTT group is configured to support multi-talker control.
2. MCPTT session is established between MCPTT clients (client A, client B and client C) and MCPTT server.
3. The maximum number of simultaneous talkers is set to 2.
4. The floor priority of floor participant A is higher than of floor participant B.
5. The floor is granted to floor participant B and floor participant C.
Figure 10.9.1.3.2.3-1: Floor override using floor revoked (also floor rejected) during an MCPTT session
1. Floor participant B and floor participant C are sending voice media over the session established.
2. Floor participant A wants to send voice media over the session.
3. Floor participant A wants to talk (i.e. send voice media) over the session. Floor participant A sends a floor request message to the floor control server.
4. Based on an arbitration result (e.g. per the priority information that is received in the floor request message), the floor control server determines to accept the floor request from floor participant A. The maximum number of simultaneous talkers in the MCPTT group has been reached, the floor control server decides to apply the override mechanism.
5. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission of floor participant B.
6. The user of floor participant B may be notified that the floor is revoked.
7. The Floor control server sends a floor granted message to floor participant A, while sending a multi-talker floor taken message to floor participant B and floor participant C including the information to whom the floor has been granted.
8. The user of floor participant A may be notified that the floor has been granted to him. Similarly, the user of floor participant B and floor participant C may be notified to whom the floor has been granted.
9. Floor participant A starts sending voice media over the session established beforehand.
10. Now floor participant B may want the floor to start sending voice media.
11. Floor participant B sends a floor request message to floor control server that may include participant priority information.
12. Based on arbitration result, e.g. per the priority information that is received in the floor request message, and if the number of MCPTT Users has already reached the maximum number of simultaneous talkers in the group, the floor control server determines whether to accept or reject the floor request from floor participant B. Due to lower priority of participant B and the applicable limitation of simultaneous talkers, the floor control server rejects the floor request.
13. The floor control server responds with a floor rejected message to floor participant B.
14. Floor participant B may be notified about the floor rejection.
NOTE: Floor control procedure is independent from whether audio mixing is performed by the MCPTT server or by the UE.
10.9.1.3.2.4 Floor release during an MCPTT session enhanced with multi-talker control
Figure 10.9.1.3.2.4-1 shows the high-level procedure where the floor controller allows a participant to release the floor while other participants continue to talk simultaneously in a MCPTT session already established between the floor participants and the floor control server. Only three UEs involved in the session are shown for simplicity.
Pre-conditions:
1. The MCPTT group is configured to support multi-talker control and audio mixing by the network is applied.
2. MCPTT session is established between MCPTT clients (client A, client B, and client C) and the MCPTT server.
3. Participants A, B, and C have the permission to talk to all other participants, and the floor is granted to floor participants A, B, and C.
Figure 10.9.1.3.2.4-1: Floor release during an MCPTT session
1. Floor participants A, B and C are sending voice media over the established session.
2. User A stops talking and wants to stop sending voice media over the session.
3. Floor participant A sends a floor release message to the floor control server.
4. The floor control server accepts the floor release from floor participant A and sends a multi-talker floor release message to floor participant B and floor participant C.
4a. The users of floor participant B and floor participant C may be notified that floor participant A has released the floor.
5. Floor participants B and C continue sending voice media over the established session.
NOTE: Floor control procedures are independent from whether audio mixing is performed by the MCPTT server or by the UE.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.3.3 Queue position during an MCPTT session
|
Figure 10.9.1.3.3-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between MCPTT clients (with floor granted to floor participant B) and server (with an override based on priority at floor control server). Only two UEs involved in the session are shown for the simplicity.
Figure 10.9.1.3.3-1: Queue status during an MCPTT session
1. It is assumed that floor participant B has been given a floor granted and is transmitting voice media. There are several other floor participants (including floor participating A) requesting floor which get queued at the floor control server.
2. Floor participant A would like to know its current position in the floor request queue.
3. Floor participant A sends a queue position request message to the floor control server.
4. Floor control server determines the current queue position of floor participant A from the floor request queue.
5. Floor control server responds with the current position in queue position info message.
6. User at floor participant A is informed about the current queue position.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.3.4 Floor request cancellation from the floor request queue
|
10.9.1.3.4.1 Floor request cancellation from the queue – MCPTT user initiated
Figure 10.9.1.3.4.1-1 illustrates the procedure for floor request cancellation from the floor queue initiated by the MCPTT user. The MCPTT user may be an authorized user who has rights to cancel the floor requests of other MCPTT users, whose floor requests are in floor control queue.
Pre-conditions:
- It is assumed that floor participant B has been granted the floor and is transmitting voice media. There are several other floor participants (including floor participant A and floor participant C) requesting the floor which have been queued at the floor control server.
Figure 10.9.1.3.4.1-1: Floor request cancellation from queue initiated by MCPTT user
1. The floor participant A wants to remove the floor request from the floor request queue. If floor participant A is an authorized MCPTT user with the rights to cancel another MCPTT user's floor request, the authorized MCPTT user may request floor request cancellation for one or more floor participants, whose floor request needs to be removed from the floor queue.
2. The floor participant A sends a floor request cancel (initiating MCPTT ID) message to the floor control server. If the floor participant A wants to remove the floor request(s) of other participant(s), the target participant(s)' MCPTT ID should be included in this message.
3. The floor control server shall check whether the requesting floor participant has authorization to cancel the floor request(s). If authorized, the floor request(s) will be removed from the floor request queue. When current transmission is completed, floor control server will process the floor request from the updated floor request queue.
4. If the floor request cancel in step 2 is sent by an authorized user (e.g., dispatcher) to cancel the floor request(s) of other participant(s) from the floor request queue, the floor request cancel notify message is sent to the floor participant whose floor request was cancelled from the floor queue. The floor request cancel notify message is also sent to the authorized user (not shown in figure) if the floor request cancel in step 2 is sent by the floor participant A is an initiating MCPTT user.
5. The floor control server provides a floor request cancel response to the floor participant A when the floor cancellation is completed. Optionally, the new queue position information may be notified to the floor participants whose floor requests are in the floor request queue (not shown in the figure).
10.9.1.3.4.2 Floor request cancellation from the queue - floor control server initiated
Figure 10.9.1.3.4.2-1 illustrates the procedure for floor request cancellation from the queue initiated by the floor control server. Only three UEs involved in the session are shown for the simplicity.
Pre-conditions:
- MCPTT session is established between MCPTT clients (client A, client B, client C and client D) and MCPTT server.
- It is assumed that floor participant B (not shown in figure) has been granted the floor and is transmitting voice media. There are several other floor participants (including floor participant A and participant C) requesting the floor which have been queued at the floor control server.
- The user at MCPTT client D is an authorized user (e.g., dispatcher) allowed to remove a floor request of other MCPTT users from the floor queue and can receive notifications about another user when their floor request is queued, when their queued floor request is rejected and when their queued floor request is removed from the queue.
Figure 10.9.1.3.4.2-1: Floor request cancellation from queue initiated by floor control server
1. The floor control server removes the floor request from the floor request queue based on policy. e.g., expiration of a timer. In the case when floor control server receives repeated floor requests from a floor participant while the floor is occupied, the new floor request is accepted and added into the floor queue and the existing/former floor request is removed from the floor queue or the new floor request is rejected and the existing/former floor request of this floor participant is retained in the floor request queue.
2. The floor control server sends a floor request cancel notify to the floor participant(s) whose floor request is removed from the floor request queue.
3. Optionally, the newly queue position information is notified to the other floor participants whose floor requests are queued.
4. If the floor request cancel in step 2 is sent by floor control server for the user whose floor request is in the floor request queue, the floor control server may send the floor cancel notify to the floor participant D who is an authorized user.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.3.5 Floor idle during an MCPTT session
|
During silence (when no talk burst is ongoing), the floor control server may send floor idle message to all floor participants from time to time.
Figure 10.9.1.3.5-1 shows the high level procedure that the floor idle is conducted for the MCPTT session already established between the floor participant and the floor control server. Only three MCPTT UEs involved in the session are shown for the simplicity.
Pre-condition:
1. The floor control is established between the floor participants and floor control server.
2. The floor participant A is granted the floor.
Figure 10.9.1.3.5.1-1: Floor idle during an MCPTT session
1. User A stops talking and wants to stop sending voice media over the session. The floor participants A sends the floor release message to the floor control server.
2. The floor control server determines the floor is idle, e.g., all the floor requests are processed and no new floor request is received. For multi-talker control case, the floor control server determines that the floor participant A was the last talker.
3. The floor control server sends the floor idle message to the participants.
4. Floor participants may notify the MCPTT users that the floor is idle.
NOTE: Floor idle may be sent multiple times during the MCPTT session.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.3.6 Floor revoke by the authorized user
|
Figure 10.9.1.3.6-1 shows the high level procedure that the floor granted to a talker user is revoked by the authorized user. Only three MCPTT UEs involved in the session are shown on the figure for the simplicity.
Pre-condition:
1. The participant B is granted the floor and transmitting the voice media to the group.
2. For multi-talker case, there may be other talkers in the group communication.
Figure 10.9.1.6.1-1: Floor revoke by authorized user
1. The authorized user at floor participant A sends floor revoke request message to revoke the floor of floor participant B. The identity of the floor participant B whose floor is to be revoked is included.
2. The floor control server checks the floor participant A is authorized to perform the floor revoke.
3. The floor control server sends the floor revoked message towards the floor participant B, and the floor participant B notifies the MCPTT user about the floor is revoked.
4. The floor control server sends the floor idle to the other participants, and the MCPTT user is notified about the floor is idle.
In multi-talker case it is also possible there are other remaining active talkers holding the floor. In such a case, the floor control server sends a Multi-talker floor release message to the other participants.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.4 Floor control with multiple floor control servers
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.4.1 Partner MCPTT system routes all floor control messages to primary MCPTT system's floor control server
|
The MCPTT users belonging to different groups in multiple MCPTT systems will participate in MCPTT media services (group communication, private calls, etc.) in scenarios like group hierarchies and temporary groups formed by group regroup. In this service delivery model involving multiple groups from different MCPTT systems, the floor control arbitration resides with the primary MCPTT system. This is determined in the group call setup stage. The MCPTT users of groups involved in the call session will transmit their floor control messages through the partner MCPTT systems to which they belong. In this scenario, the partner MCPTT systems request the floor control for its MCPTT user(s) from the floor control server of the primary MCPTT system. The protocol used for media plane signalling is non-SIP like RTCP.
Figure 10.9.1.4.1-1 describes the procedure for floor control involving groups from multiple MCPTT systems.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share all information of their users' to the primary MCPTT system (public information would still need to be shared).
2. The group 1 is hosted by primary MCPTT system and group 2 and 3 are hosted by the partner MCPTT system.
3. The floor participant 1 corresponds to the MCPTT user of group 1. The floor participant 2 corresponds to the MCPTT user of group 2. The floor participant 3 corresponds to the MCPTT user of group 3. The floor control server 1 belongs to primary MCPTT system. The floor control server 2 belongs to partner MCPTT system.
4. The floor control server 1 is the floor arbitrator of the MCPTT group call. The floor control server 2 routes all floor control messages to and from the floor participants 2 and 3 and then floor control server 1.
Figure 10.9.1.4.1-1: Floor control (partner MCPTT system forwarding) involving groups from multiple MCPTT systems
1. An MCPTT group call involving group1, group 2 and group 3 is setup and active.
2. The MCPTT users want to talk.
3. The floor participants initiate a floor request to the floor control server of their corresponding MCPTT systems. (The requests may or may not occur at the same time).
4. If only one floor request is received, or floor control server 2 handles the floor request sequentially, there is no arbitration performed and the corresponding floor request is forwarded to the floor control server 1. If the floor control server 2 receives multiple floor requests at the same time or during an interval, then it forwards the floor requests to the floor control server 1 (floor arbitrator for the MCPTT group call). As the floor participant information shall not be exposed, the floor priority related information or/and group information to be used by floor control server 1 should be included in the forwarded request.
5. The floor control server 1 performs floor arbitration for the MCPTT group call and determines the floor request to be accepted.
6. If the floor request from floor participant 2 of the partner MCPTT system is accepted, a floor granted is sent with permission to talk. The floor control messages from floor control server 1 are routed to floor participant 2 via the floor control server 2.
7. When the floor control server 2 (partner) receives the floor granted, the floor control server 2 sends a floor granted message on to floor participant 2.
8. The floor granted shall cause the user of the UE where the floor participant 2 is located to be notified.
9. The primary floor control server 1 may (9a.1) send a floor rejected message, or (9b.1) send a queue position info message for each non-granted received floor requests forwarded from the floor control server 2 (partner). When the floor control server 2 (partner) receives the floor rejected message, then the floor control server 2 (partner) (9a.2) sends a floor rejected message to the appropriate floor participant. When the floor control server 2 (partner) receives the queue position info, then the floor control server 2 (partner) (9b.2) sends a queue position info message to the appropriate floor participant.
10a.1 If floor control server 1 rejects the floor request from floor participant 1, then a floor reject message is sent.
10a.2 Upon this being received the user of the UE where floor participant 1 is located may be notified.
10b.1 If floor control server 1 supports floor queue, queue position info message is sent to the floor participant 1.
10b.2 Upon this being received the user of the UE where floor participant 1 is located may be notified.
NOTE 1: Steps 10a.1 through 10.b2 are optional as indicated by the dashed box enclosing them. However, if this box is implemented then either information flow 10a or 10b would occur.
NOTE 2: Optionally, the authorized user (e.g., dispatcher) receiving notifications about another user when their floor request is queued, when their queued floor request is rejected and when their queued floor request is removed from the queue is not shown here for the sake of brevity.
11. Since the floor is granted to floor participant 2 of the partner MCPTT system, then a floor taken is sent to all other floor participants ((11a) floor participant 1 and (11b.1) to floor control server 2 (partner) for forwarding to (11b.2) floor participant 3.
12. The receipt of the floor taken may be used to inform the users of the UEs where the floor participant entity 1 and floor participant 3 are located to be notified.
13. Upon successful floor granted, the group call media transmission occurs.
NOTE 3: The media flow between the media gateways of primary and partner MCPTT systems have not been depicted in the figure for clarity.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.4.2 Partner MCPTT system performs filtering of floor control messages entering and leaving the partner MCPTT system
|
The MCPTT users belonging to different groups in multiple MCPTT systems will participate in MCPTT media services (group communication, private calls, etc.) in scenarios like group hierarchies and temporary groups formed by group regroup. In this service delivery model involving multiple groups from different MCPTT systems, the floor control arbitration resides with the primary MCPTT system. This is determined in the group call setup stage. The MCPTT users of groups involved in the call session will transmit their floor control messages through the partner MCPTT systems to which they belong. In this scenario, the partner MCPTT system filters its MCPTT users' floor requests before communicating with the floor control server of the primary MCPTT system. The protocol used for media plane signalling is non-SIP like RTCP.
Figure 10.9.1.4.2-1 describes the procedure for floor control involving groups from multiple MCPTT systems.
Pre-conditions:
1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share all information of their users to the primary MCPTT system (public information would still need to be shared).
2. The group 1 is hosted by primary MCPTT system and group 2 and 3 are hosted by the partner MCPTT system.
3. The floor participant 1 corresponds to the MCPTT user of group 1. The floor participant 2 corresponds to the MCPTT user of group 2. The floor participant 3 corresponds to the MCPTT user of group 3. The floor control server 1 belongs to primary MCPTT system. The floor control server 2 belongs to partner MCPTT system.
4. The floor control server 1 is the floor arbitrator of the MCPTT group call. The floor control server 2 does floor control filtering with its floor participants 2 and 3 before communicating with the floor control server 1.
Figure 10.9.1.4.2-1: Floor control (filtering by partner MCPTT system) involving groups from multiple MCPTT systems
1. An MCPTT group call involving group 1, group 2 and group 3 is setup and active.
2. The MCPTT users want to talk
3. The floor participants initiate a floor request to the floor control server of their corresponding MCPTT systems. (The requests may or may not occur at the same time).
4. Floor control server 2 receives a floor request from floor participant 2 and from participant 3 at the same time or during an interval, then the floor control server 2 (partner) performs filtering of the floor requests received according to its local policy such as priority or order based on its own users, and forwards the selected floor request (floor participant 2) to the floor control server 1 (floor arbitrator for the MCPTT group call). As the floor participant information shall not be exposed, the priority related information or/and group information to be used by floor control server 1 should be included in the forwarded request.
5. The floor control server 2 (partner) may send a floor rejected towards the floor participant 3, since its floor request was not chosen to be forwarded on to the floor control server 1.
6. The user on the UE where the floor participant 3 is located may be notified of the rejection.
NOTE 1: Steps 5 and 6 can occur any time between step 4 and step 16.
7. The floor control server 2 (partner) forwards the floor request of floor participant 2 to the floor server 1.
8. The floor control server 1 performs floor arbitration for the MCPTT group call and determines the floor request to be accepted. The floor request message from floor participant 2 of the partner system is accepted by the floor control server 1 (arbitrator) and is determined that a floor granted is sent with permission to talk.
9. The floor granted message from floor control server 1 is routed to floor participant 2 via the floor control server 2 (partner).
10. Since floor participant 1 sent a floor request but was not granted,
10a.1 the primary floor control server may send a floor rejected message to floor participant 1.
10a.2 The user of the UE where the floor participant 1 is located may be notified of the rejection.
10b.1 if floor control server supports floor queuing, send a queue position info message to floor participant 1.
10b.2 The user of the UE where the floor participant 1 is located may be notified of the queue position.
NOTE 2: Steps 10a.1 through 10.b2 are optional as indicated by the dashed box enclosing them. However, if this box is implemented then either information flow 10a or 10b would occur.
NOTE 3: Optionally, the authorized user (e.g., dispatcher) receiving notifications about another user when their floor request is queued, when their queued floor request is rejected and when their queued floor request is removed from the queue is not shown here for the sake of brevity.
11. A floor taken message is sent to floor participant 1.
12. The user of the UE where the floor participant 1 is located may be notified.
NOTE 4: Step 10 through Step 12 can occur any time between step 8 and step 18.
13. Since the floor control server 2 (partner) filters floor requests, when the floor control server 2 (partner) receives the floor granted for floor participant 2 from floor control server 1, the floor control server 2 (partner) needs to use the information received to generate the floor taken which will be sent to all other floor participants (floor control participant 3).
14. The floor control server 2 (partner) sends a floor granted message to floor participant 2.
15. The user of the UE where the floor participant 2 is located is notified.
16. The floor control server 2 (partner) sends a floor taken message to all other floor participants (floor participant 3).
17. The user of the UE where the floor participant 1 is located may be notified.
18. Upon successful floor grant, the group call media transmission occurs.
NOTE 5: The media flow between the media gateways of primary and partner MCPTT systems have not been depicted in the figure for clarity.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.5 Floor control for audio cut-in enabled group
|
Figure 10.9.1.5-1 shows the procedure for audio cut-in for the session already established between the floor participants from same MCPTT service provider. Floor participants may request the floor while Floor Participant B is transmitting voice media. Floor control server grants floor immediately to the floor request received.
Editor's note: Configuration parameter for queue depth is FFS.
Pre-conditions:
- The floor control server has been configured to support audio cut-in.
- It is assumed that the floor has been granted to floor participant B and floor participant B is transmitting voice media. There are several other floor participants (including floor participant A).
Figure 10.9.1.5-1: Floor control for audio cut-in enabled group in single MCPTT system
1. Floor participant B has been given floor and is transmitting voice media.
2. Floor participant A wants to send voice media over the session.
3. Floor participant A sends a floor request message to the floor control server.
4. The floor control server applies the audio cut-in policy with floor queue disabled i.e., floor is immediately granted to the floor participant A, and revoked from floor participant B.
5. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission from floor participant B.
6. The user of floor participant B may be notified that the floor is revoked.
7. The Floor control server sends a floor granted message to floor participant A, and sends a floor taken message to floor participant B with information of who is granted the floor. The floor control server may limit the time a user talks (holds the floor).
8. The user of floor participant A may be notified that he is granted the floor. Similarly, the user of floor participant B may be notified who is granted the floor.
9. Floor participant A starts sending voice media over the session established.
10. Now floor participant B may want the floor to start sending voice media.
11. Floor participant B sends a floor request message to floor control server.
12. The floor control server applies the audio cut-in policy with floor queue disabled.
13. The floor control server sends a floor revoked message to floor participant A stopping the voice media transmission from floor participant A.
14. The user of floor participant A may be notified that the floor is revoked.
15. The Floor control server sends a floor granted message to floor participant B, and sends a floor taken message to floor participant A with information of who is granted the floor. The floor control server may limit the time a user talks (holds the floor).
16. The user of floor participant B may be notified that he is granted the floor. Similarly, the user of floor participant A may be notified who is granted the floor.
17. Floor participant B starts sending voice media over the session established.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.1.6 Unicast media stop and resume requests
|
Figure 10.9.1.6-1 shows the procedure for a floor participant to indicate to the floor control server that the unicast media flow of an active MCPTT group call can be stopped.
Pre-condition:
1. An MCPTT session is established between MCPTT client A and MCPTT server for an MCPTT group call. Other participants to the call are not shown in the figure for simplicity.
2. The floor control is established between the floor participant and the floor control server.
Figure 10.9.1.6-1: Unicast media stop request during an MCPTT session
1. Another floor participant has requested and has been granted the floor. The floor control server sends a floor taken message to floor participant A. The floor taken message may include an identifier of the associated media flow.
2. Floor control server sends the voice media flow to floor participant A over unicast.
3. Floor participant A gets the information, e.g. from the user, that media for the call is not needed.
4. Floor participant A sends a unicast media stop request to floor control server, identifying the media flow to be stopped.
5. Floor control server stops sending that unicast media flow to floor participant A. Associated bearer resources may be de-allocated by the MCPTT server.
Figure 10.9.1.6-2 shows the procedure for a floor participant to request from the floor control server that the unicast media flow of an active MCPTT group call be restarted.
Pre-condition:
1. An MCPTT session is established between MCPTT client A and MCPTT server for an MCPTT group call. Other participants to the call are not shown in the figure for simplicity
2. The floor control is established between the floor participant and the floor control server.
3. Floor participant A has previously indicated to the floor control server that unicast media flow for that call should be stopped, using the procedure described in Figure 10.9.1.6-1.
Figure 10.9.1.6-2: Unicast media resume request during an MCPTT session
1. Another floor participant has requested and has been granted the floor. The floor control server sends a floor taken message to floor participant A. The floor taken message may include an identifier of the associated media flow.
2. Floor participant A gets the information, e.g. from the user, that media for the call is needed again.
3. Floor participant A sends a unicast media resume request to floor control server, identifying the media flow to be re-started.
4. Floor control server starts sending that unicast media flow to floor participant A. This may need new bearer resources to be allocated.
NOTE 1: The identifier of the flow to be stopped or resumed is known by the floor participant from the floor control information flows associated with that MCPTT session.
NOTE 2: Stopping a media flow is not leaving the session and subsequent floor control messages will still be sent by the floor control server to the floor participant which has requested a unicast media stop.
NOTE 3: Both requests have no effect on a possible ongoing transmission of the media flow over MBMS. In particular, they are not interpreted by the MCPTT server as MBMS listening status reports.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2 Floor control for off-network MCPTT service
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.1 General
|
The procedures defined in this subclause provide floor control to MCPTT UEs in off-network operation. The procedures apply to both private calls and group calls.
In off-network, floor control is performed by using floor control messages among the MCPTT clients without centralized MCPTT server. The MCPTT client can transmit voice packets once it is granted the right to speak, either locally in the UE or by reception of a floor granted message from another MCPTT client.
In off-network, the MCPTT client currently speaking performs the temporary floor arbitrator during speaking since there is no centralized MCPTT floor control server. The floor arbitrator controls the floor whether or not queue is supported, and when floor is requested with override. If queue is supported, the MCPTT client performing floor arbitrator grants the right to speak to the next speaker and transfers the floor arbitrator role after completing the voice transfer and releasing the floor. For group calls, the floor arbitrator also transfers the floor control queue when granting the floor. The next MCPTT client receiving the right to speak becomes the new floor arbitrator and, for group calls, has the floor control queue.
For group calls, the floor control message is delivered in multicast based communication and can be monitored by all the members within the MCPTT group.
The following information flows apply among MCPTT clients.
- Floor request (from the floor participants to the floor arbitrator): used to request a floor for voice transfer.
- Floor release (from the floor arbitrator to the floor participants): used to inform that the voice transfer is completed and the floor is released.
- Floor granted (from the floor arbitrator to a floor participant): used to indicate that the request for floor is granted, that voice transfer is possible and the current queue list.
- Queue position request (from the floor participant to the floor arbitrator): used to request the position in the floor request queue.
- Queue position info (from the floor arbitrator to the floor participant): used to indicate the floor request is queued and the current queue status.
- Floor rejected (from the floor arbitrator to the floor participant): used to indicate that a request for the floor is rejected.
- Floor taken (from the floor arbitrator to the floor participant): used to indicate the floor is granted to another MCPTT user.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.2 Information flows for floor control for off-network
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.2.1 General
|
For floor control for off-network, the information flows defined under subclause 10.9.1.2 apply unless it is explicitly defined under this subclause.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.2.2 Floor granted
|
Table 10.9.2.2.2-1 describes the information flow floor granted, from the floor participant to the floor participant, which is used to indicate that a request for floor is granted and media transfer is possible.
Table 10.9.2.2.2-1: Floor granted
Information element
Status
Description
MCPTT ID
M
Requester identity
Duration
M
The time for which the granted party is allowed to transmit
Source identifier
O
Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only in case of media multiplexing
Acknowledgement required
O
Indicates if acknowledgement from the floor participant is required
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.3 Floor control during silence
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.3.1 Successful floor taken (No floor contention)
|
If a floor arbitrator still exists, the expected behaviour for floor requests during periods of silence is described in subclauses 10.9.2.5 and 10.9.2.6 (with the exception that no media was being generated prior to the floor request).
If a floor arbitrator does not exist, figure 10.9.2.3.1-1 shows the successful high level floor control procedure during periods when there is no detectable talker.
NOTE 1: The description also applies to private calls.
Pre-conditions:
1. An off-network group call had been established and all MCPTT clients have the call parameters. No participant is currently talking and no floor arbitrator is identified.
Figure 10.9.2.3.1-1: Successful floor taken flow (No floor contention)
1. The MCPTT client 1 sends the floor request message to the MCPTT group.
2. The MCPTT client 1 does not detect any floor contention. Floor contention occurs when multiple floor requests may exist simultaneously.
NOTE 2: The mechanism for detecting floor contention is out of scope of the present document.
3. The MCPTT client 1 sends the floor taken message to the MCPTT group.
4. The user gets a notification that the floor request was successful (the floor has been granted).
5. The MCPTT client 1 begins voice transmission.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.4 Simultaneous floor requests
|
If a floor arbitrator does not exist, figure 10.9.2.4.1-1 shows the expected behaviour in case of simultaneous floor requests are generated when there is no detectable talker.
Pre-conditions:
1. An off-network group call is established and all MCPTT clients have the call parameters. No participant is currently talking and no floor arbitrator is identified.
2. MCPTT client 1 has higher priority than MCPTT client 2.
Figure 10.9.2.4.1-1: Simultaneous floor requests
1a. The MCPTT client 1 sends the floor request message to the MCPTT group.
1b. The MCPTT client 2 sends the floor request message to the MCPTT group.
NOTE 1: Step 1a and 1b happen in parallel
2. On receiving a floor request message, while waiting for a response to the sent floor request message, the MCPTT client compares its floor priority with the floor priority indicated in the received floor request message.
3. On determining that it has higher floor priority than the received floor request message(s), and no response to the sent floor request message is received, the MCPTT client 1 sends the floor taken message to the MCPTT group.
4. The user at MCPTT client 1 gets notification that the floor request was successful (the floor has been granted).
NOTE 2: If the floor priority in the received floor request message is same as its own floor priority, the MCPTT client can use another scheme to decide who gets the floor.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.5 Floor request during speaking with queue
|
Figure 10.9.2.5-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. In the case, MCPTT clients should support queue function. The current speaking MCPTT client acting as the floor arbitrator put the floor request into the queue list when receiving the floor request from other MCPTT clients. This procedure happens while voice media is transmitting. In the flow, MCPTT client 1 transmits the voice media to the MCPTT group and acts as the floor arbitrator.
NOTE: The description only applies to group calls.
Figure 10.9.2.5-1: Floor request during speaking with queue
1. MCPTT client 1 is transmitting voice media to the MCPTT group.
2. MCPTT client 2 sends the floor request message to the MCPTT group.
3. MCPTT client 1 acting as the floor arbitrator put the floor request of MCPTT client 2 into the queue list.
4. MCPTT client 1 sends the queue position info message with the queuing status regarding the floor request of MCPTT client 2 in order to inform the floor request is queued.
5. MCPTT client 1 sends the floor granted message to the MCPTT group when releasing the floor. The message contains the MCPTT ID to be granted to send the voice media, and queue list, if any. MCPTT client 1 may include the maximum duration that MCPTT client 2 transmits in the floor granted message.
6. MCPTT client 2 sends the voice media when receiving the floor granted message and being granted as next speaker in the floor granted message. In addition, MCPTT client 2 becomes the floor arbitrator.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.6 Floor request during speaking without queue
|
Figure 10.9.2.6-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants. In the case, MCPTT clients do not support queue function. The current speaking MCPTT client acting as the floor arbitrator controls the floor request when receiving the floor request from other MCPTT clients. This procedure happens while voice media is transmitting. In the flow, MCPTT client 1 transmits the voice media to the MCPTT group and acts as the floor arbitrator.
NOTE: The description also applies to private calls.
Figure 10.9.2.6-1: Floor request during speaking without queue
1. MCPTT client 2 sends the floor request message to the MCPTT group.
2. MCPTT client 1 acting as the floor arbitrator rejects the floor request from MCPTT client 2 if no queue function is supported and sends the floor rejected message to the MCPTT group.
3. MCPTT client 1 sends the floor release message to the MCPTT group when releasing the floor, in order to indicate that MCPTT client 1 finishes to send the voice media and releases the floor.
When the floor release message is transmitted, there are no voice media in the MCPTT group until an MCPTT client requests the floor as described in subclause 10.9.2.3.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.7 Override
|
Figure 10.9.2.7-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. When the currently speaking MCPTT floor participant receives the floor request message from another floor participant who is authorized to revoke the active transmission (e.g. higher hierarchy), the current speaking MCPTT floor participant immediately stops sending the audio media and then grants the permission to that authorized floor participant.
NOTE: The description also applies to private calls.
Pre-condition:
- MCPTT client 1, who acts as the floor arbitrator, transmits the audio media to the MCPTT group.
Figure 10.9.2.7-1: Floor request with override authorization
1. MCPTT client 2 sends the floor request message with override criteria (e.g., priority level) to the MCPTT group.
2. MCPTT client 1 acting as the floor arbitrator determines if the floor is to be revoked based on override criteria. If this is the case, MCPTT client 1 revokes its right of the floor and stops sending the voice media immediately.
3. MCPTT client 1 sends the floor granted message to the MCPTT group. The floor granted message contains the MCPTT ID to be granted, the floor and the floor control queue (if supported). MCPTT client 1 may also include the maximum duration that MCPTT client 2 can transmit voice in the floor granted message.
MCPTT client2 who has revoked the floor is the new floor arbitrator and transmits the audio media to the MCPTT group.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.9.2.8 Floor queue status
|
Figure 10.9.2.8-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. If the floor control queueing is supported by the floor control mechanism, the current speaking MCPTT group member who is acting as the floor arbitrator collects the information about the queue status based on the received request(s) from the MCPTT group participant(s). The current speaker can then share information about the queue status of the MCPTT floor participant upon request.
NOTE: The description only applies to group calls.
Pre-condition:
- MCPTT client 1, who acts as the floor arbitrator, transmits the audio media to the MCPTT group.
Figure 10.9.2.8-1: Queue status request
1. MCPTT client 2 sends the queue position request message targeted to MCPTT client 1 i.e. the floor arbitrator by broadcasting the message to the MCPTT group to get its queue status.
2. Since the queue function is assumed to be supported in this call flow, MCPTT client 1 i.e. the floor arbitrator processes the queue position request to find out the status of MCPTT client 1 in the queue.
3. MCPTT client 1 constructs the queue position info message containing the MCPTT client 2's queue status and sends it toward MCPTT client 2 by broadcasting the message to the MCPTT group.
MCPTT client1 continues being the floor arbitrator and transmits the audio media to the MCPTT group.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10 Use of MBMS transmission (on-network)
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.1 Information flows for MBMS Transmission
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.1.1 MapGroupToBearer
|
Table 10.10.1.1-1 describes the information flow to associate a MCPTT group call to a MBMS bearer. It is sent from the MCPTT server to the MCPTT client.
Table 10.10.1.1-1: MapGroupToBearer
Information element
Status
Description
MCPTT group ID
M
This element identifies the MCPTT group, in which the call is started.
Media stream identifier
M
This element identifies the media stream of the SDP used for the group call (e.g. MBMS subchannel).
TMGI (see NOTE)
O
The MBMS bearer identifier if the media of the MCPTT group call is not sent on the same MBMS bearer as this MapGroupToBearer message.
Call acknowledgement indicator
O
Indication that the MCPTT group call requires acknowledgement from receiving MCPTT clients.
NOTE: TMGI shall be present if this message is sent over a different MBMS bearer than the media of the group call; TMGI may be present if this message is sent over the same MBMS bearer as the media of the group call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.1.2 UnmapGroupFromBearer
|
Table 10.10.1.2-1 describes the information flow to disconnect a MCPTT group call from a MBMS bearer. It is sent from the MCPTT server to the MCPTT client.
Table 10.10.1.2-1: UnmapGroupFromBearer
Information element
Status
Description
MCPTT group ID
M
This element identifies the MCPTT group which will no longer use the MBMS bearer.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.1.3 Application paging
|
Table 10.10.1.3-1 describes the information flow application paging from the MCPTT server to the MCPTT clients.
Table 10.10.1.3-1: Application paging
Information element
Status
Description
MCPTT Group ID (see NOTE)
O
This element identifies the MCPTT group which is paged by the application.
MCPTT ID (see NOTE)
O
Identity of the MCPTT user which is paged by the application for the private call.
Cause
M
The cause for this message being sent (e.g. for the use in group calls or private calls).
NOTE: Either MCPTT Group ID or MCPTT ID is present.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.2 Use of pre-established MBMS bearers
|
The MCPTT service shall support the procedure for using pre-established MBMS bearers as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-6, MCPTT‑8 and MCPTT-9 reference points for this procedure.
MCPTT may use pre-established MBMS bearer for the different types of MCPTT group calls. Both pre-arranged group calls and chat group calls can use the pre-established MBMS bearer for distributing the media. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more group calls in parallel.
Both the media packets as well as the floor control messages to the receiving users are sent on the MBMS bearer. Optionally a separate MBMS bearer could be used for the floor control messages, due to different bearer characteristic requirements.
When using the pre-established procedure for MCPTT, the MCPTT server perform the procedure of call connect and disconnect over MBMS as defined in subclause 10.10.4 at the group communication session establishment step.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.3 Use of dynamic MBMS bearer establishment
|
The MCPTT service shall support the procedure for using dynamic MBMS bearers as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-4, MCPTT-6, MCPTT‑7, MCPTT-8 and MCPTT-9 reference points for this procedure.
MCPTT may use dynamic MBMS bearer establishment for the different types of MCPTT group calls. Both pre-arranged group calls and chat group calls can use the dynamic MBMS bearer for distributing the media.
Both the media packets as well as the floor control messages to the receiving users are sent on the MBMS bearer.
When using the procedures for dynamic MBMS bearer establishment for MCPTT, the MCPTT server perform the procedure of call connect and disconnect over MBMS as defined in subclause 10.10.4 at the group communication session establishment step.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.4 Call connect and disconnect over MBMS
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.4.1 General
|
MBMS bearer can be used for MCPTT group calls. One MBMS bearer is not permanently associated to one specific group or group call. Before sending media packets of a group call over MBMS bearer, the MCPTT server shall send the association information between group call and the MBMS bearer. The group call setup procedure indicates the media stream within one MBMS bearer that is used for the specific group call. When the group call over the MBMS bearer is finished, this temporary association information of an MCPTT group call to specific resources on a MBMS bearer is undone. The procedure in figure 10.10.4.2.1-1 requires that the group session is setup before the call start. This eliminates the need for the receiving clients to continuously use a unicast bearer. Prior to this the MBMS bearer is activated and announced to the MCPTT clients.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.4.2 Procedure
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.4.2.1 Call connect over MBMS
|
In figure 10.10.4.2.1-1 the MCPTT client 1 is the client that initiate an MCPTT chat group call and also the transmitting client. MCPTT client 1 may, but does not have to, be in an MBMS service area. The MCPTT client 2 and MCPTT client 3 represents MCPTT clients receiving the MCPTT call over an MBMS bearer. There may be other receiving clients both over unicast bearers and over this or other MBMS bearer(s), however they are not illustrated in this figure.
The same procedure as for chat group call can also be applied for pre-arranged calls. However, that requires that the pre-arranged sessions are already active. If a pre-arranged group session is initiated the use of pre-established sessions are required.
Pre-conditions:
- All users participating in the MCPTT group call are already affiliated to the group.
- All participating users have joined the group session.
Figure 10.10.4.2.1-1: Chat group call connect on MBMS bearer
1. Activation and announcement of MBMS bearer availability.
NOTE 1: The procedure does not include the steps for MCPTT client location reporting, or for MBMS capability information exchange.
2. MCPTT client 1 initiate the MCPTT group call by sending an initial floor request over a unicast bearer to the MCPTT server (reference point MCPTT-4).
3. The MCPTT server will send a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the call over an MBMS bearer. The MapGroupToBearer message includes association information between the group call and MBMS bearer. The MapGroupToBearer message includes MCPTT group ID and information about the media stream identifier of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the call. The message is sent over reference point MCPTT-9.
NOTE 2: Step 3 can be deferred until step 5 and the MapGroupToBearer message can then be included in the floor taken message.
4. The MCPTT server grants the right to transmit for MCPTT client 1 and by that sends a floor granted message to the MCPTT client 1. This message is sent over a unicast bearer (reference point MCPTT-4).
5. A floor taken message is sent from the MCPTT server to all receiving users. This message includes the MCPTT ID of the transmitting MCPTT client as well as the MCPTT group ID. The message is sent over a MBMS bearer to all users that have previously been setup to receive calls over the MBMS bearer. The message is sent over reference point MCPTT-9.
6. The media is sent from MCPTT client 1 to the MCPTT server over unicast bearer and from the MCPTT server to the MCPTT client 2 and MCPTT client 3 over MBMS bearer.
NOTE 3: Additional floor request messages in the same call will not trigger the MapGroupToBearer message to be sent.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.4.2.2 Call disconnect over MBMS
|
Figure 10.10.4.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCPTT server to the MCPTT clients to indicate that the MCPTT group call is being dissociated from the MBMS bearer.
Figure 10.10.4.2.2-1: Chat group call disconnect on MBMS bearer
1. An MCPTT group call is ongoing; the media is broadcasted over MBMS bearer to MCPTT client 2 and MCPTT client 3.
2. MCPTT server has determined to disconnect the call over the MBMS bearer for the MCPTT clients
3. An UnmapGroupFromBearer message is sent by the MCPTT server to MCPTT client 2, MCPTT client 3 and possibly to MCPTT client 1 (if in MBMS coverage area) on MBMS bearer(s).
NOTE 4: The UnmapGroupFromBearer message can be sent as part of other messages.
NOTE 5: The UnmapGroupFromBearer message and the MapGroupToBearer message can be combined, to facilitate switching bearers in one signalling step, as necessary.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.5 Switching from MBMS bearer to unicast bearer
|
The MCPTT service shall support the procedure for switching from MBMS bearer to unicast bearer as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-4, MCPTT‑7, MCPTT-8 and MCPTT‑9 reference points for this procedure.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.6 Enhanced MCPTT group call setup procedure with MBMS bearer
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.6.1 Description
|
When the MCPTT server initiates a new MCPTT call, the MCPTT server shall decide to use unicast bearers or broadcast bearers for the downlink media. A similar decision may also be made for other types of media communication e.g. MCVideo. To decide to use broadcast or unicast involves a number of aspects. The figure 10.10.6.1-1 specifies a procedural flow to perform such decision.
The flow described evaluates which bearer type to use for a new MCPTT group call. It is assumed that if an MBMS bearer is active it is also announced to the MCPTT client.
When using an MBMS bearer for application level control signalling, the announcement of an already active MBMS bearer could be part of the MCPTT group call setup, however that will have an impact on the call setup time.
Figure 10.10.6.1-1: MBMS bearer decision flow
On a high level the procedure outcome is to use unicast or broadcast bearers for the new MCPTT group call. For an enhanced group call setup procedure, the MBMS bearer may be used to trigger the use of a unicast bearer.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.10.6.2 Procedure
|
The procedure in figure 10.10.6.2-1 can be used in the following scenarios:
- Initiate a new call on unicast bearer
- Transfer an ongoing call from broadcast bearer to unicast bearers
Pre-conditions:
- There must be an active and announced MBMS bearer
Figure 10.10.6.2-1: Application paging over an MBMS bearer
1. The MCPTT server initiates a new MCPTT group call on unicast or decides to transfer an ongoing call to unicast, or may initiate an MCPTT private call.
2. The MCPTT sends an application paging message on the MBMS bearer to inform the MCPTT client that the MCPTT server will initiate media transmission over a unicast bearer.
NOTE: The application paging message is sent with the assumption that there are UEs in idle mode. Furthermore, this message is an application level paging message and does not replace the normal paging procedure executed by EPC and RAN.
3. In the case that the UE is in idle mode the UE will initiate a service request to transfer the UE to connected mode.
4. The MCPTT server stops sending the media over an MBMS bearer. This step is only performed if transferring an ongoing call.
5. The MCPTT server initiates the media transmission over the unicast bearer.
Step 4-5 may be performed in parallel with step 2-3. Step 5 will trigger a normal paging in EPC and RAN if the client is still in idle mode.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.11 MCPTT resource management (on-network)
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.11.1 General
|
Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [16].
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.11.2 Request for unicast resources at session establishment
|
Void
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.11.3 Request for modification of unicast resources
|
Void
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.11.4 Management of multicast media bearers
|
Void
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.11.5 Request for resources with shared priority
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.11.5.1 General
|
Void
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.11.5.2 Procedure
|
Void
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.12 MCPTT media plane transmissions with partner MCPTT systems (on-network)
|
The MCPTT user is able to receive MCPTT media services (e.g. group communication, private calls) from partner MCPTT systems in normal and roaming conditions. In this service delivery model, the media plane transmissions between the MCPTT UE of the user and the partner MCPTT system can be achieved directly or via the primary MCPTT system, selected by the PLMN operator's policy. The protocol used for media plane signalling is non-SIP like RTCP.
Figure 10.12-1 provides the procedure for media related signalling.
Figure 10.12-2 provide the procedure for the media transmission (directly) between MCPTT UE of the user and the partner MCPTT system.
Figure 10.12-3 provides the procedure for the media transmission (via the primary MCPTT system) between MCPTT UE of the user and the partner MCPTT system.
Pre-conditions:
1. The MCPTT group is defined in the partner MCPTT system, where the MCPTT client of user receives the MCPTT service.
2. An MCPTT group call is set up and active.
3. The partner MCPTT system is the group host MCPTT server that is hosting the MCPTT group. The corresponding floor control server manages the media corresponding to the group call.
4. Protocol used for signalling of media plane is non-SIP, it can be protocol like RTCP.
5. Media related signalling is sent via the primary MCPTT system.
6. The path for media between the MCPTT UE and partner MCPTT system has been selected to be sent directly to the partner MCPTT system or via the primary MCPTT system based on PLMN operator's policy.
Figure 10.12-1: Media related signalling communication
Figure 10.12-2: Media communication direct
Figure 10.12-3: Media communication via primary MCPTT system
For media related signalling communication:
1. An MCPTT user wants to talk.
2. The floor participant corresponding to the MCPTT user sends a floor request message to floor control server (partner MCPTT system) to get the authorization and/or permission to talk.
3. The floor control server (partner MCPTT system) performs the authorization and arbitrates between requests that are in contention (i.e., floor control).
4. If the floor control server (partner MCPTT system) allows the floor participant to talk, a floor granted is provided with permission granted to talk.
For media communication:
5. The MCPTT client can now send uplink media data to the media distribution function of the MCPTT server (partner MCPTT system).
6. The media distribution function of the MCPTT server (partner MCPTT system) has downlink media data to transfer.
7. The media distribution function of the MCPTT server (partner MCPTT system) transfers the downlink media to the MCPTT client of the MCPTT user.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.13 Location information (on-network)
|
The MCPTT system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [16], utilising the CSC-14 reference point between the location management client and location management server and the CSC‑15 reference point between the MCPTT server and location management server.
- The MC service client is the MCPTT client;
- The MC service server is the MCPTT server;
- The MC service group is the MCPTT group;
- The MC service ID is the MCPTT ID; and
- The MC service group ID is the MCPTT group ID.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14 Ambient listening call
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.1 General
|
The ambient listening call is a type of a private MCPTT call that only allows a "listened to" user to transmit media to a "listening" user such that there is no indication on the MCPTT UE of the "listened to" user about the call and the media transmission.
NOTE 1: "listened to" user refers to the user who is transmitting media in an ambient listening call.
NOTE 2: "listening" user refers to the user who is receiving media in an ambient listening call.
There are two types of ambient listening call as below:
- Remotely initiated ambient listening is initiated by the authorized user (e.g., dispatcher) who wants to listen to another user. In this case, the "listened to" user is the called party, and shall automatically accept the call without causing any indication about the call and transmit the media to the "listening" user.
- Locally initiated ambient listening is initiated by an authorized user who wants another user to listen to the MCPTT UE communication. In this case, the "listened to" user is the calling party and shall automatically transmit the media to the "listening" user without causing any indication about the call processing and media transmission.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.2 Information flows for ambient listening call
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.2.1 Ambient listening call request
|
Table 10.14.2.1-1 describes the information flow ambient listening call request from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client.
Table 10.14.2.1-1: Ambient listening call request
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the "listening" user
MCPTT ID
M
The MCPTT ID of the "listened to" user
SDP offer
M
Media parameters of MCPTT client.
Ambient listening type
M
The ambient listening type indicates remotely initiated ambient listening call or locally initiated ambient listening call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.2.2 Ambient listening call response
|
Table 10.14.2.2-1 describes the information flow ambient listening call response from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client.
Table 10.14.2.2-1: Ambient listening call response
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the "listening" user
MCPTT ID
M
The MCPTT ID of the "listened to" user
SDP answer
M
Media parameters selected
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.2.3 Ambient listening call release request
|
Table 10.14.2.3-1 describes the information flow ambient listening call release request from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client.
Table 10.14.2.3-1: Ambient listening call release request
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the "listening" user
MCPTT ID
M
The MCPTT ID of the "listened to" user
Ambient listening type
M
The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.2.4 Ambient listening call release response
|
Table 10.14.2.4-1 describes the information flow ambient listening call release response from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client.
Table 10.14.2.4-1: Ambient listening call release response
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the "listening" user
MCPTT ID
M
The MCPTT ID of the "listened to" user
Ambient listening type
M
The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.2.5 Ambient listening call release notification
|
Table 10.14.2.5-1 describes the information flow ambient listening call release notification from the MCPTT server to the MCPTT client.
Table 10.14.2.5-1: Ambient listening call release notification
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the "listening" user
MCPTT ID
M
The MCPTT ID of the "listened to" user
Call release reason
M
The reason for call release by the MCPTT server
Ambient listening type
M
The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.3 Ambient listening call procedures
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.3.1 Remotely initiated ambient listening call setup
|
The MCPTT service provides the capability for an authorised user to initiate a remotely initiated ambient listening call at an MCPTT client.
Figure 10.14.3.1-1 illustrates the information flow for remotely initiated ambient listening call setup.
Pre-conditions:
- MCPTT client 1 is the client of the authorized user who is authorized to invoke a remotely initiated ambient listening call to be set up at the requested MCPTT client 2.
- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2.
Figure 10.14.3.1-1: Remotely initiated ambient listening call
1. MCPTT client 1 initiates a remotely initiated ambient listening call by sending the ambient listening call request to the MCPTT server. The remotely initiated ambient listening call type is included.
2. The MCPTT server performs an authorization check for the authorized user 1 for the remotely initiated ambient listening call. If authorization fails, the MCPTT server provides a failure response to MCPTT client 1. The MCPTT server also performs check whether MCPTT client 2 is engaged in an MCPTT Private Call or an MCPTT Group Call. If MCPTT client 2 is engaged in an MCPTT call, then the ambient listening call set up fails and response is provided to MCPTT client 1.
3. The MCPTT server sends the ambient listening call request to MCPTT client 2.
NOTE: MCPTT client 2 does not provide any indication of the ambient listening call request to its user.
4. MCPTT client 2 returns the ambient listening call response to the MCPTT server.
5. MCPTT server provides an ambient listening call response to MCPTT client 1, indicating whether the call is set up successfully or not.
6. The floor control server of the MCPTT server then sends a floor granted to MCPTT client 2 according to the ambient listening type received in step 1.
7. Accordingly, the floor control server of the MCPTT server sends a floor taken to MCPTT client 1.
8. After receiving the floor granted message at the MCPTT client 2, the media is transmitted from MCPTT client 2 to MCPTT client 1.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.3.2 Locally initiated ambient listening call setup
|
The MCPTT service provides the capability for an authorised user to initiate a locally initiated ambient listening call at an MCPTT client.
Figure 10.14.3.2-1 illustrates the information flow for locally initiated ambient listening call setup.
Pre-conditions:
- MCPTT client 2 is the client of the authorized user who is authorized to invoke a locally initiated ambient listening call to be set up at the requested MCPTT client 1.
- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2.
- MCPTT client 2 is not already engaged in an MCPTT Private Call or an MCPTT Group Call.
Figure 10.14.3.2-1: Locally initiated ambient listening call
1. MCPTT client 2 initiates a locally initiated ambient listening call by sending the ambient listening call request to the MCPTT server. The locally initiated ambient listening call type is included.
2. The MCPTT server performs an authorization check for the authorized user 2 for the locally initiated ambient listening call. If authorization fails, the MCPTT server provides a failure response to MCPTT client 2.
3. The MCPTT server sends the ambient listening call request to MCPTT client 1.
4. MCPTT client 1 returns the ambient listening call response to the MCPTT server.
5. MCPTT server provides an ambient listening call response to MCPTT client 2, indicating whether the call is set up successfully or not.
6. The floor control server of the MCPTT server then sends a floor granted to MCPTT client 2 according to the ambient listening type received in step 1.
7. Accordingly, the floor control server of the MCPTT server sends a floor taken to MCPTT client 1.
8. After receiving the floor granted message at the MCPTT client 2, the media is transmitted from MCPTT client 2 to MCPTT client 1.
NOTE: MCPTT client 2 does not provide any indication of the ambient listening call request to its user.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.3.3 Ambient listening call release – server initiated
|
Figure 10.14.3.3-1 illustrates the information flow for ambient listening call release – server initiated when trigger by the MCPTT administrator. This procedure is applied for both remotely initiated ambient listening call and the locally initiated ambient listening call.
Pre-conditions:
- MCPTT client 1 is the MCPTT client of the authorized user, who initiated the ambient listening call at MCPTT client 2.
- There is an ongoing ambient listening call between MCPTT client 2 and MCPTT client 1.
- MCPTT user 1 is the current user at MCPTT client 1 who is listening, and MCPTT user 2 is the current user at MCPTT client 2 who is being listened to.
Figure 10.14.3.3-1: Ambient listening call release – server initiated
1. The ambient listening call release is triggered by the MCPTT administrator or by one of the following events:
- the MCPTT server receives MCPTT call requests towards MCPTT client 2; or
- the MCPTT client 2 initiates MCPTT call requests;
2. The MCPTT server sends an ambient listening call release request to MCPTT client 2.
3. MCPTT client 2 stops transmitting media to MCPTT client 1.
NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user.
4. MCPTT client 2 provides an ambient listening call release response to the MCPTT server.
5. The MCPTT server sends an ambient listening call release notification to MCPTT client 1 together with a reason code identifying that the call was released.
6. MCPTT client 1 notifies the authorized user 1.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.3.4 Remotely initiated ambient listening call release – "listening" user initiated
|
Figure 10.14.3.4-1 illustrates the information flow for ambient listening call release – "listening" user initiated. This procedure is applied for both remotely initiated ambient listening call and the locally initiated ambient listening call.
Pre-conditions:
- MCPTT client 1 is the MCPTT client of the authorized user, who is authorized to release the ambient listening call at MCPTT client 2.
- There is an ongoing ambient listening call between MCPTT client 2 and MCPTT client 1.
- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to"user at MCPTT client 2.
Figure 10.14.3.4-1: Ambient listening call release – "listening" user initiated
1. The authorized user 1 at MCPTT client 1 initiates the ambient listening call release by sending an ambient listening call release request to the MCPTT server.
2. The MCPTT server provides an ambient listening call release request to MCPTT client 2.
3. MCPTT client 2 stops transmitting media to MCPTT client 1.
NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user.
4. MCPTT client 2 provides an ambient listening call release response to the MCPTT server.
5. The MCPTT server provides the ambient listening call release response to MCPTT client 1.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.14.3.5 Ambient listening call release – "listened to" user initiated
|
Figure 10.14.3.5-1 illustrates the information flow for ambient listening call release – "listened to" user initiated. This procedure is only applied for the locally initiated ambient listening call.
Pre-conditions:
- There is an ongoing ambient listening call between MCPTT client 1 and MCPTT client 2.
- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2.
- MCPTT client 2 is the MCPTT client of the authorized user, who is authorized to release the locally initiated ambient listening call at MCPTT client 2.
Figure 10.14.3.5-1: Ambient listening call release – "listened to" user initiated
1. The authorized user 2 at MCPTT client 2 initiates the ambient listening call release by sending an ambient listening call release request to the MCPTT server.
2. The MCPTT server provides an ambient listening call release request to MCPTT client 1.
3. The user 1 at MCPTT client 1 is notified about the ambient listening call release.
4. MCPTT client 1 provides an ambient listening call release response to the MCPTT server.
5. The MCPTT server provides the ambient listening call release response to MCPTT client 2.
6. MCPTT client 2 stops transmitting media to MCPTT client 1.
NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15 First-to-answer call setup
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.1 Description
|
Figure 10.15.3-1 describes the basic procedure for the MCPTT client initiating MCPTT first-to-answer call. The flow may use a floor request in the MCPTT call request indicating that the originator will be given the floor when the call starts and eliminates the need for a separate initial floor request message during media plane establishment. Alternatively, the call initiation may be sent without the floor request, which allows the called party to request the floor first. For a MCPTT first-to-answer call without floor control, floor control is not established.
Figure 10.15.3-1 also describes the handling of private calls when a functional alias replaces the MCPTT ID as target address. A functional alias can be simultaneously used by more than one MCPTT user, i.e. multiple MCPTT clients can activate the same functional alias.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.2 Information flows for first-to-answer call
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.2.1 MCPTT first-to-answer call request (MCPTT client to MCPTT server)
|
Table 10.15.2.1-1 describes the information flow MCPTT first-to-answer call request from the MCPTT client to the MCPTT server.
Table 10.15.2.1-1: MCPTT first-to-answer call request (MCPTT client to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID list (see NOTE)
O
The list of MCPTT IDs of the called party
Functional alias (see NOTE)
O
The functional alias of the called party
Use floor control indication
M
This element indicates whether floor control will be used for the private call.
SDP offer
O
Media parameters of MCPTT client.
Implicit floor request
O
An indication that the user is also requesting the floor.
Location information
O
Location of the calling party
NOTE: At least one identity shall be present. If both are present the MCPTT ID list shall be used to route the call request and the functional alias is just for information.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.2.2 MCPTT first-to-answer call request (MCPTT server to MCPTT client)
|
Table 10.15.2.2-1 describes the information flow MCPTT first-to-answer call request from the MCPTT server to the MCPTT client.
Table 10.15.2.2-1: MCPTT first-to-answer call request (MCPTT server to MCPTT client) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Functional alias
O
The functional alias of the called party
Use floor control indication
M
This element indicates whether floor control will be used for the private call.
SDP offer
M
Media parameters of MCPTT client.
Implicit floor request
O
An indication that the user is also requesting the floor.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.2.3 MCPTT first-to-answer call response (MCPTT client to MCPTT server)
|
Table 10.15.2.3-1 describes the information flow MCPTT first-to-answer call response from the MCPTT client to the MCPTT server.
Table 10.15.2.3-1: MCPTT first-to-answer call response (MCPTT client to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Functional alias
O
The functional alias of the called party
SDP answer
M
Media parameters selected
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.2.4 MCPTT first-to-answer call response (MCPTT server to MCPTT client)
|
Table 10.15.2.4-1 describes the information flow MCPTT first-to-answer call response from the MCPTT server to the MCPTT client.
Table 10.15.2.4-1: MCPTT first-to-answer call response (MCPTT server to MCPTT client) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
Functional alias
O
The functional alias of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Functional alias
O
The functional alias of the called party
SDP answer
M
Media parameters selected
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.2.5 MCPTT first-to-answer call cancel request (MCPTT server to MCPTT client)
|
Table 10.15.2.5-1 describes the information flow MCPTT first-to-answer call cancel request from the MCPTT server to the MCPTT client.
Table 10.15.2.5-1: MCPTT first-to-answer call cancel request (MCPTT server to MCPTT client) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ID
M
The MCPTT ID of the called party
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.2.6 MCPTT first-to-answer call cancel response (MCPTT client to MCPTT server)
|
Table 10.15.2.6-1 describes the information flow MCPTT first-to-answer call cancel response from the MCPTT client to the MCPTT server.
Table 10.15.2.6-1: MCPTT first-to-answer call cancel response (MCPTT client to MCPTT server) information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the called party
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.15.3 Procedure
|
All clients are served by the primary MCPTT service provider in figure 10.15.3-1.
Pre-conditions:
1. The calling MCPTT user has selected first-to-answer call.
2. MCPTT clients 1 to n are registered and their respective users, MCPTT user 1 to MCPTT user n, are authenticated and authorized to use the MCPTT service, as per procedure in subclause 10.2.
3. MCPTT clients 2 to n have activated the same functional alias.
4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates.
Figure 10.15.3-1: MCPTT first-to-answer call – MCPTT users in the same MCPTT system
1. MCPTT user at MCPTT client 1 would like to establish a MCPTT first-to-answer call indicating a set of potential target recipients or by calling a functional alias. For a MCPTT first-to-answer call with floor control, floor control is to be established. For first-to-answer call without floor control, both users will have the ability to transmit without floor arbitration.
2. MCPTT client 1 sends an MCPTT first-to-answer call request including a set of potential target recipients to the MCPTT server (via the SIP core as defined in 3GPP TS 23.228 [5]), using either a list of MCPTT IDs or a functional alias. The MCPTT first-to-answer call request contains the MCPTT ID and may contain the functional alias of originating user and an SDP offer containing one or more media types. The MCPTT first-to-answer call request may also contain a data element that indicates that MCPTT client 1 is requesting the floor, for a first-to-answer call with floor control. The MCPTT client 1 includes a first-to-answer call indication that the call is to be established only to the first answering user.
3. The MCPTT server confirms that MCPTT users are authorized for the call and whether the MCPTT user at MCPTT client 1 is authorized to initiate a first-to-answer call. The MCPTT server checks whether the provided functional alias of the calling user, if present, can be used and has been activated for the MCPTT user. If a functional alias is present, the MCPTT server shall also check whether MCPTT client 1 is allowed to use the functional alias of MCPTT client 2 (to MCPTT client n) to setup a private call and whether MCPTT client 2 (to MCPTT client n) is (are) allowed to receive a private call from MCPTT client 1 using a functional alias.
4. The MCPTT server determines the list of MCPTT users to send MCPTT first-to-answer call request, based on a set of allowed potential target recipients obtained from the request from MCPTT client 1. Alternatively, when a functional alias is used as target address, the MCPTT server resolves the functional alias to a corresponding list of related MCPTT IDs of MCPTT client 2 to MCPTT client n who have activated the functional alias. The functional alias must have been activated to identify the MCPTT IDs of the called users.
NOTE 1: Based on some selection criteria (e.g. using the current location of the initiating user to determine the dispatchers that are responsible for the related geographic areas), the MCPTT server can send MCPTT first-to-answer call requests only to a sub-set of the MCPTT users that have activated the functional alias. The selection of the appropriate sub-set of MCPTT IDs is left to implementation.
5a, 5b, 5c. The MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request and sends similar MCPTT first-to-answer call request to each potential target recipient, including the MCPTT ID and, if present, the functional alias of the calling MCPTT user at MCPTT client 1. If one or more called MCPTT users have registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the calls, then the incoming MCPTT first-to-answer call request is delivered only to the designated MCPTT UE. Otherwise MCPTT first-to-answer call request may be delivered to all the registered MCPTT UEs. If a functional alias is present and more than one MCPTT client has activated that functional alias, then the MCPTT server sends an MCPTT first-to-answer call request to each MCPTT client.
6a, 6b, 6c. The MCPTT users are alerted, regardless of the commencement mode.
7. MCPTT user at MCPTT client 2 accepted the call which causes MCPTT client 2 to send an MCPTT first-to-answer call response to the MCPTT server.
NOTE 2: MCPTT server does not divert MCPTT first-to-answer call to voicemail if MCPTT user at MCPTT client 2 has not accepted the incoming call.
8. The MCPTT server sends an MCPTT first-to-answer call response to MCPTT client 1 indicating that MCPTT user at MCPTT client 2 has accepted the call, including the accepted media parameters.
9a. The MCPTT server sends a MCPTT first-to-answer call cancel request to MCPTT client 3.
9b. Optionally, MCPTT client 3 notifies the user.
10a. The MCPTT server sends a MCPTT first-to-answer call cancel request to MCPTT client n.
10b. Optionally, MCPTT client n notifies the user.
11. The media plane for communication is established. Either user can transmit media individually when using floor control. For successful call establishment for first-to-answer call with floor request from MCPTT client 1, the floor participant associated with MCPTT client 1 is granted the floor initially. At the same time the floor participant associated with MCPTT client 2 is informed that the floor is taken. For a first-to-answer call without floor control both users are allowed to transmit simultaneously.
NOTE 3: Prior to media plane establishment, MCPTT client 1 and MCPTT client 2 set up a security association for the media, if end-to-end encryption is used for this call.
Editor's note: It is assumed that MCPTT client 1 initiates the set up as is done for private calls, but the details for the media security establishment are FFS and are in the scope of SA3. Results provided by SA3 may require changes in the procedure.
NOTE 4: The steps 9a ,10a and 11 can occur in any order and can also be performed in parallel.
12. MCPTT client 3 sends an MCPTT first-to-answer cancel call response.
13. MCPTT client n sends an MCPTT first-to-answer cancel call response.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.16 Remotely initiated MCPTT call
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.16.1 General
|
A remotely initiated MCPTT call allows an authorized user to cause a remote MCPTT UE to initiate a call by itself, without its user explicitly initiating the call.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.16.2 Information flows for remotely initiated MCPTT call
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.16.2.1 Remotely initiated MCPTT call request
|
Table 10.16.2.1-1 describes the information flow remotely initiated MCPTT call request from the MCPTT client to the MCPTT server and from the MCPTT server to MCPTT client.
Table 10.16.2.1-1: remotely initiated MCPTT call request information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the called party (remote)
Notification to remote user of remotely initiated call
M
Use to determine whether the called party (remote) receives any indication of the remotely initiated MCPTT call.
MCPTT ID
O (see NOTE)
For a remotely initiated MCPTT private call the MCPTT User ID to be called
MCPTT Group ID
O (see NOTE)
For a remotely initiated MCPTT group call to use.
Requested commencement mode
O
Requested commencement mode for the remotely initiated MCPTT private call.
Requested priority
O
Requested priority for the remotely initiated MCPTT private call or MCPTT group call.
NOTE: One and only one of these shall be present.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.16.2.2 Remotely initiated MCPTT call response
|
Table 10.16.2.2-1 describes the information flow remotely initiated MCPTT call response from the MCPTT client to the MCPTT server and from the MCPTT server to MCPTT client.
Table 10.16.2.2-1: Remotely initiated MCPTT call response information elements
Information Element
Status
Description
MCPTT ID
M
The MCPTT ID of the calling party
MCPTT ID
M
The MCPTT ID of the called party
Result
M
Result of the remotely initiated MCPTT call request – success or fail.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.16.3 Procedure
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.16.3.1 Remotely initiated MCPTT call request
|
The remotely initiated MCPTT call request procedure includes the initial remotely initiated MCPTT call request from the MCPTT user to the remote UE and either the MCPTT private call procedures or the MCPTT group call procedures originating at the remote UE.
Procedures in figure 10.16.3.1-1 show the signalling control plane procedures for the MCPTT client initiating a remotely initiated MCPTT call request with the chosen MCPTT user.
Pre-conditions:
1. If the MCPTT user on MCPTT client 1 wants the resulting remotely initiated MCPTT call to be:
a. an MCPTT group call, then MCPTT user 2 on MCPTT client 2 is an affiliated MCPTT group member of the MCPTT group that is the target of the remotely initiated MCPTT call.
b. an MPCTT private call, then the MCPTT user 2 on MCPTT client 2 is permitted to initiate an MCPTT private call to the identified MCPTT user.
Figure 10.16.3.1-1: Remotely initiated MCPTT call request
1. MCPTT user on MCPTT client 1 initiates a remotely initiated MCPTT call request to the MCPTT user of MCPTT client 2.
2. MCPTT client 1 sends a remotely initiated MCPTT call request towards the MCPTT server.
3. MCPTT server checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a remotely initiated MCPTT call request. If the resulting of this request is to initiate a group call, MCPTT client 1 is authorized to remotely initiate the MCPTT call request, and if MCPTT client 2 is a member of the group, the MCPTT server implicitly affiliates the MCPTT user 2 on MCPTT client 2 to the MCPTT group if the MCPTT client 2 is not already affiliated and notifies the MCPTT client 2 of this affiliation change.
4. If authorized, MCPTT server sends the corresponding remotely initiated MCPTT call request towards the MCPTT client 2.
5. Based on the received information the receiving MCPTT client 2 may notify the user of the remotely initiated MCPTT call request.
6. Optionally the receiving MCPTT client 2 sends a remotely initiated MCPTT call response to the MCPTT server.
7. After receiving the remotely initiated MCPTT call response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful remotely initiated MCPTT call request.
NOTE 1: Step 6 and step 7 might not be sent, since it could be determined that the remotely initiated MCPTT call was successful by receiving the MCPTT call initiated by MCPTT client 2.
8. Based on the received information the MCPTT client 2 initiates an MCPTT call (either an MCPTT group call or an MCPTT private call) using the normal MCPTT call establishment procedures (10.6.2.3.1.1.2 or 10.7.2.2) with implicit floor request and other call set up parameters if received in the remotely initiated call request. The MCPTT call request may include the additional information such as indication of whether the call initiation is due to receiving of remotely initiated call request.
NOTE 2: Step 6 and step 7 are received in this order. However, step 6 or step 7 or both might occur before or after step 8.
NOTE 3: The received information can have call setup related information, such as requested application priority level, commencement mode, etc.
9. If the remotely initiated call is a group call, then when the ongoing MCPTT group call is terminated, the MCPTT server de-affiliates the MCPTT user 2 on MCPTT client 2 from the MCPTT group if MCPTT client 2 is implicitly affiliated as defined in the step 3 above (the de-affiliation is not shown in the figure for simplicity).
The result of these procedures is an on-going MCPTT (group or private) call which includes MCPTT client 1.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.17 Support for multiple devices
| |
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.17.1 General
|
An MCPTT user may be authorized to use the MCPTT service from multiple MCPTT UEs as per the procedure in subclause 10.2.
If an MCPTT server receives a service authorization request for an MCPTT user who is previously MCPTT service authorized on another MCPTT UE, then the MCPTT server shall process this service authorization request as described in subclause 10.2. In the MCPTT service authorization response to the MCPTT user, the MCPTT server shall also indicate that the MCPTT user is already MCPTT service authorized from another MCPTT UE.
Editor's Note: How to log off remotely from MCPTT clients on one or more other MCPTT UEs that the MCPTT user is already MCPTT service authorized from is FFS.
|
4e2d9acb40e47c37b3e205bf83daf2e8
|
23.379
|
10.18 Subscription and notification for functional alias
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.