Zone Model-Based Pricing

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Zone model-based pricing enables monetization using Standard or Geographical zone models. Key attributes for zone model configurations include:

Calling party—also referred to as Call Originating Number or A-party number
Called party—also referred to as Call Terminating Number or B-party number
Distance—the distance between the calling and called party, used in Geographical zone models

Expected Result

The system applies pricing based on the calling party and called party (for example, calls from the US to EU countries, or calls from the EU to the rest of the world).

Variants

Pricing based on distance between the calling and called party
Pricing based on zone setup using wildcard expressions (for example, a called party zone configured as 44* for calls to any number in the UK)
Pricing based on best match for zone setup (for example, called party zones configured as 44123* and 44*, where a called party number beginning with 44123 matches the 44123* zone rather than 44*)

Setup

Set up zone model configurations under Configurations > Models > Zone Model. Refer to the Zone Model Configurations section under 3. Allegro Configurations > Models > Zone Model for details.
Set up the plan, plan rate schedule, and plan services in core Aria.
In Aria Allegro, set the price offer for usage services as follows:
1. Set Pricing Model to Transaction Attribute-Based, or to Composite if combining with other models. A Transaction Attributes section appears in the UI.
2. Leave time model attributes blank, or set them to ANYDAY, ANYTIME, and ANYHOLIDAY.
3. Select Zone Model from the dropdown list of applicable zone model configurations for the service type. If only one zone model configuration is set up for the service type, it is selected automatically.
4. Select Zone from the zone model configuration dropdown. Options include configured zone names.
5. Add currency rates, accumulator impacts, and allowance impacts as needed.
Use Add Transaction Attribute to add additional pricing combinations. Repeat step 3 as needed. Aria recommends setting up a default zone with fall-through pricing where both the called party and calling party are set to * (any) and configuring rates for this default zone.
The rest of the setup and processing remains unchanged.