> SGW-CDR Field Descriptions
> This chapter lists and describes the fields supported by the system for use in S-GW charging data records (SGW-CDRs).
> The following information is provided for each field:

> • | Description: The field’s description.

> • | Format: The field’s data format.

> • | Length: The field’s size, in bytes.

> All SGW-CDRs are encoded using the ASN.1 format and are sent to the charging gateway function (CGF) using the GPRS Tunneling Protocol Prime (GTPP) as defined in the following standards:

> • | 3GPP TS 29.060

> • | 3GPP TS 32.015

> • | 3GPP TS 32.215

> • | 3GPP TS 32.251 (v 8.5.0, v 8.6.0, v 8.8.0)

> • | 3GPP TS 32.298 (v 8.4.0, v 8.5.0, v 8.7.0) (SGW-CDRs)

> Also see the SGW-CDR Field Reference Tables chapter for information on CDR fields supported in SGW-CDRs.
> Important: The behavior for several of the fields supported in CDRs can be modified. For more information, refer to the gtpp attributes command in the Command Line Interface Reference.
> CDR Fields
> Access Point Name Network Identifier
> This field contain the Network Identifier part of the Access Point Name (APN). This APN is sent to the S-GW by the MME and is relayed to the P-GW in the Create PDP Context Request message.
> Format
> IA5string
> Length
> 1-63 bytes
> APN Selection Mode
> An index indicating how the APN was selected.
> The following APN selection mode indexes are possible:
> 0: MS or network provided APN, subscribed verified
> 1: MS provided APN, subscription not verified
> 2: Network provided APN, subscription not verified.
> Format
> Enumerated
> Length
> 1 byte
> Cause for Record Closing
> This field contains a reason for the closure of the CDR.
> Supported values:
> --
> -- In PGW-CDR and SGW-CDR the value servingNodeChange is used for partial record
> -- generation due to Serving Node Address list Overflow
> -- In SGSN servingNodeChange indicates the SGSN change
> --
> -- LCS related causes belong to the MAP error causes acc. TS 29.002
> --
> -- cause codes 0 to 15 are defined 'CauseForTerm' (cause for termination)
> --
> normalRelease (0),
> abnormalRelease (4),
> volumeLimit (16),
> timeLimit (17),
> servingNodeChange (18),
> maxChangeCond (19),
> managementIntervention (20),
> rATChange (22),
> mSTimeZoneChange (23),
> Format
> Integer
> Length
> 1 byte
> Charging Characteristics
> Lists the charging characteristics applied to the PDP context by the S-GW. The S-GW shall accept the charging characteristics from the MME or use its own configured values.
> Format
> Octet string
> Length
> 2 bytes
> Charging Characteristics Selection Mode
> This field specifies how the Charging Characteristics was selected.
> Supported values:
> servingNodeSupplied (0),
> homeDefault (3),
> roamingDefault (4),
> visitingDefault (5)
> Format
> Enumerated
> Length
> 1 byte
> Charging ID
> This field is a charging identifier, which can be used together with the P-GW address to identify all records involved in a single bearer context. The Charging ID is generated by the P-GW during bearer context activation and is transferred to the context requesting SGW.
> Format
> Integer
> Length
> 1-5 bytes
> Diagnostics
> This field is included in the CDR when the bearer context is released and when the option “gtpp attribute diagnostics” is configured. Only the choice of “gsm0408Value” is used (see below).
> Format
> Choice (gsm0408 only).
> Length
> 3 bytes
> gsm0408Cause
> Refer to TS 24.008 for more information.
> Format
> Integer
> Length
> Always included when the optional Diagnostics field is included.
> Duration
> This field contains the duration in seconds for the record. For partial records, only the interval described by the recordOpeningTime and the last ChangeTime in the ListOfTrafficVolumes is counted. The value is reset for each new partial CDR. This value is converted from the internal representation in milliseconds to an integer value representing only seconds. The mechanism for this conversion (ceiling, floor, round-off) can be configured.
> Format
> Integer
> Length
> 1-5 bytes
> Dynamic Address Flag
> This field indicates that PDN address has been dynamically allocated for that particular IP CAN bearer (PDN connection). This field is missing if address is static. Dynamic address allocation might be relevant for charging e.g. as one resource offered and possible owned by network operator. The presence of this field indicates that the Served PDP Address was dynamically assigned during context activation.
> Format
> Boolean
> Length
> 1 byte
> List of Traffic Data Volumes
> This list includes one or more Traffic Volume containers related to a “Change of Charging Condition”. The maximum number of containers is configurable.
> Format
> Sequence
> Length
> Variable
> GPRS Uplink data volume
> The Data Volume GPRS Uplink field is a part of the ChangeOfCharCondition element in the List of Traffic Volumes. It includes the number of octets received in the uplink direction during the timeframe specified by the container. For each new container, the counter is reset and does not accumulate.
> The data counted already includes the IP PDP bearer protocols i.e. IP or PPP.
> Format
> Integer
> Length
> 1-5 bytes
> GPRS Downlink data volume
> The Data Volume GPRS Downlink field is a part of the ChangeOfCharCondition element in the List of Traffic Volumes. It includes the number of octets transmitted in the downlink direction during the timeframe specified by the container. For each new container, the counter is reset and does not accumulate.
> The data counted already includes the IP PDP bearer protocols i.e. IP or PPP.
> Format
> Integer
> Length
> 1-5 bytes
> Change Condition
> The Change Condition field is part of the ChangeOfCharCondition element in the List of Traffic Volumes. It defines the reason for closing the container:
> Supported values:
> ChangeCondition ::= ENUMERATED
> {
> qoSChange (0),
> tariffTime (1),
> recordClosure (2),
> cGI-SAICHange (6), -- bearer modification. "CHI SAI Change"
> rAIChange (7), -- bearer modification. "RAI Change"
> eCGIChange (10), -- bearer modification. "ECGI Change"
> tAIChange (11), -- bearer modification. "TAI Change"
> }

