SM architecture

The Subscription Manager handles all of the logic related to charging, subscriptions and rules, thus isolating the core from the related provisioning overhead.

smt architecture


Key components

Core Service Logic

All charging requests are handled by the core service logic which acts as a logic server. All the rating rules are pre‐loaded in memory which ensures fast response times.


Caching and Optimisation

Prices can be cached by the core service logic to optimise the performance and response times.


Subscription Manager Core

The subscriber’s opt‐in/opt‐out information can be retrieved from the Subscription Manager as well as from external databases to determine the portability status and type of the subscriber (prepaid/postpaid/hybrid).


Catalogue Manager

The product catalogue is a database of products, prices and rules. The profiles are retrieved from an in‐memory catalogue manager that has all the rules regarding subscriptions and the charging associated with these to prepare the offering for the subscriber.


Charging and Billing Logic

The charging logic is integrated with the external charging and billing systems. It performs the charging of subscriptions based on the prices and rules configured in the product catalogue. The charging manager provides the service switching function for charging over diameter SCAPv2. There is also a built‐in audit manager which periodically checks if there are any reconciliation mismatches and if any are found, an alert is raised via SNMP and mail.

Any mismatched subscribers can be blocked/quarantined until further action is taken by the administrator.


Lifetime Manager

The lifetime manager handles the life‐span of the subscriptions for each subscriber. The lifetime of a subscription is based on the rules set up in the product catalogue; where the list of specific products and payment schemes is configured for the subscriber.


Notification Manager

The notification manager handles the notifications which are sent to subscribers when subscription events occur. The notification manager interfaces with the SDP/CCN via XML HTTP (or SMPP 5.0 as an optional feature).


Web Interface

The Subscription Manager has a management GUI which allows network operators view and manage each subscription scheme, rates, prices, offers of services as well as whitelists and blacklists for each subscriber. It also allows network managers to monitor system status, alarms and events etc. A Web Services API is also provided which can be used to allow subscribers and operators to manage and view subscriptions for a specific service of group of services as well as view the rates for each service.


Database Interfaces

Subscriber profile database interfaces are provided for opt‐in/opt‐out screening and retrieval of subscriber profiles and preferences.


CDRs and Statistics

Dedicated CDR and statistics handlers are provided as part of the iAX™ Subscriber Manager to handle the generation of comprehensive CDRs and statistics.


Reporting and Reconciliation

All iAX™ Subscription Manager transactions are recorded in a separate CDR log. The log is designed to support reconciliation with the content providers. Detailed statistics are also recorded.


Interfaces

Apart from the standard network interfaces, the Subscription Manager also interworks with a range of network elements to provide notifications, offload CDRs, for Operations and Maintenances and so on. The sections below show the types of interfaces.

Customer Care

Subscriber customer care interfaces are carried out via web services.


Service activation

  • Interface to AIR Interface (via UCIP ‐ XML/RPC HTTP) ‐ Subscription activation.

  • Interface to ASAP for provisioning of the network elements (Web service).

  • Interface to PCRF (LDAP/Gy).

  • Interface to SDP/CCN via XML (SOAP or RPC).

  • Interface to CCN (SMPP v5.0) ‐ Optional

  • Interface to SPR (LDAP)


Web service channels

Web services connect can connect via M2K/PAC/PC/WAP, etc.


Online charging service (OCS) interfaces

The OCS interface uses Diameter SCAPv2 for charging.


Internal interfaces

  • External DB interface is supported for inter‐working with an external database, Oracle, MySQL and optionally LDAP.

  • For notifications using SMS, the platform supports SMPP and XML HTTP (SOAP and XML/RPC).

  • A web services API is supported for integration with operator self‐care and customer care systems.

  • FTP is used for off‐loading CDRs, statistics, alarm logs and other system logs to mediation systems or directly to warehouses.

  • Other O&M related interfaces include SNMP traps for raising alarms to external NMS, and HTTP for web‐based O&M.


Additional interfaces

A Sync Interface is available to synchronise subscriptions with the SDP.