Dynamic Service Composition via Template Instantiation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing service composition technologies require complex semantic descriptions and indirect conversion of abstract composite service logic to concrete logic, failing to dynamically select services during execution and handle inaccessible services.
Innovation Solution
A system and method for dynamically selecting and replacing concrete services based on abstract service descriptions, using a service composition engine, discovery unit, and adaptation unit to directly execute abstract composite service logic, and generate service invocations, with a registration center for service and template mapping.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If static service composition is used to specify concrete services in advance, then service composition is simple to implement, but the system cannot dynamically select services during execution and fails when services become inaccessible
Solution Approach 1:
The patent transforms static service composition into dynamic service composition by introducing service templates that can be instantiated with different concrete services at runtime. The service template mechanism allows the system to adapt service selections dynamically based on availability, while maintaining a structured composition framework. This resolves the contradiction by making the service binding dynamic rather than fixed, enabling both implementation simplicity and runtime adaptability.
Solution Approach 2:
The patent segments the service composition into two distinct layers: service templates (abstract layer) and concrete services (implementation layer). This segmentation allows the composition logic to remain simple and stable while the service bindings can be flexibly changed. The template acts as an intermediary that decouples the composition structure from specific service implementations, resolving the contradiction between simplicity and adaptability.
2Adaptability or versatility
If dynamic service composition based on semantic technology is used, then services can be selected automatically at runtime, but the process requires complex semantic descriptions and indirect conversion of abstract to concrete logic
Solution Approach 1:
The patent extracts the complex semantic matching and conversion process from the service composition execution path. By pre-defining service templates with their semantic characteristics and using a template-matching mechanism, the system avoids complex runtime semantic analysis. The template serves as a pre-processed intermediary that simplifies the matching process, reducing runtime complexity while maintaining dynamic selection capability.
Solution Approach 2:
The patent performs service template definition and semantic characterization in advance, before runtime execution. Service templates are prepared with their interfaces, parameters, and semantic properties beforehand, allowing the runtime system to simply match incoming requests against these pre-defined templates. This preliminary action eliminates the need for complex runtime semantic processing, resolving the contradiction between dynamic selection and complexity.
3Reliability
If abstract composite service logic is indirectly converted to concrete logic before execution, then service invocation can be performed, but the process is complex and does not support dynamic service replacement when services become inaccessible
Solution Approach 1:
The patent introduces service templates as intermediaries between abstract service logic and concrete service implementations. Instead of directly converting abstract logic to concrete service bindings, the system uses templates as a mediating layer. This intermediary approach simplifies the conversion process by providing a standardized template structure that naturally bridges the abstract and concrete layers, while enabling dynamic replacement through template re-instantiation.
Solution Approach 2:
The patent maintains dynamic service replacement capability by keeping the service template instantiation process active during runtime. When a concrete service becomes inaccessible, the system can re-instantiate the same service template with a different concrete service implementation. This dynamic approach eliminates the need for complex pre-conversion processes while maintaining reliability, as the template mechanism naturally supports flexible binding at any execution stage.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
The present invention relates to a method for handling and replacing a composite service. The method for handling a composite service may include obtaining a concrete service corresponding to a service invocation segment description in a composite service logic, wherein the service invocation segment is an abstract service invocation segment or a service template invocation segment; triggering a service replacement, requesting to replace the service invocation segment with a concrete service invocation segment of the obtained concrete service; or, triggering a service invocation, requesting to generate a service invocation based on the concrete service. The method for replacing a composite service may include acquiring service template information associated with concrete service invocation segment information in the composite service logic; replacing the concrete service invocation segment information in the composite service logic with the service template information. Apparatuses for handling and replacing a composite service are also disclosed according to the present invention. A system for composite service is further disclosed. Accordingly, a concrete service can be dynamically selected when the composite service logic is being executed.