> 1. | The change condition is based on the current ULI type and not on new ULI. i.e if the ULI type is ECGI during CSRequest and while changing the ULI, whatever be the ULI type in MBRequest, the “changeCondition” should be ECGI change.

> 2. | If the initial ULI has one or more ULI Types(i.e ECGI, TAI, RAI, CGI), then the change condition the priority will be as follows:

> • | CGI-SAI Change

> • | RAI Change

> • | TAI Change

> • | ECGI Change

> 3. | If the current ULI type is not present (optional) the change condition is based on the new ULI contents. i.e if new ULI has ECGI, then we will consider it as ECGI change.

> 4. | The ULI in main CDR part indicates the ULI at the time of record opening time. i.e If CSReq comes with ULI U1 and then the ULI is changed to U2, U3 and if we generate a CDR the main ULI in CDR contains ULI as U1, but the next CDR generated contains the ULI as U3 and so on.

> 5. | In container the ULI is present in next container if the previous change condition is either RAI Change, CGI-SAI Change, TAI Change, ECGI Change.

> Format
> Enumerated
> Length
> 1 byte
> Change time
> The Change Time field is part of the ChangeOfCharCondition element in the List of Traffic Volumes. It provides the local time when a change condition (e.g. record closure) occurred and the container was closed.
> The format is shown below.
> TimeStamp ::= OCTET STRING (SIZE(6))
> -- The contents of this field are a compact form of the UTCTime format containing local time plus an offset to universal time. Binary coded decimal encoding is employed for the digits to reduce the storage and transmission overhead
> -- e.g. YYMMDDhhmmssShhmm
> -- where
> -- YY = Year 00 to 99 BCD encoded
> -- MM = Month 01 to 12 BCD encoded
> -- DD = Day 01 to 31 BCD encoded
> -- hh = hour 00 to 23 BCD encoded
> -- mm = minute 00 to 59 BCD encoded
> -- ss = second 00 to 59 BCD encoded
> -- S = Sign 0 = "+", "-" ASCII encoded
> -- hh = hour 00 to 23 BCD encoded
> -- mm = minute 00 to 59 BCD encoded
> Format
> BCD encoded octet string
> Length
> 9 bytes
> User Location Information
> This field contains the User Location Information as described in TS 29.274 for eGTP cases (e.g. CGI, SAI, RAI TAI and ECGI).
> The field is provided by the SGSN/MME and transferred to the S-GW/P-GW during the IP-CAN bearer activation/modification.
> User Location Information contains the location (e.g. CGI/SAI, ECGI/TAI or RAI) where the UE is located and used during the transfer of the data volume captured by the container (applicable only to the SGW-CDR). This is included in the Traffic data container only if previous container's change condition is “user location change”. Note the user location information in SGW-CDR main level contains the location where the UE was when CDR was opened.
> Format
> Octet string
> Length
> Based on the type of identity it may vary.
> EPC QoS Requested
> EPC QoS Information In case of IP-CAN bearer specific container this contains authorized QoS for the IP-CAN bearer. First container for each QCI/ARP pair includes this field. In following containers this field is present if previous change condition is “QoS change”. This field is applicable only in SGW-CDR.
> Format
> EPCQoSInformation ::= SEQUENCE
> {
> --
> -- See TS 29.212 for more information
> --
> qCI [1] INTEGER,
> maxRequestedBandwithUL [2] INTEGER OPTIONAL,
> maxRequestedBandwithDL [3] INTEGER OPTIONAL,
> guaranteedBitrateUL [4] INTEGER OPTIONAL,
> guaranteedBitrateDL [5] INTEGER OPTIONAL,
> aRP [6] INTEGER OPTIONAL
> }
> Length
> Variable length format (Will vary based on the values).
> iMSsignalingContext
> Indicates if the IP-CAN bearer is used for IMS signalling. It is only present if the IP-CAN bearer is an IMS signalling bearer. A IP-CAN bearer for IMS signalling is determined via the “IM CN Subsystem Signalling Flag” conveyed via the “Activate PDP context request” message from the MS to the network (refer to TS 24.008).
> Format
> Null
> Length
> Zero
> List of Served Node Addresses
> This field contains 1-16 Serving Node control plane IP used during this record (max of 15 Serving Node Changes). This is a list of IP addresses. If the PLMN-ID of the MME is same after Handover to new MME, one more IP address is added to the list. If the list is overflowed, with configured number of IP addresses, a CDR with “serving node Change” as cause for record closure will be generated. The serving node addresses, listed here map to the serving node types listed in the field “Serving node Types” in sequence.
> Format
> Octet String containing list of IPV4 or IPV6 IP addresses.
> Length
> The length can vary based on whether the encoded IP address is IPV4 or IPV6.
> Served Node IPv4 Binary Address
> The octet string included in the field described above includes the IPV4 address of the MME.
> Format
> Octet String
> Length
> 4 bytes
> Served Node IPv6 Binary Address
> The octet string included in the field described above includes the IPV6 address of the MME.
> Format
> Octet String
> Length
> 16 bytes
> Serving Node Type
> These fields contain one or several serving node types in control plane of S-GW or P-GW, which have been connected during the record. The serving node types listed here map to the serving node addresses listed in the field “Serving node Address” in sequence.
> The possible values are:
> ServingNodeType ::= ENUMERATED
> {
> sGSN (0),
> pMIPSGW (1),
> gTPSGW (2),
> ePDG (3),
> hSGW (4),
> mME (5)
> }
> Note: In the SGW-CDR, the possible values are SGSN(0) and MME(5).
> Format
> Sequence of serving Node Type.
> Length
> Variable length format (Based on number of nodes connected during this period).
> Local Record Sequence Number
> This field contains a unique sequence number associated with the NodeId field and independent of the bearer context. For each Node ID, this number with range 1..4294967295 is allocated sequentially for each CDR. This along with a Node ID uniquely identifies a CDR.For SGW-CDRs, this field is only included when the option “gtpp attribute local-record-sequence” number is configured.
> Format
> Octet String
> Length
> 1-5 bytes
> MS Time Zone
> The “Time Zone” IE that the MME may provide to the SGW during the PDN context activation/modification procedure.
> Format
> Octet String
> Length
> 2 bytes
> Node ID
> This field contains an identifier string for the node that had 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: This is a configured Node-ID-Suffix having any string between 1 to16 characters, defined using the gtpp attribute node-id command.
> If this node-id-suffix is not configured, the S-GW uses the GTPP context name as the Node-id-suffix (truncated to 16 characters).
> This field is only included when the option “gtpp attribute local-record-sequence-number” is configured.
> Format
> IA5string
> Length
> 5-20 bytes
> PDN Connection Id
> This field defines the PDN connection (IP-CAN session) identifier to identify different records belonging to same PDN connection. This field includes Charging Id of first IP-CAN bearer activated within the PDN connection. Together with P-GW address this uniquely identifies the PDN connection.
> Format
> Integer.
> Length
> 1-5 bytes
> PDP PDN Type
> -- OCTET 1: PDP Type Organization
> Spare ‘1111’ PDP Type Organization Value

