Cisco Cisco Packet Data Interworking Function (PDIF)
GGSN CDR Field Descriptions
CDR Fields ▀
GTPP Interface Administration and Reference, StarOS Release 18 ▄
205
4 bytes
IMS Signalling Context
Indicates whether or not the PDP context is used for IMS signaling based on the setting of the "IM CN Subsystem
Signalling Flag" conveyed via the "Activate PDP context request" message from the MS to the network.
Signalling Flag" conveyed via the "Activate PDP context request" message from the MS to the network.
Important:
This field is not supported at this time.
Format
Octet string
List of Service Data Volumes
A list of the changes that occurred in charging conditions for all service data flows for the PDP context.
The first container includes an optional field “QoS Negotiated”. In the following containers “QoS Negotiated” is present
if the previous change condition is "QoS change".
if the previous change condition is "QoS change".
In 16.0 and earlier releases, if in the CDRs there are multiple LOSDVs with same content-id and different service-
identifiers, then the QOS-Info Information Element (IE) is included only in the very first LOSDV and not in the
subsequent LOSDVs unless its previous LOSDV is closed for QoS change.
identifiers, then the QOS-Info Information Element (IE) is included only in the very first LOSDV and not in the
subsequent LOSDVs unless its previous LOSDV is closed for QoS change.
In 17.0 and later releases, this implementation has been modified to include QOS-Info in all LOSDVs having different
combination of service-id and content-id. Thus if there are multiple LOSDVs with same content-id but different service-
id, QOS-Info will be present in every such LOSDV.
combination of service-id and content-id. Thus if there are multiple LOSDVs with same content-id but different service-
id, QOS-Info will be present in every such LOSDV.
Important:
This behavior change is applicable to Rel.8 and Rel.10 compliant GTPP dictionaries.
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 “
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.
Default value of max_lotv in GTPP group is 8 and max_lotv is now configurable.
The list will include one or more of the following fields:
Service Identifier: Service identifier is an identifier for a service. The service identifier may designate an end
user service, a part of an end user service or an arbitrarily formed group thereof. Present only if the rating group
is online (DCCA) charged.
user service, a part of an end user service or an arbitrarily formed group thereof. Present only if the rating group
is online (DCCA) charged.
Rating Group: This is the service flow identity and has to be used for differentiated evaluation of user’s traffic.
This is also known as content-id.
This is also known as content-id.
Charging Rulebase Name: The name of the Rulebase used for charging. This is the group name of charging
rules.
rules.
Important:
The maximum length of charging rulebase name in the List of Service Data
Volumes (LOSDVs) can be trimmed. For more information, refer to the
gtpp egcdr charging-