A Robust Rule-Based Event Management Architecture for Call-Data Records

Presented at KES 2004: Wellington, New Zealand

A Robust Rule-Based Event Management Architecture for Call-Data Records

Abstract:

Rules provide a flexible method of recognizing events and event patterns through the matching of CDR data fields. The first step in automatic CDR filtering is to identify the data fields that comprise the CDR format. In the particular case of the Nortel Meridian One PABX, five different call data types can be identified that are critical for call reporting. The architecture we have proposed will allow for line activity analysis while continuously publishing action choices in real-time. For performance evaluation of serial-line CDR data communications, an approximation to the CDR record loss rate at different simulated call traffic intensities was calculated. Here, the arrival process represents the arrival of newly generated CDR to the output buffer and the service process represents the process of transmitting the CDR over the serial connection. We calculate the CDR loss rate at different arrival intensities and observed that the CDR loss rate is negligible when the CDR arrival rate is less than 4 CDR per second.

Keywords:

Rule-based system, CDR loss rate, event filtering and correlation.

Related posts:

  1. Network Programmer for Société Générale
  2. Quick way to create patch files based on modified date with xcopy
  3. What’s your ideal hourly rate?
  4. Mindomo: web-based mind mapping
  5. Moving from WebCollab to activeCollab for project management

[...] I also co-authored and presented a paper at KES™2004 (Knowledge-based Intelligent Information & Engineering Systems) on the topic of “A Robust Rule-based Event Management Architecture for Call-Data Records“. [...]

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>