hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.4 3GPP system scheduling controls | [R-6.8.4-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.5 UE access controls | [R-6.8.5-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.6 Application layer priorities | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.6.1 Overview | Dispatchers from different critical communication organizations access the same networks and network resources. Depending on the event, the priority is given to an organization and/or a group rather than to another. For instance, in case of a fire priority is given to the fire brigades dealing with it, while in case of a criminal arrest priority is given to the police officers in charge of the arrest. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.6.2 Requirements | [R-6.8.6.2-001] Void
[R-6.8.6.2-002] Void
[R-6.8.6.2-003] Void
[R-6.8.6.2-004] The MCPTT system may stop already established MCPTT calls with the capability to be pre-empted and a lower application layer priority to allow a new MCPTT call with pre-emption capability enabled for pre-emption to be established.
[R-6.8.6.2-005] Void
[R-6.8.6.2-006] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.7 Call types based on priorities | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.7.1 MCPTT Emergency Group Call requirements | [R-6.8.7.1-001] Void
[R-6.8.7.1-002] Void
[R-6.8.7.1-003] Void
[R-6.8.7.1-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.7.2 MCPTT Emergency Private Call (with Floor control) requirements | [R-6.8.7.2-001] The MCPTT Service shall ensure that MCPTT Emergency Private Calls (with Floor control) have the highest priority over all other MCPTT Private Calls.
[R-6.8.7.2-002] The MCPTT Service shall be capable of requesting increased priority for the Participants of an MCPTT Emergency Private Call.
[R-6.8.7.2-003] The MCPTT Service shall be capable of changing a Private Call (with Floor control) in progress to an MCPTT Emergency Private Call (with Floor control).
[R-6.8.7.2-004] MCPTT Emergency Private Calls (with Floor control), including their content and signalling, shall have pre-emptive priority over all other types of MCPTT calls, except System Calls, MCPTT Emergency Group Calls and other MCPTT Emergency Private Calls (with Floor control). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.7.3 Imminent Peril group call requirements | [R-6.8.7.3-001] Void
[R-6.8.7.3-002] Void
[R-6.8.7.3-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.7.4 MCPTT Emergency Alert | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.7.4.1 Requirements | [R-6.8.7.4.1-001] Void
[R-6.8.7.4.1-002] Void
[R-6.8.7.4.1-003] Void
[R-6.8.7.4.1-004] Void
[R-6.8.7.4.1-005] Void
[R-6.8.7.4.1-006] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.7.4.2 MCPTT Emergency Alert cancellation requirements | [R-6.8.7.4.2-001] Void
[R-6.8.7.4.2-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.9 IDs and aliases | [R-6.9-001] Void
[R-6.9-002] Void
[R-6.9-003] Void
[R-6.9-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.10 User Profile management | [R-6.10-001] Void
[R-6.10-002] Void
[R-6.10-003] Void
[R-6.10-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.11 Support for multiple devices | [R-6.11-001] Void
[R-6.11-002] Void
[R-6.11-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.12 Location | [R-6.12-001] Void
[R-6.12-002] Void
[R-6.12-003] Void
[R-6.12-004] Void
[R-6.12-005] Void
[R-6.12-006] Void
[R-6.12-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.13 Security | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.13.1 Overview | Security covers areas designed to protect the confidentiality, integrity, and availability of information that is processed, stored, and transmitted. The security requirements listed here cover the areas of cryptographic protocols, authentication, access control, and regulatory issues. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.13.2 Cryptographic protocols | [R-6.13.2-001] Void
[R-6.13.2-002] Void
[R-6.13.2-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.13.3 Authentication | [R-6.13.3-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.13.4 Access control | [R-6.13.4-001] Void
[R-6.13.4-002] Void
[R-6.13.4-003] Void
[R-6.13.4-004] Void
[R-6.13.4-005] Void
[R-6.13.4-006] Void
[R-6.13.4-007] Void
[R-6.13.4-008] Void
[R-6.13.4-009] Void
[R-6.13.4-010] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.13.5 Regulatory issues | [R-6.13.5-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.14 Interactions for MCPTT Group Calls and MCPTT Private Calls | [R-6.14-001] Void
[R-6.14-002] Void
[R-6.14-003] The MCPTT Service shall only allow an MCPTT User to participate in one MCPTT Private Call (without Floor control) at a time. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15 Audio MCPTT call performance | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.1 General overview | Meeting the KPIs defined in the following subclauses is based on a number of factors, including the selection of appropriate protocols, minimizing messaging, the backhaul technology used, and appropriate configuration of the deployed network. The corresponding requirements are intended to convey the resulting KPIs when all of those factors are taken into account. For example, where there is significant backhaul delay, that delay is expected to be added to the KPIs. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.2 General requirements | [R-6.15.2-001] The architecture and protocols providing the MCPTT Service shall be designed in a way to eventually allow a deployed network to meet the KPIs specified hereafter (subclause 6.15.3.2 and subclause 6.15.4.2). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.3 MCPTT access time and mouth-to-ear latency | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.3.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 request to speak (normally by pressing the MCPTT control on the MCPTT UE) and when this user gets a signal to start speaking. This time does not include confirmations from receiving users.
The MCPTT Access time (KPI 1) does not include the time for an MCPTT User to affiliate to the group. This is a common scenario within public safety, meaning that affiliations to MCPTT Groups are long lived during several working hours. KPI 1 is applicable in both an MCPTT Group call setup request and subsequent MCPTT Requests that are part of the same call. KPI 1 for subsequent MCPTT Requests might take a slightly shorter time than the first MCPTT setup request of the same call due to its potential need of resource allocation in terms of bearer establishment. However from an end user perspective there is no need to differentiate required performance for an MCPPT Group call setup request and subsequent MCPTT Requests.
The End-to-end MCPTT Access time (KPI 2) is defined as the time between when an MCPTT User requests to speak (normally by pressing the MCPTT control on the MCPTT UE) and when this user gets a signal to start speaking, including MCPTT call establishment (if applicable) and possibly acknowledgement from first receiving user before voice can be transmitted. Group calls can be set up with or without acknowledgements from receiving users.
For MCPTT Private Calls (with Floor control), end-to-end MCPTT Access time (also KPI 2) is measured from the initiating client’s Private call request to reception of either a Private Call response for automatic commencement or the MCPTT ringing indication for manual commencement. End-to-end access time for both automatic and manual commencement private calls (KPI 2) is shown in Figure 6.15.3.1.1.
NOTE: The End-to-end MCPTT Access time (KPI 2) is not applicable for an MCPTT Group transmission call setup when no acknowledgement is requested from any Affiliated MCPTT Group Member.
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 6.15.3.1.1 illustrates the MCPTT Access time and Mouth-to-ear latency.
Figure 6.15.3.1.1: Illustration of MCPTT access time and mouth-to-ear latency
6.15.3.2 Requirements
[R-6.15.3.2-001] KPI 1, KPI 2, and KPI 3 should be measured where there is negligible backhaul delay.
[R-6.15.3.2-002] The MCPTT Service shall provide the MCPTT Access time and Mouth-to-ear latency specified in this subclause to all MCPTT Users related to an MCPTT call regardless of call type (e.g., group, Private Call), group size and/or user density.
NOTE: This ensures that all MCPTT Users experience the same performance regardless of whether the audio is transferred over unicast or multicast delivery.
[R-6.15.3.2-003] The MCPTT Service shall be capable of providing the performance specified herein for all Affiliated MCPTT Group Members in the Group Call when there is not a transcoder in the bearer path.
[R-6.15.3.2-004] The MCPTT Service shall be capable of providing the performance specified herein for all Participants in a Private Call when there is not a transcoder in the bearer path.
[R-6.15.3.2-005] The KPIs defined in this subclause shall apply in an 3GPP network under traffic load not exceeding 70% of each network nodes capacity.
[R-6.15.3.2-006] On networks with QOS services, the KPIs defined in this subclause shall apply when the total sector loading of the serving sector by MCPTT Users with equal or greater priority than the subject MCPTT User is less than 70%.
[R-6.15.3.2-007] The KPIs defined in this subclause shall apply to group calls when the transmitting MCPTT User is connected to the MCPTT Service and has selected an MCPTT Group.
[R-6.15.3.2-008] The KPIs defined in this subclause shall apply to group calls when the receiving MCPTT User is connected to the MCPTT Service and affiliated with the MCPTT Group.
[R-6.15.3.2-009] The KPIs defined in this subclause shall apply to Automatic Commencement Private Calls when both the transmitting and receiving MCPTT Users are connected to the MCPTT Service.
[R-6.15.3.2-010] Void
[R-6.15.3.2-011] When there are transcoding functions in the bearer path of the MCPTT Service, the performance provided by the MCPTT Service shall be no more than 40 ms greater than the performance specified herein when there are no transcoding functions in the bearer path.
[R-6.15.3.2-012] For group calls where no acknowledgement is requested from affiliated MCPTT group members, the MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 95% of all MCPTT Request.
[R-6.15.3.2-012a] For group and private calls where the call is already established, the MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 95% of all MCPTT PTT Requests.
[R-6.15.3.2-013] For MCPTT Emergency Group Calls and Imminent Peril Calls the MCPTT Service shall provide an MCPTT Access time (KPI 1) less than 300 ms for 99% of all MCPTT Requests.
[R-6.15.3.2-014] For group calls where automatic acknowledgement is requested from the UEs of the affiliated MCPTT group members, the MCPTT Service shall provide an End-to-end MCPTT Access time (KPI 2) less than 1000 ms for users under coverage of the same network.
[R-6.15.3.2-015] The MCPTT Service shall provide a Mouth-to-ear latency (KPI 3) that is less than 300 ms for 95% of all voice bursts.
[R-6.15.3.2-016] There shall be no (0 ms) initial lost audio at receiving user.
[R-6.15.3.2-017] There shall be no (0 ms) trailing lost audio at the end of the voice burst at receiving user. [R-6.15.3.2-018] The KPIs defined in this subclause shall apply to Manual Commencement Private Calls when both the transmitting and receiving MCPTT Users are connected to the MCPTT Service.
[R-6.15.3.2-019] The MCPTT Service shall provide private call End-to-end MCPTT Access time (KPI 2) equal to or less than 1000 ms for users under coverage of the same network when the MCPTT private call is setup in the Manual Commencement mode.
[R-6.15.3.2-020] The MCPTT Service shall provide private call End-to-end MCPTT Access time (KPI 2) equal to or less than 1000 ms for users under coverage of the same network when the MCPTT private call is setup in the Automatic Commencement mode. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.4 Late call entry performance | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.4.1 General overview | An MCPTT User is able to join or leave already ongoing MCPTT Group calls. 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 a user decides to monitor such an MCPTT Group Call, to the time when the MCPTT 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. Figure 6.15.4.1.1 illustrates the Late call entry time.
Figure 6.15.4.1.1: Illustration of Late call entry time |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.4.2 Requirements | [R-6.15.4.2-001] The KPIs in this subclause shall apply for terrestrial use only, and when users are under coverage of the same network.
NOTE: Terrestrial use refers to using terrestrial 3GPP access, e.g. not using satellite 3GPP access. It includes support of air-to-ground scenarios, such as communication with MCPTT users in helicopters, fixed wing aircraft or other crewed aerial vehicles.
[R-6.15.4.2-002] The KPIs defined in this subclause shall apply in an 3GPP network under traffic load not exceeding 70% of each network nodes capacity.
[R-6.15.4.2-002a] The KPIs defined in this subclause shall apply to MCPTT users who have affiliated or have been affiliated by the network and are now performing late call entry due to activity on the affiliated group.
NOTE: Cases of UE mobility, or loss of coverage and re-establishment, are not covered.
[R-6.15.4.2-003] The maximum Late call entry time (KPI 4a) for calls without application layer encryption within one MCPTT system shall be less than 150 ms for 95% of all Late call entry requests.
[R-6.15.4.2-004] The maximum Late call entry time (KPI 4b) for application layer encrypted calls within one MCPTT system should meet the requirements for KPI 4 for unencrypted calls.
[R-6.15.4.2-005] The maximum Late call entry time (KPI 4b) for application layer encrypted calls within one MCPTT system shall be less than 350 ms for 95% of all Late Call Entries into encrypted calls.
[R-6.15.4.2-006] The Late call entry Time for encrypted calls interworking with other non-3GPP PTT systems should meet the requirements for KPI 4b for application layer encrypted calls within one MCPTT system.
NOTE: Additional delay deriving from the non-3GPP PTT system is not included in this KPI.
[R-6.15.4.2-007] The additional Late call entry Time for an MCPTT UE late entering an application layer encrypted call interworking with other non-3GPP PTT systems shall not exceed the difference in the encrypted and unencrypted Late call entry Times for the interworking system. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.5 Audio / voice quality | [R-6.15.5-001] The MCPTT UE shall support at least one mandatory 3GPP voice codec.
NOTE 1: The UE implementation could include other non-3GPP voice codecs, e.g., TETRA voice codecs, P25 voice codecs [4].
NOTE 2: Refer to [R-6.4.9-006], which enables an MCPTT Administrator to set the preferred voice codec for an MCPTT Group.
[R-6.15.5-002] When an MCPTT call is within one MCPTT system the average MOS-LQO shall be greater than or equal to 3.0 measured according to the ITU standard Perceptual Evaluation of Speech Quality (PESQ) as defined in P.862 [7] and P.862.1 [8].
[R-6.15.5-003] When an MCPTT call involves interworking with other non-3GPP PTT systems the average MOS-LQO shall be greater than or equal to 2.7 measured according to the ITU standard PESQ as defined in P.862 [7] and P.862.1 [8].
[R-6.15.5-004] When an MCPTT call is within one MCPTT system the average MOS-LQO shall be greater than or equal to 3.0 measured according to the ITU standard Perceptual Objective Listening Quality Assessment (POLQA) as defined in P.863 [9].
[R-6.15.5-005] When an MCPTT call involves interworking with other non-3GPP PTT systems the average MOS LQO shall be greater than or equal to 2.7 measured according to the ITU standard POLQA as defined in P.863 [9]. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.15.6 Radio Resource Efficiency Performance | [R-6.15.6-001] Void
[R-6.15.6-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16 Additional services for MCPTT calls | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.1 Discreet listening capabilities | [R-6.16.1-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.2 Ambient listening | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.2.1 Overview of ambient listening | Ambient Listening is a feature that allows an authorized MCPTT User, typically a dispatcher, to cause an MCPTT UE to initiate a call which results in no indication on the MCPTT UE that it is transmitting. Ambient Listening can be initiated by an authorized MCPTT User who wants to be listened to by another remote authorized MCPTT User or can be initiated by a remote authorized MCPTT User who wants to listen to another MCPTT User. The purpose of this feature allows a dispatcher to listen to activities at the Location of the remote MCPTT UE to find out what is happening around that MCPTT UE without providing an indication to the MCPTT User or people around the user (whom the MCPTT User does not want to make aware of this action) that this is happening. This type of call is different from other types of call, as for Ambient Listening audio is only transmitted to one party in the call (i.e., a dispatcher or an authorized MCPTT User that is acting in a similar role to a dispatcher).
This is used for stolen MCPTT UEs, monitoring officers, officer safety and particular operations, where it is important that the MCPTT UE does not indicate what is happening. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.2.2 Ambient listening requirements | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.2.2.1 General Ambient Listening requirements | [R-6.16.2.2.1-001] Void
[R-6.16.2.2.1-002] Void
[R-6.16.2.2.1-003] Void
[R-6.16.2.2.1-004] The MCPTT Service shall terminate Ambient Listening if the MCPTT User being listened to starts to transmit in an MCPTT Private Call or an MCPTT Group Call.
NOTE: An authorized MCPTT User could initiate Discreet Listening at this point if needed. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.2.2.2 Remotely initiated Ambient Listening requirements | [R-6.16.2.2.2-001] Void
[R-6.16.2.2.2-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.2.2.3 Locally initiated Ambient Listening requirements | [R-6.16.2.2.3-001] Void
[R-6.16.2.2.3-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.3 Remotely initiated MCPTT call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.3.1 Overview | A Remotely initiated MCPTT Call is a feature that allows an authorized user, typically a dispatcher, to cause a remote MCPTT UE to initiate a call by itself, without its user explicitly initiating the call by depressing the PTT switch. The purpose of this feature allows the dispatcher to listen to activities at the Location of the remote MCPTT UE to find out what is happening around that MCPTT UE. This feature is also known as "Remote Unit Monitoring" in P25 systems.
There are two typical use cases for this feature.
The first one is the case where a user could have been incapacitated. This could be both accidentally, say a traffic accident, or deliberately, for example a violent attack. In both cases it would be necessary to remotely open the microphone of the MCPTT UE in order to allow another user or a group of users to listen to what is happening to prepare assistance. The communication that is set up is either a Private Call or a Group Call, and the call could optionally be visible to the remote MCPTT UE's user.
The second one is the case of a stolen MCPTT UE. Here it is just necessary to activate the radio so that a dispatcher can listen to any background noise or speech in order to make an analysis of the situation. In this situation, the initiation of the call from the remote MCPTT UE, typically a Private Call in that case, is not visible by that MCPTT UE's user.
Other use cases, such as undercover operations, discreet surveillance of users or investigations, could exist depending on the missions of the critical communications users and on legislations.
The behaviour of the remotely initiated Call is not different from a normal call initiated by the local user. The same rules for resource allocation and interactions with other services apply, but the initiator of the feature can have the capability to request a pre-emptive or high priority for that Call to ensure it is set up even in case of resource congestion or to limit disturbance by other services. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.3.2 Requirements | [R-6.16.3.2-001] Void
[R-6.16.3.2-002] Void
[R-6.16.3.2-003] Void
[R-6.16.3.2-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.16.4 Recording and audit requirements | [R-6.16.4-001] Void
[R-6.16.4-002] Void
[R-6.16.4-003] Void
[R-6.16.4-004] Void
[R-6.16.4-005] Void
[R-6.16.4-006] Void
[R-6.16.4-007] Void
[R-6.16.4-008] Void
[R-6.16.4-009] Void
[R-6.16.4-010] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.17 Interaction with telephony services | [R-6.17-001] Void
[R-6.17-002] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure the interaction between telephony calls and MCPTT calls for an MCPTT User.
[R-6.17-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18 Interworking | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.1 Non-3GPP access | [R-6.18.1-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.2 Interworking between MCPTT systems | [R-6.18.2-001] Void
[R-6.18.2-002] Void
[R-6.18.2-003] Void
[R-6.18.2-004] Void
[R-6.18.2-005] Void
[R-6.18.2-006] Void
[R-6.18.2-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.3 Interworking with non-3GPP PTT systems | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.3.1 Overview | Mission critical users currently employ a wide range of narrowband mission critical Push To Talk services. Project 25 (governed by the TIA-102 standards) and TETRA (governed by ETSI standards) are digital public safety grade PTT systems. In addition, "legacy" or "conventional FM" systems are common throughout the world. These systems provide PTT and related services that are analogous to those provided by MCPTT, including group calls, Private Calls, broadcast calls, dynamic group management and other services.
The MCPTT Service is intended to interwork with these non-3GPP PTT systems. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.3.2 Project 25 | [R-6.18.3.2-001] The MCPTT Service shall enable interworking with non-3GPP PTT Systems that are compliant with the TIA-102 (P25) standards.
[R-6.18.3.2-002] Interworking between the MCPTT Service and P25 shall be capable of interworking with a multiplicity of independently administered Project 25 Radio Frequency Subsystems (RFSS).
[R-6.18.3.2-003] Interworking between the MCPTT Service and P25 shall support interoperable MCPTT Group Calls between MCPTT Users and P25 subscriber units and consoles.
[R-6.18.3.2-004] Interworking between the MCPTT Service and P25 shall support interoperable MCPTT Emergency Group Calls and P25 emergency calls.
[R-6.18.3.2-005] Interworking between the MCPTT Service and P25 shall support end-to-end encrypted MCPTT Group Calls between MCPTT Users and P25 subscriber units and consoles.
[R-6.18.3.2-006] Interworking between the MCPTT Service and P25 shall provide a means for an authorized user to initiate an override of a PTT Group call between MCPTT Users and P25 subscriber units and consoles.
[R-6.18.3.2-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize an MCPTT User to be able to initiate an override of a PTT Group call between MCPTT Users and P25 subscriber units and consoles.
[R-6.18.3.2-008] Interworking between the MCPTT Service and P25 shall provide a means for an authorized P25 subscriber units and consoles to initiate an override of a PTT Group call between MCPTT Users and P25 subscriber units and consoles.
[R-6.18.3.2-009] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize a P25 subscriber unit or P25 console to be able to initiate an override of a PTT Group call between MCPTT Users and P25 subscriber units and consoles.
[R-6.18.3.2-010] Interworking between the MCPTT Service and P25 shall support Group Regrouping that includes both MCPTT Groups and P25 groups.
[R-6.18.3.2-011] Interworking between the MCPTT Service and P25 shall support User Regrouping that includes both MCPTT Users and P25 subscriber units.
[R-6.18.3.2-012] Interworking between the MCPTT Service and P25 shall support interworking of Group-Broadcast Group Calls and P25 announcement group calls.
[R-6.18.3.2-013] Interworking between the MCPTT Service and P25 shall support interoperable User IDs and P25 subscriber IDs.
[R-6.18.3.2-014] Interworking between the MCPTT Service and P25 shall support interoperable PTT Private Calls (with Floor control) between an MCPTT User and a P25 subscriber unit or console.
[R-6.18.3.2-015] Interworking between the MCPTT Service and P25 shall provide a mechanism to reconcile the Private Call (with Floor control) commencement mode between an MCPTT User and a P25 subscriber unit or console.
[R-6.18.3.2-016] Interworking between the MCPTT Service and P25 shall support end-to-end encrypted PTT Private Calls (with Floor control) between an MCPTT User and a P25 subscriber unit or console.
[R-6.18.3.2-017] Interworking between the MCPTT Service and P25 shall support a means of reconciling codecs between interoperable calls.
[R-6.18.3.2-018] Interworking between the MCPTT Service and P25 shall support conveyance of Losing audio from P25 subscriber units and consoles to authorized MCPTT Users.
[R-6.18.3.2-019] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize MCPTT Users to be able to receive Losing audio from P25 subscribers units and consoles.
[R-6.18.3.2-020] For Private Calls (with Floor control) interworking between the MCPTT Service and non-3GPP PTT systems that do not support Private Call override (e.g., Project 25 Phase 1 systems), the Participant attempting to override shall be notified that the override can not be accomplished.
[R-6.18.3.2-021] For Private Call (with Floor control) interworking, between the MCPTT Service and non-3GPP PTT systems that do support Private Call override (e.g., Project 25 Phase 2 systems), 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 is ranked higher than the priority level of the transmitting Participant. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.3.3 TETRA | [R-6.18.3.3-001] The MCPTT Service shall enable interworking with non-3GPP PTT Systems that are compliant with the ETSI TETRA standards.
[R-6.18.3.3-002] Interworking between the MCPTT Service and TETRA shall be capable of interworking with a multiplicity of independently administered TETRA systems (Switching and management Infrastructures).
[R-6.18.3.3-003] Interworking between the MCPTT Service and TETRA shall support interoperable MCPTT Group Calls between MCPTT Users and TETRA mobile stations and consoles.
[R-6.18.3.3-004] Interworking between the MCPTT Service and TETRA shall support interoperable MCPTT Emergency Group Calls and TETRA emergency calls.
[R-6.18.3.3-005] Interworking between the MCPTT Service and TETRA shall support end-to-end encrypted MCPTT Group Calls between MCPTT Users supporting the TETRA voice codec and end-to-end encryption and TETRA mobile stations and consoles.
[R-6.18.3.3-006] Interworking between the MCPTT Service and TETRA shall provide a means for an authorized user to initiate an override of a PTT Group call between MCPTT Users and TETRA mobile stations and consoles.
[R-6.18.3.3-007] Interworking between the MCPTT Service and TETRA shall provide a means for an authorized TETRA mobile station or console to initiate an override of a PTT Group call between MCPTT Users and TETRA mobile stations and consoles.
[R-6.18.3.3-008] Interworking between the MCPTT Service and TETRA shall support Group Regrouping that includes both MCPTT Groups and TETRA groups.
[R-6.18.3.3-009] Interworking between the MCPTT Service and TETRA shall support User Regrouping that includes both MCPTT Users and TETRA mobile stations.
[R-6.18.3.3-010] Interworking between the MCPTT Service and TETRA shall support interoperable User IDs and TETRA IDs.
[R-6.18.3.3-011] Interworking between the MCPTT Service and TETRA shall support interoperable PTT Private Calls between an MCPTT User and a TETRA mobile station or console.
[R-6.18.3.3-012] Interworking between the MCPTT Service and TETRA shall support end-to-end encrypted PTT Private Calls between an MCPTT User supporting TETRA codec and encryption and a TETRA mobile station or console.
[R-6.18.3.3-013] Interworking between the MCPTT Service and TETRA shall support a means of reconciling codecs between interoperable calls when not end-to-end encrypted.
[R-6.18.3.3-014] For Private Call (with Floor control) interworking, between the MCPTT Service and non-3GPP PTT systems that do support Private Call override, 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 is ranked higher than the priority level of the transmitting Participant. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.3.4 Legacy land mobile radio | [R-6.18.3.4-001] The MCPTT Service shall enable interworking with legacy Land Mobile Radio systems that are compliant with the TIA-603-D [3] Standard.
[R-6.18.3.4-002] Interworking between the MCPTT Service and TIA-603 systems shall be capable of interworking with a multiplicity of independently administered systems based on the TIA-603-D [3] Standard.
[R-6.18.3.4-003] Interworking between the MCPTT Service and TIA-603 systems shall support interoperable PTT Group calls between MCPTT Users and TIA-603 subscriber units and consoles.
[R-6.18.3.4-004] Interworking between the MCPTT Service and TIA-603 systems shall provide a mechanism for an authorized MCPTT User to initiate an override within a PTT Group call that has both MCPTT Users and TIA 603 subscriber units and consoles.
[R-6.18.3.4-005] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize an MCPTT User to be able to initiate an override of a PTT Group call between MCPTT Users and TIA-603 subscriber units and consoles.
[R-6.18.3.4-006] Interworking between the MCPTT Service and TIA-603 systems shall provide a mechanism for an authorized TIA-603 subscriber unit or console to initiate an override within a PTT Group call that has both MCPTT Users and TIA 603 subscriber units and consoles.
[R-6.18.3.4-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize a TIA-603 subscriber unit or TIA-603 console to be able to initiate an override of a PTT Group call between MCPTT Users and TIA-603 subscriber units and consoles.
[R-6.18.3.4-008] Interworking between the MCPTT Service and TIA-603 systems shall support interoperable PTT Private Calls (with Floor control) between MCPTT Users and TIA-603 subscriber units or consoles.
[R-6.18.3.4-009] Interworking between the MCPTT Service and TIA-603 systems shall support a means of reconciling codecs between interoperable calls.
[R-6.18.3.4-010] Interworking between the MCPTT Service and TIA-603 systems shall support conveyance of Losing audio from TIA 603 subscribers units and consoles to suitably privileged MCPTT Users.
[R-6.18.3.4-011] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize MCPTT Users to be able to receive Losing audio from TIA-603 subscribers units and consoles. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.3.5 Void | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.4 GSM-R | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.4.1 Overview | GSM-R, governed by 3GPP standards, is widely and globally used for rail communication. GSM-R offers capabilities analogous to those provided by MCPTT, including group calls, point-to point calls, broadcast calls, dynamic group management and the bearer service for train safety applications. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.18.4.2 Requirements | [R-6.18.4.2-001] Void
[R-6.18.4.2-002] Void
[R-6.18.4.2-002a] Void
[R-6.18.4.2-002b] Void
[R-6.18.4.2-003] The MCPTT Service shall enable interworking between Ad hoc Group Calls and Advanced Speech Call Items used in GSM-R.
NOTE: The impact on GSM-R needs to be minimised.
[R-6.18.4.2-004] Interworking between the MCPTT Service and GSM-R shall support interoperable PTT Private Calls between an MCPTT User and a GSM-R mobile station or controller terminal.
[R-6.18.4.2-005] Interworking between the MCPTT Service and GSM-R voice services shall support a means of reconciling codecs. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.19 MCPTT coverage extension using ProSe UE-to-Network Relays | [R-6.19-001] Void
[R-6.19-002] Void
[R-6.19-003] Void
[R-6.19-004] Void
[R-6.19-005] Void
[R-6.19-006] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7 MCPTT Service requirements specific to off-network use | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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:
a) An MCPTT User Profile associated with each of the intended MCPTT Users of the MCPTT UE that might be used for off-network operation;
1) An alphanumeric identifier (with a minimum length of N3) (i.e., alias) for each MCPTT User;
2) A number of off-network MCPTT Groups for use by the MCPTT User;
3) An alphanumeric identifier (i. e., alias) for the authorized off-network MCPTT Groups;
4) A Mission Critical Organization name if available, associated with each of the intended MCPTT Users or Administrator;
5) A number of off-network MCPTT Users for Private Call for which the MCPTT User is authorized;
b) 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. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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 |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.3 Floor control | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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 |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.5 Broadcast Group | [R-7.5-001] Void
[R-7.5-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.6 Dynamic group management (i.e., dynamic regrouping) | NOTE: No specific off-network MCPTT requirements for dynamic group management have been identified. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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 |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.8 Call types based on priorities | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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 |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.8.2 MCPTT Emergency Group Call cancellation requirements | [R-7.8.2-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.8.3 Imminent Peril Call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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 |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.9 Location | [R-7.9-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.10 Security | [R-7.10-001] Void
[R-7.10-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.11 Audio MCPTT Call performance | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.11.1 MCPTT Access time and Mouth-to-ear latency | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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 |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.11.1.2 Requirements | NOTE: The MCPTT Access time and Mouth-to-ear latency for off-network use is FFS. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.11.2 Late call entry performance | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.11.2.2 Requirements | NOTE: The Late call entry time (KPI 4) for off-network use is FFS. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.11.3 Audio / Voice quality | [R-7.11.3-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.12 Off-network MCPTT operations | [R-7.12-001] Void
[R-7.12-002] Void
[R-7.12-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.14 Switching to off-network MCPTT | [R-7.14-001] Void
[R-7.14-002] Void
[R-7.14-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.15 Off-network recording and audit requirements | [R-7.15-001] Void
[R-7.15-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.16 Off-network UE-to-UE Relay | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 7.16.1 Private Calls | [R-7.16.1-001] Void
[R-7.16.1-002] Void
[R-7.16.1-003] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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 S1-163011 22.179 0047 Rel-14 D Editorial change to MCPTT TS 22.179 sub-clause 6.2.3.6.2 14.2.0 14.3.0 MCImp-MCPTTR SP-74 SP-160890 S1-163012 22.179 0048 Rel-14 D Editorial changes to Annex A1 sub-clause 6.2.3.6 14.2.0 14.3.0 MCImp-MCPTTR SP-76 SP-170445 S1-172430 22.179 0052 6 Rel-15 B multi-talker group call 14.3.0 15.0.0 MONASTERY 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 S1-180433 22.179 0062 1 Rel-16 B Adding more functionality to interworking between FRMCS and GSM-R 16.0.0 16.1.0 MONASTERY2 SP-80 SP-180310 S1-181707 22.179 0064 4 Rel-16 F Interworking between MCX Service system and GSM-R 16.1.0 16.2.0 MONASTERY2 SP-80 SP-180310 S1-181708 22.179 0063 2 Rel-16 B Adding functionality to 22.179 to support assured voice communication 16.1.0 16.2.0 MONASTERY2 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 2023-06 SA#100 - CR 0076r2 in SP-230529 creates Rel-19 from Rel-17. Version 18.0.0 is a technical-content duplicate of v.17.1.0. created for administrative reasons. 18.0.0 2023-06 SA#100 SP-230529 0076 2 C Usage of multi-talker control for Ad hoc Group Emergency Voice Communications 19.0.0 2023-09 SA#101 SP-231022 0077 1 C Enhancement of multi-talker control 19.1.0 2023-12 SA#102 SP-231395 0078 2 C Enhancement of multi-talker control due to updates of FRMCS functional requirements 19.2.0 2024-09 SA#105 SP-241145 0081 1 F Enhancement of interworking with GSM-R using Ad hoc Group Calls 19.3.0 |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 1 presented to TSG for information; | 2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The need to support different kinds of UEs (e.g. for the Internet of Things (IoT)), services, and technologies is driving the technology revolution to a high-performance and highly efficient 3GPP system. The drivers include IoT, Virtual Reality (VR), industrial control, ubiquitous on-demand coverage, as well as the opportunity to meet customized market needs. These drivers require enhancements to the devices, services, and technologies well established by 3GPP. The key objective with the 5G system is to be able to support new deployment scenarios to address diverse market segments.
This document compiles requirements that define a 5G system.
The 5G system is characterised, for example, by:
- Support for multiple access technologies
- Scalable and customizable network
- Advanced Key Performance Indicators (KPIs) (e.g. availability, latency, reliability, user experienced data rates, area traffic capacity)
- Flexibility and programmability (e.g. network slicing, diverse mobility management, Network Function Virtualization)
- Resource efficiency (both user plane and control plane)
- Seamless mobility in densely populated and heterogeneous environment
- Support for real time and non-real time multimedia services and applications with advanced Quality of Experience (QoE)
1 Scope
The present document describes the service and operational requirements for a 5G system, including a UE, NG-RAN, and 5G Core network. Requirements for a 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC are found in TS 22.278 [5]. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] NGMN 5G White Paper v1.0, February 2015.
[3] 3GPP TS 22.011: "Service accessibility".
[4] Void
[5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[6] 3GPP TS 22.101: "Service aspects; Service principles".
[7] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service (MBMS)".
[8] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services".
[9] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios".
[10] NGMN, "Recommendations for NGMN KPIs and Requirements for 5G", June 2016
[11] 3GPP TS 22.115: "Service aspects; Charging and billing".
[12] Void
[13] Soriano, R., Alberto, M., Collazo, J., Gonzales, I., Kupzo, F., Moreno, L., & Lorenzo, J. OpenNode. Open Architecture for Secondary Nodes of the Electricity Smartgrid. In Proceedings CIRED 2011 21st International Conference on Electricity Distribution, CD1. June 2011.
[14] North American Electric Reliability Council. Frequently Asked Questions (FAQs) Cyber Security Standards CIP–002–1 through CIP–009–1. Available: http://www.nerc.com/docs/standards/sar/Revised_CIP-002-009_FAQs_06Mar06.pdf. 2006.
[15] McTaggart, Craig, et al. "Improvements in power system integrity protection schemes". Developments in Power System Protection (DPSP 2010). Managing the Change, 10th IET International Conference on. IET, 2010.
[16] IEEE Power Engineering Society – Power System Relaying Committee – System Protection Subcommittee Working Group C-6. Wide Area Protection and Emergency Control.
[17] Begovic, Miroslav, et al. "Wide-area protection and emergency control". Proceedings of the IEEE 93.5, pp. 876-891, 2005.
[18] ITU-T Recommendation G.1000 "Communications quality of service: A framework and definitions".
[19] IEC 61907, "Communication network dependability engineering".
[20] NIST, "Framework for Cyber-Physical Systems", 2016.
[21] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".
[22] 3GPP TS 22.262: "Message Service within the 5G System".
[23] 3GPP TS 22.289: "Mobile Communication System for Railways".
[24] 3GPP TS 22.071: "Location Services".
[25] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[26] 3GPP TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP".
[27] Void
[28] 3GPP TS 22.263: "Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA)".
[29] Void
[30] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT)".
[31] IEEE 1588-2019, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems.
[32] IEC 61850-9-3-2016 - IEC/IEEE International Standard - Communication networks and systems for power utility automation – Part 9-3: Precision time protocol profile for power utility automation.
[33] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN"
[34] ATIS-0900005: "Technical Report on GPS Vulnerability", https://access.atis.org/apps/group_public/download.php/36304/ATIS-0900005.pdf
[35] European Commission, Regulatory Technical Standard 25. Level of accuracy of business clocks
https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25_en.pdf (annex https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25-annex_en.pdf)
[36] 5G-ACIA, "Exposure of 5G capabilities for Connected Industries and Automation Applications", 5G-ACIA white pater, February 2021, https://5g-acia.org/wp-content/uploads/2021/04/5G-ACIA_ExposureOf5GCapabilitiesForConnectedIndustriesAndAutomationApplications.pdf
[37] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services".
[38] ITU-T, "Technology Watch Report: The Tactile Internet", August 2014.
[39] D. Soldani, Y. Guo, B. Barani, P. Mogensen, I. Chih-Lin, S. Das, "5G for ultra-reliable low-latency communications". IEEE Network. 2018 Apr 2; 32(2):6-7.
[40] O. Holland et al., "The IEEE 1918.1 "Tactile Internet" Standards Working Group and its Standards," Proceedings of the IEEE, vol. 107, no. 2, Feb. 2019.
[41] Altinsoy, M. E., Blauert, J., & Treier, C., "Inter-Modal Effects of Non-Simultaneous Stimulus Presentation," A. Alippi (Ed.), Proceedings of the 7th International Congress on Acoustics, Rome, Italy, 2001.
[42] Hirsh I.J., and Sherrrick C.E, 1961. J. Exp. Psychol 62, 423-432
[43] Altinsoy, M.E. (2012). "The Quality of Auditory-Tactile Virtual Environments," Journal of the Audio Engineering Society, Vol. 60, No. 1/2, pp. 38-46, Jan.-Feb. 2012.
[44] M. Di Luca and A. Mahnan, "Perceptual Limits of Visual-Haptic Simultaneity in Virtual Reality Interactions," 2019 IEEE World Haptics Conference (WHC), 2019, pp. 67-72, doi: 10.1109/WHC.2019.8816173.
[45] K. Antonakoglou et al., “Toward Haptic Communications Over the 5G Tactile Internet”, IEEE Communications Surveys & Tutorials, 20 (4), 2018.
[46] ETSI GS OEU 020 (v1.1.1): "Operational energy Efficiency for Users (OEU); Carbon equivalent Intensity measurement; Operational infrastructures; Global KPIs; Global KPIs for ICT Sites".
[47] 3GPP TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[48] ETSI EN 303 472: "Environmental Engineering (EE); Energy Efficiency measurement methodology and metrics for RAN equipment".
[49] 3GPP TS 32.299: " Telecommunication management; Charging management; Diameter charging applications".
[50] N. Nonaka et al., "Experimental Trial aboard Shinkansen Test Train Running at 360 km/h for 5G Evolution," 2022 IEEE 95th Vehicular Technology Conference: (VTC2022-Spring), Helsinki, Finland, 2022.
[51] 3GPP TS 22.137: " Service requirements for Integrated Sensing and Communication ".
[52] 3GPP TS 22.369: " Service requirements for Ambient power-enabled IoT ".
[53] 3GPP TS 22.156: "Mobile Metaverse Services”.
[54] IEEE Std 802.1Q: "IEEE Standard for Local and Metropolitan Area Networks---Bridges and Bridged Networks". |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 3 Definitions, symbols and abbreviations | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
5G enhanced positioning area: a subset of the 5G positioning service area that is assumed to be provided with additional infrastructure or deploy a particular set of positioning technologies to enhance positioning services.
NOTE 1: The enhanced positioning service area represents for example a factory plant, a dense urban area, an area along a road or railway track, a tunnel and covers both indoor and outdoor environments.
5G LAN-type service: a service over the 5G system offering private communication using IP and/or non-, i.e. UEs that are members of the same 5G LAN-VN IP type communications.
5G LAN-virtual network: a virtual network capable of supporting 5G LAN-type service.
5G satellite access network: 5G access network using at least one satellite.
5G positioning service area: a service area where positioning services would solely rely on infrastructures and positioning technologies that can be assumed to be present anywhere where 5G is present (e.g. a country-wide operator-supplied 5G network, GNSS, position/motion sensors).
NOTE 2: This includes both indoor and any outdoor environments.
active communication: a UE is in active communication when it has one or more connections established. A UE may have any combination of PS connections (e.g. PDP contexts, active PDN connections).
activity factor: percentage value of the amount of simultaneous active UEs to the total number of UEs where active means the UEs are exchanging data with the network.
Ambient IoT device: An ambient power-enabled Internet of Things device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor).
aggregated QoS: QoS requirement(s) that apply to the traffic of a group of UEs.
area traffic capacity: total traffic throughput served per geographic area.
authorised administrator: a user or other entity authorised to partially configure and manage a network node in a CPN (e.g. a PRAS, or eRG) or a PIN element in a PIN.
carbon emission: quantity of equivalent carbon dioxide emitted (e.g. kg of CO2 equivalent).
communication service availability: percentage value of the amount of time the end-to-end communication service is delivered according to a specified QoS, divided by the amount of time the system is expected to deliver the end-to-end service.
NOTE 3: The end point in "end-to-end" is the communication service interface.
NOTE 4: The communication service is considered unavailable if it does not meet the pertinent QoS requirements. For example, the communication service is unavailable if a message is not correctly received within a specified time, which is the sum of maximum allowed end-to-end latency and survival time.
Customer Premises Network: a network located within a premise (e.g. a residence, office or shop), which is owned, installed and/or (at least partially) configured by the customer of a public network operator.
direct device connection: the connection between two UEs without any network entity in the middle.
direct network connection: one mode of network connection, where there is no relay UE between a UE and the 5G network.
Disaster Condition: This is the condition that a government decides when to initiate and terminate, e.g. a natural disaster. When this condition applies, users may have the opportunity to mitigate service interruptions and failures.
Disaster Inbound Roamer: A user that (a) cannot get service from the PLMN it would normally be served by, due to failure of service during a Disaster Condition, and (b) is able to register with other PLMNs.
Disaster Roaming: This is the special roaming policy that applies during a Disaster Condition.
DualSteer device: A device supporting traffic steering and switching of user data (for different services) across two 3GPP access networks; it can be a single UE, in case of non-simultaneous data transmission over the two networks, or two separate UEs in case of simultaneous data transmission over the two networks.
end-to-end latency: the time that it takes to transfer a given piece of information from a source to a destination, measured at the communication interface, from the moment it is transmitted by the source to the moment it is successfully received at the destination.
energy charging rate: a means of determining the energy consumption consequence (use of energy credit) associated with charging events.
energy credit: a quantity of energy credit associated with the subscriber that can be used for credit control by the 5G system.
energy state: state of a cell, a network element and/or a network function with respect to energy, e.g. (not) energy saving states, which are defined in TS 28.310 [47].
evolved Residential Gateway: a gateway between the public operator network (fixed/mobile/cable) and a customer premises network.
holdover: A clock A, previously synchronized/syntonized to another clock B (normally a primary reference or a Master Clock) but whose frequency is determined in part using data acquired while it was synchronized/syntonized to B, is said to be in holdover or in the holdover mode as long as it is within its accuracy requirements.
NOTE 4a: holdover is defined in [31]
Holdover time: the time period that is available to repair the first priority timing source when it is lost (e.g., when the primary GNSS reference is lost). During this period the synchronization accuracy requirement should be guaranteed, e.g., by means of defining multiple synchronization references.
Hosted Service: a service containing the operator's own application(s) and/or trusted third-party application(s) in the Service Hosting Environment, which can be accessed by the user.
Hosting NG-RAN Operator: the operator that has operational control of a Shared NG-RAN.
NOTE 4b: Hosting NG-RAN Operator is a Hosting RAN Operator.
Hosting RAN Operator: as defined in 3GPP TS 22.101 [6].
hybrid access: access consisting of multiple different access types combined, such as fixed wireless access and wireline access.
indirect network connection: one mode of network connection, where there is a relay UE between a UE and the 5G network.
Indirect Network Sharing: a type of NG-RAN Sharing in which the communication between the Shared NG-RAN and the Participating Operator’s core network is routed through the Hosting NG-RAN Operator’s core network.
IoT device: a type of UE which is dedicated for a set of specific use cases or services and which is allowed to make use of certain features restricted to this type of UEs.
NOTE 5: An IoT device may be optimized for the specific needs of services and application being executed (e.g. smart home/city, smart utilities, e-Health and smart wearables). Some IoT devices are not intended for human type communications.
maximum energy consumption: a policy establishing an upper bound on the quantity of energy consumption [47] by the 5G system in a specific period of time, or space, e.g. energy consumption inside a given service area.
maximum energy credit limit: a policy establishing an upper bound on the aggregate quantity of energy consumption by the 5G system to provide services to a specific subscriber, e.g. in kilowatt hours.
NOTE: The terms maximum energy credit limit is distinct from 'maximum energy consumption' because the credit limit is a total amount of energy consumed, where maximum energy consumption is a limit to the consumption in a given interval of time.
network slice: a set of network functions and corresponding resources necessary to provide the required telecommunication services and network capabilities.
NG-RAN: a radio access network connecting to the 5G core network which uses NR, E-UTRA, or both.
NG-RAN Sharing: the sharing of NG-RAN among a number of operators.
non-public network: a network that is intended for non-public use.
NR: the new 5G radio access technology.
Participating NG-RAN Operator: authorized operator that is using Shared NG-RAN resources provided by a Hosting NG-RAN Operator.
NOTE 5a: Participating NG-RAN Operator is a Participating Operator.
Participating Operator: as defined in 3GPP TS 22.101 [6].
Personal IoT Network: A configured and managed group of at least one UE PIN Element and one or more PIN Element that communicate with each other.
PIN Element: UE or non-3GPP device that can communicate within a PIN.
PIN direct connection: the connection between two PIN Elements without any 3GPP RAN or core network entity in the middle.
NOTE 5A: A PIN direct connection could internally be relayed by other PIN Elements.
NOTE 5B: When a PIN direct connection is between two PIN Elements that are UEs this direct connection is typically known as a direct device connection.
PIN Element with Gateway Capability: a UE PIN Element that has the ability to provide connectivity to and from the 5G network for other PIN Elements.
NOTE 5C: A PIN Element can have both PIN management capability and Gateway Capability.
PIN Element with Management Capability: A PIN Element with capability to manage the PIN.
positioning service availability: percentage value of the amount of time the positioning service is delivering the required position-related data within the performance requirements, divided by the amount of time the system is expected to deliver the positioning service according to the specification in the targeted service area.
proximity-based work task offloading: a relay UE receives data from a remote UE via direct device connection and performs calculation of a work task for the remote UE. The calculation result can be further sent to network server.
positioning service latency: time elapsed between the event that triggers the determination of the position-related data and the availability of the position-related data at the system interface.
Premises Radio Access Station: a base station installed at a customer premises network.
priority service: a service that requires priority treatment based on regional/national or operator policies.
private communication: a communication between two or more UEs belonging to a restricted set of UEs.
private network: an isolated network deployment that does not interact with a public network.
private slice: a dedicated network slice deployment for the sole use by a specific third-party.
ProSe UE-to-UE Relay: a Public Safety ProSe-enabled UE that acts as a relay between two other Public Safety ProSe-enabled UEs.
Ranging: refers to the determination of the distance between two UEs and/or the direction of one UE from the other one via direct device connection.
relative positioning: relative positioning is to estimate position relatively to other network elements or relatively to other UEs.
reliability: in the context of network layer packet transmissions, percentage value of the packets successfully delivered to a given system entity within the time constraint required by the targeted service out of all the packets transmitted.
renewable energy: energy from renewable sources as energy from renewable non-fossil sources, namely wind, solar, aerothermal, geothermal, hydrothermal and ocean energy, hydropower, biomass, landfill gas, sewage treatment plant gas and biogases
NOTE 2: This definition was taken from [48].
satellite: a space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO) typically at an altitude between 300 km to 1 500 km, Medium-Earth Orbit (MEO) typically at an altitude between 7 000 to 15 000 km, or Geostationary satellite Earth Orbit (GEO) at 35 786 km altitude.
satellite access: direct connectivity between the UE and the satellite.
satellite NG-RAN: a NG-RAN which uses NR in providing satellite access to UEs.
service area: geographic region where a 3GPP communication service is accessible.
NOTE 6: The service area can be indoors.
NOTE 7: For some deployments, e.g. in process industry, the vertical dimension of the service area can be considerable.
service continuity: the uninterrupted user experience of a service that is using an active communication when a UE undergoes an access change without, as far as possible, the user noticing the change.
NOTE 8: In particular service continuity encompasses the possibility that after a change the user experience is maintained by a different telecommunication service (e.g. tele- or bearer service) than before the change.
NOTE 9: Examples of access changes include the following. For EPS: CS/PS domain change. For EPS and 5G: radio access change, switching between a direct network connection and an indirect network connection.
Service Hosting Environment: the environment, located inside of 5G network and fully controlled by the operator, where Hosted Services are offered from.
serving satellite: a satellite providing the satellite access to an UE. In the case of NGSO, the serving satellite is always changing due to the nature of the satellite constellation.
Shared NG-RAN: as defined in 3GPP TS 22.101 [6].
Stand-alone Non-Public Network: A non-public network not relying on network functions provided by a PLMN
SNPN Credential Provider: Entity within the 5G system that creates and manages identity information and provides authentication services for those identities for the purpose of accessing a SNPN
NOTE: The SNPN Credential Provider can also authorize access to a non-public network for a subscriber associated with an identity handled by this SNPN Credential Provider.
S&F Satellite operation: S&F (Store and Forward) Satellite operation is an operation mode of a 5G system with satellite-access where the 5G system can provide some level of service (in storing and forwarding the data) when satellite connectivity is intermittently/temporarily unavailable, e.g. to provide communication service for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment.
S&F data retention period: it is the data storage validity period for a 5G system with satellite access supporting store and forward operation (e.g. after which undelivered data stored is being discarded).
synchronization threshold: A synchronization threshold can be defined as the maximum tolerable temporal separation of the onset of two stimuli, one of which is presented to one sense and the other to another sense, such that the accompanying sensory objects are perceived as being synchronous.
NOTE 10: This definition is based on [41].
survival time: the time that an application consuming a communication service may continue without an anticipated message.
Time to First Fix (TTFF): time elapsed between the event triggering for the first time the determination of the position-related data and the availability of the position-related data at the positioning system interface.
Traffic steering: the procedure that selects an access network and transfers traffic over the selected access network. This can apply to traffic of one or multiple services/applications across two 3GPP access networks, including scenarios where all services use the same network connection (no simultaneous data over the two networks) or different services are steered across different networks (with simultaneous data over the two networks).
Traffic switching: the procedure that moves all traffic from one access network to another access network in a way that minimizes service interruption. This can apply to traffic of one or multiple services/applications across two 3GPP access networks, including scenarios where all services use the same network connection (no simultaneous data over the two networks) or different services are moved to different networks (with simultaneous data over the two networks).
UE-Satellite-UE communication: for a 5G system with satellite access, it refers to the communication between UEs under the coverage of one or more serving satellites, using satellite access without the user traffic going through the ground segment.
User Equipment: An equipment that allows a user access to network services via 3GPP and/or non-3GPP accesses.
user experienced data rate: the minimum data rate required to achieve a sufficient quality experience, with the exception of scenario for broadcast like services where the given value is the maximum that is needed.
wireless backhaul: a link which provides an interconnection between 5G network nodes and/or transport network using 5G radio access technology. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
5G LAN-VN 5G LAN-Virtual Network
A/S Actuator/Sensor
CPN Customer Premises Network
eFMSS Enhancement to Flexible Mobile Service Steering
eRG Evolved Residential Gateway
eV2X Enhanced V2X
FL Federated Learning
FMSS Flexible Mobile Service Steering
GEO Geostationary satellite Earth Orbit
ICP Internet Content Provider
ID Identification
IMU Inertial Measurement Unit
IOPS Isolated E-UTRAN Operation for Public Safety
ISL Inter-Satellite Link
LEO Low-Earth Orbit
MBS Metropolitan Beacon System
MCS Mission Critical Services
MCX Mission Critical X, with X = PTT or X = Video or X = Data
MEO Medium-Earth Orbit
MIoT Massive Internet of Things
MMTEL Multimedia Telephony
MOCN Multi-Operator Core Network
MPS Multimedia Priority Service
MSGin5G Message Service Within the 5G System
MSTP Multiple Spanning Tree Protocol
NGSO Non-Geostationary Satellite Orbit
NPN Non-Public Network
PIN Personal IoT Network
PRAS Premises Radio Access Station
RSTP Rapid Spanning Tree Protocol
RVAS Roaming Value-Added Service
SEES Service Exposure and Enablement Support
SNPN Stand-alone Non-Public Network
S&F Store and Forward
SST Slice/Service Type
TBS Terrestrial Beacon System
TTFF Time To First Fix
UAV Uncrewed Aerial Vehicle
UTC Coordinated Universal Time
XR eXtended Reality |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 4 Overview | Unlike previous 3GPP systems that attempted to provide a 'one size fits all' system, the 5G system is expected to be able to provide optimized support for a variety of different services, different traffic loads, and different end user communities. Various industry white papers, most notably, the NGMN 5G White Paper [2], describe a multi-faceted 5G system capable of simultaneously supporting multiple combinations of reliability, latency, throughput, positioning, and availability. This technology revolution is achievable with the introduction of new technologies, both in access and the core, such as flexible, scalable assignment of network resources. In addition to increased flexibility and optimization, a 5G system needs to support stringent KPIs for latency, reliability, throughput, etc. Enhancements in the radio interface contribute to meeting these KPIs as do enhancements in the core network, such as network slicing, in-network caching and hosting services closer to the end points.
A 5G system also supports new business models such as those for IoT and enterprise managed networks. Drivers for the 5G KPIs include services such as Uncrewed Aerial Vehicle (UAV) control, Augmented Reality (AR), and factory automation. Network flexibility enhancements support self-contained enterprise networks, installed and maintained by network operators while being managed by the enterprise. Enhanced connection modes and evolved security facilitate support of massive IoT, expected to include tens of millions of UEs sending and receiving data over the 5G network.
Flexible network operations are the mainstay of the 5G system. The capabilities to provide this flexibility include network slicing, network capability exposure, scalability, and diverse mobility. Other network operations requirements address the necessary control and data plane resource efficiencies, as well as network configurations that optimize service delivery by minimizing routing between end users and application servers. Enhanced charging and security mechanisms handle new types of UEs connecting to the network in different ways. The enhanced flexibility of the 5G system also allows to cater to the needs of various verticals. For example, the 5G system introduces the concept of non-public networks providing exclusive access for a specific set of users and specific purpose(s). Non-public networks can, depending on deployment and (national) regulations, support different subsets of 5G functionality. In this specification 5G network requirements apply to both NPNs and PLMNs, unless specified otherwise. Additionally, there are specific requirements dedicated only to NPNs or PLMNs, which are indicated accordingly. More information can be found in Section 6.25.
Mobile Broadband (MBB) enhancements aim to meet a number of new KPIs. These pertain to high data rates, high user density, high user mobility, highly variable data rates, deployment, and coverage. High data rates are driven by the increasing use of data for services such as streaming (e.g. video, music, and user generated content), interactive services (e.g. AR), and IoT. These services come with stringent requirements for user experienced data rates as well as associated requirements for latency to meet service requirements. Additionally, increased coverage in densely populated areas such as sports arenas, urban areas, and transportation hubs has become essential for pedestrians and users in urban vehicles. New KPIs on traffic and connection density enable both the transport of high volumes of data traffic per area (traffic density) and transport of data for a high number of connections (e.g. UE density or connection density). Many UEs are expected to support a variety of services which exchange either a very large (e.g. streaming video) or very small (e.g. data burst) amount of data. The 5G system will handle this variability in a resource efficient manner. All of these cases introduce new deployment requirements for indoor and outdoor, local area connectivity, high user density, wide area connectivity, and UEs travelling at high speeds.
Another aspect of 5G KPIs includes requirements for various combinations of latency and reliability, as well as higher accuracy for positioning. These KPIs are driven by support for both commercial and public safety services. On the commercial side, industrial control, industrial automation, UAV control, and AR are examples of those services. Services such as UAV control will require more precise positioning information that includes altitude, speed, and direction, in addition to horizontal coordinates.
Support for Massive Internet of Things (MIoT) brings many new requirements in addition to those for the enhanced KPIs. The expansion of connected things introduces a need for significant improvements in resource efficiency in all system components (e.g. UEs, IoT devices, radio, access network, core network).
The 5G system also aims to enhance its capability to meet KPIs that emerging V2X applications require. For these advanced applications, the requirements, such as data rate, reliability, latency, communication range and speed, are made more stringent. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.