Relationship Service Engine for Cross-System Resource Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing relationships between disparate resources created and managed by different underlying systems, as well as similar resources managed by the same system, poses challenges due to the need for a unified management system that can associate and manage multiple systems.
Innovation Solution
A method for managing relationships among resources involves providing resource identifiers for each resource, allowing a relationship service to create and manage connections between resources, regardless of whether they are managed by the same or different systems, using a relationship service engine and state machine to facilitate and manage these relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a unified management system is implemented to manage relationships between disparate resources from different underlying systems, then the ability to manage relationships across multiple systems is improved, but the system complexity increases
Solution Approach 1:
The patent introduces a relationship management system as an intermediary layer between disparate underlying systems. This mediator translates and coordinates relationship management operations across different systems without requiring direct integration between them, thereby enabling multi-system relationship management while containing complexity within the intermediary layer rather than propagating it across all connected systems.
Solution Approach 2:
The relationship management system is designed with universal interfaces and standardized data structures that enable it to work with multiple different underlying systems through common protocols. This multi-functional design allows a single system to manage relationships across diverse platforms without requiring separate management mechanisms for each system, improving versatility while managing complexity through standardization.
2Adaptability or versatility
If resources from different underlying systems are integrated into a unified management framework, then interoperability between systems is improved, but the difficulty of managing different data formats and protocols increases
Solution Approach 1:
The patent employs parameter transformation mechanisms that convert data between different formats and protocols. The relationship management system dynamically adjusts data representation parameters based on the source and target systems, translating disparate data formats into a common internal representation and then converting to appropriate target formats, thereby achieving interoperability while managing format complexity through automated parameter transformation.
Solution Approach 2:
The system segments the data translation process into distinct layers: data extraction from source systems, normalization to internal standards, and transformation to target system formats. This segmentation isolates protocol management complexity into manageable stages, allowing each layer to handle specific format conversions without requiring the entire system to manage all possible format combinations simultaneously.
3Ease of operation
If a relationship management system is implemented to track and manage relationships between resources, then relationship management capability is improved, but the computational resources and storage requirements increase
Solution Approach 1:
The patent extracts only the essential relationship metadata from full resource data, storing minimal relationship information (such as relationship type, target resource identifier, and timestamp) separately from the underlying resource data. This extraction approach enables comprehensive relationship management capability while minimizing storage requirements by avoiding duplication of full resource copies in the relationship management system.
Solution Approach 2:
The relationship management system implements a nested data structure where relationship information is embedded within the resource identifier hierarchy rather than storing complete relationship graphs. This nesting allows the system to track relationships efficiently by leveraging existing resource identification structures, reducing computational overhead and storage requirements while maintaining full relationship management capability.
Data Source
AI summary
A method for managing relationships among resources includes providing a first resource having a first resource identifier, providing a second resource having a second resource identifier, and upon user initiation creating a managed relationship between the first resource identifier and the second resource identifier.