RS

Remote Source

Protocol →
Introduced in Rel-8

RS is a logical entity representing an inbound media stream endpoint on a Media Gateway, such as audio from a circuit-switched network leg or an IP stream.

Category
Protocol
Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Specifications
23 specs
RS Description Purpose Related Classification Specifications

Description

In the context of 3GPP architectures, particularly those involving Media Gateways (MGW) and the Media Gateway Control Function (MGCF) or Media Resource Function Controller (MRFC), "RS" stands for Remote Source. This is a protocol-level term inherited from the H.248 (Megaco) protocol, which is the standard interface for controlling media gateways. Within the H.248 model, a Media Gateway is abstracted into a series of terminations and contexts. Terminations are sources or sinks of media streams, and contexts are associations mixing or switching multiple terminations. The "Remote Source" is a specific type of termination descriptor or property that identifies the remote endpoint from which a media stream is originating.

Operationally, when a Media Gateway Controller (MGC) like an MGCF sets up a call traversing a media gateway—for instance, converting between Time-Division Multiplexing (TDM) voice from the legacy PSTN and RTP/IP packets for the IMS core—it uses H.248 commands to configure the terminations within the MGW. For the termination that will receive the incoming media stream (e.g., the RTP stream from the IP side, or the timeslot from the TDM trunk), the controller may specify properties that include identifying it as a Remote Source. This descriptor carries information about the remote party's media parameters, such as the IP address, port number, codec type, and packetization characteristics. It essentially tells the media gateway, "expect to receive a stream from this remote source with these properties."

The RS descriptor is crucial for the MGW to properly configure its receive path. It allows the gateway to open the correct ports, initialize the appropriate jitter buffers, and prepare the necessary transcoding resources if the received codec differs from what needs to be sent out on the other termination. The concept is symmetrical with "Remote Sink," which describes the destination for an outbound stream. Together, they enable the MGC to fully describe a bidirectional media flow using the H.248 protocol's connection model. In 3GPP specifications like TS 29.232 (Mn interface), which profiles H.248 for 3GPP use, these terms are used to define the precise information exchanged between the MGCF and the MGW to establish media bearers for services like voice call continuity between CS and IMS domains.

Purpose & Motivation

The purpose of the "Remote Source" concept within the 3GPP control framework is to provide an abstract, standardized way for a controller to instruct a media gateway about the characteristics of an incoming media stream. This abstraction is fundamental to the decomposition of call control and media processing mandated by the Gateway Control architecture. Historically, in monolithic switches, call control and media switching were tightly integrated. The move to decomposed architectures, with separate MGCFs (for signaling) and MGWs (for media), required a robust protocol—H.248—to allow the controller to command the media plane. The RS descriptor is a key element of this protocol, solving the problem of how to precisely describe a dynamic, remote media endpoint to a relatively dumb media gateway.

Before such abstractions, configuring media paths was often low-level and vendor-specific. The RS term, as part of the H.248 standard, creates a common language. It allows a Media Gateway Controller from one vendor to successfully configure a Media Gateway from another vendor to receive a stream from a third-party endpoint. This interoperability is critical for multi-vendor networks. Its creation was motivated by the need for flexibility and scalability in next-generation networks. An MGCF handling complex call routing (e.g., for a roaming subscriber's call) needs to be able to instruct the MGW to connect a stream from a potentially unknown remote IP address (the RS) to a local TDM circuit. The RS descriptor encapsulates all the necessary IP transport and media encoding information in a structured way.

Furthermore, in 3GPP's evolution towards IMS and SRVCC (Single Radio Voice Call Continuity), the ability to rapidly repoint media streams during handovers is vital. The MGCF uses H.248 commands with RS (and Remote Sink) descriptors to quickly reconfigure the MGW's media connections when a call is handed over from LTE to 2G/3G. Thus, the RS concept exists to enable precise, interoperable, and dynamic control of media flows in a decomposed network architecture, which is a cornerstone of modern telecom networks supporting both legacy and IP-based services.

Classification

Part ofMGCF

Evolution Across Releases

Rel-8 Initial

The term 'Remote Source' was adopted as part of the 3GPP profiling and usage of the ITU-T H.248.1 Gateway Control Protocol. It was introduced in specifications governing the Mn interface (between MGCF and MGW) and other media control interfaces, establishing the foundational model for describing media stream endpoints in IMS and CS-IMS interworking scenarios.

Explore further

Broader topics and technologies where RS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 29.238 vj00 H.248 Profile for IBCF-TrGW Interface Rel-19
TS 36.104 vj10 Base Station (BS) radio transmission and reception Rel-19
TS 36.116 vj00 E-UTRA Relay RF Requirements Rel-19
TS 36.117 vj00 E-UTRA Relay RF Test Methods & Requirements Rel-19
TS 36.141 vj00 E-UTRA BS Conformance Testing Rel-19
TS 36.213 vj10 LTE Physical Layer Procedures Rel-19
TS 37.104 vj10 MSR Base Station RF Characteristics Rel-19
TS 37.141 vj10 RF Test Methods for Multi-Standard Radio Base Stations Rel-19
TS 37.145 vj10 AAS Base Station Conducted Conformance Testing Rel-19
TS 37.802 va10 MSR BS RF Requirements for Non-Contiguous Spectrum Rel-10
TS 37.812 vb30 Multi-band Multi-standard Radio BS Requirements Rel-11
TR 37.900 vj00 Multi-Standard Radio (MSR) Base Station Requirements Rel-19
TS 38.104 vj20 NR Base Station RF Requirements Rel-19
TS 38.141 vj20 NR Base Station RF Conformance Testing Part 1 Rel-19
TS 38.176 vj20 IAB Conformance Testing Specification Rel-19
TS 38.213 vj10 NR Physical Layer Control Procedures Rel-19
TS 38.214 vj10 NR Physical Layer Procedures for Data Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TR 38.869 vi00 Study on low-power wake up signal and receiver for NR Rel-18
TR 38.889 vg00 NR-based access to unlicensed spectrum study Rel-16
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.