Service Delivery Platform OSS BSS Integration via SOA
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Telecommunication service providers face challenges in integrating complex and archaic OSS and BSS systems with evolving NGNs, which hinders the efficient deployment of converged services and revenue generation due to silo-based architectures and static network resources.
Innovation Solution
Integration of OSS, BSS, and SDP components using a service-oriented architecture (SOA) and event-driven architecture (EDA), enabling message transformation and delegation across components, and sharing managed identities to facilitate end-to-end integration and convergence across multiple network technologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If OSS and BSS systems are integrated with SDP using SOA and EDA, then service delivery efficiency and operational efficiency are improved, but system complexity increases
Solution Approach 1:
The system is divided into independent components (OSS, BSS, SDP) that communicate through standardized interfaces. Each component operates autonomously but can be integrated through message transformation and delegation, allowing efficient service delivery while managing complexity through modular architecture.
Solution Approach 2:
A message transformation and delegation mechanism acts as an intermediary between OSS, BSS, and SDP components. This intermediary layer handles protocol conversion and message routing, enabling integration without direct complex point-to-point connections between all components.
2Adaptability or versatility
If legacy OSS and BSS systems are integrated with modern NGN, then service convergence is enabled, but integration difficulty increases due to archaic system architecture
Solution Approach 1:
The system transforms messages between different protocols and formats to bridge legacy OSS/BSS systems with modern NGN. By changing message parameters and using standardized interfaces, the system enables service convergence without requiring replacement of existing archaic systems.
3Loss of time
If zero-touch service lifecycle management is implemented, then service deployment time is reduced, but automation complexity increases
Solution Approach 1:
The system implements automated service lifecycle management where OSS and BSS components automatically provision, activate, and manage services without manual intervention. The event-driven architecture enables self-service automation through predefined workflows and message routing between components.
4Reliability
If managed identities are shared across OSS, BSS, and SDP components, then integration consistency is improved, but security management complexity increases
Solution Approach 1:
A universal identity management mechanism is implemented that allows OSS, BSS, and SDP components to share common managed identities. This universal approach enables consistent integration across all components while using standardized authentication and authorization protocols to manage security.
Data Source
AI summary
A service-oriented approach provides for an integration of components that would otherwise be considered different and unrelated components, such as runtime, business support systems (BSS), operational support systems (OSS), and third party components. Such integration allows messages to be transformed and passed between components as necessary to perform a particular task. For example, a BPEL workflow can be initiated upon receiving a user request through a network and gateway layer which will direct provisioning, activation, and processing via these various components. Identities can be managed across these various layers to provide for seamless end-to-end integration.