Skip to main content
Real-time Media Communication (RTC)

Architecture

TS 26.506 specifies an architecture for real-time media communication integrated into the 5G System: the functions involved, the reference points between them, and the collaboration scenarios between the 5G System operator and third-party providers. The media data is exchanged between two or more RTC endpoints over the 5G System.

At a glance
  • Network side: an RTC AF (provisioning, configuration, network support) and an RTC AS (ICE, signalling, media and interworking functions).
  • UE side: an RTC Client with a Media Session Handler and an Access Function, used by native or web apps.
  • Shared with 5GMS: RTC is one realisation of a generalised Media Delivery architecture, with M1 to M13 as the generalised reference points.

Functions​

General architecture
RTC General ArchitectureRedrawn from TS 26.506 V20.0.0, figure 4.1.1-2
In the 5G System
Real-time media communication (RTC) in 5G SystemRedrawn from TS 26.506 V20.0.0, figure 4.1.1-1

Click a figure to enlarge it. The RTC functions are shown in light blue; circles mark exposed APIs.

FunctionInRole
Provisioning FunctionRTC AFLets an RTC Application Provider provision QoS, charging, consumption and QoE metrics collection, ICE (STUN and TURN) and the WebRTC Signalling Function (TS 26.506 V20.0.0 clause 4.2.2).
Configuration FunctionRTC AFStores WebRTC-related configuration information and makes it accessible to the UE (TS 26.506 V20.0.0 clause 4.2.3).
Network Support FunctionRTC AFRequests the network to allocate QoS for a starting or modified session. Shown as NS-AF in the figures (TS 26.506 V20.0.0 clauses 4.2.5, 5.5).
ICE FunctionRTC ASSTUN and TURN services that facilitate NAT and firewall traversal. When provided by the operator, they may assist with the 5G integration of RTC Applications (TS 26.506 V20.0.0 clause 4.2.6).
WebRTC Signalling FunctionRTC ASHandles the offer/answer exchange, with access to the SDP in both directions. It may be co-located with the RTC AF, in which case it acts as an RTC AF with access to the 5G Core (TS 26.506 V20.0.0 clauses 4.2.7, 4.1.1).
Media FunctionRTC ASAn RTC endpoint incorporating a WebRTC Framework, used for example as a content server, for media processing, scene composition, or as an MCU or SFU (TS 26.506 V20.0.0 clause 4.2.10).
Application-supporting Web FunctionRTC ASA web server offering a service entry point, authorisation and authentication, file sharing, or conference scheduling (TS 26.506 V20.0.0 clause 4.2.11).
Transport Gateway FunctionRTC ASSupports cross-operator RTC sessions (TS 26.506 V20.0.0 clause 4.2.9).
Interworking FunctionRTC ASEnables operator-facilitated RTC sessions with endpoints across different operators (TS 26.506 V20.0.0 clause 4.2.8).
RTC Media Session HandlerRTC ClientRuns on the UE and assists with the integration of the RTC Application: it communicates with the RTC AF at RTC-5 (TS 26.506 V20.0.0 clauses 4.2.4, 4.3.4).
RTC Access FunctionRTC ClientSends and receives media at RTC-4m and RTC-12, relays signalling from RTC-7 to RTC-4s, and offers client APIs at RTC-7 and RTC-11 (TS 26.506 V20.0.0 clauses 3.1, 4.2.12).

If both the RTC AF and the RTC AS are deployed in an external DN, this is out of scope of TS 26.506.

Reference points​

