Shell Record Splitting for Mixed Itinerary Data Manipulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in handling heterogeneous data records from different suppliers due to distinct communication protocols and update mechanisms, leading to inconsistent rendering and obstructed manipulations of travel-related itineraries.
Innovation Solution
An aggregator server generates a shell record with a new identifier to split mixed itineraries into distinct subsets, allowing flexible manipulation of data records while maintaining associations, and provides a new identifier to the client subsystem for independent handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If intermediation services combine multiple record types into a single unified record for client viewing, then clients can view and manipulate records as a single entity, but manipulations affecting only a portion of the records are complicated or prevented
Solution Approach 1:
The patent divides the unified mixed record into separate component records (e.g., flight record, hotel record, car rental record) that can be independently manipulated. Each component record maintains its own identifier and can be processed separately while still being part of the overall itinerary, enabling partial manipulations without affecting the entire record set.
Solution Approach 2:
The patent implements a nested structure where component records are embedded within or linked to a master mixed record. The master record contains references to component records, allowing the system to present a unified view to clients while maintaining the ability to access and manipulate individual components independently, similar to nested dolls where smaller units are contained within larger units.
2Adaptability or versatility
If distinct data-exchange infrastructure is used for each supplier entity, then each supplier's data can be stored and communicated using its own protocols and formats, but retrieving and modifying data from multiple suppliers becomes complex
Solution Approach 1:
The patent introduces a master record as an intermediary layer between client systems and multiple supplier-specific component records. This master record abstracts the complexity of dealing with multiple suppliers by providing a unified access point that automatically routes operations to the appropriate component records, eliminating the need for clients to directly handle multiple distinct protocols and formats.
Solution Approach 2:
The master mixed record serves multiple functions simultaneously: it acts as a container for component records, provides a unified interface for client interactions, maintains relationships between different supplier records, and enables both collective and individual manipulation of records. This multi-functional design simplifies the system architecture by replacing multiple specialized interfaces with a single universal record type.
Data Source
Figure 1
Figure 2
Figure 3
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.