CDR Fields

[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]

Steel Belted Radius Carrier 7.0 Reference Guide > Configuring Call Detail Record Accounting > CDR Fields
CDR Fields

CDR fields can be of type Version 1, Version 2, or ASN.1. Table 171 describes the fields that are contained in the CDR and displayed using cdrdump. Table 172 describes the field formats for Version 1 and Version 2 CDRs. Figure 30 describes the field formats for ASN.1 CDRs

NOTE: Use the CdrType field in the [Settings] section of the cdracct.acc file to set the type of CDR file (binary version 1, binary version 2, or ASN.1). See Table 168 for more information.

.

Table 171: CDR Fields

Field Name in CDR Display

Present in Version 1

Present in Version 2 and ASN.1

Field Format

Meaning of Field in cdrdump

RecordType

Yes

Yes

V1/V2: Byte length 1

ASN.1:Integer

Access context of the record. This is always a WLAN context record (W-CDR). The value of this field is always 95.

ServedImsi

Yes

Yes

V1/V2: BCD encoding. Length 8 bytes.

ASN.1:
NumericString

IMSI of the served party, the user. If IMSI is not present or available, this field contains exactly the home operator's MCC+MNC.

ChargingId

Yes

Yes

Integer
length 4

Particular session of the user, together with the GGSN (or AC) address and the Record Sequence Number. Subsequent sessions of a user have a different Charging ID.

GgsnAddress

No

Yes

V2:
IP-Address length 16

ASN.1:
IPv6 Address

Specifies the IP address of the GGSN in IPv6 format; for IPv4 addresses, the first 12 bytes are all 0x0. If the user is not connected with GGSN, then use the Access Controller's IP address.

NasAddress

Yes

Yes

V1/V2:
IP-Address length 16

ASN.1:
IPv6 Address

IP address of the Network Access Server (Access Point in 802.1x and Access Controller in Open System) used for the session. Field is in IPv6 format; for IPv4 addresses, the first 12 bytes are all 0x00.

NasPortType

No

Yes

V2:Integer length 4

ASN.1:
Integer

15=Ethernet, 19=802.11. Defines the port type. Value directly from GSMA Vendor-Specific NAS port type attribute received from NAS.

NasTimeZone

No

Yes

V2:Byte
length 2

ASN.1:
NAS-
TimeZone

Field specifies the time zone and daylight saving usage. First byte indicates Time zone in 15 minutes intervals preceded by + for positive or - for negative from GMT.

2nd byte is daylight saving indication. 1 indicates 1 hour adjustment for Daylight Saving Time. 2 indicates 2 hour adjustment for Daylight Saving Time.

AsAddress

Yes

Yes

V1/V2:
IP-Address length 16

ASN.1:
IPv6 Address

Address of Application Server (AS) that generates the CDR in IPv6 format; for IPv4 addresses, the first 12 bytes are all 0x00.

NodeId

Yes

Yes

V1/V2:
Text length 20

ASN.1:
UTF8String

Distinguished Name of the AS that created the record.

AccessPoint
Name/NasId

Yes

Yes

V1/V2:
Text length 63

ASN.1:
UTF8String

NAS-identifier or other available data concerning the location of access zone. This field can be zero.

ProtocolType

Yes

Yes

V1/V2:
Word length 2

ASN.1:
Protocol-Type

First byte is the PDP type organization (0=ETSI, 1=IETF). Second byte is the PDP type value; for ETSI, valid values are 0 (X.25), 1 (PPP) and 2 (OSP:IHOSS). For IETF valid values are HEX(21) (End User Address information element for IPv4) and HEX(57) (for IPv6).

In OWLAN context, the PDP type organization is always 1=IETF.

MtAddress

Yes

Yes

V1/V2:
IP-Address length 16

ASN.1:
IPv6 Address

IP address of the Mobile Terminal.

IP address of the end user's terminal can be sent in the Framed-IP-Address attribute in Accounting-Requests [RFC2866].

If the Framed-IP-Address attribute is present in Accounting-Request, AS includes that IP address in the MT Address field of CDR.

DataVolume
Uplink

Yes

Yes

Integer
length 4

Number of bytes transmitted from the MT since the opening of the CDR.

