Telecommunication transaction processing systems

TPS can be regarded as the link between the various network elements and platforms and the information management uses to drive the business.

Some governments require that a record of each and every transaction needs to be stored infinitely in its raw (encoded) format.

The batch sizes and frequency differ for each network-element and is also directly related to the number of active subscribers on a particular telecommunication network.

[3][4] Once the TPS has successfully retrieved all the CDR batches, its first task is to decode the CDRs into human readable (ASCII) format.

Should a particular platform vendor encode CDR's in non standard protocols, customization on the TPS is required.

Some high-end enterprise RDMS includes the likes of ORACLE, Microsoft SQL Server and MySQL.

The different entities within the RDMS now contains detailed records of each transaction which occurred on any particular platform within the network.

In order to speed up recurring queries and reports on the CDR detail within the RDMS entities, the TPS often summarizes the data based on certain dimensions, also known as aggregates.

The summaries regularly retrieve data from the detail entities within the RDBMS and summarizes it based on certain required information (dimensions).

Key measures are summed in order to give hourly, weekly or daily summaries depending on the reporting requirements.

Due to the high costs of storage, telecommunication organization regularly archive data not required anymore.

This gives the user up to date information and the ability to cross tabulate and build higher level summaries.