> PDP Type Organization | Value
> ETSI | 0
> IETF | 1

> ‌
> Note: In LTE, only IETF is supported.
> -- OCTET 2: PDP/PDN Type Number
> Bits
> 3 2 1
> 0 0 1 IPv4
> 0 1 0 IPv6
> 0 1 1 IPv4/IPv6
> Bits 8-4 of octet are spare and are coded as zero.
> Format
> Octet string
> Length
> 2 bytes
> PGW Address used
> These field is the serving P-GW IP address for the Control Plane. If both an IPv4 and an Ipv6 address of the P-GW is available, the P-GW shall include the Ipv4 address in the CDR. This is a choice attribute and the CDR can contain the Binary format or the ASCII format in the CDR.
> Format
> Octet string
> Length
> The length can vary based on whether the encoded IP address is IPv4 or IPv6.
> PGW IPv4 Binary Address
> The octet string included in the field described above includes the IPv4 address assigned to the subscriber by of the P-GW in binary coding.
> Format
> Octet string
> Length
> 4 bytes
> PGW IPv6 Binary Address
> The octet string included in the field described above includes the IPv6 address assigned to the subscriber by of the P-GW in binary coding.
> Format
> Octet string
> Length
> 16 bytes
> RAT Type
> Holds the value of RAT Type, as provided to S-GW and P-GW, described in TS 29.274 for eGTP case.
> The field is provided by the SGSN/MME and transferred to the S-GW/P-GW during the IP-CAN bearer activation/modification.
> Format
> Integer
> Length
> 1 byte
> Record Extensions
> A set of network operator/manufacturer specific extensions to the record.
> Important: This field is operator-defined and is not encoded in any S-GW CDR dictionary in this release
> Format
> Sequence
> Length
> Variable Length Format
> Record Opening Time
> This field contains the time stamp when a PDP context is activated in SGSN or when a subsequent record is opened after a partial record.
> The timestamp is determined based on the internal timer which has an accuracy of 10ms. Depending on the configured mechanism this is translated into the timestamp which only shows the full seconds.
> The format is shown below.
> TimeStamp ::= OCTET STRING (SIZE(6))
> The contents of this field are a compact form of the UTCTime format containing local time plus an offset to universal time. Binary coded decimal encoding is employed for the digits to reduce the storage and transmission overhead
> -- e.g. YYMMDDhhmmssShhmm
> -- where
> -- YY = Year 00 to 99 BCD encoded
> -- MM = Month 01 to 12 BCD encoded
> -- DD = Day 01 to 31 BCD encoded
> -- hh = hour 00 to 23 BCD encoded
> -- mm = minute 00 to 59 BCD encoded
> -- ss = second 00 to 59 BCD encoded
> -- S = Sign 0 = "+", "-" ASCII encoded
> -- hh = hour 00 to 23 BCD encoded
> -- mm = minute 00 to 59 BCD encoded
> Format
> BCD encoded octet string
> Length
> 9 bytes
> Record Sequence Number
> A running sequence number with range 1.. 4294967296 used to link partial records generated by the SGW for a specific IP-CAN bearer context (characterized with the same Charging ID and P-GW address). This field is not present if the first record is also the final record.
> Format
> Integer
> Length
> 1-5 bytes
> Record Type
> The field identifies the type of the record:
> SGW-CDR(sgwPDPRecord) 84 (0x54)
> Format
> Integer
> Length
> 1 byte
> Served IMEISV
> This fields contains the international mobile equipment identity (IMEISV) of the equipment served, if available.
> The structure of the IMEI is defined in TS 23.003.
> The IMEI is composed of the following elements:

