Ontological Resource Graph for Cross-Provider Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for cross-provider interoperability in cloud and edge computing are technically complex and lack comprehensive operational automation, compliance with regulations like GDPR and CCPA, and require significant development effort, especially for managing resources and data lifecycle across multiple providers.
Innovation Solution
A computer-implemented method using a graphical user interface to create and manage a resource management infrastructure by representing resources and components as ontological classes, allowing users to define technical functions and relationships between them, enabling seamless interaction and access across different providers through a language-independent, type-safe distributed program.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If standardization projects like Gaia-X are implemented to enable cross-provider interoperability, then user independence from individual providers is improved, but device complexity and implementation difficulty increase significantly
Solution Approach 1:
The patent introduces an intermediary layer (the method and system described) that mediates between users and multiple cloud/edge providers. This intermediary handles the complexity of cross-provider interoperability, authentication, and resource management, allowing users to benefit from provider independence without directly facing the implementation complexity. The intermediary translates user requests into provider-specific operations and manages the integration of multiple providers' resources and APIs.
2Adaptability or versatility
If multiple providers with different technical measures are integrated, then resource availability and versatility improve, but ease of operation deteriorates due to incompatible access processes
Solution Approach 1:
The patent implements a universal interface that can access and manage resources from multiple different providers through a single unified system. The method enables one access process to interact with multiple providers' resources (cloud storage, edge computing resources, etc.) without requiring separate access mechanisms for each provider. This universal interface abstracts the provider-specific details while maintaining the ability to operate with diverse resource types and access protocols.
3Adaptability or versatility
If comprehensive cross-provider mechanisms are implemented, then functional capability improves, but development effort and time loss increase
Solution Approach 1:
The patent performs preliminary actions by establishing a standardized framework and interface layer before actual cross-provider operations are needed. The method pre-configures authentication mechanisms, resource access patterns, and integration protocols, so that when users need to access multiple providers, the heavy lifting of integration is already done. This preliminary setup reduces the development time and effort required for each specific cross-provider scenario.
4Ease of operation
If provider-specific resources are accessed through unified interface, then ease of operation improves, but measurement precision deteriorates due to abstraction layer
Solution Approach 1:
The patent applies local quality by maintaining provider-specific implementation details at the appropriate level while presenting a unified interface at the user level. The system allows for provider-specific optimizations and precise control mechanisms to remain intact at the provider interface layer, while the unified interface above it provides consistent access patterns. This means that precision and control accuracy are preserved where needed (at the provider level) while maintaining operational simplicity at the user level.
Data Source
AI summary
A graphical user interface display symbols for actuators and components for selection and creation of a graph by a user. The actuators represent resources of a provider, and the components include, as components of the actuators, technical implementations for interacting with programming interfaces of one or more providers of the resources, wherein the components are implemented as ontological classes that include declarative definitions of properties of the respective component; wherein, in response to selection of a new actuator by the user, the actuator is represented as a node in the graph, and wherein, in response to selection of a new component for an actuator in the graph, contact is made with the resource, and wherein the actuator and/or the components of the graph indicate technical properties of the resources as well as indicate user elements enabling the user to access the resources by means of functionalities of the components.