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

Glossary term · Services

MC server

Mission Critical Server

Services →

MC server is a unified logical entity that aggregates multiple mission critical service servers, including group, configuration, identity, key, location, and MC service servers, to collectively serve MC clients.

Introduced
Rel-18
Where
Services › IMS
Specifications
2 specs
MC server Description Purpose What changed Neighbours Detected Changes Specifications

Description

The MC server is a logical entity introduced in 3GPP Release 18 that aggregates a set of servers required to deliver mission critical services to MC clients. These constituent servers include the Group Management Server, Configuration Management Server, Identity Management Server, Key Management Server, Location Management Server, and the MC Service Server (which itself may be an MCPTT, MCVideo or MCData server). By grouping these functions under a single umbrella, the MC server simplifies the architecture and provides a clear point of reference for MC service delivery. The concept is specified in 3GPP TS 23.280 (Common functional architecture to support mission critical services) and discussed in TS 23.700 (Study on mission critical services).

Each constituent server has a specific role. The Group Management Server manages group definitions, memberships, and affiliations. The Configuration Management Server provides UE configuration data, such as service settings and parameters. The Identity Management Server handles user authentication and identity management. The Key Management Server is responsible for security key distribution and management. The Location Management Server provides location information for MC users. The MC Service Server implements the actual mission critical service logic (e.g., call control for MCPTT, video control for MCVideo, data control for MCData). Together, these servers enable an MC client to discover, join, and participate in mission critical services.

The MC server concept is primarily an architectural aggregation. It does not necessarily imply a single physical deployment, although in practice many deployments may co-locate these servers. The aggregation is useful for describing reference points and interfaces: the MC client interacts with the MC server as a whole, and the MC server internally routes requests to the appropriate constituent server. This abstraction simplifies the client-server interface and allows for flexible deployment options, including cloud-native and distributed implementations.

In the 3GPP architecture, the MC server communicates with the MC client over the network, using protocols such as HTTP, SIP, and others depending on the service. The MC server also interfaces with the 3GPP core network (e.g., via the EPS/5GS) to obtain bearer services, and with other functions like the Location Management Server for location data. The aggregation into an MC server does not change the individual server functionalities; rather, it provides a unified management and deployment view. This is particularly relevant for Release 18 and beyond, where mission critical services are increasingly integrated with 5G capabilities such as network slicing and edge computing.

The MC server is a key concept for interoperability and multi-vendor deployments. By standardizing the set of servers that constitute an MC server, 3GPP ensures that an MC client from one vendor can interact with an MC server from another vendor, as long as both conform to the specifications. The MC server also facilitates the introduction of new services: a new service can be added by including an additional server in the aggregation. The concept has been maintained in Releases 19 and 20, with the definition text remaining unchanged, indicating a stable architectural foundation for mission critical services.

Purpose & Motivation

The MC server was introduced to provide a clear, standardized aggregation of the various servers needed for mission critical services. Prior to Release 18, the architecture defined individual servers (group management, configuration management, etc.) but did not have a single term to refer to the collection. This made it cumbersome to describe deployments, interfaces, and conformance requirements. The MC server term solves this by providing a single logical entity that encompasses all the necessary server functions, simplifying architecture descriptions and procurement.

The motivation also stems from the need for scalability and flexibility. As mission critical services evolve, new servers may be added (e.g., for new services or features). The MC server concept allows the architecture to evolve by simply adding a new constituent server without redefining the overall client-server model. This is particularly important in the context of 5G, where mission critical services are expected to leverage network slicing, edge computing, and other advanced capabilities. The MC server can be deployed as a set of microservices, and the aggregation term helps in describing such deployments.

Historically, mission critical services were defined in Releases 13-17 with separate specifications for each server. The Release 18 introduction of the MC server term reflects a maturation of the architecture, providing a unified view. It also aligns with the industry trend towards cloud-native, service-based architectures where multiple functions are aggregated into a single logical entity. The MC server concept is expected to remain stable in Releases 19 and 20, serving as the foundation for future mission critical service enhancements.

What changed in its specifications

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

TS 23.280Rel-18 → Rel-19

Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.

Full comparison in TS 23.280 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-18, normative work from Rel-19.

Rel-19 1 change

Defining Specifications

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

SpecificationTitleRelease
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read