Cisco Cisco Tunnel Terminating Gateway (TTG)
Policy Control Configuration Mode Commands
▀ re-auth-trigger
▄ Command Line Interface Reference, StarOS Release 16
7882
Network-Charging-Identifier-Gx AVP. The Charging-Correlation-Indicator AVP with the value
CHARGING_IDENTIFIER_REQUIRED will be provided.
When used in a CCR command, this value indicates that an access network charging identifier has been
assigned. The actual value will be reported through the Access-Network-Charging-Identifier-Gx AVP.
In releases prior to 15.0, the Access-Network-Charging-Identifier-Gx AVP was always included in CCR-
I/CCR-U messages sent from the system to PCRF and contains default bearer's charging ID. Now in 15.0 and
later releases, it is sent only if the event trigger “CHARGING_CORRELATION_EXCHANGE (28)” is
enabled and a new AVP “Charging-Correlation-Indicator 0 (identifier required) is sent by PCRF to the
system. This behavioral change is introduced to conform to the 3GPP TS 29.212 V10.5.0, and it is important
to be noted that this CLI command helps to retain the old behavior, that is, send the Access-Network-
Charging-Identifier-Gx AVP in all CCR messages.
PCRF can install the event trigger (28) and request for the charging correlation while installing/modifying a
dynamic rule in RAR/CCA. PCRF can install the trigger and request for charging correlation alone without
modifying the rule in RAR/CCA message.
Earlier, this AVP “Access-Network-Charging-Identifier-Gx” was included in the RAA message. But, in 15.0
and later releases, this AVP is not sent in RAA but a new CCR-U is triggered if the system receives
Charging-Correlation-Indicator AVP in RAR message and the trigger is enabled.
CHARGING_IDENTIFIER_REQUIRED will be provided.
When used in a CCR command, this value indicates that an access network charging identifier has been
assigned. The actual value will be reported through the Access-Network-Charging-Identifier-Gx AVP.
In releases prior to 15.0, the Access-Network-Charging-Identifier-Gx AVP was always included in CCR-
I/CCR-U messages sent from the system to PCRF and contains default bearer's charging ID. Now in 15.0 and
later releases, it is sent only if the event trigger “CHARGING_CORRELATION_EXCHANGE (28)” is
enabled and a new AVP “Charging-Correlation-Indicator 0 (identifier required) is sent by PCRF to the
system. This behavioral change is introduced to conform to the 3GPP TS 29.212 V10.5.0, and it is important
to be noted that this CLI command helps to retain the old behavior, that is, send the Access-Network-
Charging-Identifier-Gx AVP in all CCR messages.
PCRF can install the event trigger (28) and request for the charging correlation while installing/modifying a
dynamic rule in RAR/CCA. PCRF can install the trigger and request for charging correlation alone without
modifying the rule in RAR/CCA message.
Earlier, this AVP “Access-Network-Charging-Identifier-Gx” was included in the RAA message. But, in 15.0
and later releases, this AVP is not sent in RAA but a new CCR-U is triggered if the system receives
Charging-Correlation-Indicator AVP in RAR message and the trigger is enabled.
Example
The following command enables the CHARGING_CORRELATION_EXCHANGE event trigger.
re-auth-trigger charging-correlation-exchange