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…

 

7  MCX Service requirements specific to off-network useWord‑p. 53

7.1  Off-network communications overviewWord‑p. 53

The MCX Service while operating in off-network mode comprises a set or collection of functions necessary to provide Mission Critical Services (e.g., MCPTT, MCVideo, MCData, etc.) using a ProSe direct (UE-to-UE) Communication path (ProSe direct communication path) for transport. The ProSe direct communication path does not traverse the network infrastructure.
Users operating off the network are either out of network coverage (not served by a 3GPP network) (e.g., in a remote mountain area fighting a forest fire 20 miles from the nearest network) or have selected a ProSe direct communication path for MCX Service while in network coverage. MCX Users operating off the network need to be in ProSe direct communication range in order to communicate.
MCX Users outside of the coverage of the fixed network might be first responders in a rural area assisting in a response to a plane crash, fire fighters in a remote mountain area fighting a forest fire or police officers inside a residence responding to a domestic issue. Off-network MCX Service communications are expected to be immediately accessible to users in the absence of the network.
MCX Users in network coverage might be working in a confined area, such as fire fighters fighting a structure fire where direct UE-to-UE communication is more desirable and reliable. Users can communicate directly with one another without having to overcome the resistance of a building and distance to the nearest base station to communicate with other members of their team inside the building that are nearby.
To operate off the network, an MCX UE is capable of automatically switching to a ProSe direct communication path for use of MCX Services when detecting an off-network (out of coverage) condition. In addition, a mechanism is provided for an authorized user to select (manually switch to) a ProSe direct communication path for use of off-network MCX Service communications (e.g., while in network coverage).
When operating off the network, the MCX Service is provided by the MCX Service Application on the UE as compared to operations on the network, where the MCX Service Application on the UE interacts with an MCX Service server and the network to provide the MCX Service.
The Off-Network MCX Service builds upon ProSe enablers to establish, maintain and terminate the signalling and communication path(s) among the off-network users. To the extent feasible, it is expected that the end user's experience is similar regardless if the MCX Service is used with a 3GPP network or based on the use of a ProSe direct communication path.
The Off-Network MCX Service is intended to support communication between a group of users (a group communication), where each user has the ability to gain access to transmit in an arbitrated manner. However, the MCX Service also supports Private Communications between pairs of users.
When operating off the network the MCX Service allows users to request the permission to transmit (transmit voice/audio) and provides a deterministic mechanism to arbitrate between requests that are in contention (i.e., Floor control).
The Off-Network MCX Service provides a means for a user with higher priority (e.g., MCX Service Emergency condition) to override (interrupt) the current sender. The Off-Network MCX Service also supports a mechanism to limit the time a user transmits (has access to the resources) thus permitting users of the same or lower priority a chance to gain access to the resources.
The Off-Network MCX Service provides the means for a user to monitor activity on a number of separate communications and enables the user to switch focus to a chosen communication. An Off-Network MCX User might join an already established MCX Service Group Communication (Late communication entry). In addition the Off-Network MCX Service supports MCX Service User IDs, aliases and user Location determination features.
For operation off the network (e.g., when out of network coverage), an MCX UE is (pre-)provisioned by an MCX Service Administrator and/or authorized user with the following in order to use MCX Services:
  1. An MCX Service User Profile associated with each of the intended MCX Users of the MCX UE that might be used for off-network operation;
    1. An alphanumeric identifier (with a minimum length of Nc3) (i.e., alias) for each MCX User;
    2. A number of off-network MCX Service Groups for use by the MCX User;
    3. An alphanumeric identifier (i.e., alias) for the authorized off-network MCX Service Groups;
    4. A Mission Critical Organization name if available, associated with each of the intended MCX Users or Administrator;
    5. A number of off-network MCX Users for Private Communications for which the MCX User is authorized;
  2. Authentication and end-to-end security keys.
