Document Logs
Change log:
Date: |
Author: |
Version: |
Changes: |
Completed |
Ext. |
Int. |
Is in Core |
|---|---|---|---|---|---|---|---|
27 October 2011 |
Rida Riaz |
1.0 |
|
No |
x |
|
|
|
|
|
|
|
|
|
|
Reference log:
Document: |
Version: |
Date: |
|---|---|---|
|
|
|
Distribution log:
Date: |
Distributed to (f. ex. name, title, company, email): |
|---|---|
|
|
Terms and Definitions:
Terms/definitions: |
Meaning: |
|---|---|
N/A |
Not applicable |
TBD |
To be defined |
The Rating Process
This document describes the flow of the Rating Process and could also be used to track down rating errors by following the steps of the rating process and finding out which step is failing.
The rating method defines how the different elements of billing record and price configuration are combined together to determine the cost of the particular usage handled by the number plan. Billing records are rated against subscribers.
The first activities are aimed at finding the subscriber and his/her rate plan. Once the number plan is known, the standard rating (or rating as per price configuration) happens.
The Rating Flow ">The Rating Flow
Unable to render embedded object: File (Rating_Process.png) not found.
Step 1
The rating process starts when a billing record is received. The billing record contains the subscriber's information such as the ICC, IMSI or the Anumber. The billing record also contains the event information, the date, time etc the call/event took place. The rating code, rating key or the Bnumber is also available in this record. All this info is very important because in each step of the rating process, this info will be compared with the product configuration stuff.
Step 2
The IMSI/ICC/Anumber is then picked up from the billing record and is used to find the relevant rate plan. The rate plan could be seen in the Product Configuration, 'Products, Rate Plans & Options'.