Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

BRAS

Broadband Remote Access Server

Core Network →

BRAS is a network gateway that aggregates subscriber sessions from broadband access networks, providing authentication, IP management, and policy enforcement between the access and core networks.

Introduced
Rel-7
Where
Core Network › 5G Core
Specifications
7 specs
BRAS Description Purpose What changed Specifications

Description

The Broadband Remote Access Server (BRAS) is a pivotal aggregation and control point within a service provider's network, situated at the edge of the core IP network. Its primary role is to terminate and manage subscriber sessions originating from various broadband access technologies, such as Digital Subscriber Line (DSL), Passive Optical Networks (PON), and Ethernet-based access. Architecturally, the BRAS sits between the access network (e.g., DSLAMs, OLTs) and the core network routers, acting as the first IP-aware hop for subscriber traffic. It establishes Point-to-Point Protocol (PPP) or IP over Ethernet (IPoE) sessions with customer premises equipment (CPE), handling the entire lifecycle from session initiation to termination.

Operationally, the BRAS performs several key functions. During session establishment, it interacts with AAA servers (typically using RADIUS or Diameter protocols) to authenticate subscribers and authorize their service profiles. It assigns IP addresses to subscribers, either from local pools or via interaction with a Dynamic Host Configuration Protocol (DHCP) server. A core function is policy enforcement, where the BRAS applies rules defined in the subscriber's profile or from a Policy and Charging Rules Function (PCRF). These rules govern bandwidth, QoS parameters (e.g., traffic prioritization, shaping), and access control lists (ACLs), enabling the creation of tiered service plans (e.g., basic, premium, business). The BRAS also performs detailed accounting, collecting data on session duration, volume of data transferred, and other metrics for billing and network analysis.

From a traffic forwarding perspective, the BRAS routes subscriber traffic into the appropriate service network or the public internet. It often implements Network Address Translation (NAT) for private IPv4 addresses and may support IPv6 transition mechanisms. Advanced BRAS platforms integrate deep packet inspection (DPI) capabilities for enhanced service awareness and application-based policy control. In a 3GPP context, the BRAS/BNG is referenced in specifications for fixed broadband access interworking, where its role in QoS and policy control is aligned with the PCC (Policy and Charging Control) architecture, allowing for unified policy management across fixed and mobile networks. Its management interfaces support configuration, fault management, and performance monitoring as part of the operator's OSS/BSS.

Purpose & Motivation

The BRAS was created to address the fundamental challenges of scaling and managing large-scale broadband subscriber networks. As DSL and other broadband technologies moved beyond simple internet connectivity to offer differentiated services (like VoIP, IPTV, and gaming), network operators needed a centralized point of control at the network edge. Prior approaches, using simple routers or layer-2 switches, lacked the granular subscriber awareness, robust AAA integration, and sophisticated policy enforcement required for commercial service delivery. The BRAS solved this by providing a dedicated network element that could uniquely identify and manage thousands of individual subscriber sessions on a single physical interface.

Historically, its development was driven by the mass deployment of DSL in the late 1990s and early 2000s. Operators required a way to aggregate countless individual PPP sessions from DSL modems, authenticate them against a subscriber database, assign IP addresses dynamically, and apply service-specific policies. The BRAS became the cornerstone for turning a raw broadband access infrastructure into a manageable, billable, and service-rich network. It enabled the business model of tiered internet services and paved the way for triple-play offerings (data, voice, video).

In the 3GPP ecosystem, the formal recognition and specification of BRAS/BNG functionalities, particularly in releases covering fixed broadband access and convergence (FMC), were motivated by the need for seamless interworking between mobile and fixed networks. By defining how a BRAS interacts with 3GPP-defined policy control (PCRF) and authentication frameworks, 3GPP standards allow operators to deliver consistent service experiences and unified policy management across all access types, addressing the limitation of siloed network management.

What changed in its specifications

The latest release-to-release comparison of specifications that define BRAS. Each summary describes the whole specification, not only this term.

TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →
TS 24.229Rel-18 → Rel-19

Rel-19 adds Rich Call Data support to TS 24.229, including the DC-Info header, rcd-np Call-Info parameter, and RCD info retrieval and verification across originating, terminating, IBCF and AS behaviour. It also adds MPS for Messaging, eCall alignment with EN 17184:2024 (test eCall and updated-MSD transfer), and satellite identifiers in P-Access-Network-Info.

Full comparison in TS 24.229 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Introduced the BRAS/BNG concept within the 3GPP framework for Fixed Broadband Access Interworking. Initial specifications defined its role as the termination point for fixed access, focusing on basic session management, IP address allocation, and integration with the Policy and Charging Control (PCC) architecture for QoS and policy enforcement. This established the foundation for converged policy management across fixed and mobile domains.

Defining Specifications

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

SpecificationTitleRelease
TS 23.139 vj00 3GPP-Fixed Broadband Interworking Stage 2 Rel-19 read
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 23.839 vc00 Fixed-Mobile Convergence Architecture Study Rel-12 read
TS 23.896 vc00 Policy & Charging Control for Fixed Broadband Convergence Rel-12 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.819 v700 IMS Services via Fixed Broadband Access Rel-7 read
TS 32.833 vb00 Converged OSS End-to-End Management Study Rel-11 read