An MCX UE operating off the network is capable of transmitting the sender's Location information, MCX Service User ID, alias(es), off-network MCX Service Group ID, group alias and, if available, Mission Critical Organization name of the user who is transmitting (i.e., whose UE is transmitting) to all other users in a communication including MCX UEs operating off the network that are late entering a communication in progress.
The Off-Network MCX Service uses the capabilities defined in ProSe TS 22.278, including the ProSe Relay capabilities defined in ProSe TS 22.278 and GCSE_LTE TS 22.468.
MCX Service requirements specific to off-network use are defined in clause 7. Common MCX Service requirements defined in clause 5 apply whether the MCX Service is in use on the network or off the network.
Up

7.2  General off-network MCX Service requirementsWord‑p. 55

[R-7.2-001]
In order to operate off the network using the direct communication path, an MCX UE shall be a Public Safety ProSe-enabled UE.
[R-7.2-002]
The Off-Network MCX Service shall make use of the ProSe capabilities related to ProSe Communication using the direct communication path between Public Safety ProSe-enabled UEs as defined in TS 22.278.
[R-7.2-003]
The MCX Service shall provide a mechanism for an MCX Service Administrator and/or authorized user to pre-provision MCX UEs that may not be served by the network with the following in order to operate using off-network MCX Service:
  1. An MCX Service User Profile associated with each of the intended MCX Users of the MCX UE that might be used for off-network operation:
    1. alphanumeric identifier (i.e., Alias ID) for the authorized off-network MCX Service Groups;
    2. a number of off-network MCX Service Groups for use by an MCX User;
    3. a MCX Service User ID associated with each of the intended MCX Users;
    4. an alphanumeric identifier (with a minimum length of Nc3) (i.e., alias) for each MCX Service User ID.
  2. authentication and end to end security keys.
[R-7.2-004]
An MCX UE operating off the network shall be capable of transmitting the MCX Service User ID, alias(es), off-network MCX Service Group and, if available, Mission Critical Organization name of the user who is talking (i.e., whose UE is transmitting) to all other users in the communication including MCX UEs operating off the network that enter the communication late.
[R-7.2-005]
An MCX UE operating off the network shall be capable of transmitting the sender's Location information (i.e., whose UE is transmitting) to all other users in the communication including MCX UEs operating off the network that enter the communication late.
Up

7.3  Admission controlWord‑p. 56

7.3.1  General aspectsWord‑p. 56

[R-7.3.1-001]
The admission control functionality shall authorize a participant to start a communication.
[R-7.3.1-002]
The admission control function shall be common to all services. That is to say resources are shared by all MCX Services depending on priorities. When a new communication is started an MCX service shall take into account priorities of all MCX Services communications as well as the resources they take/need.
[R-7.3.1-003]
The off-network Floor control functionality in an MCX Service shall determine at a point in time which received transmission(s) from off-network Participant(s) shall be presented to the receiving off-network Participant(s).
Up

7.3.2  Communication initiationWord‑p. 56

[R-7.3.2-001]
An authorized participant shall be able to request to start a communication.
[R-7.3.2-002]
The admission control functionality shall determine if an MCX User is allowed to start a communication and transmit according to resource management.
[R-7.3.2-003]
Following an off network MCX Service request for permission to transmit on the Selected MCX Group, the Affiliated MCX Group Member that made and was granted the request shall be given an indication of being granted permission to transmit.
[R-7.3.2-004]
When an MCX User is not allowed to start a communication, the MCX Service shall notify the MCX User that his communication has been queued or rejected.
[R-7.3.2-005]
When an MCX User is not allowed to start a communication the request may be queued or rejected.
Up

7.4  Communication terminationWord‑p. 56

[R-7.4-001]
The MCX Service when operating off the network shall provide a mechanism for an MCX Service Administrator to preconfigure separately the limit for the total length of time of an MCX Service Group Communication and an MCX Service Private Communication.
[R-7.4-002]
The MCX Service when operating off the network shall provide an indication to the Participants that the communication is within a configurable amount of time before the communication time limit is reached.
[R-7.4-003]
The MCX Service when operating off the network shall provide an indication to the Participants that the communication time limit has been reached.
[R-7.4-004]
The MCX Service when operating off the network shall release the communication when the communication time limit has been reached.
Up

7.5  Broadcast GroupWord‑p. 56

