4 Overview

22.2803GPPMission Critical Services Common Requirements (MCCoRe)Release 19Stage 1TS

4.1 Rationale for MCCoRe

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 (3GPP TS 22.280). Each requirement that was moved has been voided in 3GPP TS 22.179, and an informative annex has been created at the end of that specification documenting the location of the originating 3GPP TS 22.179 requirement in the present document.

4.2 MCCoRe creation process

The creation of 3GPP TS 22.280 followed a thorough analysis by mission critical application stakeholders of all the requirements in 3GPP 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-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 sub-clause 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:

a) create generic MCX Service functionality that can be re-used by all Mission Critical Applications virtually unmodified;

b) extend and/or customize common MCX Services, if they determine that a Mission Critical Application has special needs, or

c) 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.