DataVolume
Downlink

Yes

Yes

Integer
length 4

Number of bytes transmitted towards the MT since the opening of the CDR

Record
Opening Time

Yes

Yes

V1:
Local time

V2 andASN.1:
UTC

Number of times when the record was opened, that is, when an Accounting-Request with Acct-Status-Type Start (session started) or Interim-Update (partial CDR written) was received. In CDR, the time is AS local time.

ChangeTime

Yes

Yes

V1:
Local time

V2 andASN.1:
UTC

Time when the container was closed, that is, when an Accounting-Request with Acct-Status-Type Stop or Interim-Update was received.
V1: Local time.
V2 and ASN.1:Timestamp

Duration

Yes

Yes

Integer
length 4

Duration of the session in seconds. This value is received from the NAS and is not necessarily the difference between Change Time and Record Opening Time. Use this field as the basis for time-based billing.

CauseFor
RecordClosing

Yes

Yes

V1/V2: Byte length 1

ASN.1:Integer

Reason why the CDR is closed. The valid values for this field are:

0 indicates user logged out, lost service, NAS request, callback, or host request.

1 indicates partial CDR volume threshold exceeded.

2 indicates partial CDR time threshold exceeded.

7 indicates user's session was lost, session timeout, port error, NAS error, NAS reboot, port unneeded, port preempted, port suspended, service unavailable, user error, or idle timeout.

16 indicates Acct-Input/Output-Gigawords counter value has incremented. User has transferred over 2^32 bytes.

20 indicates a management action caused session termination.

Record
Sequence
Number

Yes

Yes

Integer
length 4

Running sequence number starting from 1, which is used to link charging records generated for a given end user's session. Value is incremented for each partial record.

ChargingType

Yes

Yes

V1/V2: Byte length 1

ASN.1:Integer

Charging type is always 8 (normal postpaid record).

Charging
Characteristics

Yes

Yes

V1/V2: Byte length 1

ASN.1:
String

Type of CDR. CDRs are created based on the authentication method. The possible values are 0-EAP-SIM, 1-SMS Fixed fee CDR, 2-SMS Session CDR.

These values are also used in partial CDRs.

Connection
Type

No

Yes

Integer

Identifies the type of connection.

0 indicates direct

7 indicates GGSN

ServedMsIsdn

Yes

Yes

V1/V2: BCD encoding. Length 9 bytes.

ASN.1:
NumericString

Mobile Station ISDN number of the served party.

ChargeableUid
Type

No

Yes

V1/V2: Byte length 1

ASN.1:
Integer

Field specifies the used type of ChargeableUid (Charging Type identifier).

Charging Type identifiers are initially assigned as follows:

00 - reserved

01 - IMSI (example: 1231231231244...)

02 - NAI (example: foo@bar.com)

03 - E.164 (a MSISDN - example: +358405627015)

04 - TMPID (as described in 3GPP TS33.234 Temporary Identity Generation example)

Note: TMPID not supported

The choice of the identifier (IMSI, NAI, or MSISDN) is determined by the value set for ChargeableUserIdInResponse in the simauth.aut file. If more than one value is set, the identifier returned by the NAS is used. Usually, the identifier returned by the NAS is the first in the list of multiple identifiers specified for ChargeableUserIdInResponse in the simauth.aut file.

For more information, see ChargeableUserIdIn Response in Table 174, "simauth.aut [Settings] Fields" .

Also see ChargeableUid Length and ChargeableUid in this table.

ChargeableUid
Length

No

Yes

V1/V2: Byte length 1

ASN.1:
String

Specifies the length of the string in ChargeableUserID.

Valid only if the Charging Type Identifier value is 2.

Also see ChargeableUidType and ChargeableUid in this table.

DomainIndex

Yes

Yes

V1/V2: Byte length 1

ASN.1:
Integer

Location where the domain part starts in the Username and domain field.

V2: Valid only if the Charging Type Identifier value is 2 (NAI).

UserNameAndDomain

Yes

No

Text length 253

Username and realm/domain of the user in NAI format.

ChargeableUid

No

Yes

V1/V2: Integer length 1

ASN.1:
UTF8String