> • | Type Allocation Code (TAC). Its length is 8 digits;

> • | Serial Number (SNR) is an individual serial number uniquely identifying each equipment within each TAC. Its length is 6 digits;

> • | Software Version Number (SVN) identifies the software version number of the mobile equipment. Its length is 2 digits.

> If SV is not available, a filler digit “f” is added after the spare digit to fill up the last byte. Spare digit: this digit shall be zero, when transmitted by the MS.
> Format
> BCD encoded octet string
> Length
> 8 bytes
> Served IMSI
> This field contains the International Mobile Subscriber Identity (IMSI) of the served party. The IMSI is formatted in accordance with 3GPP TS 23.003.
> Format
> BCD encoded octet string
> Length
> 3-8 bytes
> Served MSISDN
> The field tracks the Mobile Station (MS) ISDN number (MSISDN) of the subscriber which is transparently copied from the Create Session Request message.
> Format
> BCD encoded octet string
> Length
> 1-9 bytes
> Serving Node PLMN Identifier
> PLMN identifier (MCC and MNC) of the P-GW used. This field is present in CDRs if the P-GW PLMN-ID is available in the CSR message from Serving Node (e,g MME).
> MCC and MNC are coded as described for “User Location Info” in TS 29.274.
> Format
> Octet string
> Serving PDP IP Address
> This field contains the IP address for the PDN connection (PDP context, IP-CAN bearer) if available. This is a network layer address of type IP version 4 or IP version 6. The address for each Bearer type is allocated either temporarily or permanently (see “Dynamic Address Flag”).
> Format
> Octet string
> Length
> The length can vary based on whether the encoded IP address is IPv4 or IPv6.
> PDP IPv4 Binary Address
> The octet string included in the field described above includes the IPv4 address assigned to the subscriber by of the P-GW in binary coding.
> Format
> Octet string
> Length
> 4 bytes
> PDP Ipv6 Binary Address
> The octet string included in the field described above includes the IPv6 address assigned to the subscriber by of the P-GW in binary coding.
> Format
> Octet string
> Length
> 16 bytes
> SGW Address
> These field is the serving S-GW IP address for the Control Plane. If both an IPv4 and an IPv6 address of the S-GW is available, the S-GW shall include the IPv4 address in the CDR. This is a choice attribute and the CDR can contain the Binary format or the ASCII format in the CDR.
> Format
> Octet string
> Length
> The length can vary based on whether the encoded IP address is IPv4 or IPv6.
> SGW IPv4 Binary Address
> This field is the serving control plane S-GW IPv4 address on the S5 interface.
> Format
> Octet string
> Length
> 4 bytes
> SGW IPv6 Binary Address
> This field is the serving control plane S-GW IPv6 address on the S5 interface.
> Format
> Octet string
> Length
> 16 bytes
> SGW Change
> This field is present only in the SGW-CDR to indicate that this is the first record after an S-GW change. In this case, it is set to TRUE (“FF”)
> Format
> Boolean
> Length
> 1 byte
> Start Time
> This field contains the time when the IP-CAN session starts at the S-GW/P-GW, available in the CDR for the first bearer in an IP-CAN session.
> The timestamp is determined based on the internal timer which has an accuracy of 10ms. Depending on the configured mechanism this is translated into the timestamp which only shows the full seconds.
> The format is shown below.
> TimeStamp ::= OCTET STRING (SIZE(6))
> The contents of this field are a compact form of the UTCTime format containing local time plus an offset to universal time. Binary coded decimal encoding is employed for the digits to reduce the storage and transmission overhead
> -- e.g. YYMMDDhhmmssShhmm
> -- where
> -- YY = Year 00 to 99 BCD encoded
> -- MM = Month 01 to 12 BCD encoded
> -- DD = Day 01 to 31 BCD encoded
> -- hh = hour 00 to 23 BCD encoded
> -- mm = minute 00 to 59 BCD encoded
> -- ss = second 00 to 59 BCD encoded
> -- S = Sign 0 = "+", "-" ASCII encoded
> -- hh = hour 00 to 23 BCD encoded
> -- mm = minute 00 to 59 BCD encoded
> Format
> BCD encoded octet string
> Length
> 9 bytes
> Stop Time
> This field contains the time when the IP-CAN session is terminated at the S-GW/P-GW, available in the CDR for the last bearer in an IP-CAN session.
> The timestamp is determined based on the internal timer which has an accuracy of 10ms. Depending on the configured mechanism (ceiling, floor, round-off) this is translated into the timestamp which only shows the full seconds.
> The format is shown below.
> TimeStamp ::= OCTET STRING (SIZE(6))
> The contents of this field are a compact form of the UTCTime format containing local time plus an offset to universal time. Binary coded decimal encoding is employed for the digits to reduce the storage and transmission overhead
> -- e.g. YYMMDDhhmmssShhmm
> -- where
> -- YY = Year 00 to 99 BCD encoded
> -- MM = Month 01 to 12 BCD encoded
> -- DD = Day 01 to 31 BCD encoded
> -- hh = hour 00 to 23 BCD encoded
> -- mm = minute 00 to 59 BCD encoded
> -- ss = second 00 to 59 BCD encoded
> -- S = Sign 0 = "+", "-" ASCII encoded
> -- hh = hour 00 to 23 BCD encoded
> -- mm = minute 00 to 59 BCD encoded
> Format
> BCD encoded octet string
> Length
> 9 bytes
> User Location Information
> This field contains the User Location Information as described in TS 29.274 for eGTP case (e.g. CGI, SAI, RAI TAI and ECGI).
> The field is provided by the SGSN/MME and transferred to the S-GW/P-GW during the IP-CAN bearer activation/modification.
> User Location Information contains the location (e.g. CGI/SAI, ECGI/TAI or RAI) where the UE is located and used during the transfer of the data volume captured by the container (applicable only to the SGW-CDR). This is included in the Traffic data container only if previous container's change condition is “user location change”. Note the user location information in SGW-CDR main level contains the location where the UE was when PGW-CDR was opened.
> The flags ECGI, TAI, RAI, SAI and CGI in octet 5 indicate if the corresponding fields are present in the IE or not. If one of these flags is set to “0”, the corresponding field is not present at all. The respective identities are defined in 3GPP TS 23.003.
> The following subclauses specify the coding of the different identities. For each identity, if an Administration decides to include only two digits in the MNC, then bits 5 to 8 of octet 7 are coded as “1111”.
> CGI field:
> The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet 9 is the most significant bit and bit 1 of Octet 10 the least significant bit. The coding of the location area code is the responsibility of each administration. Coding using full hexadecimal representation shall be used.
> The Cell Identity (CI) consists of 2 octets. Bit 8 of Octet 11 is the most significant bit and bit 1 of Octet 12 the least significant bit. The coding of the cell identity is the responsibility of each administration. Coding using full hexadecimal representation shall be used.
> SAI field:
> The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet 9 is the most significant bit and bit 1 of Octet 10 the least significant bit. The coding of the location area code is the responsibility of each administration. Coding using full hexadecimal representation shall be used.
> The Service Area Code (SAC) consists of 2 octets. Bit 8 of Octet 11 is the most significant bit and bit 1 of Octet 12 the least significant bit. The SAC is defined by the operator.
> RAI field:
> The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet 9 is the most significant bit and bit 1 of Octet 10 the least significant bit. The coding of the location area code is the responsibility of each administration. Coding using full hexadecimal representation shall be used.
> The Routing Area Code (RAC) consists of 2 octets. Only Octet 11 contains the RAC. Octet 12 is coded as all 1's (11111111). The RAC is defined by the operator.
> TAI field:
> The Tracking Area Code (TAC) consists of 2 octets. Bit 8 of Octet 9 is the most significant bit and bit 1 of Octet 10 the least significant bit. The coding of the tracking area code is the responsibility of each administration. Coding using full hexadecimal representation shall be used.
> ECGI field:
> The E-UTRAN Cell Identifier (ECI) consists of 28 bits. Bit 4 of octet 10 is the most significant bit and bit 1 of Octet 11 the least significant bit. The coding of the E-UTRAN cell identifier is the responsibility of each administration. Coding using full hexadecimal representation shall be used.
> Format
> Octet string
> Length
> Varies based on the type of identity.

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