The network identifier portion 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 EGTP Create Session Request message.

The APN string may consist of alphabetic characters ("A...Z", "a...z"), digits ("0...9") and the dash "-".

Format

IA5 string

Length

1–63 bytes

This field includes the AF Charging Identifier and associated flow identifiers generated by the AF and received by the P-GW over Gx interfaces.

Note

'Flows' information is not supported on Cisco P-GW currently. The AF Record Information field is not part of the 3GPP 32.298 Release 6 and 7 specifications. The AF Record Information field is an Release 15 attribute and it is present in Release 8 dictionary if enabled through the gtpp attribute af-record-info CLI command. This attribute will be available for the dictionaries custom35, custom24, custom44, custom48, custom50,custom52,custom53, and custom34 only when the CLI command gtpp attribute af-record-info is configured. The P-GW CDR generated for PDP Context Release does not contain the AFCID field in the following scenario: When P-GW sends Re-Authorization Request (RAR) with Dynamic Rule1 with AFCID and traffic is not sent after the RAR, and if P-GW sends a second RAR with Dynamic Rule2 without AFCID and traffic is sent after the RAR.

Format

Sequence OF

Section

Holds the OCTET String size

An index indicating how the APN was selected.

The following APN selection mode indexes are possible:

Format

Enumerated

Length

1 byte

This field contains a reason for the closure of the CDR.

Some of the possible reasons are as follows:

Note that the Ocs_Unreachable (302), Ocs_Reachable (303), and Ocs_Status_Unknown (304) Cause for Record Closing reasons are applicable only to custom45 GTPP dictionary for P-GW.

Format

Integer

Length

1 byte

Lists the charging characteristics applied to the PDP context by the P-GW.

Format

Octet string

Length

2 bytes

This field specifies how the Charging Characteristics were selected.

Supported values:

Note: The values AAASupplied (6) and GWOverride (7) are only supported in the custom40 GTPP dictionary.

Format

Enumerated

Length

1 byte

This field contains 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 P-GW.

Format

Integer

Length

1–5 bytes

This field is included in the CDR when the bearer is released and when the option gtpp attribute diagnostics is configured.

Format

Integer

Length

Variable

This field contains the duration in seconds for the record. 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.

Important

For custom40 GTPP dictionary, the duration is first calculated based on the actual opening and closing times of the record, and then rounded off. For all other GTPP dictionaries, the opening and closing times are first rounded off and then used for the calculation of duration.

Format

Integer

Length

1–5 bytes

This field indicates that the PDN address has been dynamically allocated for that particular IP CAN bearer (PDN connection). This field is missing if the address is static.

Format

Boolean

Length

1 byte

This field includes one or more containers reported from the RAN for a secondary RAT.

Format

Sequence of RAN Secondary RAT Usage Report

Length

Variable

This list includes one or more service data containers. Each container is associated with a service condition change on a service data flow (categorized per rating group or per combination of the rating group and service ID) within this IP CAN bearer.

Important

The List of Service Data field will be present in a P-GW CDR only if there is non-zero data consumption.

In releases prior to 18.0, the customer-specific GTPP dictionaries "custom38" and "custom39" have restriction of one Service Data Container per CDR. In 18.0 and later releases, this restriction is removed for these two dictionaries and the number of containers per CDR is configurable through the CLI "gtpp egcdr losdv-max-containers ". Note that the default value of max_losdv is 10 and max_losdv attribute is configurable for both custom38 and custom39 dictionaries. Default value of max_lotv in GTPP group is 8 and max_lotv is now configurable.

Format

Sequence

Length

Variable

This field contains a unique sequence number associated with the Node ID field and independent of the bearer context.

Format

Integer

Length

1–5 bytes

This field indicates if the PDN connection has a low priority, i.e. for Machine Type Communication.

Format

Important

This attribute field is currently available only in custom35 , custom38 and custom40 GTPP dictionaries for PGW-CDRs when the CLI command "gtpp attribute lapi " is configured in GTPP Server Group Configuration mode.

Null

Length

1 Byte

The "Time Zone" IE that the SGSN may provide to the P-GW during the PDP context activation/modification procedure.

Format

Octet string

Length

2 bytes

This field contains an identifier string for the node that had generated the CDR.

On the Cisco P-GW, this Node ID field is a printable string in the format ndddSTRING:

Format

IA5string

Length

1–20 bytes

This field defines the PDN connection (IP-CAN session) identifier to identify different records belonging to same PDN connection. This field includes the Charging Id of the 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

-- OCTET 1: PDP Type Organization

       Spare '1111'                PDP Type Organization Value 

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

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.

Format

Octet string

Length

6 or 18 bytes (depending on v4 or v6 address)

This field is the P-W PMLN Identifier (Mobile Country Code and Mobile Network Code).

The MCC and MNC are coded as described for "User Location Info" in TS 29.274 [91].

Format

Octet string

Length

3 bytes

