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

Glossary term · Interface

SGi

Reference point between the PDN GW and a packet data network

Interface →

SGi is the 3GPP reference point connecting the PDN Gateway to an external packet data network, such as the Internet, and it carries user-plane IP traffic.

Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
1 specs
SGi Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

SGi is a 3GPP reference point that connects the PDN Gateway (PGW) to an external packet data network (PDN), such as the Internet, an IMS network, a corporate IP network, or an operator-hosted service platform. In the Evolved Packet Core introduced in Release 8, the PGW is the anchor point for user-plane IP traffic between the mobile network and external IP networks. SGi is therefore the logical boundary where mobile IP sessions are terminated and where packets are routed into or out of the operator's core network. It is not defined as a single physical port or proprietary protocol; it is a reference point whose implementation can use standard IP routing, Ethernet, VLANs, or other transport mechanisms inside the operator's Gi LAN.

From an operational perspective, SGi carries user-plane IP packets only. When a UE establishes a PDN connection, the MME and S-GW coordinate bearer setup, and the PGW allocates an IP address for the UE based on the requested APN and PDN type. The PGW then maintains a session context that maps the UE IP address, bearer identifiers, packet filters, QoS parameters, and charging information. Downlink traffic from an external host arrives on SGi addressed to the UE IP. The PGW identifies the corresponding EPS bearer, applies packet filtering and policy rules, and forwards the packet toward the S-GW and eNodeB. Uplink traffic follows the reverse path: packets arrive from the S-GW, are inspected by the PGW, and are sent toward the external network through SGi.

The SGi interface supports multiple PDN connections for a single UE. A UE can connect to the public Internet and to a private IMS or enterprise network simultaneously, with separate PGW contexts and possibly different IP addresses. This separation is important for services that require distinct routing, security, or charging domains. SGi can support IPv4, IPv6, or dual-stack connectivity, depending on the PDN type negotiated during attachment. It may also support IPv6 prefix delegation and related mobile IP mechanisms, allowing the UE or external service to receive routable prefixes. The reference point can be implemented in the home network or in a visited network, depending on roaming architecture: home-routed roaming keeps SGi in the home network, while local breakout may use a visited PGW and a different SGi path.

Because SGi is the boundary between the mobile core and external networks, it is a natural place for operator functions that must act on all user traffic. The PGW can apply policy enforcement, packet marking, rate limiting, deep packet inspection integration points, lawful interception, and charging-related packet inspection. In many deployments, SGi connects to a Gi LAN containing routers, firewalls, NAT devices, charging systems, and monitoring probes. Although the external network does not need to understand LTE bearer concepts, the PGW hides mobility and bearer changes from it. A UE can move between eNodeBs, S-GWs, or access technologies while keeping the same IP anchor, so the external PDN sees a stable IP endpoint.

In standards terms, SGi is specified in 23.401 as part of the EPC architecture. Its main role is to define the reference point for IP connectivity between the PGW and the PDN, while leaving transport implementation details to operators. The interface is fundamental to all-IP mobile networks because it separates the radio access and core mobility functions from external IP services. This allows the operator to evolve access technologies, bearer management, and policy control without requiring changes in the Internet or private IP networks. As a result, SGi provides the stable IP edge that supports voice, data, messaging, IoT, and enterprise connectivity over LTE and later 5G interworking architectures.

Purpose & Motivation

SGi exists to provide a standardized IP boundary between the mobile core and external packet data networks. In earlier GPRS and UMTS architectures, gateways such as the GGSN connected to external IP networks, but the Evolved Packet Core introduced a flatter, all-IP architecture in which the PGW became the central anchor for mobility, bearer management, and policy enforcement. A clear reference point was needed to describe how the PGW interacts with the Internet, IMS, private networks, and roaming networks without specifying every physical or vendor implementation detail.

The problem SGi solves is the separation of mobile network complexity from external IP services. Without a stable IP anchor, an external server would need to understand radio bearers, handovers, access technology changes, and roaming paths. SGi allows the PGW to present a normal IP endpoint to the external network while internally mapping packets to EPS bearers and applying operator policies. It also supports multiple PDN connections, different IP versions, and separate routing domains, which are essential for voice, data, IoT, and enterprise services.

Historically, operators needed a way to apply charging, lawful interception, packet filtering, and QoS mapping at the edge of the mobile core. SGi made those functions possible at a well-defined network boundary. It also enabled roaming architectures to distinguish home-routed and local-breakout paths, improving performance and control. By defining SGi as a reference point rather than a fixed protocol, 3GPP allowed operators to use standard IP routing and security mechanisms while preserving interoperability with EPC functions.

What changed in its specifications

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

TS 23.401Rel-18 → Rel-19

Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.

Full comparison in TS 23.401 →

Technology family

Core network interfaces and reference points · Core Network

  1. R97 Gi, Gn, Gp
  2. Rel-7 Gx
  3. Rel-8 S1-MME, S1-U, S11, S5, S8, SGi
  4. Rel-15 N11, N2, N3, N4, N6, N7, N9
  • SGi counterpart in another generation: Gi
    “This reference point corresponds to Gi for 3GPP accesses.” TS 23.401
  • SGi counterpart in another generation: N6
    “A Traffic Endpoint can correspond to a GTP-u endpoint, an SGi or an N6 endpoint.” TS 29.244

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 9 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-8 introduced

