Rate Table Examples

The following shows examples of rate tables (created using My MATRIXX) for various charging scenarios.

Phone Network and Friends and Family

In this example, different rates are applicable to phone calls based on whether the call is placed within a local or long distance phone network, whether the call is within a Friends and Family group, or both.

For example, Figure 1 shows a rate table that uses a decision table containing two normalizers, Voice Zone and Friends Family, to charge for phone calls. The Voice Zone normalizer has two possible parameters, Local and Long Distance, and the Friends Family normalizer has two possible parameters, Normal Call, and Friend Call.

Figure 1. Free Local Calling for Friends and Family

This rate table contains 4 rows to handle all parameter value combinations—two Zone values and two Friends Family values (2 × 2 = 4). When the call is made, the MATRIXX Charging Application uses the information in the network message to determine which row in the rate table is valid and applies that rating formula.

As a more complex example, say a voice product offer contains a charge that uses three normalizers: voice zone, time-of-day, and device type:

  • The voice zone normalizer has four possible zone parameters: Domestic, Zone 1, Zone 2, and Zone 3.
  • The time-of-day normalizer has three possible time parameters: Peak, Off-Peak, and Weekend.
  • The device type normalizer has two possible values Blackberry and Smart Phone.

The charge will contain one rate table with three columns (one for each normalizer) and 24 possible rows. Each row defines a rate for a unique combination of the possible values—three possible time band values, four possible zoning values, and two possible device type values (4 × 3 × 2). If the value combination in a row is not relevant to your pricing strategy, you can omit the row or choose to skip it.

When a subscriber with this product offer makes a call, the MATRIXX Charging Application uses the call origination and destination values, the event time value, and the device ID to determine which row is valid and uses that rating formula to calculate the charges. The rating formulas all define charges based on the usage quantity (call duration), but they charge different amounts based on the parameter values valid at the time of the call.