Content for TS 22.280 Word version: 19.6.0
6 MCX Service requirements specific to on-network use
6.1 General administrative - groups and users
6.2 MCX Service communications
6.3 General requirements
6.4 General MCX Service Group Communications
6.5 Broadcast Group
6.6 Dynamic group management (i.e., dynamic regrouping)
6.7 Private Communication
...
...
6 MCX Service requirements specific to on-network use p. 31
6.1 General administrative - groups and users p. 31
[R-6.1-001]
The MCX Service shall provide a mechanism for an MCX Service Administrator to limit the total number (Nc6) of MCX Service Group Members of an MCX Service Group.
[R-6.1-002]
The MCX Service shall provide a mechanism for an MCX Service Administrator to remove MCX Service Groups from the MCX Service system.
[R-6.1-003]
The MCX Service shall provide a mechanism for an MCX Service Administrator to disable and re-enable MCX Service Groups.
[R-6.1-004]
The MCX Service shall provide a mechanism to log MCX Service Administrators' activities (e.g., cryptographic key updates, MCX Service User Profile changes, password changes, invalid access attempts).
[R-6.1-005]
The MCX Service shall provide a mechanism for an MCX Service Administrator to define geographic areas that can be associated to dispatchers for the purpose of routing Location dependent communications and alerts, as part of handling MCX Service Private Communication requests and MCX Service Group Communications, when the receiving/alerted party is based on the MCX User's current Location.
6.2 MCX Service communications p. 31
6.2.1 Notification and acknowledgement for MCX Service Group Communications p. 31
[R-6.2.1-001]
The MCX Service shall be capable of allowing an MCX Service Group Communication to proceed without prior acknowledgement by any MCX User of that MCX Service Group.
[R-6.2.1-002]
The MCX Service shall provide a notification and acknowledgement function for an MCX User currently affiliated to an MCX Service Group to acknowledge receipt of an MCX Service Group Communication, if configured to do so.
[R-6.2.1-003]
The MCX User's acknowledgement may require direct interaction of the MCX UE with the human user, or may be automatically executed by the MCX UE, in accordance with policy established by an MCX Service Administrator.
[R-6.2.1-004]
If the MCX Service has knowledge that some affiliated members of a group cannot be Participants in an MCX Service Group Communication, the MCX Service shall provide an indication to the requester that the communication is proceeding without all affiliated members, and shall provide the list of the missing members based on policy established by the MCX Service Administrator.
[R-6.2.1-005]
If MCX User(s) are excluded from an MCX Service communication as there is insufficient capacity to support their participation the MCX Service shall notify the MCX User(s) that they have been excluded from the communication for reasons of lack of capacity.
6.2.2 Queuing p. 31
[R-6.2.2-001]
The MCX Service shall prioritize the transmit request queue based on the type of communication (e.g., group, private), urgency of the communication (e.g., general group, MCX Service Emergency, Imminent Peril), attributes (e.g., priority level) of the MCX Service Group (if a group communication), and attributes (e.g., priority level) of the requesting MCX User.
[R-6.2.2-002]
When prioritizing the transmit queue, the MCX Service may assign higher priority to communications of the MCX Service Groups and MCX Users operating within the boundaries of their jurisdictions, if known.
[R-6.2.2-003]
When prioritizing the transmit queue, the MCX Service may assign higher priority to communications of the MCX Service Groups and MCX Users during hours of operation or while on duty, if known.
[R-6.2.2-004]
The MCX Service shall allow MCX Users with queued requests for permission to transmit to cancel their requests.
[R-6.2.2-005]
If an MCX Service Group Communication request to transmit has been queued, the MCX Service shall provide, upon request, that MCX User's current position in the queue.
[R-6.2.2-006]
If a request for an MCX Service Group Communication is queued, the MCX Service shall provide an indication to the requester when the communication continues.
6.3 General requirements p. 32
[R-6.3-001]
A PLMN shall support multiple MCX Service systems.
[R-6.3-002]
An MCX Service system shall be capable of providing MCX Services to MCX Users in multiple PLMNs.
[R-6.3-003]
The MCX Service shall provide a means by which changes performed by an MCX Service Administrator take effect immediately.
[R-6.3-004]
The MCX Service shall provide a means by which changes performed by an MCX Service Administrator take effect at a specified date/time.
6.4 General MCX Service Group Communications p. 32
6.4.1 General aspects p. 32
[R-6.4.1-001]
Interruption to an MCX Service Group Communication shall be minimized when participants move from one area to another.
6.4.2 Group status/information p. 32
[R-6.4.2-001]
The MCX Service shall provide a mechanism by which an authorized MCX User determines which MCX Service Groups have at least one other MCX User affiliated.
[R-6.4.2-002]
The MCX Service shall provide a mechanism by which an authorized MCX UE determines what MCX Service Groups have at least one active receiving member.
[R-6.4.2-003]
The MCX Service shall provide a mechanism by which an authorized MCX UE determines that a number (Nc1) of receiving members are present for an MCX Service Group.
[R-6.4.2-004]
The MCX Service shall provide a mechanism by which an authorized MCX UE determines that a particular receiving member(s) is present for an MCX Service Group.
[R-6.4.2-005]
The MCX Service shall provide a notification, for example audio and/or visual, to a user that there are no members on an MCX Service Group being used/monitored by the user and that the user is the only user affiliated to that MCX Service Group.
[R-6.4.2-006]
The MCX Service shall provide a mechanism by which an authorized MCX User can determine which MCX Service Group(s) another MCX User has affiliated to.
[R-6.4.2-007]
The MCX Service shall provide a mechanism by which an authorized MCX User can determine which MCX Service Group(s) another MCX User has selected.
6.4.3 Identification p. 32
[R-6.4.3-001]
The MCX Service shall provide the MCX Service User ID, associated MCX Service User ID alias(es), MCX Service Group ID, group aliases and, if available, the identity of the Mission Critical Organization name of the transmitting Participant to the receiving MCX UEs unless the transmitting Participant's identity is restricted.
[R-6.4.3-002]
The MCX Service shall present users with human readable identifiers (with a minimum length of Nc3) for MCX Users (i.e., MCX Service User ID alias(es)) and for the MCX Service Groups (i.e., group alias(es)).
6.4.4 Membership/affiliation p. 33
[R-6.4.4-001]
The MCX Service shall support automatic affiliation of the MCX UE to a Group-Broadcast Group or User-Broadcast Group within that MCX Service.
[R-6.4.4-002]
The MCX Service shall support an MCX User's ability to revoke their affiliation with an MCX Service Group.
[R-6.4.4-002a]
The MCX Service shall enable an MCX User to revoke their affiliation with a specific MCX Service Group on specific MCX UEs.
[R-6.4.4-003]
The MCX Service shall be able to prevent the MCX User having registered a specific Functional Alias from revoking their affiliation with a specific MCX Service Group.
[R-6.4.4-004]
The MCX Service shall be able to prevent the MCX User to revoke their affiliation with a specific MCX Service Group if the MCX User is the only MCX User in the MCX Service Group registered a specific Functional Alias.
6.4.5 Membership/affiliation list p. 33
[R-6.4.5-001]
The MCX Service shall provide, upon request, the list of currently affiliated members on an MCX Service Group to an authorized user regardless of the user's affiliation.
[R-6.4.5-002]
The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to request the list of currently affiliated members on an MCX Service Group regardless of the MCX User's affiliation or group membership.
[R-6.4.5-003]
The MCX Service shall provide, upon request, the list of currently affiliated members of an MCX Service Group to an authorized MCX UE.
[R-6.4.5-003a]
The MCX Service shall provide a mechanism to enable an authorized MCX User to automatically receive any changes made to the list of currently affiliated members for an MCX Service Group.
[R-6.4.5-004]
When a list of affiliated members is provided, the list shall reference each member by MCX Service User ID and/or associated aliases.
[R-6.4.5-005]
The MCX Service shall provide, upon request, the current list of members of an MCX Service Group to an authorized user.
[R-6.4.5-006]
The MCX Service shall provide, upon request, the current list of members of an MCX Service Group to an authorized MCX UE regardless of the MCX UE's membership.
[R-6.4.5-007]
The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to request the complete list of members of an MCX Service Group, regardless of the MCX User's membership.
[R-6.4.5-008]
When a list of members is provided, the list shall reference each member by MCX Service User ID and/or associated aliases.
6.4.6 Authorized user remotely changes another MCX User's affiliated and/or Selected MCX Service Group(s) p. 33
6.4.6.1 Mandatory change p. 33
[R-6.4.6.1-001]
The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to change an on-network MCX User's Selected MCX Service Group(s) and then the MCX Service shall send a notification to the on-network MCX User.
[R-6.4.6.1-002]
The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to make changes to the group(s) that an on-network MCX User is affiliated to and then the MCX Service shall send a notification to the on-network MCX User.
[R-6.4.6.1-003]
The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to change multiple other on-network MCX Users' Affiliated MCX Service Group(s) to a specific MCX Service Group, and the MCX Service shall notify this to the on-network MCX Users.
[R-6.4.6.1-004]
The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to change multiple other on-network MCX Users' Selected MCX Service Group(s) to a specific MCX Service Group, and the MCX Service shall notify this to the on-network MCX Users.
6.4.6.2 Negotiated change p. 34
[R-6.4.6.2-001]
The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to send a notification that proposes that another on-network MCX User should affiliate to a specific MCX Service Group.
[R-6.4.6.2-002]
The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to send a notification that proposes that multiple other on-network MCX Users should affiliate to a specific MCX Service Group.
[R-6.4.6.2-003]
The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to send a notification that proposes that another on-network MCX User should select a specific MCX Service Group.
[R-6.4.6.2-004]
The MCX Service shall provide a mechanism that allows an authorized MCX User (e.g., dispatcher) to send a notification that proposes that multiple on-network MCX Users should select a specific MCX Service Group.
[R-6.4.6.2-005]
The MCX Service shall provide a mechanism to the on-network MCX User to accept or reject a proposed change in selected or affiliated MCX Service Group(s).
[R-6.4.6.2-006]
The MCX Service shall provide a notification to the authorized MCX User (e.g., dispatcher) if the change that they proposed to another on-network MCX User(s) affiliated/Selected MCX Service Group was accepted/rejected by the MCX User(s).
6.4.7 Prioritization p. 34
[R-6.4.7-001]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of different MCX Service Group Communications with respect to transport.
[R-6.4.7-002]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of different MCX Service Group Communications with respect to presentation.
[R-6.4.7-003]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of MCX Service Groups Communications and other traffic with respect to transport.
[R-6.4.7-004]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of MCX Service Groups Communications and other traffic with respect to presentation.
6.4.8 Relay requirements p. 34
[R-6.4.8-001]
The MCX UE-to-Network Relay service shall provide on-network MCX Service to MCX UEs not currently connected to the serving network.
6.4.9 Administrative p. 34
[R-6.4.9-001]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the conditions under which MCX Service communications shall be terminated (e.g., last Participant leaving, second last Participant leaving, initiator leaving).
[R-6.4.9-002]
The MCX Service shall provide a mechanism for MCX Service Administrators to configure the maximum allowed time duration for MCX Service Group communications to remain active.
[R-6.4.9-003]
The MCX Service shall provide a mechanism for an MCX Service Administrator to determine how many MCX Users shall remain participating for MCX Service Group Communications to remain active.
[R-6.4.9-004]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure MCX Service Groups to be receive-only for specified MCX Service Group Members.
[R-6.4.9-005]
The MCX Service shall provide a mechanism for an MCX Service Administrator to set the preferred codecs for an MCX Service Group.
[R-6.4.9-006]
The MCX Service shall provide a mechanism for an MCX Service Administrator to confine use of an MCX Service Group to MCX Service Group Members in a particular geographic area.
6.5 Broadcast Group p. 35
6.5.1 General Broadcast Group Communication p. 35
[R-6.5.1-001]
The MCX Service shall deliver an on-Network Broadcast Group Communication within that MCX Service to the members of a Broadcast Group who are on-Network, and who may be all of the MCX Service system users, or a subset thereof.
[R-6.5.1-002]
The MCX Service shall support Broadcast Group Communications within that MCX Service to a dynamically defined geographic area.
6.5.2 Group-Broadcast Group (e.g., announcement group) p. 35
[R-6.5.2-001]
The MCX Service shall optionally support termination of all, or a subset of, subordinate group communications within that MCX Service upon initiation of a Broadcast Group Communication transmitted on a Group-Broadcast Group.
6.5.3 User-Broadcast Group (e.g., System Communication) p. 35
[R-6.5.3-001]
The MCX Service shall optionally support termination of all group communications within that MCX Service that are not MCX Service Emergency Group Communications involving those users within the user hierarchy upon initiation of a Broadcast Group Communication transmitted on a User-Broadcast Group.
6.6 Dynamic group management (i.e., dynamic regrouping) p. 35
6.6.1 General dynamic regrouping p. 35
[R-6.6.1-001]
Group Regroup and User Regroup operations shall be manageable by authorized MCX Users.
[R-6.6.1-002]
The temporary group formed by Group Regroup or User Regroup operations shall persist until torn down by an authorized MCX User.
[R-6.6.1-003]
The priority of the temporary group formed by a Group Regroup or User Regroup operations shall be established by the creator of the group within bounds established by MCX Service Administrators.
[R-6.6.1-004]
The MCX Service shall enable an MCX Service Administrator to grant and to revoke the authorization of an MCX User to be able to perform dynamic regrouping operations.
[R-6.6.1-005]
The MCX Service shall enable an MCX Service Administrator to configure whether a temporary group is encrypted.
[R-6.6.1-006]
The temporary group formed by Group Regroup or User Regroup operations shall be treated like any other MCX Service Group, except the ability for a temporary group formed by a Group Regroup operation to be included in another Group Regroup operation.
6.6.2 Group regrouping p. 36
6.6.2.1 Service description p. 36
Group regrouping enables dispatchers or any authorized user to temporarily combine MCX Service Groups. A dispatcher uses group regrouping for different reasons.
Due to an incident in an area it can be necessary to temporarily enable MCX Users from different MCX Service Groups to communicate to each other to coordinate. After the incident the dispatcher cancels the group regrouping and the MCX Users continue with their original configured MCX Service Groups.
During quiet periods control room managers can decide to combine MCX Service Groups and handle their operations and communications with one dispatcher. In the busier period the group regrouping is cancelled and the MCX Service Groups are handled by separate dispatchers.
MCX Service Groups that are being combined in a Group Regroup operation may belong to the same or different MCX servers and may have different security and priority levels, different floor control methods, as well as different operational characteristics (e.g. different call start criteria, different call or session hang timers, different transmit time limits, different override settings, different floor control parameters such as queue depth, queing policy and time-to-live in the queue). However, the newly created temporary MCX Service Group can have only a single security level, priority level, floor control method, and set of operational characteristics. The MCX Service will apply the proper setting of those parameters for the new MCX Service Group.
6.6.2.2 Requirements p. 36
[R-6.6.2.2-001]
The MCX Service shall provide a means of dynamically combining a multiplicity of groups into a new, temporary group (i.e., to perform a "Group Regroup operation").
[R-6.6.2.2-002]
The MCX Service shall notify MCX Users when and how any of their affiliated groups are affected by a Group Regroup operation including notification of modified security, priority, floor control, and other operational characteristics.
[R-6.6.2.2-003]
The MCX Service shall provide notification and information to an authorized MCX User if that user is attempting to Group Regroup MCX Service Groups of different security levels, priority levels, and/or floor control methods.
[R-6.6.2.2-004]
The MCX Service shall enable an authorized MCX User to set the security level of the Group created from a Group Regroup operation. Where an MCX User does not specify the security level the MCX Service shall default the security level to be set to the lowest security level of the constituent Groups.
[R-6.6.2.2-005]
The MCX Service shall notify Affiliated MCX Service Group Members of a constituent MCX Service Group when the security level of the MCX Service Group that they are using lowers as a result of a Group Regroup operation.
[R-6.6.2.2-006]
The MCX Service shall enable an authorized MCX User to set the priority level of the group formed from a Group Regroup operation. Where an MCX User does not specify the priority level the MCX Service shall default the priority level to be set to the highest priority level of the constituent Groups.
[R-6.6.2.2-007]
Broadcast Groups shall be able to be included in a Group Regroup operation.
[R-6.6.2.2-008]
The MCX Service shall enable an authorized MCX User or MCX Service Administrator to configure default settings and rules for the operational characteristics of temporary MCX Service Groups resulting from Group Regroup operations (e.g. call start criteria, hang time).
[R-6.6.2.2-009]
The MCX Service shall enable an authorized MCX User to specify the operational characteristics of temporary MCX Service Groups resulting from Group Regroup operations either explicitly, or via pre-defined implicit rules, or via pre-configured default values, or, in case all the constituent Groups have in common the same operational characteristics, to use the common settings.
[R-6.6.2.2-010]
The MCX Service shall enable an authorized MCX User to set the floor control method of the Group created from a Group Regroup operation when the Group Regroup includes one or more groups configured for audio cut-in operation. Where an MCX User does not specify the floor control method the MCX Service shall default to using normal floor control for the Group Regroup (i.e. do not use audio cut-in).
[R-6.6.2.2-011]
The MCX Service shall prevent an authorized MCX User from including a temporary group in a Group Regroup operation.
[R-6.6.2.2-012]
The MCX Service shall prevent an authorized MCX User from including a MCX Group that is already part of an existing Group Regroup in a different Group Regroup operation.
[R-6.6.2.2-013]
The MCX Service shall be configurable either to prevent or to allow all authorized MCX Users from including a MCX Group that is in emergency state in a Group Regroup operation.
6.6.3 Temporary Broadcast Groups p. 37
[R-6.6.3-001]
The MCX Service shall enable an authorized MCX User to create a temporary Group-Broadcast Group from a multiplicity of MCX Service Groups within that MCX Service.
[R-6.6.3-001a]
The MCX Service shall enable an authorized MCX User to create a temporary User-Broadcast Group from a multiplicity of MCX Users within that MCX Service.
[R-6.6.3-001b]
The MCX Service shall enable an authorized MCX User to create a temporary Broadcast Group from a combination of a multiplicity of MCX Service Groups and a multiplicity of MCX Users within that MCX Service.
[R-6.6.3-002]
The MCX Service shall only allow the creator of the temporary Broadcast Group to transmit on it.
6.6.4 User regrouping p. 37
6.6.4.1 Service description p. 37
6.6.4.1.1 User regrouping controlled by dispatcher or authorized user |R16| p. 37
There is a need for a mechanism for combining MCX Users into a new MCX Service Group under control by a dispatcher or authorized user to support ad-hoc communication needs.
In the operational MCX Service environment, most tasks are covered by standard procedures and communication structures, and MCX Users can easily access the MCX Service Groups to handle their tasks.
Exceptionally it could happen that there is an urgent need for a dedicated set of individual MCX Users to communicate in an MCX Service 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 MCX Service Group to these MCX Users to enable the required communication. Depending on configuration the MCX Users could be automatically affiliated to this MCX Service Group. After the operation this MCX Service Group is removed by the dispatcher or authorized user.
6.6.4.1.2 Automatic user regrouping |R16| p. 37
There is also a need to for an automatic mechanism that determines a set of individual MCX Users to become members of a MCX Service Group and to automatically become affiliated to that MCX Service Group.
These individual MCX Users are selected automatically by the MCX Service based on certain parameters (e.g. location, geographic area, participant type, direction of movement, speed). If MCX Service Group members do not meet the parameters anymore they will automatically be de-affiliated from the MCX Service Group and removed from the MCX Service Group member list. The remaining MCX Service Group members and the MCX Service Group member(s) removed will be informed accordingly. Conversely, MCX Users that are starting to meet the parameters (e.g due to location changes) will automatically be added and affiliated to the MCX Service Group. The MCX Service Group members and the added MCX Service Group member(s) will be informed accordingly.
6.6.4.2 Requirements p. 37
[R-6.6.4.2-001]
The MCX Service shall provide a means for combining a multiplicity of MCX Users into a new, temporary group (i.e., to perform a "User Regroup operation").
[R-6.6.4.2-002]
The MCX Service shall provide a means for combining a multiplicity of MCX Users into a new, temporary group based on a parameter or a combination of parameters (e.g., particular geographic area, Participant type, initiation of urgent type communication such as MCX Emergency Alert or MCX Emergency Group Communication).
[R-6.6.4.2-002a]
The MCX Service shall provide a means for automatically combining a multiplicity of MCX Users into a temporary MCX Service Group based on certain criteria. For example, the criteria may include one or more parameters from the list below:
- A specific element or combination of specific elements in the functional alias of a MCX User
- Location (including speed and heading) of a MCX User
- Location or particular geographic area specified by an MCX Service Administrator
- MCX Service configuration (e.g. MCX User responsible for a certain geographic area or MCX User responsible for a certain MCX Service Group)
The MCX Service shall be able to automatically update the memberslist of a temporary MCX Service Group based on certain criteria i.e. to remove MCX Users no more meeting the criteria and add MCX Users starting to meet the criteria. For example, the criteria may include one or more parameters from the list below:
- A specific element or combination of specific elements in the functional alias of a MCX User
- Location (including speed and heading) of a MCX User
- Location or particular geographic area specified by an MCX Service Administrator
- MCX Service configuration (e.g. MCX User responsible for a certain geographic area or MCX User responsible for a certain MCX Service Group)
The MCX Service shall provide a mechanism to preconfigure the parameters for a particular User Regroup operation, such that an authorized MCX User activates this preconfigured User Regroup and communicates with this temporary group with minimal delay.
[R-6.6.4.2-004]
The MCX Service shall notify MCX Users when they are affected by a User Regroup operation.
[R-6.6.4.2-005]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure whether an MCX Service system shall automatically affiliate the MCX Users included in the temporary group created by the User Regroup operation.
6.6.5 Dynamic Group Participation |R16| p. 38
6.6.5.1 Service description p. 38
Dynamic group participation enables control of group affiliation, de-affiliation, and selection on MCX Service Groups based on various combinations of criteria. For highly mobile MCX UEs, such as those used in railway communication, the group affiliation and selection needs to change, for example, when a train crosses a controlling area border.
6.6.5.2 Requirements p. 38
[R-6.6.5.2-001]
The MCX Service shall enable an MCX User to automatically affiliate to one or more MCX Service Groups based on one, or a combination of, criteria.
[R-6.6.5.2-002]
The MCX Service shall be able to automatically affiliate an MCX User to one or more MCX Service Groups based one, or a combination of, criteria.
[R-6.6.5.2-003]
The MCX Service shall enable an MCX User to automatically choose the Selected MCX Service Group based on one, or a combination of, criteria.
[R-6.6.5.2-004]
The MCX Service shall be able to automatically choose the Selected MCX Service Group of an MCX User based on one, or a combination of, criteria.
[R-6.6.5.2-005]
The MCX Service shall enable an MCX User to automatically de-affiliate from one or more currently affiliated groups based on a change to one, or a combination of, criteria.
[R-6.6.5.2-006]
The MCX Service shall be able to automatically de-affiliate an MCX User from one or more currently affiliated groups based on a change to one, or a combination of, criteria.
[R-6.6.5.2-007]
The MCX Service shall be able to prevent an MCX User de-affiliating from specific currently affiliated groups based on one, or a combination of, criteria.
[R-6.6.5.2-008]
The MCX Service shall enable an MCX User to select on specific MCX UEs whether automatic affiliation and/or de-affiliation is allowed.
6.7 Private Communication p. 39
6.7.1 Overview p. 39
Private Communications can use some form of Floor control or not.
6.7.2 General requirements p. 39
[R-6.7.2-001]
The MCX Service should provide a mechanism for authorized MCX Users to query whether a particular MCX User is present on the network.
[R-6.7.2-002]
The MCX Service should provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to place a Private Communication (without Floor control).
[R-6.7.2-003]
The MCX Service should provide a mechanism for authorized MCX Users to query whether a particular MCX User is capable of participating in a Private Communication.
[R-6.7.2-004]
The MCX Service shall provide a mechanism by which an MCX User can make a Private Communication to the local dispatcher based on the MCX User's current Location.
[R-6.7.2-005]
The MCX Service shall provide a mechanism for the Private Communication to be set up with the MCX UE designated by the receiving MCX User to be used for Private Communications when the receiving MCX User has signed on to the MCX Service with multiple MCX UEs.
[R-6.7.2-006]
The MCX Service shall provide ability for the MCX Service Administrator to set up a Private Communications with a different MCX UE than the one designated by the receiving MCX User, who has signed on to the MCX Service with multiple MCX UEs.
6.7.3 Administrative p. 39
[R-6.7.3-001]
The MCX Service should provide a mechanism for an MCX Service Administrator to configure whether the presence on the network of a particular MCX User is available.
[R-6.7.3-002]
The MCX Service should provide a mechanism for an MCX Service Administrator to configure which MCX Users may determine whether a particular MCX User is present on the network.
[R-6.7.3-003]
The MCX Service should provide a mechanism for an MCX Service Administrator to configure whether the ability to participate in Private Communications of a particular MCX User is available.
[R-6.7.3-004]
The MCX Service should provide a mechanism for an MCX Service Administrator to configure which MCX Users may determine whether a particular MCX User is capable of participating in a Private Communication.
[R-6.7.3-005]
Void.
[R-6.7.3-006]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Users, within their authority, are authorized to place an Automatic Commencement Private Communication (without Floor control).
[R-6.7.3-007]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular authorized MCX User, a set of MCX Users under the same authority to which a Private Communication (without Floor control) can be made by this particular MCX User.
[R-6.7.3-007a]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure for a particular authorized MCX User, a set of MCX Users under the same authority from which Private Communication (without Floor control) is allowed to this particular MCX User.
[R-6.7.3-008]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the maximum duration for Private Communication for MCX Users within their authority.
6.7.4 Prioritization p. 40
[R-6.7.4-001]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of Private Communications and Group Communications with respect to transport.
[R-6.7.4-002]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of Private Communications and Group Communications with respect to presentation.
[R-6.7.4-003]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of different Private Communications with respect to transport.
[R-6.7.4-004]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of different Private Communications with respect to presentation.
[R-6.7.4-005]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of Private Communications and other traffic with respect to transport.
[R-6.7.4-006]
The MCX Service shall provide a mechanism to establish, dynamically and in real-time, the relative priorities of Private Communications and other traffic with respect to presentation.
[R-6.7.4-007]
The MCX Service shall provide a mechanism to prioritize Private Communications based on the priorities associated with elements of the communication (e.g., service type, requesting identity, and target identity).
6.7.5 Private Communication (without Floor control) commencement requirements p. 40
[R-6.7.5-001]
The MCX Service shall provide a means by which an MCX UE initiates a Private Communication (without Floor control) to any MCX User for which the MCX UE's current MCX User is authorized.
[R-6.7.5-002]
The MCX Service shall provide a means by which an MCX User initiates an Automatic Commencement Private Communication (without Floor control) to any MCX User for which the MCX User is authorized.
[R-6.7.5-003]
The MCX Service shall provide a means by which the transmitting authorized MCX User is notified the receiving MCX User received the Private Communication (without Floor control) request.
6.7.6 Private Communication (without Floor control) termination p. 41
[R-6.7.6-001]
The MCX Service shall provide a mechanism for an MCX User to reject a Private Communication (without Floor control).
[R-6.7.6-002]
The MCX Service shall provide a means by which an MCX User ends a Private Communication (without Floor control) in which the MCX User is a Participant.
