Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 22.280  Word version:  18.1.0

Top   Top   None   None   Next
1…   5…   5.9…   6…   6.8…   7…   8…   A…


1  ScopeWord‑p. 9

The present document provides the service requirements that are common across two or more mission critical services, that is MCPTT, MCData and MCVideo. The mission critical services make use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service as specified in TS 22.179, MCVideo Service as specified in TS 22.281, and MCData Service as specified in TS 22.282. The mission critical services can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specification do not apply to GSM or UMTS.

2  ReferencesWord‑p. 9

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1".
TS 22.281: "Mission Critical Video services".
TS 22.282: "Mission Critical Data services".
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
TS 22.468: "Group Communication System Enablers for LTE (GCSE_LTE) ".
TS 22.011: "Service accessibility".
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Stations (MS) in idle mode".
ISBN 2-7461-1832-4: "UIC Project EIRENE System Requirements Specification".
ETSI EN 301 515 V3.0.0 (2018-03): "Global System for Mobile communication (GSM); Requirements for GSM operation on railways".

3  Definitions and abbreviationsWord‑p. 9

3.1  DefinitionsWord‑p. 9

For the purposes of th geographic e present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Affiliated MCX Service Group Member:
An MCX Service Group Member who has indicated an interest in participating in communications of the group, has been accepted by the MCX Service, and is prepared to receive and/or transmit Group Communications from/to the particular MCX Group.
Air ground air Communication:
A communication (point-to-point or group) between at least one MCX User located on the ground and one or more MCX Users in helicopter(s) or aircraft while not on the ground, but in flight (in the air).
Broadcast Group Communication:
A group communication where the initiating MCX User expects no response from the other MCX Users, so that when the user's transmission is complete, so is the communication.
Group Communication:
A one-to-many or many-to-many communication using an MCX Service.
In-progress Emergency:
An emergency condition that has been accepted by the MCX Service, but has not yet been cancelled.
Late Entry:
An Affiliated MCX Service Group Member joins in an in progress MCX Service Group Communication.
The currentposition and if available information about the instantaneous velocity and direction of the MCX UE.
MCX Service Ad hoc Group Communication:
The combining of a multiplicity of MCX Users into a group for the duration of a communication and when the communication is terminated the group no longer exists.
MCX Service Administrator:
An individual authorized to control MCX parameters for an organization including, for example, user and group definitions, user/group aliases, user priorities, group membership/priorities/hierarchies, security and privacy controls.
MCX Service Emergency Alert:
A notification from the MCX UE to the MCX Service that the MCX User has an emergency condition.
MCX Service Emergency State:
A heightened condition of alarm for an MCX User indicating a need for immediate assistance due to a personal life-threatening situation.
MCX Service Emergency Group Communication:
An urgent MCX Service group communication initiated by a MCX user when there is the potential of immediate death or serious injury.
MCX Service Group:
A defined set of MCX Users with associated communication dispositions (e.g. media restrictions, default priority and commencement directions).
MCX Service Group Communication:
A group communication for a particular MCX Service.
MCX Service Group Member:
An MCX User authorized, upon successful affiliation, to participate in Group Communications of a particular MCX Group.
MCX Service Imminent Peril Group Communication:
An urgent MCX Service Group Communication initiated by an MCX user when there is a potential of death or serious injury, but is less critical than an MCX Service Emergency Group Communication.
MCX Service User Profile:
The set of information associated to an MCX User that allows that user to employ the MCX Service in a given role and/or from a given MCX UE.
A UE that can be used to participate in MCX Services.
MCX User:
A user of MCX Service, who can use an MCX UE to participate in MCX Services.
Mission Critical:
Quality or characteristic of a communication activity, application, service or device, that requires low setup and transfer latency, high availability and reliability, ability to handle large numbers of users and devices, strong security and priority and pre-emption handling.
Mission Critical Applications:
Generic communication applications with mission critical characteristics, traditionally encompassing push-to-talk voice (MCPTT), real-time video (MCVideo) and real-time data (MCData).
Mission Critical Organization:
An end-user organization that includes MCX Users and/or MCX UEs, and can include MCX Service Administrators, and can be organized hierarchically with administrative control delegated within the organization or to an outside entity.
Mission Critical Service:
Communication service providing enabling capabilities for Mission Critical Applications that are provided to end users from Mission Critical Organizations or other businesses and organizations (e.g., utilities, railways).
An MCX User who is currently receiving and/or transmitting in a Group Communication or a Private Communication.
Participant type:
Functional category of the Participant (e.g., first responder, second responder, dispatch, dispatch supervisor), typically defined by the MCX Service Administrators.
Private Communication:
A one-to-one communication between a pair of users using an MCX Service.
Selected MCX Service Group:
An MCX Service Group that a particular Affiliated MCX Service Group Member uses for transmission.
Transmitting MCX Service Group Member:
An Affiliated MCX Service Group Member who is currently transmitting in a Group Communication to a Selected MCX Service Group.

