для Cisco Cisco Packet Data Gateway (PDG)
GGSN CDR Field Reference
▀ CDR Fields Supported in eG-CDRs
▄ GTPP Interface Administration and Reference, StarOS Release 19
152
Field
Tag
number
number
Category
Description
Format
Size (in
bytes)
bytes)
ASN1
code
code
FBC data volume
downlink
downlink
34-0-
13
13
M
The number of octets transmitted during the use
of the packet data services in the downlink
direction.
of the packet data services in the downlink
direction.
Integer
1-5
8d
Time of report
34-0-
14
14
M
A time stamp defining the moment when the
service data container is closed.
service data container is closed.
BCD encoded
octet string
octet string
9
8e
RAT Type
34-0-
15
15
O
The valid RAT type during the service data
recording interval.
recording interval.
Integer
1
8f
Failurehandling
Continue
Continue
34-0-
16
16
O
A Boolean expression included if the failure
handling condition has been executed.
handling condition has been executed.
Boolean
1
90
Service Identifier
34-0-
17
17
O
The service identifier may designate an end user
service, a part of an end user service or an
arbitrarily formed group thereof.
service, a part of an end user service or an
arbitrarily formed group thereof.
Integer
1-5
91
Notes:
The subfields included in other fields are marked Mandatory even if the main field is optional. For example, the
list of service containers is optional, but if there is at least one container, then all subfields for the container that
are marked as Mandatory will be included.
are marked as Mandatory will be included.
The field “Served PDP PDN Address Extension”(servedPDPPDNAddressExt) is not part of the 3GPP 32.298
v8.5.0 specification. This field will be available in the CDR only when the CLI command
gtpp attribute
served-pdp-pdn-address-extension
is configured in the GTPP Server Group Configuration Mode. This
field is disabled by default. For more information on this command, refer to the Command Line Interface
Reference.
Reference.
Record Extensions (recordExtensions) is a customer-specific field. This field will be available in the CDR only
when the CLI command
gtpp trigger direct-tunnel
is configured in the GTPP Server Group
Configuration Mode. This field is disabled by default. For more information on this command, refer to the
Command Line Interface Reference.
Command Line Interface Reference.
In releases prior to 14.0, the CGISAIChange service condition is present in LOSDV of GGSN CDR even if ULI
Change trigger is disabled. In 14.0 and later releases, if the ULI Change trigger is disabled and if the ULI is
changed, the CGISAIChange service condition is not present in LOSDV of GGSN CDR.
changed, the CGISAIChange service condition is not present in LOSDV of GGSN CDR.
Rulebase change triggered from any external interface e.g. OCS/PCRF, will generate CDR with closure reason
“Management Intervention”. This change is applicable to all standard dictionaries except for custom42 GTPP
dictionary as it is customized to suppress interim CDR.
dictionary as it is customized to suppress interim CDR.
In releases prior to 16, if there was a LOSDV bucket created between the packet arrival time and service-idle-out
expiry time, no data counts were reported. So, a zero-volume LOSDV was generated for service idle timeout
scenario. In 16 and later releases, if there are no data counts available for a service flow, the LOSDV for
service idle timeout will not be created. The service-idle timeout will be started only when the next data packet
arrives.
scenario. In 16 and later releases, if there are no data counts available for a service flow, the LOSDV for
service idle timeout will not be created. The service-idle timeout will be started only when the next data packet
arrives.
This behavior change is applicable to eG-CDRs and PGW-CDRs for all GTPP dictionaries except custom5 and
custom40 dictionaries.
custom40 dictionaries.