Intermediation Server for Heterogeneous Data Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to seamlessly integrate and display data generated via distinct mechanisms, such as NDC and GDS, for travel-related products and services, leading to inconsistencies and limitations in presenting and updating data from different sources.
Innovation Solution
A system and method that utilize an intermediation server to integrate data from multiple repositories, using field mappings and similarity metrics to merge records from different data generation mechanisms, enabling a common interface for viewing and updating data regardless of the generation mechanism.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data from multiple independent generation mechanisms are integrated into a single interface, then data consistency and user experience are improved, but system complexity increases due to the need for field mappings and similarity metrics
Solution Approach 1:
The patent introduces an intermediation server that acts as a mediator between multiple independent data generation mechanisms (NDC, GDS, etc.) and the user interface. This server contains integration logic with field mappings and similarity metrics that automatically matches and integrates data from different sources, shielding the complexity from both the source systems and the interface layer.
Solution Approach 2:
The system architecture is segmented into distinct layers: independent data generation mechanisms, an intermediation server with integration logic, and a unified user interface. This segmentation allows each component to remain simple while the integration layer handles the complexity of combining multiple data sources.
2Device complexity
If separate interfaces are used for each data generation mechanism, then system complexity is reduced, but data consistency and user experience deteriorate due to inconsistent display and update operations
Solution Approach 1:
The patent implements a universal user interface that can display and update data from any generation mechanism through a single consistent interaction model. The intermediation server translates data from different mechanisms into a unified format that the single interface can handle, allowing the interface to serve multiple data sources universally without needing separate interfaces for each mechanism.
3Measurement precision
If field mappings and similarity metrics are implemented to merge records, then data integration accuracy is improved, but processing time and computational resources increase
Solution Approach 1:
The patent pre-establishes field mappings between different data generation mechanisms during system setup or initialization. These mappings define how fields from NDC, GDS, and other mechanisms correspond to each other, allowing the integration process to quickly match records without performing complex real-time analysis of all possible field combinations.
Solution Approach 2:
The system uses similarity metrics that compare data fields based on defined parameters and thresholds. By adjusting these parameters and using efficient comparison algorithms, the system achieves accurate matching while minimizing processing time, balancing precision with performance.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of integrating data objects includes: storing (i) an originating record containing a first unique identifier and a first set of data fields defining a first item supplied by a first provider, and (ii) a destination record containing a second unique identifier and a second set of data fields defining a second item supplied by a second provider; receiving an instruction to merge the originating record into the destination record, the request containing the first and second unique identifiers; in response to receiving the instruction, updating the destination record by: comparing the first set of data fields with the second set of data fields; and for each data field of the first set that matches a corresponding data field of the second set, marking the corresponding data field of the second set as a shared field; and sending the updated destination record to a client device for display.