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

Glossary term · Core Network

P-GW

Packet Data Network Gateway

Also written as: PGW

Core Network →

P-GW is the core network node that connects the mobile network to external packet data networks like the internet, performing IP address allocation, policy enforcement, charging, and packet filtering.

Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
33 specs
Also in
Services, Management
P-GW Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Packet Data Network Gateway (P-GW) is a fundamental component of the Evolved Packet Core (EPC) architecture defined in 3GPP Release 8 and beyond. It functions as the primary gateway between the mobile operator's network and external Packet Data Networks (PDNs), such as the public internet, IMS, or private corporate networks. The P-GW is the point of entry and exit for all user plane IP traffic for a UE. It is responsible for assigning the UE an IP address (via DHCP or other mechanisms) and managing the IP bearer context for each data session. The P-GW enforces policy and charging rules received from the Policy and Charging Rules Function (PCRF), applying gating, filtering, and quality-of-service (QoS) marking to packets. It also performs deep packet inspection (DPI) for service-aware charging and policy enforcement.

Architecturally, the P-GW interfaces with several key network elements. On the mobile network side, it connects to the Serving Gateway (S-GW) via the S5/S8 interface (GTP-based or PMIP-based) for user plane traffic and control signaling. The S5 interface is used when the S-GW and P-GW are within the same PLMN, while S8 is used for roaming scenarios between PLMNs. On the external network side, the P-GW connects to PDNs via the SGi interface, which is a standard IP interface. For control plane functions, the P-GW communicates with the PCRF over the Gx interface to receive dynamic policy and charging control (PCC) rules. It also interfaces with Online Charging Systems (OCS) via the Gy interface and Offline Charging Systems (OFCS) via the Gz interface.

A critical role of the P-GW is as an anchor for mobility. When a UE moves between different eNodeBs or even between 3GPP and non-3GPP access networks (like Wi-Fi), the P-GW remains the stable IP point of attachment. This ensures session continuity as the UE's IP address is preserved. The P-GW also supports advanced features like Traffic Detection Function (TDF) for application detection and reporting, and Bearer Binding and Event Reporting Function (BBERF) for non-3GPP accesses. In later 3GPP releases, with the introduction of 5G Core (5GC), many P-GW functions were integrated into the new User Plane Function (UPF), but the P-GW remains central to 4G EPS deployments and is a key element in interworking between 4G and 5G networks.

Purpose & Motivation

The P-GW was created as part of the System Architecture Evolution (SAE) in 3GPP Release 8 to address the limitations of previous 3G packet core architectures, specifically the Gateway GPRS Support Node (GGSN). The GGSN in 2G/3G networks handled similar gateway functions but was part of a less flexible, more monolithic architecture. The EPC, with the P-GW as a distinct entity, introduced a flatter, all-IP architecture designed for higher data throughput, lower latency, and more efficient packet routing. This was essential to support the burgeoning demand for mobile broadband services driven by smartphones and new applications.

The P-GW solves several key problems. It centralizes the policy enforcement and charging functions, allowing operators to implement sophisticated service plans and monetization strategies based on user, application, or network conditions. By acting as the single IP anchor point, it simplifies mobility management and enables seamless handovers between different radio access technologies. Furthermore, its design supports deep packet inspection and service-aware capabilities, which are crucial for implementing parental controls, enterprise VPNs, and optimized traffic management. The separation of the S-GW and P-GW also allowed for more flexible network deployments, where the S-GW could be distributed for latency optimization while the P-GW could be centralized for policy consistency.

What changed in its specifications

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

TS 23.221Rel-18 → Rel-19

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

Full comparison in TS 23.221 →
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 →

Technology family