This field contains charging information sent by the OCS in the Diameter Credit Control Credit-Control-Answer messages as defined in 3GPP TS 32.251.

Important

The Furnish Charging Information (FCI) feature is currently applicable to all GTPP dictionaries that are compliant to 3GPP Rel.7 and 3GPP Rel.8 standard. Note that custom43 (rel. 8 compliant) dictionary has additional custom handling with respect to free format data encoding and FCI change trigger for CDR generation. This feature is CLI-controlled.

Note that inclusion of this field in the CDR for any given GTPP dictionary is controlled through the CLI command gtpp attribute furnish-charging-information in the GTPP Server Group Configuration mode. PGW-CDR and eG-CDR will contain FCI based on the GTPP group configuration.

For dictionaries other than custom43, whenever FCI changes, a new Free-Format-Data (FFD) value is either appended to existing FFD or overwritten on the current FFD for online charging session depending on Append-Free-Format-Data (AFFD) flag. CDR is not generated upon FCI change.

FCI is supported in main CDR as well as in LOSDV. Whenever a trigger (volume, time, RAT, etc.) happens current available FFD at command level is added to the main body of the CDR. The same FFD at command level is added to the main body of the next CDRs until it is not appended or overwritten by next Credit-Control-Answer message at command level.

The command level FCI implementation for custom43 dictionary can be outlined as follows:

Important

Note the above described behavior applies only to command level PS FCI.

Format

Sequence

Length

Variable

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

Proprietary field used to report a RAN cause code and packet counts. In 16.0 and later releases, the IE "packet count" in the Record Extension field of custom34 and custom35 dictionaries has been changed as "packetCount".

Format

Management Extensions

Length

Variable

List of Service Level CDRs.

Format

Sequence

Length

Variable

This field contains the timestamp when a PDP context is activated in PGW 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 (ceiling, floor, or round-off) this field is translated to only show full seconds.

TimeStamp ::= OCTET STRING (SIZE(6))

The contents of this field are a compact form of the UTC Time 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

For example: YYMMDDhhmmssShhmm

Format

BCD encoded octet string

Length

9 bytes

A running sequence number within the range of 1 to 4294967296 used to link partial records generated by the P-GW 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

This field identifies the type of the record:

PGW-CDR (pgwPDPRecord) 85 (0x55)

Format

Integer

Length

1 byte

This field contains the International Mobile Equipment Identity (IMEISV) of the equipment served.

The structure of the IMEI is defined in TS 23.003.

The IMEI is composed of the following elements:

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

The International Mobile Subscriber Identity (IMSI) of the MS. The IMSI is formatted in accordance with 3GPP TS 23.003. This will be present if the Anonymous Access Indicator is FALSE or not supplied.

The IMSI is formatted in accordance with 3GPP TS 23.003.

Format

BCD encoded octet string

Length

3–8 bytes

This field contains the Mobile identifier of the served user in Network Access Identifier (NAI) format based on IMSI, as defined in TS 23.003 [68].

SubscriptionID ::= SET

{

subscriptionIDType [0] SubscriptionIDType,

subscriptionIDData [1] UTF8String

}

SubscriptionIDType ::= ENUMERATED

{

END_USER_E164 (0),

END_USER_IMSI (1),

END_USER_SIP_URI (2),

END_USER_NAI (3),

END_USER_PRIVATE (4)

}

The type will be END_USER_NAI.

For IMSI: 123456789012345 mcc=123 mnc=045

subscriptionIDData is a string will be

0123456789012345@nai.epc.mnc045.mcc123.3gppnetwork.org

Format

Set

Length

Variable (Max 62)

The field tracks the Mobile Station (MS) ISDN number (MSISDN) of the subscriber which is transparently copied from the Create Session Request message.

The MSISDN is TBCD encoded as shown in the example below:3GPP TS 23.003 (CCITT Rec. E 213)

ServedMSISDN ::= OCTET STRING (SIZE(1..9))

subscriber identification MSISDN

octet 1 : bit 8 (msb): extension bit

= 1 : no extension

other : not relevant

bit 7..5 : type of number

= 000 : unknown

= 001 : international number

= 010 : national significant number

= 011 : network specific number

= 100 : subscriber number

= 101 : reserved

= 110 : abbreviated number

= 111 : reserved for extension

bit 4..1 : numbering plan indicator

= 0001: ISDN/Telephony Numbering Plan (Rec CCITT E.164)

other : not relevant

octet 2..9: <= 16 digits TBCD-String (twisted)

substructure (without spares or fillers):

1..3 digits - country code (CC)

(only international number)

3 digits - national destination code (NDC)

<= 10 digits - subscriber number (SN)

first and intermediate octet = 2 digits

last octet = 2 digits or 1 digit + 1 fill digit H'F

As per 3GPP TS 29.274 v 8.11.0, "MSISDN value contains only the actual MSISDN number (does not contain the 'nature of address indicator' octet, which indicates 'international number' as in 3GPP TS 29.002 [37]) and is encoded as TBCD digits."

