Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 22.280  Word version:  18.1.0

Top   Top   Up   Prev   Next
1…   5…   5.9…   6…   6.8…   7…   8…   A…

 

5  MCX Service requirements common for on the network and off the networkWord‑p. 12

5.1  General Group Communications requirementsWord‑p. 12

5.1.1  General aspectsWord‑p. 12

[R-5.1.1-001]
The MCX Service shall allow an MCX User utilizing one or more MCX UE(s), concurrently, to sign-in and receive service on each of the MCX UE(s).
[R-5.1.1-002]
The MCX Service shall provide a mechanism by which an MCX UE makes a MCX Service group transmission to any MCX Service Group(s) for which the current MCX User is authorized.
[R-5.1.1-003]
The MCX Service shall be able to notify the Affiliated MCX Service Group Members when the group communication is set up (e.g., this can be provided as an audible tone on the MCX UE).
[R-5.1.1-004]
The MCX Service shall provide a mechanism to disable notifications (e.g., audible tone) on an MCX UE when receiving normal MCX Service Group Communications (not MCX Service Emergency or Imminent Peril Communications).
[R-5.1.1-005]
At any moment in time in an MCX Service Group communication, only one Participant type shall be used per Participant.
[R-5.1.1-006]
The MCX Service shall provide a mechanism for a dispatcher or authorized user to configure which content source shall be able to transmit the content to an MCX Service Group (e.g. video cameras near an incident).
Up

5.1.2  Group/status informationWord‑p. 12

[R-5.1.2-001]
The MCX Service shall provide a mechanism by which an MCX Service UE determines in which of the MCX Service Groups for which it is authorized there is an on-going MCX Service Group Communication.
[R-5.1.2-002]
The MCX Service shall provide a mechanism by which an authorized MCX User determines in which MCX Service Groups there is an on-going MCX Service Group Communication.

5.1.3  Group configurationWord‑p. 13

[R-5.1.3-001]
The MCX Service shall allow the MCX Service Administrator to restrict who can be a member of specific MCX Service Groups, so that those MCX Service Groups shall be inaccessible to other users, including dispatchers or supervisors.
[R-5.1.3-002]
The MCX Service shall enable a properly provisioned and authorized MCX UE operating on the network to receive its application layer level parameters (e.g., MCX Service Group ID, group keys) necessary for initiating and participating in Selected MCX Service Group and Private Communications at a future time, while off the network.
Up

5.1.4  IdentificationWord‑p. 13

[R-5.1.4-001]
The MCX Service shall support identifiers using character sets for international languages specified via configuration.

5.1.5  Membership/affiliationWord‑p. 13

[R-5.1.5-001]
The MCX Service shall provide a mechanism by which an MCX User determines the currently defined MCX Service Groups for which the MCX User is authorized.
[R-5.1.5-002]
The MCX Service shall provide a mechanism by which an MCX UE determines the currently defined MCX Service Groups for which it is authorized.
[R-5.1.5-003]
The MCX Service shall support an MCX User's ability to affiliate to one or more MCX Service Groups.
[R-5.1.5-004]
The MCX Service shall provide a mechanism for an MCX Service Administrator to limit the total number (Nc2) of MCX Service Groups that an MCX User can be affiliated to simultaneously.
[R-5.1.5-005]
An MCX User may simultaneously be an MCX Service Group Member of one or more MCX Service Groups.
[R-5.1.5-006]
The MCX Service shall provide a mechanism for an MCX Service Group Member to select zero or one Selected MCX Service Group.
[R-5.1.5-007]
The MCX Service shall require that MCX Users affiliate with MCX Service Groups prior to participation in the communications of those groups.
[R-5.1.5-008]
An MCX User shall be able to affiliate with a multiplicity of MCX Service Groups, subject to restrictions configured by the MCX Service Administrator.
Up

5.1.6  Group Communication administrationWord‑p. 13

[R-5.1.6-001]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure the maximum duration for MCX Service Group Communications for MCX Users within their authority.

5.1.7  PrioritizationWord‑p. 13

[R-5.1.7-001]
The MCX Service shall provide a mechanism to organize MCX Service Groups into a hierarchy(ies).
[R-5.1.7-002]
The MCX Service shall provide a mechanism to prioritize MCX Service Group Communications based on the priorities associated with elements of the communication (e.g., service type, requesting identity, and target identity).

