Event Type and Service Type Association

Event types and service types are defined during pricing configuration. The event type definition identifies the container to use for the Event Detail Record (EDR) and fields to map to the EDR. The service type definition identifies an associated event type and the fields to map to the EDR.

For complete descriptions of the event type and service type definitions, including procedures on how to define event types and service types, see My MATRIXX Help.

In My MATRIXX, the Event Types page lists all event types that are available to MATRIXX Engine. These event types are compiled into the pricing configuration file and are stored in the Pricing database. The event types are examined during rating of a service to determine which EDR to generate.

Example myVoice Event lists the properties for an example private usage event type named myVoice that is a child of the Usage | Voice event.
Table 1. Example myVoice Event
Property Description
ID 2006
Path Usage | Voice
Name MyVoiceEvent
Normalized Event Type Usage
Container Name MyVoiceEvent
Type ID 1
Application Usage

The MyVoiceEvent event type uses a custom MDC named MyVoiceEvent. A service type uses the Name, in this case MyVoiceEvent to identify its associated event type. The association is specified in the service type definition's Event Type Object ID field.

The MATRIXX Engine associates each network message received for subscriber usage with a service type. The service type identifies the following information:

  • The EDR to generate.
  • The event type to add to the EDR.
  • Event aggregation settings.
  • Service authorization and quota management settings.
  • Service context information.
  • Any fields to copy into the EDR.
  • Any fields to copy into the response message during a session.
  • Final unit indicator settings.
  • Rating beats.

The service type also controls which product offers are applicable during rating.

Service Types in My MATRIXX lists the service types that are available to the MATRIXX Engine. These service types are compiled into the pricing configuration file, are stored in the Pricing database, and are examined during rating.

MyVoiceEvent Service Type Properties lists the properties for a simple service type based on the MyVoiceEvent example event.

Table 2. MyVoiceEvent Service Type Properties
Property Value
Full Name Root Event | usage | voice | MyVoice
Type ID 1
Parent ID 3
ID 7779
Name MyVoice
Event Type Object ID MyVoiceEvent
Quantity Type actual_duration
Quantity Units seconds
Audit Data Container Name none
Session Data Container Name CustomChargingSessionExtension
Note: You can map date/time fields into aggregated events as aggregation grouping fields or non-grouping fields. Use caution when mapping date/time fields as grouping fields to prevent many different aggregations from being created.

The Event Type Object ID identifies the event created in Event Types. To add fields from this event to EDRs, you must add an event field mapping in the service type Event Field Mappings. For information about event field mapping properties, see the discussion about event and failed event field mapping properties in My MATRIXX Help.

Field mappings in the event type are added to EDRs for all services based on this event type. To add fields to EDRs from usage events, you specify the event field mapping in the event type or service type definition. Specifying them for a service type enables you to map different fields into the EDR based on the service being used. To add fields to EDRs from non-usage events, you must specify the mappings in the event type. For more information, see the discussion about customizing non-usage events in MATRIXX Integration.

Field mappings defined in the hierarchies of Event Types and Service Types are applied starting from the bottom (leaf or middle node) to the top (root). If the target event field is set already, the source field is not copied. For example, assume you have the event type mappings in Example Event Field Mapping. The last field mapping is used for MyVoice from MyDiamRoMsg. For all the other types of traffic, the mapping from MyChargingSessionExtension is used.
Table 3. Example Event Field Mapping
Path Source Destination
Event Types | usage | voice MyChargingSessionExtension.DestinationTypeId MyUsageEvent.DestinationTypeId
Event Types | usage | voice | MyVoice MyDiamRoMsg.DestinationTypeId MyUsageEvent.DestinationTypeId

After defining the event type and service type pricing components, you must compile the pricing configuration file and load the new pricing into the pricing database so the pricing components are available during rating. Then run the create_config.py script to create a custom MDC to hold the EDR and to create the new fields to add to it.