Configuring Ha/Pdsn Rel. 8 Gx Interface Support - Cisco ASR 5x00 Administration Manual

▀ Rel. 8 Gx Interface
Step Description
6 DPCA sends a CCR initial message to the selected PCRF.
7 PCRF may send preconfigured charging rules in CCA. The dynamic rules and the authorized QoS parameters could also be
included by the PCRF.
8 DPCA passes the charging rule definition, charging rule install, QoS information received from the PCRF, event triggers,
etc. IMSA stores the information.
9 DPCA calls the callback function registered with it by IMSA.
10 PCRF-provided information common to the entire IP-CAN session (event trigger, primary/secondary OCS address, etc.) is
stored within the IMSA. After processing the information, IMSA notifies the SessMgr about the policy authorization
complete.
11 If the validation of the rules fails in IMSA/DPCA, a failure is notified to PCRF containing the Charging-Rule-Report AVP.
Else, IMSA initiates creation of ECS session. The primary/secondary OCS server address, etc. are sent to the ECS from the
SessMgr.
12 ECS performs credit authorization by sending CCR(I) to OCS with CC-Request-Type set to INITIAL_REQUEST to open
the credit control session. This request includes the active Rulebase-Id (default rulebase ID from the AAA).
13 OCS returns a CCA initial message that may activate a statically configured Rulebase and may include preemptive quotas.
14 ECS responds to SessMgr with the response message.
15 SessMgr requests IMSA for the dynamic rules.
16 IMSA sends the dynamic rules to SessMgr.
Note that, in 14.0 and later releases, the RAR messages are allowed before the session is established. In earlier releases,
until the MIP session is established, all RAR messages from the PCRF were rejected.
Also note that, in 14.0 and later releases, the RAR message is rejected and RAA is sent with 3002 result code when the
recovery of dynamic rule information and audit of Session Manager are in progress. Earlier, the RAR messages were
processed by DPCA even when the recovery audit was in progress.
17 SessMgr sends the dynamic rule information to the ECS. The gate flow status information and the QoS per flow (charging
rule) information are also sent in the message.
18 ECS activates the predefined rules received, and installs the dynamic rules received. Also, the gate flow status and the QoS
parameters are updated by ECS as per the dynamic charging rules. The Gx rulebase is treated as an ECS group-of-ruledefs.
The response message contains the Charging Rule Report conveying the status of the rule provisioning at the ECS.
19 If the provisioning of rules fails partially, the context setup is accepted, and a new CCR-U is sent to the PCRF with the
Charging-Rule-Report containing the PCC rule status for the failed rules. If the provisioning of rules fails completely, the
context setup is rejected.
20 Depending on the response for the MIP Session Authorization, SessMgr sends the response to the UE and activates/rejects
the call. If the Charging-Rule-Report contains partial failure for any of the rules, the PCRF is notified, and the call is
activated. If the Charging-Rule-Report contains complete failure, the call is rejected.

Configuring HA/PDSN Rel. 8 Gx Interface Support

To configure HA/PDSN Rel. 8 Gx Interface functionality:
1. At the context level, configure IMSA service for IMS subscribers as described in the
Authorization Service at Context Level
▄ Cisco ASR 5x00 Packet Data Network Gateway Administration Guide
314
section.
Gx Interface Support
Configuring IMS