Orchestration Process Template for Error Tolerance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current BPEL orchestration engines require hard-coded underlying implementation for each activity, making it difficult to reuse code and manage complex cross-domain processes effectively, especially in cloud computing environments where interactions with multiple sub-systems can lead to errors and process failures.
Innovation Solution
A method and system that query users for initial and undo codes, load pre-defined error check and correction codes, and generate an executable orchestration function to manage service activation, error determination, and correction, enabling reusable orchestration processes across various services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If hard-coded underlying implementation is used for each activity in BPEL orchestration engines, then the orchestration process can be executed, but the code cannot be easily reused and device complexity increases
Solution Approach 1:
The patent implements a template-based orchestration system where a single error check template and error correction template can be applied across multiple different activities and services. The templates define universal error handling logic that works with various sub-systems (virtual machines, storage devices, networks), eliminating the need to create separate error handling code for each activity and enabling code reuse across the entire orchestration process.
Solution Approach 2:
The patent segments the orchestration process into distinct template components: error check templates that define error detection logic, error correction templates that define remediation actions, and activity-specific templates that combine these elements. This segmentation allows each template to be independently developed, validated, and reused, reducing overall system complexity while improving maintainability and reusability.
2Adaptability or versatility
If multiple sub-systems are interacted with in cloud service delivery, then more services can be provided, but errors can occur and cause failure of the overall orchestration process
Solution Approach 1:
The patent implements error check templates that define error detection logic before errors can propagate through the orchestration process. By pre-defining error checking mechanisms for each activity and pre-defining correction actions, the system cushions against potential failures from multiple sub-systems, ensuring that errors are detected and corrected promptly rather than causing overall process failure.
Solution Approach 2:
The patent establishes feedback loops where error check templates continuously monitor the state of multiple sub-systems (virtual machines, storage, networks) and trigger error correction templates when anomalies are detected. This feedback mechanism enables the orchestration process to adapt to errors from any sub-system and maintain reliability by automatically initiating corrective actions based on predefined error handling logic.
3Reliability
If error check and correction templates are pre-defined and reused, then reliability improves, but initial setup complexity increases
Solution Approach 1:
The patent designs error check templates and error correction templates as universal, reusable components that can be applied across multiple activities and services. By creating templates that work with various sub-systems and error types, the initial setup effort is amortized across numerous orchestration processes, making the template management complexity worthwhile given the significant reliability improvements and ongoing maintenance benefits.
Solution Approach 2:
The patent requires that error check templates and error correction templates be pre-defined and configured before the orchestration process executes. This preliminary action ensures that error handling logic is validated and ready in advance, improving runtime reliability. The templates are established once and then reused repeatedly, so the initial setup complexity is incurred only once rather than for each execution.
Data Source
AI summary
A method to generate an executable orchestration process includes: querying a user to enter first computer code for activating a service; querying the user to enter second computer code for undoing actions performed in the activating; loading pre-defined third computer code for determining whether the activated service is a success or has an error, based on the service; loading pre-defined fourth computer code for correcting the error; generating an executable orchestration function from the first through fourth computer code; and generating the orchestration process from the executable orchestration function.