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

Glossary term · Services

Media Flow

Media Flow

Services →

Media Flow is a packet flow or set of flows carrying a single media instance, such as audio or video, within an IP multimedia session for transport in IMS and 5GS.

Introduced
Rel-7
Where
Services › IMS
Specifications
2 specs
Media Flow Description Purpose What changed Neighbours Specifications

Description

A media flow is a logical grouping of one or more packet flows that together transport a single media instance, such as an audio stream, video stream, or text, within an IP multimedia session. It is a key concept in the IP Multimedia Subsystem (IMS) and the 5G System (5GS) for describing media transport between endpoints. The term is defined in 3GPP TS 23.228 for IMS and TS 23.503 for policy control, and it is used by the Application Function (AF) to request QoS treatment for specific media.

In the IMS context, a media flow is defined as one or more IP flows carrying a single media instance. This includes both media plane information (e.g., RTP audio) and control signalling (e.g., RTCP or SIP). The media flow concept allows the network to apply appropriate QoS and policy control to each media component of a session. For example, an audio and a video stream in a video call would be two separate media flows, each potentially with different QoS requirements.

With the introduction of 5GS, the definition was updated to be more generic: 'one or more packet flows that are used for the transfer of a single media of a specific Media Type in an AF session.' This new definition covers not only IP-based flows but also non-IP packet flows, reflecting the broader capabilities of 5G. It also explicitly ties the media flow to an AF session and a Media Type as defined in TS 29.514. A media flow describes a service data flow from the perspective of the AF, meaning it is the AF's view of the traffic that should receive a certain QoS treatment.

The media flow concept is used in policy and charging control (PCC) to map application-level media descriptions to IP flows and then to QoS flows in 5G or bearers in 4G. The AF can provide media flow descriptions (e.g., IP addresses, port numbers, protocol) to the Policy Control Function (PCF), which then creates the appropriate PCC rules. In 5GS, these rules are enforced by the Session Management Function (SMF) and User Plane Function (UPF) to ensure the media gets the requested QoS.

Media flows are essential for enabling differentiated QoS for multimedia services. They allow the network to treat each media component according to its needs, such as low latency for voice or high throughput for video. They also enable charging based on media type and facilitate lawful interception and policy enforcement. The evolution from IP-only to generic packet flows ensures that the concept remains relevant as networks move towards all-IP and non-IP transports.

Purpose & Motivation

The media flow concept was created to provide a standardized way to describe and manage individual media components within a multimedia session. In early IMS deployments, it became clear that a single session could contain multiple media streams with different characteristics and QoS requirements. Without a common terminology, it was difficult for the network to apply the right policies and for applications to request appropriate resources.

Before the media flow definition, media was often described at the IP flow level, which was too granular and did not capture the application-level notion of a media instance. The media flow abstraction groups related IP flows (e.g., RTP and RTCP for a single audio stream) into a single logical unit. This simplifies policy control and QoS management because the network can treat the entire media component as one entity.

As networks evolved to 5G, the original IP-centric definition became limiting because 5G supports non-IP packet flows and a wider variety of media types. The Rel-19 update redefined media flow in terms of packet flows and Media Types, making it applicable to any type of media transport. This ensures that the concept can be used uniformly across IMS, 5GS, and future systems, supporting new services like immersive media and machine-type communications.

Thus, media flow solves the problem of mapping application media to network transport, enabling efficient QoS, policy, and charging control in a multi-media, multi-access environment.

What changed in its specifications

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

TS 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →
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

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

Initial definition introduced for IMS: 'One or more IP flows carrying a single media instance, e.g., an audio stream or a video stream.' It clarified that the term is used instead of IP Flow regardless of whether the packets are media or control signalling.

Definition carried over unchanged from Rel-7, maintaining the IP flow-based description.

Definition carried over unchanged from Rel-8, with no textual modifications.

Definition carried over unchanged from Rel-9, continuing the same IP-centric wording.

Definition carried over unchanged from Rel-10, with no textual modifications.

Definition carried over unchanged from Rel-11, maintaining the IP flow-based description.

Definition carried over unchanged from Rel-12, with no textual modifications.

Definition carried over unchanged from Rel-13, continuing the same IP-centric wording.

Definition carried over unchanged from Rel-14, with no textual modifications.

Definition carried over unchanged from Rel-15, maintaining the IP flow-based description.

Definition carried over unchanged from Rel-16, with no textual modifications.

Definition carried over unchanged from Rel-17, continuing the same IP-centric wording.

Wording changed significantly: redefined as 'One or more packet flows that are used for the transfer of a single media of a specific Media Type in an AF session.' The new definition replaces the IMS-specific one for 5GS, covers non-IP packet flows, and explicitly links to AF session and Media Type.

Definition carried over unchanged from Rel-19, maintaining the new packet flow-based and AF-centric description.

Defining Specifications

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

SpecificationTitleRelease
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 read