Rx Session Specific Actions

If an Rx session subscribes to Gx changes by including Specific-Action AVP values, and the subscribed Gx data changes, Rx then sends an RAR with the changes. The PCRF then tracks the registered Rx Specific-Action AVP values in the Rx AAR and translates these to the appropriate Gx event triggers in the Event-Trigger AVP to the PCEF, in addition to any associated Event-Triggers provided by the PCC rule provision procedure.

For example, if the Rx RAA subscribes to a PLMN_CHANGE Specific-Action, the MATRIXX PCRF sends a Gx RAR to the PCEF with the corresponding Event_Tigger armed. At some point in the future if the subscribed information changes on the PCEF, the MATRIXX PCRF is notified by a CCA (Update) containing the new value. The PCRF sends the new value to the AF using an Rx RAR. Supported Specific-Action AVP values are:

Support for Specific-Action AVPs includes the following AVPs:
  • 1 — CHARGING_CORRELATION_EXCHANGE (AVP Access-Network-Charging-Identifier and Access-Network-Charging-Address if applicable).
  • INDICATION_OF_LOSS_OF_BEARER (2) — When MATRIXX Engine receives a Gx Update-CCR with a LOSS_OF_BEARER (5) Event-Trigger AVP, it sends an Rx RAR with an INDICATION_OF_LOSS_OF_BEARER (2) Specific-Action AVP.
  • INDICATION_OF_RECOVERY_OF_BEARER (3) — When MATRIXX Engine receives a Gx Update-CCR with a RECOVERY_OF_BEARER (6) Event-Trigger AVP, it sends an Rx RAR with an INDICATION_OF_RECOVERY_OF_BEARER (3) Specific-Action AVP.
  • INDICATION_OF_RELEASE_OF_BEARER (4) — When MATRIXX Engine receives a Gx Update-CCR with a Charging-Rule-Report AVP with Rule-Failure-Code set to RESOURCE_ALLOCATION_FAILURE (10) or PS_TO_CS_HANDOVER (13), it sends an Rx RAR with an INDICATION_OF_RELEASE_OF_BEARER (4) Specific-Action AVP.
  • 6 — IP-CAN_CHANGE (one or more of AVPs IP-CAN-Type, RAT-Type (if applicable), AN-Trusted, and AN-GW-Address (if applicable)).
  • 12 — ACCESS_NETWORK_INFO_REPORT (AVPs Required-Access-Info, 3GPP-User-Location-Info).
  • 16 — PLMN_CHANGE (AVP 3GPP-SGSN-MCC-MNC).

Most values must appear in the initial Rx AAR and might result in an Rx RAR when the requested data is provided to the MATRIXX PCRF and each time it is updated until the Rx session ends. Separately, ACCESS_NETWORK_INFO_REPORT is a one-time specific action that might be requested by any Rx AAR and that results in a one-time Rx RAR for that request. In both cases, the Rx RAR includes the requested data and the Specific-Action values indicating which of the requested data was included.

By default, the PCRF obtains this data by sending Gx RARs to the PCEF including Event-Trigger AVPs with values for the data requested by Rx, in addition to any values provided by the PCC rule provision procedure, which would then trigger Gx CCRs to add or update the requested data. This can be overridden for Specific-Action value CHARGING_CORRELATION_EXCHANGE by answering y to the following create_config.info question:

create_config.info question: Global:Session:Application:Notify:Propagate CHARGING_CORRELATION_EXCHANGE from Rx Specific-Action to Gx Event-Trigger (y/n)?

If you answer y (the default), a Gx RAR with Event-Trigger value CHARGING_CORRELATION_EXCHANGE is sent to request charging correlation data. An answer of n neither sends a Gx RAR for this purpose nor includes this value in a Gx RAR sent for other purposes, although PCEF configuration might allow the MATRIXX PCRF to continue to receive Gx CCRs with that data and then send Rx RARs with that data.

In addition, you can answer y to the following create_config.info question so that MATRIXX Policy Application responds without an error to unsupported Specific-Action AVPs: Global:Session:Application:Notify:Allow unsupported Rx Specific-Actions (y/n)?

When disabled (default), the PCRF responds with an error. When enabled (answer y), the PCRF accepts and acknowledges the message, but does not handle the unsupported action.