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

Glossary term · Services

MCData server

Mission Critical Data Server

Services →

MCData server is an MC service server instance providing the server application function for the MCData service to enable mission-critical data communication such as SDS, file distribution, and data streaming.

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

Description

The MCData server is a core functional entity within the 3GPP Mission Critical Services (MCX) architecture, specifically dedicated to the Mission Critical Data (MCData) service. It is defined in 3GPP TS 23.282 and TS 23.783 as an instance of an MC service server that provides the server application function for the MCData service. In essence, it acts as the central application-layer server that manages and orchestrates all MCData communications among authorized MCData UEs. The server is part of the broader MC service server framework, which includes the MCData server, the MC service server (common functions), and interfaces to the underlying 3GPP core network (e.g., EPS, 5GS) and to external application servers.

Architecturally, the MCData server sits above the 3GPP bearer network and relies on the common MC service server functions for user authentication, authorization, service discovery, and group management. It communicates with MCData UEs over the application plane using protocols such as HTTP, SIP, and MSRP, depending on the specific MCData capability being invoked. The server maintains state for ongoing data sessions, including file transfers, streaming sessions, and short data bursts. It also interfaces with the MC service server for group management and with the MC service server for configuration management to obtain service settings and user profiles. The MCData server may be deployed in a centralized or distributed manner, and it can be interconnected with other MCData servers across mission-critical networks to support inter-domain communications.

The primary functions of the MCData server include: handling short data service (SDS) messages, which can be either one-to-one or one-to-many; managing file distribution (FD) sessions, including file upload, download, and remote deletion; and controlling data streaming (DS) sessions for real-time video or telemetry. For SDS, the server receives messages from originating UEs, applies priority and security policies, and delivers them to target UEs, possibly using multicast or unicast delivery. For FD, the server coordinates the transfer of files among participants, ensuring reliability and integrity through mechanisms like chunking and retransmission. For DS, the server manages media streams, including session setup, modification, and teardown, and may interact with media servers for transcoding or mixing.

The MCData server also enforces mission-critical requirements such as priority handling, pre-emption, and quality of service (QoS) differentiation. It interacts with the policy and charging control (PCC) framework to request appropriate QoS for MCData traffic, ensuring that critical data gets preferential treatment during network congestion. Security is another key aspect: the server authenticates UEs, encrypts data in transit, and ensures that only authorized users can access specific MCData groups or services. It may also support lawful interception and logging for regulatory compliance.

In the overall network, the MCData server is essential for enabling mission-critical organizations (e.g., public safety, utilities, railways) to exchange data reliably and securely. It bridges the gap between the application-level requirements of these organizations and the underlying 3GPP network capabilities, providing a standardized, interoperable platform for data communication. Its evolution across 3GPP releases has focused on enhancing capabilities such as group management, interworking with other MC services (MCPTT, MCVideo), and integration with 5G features like network slicing and edge computing.

Purpose & Motivation

The MCData server exists to provide a standardized, reliable, and secure platform for mission-critical data communications over 3GPP networks. Before its introduction, mission-critical organizations often relied on proprietary or non-interoperable systems for data exchange, which lacked the robustness, priority handling, and security required for life-saving operations. The MCData server addresses these limitations by defining a common architecture that leverages 3GPP core network capabilities to deliver data services with guaranteed QoS, high availability, and strong security.

One of the key motivations for the MCData server is the need for interoperability among different vendors and networks. By adhering to 3GPP specifications, the server enables seamless communication between users from different agencies or countries, which is crucial for coordinated emergency response. Additionally, the server provides a centralized point for policy enforcement, ensuring that mission-critical data receives appropriate priority even during network congestion. This is achieved through integration with the PCC framework and the ability to request pre-emptive QoS.

The MCData server also simplifies the deployment and management of mission-critical data services. It abstracts the complexity of the underlying network from the applications, allowing organizations to focus on their operational needs rather than network intricacies. Furthermore, the server supports a range of data capabilities (SDS, FD, DS) within a single framework, reducing the need for multiple disparate systems. This convergence not only lowers costs but also improves operational efficiency and situational awareness for mission-critical users.

What changed in its specifications

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

TS 23.282Rel-18 → Rel-19

Adds ad hoc group data session leave, standalone data/FD, criteria modification procedures, and new information elements.

Full comparison in TS 23.282 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 4 changes
  • MCData server limits the number of simultaneous successful service authorisations TS 23.282CR0156
  • Media storage function in the MCData server TS 23.282CR0111
  • Remove the procedure in 7.5.2.9 File removal using HTTP by MCData server TS 23.282CR0151
  • Remove the duplicated MCData server URI in UE configuration table TS 23.282CR0152
Rel-19 1 change
  • Corrections to file availability request flow between Content and MCData server TS 23.282CR0333

Defining Specifications

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

SpecificationTitleRelease
TS 23.282 vk31 Mission Critical Data Architecture Rel-20 read
TR 23.783 vi00 Technical Report on Mission Critical Services over 5GS Rel-18 read