Shell Record Linking for Mixed Itinerary Data Manipulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in handling heterogeneous data records from different suppliers, leading to inconsistent rendering and manipulation of travel-related products, such as flights and hotel reservations, due to distinct communication protocols and update mechanisms, which complicates or prevents manipulation of partial records.
Innovation Solution
An aggregator server integrates and manages multiple data records by generating shell records with new identifiers, allowing for the splitting and manipulation of mixed itineraries while maintaining associations between them, thereby enabling flexible and consistent manipulation by client systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If intermediation services are used to present multiple record types as a single record, then ease of operation is improved, but device complexity increases
Solution Approach 1:
The patent segments the record manipulation process into two distinct modes: mixed mode (presenting multiple record types as a unified record for ease of operation) and split mode (separating records for targeted manipulation). This segmentation allows the system to maintain simplicity in the mixed mode while enabling complex operations in the split mode when needed, thus resolving the contradiction between ease of operation and device complexity.
Solution Approach 2:
The system dynamically switches between mixed mode and split mode based on the manipulation requirements. The ability to transition between these modes allows the system to adapt its behavior, presenting a simplified unified record interface during normal operation while enabling detailed control when required, thereby balancing ease of operation with the capability to handle complex scenarios.
2Adaptability or versatility
If multiple distinct communication protocols and update mechanisms are used for different supplier records, then adaptability is improved, but ease of operation deteriorates
Solution Approach 1:
The patent implements a universal record identifier and unified communication interface that can handle multiple record types from different suppliers. This universal interface abstracts the underlying protocol differences, allowing clients to interact with diverse record types through a consistent mechanism, thus maintaining adaptability while significantly improving ease of operation.
Solution Approach 2:
The system introduces an intermediary layer that translates between the diverse supplier-specific protocols and a unified client interface. This intermediary handles the protocol conversion and update mechanism coordination, allowing clients to operate with simplicity while the system maintains the ability to adapt to different supplier requirements underneath the abstraction layer.
3Ease of operation
If records are presented as a single unified record, then ease of operation is improved, but manufacturing precision deteriorates
Solution Approach 1:
The patent segments the unified record into manageable portions through the split mode functionality. When precise manipulation is required, the system can divide the mixed record into individual component records, allowing for precise targeted operations while maintaining the ability to present them as a unified whole during normal operation, thus resolving the contradiction between ease of operation and manufacturing precision.
Data Source
AI summary
A method includes: storing a set of records including: (i) a first record having a first identifier, and (ii) a second record having a second identifier and a link to the first record, the second identifier configured, via the link to the first record, to identify a first mixed record generated from the first and second records; receiving a request containing the second identifier; generating a shell record including a third identifier and a further link to the first record, the third identifier configured, via the further link to the first record, to identify a second mixed record generated from the shell record and the first record; and storing the shell record.