Cisco Cisco Packet Data Gateway (PDG) Documentation Roadmaps
GGSN Support in GPRS/UMTS Wireless Data Services
▀ Features and Functionality - Base Software
▄ Cisco ASR 5000 Series Product Overview
OL-22938-01
Decreases header overhead
Reduces packet loss rate over lossy links
The system supports the Van Jacobson (VJ) IP header compression algorithms by default for subscriber traffic.
The VJ header compression is supported as per RFC 1144 (CTCP) header compression standard developed by V.
Jacobson in 1990. It is commonly known as VJ compression. It describes a basic method for compressing the headers of
IPv4/TCP packets to improve performance over low speed serial links.
Jacobson in 1990. It is commonly known as VJ compression. It describes a basic method for compressing the headers of
IPv4/TCP packets to improve performance over low speed serial links.
By default IP header compression using the VJ algorithm is enabled for subscribers. You can also turn off IP header
compression for a subscriber.
compression for a subscriber.
Important:
For more information on IP header compression support, refer IP Header Compression chapter in
System Enhanced Feature Configuration Guide.
IPv6 Support
Native IPv6 support allows for the configuration of interfaces/routes with IPv6 (128 bit) addressing. The increased
address space allows for future subscriber growth beyond what is currently possible in IPv4. Native IPv6 support on the
Gi interface allows support for packets coming from or destined to a mobile over the Gi interface. IPv6 address
assignment is supported from a dynamic or static pool via standard 3GPP attributes. The GGSN can communicate using
DIAMETER as the transport protocol for Gx to the AAA. Overlapping address space or resource pools are supported if
they are in different VPNs. The VPN subsystem is responsible for the configuration and recovery of IP interfaces and
routes. IP resources are grouped into separate routing domains know as contexts. The VPN subsystem creates and
maintains each context and the resources associated with them. The existing IPv4 model of interface and route
notification will be extended to support IPv6.
address space allows for future subscriber growth beyond what is currently possible in IPv4. Native IPv6 support on the
Gi interface allows support for packets coming from or destined to a mobile over the Gi interface. IPv6 address
assignment is supported from a dynamic or static pool via standard 3GPP attributes. The GGSN can communicate using
DIAMETER as the transport protocol for Gx to the AAA. Overlapping address space or resource pools are supported if
they are in different VPNs. The VPN subsystem is responsible for the configuration and recovery of IP interfaces and
routes. IP resources are grouped into separate routing domains know as contexts. The VPN subsystem creates and
maintains each context and the resources associated with them. The existing IPv4 model of interface and route
notification will be extended to support IPv6.
This feature allows IPv6 subscribers to connect via the GPRS/UMTS infrastructure in accordance with the following
standards:
standards:
RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
RFC 2461: Neighbor Discovery for IPv6
RFC 2462: IPv6 Stateless Address Autoconfiguration
RFC 3314: Recommendations for IPv6 in 3GPP Standards
RFC 3316: Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts
RFC 3056: Connection of IPv6 domains via IPv4 clouds
3GPP TS 23.060: General Packet Radio Service (GPRS) Service description
3GPP TS 27.060: Mobile Station Supporting Packet Switched Services
3GPP TS 29.061: Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based
Services and Packet Data Networks (PDN)
IP version 6 is enhanced version of IP version 4 with following modifications:
Expanded addressing capabilities with 128 bit for address as compared to 32 bits in IPv4.
Header format simplification
Improved support of extensions and options