Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Members
Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

The Call Detail Record

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search

Call Detail Records (CDRs) are still the core of the customer profile. CDRs are an important resource for a Communications company, and the complete record must be stored and made available across the company. CDRs will be utilized in some vastly different ways across a Communications company, as will be demonstrated below.

CDR provides comprehensive information on each and every call occurring on the data circuits, including:

• Voice capture for both directions

• Complete signaling information for each direction

• Disruptive alarms and errors occurring during the call including bipolar violations, loss of frame, cyclic redundancy check errors and loss of signal

• Detailed voiceband event information occurring during the call including dual tones, fax tones, modem signals, and more

• Detailed analysis of the call including noise level, speech level, speech activity factor, echo measurements, and more

• Categorization of the call as voice, fax, modem, or data


An Analytic Database is ideal for analyzing CDR data because the data is characterized by two key properties:

1. Massive quantity of data – Calls produce readings at regular rates – sometimes thousands of times per second – over long time periods. Communications devices are “always on” and generating data. Consider the packets in a streaming video going to and from the device.

2. Need for scan queries – A common use of CDR data is to study historical trends and compare time periods and regions. For example, a region manager may want to query all the data in his region and surrounding regions. This requires a series of aggregate queries over large amounts of historical data.

The 80/20 rule here is that 80% of the time you are going to use 20% of the CDR data in a query. However, depending on the project, that 20% will be different every time. CDR data is “big data” in the sense that it is rapidly accumulating semi-structured data though not every CDR record is necessarily the same structure since the record can vary according to the type of call. The benefits of columnar databases exacerbate with large amounts of data and large scans. The overhead of the multi-loads and the “gluing” together of a result set from multiple column structures would not be a valuable exercise with smaller data sets. However, whether the Communications Company is small or large, it has big data and needs something more than a traditional database to meet the demands of big data.

Wiki Contributors
Collapse Expand Close

View more contributors