Cisco Cisco Packet Data Gateway (PDG) Documentation Roadmaps
PDN Gateway Overview
▀ Features and Functionality - Base Software
▄ Cisco ASR 5000 Series Product Overview
OL-22938-01
Support for any combination of IPv4, IPv6 or dual stack IPv4/v6 address assignment from dynamic or static
address pools on the P-GW.
Support for native IPv6 transport and service addresses on PMIPv6 S2a interface. Note that transport on GTP
S5/S8 connections in this release is IPv4 based.
Support for IPv6 transport for outbound traffic over the SGi reference interface to external Packet Data
Networks.
IPv6 transport and interfaces are supported on all of the following connections:
Diameter Gx policy signaling interface
Diameter Gy online charging reference interface
S6b authentication interface to external 3GPP AAA server
Diameter Rf offline charging interface
Lawful Intercept (X1, X2 interfaces)
OSPFv3
MP-BGP v6 extensions
IPv6 flows (Supported on all Diameter QoS and Charging interfaces as well as Inline Services (e.g. ECS)
Source IP Address Validation
Insures integrity between the attached subscriber terminal and the PDN GW by mitigating the potential for unwanted
spoofing or man-in-the-middle attacks.
spoofing or man-in-the-middle attacks.
The P-GW includes local IPv4/IPv6 address pools for assigning IP addresses to UE's on a per-PDN basis. The P-GW
defends its provisioned address bindings by insuring that traffic is received from the host address that it has awareness
of. In the event that traffic is received from a non-authorized host, the P- GW includes the ability to block the non-
authorized traffic. The P-GW uses the IPv4 source address to verify the sender and the IPv6 source prefix in the case of
IPv6.
defends its provisioned address bindings by insuring that traffic is received from the host address that it has awareness
of. In the event that traffic is received from a non-authorized host, the P- GW includes the ability to block the non-
authorized traffic. The P-GW uses the IPv4 source address to verify the sender and the IPv6 source prefix in the case of
IPv6.
Default and Dedicated EPC Bearers
Provides a foundation for contributing towards improved Quality of User Experience (QoE) by enabling deterministic
end-to-end forwarding and scheduling treatments for different services or classes of applications pursuant to their
requirements for committed bandwidth resources, jitter and delay. In this way, each application receives the service
treatment that users expect.
end-to-end forwarding and scheduling treatments for different services or classes of applications pursuant to their
requirements for committed bandwidth resources, jitter and delay. In this way, each application receives the service
treatment that users expect.
In the StarOS 9.0 release, the Cisco EPC core platforms support one or more EPS bearers (default plus dedicated). An
EPS bearer is a logical aggregate of one or more Service Data Flows (SDFs), running between a UE and a P-GW in the
case of a GTP-based S5/S8 interface, and between a UE and HSGW in case of a PMIP-based S2a interface. In networks
EPS bearer is a logical aggregate of one or more Service Data Flows (SDFs), running between a UE and a P-GW in the
case of a GTP-based S5/S8 interface, and between a UE and HSGW in case of a PMIP-based S2a interface. In networks