[R-7.5-001]
The MCX Service when operating off the network shall support Broadcast Group Communications within that MCX Service.
[R-7.5-002]
The MCX Service shall deliver an off-Network Broadcast Group Communication to the members of a Broadcast Group within that MCX Service who are within communication range, and who may be all of the MCX Service system users, or a subset thereof.

7.6  MCX Service priority requirementsWord‑p. 57

[R-7.6-001]
The Off-Network MCX Service shall assign to each MCX Service Group or Private Communication:
  • an application layer pre-emption capability;
  • a capability to be pre-empted; and
  • an application layer priority value.
[R-7.6-002]
The Off-Network MCX Service shall support at least 8 configurable levels of priority.
[R-7.6-003]
The Off-Network MCX Service shall support multiple MCX Service Application priorities which are mapped to ProSe priority levels, based on network operator policy.
[R-7.6-004]
The Off-Network MCX Service shall enable an MCX Service Administrator to prioritize MCX Groups in relation to other MCX Groups (with respect to transport and presentation).
[R-7.6-005]
When determining priority for an MCX communication, the Off-Network MCX Service shall use the MCX User/Participant's attributes (e.g., first/second responder, supervisor, dispatcher, on/off duty) and the MCX Group's attributes (e.g., type of group, owning organization of the group, MCX Emergency, Imminent Peril).
[R-7.6-006]
The Off-Network MCX Service shall support multiple pre-emptive priorities.
[R-7.6-007]
The Off-Network MCX Service shall provide a mechanism for MCX Administrators to create, a pre-emption hierarchy for MCX Group communications and their associated users (i.e., to facilitate local management of the service and its resources).
[R-7.6-008]
The Off-Network MCX Service shall support MCX Groups with the permission to pre-empt other MCX communications.
[R-7.6-009]
In case of resource shortage an MCX communication made to a group with pre-emption permissions shall be given resources to complete this communication by pre-empting lower priority MCX communications.
Up

7.7  Communication types based on prioritiesWord‑p. 57

7.7.1  MCX Service Emergency Group Communication requirementsWord‑p. 57

[R-7.7.1-001]
The Off-Network MCX Service shall provide a mechanism for an authorized Participant of an off-network MCX Service Group Communication to change the status of the off-network MCX Service Group Communication in progress to an off-network MCX Service Emergency Group Communication.
[R-7.7.1-002]
An off-network MCX UE that has initiated the MCX Service Emergency Group Communication shall maintain knowledge of the in progress off-network MCX Service Emergency Group Communication until it is cancelled.
[R-7.7.1-003]
An off-network MCX UE initiating an off-network MCX Service Emergency Group Communication shall be capable of transmitting its MCX Service User ID and an indication that it is an off-network MCX Service Emergency Group Communication to all other users in the communication.
Up

7.7.2  MCX Service Emergency Group Communication cancellation requirementsWord‑p. 57

[R-7.7.2-001]
An indication of the cancellation of an off-network MCX Service Emergency Communication and the identity of the cancelling user shall be transmitted to Affiliated MCX Service Group Members of the off-network MCX Service Emergency Group Communication.

7.7.3  Imminent Peril CommunicationWord‑p. 58

7.7.3.1  Imminent Peril Group Communication requirementsWord‑p. 58

[R-7.7.3.1-001]
The Off-Network MCX Service shall provide a mechanism for an Affiliated MCX Service Group Member to initiate (or join) an off-network MCX Service Group Communication and set (or change) the status of the communication to Imminent Peril.
[R-7.7.3.1-002]
If an MCX Service Group has previously been configured to be used for Imminent Peril communications by the MCX User, that MCX Service Group shall be used for the communication.
[R-7.7.3.1-003]
The MCX Service when operating in off-network mode shall provide a mechanism, for an authorized Participant of an in progress off-network MCX Service Group Communication, to change the status of the communication to an off-network MCX Service Imminent Peril group communication.
[R-7.7.3.1-004]
The off-network MCX UE that has initiated an MCX Service Imminent Peril group communication shall be responsible for maintaining the knowledge of the Imminent Peril status until it is cancelled.
[R-7.7.3.1-005]
The Off-Network MCX Service shall provide a mechanism to inform and keep updated other Participants of the MCX Service Group Communication regarding the Imminent Peril status of the communication and regarding the MCX Service User ID of the MCX User setting the status to Imminent Peril.
Up