3.2  AbbreviationsWord‑p. 11

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
Mission Critical Services Common Requirements
Mission Critical Data
Mission Critical Push To Talk
Mission Critical Video
Mission Critical X, with X = PTT or X= Video or X= Data
MCX Service
Mission Critical Service

4  OverviewWord‑p. 11

4.1  Rationale for MCCoReWord‑p. 11

Further development of mission critical services beyond Mission Critical Push To Talk (MCPTT), such as Mission Critical Video (MCVideo) and Mission Critical Data (MCData), created an opportunity to re-use base functionality documented in the Stage 1 requirements for MCPTT. For example, the ability to communicate mission critical information to groups of users is a common need regardless of service type. Wherever originating MCPTT requirements were found to be in common with other mission critical services, those requirements were moved to this Technical Specification (TS 22.280). Each requirement that was moved has been voided in TS 22.179, and an informative annex has been created at the end of that specification documenting the location of the originating TS 22.179 requirement in the present document.

4.2  MCCoRe creation processWord‑p. 11

The creation of TS 22.280 followed a thorough analysis by mission critical application stakeholders of all the requirements in TS 22.179, TR 22.879, and TR 22.880. Each set of requirements was evaluated, requirement-by-requirement, to determine if any one requirement was applicable to another service (MCPTT, MCVideo, or MCData). If anyone requirement was shared between two or more services, it was designated as a Mission Critical Services Common Requirements (MCCoRe) requirement and placed into this technical specification. At the end of this specification, there are sets of normative annexes that enumerate each requirement in the present document that is applicable to the given scope for the annex. For instance, one annex covers MCPTT, and there is a comprehensive table that lists every requirement that follows in clauses 5 to 9 that are applicable to MCPTT.
In the present document the term, MCX Service, is used to mean any mission critical service and when applied in requirements it means any mission critical service that is identified in the normative annexes as applying to the requirement in question. When the term, MCX Service, is used multiple times in a single requirement it means the same MCX Service except in the case of the inter service interworking in clause 8. Therefore, other than requirements in the inter services interworking clause, all requirements in the present document are single service requirements.
In principle, a mission critical group could use multiple services. At any time during a mission critical group communication, a group of mission critical users can, subject to permissions and availability of services and capable UEs, start or stop using any one or more instantiation(s) of any of the MCX services. In the text of the specification for each individual service, the group is considered to use the services of that individual type, and consequently is called MCPTT Group, MCVideo Group, MCData Group, or generically, MCX Service Group. Referring to a group as an individual service group is for writing simple requirements purposes, and does not mean that the group cannot actively use other services. See subclause 8.4 for more information.
The grouping and consolidation of common requirements shared by multiple mission critical applications is not to be construed as a statement or requirement of architectural design, impacting entities and interfaces. It is for downstream working groups to determine whether they can:
  1. create generic MCX Service functionality that can be re-used by all Mission Critical Applications virtually unmodified;
  2. extend and/or customize common MCX Services, if they determine that a Mission Critical Application has special needs, or
  3. define separate support for Mission Critical Applications if they determine that they are so specialized that they cannot take advantage of a common MCX Service.

Up   Top   ToC