Cross-Domain Backup Service Orchestration for Predictable Restoration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-provider, multi-domain ecosystems, the restoration time for service components after infrastructure failure is lengthy and unpredictable, and the resource usage for backup components is inefficient, leading to complex and uncertain failover times.
Innovation Solution
A Reliability Life-Cycle Manager (RLCM) initiates a restoration trial process during the deployment phase of the original service, allowing orchestrators to emulate backup service deployments across different domains, reducing the time required for actual deployment during failures by pre-determining backup service components and their deployment times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If pre-deployed active or backup service components are used, then service reliability is improved, but resource usage increases significantly
Solution Approach 1:
The patent performs preliminary determination of backup service components during the deployment phase. The system identifies and prepares backup network functions and their deployment locations in advance, but does not fully deploy them. This preliminary action ensures that when a failure occurs, the backup components can be rapidly activated without requiring extensive resource allocation for fully deployed backup services.
2Loss of time
If restoration trial process is initiated during deployment phase, then restoration time is decreased, but deployment complexity increases
Solution Approach 1:
The restoration trial process is initiated during the deployment phase to pre-determine backup service components. This preliminary action includes identifying potential backup locations, testing deployment scenarios, and establishing failover procedures before actual failures occur. By performing these actions in advance, the system reduces restoration time when failures happen, despite the increased complexity during the initial deployment phase.
Solution Approach 2:
The system incorporates feedback mechanisms where the results of restoration trials are used to refine and optimize backup deployment strategies. The feedback loop allows the system to learn from trial outcomes and adjust deployment configurations, improving both restoration efficiency and reducing complexity in subsequent operations.
3Reliability
If 1+1 or N+M redundancy is applied, then service reliability is improved, but resource needs increase significantly
Solution Approach 1:
Instead of fully deploying backup service components (excessive action), the system determines and prepares only the necessary backup components partially during the deployment phase. This partial action approach provides sufficient redundancy for reliability while avoiding the resource overhead of fully deployed backup services. The system activates only the minimal required backup resources when failures occur.
4Adaptability or versatility
If orchestration process traverses multiple domains, then service coverage is improved, but restoration time increases
Solution Approach 1:
The system performs preliminary determination of backup service components and their deployment across multiple domains during the initial deployment phase. By pre-identifying backup locations and testing cross-domain deployment scenarios in advance, the system reduces the time required for orchestration to traverse multiple domains when actual restoration is needed, while still maintaining comprehensive service coverage.
Data Source
AI summary
Embodiments described herein relate to methods and apparatuses for providing a back-up service. A method in a reliability lifecycle manager (RLCM) is provided for managing orchestration of a back-up service for an original service. The method comprises receiving an indication of successful deployment of at least a first part of an original service from a first network domain, wherein the at least part of the original service comprises at least a first network function; responsive to the indication, transmitting a restoration preparation request to the first network domain to request that the first network domain initiate determination of a back-up service for the first part of the original service, the back-up service comprising a first back-up network domain capable of deploying the first network function, wherein the first back-up network domain is different to a first original network domain deploying the first network function in the original service; and responsive to transmitting the restoration preparation request, receiving a restoration response comprising an indication of the back-up service.