Content for TS 22.179 Word version: 19.2.0
6.6 Dynamic group management (i.e., dynamic regrouping)
6.6.1 General dynamic regrouping
6.6.2 Group Regrouping
6.6.2.1 Service description
6.6.2.2 Requirements
6.6.3 Temporary Group-Broadcast Group
6.6.4 User regrouping
6.6.4.1 Service description
6.6.4.2 Requirements
6.7 Private Call
6.7.0 Overview
6.7.1 General requirements
6.7.2 Administrative
6.7.3 Prioritization
6.7.4 Private Call (without Floor control) commencement requirements
6.7.4a Private Call (with Floor control) commencement requirements
6.7.5 Private Call (without Floor control) termination
6.7.6 Call back request requirements
...
...
6.6 Dynamic group management (i.e., dynamic regrouping) p. 43
6.6.1 General dynamic regrouping p. 43
[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
6.6.2 Group Regrouping p. 43
6.6.2.1 Service description p. 43
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 incident the dispatcher cancels the Group Regrouping and the MCPTT Users continue with their original configured MCPTT Groups.
During quiet periods control room managers can decide to combine MCPTT Groups and handle their operations and communications with one dispatcher. In the busier period the Group Regrouping is cancelled and the MCPTT Groups are handled by separate dispatchers.
6.6.2.2 Requirements p. 44
[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
6.6.3 Temporary Group-Broadcast Group p. 44
[R-6.6.3-001]
Void
[R-6.6.3-002]
Void
6.6.4 User regrouping p. 44
6.6.4.1 Service description p. 44
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 Group, but that this is not foreseen in the communication structure. This could be due to extreme conditions or due to a cooperation that is outside normal procedures.
User Regrouping enables dispatchers or authorized users to instantaneously provide a dedicated MCPTT Group to these MCPTT Users to enable the required communication. Depending on configuration the MCPTT Users could be automatically affiliated to this MCPTT Group. After the operation this MCPTT Group is removed by the dispatcher or authorized user.
6.6.4.2 Requirements p. 44
[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
6.7 Private Call p. 44
6.7.0 Overview p. 44
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 control) in subclause 5.6.2, subclause 5.6.3, subclause 5.6.4, subclause 5.6.5. Comparable requirements are included in subclause 6.7.1, subclause 6.7.2, subclause 6.7.4 and subclause 6.7.5, with the exception of R-5.6.5-005, which is specific to Private Calls (with Floor control).
6.7.1 General requirements p. 45
[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.
[R-6.7.1-002]
Void
[R-6.7.1-003]
Void
[R-6.7.1-004]
Void
[R-6.7.1-005]
Void
[R-6.7.1-006]
Void
[R-6.7.1-007]
Void
[R-6.7.1-008]
Void
[R-6.7.1-009]
Void
[R-6.7.1-010]
The MCPTT Service shall provide a mechanism by which specified Participants or Participant types (e.g., dispatch) have the ability to override an active PTT transmission of the other Participant in the Private Call.
[R-6.7.1-011]
Void
[R-6.7.1-012]
The MCPTT Service shall provide the status (e.g., ringing, accepted, rejected, active) of an MCPTT Private Call (without Floor control) to the relevant MCPTT User that is a Participant of the MCPTT Private Call (without Floor control).
[R-6.7.1-013]
The MCPTT Service shall provide a mechanism for an authorized MCPTT User that is a called party in an MCPTT Private Call (without Floor control), to restrict providing the reason why an MCPTT Private Call (without Floor control) setup has failed to the calling MCPTT User.
[R-6.7.1-014]
Void
6.7.2 Administrative p. 45
[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
6.7.3 Prioritization p. 45
[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
6.7.4 Private Call (without Floor control) commencement requirements p. 46
[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 (without Floor control) prior to the call setup.
[R-6.7.4-003]
The MCPTT Service shall provide a means by which an authorized MCPTT User initiates an MCPTT Private Call (without Floor control).
[R-6.7.4-004]
Void
[R-6.7.4-005]
The MCPTT Service shall provide a means by which an MCPTT User initiates a Manual Commencement Private Call (without Floor control) to any MCPTT User for which the MCPTT User is authorized.
[R-6.7.4-006]
The MCPTT Service shall require that the called MCPTT User accepts a Manual Commencement Private Call (without Floor control) setup request before the call proceeds.
[R-6.7.4-007]
The MCPTT Service shall provide a means for an MCPTT User to accept a Manual Commencement Private Call (without Floor control) request from another MCPTT User.
[R-6.7.4-008]
Void
[R-6.7.4-009]
The MCPTT UE shall support automatic commencement mode and manual commencement mode for Private Calls (without Floor control).
[R-6.7.4-010]
The MCPTT Service shall provide a manual commencement mode countermand by which an authorized MCPTT User may request that the invited MCPTT UE answers automatically.
[R-6.7.4-011]
Void
[R-6.7.4-012]
The MCPTT Service shall require that the called MCPTT UE acknowledge receipt of an Automatic Commencement Private Call (without Floor control) setup request before the audio transmission proceeds.
[R-6.7.4-013]
The MCPTT Service shall provide a first-to-answer commencement mode by allowing the originating user to indicate multiple potential target recipients for a Private Call (without Floor control) and shall ensure that the call is established only to the first answering user.
[R-6.7.4-014]
When a receiving user answers a first-to-answer Private Call (without Floor control) the MCPTT Service shall remove all other receiving users from that call.
[R-6.7.4-015]
The MCPTT Service shall provide a mechanism for an authorized MCPTT User to transfer an ongoing MCPTT Private Call (without Floor control) to another MCPTT user.
[R-6.7.4-016]
The MCPTT Service shall provide a mechanism for an authorized MCPTT User to configure forwarding of incoming MCPTT Private Calls (without Floor control) to another MCPTT user in the following situations:
- Always
- If the MCPTT User is not reachable
- If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period
- Based on manual input of the MCPTT User
6.7.4a Private Call (with Floor control) commencement requirements |R14| p. 47
[R-6.7.4a-001]
The MCPTT Service shall provide a first-to-answer commencement mode by allowing the originating user to indicate multiple potential target recipients for a Private Call (with Floor control) and shall ensure that the call is established only to the first answering user.
[R-6.7.4a-002]
When a receiving user answers a first-to-answer Private Call (with Floor control) the MCPTT Service shall remove all other receiving users from that call.
6.7.5 Private Call (without Floor control) termination p. 47
[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.
[R-6.7.5-003]
Void
6.7.6 Call back request requirements p. 47
[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 party of an MCPTT Private Call to assign an urgency indication (i.e., low, normal, urgent) to any call back request.
[R-6.7.6-003]
The MCPTT Service shall provide an MCPTT UE receiving an MCPTT Private Call call back request with an indication of the assigned call back urgency assigned by the calling party.
[R-6.7.6-004]
The MCPTT Service shall provide a mechanism for an MCPTT User to cancel a call back request.
[R-6.7.6-005]
The MCPTT Service shall provide an MCPTT UE receiving an MCPTT Private Call call back request with an indication of which MCPTT User called and when.
