Cisco Cisco Packet Data Gateway (PDG) Wartungshandbuch
New Feature Summary
Generally Available 06-30-2010
1-6
3GPP R7 Gx Interface Support
As defined by the 3GPP standards, the R7 Gx interface is located between the GGSN and
the Policy Decision Function (PDF) / Policy and Charging Rule Function (PCRF). It is a
Diameter-based interface and provides the functions provided earlier by the Gx (R6) and Go
interfaces. Gx interface as part of a Policy / PCC framework allows the operator to have
dynamic policy and charging control, key features when “flat rate” broadband services are
offered. However, it is paramount that the operator maintains control over the available
resources, and provides a fair usage policy to its subscribers, via bandwidth control, quota
management and other mechanisms.
the Policy Decision Function (PDF) / Policy and Charging Rule Function (PCRF). It is a
Diameter-based interface and provides the functions provided earlier by the Gx (R6) and Go
interfaces. Gx interface as part of a Policy / PCC framework allows the operator to have
dynamic policy and charging control, key features when “flat rate” broadband services are
offered. However, it is paramount that the operator maintains control over the available
resources, and provides a fair usage policy to its subscribers, via bandwidth control, quota
management and other mechanisms.
This release supports the following features:
●
PCEF-based bearer binding
●
IMSA support for secondary contexts
●
QoS Negotiation AVP and QoS Upgrade AVP in Gx messages
●
Single repository of ruledefs for all PDP contexts
●
Moving of PCC rules across PDP contexts if indicated by PCRF
●
QoS enforcement per service data flow
●
Bearer identifier value extensible to non-GPRS access type
●
Ability to define static policies to deny and allow based on 5-tuple information; ability to
enable and disable from the PCRF
enable and disable from the PCRF
Bearer ID in Bearer-level QoS Information
In previous releases, in case of PCRF-based binding, when the bearer-level QoS
information was received from PCRF without bearer ID, the UPC request with the change
in QoS was sent to the default bearer.
information was received from PCRF without bearer ID, the UPC request with the change
in QoS was sent to the default bearer.
In this release, this behavior has changed. In case of PCRF-based binding, the bearer ID is
expected as part of the bearer-level QoS information from the PCRF. Otherwise the QoS
information is ignored.
expected as part of the bearer-level QoS information from the PCRF. Otherwise the QoS
information is ignored.
Bearer ID Validation
In previous releases, the bearer ID in the QoS-Information AVP from the PCRF was not
being validated at the PCEF.
being validated at the PCEF.
In this release, the bearer ID is validated and if found to be invalid is ignored.
Failure Handling Action
In StarOS 8.1 and earlier releases, when the failure handling action configured under the
IMSA service is terminate, and if the primary server is down but the secondary server is up
during call establishment, the call is terminated.
IMSA service is terminate, and if the primary server is down but the secondary server is up
during call establishment, the call is terminated.
In this release, this behavior has changed, the call is established with the secondary server.