> WLAN CDR Field Reference Tables
> The PDG/TTG provides CDRs that are compliant with the definitions in 3GPP TS32.298. When modifications are required, changes to the standard behavior can be implemented in different dictionaries which can be selected in the configuration file. This provides the flexibility to adapt to a customer’s needs, and therefore, to a legacy post-processing billing interface, while retaining the standard behavior.
> Configure GTPP dictionaries with the gtpp dictionary command in the Context Configuration Mode of the system’s command line interface (CLI).
> The Category column in all tables use key described in the following table.
> Dictionary Table Key

> Abbreviation | Meaning | Description
> M | Mandatory | A field that must be present in the CDR.
> C | Conditional | A field that must be in a CDR if certain conditions are met.
> O | Operator Provisonable: Mandatory | A field that an operator has provisioned and must be included in the CDR for all conditions.
> O | Operator Provisionable: Conditional | A field that an operator has provisioned that must be included in the CDR if certain conditions are met.

> ‌
> CDR Fields Supported in WLAN CDRs
> The table in this section lists the WLAN fields present in GTPP dictionaries.
> standard, and custom1 - custom6 Dictionaries
> WLAN CDR fields for TS 32.252

> Field | Category | Description
> Record Type | M | This field identifies the type of record. The 3GPP 32298 does not define any values for record type. This value is selected as this is not yet reserved by any CDRs.
> Network Initiated PDP Context | O | This field indicates that the PDP context was network-initiated. The field is missing in case of UE-activated PDP context.
> Served IMSI | M | This field contains the International Mobile Subscriber Identity (IMSI) of the served party. The IMSI is formatted in accordance with 3GPP TS 23.003.
> PDG Address | M | This field provides the current service PDG IP address for the control plane.
> PDG IPv4 Binary Address | M | The octet string included in the field described above includes the address of the PDG service in binary coding.
> Charging ID | M | This field is a charging identifier, which can be used with the PDG address to identify all records produced in the PDG involved in a single PDP context. The charging ID is generated by the PDG at PDP context activation.
> Serving WAG Address | M | This field provides the current serving WAG IP address for the control plane.
> Serving WAG IPv4 Binary Address | M | The octet string included in the filed described above includes the address of the PDG service in binary coding.
> Access Point Name Network Identifier | M | This field contains the Network Identifier part of the Access Point Name (APN). It is provided by WMN during the IPSec or SSL establishment procedure.
> PDP Type | O | This field defines the PDG type: IP or PPP.
> Served WLAN PDP Address | M | This field contains the PDP address of the served IMSI. The standard 3GPP TS 32.298 allows a choice of either IPAddress or ETSIAddress.
> WLAN UE Remote Address | M | Only the choice of IPAddress is supported by the PDG for the field described above.
> WLAN UE Remote IPv4 Binary Address | M | The octet string included in the field WLAN UE Remote Address includes the IPv4 address assigned to the subscriber by the PDG in binary coding.
> Dynamic Address Flag | O | This field indicates that the PDP address has been dynamically allocated for that particular PDP context. This field is missing if the address is static, that is, part of the PDP context subscription.
> List of Traffic Data Volumes | M | This list includes one or more Traffic Data Volume containers. The number of containers is configurable with a maximum of 4 for WLAN CDRs.
> Change of Charging Condition | M | One traffic data volume container contains a list of change of charging conditions: Data Volume Uplink, Data Volume Downlink, Change Condition, Change Time, Failurehandling Continue. The QoS values may only be included in the first container. In later containers, the presence depends on what was changed.
> QoS Negotiated | O | QoS Negotiated indicates that the applied QoS was accepted by the network. Field is compliant with 3GPP standards.
> GPRS Uplink Data Volume | M | Data Volume Uplink includes the number of octets transmitted during the use of the packet data services in the uplink direction. Note that a maximum of 2^32 bytes can be counted in this field. A volume trigger should be defined for this value to avoid an overflow, if not already done for a smaller amount of traffic.
> GPRS Downlink Data Volume | M | Data Volume Downlink includes the number of octets transmitted during the use of the packet data services in the downlink direction. Note that a maximum of 2^32 bytes can be counted in this field. A volume trigger should be defined for this value to avoid an overflow, if not already done for a smaller amount of traffic.
> Change Condition | M | Change Condition defines the reason for closing the container, such as tariff time change, QoS change, or closing of the CDR. Values according to TS 32.998 are: qoSChange = 0, tariffTime = 1, recordClosure = 2.
> Change Time | M | A time stand that defines the moment when the volume container or the CDR is closed.
> Record Opening Time | M | This field contains the time stamp of when the PDP context was activated in the PDG or when a subsequent record was opened after a partial record. The timestamp is based on the internal timer which has an accuracy of 10ms. Depending on the configured mechanism, this is translated into a timestamp that shows only the full seconds.
> Duration | M | This field contains the duration in seconds of the PDP contexts with the range of 0 to 4294967295. It is the duration from Record Opening Time to record closure. For partial records, this is the duration of the individual partial record and not the cumulative duration.
> Cause for Record Closing | M | This field shows the reason for the release of the CDR. The values are:
> • | normalRelease = 0
> • | abnormalRelease = 4
> • | volumeLimit = 16
> • | timeLimit = 17
> • | maxChangeCond = 19
> • | managmenetIntervention = 20
> Diagnostics | O | This field is included in the CDR when the PDP context is released and when the option gtpp-attribute diagnostics is configured.
> gsm0408Cause | M | The cause is used in the Diagnostics field and contains one of the following values: The PDP context is terminated gracefully = 36 AAA server disconnect = 40 The PDG sends delete PDP context request for any other reason = 26
> Record Sequence Number | O | A running sequence number with range 1 to 4294967295 that links partial records generated by the PDG for a specific PDP context (characterized with the same Charging ID and PDG address pair). This field is not present if the first record is also the final record.
> Node ID | O | This field contains an identifier string for the node that generated the CDR. The 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: A configured Node-ID-Suffix string of 1 to 16 characters. Defined with the gtpp attribute node-id command.
> recordExtensions | O |
> Local Record Sequence Number | O | For each Node ID, this number, with range 1 to 4294967295, is allocated sequentially for each CDR. With the Mode ID, it uniquely identifies a CDR. For WLAN-CDRs, this field is only included when the option gtpp attribute local-record-sequence number is configured.
> APN Selection Mode | O | An index that shows how the APN was selected:
> • | 0 = MS or network provided APN, subscribed verified.
> • | 1 = MS provided APN, subscription not verified.
> • | 2 = Network provided APN, subscription not verified.
> Served MSISDN | O | This field tracks the Mobile Station (MS) ISDN number (MSISDN) of the subscriber. Sent by the AAA server.
> Charging Characteristics | M | Lists the charging characteristics applied to the PDP context. The PDG can accept charging characteristics from the AAA server or use its own configured value. PDG-configured charging characteristics are specified as part of the PDG Service and are applied for WLAN CDRs to subscriber PDP contexts through APN templates.
> Charging Characteristics Selection Mode | O | Lists the charging characteristic type that the PDP applied to the CDR. The values for this field are defined in 3GPP TS 32.298:
> • | AAA supplied: The PDG is using the charging characteristics supplied by the AAA server. AAASupplied = 0
> • | Home default: Home subscriber PDG-configured charging characteristics. homeDefault = 3
> • | Roaming default: Roaming subscriber PDG-configured charging characteristics. roamingDefault = 4
> • | Visiting default: Visiting subscriber PDG-configured charging characteristics. visitingDefault = 5
> WAG PLMN Identifier | O | The WAG PLMN identifier (MSS and MNC) used during this record.
> Rat Type | O | This field shows the Radio Access Technology (RAT) type currently used by the Mobile Station. The field is present in the CDR if provided by WLAN:
> • | 0 = Reserved
> • | 1 = UTRAN
> • | 2 = GERAN
> • | 3 = WLAN

> ‌

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883