Extended Data Record for Non-Standard Travel Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Global Distribution Systems (GDS) are limited in managing travel services from destination service providers due to standardization constraints and security reasons, preventing seamless integration of non-standard travel services into travel itineraries.
Innovation Solution
A data processing system that links standard and extended data structures to manage service offers, enabling the search, reservation, pricing, and tracking of non-standard travel services by transmitting service requests and offers between standard and non-standard provider systems, and updating their statuses within an extended data record.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the GDS uses a centralized database with standard data structures to manage travel services, then data management and tracking are improved, but the ability to integrate non-standard destination service provider systems is limited
Solution Approach 1:
The patent segments the data structure into two distinct parts: a standard data structure (PNR) for core travel service management and an extended data structure for non-standard destination service provider information. This segmentation allows each part to serve its specific purpose while maintaining overall system integrity. The standard PNR handles flights, hotels, and car rentals through established protocols, while the extended structure accommodates local services with non-standard data formats without disrupting the core system.
Solution Approach 2:
The extended data structure is nested within the standard PNR data structure. The patent creates an extended record that contains both the standard PNR elements and additional fields for non-standard service provider data. This nested approach allows the extended information to be stored and managed as part of the overall itinerary while preserving the hierarchical organization of the standard GDS architecture. The extended data structure acts as a container that holds supplementary information alongside the core travel service data.
2Reliability
If the GDS restricts access to PNR database for security reasons, then data security is improved, but the ability to search and book destination services is reduced
Solution Approach 1:
The patent extracts the extended service provider data from the core PNR database while maintaining a reference link. The extended data structure stores additional service information in a separate but associated record, allowing the system to access destination service provider information without compromising the security of the central PNR database. This extraction enables broader data access for booking purposes while the core sensitive information remains protected within the restricted PNR system.
Solution Approach 2:
The extended data structure acts as an intermediary layer between the secure PNR database and external service provider systems. It provides a controlled interface that allows travel agents and users to search for and book destination services without direct access to the core PNR database. The extended structure mediates data exchange by translating between standard GDS protocols and non-standard service provider formats, enabling secure yet functional integration.
3Reliability
If the GDS maintains standardized communication protocols, then system reliability is improved, but compatibility with non-standard destination service providers deteriorates
Solution Approach 1:
The patent applies local quality by allowing different data structure formats for different types of service providers. The standard PNR data structure maintains consistent formatting for major airlines, hotels, and car rental companies, ensuring system reliability. Meanwhile, the extended data structure allows each destination service provider to maintain its own data format and communication protocol locally, accommodating non-standard providers without compromising the overall system architecture. Each provider can have customized data fields while the core system remains standardized.
Data Source
AI summary
Systems, methods, and computer program products for managing non-standard data. A data management system stores profile records for non-standard providers in a DTN database, and elements defining an itinerary in an EDR database. The data management system queries the DTN database for profiles matching search criteria, and generates a service request for one of the matching profiles. The service request is stored in an extended data structure of an extended data record in the EDR database. The extended data record includes a standard data structure for storing standard elements and the extended data structure for storing non-standard elements. The service request is also transmitted to non-standard provider systems. Service offers from the non-standard provider systems are stored in the extended data structure. The system thereby manages an itinerary that includes non-standard services defined by the non-standard elements and standard services defined by the standard elements using the extended data record.