Core network elements and functions · Core Network

  1. Phase 1 AuC, EIR, GMSC, HLR, IWF, MSC, VLR
  2. Phase 2 SMS-GMSC, SMS-IWMSC
  3. R96 GGSN, SGSN
  4. R99 3G-SGSN, GLR, IM-GSN, IM-MSC
  5. Rel-4 CS-MGW, GMSC Server, MSC Server
  6. Rel-5 HSS, SLF
  7. Rel-6 3GPP AAA Server
  8. Rel-7 PCEF, PCRF
  9. Rel-8 ANDSF, BBERF, ePDG, MME, PGW, SGW
  10. Rel-9 HLR-FE, HSS-FE, UDR
  11. Rel-10 L-GW
  12. Rel-11 TDF
  13. Rel-14 PGW-C, PGW-U, SGW-C, SGW-U, TDF-C, TDF-U
  14. Rel-15 AMF, AUSF, PCF, SMF, SMF+PGW-C, UDM, UPF
  • P-GW decomposed into PGW-C (not stated verbatim in the specifications)
  • P-GW decomposed into PGW-U (not stated verbatim in the specifications)
  • P-GW counterpart in another generation: GGSN
    “the SGSN uses the L-GW address included by HNB in RANAP messages as the GGSN/PGW address to be used” TS 23.060
  • P-GW counterpart in another generation: SMF (not stated verbatim in the specifications)

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 12 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 P-GW is specified for the first time in Rel-8: it provides PDN connectivity, allocates IPv4/IPv6 addresses, enforces APN-AMBR and performs charging via CDRs and online charging.

  • “The P‑GW provides PDN connectivity to both GERAN/UTRAN only UEs and E‑UTRAN capable UEs using any of E‑UTRAN, GERAN or UTRAN.” TS 23.401 v8.18.0
  • “P-GW acts as an access router, and allocates to a UE a globally unique /64 IPv6 prefix if the PLMN allocates the prefix” TS 29.061 v8.12.0
  • “When P-GW provides connectivity to GERAN/UTRAN (P-GW acts as a GGSN) it employs P-GW Charging defined in this specification.” TS 32.251 v8.16.0
Rel-9 specification text

P-GW behaviour was extended in Rel-9: it may initiate RADIUS/Diameter re-authorization for deferred IPv4 allocation, handles CSG information reporting, and ignores the Maximum APN restriction for emergency APN requests.

  • “the P-GW may intiate RADIUS re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease” TS 29.061 v9.16.0
  • “The P-GW shall ignore Maximum APN restriction if the request includes the Emergency APN.” TS 23.401 v9.16.0
  • “the P‑GW shall send an Update Bearer Request message to the S‑GW” TS 23.060 v9.14.0
Rel-10 specification text

P-GW behaviour changed in Rel-10: it handles charging characteristics and PMIP-based charging per IP-CAN session, and relay-node DeNB provides S/P-GW functions; SIPTO GW selection and per-APN congestion handling were also added.

  • “The P-GW shall support the configuration of one set of default Charging Characteristics (i.e. home, visiting, roaming) for each of its supported APNs.” TS 32.251 v10.15.0
  • “DeNB provides the necessary S/P‑GW functions for the operation of RNs connected to the DeNB.” TS 23.401 v10.13.0
  • “l) Mechanisms that permit the GGSN/P-GW to handle per-APN congestion” TS 23.060 v10.14.0
Rel-11 1 CR

P-GW behaviour was extended for trusted WLAN access over S2a: it answers Neighbor Solicitations and sends Router Advertisements to renew IPv6 prefixes, and TWAN becomes an access router for GTP/PMIP S2a.

  • “To renew the allocated IPv6 prefix, the P-GW (GTP based S5/S8) , S-GW (PMIPv6 based S5/S8) or TWAN (GTP/PMIP based S2a) shall send an IPv6 Router Advertisement” TS 29.061 v11.12.0
  • “for GTP/PMIP -based S2a, TWAN acts as an access router.” TS 29.061 v11.12.0
  • Correct description of the impact on P-GW due to SRVCC TS 23.216CR0311
Rel-12 specification text

In Rel-12 the P-GW gained new behaviour: it can request Presence Reporting Area reporting, may authenticate users from PAP/CHAP credentials in PCO/APCO, and handles GTP-C overload information.

  • “The P-GW may also request for each PDP context independently using the Presence Reporting Area Action parameter that the S4-SGSN shall report changes” TS 23.060 v12.11.0
  • “If such information is provided to the P-GW, the P-GW may perform user authentication based on these credentials.” TS 29.061 v12.12.0
  • “GTP-C Overload Control feature allows the Serving GW to send its Overload Control Information to the MME/SGSN and P-GW.” TS 23.401 v12.11.0
Rel-13 specification text

Rel-13 adds P-GW behaviour for Non-IP/CIoT data: transparent forwarding to the AS over SGi PtP tunnels, AS selection, and IP address handling without informing the UE, plus Non-IP charging.

  • “the P-GW shall forward the received data to the AS over the SGi PtP tunnel associated with the GTP-U tunnel” TS 29.061 v13.7.0
  • “A point-to-point tunnel is established by the P-GW towards the AS.” TS 23.401 v13.14.0
  • “The P-GW/S-GW shall support charging for Non-IP PDN connection.” TS 32.251 v13.6.1
Rel-14 specification text

For PRA reporting, the initial UE presence status is now reported only if the PRA is set to inactive by the serving node, with enter/leave reporting stated separately; plain Non-IP tunnelling text only extends to GGSN/PDP context.

  • “if the corresponding Presence Reporting Area(s) is set to inactive by the serving node shall be reported by the P-GW to the OCS for online charging” TS 32.251 v14.4.0
