Event Types

MATRIXX Engine supports multiple built-in event types that are defined in a tree hierarchy based on pricing configuration and stored in the pricing database. You can define custom subordinate event types (sub events) for an event type.

For example, a service provider offering data services can define new event types based on the VoIP phone app a subscriber uses. Each subordinate event type definition has information about the activity being performed. It can also include data from a parent event type and the Event Detail Record (EDR) generated can contain the parent's data when it is a descendant of the parent EDR. The data recorded for each subordinate event type can vary, depending on its parent event type. For example, a subordinate data event type has different parental information than a subordinate voice event type. When you compile a pricing plan and load it into the pricing database, the custom event type name and ID are saved in the event type object. These values are used to look up the object when a usage message is received.

Each service type that is a leaf node in the service type hierarchy must be associated with exactly one event type. MATRIXX Engine supports several service types out-of-the-box, including voice, data, and messaging. IT personnel can define additional service types and event types as necessary. If a service type has accessory services, each accessory service is handled as a subordinate event type. For example, a voice service might be bundled with two accessory services: call forwarding and conference calling. Each accessory service is translated into a separate event type that is subordinate to the voice event.