5.1.8  Charging requirements for MCX ServiceWord‑p. 14

[R-5.1.8-001]
The MCX Service shall support charging for MCX Service Group Communications.
[R-5.1.8-002]
Void
[R-5.1.8-003]
The MCX Service shall support time-of-day sensitive charging based on actual resource utilization, provided QoS and provided priority.
[R-5.1.8-004]
The MCX Service shall generate charging data that identifies the device(s) involved in a communication.
[R-5.1.8-005]
The MCX Service shall support confidentiality of the charging between the service provider and the network operator.
[R-5.1.8-006]
The MCX Service shall support confidentiality of the identity of the Mission Critical Organization.
[R-5.1.8-007]
The MCX Service shall support reconciliation of the charging records between the service provider and the network operator.
[R-5.1.8-008]
The MCX Service shall support offline charging.
[R-5.1.8-009]
The MCX Service shall support online charging.
[R-5.1.8-010]
The MCX Service shall be able to generate charging data for on-network mode.
[R-5.1.8-011]
The MCX Service shall be able to generate charging data for off-network mode.
Up

5.1.9  MCX Service Emergency Alert triggered by LocationWord‑p. 14

[R-5.1.9-001]
The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to be triggered when an MCX UE moves into a predefined area.
[R-5.1.9-002]
The MCX Service shall provide a mechanism for an MCX Service Emergency Alert to be cancelled when the MCX UE moves out of a predefined area or to remain active until cancelled by the MCX User.

5.2  Broadcast GroupWord‑p. 14

5.2.1  General Broadcast Group CommunicationWord‑p. 14

[R-5.2.1-001]
The MCX Service shall support Broadcast Group Communications within that MCX Service from authorized MCX Service Group Members as determined by the MCX Service Administrator.
[R-5.2.1-002]
The MCX Service shall only allow the initiating MCX Service Group Member to transmit on a Broadcast Group Communication, unless overridden (e.g., by a supervisor).

5.2.2  Group-Broadcast Group (e.g., announcement group)Word‑p. 14

[R-5.2.2-001]
The MCX Service shall provide for the creation of Group-Broadcast Groups within that MCX Service with up to Bc1 levels of group hierarchy.
[R-5.2.2-002]
The MCX Service shall be configurable to create a Group-Broadcast Group from one or more Group-Broadcast Groups within that MCX Service with any other non-Broadcast Group from the same MCX Service.
[R-5.2.2-003]
The MCX Service shall enable an MCX Service Administrator to create a Group-Broadcast Group.
[R-5.2.2-004]
A Broadcast Group Communication transmitted on a Group-Broadcast Group shall have priority over Group Communications on its subordinate groups from the same MCX Service.
Up

5.2.3  User-Broadcast Group (e.g., System Communication)Word‑p. 14

[R-5.2.3-001]
The MCX Service shall provide for the creation of User-Broadcast Groups within that MCX Service with up to Bc2 levels of user hierarchy.
[R-5.2.3-002]
A Broadcast Group Communication transmitted on a User-Broadcast Group shall have priority over Group Communications from the same MCX Service involving users within the user hierarchy.

5.3  Late communication entryWord‑p. 15

[R-5.3-001]
The MCX Service shall provide a mechanism by which an Affiliated MCX Service Group Member can join an on-going MCX Service Group Communication.
[R-5.3-002]
The MCX Service shall provide the identities of the transmitting MCX Service Group Member, and of the MCX Service Group and, if available, the aliases of the transmitting MCX Service Group Member and the identity of the Mission Critical Organization to the MCX UEs that enter the communication late.
[R-5.3-003]
The MCX Service shall provide the transmitting MCX Service Group Member's Location information to MCX UEs that are late entering a communication in progress, subject to permissions.
[R-5.3-004]
If an MCX Service Group Communication proceeds without all Affiliated MCX Service Group Members (e.g., due to one or more members being temporarily out of coverage during the communication setup or in one or more higher priority communications), the MCX Service shall attempt to add those affiliated members as the communication proceeds and they become available.
[R-5.3-005]
If during an on-going MCX Service Group Communication, additional MCX Service Group Members affiliate with the MCX Service Group, the MCX Service shall add those members to the Group Communication.
[R-5.3-006]
When the late entry user(s) become(s) member of the Group communication, all participants may be notified about the late entry member joining the Group communication.
Up

5.4  Receiving from multiple MCX Service communicationsWord‑p. 15

