ETSI TS 126 506 V18.6.0 (2025-10)

5G; 5G Real-time Media Communication Architecture (Stage 2) (3GPP TS 26.506 version 18.6.0 Release 18)

RTS/TSGS-0426506vi60

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 4 - Codec
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 10-Oct-2025

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G Real-time Media Communication Architecture (Stage 2)
(3GPP TS 26.506 version 18.6.0 Release 18)

3GPP TS 26.506 version 18.6.0 Release 18 1 ETSI TS 126 506 V18.6.0 (2025-10)

Reference
RTS/TSGS-0426506vi60
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2025.
All rights reserved.
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 2 ETSI TS 126 506 V18.6.0 (2025-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 3 ETSI TS 126 506 V18.6.0 (2025-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 6
1 Scope . 7
2 References . 7
3 Definitions of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Real-Time media Communication Architecture . 9
4.1 Overall architecture for Real-Time media Communication (RTC) . 9
4.1.1 Definition of RTC architecture . 9
4.1.2 Generalized Media Delivery architecture . 11
4.1.2.1 Generalized Media Delivery in the 5G System . 11
4.1.2.2 Reference architecture for Media Delivery . 12
4.1.2.3 Network Functions and UE entities . 12
4.1.2.4 Reference points . 13
4.1.2.5 Interfaces and APIs . 14
4.1.2.5.1 Interfaces and APIs supporting media session handling . 14
4.1.2.5.2 Interfaces and APIs supporting media transport . 14
4.1.2.5.3 Interfaces and APIs supporting application functionality . 15
4.2 Functions and entities . 15
4.2.1 General . 15
4.2.2 Provisioning Function . 15
4.2.3 Configuration Function . 15
4.2.4 RTC Media Session Handler (MSH) . 15
4.2.5 Network Support Function . 16
4.2.6 ICE Function . 16
4.2.7 WebRTC Signalling Function. 16
4.2.8 Interworking Function . 16
4.2.9 Transport Gateway Function. 17
4.2.10 Media Function . 17
4.2.11 Application-supporting Web Function. 17
4.2.12 RTC Access Function . 17
4.3 Interfaces . 18
4.3.1 RTC-1: Provisioning interface . 18
4.3.2 RTC-3: RTC AS to RTC AF interface. 18
4.3.3 RTC-4: Media-centric transport interface via RTC AS . 18
4.3.4 RTC-5: Transport control interface. 19
4.3.5 RTC-6: Client API . 19
4.3.6 RTC-7: Client interface . 19
4.3.7 RTC-8: Application interface . 19
4.3.7A RTC-10: RTC AS to another RTC AS interface . 20
4.3.8 RTC-11: RTC Client configuration APIs . 20
4.3.9 RTC-12: Peer-to-peer media-centric transport interface . 20
4.4 RTC Architecture extension . 20
4.4.1 Introduction. 20
4.4.2 Extended RTC architecture for Edge Computing . 20
4.4.2.1 General . 20
4.4.2.2 Edge Application Server (EAS) . 21
4.4.2.3 Edge Interfaces . 22
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 4 ETSI TS 126 506 V18.6.0 (2025-10)
4.5 QoE metrics reporting for RTC . 22
4.6 Media consumption reporting for RTC . 23
4.7 Dynamic Policies for RTC . 24
4.7.1 General . 24
4.7.2 PDU Set-based QoS handling . 25
4.7.2.1 General . 25
4.7.2.2 N6-unmarked PDUs . 25
4.7.3 Dynamically changing traffic characteristics . 25
4.7.3.1 Downlink data bursts. 25
4.7.3.1.1 General . 25
4.7.3.1.2 End of data burst . 25
5 Procedures for basic RTC architecture . 26
5.1 General . 26
5.2 Common Procedure . 26
5.2.1 Provisioning . 26
5.2.2 Configuration . 26
5.2.3 Metrics reporting . 27
5.2.3.1 Metrics reporting by RTC Access Function . 27
5.2.3.2 Metrics reporting by RTC AS . 28
5.2.4 Consumption reporting . 30
5.2.4.1 Consumption reporting by RTC Access Function. 30
5.2.4.2 Consumption reporting by RTC AS . 31
5.3 Call flow for over-the-top (OTT) RTC sessions (CS#1) . 32
5.4 Call flow for Network-supported RTC sessions (CS#2) . 34
5.5 Call flow for MNO-facilitated RTC sessions (CS#3) . 36
6 Procedures for Edge Processing . 40
6.1 Client-driven management of RTC edge processing . 40
6.2 AF-driven management of RTC edge processing . 43
7 Media plane extensions for RTC . 44
7.1 Overview . 44
7.2 Application-specific PDU handling. 44
7.2.1 Overview . 44
7.2.2 Signalling of PDU Sets . 44
7.2.3 Signalling of dynamically changing traffic characteristics . 44
Annex A (normative): Architecture variants for collaboration scenarios . 45
A.1 General . 45
A.2 Collaboration scenario 1 . 46
A.3 Collaboration scenario 2 . 47
A.4 Collaboration scenario 3 . 48
A.5 Collaboration scenario 4 . 48
Annex B (normative): Architecture variants for RTC Application . 49
B.1 General . 49
B.2 RTC Application is a Native WebRTC App . 49
B.3 RTC architecture for Web App . 50
Annex C (informative): Change history . 52
History . 53

ETSI
3GPP TS 26.506 version 18.6.0 Release 18 5 ETSI TS 126 506 V18.6.0 (2025-10)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 6 ETSI TS 126 506 V18.6.0 (2025-10)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
Introduction
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 7 ETSI TS 126 506 V18.6.0 (2025-10)
1 Scope
The present document specifies an architecture for real-time media communication integrated into the 5G System. To
support Mobile Network Operator (MNO) and third-party services for real-time media, essential functionalities and
interfaces are specified. The primary scope of this Technical Specification is the documentation of the following
aspects:
- The definition of a real-time media communication architecture mapped to the 5GS architecture, with relevant
core building blocks, reference point, and interfaces to support modern operator and third-party media services,
based on the 5GMS architecture.
- Definition of all relevant reference points and interfaces to support different collaboration scenarios between 5G
System operator and third-party media communication service provider, including but not limited to an
Augmented Reality (AR) media communication service provider.
- Call flows and procedures for different real-time communication service types.
- Specification to support functionalities relevant to AR such as split-rendering or spatial computing on top of a
5G System based on this architecture.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TR 26.998: "Support of 5G glass-type Augmented Reality / Mixed Reality (AR/MR)
devices".
[3] 3GPP TS 26.119: "Media Capabilities for Augmented Reality".
[4] 3GPP TS 26.113: "Enabler for Immersive Real-time Communication".
[5] 3GPP TR 26.930: "Study on the enhancement for Immersive Real-Time communication for
WebRTC".
[6] 3GPP TS 26.501: "5G Media Streaming (5GMS); General description and architecture".
[7] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
[8] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[9] 3GPP TS 36.321: "LTE; Medium Access Control (MAC) protocol specification".
[10] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and
interaction".
[11] 3GPP TS 23.501: " System architecture for the 5G System (5GS)".
[12] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[13] IETF RFC 8825: "Overview: Real-Time Protocols for Browser-Based Applications".
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 8 ETSI TS 126 506 V18.6.0 (2025-10)
3 Definitions of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term
defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Application Data Unit: a unit of information generated by an application, such as a video frame or slice, that is
handled together by the application
RTC Application: a Native WebRTC Application or a Web App that is compliant with the profile of a WebRTC-based
application defined in the present document
RTC endpoint: an entity that is capable of participating in an RTC session and exchanging real-time media and data by
incorporating an instance of the WebRTC Framework
NOTE: A UE incorporating an RTC Client (including an RTC Access Function) as well as an RTC Application is
an RTC endpoint. An RTC AS is an RTC endpoint by virtue of containing a Media Function and a
WebRTC Signalling Function.
RTC Client: a UE function comprising an RTC Access Function and an RTC Media Session Handler which interacts
with functions in the network and UE applications
RTC Access Function: a set of functions including an instance of the WebRTC Framework which exchanges real-time
media with one or more RTC endpoints via reference point RTC-4m or RTC-12, and which exchanges signalling
messages with WebRTC Signalling Function via reference point RTC-4s, and which exposes client APIs defined in the
present document to the RTC Application at reference point RTC-7 and to the RTC Media Session Handler at reference
point RTC-11
WebRTC Framework: a well-defined subset of the WebRTC protocol stack for data transport and data framing that
supports real-time media communication between an RTC endpoint and its peer(s) within the scope of an RTC session
3.2 Symbols
For the purposes of the present document, the following symbols apply:
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
ADU Application Data Unit
AR Augmented Reality
CDRx Connected mode Discontinuous Reception
EAS Edge Application Server
ECS Edge Configuration Server
EEC Edge Enabler Client
EES Edge Enabler Server
IETF Internet Engineering Task Force
ICE Interactive Connectivity Establishment
IMS IP Multimedia Subsystem
MCU Multi-point Control Unit
MNO Mobile Network Operator
MR Mixed Reality
MSH Media Session Handler
MTSI Multimedia Telephony Service for IMS
NAT Network Address Translation
PDU Protocol Data Unit
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 9 ETSI TS 126 506 V18.6.0 (2025-10)
PSI PDU Set Importance
QoS Quality of Service
RTC Real-Time media Communication
RTT Round-Trip Time
SDP Session Description Protocol
SFU Selective Forwarding Unit
STUN Session Traversal Utilities for NAT
TURN Traversal Using Relays around NAT
W3C World Wide Web Consortium
WebRTC Web Real-Time Communication
XR eXtended Reality
4 Real-Time media Communication Architecture
4.1 Overall architecture for Real-Time media Communication
(RTC)
4.1.1 Definition of RTC architecture
Real-Time media Communication (RTC) over 5G system in the context of this specification is defined as the delivery
of delay-sensitive media from one peer to another with support of 5G network. AR conversational service described in
TR 26.998 [2] is a typical use cases for RTC, which enables end-users to directly communicate real-time media
including AR/MR media content as specified in TS 26.119 [3]. As identified in clause 8.4 of TR 26.998, there may be
different options to enable such AR conversational service, for example re-use of parts of MTSI as defined in
TS 26.114 [10] such as the IMS data channel or 5G Media Streaming for managed services.
The overall RTC architecture is shown in figure 4.1.1-1 below.
RTC
NEF
Application
RTC Application
5GS Provider
SMF
N33
N7
External
N5
PCF RTC AF RTC-1
External DN
UE
Trusted DN
RTC Client RTC AS
N6
Uu
RAN N3 UPF
NOTE: The functions indicated by the yellow filled boxes are in scope of the present document for RTC. The functions
indicated by the grey boxes are defined in 5G System specifications. The functions indicated by the blue
boxes are neither in scope of 5G RTC nor 5G System specifications.

Figure 4.1.1-1: Real-time media communication (RTC) in 5G System
The media data is exchanged between two or more RTC endpoints over a 5G System as defined in TS 23.501 [11 An
RTC endpoint incorporates an instance of the WebRTC Framework configured by the RTC System defined in the
present document. An RTC endpoint is typically realised by a UE, but an RTC AS, possibly deployed as an edge
computing server as defined in clause 4.4.2, may also play the role of RTC endpoint. The Application Provider provides
an RTC Application on the UE to make use of RTC endpoint and network functions using interfaces and APIs. The
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 10 ETSI TS 126 506 V18.6.0 (2025-10)
RTC architecture defines the functions and entities to support WebRTC-based service over the 5G System. Two main
functions are defined in the Trusted DN.
- RTC AF: An Application Function as defined in TS 26.501 [6] dedicated to real-time media communication.
- RTC AS: An Application Server dedicated to real-time media communication.
NOTE: If both the RTC AF and RTC AS are deployed in an external DN, this is out of scope of the present
document.
The detailed RTC architecture mapping to the overall high-level architecture in figure 4.1.1-1 is shown in figure 4.1.1-2
below.
RTC-8
PCF
UE
RTC AF
NEF
RTC Application Network
RTC-1
Support Configuration Provisioning
SMF
Function Function Function
(NS-AF)
RTC-6
RTC RTC-5
Media
RTC-7
RTC
RTC-3
Session
(W3C JS
Application
Handler
API)
RTC AS Provider
RTC-11
WebRTC Application- Transport
Signalling supporting Gateway
RTC Access Function
Function Web Function Function
RTC-4
Media
WebRTC Framework
RTC-12
ICE Function Interworking
Function WebRTC Function RTC-10
Framework
RTC Client
Exposed API
RTC scope
RTC 5GS External
5GS scope
Out of scope
NOTE 1: Some subfunctions may not be required depending on the collaboration scenario. Description of
collaboration scenario and its architecture variant are specified in annex A.
NOTE 2: Void.
NOTE 3: Red ovals indicate API provider functions.
NOTE 4: The RTC Access Function may be realised by a web browser in deployments of the RTC Client that
support Web App through the W3C defined JavaScript APIs including WebRTC API.

Figure 4.1.1-2: RTC General Architecture
The WebRTC Signalling Function may be co-located with the RTC AF. In such deployments, the WebRTC Signalling
Function acts as an RTC AF with access to the 5G Core, and some of the RTC AF interactions with the WebRTC
Signalling Function may be replaced to avoid concurrent/redundant requests from the RTC endpoint in the UE.
Specifically, media session handling interactions between the RTC AF and the UE at reference point RTC-5 may be
replaced by the equivalent WebRTC signalling interactions defined at reference point RTC-4.
The subfunctions inside the RTC AF, RTC AS and the RTC Client are defined in clause 4.2 and the reference points
shown in figure 4.1.1-2 are defined in clause 4.3.
Two types of RTC Application are defined in the present document:
- Native WebRTC App: An RTC Application running on the UE that makes use of client APIs at reference points
RTC-6 and RTC-7.
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 11 ETSI TS 126 506 V18.6.0 (2025-10)
- Web App: A web application running in a web browser on the UE that makes use of the W3C-defined WebRTC
APIs.
NOTE: Detailed deployment architecture for the Native WebRTC App and the Web App are described in annex B.
4.1.2 Generalized Media Delivery architecture
4.1.2.1 Generalized Media Delivery in the 5G System
This clause and subsequent subclauses of clause 4.1.2 define a generalized Media Delivery architecture of which the
architecture for Real-Time Communication (RTC) defined elsewhere in the present document is one possible
realisation. In case of any misalignment between the two, the RTC architecture has precedence over this generalised
architecture.
Due to the similarity of the 5GMS architecture (as defined in TS 26.501 [6]) to the architecture for Real-Time media
Communication (RTC) defined in the present document, the RTC functions and 5GMS functions may share or may
make use of many common functionalities for both media session handling and media delivery. A generalized Media
Delivery architecture that integrates 5GMS and RTC functionality in the 5G System is defined in figure 4.1.2.1-1.
NOTE: Full integration of 5GMS and RTC is not addressed in the present document.
5G
Media Application
Media
External
System
Provider
Media-aware
Application
N33
NEF
Media AF
N33
N5
PCF Media AF
UE
External DN
Trusted DN
Media
Media AS
N6
Client
Media AS
Uu RAN N3 UPF
N6
Figure 4.1.2.1-1: Generalized Media Delivery architecture within the 5G System
In this representation:
- The Media Application Provider plays the role of the RTC Application Provider.
- The Media-aware Application plays the role of the Native WebRTC App.
- The RTC AF is one possible realisation of the general Media AF.
- The RTC AS is one possible realisation of the general Media AS.
- The RTC Client is part of the general Media Client.
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 12 ETSI TS 126 506 V18.6.0 (2025-10)
4.1.2.2 Reference architecture for Media Delivery
A functional description with additional details as well as reference points is provided below, as illustrated in
figure 4.1.2.2-1.
M8
Media-aware
Application
NEF N33
Nnef_AFSessionWithQoS
M6 Nnef_ChargeableParty
Npcf_PolicyAuthorization
Nnef_BDTPNegotiation
N30
Npcf_BDTPolicyControl
Maf_Provisioning
Media
M1
Media Session Handling Client API
PCF N5 AF
M7 Npcf_PolicyAuthorization
Npcf_BDTPolicyControl
Media Media
M9
Application
Session M5
Maf_SessionHandling
Provider
Handler
Maf_?
Media Session Handling Client API Maf_SessionHandling
M3
M11
Media Access Client API
Mas_Configuration
M12 M10
Media
Media Access
AS
Function M4 M2
Media Delivery scope
Media Client UPF
5GS scope
UE Exposed API DN
Out of scope
Media 5GS External
NOTE 1: Exposed APIs are named in italics.
NOTE 2: If the Media Client is deployed as a monolithic functional block, it may choose not to expose interfaces
externally at reference point M11.

Figure 4.1.2.2-1: Generalized Media Delivery architecture
4.1.2.3 Network Functions and UE entities
Functional definitions may be generalized as follows:
- Media AF: An Application Function as defined in clause 6.2.10 of TS 23.501 [11] dedicated to Media Delivery.
- Media AS: An Application Server dedicated to Media Delivery.
- Media Client: A UE internal function dedicated to Media Delivery comprising:
- Media Session Handler: An entity on the UE that communicates with the Media AF in order to establish,
control and support the delivery of a media session.
- Media Access Function: An entity on the UE that communicates with the Media AS in order to access and
deliver media content. The media access function for example may be further sub-divided into content
delivery protocols, codecs, media types and metadata representation.
- Media-aware Application: An application entity on the UE that makes use of 3GPP-defined APIs to invoke the
Media Session Handler and/or the Media Access Function in order to support Media Delivery.
NOTE: An application (e.g., a web browser application) that does not invoke either the Media Session Handler or
the Media Access Function using 3GPP-defined APIs is not considered a Media-aware Application and is
not mapped into the generalized Media Delivery reference architecture.
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 13 ETSI TS 126 506 V18.6.0 (2025-10)
Table 4.1.2.3-1: Mapping of RTC functions to generalized Media Delivery architecture
Generalized media RTC function
architecture function
Media AF RTC AF
Media AS RTC AS
Media Client RTC Client
Media Session Handler RTC Media Session Handler
Media Access Function RTC Access Function
Media Application Provider RTC Application Provider
Media-aware Application Native WebRTC App

4.1.2.4 Reference points
The following reference points are defined for Media Delivery:
M1: Reference point between the Media Application Provider and the Media AF for the provisioning of
Media Delivery.
M2: Reference point between the Media Application Provider and the Media AS for the purposes of
ingesting media into the Media AS or egesting media from the Media AS.
NOTE 1: Reference point M2 is not defined by the RTC architecture in this release.
M3: Reference point between the Media AF and the Media AS for the purposes of Media AS
configuration and/or for media session handling in relation to Media Delivery.
NOTE 2: Reference point M3 is defined by the RTC architecture in this release but specification is for future study.
M4: Reference point between the Media AS and the Media Access Function in the UE for the purpose
of downlink transport of media from the Media AS to the Media Access Function ("content
distribution") or uplink transport of media from the Media Access Function to the Media AS
("content contribution").
NOTE 3: Session setup signalling at reference point RTC-4 lies outside the scope of reference point M4.
M5: Reference point between the Media AF and the Media Session Handler in the Media Client for the
purpose of media session handling in relation to Media Delivery.
M6: Reference point between the Media-aware Application and the Media Session Handler for the
purpose of configuring the Media Session Handler.
M7: Reference point between the Media-aware Application and the Media Access Function for the
purpose of media access control.
M8: Reference point between the Media-aware Application and the Media Application Provider.
NOTE 4: Reference point M8 is private and therefore beyond the scope of standardisation.
M9: Reference point between one instance of the Media AF and another for the purpose of Media AF
instance chaining.
NOTE 5: Reference point M9 is not defined by the RTC architecture in this release.
M10: Reference point between one instance of the Media AS and another for the purpose of distributed
service chaining over multiple Media AS instances.
NOTE 6: Reference point M10 is defined by the RTC architecture but is not further specified in this release.
M11: Reference point between the Media Session Handler and the Media Access Function (both in the
Media Client) for the purpose of configuring the Media Session Handler and/or media access
control.
ETSI
3GPP TS 26.506 version 18.6.0 Release 18 14 ETSI TS 126 506 V18.6.0 (2025-10)
M12: Reference point between one RTC Access Function in a UE and another for the purpose of peer-
to-peer media transport between different Media Clients when this is permitted by the 5G System.
Table 4.1.2.4-1: Mapping of RTC reference points to generalized Media Delivery architecture
Generalized Media Delivery RTC
architecture reference point reference point
M1 RTC-1
M2 Not defined
M3 RTC-3
M4 RTC-4
M5 RTC-5
M6 RTC-6
M7 RTC-7
M8 RTC-8
M9 Not defined
M10 RTC-10
M11 RTC-11
M12 RTC-12
4.1.2.5 Interfaces and APIs
4.1.2.5.1 Interfaces and APIs supporting media session handling
The Media AF exposes the following network service interfaces for media session handling:
- Provisioning API (Maf_Provisioning): External API, exposed to the Media Application Provider by the
Media AF at reference point M1 to provision the usage of the Media Delivery and to obtain feedback.
- Media Session Handling API (Maf_SessionHandling) exposed by a Media AF to the Media Session Handler at
reference point M5 and/or to the Media AS at reference point M3 for media session handling, control, reporting
and assistance that also include appropriate security mechanisms, e.g. authorization and authentication.
The Media Session Handler exposes the following UE APIs for media sessi
...