Description
The Fixed Network Residential Gateway (FN-RG) is a critical architectural element defined within the 5G System (5GS) to support Fixed Mobile Convergence (FMC). It functions as a standardized, trusted non-3GPP Interworking Function (TNGF) specifically designed for residential or business fixed access scenarios. The FN-RG acts as a termination point for the user's fixed network (e.g., a fiber or DSL line) and establishes a secure, standardized interface (N2 and N3) with the 5G Core Network (5GC). This allows the 5GC's Access and Mobility Management Function (AMF) and User Plane Function (UPF) to manage sessions and data flows for devices connected via the fixed network as if they were connected via 3GPP radio access.
Architecturally, the FN-RG contains both control plane and user plane components. On the control plane, it implements the N2 interface towards the AMF, carrying Non-Access Stratum (NAS) signaling for devices behind the gateway. It also supports the N1 interface termination, allowing the User Equipment (UE) – which could be a router, set-top box, or any IP device in the home – to communicate with the 5GC core. For authentication and security, the FN-RG interacts with the Authentication Server Function (AUSF) and Security Anchor Function (SEAF) using standard 5G authentication procedures over the N2 reference point, ensuring the fixed access is a trusted entry point into the 5G network.
On the user plane, the FN-RG implements the N3 interface towards the UPF. It encapsulates and forwards user data packets from the fixed network into GTP-U tunnels directed to the appropriate UPF, as determined by the Session Management Function (SMF). This enables seamless routing of traffic and application of 5G Quality of Service (QoS) policies, including 5G QoS Identifiers (5QI) and reflective QoS, to flows originating from the fixed network. The FN-RG's role is therefore to abstract the underlying fixed access technology (e.g., xDSL, PON) and present it to the 5GC as a standardized, manageable access leg, enabling unified policy control, charging, and mobility management across 3GPP and non-3GPP accesses.
Purpose & Motivation
The FN-RG was introduced to solve the problem of fragmented network management and service delivery in converged operator environments. Historically, fixed and mobile networks operated as separate silos with distinct cores (e.g., Broadband Network Gateway (BNG) for fixed, Packet Data Network Gateway (PGW) for mobile), leading to duplicated functions, inconsistent user policies, and an inability to offer truly seamless services. The rise of 5G and its cloud-native, service-based architecture (SBA) presented an opportunity to unify core network functions. The FN-RG enables this by allowing a single 5G Core to serve as the unified anchor for both mobile and fixed access.
Its creation was motivated by the industry drive towards Fixed-Mobile Convergence (FMC), a key trend for operators who own both fixed and mobile assets. By integrating fixed access as a trusted non-3GPP access type into the 5GS, operators can leverage the advanced capabilities of the 5GC—such as network slicing, edge computing (MEC), and unified authentication—for their fixed broadband subscribers. This allows for the creation of innovative converged services, like a single subscription for home, mobile, and IoT, with consistent security, parental controls, and application-aware routing policies applied regardless of how the user connects.
Furthermore, the FN-RG addresses the limitations of earlier, proprietary gateways by providing a 3GPP-standardized interface. This standardization reduces vendor lock-in, simplifies network integration, and ensures interoperability between fixed access equipment and the 5G core from different suppliers. It future-proofs the fixed network by aligning it with the agile, software-defined principles of 5G, enabling faster deployment of new services and more efficient use of network resources across the entire operator domain.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (47 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the FN-RG function was introduced with a specific enhancement to its authentication procedure, mandating that the authentication response parameter Information Element (IE) be of a fixed length. This change, detailed in the 24.501 specification, standardized the format for this critical signaling element to ensure interoperability and reliable communication between the fixed network residential gateway and the core network.
- Authentication response parameter IE to be of fixed length (24.501) TS 24.501CR0275
In Release 16, the FN-RG function introduced new procedures including explicit deregistration and service request mechanisms, along with enhanced PDU session modification and release procedures. The release also defined capabilities for the W-AGF to act on behalf of the FN-RG and provided clarifications for network access control and N2 procedures. Furthermore, it specified updates for FN-RG configuration and registration, and addressed IP address allocation and the handling of untrusted FN-RG PEI (Portable Equipment Identity).
- 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
+ 25 more changes
In Release 17, the FN-RG function saw clarifications and specific exclusions, including that emergency registration procedures are not applicable for FN-RG devices. The release also defined the support of Session and Service Continuity (SSC) modes for FN-RG and provided clarifications on authentication mechanisms for User Equipment behind such gateways.
In Release 18, enhancements for the FN-RG included clarifying the handling of User Equipment behind the gateway and introducing support for UE Route Selection Policy (URSP). The release also added mandatory error code reporting, specifically the "502 Bad Gateway" error, and addressed authentication procedures for UE behind the FN-RG using Non-Seamless WLAN Offload (NSWO). Furthermore, corrections were made to technical attributes, such as the Access Network Gateway Address.
- USRP rule enforcement reporting is not supported by 5G-RG and FN-RG TS 24.501CR6084
- Authentication for UE behind 5G-RG and FN-RG using NSWO TS 33.501CR1593
- Clarification on UE behind 5G-RG and FN-RG TS 23.316CR2116
- URSP for 5G-RG and FN-RG TS 23.316CR2128
- Adding the mandatory error code 502 Bad Gateway TS 29.507CR0230
- Adding the mandatory error code 502 Bad Gateway TS 29.512CR0969
+ 5 more changes
In Release 19, the new work for the Fixed Network Residential Gateway (FN-RG) function introduced support for the NR Femto architecture with an NR Femto Gateway. This enhancement integrates the FN-RG into a new network topology for 5G small cell deployments, specifically defining its role in relation to the new gateway entity. The update establishes the FN-RG's operational procedures and identities within this architecture, leveraging existing fixed part identification principles.
- Support of NR Femto architecture with NR Femto Gateway TS 38.413CR1232
Explore further
Broader topics and technologies where FN-RG plays a role.
Defining Specifications
3GPP specifications that define or reference FN-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.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 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.502 vj20 | 5G Core Access via Non-3GPP Networks; Stage 3 | Rel-19 |
| TS 29.413 vj00 | NGAP for Non-3GPP Access | Rel-19 |
| TS 29.503 vj50 | UDM Service Based Interface Stage 3 | Rel-19 |
| TS 29.507 vj40 | 5G Access & Mobility Policy Control Service | Rel-19 |
| TS 29.509 vj50 | AUSF Service Based Interface Protocol | Rel-19 |
| TS 29.512 vj40 | 5G Session Management Policy Control Service | Rel-19 |
| TS 29.514 vj40 | 5G System; Policy Authorization Service; Stage 3 | Rel-19 |
| TS 29.521 vj40 | 5G Binding Support Management Service Stage 3 | Rel-19 |
| TS 29.525 vj40 | 5G UE Policy Control Service Stage 3 | Rel-19 |
| TS 29.594 vj20 | 5G Spending Limit Control Service Stage 3 | Rel-19 |
| TS 33.501 vk00 | 5G Security Architecture and Procedures | Rel-20 |
| TS 38.413 vj10 | NG Application Protocol (NGAP) | Rel-19 |