Page Comparison

{noprint}{float:right|width=300px|background=#FFFFCE|border=solid blue 2px|margin=10px|padding=8px}
*Contents*
{toc:all=true|depth=4|excerpt=true|indent=14px}
{float}{noprint}{table-plus:width=665|enableSorting=false}

















































*Document Logs*
*Change log:*
|| *Date:* || *Author:* || *Version:* || *Changes:* || Completed || *Ext.* || *Int.* || *Is in Core* ||
| 27 October 2011 | Rida Riaz | 1.0 | \\ | No | x \\ | | |
| 31 October 2011 \\ | Luca Casarini \\ | 1.1 \\ | Review \\ | No \\ | x \\ | | |
| 31 *Reference log:*October 2011 || *Document:* || *Version:* || *Date:* ||
| Product configuration documentation  SD\\ | 1.1\\ | Checked\\ | Yes\\ | x\\ | | |
*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 |

----














































h1. The Rating Process


This document describes the activities which the Rating Process executes in order to rate billing records against subscribers. Any missing information throughout the process will move the billing record to the error queue; hence this document could also be used to track down rating errors by following the steps of the rating process and finding out which information is missing in the system (and most likely in the product configuration). Please note that understanding the rating process requires knowledge of the product configuration.


















































h1. {color:#003366}{*}The Rating Flow{*}{color} 

 
\\






----


h2. Rating Process


This page describes the activities which the Rating Process executes in order to rate billing records against subscribers. Any missing information throughout the process will move the billing record to the error queue; hence this document could also be used to track down rating errors by following the steps of the rating process and finding out which information is missing in the system (and most likely in the product configuration). Please note that understanding the rating process requires knowledge of the product configuration.


h2. Rating Flow

{gliffy:name=Rating Process|align=left|size=M|version=1}











The rating process starts when a billing record is received. The first activities of the rating process are aimed at finding the subscriber and his/her rate plan.






















h3. Step 1 - The billingBilling recordRecord
The billing record contains the subscriber's information such as the ICC, IMSI or the AnumberA-number - depending on the implementation of the system. The billing record also contains the event information:, i.a. the date and time when the event took place, the rating code and rating key or the bnumberb-number. This information is very important, because each step of the rating process will use it against the product configuration. 

































 use it against the product configuration. 


h3. Step 2 - Find the rateRate planPlan
The IMSI/ICC/Anumber is picked up from the billing record and is used tofor findfinding the subscriber and the theirassociated rate plan.
\\
\\
The rate plan could be seen in the *Product Configuration.* In the screenshot below, the rate plan is 'Fixedline'.

!rate plan.jpg|border=1!
































h3. Step 3 - Find the numberNumber planPlan
AfterWhen the rate plan is found, the rating process will look into the tele rates and find the number plan linked to the service code within the tele rates. The Ratingrating process uses the rating code from the billing record to find the service code and therefore the number plan.

\\
In order to look atexamine the number plan, select the relevant rate plan and then click *Edit*. This will open up the 'Edit Rate Plan' popup. Select the 'Service Code' under 'Tele Rates' to can see the associated number plan in the 'Number Plan' panel. In the screenshot below, the rate plan 'Fixedline' has athe service code 'NATIONAL CALL', and the number plan associated with this service code is 'Mobile National'. The rating process will compare the event/charge date present within the billing record with the from and to datedates listed in the number plan configuration.




!edit rate plan - number plan.jpg|border=1!





























h3. Step 4 - Find the bnumberB-number methodMethod
After finding out the associated number plan, the rating plan moves on to the number plan and looks at the configured bnumberb-number method. Keep in mind that the type of bnumberb-number method depends on the configuration of the customer. It could be _getRatingKey_ or could also be _getBNumber_ method. If it is getRatingKey, then the rating process will look at the rating key given in the billing record and compare it with the configured plan elements. If it is the getBNumber method, then the rating process will pick up the bnumberb-number from the billing record and compare it with the available plan elements. The rating process finds out the plan element using the 'Best Match'.
\\
\\
The rating key or bnumberb-number method for the number plan could be seen by looking at 'Number Plans'. Select the number plan that was selected in the 'Edit Rate Plan' from the 'Number Plans' GUIpanel. After selecting the number plan, click *Edit*. In the 'Edit Number Plan' popuppop-up the bnumberb-number method can be seen. In the screenshot below, the bnumberb-number method for the number plan 'Mobile National' is 'getRatingKey'. This means that the rating key mentioned in the billing record will be taken in order to find the plan element in the next step.




!bnumber method.jpg|border=1!





























h3. Step 5 - Find the planPlan elementElement
The rating process finds the plan element via 'Best Match' using the bnumberb-number method information. Once the plan element has been found, the rating process looks at the rate day information associated with that plan element.

In order to look at the plan element, use the bnumberb-number method to select a plan element from the 'Plan Elements' panel. For example, if the bnumberb-number is getRatingKey, then compare the value of the rating key with the available plan elements. In the screenshot below, 'MOBILE..Mobile national' is the plan element selected when looking at the rating key in the billing record (for example the rating key = MOBILE).




!plan element.jpg|border=1!




























!plan element.jpg|border=1!



h3. Step 6 - Checking the rateRate daysDays
Now the rating process looks at the configured rate days. The rating process will compare the event/charge date present within the billing record with the start and end datedates listed in the 'Rate Day' configuration.


In order to look at the 'Rate Day' configuration, select the relevant plan element and then have a look at the 'Rate Day' panel. Please note that the charge/event date should be equal to or shoudshould lie between the configured dates. In the screenshot it can be seen that the rate day is 'N-SINGLE' and has an open start and end date.




!rate days.jpg|border=1!






























h3. Step 7 - Checking the dayDay chargesCharges
 After the rating process hadhas found the rate day then, it looks at the day charges. It again compares the charge/event data present in the billing record with the configured day charges.


In order to look at the 'Day Charge' configuration, select the relevant 'Rate Day' and then click *Edit*. On the 'Edit Rate Day' popuppop-up, there will be a 'Day Charge' panel. Please note that the day the charge/event took place should be within the configured days. In the screenshot it can be seen that all the days of the week are selected for the rate day 'N-SINGLE'.



!day charge.jpg|border=1!































h3. Step 8 \- Checking the timeTime chargesCharges

After looking at the day charge, the rating process looks at the time the event occured. The rating process would look at the start and the end time configured for the day the event ocurredoccurred.

In order to look at the 'Time Charge' configuration, select the relevant 'Day Charge', to see the 'Time Charge' configured for the selected day. Please note that the time the event took place should be within an already configured time charge. In the screenshot below the time configured is 00:00 til 24:00.



!time charge.jpg|border=1!
























!



h3. Step 9 - Finding the chargeCharge itemsItems

The rating process will now look at the charges defined for the time the event took place. It would pick up the relevant charge and use it tofor raterating the event.

In order to look at the configured charge items, double click or *Edit* the 'Time Charge'. In the 'Edit Time Charge' popuppop-up, the configured charge items are present. Please note that the charge item for the time selected should be present, otherwise there could can be no rating and the rating would fail. In the screenshot below, both the 'Initial' and 'RecurentRecurrent' charge items have been configured.  



!charge item.jpg|border=1!






























h3. Step 10 - Successfully ratedRated billingBilling recordRecord
If there are no missing or misconfigured items in each of the above mentioned steps, and they run successfully, then the rating process will result in the successful rating of the billing record.

*NOTE: Any {note}Any missing information or misconfigured items on any step of the rating process, will result intoin failure of the rating process, and the respective billing record will end up in the 'Error Queue'.  * 


































{note}


{table-plus}