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

Glossary term · Core Network

BG

Border Gateway

Core Network →

BG is a functional entity in GPRS/UMTS networks that acts as a secure gateway between the GPRS backbone and external packet data networks, handling IP routing, address translation, and firewall functions.

Introduced
R99
Where
Management
Specifications
11 specs
Also in
Core Network, Services
BG Description Purpose What changed Neighbours Specifications

Description

The Border Gateway (BG) is a critical architectural component within the GPRS core network, specifically part of the Gateway GPRS Support Node (GGSN) functionality or implemented as a standalone node. Its primary role is to serve as the demarcation point between the secure, operator-controlled GPRS backbone (the GPRS Tunneling Protocol or GTP-based domain) and external, untrusted packet data networks like the public Internet or corporate intranets. The BG enforces security policies, performs network address translation (NAT), and manages IP routing to ensure data packets are correctly forwarded between the mobile user's device (MS) and the destination PDN.

Architecturally, the BG interfaces internally with other GPRS network nodes, primarily the GGSN, via the Gi reference point. Externally, it connects to PDNs. It operates at the IP layer, inspecting and processing IP packets. Key functional components include a firewall for packet filtering and access control, a NAT module to translate between private GPRS backbone IP addresses and public IP addresses used on external networks, and routing functions to determine the optimal path for data traffic. It may also incorporate charging gateway functions to collect data usage records for billing.

In operation, when a mobile device activates a Packet Data Protocol (PDP) context, the GGSN assigns it an IP address from the GPRS network's address pool. Outbound traffic from the mobile station is tunneled via GTP to the GGSN, which then forwards IP packets to the BG. The BG performs necessary NAT, replacing the private source IP with a public one, applies firewall rules, and routes the packet onto the external PDN. For inbound traffic destined for the mobile, the reverse process occurs: the BG receives packets, translates the public destination IP to the corresponding private IP, and forwards them to the GGSN for GTP tunneling to the Serving GPRS Support Node (SGSN) and ultimately the radio access network. This architecture isolates the GPRS core from external threats and manages IP address scarcity.

Purpose & Motivation

The Border Gateway was introduced in 3GPP Release 99 to address fundamental challenges in securely and efficiently connecting mobile networks to external IP-based networks as GPRS enabled packet-switched data services. Prior to GPRS, cellular networks were primarily circuit-switched for voice, with limited data capabilities. The shift to packet data required a secure gateway to bridge the operator's private network realm and public data networks, protecting network infrastructure and subscriber data from external attacks.

It solved several key problems: First, it provided essential security through firewall functionality, preventing unauthorized access from the Internet into the GPRS core. Second, it enabled efficient use of scarce public IPv4 addresses via Network Address Translation (NAT), allowing many mobile devices to share a pool of public IPs. Third, it managed routing between different administrative domains, ensuring packets correctly traversed from the mobile network to various external PDNs (e.g., Internet, IMS, corporate networks). The BG's creation was motivated by the need for a standardized, controlled interface (the Gi reference point) that could support diverse services like WAP browsing, email, and later, IMS multimedia, while maintaining operator control over security, charging, and policy enforcement.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.060Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.060 →

Evolution Across Releases

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

R99 Initial

Introduced the Border Gateway as part of the GPRS architecture. Defined its role in providing secure interworking between the GPRS backbone and external Packet Data Networks (PDNs) via the Gi interface. Initial capabilities included basic firewall functions, NAT, and IP routing to enable early mobile data services like WAP and Internet access.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.622 vb10 Generic Network Resources IRP NRM Rel-11 read
TS 32.632 vb00 Core Network Resources IRP: Network Resource Model Rel-11 read
TS 32.732 vb00 IMS Network Resource Model IRP: Information Service Rel-11 read
TS 33.210 vk00 Network Domain Security for IP Networks Rel-20 read