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

Glossary term · Services

In-progress Emergency

In-progress Emergency (MCPTT Group Emergency State)

Services →

In-progress Emergency is an emergency condition for an MCPTT group that has been accepted by the MCPTT Service but not yet cancelled by an authorized user, governing priority treatment and resource allocation for mission-critical group communications.

Introduced
Rel-13
Where
Services
Specifications
2 specs
In-progress Emergency Description Purpose What changed Neighbours Specifications

Description

In-progress Emergency is a state defined in 3GPP's Mission Critical Push-To-Talk (MCPTT) specifications, TS 22.179 and TS 22.280. It denotes an emergency condition for a group that has been accepted by the MCPTT Service but has not yet been cancelled by an authorized user. Unlike a per-user emergency, this is a group-level state: once an authorized MCPTT user declares an emergency for a group, the group enters the in-progress emergency condition, and the MCPTT Service must treat communications for that group with elevated priority until an authorized user explicitly cancels it. The state is therefore persistent and requires an explicit cancellation action rather than timing out automatically.

The concept is central to mission-critical communications because emergency handling must be deterministic and robust. When a group is in the in-progress emergency state, the MCPTT Service applies priority treatment to the group's sessions: emergency calls and group communications receive preferential resource allocation, pre-emption of lower-priority traffic, and priority queuing. The MCPTT server (and underlying EPS/5GS via PCRF/PCF and PCF policy) enforces this through the Mission Critical Services (MCX) priority mechanisms, including the allocation and retention priority (ARP) and pre-emption capabilities of the underlying bearer. The group emergency state propagates to affiliated members so that all participants' devices and network resources are aligned.

Operationally, the lifecycle of the state is: an authorized user (e.g., a group leader or dispatcher) initiates an emergency for the group; the MCPTT server validates authorization, accepts the emergency, and marks the group as being in the in-progress emergency condition; the server then applies priority handling to the group's communications and notifies affiliated members. The state persists across sessions and participant changes until an authorized user cancels it. This explicit cancellation requirement is a deliberate design choice: emergencies in public safety cannot be allowed to silently expire, and the state must remain visible and controllable by authorized personnel.

The state interacts with the broader MCX priority framework. In-progress Emergency is one of several emergency-related states (alongside per-user emergency and imminent-peril conditions). It drives the MCPTT server's decisions on session admission, resource reservation, and pre-emption. It also interacts with the underlying 3GPP priority services: MCPTT uses the GCSE (Group Communication System Enablers) and MCVideo/MCData frameworks, and the emergency state maps to priority treatment in the EPS/5GS via the PCF/PCRF. The definition's careful wording — 'accepted by the MCPTT Service' and 'not yet been cancelled by an authorized user' — captures both the authorization gate and the persistence requirement.

For engineers, In-progress Emergency is important because it defines the group-level emergency semantics that must be implemented in MCPTT servers, clients, and the underlying policy functions. It affects how sessions are admitted, how resources are prioritized, and how emergency states are synchronized across the group. Understanding it is essential for designing mission-critical services where group-level emergencies must be handled reliably and with clear, auditable state transitions.

Purpose & Motivation

In-progress Emergency exists to give mission-critical group communications a well-defined, persistent emergency state. In public safety and mission-critical operations, an emergency declared for a group must be treated with elevated priority and must remain in force until explicitly cancelled by an authorized user. Without a standardized state, different implementations could handle group emergencies inconsistently — some timing out, some applying priority only to the declaring user, and some lacking any cancellation semantics. TS 22.179 and TS 22.280 define the state to ensure consistent, interoperable behaviour across MCPTT vendors and networks.

The concept solves the problem of group-level priority in a multi-user, multi-device environment. A per-user emergency is insufficient when an entire talkgroup must be prioritized: responders joining later must inherit the emergency treatment, and network resources must be reserved or pre-empted for the group as a whole. By defining the state as group-scoped and requiring explicit cancellation, the standard ensures that emergency priority is durable, visible, and controllable by authorized personnel.

Historically, the term was introduced in Rel-13 with the first MCPTT specifications and has been carried forward unchanged through Rel-20. Its stability reflects the maturity of the mission-critical priority framework and the importance of not changing emergency semantics once deployed in public safety networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define In-progress Emergency. 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

Initial definition introduced with the first MCPTT specifications: an emergency condition for a group accepted by the MCPTT Service but not yet cancelled by an authorized user.

Definition text carried over unchanged; MCPTT emergency handling continued to mature alongside MCVideo and MCData work.

Definition unchanged; the state remained part of the stable mission-critical priority framework.

Definition unchanged; carried forward as MCX services expanded.

Definition unchanged; the concept persisted through further mission-critical enhancements.

Definition unchanged; carried over into the 5G mission-critical context.

Definition unchanged; the term continued to apply as MCX evolved.

Definition unchanged; the state remains a stable reference concept in the latest release.

Defining Specifications

3GPP specifications that define or reference In-progress Emergency, 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