Reference pointBetweenPurposeStage 3
RTC-1RTC Application Provider and RTC AFProvisioning support for the RTC sessions the provider offersTS 26.113, clause 6
RTC-2Not named in TS 26.506Not specified in this release
RTC-3RTC AS and RTC AFInformation about the RTC sessionAn RTC AS may use some of the TS 26.510 media session handling APIs; the specification of RTC-3 is for future study (TS 26.506 V20.0.0 clauses 4.3.2, 4.1.2.4 NOTE 2; TS 26.113 V19.2.0 clause 8, clause 10.1 table 10.1-1, annex B.3 NOTE)
RTC-4sRTC Access Function and RTC AS (e.g. WebRTC Signalling Function)SignallingTS 26.113, clause 13.2
RTC-4mRTC Access Function and RTC ASMedia and related data, when at least one RTC endpoint of the session is in the RTC AS; also between UEs where peer-to-peer communication is not permittedTS 26.113, clauses 9 and 13
RTC-5RTC Media Session Handler and RTC AFConfiguration information to the Media Session Handler, and requests for media session handling supportTS 26.113, clause 10
RTC-6RTC Application and RTC Media Session HandlerMedia session handling functions offered on request, or transparently without the applicationTS 26.113, clause 11
RTC-7RTC Application and RTC Access FunctionThe client API for a Native WebRTC App, or the W3C JavaScript APIs including the WebRTC API for a Web AppTS 26.113, clause 12
RTC-8RTC Application and RTC Application ProviderProprietary exchange of configuration informationOut of scope (TS 26.506 V20.0.0 clauses 4.3.7, 4.1.2.4 NOTE 4)
RTC-10RTC AS and RTC ASDistributed service chaining over multiple RTC AS instancesDefined, not further specified in this release (TS 26.506 V20.0.0 clauses 4.3.7A, 4.1.2.4 NOTE 6)
RTC-11RTC Access Function and RTC Media Session HandlerInside the RTC Client; may be an internal API rather than one exposed to application developersTS 26.113, clauses 11 and 12
RTC-12RTC Access Function and RTC Access FunctionPeer-to-peer communication between UEs, where permitted by the 5G System. Its protocols are a subset of those at RTC-4m.TS 26.113, clause 9.2

Collaboration scenarios​

The four collaboration scenarios are defined by which functions are in the operator's trusted domain. TS 26.506 draws a derivative architecture for scenarios 1 to 3, and gives a call flow for each.

ScenarioDescription
1. Over the top WebRTCThe RTC session runs completely over the top, established using external signalling mechanisms. The operator may offer QoS allocation, bit rate recommendations and QoE report collection on request by the UE (TS 26.506 V20.0.0 annex A.1; clause 5.3).
2. MNO-provided WebRTC functionsIn addition, the operator offers trusted ICE functionality in the RTC AS, such as a list of trusted STUN and TURN servers for the RTC Client. RTC-4 is present only when the ICE Function contains the TURN server (TS 26.506 V20.0.0 annex A.1, annex A.3 NOTE; clause 5.4).
3. MNO-facilitated WebRTC servicesThe operator hosts the RTC sessions with a trusted WebRTC Signalling Function in the RTC AS, which may also offer 5G network assistance. The Simple WebRTC Application Protocol (SWAP) of TS 26.113 supports this scenario.
4. Interoperable WebRTC servicesScenario 3 extended to interoperability between operators. It is in scope, but some of its details are for future study, including its signalling protocol (TS 26.506 V20.0.0 annex A.1 NOTE, annex A.5 NOTE; TS 26.113 V19.2.0 clause 13.2.1 NOTE).

Functions required in each scenario (TS 26.506 table A.1-1):

Function1234
Provisioning FunctionOptionalOptionalOptionalOptional (TS 26.506 V20.0.0 annex A.1, table A.1-1)
Configuration FunctionOptionalRequiredOptional (may be fulfilled by the WebRTC Signalling Function)Optional (may be fulfilled by the WebRTC Signalling Function) (TS 26.506 V20.0.0 annex A.1, table A.1-1)
RTC Media Session HandlerRequiredOptionalOptionalOptional (TS 26.506 V20.0.0 annex A.1, table A.1-1)
Network Support FunctionRequiredRequiredOptional (may be fulfilled by the WebRTC Signalling Function)Optional (may be fulfilled by the WebRTC Signalling Function) (TS 26.506 V20.0.0 annex A.1, table A.1-1)
ICE FunctionN/ARequiredOptionalOptional (TS 26.506 V20.0.0 annex A.1, table A.1-1)
WebRTC Signalling FunctionN/AN/ARequiredRequired (TS 26.506 V20.0.0 annex A.1, table A.1-1)
Media FunctionN/AOptionalOptionalOptional (TS 26.506 V20.0.0 annex A.1, table A.1-1)