5.4.1  OverviewWord‑p. 15

MCX Users receive communications traffic of their affiliated MCX Service Groups. This multiple receiving, called monitoring by some organizations, provides MCX 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 not be the primary support for that event at that moment. The information gained by monitoring might be useful for the dispatcher to determine any actions to take or be useful later if the MCX User is deployed to provide additional support for that event. The MCX User might be assigned to support the activities of more than one MCX Service Group on the same shift. This means that the MCX User receives multiple MCX Service Groups.
An MCX User with limited resources (e.g., a handheld UE) might find that using concurrent received MCX Service communications from multiple active MCX Service Groups becomes confusing. During periods of time when the MCX User is receiving communications from multiple MCX Service Groups, which MCX Service Group's communication is presented to the MCX User is determined by the MCX User's choice, the priority associated with the sender of the Selected MCX Service Group, other considerations or combinations of these. The MCX UE is aware of all the active groups to which the MCX User has affiliated and which is the selected group (if any). The identities of the other active receiving groups can be made available for display on the MCX UE. When the receive activity from the Selected MCX Service Group stops, the MCX UE might present the communications from another group per the MCX User's choice or by other means.
If none of the multiple groups to which the MCX User has affiliated or selected is active, the MCX UE would continue to monitor for activity by any of the multiple affiliated or Selected MCX Service Groups. Monitoring for activity of multiple MCX Service Groups is also known as scanning and the list of the multiple groups is also known as a scan list.
Up

5.4.2  RequirementsWord‑p. 15

[R-5.4.2-001]
The MCX Service shall allow an MCX UE to be receiving or transmitting in one MCX Service Group while simultaneously receiving additional MCX Service Groups.
[R-5.4.2-002]
The MCX Service shall provide a mechanism to configure the number (Nc4) of MCX Service Group Communications to be simultaneously received by an MCX UE, authorized by an MCX Service Administrator and/or authorized user.
[R-5.4.2-003]
The MCX Service shall provide a mechanism to configure the number (Nc5) of MCX Service Group Communications to be simultaneously received by an MCX User, authorized by an MCX Service Administrator and/or authorized user.s
[R-5.4.2-004]
The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to prioritize the order in which communications on multiple MCX Service Groups within an MCX Service User Profile are presented by the MCX user's MCX UE.
[R-5.4.2-004A]
The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to prioritize the order in which multiple MCX Service Private Communications are presented by the MCX user's MCX UE.
[R-5.4.2-004B]
The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to prioritize the order in which communications on MCX Service Groups within an MCX Service User Profile and MCX Service Private Communications are presented by the MCX user's MCX UE.
[R-5.4.2-005]
The MCX Service shall provide multiple MCX Service User IDs to an MCX UE when multiple MCX Service Groups that have a sender are received by the MCX UE.
[R-5.4.2-006]
The MCX Service shall allow an authorized MCX UE to receive on-network MCX Service Group and off-network MCX Service Group Communications simultaneously.
[R-5.4.2-007]
The MCX Service shall ensure that if there is an MCX Service Emergency Group Communication on one of the MCX Service Groups that an MCX User is affiliated to, but that user is already in a lower priority MCX Service Group Communication or Private Communication, that the MCX User automatically hears/displays the MCX Service Emergency Group Communication.
[R-5.4.2-007a]
Depending on meaningful elements of a functional alias the MCX Service shall be able to restrict or allow MCX Users to be involved in more than one MCX Service Emergency Group Communication at a time.
[R-5.4.2-008]
The MCX Service shall support reception and recording of multiple concurrent Private Communications by an authorized user (e.g., dispatch operator).
[R-5.4.2-009]
The MCX Service shall provide a mechanism by which an MCX UE can receive and record multiple concurrent Private Communications from MCX users for which the current MCX User is authorized.
Up

5.5  Private CommunicationWord‑p. 16

5.5.1  Private Communication general requirementsWord‑p. 16

[R-5.5.1-001]
The MCX Service shall provide a mechanism for a dispatcher or authorized user to configure which content source shall be able to send the content to an MCX User (e.g. video cameras near an incident).

5.5.2  Charging requirements for MCX ServiceWord‑p. 16

[R-5.5.2-001]
The MCX Service shall support charging for Private Communications.

5.6  MCX Service priority requirementsWord‑p. 16

5.6.1  OverviewWord‑p. 16

