|
 |
| |
CRESTEL Architecture |
| |
| CRESTEL architecture is a carrier grade modular architecture which support multiple services on its platform. CRESTEL has a multi-tier architecture. Each tier communicates with other tier through published API’s on TCP/IP protocol means CRESTEL architecture can seamlessly integrate with 3rd party elements and support different services on a single platform. |
| |
|
| |
|
 |
The Network layer |
| |
This layer constitutes a range of network devices including Access Servers, UMTS, GGSN, Cisco Netflow Collector and many more such devices. |
| |
|
|
The Mediation layer |
| |
This layer constitutes the Provisioning server, RADIUS and Mediation Engine. Components at this layer interact with elements in the Network layer via varied protocols such as SOAP over HTTP/XML, AAA, SNMP, FTP/FTAM. Mode of exchange can be in real-time or in batch mode and can be through push or pull techniques. A new device added in the Network Layer enables services by adding a new plug-in in the Mediation and Provisioning layer. All components at this layer can run on multiple instances and also on different machines. Thus it facilitates billing to be distributed as well as scaleable. The mediation engine collects raw usage data and formats it according to billing layer requirements. |
| |
|
|
The Billing Platform |
| |
This platform is the central hub of the overall architecture, it Interacts with every layer through published APIs on TCP/IP layer. The Billing platform constitutes Billing, Rating and the Database store. The Billing platform interacts with mediation through published APIs. This gives tremendous benefit of being open and expandable. |
| |
|
| |
Rating collects formatted xDRs from Mediation layer, filters them, correlates them, applies rates, usage discounts, promotions, submits rated usage records to billing engine. Rating can run on multiple instances and also on multiple machines for scalability requirements. Rating can be done in batch or real-time. |
| |
|
| |
Billing takes input as rated records, applies taxes, discounts, calculates charges and finally generates invoice records for every customer. Billing can take rated records from 3rd party rating engine, 3rd party billing system and can also exchange invoice records to 3rd party systems like FAS, Billing Printing. All these is possible because of well published APIs of Billing. The Billing Engine can also run on multiple instances and in multiple servers. Agent can run in cluster because of this concurrent processes can take place so that TPM can be reduced. |
| |
|
|
Customer Care |
| |
This includes the CRM, Customer Order Management and interface to external messaging systems. This layer is also independent of other layers of the system. Thus CRM as a whole layer can be in public LAN which is direct interface to customer and call centre. Customer care interacts with billing, customer management, 3rd party messaging system through well published API’s. |
| |
|
|
Back Office layer |
| |
Product and Tariff management in back office layer interacts with billing, rating, 3rd party payment merchants. |
| |
|
| |
Finally the architecture merges in to Convergent Platform where we have a gamut of services on voice, data, video and content supporting different business models. |
| |
|
| |
 |
Diagram |
| |
|
|
|
|
| CRESTEL Architecture |
 |
|
