Network

In the Network In the context of CMP, the infrastructure on which usage of registered customers will be measured – this could be a mobile phone network, broadband network or other non-telecommunications network. module of Business Configuration A module in the CMP Administation console that provides for viewing and modification of business and user applicable system configuration. you can define network commands, configuration and other network parameters. This includes:

• Networks
• Network Commands
• Network Command Groups
• Network Features
• Network Feature Defaults
• Subscription A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription Groups

Networks

Networks and their associated settings can be configured. This includes the change rules and serial numbers that are configured for a particular network. Change rules define what numbers allocated to a subscriber The end user of a network. can be updated for a given network, and could be the mobile number, SIM Subscriber Identity Module. A smart card (electronic chip) inside a mobile phone that communicates with the network and carries an identification number unique to the owner. The SIM can also store personal data. number, and so on.

Both managed and non-managed serial numbers are defined for a selected network. You can also maintain alphanumeric prefixes for managed serial numbers, or list values for non-managed numbers.

Network Commands

Commands are used in CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. to send specific information to the required network in order for the network to carry out the required behaviour (the network action) - for example, to apply a bar when a customer In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement. has lost their phone, to provision a new subscriber or to apply a change of tariff.

Network commands can be organised in command groups, for example by type of command or by network. In Business Configuration, you can create, edit and remove network commands. You can also configure network command attributes.

To create a network command, you:

• Provide a unique alphanumeric code for the command and a brief meaningful description.
• Choose the network action type: connection, disconnection, bar, unbar, network service, number change, tariff change or other.
• Indicate if there is to be a parallel command.
• Specify whether the command is an admin bar.
• Indicate whether the command is active and is thus available to new subscriptions.
• Provide an optional explanation to help future Business Configuration users understand the network command.

Network Command Groups

You can create network command groups to organise network commands, for example by grouping all the commands for a particular network together. This can simplify adding multiple commands to other CMP components.

To create a network command group In the Customer Manager Platform hierarchy, the highest level of the structure. The group level can be used to group corporates. Groups can hold financial information. you:

• Provide a unique alphanumeric code for the command and a brief meaningful description.
• Indicate whether the command group is active.
• Provide an optional explanation to help future Business Configuration users understand the network command group.
• Add network commands as group members.

Network Features

Network features are subscription features that can be provisioned onto the underlying service provider The owner of the infrastructure in which accounts will be created. The Service Provider can host and operate the instance of CMP, or CMP can be provided as a Managed Service. network to offer additional network capabilities for the subscriber. These can include, for example, bars, spend caps or premium services. Features can correspond to network attributes or OCS attributes.

To make the feature available to a subscriber, the feature is then enabled via AgentView The graphical user interface of the CMP that is typically used by Customer Service Agents to access CMP customer and billing data. In versions prior to CMP 8.0, this was called the CMP GUI. or the Set Feature web service XML- or JSON-based information exchange systems that use the Internet for direct application-to-application interaction. These systems can include programs, objects, messages, or documents.. Features can also be disabled in the same way.

So for each feature, you need to define either:

• Enable and disable workflow events.

Or

• Bar and unbar workflow events.

Regardless of the workflow event you configure, features appear only as enabled or disabled in AgentView or by web services. Only one action is allowed on a feature workflow.

Example:

A feature called International Calls Bar can be configured with enable and disable workflow events. The same feature could be configured with bar and unbar workflow events.

Alternatively, the same feature can be named International Calls and configured with enable and disable workflow events, or bar and unbar workflow events.

A feature can be configured to daily charge when the feature is enabled.

A feature can be barred or unbarred. These are normal subscription bars, that is, visible from AgentView Subscription Summary. Features cannot be manipulated by adding or removing a service.

To create a network feature you:

• Provide a six-character code for the feature and a meaningful descriptive name.
• For an online charging implementation, select the network.
• Optionally provide additional descriptive text.
• Specify whether the feature is a bar feature.
• Select the corresponding feature name in the OCS.
• Indicate whether the feature can be controlled by the subscriber.
• If the feature is a bar feature, specify the following:
  • Event type and code for the bar workflow event.
  • Event type and code for the unbar workflow event.
• If the feature is not a bar feature, specify the following:
  • Event type and code for the enable workflow event.
  • Event type and code for the disable workflow event.
• Choose whether the feature enables a charge.
• Indicate whether the feature is active, that is, available to new subscriptions.

Network Feature Defaults

You can configure default behaviour for network features for specific network, for example whether a bar is enabled by default for one network, but disabled by default for a different network. Network feature defaults provide AgentView and web services with a default view of the expected state that network features should be in at connection. These are not provisioned at connection time.

To configure a network default, you:

• Select the network (for online charging implementations only).
• Specify the network type - postpaid or prepaid.
• Choose the network feature.
• Select the default state for the feature.
• Indicate whether the feature is active, that is, available to new subscribers.

Subscription Groups

Subscription Groups are a means to further categorise subscriptions with similar capabilities and usage The consumption of services, for example a subscriber using call minutes. patterns, for example pre-paid.

To define a subscription group, you add the description and code for the network under which the subscription group is defined, a description and code for the grouping of subscriptions, and the description and code for the network command group.

You can access the workflow events that are used to create and disconnect subscriptions, and the rules that define what group changes are supported for the selected subscription group.

Subscription Group Links

You view and manage the links for a subscription from the following tabs:

• Connection Events

  These define the workflow events that are used to create a subscription in CMP and on the associated network.

• Disconnection Events

  A disconnection event indicates if the subscription is also terminated by the workflow event.

  When a subscription is disconnected, it can be terminated and receive the final bill, or disconnected but not terminated and continue to be billed, for example if there are still outstanding charges such as handset A mobile phone charges. This tab displays the disconnection workflows configured for a given network and subscription group, and include details about the Event Type, Event Code, and if the disconnection is valid (Termination? Yes or No).

• Group Change Rules

  The Group Change Rules define what changes are allowed between subscription groups. This change is related to a Price Plan change - a price plan has a tariff linked to a subscription group, and changing the price plan can result in a subscription group change, and what is supported for a given network.

  This tab displays the group change rules that have been configured for a given network and subscription group, and includes the Network description and code, and the Subscription Group description and network code to which the change applies.