MCX Service Emergency Group Communications and MCX Service Imminent Peril Group Communications are MCX Service Group Communications that provide the MCX User elevated priority towards obtaining resources of the MCX Service system. The MCX Service Emergency Private Communication similarly provides elevated priority to resources of the MCX Service system. The MCX Service Emergency Alert provides a notification of an MCX Service Emergency situation from an MCX UE, regardless if the MCX User is signed in with the MCX Service or not.
The MCX Service Emergency Alert is initiated from an MCX UE to inform the MCX Service of the MCX User's immediate need of assistance due to the MCX User's personal, life-threatening situation. If the MCX User is not properly authenticated, he/she is treated as a temporary MCX User with limited permissions. The MCX User initiates this notification by actuating an MCX User interface on the MCX UE. The notification to the MCX Service includes the MCX User's ID, potentially an MCX Service Group ID, the user's Mission Critical Organization name and the most current location available for the user's MCX UE.
The MCX Service User Profile/group configuration determines which MCX Service Group ID is used, if any. If the MCX Service User Profile indicates that a dedicated (i.e., not used for everyday traffic) MCX Service Emergency Group is to be used, then the MCX Service Emergency communication traffic moves to a different group. MCX Users that support MCX Service Emergency situations monitor the dedicated MCX Service Emergency Group(s) for communications activity. If the MCX Service User Profile indicates that the Selected MCX Service Group is to be used, then its MCX Service Group ID is used, unless no group is selected for transmissions.
After the MCX User has initiated an MCX Service Emergency Alert, MCX Service Emergency Private Communication or MCX Service Emergency Group Communication, the MCX User is considered to be in the MCX Service Emergency State. The user remains in the MCX Service Emergency State until the MCX User cancels the MCX Service Emergency State.
An MCX Service Group Communication started by an MCX User while in the MCX Service Emergency State or previously started but followed by an MCX Service Emergency Alert becomes an MCX Service Emergency Group Communication. The MCX Service Group ID used for the MCX Service Emergency Group Communication is the same MCX Service Group ID included in the MCX Service Emergency Alert. An MCX User or dispatcher might initiate an MCX Service Emergency Group Communication without an MCX Service Emergency Alert. The start of an MCX Service Emergency Group Communication starts an In-progress Emergency condition for the MCX Service Group. Any subsequent MCX Service Group Communications made by any MCX Service Group Member of an MCX Service Group, which has an In-progress Emergency, is treated as an MCX Service Emergency Group Communication. MCX Service Emergency Group Priority is removed when the In-progress Emergency for the group is cancelled.
An MCX Service Private Communication started by an MCX User while in the MCX Service Emergency State becomes an MCX Service Emergency Private Communication.
MCX Service Imminent Peril Group Communications are differentiated from MCX Service Emergency Group Communications based on for whom the assistance is required. The MCX Service Emergency Group Communication is initiated by an MCX User for assistance for the MCX Service Emergency condition involving that user. An MCX Service Imminent Peril Group Communication is initiated by an MCX User for assistance to other MCX Users or persons of the general public observed to be in trouble and may soon need assistance.
There is no MCX Service Imminent Peril Alert and no MCX Service Imminent Peril State for MCX Users. The granting of an MCX Service Imminent Peril Group Communication starts an In-progress Imminent Peril condition for the MCX Service Group. Any subsequent MCX Service Group Communication made by any MCX Service Group Member of an MCX Service Group that has an In-progress Imminent Peril condition is treated as an MCX Service Imminent Peril Group Communication. MCX Service Imminent Peril Group Priority is removed when the In-progress Imminent Peril for the group is cancelled.
Up

5.6.2  Communication types based on prioritiesWord‑p. 17

5.6.2.1  MCX Service Emergency and Imminent Peril general requirementsWord‑p. 17

