Cisco Cisco Packet Data Gateway (PDG) Wartungshandbuch
Generally Available 06-30-2010
Common Features in Release 9.0
1-7
Gn APN in Gx Messages
In StarOS 8.0, if in the APN configuration both the virtual APN name and Gn APN name
are configured, the virtual APN name is sent in the Gx messages.
are configured, the virtual APN name is sent in the Gx messages.
In this release, if both the virtual APN name and Gn APN name are configured, the Gn APN
name is sent in the Gx messages. In case only the Gn APN name is configured, the Gn APN
name is sent.
name is sent in the Gx messages. In case only the Gn APN name is configured, the Gn APN
name is sent.
Maximum Number of Charging-Rule-Definition AVPs Supported in a
Single CCA
Single CCA
In previous releases, there was no limit check for the number of Charging-Rule-Definition
AVPs (dynamic rules) that are processed in a single Gx CCA command. In StarOS 9.0, the
number of dynamic rules is limited to 100 per Gx message.
AVPs (dynamic rules) that are processed in a single Gx CCA command. In StarOS 9.0, the
number of dynamic rules is limited to 100 per Gx message.
In this release, the following per Gx message limits are applicable:
●
Charging-Rule-Names: 256
●
Charging-Rule-Base-Names: 20
●
Charging-Rule-Definitions: 100
●
Length of Charging-rule-name/base-name: 32
Provisioning of Event Triggers
In this release, whenever the PCRF subscribes to one or more event triggers by using the
RAR command, the PCEF sends the corresponding currently applicable values (e.g.
3GPP-SGSN-Address AVP or 3GPP-SGSN-IPv6-Address AVP, RAT-Type,
3GPP-User-Location-Info, etc.) to the PCRF in the RAA if available, and in this case, the
Event-Trigger AVPs will not be included.
RAR command, the PCEF sends the corresponding currently applicable values (e.g.
3GPP-SGSN-Address AVP or 3GPP-SGSN-IPv6-Address AVP, RAT-Type,
3GPP-User-Location-Info, etc.) to the PCRF in the RAA if available, and in this case, the
Event-Trigger AVPs will not be included.
Rejection of Unauthorized Gx Messages
In StarOS 8.1, if PCRF does not authorize the requested QoS values, the PCEF does not
reject the Gx response messages.
reject the Gx response messages.
In StarOS 9.0, if the PCRF does not authorize the requested QoS values, or if QoS values
previously authorized by the PCRF are not available, the PCEF rejects the Gx messages
from PCRF and the corresponding access side procedure. The Max Uplink/Downlink,
Guaranteed Uplink/Downlink parameters are considered to check whether the QoS values
are authorized or not. Validation is done across all Gx messages.
previously authorized by the PCRF are not available, the PCEF rejects the Gx messages
from PCRF and the corresponding access side procedure. The Max Uplink/Downlink,
Guaranteed Uplink/Downlink parameters are considered to check whether the QoS values
are authorized or not. Validation is done across all Gx messages.