hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.2 Requirements | [R-6.2.3.6.2-001] The MCPTT Group shall be configurable to allow audio cut-in.
NOTE 1: MCPTT Groups configured for audio cut-in behave in the same way as MCPTT Groups not configured for audio cut-in in all other respects other than the Floor control logic described in this sub-clause.
[R-6.2.3.6.2-002] When an MCPTT Gr... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.3 Requesting permission to transmit | [R-6.2.3.6.3-001] An authorized Participant shall be able to request to transmit to an MCPTT Group configured to support audio cut-in.
[R-6.2.3.6.3-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that there are no other... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.4 Terminating permission to transmit | [R-6.2.3.6.4-001] The MCPTT Service shall enable an authorized MCPTT User to terminate the permission to transmit of a transmitting Participant at any time on a group configured for audio cut-in.
[R-6.2.3.6.4-002] A transmitting Participant shall be able to indicate to the MCPTT Service that the Participant no longer w... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.6.5 Transmit time limit | [R-6.2.3.6.5-001] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit on a group configured for audio cut-in.
[R-6.2.3.6.5-002] The Floor control functionality for a group configured for audio cut-in shall hav... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7 MCPTT Groups configured for multi-talker control | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7.1 Overview | The multi-talker control applies to designated MCPTT Groups and results in allowing several Participants talking simultaneously within the MCPTT Group. For example, Multi-talker control is used by railway communication e.g. during shunting operation.
Except for Floor control as specified in clauses 6.2.3.1, 6.2.3.2, 6.... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7.2 General aspects | [R-6.2.3.7.2-001] An MCPTT Group shall be configurable to allow multi-talker control.
[R-6.2.3.7.2-002] The MCPTT Service shall provide a mechanism for multiple MCPTT Users to talk simultaneously in an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.2-003] The MCPTT Service shall determine which Participant... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7.3 Requesting permission to transmit | [R-6.2.3.7.3-001] The MCPTT Service shall enable authorized Participants to request to transmit to an MCPTT Group configured for multi-talker control.
[R-6.2.3.7.3-002] At call setup the MCPTT Service shall provide a notification, for example audio and/or visual, to the MCPTT Group Member attempting to transmit that th... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.3.7.4 Override | 6.2.3.7.4.1 General aspects
[R-6.2.3.7.4.1-001] If the number of MCPTT Users requesting the permission to talk exceeds the maximum number of simultaneous talkers in an MCPTT Group configured for multi-talker control, the MCPTT Service shall apply the override mechanism.
[R-6.2.3.7.4.1-002] The MCPTT Service shall enabl... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.2.4 Call termination | [R-6.2.4-001] If a Participant of an MCPTT Group call is pre-empted, the MCPTT Service shall terminate the call or continue the call with an indication to the transmitting Participant that one or more receiving Participants was pre-empted.
[R-6.2.4-002] If MCPTT User(s) are pre-empted from an ongoing MCPTT call as ther... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.3 General requirements | [R-6.3-001] Void
[R-6.3-002] Void
[R-6.3-003] Void
[R-6.3-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4 General group call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.1 General aspects | [R-6.4.1-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.2 Group status/information | [R-6.4.2-001] Void
[R-6.4.2-002] Void
[R-6.4.2-003] Void
[R-6.4.2-004] Void
[R-6.4.2-005] Void
[R-6.4.2-006] Void
[R-6.4.2-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.3 Identification | [R-6.4.3-001] Void
[R-6.4.3-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.4 Membership/affiliation | [R-6.4.4-001] Void
[R-6.4.4-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.5 Membership/affiliation list | [R-6.4.5-001] Void
[R-6.4.5-002] Void
[R-6.4.5-003] Void
[R-6.4.5-004] Void
[R-6.4.5-005] Void
[R-6.4.5-006] Void
[R-6.4.5-007] Void
[R-6.4.5-008] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.6 Authorized user remotely changes another MCPTT User's affiliated and/or Selected MCPTT Group(s) | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.6.1 Mandatory change | [R-6.4.6.1-001] Void
[R-6.4.6.1-002] Void
[R-6.4.6.1-003] Void
[R-6.4.6.1-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.6.2 Negotiated change | [R-6.4.6.2-001] Void
[R-6.4.6.2-002] Void
[R-6.4.6.2-003] Void
[R-6.4.6.2-004] Void
[R-6.4.6.2-005] Void
[R-6.4.6.2-006] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.7 Prioritization | [R-6.4.7-001] Void
[R-6.4.7-002] Void
[R-6.4.7-003] Void
[R-6.4.7-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.8 Relay requirements | [R-6.4.8-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.4.9 Administrative | [R-6.4.9-001] Void
[R-6.4.9-002] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to set a predefined time period (Hang Time) without any traffic in MCPTT calls (with Floor control), after which the MCPTT calls shall terminate.
[R-6.4.9-003] Void
[R-6.4.9-004] Void
[R-6.4.9-005] Void
[R-6.4.9-006]... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.5 Broadcast group | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.5.1 General Broadcast Group Call | [R-6.5.1-001] Void
[R-6.5.1-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.5.2 Group-Broadcast Group (e.g., announcement group) | [R-6.5.2-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.5.3 User-Broadcast Group (e.g., System Call) | [R-6.5.3-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6 Dynamic group management (i.e., dynamic regrouping) | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.1 General dynamic regrouping | [R-6.6.1-001] Void
[R-6.6.1-002] Void
[R-6.6.1-003] Void
[R-6.6.1-004] Void
[R-6.6.1-005] Void
[R-6.6.1-006] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.2 Group Regrouping | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.2.1 Service description | Group Regrouping enables dispatchers or any authorized user to temporarily combine MCPTT Groups. A dispatcher uses Group Regrouping for different reasons.
Due to an incident in an area it can be necessary to temporarily enable MCPTT Users from different MCPTT Groups to communicate to each other to coordinate. After the... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.2.2 Requirements | [R-6.6.2.2-001] Void
[R-6.6.2.2-002] Void
[R-6.6.2.2-003] Void
[R-6.6.2.2-004] Void
[R-6.6.2.2-005] Void
[R-6.6.2.2-006] Void
[R-6.6.2.2-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.3 Temporary Group-Broadcast Group | [R-6.6.3-001] Void
[R-6.6.3-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.4 User regrouping | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.4.1 Service description | In the operational MCPTT environment most tasks are covered by standard procedures and communication structures and MCPTT Users can easily access the MCPTT Groups to handle their tasks.
Exceptionally it could happen that there is an urgent need for a dedicated set of individual MCPTT Users to communicate in an MCPTT Gr... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.6.4.2 Requirements | [R-6.6.4.2-001] Void
[R-6.6.4.2-002] Void
[R-6.6.4.2-003] Void
[R-6.6.4.2-004] Void
[R-6.6.4.2-005] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7 Private Call | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.0 Overview | Private Calls can use Floor control or not. Private Calls (without Floor control) are only supported on network, whereas Private Calls (with Floor control) are supported both on and off network. Private Calls (without Floor contol) are intended to have the same functionality as specified for Private Calls (with Floor c... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.1 General requirements | [R-6.7.1-001] The on-network MCPTT Service shall support two types of Private Calls, one which uses Floor control and one which does not.
NOTE: An MCPTT Private Call (without Floor control) is effectively a full voice duplex call between two users.
[R-6.7.1-002] Void
[R-6.7.1-003] Void
[R-6.7.1-004] Void
[R-6.7.1-005] ... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.2 Administrative | [R-6.7.2-001] Void
[R-6.7.2-002] Void
[R-6.7.2-003] Void
[R-6.7.2-004] Void
[R-6.7.2-005] Void
[R-6.7.2-006] Void
[R-6.7.2-007] Void
[R-6.7.2-008] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.3 Prioritization | [R-6.7.3-001] Void
[R-6.7.3-002] Void
[R-6.7.3-003] Void
[R-6.7.3-004] Void
[R-6.7.3-005] Void
[R-6.7.3-006] Void
[R-6.7.3-007] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.4 Private Call (without Floor control) commencement requirements | [R-6.7.4-001] The MCPTT Service shall support Call Commencement Modes for Private Calls (without Floor control), which determine the conditions under which Private Calls (without Floor control) are set up.
[R-6.7.4-002] The MCPTT Service shall provide a mechanism for an MCPTT User to cancel an MCPTT Private Call (witho... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.5 Private Call (without Floor control) termination | [R-6.7.5-001] Void
[R-6.7.5-002] The MCPTT Service shall provide a means by which an authorized MCPTT User ignores a Manual Commencement Private Call (without Floor control) request from another MCPTT User.
NOTE: Ignoring a Manual Commencement Private Call (without Floor control) results in no indication of the reason ... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.7.6 Call back request requirements | [R-6.7.6-001] The MCPTT Service shall provide a mechanism (i.e., MCPTT Private Call call back request) for the calling party of an MCPTT Private Call to request that the called party (at earliest convenience) place a call to the calling party.
[R-6.7.6-002] The MCPTT Service shall provide a mechanism for the calling pa... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8 MCPTT priority requirements | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.1 General | [R-6.8.1-001] Void
[R-6.8.1-002] The MCPTT Service shall provide an access control mechanism to support multiple Access Priorities to prioritize MCPTT MO call initiation attempts, depending on their access priorities.
[R-6.8.1-003] Void
[R-6.8.1-004] Void
[R-6.8.1-005] Void
[R-6.8.1-006] Void
[R-6.8.1-007] Void
[R-6.8.... |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.2 3GPP system access controls | [R-6.8.2-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 6.8.3 3GPP system admission controls | [R-6.8.3-001] Void |
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... |
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... |
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... |
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... |
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 inclu... |
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 me... |
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 u... |
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 G... |
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 author... |
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 ... |
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 Loc... |
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... |
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 Subsys... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.