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

Glossary term · Services

IP Data

IP Data

Services →

IP Data is a structured or unstructured payload transparent to the MCData transport service, representing application-level data carried over MCData for mission-critical data communication involving public safety and other users.

Introduced
Rel-16
Where
Services › IMS
Specifications
2 specs
IP Data Description Purpose Neighbours Specifications

Description

In the context of Mission Critical Data (MCData) services defined by 3GPP, IP Data refers to the payload that is transported by the MCData service. MCData is a suite of specifications (TS 23.282) that enables mission-critical data communication, such as file transfers, messaging, and streaming, over LTE and 5G networks. IP Data is the actual content that the MCData transport service carries; it can be structured (e.g., formatted messages, files with metadata) or unstructured (e.g., raw byte streams). The key characteristic is that the MCData transport service is transparent to the IP Data, meaning it does not inspect or modify the payload; it simply delivers it from source to destination with the required quality of service (QoS).

The MCData architecture consists of several functional entities: the MCData Client (on the UE), the MCData Server (in the network), and the MCData transport service, which uses the underlying 3GPP network (e.g., EPS, 5GS) for connectivity. The MCData Server handles authentication, authorization, group management, and data distribution. When a client sends IP Data, it is encapsulated in MCData signalling messages (e.g., using HTTP, SIP, or MSRP) and transported to the MCData Server, which then forwards it to the intended recipients. The IP Data itself is opaque to the transport; the server does not need to understand its content, only its destination and QoS requirements.

IP Data can be used for various applications: text messaging, file sharing, location sharing, and telemetry. For example, a first responder might send a photo (structured IP Data) or a live video stream (unstructured IP Data) to a command center. The MCData service ensures that the data is delivered reliably and with appropriate priority, even under network congestion. The transparency of the transport allows applications to use any protocol (e.g., IP, UDP, TCP) and any data format, making MCData a flexible enabler for mission-critical applications.

The concept of IP Data was introduced in Rel-16 as part of the MCData specifications. It is defined in TS 23.282 (Functional architecture and information flows to support Mission Critical Data) and TS 23.783 (Mission Critical Data services). The definition emphasizes that the payload is transparent to the transport service, which means that the MCData service does not perform deep packet inspection or content adaptation. This separation of concerns allows the transport to focus on delivery guarantees (e.g., latency, reliability) while applications handle the data semantics.

In practice, IP Data is carried over MCData bearers that are established with specific QoS characteristics (e.g., QCI/5QI values for mission-critical data). The MCData Server may use different transport mechanisms depending on the type of data: for one-to-one messaging, it might use SIP MESSAGE; for group file distribution, it might use HTTP-based protocols. The IP Data itself is typically encrypted end-to-end by the application, ensuring confidentiality even if the transport is not trusted. The MCData service also supports data aggregation and fragmentation to handle large payloads efficiently.

Purpose & Motivation

The IP Data concept exists to clearly delineate the boundary between the application payload and the MCData transport service. In mission-critical communications, it is essential that the transport service can deliver data reliably and with low latency without being burdened by application-specific processing. By defining IP Data as transparent payload, 3GPP enables a modular architecture where the transport service can be optimized for delivery (e.g., using QoS, priority, and pre-emption) while applications can evolve independently. This separation also facilitates interoperability: different vendors can implement the transport and applications separately, as long as they adhere to the MCData specifications.

Historically, public safety communication systems (e.g., TETRA, P25) were vertically integrated, with proprietary data services. The introduction of LTE and 5G for public safety (via MCPTT, MCVideo, and MCData) aimed to leverage commercial broadband technology while meeting mission-critical requirements. MCData was developed to provide a standardized data service that could carry any IP-based application, from text messaging to real-time video. The IP Data definition ensures that the MCData service is future-proof: as new applications emerge, they can use the same transport without requiring changes to the network.

The transparency of IP Data also supports security and privacy. Since the transport does not inspect the payload, end-to-end encryption can be applied by the applications, and the network does not need to be trusted with the content. This is crucial for law enforcement and emergency services. Furthermore, the definition allows for both structured and unstructured data, accommodating a wide range of use cases, from simple text alerts to complex multimedia streams.

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-16 Initial

Initial definition introduced: IP Data is structured or unstructured payload that is transparent to the MCData transport service.

Definition carried over unchanged from Rel-16.

Definition carried over unchanged from Rel-17.

Definition carried over unchanged from Rel-18.

Definition carried over unchanged from Rel-19.

Defining Specifications

3GPP specifications that define or reference IP Data, 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