Cisco Cisco Packet Data Gateway (PDG)
GTPP Server Group Configuration Mode Commands
gtpp egcdr ▀
Command Line Interface Reference, StarOS Release 17 ▄
6085
rulebase-max-length rulebase_name_max_length
Specifies the maximum character length of charging rulebase name in LOSDVs of eG- CDR/P-GW-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-GW-
CDR.
Default: None. That is, full (un-truncated) charging rulebase name will go in LOSDVs of eG-CDR/P-GW-
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.
The interval is an integer from 60 through 40000000. Default: Disabled
The interval is 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 eG-
CDR/P-CDRs to the 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.
In 12.3 and earlier releases, when the CLI command
service data flow container is closed.
In 12.3 and earlier releases, when the CLI command
gtpp egcdr service-data-flow threshold
interval
was configured to ‘n’ seconds, the difference between “timeOfFirstUsage” and “timeOfReport” of
LOSDV was always ‘n’ seconds for the LOSDVs closed due to “service-data-flow” threshold. Here,
changeTime of LOSDV was reported incorrectly. It was always timeOfFirstUsage + ‘n’. This does not hold
true when the traffic for a particular content ID was not continuous.
In StarOS release 14.0 and later, when the command
changeTime of LOSDV was reported incorrectly. It was always timeOfFirstUsage + ‘n’. This does not hold
true when the traffic for a particular content ID was not continuous.
In StarOS release 14.0 and later, when the command
gtpp egcdr service-data-flow threshold
interval
is configured to ‘n’ seconds, the difference between “timeOfFirstUsage” and “timeOfReport” of
LOSDV can be any value between 1 and ‘n’ seconds depending on the continuity of traffic. If the traffic is
not continuous, the difference is less than ‘n’ seconds. And if the traffic is continuous the difference will be
‘n’ seconds. When this CLI command is configured in the GTPP Server Group Configuration mode, each
LOSDV will be closed at configured regular interval after the arrival of first packet.
not continuous, the difference is less than ‘n’ seconds. And if the traffic is continuous the difference will be
‘n’ seconds. When this CLI command is configured in the GTPP Server Group Configuration mode, each
LOSDV will be closed at configured regular interval after the arrival of first packet.
service-idle-timeout { 0 | service_idle_timeout}
Specifies a time period during which 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.
and added to eG-CDR/P-CDR (as part of LOSDV container list) with service condition change as
ServiceIdleOut.
0
: Specifies there is no service-idle-timeout trigger.
service_idle_timeout
is an integer from 10 through 86,400. Default: 0
Usage
Use this command to configure individual triggers for eG-CDR/P-CDR generation.
Example