...
The rate plan is basically the plan that the customer signs up for. It is essentially a container for one or more rate groups. A rate plan can be assigned to a bucketservice, a tier in a bucket, a service or a packagepackage an account or an owner. The order of precedence is from the lowest to highest to lowestlevel: bucket, service, package, account, owner.
Rate plan inheritance is also supported, where a sub child account can inherit a rate plan configured at the parent level. A rate plan is defined by a name. Each rate plan configuration also defines the level of precision used by the rating engine when processing charges associated with that plan; LogiSense supports up to 11 places of precision.
...
A Rate Group defines the umbrella under which a rate applies. For example, in the telecom and UCaaS scenarios, different rates are applied to domestic vs. international calls. In such a scenario, a provider can define two rate groups: one for domestic and one for international. Furthermore, a provider may desire to charge a different rate for each group based on time period - for example, data usage during peak hours may be charged a higher rate than non-peak usage. Rate group conditions can be attached to each rate group to accommodate the peak vs. non peak rates or other conditions that you wish to configure.
Usage Class
A Usage class identifies the type of usage that is going to be charged by the rating engine. Usage classes must be configured prior to creating rates. A Usage Class can have one of the following types:
...
Along with the data type, the class configuration also defines whether the rating is class based or Geotree GeoTree based. The major use of the GeoTree is for location or zone based service rating (i.e. telecom calls). Unlike most systems which have you simply enter a calling pattern (i.e. 1212) and associated rate, without any real understanding of where it is entered or structured, LogiSense allows you to get as granular as you like within a structured tree. For instance, you can define what actually makes up the calling patterns within a state, deploy rates based on zones, set top level rates (one price for the Continental US instead of having to define each individual pattern), setup rates by regions, types or operators (allowing you to specify a different rate based on which mobile operator's network the user is on).
...
When looking for a rate, the rating logic will determine the appropriate rate plan associated with that usage. As explained previously a rate plan may contain multiple rate groups based on rate group conditions. The rating engine will choose a rate group that matches the given conditions. A rate group can contain one or more rates once again subject to conditions such as the class of usage (Data vvs. s. API v.svs. Voice) and location groups. Once the correct rate is determined, the system will apply that rate to the usage being rated and calculate the charge.
...