5.6.2.1.1  OverviewWord‑p. 17
Emergency Group Communication and Imminent Peril Group Communication are MCX Service Group Communications that provide the MCX User elevated priority towards obtaining resources of the MCX Service system. The MCX Service Emergency Alert provides a notification of an MCX Service Emergency situation from an MCX UE, regardless if the user is signed in with the MCX Service or not. The MCX Service Emergency Alert is initiated from an MCX UE to inform the MCX Service of the user's immediate need of assistance due to the user's personal, life-threatening situation.
When multiple MCX Services are active in an MCX UE, the interaction of these features between the services needs to be considered. When an MCX User initiates an Emergency Group Communication, he/she may only want a subset of the active MCX Services to have emergency priority. Likewise, for Imminent Peril the North American user requirement is that only the active MCX Service receives Imminent Peril priority when the Imminent Peril condition is initiated. For example, if the MCX User is transmitting a video when he/she initiates Imminent Peril, then only the MCVideo service will be granted elevated priority.
Up
5.6.2.1.2  RequirementsWord‑p. 18
[R-5.6.2.1.2-001]
When an MCX User initiates an MCX Service Emergency Group Communication, a subset of MCX Service applications (e.g. MCPTT, MCVideo) relevant to the MCX User and configured for the MCX Service Group, shall be used for MCX Service Emergency Group Communications.
[R-5.6.2.1.2-002]
The MCX Service shall support an MCX Service Emergency Alert, which on initiation by an MCX User shall put that MCX User into the MCX Service Emergency State and cause that MCX UE to send an MCX Service Emergency Alert containing the following information: Location, MCX Service User ID, the user's Mission Critical Organization name, the list of notification IDs (e.g. groups, other users), and the list of application service MCX Service Group IDs to be used for MCX Service Emergency Group Communication (i.e., user's selected group or dedicated MCX Service Emergency Group).
[R-5.6.2.1.2-003]
The MCX Service in the UE shall request Imminent Peril priority for the currently active MCX Service Application (e.g. MCPTT, MCVideo) when the MCX User requests an MCX Service Imminent Peril Group Communication.
[R-5.6.2.1.2-004]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Applications (e.g. MCPTT, MCVideo) are used for MCX Service Emergency Group Communications by an MCX User when that user is in an MCX Service Emergency State.
[R-5.6.2.1.2-005]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Applications (e.g. MCPTT, MCVideo) can be used for Imminent Peril Group Communication.
Up

5.6.2.2  MCX Service Emergency Group CommunicationWord‑p. 18