The reference points used for media in each scenario (TS 26.113 table 4.3.1.1-1): in scenario 1 none is in the scope of TS 26.113; in scenario 2, RTC-4m (only with TURN) and RTC-12; in scenarios 3 and 4, RTC-4m, RTC-12 and RTC-4s.

Application types​

TypeUsesWebRTC terminology (RFC 8825)
Native WebRTC AppThe client APIs at RTC-6 and RTC-7A WebRTC non-browser (TS 26.506 V20.0.0 clause 4.1.1; annex B.2)
Web AppThe W3C-defined WebRTC APIs, in a web browser on the UE. It does not instantiate RTC-6 (TS 26.506 V20.0.0 clause 4.1.1; annex B.3).A WebRTC browser

The RTC Access Function may be realised by a web browser, for RTC Clients that support Web Apps (TS 26.506 V20.0.0 clause 4.1.1 NOTE 4).

The generalised Media Delivery architecture​

TS 26.506 defines a generalised Media Delivery architecture, of which the RTC architecture is one possible realisation. In case of misalignment, the RTC architecture has precedence. TS 26.501 defines the same generalised architecture for 5G Media Streaming.

The UE with the Media-aware Application and the Media Client, which holds the Media Session Handler and the Media Access Function; the UPF; NEF and PCF joined by N30; the DN with the Media AF, the Media AS and the Media Application Provider. Reference points M1 to M13, with M8, M9, M10 and M13 out of scope; N5 and N33 to the Media AF; services Maf_Provisioning, Maf_SessionHandling and Mas_Configuration.
Generalized Media Delivery architectureRedrawn from TS 26.506 V20.0.0, figure 4.1.2.2-1Scroll sideways, or tap the figure to open it full size.
GeneralisedRTC
Media AFRTC AF (TS 26.506 V20.0.0 clause 4.1.2.3, table 4.1.2.3-1)
Media ASRTC AS (TS 26.506 V20.0.0 clause 4.1.2.3, table 4.1.2.3-1)
Media ClientRTC Client (TS 26.506 V20.0.0 clause 4.1.2.3, table 4.1.2.3-1)
Media Session HandlerRTC Media Session Handler (TS 26.506 V20.0.0 clause 4.1.2.3, table 4.1.2.3-1)
Media Access FunctionRTC Access Function (TS 26.506 V20.0.0 clause 4.1.2.3, table 4.1.2.3-1)
Media Application ProviderRTC Application Provider (TS 26.506 V20.0.0 clause 4.1.2.3, table 4.1.2.3-1)
Media-aware ApplicationNative WebRTC App (TS 26.506 V20.0.0 clause 4.1.2.3, table 4.1.2.3-1; clause 4.1.2.1)
Generalised reference pointIn RTC
M1, M4 to M8, M11, M12RTC-1, RTC-4 to RTC-8, RTC-11, RTC-12 (TS 26.506 V20.0.0 clause 4.1.2.4, table 4.1.2.4-1)
M2Not defined by the RTC architecture in this release (TS 26.506 V20.0.0 clause 4.1.2.4 NOTE 1, table 4.1.2.4-1)
M3RTC-3; defined, but its specification is for future study (TS 26.506 V20.0.0 clause 4.1.2.4 NOTE 2, table 4.1.2.4-1)
M9Not defined by the RTC architecture in this release (TS 26.506 V20.0.0 clause 4.1.2.4 NOTE 5, table 4.1.2.4-1)
M10RTC-10; defined, but not further specified in this release (TS 26.506 V20.0.0 clause 4.1.2.4 NOTE 6, table 4.1.2.4-1)
M13Not defined in RTC; private, beyond the scope of standardisation (TS 26.506 V20.0.0 clause 4.1.2.4 NOTE 7, table 4.1.2.4-1)

A Web App, which does not invoke the Media Session Handler or the Media Access Function through 3GPP-defined APIs, is not a Media-aware Application and is not mapped into the generalised architecture (TS 26.506 V20.0.0 clause 4.1.2.3 NOTE).

Edge-enabled RTC​

