In telecommunications rating is the activity of determining the cost of a particular call.[1] The rating process involves converting call-related data into a monetary-equivalent value.
Call-related data is generated at various points in the network or measurements may be taken by third party equipment such as network probes. Generally this data is something quantifiable and specific. The usage data so gathered is then either packaged by the equipment or it may be sent to a charging gateway.etc.
Rating systems typically use some or all of the following types of data about a call:
Generally individual calls are rated and then the rated amounts are sent to a billing system to provide a bill to the subscriber. Often the rating system will be a module of a larger "Billing System" architecture.
A rating system must be adapted to the constantly changing pricing policies, which have the strategic goal of stimulating demand.[2]
To perform the rating calculations it is necessary to produce a Call detail record/EDR. A Call detail record[3] [4] (CDR, also known as Call Data Record)[5] is "a record of a call setup and completion",[5] and its format "varies among telecom providers or programs", which some allow to be configured by the user.[6]
EDR stands for Event Data/Detail Record. EDR records are used for systems that charge more than calls - content. e.g. buying ring tones. The generated CDR/EDR may not be in a form suitable for the particular rating system. In this case a piece of software, known as the mediation system, may be required to render the data into a form useful by the rating system. The mediation system is also useful for gathering data from various sources to aggregate into one record.
In spoken language CDR usually refers to any type of record: voice, SMS or data.
In complex systems there's the need of the flexibility to modify and maintain the system by an interface more human-readable than programming code, like editing tables where the behavior of the system is defined. This allows both a quicker editing and the possibility to let the configuration and maintenance of the system to non programmers, like business/tariff analysts. This flexibility comes at the cost of a heavier computational time. The support for "code external" textual configuration of both rating cases-amounts and the algorithmic rating process steps, is sometimes called "Rule-based Rating".[7] Rule-based rating is one simple example of the use of the more general control table technique.
As the telecommunications market comes under increasing pressure from new technologies (for example WiMAX), the leading differentiating factors between competing operators is often the innovation in new product offerings, and time to market. This leads to a natural tension between the capabilities that are offered by:
In real life situations, even the most configurable systems generally have an implementation phase, in which new capabilities are created using programming methods, and a configuration phase, in which the new capabilities are configured and offered to the mass market.
As competition increased in the telecommunications space, rating is getting increasingly complex. Some rating scenarios use multiple measurements.
Example:
Rating for a video download may involve measuring the number of minutes, the amount of data, the quality of data transfer as identified by the service level agreement (SLA) and the usage (copyright) cost of the video.
Example:
A data session representing viewing a video-on-demand session, with a one-off charge, should not charge the user for the data volume since it was already charged for the video. These two charging events are correlated and the data volume spent on streaming video isn't charged to the user's data bundle/account.
Complex rating could also involve non-network related parameters. Some of the rating data may come from the customer care or billing sub-systems.
Example:
When usage above a certain amount is triggered in the billing sub-system the rating engine may assign a lower rate for the user. This is also known as an adjusting rate and can be complex to model in certain systems.
Complex rating behaviour could be due to particular real or virtual behaviour.
Example:
Subscribers who play an affiliated on line game may trade in-game currency or equipment or incentive tokens for discounted calls to other players of the game.
Among the issues of rating that are unexpected sources of complexity is Daylight Saving Time time offsets.[8]
Modern rating engines may also be currency neutral. Certain multi-national telecommunication providers provide the ability for subscribers settlement in multiple currencies. In this scenario the rating engine generates a currency neutral billing record. It is the billing engine which is assigned with converting the virtual currency into an actualized cost.
In some scenarios it may be necessary to re-rate calls but not all rating engines are capable of this. There is a philosophical argument as to the usefulness of re-rating, with no clear correct answer: