7 MCPTT Service requirements specific to off-network use
22.1793GPPMission Critical Push to Talk (MCPTT)Release 17Stage 1TS
7.1 Off-network Push To Talk overview
The MCPTT Service while operating in off-network mode comprises a set or collection of functions necessary to provide Mission Critical Push To Talk (MCPTT) using a ProSe direct (UE-to-UE) Communication path (ProSe direct communication path) for transport. The ProSe direct communication path does not traverse the network infrastructure.
Users operating off the network are either out of network coverage (not served by a 3GPP network) (e.g., in a remote mountain area fighting a forest fire 20 miles from the nearest network) or have selected a ProSe direct communication path for MCPTT while in network coverage. MCPTT Users operating off the network need to be in ProSe direct communication range in order to communicate.
NOTE 1: While the network is likely to be a primary, reliable transport of MCPTT communications, there are many situations where MCPTT communications are needed in areas where the network is not available, or coverage is not reliable.
MCPTT Users outside of the coverage of the fixed network might be first responders in a rural area assisting in a response to a plane crash, fire fighters in a remote mountain area fighting a forest fire or police officers inside a residence responding to a domestic issue. Off-network MCPTT communications are expected to be immediately accessible to users in the absence of the network.
MCPTT Users in network coverage might be working in a confined area, such as fire fighters fighting a structure fire where direct UE-to-UE communication is more desirable and reliable. Users can communicate directly with one another without having to overcome the resistance of a building and distance to the nearest base station to communicate with other members of their team inside the building that are nearby.
To operate off the network, an MCPTT UE is capable of automatically switching to a ProSe direct communication path for use of MCPTT when detecting an off-network (out of coverage) condition. In addition a mechanism is provided for an authorized user to select (manually switch to) a ProSe direct communication path for use of off-network MCPTT communications (e.g., while in network coverage).
When operating off the network, the MCPTT Service is provided by the MCPTT application on the UE as compared to operations on the network, where the MCPTT Application on the UE interacts with an MCPTT server and the network to provide the MCPTT Service.
NOTE 2: For MCPTT UEs that have selected a ProSe Direct Communication path for use of MCPTT while in network coverage, signalling with the network and MCPTT Service might be available (e.g., radio resource allocation, MCPTT User Profile management updates and cryptographic key management updates), while the MCPTT User transmissions would be direct between the MCPTT UEs (e.g., not traversing the network).
The Off-Network MCPTT Service builds upon ProSe enablers to establish, maintain and terminate the signalling and communication path(s) among the off-network users. To the extent feasible, it is expected that the end user’s experience is similar regardless if the MCPTT Service is used with a 3GPP network or based on the use of a ProSe direct communication path.
The Off-Network MCPTT Service is intended to support communication between a group of users (a group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. However, the MCPTT Service also supports Private Calls between pairs of users.
When operating off the network the MCPTT Service allows users to request the permission to talk (transmit voice/audio) and provides a deterministic mechanism to arbitrate between requests that are in contention (i.e., Floor control).
The Off-Network MCPTT Service provides a means for a user with higher priority (e.g., MCPTT Emergency condition) to override (interrupt) the current talker. The Off-Network MCPTT Service also supports a mechanism to limit the time a user talks (hold the floor) thus permitting users of the same or lower priority a chance to gain the floor.
The Off-Network MCPTT Service provides the means for a user to monitor activity on a number of separate calls and enables the user to switch focus to a chosen call. An Off-Network MCPTT Service user might join an already established MCPTT Group call (Late call entry). In addition the Off-Network MCPTT Service supports User IDs, aliases and user Location determination features.
For operation off the network (e.g., when out of network coverage), an MCPTT UE is (pre-)provisioned by an MCPTT Administrator and/or authorized user with the following in order to use MCPTT:
- An MCPTT User Profile associated with each of the intended MCPTT Users of the MCPTT UE that might be used for off-network operation;
- An alphanumeric identifier (with a minimum length of N3) (i.e., alias) for each MCPTT User;
- A number of off-network MCPTT Groups for use by the MCPTT User;
- An alphanumeric identifier (i. e., alias) for the authorized off-network MCPTT Groups;
- A Mission Critical Organization name if available, associated with each of the intended MCPTT Users or Administrator;
- A number of off-network MCPTT Users for Private Call for which the MCPTT User is authorized;
- Authentication and end to end security keys.
NOTE 3: MCPTT UEs can be provisioned for off-network use by either configuration outside of network coverage or by attaching to the network.
An MCPTT UE operating off the network is capable of transmitting the talker Location information, User ID, alias(es), off-network MCPTT Group ID, group alias and, if available, Mission Critical Organization name of the user who is talking (i.e., whose UE is transmitting) to all other users in a call including MCPTT UEs operating off the network that are late entering a call in progress.
The Off-Network MCPTT Service uses the capabilities defined in ProSe TS 22.278 [5], including the ProSe Relay capabilities defined in ProSe TS 22.278 [5] and GCSE_LTE TS 22.468 [6].
NOTE 4: As indicated in TS 22.278 [5] use of a ProSe Direct Communication path outside of network coverage is only applicable for Public Safety ProSe enabled UEs. For non-Public Safety ProSe enabled UEs the selection of the most appropriate communication path (ProSe Communication path (direct or routed via local basestation) or 3GPP network path) is under network control and based on operator preferences.
MCPTT Service requirements specific to off-network use are defined in clause 7. Common MCPTT service requirements defined in clause 5 apply whether the MCPTT Service is in use on the network or off the network.
7.2 General off-network MCPTT requirements
[R-7.2-001] Void
[R-7.2-002] Void
[R-7.2-003] Void
[R-7.2-004] Void
[R-7.2-005] Void
7.3 Floor control
7.3.1 General aspects
[R-7.3.1-001] The off-network Floor control functionality in an MCPTT Service shall determine at a point in time which off-network Participant(s) are allowed to transmit to other off-network Participants.
[R-7.3.1-002] The off-network Floor control functionality in an MCPTT Service shall determine at a point in time which received transmission(s) from off-network Participant(s) shall be presented to the receiving off-network Participant(s).
7.3.2 Requesting permission to transmit
[R-7.3.2-001] A Participant in an off-network MCPTT Group call, with the authority to transmit, shall be able to request to transmit to the off-network MCPTT Group.
[R-7.3.2-002] The off-network Floor control functionality shall have a mechanism for resolving simultaneous requests for permission to transmit within the same call.
[R-7.3.2-003] Following an MCPTT Request for permission to transmit, the Affiliated MCPTT Group Member that is allowed to transmit shall be given an indication that the member is allowed to transmit on the member’s Selected MCPTT Group.
[R-7.3.2-004] Following an MCPTT Request for permission to transmit, an Affiliated MCPTT Group Member that is not allowed to transmit on the Selected MCPTT Group shall be given an indication that permission to transmit was rejected or queued.
[R-7.3.2-005] 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-7.3.2-006] 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.
7.3.3 Override
[R-7.3.3-001] An MCPTT UE shall be pre-provisioned by an MCPTT Administrator and/or authorized user with the necessary information in order that Floor control override may operate during off-network MCPTT.
[R-7.3.3-002] The MCPTT Service shall provide a mechanism for MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types, when operating off the network, be granted a request to override an active off-network MCPTT transmission.
[R-7.3.3-003] The priority hierarchy used for granting a request to override an active MCPTT transmission shall contain at least four (4) levels.
[R-7.3.3-004] 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 are ranked higher than the priority level of the transmitting Participant or call type.
[R-7.3.3-005] 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.
[R-7.3.3-006] The MCPTT Service shall provide a mechanism to 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 off-network MCPTT transmission. This mechanism, at the receiving Participant, shall also determine which transmission should be presented to the MCPTT User when an unauthorized transmission override has occurred due to a failure of transmit Floor control (e.g., due to the best effort nature of ProSe direct communication).
[R-7.3.3-007] If the MCPTT Group has been configured to only allow the overriding transmitting Participant to transmit, the MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant.
[R-7.3.3-008] If the MCPTT Group has been configured to allow both overriding and overridden transmitting Participants to transmit, the MCPTT Service shall provide a mechanism for authorized receiving Participants to be able to listen to both the overriding transmission and any overridden Participant transmissions, dependent on configuration.
7.3.4 Terminating permission to transmit
[R-7.3.4-001] A transmitting Participant shall be able to indicate to the Off-Network MCPTT Service that the Participant no longer wants to transmit.
[R-7.3.4-002] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting.
7.3.5 Transmit time limit
[R-7.3.5-001] An MCPTT UE shall be pre-provisioned by an MCPTT Administrator and/or authorized user with the necessary information in order that a transmit time limit function may operate during off-network MCPTT.
[R-7.3.5-002] 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-7.3.5-003] 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-7.3.5-004] 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-7.3.5-005] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant’s transmit time limit has been reached.
[R-7.3.5-006] The Floor control functionality shall remove the permission to transmit from the transmitting Participant when the Participant’s transmit time limit has been reached.
7.4 Call Termination
[R-7.4-001] The MCPTT Service when operating off the network shall terminate a call after a period of inactivity.
[R-7.4-002] The MCPTT Service when operating off the network shall provide a mechanism for an MCPTT Administrator to preconfigure the inactivity timer.
[R-7.4-003] Void
[R-7.4-004] Void
[R-7.4-005] Void
[R-7.4-006] Void
7.5 Broadcast Group
[R-7.5-001] Void
[R-7.5-002] Void
7.6 Dynamic group management (i.e., dynamic regrouping)
NOTE: No specific off-network MCPTT requirements for dynamic group management have been identified.
7.7 MCPTT priority requirements
[R-7.7-001] Void
[R-7.7-002] The Off-Network MCPTT Service shall pass these attributes to the ProSe transport layer for the purposes of prioritizing the associated user data.
[R-7.7-003] Void
7.8 Call types based on priorities
7.8.1 MCPTT Emergency Group Call requirements
[R-7.8.1-001] Void
[R-7.8.1-002] Void
[R-7.8.1-003] Void
7.8.2 MCPTT Emergency Group Call cancellation requirements
[R-7.8.2-001] Void
7.8.3 Imminent Peril Call
7.8.3.1 Imminent Peril group call requirements
[R-7.8.3.1-001] Void
[R-7.8.3.1-002] Void
[R-7.8.3.1-003] Void
[R-7.8.3.1-004] Void
[R-7.8.3.1-005] Void
7.8.3.2 Imminent Peril group call cancellation requirements
[R-7.8.3.2-001] Void
[R-7.8.3.2-002] Void
7.9 Location
[R-7.9-001] Void
7.10 Security
[R-7.10-001] Void
[R-7.10-002] Void
7.11 Audio MCPTT Call performance
7.11.1 MCPTT Access time and Mouth-to-ear latency
7.11.1.1 General overview
For MCPTT Users, one of the most important performance criteria is the MCPTT Access time (KPI 1). The MCPTT Access time is defined as the time between when an MCPTT User requests to speak (normally by pressing the MCPTT control on the UE) and when this user gets a signal to start speaking. This time does not include confirmations from receiving users.
The Mouth-to-ear latency (KPI 3) is the time between an utterance by the transmitting user, and the playback of the utterance at the receiving user’s speaker. Figure 7.11.1.1.1 illustrates the MCPTT Access time and Mouth-to-ear latency.
Figure 7.11.1.1-1: Illustration of MCPTT Access time and Mouth-to-ear latency
7.11.1.2 Requirements
NOTE: The MCPTT Access time and Mouth-to-ear latency for off-network use is FFS.
7.11.2 Late call entry performance
7.11.2.1 General overview
An MCPTT User is able to join or leave an already ongoing MCPTT Group Call. Late call entry is the activity when an Affiliated MCPTT Group Member joins an MCPTT Group Call in which other Affiliated MCPTT Group Members are already active. The Late call entry time (KPI 4) is the time to enter an ongoing MCPTT Group Call measured from the time that the user decides to monitor such an MCPTT Group Call, to the time when the UE’s speaker starts to play the audio. The performance requirements for Late call entry time only applies to when there is ongoing voice transmitted at the time the MCPTT User joins the call.
In a Late call entry there might be an initial lost audio of the voice burst sent to the new Receiving MCPTT Group Member.
7.11.2.2 Requirements
NOTE: The Late call entry time (KPI 4) for off-network use is FFS.
7.11.3 Audio / Voice quality
[R-7.11.3-001] Void.
7.12 Off-network MCPTT operations
[R-7.12-001] Void
[R-7.12-002] Void
[R-7.12-003] Void
7.13 Off-network UE functionality
[R-7.13-001] Void
[R-7.13-002] Void
[R-7.13-003] Void
[R-7.13-004] Off-network MCPTT UEs shall support a minimum number of (N8) simultaneous off-network MCPTT calls.
7.14 Switching to off-network MCPTT
[R-7.14-001] Void
[R-7.14-002] Void
[R-7.14-003] Void
7.15 Off-network recording and audit requirements
[R-7.15-001] Void
[R-7.15-002] Void
7.16 Off-network UE-to-UE Relay
7.16.1 Private Calls
[R-7.16.1-001] Void
[R-7.16.1-002] Void
[R-7.16.1-003] Void
7.16.2 Group Calls
[R-7.16.2-001] Void
[R-7.16.2-002] Void
Annex A (informative):
Variables
Table A.1: List of variables
Variable |
Meaning |
Value |
Reference |
B1 |
Number of levels of group hierarchy |
5.2.2 |
|
B2 |
Number of levels of user hierarchy |
5.2.3 |
|
KPI 1 |
MCPTT Access time |
< 300 ms |
6.15.3.2 |
KPI 2 |
End-to-end MCPTT Access time |
< 1000 ms |
6.15.3.2 |
KPI 3 |
Mouth-to-ear latency |
< 300 ms |
6.15.3.2 |
KPI 4a |
Maximum Late call entry time (without application layer encryption) |
< 150 ms |
6.15.4.2 |
KPI 4b |
Maximum Late call entry time (with application layer encryption) |
< 350 ms |
6.15.4.2 |
N1 |
Number of receiving members present for an MCPTT Group. |
6.4.2 |
|
N2 |
Total number of MCPTT Groups that an MCPTT User can be affiliated to simultaneously |
5.1.5 |
|
N3 |
Minimum length of alphanumeric identifiers (i.e., Alias ID) |
5.8, 6.4.3, 7.1, and 7.2 |
|
N4 |
Number of simultaneous MCPTT Group calls received by a UE |
5.5.2 |
|
N5 |
Total number of MCPTT Group transmissions that a UE can receive |
5.5.2 |
|
N6 |
Number of simultaneous MCPTT Group calls received by a user |
5.5.2 |
|
N7 |
Total number of MCPTT Group transmissions that a user can receive |
5.5.2 |
|
N8 |
Minimum number of simultaneous off-network MCPTT calls supported by an off-network MCPTT UE. |
7.13 |
|
N9 |
Maximum number of simultaneous audios received by an MCPTT User in a single MCPTT Group |
6.2.3.1 |
|
N10 |
Total number of MCPTT Private Calls (with Floor control) in which a UE simultaneously participates |
5.5.2 |
|
N11 |
Total number of MCPTT Group Members of an MCPTT Group |
6.1 |
Annex A1 (Informative):
MCPTT Requirements for MCCoRe
This table provides an exhaustive list of those requirements in 3GPP TS 22.179 that have been mapped to MCCoRe.
5 MCPTT Service Requirements common for on the network and off the network |
|
5.1 General Group call requirements |
|
5.1.1 General Aspects |
|
R-5.1.1-001 R-5.1.1-001 |
R-5.1.1-002 R-5.1.1-002 |
R-5.1.1-003 R-5.1.1-003 |
R-5.1.1-004 R-5.1.1-004 |
R-5.1.1-005 R-5.1.1-005 |
|
5.1.2 Group/status information |
|
R-5.1.2-001 R-5.1.2-001 |
R-5.1.2-002 R-5.1.2-002 |
5.1.3 Group configuration |
|
R-5.1.3-001 R-5.1.3-001 |
R-5.1.3-002 R-5.1.3-002 |
5.1.4 Identification |
|
R-5.1.4-001 R-5.1.4-001 |
|
5.1.5 Membership/affiliation |
|
R-5.1.5-001 R-5.1.5-001 |
R-5.1.5-002 R-5.1.5-002 |
R-5.1.5-003 R-5.1.5-003 |
R-5.1.5-004 R-5.1.5-004 |
R-5.1.5-005 R-5.1.5-005 |
R-5.1.5-006 R-5.1.5-006 |
R-5.1.5-007 R-5.1.5-007 |
R-5.1.5-008 R-5.1.5-008 |
5.1.6 Group Call administration |
|
R-5.1.6-001 R-5.1.6-001 |
|
5.1.7 Prioritization |
|
R-5.1.7-001 R-5.1.7-001 |
R-5.1.7-002 R-5.1.7-002 |
5.1.8 Charging requirements for MCPTT |
|
R-5.1.8-001 R-5.1.8-001 |
R-5.1.8-002 R-5.1.8-002 |
R-5.1.8-003 R-5.1.8-003 |
R-5.1.8-004 R-5.1.8-004 |
R-5.1.8-005 R-5.1.8-005 |
R-5.1.8-006 R-5.1.8-006 |
R-5.1.8-007 R-5.1.8-007 |
R-5.1.8-008 R-5.1.8-008 |
R-5.1.8-009 R-5.1.8-009 |
R-5.1.8-010 R-5.1.8-010 |
R-5.1.8-011 R-5.1.8-011 |
|
5.2 Broadcast Group |
|
5.2.1 General Broadcast Group Communication |
|
R-5.2.1-001 R-5.2.1-001 |
R-5.2.1-002 R-5.2.1-002 |
5.2.2 Group-Broadcast Group (e.g., announcement group) |
|
R-5.2.2-001 R-5.2.2-001 |
R-5.2.2-002 R-5.2.2-002 |
R-5.2.2-003 R-5.2.2-003 |
R-5.2.2-004 R-5.2.2-004 |
5.2.3 User-Broadcast Group (e.g., System Communication) |
|
R-5.2.3-001 R-5.2.3-001 |
R-5.2.3-002 R-5.2.3-002 |
5.3 Late call entry |
|
R-5.3-001 R-5.3-001 |
R-5.3-002 R-5.3-002 |
R-5.3-003 R-5.3-003 |
R-5.3-004 R-5.3-004 |
R-5.3-005 R-5.3-005 |
|
5.4 Dynamic group management (i.e., dynamic regrouping) |
|
NA |
|
5.5 Receiving from multiple MCPTT calls |
|
5.5.1 Overview |
|
NA |
|
5.5.2 Requirements |
|
R-5.5.2-004 R-5.4.2-001 |
R-5.5.2-005 R-5.4.2-002 |
R-5.5.2-008 R-5.4.2-003 |
R-5.5.2-010 R-5.4.2-004 |
R-5.5.2-011 R-5.4.2-005 |
R-5.5.2-012 R-5.4.2-006 |
R-5.5.2-013 R-5.4.2-007 |
|
5.6 Private Call |
|
NA |
|
5.6.1 Private Call Overview |
|
NA |
|
5.6.2 Private Call (with Floor control) general requirements |
|
NA |
|
5.6.3 Private Call (with Floor control) commencement requirements |
|
NA |
|
5.6.4 Private Call (with Floor control) termination |
|
NA |
|
5.6.5 Private Call (with Floor control) administration |
|
NA |
|
5.7 MCPTT priority requirements |
|
NA |
|
5.7.1 Overview |
|
NA |
|
5.7.2 Call types based on priorities |
|
NA |
|
5.7.2.1 MCPTT Emergency Group Call |
|
NA |
|
5.7.2.1.1 MCPTT Emergency Group Call requirements |
|
R-5.7.2.1.1-002 R-5.6.2.2.1-002 |
R-5.7.2.1.1-003 R-5.6.2.2.1-003 |
R-5.7.2.1.1-004 R-5.6.2.2.1-004 |
R-5.7.2.1.1-005 R-5.6.2.2.1-005 |
R-5.7.2.1.1-006 R-5.6.2.2.1-006 |
R-5.7.2.1.1-007 R-5.6.2.2.1-007 |
R-5.7.2.1.1-008 R-5.6.2.2.1-008 |
R-5.7.2.1.1-009 R-5.6.2.2.1-009 |
R-5.7.2.1.1-010 R-5.6.2.2.1-010 |
R-5.7.2.1.1-011 R-5.6.2.2.1-011 |
R-5.7.2.1.1-012 R-5.6.2.2.1-012 |
R-5.7.2.1.1-013 R-5.6.2.2.1-013 |
R-5.7.2.1.1-014 R-5.6.2.2.1-014 |
R-5.7.2.1.1-001 R-5.6.2.2.1-001 |
5.7.2.1.2 MCPTT Emergency Group Call cancellation requirements |
|
R-5.7.2.1.2-001 R-5.6.2.2.2-001 |
R-5.7.2.1.2-002 R-5.6.2.2.2-002 |
R-5.7.2.1.2-003 R-5.6.2.2.2-003 |
R-5.7.2.1.2-004 R-5.6.2.2.2-004 |
R-5.7.2.1.2-005 R-5.6.2.2.2-005 |
|
5.7.2.2 Imminent Peril group call |
|
NA |
|
5.7.2.2.1 Imminent Peril group call requirements |
|
R-5.7.2.2.1-001 R-5.6.2.3.1-001 |
R-5.7.2.2.1-002 R-5.6.2.3.1-002 |
R-5.7.2.2.1-003 R-5.6.2.3.1-003 |
R-5.7.2.2.1-004 R-5.6.2.3.1-004 |
R-5.7.2.2.1-005 R-5.6.2.3.1-005 |
R-5.7.2.2.1-006 R-5.6.2.3.1-006 |
R-5.7.2.2.1-007 R-5.6.2.3.1-007 |
R-5.7.2.2.1-008 R-5.6.2.3.1-008 |
R-5.7.2.2.1-009 R-5.6.2.3.1-009 |
|
5.7.2.2.2 Imminent Peril group call cancellation requirements |
|
R-5.7.2.2.2-001 R-5.6.2.3.2-001 |
R-5.7.2.2.2-002 R-5.6.2.3.2-002 |
R-5.7.2.2.2-003 R-5.6.2.3.2-003 |
R-5.7.2.2.2-004 R-5.6.2.3.2-004 |
5.7.2.3 MCPTT Emergency Private Call (with Floor Control) |
|
NA |
|
5.7.2.3.1 MCPTT Emergency Private Call (with Floor Control) requirements |
|
NA |
|
5.7.2.3.2 MCPTT Emergency Private Call (with Floor Control) cancellation requirements |
|
NA |
|
5.7.2.4 MCPTT Emergency Alert |
|
NA |
|
5.7.2.4.1 MCPTT Emergency Alert requirements |
|
R-5.7.2.4.1-001 R-5.6.2.4.1-001 |
R-5.7.2.4.1-002 R-5.6.2.4.1-002 |
R-5.7.2.4.1-003 R-5.6.2.4.1-003 |
R-5.7.2.4.1-004 R-5.6.2.4.1-004 |
R-5.7.2.4.1-005 R-5.6.2.4.1-005 |
R-5.7.2.4.1-006 R-5.6.2.4.1-006 |
R-5.7.2.4.1-007 R-5.6.2.4.1-007 |
R-5.7.2.4.1-008 R-5.6.2.4.1-008 |
R-5.7.2.4.1-009 R-5.6.2.4.1-009 |
R-5.7.2.4.1-010 R-5.6.2.4.1-010 |
R-5.7.2.4.1-011 R-5.6.2.4.1-011 |
R-5.7.2.4.1-012 R-5.6.2.4.1-012 |
5.7.2.4.2 MCPTT Emergency Alert cancellation requirements |
|
R-5.7.2.4.2-001 R-5.6.2.4.2-001 |
R-5.7.2.4.2-002 R-5.6.2.4.2-002 |
R-5.7.2.4.2-003 R-5.6.2.4.2-003 |
|
5.8 User ID |
|
R-5.8-001 R-5.7-001 |
R-5.8-002 R-5.7-002 |
R-5.8-003 R-5.7-003 |
|
5.9 MCPTT UE Management |
|
R-5.9-001 R-5.8-001 |
R-5.9-002 R-5.8-002 |
5.10 MCPTT User Profile |
|
R-5.10-001 R-5.9-001 |
R-5.10-002 R-5.9-002 |
5.11 Support for multiple devices |
|
R-5.11-001 R-5.10-001 |
R-5.11-002 R-5.10-002 |
5.12 Location |
|
R-5.12-001 R-5.11-001, R-5.11-002 |
R-5.12-002 R-5.11-003 |
R-5.12-003 R-5.11-004 |
R-5.12-004 R-5.11-005 |
R-5.12-005 R-5.11-006 |
R-5.12-006 R-5.11-007 |
R-5.12-007 R-5.11-008 |
R-5.12-008 R-5.11-009 |
R-5.12-009 R-5.11-010 |
R-5.12-010 R-5.11-011 |
R-5.12-012 R-5.11-012 |
R-5.12-013 R-5.11-013 |
R-5.12-014 R-5.11-014 |
R-5.12-015 R-5.11-015 |
5.13 Security |
|
R-5.13-001 R-5.12-001 |
R-5.13-002 R-5.12-002 |
R-5.13-003 R-5.12-003 |
R-5.13-004 R-5.12-004 |
R-5.13-005 R-5.12-005 |
R-5.13-006 R-5.12-006 |
R-5.13-007 R-5.12-007 |
R-5.13-008 R-5.12-008 |
R-5.13-009 R-5.12-009 |
R-5.13-010 R-5.12-010 |
R-5.13-011 R-5.12-011 |
R-5.13-012 R-5.12-012 |
R-5.13-013 R-5.12-013 |
|
5.14 Audio/voice quality |
|
R-5.14-001 R-5.13-001 |
|
5.15 Interactions between MCPTT Group calls and MCPTT Private Calls (with Floor Control) |
|
NA |
|
5.16 Relay requirements |
|
R-5.16-001 R-5.14-001 |
R-5.16-002 R-5.14-002 |
R-5.16-003 R-5.14-003 |
|
5.17 Gateway Requirements |
|
R-5.17-001 R-5.15-001 |
|
5.18 Control and management by Mission Critical Organizations |
|
NA |
|
5.18.1 Overview |
|
NA |
|
5.18.2 General Requirements |
|
R-5.18.2-001 R-5.16.2-001 |
R-5.18.2-002 R-5.16.2-002 |
R-5.18.2-003 R-5.16.2-003 |
R-5.18.2-004 R-5.16.2-004 |
R-5.18.2-005 R-5.16.2-005 |
|
5.18.3 Operational visibility for Mission Critical Organizations |
|
R-5.18.3-001 R-5.16.3-001 |
|
5.19 General Administrative – groups and users |
|
R-5.19-001 R-5.17-001 |
R-5.19-002 R-5.17-002 |
R-5.19-003 R-5.17-003 |
R-5.19-004 R-5.17-004 |
R-5.19-005 R-5.17-005 |
R-5.19-006 R-5.17-006 |
R-5.19-007 R-5.17-007 |
R-5.19-008 R-5.17-008 |
6 MCPTT Service requirements specific to on-network use |
|
NA |
|
6.1 General administrative – groups and users |
|
R-6.1-001 R-6.1-001 |
R-6.1-002 R-6.1-002 |
R-6.1-003 R-6.1-003 |
R-6.1-006 R-6.1-004 |
R-6.1-007 R-6.1-005 |
|
6.2 MCPTT calls |
|
NA |
|
6.2.1 Commencement modes for MCPTT Group calls |
|
NA |
|
|
|
6.2.2 Queuing |
|
R-6.2.2-001 R-6.2.2-001 |
R-6.2.2-002 R-6.2.2-002 |
R-6.2.2-003 R-6.2.2-003 |
R-6.2.2-004 R-6.2.2-004 |
R-6.2.2-005 R-6.2.2-005 |
R-6.2.2-006 R-6.2.2-006 |
6.2.3 Floor control |
|
NA |
|
6.2.3.1 General aspects |
|
NA |
|
6.2.3.2 Requesting permission to transmit |
|
NA |
|
6.2.3.3 Override |
|
NA |
|
6.2.3.3.1 General aspects |
|
NA |
|
6.2.3.3.2 Override – one transmitting Participant |
|
NA |
|
6.2.3.3.3 Override – simultaneously Transmitting MCPTT Group Members |
|
NA |
|
6.2.3.4 Terminating permission to transmit |
|
NA |
|
|
|
6.2.3.5 Transmit time limit |
|
NA |
|
6.2.3.6 Audio cut-in designated MCPTT Groups |
|
NA |
|
6.2.3.6.1 Overview |
|
NA |
|
6.2.3.6.2 Requirements |
|
NA |
|
6.2.3.6.3 Requesting permission to transmit |
|
NA |
|
6.2.3.6.4 Terminating permission to transmit |
|
NA |
|
6.2.3.6.5 Transmit time limit |
|
NA |
|
6.2.3.7 MCPTT Groups designated for multi-talker control |
|
NA |
|
6.2.3.7.1 Overview |
|
NA |
|
6.2.3.7.2 General Aspects |
|
NA |
|
6.2.3.7.3 Requesting permission to transmit |
|
NA |
|
6.2.3.7.3 Requesting permission to transmit |
|
NA |
|
6.2.3.7.4 Override |
|
NA |
|
6.2.3.7.4.1 General Aspects |
|
NA |
|
6.2.4 Call termination |
|
NA |
|
|
|
6.3 General requirements |
|
R-6.3-001 R-6.3-001 |
R-6.3-002 R-6.3-002 |
R-6.3-003 R-6.3-003 |
R-6.3-004 R-6.3-004 |
6.4 General group call |
|
NA |
|
6.4.1 General aspects |
|
R-6.4.1-001 R-6.4.1-001 |
|
6.4.2 Group status/information |
|
R-6.4.2-001 R-6.4.2-001 |
R-6.4.2-002 R-6.4.2-002 |
R-6.4.2-003 R-6.4.2-003 |
R-6.4.2-004 R-6.4.2-004 |
R-6.4.2-005 R-6.4.2-005 |
R-6.4.2-006 R-6.4.2-006 |
R-6.4.2-007 R-6.4.2-007 |
|
6.4.3 Identification |
|
R-6.4.3-001 R-6.4.3-001 |
R-6.4.3-002 R-6.4.3-002 |
6.4.4 Membership/affiliation |
|
R-6.4.4-001 R-6.4.4-001 |
R-6.4.4-002 R-6.4.4-002 |
6.4.5 Membership/affiliation list |
|
R-6.4.5-001 R-6.4.5-001 |
R-6.4.5-002 R-6.4.5-002 |
R-6.4.5-003 R-6.4.5-003 |
R-6.4.5-004 R-6.4.5-004 |
R-6.4.5-005 R-6.4.5-005 |
R-6.4.5-006 R-6.4.5-006 |
R-6.4.5-007 R-6.4.5-007 |
R-6.4.5-008 R-6.4.5-008 |
6.4.6 Authorized user remotely changes another MCPTT User’s affiliated and/or Selected MCPTT Group(s) |
|
NA |
|
6.4.6.1 Mandatory change |
|
R-6.4.6.1-001 R-6.4.6.1-001 |
R-6.4.6.1-002 R-6.4.6.1-002 |
R-6.4.6.1-003 R-6.4.6.1-003 |
R-6.4.6.1-004 R-6.4.6.1-004 |
6.4.6.2 Negotiated change |
|
R-6.4.6.2-001 R-6.4.6.2-001 |
R-6.4.6.2-002 R-6.4.6.2-002 |
R-6.4.6.2-003 R-6.4.6.2-003 |
R-6.4.6.2-004 R-6.4.6.2-004 |
R-6.4.6.2-005 R-6.4.6.2-005 |
R-6.4.6.2-006 R-6.4.6.2-006 |
6.4.7 Prioritization |
|
R-6.4.7-001 R-6.4.7-001 |
R-6.4.7-002 R-6.4.7-002 |
R-6.4.7-003 R-6.4.7-003 |
R-6.4.7-004 R-6.4.7-004 |
6.4.8 Relay requirements |
|
R-6.4.8-001 R-6.4.8-001 |
|
6.4.9 Administrative |
|
R-6.4.9-001 R-6.4.9-001 |
R-6.4.9-003 R-6.4.9-002 |
R-6.4.9-004 R-6.4.9-003 |
R-6.4.9-007 R-6.4.9-004 |
R-6.4.9-006 R-6.4.9-005 |
R-6.4.9-007 R-6.4.9-006 |
6.5 Broadcast Group |
|
NA |
|
6.5.1 General Broadcast Group Call |
|
R-6.5.1-001 R-6.5.1-001 |
R-6.5.1-002 R-6.5.1-002 |
6.5.2 Group-Broadcast Group (e.g., announcement group) |
|
R-6.5.2-001 R-6.5.2-001 |
|
6.5.3 User-Broadcast Group (e.g., System Call) |
|
R-6.5.3-001 R-6.5.3-001 |
|
6.6 Dynamic group management (i.e., dynamic reporting) |
|
NA |
|
6.6.1 General dynamic regrouping |
|
R-6.6.1-001 R-6.6.1-001 |
R-6.6.1-002 R-6.6.1-002 |
R-6.6.1-003 R-6.6.1-003 |
R-6.6.1-004 R-6.6.1-004 |
R-6.6.1-005 R-6.6.1-005 |
R-6.6.1-006 R-6.6.1-006 |
6.6.2 Group Regrouping |
|
NA |
|
6.6.2.1 Service Description |
|
NA |
|
6.6.2.2 Requirements |
|
R-6.6.2.2-001 R-6.6.2.2-001 |
R-6.6.2.2-002 R-6.6.2.2-002 |
R-6.6.2.2-003 R-6.6.2.2-003 |
R-6.6.2.2-004 R-6.6.2.2-004 |
R-6.6.2.2-005 R-6.6.2.2-005 |
R-6.6.2.2-006 R-6.6.2.2-006 |
R-6.6.2.2-007 R-6.6.2.2-007 |
|
6.6.3 Temporary Group-Broadcast Group |
|
R-6.6.3-001 R-6.6.3-001 |
R-6.6.3-002 R-6.6.3-002 |
6.6.4 User regrouping |
|
NA |
|
6.6.4.1 Service description |
|
NA |
|
6.6.4.2 Requirements |
|
R-6.6.4.2-001 R-6.6.4.2-001 |
R-6.6.4.2-002 R-6.6.4.2-002 |
R-6.6.4.2-003 R-6.6.4.2-003 |
R-6.6.4.2-004 R-6.6.4.2-004 |
R-6.6.4.2-005 R-6.6.4.2-005 |
|
6.7 Private Call |
|
NA |
|
6.7.0 Overview |
|
NA |
|
6.7.1 General Requirements |
|
R-6.7.1-002 R-6.7.2-001 |
R-6.7.1-003 R-6.7.2-002 |
R-6.7.1-004 R-6.7.2-003 |
R-6.7.1-011 R-6.7.2-004 |
R-6.7.1-014 R-6.7.2-005 |
|
6.7.2 Administrative |
|
R-6.7.2-001 R-6.7.3-001 |
R-6.7.2-002 R-6.7.3-002 |
R-6.7.2-003 R-6.7.3-003 |
R-6.7.2-004 R-6.7.3-004 |
R-6.7.2-005 R-6.7.3-005 |
R-6.7.2-006 R-6.7.3-006 |
R-6.7.2-007 R-6.7.3-007 |
R-6.7.2-008 R-6.7.3-008 |
6.7.3 Prioritization |
|
R-6.7.3-001 R-6.7.4-001 |
R-6.7.3-002 R-6.7.4-002 |
R-6.7.3-003 R-6.7.4-003 |
R-6.7.3-004 R-6.7.4-004 |
R-6.7.3-005 R-6.7.4-005 |
R-6.7.3-006 R-6.7.4-006 |
R-6.7.3-007 R-6.7.4-007 |
|
6.7.4 Private Call (without Floor control) commencement requirements |
|
R-6.7.4-004 R-6.7.5-001 |
R-6.7.4-008 R-6.7.5-002 |
R-6.7.4-011 R-6.7.5-003 |
|
6.7.4a Private Call (with Floor control) commencement requirements |
|
NA |
|
6.7.5 Private Call (without Floor control) termination |
|
R-6.7.5-001 R-6.7.6-001 |
R-6.7.5-003 R-6.7.6-002 |
6.7.6 Call back request requirements |
|
NA |
|
6.8 MCPTT Priority Requirements |
|
NA |
|
6.8.1 General |
|
R-6.8.1-001 R-6.8.1-001 |
R-6.8.1-003 R-6.8.1-002 |
R-6.8.1-004 R-6.8.1-003 |
R-6.8.1-005 R-6.8.1-004 |
R-6.8.1-006 R-6.8.1-005 |
R-6.8.1-007 R-6.8.1-006 |
R-6.8.1-008 R-6.8.1-007 |
R-6.8.1-009 R-6.8.1-008 |
R-6.8.1-010 R-6.8.1-009 |
R-6.8.1-011 R-6.8.1-010 |
R-6.8.1-012 R-6.8.1-011 |
R-6.8.1-013 R-6.8.1-012 |
R-6.8.1-014 R-6.8.1-013 |
R-6.8.1-015 R-6.8.1-014 |
R-6.8.1-016 R-6.8.1-015 |
R-6.8.1-017 R-6.8.1-016 |
6.8.2 3GPP system access controls |
|
R-6.8.2-001 R-6.8.2-001 |
|
6.8.3 3GPP system admission controls |
|
R-6.8.3-001 R-6.8.3-001 |
|
6.8.4 3GPP system scheduling controls |
|
R-6.8.4-001 R-6.8.4-001 |
|
6.8.5 UE access controls |
|
R-6.8.5-001 R-6.8.5-001 |
|
6.8.6 Application layer priorities |
|
NA |
|
6.8.6.1 Overview |
|
NA |
|
6.8.6.2 Requirements |
|
R-6.8.6.2-001 R-6.8.7.2-001 |
R-6.8.6.2-002 R-6.8.7.2-002 |
R-6.8.6.2-003 R-6.8.7.2-003 |
R-6.8.6.2-005 R-6.8.7.2-004 |
R-6.8.6.2-006 R-6.8.7.2-005 |
|
6.8.7 Call types based on priorities |
|
NA |
|
6.8.7.1 MCPTT Emergency Group Call requirements |
|
R-6.8.7.1-001 R-6.8.8.1-001 |
R-6.8.7.1-002 R-6.8.8.1-002 |
R-6.8.7.1-003 R-6.8.8.1-003 |
R-6.8.7.1-004 R-6.8.8.1-004 |
6.8.7.2 MCPTT Emergency Private Call (with Floor control) requirements |
|
NA |
|
6.8.7.3 Imminent Peril group call requirements |
|
R-6.8.7.3-001 R-6.8.8.3-001 |
R-6.8.7.3-002 R-6.8.8.3-002 |
R-6.8.7.3-003 R-6.8.8.3-003 |
|
6.8.7.4 MCPTT Emergency Alert |
|
NA |
|
6.8.7.4.1 Requirements |
|
R-6.8.7.4.1-001 R-6.8.8.4.1-001 |
R-6.8.7.4.1-002 R-6.8.8.4.1-002 |
R-6.8.7.4.1-003 R-6.8.8.4.1-003 |
R-6.8.7.4.1-004 R-6.8.8.4.1-004 |
R-6.8.7.4.1-005 R-6.8.8.4.1-005 |
R-6.8.7.4.1-006 R-6.8.8.4.1-006 |
6.8.7.4.2 MCPTT Emergency Alert cancellation requirements |
|
R-6.8.7.4.2-001 R-6.8.8.4.2-001 |
R-6.8.7.4.2-002 R-6.8.8.4.2-002 |
6.9 IDs and aliases |
|
R-6.9-001 R-6.9-001 |
R-6.9-002 R-6.9-002 |
R-6.9-003 R-6.9-003 |
R-6.9-004 R-6.9-004 |
6.10 User Profile Management |
|
R-6.10-001 R-6.10-001 |
R-6.10-002 R-6.10-002 |
R-6.10-003 R-6.10-003 |
R-6.10-004 R-6.10-004 |
6.11 Support for multiple devices |
|
R-6.11-001 R-6.11-001 |
R-6.11-002 R-6.11-002 |
R-6.11-003 R-6.11-003 |
|
6.12 Location |
|
R-6.12-001 R-6.12-001 |
R-6.12-002 R-6.12-002 |
R-6.12-003 R-6.12-003 |
R-6.12-004 R-6.12-004 |
R-6.12-005 R-6.12-005 |
R-6.12-006 R-6.12-006 |
R-6.12-007 R-6.12-007 |
|
6.13 Security |
|
NA |
|
6.13.1 Overview |
|
NA |
|
6.13.2 Cryptographic protocols |
|
R-6.13.2-001 R-6.13.2-001 |
R-6.13.2-002 R-6.13.2-002 |
R-6.13.2-003 R-6.13.2-003 |
|
6.13.3 Authentication |
|
R-6.13.3-001 R-6.13.3-001 |
|
6.13.4 Access control |
|
R-6.13.4-001 R-6.13.4-001 |
R-6.13.4-002 R-6.13.4-002 |
R-6.13.4-003 R-6.13.4-003 |
R-6.13.4-004 R-6.13.4-004 |
R-6.13.4-005 R-6.13.4-005 |
R-6.13.4-006 R-6.13.4-006 |
R-6.13.4-007 R-6.13.4-007 |
R-6.13.4-008 R-6.13.4-008 |
R-6.13.4-009 R-6.13.4-009 |
R-6.13.4-010 R-6.13.4-010 |
6.13.5 Regulatory Issues |
|
R-6.13.5-001 R-6.13.5-001 |
|
6.14 Interactions for MCPTT Group Calls and MCPTT Private Calls |
|
R-6.14-001 R-6.14-001 |
R-6.14-002 R-6.14-002 |
6.15 Audio MCPTT call performance |
|
NA |
|
6.16 Additional services for MCPTT calls |
|
NA |
|
6.16.1 Discreet listening capabilities |
|
R-6.16.1-001 R-6.15.1-001 |
|
6.16.2 Ambient listening |
|
NA |
|
6.16.2.1 Overview of ambient listening |
|
NA |
|
6.16.2.2 Ambient listening requirements |
|
NA |
|
6.16.2.2.1 General Ambient Listening Requirements |
|
R-6.16.2.2.1-001 R-6.15.2.2.1-001 |
R-6.16.2.2.1-002 R-6.15.2.2.1-002 |
R-6.16.2.2.1-003 R-6.15.2.2.1-003 |
|
6.16.2.2.2 Remotely initiated ambient listening requirements |
|
R-6.16.2.2.2-001 R-6.15.2.2.2-001 |
R-6.16.2.2.2-002 R-6.15.2.2.2-002 |
6.16.2.2.3 Locally initiated ambient listening requirements |
|
R-6.16.2.2.3-001 R-6.15.2.2.3-001 |
R-6.16.2.2.3-002 R-6.15.2.2.3-002 |
6.16.3 Remotely initiated MCPTT call |
|
NA |
|
6.16.3.1 Overview |
|
NA |
|
6.16.3.2 Requirements |
|
R-6.16.3.2-003 R-6.15.3.2-003 |
R-6.16.3.2-004 R-6.15.3.2-004 |
R-6.16.3.2-002 R-6.15.3.2-002 |
R-6.16.3.2-001 R-6.15.3.2-001 |
6.16.4 Recording and audit requirements |
|
R-6.16.4-001 R-6.15.4-001 |
R-6.16.4-002 R-6.15.4-002 |
R-6.16.4-005 R-6.15.4-005 |
R-6.16.4-006 R-6.15.4-006 |
R-6.16.4-007 R-6.15.4-007 |
R-6.16.4-008 R-6.15.4-008 |
R-6.16.4-009 R-6.15.4-009 |
R-6.16.4-010 R-6.15.4-010 |
R-6.16.4-003 R-6.15.4-003 |
R-6.16.4-004 R-6.15.4-004 |
6.17 Interaction with telephony services |
|
R-6.17-001 R-6.16-001 |
R-6.17-003 R-6.16-002 |
6.18 Interworking |
|
NA |
|
6.18.1 Non-3GPP access |
|
R-6.18.1-001 R-6.17.1-001 |
|
6.18.2 Interworking between MCCore systems |
|
R-6.18.2-001 R-6.17.2-001 |
R-6.18.2-002 R-6.17.2-002 |
R-6.18.2-003 R-6.17.2-003 |
R-6.18.2-004 R-6.17.2-004 |
R-6.18.2-005 R-6.17.2-005 |
R-6.18.2-006 R-6.17.2-006 |
R-6.18.2-007 R-6.17.2-007 |
|
6.18.3 Interworking with non-3GPP PTT systems |
|
NA |
|
6.18.3.1 Overview |
|
NA |
|
6.18.3.2 Project 25 |
|
NA |
|
6.18.3.3 TETRA |
|
NA |
|
6.18.3.4 Legacy land mobile radio |
|
NA |
|
6.18.4 GSM-R |
|
NA |
|
6.18.4.1 Overview |
|
NA |
|
6.18.4.2 Requirements |
|
NA |
|
6.19 MCPTT coverage extension using ProSe UE-to-Network Relays |
|
R-6.19-001 R-6.18-001 |
R-6.19-002 R-6.18-002 |
R-6.19-003 R-6.18-003 |
R-6.19-004 R-6.18-004 |
R-6.19-005 R-6.18-005 |
R-6.19-006 R-6.18-006 |
7 MCPTT Service Requirements specific to off-network use |
|
NA |
|
7.1 Off-network Push To Talk overview |
|
NA |
|
7.2 General off-network MCPTT requirements |
|
R-7.2-001 R-7.2-001 |
R-7.2-002 R-7.2-002 |
R-7.2-003 R-7.2-003 |
R-7.2-004 R-7.2-004 |
R-7.2-005 R-7.2-005 |
|
7.3 Floor control |
|
NA |
|
7.3.1 General Aspects |
|
NA |
|
7.3.2 Requesting permission to transmit |
|
NA |
|
7.3.3 Override |
|
NA |
|
7.3.4 Terminating permission to transmit |
|
NA |
|
7.3.5 Transmit time limit |
|
NA |
|
7.4 Call Termination |
|
R-7.4-003 R-7.4-001 |
R-7.4-004 R-7.4-002 |
R-7.4-005 R-7.4-003 |
R-7.4-006 R-7.4-004 |
7.5 Broadcast Group |
|
R-7.5-001 R-7.5-001 |
R-7.5-002 R-7.5-002 |
7.6 Dynamic group management (i.e., dynamic regrouping) |
|
NA |
|
7.7 MCPTT priority requirements |
|
R-7.7-001 R-7.6-001 |
R-7.7-003 R-7.6-002 |
7.8 Call types based on priorities |
|
NA |
|
7.8.1 MCPTT Emergency Group Call requirements |
|
R-7.8.1-001 R-7.7.1-001 |
R-7.8.1-002 R-7.7.1-002 |
R-7.8.1-003 R-7.7.1-003 |
|
7.8.2 MCPTTEmergency Group Call cancellation requirements |
|
R-7.8.2-001 R-7.7.2-001 |
|
7.8.3 Imminent Peril Call |
|
NA |
|
7.8.3.1 Imminent Peril group call requirements |
|
R-7.8.3.1-001 R-7.7.3.1-001 |
R-7.8.3.1-002 R-7.7.3.1-002 |
R-7.8.3.1-003 R-7.7.3.1-003 |
R-7.8.3.1-004 R-7.7.3.1-004 |
R-7.8.3.1-005 R-7.7.3.1-005 |
|
7.8.3.2 Imminent Peril group call cancellation requirements |
|
R-7.8.3.2-001 R-7.7.3.2-001 |
R-7.8.3.2-002 R-7.7.3.2-002 |
7.9 Location |
|
R-7.9-001 R-7.8-001 |
|
7.10 Security |
|
R-7.10-001 R-7.9-001 |
R-7.10-002 R-7.9-002 |
7.11 Audio MCPTT Call performance |
|
NA |
|
7.11.1 MCPTT Access time and Mouth-to-ear latency |
|
NA |
|
7.11.1.1 General overview |
|
NA |
|
7.11.1.2 Requirements |
|
NA |
|
7.11.2 Late call entry performance |
|
NA |
|
7.11.2.1 General overview |
|
NA |
|
7.11.2.2 Requirements |
|
NA |
|
7.11.3 Audio/voice quality |
|
NA |
|
7.12 Off-network MCPTT operations |
|
R-7.12-001 R-7.10-001 |
R-7.12-002 R-7.10-002 |
R-7.12-003 R-7.10-003 |
|
7.13 Off-network UE functionality |
|
R-7.13-001 R-7.11-001 |
R-7.13-002 R-7.11-002 |
R-7.13-003 R-7.11-003 |
|
7.14 Switching to off-network MCPTT |
|
R-7.14-001 R-7.13-001 |
R-7.14-002 R-7.13-002 |
R-7.14-003 R-7.13-003 |
|
7.15 Off-network recording and audit requirements |
|
R-7.15-001 R-7.14-001 |
R-7.15-002 R-7.14-002 |
7.16 Off-network UE-to-UE relay |
|
NA |
|
7.16.1 Private Communications |
|
R-7.16.1-001 R-7.15.1-001 |
R-7.16.1-002 R-7.15.1-002 |
R-7.16.1-003 R-7.15.1-003 |
|
7.16.2 Group Communications |
|
R-7.16.2-001 R-7.15.2-001 |
R-7.16.2-002 R-7.15.2-002 |
Annex B (informative):
Bibliography
– 3GPP TS 22.115: "Service aspects; Charging and billing".
Annex C (informative):
MCPTT scalability guide
The MCPTT Service might support an authorized MCPTT UE to be an MCPTT member of at least 5,000 MCPTT Groups.
The MCPTT Service might support a minimum of 500,000 MCPTT Groups.
The MCPTT Service might support MCPTT Group membership from two MCPTT Users to all the MCPTT Users signed on the MCPTT system.
The MCPTT Service might support an MCPTT Group Call where all the Participants are located in one cell of the MCPTT system.
The MCPTT Service might support an MCPTT Group Call with one or more Participants located in every cell of the MCPTT system.
The MCPTT Service might support a range of 36 to 150 simultaneous MCPTT Group Calls in every cell of the MCPTT system per regional regulatory requirement.
The MCPTT Service might support a minimum of 2000 MCPTT Users within an MCPTT Group or a combination of different MCPTT Groups, in every cell of the MCPTT system.
NOTE: The concurrent number of Participants in a cell is subject to radio capacity limitation in a cell per operator policy.
Annex D (informative):
Change history
Change history |
|||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
Work Item |
SP-66 |
SP-140844 |
Raised by MCC to version 13.0.0 following SA’s approval |
2.1.0 |
13.0.0 |
|||||||
SP-66 |
– |
– |
Correction of Figure 4.6.1-1 (previously corrupted) and of some typos, including: consistent use of capital and spaces instead of hyphens in "Push To Talk", removal of the requirement numbering for the three paragraph of sections 6.6.2.1 and 6.6.4.1 since they are not requirements |
13.0.0 |
13.0.1 |
||||||
SP-67 |
SP-150040 |
S1-150011 |
22.179 |
1 |
– |
Rel-13 |
F |
Replacement of Home and Visited by Primary and Partner |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150225 |
22.179 |
2 |
1 |
Rel-13 |
F |
Completion of application of S1-144278 |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150226 |
22.179 |
3 |
1 |
Rel-13 |
F |
Clarification of number and types of Private Calls |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150228 |
22.179 |
5 |
1 |
Rel-13 |
F |
Completion of application of S1-144570 |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150016 |
22.179 |
6 |
– |
Rel-13 |
F |
Improper use of ’emergency’ |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150230 |
22.179 |
7 |
2 |
Rel-13 |
D |
Correct use of MCPTT terminology |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150229 |
22.179 |
8 |
1 |
Rel-13 |
F |
Clarifying KPI requirement |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150019 |
22.179 |
9 |
– |
Rel-13 |
D |
Wording correction |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150021 |
22.179 |
11 |
– |
Rel-13 |
F |
Change the title of TS 22.179 to align with MCPTT WID and agreed contribution S1-144232 |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150022 |
22.179 |
12 |
– |
Rel-13 |
D |
Changing Ues to UEs |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150023 |
22.179 |
13 |
– |
Rel-13 |
D |
Editorial clean ups |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150342 |
22.179 |
14 |
2 |
Rel-13 |
F |
Correction of type of Private Calls supported in for both on and off the network use. |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150025 |
22.179 |
15 |
– |
Rel-13 |
F |
Clarification of dedicated MCPTT Group type used for Imminent Peril Group call communication by MCPTT User |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150026 |
22.179 |
16 |
– |
Rel-13 |
F |
Replacement of personality management with user profile management |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150027 |
22.179 |
17 |
– |
Rel-13 |
F |
Modify text in first sentence of third paragraph for clause 7.1 Off-Network Push-to-Talk overview. |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150028 |
22.179 |
18 |
– |
Rel-13 |
F |
Replacement of clause 5.14 title Audio/ video quality with Audio/ voice quality. |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150232 |
22.179 |
19 |
1 |
Rel-13 |
F |
Convert 2nd sentence of 5th requirement in clause 6.2.4 Call Termination into a new requirement |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150309 |
22.179 |
20 |
2 |
Rel-13 |
F |
Move two requirements from clause 6.1 General Administrative -groups and users into common clause 5.19 General Administrative -groups and users. |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150234 |
22.179 |
21 |
1 |
Rel-13 |
B |
Charging for MCPTT usage |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150092 |
22.179 |
22 |
– |
Rel-13 |
F |
Reinstatement of MCPTT User Profile |
13.0.1 |
13.1.0 |
MCPTT-SA1 |
SP-67 |
SP-150040 |
S1-150093 |
22.179 |
23 |
– |
Rel-13 |
F |
Fix improper multiple requirements |
13.0.1 |
13.1.0 |
MCPTT-SA1 |
SP-67 |
SP-150040 |
S1-150094 |
22.179 |
24 |
– |
Rel-13 |
F |
Remove implementation-specific requirement for default value |
13.0.1 |
13.1.0 |
MCPTT-SA1 |
SP-67 |
SP-150040 |
S1-150236 |
22.179 |
26 |
1 |
Rel-13 |
F |
CR- to clarify requirements in 6.4.9 and 6.2.4. |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150265 |
22.179 |
28 |
1 |
Rel-13 |
F |
CR to clarify what call type refers to in 6.2.3.3.1 |
13.0.1 |
13.1.0 |
MCPTT |
SP-67 |
SP-150040 |
S1-150107 |
22.179 |
30 |
– |
Rel-13 |
D |
Separation of supplementary service, callback, requirements |
13.0.1 |
13.1.0 |
MCPTT |
SP-68 |
SP-150354 |
– |
22.179 |
31 |
1 |
Rel-13 |
F |
Clarification on the update and use of codecs in MCPTT |
13.1.0 |
13.2.0 |
MCPTT |
SP-68 |
SP-150355 |
– |
22.179 |
32 |
1 |
Rel-13 |
F |
Clarification on Broadcast Groups Off-Network Requirement R-7.5-002 |
13.1.0 |
13.2.0 |
MCPTT |
SP-70 |
SP-150750 |
S1-154482 |
22.179 |
0033 |
1 |
Rel-13 |
F |
Edits, formatting, and style corrections |
13.2.0 |
13.3.0 |
MCPTT |
SP-70 |
SP-150750 |
S1-154483 |
22.179 |
0034 |
1 |
Rel-13 |
F |
MCPTT Emergency Group Call correction |
13.2.0 |
13.3.0 |
MCPTT |
SP-70 |
SP-150750 |
S1-154546 |
22.179 |
0035 |
1 |
Rel-13 |
F |
KPI 4 when MBMS is used |
13.2.0 |
13.3.0 |
MCPTT |
SP-71 |
SP-160103 |
S1-160313 |
22.179 |
0036 |
1 |
Rel-14 |
C |
Mission Critical Push to Talk over LTE Realignment (MCPTT-R) |
13.3.0 |
14.0.0 |
MCImp-MCPTTR |
SP-72 |
SP-160359 |
S1-161580 |
22.179 |
38 |
3 |
Rel-14 |
B |
Inclusion of “first-to-answer” commencement mode for private calls |
14.0.0 |
14.1.0 |
MCPTT |
SP-72 |
SP-160391 |
– |
22.179 |
40 |
Rel-14 |
B |
Introduction of Audio cut-in requirements in MCPTT |
14.0.0 |
14.1.0 |
MCImp-MCPTTR |
|
SP-72 |
SP-160359 |
S1-161626 |
22.179 |
37 |
2 |
Rel-14 |
C |
Mission Critical Push to Talk over LTE for Realignment (MCPTT-R) |
14.0.0 |
14.1.0 |
MCPTT |
SP-73 |
SP-160542 |
S1-162402 |
22.179 |
0043 |
1 |
Rel-14 |
F |
Remove definitions for participant and participant type in MCPTT TS 22.179 that are being added to MCCoRe TS 22.280. |
14.1.0 |
14.2.0 |
MCImp-MCPTTR |
SP-73 |
SP-160542 |
S1-162404 |
22.179 |
0044 |
1 |
Rel-14 |
D |
In MCPTT TS 22.179 Provide editorial changes to sub-clause 6.6.2.2. |
14.1.0 |
14.2.0 |
MCImp-MCPTTR |
SP-73 |
SP-160542 |
S1-162405 |
22.179 |
0045 |
1 |
Rel-14 |
F |
Remove definition for Mission Critical Organization in MCPTT TS 22.179 that was added to MCCoRe TS 22.280 as a common definition. |
14.1.0 |
14.2.0 |
MCImp-MCPTTR |
SP-73 |
SP-160542 |
S1-162400 |
22.179 |
0046 |
1 |
Rel-14 |
F |
Clarifications and corrections to audio cut-in |
14.1.0 |
14.2.0 |
MCImp-MCPTTR |
SP-74 |
SP-160890 |
0047 |
|
D |
Editorial change to MCPTT TS 22.179 sub-clause 6.2.3.6.2 |
14.2.0 |
14.3.0 |
||||
SP-74 |
SP-160890 |
0048 |
|
D |
Editorial changes to Annex A1 sub-clause 6.2.3.6 |
14.2.0 |
14.3.0 |
||||
SP-170445 |
0052 |
6 |
B |
multi-talker group call |
14.3.0 |
15.0.0 |
|||||
SP-77 |
SP-170696 |
S1-173507 |
22.179 |
0054 |
2 |
Rel-15 |
F |
Clarify MCPTT group in 6.2.3.7 |
15.0.0 |
15.1.0 |
MONASTERY |
SP-77 |
SP-170696 |
S1-173506 |
22.179 |
0055 |
3 |
Rel-15 |
F |
Correction on behavior of groups configured for multi talker control wrt groups using public safety floor control |
15.0.0 |
15.1.0 |
MONASTERY |
SP-78 |
SP-170985 |
S1-174039 |
22.179 |
0057 |
Rel-15 |
F |
Removing ‘over LTE’ from the title of the specification |
15.1.0 |
15.2.0 |
MCOver |
|
SP-78 |
SP-170985 |
S1-174541 |
22.179 |
0058 |
1 |
Rel-15 |
F |
Updates to the wording in the specification to clarify that the requirements are applicable from LTE onwards |
15.1.0 |
15.2.0 |
MCOver |
SP-78 |
SP-170997 |
S1-174424 |
22.179 |
0061 |
3 |
Rel-16 |
B |
Addition of requirement on interworking with SCP in GSM-R |
15.2.0 |
16.0.0 |
MONASTERY2 |
SP-79 |
SP-180134 |
0062 |
1 |
B |
Adding more functionality to interworking between FRMCS and GSM-R |
16.0.0 |
16.1.0 |
||||
SP-180310 |
0064 |
4 |
F |
Interworking between MCX Service system and GSM-R |
16.1.0 |
16.2.0 |
|||||
SP-180310 |
0063 |
2 |
B |
Adding functionality to 22.179 to support assured voice communication |
16.1.0 |
16.2.0 |
|||||
SP-81 |
SP-180757 |
S1-182565 |
22.179 |
0066 |
1 |
Rel-16 |
B |
Enhancement for interworking of group communication between FRMCS and GSM-R |
16.2.0 |
16.3.0 |
MONASTERY2 |
SP-81 |
SP-180761 |
S1-182613 |
22.179 |
0065 |
1 |
Rel-16 |
B |
Application of MCPTT to maritime usage |
16.2.0 |
16.3.0 |
MARCOM |
Change history |
|||||||
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
2018-12 |
SP-82 |
SP-181000 |
0067 |
1 |
C |
Addition of new Group Call Commencement Modes |
16.4.0 |
2018-12 |
SP-82 |
SP-181000 |
0068 |
1 |
B |
Move interworking of functional alias from MCPTT to MCCoRe TS, MCPTT part |
16.4.0 |
2019-03 |
SA#83 |
SP-190084 |
0069 |
|
B |
Add forwarding for private calls |
16.5.0 |
2019-12 |
SA#86 |
SP-191036 |
0073 |
1 |
C |
Group and Private call setup KPIs |
17.0.0 |
2022-03 |
SP#95e |
SP-220081 |
0075 |
1 |
F |
Clarification on use of MCPTT Late call entry KPIs |
17.1.0 |