5.6.2.2.1  MCX Service Emergency Group Communication requirementsWord‑p. 18
[R-5.6.2.2.1-001]
The MCX Service shall support MCX Service Emergency Group Communications from an authorized MCX Group Member on the currently Selected MCX Group or on an MCX Group designated for MCX Service Emergency Group Communications.
[R-5.6.2.2.1-002]
When an MCX User initiates an MCX Service Emergency Group Communication this may trigger an MCX Service Emergency Alert for that MCX User.
[R-5.6.2.2.1-003]
When an MCX User initiates an MCX Service Emergency Group Communication this shall put that MCX User into an MCX Service Emergency State.
[R-5.6.2.2.1-004]
The MCX Service shall ensure that MCX Service Emergency Group Communications have the highest priority over all other MCX Service Group transmissions from the same MCX Service, except MCX Service System Communications, MCX Service Emergency Private Communications, and other MCX Service Emergency Group Communications.
[R-5.6.2.2.1-005]
The MCX Service shall be capable of changing a group communication in progress to an MCX Service Emergency Group Communication.
[R-5.6.2.2.1-006]
MCX Service Emergency Group Communications, including their content and signalling, shall have pre-emptive priority over all other types of MCX Service communications from the same MCX Service, except MCX Service System Communications, MCX Emergency Private Communications, and other MCX Service Emergency Group Communications.
[R-5.6.2.2.1-007]
The MCX Service shall provide the MCX Service User ID of the initiator of an MCX Service Emergency Group Communication and an indication that it is an MCX Service Emergency Group Communication to Affiliated MCX Service Group Members.
[R-5.6.2.2.1-008]
The MCX Service shall add the MCX Service Emergency priority to the group when an In-progress Emergency on that group is initiated.
[R-5.6.2.2.1-009]
The MCX Service shall remove the MCX Service Emergency Priority associated with the group when an In-progress Emergency on that group is cancelled.
[R-5.6.2.2.1-010]
The Affiliated MCX Service Group Members shall be notified when their group communication transitions to an In-progress Emergency.
[R-5.6.2.2.1-011]
The MCX Service shall maintain knowledge of the Affiliated MCX Service Group Member(s) that initiated the MCX Service Emergency Group Communication(s) until the In-progress Emergency is cancelled.
[R-5.6.2.2.1-012]
The MCX Service shall maintain an In-progress Emergency condition for a group from the time the initial MCX Service Emergency Group Communication was requested until the In-progress Emergency condition is cancelled.
[R-5.6.2.2.1-013]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Group (i.e., user's selected group or dedicated MCX Service Emergency Group) is used for the MCX Service Emergency Group Communication by an MCX User.
[R-5.6.2.2.1-014]
While In-progress Emergency status is maintained for an MCX Service Group Communication, the MCX Service shall provide the MCX Service User ID of the initiator of the In-progress Emergency status and an indication that it is an MCX Service Emergency Group Communication to existing and Late communication entry Affiliated MCX Service Group Members.
Up
5.6.2.2.2  MCX Service Emergency Group Communication cancellation requirementsWord‑p. 19
[R-5.6.2.2.2-001]
The MCX Service shall support cancellation of an In-progress Emergency by an authorized MCX User for an MCX Service Group.
[R-5.6.2.2.2-002]
The MCX Service shall support cancellation of an In-progress Emergency for an MCX Service Group when criteria established by the MCX Service Administrator are met (e.g., timeout).
[R-5.6.2.2.2-003]
The MCX Service shall support cancellation of an In-progress Emergency for an MCX Service Group and MCX Service Emergency State for an MCX User by the MCX Service Emergency Group Communication initiator.
[R-5.6.2.2.2-004]
The MCX Service shall notify Affiliated MCX Service Group Members of the cancellation of the In-progress Emergency and the identity of the cancelling MCX User.
[R-5.6.2.2.2-005]
The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to cancel in-progress Emergencies.
Up

5.6.2.3  MCX Service Imminent Peril Group CommunicationWord‑p. 19

5.6.2.3.1  MCX Service Imminent Peril Group Communication requirementsWord‑p. 19
[R-5.6.2.3.1-001]
The MCX Service shall support Imminent Peril group communications from authorized Affiliated MCX Service Group Members.
[R-5.6.2.3.1-002]
The MCX Service (e.g. MCPTT, MCVideo) shall ensure that MCX Service Imminent Peril group communications have priority over all other MCX Service Group transmissions from the same MCX Service, except MCX Service System Communications, MCX Service Emergency Group Communications, MCX Service Emergency Private Communications, and other MCX Service Imminent Peril group communications.
[R-5.6.2.3.1-003]
The MCX Service shall be capable of changing an MCX Service Group communication in progress to an Imminent Peril group communication.
[R-5.6.2.3.1-004]
MCX Service Imminent Peril group communications, including their content and signalling, shall have pre-emptive priority over all other types of MCX Service communications from the same MCX Service, except MCX Service Emergency Group Communications, MCX Service Emergency Private Communications, MCX Service System Communications, and other MCX Service Imminent Peril group communications.
[R-5.6.2.3.1-005]
The Affiliated MCX Service Group Members shall be notified when an MCX Service Group communications transitions to In-progress Imminent Peril status.
[R-5.6.2.3.1-006]
While Imminent Peril status is maintained for an MCX Service Group communications, the MCX Service shall provide the MCX Service User ID of the initiator of the Imminent Peril status and an indication that it is an Imminent Peril group communication to existing and Late communication entry Affiliated MCX Service Group Members.
[R-5.6.2.3.1-007]
The MCX Service shall add the Imminent Peril priority to the group when an In-progress Imminent Peril on that group is initiated.
[R-5.6.2.3.1-008]
The MCX Service shall remove the Imminent Peril priority associated with the MCX Service Group when the In-progress Imminent Peril status of that MCX Service Group is cancelled.
[R-5.6.2.3.1-009]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Group (i.e., user's selected group or dedicated imminent peril group) shall be used for the Imminent Peril communications for an MCX User.
Up
5.6.2.3.2  MCX Service Imminent Peril Group Communication cancellation requirementsWord‑p. 20
[R-5.6.2.3.2-001]
The MCX Service shall support cancellation of an In-progress Imminent Peril by an authorized MCX User.
[R-5.6.2.3.2-002]
The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize MCX Service Users to cancel an In-progress Imminent Peril.
[R-5.6.2.3.2-003]
The MCX Service shall support cancellation of an In-progress Imminent Peril by the Imminent Peril group communication initiator.
[R-5.6.2.3.2-004]
The MCX Service shall support cancellation of an In-progress Imminent Peril when criteria created by the MCX Service Administrator are met.
Up

5.6.2.4  MCX Service Emergency AlertWord‑p. 20

5.6.2.4.1  MCX Service Emergency Alert requirementsWord‑p. 20
[R-5.6.2.4.1-001]
The MCX Service shall support an MCX Service Emergency Alert capability, which on initiation by an MCX User shall put that MCX User into the MCX Service Emergency State and cause that MCX UE to send an MCX Service Emergency Alert.
[R-5.6.2.4.1-002]
The MCX Service shall provide a means for an authorized user to be able to activate the MCX Service Emergency Alert capability.
[R-5.6.2.4.1-003]
The MCX Service Emergency Alert shall contain the following information: Location, MCX Service User ID and MCX Service Group ID (i.e., user's selected group or dedicated MCX Service Emergency Group, as per group configuration) and the user's Mission Critical Organization name.
[R-5.6.2.4.1-004]
The MCX Service Emergency Alert shall be distributed to affiliated members of the group that was used in the MCX Service Emergency Alert.
[R-5.6.2.4.1-004a]
For an MCX Service Emergency Private Communication the MCX Service Emergency Alert shall be distributed to the MCX User that the communication was initiated to.
[R-5.6.2.4.1-005]
The MCX Service shall provide a mechanism for an authorized MCX User to configure an MCX Service Emergency Alert to send a notification to MCX Users within a configurable geographic area of the MCX User entering the MCX Service Emergency State, independent of the MCX Service Group Membership.
[R-5.6.2.4.1-006]
The MCX UE shall maintain knowledge of the MCX Service Emergency State, until cancelled.
[R-5.6.2.4.1-007]
Until the MCX Service Emergency State is cancelled on the MCX UE, all MCX Service Group communications or Private Communications transmissions by the MCX User shall be an MCX Service Emergency Group Communication or Emergency Private Communication.
[R-5.6.2.4.1-008]
The MCX UE shall be configurable as to which group (i.e., user's selected group or dedicated MCX Service Emergency Group) or MCX User is used for the MCX Service Emergency communications.
[R-5.6.2.4.1-009]
The MCX UE shall immediately affiliate to the group configured for MCX Service Emergency Group Communication, if not already affiliated to the group, after activating an MCX Service Emergency Alert.
[R-5.6.2.4.1-010]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure how an MCX User is notified of an incoming MCX Service Emergency Alert (e.g., visual, audio).
[R-5.6.2.4.1-011]
The MCX Service shall provide a mechanism for an MCX User to configure, subject to MCX Service Policy, how they are notified of an incoming MCX Service Emergency Alert (e.g., visual, audio).
[R-5.6.2.4.1-012]
The MCX Service shall provide a mechanism for an MCX Service Administrator to configure which MCX Service Group (i.e., user's selected group or dedicated MCX Service Emergency Group) or MCX User (e.g., dispatcher) is used for the MCX Service Emergency Alert by an MCX User.
[R-5.6.2.4.1-013]
The MCX Administrator shall be able to configure whether the initiation of a MCX Service Emergency Alert shall also automatically trigger a MCX Service Emergency Group Communication.
Up
5.6.2.4.2  MCX Service Emergency Alert cancellation requirementsWord‑p. 21
[R-5.6.2.4.2-001]
The MCX UE shall only provide a means for cancelling the MCX Service Emergency State locally by an authorized user of that MCX UE.
[R-5.6.2.4.2-002]
The MCX Service shall support MCX Service Emergency Alert cancellation by authorized MCX Users.
[R-5.6.2.4.2-003]
The MCX Service shall distribute MCX Service Emergency Alert cancellation to all affiliated members of the group identified in the cancellation.

5.7  MCX Service User IDWord‑p. 21

[R-5.7-001]
The MCX Service shall provide a mechanism for the creation and deletion of aliases for an MCX User and its associated MCX Service User Profiles by authorized parties.
[R-5.7-002]
The MCX Service shall provide a mechanism for each MCX Service User ID to be associated with an alphanumeric identifier (with a minimum length of Nc3) (i.e., alias) assigned by an MCX Service Administrator.
[R-5.7-003]
All UEs shall provide a configurable capability to display the MCX Service User ID, aliases associated with the MCX Service User ID, with the Selected MCX Service Group, and with the Mission Critical Organization name.
Up

5.8  MCX UE managementWord‑p. 21

[R-5.8-001]
An MCX UE shall support one or more MCX Service User Profiles.
[R-5.8-002]
The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized MCX User to perform MCX UE Provisioning.

Up   Top   ToC