Replaces User Name field in Version 1.

GSMA-specified chargeable user with ChargeableUid
Type and with ChargeableUid
Length. The content string interpretation is based on the ChargeableUidType. (It is either the value of the IMSI, NAI, or MSISDN.)

The choice of the identifier (IMSI, NAI, or MSISDN) is determined by the value set for ChargeableUserIdInResponse in the simauth.aut file. If more than one value is set, the identifier returned by the NAS is used. Usually, the identifier returned by the NAS is the first in the list of multiple identifiers specified for ChargeableUserIdInResponse in the simauth.aut file.

If the NAS fails to return a CUID, the value set for DefaultCUIDType in the cdracct.acc file is used.

For more information, see ChargeableUserIdIn Response in Table 174, "simauth.aut [Settings] Fields" .

Also see ChargeableUidLength and ChargeableUidType in this table.

LocationName

Yes

Yes

V1/V2: Text length 32

ASN.1:
String

Textual description of the WLAN Hot Spot. For example, "London City Airport." Human readable string without mandated format - printable. Attribute can be used:

For string information printed into subscriber's detailed bill

For bilaterally agreed data between operators

The contents are copied directly from GSMA Vendor-Specific Location-Name attribute received from NAS. Possible truncation may be done at the end of the string.

V1: Format is WISPr. Source is WISpr specific attribute Location-Name.

V2 and ASN.1:Format changed from WISPr to IR.61. Source is Vendor Specific Location-Name.

LocationInfo

Yes

Yes

V1/V2: Text length 64

ASN.1:
String

Location-Information attribute:

The ISO 3166 country code is mandatory.

The location identifies the network ("what" is code 3).

Other recommended information includes:

A1 - State, region, province, or prefecture

A2 - County, parish, gun (Korean county), or district

A3 - City or township

NAM - Name (residence, business or office occupant)

Additional location information fields may be defined according to bilateral agreements between operators. The contents are copied directly from the GSMA Vendor-Specific Location-Info attribute received from NAD. Strings may be truncated.

V1: Format is WISPr. Source is WISPr vendor specific attribute: Location-ID.

V2 and ASN.1: Format changed from WISPr to IR.61. Source is WISPr vendor specific attribute: Location-Info.

Visited
OperatorID

Yes

Yes

V1/V2: Text length 8

ASN.1:
String

Formatted ASCII string that has two parts separated with a colon.

GSM:TADIG - Prefix string is "GSM" and the following code is a GSMA assigned TADIG code presented in capital ASCII letters.

REALM:realm - Prefix string is "REALM" and the following code is any valid domain name string that has been acquired from any valid registrar or registry.

The contents are copied directly from GSMA Vendor-Specific Visited-Operator-ID attribute received from NAS. Possible truncation may be done at the end of the string.

V1: Format WISPr. Set to zero.

V2 and ASN.1:Format changed from WISPr to IR.61. Source is Vendor Specific Visitor-Operator-ID.

OperatorName

No

Yes

V1/V2: Text length 128

ASN.1:
String

Contains a formatted ASCII string that has two parts separated with a colon:

GSM:TADIG - Prefix string is "GSM" and the following code is a GSMA assigned TADIG code presented in capital ASCII letters.

REALM:realm - Prefix string is "REALM" and the following code is any valid domain name string that has been acquired from any valid registrar or registry.

The contents are copied directly from GSMA Vendor-Specific Visited-Operator-ID attribute received from NAS. Truncation can be done at the end of the string. The contents are copied directly from GSMA Vendor-Specific Operator- Name attribute received from NAS. Possible truncation can be done at the end of the string.

If both Visited-Operator-ID and Operator-ID are present in the Access-Response, the Visited-Operator-ID is used.

ExChargingId
Length

No

Yes

V1/V2: Text length 1

ASN.1:
Integer

Length of ExternalChargingID attribute. Contains length of ExChargingID. For example, if the value of the ExternalChargingID attribute is 20, the length is 2.

ExChargingId

No

Yes

V1/V2: Text length 1

ASN.1:
String

Value of the RADIUS attribute, Acct-Session-ID.

PDPCharging
Characteristics

No

Yes

V1/V2: Byte length 1