To comply with this, octet 1 (nature of address indicator) is not added in the encoded value of MSISDN.

For example:

MSISDN: '491720400305'

encoded: H'94 71 02 04 30 50

Format

BCD encoded octet string.

Length

1–9 bytes

This field contains the IP address for the PDN connection (PDP context, IP-CAN bearer). This is a network layer address of type IP version 4 (PDN Type is IPv4) or IP version 6 (PDN Type is IPv6 or IPv4v6). The address for each Bearer type is allocated either temporarily or permanently (see "Dynamic Address Flag"). This parameter shall be present except when both the Bearer type is PPP and dynamic address assignment is used.

Format

Octet string

Length

The length can vary based on whether the encoded IP address is IPv4 or IPv6.

This field contains the IPv4 address for the PDN connection (PDP context, IP-CAN bearer) when dual-stack IPv4v6 is used, and the IPv6 address is included in Served PDP Address or Served PDP PDN Address.

This field is not included if the PDP/PDN address is IPv4 or IPv6. By default, this field is not sent, even if the PDP Type is IPv4v6; this field must be enabled using the gtpp attribute served-pdp-pdn-address-extension CLI command.

Important

Note that this field is not part of the 3GPP 32.298 Release 6 and 7 specifications. This field is an Rel.9 attribute and it can be present in Rel.7 or Rel.8 dictionary if enabled through the gtpp attribute served-pdp-pdn-address-extension CLI command.

ASN.1 Definition:

-- This field was made available in PGWRecord in Release 8. If the above mentioned CLI is enabled 
-- we can treat this field to be available in GGSNPDPRecord or EGSNPDPRecord. 
-- PGWRecord                      ::= SET 
{ 
... 
  servedPDPPDNAddressExt                      [45] PDPAddress OPTIONAL 
} 

Format

Octet string

Length

8 bytes

The serving node control plane IP address of the S-GW used during this record. This is a list of IP addresses. If the list overflows with a configured number of IP addresses, a CDR with "serving node Change" as cause for record closure will be generated. The serving node addresses that are listed here are sequentially mapped to the serving node types listed in the field "Serving node Types".

Format

Sequence of IPv4 orIPv6 addresses.

Length

6-98 or 18-292 bytes (depending on IPv4 or IPv6 address; for 1-16 S-GW/SGSN addresses)

This field contains a serving node (SGSN/S-GW/MME/ePDG/HSGW) PLMN Identifier (Mobile Country Code and Mobile Network Code).

The MCC and MNC are coded as described for "Routing Area Identity" in TS 29.060 [75].

Format

Octet string

Length

3 bytes

These fields contain one or several serving node types in the control plane of an S-GW or P-GW, which have been connected during the record. The serving node types listed here are sequentially mapped to the serving node addresses listed in the field "Serving node Address".

The possible values are:

ServingNodeType    ::= ENUMERATED 
{ 
                sGSN            (0), 
                pMIPSGW      (1), 
                gTPSGW        (2), 
                ePDG            (3), 
                hSGW            (4), 
                mME              (5) 
} 

Format

Sequence of serving Node Type

Length

3-48; variable length format (based on number of nodes connected during this period)

This field contains the time when the User IP-CAN session starts at the P-GW, available in the CDR for the first bearer in an IP-CAN session.

In releases prior to 14.0, for P-GW service, the "startTime" attribute is added only to the first CDR of the default bearer of the IP-CAN session. In this case, if the first CDR was lost, the start time of the session remained unknown. Releases beyond 14.0, the "startTime" attribute is present in every PGW-CDR of the default bearer. Hence, if for any reason the first CDR is lost, the start time of the session can still be retrieved through the subsequent PGW-CDRs.

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 UTC Time 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.

For example: YYMMDDhhmmssShhmm

Format

BCD encoded octet string

Length

9 bytes

This field contains the time when the User IP-CAN session is terminated at the 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 UTC Time 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

For example: YYMMDDhhmmssShhmm

Format

BCD encoded octet string

Length

9 bytes

This field contains the location information of UE in a Trusted WLAN Access Network (TWAN).

Format

Octet string

Length

38 bytes

This field contains the User Location Information of the MS as defined in TS 29.060 for GPRS case, and in TS 29.274 for EPC case (e.g. CGI, SAI, RAI TAI and ECGI), if available.

This 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.

In releases prior to 16.0, only a fixed number of combinations of User Location Information (ULI) identity types is supported. That is, Release 10 ULI values were only partially populated in PGW-CDRs as the ULI identity type combinations "CGI & RAI" and "SAI & RAI" introduced in 3GPP Release 10 specification were not supported. In 16.0 and later releases, Release 10 ULI values are populated as received in PGW-CDRs. This support is extended to Create Session Request, Create Bearer Response, Modify Bearer Request and Delete Session Requests.

Important

This behavior change is applicable to Release 10 GTPP dictionaries for P-GW.

Format

Octet string

Length

6–13 bytes