![Transaction processing system companies](https://loka.nahovitsyn.com/6.jpg)
![transaction processing system companies transaction processing system companies](https://resources.reed.co.uk/courses/coursemedia/365999/3a68f634-011f-4470-848e-84c60fd3e780.jpg)
Advanced application administrators can now query the detailed data by means of SQL. The different entities within the RDMS now contains detailed records of each transaction which occurred on any particular platform within the network. The architecture and layout of the RDMS is usually dictated by the particular TPS. Separate entities within the RDMS is used to store the data from the different network platforms. Once all intermediate processing on the CDR batches have completed, the TPS can now load the data into the particular 'datastore'. The RDMS should at least be able to support the volumes of CDRs generated by the particular network. The choice of RDMS to use, is usually driven by company policy, price and recommendations from the TPS supplier. Some high-end enterprise RDMS includes the likes of ORACLE, Microsoft SQL Server and MySQL. The 'datastore' used by the TPS consists of a Relational database management system. Some high-end TPS combines information from various elements to create master CDRs before being loaded into the 'datastore', whilst a lower-end or entry-level TPS directly loads data upon completion of CDR duplicate checking.
TRANSACTION PROCESSING SYSTEM COMPANIES SOFTWARE
Äepending on the TPS software used, the processes following the CDR duplicate level checking can differ.
![transaction processing system companies transaction processing system companies](https://4.bp.blogspot.com/_JJklOQ3XQEU/TTR9b-lT2iI/AAAAAAAAACQ/0HDO--TIeik/s1600/Credit+Card+Transaction+Fee+Distribution+Example-A.png)
The TPS administrators are responsible for verifying the CDRs flagged as duplicates, are in fact true duplicates. Duplicate CDRs are discarded and reported on. Upon successful completion of the decoding, the decoded CDR batches are then checked for duplicate records. Vendors are then required to supply detailed CDR specifications to the suppliers of the TPS in order to enhance the TPS to recognize the CDR formats and also detailed explanations of which information is contained within the CDR about a particular subscriber's activity on the network. Should a particular platform vendor encode CDR's in non standard protocols, customization on the TPS is required. The TPS usually consists of standard functionality to decode all standard CDR encoding protocols like XML, CSV and ASN.1. This is probably one of the most important functions of the TPS within the telecommunication industry, as any error in the decoding process will result in inaccurate, unreliable information being passed onto downstream processes and ultimately to the reports viewed by the management. Once the TPS has successfully retrieved all the CDR batches, its first task is to decode the CDRs into human readable ( ASCII) format. Decoding / Enrichment and Loading of CDRs 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. Some governments require that a record of each and every transaction needs to be stored infinitely in its raw (encoded) format. Once batch files are retrieved from a particular network-element, they are backed up to long-term media. Checking for duplicate files from the particular platform is also a responsibility of the TPS to ensure that no file is processed more than once, resulting in duplication of CDRs. The TPS is also responsible for ensuring the integrity of each file transferred, ensuring that no IP network errors render the file corrupt. Some platform vendors have developed their own file transfer protocols, in which case, the TPS need to be customized in order to retrieve the batch files from these platforms. The TPS uses standard network protocols, including FTP, SFTP and FTPS to transfer the CDR batch file to the TPS. The TPS is configured to periodically check each platform for any new CDR batches becoming available. Encoded CDRs are grouped into batches and periodically moved to locations from where the TPS can collect the CDR batches in order to process it. Some platform vendors develop their own encoding protocols for security reasons. Various formats and protocols are used to encode these CDRs, some example encoding protocols used includes ASN.1, XML and CSV. The recorded transactions, is called Call Data Records(CDR).
![transaction processing system companies transaction processing system companies](https://images.wuzzuf-data.net/files/company_logo/Statements-for-Consulting-Egypt-8643-1612016739-og.jpg)
All available information about the particular transaction is recorded and encoded into different formats. 3 Decoding / Enrichment and Loading of CDRsĮach activity occurring on a specific network element within the telecommunication network, is recorded by the particular platform.
![Transaction processing system companies](https://loka.nahovitsyn.com/6.jpg)