Release Note для Cisco Cisco Packet Data Gateway (PDG)
AAA Changes in Release 15.0
AAA Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
49
New Diameter AVPs on S6b
Applicable Product(s): GGSN, P-GW
To enable virtual APN signaling on S6b, a new vendor-specific AVP “Virtual-APN-Name” has been added to the S6b
dictionary. This optional AVP is included in the AAA message sent over the S6b interface.
dictionary. This optional AVP is included in the AAA message sent over the S6b interface.
New Gy Dictionary to Support LNS/PDSN/HA
Applicable Product(s): HA, PDSN
A new dictionary is created based out of Gy standards for PDSN services and associated with dcca-custom29 in credit-
control group. If this dictionary is configured, then Subscription-Id-Type AVP will be encoded always with the value
"END_USER_IMSI" in the CCR-I message from PDSN.
control group. If this dictionary is configured, then Subscription-Id-Type AVP will be encoded always with the value
"END_USER_IMSI" in the CCR-I message from PDSN.
New Rule Failure Codes
Applicable Product(s): GGSN, HA, HSGW, IPSG, PDSN, P-GW, S-GW
The following two new rule failure codes have been added to Rule-Failure-Code AVP:
INCORRECT_FLOW_INFORMATION
An IP-CAN session is identified by an IPv4 address and/or an IPv6 prefix. When both addresses are assigned
to an IP-CAN session, the PCRF provides PCC rules with flows that include IPv4 addresses or IPv6
prefixes/addresses in the Flow-Description AVP. When only one IP version is supported, the PCC rules only
include IP addresses/prefixes corresponding to the version supported by the IP-CAN session. If PCRF provides
incorrect versions of IP addresses, the PCEF reports a specific error.
to an IP-CAN session, the PCRF provides PCC rules with flows that include IPv4 addresses or IPv6
prefixes/addresses in the Flow-Description AVP. When only one IP version is supported, the PCC rules only
include IP addresses/prefixes corresponding to the version supported by the IP-CAN session. If PCRF provides
incorrect versions of IP addresses, the PCEF reports a specific error.
NO_BEARER_BOUND
If the PCC rule(s) that include the Rule-Activation-Time AVP are bound to a bearer that will require traffic
mapping information to be sent to the UE, the PCEF reports the failure to the PCRF by including the Charging-
Rule-Report AVP with the Rule-Failure-Code set the value “NO_BEARER_BOUND (xx)” for the affected
PCC rule(s) identified by the Charging-Rule-Name AVP in either a CCR or an RAA command.
mapping information to be sent to the UE, the PCEF reports the failure to the PCRF by including the Charging-
Rule-Report AVP with the Rule-Failure-Code set the value “NO_BEARER_BOUND (xx)” for the affected
PCC rule(s) identified by the Charging-Rule-Name AVP in either a CCR or an RAA command.
These new rule failure codes are added in the Gx dictionaries “dpca-custom15” and “r8-gx-standard”.
In addition to this, the name of old rule failure code 9 is changed to MISSING_FLOW_INFORMATION. For 3GPP
Rel.10, rule failure code 9 maps to GW/PCEF_MALFUNCTION.
Rel.10, rule failure code 9 maps to GW/PCEF_MALFUNCTION.
New Schemas and Bulkstats Support for RLF
Applicable Product(s): GGSN, MME, P-GW
New schemas “rlf” and “rlf-detailed” are added to support RLF related bulkstatistic collection. Some bulkstatistic
variables are added to each of these new schemas. For the complete list of variables, see the
variables are added to each of these new schemas. For the complete list of variables, see the
NI-LR Messages on SLg
Applicable Product(s): MME
This feaure implementation involves sending a new server initiated message “Location-Report-Request” on the SLg
interface to inform the LCS client about the UE information (on sLg interface), when an emergency call is received.
interface to inform the LCS client about the UE information (on sLg interface), when an emergency call is received.
RAN Bandwidth Optimization
Applicable Product(s): P-GW