Cisco Cisco ASR 5000
Context Configuration Mode Commands E-H
▀ gtpp egcdr
▄ Command Line Interface Reference, StarOS Release 18
2482
In this release, both current and new framework are functional to enable field defined (customer created)
eGCDR/PGW-CDR generation. By default, the new framework is disabled.
eGCDR/PGW-CDR generation. By default, the new framework is disabled.
rulebase-max-length rulebase_name_max_length
Specifies the maximum character length of charging rulebase name in LOSDVs of eG- CDR/P-CDR.
rulebase_name_max_length
must be an integer from 0 through 63. Zero (0) means the rulebase name is
added as-is.
Default: None. That is, full (un-truncated) charging rulebase name will go in LOSDVs of eG-CDR/P-CDR.
Default: None. That is, full (un-truncated) charging rulebase name will go in LOSDVs of eG-CDR/P-CDR.
service-data-flow threshold { interval interval | volume { downlink bytes [
uplink bytes ] | total bytes | uplink bytes [ downlink bytes ] } }
uplink bytes ] | total bytes | uplink bytes [ downlink bytes ] } }
Configures the thresholds for closing a service data flow container within an eG-CDR/P-CDR.
interval interval
: Specifies the time interval, in seconds, to close the eG-CDR/P-CDR if the
minimum time duration thresholds for service data flow containers satisfied in flow-based charging.
interval
must be an integer from 60 through 40000000.
Default: Disabled
volume { downlink bytes [ uplink bytes ] | total bytes | uplink bytes [
downlink bytes ] }
: Specifies the volume octet counts for the generation of the interim G-
CDR/P-CDRs to service data flow container in FBC.
downlink bytes
: specifies the limit for the number of downlink octets after which the eG-
CDR/P-CDR is closed.
total bytes
: Specifies the limit for the total number of octets (uplink+downlink) after
which the eG-CDR/P-CDR is closed.
uplink bytes
: specifies the limit for the number of uplink octets after which the eG-CDR/P-
CDR is closed.
bytes
must be an integer from 10000 through 400000000.
A service data flow container has statistics for an individual content ID. When the threshold is reached, the
service data flow container is closed.
service data flow container is closed.
service-idle-timeout { 0 | service_idle_timeout }
Specifies a time period where if no data is reported for a service flow, the service container is closed and
added to eG-CDR/P-CDR (as part of LOSDV container list) with service condition change as ServiceIdleOut.
added to eG-CDR/P-CDR (as part of LOSDV container list) with service condition change as ServiceIdleOut.
service_idle_timeout
must be an integer from 10 through 86400.
0
: Specifies no service-idle-timeout trigger.
Default: 0
Usage
Use this command to configure individual triggers for eG-CDR/P-CDR generation.
Use the
Use the
service-data-flow threshold
option to configure the thresholds for closing a service data flow
container within an eG-CDR (eG-CDRs for GGSN and P-CDRs for PGW) during flow-based charging
(FBC). A service data flow container has statistics regarding an individual content ID.
Thresholds can be specified for time interval and for data volume, by entering the command twice (once with
interval and once with volume). When either configured threshold is reached, the service data flow container
will be closed. The volume trigger can be specified for uplink or downlink or the combined total (uplink +
downlink) byte thresholds.
(FBC). A service data flow container has statistics regarding an individual content ID.
Thresholds can be specified for time interval and for data volume, by entering the command twice (once with
interval and once with volume). When either configured threshold is reached, the service data flow container
will be closed. The volume trigger can be specified for uplink or downlink or the combined total (uplink +
downlink) byte thresholds.