hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.6 Private Call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.6.1 Private Call overview | Private Calls allow two MCPTT Users to communicate directly with each other without the use of MCPTT Groups. They leverage many of the functions and features of MCPTT Group Calls, such as MCPTT User identity and alias information, location information, encryption, privacy, priority, and administrative control. Private Calls can use Floor control or not (i.e., be full voice duplex calls between users), though Private Calls without Floor control are only supported on the network.
Two commencement modes of Private Calls are supported: Manual Commencement Private Call and Automatic Commencement Private Call. The two commencement modes can be used in conjunction with Private Calls with/without Floor control.
Manual Commencement Private Calls mimic a telephone conversation where the called party receives a notification that they are being requested to join a Private Call, and the called party may accept, reject, or ignore the call request. Once the call setup is accepted, the Private Call is established and both Participants may communicate with each other.
Automatic Commencement Private Calls mimic the immediate setup and voice propagation of Group Call operation between two users where the calling party initiates an Automatic Commencement Private Call to another user and sends audio without any additional call setup delay beyond Group Calls. If available and able to accept the Private Call from the calling party, the called party immediately joins the Private Call and processes the calling party's audio. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.6.2 Private Call (with Floor control) general requirements | NOTE: The requirements in this subclause should mirror requirements in 6.7.1 for Private Call (without Floor control).
[R-5.6.2-001] The MCPTT Service shall provide the status (e.g., ringing, accepted, rejected, active) of an MCPTT Private Call (with Floor control) to the relevant MCPTT User that is a Participant of the MCPTT Private Call (with Floor control).
[R-5.6.2-002] The MCPTT Service shall support Private Calls with Floor control.
[R-5.6.2-003] The MCPTT Service shall provide a mechanism for an authorized MCPTT User that is a called party in an MCPTT Private Call (with Floor control), to restrict providing the reason why an MCPTT Private Call (with Floor control) setup has failed to the calling MCPTT User.
[R-5.6.2-004] The MCPTT Service shall provide a mechanism for the Private Call (with Floor control) to be set up with the MCPTT UE designated by the called MCPTT User to be used for Private Calls (with Floor control) when the called MCPTT User has signed on to the MCPTT Service with multiple MCPTT UEs.
[R-5.6.2-005] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.6.3 Private Call (with Floor control) commencement requirements | NOTE 1: The requirements in this subclause should mirror the requirements in 6.7.4 for Private Call (without Floor control).
[R-5.6.3-001] The MCPTT Service shall support Call Commencement Modes for Private Calls (with Floor control), which determine the conditions under which Private Calls (with Floor control) are set up.
[R-5.6.3-002] Void
[R-5.6.3-003] The MCPTT Service shall provide a mechanism for an MCPTT User to cancel an MCPTT Private Call (with Floor control) prior to the call setup.
[R-5.6.3-004] The MCPTT Service shall provide a means by which an authorized MCPTT User initiates an MCPTT Private Call (with Floor control).
[R-5.6.3-005] The MCPTT Service shall provide a means by which an MCPTT UE initiates an MCPTT Private Call (with Floor control) to any MCPTT User for which the MCPTT UE's current MCPTT User is authorized.
NOTE 2: For off-network use, only an MCPTT UE within communication range (possibly via a ProSe UE-to-UE Relay) receives the transmission.
[R-5.6.3-006] The MCPTT Service shall provide a means by which an MCPTT User initiates a Manual Commencement Private Call (with Floor control) to any MCPTT User for which the MCPTT User is authorized.
[R-5.6.3-007] The MCPTT Service shall require that the called MCPTT User accepts a Manual Commencement Private Call (with Floor control) setup request before the call proceeds.
[R-5.6.3-008] The MCPTT Service shall provide a means for an MCPTT User to accept a Manual Commencement Private Call (with Floor control) request from another MCPTT User.
[R-5.6.3-009] The MCPTT Service shall provide a means by which an MCPTT User initiates an Automatic Commencement Private Call (with Floor control) to any MCPTT User for which the MCPTT User is authorized.
[R-5.6.3-010] The MCPTT UE shall support automatic commencement mode and manual commencement mode for Private Calls (with Floor control).
[R-5.6.3-011] The MCPTT Service shall provide a manual commencement mode countermand by which an authorized MCPTT User may request that the invited MCPTT UE answer automatically.
[R-5.6.3-012] The MCPTT Service shall provide a means by which the calling authorized MCPTT User is notified the called MCPTT User received the Private Call (with Floor control) request.
[R-5.6.3-013] The MCPTT Service shall require that the called MCPTT UE acknowledge receipt of an Automatic Commencement Private Call (with Floor control) setup request before the audio transmission proceeds.
[R-5.6.3-014] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to transfer an ongoing MCPTT Private Call (with Floor control) to another MCPTT user.
[R-5.6.3-015] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to configure forwarding of incoming MCPTT Private Calls (with Floor control) to another MCPTT user in the following situations:
- Always
- If the MCPTT User is not reachable
- If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
- Based on manual input of the MCPTT User |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.6.4 Private Call (with Floor control) termination | NOTE 1: The requirements in this subclause should mirror the requirements in 6.7.5 for Private Call (without Floor control).
[R-5.6.4-001] The MCPTT Service shall provide a mechanism for an MCPTT User to reject an MCPTT Private Call (with Floor control).
[R-5.6.4-002] The MCPTT Service shall provide a means by which an authorized MCPTT User ignores a Manual Commencement Private Call (with Floor control) request from another MCPTT User.
NOTE 2: Ignoring a Manual Commencement Private Call (with Floor control) results in no indication of the reason for call failure being sent to the calling MCPTT User.
[R-5.6.4-003] The MCPTT Service shall provide a means by which an MCPTT User ends a Private Call (with Floor control) in which the MCPTT User is a Participant. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.6.5 Private Call (with Floor control) administration | NOTE: The requirements in this subclause should mirror requirements in 6.7.2 for Private Call (without Floor control), except [R-5.6.5-005] which is specific to Private Call with Floor control.
[R-5.6.5-001] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure which MCPTT Users, within their authority, are authorized to place a Manual Commencement Private Call (with Floor control).
[R-5.6.5-002] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure which MCPTT Users, within their authority, are authorized to place an Automatic Commencement Private Call (with Floor control).
[R-5.6.5-003] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure for a particular authorized MCPTT User, a set of MCPTT Users under the same authority to which an MCPTT Private Call (with Floor control) can be made.
[R-5.6.5004] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure the maximum duration for MCPTT Private Calls (with Floor control) for MCPTT Users within their authority.
[R-5.6.5-005] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure a timeout value in which an MCPTT Private Call (with Floor control) without a transmitting or receiving MCPTT User ends, for MCPTT Users within their authority.
[R-5.6.5-006] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure whether an MCPTT User, within their authority, that is a called party in an MCPTT Private Call (with Floor control), may restrict providing the reason why an MCPTT Private Call (with Floor control) setup has failed to the calling MCPTT User. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7 MCPTT priority requirements | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.1 Overview | MCPTT Emergency Group Call and MCPTT Imminent Peril group call are MCPTT Group Calls that provide the MCPTT User elevated priority towards obtaining resources of the MCPTT system. The MCPTT Emergency Private Call similarly provides elevated priority to resources of the MCPTT system. The MCPTT Emergency Alert provides a notification of an MCPTT Emergency situation from an MCPTT UE, regardless if the user is signed in with the MCPTT Service or not.
The MCPTT Emergency Alert is initiated from an MCPTT UE to inform the MCPTT Service of the user's immediate need of assistance due to the user's personal, life-threatening situation. If the user is not properly authenticated, he is treated as a temporary MCPTT User with limited permissions. The user initiates this notification by actuating a user interface on the MCPTT UE. The notification to the MCPTT Service includes the MCPTT User's ID, potentially an MCPTT Group ID, the user's Mission Critical Organization name and the most current location available for the user's MCPTT UE.
The user profile/group configuration determines which MCPTT Group ID is used, if any. If the user profile indicates that a dedicated (i.e., not used for everyday traffic) MCPTT Emergency Group is to be used, then the MCPTT Emergency call traffic moves to a different group. MCPTT Users that support MCPTT Emergency situations are required to monitor the dedicated MCPTT Emergency Group(s) for call activity. If the user profile indicates that the selected (i.e., currently active) MCPTT Group is to be used, then its Group ID is used, unless no group is selected.
After the MCPTT User has initiated an MCPTT Emergency Alert, MCPTT Emergency Private Call or MCPTT Emergency Group Call, the MCPTT User is considered to be in the MCPTT Emergency State. The user remains in the MCPTT Emergency State until the MCPTT User cancels the MCPTT Emergency State.
An MCPTT Group Call started by an MCPTT User while in the MCPTT Emergency State or previously started but followed by an MCPTT Emergency Alert becomes an MCPTT Emergency Group Call. The MCPTT Group ID used for the MCPTT Emergency Group Call is the same MCPTT Group ID included in the MCPTT Emergency Alert. An MCPTT User or dispatcher might initiate an MCPTT Emergency Group Call without an MCPTT Emergency Alert. The start of an MCPTT Emergency Group Call starts an In-progress Emergency condition for the MCPTT Group. Any subsequent MCPTT Group Call made by any MCPTT Group Member of an MCPTT Group which has an In-progress Emergency is treated as an MCPTT Emergency Group Call. MCPTT Emergency Group priority is removed when the In-progress Emergency for the group is cancelled.
An MCPTT Private Call started by an MCPTT User while in the MCPTT Emergency State becomes an MCPTT Emergency Private Call.
MCPTT Imminent Peril group call is differentiated from MCPTT Emergency Group Call based on for whom the assistance is required. The MCPTT Emergency Group Call is initiated by an MCPTT User for assistance for the MCPTT Emergency condition involving that user. The MCPTT Imminent Peril group call is initiated by an MCPTT User for assistance to other MCPTT Users or persons of the general public observed to be in trouble and may soon need assistance.
There is no MCPTT Imminent Peril Alert and no MCPTT Imminent Peril State for MCPTT Users. The granting of an MCPTT Imminent Peril group call starts an In-progress Imminent Peril condition for the MCPTT Group. Any subsequent MCPTT Group Call made by any MCPTT Group Member of an MCPTT Group which has an In-progress Imminent Peril condition is treated as an MCPTT Imminent Peril group call. MCPTT Imminent Peril Group priority is removed when the In-progress Imminent Peril for the group is cancelled. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2 Call types based on priorities | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.1 MCPTT Emergency Group Call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.1.1 MCPTT Emergency Group Call requirements | [R-5.7.2.1.1-001] Void
[R-5.7.2.1.1-002] Void
[R-5.7.2.1.1-003] Void
[R-5.7.2.1.1-004] Void
[R-5.7.2.1.1-005] Void
[R-5.7.2.1.1-006] Void
[R-5.7.2.1.1-007] Void
[R-5.7.2.1.1-008] Void
[R-5.7.2.1.1-009] Void
[R-5.7.2.1.1-010] Void
[R-5.7.2.1.1-011] Void
[R-5.7.2.1.1-012] Void
[R-5.7.2.1.1-013] Void
[R-5.7.2.1.1-014] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.1.2 MCPTT Emergency Group Call cancellation requirements | [R-5.7.2.1.2-001] Void
[R-5.7.2.1.2-002] Void
[R-5.7.2.1.2-003] Void
[R-5.7.2.1.2-004] Void
[R-5.7.2.1.2-005] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.2 Imminent Peril group call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.2.1 Imminent Peril group call requirements | [R-5.7.2.2.1-001] Void
[R-5.7.2.2.1-002] Void
[R-5.7.2.2.1-003] Void
[R-5.7.2.2.1-004] Void
[R-5.7.2.2.1-005] Void
[R-5.7.2.2.1-006] Void
[R-5.7.2.2.1-007] Void
[R-5.7.2.2.1-008] Void
[R-5.7.2.2.1-009] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.2.2 Imminent Peril group call cancellation requirements | [R-5.7.2.2.2-001] Void
[R-5.7.2.2.2-002] Void
[R-5.7.2.2.2-003] Void
[R-5.7.2.2.2-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.3 MCPTT Emergency Private Call (with Floor control) | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.3.1 MCPTT Emergency Private Call (with Floor control) requirements | [R-5.7.2.3.1-001] The MCPTT Service shall support MCPTT Emergency Private Calls (with Floor control) from authorized MCPTT Users.
NOTE: This functionality out of network relies on the MCPTT User being called being within ProSe Communication range. For this reason this functionality is more likely to be used on the network.
[R-5.7.2.3.1-002] When an MCPTT User initiates an MCPTT Emergency Private Call (with Floor control) this may trigger an MCPTT Emergency Alert for that MCPTT User.
[R-5.7.2.3.1-003] When an MCPTT User initiates an MCPTT Emergency Private Call (with Floor control) this shall put that MCPTT User into an MCPTT Emergency State. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.3.2 MCPTT Emergency Private Call (with Floor control) cancellation requirements | [R-5.7.2.3.2-001] The MCPTT Service shall support cancellation of the MCPTT Emergency priority of an MCPTT Emergency Private Call (with Floor control) by an authorized MCPTT User.
[R-5.7.2.3.2-002] The MCPTT Service shall support cancellation of the MCPTT Emergency priority of an MCPTT Emergency Private Call (with Floor control) when criteria established by the MCPTT Administrator are met (e.g., timeout).
[R-5.7.2.3.2-003] The MCPTT Service shall support an MCPTT User cancelling their own MCPTT Emergency State. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.4 MCPTT Emergency Alert | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.4.1 MCPTT Emergency Alert requirements | [R-5.7.2.4.1-001] Void
[R-5.7.2.4.1-002] Void
[R-5.7.2.4.1-003] Void
[R-5.7.2.4.1-004] Void
[R-5.7.2.4.1-005] Void
[R-5.7.2.4.1-006] Void
[R-5.7.2.4.1-007] Void
[R-5.7.2.4.1-008] Void
[R-5.7.2.4.1-009] Void
[R-5.7.2.4.1-010] Void
[R-5.7.2.4.1-011] Void
[R-5.7.2.4.1-012] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.7.2.4.2 MCPTT Emergency Alert cancellation requirements | [R-5.7.2.4.2-001] Void
[R-5.7.2.4.2-002] Void
[R-5.7.2.4.2-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.8 User ID | [R-5.8-001] Void
[R-5.8-002] Void
[R-5.8-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.9 MCPTT UE management | [R-5.9-001] Void
[R-5.9-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.10 MCPTT User Profile | [R-5.10-001] Void
[R-5.10-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.11 Support for multiple devices | [R-5.11-001] Void
[R-5.11-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.12 Location | [R-5.12-001] Void
[R-5.12-002] Void
[R-5.12-003] Void
[R-5.12-004] Void
[R-5.12-005] Void
[R-5.12-006] Void
[R-5.12-007] Void
[R-5.12-008] Void
[R-5.12-009] Void
[R-5.12-010] Void
[R-5.12-011] The MCPTT Service shall provide a means for an MCPTT UE to send a Location information update whenever the MCPTT User initiates an MCPTT Imminent Peril Call.
[R-5.12-012] Void
[R-5.12-013] Void
[R-5.12-014] Void
[R-5.12-015] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.13 Security | [R-5.13-001] Void
[R-5.13-002] Void
[R-5.13-003] Void
[R-5.13-004] Void
[R-5.13-005] Void
[R-5.13-006] Void
[R-5.13-007] Void
[R-5.13-008] Void
[R-5.13-009] Void
[R-5.13-010] Void
[R-5.13-011] Void
[R-5.13-012] Void
[R-5.13-013] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.14 Audio / voice quality | [R-5.14-001] Void
[R-5.14-002] MOS-LQO shall achieve the noise reduction performance of TIA-102.BABG [10] Table 3-1.
[R-5.14-003] MOS-LQO shall achieve a noise reduction performance for the 3GPP Adaptive Multi-Rate Wide Band codec (AMR-WB TS 26.190 [11] and TS 26.194 [12] that is equal to or greater than that specified for the P25 full rate and half rate voice codecs in TIA-102. BABG [10]. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.15 Interactions between MCPTT Group calls and MCPTT Private Calls (with Floor control) | [R-5.15-001] The MCPTT Service shall allow an MCPTT UE to be transmitting in one MCPTT Group Call while simultaneously receiving transmissions from one or more MCPTT Private Calls (with Floor control).
[R-5.15-002] The MCPTT Service shall allow an MCPTT UE to be receiving or transmitting in one MCPTT Private Call (with Floor control) while simultaneously receiving transmissions from one or more MCPTT Group Calls.
[R-5.15-003] The MCPTT Service shall allow an MCPTT UE to be receiving one or more MCPTT Group Calls while simultaneously receiving transmissions from one or more MCPTT Private Calls (with Floor control). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.16 Relay requirements | [R-5.16-001] Void
[R-5.16-002] Void
[R-5.16-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.17 Gateway requirements | [R-5.17-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.18 Control and management by Mission Critical Organizations | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.18.1 Overview | Subclause 5.18 contains general requirements for management of the MCPTT Service by Mission Critical Organizations sharing the same MCPTT system, and more specific requirements pertaining to management controls and operational visibility, and to management of security services. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.18.2 General requirements | [R-5.18.2-001] Void
[R-5.18.2-002] Void
[R-5.18.2-003] Void
[R-5.18.2-004] Void
[R-5.18.2-005] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.18.3 Operational visibility for Mission Critical Organizations | [R-5.18.3-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.19 General Administrative – groups and users | [R-5.19-001] Void
[R-5.19-002] Void
[R-5.19-003] Void
[R-5.19-004] Void
[R-5.19-005] Void
[R-5.19-006] Void
[R-5.19-007] Void
[R-5.19-008] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6 MCPTT Service requirements specific to on-network use | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.1 General administrative – groups and users | [R-6.1-001] Void
[R-6.1-002] Void
[R-6.1-003] Void
[R-6.1-004] Void
[R-6.1-005] Void
[R-6.1-006] Void
[R-6.1-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2 MCPTT calls | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.1 Commencement modes for MCPTT Group calls | [R-6.2.1-001] The MCPTT Service shall be capable of allowing an MCPTT Group call setup request to proceed without prior acknowledgement by any MCPTT User of that MCPTT Group.
[R-6.2.1-001a] The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if a minimum number of MCPTT Group Members are currently affiliated.
[R-6.2.1-001b] The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if specific MCPTT Group Member(s) are currently affiliated.
[R-6.2.1-002] An MCPTT User currently affiliated to an MCPTT Group shall acknowledge receipt of an MCPTT Group call setup request, if requested to do so by the MCPTT Service.
[R-6.2.1-003] The MCPTT User's acknowledgement may require direct interaction of the MCPTT UE with the human user, or may be automatically executed by the MCPTT UE, in accordance with policy established by an MCPTT Administrator.
[R-6.2.1-004] The MCPTT Service shall be capable of requiring that a minimum number of Affiliated MCPTT Group Members acknowledges receipt of the MCPTT Group call setup request before the audio transmission proceeds.
[R-6.2.1-005] The MCPTT Service shall be capable of requiring that specific MCPTT Users acknowledge receipt of the MCPTT Group call setup request before the audio transmission proceeds, regardless of the affiliation state of those users.
NOTE 1: In this case the MCPTT Service affiliates the specific MCPTT Users who are not currently affiliated to the target MCPTT Group and then returns them to their previous affiliation state when the transmission ends.
[R-6.2.1-006] The MCPTT Service shall be capable of requiring that all MCPTT Users that are both affiliated to the MCPTT Group and in a given geographical area acknowledge receipt of an MCPTT Group call setup request before the audio transmission proceeds.
[R-6.2.1-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to determine the subset of Affiliated MCPTT Group Members that shall acknowledge receipt of the MCPTT Group call setup request before the audio transmission proceeds.
NOTE 2: In the following requirements, the term, "MCPTT Group Call setup request requires acknowledgement" is used when one or more of the acknowledgement conditions defined above (i.e., [R-6.2.1-004], [R-6.2.1-005], [R-6.2.1-006], and/or [R-6.2.1-007]) applies.
[R-6.2.1-008] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), the MCPTT Service may proceed with the call and then may notify the initiating MCPTT User that the acknowledgements did not include all required members.
[R-6.2.1-009] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members do not acknowledge the call setup within a configured time, the MCPTT Service may abandon the call and then may notify the initiating MCPTT User that the acknowledgements did not include all required members.
[R-6.2.1-010] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the initiating MCPTT User shall at any time have the option of allowing the call to proceed regardless of the state of the acknowledgements (i.e., to "convert" the call to an unacknowledged call).
[R-6.2.1-010a] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, and the required MCPTT Group Members did not acknowledge the call setup within a configured time, the MCPPT Service shall be able to provide the list of MCPTT Group Members who did not acknowledge the call to the initiating MCPTT User.
[R-6.2.1-011] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the acknowledged call setup timeout shall be established by an MCPTT Administrator.
[R-6.2.1-012] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the behaviour in response to the expiration of the acknowledged call setup timeout shall be established by an MCPTT Administrator.
[R-6.2.1-013] If an MCPTT Group Call setup request requires acknowledgement from Affiliated MCPTT Group Members, the MCPTT Service shall support an indefinite (i.e., infinite) call setup timeout.
[R-6.2.1-014] If the MCPTT Service has knowledge that some affiliated members of a group can not be Participants in an unacknowledged MCPTT Group Call, the MCPTT Service shall provide an indication to the requester that the call is proceeding without all affiliated members, and shall provide the list of the missing members based on policy established by the MCPTT Administrator.
[R-6.2.1-015] If MCPTT User(s) are excluded from an MCPTT call as there is insufficient capacity to support their participation the MCPTT Service shall ensure that the MCPTT User(s) receive a notification that they have been excluded from the call for reasons of lack of capacity. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.2 Queuing | [R-6.2.2-001] Void
[R-6.2.2-002] Void
[R-6.2.2-003] Void
[R-6.2.2-004] Void
[R-6.2.2-005] Void
[R-6.2.2-006] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3 Floor control | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.1 General aspects | [R-6.2.3.1-001] The Floor control functionality in an MCPTT Service shall determine at a point in time which Participant(s) are allowed to transmit to other Participant(s).
[R-6.2.3.1-002] Receiving Participant(s) shall receive audio from one transmitting Participant. The only exception is if an MCPTT Group is configured to allow simultaneous Transmitting MCPTT Group Members in override.
[R-6.2.3.1-003] The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the number (maximum of N9) of simultaneous audios received by an MCPTT User in a single MCPTT Group. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.2 Requesting permission to transmit | [R-6.2.3.2-001] An authorized Participant shall be able to request to transmit to an MCPTT Group or an individual Participant.
[R-6.2.3.2-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Members who have affiliated to the MCPTT Group.
[R-6.2.3.2-003] The Floor control functionality shall determine the transmitting Participant(s) when there are simultaneous requests for permission to transmit within the same call.
[R-6.2.3.2-004] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group, the Affiliated MCPTT Group Member that made and was granted the request shall be given an indication of being allowed to transmit.
[R-6.2.3.2-005] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group, an Affiliated MCPTT Group Member that made and was not granted the request shall be given an indication that permission to transmit was rejected or queued.
[R-6.2.3.2-006] The depth of the Floor control queue shall be configurable.
[R-6.2.3.2-007] Following an MCPTT Private Call (with Floor control) request for permission to transmit, the MCPTT User that is allowed to transmit shall be given an indication that the user is allowed to transmit to the targeted MCPTT User.
[R-6.2.3.2-008] Following an MCPTT Private Call (with Floor control) request for permission to transmit, an MCPTT User that is not allowed to transmit shall be given an indication that the permission to transmit was rejected or queued.
[R-6.2.3.2-009] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant is starting to transmit.
[R-6.2.3.2-010] The MCPTT Service shall provide a mechanism for an MCPTT Participant to remove its MCPTT Request from the Floor control queue.
[R-6.2.3.2-011] The MCPTT Service shall provide a mechanism for removal (i.e., request accepted, request denied, or expiration of a timer) of an MCPTT Request from the Floor control queue.
[R-6.2.3.2-012] The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the parameter(s) of the Floor control queue for an MCPTT Group (i.e., timer). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.3 Override | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.3.1 General aspects | [R-6.2.3.3.1-001] The MCPTT Service shall enable MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types shall be granted a request to override an active MCPTT transmission.
[R-6.2.3.3.1-002] The MCPTT Service shall enable an MCPTT Administrator to configure which MCPTT Group transmission a Participant(s) receives, overriding and/or overridden for cases where an authorized Participant overrides an MCPTT transmission.
[R-6.2.3.3.1-003] The MCPTT Service shall enable the MCPTT Administrator to configure the MCPTT Group to allow only the overriding Participant to transmit or to allow both the overriding and overridden Participant to transmit.
[R-6.2.3.3.1-004] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure MCPTT Private Calls (with Floor control) to allow only the overriding Participant to transmit or to allow both the overriding and overridden Participant to transmit.
[R-6.2.3.3.1-005] The priority hierarchy used for granting a request to override an active MCPTT transmission shall contain at least four (4) levels.
[R-6.2.3.3.1-006] The transmitting Participant shall be determined by the relative Floor control priorities of the Participants and Call type based on priority (e.g MCPTT Emergency).
[R-6.2.3.3.1-007] The MCPTT Service shall provide a mechanism for Participants, to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant or Call type based on priority (e.g MCPTT Emergency) are ranked higher than the priority level of the transmitting Participant or Call type based on priority.
[R-6.2.3.3.1-008] If an authorized Participant overrides an MCPTT transmission, the MCPTT Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.3.2 Override – one transmitting Participant | [R-6.2.3.3.2-001] If the MCPTT Group has been configured to only allow the overriding transmitting Participant, the MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.3.3 Override – simultaneously Transmitting MCPTT Group Members | [R-6.2.3.3.3-001] If the MCPTT Group has been configured to allow both overriding and overridden transmitting Participants, authorized receiving Participants shall be enabled to listen to both the overriding and overridden Participant transmissions, dependent on configuration.
[R-6.2.3.3.3-002] The MCPTT Service shall allow successive overrides of an MCPTT Group Call when the request to override is made by an MCPTT User having a higher Floor control priority than the currently transmitting Participants.
[R-6.2.3.3.3-003] In the case of successive overrides, the MCPTT Service shall enable only two transmissions, one overriding transmission, from the highest priority MCPTT User, and one overridden transmission, chosen from among the two overridden Participants based upon configured rule(s). (i.e., this could be based simply on priority of user, it could be based on a policy that an overridden MCPTT Emergency transmission shall remain as the overridden transmission or a rule could be established that the MCPTT system shall not allow two dispatchers to be both the overriding and overridden transmitters.). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.4 Terminating permission to transmit | [R-6.2.3.4-001] The MCPTT Service shall enable an authorized MCPTT User to terminate the permission to transmit of a transmitting Participant at any time.
[R-6.2.3.4-002] A transmitting Participant shall be able to indicate to the MCPTT Service that the Participant no longer wants to transmit.
NOTE: In this case audio stops being transmitted to the receiver Participant(s) until an authorized Participant sends a subsequent request for permission to transmit.
[R-6.2.3.4-003] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.5 Transmit time limit | [R-6.2.3.5-001] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit.
[R-6.2.3.5-002] The Floor control functionality shall have a configurable limit for the length of time that a Participant transmits from a single request to transmit.
[R-6.2.3.5-003] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant is within a configurable amount of time before his transmit time limit is reached.
[R-6.2.3.5-004] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant's transmit time limit has been reached.
[R-6.2.3.5-005] The Floor control functionality shall remove the permission to transmit from the transmitting Participant when the Participant's transmit time limit has been reached. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6 Audio cut-in on designated MCPTT Groups | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.1 Overview | The audio cut-in feature applies to specially designated MCPTT Groups and results in Floor control for that group allowing any participant within the MCPTT Group to interrupt any other participant. In particular the audio cut-in feature means that the last Participant to request the floor is assigned the floor immediately and there is only ever one talker on the call at a particular point in time. Audio cut-in is often used for teams escorting VIPs where timeliness is essential to allow teams to react as quickly as possible.
Other than the difference in floor control logic, the MCPTT Groups configured to support audio cut-in behave in the same way as other MCPTT Groups with group management, affiliation, selection of a group, requesting the floor, the notifications received related to Floor control etc working in the same way. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.2 Requirements | [R-6.2.3.6.2-001] The MCPTT Group shall be configurable to allow audio cut-in.
NOTE 1: MCPTT Groups configured for audio cut-in behave in the same way as MCPTT Groups not configured for audio cut-in in all other respects other than the Floor control logic described in this sub-clause.
[R-6.2.3.6.2-002] When an MCPTT Group has been configured to support audio cut-in, the Floor control functionality shall give the floor to the MCPTT Group Member that has selected that MCPTT Group and made the most recent request to transmit in that MCPTT Group.
NOTE 2: Requests to transmit that are received simultaneously will be addressed by manufacturer implementation.
[R-6.2.3.6.2-003] When an MCPTT Group has been configured to support audio cut-in the Floor control functionality shall restrict the number of talkers in the group to one.
[R-6.2.3.6.2-004] When an MCPTT Group has been designated to support audio cut-in the MCPTT Group shall not support any form of floor control queuing and associated functionality.
[R-6.2.3.6.2-005] When the current talker is interrupted by a request to transmit on an MCPTT Group supporting audio cut-in, the talk request of the interrupted talker shall end.
NOTE 3: The interrupted talker must make a new request to transmit in order to transmit again.
[R-6.2.3.6.2-006] Void
[R-6.2.3.6.2-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.3 Requesting permission to transmit | [R-6.2.3.6.3-001] An authorized Participant shall be able to request to transmit to an MCPTT Group configured to support audio cut-in.
[R-6.2.3.6.3-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Members who have affiliated to the MCPTT Group configured to support audio cut-in.
[R-6.2.3.6.3-003] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group configured to support audio cut-in, the Affiliated MCPTT Group Member that made and was granted the request shall be given an indication of being allowed to transmit.
[R-6.2.3.6.3-004] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant is starting to transmit on a group configured for audio cut-in. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.4 Terminating permission to transmit | [R-6.2.3.6.4-001] The MCPTT Service shall enable an authorized MCPTT User to terminate the permission to transmit of a transmitting Participant at any time on a group configured for audio cut-in.
[R-6.2.3.6.4-002] A transmitting Participant shall be able to indicate to the MCPTT Service that the Participant no longer wants to transmit on a group configured for audio cut-in.
NOTE: In this case audio stops being transmitted to the receiver Participant(s) until an authorized Participant sends a subsequent request for permission to transmit.
[R-6.2.3.6.4-003] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting on a group configured for audio cut-in. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.5 Transmit time limit | [R-6.2.3.6.5-001] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit on a group configured for audio cut-in.
[R-6.2.3.6.5-002] The Floor control functionality for a group configured for audio cut-in shall have a configurable limit for the length of time that a Participant transmits from a single request to transmit.
[R-6.2.3.6.5-003] The Floor control functionality for a group configured for audio cut-in shall provide an indication to the transmitting Participant that the Participant is within a configurable amount of time before his transmit time limit is reached.
[R-6.2.3.6.5-004] The Floor control functionality for a group configured for audio cut-in shall provide an indication to the transmitting Participant that the Participant's transmit time limit has been reached.
[R-6.2.3.6.5-005] The Floor control functionality for a group configured for audio cut-in shall remove the permission to transmit from the transmitting Participant when the Participant's transmit time limit has been reached. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7 MCPTT Groups configured for multi-talker control | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7.1 Overview | The multi-talker control applies to designated MCPTT Groups and results in allowing several Participants talking simultaneously within the MCPTT Group. For example, Multi-talker control is used by railway communication e.g. during shunting operation.
Except for Floor control as specified in clauses 6.2.3.1, 6.2.3.2, 6.2.3.3 and 6.2.3.6 all other requirements specified in 6.2.3 floor control are applicable to all types of MCPTT Groups configured to support multi-talker control
When an MCPTT Group is configured for multi-talker control, the requirements listed below apply.
NOTE: All requirements for MCPTT Groups in clause 6.2.3.7 apply to all forms of MCPTT Groups (e.g., MCPTT Ad hoc Groups). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7.2 General aspects | [R-6.2.3.7.2-001] An MCPTT Group shall be configurable to allow multi-talker control.
[R-6.2.3.7.2-002] The MCPTT Service shall provide a mechanism for multiple MCPTT Users to talk simultaneously in an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.2-003] The MCPTT Service shall determine which Participant(s) are allowed to transmit to all other Participant(s) in an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.2-004] The MCPTT Service shall support all Participant(s) to receive audio from all other Participant(s) that are transmitting in an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.2-005] The MCPTT Service shall provide a mechanism for the MCPTT Administrator to configure the maximum number of simultaneous talkers in an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.2-006] The MCPTT Service shall allow an authorized MCPTT User to change the maximum number of simultaneous talkers at any time during a group call in an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.2-007] The MCPTT Service shall allow an authorized MCPTT User to change the priority hierarchy of simultaneous talkers at any time during a group call in an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.2-008] In case the maximum number of simultaneous talkers is reduced by an authorized MCPTT User, the permission to talk will be revoked, until the new maximum number of simultaneous talkers is met.
NOTE: The selection of the participants for revoking the permission to talk is left for implementation. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7.3 Requesting permission to transmit | [R-6.2.3.7.3-001] The MCPTT Service shall enable authorized Participants to request to transmit to an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.3-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Members who have affiliated to the MCPTT Group configured for multi-talker control.
[R-6.2.3.7.3-003] The MCPTT Service shall determine the transmitting Participant(s) when there are simultaneous requests for permission to transmit within the same call for an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.3-004] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group configured for multi-talker control the MCPTT Service shall provide an Affiliated MCPTT Group Member that made and was granted the request an indication of being allowed to transmit.
[R-6.2.3.7.3-004a] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group configured for multi-talker control the MCPTT Service shall provide an Affiliated MCPTT Group Member that made and was denied the request, the reason for denial.
[R-6.2.3.7.3-004b] Following an MCPTT Request for permission to transmit on the Selected MCPTT Group configured for multi-talker control the MCPTT Service shall provide an Affiliated MCPTT Group Member that made and was queued the request, the position in the queue.
NOTE: The queueing mechanism is left for implementation.
[R-6.2.3.7.3-005] Once in the queue, the MCPTT service shall provide to an Affiliated MCPTT Group Member, the position in the queue on demand. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7.4 Override | 6.2.3.7.4.1 General aspects
[R-6.2.3.7.4.1-001] If the number of MCPTT Users requesting the permission to talk exceeds the maximum number of simultaneous talkers in an MCPTT Group configured for multi-talker control, the MCPTT Service shall apply the override mechanism.
[R-6.2.3.7.4.1-002] The MCPTT Service shall enable MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types (e.g., dispatcher) and urgent transmission types shall be granted a request to override an active MCPTT transmission on an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.4.1-003] The priority hierarchy used for granting a request to override an active MCPTT transmission on a group configured for multi-talker control shall contain at least four (4) levels.
[R-6.2.3.7.4.1-004] The transmitting Participant on an MCPTT Group a group configured for multi-talker control shall be determined by the relative priorities of the Participants and Call type based on priority (e.g., MCPTT Emergency).
[R-6.2.3.7.4.1-005] Transmission requests of Participants with insufficient relative priority shall be rejected.
[R-6.2.3.7.4.1-006] The MCPTT Service shall provide a mechanism for Participants, to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant or Call type based on priority (e.g., MCPTT Emergency) are ranked higher than the priority level of the transmitting Participant or Call type based on priority for an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.4.1-007] If an authorized Participant overrides an MCPTT transmission, the MCPTT Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden for an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.4.1-008] The MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant on an MCPTT Group configured for multi-talker control. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.4 Call termination | [R-6.2.4-001] If a Participant of an MCPTT Group call is pre-empted, the MCPTT Service shall terminate the call or continue the call with an indication to the transmitting Participant that one or more receiving Participants was pre-empted.
[R-6.2.4-002] If MCPTT User(s) are pre-empted from an ongoing MCPTT call as there is insufficient capacity to support their ongoing participation, the MCPTT Service shall ensure that the MCPTT User(s) receive a notification that they have been removed from the call for reasons of lack of capacity.
[R-6.2.4-003] The MCPTT Service shall terminate a call after the Hang Time expires.
[R-6.2.4-004] Void
[R-6.2.4-005] The MCPTT Service shall provide an indication to the Participants that the call is within a configurable amount of time before the call time limit is reached.
[R-6.2.4-006] The MCPTT Service shall release the call when the call time limit has been reached.
[R-6.2.4-007] The MCPTT Service shall provide an indication to the Participants that the call time limit has been reached.
[R-6.2.4-008] The MCPTT Service shall release an MCPTT Group call if any of the termination conditions are met (e.g., last Participant leaving, second last Participant leaving, initiator leaving) or the minimum number of Affiliated MCPTT Group Members are not present. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.3 General requirements | [R-6.3-001] Void
[R-6.3-002] Void
[R-6.3-003] Void
[R-6.3-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4 General group call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.1 General aspects | [R-6.4.1-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.2 Group status/information | [R-6.4.2-001] Void
[R-6.4.2-002] Void
[R-6.4.2-003] Void
[R-6.4.2-004] Void
[R-6.4.2-005] Void
[R-6.4.2-006] Void
[R-6.4.2-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.3 Identification | [R-6.4.3-001] Void
[R-6.4.3-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.4 Membership/affiliation | [R-6.4.4-001] Void
[R-6.4.4-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.5 Membership/affiliation list | [R-6.4.5-001] Void
[R-6.4.5-002] Void
[R-6.4.5-003] Void
[R-6.4.5-004] Void
[R-6.4.5-005] Void
[R-6.4.5-006] Void
[R-6.4.5-007] Void
[R-6.4.5-008] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.6 Authorized user remotely changes another MCPTT User's affiliated and/or Selected MCPTT Group(s) | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.6.1 Mandatory change | [R-6.4.6.1-001] Void
[R-6.4.6.1-002] Void
[R-6.4.6.1-003] Void
[R-6.4.6.1-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.6.2 Negotiated change | [R-6.4.6.2-001] Void
[R-6.4.6.2-002] Void
[R-6.4.6.2-003] Void
[R-6.4.6.2-004] Void
[R-6.4.6.2-005] Void
[R-6.4.6.2-006] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.7 Prioritization | [R-6.4.7-001] Void
[R-6.4.7-002] Void
[R-6.4.7-003] Void
[R-6.4.7-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.8 Relay requirements | [R-6.4.8-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.9 Administrative | [R-6.4.9-001] Void
[R-6.4.9-002] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to set a predefined time period (Hang Time) without any traffic in MCPTT calls (with Floor control), after which the MCPTT calls shall terminate.
[R-6.4.9-003] Void
[R-6.4.9-004] Void
[R-6.4.9-005] Void
[R-6.4.9-006] Void
[R-6.4.9-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.5 Broadcast group | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.5.1 General Broadcast Group Call | [R-6.5.1-001] Void
[R-6.5.1-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.5.2 Group-Broadcast Group (e.g., announcement group) | [R-6.5.2-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.5.3 User-Broadcast Group (e.g., System Call) | [R-6.5.3-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6 Dynamic group management (i.e., dynamic regrouping) | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.1 General dynamic regrouping | [R-6.6.1-001] Void
[R-6.6.1-002] Void
[R-6.6.1-003] Void
[R-6.6.1-004] Void
[R-6.6.1-005] Void
[R-6.6.1-006] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.2 Group Regrouping | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.2.1 Service description | Group Regrouping enables dispatchers or any authorized user to temporarily combine MCPTT Groups. A dispatcher uses Group Regrouping for different reasons.
Due to an incident in an area it can be necessary to temporarily enable MCPTT Users from different MCPTT Groups to communicate to each other to coordinate. After the incident the dispatcher cancels the Group Regrouping and the MCPTT Users continue with their original configured MCPTT Groups.
During quiet periods control room managers can decide to combine MCPTT Groups and handle their operations and communications with one dispatcher. In the busier period the Group Regrouping is cancelled and the MCPTT Groups are handled by separate dispatchers. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.2.2 Requirements | [R-6.6.2.2-001] Void
[R-6.6.2.2-002] Void
[R-6.6.2.2-003] Void
[R-6.6.2.2-004] Void
[R-6.6.2.2-005] Void
[R-6.6.2.2-006] Void
[R-6.6.2.2-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.3 Temporary Group-Broadcast Group | [R-6.6.3-001] Void
[R-6.6.3-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.4 User regrouping | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.4.1 Service description | In the operational MCPTT environment most tasks are covered by standard procedures and communication structures and MCPTT Users can easily access the MCPTT Groups to handle their tasks.
Exceptionally it could happen that there is an urgent need for a dedicated set of individual MCPTT Users to communicate in an MCPTT Group, but that this is not foreseen in the communication structure. This could be due to extreme conditions or due to a cooperation that is outside normal procedures.
User Regrouping enables dispatchers or authorized users to instantaneously provide a dedicated MCPTT Group to these MCPTT Users to enable the required communication. Depending on configuration the MCPTT Users could be automatically affiliated to this MCPTT Group. After the operation this MCPTT Group is removed by the dispatcher or authorized user. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.4.2 Requirements | [R-6.6.4.2-001] Void
[R-6.6.4.2-002] Void
[R-6.6.4.2-003] Void
[R-6.6.4.2-004] Void
[R-6.6.4.2-005] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7 Private Call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.0 Overview | Private Calls can use Floor control or not. Private Calls (without Floor control) are only supported on network, whereas Private Calls (with Floor control) are supported both on and off network. Private Calls (without Floor contol) are intended to have the same functionality as specified for Private Calls (with Floor control) in subclauses 5.6.2, 5.6.3, 5.6.4, 5.6.5. Comparable requirements are included in subclauses 6.7.1, 6.7.2, 6.7.4 and 6.7.5, with the exception of R-5.6.5-005, which is specific to Private Calls (with Floor control). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.1 General requirements | [R-6.7.1-001] The on-network MCPTT Service shall support two types of Private Calls, one which uses Floor control and one which does not.
NOTE: An MCPTT Private Call (without Floor control) is effectively a full voice duplex call between two users.
[R-6.7.1-002] Void
[R-6.7.1-003] Void
[R-6.7.1-004] Void
[R-6.7.1-005] Void
[R-6.7.1-006] Void
[R-6.7.1-007] Void
[R-6.7.1-008] Void
[R-6.7.1-009] Void
[R-6.7.1-010] The MCPTT Service shall provide a mechanism by which specified Participants or Participant types (e.g., dispatch) have the ability to override an active PTT transmission of the other Participant in the Private Call.
[R-6.7.1-011] Void
[R-6.7.1-012] The MCPTT Service shall provide the status (e.g., ringing, accepted, rejected, active) of an MCPTT Private Call (without Floor control) to the relevant MCPTT User that is a Participant of the MCPTT Private Call (without Floor control).
[R-6.7.1-013] The MCPTT Service shall provide a mechanism for an authorized MCPTT User that is a called party in an MCPTT Private Call (without Floor control), to restrict providing the reason why an MCPTT Private Call (without Floor control) setup has failed to the calling MCPTT User.
[R-6.7.1-014] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.2 Administrative | [R-6.7.2-001] Void
[R-6.7.2-002] Void
[R-6.7.2-003] Void
[R-6.7.2-004] Void
[R-6.7.2-005] Void
[R-6.7.2-006] Void
[R-6.7.2-007] Void
[R-6.7.2-008] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.3 Prioritization | [R-6.7.3-001] Void
[R-6.7.3-002] Void
[R-6.7.3-003] Void
[R-6.7.3-004] Void
[R-6.7.3-005] Void
[R-6.7.3-006] Void
[R-6.7.3-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.4 Private Call (without Floor control) commencement requirements | [R-6.7.4-001] The MCPTT Service shall support Call Commencement Modes for Private Calls (without Floor control), which determine the conditions under which Private Calls (without Floor control) are set up.
[R-6.7.4-002] The MCPTT Service shall provide a mechanism for an MCPTT User to cancel an MCPTT Private Call (without Floor control) prior to the call setup.
[R-6.7.4-003] The MCPTT Service shall provide a means by which an authorized MCPTT User initiates an MCPTT Private Call (without Floor control).
[R-6.7.4-004] Void
[R-6.7.4-005] The MCPTT Service shall provide a means by which an MCPTT User initiates a Manual Commencement Private Call (without Floor control) to any MCPTT User for which the MCPTT User is authorized.
[R-6.7.4-006] The MCPTT Service shall require that the called MCPTT User accepts a Manual Commencement Private Call (without Floor control) setup request before the call proceeds.
[R-6.7.4-007] The MCPTT Service shall provide a means for an MCPTT User to accept a Manual Commencement Private Call (without Floor control) request from another MCPTT User.
[R-6.7.4-008] Void
[R-6.7.4-009] The MCPTT UE shall support automatic commencement mode and manual commencement mode for Private Calls (without Floor control).
[R-6.7.4-010]The MCPTT Service shall provide a manual commencement mode countermand by which an authorized MCPTT User may request that the invited MCPTT UE answers automatically.
[R-6.7.4-011] Void
[R-6.7.4-012] The MCPTT Service shall require that the called MCPTT UE acknowledge receipt of an Automatic Commencement Private Call (without Floor control) setup request before the audio transmission proceeds.
[R-6.7.4-013] The MCPTT Service shall provide a first-to-answer commencement mode by allowing the originating user to indicate multiple potential target recipients for a Private Call (without Floor control) and shall ensure that the call is established only to the first answering user.
NOTE: Attention needs to be given to prevent undesired outcomes caused, for example, by automatic answer or divert to voicemail.
[R-6.7.4-014] When a receiving user answers a first-to-answer Private Call (without Floor control) the MCPTT Service shall remove all other receiving users from that call.
[R-6.7.4-015] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to transfer an ongoing MCPTT Private Call (without Floor control) to another MCPTT user.
[R-6.7.4-016] The MCPTT Service shall provide a mechanism for an authorized MCPTT User to configure forwarding of incoming MCPTT Private Calls (without Floor control) to another MCPTT user in the following situations:
- Always
- If the MCPTT User is not reachable
- If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
- Based on manual input of the MCPTT User
6.7.4a Private Call (with Floor control) commencement requirements
[R-6.7.4a-001] The MCPTT Service shall provide a first-to-answer commencement mode by allowing the originating user to indicate multiple potential target recipients for a Private Call (with Floor control) and shall ensure that the call is established only to the first answering user.
NOTE: Attention needs to be given to prevent undesired outcomes caused, for example, by automatic answer or divert to voicemail.
[R-6.7.4a-002] When a receiving user answers a first-to-answer Private Call (with Floor control) the MCPTT Service shall remove all other receiving users from that call. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.5 Private Call (without Floor control) termination | [R-6.7.5-001] Void
[R-6.7.5-002] The MCPTT Service shall provide a means by which an authorized MCPTT User ignores a Manual Commencement Private Call (without Floor control) request from another MCPTT User.
NOTE: Ignoring a Manual Commencement Private Call (without Floor control) results in no indication of the reason for call failure being sent to the calling MCPTT User.
[R-6.7.5-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.6 Call back request requirements | [R-6.7.6-001] The MCPTT Service shall provide a mechanism (i.e., MCPTT Private Call call back request) for the calling party of an MCPTT Private Call to request that the called party (at earliest convenience) place a call to the calling party.
[R-6.7.6-002] The MCPTT Service shall provide a mechanism for the calling party of an MCPTT Private Call to assign an urgency indication (i.e., low, normal, urgent) to any call back request.
[R-6.7.6-003] The MCPTT Service shall provide an MCPTT UE receiving an MCPTT Private Call call back request with an indication of the assigned call back urgency assigned by the calling party.
[R-6.7.6-004] The MCPTT Service shall provide a mechanism for an MCPTT User to cancel a call back request.
[R-6.7.6-005] The MCPTT Service shall provide an MCPTT UE receiving an MCPTT Private Call call back request with an indication of which MCPTT User called and when. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8 MCPTT priority requirements | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.1 General | [R-6.8.1-001] Void
[R-6.8.1-002] The MCPTT Service shall provide an access control mechanism to support multiple Access Priorities to prioritize MCPTT MO call initiation attempts, depending on their access priorities.
[R-6.8.1-003] Void
[R-6.8.1-004] Void
[R-6.8.1-005] Void
[R-6.8.1-006] Void
[R-6.8.1-007] Void
[R-6.8.1-008] Void
[R-6.8.1-009] Void
[R-6.8.1-010] Void
[R-6.8.1-011] Void
[R-6.8.1-012] Void
[R-6.8.1-013] Void
[R-6.8.1-014] Void
[R-6.8.1-015] Void
[R-6.8.1-016] Void
[R-6.8.1-017] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.2 3GPP system access controls | [R-6.8.2-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.3 3GPP system admission controls | [R-6.8.3-001] Void |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.