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

Glossary term · Services

Multi-modal service

Multi-modal service

Services →

Multi-modal service is a communication service composed of several interrelated data flows subject to application coordination, potentially carrying different media types, including audio, video, positioning, or haptic, from one or multiple user equipment or devices.

Introduced
Rel-18
Where
Core Network › 5G Core
Specifications
2 specs
Multi-modal service Description Purpose What changed Neighbours Detected Changes Specifications

Description

A multi-modal service is a 5GS communication service that consists of several data flows which relate to each other and are subject to application coordination. Unlike a conventional single-flow service, the constituent flows of a multi-modal service are logically coupled: the application layer coordinates them so that, for example, an audio stream, a video stream, and a haptic feedback stream are delivered in a synchronized and mutually dependent manner. The data flows may transfer different types of data — audio, video, positioning information, haptic data, and others — and may originate from different sources. A source can be a single UE, a single device, multiple devices connected to a single UE (such as wearables or sensors tethered to a smartphone), or multiple UEs altogether.

From an architecture standpoint, the multi-modal service concept is defined primarily in the policy and service-level specifications (23.503 for policy and charging control, 24.543 for the related protocol aspects). The service is realized by grouping multiple media or data flows into a coordinated service context that the network can treat with common policy, QoS, and charging treatment where appropriate, while still allowing per-flow differentiation. The application function (AF) plays a central role: it describes the service to the PCF via service information, indicating the relationships between flows, their individual QoS requirements, and the coordination constraints that must be respected. The PCF then derives PCC rules that map these flows onto appropriate QoS flows within PDU sessions.

Because the flows may come from multiple devices or UEs, the network must be able to correlate them. This correlation is achieved through application-level identifiers and service-level parameters exchanged between the AF, the PCF, and the SMF. The SMF binds the QoS flows to the correct PDU sessions, which may belong to different UEs, and enforces the corresponding QoS treatment. The coordination itself — the timing and semantic relationship between flows — remains an application responsibility; the network provides the transport and policy framework that makes such coordination feasible, for example by ensuring that the flows receive consistent QoS and are established or modified together.

Typical use cases include extended reality (XR) and immersive services, where video, audio, and haptic or positioning data must be delivered together; teleoperation and remote control, where control commands, video feedback, and sensor data form a coordinated set; and multi-device experiences such as those involving a primary device plus wearables. In these scenarios, treating each flow independently would lead to inconsistent QoS, misaligned charging, and poor user experience. The multi-modal service abstraction allows the network to understand the service as a whole while still applying flow-specific handling.

The concept was introduced in Release 18 as part of the broader work on immersive and media-rich services, and it is carried forward unchanged in Releases 19 and 20, indicating a stable definition that continues to underpin policy and protocol work for coordinated multi-flow services.

Purpose & Motivation

As 5G services evolved toward immersive and interactive experiences, applications increasingly relied on multiple simultaneous data flows of different media types that must be delivered in a coordinated way. Previous service models treated each data flow largely in isolation, which made it difficult for the network to apply consistent policy, QoS, and charging across a set of related flows, especially when those flows originated from different devices or UEs. The multi-modal service concept was created to give the network a first-class abstraction for such coordinated flow sets.

The motivation is both technical and commercial. Technically, flows belonging to one application experience need consistent treatment: if the video component of an XR session receives premium QoS while the haptic or audio component is degraded, the overall experience suffers. Commercially, operators need to charge and police such services coherently rather than flow-by-flow. By defining the multi-modal service in the policy architecture (23.503) and its protocol support (24.543), 3GPP enables the AF to describe the service structure to the network and lets the PCF and SMF enforce coordinated treatment.

The concept also addresses the growing reality of multi-device setups, where a single user experience spans a phone, wearables, and other tethered devices. Prior approaches had no standard way to express that these flows belong together. The Release 18 definition provides that common vocabulary, and its unchanged retention through Releases 19 and 20 reflects its role as a stable foundation for further immersive-service work.

What changed in its specifications

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

TS 23.503Rel-18 → Rel-19

Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.

Full comparison in TS 23.503 →

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
  • Clarification on multi-modal service TS 23.503CR1452

Defining Specifications

3GPP specifications that define or reference Multi-modal service, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 read
TS 24.543 vk10 SEAL Data Delivery Management Protocol Rel-20 read