Руководство По Обслуживанию для Cisco Cisco Packet Data Gateway (PDG)
Generally Available 06-30-2010
GGSN Features in Release 8.1
1-29
The PCC architecture allows operators to perform service-based QoS policy, and
flow-based charging control. In the PCC architecture, this is accomplished mainly by the
Policy and Charging Enforcement Function (PCEF)/Starent Networks GGSN and the Policy
and Charging Rules Function (PCRF).
flow-based charging control. In the PCC architecture, this is accomplished mainly by the
Policy and Charging Enforcement Function (PCEF)/Starent Networks GGSN and the Policy
and Charging Rules Function (PCRF).
For more information see the Gx Interface Support chapter of the System Enhanced Feature
Configuration Guide.
Configuration Guide.
Quad Gig-E Line Card (QGLC) & Link Aggregation
The GGSN now supports the four-port gigabit-Ethernet line card - QGLC. This card will
enable the GGSN to utilize standard-compliant link aggregation. For additional feature
information, see
enable the GGSN to utilize standard-compliant link aggregation. For additional feature
information, see
QGLC
and Link Aggregation feature descriptions in the Common Features
in Release 8.0 section of this chapter.
For details about this new line card, see the Hardware Platform Overview chapter of the
Hardware Installation and Administration Guide.
Hardware Installation and Administration Guide.
GGSN Behavior on QOS Change
The GGSN system now drops uplink/downlink packets when SGSN sends Update PDP
Context request for QOS change with maximum bit rate (MBR) as zero for
conversational/streaming class of services. This is the default behavior and no configuration
required.
Context request for QOS change with maximum bit rate (MBR) as zero for
conversational/streaming class of services. This is the default behavior and no configuration
required.
Secondary GTPP Group and Enable/Disable CDR Archiving
Regulatory requirements in EU require GGSN to send CDRs to both GSS and CGF while
GSS being the billing interface. CDRs sent to CGF should not be buffered and retried in the
event the CGF goes down and later comes back. To support this, a secondary GTPP group
can be configured under APN, and SessMgr duplicates CDRs to both GTPP groups with a
CLI to enable/disable archiving in GTPP group.
GSS being the billing interface. CDRs sent to CGF should not be buffered and retried in the
event the CGF goes down and later comes back. To support this, a secondary GTPP group
can be configured under APN, and SessMgr duplicates CDRs to both GTPP groups with a
CLI to enable/disable archiving in GTPP group.
Configuring Secondary GTPP Group under the APN
This feature enables configuring a secondary GTPP group in the APN. If the secondary
group is configured, when the accounting information is generated, it will also be duplicated
to the specified secondary group. This can serve as a backup of the accounting information
by sending one record to a GSS server and the other to a CGF server or both to either the
GSS/CGF.
group is configured, when the accounting information is generated, it will also be duplicated
to the specified secondary group. This can serve as a backup of the accounting information
by sending one record to a GSS server and the other to a CGF server or both to either the
GSS/CGF.
Enabling/disabling CDR Archiving in GTPP Group
This enables/disables archiving for CGF only. When enabled, once the server is detected to
be down, the request sent to the CGF is purged. Also, the requests generated for the period
when the server is down is purged. If a secondary CGF is configured, new requests are
directed to the secondary CGF while the requests retried with the primary are purged. By
default this is disabled.
be down, the request sent to the CGF is purged. Also, the requests generated for the period
when the server is down is purged. If a secondary CGF is configured, new requests are
directed to the secondary CGF while the requests retried with the primary are purged. By
default this is disabled.