Shared Software Function Management in Converged Infrastructure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In converged infrastructure architectures, maintaining and updating multiple copies of shared software functions across service instances is inefficient, leading to waste of resources, complex maintenance, and difficulty in updating software functions due to their physical isolation and dependency on virtualization.
Innovation Solution
A method where a software function shared by multiple service instances is stored independently, with a management component handling call requests from service instances, including identification information and operation parameters, to execute the software function and return execution results, eliminating the need for multiple copies and simplifying maintenance and updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If multiple copies of shared software functions are maintained across service instances, then each service instance can independently execute functions, but resource consumption increases and maintenance becomes complex
Solution Approach 1:
The patent merges multiple copies of the same software function into a single shared copy stored in a common location. Service instances access this shared function through standardized interfaces, eliminating redundant storage while maintaining execution capability. This resolves the contradiction by combining resources to reduce consumption while preserving operational independence through interface-based access.
Solution Approach 2:
The shared software function is designed with universal interfaces that allow multiple service instances to access and execute the same function through standardized methods. This multi-functionality enables a single function copy to serve multiple purposes and multiple callers, reducing resource consumption while maintaining the ability of each service instance to independently invoke functions as needed.
2Ease of operation
If multiple copies of shared software functions are maintained across service instances, then each service instance has local access, but maintenance and updates become complex and difficult
Solution Approach 1:
The patent extracts the software function from individual service instances and places it in a shared, centralized location. This extraction allows maintenance and updates to be performed on a single copy rather than multiple distributed copies, significantly reducing maintenance complexity while service instances retain access through standardized interfaces that preserve local invocation capability.
Solution Approach 2:
The patent introduces an intermediary layer (standardized interface/API) between service instances and the shared software function. This intermediary allows service instances to access the function locally through standard calls while the actual function resides in a centralized, easily maintainable location. Updates propagate through the intermediary without requiring modifications to individual service instances.
3Adaptability or versatility
If software functions are physically isolated and dependent on virtualization, then service instances can be independently deployed, but updating software functions becomes difficult
Solution Approach 1:
The patent segments the software architecture into two independent parts: service instances that can be independently deployed and a shared software function repository that can be independently updated. This segmentation allows service instances to maintain their deployment independence while the shared function repository provides a centralized update mechanism, resolving the contradiction between independent deployment and ease of updating.
Data Source
AI summary
The present disclosure provides for managing a software function. The system determines that a service instance is to call the software function and, in response, initiates a call request for the software function to a management component The call request includes identification information and an operation parameter of the software function, with the software function shared by a service instance and at least one further service instance deployed and stored in a converged infrastructure architecture independently from the service instance and the at least one further service instance. The system receives a response to the call request from the management component, with the response including a result of execution of the software function based on the operation parameters. The system prevents the need to deploy copies of a common software function of service instances, conserving performance and storage space, and enabling more convenient maintenance, updates, and software function calls.