7.7.3.2  Imminent Peril Group Communication cancellation requirementsWord‑p. 58

[R-7.7.3.2-001]
An indication of the cancellation of the Imminent Peril status of an off-network MCX Service Imminent Peril group communication and the MCX Service User ID of the cancelling user shall be transmitted to Affiliated MCX Service Group Members of an off-network MCX Service Imminent Peril group communication.
[R-7.7.3.2-002]
If the Imminent Peril status of an MCX Service Imminent Peril group communication is cancelled by an MCX User other than the user initiating the Imminent Peril status, then the Off-Network MCX Service shall provide a mechanism to clear the knowledge of the Imminent Peril status maintained at the UE of the initiating MCX User.
Up

7.8  LocationWord‑p. 58

[R-7.8-001]
An MCX UE shall be capable of transmitting its Location, if known, to other MCX UEs when operating off the network, subject to privacy restrictions.
[R-7.8-002]
An MCX UE shall be capable of providing a mechanism for obtaining the distance between the MCX UE and other MCX UEs within communication range.
[R-7.8-003]
The Off-Network MCX Service shall provide a means for an authorized MCX User to activate a one-time Location information report of a particular target MCX User within communication range.

7.9  SecurityWord‑p. 58

[R-7.9-001]
MCX UEs operating off the network shall be capable of protecting the confidentiality of Location and identity information conveyed to or from other MCX UEs.
[R-7.9-002]
MCX UEs operating off the network shall be capable of authenticating the sender of messages carrying Location and identity information.

7.10  Off-network MCX Service operationsWord‑p. 58

[R-7.10-001]
Off-Network MCX Services shall be able to operate in the complete absence of any fixed infrastructure.
[R-7.10-002]
Off-Network MCX Services shall only be available for authorized users.
[R-7.10-003]
The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize users for Off-Network MCX Services.

7.11  Off-network UE functionalityWord‑p. 59

[R-7.11-001]
An MCX UE shall be capable of utilizing off-network MCX Service and on-network MCX Service at the same time.
[R-7.11-002]
When switching from on-network to off-network operation (either manually or automatically), an MCX UE should attempt to notify the MCX Service that it is leaving the network.
[R-7.11-003]
Prior to automatically going off the network an MCX UE should attempt to make use of suitable ProSe UE-to-Network Relay in its proximity.
Up

7.12  Streaming for ProSe UE-to-UE Relay and UE-to-Network RelayWord‑p. 59

7.12.1  UE-to-Network Relay for all data typesWord‑p. 59

[R-7.12.1-001]
MCX Users shall be able to transmit and receive real time data (e.g., voice, streaming video/data) between an on-network MCX UE and an off-network MCX UE via a ProSe UE-to-Network relay using the MCX UE-to-Network Relay service.
[R-7.12.1-002]
The MCX Service shall provide a mechanism for an authorized MCX User to forward real-time data (e.g. voice, streaming video/data) from an MCX User to another MCX User across a ProSe UE-to-Network relay using the MCX UE-to-Network Relay service.
[R-7.12.1-003]
The MCX Service shall provide a mechanism for an MCX Service Administrator to authorize an MCX User to forward real time data (e.g. voice, streaming video/data) from one MCX User to another MCX User.
[R-7.12.1-004]
The MCX Service shall provide a mechanism to select/re-select a UE-to-Network Relay node that has enough capability for the real time data (e.g. video) forwarding.
Up

7.12.2  UE-to-UE Relay streamingWord‑p. 59

[R-7.12.2-001]
MCX Users shall be able to transmit and receive streaming video or data between an off-network MCX UE and another off-network MCX UE via a ProSe UE-to-UE relay using the MCX UE-to-UE Relay service.
[R-7.12.2-002]
The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from on-network operation to off-network operation via a ProSe UE-to-UE relay.
[R-7.12.2-003]
The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from off-network operation via a ProSe UE-to-UE relay to on-network operation.
Up

7.12.3  Off-Network streamingWord‑p. 59

