5 MCPTT Service requirements common for on the network and off the network
22.1793GPPMission Critical Push to Talk (MCPTT)Release 17Stage 1TS
5.1 General group call requirements
5.1.1 General aspects
[R-5.1.1-001] Void
[R-5.1.1-002] Void
[R-5.1.1-003] Void
[R-5.1.1-004] Void
[R-5.1.1-005] Void
5.1.2 Group/status information
[R-5.1.2-001] Void
[R-5.1.2-002] Void
5.1.3 Group configuration
[R-5.1.3-001] Void
[R-5.1.3-002] Void
5.1.4 Identification
[R-5.1.4-001] Void
5.1.5 Membership/affiliation
[R-5.1.5-001] Void
[R-5.1.5-002] Void
[R-5.1.5-003] Void
[R-5.1.5-004] Void
[R-5.1.5-005] Void
[R-5.1.5-006] Void
[R-5.1.5-007] Void
[R-5.1.5-008] Void
5.1.6 Group Call administration
[R-5.1.6-001] Void
5.1.7 Prioritization
[R-5.1.7-001] Void
[R-5.1.7-002] Void
5.1.8 Charging requirements for MCPTT
[R-5.1.8-001] Void
[R-5.1.8-002] Void
[R-5.1.8-003] Void
[R-5.1.8-004] Void
[R-5.1.8-005] Void
[R-5.1.8-006] Void
[R-5.1.8-007] Void
[R-5.1.8-008] Void
[R-5.1.8-009] Void
[R-5.1.8-010] Void
[R-5.1.8-011] Void
5.2 Broadcast Group
5.2.1 General Broadcast Group Call
[R-5.2.1-001] Void
[R-5.2.1-002] Void
5.2.2 Group-Broadcast Group (e.g., announcement group)
[R-5.2.2-001] Void
[R-5.2.2-002] Void
[R-5.2.2-003] Void
[R-5.2.2-004] Void
5.2.3 User-Broadcast Group (e.g., System Call)
[R-5.2.3-001] Void
[R-5.2.3-002] Void
5.3 Late call entry
[R-5.3-001] Void
[R-5.3-002] Void .
[R-5.3-003] Void
[R-5.3-004] Void .
[R-5.3-005] Void
5.4 Dynamic group management (i.e., dynamic regrouping)
NOTE: No common on-network and off-network dynamic group management requirements have been identified.
5.5 Receiving from multiple MCPTT calls
5.5.1 Overview
MCPTT Users receive call traffic of their affiliated MCPTT Groups. This multiple receiving, called monitoring by some organizations, provides MCPTT Users current information about police, fire or critical medical events that are occurring within their jurisdictions. This is useful for dispatchers or those that might not be the primary support for that event at that moment. The information gained by monitoring might be useful for the dispatcher to determine any actions to take or be useful later if the MCPTT User is deployed to provide additional support for that event. The MCPTT User might be assigned to support the activities of more than one MCPTT Group on the same shift. This means that the MCPTT User receives multiple MCPTT Groups.
An MCPTT User with limited speaker resources (e.g., a handheld UE) might find that playing out concurrent received audio from multiple active MCPTT Groups becomes confusing and could also cause undesired voice distortion for the receiving user. During periods of time when the MCPTT User is receiving audio from multiple MCPTT Groups, which MCPTT Group’s audio is presented to the MCPTT User is determined by the MCPTT User’s choice, the priority associated with the talker of the Selected MCPTT Group(s), other considerations or combinations of these. The MCPTT UE is aware of all the active groups to which the MCPTT User has affiliated or selected and the identity of the other active receiving groups is available for display on the MCPTT UE. When the receive activity from the Selected MCPTT Group stops, the MCPTT UE might present the audio from the next group per the MCPTT User’s choice or by other means.
If none of the multiple groups to which the MCPTT User has affiliated or selected is active, the MCPTT UE would continue to monitor for activity by any of the multiple affiliated or Selected MCPTT Groups. Monitoring for activity of multiple MCPTT Groups is also known as scanning and the list of the multiple groups is also known as a scan list.
5.5.2 Requirements
[R-5.5.2-001] Void
[R-5.5.2-002] Void
[R-5.5.2-003] Void
[R-5.5.2-004] Void
[R-5.5.2-005] Void
[R-5.5.2-006] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N5) of MCPTT Group transmissions that an MCPTT UE simultaneously receives in one MCPTT Group call in case of override.
[R-5.5.2-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N10) of MCPTT Private Calls (with Floor control) in which an MCPTT UE simultaneously participates.
[R-5.5.2-008] Void
[R-5.5.2-009] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N7) of MCPTT Group transmissions that an MCPTT User simultaneously receives in one MCPTT Group call in case of override.
[R-5.5.2-010] Void
[R-5.5.2-011] Void
[R-5.5.2-012] Void
[R-5.5.2-013] Void
5.6 Private Call
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.
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
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
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.
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.
5.7 MCPTT priority requirements
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.
5.7.2 Call types based on priorities
5.7.2.1 MCPTT Emergency Group Call
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
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
5.7.2.2 Imminent Peril group call
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
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
5.7.2.3 MCPTT Emergency Private Call (with Floor control)
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.
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.
5.7.2.4 MCPTT Emergency Alert
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
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
5.8 User ID
[R-5.8-001] Void
[R-5.8-002] Void
[R-5.8-003] Void
5.9 MCPTT UE management
[R-5.9-001] Void
[R-5.9-002] Void
5.10 MCPTT User Profile
[R-5.10-001] Void
[R-5.10-002] Void
5.11 Support for multiple devices
[R-5.11-001] Void
[R-5.11-002] Void
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
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
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].
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).
5.16 Relay requirements
[R-5.16-001] Void
[R-5.16-002] Void
[R-5.16-003] Void
5.17 Gateway requirements
[R-5.17-001] Void
5.18 Control and management by Mission Critical Organizations
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.
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
5.18.3 Operational visibility for Mission Critical Organizations
[R-5.18.3-001] Void
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