Service Provider Infrastructure Management via Workflow and Provisioning Engines
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing a service provider's infrastructure is complex, time-consuming, and expensive due to the need to activate, deactivate, or modify services across diverse network elements from different vendors, which often require different protocols and programming languages, and can be hindered by busy network elements or errors.
Innovation Solution
A computer-based method using a workflow engine and provisioning engine to receive service orders, assemble commands specific to network elements, execute tasks sequentially or in parallel, and handle errors, while simplifying the activation and deactivation of services across heterogeneous infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual management methods are used for heterogeneous network elements from different vendors, then flexibility in supporting multiple protocols and programming languages is achieved, but the complexity and time consumption of service activation and modification increase significantly
Solution Approach 1:
The patent introduces a gateway as an intermediary component that mediates between the service provider's management system and diverse network elements from different vendors. The gateway handles protocol translation and command formatting, allowing the core management system to interact with network elements through a standardized interface while supporting multiple communication protocols (SNMP, TL1, Telnet, SSH, FTP, HTTP, LDAP, CORBA, SQL, Netconf, DOCSIS) and programming languages (Perl, Python, Ruby, PHP, C#, C++, Java). This intermediary approach resolves the contradiction by absorbing the complexity of multi-protocol support in the gateway layer rather than in the entire management system.
Solution Approach 2:
The management system is segmented into distinct functional components: a service order management layer, a gateway layer for protocol handling, and network element layers. This segmentation allows each component to specialize in specific tasks - the gateway handles vendor-specific protocols while the core system manages service logic. The system further segments service activation into discrete workflows with individual tasks that can be executed independently or in parallel, reducing overall system complexity while maintaining versatility.
2Ease of operation
If traditional service activation processes are used across diverse network elements, then comprehensive service management is achieved, but the time required for service activation and modification increases
Solution Approach 1:
The system performs preliminary actions by pre-compiling service activation workflows into structured task sequences before actual service activation. Workflows are designed in advance with defined tasks, dependencies, and execution paths. When a service activation request arrives, the system retrieves the pre-prepared workflow and executes it, significantly reducing activation time compared to ad-hoc manual configuration. The gateway also maintains pre-established connections and command templates for common network element operations.
Solution Approach 2:
The system ensures continuous service activation by implementing parallel task execution where independent tasks are performed simultaneously rather than sequentially. The workflow engine monitors task dependencies and executes independent tasks in parallel across multiple network elements. The system also implements continuous error handling and retry mechanisms that maintain activation progress even when individual tasks fail, ensuring the overall service activation process continues without complete interruption.
3Reliability
If centralized service management is implemented, then consistent service provisioning is achieved, but the system becomes vulnerable to errors and requires robust error handling mechanisms
Solution Approach 1:
The system implements comprehensive feedback mechanisms at multiple levels. The gateway receives responses from network elements and feeds them back to the workflow engine for interpretation and next-step determination. Error feedback triggers automated retry logic with exponential backoff. The system also implements feedback loops that monitor task execution status and dynamically adjust workflow progression. Successful task completion feedback updates the service activation state and triggers subsequent dependent tasks, ensuring consistent service provisioning while automatically handling errors through structured feedback-response cycles.
4Productivity
If parallel task execution is enabled for faster service activation, then productivity increases, but the risk of errors and the need for coordination increases
Solution Approach 1:
The workflow execution model is dynamic rather than static. The system dynamically determines task execution timing based on dependency resolution, resource availability, and error state. Independent tasks are dynamically launched in parallel when their prerequisites are met, while dependent tasks wait for their predecessors. The workflow engine dynamically adjusts execution paths based on task success or failure, routing to error handling procedures when needed and to continuation paths when successful. This dynamic approach maximizes parallel execution for productivity while maintaining reliability through adaptive error response.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A computer-based method (and associated system) for managing services provided by a service provider includes receiving a service order at a computer-based workflow engine, sending a generic ready-to-activate service order to a provisioning engine if network element involvement is needed to perform a step involved in satisfying the service order, assembling a command at the provisioning engine, in a format that is specific to the network element, to perform the step, and sending the network element-specific command from the provisioning engine to the network element.