Service Order Management — Part 3: Resource Allocation and Service Activation

Idea Light Bulb Touching on Visual Screen

In the previous two articles in the Service Order Management Series, we discussed processes for offering subscriber services as well as capturing and validating orders. Next up in our process steps are resource allocation and service activation.

Resource Allocation

Some service types require equipment or some other allocated resource, e.g. a phone number. They also need to be managed so that if we need to activate a data service for a cable subscriber, we will need to allocate this resource from (typically) an inventory database.

resource--allocation
For such service types, this order management step should check to see if resources are available to fulfill the order. Typical resources include customer premise equipment, port availability, telephone numbers, and so on. If resources are not available, then the order should be pushed to an error-handling subprocess.

Validating a subscriber’s order may involve integration of the following components:

  • Inventory Database
  • Order Management Server

Service Activation

 

service--activation

For successful service activation, we need to connect to the various network servers and devices in order to activate the desired service. The complexity here is that there are many different types of servers using many different communications protocols, such as SOAP, REST, CORBA, TL1, and so on. Usually new servers will use newer communications protocols but there are still many older protocols in use today.

With service activation, the trick is to abstract the communications protocol from the business process logic. This abstraction provides the ability to plug and play adapters to third party systems with minimal or even no changes to business processes. For example, if a service provider changes from one vendor’s TV CAS (Conditional Access System) to another vendor’s equipment, the core business logic can stay intact but the adapter to the third party system will change.

The business logic can usually be broken down into the following:

  1. Service activation (Create)
  2. Service deactivation (Delete)
  3. Service upgrade/downgrade (Update)
  4. Service suspend/resume (Update)
  5. Service get (Read)
  6. Other:
    1. Service: refresh, synchronise
    2. Device: reset, initialise, swap, probe

Typical network servers include:

  • Data: DHCP, DNS, AAA
  • Voice: Softswitch, Tariff, Phone Credit, Call Features
  • TV: CAS, IPTV platform, VOD
  • Other: E-mail, Web Host

With resource allocation and service activation complete, we now move onto the next processes in our order management cycle, Installation and Activation Validation. These will be covered in the next part of the Service Order Management Series.

  • Share: