Description
The Residential Gateway (RG) is a customer-premises equipment (CPE) device that serves as the demarcation point between the subscriber's internal local area network (LAN) and the service provider's access network. In 3GPP architectures, particularly for fixed-mobile convergence and broadband access, the RG facilitates connectivity over various access technologies, including DSL, fiber (PON), or wireless (e.g., via 3GPP radio interfaces). It typically incorporates a router with Network Address Translation (NAT) and firewall capabilities, a DHCP server for IP address assignment to connected devices, and often an integrated wireless access point for Wi-Fi connectivity. The RG manages Quality of Service (QoS) policies for traffic prioritization, supports multiple service flows for different applications (like voice, video, and data), and may implement security features such as WPA2/WPA3 for Wi-Fi. In 3GPP specifications, the RG interfaces with network elements like the Broadband Network Gateway (BNG) or User Plane Function (UPF) in 5G systems, using protocols such as PPPoE or IPoE for authentication and session management. Its role is critical in delivering triple-play services (internet, TV, voice) and enabling smart home applications by providing reliable, managed connectivity.
Purpose & Motivation
The Residential Gateway was introduced to provide a standardized, managed endpoint for broadband services in residential and small business environments. It solves the problem of disparate, unmanaged customer equipment that could lead to inconsistent service quality, security vulnerabilities, and complex troubleshooting for operators. By deploying a provider-managed RG, operators can ensure consistent performance, enforce QoS policies, remotely diagnose issues, and offer value-added services like managed Wi-Fi or parental controls. Historically, as broadband services evolved from simple internet access to bundled offerings including IPTV and VoIP, the need for a robust, feature-rich gateway became apparent to handle multiple service flows with different latency and bandwidth requirements. The RG addresses limitations of basic modems by integrating routing, switching, and often wireless capabilities into a single device, simplifying the customer installation and reducing support costs.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (92 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-6, normative work from Rel-16.
In Release 16, the standardization of the Fixed Network Residential Gateway (FN-RG) and 5G-RG was significantly expanded, introducing specific procedures for deregistration, service requests, PDU session modification, and user profile management. It defined how a Wireline Access Gateway Function (W-AGF) can act on behalf of an FN-RG and clarified network access control and N2 procedures. The release also detailed user location reporting for access via Wireline 5G Cable or BBF Access Networks (W-5GCAN/W-5GBAN) using identifiers like an HFC Node ID, and established EPS interworking mechanisms for Multi-Access PDU sessions.
- Deregistration procedure for FN-RG TS 23.316CR0003
- Service request procedure for FN-RG TS 23.316CR0004
- Other procedures for FN-RG TS 23.316CR0005
- User profile management and handover clarifications for FN-RG TS 23.316CR0006
- PDU Session Modification and Release procedures for FN-RG TS 23.316CR0007
- Features for W-AGF to act on behalf of FN-RG TS 23.316CR0009
+ 48 more changes
In Release 17, key enhancements for the Residential Gateway (RG) function included expanded support for 5G-RGs accessing the 5G Core via different wireline networks, with specific user location information defined for W-5GCAN (using an HFC Node ID) and W-5GBAN. The release also introduced the definition of User Location Information for a UE behind a 5G-RG acting as a Trusted Non-3GPP Access Point (TNAP), incorporating a TNAP ID with civic address information. Furthermore, it addressed the applicability of ATSSS to 5G-RG and removed previous limitations on 3GPP access leg support in the EPC.
In Release 18, the specifications introduced new capabilities for the 5G-RG (Residential Gateway) to act as a Trusted Non-3GPP Access Point (TNAP), including defining its User Location Information with civic address details for this role. The release also added specific procedures to support and authenticate AUN3 and NAUN3 devices connected behind a 5G-RG, such as enhanced authentication methods and impacts on registration. Furthermore, it defined differentiated service handling for devices behind the RG and clarified support for the NSWO (Non-Seamless WLAN Offload) procedure to authorize UEs behind the gateway.
- Add definition of User Location Information of 5G-RG acting as a TNAP to TNGF TS 23.003CR0695
- Differentiation for UEs behind 5G-RG TS 23.316CR2085
- New feature for 5G-RG to support NSWO procedure to authorize UE behind RG TS 23.316CR2087
- 5G-RG ID provided in Trusted Non-3GPP access procedure TS 23.316CR2097
- Differentiated service for NAUN3 devices connected behind a 5G-RG TS 23.316CR2099
- Support of AUN3/NAUN3 device behind 5G-RG TS 24.501CR5421
+ 19 more changes
In Release 19, key enhancements for the Residential Gateway (RG) function introduced new capabilities for managing non-3GPP devices connected behind a 5G-RG, including the definition of their identifiers and support for QoS differentiation of their traffic. The release also added support for Explicit Congestion Notification (ECN) marking for L4S on the 5G-RG and included corrections to the 5G-RG de-registration procedure. Furthermore, specifications for User Location Information were expanded to cover a 5G-RG acting as a Trusted Non-3GPP Access Point (TNAP), incorporating the TNAP ID and civic address.
- Identifying non-3GPP devices behind 5G-RG TS 23.316CR2136
- Support of N3GPP device behind UE/5G-RG as concluded in TS 23.700-34 KI#4 TS 23.501CR5750
- UDR enhancement supporting Device Identifier of non-3GPP Devices connecting behind a UE/5G-RG TS 23.501CR5547
- Definition of identifiers of N3GPP device behind UE/5G-RG TS 23.501CR5749
- Support of ECN marking for L4S for 5G-RG TS 24.501CR6626
- Support of QoS differentiation of traffic for N3GPP device behind UE or 5G-RG TS 24.501CR6618
+ 2 more changes
Explore further
Broader topics and technologies where RG plays a role.
Defining Specifications
3GPP specifications that define or reference RG, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.003 vj50 | Numbering, addressing and identification in 3GPP | Rel-19 |
| TS 23.008 vj00 | Organization of Subscriber Data | Rel-19 |
| TS 23.139 vj00 | 3GPP-Fixed Broadband Interworking Stage 2 | Rel-19 |
| TS 23.203 vj20 | Policy and charging control architecture | Rel-19 |
| TS 23.316 vj30 | Wireline and Wireless Convergence Access Support | Rel-19 |
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.716 vg00 | Wireline and Trusted Non-3GPP Access to 5G Core | Rel-16 |
| TS 23.725 vg20 | Study on URLLC Architecture Enhancements | Rel-16 |
| TS 23.839 vc00 | Fixed-Mobile Convergence Architecture Study | Rel-12 |
| TS 23.896 vc00 | Policy & Charging Control for Fixed Broadband Convergence | Rel-12 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.524 vj00 | Hosted Enterprise Services Architecture | Rel-19 |
| TS 25.309 v1600 | FDD Enhanced Uplink Support | Rel-6 |
| TS 25.319 vj00 | Enhanced Uplink for UTRA FDD/TDD | Rel-19 |
| TS 25.321 vj00 | MAC Protocol Specification for UTRAN | Rel-19 |
| TS 25.331 vj00 | UTRAN RRC Protocol Specification | Rel-19 |
| TS 29.212 vj00 | Gx/Gxx/Sd/St Diameter Protocol | Rel-19 |
| TS 29.213 vj20 | PCC Signalling Flows and QoS Mapping | Rel-19 |
| TS 29.215 vj00 | S9 Reference Point Stage 3 Specification | Rel-19 |
| TS 29.503 vj50 | UDM Service Based Interface Stage 3 | Rel-19 |
| TS 29.509 vj50 | AUSF Service Based Interface Protocol | Rel-19 |
| TS 29.561 vj30 | 5G Interworking with External Data Networks | Rel-19 |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 |
| TS 32.298 vj30 | Charging Data Record (CDR) Parameter Specification | Rel-19 |
| TS 32.833 vb00 | Converged OSS End-to-End Management Study | Rel-11 |
| TS 32.843 vd00 | PS Domain Online Charging in Roaming | Rel-13 |
| TR 38.825 vg00 | Study on NR Industrial IoT | Rel-16 |