Skip to main content
Skip table of contents

Zone Models Management (FT-1003.004)

About this document

Scope

This document provides background information as well as a functional description of the FT-1003.004 Zone Models Management standard feature. The described feature is supported from the release version 4.0 onwards.

Note

Zone Models Management is a standard feature and does not require a special license.

This feature is part of the Usage-based Charging functionality with number FN-1023.

Feature Availability

Feature Version

Available from

Summary of changes

v1

CMP Release 4.0

Initial release 

v2

CMP Release 4.3.8

External Zone Number added


Feature overview

Goals

The aim of the Zone Models Management feature is to allow CSPs to create different geographic charging Zones. The Zone Model is a set of Zones, which can be imported when creating a Zone Price Plan. Each Zone can then have a different included allowance and overage rate.

Out of scope

  • Modifying any Zone or Zone Model once activated (i.e. not in status Draft)

Functionality of the feature

A Zone Model is a collection of Zones for the purpose of charging one monthly fee for each of the Zones. The Zones are comprised of a set of Networks. In order to simplify Zone creation, individual Networks, Network Groups, or Countries can be selected to be part of a Zone. Zone Models are used to create Zone Price Plans in the CSP Portal.

Two types of Zone Models are supported in the CMP.

NETWORK

Zones of the Zone Model are defined by Networks and Network Groups (Location Zone Model).

COUNTRY

Zones of the Zone Model are defined by Countries (Destination Zone Model).

Each Zone Model created within the CMP must have at least two Zones: the Home Zone and the Rest of World Zone. In addition, the Zone Model can also contain a number of custom Zones.

Example

Zone setup for networks in the EU

  1. the Home Zone - usually the networks of the country of residence of the end customer,

  2. a single custom Zone - covering the rest of the EU, and

  3. the Rest of World Zone - covering

literally the rest of the world, since any network not defined in the other zones will automatically fall into the Rest of the World Zone.

The Home Zone and the Rest of the World Zone are created automatically at the creation of a Zone Model. It is verified that when a Zone Model is deleted, the Rest of World Zone is also deleted.

External Zone Number

The External Zone Number is fully optional, but has to be unique within a Zone Model. External Zone Number Validation is enabled or disabled on the CMP instance using a configuration item. The configuration item's available values are:

  • Disabled,

  • Enabled, and

  • Enabled without RoW (Rest of World Zone).

External Zone Number Validation is by default disabled.

Some constraints apply to External Zone Number Validation.

  • If External Zone Number Validation is Enabled the value of External Zone Number has to be unique per Zone Model and can't be empty.

  • If External Zone Number Validation is Enabled without RoW

    • the value of External Zone Number has to be unique per Zone Model and can't be empty, and

    • the value of External Zone Number has to be empty at Rest of World Zone.

  • If External Zone Number Validation is Disabled, the value of External Zone Number has to be empty.

When activating a Zone Model,

  • if External Zone Number Validation is Enabled, all Zones of the Zone Model are verified and in case any of them has an empty External Zone Number, the User is presented with an error message and the Zone Model won’t be activated,

  • if External Zone Number Validation is Enabled without RoW,

    • all Zones (excluding for the RoW Zone) of the Zone Model are verified and in case any of them has an empty External Zone Number, the User is presented with an error message,

    • the Rest of World Zone is verified and in case the External Zone Number is populated (i.e. not empty), the User is presented with an error message and

    • the Zone Model won’t be activated.

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.