TS 26.506 supports two ways of managing edge processing. In client-driven management, an RTC Application aware of edge processing requests an edge resource directly and discovers the Edge Application Server best suited to serve it. In Application Function-driven management, the RTC AF allocates edge resources on behalf of the application, using information in the RTC provisioning session.

The RTC architecture with edge functions in orange: an Application Client in the RTC Application, an EEC in the RTC Media Session Handler, an EES in the RTC AF, an ECS between the RTC AF and the RTC AS, and an EAS in the RTC AS beside the ICE Function. EDGE-1, EDGE-3, EDGE-4, EDGE-5, EDGE-6 and EDGE-9 join them.
Edge-enabled RTC architectureRedrawn from TS 26.506 V20.0.0, figure 4.4.2-1Scroll sideways, or tap the figure to open it full size.

The figure corresponds to collaboration scenario 2 (TS 26.506 V20.0.0 clause 4.4.2.1 NOTE (figure 4.4.2-1)).

FunctionEdge roleEdge interfaces
RTC AFEdge Enabler Server (EES), shall supportEDGE-1, EDGE-3, EDGE-6, EDGE-9 (TS 26.506 V20.0.0 clause 4.4.2.3 item 1)
RTC ASEdge Application Server (EAS), shall supportEDGE-3, for registration with the EES (TS 26.506 V20.0.0 clause 4.4.2.3 item 2)
RTC Media Session HandlerEdge Enabler Client (EEC), should supportEDGE-1, EDGE-4, EDGE-5 (TS 26.506 V20.0.0 clause 4.4.2.3 item 3)

Release differences​

  • Release 18: TS 26.506 V18.6.0 has the same functions, reference points, scenarios and figures, except figure 4.1.2.2-1.
  • Release 19: the generalised architecture adds reference point M13, between the Media Access Function and the Media Application Provider (figure 4.1.2.2-1) (TS 26.506 V19.2.0 clause 4.1.2.4 (M13, NOTE 7), annex C (CR 0009, V19.0.0); TS 26.506 V18.6.0 clause 4.1.2.4).
  • Release 20: TS 26.506 V20.0.0 adds clause 4.8 (energy information collection, reporting and exposure) and clause 8 (procedures), which instantiate the energy architecture of TS 23.367 in the RTC System (annex C, CR 0013). Reference point M4 also carries the in-band exposure of energy consumption information (clause 4.1.2.4).
Sources for this page
  • Introduction: TS 26.506 V20.0.0, clauses 1 and 4.1.1.
  • Functions: TS 26.506 V20.0.0, clause 4.1.1 and its NOTE, clauses 4.2.2 to 4.2.12; placement from figure 4.1.1-2.
  • Reference points: TS 26.506 V20.0.0, clauses 4.3.1 to 4.3.9 and clause 4.1.2.4, NOTE 1, NOTE 2 and NOTE 6; TS 26.113 V19.2.0, clauses 4.3.1.1, 6 to 13 and annex B.3, NOTE.
  • Collaboration scenarios: TS 26.506 V20.0.0, annex A.1, table A.1-1, annexes A.3 and A.5, and clauses 5.3 to 5.5; TS 26.113 V19.2.0, clause 13.2.1 and its NOTE, table 4.3.1.1-1.
  • Application types: TS 26.506 V20.0.0, clause 4.1.1 and NOTE 4, annexes B.2 and B.3.
  • The generalised Media Delivery architecture: TS 26.506 V20.0.0, clauses 4.1.2.1, 4.1.2.3 and its NOTE, 4.1.2.4 and NOTE 1 to NOTE 7, table 4.1.2.3-1; TS 26.501 V20.0.0, clause 4.1.2.1.
  • Edge-enabled RTC: TS 26.506 V20.0.0, clauses 4.4.1, 4.4.2.1 and its NOTE, 4.4.2.3.
  • Figures: redrawn from TS 26.506 V20.0.0, figures 4.1.1-1, 4.1.1-2, 4.1.2.2-1 and 4.4.2-1.
  • Release differences: TS 26.506 V18.6.0 and V19.2.0, annex C and the figure media files compared.