Cisco Cisco Packet Data Interworking Function (PDIF)
WLAN CDR Field Descriptions
CDR Fields ▀
GTPP Interface Administration and Reference, StarOS Release 17 ▄
397
-- YYMMDDhhssShhmm
-- octet 1..6: local time
-- octet 1: YY .. decade (2 digits BCD non-twisted, readable)
-- octet 2: MM ... month (2 digits BCD non-twisted, readable)
-- octet 3: DD ... day (2 digits BCD non-twisted, readable)
-- octet 4: hh ... hour (2 digits BCD non-twisted, readable)
-- octet 5: mm ... minute (2 digits BCD non-twisted, readable)
-- octet 6: ss ... second (2 digits BCD non-twisted, readable)
-- octet 7..9: … offset to GMT (universal time)
-- octet 7: S ... H'2B: "+" H'2D: "-"(ASCII)
-- octet 8: hh ... hour (2 digits BCD non-twisted, readable)
-- octet 9: mm ... minute (2 digits BCD non-twisted, readable)
Format
BCD encoded octet string
Length
9 bytes
Node ID
This field contains an identifier string for the node that generated the CDR.
On the PDG, this NodeID field is a printable string of the ndddSTRING format:
n: The first digit is the sessmgr restart counter having a value between 0 and 7.
ddd: The number of the sessmgr instance generating the CDR.
STRING: This is a configured node-id-suffix having any string from 1 to16 characters, defined using the
gtpp
attribute node-id
command.
If this node-id-suffix is not configured, the PDG uses the GTPP context name as the node-id-suffix (truncated to 16
characters).
characters).
For WLAN-CDRs, this field is only included when the option
gtpp attribute local-record-sequence number
is configured.
Format
IA5string
Length
5-20 bytes
PDG Address
This field provides the current serving PDG IP address for the Control Plane. The standard 32.298 offers a choice for the
encoding of the address to be either in binary or text format.
encoding of the address to be either in binary or text format.
The PDG encodes the address in binary format and includes the octet string.
Format