FN-BRG

Fixed Network Broadband Residential Gateway

Other →
Introduced in Rel-16

FN-BRG is a standardized residential gateway in 5G systems that acts as customer premises equipment to connect homes via fixed broadband access to the 5G core network.

Category
Other
Introduced
Rel-16
Where
Core Network › 5G Core
Specifications
8 specs
FN-BRG Description Purpose Detected Changes Specifications

Description

The Fixed Network Broadband Residential Gateway (FN-BRG) is a network function and physical device defined in 3GPP Release 16 and later as part of the 5G System (5GS) architecture for fixed wireless and wireline convergence. It resides at the customer premises and terminates the fixed network access line (e.g., GPON fiber, DOCSIS cable, or Ethernet). The FN-BRG functions as the User Plane Function (UPF) and potentially part of the Control Plane for the residential user's traffic when accessing the 5G core network (5GC). It essentially extends the 5GC's service-based architecture into the home network, treating the fixed broadband connection as another type of 5G access.

Architecturally, the FN-BRG connects to the 5G Core Network via the N3 (user plane) and N2 (control plane) interfaces, analogous to how a gNB connects in mobile access. It contains a UPF instance that handles packet routing, forwarding, QoS enforcement, and traffic measurement for the residential subscriber's data flows. The Access and Mobility Management Function (AMF) and Session Management Function (SMF) in the 5GC manage the FN-BRG's control plane. Key specifications like TS 23.501 (system architecture) and TS 23.316 (wireline access evolution) detail its integration. The FN-BRG authenticates with the 5GC using 5G Authentication and Key Agreement (5G-AKA) or EAP-based methods, leveraging the Unified Data Management (UDM) for subscriber credentials.

Its operation involves establishing a Packet Data Unit (PDU) Session for the residential subscriber, just like a mobile device. The FN-BRG encapsulates/de-encapsulates user traffic into GTP-U tunnels (over N3) towards the UPF in the core or other data networks. It applies QoS rules (5QI mappings) received from the SMF via the N4 interface to prioritize traffic (e.g., voice, video) appropriately over the fixed access. The FN-BRG also provides typical home gateway functions like Network Address Translation (NAT), firewall, DHCP server, and Wi-Fi access point, but now managed and orchestrated through 5G network slices and policies, enabling true fixed-mobile service parity.

Purpose & Motivation

The FN-BRG was created to fully integrate high-performance fixed broadband access into the 5G service-based architecture, addressing the industry trend towards Fixed Mobile Convergence (FMC). Prior to Release 16, fixed broadband networks (DSL, fiber) and mobile networks (4G/5G) were largely separate domains with different management systems, policy controls, and service delivery mechanisms. This separation led to operational complexity, inability to offer uniform service-level agreements (SLAs) across access types, and missed opportunities for network resource optimization.

The FN-BRG solves this by making the residential gateway a first-class citizen in the 5G core. It allows operators to leverage a single, unified 5G core (with its cloud-native, scalable, slice-aware capabilities) to deliver services to both mobile and fixed subscribers. This enables the creation of network slices that span both access types—for example, a single ultra-reliable low-latency communication (URLLC) slice serving a factory's mobile robots and its fixed-line sensors. It also simplifies the subscriber's experience by providing a single identity, policy, and billing profile regardless of whether they connect via a smartphone on 5G radio or a laptop on home Wi-Fi through the FN-BRG. The motivation stems from operators' desires to reduce costs through consolidated network cores and to launch innovative converged services (like seamless video call handover from mobile to home Wi-Fi) faster.

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change

In Release 15, the FN-BRG function was introduced with a specific enhancement to its authentication procedure. This involved defining that a key authentication response parameter Information Element (IE) must be of a fixed length. This change standardized the format of this critical signaling element for the Fixed Network Broadband Residential Gateway.

  • Authentication response parameter IE to be of fixed length (24.501) TS 24.501CR0275
Rel-16 2 changes

In Release 16, the FN-BRG function was clarified regarding the application of Service Area Restrictions. The change specifically defined that Service Area Restrictions are not applicable to the FN-BRG, resolving an editor's note on the matter, while confirming their continued applicability to the FN-CRG function.

  • Service Area Restrictions applicability for FN-CRG, and not FN-BRG TS 23.316CR0056
  • Resolving editor's note on service area restrictions in case of FN-BRG TS 24.501CR1872
Rel-17 1 change

In Release 17, the FN-BRG function saw updates primarily focused on correcting formatting issues in the specification's notes and editor's notes. The release included editorial clarifications and fixes to improve the document's readability and consistency. No new technical procedures, interfaces, or capabilities for the FN-BRG were introduced in this specific set of changes.

  • Notes and editor notes formatting issues fixed TS 29.561
Rel-18 3 changes

In Release 18, the FN-BRG function was enhanced to allow a Wireless Access Gateway Function (W-AGF) to act on its behalf for accessing a Standalone Non-Public Network (SNPN). Furthermore, the protocol support was updated by mandating the inclusion of the "502 Bad Gateway" error code for specific error handling scenarios.

  • W-AGF acting on behalf of FN-BRG and accessing SNPN TS 24.502CR0266
  • Adding the mandatory error code 502 Bad Gateway TS 29.507CR0230
  • Adding the mandatory error code 502 Bad Gateway TS 29.525CR0227

Explore further

Broader topics and technologies where FN-BRG plays a role.

Defining Specifications

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

SpecificationTitleRelease
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 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.507 vj40 5G Access & Mobility Policy Control Service Rel-19
TS 29.525 vj40 5G UE Policy Control Service Stage 3 Rel-19
TS 29.561 vj30 5G Interworking with External Data Networks Rel-19