The SGi reference point between the PDN GW and the external packet data network is defined for the first time in the EPC specifications, covering AAA interaction, fragmentation and interworking.

  • “SGi: It is the reference point between the PDN GW and the packet data network.” TS 23.401 v8.18.0
  • “The PDN GW is the gateway which terminates the SGi interface towards the PDN.” TS 23.401 v8.18.0
  • “SGi The reference point between the EPC based PLMN and the packet data network.” TS 29.061 v8.12.0
Rel-10 specification text

For relay node support, SGi is used to carry RN configuration retrieval traffic and is mapped to S1-U of the UE in the DeNB's PGW function, with DSCP/QCI packet mapping.

  • “The RN retrieves initial RN configuration parameters as user plane traffic, across the SGi reference point, from RN OAM” TS 23.401 v10.13.0
  • “the DSCP value used over S1-U of the UE (which is the SGi interface of the PGW function in the DeNB)” TS 23.401 v10.13.0
Rel-11 specification text

TS 29061 added a section and table of Diameter AVPs re-used on the Gi/SGi reference point, including IMEISV passed over Gi and SGi, and removed an SGSN-MCC-MNC item for SGi.

  • “Table 9b lists the Diameter AVPs re-used by the Gi/SGi reference point from existing Diameter Applications” TS 29.061 v11.12.0
  • “IMEISV passed on Gi and SGi Interface” TS 29.061 v11.12.0
Rel-13 specification text

SGi gains support for delivering Non-IP data via point-to-point tunnels (UDP/IP, PMIPv6/GRE, L2TP, GTP-C/U) between the P-GW and the application server, with SGi Non-IP PDN connections handled by the MME.

  • “When support of Non-IP data is provided at the SGi interface, different point-to-point tunneling techniques may be used.” TS 23.401 v13.14.0
  • “The P-GW decides at PDN connection establishment based on pre-configuration which point-to-point tunneling technique is used for the SGi based delivery” TS 23.401 v13.14.0
  • “For uplink Non-IP data, the P-GW forwards the received data to the AS over the SGi PtP tunnel using UDP/IP encapsulation.” TS 23.401 v13.14.0
Rel-14 1 CR

SGi-based Non-IP data delivery was extended in Rel-14: Gi/SGi PtP tunnelling text was corrected, SGi Non-IP PDN support was extended to SGSN and inter-MME/SGSN mobility, and SGi PDN connections for CP-to-UP switching were specified.

  • “The source MME/SGSN shall include this IE on the S10/S3/S16 interface, for a Non-IP PDN Connection, during an inter MME/SGSN mobility procedure” TS 29.274 v14.8.0
  • “Gi/SGi PtP tunnelling based on UDP/IP may be used to deliver Non-IP data to an AS via Gi/SGi.” TS 29.061 v14.4.0
  • Correction to SGi PtP tunnelling based on UDP/IP TS 29.061CR0483
Rel-15 1 CR

Rel-15 adds Reliable Data Service with PtP SGi tunnelling, where the P-GW forwards uplink Non-IP data over an SGi PtP tunnel using UDP/IP, and extends SGi Non-IP PDN connection handling to 5GS interworking.

  • “the P-GW forwards the received data to the AS over the SGi PtP tunnel using UDP/IP encapsulation” TS 23.401 v15.13.0
  • Reliable Data Service with PtP SGi Tunnelling TS 23.401CR3344
  • “Addition of a note that input-packets / output-packets are not reported in SGi signalling with CUPS” TS 29.061 v15.7.0
Rel-16 specification text

SGi gained Ethernet PDN connection support and SGi point-to-point UDP/IP tunnelling for Non-IP PDN type, with a new SGi PtP Tunnel Address IE and extended signalling covering SGi Ethernet PDN connections.

  • “When present, the IE shall contain the IPv4 or IPv6 address, and optionally the UDP port, that is allocated for the SGi PtP tunnel based on UDP/IP.” TS 29.274 v16.13.0
  • “Part of it also applies for PDN Type Non-IP when SGi PtP Tunnelling based on UDP/IP, see clause 4.3.17.8, is used.” TS 23.401 v16.14.0
  • “for transmitting the UE's IP, non-IP or Ethernet data related to a specific application.” TS 24.301 v16.9.0
Rel-17 1 CR

Rel-17 adds support for CUPS across SGi, including L2TP for CUPS across SGi, and a CR adds L2TP support on SGi.

Rel-20 specification text

TS 23.401 in Rel-20 adds PDN GW behaviour at SGi: UDP/IP header restored and forwarded via SGi on uplink, and removed from downlink SGi packets before GTP forwarding over S5/S8.

  • “the PGW restores UDP/IP header and then forwards the packet via SGi” TS 23.401 v20.1.0
  • “When the PDN GW receives downlink packet which is UDP/IP packet from SGi, the PDN GW removes the UDP/IP header” TS 23.401 v20.1.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read