[R-7.12.3-001]
MCX Users shall be able to transmit and receive streaming video or data between an off-network MCX UE and another off-network MCX UE via ProSe communications.
[R-7.12.3-002]
The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from a ProSe UE-to-UE relay to ProSe direct communications with another MCX UE.
[R-7.12.3-003]
The MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection for that communication from ProSe direct communications with another MCX UE to a ProSe UE-to-UE relay.
Up

7.13  Switching to off-network MCX ServiceWord‑p. 60

[R-7.13-001]
An MCX UE shall be capable of automatically switching to a ProSe direct communications path for use of MCX Service when detecting an off-network (out of coverage) condition.
[R-7.13-002]
A means shall be provided for an authorized MCX User to be able to manually switch between on-network operation and a ProSe direct communication path for use of Off-Network MCX Service while in network coverage.
[R-7.13-003]
Subject to operator policy and/or network authorization, a means shall be provided for an authorized MCX User using a Public Safety ProSe-enabled UE to be able to manually switch between the on-network operation and a ProSe direct communication path for use of Off-Network MCX Service while in network coverage or out of network coverage.
[R-7.13-004]
An MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection to that communication from on-network operation to off-network ProSe direct communication with another MCX UE.
[R-7.13-005]
An MCX Service shall minimize the interruption to an on-going MCX Service communication when an MCX UE transitions its connection to that communication from off-network ProSe direct communication with another MCX UE to on-network operation.
Up

7.14  Off-network recording and audit requirementsWord‑p. 60

[R-7.14-001]
The Off-Network MCX Service shall provide a mechanism to collect metadata for MCX Service Group Communications and MCX Service Private Communications (e.g., initiating MCX Service User ID, MCX Service Group ID) and non-communication activities (e.g., changing group settings) from MCX UEs operating in off-network mode. Metadata shall be logged for both the transmitting Participant and the receiving Participant(s).
[R-7.14-001a]
The Off-Network MCX Service shall provide a mechanism for a Mission Critical Organization to record the media content of the transmitting Participant of Group Communications and Private Communications under the organization's authority from MCX UEs operating in off-network mode.
[R-7.14-002]
Upon return to on-network operation, the MCX Service shall provide a mechanism to retrieve communication and non-communication activity metadata from an MCX UE that has collected such metadata while operating in off-network mode.
[R-7.14-002a]
Upon return to on-network operation, the MCX Service shall provide a mechanism to retrieve the media content of the transmitting Participant of Group Communications and Private Communications from an MCX UE that has recorded such media content while operating in off-network mode.
Up

7.15  Off-network UE-to-UE RelayWord‑p. 60

7.15.1  Private CommunicationsWord‑p. 60

[R-7.15.1-001]
The Off-Network MCX Service shall provide a means by which the MCX User of a (source) UE can make a Private Communication to the MCX User of a (target) UE via a ProSe UE-to-UE Relay.
[R-7.15.1-002]
The Off-Network MCX Service shall provide a mechanism for a source MCX User to query whether a particular target MCX User is within ProSe direct communication range.
[R-7.15.1-003]
An MCX UE shall be able to:
  • discover whether the UE of the target MCX User is itself within direct communication range of the source UE; and if not;
  • instead discover whether the UE of the target MCX User is within communication range of a ProSe UE-to-UE Relay that is within direct communication range of the source UE.
Up

7.15.2  Group CommunicationsWord‑p. 61

[R-7.15.2-001]
An MCX Service Administrator or authorized user shall be able to configure a ProSe-enabled UE, authorized to act as a ProSe UE-to-UE Relay, to relay any received MCX Service transmissions for one (or more) specified MCX Service Groups.
[R-7.15.2-002]
An MCX UE receiving both the original MCX Service Group transmission and a relayed transmission shall be able to associate the two transmissions, correctly order a mixture of packets (received directly and indirectly) and identify duplicate packets.

7.16  Off-network Ad hoc Group Communication |R18|Word‑p. 61

[R-7.16-001]
The off-network MCX Service shall provide a mechanism to combine an ad hoc multiplicity of MCX Users within communication range into a group communication.

Up   Top   ToC