Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Mission Critical Organization

Mission Critical Organization

Services →

Mission Critical Organization is an end-user organization that includes MCX users and UEs, may include MCX service administrators, and can be organized hierarchically with delegated administrative control.

Introduced
Rel-13
Where
Services
Specifications
2 specs
Mission Critical Organization Description Purpose What changed Neighbours Specifications

Description

A Mission Critical Organization (MCO) is an end-user organization that uses Mission Critical Services (MCX) over 3GPP networks. It includes MCX Users and/or MCX User Equipment (UEs), and may also include MCX Service Administrators. The organization can be structured hierarchically, with administrative control delegated within the organization or to an outside entity. This concept is defined in 3GPP TS 22.179 (Mission Critical Push To Talk) and TS 22.280 (Mission Critical Services Common Requirements).

MCOs are fundamental to the deployment of mission-critical communication systems such as MCPTT (Mission Critical Push To Talk), MCVideo, and MCData. They represent the entities that own and manage the users and devices participating in these services. An MCO may be a public safety agency, a utility company, a transportation authority, or any organization requiring reliable, prioritized communications. The hierarchical structure allows for flexible administration, where a central authority can delegate management of sub-organizations to local administrators.

The MCO concept enables scalable and secure management of mission-critical users. Each MCO can have its own set of policies, groups, and roles. MCX Service Administrators within the organization are responsible for provisioning users, managing groups, and configuring service settings. The delegation of administrative control means that large organizations can distribute management tasks without compromising overall security or policy consistency.

In the 3GPP architecture, MCOs are identified and managed through the MCX service layer, which sits above the underlying 3GPP network. The MCO identity is used for authorization, billing, and policy enforcement. For example, when an MCX user initiates a group call, the network verifies that the user belongs to an authorized MCO and that the call is permitted according to the organization's policies. The MCO structure also supports interoperability between organizations, allowing coordinated responses during emergencies.

The term was introduced in Release 13 as 'MCPTT Organization' and was broadened in Release 14 to 'Mission Critical Organization' to cover all MCX services. This evolution reflects the expansion of mission-critical services beyond push-to-talk to include video and data. The definition has remained stable since Release 14, underscoring the maturity of the concept.

Purpose & Motivation

The Mission Critical Organization concept was created to provide a standardized way to model the organizational entities that use mission-critical services. Early mission-critical communications were often built on proprietary systems with limited interoperability. 3GPP's MCX standards aimed to leverage LTE and 5G networks to provide broadband mission-critical services, but this required a clear definition of the organizations that would use them.

By defining MCOs, 3GPP enables consistent management of users, groups, and policies across different vendors and networks. It allows for hierarchical administration, which is essential for large agencies with multiple departments or for mutual aid scenarios where control may be delegated. The concept also supports security and authorization, ensuring that only authorized users can access sensitive communications.

The introduction of MCOs in Release 13 and its expansion in Release 14 addressed the need for a common framework that could accommodate various mission-critical services. It provides a foundation for interoperability, allowing different organizations to communicate seamlessly during emergencies while maintaining their own administrative boundaries.

What changed in its specifications

The latest release-to-release comparison of specifications that define Mission Critical Organization. Each summary describes the whole specification, not only this term.

TS 22.179Rel-16 → Rel-17

Rel-17 added Mission Critical Push-to-talk Phase 3 to TS 22.179, covering general overview, Figure 6.15.3.1.1, and requirements. It also changed three other related items in the same release.

Full comparison in TS 22.179 →
TS 22.280Rel-18 → Rel-19

Rel-19 adds FRMCS Phase 5 changes to TS 22.280 Annexes A, B and C. It adds general requirements and removes or replaces several MCPTT, MCVideo and MCData requirements.

Full comparison in TS 22.280 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-13 Initial

Introduced as 'MCPTT Organization', defined as an end-user organization that includes MCPTT Users and/or UEs, and can include MCPTT Administrators, with hierarchical structure and delegated administrative control.

Wording changed to 'Mission Critical Organization', broadening the scope from MCPTT to all MCX services; the definition now refers to MCX Users, MCX UEs, and MCX Service Administrators.

Definition carried over unchanged from Release 14; no further modifications.

Definition carried over unchanged; the term continued to apply to MCX services.

Definition carried over unchanged; no technical or editorial changes.

Definition carried over unchanged; the concept remained stable.

Definition carried over unchanged; no modifications were made.

Definition carried over unchanged; the term persists as a foundational concept for mission-critical services.

Defining Specifications

3GPP specifications that define or reference Mission Critical Organization, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.179 vl00 MCPTT Service Requirements Rel-21 read
TS 22.280 vl00 Mission Critical Services Common Requirements Rel-21 read