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
48
Present release of P-GW supports SRVCC PS-CS handover. Post handover completion, all dedicated bearers gets
deactivated and the associated rules get deleted by ECS upon release bearer instruction from Session Manager.
However, ECS is unaware of this hand-over situation and also it does not generate any charging rule failure indication
to the Session Manager in response to release bearer indication. Due to this, PCRF is unaware of why a rule is deleted
by PCEF.
deactivated and the associated rules get deleted by ECS upon release bearer instruction from Session Manager.
However, ECS is unaware of this hand-over situation and also it does not generate any charging rule failure indication
to the Session Manager in response to release bearer indication. Due to this, PCRF is unaware of why a rule is deleted
by PCEF.
In this release, a new rule failure code PS_TO_CS_HANDOVER(13) is supported. When an IP-CAN bearer is deleted
due to SRVCC, the PCEF is notifying the PCRF the exact reason for PCC rule deactivation.
due to SRVCC, the PCEF is notifying the PCRF the exact reason for PCC rule deactivation.
When the IP-CAN bearer is terminated due to PS to CS handover, then P-GW sends a Charging Rule Report with rule
failure code set to PS_TO_CS_HANDOVER. The PCEF reports the related PCC rules for this IP-CAN bearer by
including the Rule-Failure-Code AVP set to the value PS_TO_CS_HANDOVER.
failure code set to PS_TO_CS_HANDOVER. The PCEF reports the related PCC rules for this IP-CAN bearer by
including the Rule-Failure-Code AVP set to the value PS_TO_CS_HANDOVER.
LMA-coupled Web Authentication using Gx
Applicable Product(s): P-GW
WebAuth is a standard for authentication to Wireless LAN access. In this method, the subscriber is always redirected to
a Web portal on associating to the WiFi network and is expected to enter his/her credentials into the Web portal. The
subscriber creates a PMIPv6 binding between the Mobile Access Gateway (MAG) and Local Mobility Anchor (LMA)
prior to being redirected to the Web portal. Upon successful validation of the credentials, the subscriber is allowed to
access any website of his/her choice. The subscriber does not have to provide his/her credentials even after a handoff to
another Access Point within the same WiFi access area.
a Web portal on associating to the WiFi network and is expected to enter his/her credentials into the Web portal. The
subscriber creates a PMIPv6 binding between the Mobile Access Gateway (MAG) and Local Mobility Anchor (LMA)
prior to being redirected to the Web portal. Upon successful validation of the credentials, the subscriber is allowed to
access any website of his/her choice. The subscriber does not have to provide his/her credentials even after a handoff to
another Access Point within the same WiFi access area.
For Web authentication, the Subscription-Id and User-Equipment-Info AVPs are populated in the Mobile Link Layer
Identifier Option (LLID) AVP in the Proxy Binding Update (PBU) message from the MAG to the LMA using the S2a
PMIPv6 interface.
Identifier Option (LLID) AVP in the Proxy Binding Update (PBU) message from the MAG to the LMA using the S2a
PMIPv6 interface.
While authorizing the subscriber with PCRF, P-GW sends the User Equipment Info with the MAC address to PCRF
instead of subscription ID.
instead of subscription ID.
Important:
The feature changes are applicable to the r8-gx-standard dictionary.
NAPTR-based Dynamic HSS Discovery
Applicable Product(s): SGSN
In releases prior to R15.0, the SGSN could contact a HSS only through static configuration of the HSS peer end point
through the HSS service. From Release R15.0 onwards, dynamic peer discovery is supported. The HSS address will be
resolved using NAPTR based DNS request-response method. The following commands have to be enabled for dynamic
peer discovery:
through the HSS service. From Release R15.0 onwards, dynamic peer discovery is supported. The HSS address will be
resolved using NAPTR based DNS request-response method. The following commands have to be enabled for dynamic
peer discovery:
In the Context Configuration Mode, the command
diameter endpoint < endpoint_name >
has to be
enabled.
In the Diameter Endpoint Configuration Mode, the command
dynamic-peer-discovery [ protocol {
sctp | tcp } ]
has to be enabled.
In the Diameter Endpoint Configuration Mode, the command
dynamic-peer-realm < realm_name >
has to
be enabled.
In the Diameter Endpoint Configuration Mode, the command
dynamic-peer-failure-retry-count <
no_of_retries >
has to be enabled.
The “realm name” is used for dynamic peer discovery. The “dynamic-peer-failure-retry-count” is used to configure the
number of re-tries in peer discovery.
number of re-tries in peer discovery.