hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
5
1.47k
content
stringlengths
0
6.67M
72a4e55cbcd7a63aa54799710b138216
22.156
8.1 Description
This clause gathers all charging requirements that apply to functionalities whose requirements are specified in other clauses of the present document.
72a4e55cbcd7a63aa54799710b138216
22.156
8.2 Requirements
72a4e55cbcd7a63aa54799710b138216
22.156
8.2.1 Localized mobile metaverse service
[R-8.2.1-001] The 5G system shall be able to collect charging information for the actions related to spatial anchors, where a third party creates, deletes, or modifies a spatial anchor or associated service information. NOTE: It is assumed that exposure of network anchors and associated service information can be a ser...
72a4e55cbcd7a63aa54799710b138216
22.156
8.2.2 Avatar-based real-time communication
[R-8.2.2-001] The 5G system shall support collection of charging information associated with initiating and terminating avatar call. [R-8.2.2-002] The 5G system shall be able to collect charging information for transcoding services associated with avatar call.
72a4e55cbcd7a63aa54799710b138216
22.156
8.2.3 Digital asset management
[R-8.2.3-001] The 5G system shall be able to collect charging information per UE or per application, related to the use of digital assets associated with a user (e.g., typically a human user with a certain subscription). [R-8.2.3-002] The 5G system shall be able to collect charging information per UE for managing the d...
025654ae449f21f6a2c0a037ab2affe6
22.179
1 Scope
The present document provides the service requirements for operation of the MCPTT Service. MCPTT makes use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service. The MCPTT Service can be used for public safety applications and...
025654ae449f21f6a2c0a037ab2affe6
22.179
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. - Fo...
025654ae449f21f6a2c0a037ab2affe6
22.179
3 Definitions and abbreviations
025654ae449f21f6a2c0a037ab2affe6
22.179
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 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 TR 21.905 [1]. Definitions provided in 3GPP TS 22.280 [15] also apply to this specification. Affili...
025654ae449f21f6a2c0a037ab2affe6
22.179
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 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 TR 21.905 [1]. FIFO First In First Out GCSE_LTE Group Communication System Enablers for LT...
025654ae449f21f6a2c0a037ab2affe6
22.179
4 Mission Critical Push To Talk overview
025654ae449f21f6a2c0a037ab2affe6
22.179
4.1 General
A Push To Talk service provides an arbitrated method by which two or more users may engage in communication. Users may request permission to transmit (e.g., traditionally by means of a press of a button). The Mission Critical Push To Talk (MCPTT) service supports an enhanced PTT service, suitable for mission critical s...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.2 Typical use of the MCPTT Service
NOTE: Even though this subclause is written from an organization specific perspective the text is illustrative for typical use of MCPTT Services by all MCPTT Users. Public safety workers often operate in groups and perform different tasks during the day/week. Many tasks and operations are controlled, assisted and/or co...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.3 Overview of MCPTT Group affiliation, call and transmission
An MCPTT Service provides Group Call and Private Call capabilities, which have various process flows, states and permissions associated with them. The figure 4.3.1, figure 4.3.2, and figure 4.3.3 indicate the high level flows, states and permissions associated with Group Calls and Private Calls. The diagrams apply to t...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.4 General handling of requests
Request handling is by no means specific only to MCPTT Service, but it plays a central role in its functionality. Requests appear in the MCPTT Service in many forms and under many circumstances: e.g., requests for the floor during a call, requests for starting a call, requests for resources. Conceptually, requests are ...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.5 Overview of MCPTT UE and MCPTT User in the MCPTT Service
The MCPTT Service supports MCPTT User Profiles. The MCPTT User Profile contains important information related to the MCPTT User receiving the MCPTT Service, including the MCPTT User identity, which is globally unique and independent of the mobile subscriber identity (IMSI) assigned by a 3GPP network operator. Part of t...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.5.1 MCPTT User association to MCPTT UE in on-network mode
Consistent with the 3GPP paradigm, when an MCPTT UE is powered on, it accesses the 3GPP system, and connects to the 3GPP network. During this phase, the credentials from a USIM application (or possibly, an ISIM application, if IMS is used) on a UICC associated with the MCPTT UE is used for authentication with an HSS. T...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.5.2 MCPTT User and MCPTT UE relationship
A user can enter his identifying/authenticating credentials (e.g., user name/ password, PIN, biometrics, asserted identity from a remote, trusted device). This step typically gives the MCPTT User access to local information and applications stored on the MCPTT UE, and in particular, to the MCPTT client application. The...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.5.3 MCPTT Users accessing the service through non-3GPP access interface
This document primarily focuses on MCPTT Users accessing and managing the MCPTT Service through MCPTT UEs, however there might be some dispatchers and administrators who might access the service through a non-3GPP access interface.
025654ae449f21f6a2c0a037ab2affe6
22.179
4.5.4 Shareable MCPTT UEs and gateway UEs
The conceptual model for shareable MCPTT UEs is that of a pool of UEs, each UE being interchangeable with any other, and users randomly choosing one or more UEs from the pool, each user for his temporary exclusive use. A shareable MCPTT UE can be used by user who can gain access to the MCPTT client application stored o...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.5.5 MCPTT User association to MCPTT UE in off-network mode
A user can enter his identifying/authenticating credentials (e.g., user name/ password, PIN, biometrics, asserted identity from a remote, trusted device). This step typically gives the MCPTT User access to local information and applications stored on the MCPTT UE, and in particular, to the MCPTT client application. Aft...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.6 Overview of MCPTT priorities
025654ae449f21f6a2c0a037ab2affe6
22.179
4.6.1 MCPTT priority model
Many non-public safety 3GPP users today subscribe to one particular priority and QoS level of service (e.g., "gold", "silver" or "bronze"), which always provides fixed differentiation. This model, effective and relatively straightforward for non-public safety users, falls short when it comes to the needs of the public ...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.6.2 Generic processing of priority information
This functionality applies to MCPTT Call initiations and transmissions for the management of potentially contended resources (e.g., GBR bearers) and also for Floor control during an MCPTT Group Call. Each request for exclusive access to resource(s) or for preferential treatment over a contending request arrives accompa...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.6.3 Handling of MCPTT priority information for Floor control
Floor control is applied in the context of a single MCPTT Call and is triggered by a Participant request for the permission to transmit. Priority information accompanies each grant request.
025654ae449f21f6a2c0a037ab2affe6
22.179
4.6.4 Handling of MCPTT priority information for interactions at the transport layer
At the Transport Layer, the MCPTT Service uses3GPP controls to adapt the overall behaviour of the MCPTT System to the needs for resources and/or preferential treatment over other contenders, based on the priority information accompanying the request. The following four controls are available, to be used as necessary, b...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.6.5 Handling of MCPTT priority information for interactions with non-3GPP PTT systems
An MCPTT call can be mixed, with some Participants served by one network/system and other Participants served by a different network(s)/system(s). In general the systems can be quite different. For example, some Participants use MCPTT/LTE, while others could use a P25-based system.
025654ae449f21f6a2c0a037ab2affe6
22.179
4.6.6 MCPTT priority for Private Call
The MCPTT Service uses User Static Attributes of the Participants, potentially adjusted based on User Dynamic Attributes, if applicable. By default, the priority of an MCPTT Private Call is the same as the priority of the originator of the call. Similar to group calls there are MCPTT Emergency Private Calls (with Floor...
025654ae449f21f6a2c0a037ab2affe6
22.179
4.7 Overview of MCPTT identifiers
The main identifiable entities in use by the MCPTT Service are Mission Critical Organizations, MCPTT Groups, MCPTT Users, and MCPTT Administrators. The UEs are identified at the transport or network layer, but in some situations they might also be identified by the MCPTT Service. Each identifiable entity is distinct fr...
025654ae449f21f6a2c0a037ab2affe6
22.179
5 MCPTT Service requirements common for on the network and off the network
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1 General group call requirements
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1.1 General aspects
[R-5.1.1-001] Void [R-5.1.1-002] Void [R-5.1.1-003] Void [R-5.1.1-004] Void [R-5.1.1-005] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1.2 Group/status information
[R-5.1.2-001] Void [R-5.1.2-002] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1.3 Group configuration
[R-5.1.3-001] Void [R-5.1.3-002] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1.4 Identification
[R-5.1.4-001] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1.5 Membership/affiliation
[R-5.1.5-001] Void [R-5.1.5-002] Void [R-5.1.5-003] Void [R-5.1.5-004] Void [R-5.1.5-005] Void [R-5.1.5-006] Void [R-5.1.5-007] Void [R-5.1.5-008] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1.6 Group Call administration
[R-5.1.6-001] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1.7 Prioritization
[R-5.1.7-001] Void [R-5.1.7-002] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.1.8 Charging requirements for MCPTT
[R-5.1.8-001] Void [R-5.1.8-002] Void [R-5.1.8-003] Void [R-5.1.8-004] Void [R-5.1.8-005] Void [R-5.1.8-006] Void [R-5.1.8-007] Void [R-5.1.8-008] Void [R-5.1.8-009] Void [R-5.1.8-010] Void [R-5.1.8-011] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.2 Broadcast Group
025654ae449f21f6a2c0a037ab2affe6
22.179
5.2.1 General Broadcast Group Call
[R-5.2.1-001] Void [R-5.2.1-002] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.2.2 Group-Broadcast Group (e.g., announcement group)
[R-5.2.2-001] Void [R-5.2.2-002] Void [R-5.2.2-003] Void [R-5.2.2-004] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.2.3 User-Broadcast Group (e.g., System Call)
[R-5.2.3-001] Void [R-5.2.3-002] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.3 Late call entry
[R-5.3-001] Void [R-5.3-002] Void [R-5.3-003] Void [R-5.3-004] Void [R-5.3-005] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.4 Dynamic group management (i.e., dynamic regrouping)
NOTE: No common on-network and off-network dynamic group management requirements have been identified.
025654ae449f21f6a2c0a037ab2affe6
22.179
5.5 Receiving from multiple MCPTT calls
025654ae449f21f6a2c0a037ab2affe6
22.179
5.5.1 Overview
MCPTT Users receive call traffic of their affiliated MCPTT Groups. This multiple receiving, called monitoring by some organizations, provides MCPTT Users current information about police, fire or critical medical events that are occurring within their jurisdictions. This is useful for dispatchers or those that might no...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.5.2 Requirements
[R-5.5.2-001] Void [R-5.5.2-002] Void [R-5.5.2-003] Void [R-5.5.2-004] Void [R-5.5.2-005] Void [R-5.5.2-006] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N5) of MCPTT Group transmissions that an MCPTT UE simultaneously receives in one MCPTT Group call in case of over...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.6 Private Call
025654ae449f21f6a2c0a037ab2affe6
22.179
5.6.1 Private Call overview
Private Calls allow two MCPTT Users to communicate directly with each other without the use of MCPTT Groups. They leverage many of the functions and features of MCPTT Group Calls, such as MCPTT User identity and alias information, location information, encryption, privacy, priority, and administrative control. Private ...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.6.2 Private Call (with Floor control) general requirements
NOTE: The requirements in this subclause should mirror requirements in 6.7.1 for Private Call (without Floor control). [R-5.6.2-001] The MCPTT Service shall provide the status (e.g., ringing, accepted, rejected, active) of an MCPTT Private Call (with Floor control) to the relevant MCPTT User that is a Participant of th...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.6.3 Private Call (with Floor control) commencement requirements
NOTE 1: The requirements in this subclause should mirror the requirements in 6.7.4 for Private Call (without Floor control). [R-5.6.3-001] The MCPTT Service shall support Call Commencement Modes for Private Calls (with Floor control), which determine the conditions under which Private Calls (with Floor control) are set...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.6.4 Private Call (with Floor control) termination
NOTE 1: The requirements in this subclause should mirror the requirements in 6.7.5 for Private Call (without Floor control). [R-5.6.4-001] The MCPTT Service shall provide a mechanism for an MCPTT User to reject an MCPTT Private Call (with Floor control). [R-5.6.4-002] The MCPTT Service shall provide a means by which an...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.6.5 Private Call (with Floor control) administration
NOTE: The requirements in this subclause should mirror requirements in 6.7.2 for Private Call (without Floor control), except [R-5.6.5-005] which is specific to Private Call with Floor control. [R-5.6.5-001] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to configure which MCPTT Users, within th...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7 MCPTT priority requirements
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.1 Overview
MCPTT Emergency Group Call and MCPTT Imminent Peril group call are MCPTT Group Calls that provide the MCPTT User elevated priority towards obtaining resources of the MCPTT system. The MCPTT Emergency Private Call similarly provides elevated priority to resources of the MCPTT system. The MCPTT Emergency Alert provides a...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2 Call types based on priorities
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.1 MCPTT Emergency Group Call
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.1.1 MCPTT Emergency Group Call requirements
[R-5.7.2.1.1-001] Void [R-5.7.2.1.1-002] Void [R-5.7.2.1.1-003] Void [R-5.7.2.1.1-004] Void [R-5.7.2.1.1-005] Void [R-5.7.2.1.1-006] Void [R-5.7.2.1.1-007] Void [R-5.7.2.1.1-008] Void [R-5.7.2.1.1-009] Void [R-5.7.2.1.1-010] Void [R-5.7.2.1.1-011] Void [R-5.7.2.1.1-012] Void [R-5.7.2.1.1-013] Void [R-5.7.2.1.1-014] Voi...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.1.2 MCPTT Emergency Group Call cancellation requirements
[R-5.7.2.1.2-001] Void [R-5.7.2.1.2-002] Void [R-5.7.2.1.2-003] Void [R-5.7.2.1.2-004] Void [R-5.7.2.1.2-005] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.2 Imminent Peril group call
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.2.1 Imminent Peril group call requirements
[R-5.7.2.2.1-001] Void [R-5.7.2.2.1-002] Void [R-5.7.2.2.1-003] Void [R-5.7.2.2.1-004] Void [R-5.7.2.2.1-005] Void [R-5.7.2.2.1-006] Void [R-5.7.2.2.1-007] Void [R-5.7.2.2.1-008] Void [R-5.7.2.2.1-009] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.2.2 Imminent Peril group call cancellation requirements
[R-5.7.2.2.2-001] Void [R-5.7.2.2.2-002] Void [R-5.7.2.2.2-003] Void [R-5.7.2.2.2-004] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.3 MCPTT Emergency Private Call (with Floor control)
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.3.1 MCPTT Emergency Private Call (with Floor control) requirements
[R-5.7.2.3.1-001] The MCPTT Service shall support MCPTT Emergency Private Calls (with Floor control) from authorized MCPTT Users. NOTE: This functionality out of network relies on the MCPTT User being called being within ProSe Communication range. For this reason this functionality is more likely to be used on the netw...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.3.2 MCPTT Emergency Private Call (with Floor control) cancellation requirements
[R-5.7.2.3.2-001] The MCPTT Service shall support cancellation of the MCPTT Emergency priority of an MCPTT Emergency Private Call (with Floor control) by an authorized MCPTT User. [R-5.7.2.3.2-002] The MCPTT Service shall support cancellation of the MCPTT Emergency priority of an MCPTT Emergency Private Call (with Floo...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.4 MCPTT Emergency Alert
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.4.1 MCPTT Emergency Alert requirements
[R-5.7.2.4.1-001] Void [R-5.7.2.4.1-002] Void [R-5.7.2.4.1-003] Void [R-5.7.2.4.1-004] Void [R-5.7.2.4.1-005] Void [R-5.7.2.4.1-006] Void [R-5.7.2.4.1-007] Void [R-5.7.2.4.1-008] Void [R-5.7.2.4.1-009] Void [R-5.7.2.4.1-010] Void [R-5.7.2.4.1-011] Void [R-5.7.2.4.1-012] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.7.2.4.2 MCPTT Emergency Alert cancellation requirements
[R-5.7.2.4.2-001] Void [R-5.7.2.4.2-002] Void [R-5.7.2.4.2-003] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.8 User ID
[R-5.8-001] Void [R-5.8-002] Void [R-5.8-003] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.9 MCPTT UE management
[R-5.9-001] Void [R-5.9-002] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.10 MCPTT User Profile
[R-5.10-001] Void [R-5.10-002] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.11 Support for multiple devices
[R-5.11-001] Void [R-5.11-002] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.12 Location
[R-5.12-001] Void [R-5.12-002] Void [R-5.12-003] Void [R-5.12-004] Void [R-5.12-005] Void [R-5.12-006] Void [R-5.12-007] Void [R-5.12-008] Void [R-5.12-009] Void [R-5.12-010] Void [R-5.12-011] The MCPTT Service shall provide a means for an MCPTT UE to send a Location information update whenever the MCPTT User initiates...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.13 Security
[R-5.13-001] Void [R-5.13-002] Void [R-5.13-003] Void [R-5.13-004] Void [R-5.13-005] Void [R-5.13-006] Void [R-5.13-007] Void [R-5.13-008] Void [R-5.13-009] Void [R-5.13-010] Void [R-5.13-011] Void [R-5.13-012] Void [R-5.13-013] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.14 Audio / voice quality
[R-5.14-001] Void [R-5.14-002] MOS-LQO shall achieve the noise reduction performance of TIA-102.BABG [10] Table 3-1. [R-5.14-003] MOS-LQO shall achieve a noise reduction performance for the 3GPP Adaptive Multi-Rate Wide Band codec (AMR-WB TS 26.190 [11] and TS 26.194 [12] that is equal to or greater than that specified...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.15 Interactions between MCPTT Group calls and MCPTT Private Calls (with Floor control)
[R-5.15-001] The MCPTT Service shall allow an MCPTT UE to be transmitting in one MCPTT Group Call while simultaneously receiving transmissions from one or more MCPTT Private Calls (with Floor control). [R-5.15-002] The MCPTT Service shall allow an MCPTT UE to be receiving or transmitting in one MCPTT Private Call (with...
025654ae449f21f6a2c0a037ab2affe6
22.179
5.16 Relay requirements
[R-5.16-001] Void [R-5.16-002] Void [R-5.16-003] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.17 Gateway requirements
[R-5.17-001] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.18 Control and management by Mission Critical Organizations
025654ae449f21f6a2c0a037ab2affe6
22.179
5.18.1 Overview
Subclause 5.18 contains general requirements for management of the MCPTT Service by Mission Critical Organizations sharing the same MCPTT system, and more specific requirements pertaining to management controls and operational visibility, and to management of security services.
025654ae449f21f6a2c0a037ab2affe6
22.179
5.18.2 General requirements
[R-5.18.2-001] Void [R-5.18.2-002] Void [R-5.18.2-003] Void [R-5.18.2-004] Void [R-5.18.2-005] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.18.3 Operational visibility for Mission Critical Organizations
[R-5.18.3-001] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
5.19 General Administrative – groups and users
[R-5.19-001] Void [R-5.19-002] Void [R-5.19-003] Void [R-5.19-004] Void [R-5.19-005] Void [R-5.19-006] Void [R-5.19-007] Void [R-5.19-008] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
6 MCPTT Service requirements specific to on-network use
025654ae449f21f6a2c0a037ab2affe6
22.179
6.1 General administrative – groups and users
[R-6.1-001] Void [R-6.1-002] Void [R-6.1-003] Void [R-6.1-004] Void [R-6.1-005] Void [R-6.1-006] Void [R-6.1-007] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2 MCPTT calls
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.1 Commencement modes for MCPTT Group calls
[R-6.2.1-001] The MCPTT Service shall be capable of allowing an MCPTT Group call setup request to proceed without prior acknowledgement by any MCPTT User of that MCPTT Group. [R-6.2.1-001a] The MCPTT Service shall be capable of allowing an MCPTT Group Call setup request to proceed only if a minimum number of MCPTT Grou...
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.2 Queuing
[R-6.2.2-001] Void [R-6.2.2-002] Void [R-6.2.2-003] Void [R-6.2.2-004] Void [R-6.2.2-005] Void [R-6.2.2-006] Void
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3 Floor control
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.1 General aspects
[R-6.2.3.1-001] The Floor control functionality in an MCPTT Service shall determine at a point in time which Participant(s) are allowed to transmit to other Participant(s). [R-6.2.3.1-002] Receiving Participant(s) shall receive audio from one transmitting Participant. The only exception is if an MCPTT Group is configur...
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.2 Requesting permission to transmit
[R-6.2.3.2-001] An authorized Participant shall be able to request to transmit to an MCPTT Group or an individual Participant. [R-6.2.3.2-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other Group Mem...
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.3 Override
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.3.1 General aspects
[R-6.2.3.3.1-001] The MCPTT Service shall enable MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types shall be granted a request to override an active MCPTT transmission. [R-6.2.3.3.1-002] The MCPTT Service shall enable an MCPTT Administ...
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.3.2 Override – one transmitting Participant
[R-6.2.3.3.2-001] If the MCPTT Group has been configured to only allow the overriding transmitting Participant, the MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant.
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.3.3 Override – simultaneously Transmitting MCPTT Group Members
[R-6.2.3.3.3-001] If the MCPTT Group has been configured to allow both overriding and overridden transmitting Participants, authorized receiving Participants shall be enabled to listen to both the overriding and overridden Participant transmissions, dependent on configuration. [R-6.2.3.3.3-002] The MCPTT Service shall ...
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.4 Terminating permission to transmit
[R-6.2.3.4-001] The MCPTT Service shall enable an authorized MCPTT User to terminate the permission to transmit of a transmitting Participant at any time. [R-6.2.3.4-002] A transmitting Participant shall be able to indicate to the MCPTT Service that the Participant no longer wants to transmit. NOTE: In this case audio ...
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.5 Transmit time limit
[R-6.2.3.5-001] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit. [R-6.2.3.5-002] The Floor control functionality shall have a configurable limit for the length of time that a Participant transmits from a s...
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.6 Audio cut-in on designated MCPTT Groups
025654ae449f21f6a2c0a037ab2affe6
22.179
6.2.3.6.1 Overview
The audio cut-in feature applies to specially designated MCPTT Groups and results in Floor control for that group allowing any participant within the MCPTT Group to interrupt any other participant. In particular the audio cut-in feature means that the last Participant to request the floor is assigned the floor immediat...