RCB workflow
Now that you have installed, configured and deployed the RCB Cyclops framework, you can proceed with the Rating-Charging-Billing workflow.
Based on your underlying system, whether you are measuring CloudStack or OpenStack - both being IaaS, or you have developed your own collector for any PaaS, SaaS or IoT scenario, all events and usage records will be processed and persisted by UDR micro service.
Every single core micro service is listening on two queues, one being data queue and second designated for execution of predefined commands.
In case of UDR micro service the usage data records are being stored into InfluxDB time series database and based on developer's preference, published over RabbitMQ.
The usage data records are made available to you via RESTful API paginated queries, where more domain specific APIs are to come.
If you need to process ingested data points/events and create usage records manually, you can proceed by writing your own commands.
As the micro services can already process batches of data points, we will be releasing "flush" processing commands very soon.
As can be seen in the architecture picture, RC micro service consists of the following two components:
Once UDR publishes usage data records over RabbitMQ, it's the rating function that takes care of the calculation of charge data records. You can either use included [Static rating] (https://github.com/icclab/cyclops/wiki/Static-rating) micro service, [Rule engine] (https://github.com/icclab/cyclops/wiki/Rule-engine) with your own pricing strategies, or write your own.
which continues by persisting them into time series database, as well as making them available over RESTful API queries.