ASN.1:
Integer

Charging type applied to PDP context.

QosTraffic
Class

No

Yes

V1/V2: Byte length 1

ASN.1:
Integer

Quality of Service. Possible values = 0, 1, 2, 3. the default is 255 if no value is present.

PdpAddress

V1/V2: IP Address length 16

ASN.1:IPV-6 Address

UE address on the TTG towards the GGSN. Same as "MT address" specified above in this table.

Field Name in CDR Display	Present in Version 1	Present in Version 2 and ASN.1	Field Format	Meaning of Field in cdrdump
RecordType	Yes	Yes	V1/V2: Byte length 1 ASN.1:Integer	Access context of the record. This is always a WLAN context record (W-CDR). The value of this field is always 95.
ServedImsi	Yes	Yes	V1/V2: BCD encoding. Length 8 bytes. ASN.1: NumericString	IMSI of the served party, the user. If IMSI is not present or available, this field contains exactly the home operator's MCC+MNC.
ChargingId	Yes	Yes	Integer length 4	Particular session of the user, together with the GGSN (or AC) address and the Record Sequence Number. Subsequent sessions of a user have a different Charging ID.
GgsnAddress	No	Yes	V2: IP-Address length 16 ASN.1: IPv6 Address	Specifies the IP address of the GGSN in IPv6 format; for IPv4 addresses, the first 12 bytes are all 0x0. If the user is not connected with GGSN, then use the Access Controller's IP address.
NasAddress	Yes	Yes	V1/V2: IP-Address length 16 ASN.1: IPv6 Address	IP address of the Network Access Server (Access Point in 802.1x and Access Controller in Open System) used for the session. Field is in IPv6 format; for IPv4 addresses, the first 12 bytes are all 0x00.
NasPortType	No	Yes	V2:Integer length 4 ASN.1: Integer	15=Ethernet, 19=802.11. Defines the port type. Value directly from GSMA Vendor-Specific NAS port type attribute received from NAS.
NasTimeZone	No	Yes	V2:Byte length 2 ASN.1: NAS- TimeZone	Field specifies the time zone and daylight saving usage. First byte indicates Time zone in 15 minutes intervals preceded by + for positive or - for negative from GMT. 2nd byte is daylight saving indication. 1 indicates 1 hour adjustment for Daylight Saving Time. 2 indicates 2 hour adjustment for Daylight Saving Time.
AsAddress	Yes	Yes	V1/V2: IP-Address length 16 ASN.1: IPv6 Address	Address of Application Server (AS) that generates the CDR in IPv6 format; for IPv4 addresses, the first 12 bytes are all 0x00.
NodeId	Yes	Yes	V1/V2: Text length 20 ASN.1: UTF8String	Distinguished Name of the AS that created the record.
AccessPoint Name/NasId	Yes	Yes	V1/V2: Text length 63 ASN.1: UTF8String	NAS-identifier or other available data concerning the location of access zone. This field can be zero.
ProtocolType	Yes	Yes	V1/V2: Word length 2 ASN.1: Protocol-Type	First byte is the PDP type organization (0=ETSI, 1=IETF). Second byte is the PDP type value; for ETSI, valid values are 0 (X.25), 1 (PPP) and 2 (OSP:IHOSS). For IETF valid values are HEX(21) (End User Address information element for IPv4) and HEX(57) (for IPv6). In OWLAN context, the PDP type organization is always 1=IETF.
MtAddress	Yes	Yes	V1/V2: IP-Address length 16 ASN.1: IPv6 Address	IP address of the Mobile Terminal. IP address of the end user's terminal can be sent in the Framed-IP-Address attribute in Accounting-Requests `[RFC2866]`. If the Framed-IP-Address attribute is present in Accounting-Request, AS includes that IP address in the MT Address field of CDR.
DataVolume Uplink	Yes	Yes	Integer length 4	Number of bytes transmitted from the MT since the opening of the CDR.
DataVolume Downlink	Yes	Yes	Integer length 4	Number of bytes transmitted towards the MT since the opening of the CDR
Record Opening Time	Yes	Yes	V1: Local time V2 andASN.1: UTC	Number of times when the record was opened, that is, when an Accounting-Request with Acct-Status-Type Start (session started) or Interim-Update (partial CDR written) was received. In CDR, the time is AS local time.
ChangeTime	Yes	Yes	V1: Local time V2 andASN.1: UTC	Time when the container was closed, that is, when an Accounting-Request with Acct-Status-Type Stop or Interim-Update was received. V1: Local time. V2 and ASN.1:Timestamp
Duration	Yes	Yes	Integer length 4	Duration of the session in seconds. This value is received from the NAS and is not necessarily the difference between Change Time and Record Opening Time. Use this field as the basis for time-based billing.
CauseFor RecordClosing	Yes	Yes	V1/V2: Byte length 1 ASN.1:Integer	Reason why the CDR is closed. The valid values for this field are: 0 indicates user logged out, lost service, NAS request, callback, or host request. 1 indicates partial CDR volume threshold exceeded. 2 indicates partial CDR time threshold exceeded. 7 indicates user's session was lost, session timeout, port error, NAS error, NAS reboot, port unneeded, port preempted, port suspended, service unavailable, user error, or idle timeout. 16 indicates Acct-Input/Output-Gigawords counter value has incremented. User has transferred over 2^32 bytes. 20 indicates a management action caused session termination.
Record Sequence Number	Yes	Yes	Integer length 4	Running sequence number starting from 1, which is used to link charging records generated for a given end user's session. Value is incremented for each partial record.
ChargingType	Yes	Yes	V1/V2: Byte length 1 ASN.1:Integer	Charging type is always 8 (normal postpaid record).
Charging Characteristics	Yes	Yes	V1/V2: Byte length 1 ASN.1: String	Type of CDR. CDRs are created based on the authentication method. The possible values are 0-EAP-SIM, 1-SMS Fixed fee CDR, 2-SMS Session CDR. These values are also used in partial CDRs.
Connection Type	No	Yes	Integer	Identifies the type of connection. 0 indicates direct 7 indicates GGSN
ServedMsIsdn	Yes	Yes	V1/V2: BCD encoding. Length 9 bytes. ASN.1: NumericString	Mobile Station ISDN number of the served party.
ChargeableUid Type	No	Yes	V1/V2: Byte length 1 ASN.1: Integer	Field specifies the used type of ChargeableUid (Charging Type identifier). Charging Type identifiers are initially assigned as follows: 00 - reserved 01 - IMSI (example: 1231231231244...) 02 - NAI (example: foo@bar.com) 03 - E.164 (a MSISDN - example: +358405627015) 04 - TMPID (as described in 3GPP TS33.234 Temporary Identity Generation example) Note: TMPID not supported The choice of the identifier (IMSI, NAI, or MSISDN) is determined by the value set for `ChargeableUserIdInResponse` in the simauth.aut file. If more than one value is set, the identifier returned by the NAS is used. Usually, the identifier returned by the NAS is the first in the list of multiple identifiers specified for `ChargeableUserIdInResponse` in the simauth.aut file. For more information, see `ChargeableUserIdIn Response` `in` Table 174, "simauth.aut [Settings] Fields" . Also see ChargeableUid Length and `ChargeableUid` in this table.
ChargeableUid Length	No	Yes	V1/V2: Byte length 1 ASN.1: String	Specifies the length of the string in ChargeableUserID. Valid only if the Charging Type Identifier value is 2. Also see `ChargeableUidType` and `ChargeableUid` in this table.
DomainIndex	Yes	Yes	V1/V2: Byte length 1 ASN.1: Integer	Location where the domain part starts in the Username and domain field. V2: Valid only if the Charging Type Identifier value is 2 (NAI).
UserNameAndDomain	Yes	No	Text length 253	Username and realm/domain of the user in NAI format.
ChargeableUid	No	Yes	V1/V2: Integer length 1 ASN.1: UTF8String	Replaces User Name field in Version 1. GSMA-specified chargeable user with ChargeableUid Type and with ChargeableUid Length. The content string interpretation is based on the ChargeableUidType. (It is either the value of the IMSI, NAI, or MSISDN.) The choice of the identifier (IMSI, NAI, or MSISDN) is determined by the value set for `ChargeableUserIdInResponse` in the simauth.aut file. If more than one value is set, the identifier returned by the NAS is used. Usually, the identifier returned by the NAS is the first in the list of multiple identifiers specified for `ChargeableUserIdInResponse` in the simauth.aut file. If the NAS fails to return a CUID, the value set for DefaultCUIDType in the cdracct.acc file is used. For more information, see `ChargeableUserIdIn Response` `in` Table 174, "simauth.aut [Settings] Fields" . Also see `ChargeableUidLength` and `ChargeableUidType` in this table.
LocationName	Yes	Yes	V1/V2: Text length 32 ASN.1: String	Textual description of the WLAN Hot Spot. For example, "London City Airport." Human readable string without mandated format - printable. Attribute can be used: For string information printed into subscriber's detailed bill For bilaterally agreed data between operators The contents are copied directly from GSMA Vendor-Specific Location-Name attribute received from NAS. Possible truncation may be done at the end of the string. V1: Format is WISPr. Source is WISpr specific attribute Location-Name. V2 and ASN.1:Format changed from WISPr to IR.61. Source is Vendor Specific Location-Name.
LocationInfo	Yes	Yes	V1/V2: Text length 64 ASN.1: String	Location-Information attribute: The ISO 3166 country code is mandatory. The location identifies the network ("what" is code 3). Other recommended information includes: A1 - State, region, province, or prefecture A2 - County, parish, gun (Korean county), or district A3 - City or township NAM - Name (residence, business or office occupant) Additional location information fields may be defined according to bilateral agreements between operators. The contents are copied directly from the GSMA Vendor-Specific Location-Info attribute received from NAD. Strings may be truncated. V1: Format is WISPr. Source is WISPr vendor specific attribute: Location-ID. V2 and ASN.1: Format changed from WISPr to IR.61. Source is WISPr vendor specific attribute: Location-Info.
Visited OperatorID	Yes	Yes	V1/V2: Text length 8 ASN.1: String	Formatted ASCII string that has two parts separated with a colon. GSM:TADIG - Prefix string is "GSM" and the following code is a GSMA assigned TADIG code presented in capital ASCII letters. REALM:realm - Prefix string is "REALM" and the following code is any valid domain name string that has been acquired from any valid registrar or registry. The contents are copied directly from GSMA Vendor-Specific Visited-Operator-ID attribute received from NAS. Possible truncation may be done at the end of the string. V1: Format WISPr. Set to zero. V2 and ASN.1:Format changed from WISPr to IR.61. Source is Vendor Specific Visitor-Operator-ID.
OperatorName	No	Yes	V1/V2: Text length 128 ASN.1: String	Contains a formatted ASCII string that has two parts separated with a colon: GSM:TADIG - Prefix string is "GSM" and the following code is a GSMA assigned TADIG code presented in capital ASCII letters. REALM:realm - Prefix string is "REALM" and the following code is any valid domain name string that has been acquired from any valid registrar or registry. The contents are copied directly from GSMA Vendor-Specific Visited-Operator-ID attribute received from NAS. Truncation can be done at the end of the string. The contents are copied directly from GSMA Vendor-Specific Operator- Name attribute received from NAS. Possible truncation can be done at the end of the string. If both Visited-Operator-ID and Operator-ID are present in the Access-Response, the Visited-Operator-ID is used.
ExChargingId Length	No	Yes	V1/V2: Text length 1 ASN.1: Integer	Length of ExternalChargingID attribute. Contains length of ExChargingID. For example, if the value of the ExternalChargingID attribute is 20, the length is 2.
ExChargingId	No	Yes	V1/V2: Text length 1 ASN.1: String	Value of the RADIUS attribute, Acct-Session-ID.
PDPCharging Characteristics	No	Yes	V1/V2: Byte length 1 ASN.1: Integer	Charging type applied to PDP context.
QosTraffic Class	No	Yes	V1/V2: Byte length 1 ASN.1: Integer	Quality of Service. Possible values = 0, 1, 2, 3. the default is 255 if no value is present.
PdpAddress			V1/V2: IP Address length 16 ASN.1:IPV-6 Address	UE address on the TTG towards the GGSN. Same as "MT address" specified above in this table.

[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]