Transformation of OSS/BSS architecture

Traditional Architecture Of OSS/ BSS

 The term OSS describes "network systems" dealing with the telecom network itself and supporting processes such as maintaining network inventory, provisioning services, configuring network components, and managing faults. The term BSS typically refers to "business systems" dealing with customers and the supporting processes such as taking orders, processing bills, and collecting payments etc. Originally, these were mainframe-based, stand- alone systems designed to support telecom company’s staff members in their daily jobs.These systems used to be very complex and tightly coupled with each other. A small change in one system could affect all the interfacing systems.

In today’s scenario the next - generation service providers are required to manage a much more complex set of products and services in a dynamic and competitive marketplace. These systems ultimately help in enabling next-generation service providers to reduce costs, provide superior customer service and accelerate their time to market for new products and services.

                                        

Limitations of traditional OSS/BSS Architecture

The traditional OSS/BSS architecture includes custom development of integration code which is inadequate in satisfying the requirements of telecom service providers. Integrating systems when multiple TSP’s collaborate is also a challenge.  Common problems in traditional OSS/BSS architecture are:

•         Point to point integration

: OSS/BSS architecture involves integration with multiple external systems. For example, changes made into CRM system by CSR needs to updated into billing system automatically. This requires a number of interfaces between these external systems so that they can talk to each other. Such an approach is time consuming and integration is fragile. Furthermore, the integration does not offer end-to -end process picture that is essential to structure and reduce integration complexity.

•         Tightly Coupled.

Business rules and integration logic is tightly coupled with software components and any change in business environment will require overhauling and rebuilding application. OSS/BSS system is not flexible to handle frequently changing business requirements like introduction to new policies and service offerings..

•         Integration with External Systems

 External systems have their legacy implementation technologies which make the interaction with them difficult and require huge development effort. Also, each external system understands its own set of data types, so a transformation model is also required to convert information from one system to another.

•         Complex Transaction Management

Any operation performed by end user appears to be a single transaction. But the corresponding changes needs to be committed to multiple systems. For example, creating an account involves creating an account in billing system, LDAP, CRM System.

Integration Architecture

Mobile services are becoming more and more diversified. They range from basic circuit switched voice service to packet switched data services with multitudes of applications, both in the network and the handset. The services may have complex pricing rules and they require correct settings in multiple independent network elements. Many services are provided by third parties, which are outside the control of network operators.

The integration enablers consist of the integration technology platform (OSS and IT middleware), with both generic framework and OSS/BSS-specific abstraction services, which are accessed through standard APIs when possible. The solution for the end-to-end automated fulfillment consists of the following components:

BSS layer:  A self service (web) portal, where the subscriber is able to manage his subscription and activate new services and deactivate unwanted ones, customer Relationship Management (CRM) system, order management, subscriber management, pricing and rating information and charging & billing system. All these are included in BSS.

OSS layer: Resource inventory management and service management in OSS would serve as an effective measure.

Shruti Bhardwaj

Class of 2014