Important: Revision history details are not provided for features
introduced before releases 21.2 and N5.5.
release, the feature is enhanced for the gateway to terminate the Gy session
with OCS when there are no active rules that require OCS.
For few subscribers,
Gy session is required only for a short period. After that period, there will
not be any Online Rules for the subscriber. However, Gy session remains active
at the gateway and Online Charging System (OCS) continues to maintain the
With this feature,
gateway terminates the Gy session with OCS when there are no active rules that
Previous Behavior: In
releases prior to 21.3, the CCR-T with volume usage was sent to Gy only on
New Behavior: In 21.3 and
later releases, the CCR-T is sent when the call has no rules (static, dynamic,
and predefined) with online-charging.
works with the customer-specific Gy dictionary. For more information, contact
your Cisco account representative.
How It Works
Following is an
overview of how the feature works:
works with the customer-specific Gy dictionary. There are no CLI commands to
enable or disable the behavior.
CCR-T can be
Dynamic rule when online-charging moves from online to offline.
Dynamic rule when the installed rule had online-charging.
On any of the
above 3 triggers, the CCR-T is sent only when there are no active
static/predefined/dynamic rules with online-charging. Status of the Predefined
rule online-charging at the time of installation is considered.
the volume/time usage as expected.
configuration change for static rules on its own cannot trigger a CCR-T. On
receiving valid triggers (mentioned in Step 2), latest static configuration is
checked for static rules online-charging status.
online-charging status change (change to the "cca charging credit" CLI command
in predefined rule’s charging-action) cannot trigger a CCR-T. On receiving
valid triggers (mentioned in Step 2), Predefined rule online-charging status at
the time of installation is considered. Any run-time modifications regarding
online-charging status are not applicable.
After Gy Session
Termination, new rule installation with online-charging reestablishes Gy
session with new session-ID.
Rule base change
over PCRF/static configuration, continues to work for Dynamic rules which are
retained after rule base change. Predefined rules, by default, are not
Rule Retention Feature enabled, if the predefined rules are retained,
behavior is as mentioned in Step 4.
processed when access side response for all the pending transactions is
This feature is
supported for bearer and call-level Gy. CCR-T on call-level Gy cleans up the Gy
session, however, Subscriber (PDN session) is retained.
CCR-T is sent
with Termination Cause as DIAMETER_LOGOUT.
works as expected after Session Manager Recovery/ICSR. After SessMgr
Recovery/ICSR, session is retained and CCR-T is sent once rules go offline.
works as expected with or without ADC ruledefs.
Gy session is
timeout being fired. In this case, usage is lost.
cannot be established. In this case, usage is lost.