Rel-15 specification text

P-GW gained new behaviour in Rel-15: processing the Reliable Data Service Header for Non-IP data over SGi PtP tunnels, and reporting PRA UE presence status and Secondary RAT volume to OCS/PCRF for charging.

  • “When the Reliable Data Service is enabled, the P-GW processes the Reliable Data Service Header.” TS 23.401 v15.13.0
  • “The UE presence initial status in the PRA(s) at the time of the subscription shall be reported by the P-GW to the OCS” TS 32.251 v15.5.0
  • “Volume reporting for Secondary RAT is an optional capability in the S-GW and P-GW” TS 32.251 v15.5.0
Rel-16 specification text

P-GW behaviour changed: for non-IP/Ethernet-related PDN connections it must now inform the MME of the assigned IP address, and Ethernet PDN type requires a combined PGW+SMF; VoLTE volume-based charging is added.

  • “The P-GW shall inform the MME of the assigned IPv4 address or IPv6 prefix and Interface Identifier for a PDN Connection of a given UE.” TS 23.401 v16.14.0
  • “The support of Ethernet PDN type relies upon the selection of a P-GW that supports combined PGW+SMF functionality” TS 23.401 v16.14.0
  • “Volume based charging for VoLTE services allows the P-GW to collect charging information for VoLTE service.” TS 32.251 v16.0.0
Rel-17 1 CR

Rel-17 changes P-GW related behaviour: a CR addresses PDN connection release for a standalone P-GW in interworking, and TS 32.251 now refers to TS 23.401 for Secondary RAT volume reporting in the S-GW and P-GW.

  • PDN connection release in case of standalone P-GW for interworking TS 24.301CR3580
  • “Use of Secondary RAT refers to options supported by E-UTRAN with dual radio accesses specified in TS 23.401 [208].” TS 32.251 v17.0.0
Rel-18 specification text

P-GW behaviour for packet marking was specified: it must not modify ToS/Traffic Class in downlink packets, and uplink DSCP marking may be based on QCI and optionally ARP priority level.

  • “The P-GW shall not modify the fields Type of Service (IPv4) and Traffic Class (IPv6) of the received downlink packets.” TS 29.061 v18.1.0
  • “the transport level packet marking (e.g. setting the DiffServ Code Point) by the P-GW in the uplink may be based on the QCI” TS 29.061 v18.1.0
Rel-19 1 CR

Rel-19 TS 23.401 adds a new clause and a CR on handling stale PDN sessions at the P-GW, a new P-GW behaviour.

Defining Specifications

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

SpecificationTitleRelease
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.302 vj00 Access to EPC via non-3GPP networks; Stage 3 Rel-19 read
TS 26.233 vf00 3GPP Packet-Switched Streaming Service (PSS) Rel-15 read
TR 26.938 vj00 DASH Deployment Guidelines for 3GPP Networks Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 read
TS 29.468 vj00 MB2 Reference Point Protocol Definition Rel-19 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read
TS 29.804 v801 CT3 Aspects of System Architecture Evolution Rel-8 read
TS 29.806 vc10 P-CSCF Restoration Analysis & Solutions Rel-12 read
TS 29.826 vd10 P-CSCF Restoration Enhancements for WLAN Rel-13 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read
TS 31.829 vd00 ISIM-ME Interface Conformance Requirements Rel-13 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.298 vk10 Charging Data Record Specification Rel-20 read
TS 32.820 v801 Study on Evolved 3GPP Charging Architecture Rel-8 read
TS 32.833 vb00 Fixed-Mobile Convergence Management Study Rel-11 read
TS 33.863 ve20 Security for Battery-Efficient IoT Device to Enterprise Rel-14 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.868 vc00 Study on Group Communication for E-UTRA Rel-12 read
TS 23.214 vj00 Control and User Plane Separation for EPC Rel-19 read
TS 23.380 vk00 IMS Restoration Procedures Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TR 23.799 ve00 Study on Next Generation System Architecture Rel-14 read
TS 23.857 vb00 EPC Node Failure and Restoration Study Rel-11 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TS 29.273 vj20 EPS AAA Reference Points and Procedures Rel-19 read
TS 29.274 vk00 GTPv2-C Control Plane Protocol Rel-20 read
TS 29.281 vj20 GTPv1-U Protocol Specification Rel-19 read
TS 29.303 vk00 DNS Procedures for EPS and 5G Interworking Rel-20 read
TS 32.867 vf10 Management Impacts of EPC CUPS Rel-15 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read