EXAMPLE — CDR Pricing Configuration

To write CDR data to EDRs, each CDR type must have an associated event type defined in the pricing configuration and the fields to add to that event type's EDR must be defined in the associated service type definitions, which are also defined in the pricing configuration.

Sample Event Type Definition

Each event type for which to generate an EDR must be defined in My MATRIXX. The event type must have the same name as the custom MDC added to contain the CDR fields. For example, if you add an MDC called AnalyticsDataEvent, you must define the event types listed in AnalyticsDataEvent Event in My MATRIXX.
Table 1. AnalyticsDataEvent Event
Property Description
ID 13
Path Usage | Voice
Name AnalyticsDataEvent
Normalized Event Type Undefined
Container Name AnalyticsDataEvent
Type ID 3
Application usage

Sample Service Type Definitions

Service type definitions are defined in My MATRIXX. Pricing administrators define service types as part of pricing configuration. The Event Field Mapping contains the mapping of incoming fields to event type MDCs, which generates these fields in the associated EDRs. The event field map contains the properties listed in Field Mapping Properties.

Table 2. Field Mapping Properties
Attribute Description Data Type
Source Container The name of the MATRIXX Data Container (MDC) containing the field to add to the EDR. This is required if the event type specified or the parent of this event type, does not already contain the field.
The Source Container Name must be one of the following MDCs, an extension of it, or one of its descendants:
  • Mtx5GMultiUnitInfoData
  • Mtx5GMultiUnitUsageData
  • Mtx5GUsedUnitContainerData
  • Mtx5GRequest
  • Mtx5GResponse
  • MtxChrgCompWorkspace
  • MtxChrgMsgWorkspace
  • MtxChrgSegWorkspace
  • MtxChargingSessionExtension
  • MtxDeviceObject
  • MtxGroupObject
  • MtxMsg
  • MtxMultiServiceData
  • MtxPolicySessionExtension
  • MtxSessionContextData
  • MtxSubscriberObject
  • MtxTenantProfile
  • MtxUserExtension
  • MtxUserObject
  • MtxWalletObject

Use the MtxMultiServiceData MDC to populate EDRs with fields from specific service contexts. The source field must be located in the MultiServiceList element (in the message MDC) for a service context.

String
Source Field The name of the MDC field to add to the EDR.

The value is the full path of the field in the MDC, separated by a dot (.). For example, if a field is nested in an array, the syntax is: array_field_name.event_field_name

Note: You can map DateTime fields into aggregated events as aggregation grouping fields or non-grouping fields. Use caution when mapping DateTime fields as grouping fields to avoid many different aggregations.
 String
Source Tier (Optional) The name of a Tier (level) within a group hierarchy if the source container is a group object. Only group objects above the event initiator in the hierarchy can be source containers. Set the source tier in situations where there is a field, such as an account number associated with a group, that must be included in the subscriber events of its group members. String
Destination Container The name of the MDC containing the event field, for example, MtxVoiceEvent. This value is located in the Event Types list in Application Configuration.

The container name can be a super class of the container for the event type.

String
Destination Field The name of the event object field in which to copy the source field value.

The value is the full path of the field in the MDC, separated by a dot (.). For example, if a field is nested in an array, the syntax is: array_field_name.event_field_name

String
Group Aggregation? Configures field-based aggregation of usage data based on the field identified in the Destination Field name.
This property is used when event aggregation is enabled. When not aggregating, it has no effect. Values are:
  • true
  • false (default)
Boolean

Event field mappings for a GPRS service

The following event field mappings are used for a GPRS service during CDR rating. The mappings add several fields from different source MDCs to the AnalyticsDataEvent MDC (event_type_id 13), which produces the EDR for the data CDR.

  • Event Field Map 1
    • Source Container Name – MtxDiamRoMsg
    • Source Field Name – SessionId
    • Destination Container Name – AnalyticsDataEvent
    • Destination Field Name – sessionId
  • Event Field Map 2
    • Source Container Name – MtxMsg
    • Source Field Name – Op
    • Destination Container Name – AnalyticsDataEvent
    • Destination Field Name – ccRequestType
  • Event Field Map 3
    • Source Container Name – AnalyticsDiamRoMsg
    • Source Field Name – SessionMsgId
    • Destination Container Name – AnalyticsDataEvent
    • Destination Field Name – ccRequestNumber
  • Event Field Map 4
    • Source Container Name – AnalyticsDiamRoMsg
    • Source Field Name – SubscriberIdList
    • Destination Container Name – AnalyticsDataEvent
    • Destination Field Name – SubscriberIdList
  • Event Field Map 5
    • Source Container Name – AnalyticsDiamRoMsg
    • Source Field Name – EventTime
    • Destination Container Name – AnalyticsDataEvent
    • Destination Field Name – diamEventTime
  • Event Field Map 6
    • Source Container Name – MtxMultiServiceData
    • Source Field Name – RatingGroupId
    • Destination Container Name – AnalyticsDataEvent
    • Destination Field Name – RatingGroupId
  • Event Field Map 7
    • Source Container Name – AnalyticsDiamRoMsg
    • Source Field Name – Imsi
    • Destination Container Name – AnalyticsDataEvent
    • Destination Field Name – Imsi
  • Event Field Map 8
    • Source Container Name – AnalyticsDiamRoMsg
    • Source Field Name – CalledStationId
    • Destination Container Name – AnalyticsDataEvent
    • Destination Field Name – CalledStationId