Provisioning Framework Resuming Failed Orders via Fake Environment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional provisioning systems face challenges in maintaining data consistency and efficiently resuming failed Customer Service Orders (CSOs) due to complexities in retrying and rollback processes, especially in scenarios with complex logic and interactions with Network Elements (NEs).
Innovation Solution
A method and system that directs the successful part of a CSO to a fake environment based on historical processing data and the uncompleted part to actual NEs, allowing for automatic retry and resumption of failed CSOs without requiring the provisioning logic to be aware of failure scenarios, thus simplifying the design and reducing development costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional retrying approach by storing uncompleted commands is used, then the system can attempt to complete failed provisioning, but it cannot successfully predict remaining commands in complex logic scenarios
Solution Approach 1:
The system stores the original Customer Service Order (CSO) and provisioning logic code before execution. When a failure occurs, the system retrieves these pre-stored elements and re-executes the provisioning process from the beginning using the same logic, eliminating the need to predict which commands remain to be executed.
Solution Approach 2:
The system creates a copy of the original provisioning environment by retrieving the stored CSO and provisioning logic code. This copied environment is then re-executed to complete the failed provisioning, avoiding the complexity of analyzing and predicting the state of the original execution.
2Stability of the object's composition
If rollback approach is used to solve inconsistency immediately, then data consistency is restored, but the system gets stuck when rollback itself fails
Solution Approach 1:
The system stores the original CSO and provisioning logic code before execution. When provisioning fails at any point, the system retrieves these pre-stored elements and re-executes the entire provisioning process, ensuring that the network elements end up in the correct final state without requiring complex rollback scenarios.
Solution Approach 2:
Instead of attempting to rollback from the failed state (which may itself fail), the system inverts the approach by re-executing the provisioning from the beginning using stored original parameters. This ensures correctness without relying on the reliability of rollback operations.
3Stability of the object's composition
If provisioning logic is made aware of failure scenarios and rollback scenarios, then consistency can be managed, but the design complexity and development costs increase significantly
Solution Approach 1:
The system extracts the failure handling logic from the provisioning logic itself. By storing the original CSO and provisioning code and re-executing them after failures, the system removes the need for provisioning logic to contain complex failure detection, rollback scenario management, and consistency checking code.
Solution Approach 2:
The system introduces an intermediary mechanism (storing and re-executing original CSO and provisioning logic) that handles failure scenarios. This intermediary layer absorbs the complexity of failure management, allowing the core provisioning logic to remain simple and focused on its primary function.
Data Source
AI summary
A method and system of provisioning one or more Network Elements, as well as a method and apparatus for resuming a failed Customer Service Order for provisioning one or more Network Elements, is disclosed. A provisioning logic framework receives a Customer Service Order CSO from a Business Support System, calls respective provisioning logic for performing said Customer Service Order and detects if the received Customer Service Order is a CSO to be resumed. During the performing time of said Customer Service Order, historical processing data is stored. If it is detected that the received Customer Service Order is a CSO to be resumed, the provisioning logic framework builds up a fake environment on the basis of historical processing data stored previously for the CSO to be resumed. Then the successful part of the CSO is directed to the fake environment and the uncompleted part of the CSO is directed to actual Network elements.