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-22937-01
PDP context processing is based on the APN that the subscriber is attempting to access. Templates for all of the possible
APNs that subscribers will be accessing must be configured within the system. Up to 1024 APNs can be configured on
the system.
APNs that subscribers will be accessing must be configured within the system. Up to 1024 APNs can be configured on
the system.
Each APN template consists of parameters pertaining to how PDP contexts are processed such as the following:
Type (IPv4, IPv6, and/or PPP)
Accounting protocol (GTPP or RADIUS
Authentication protocol (CHAP, MSCHAP, PAP, MSID-based)
Charging characteristics (use SGSN-supplied or use configured)
IP address allocation method (static or dynamic)
PDP Context timers
Quality of Service
A total of 11 PDP contexts are supported per subscriber. These could be all primaries, or 1 Primary and 10 secondaries
or any combination of primary and secondary. Note that there must be at least one primary PDP context in order for
secondaries to come up.
or any combination of primary and secondary. Note that there must be at least one primary PDP context in order for
secondaries to come up.
Per APN Configuration to Swap out Gn to Gi APN in CDRs
In order to allow for better correlation of CDRs with the network or application used by the subscriber, a configuration
option has been added to the GGSN replace the Gn APN with the Gi (virtual) APN in emitted G-CDRs.
option has been added to the GGSN replace the Gn APN with the Gi (virtual) APN in emitted G-CDRs.
When virtual APNs are used, the operator can specify via EMS or a configuration command that the Gi APN should be
used in the ―Access Point Name Network Identifier‖ field of emitted G-CDRs, instead of the Gn APN.
used in the ―Access Point Name Network Identifier‖ field of emitted G-CDRs, instead of the Gn APN.
Port Insensitive Rule for Enhanced Charging Service
This feature allows a single host or url rule to be applied to two different addresses, one with and one without the port
number appended. As adding the port to the address is optional, this means that the number of rules could be halved.
number appended. As adding the port to the address is optional, this means that the number of rules could be halved.
Browser applications can sometimes appended the port number to the host or url when sending the host or URL fields.
RFC 2616 for example states that port should be appended but if it is omitted then 80 should be assumed.
RFC 2616 for example states that port should be appended but if it is omitted then 80 should be assumed.
When configuring rules to define the content, as the web browser may provide the port number, even if it is the default
one of 80 for HTTP, then two of each URL are needed.
one of 80 for HTTP, then two of each URL are needed.
Example
This feature provides a means to configure the rule such that the traffic is matched irrespective of the presence of a port
number.
number.
A new configurable has been added to the rulebase configuration that will ignore the port numbers embedded in the
application headers of HTTP, RTSP, SIP, and WSP protocols.
application headers of HTTP, RTSP, SIP, and WSP protocols.