Central Cross-Model Stack for Backend Data References
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional computing systems face inefficiencies in storing and managing cross-system references, leading to redundancy and complexity in developing and activating cross-system scenarios due to mixed development of cross-system and non-cross-system content.
Innovation Solution
A system and method for modeling metadata that separates and structures storage of model content and cross-model content, using a central cross-model stack for cross-elements and separate cross-model stacks for referencing, allowing efficient and transparent establishment of cross-system scenarios.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cross elements are stored in all models they reference, then cross-system connections are established, but resource consumption increases and synchronization complexity worsens
Solution Approach 1:
The patent segments cross elements into two distinct storage locations: central cross model stacks for autonomous cross elements, and individual model stacks for reference elements. This segmentation eliminates the need to store cross elements in all referenced models, reducing synchronization complexity while maintaining reliable cross-system connections through the centralized structure.
2Adaptability or versatility
If cross content is included in models, then cross-system scenarios are enabled, but development complexity increases and activation/deactivation becomes complicated
Solution Approach 1:
The patent extracts cross-system content from individual models and places it in separate central cross model stacks. This extraction allows cross-system scenarios to be enabled or disabled independently of individual model development, simplifying the development process while maintaining adaptability. The central stacks act as independent containers that can be activated or deactivated without affecting model content.
Solution Approach 2:
The central cross model stacks serve as intermediary structures between different backend systems. These stacks mediate cross-system references by providing a centralized repository for cross elements, eliminating the need to mix cross-system and non-cross-system content in individual models. This intermediary structure simplifies activation/deactivation operations.
3Adaptability or versatility
If cross elements are stored without structured separation, then storage flexibility is maintained, but redundancy increases and storage efficiency decreases
Solution Approach 1:
The patent segments storage into distinct central cross model stacks for autonomous cross elements and individual model stacks for reference elements. This structured separation eliminates redundancy by ensuring cross elements are stored only once in the central stacks, while still maintaining storage flexibility through the hierarchical reference structure that allows flexible association of cross elements with different models.
Data Source
AI summary
A system and method for modeling cross system content between a hub and one or more backend systems is disclosed. Model content of one or more data models is stored in a model stack defined in a storage. The model content of each data model includes model metadata representing a model of a backend system. Cross model content is stored in a cross model stack. The cross model content includes reference metadata representing one or more references associated with a data model of one backend system and that reference a data model of another backend system. Central cross model content is stored in a central cross model stack. The central cross model content includes one or more cross elements that do not belong to the model content of any of the data models, and that establish a connection between two data models of different backend systems.