Extended Record Data Structure for Non-Standard Content Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional travel management systems are limited in handling non-GDS content due to standardization constraints, requiring complex validation, encoding, and decoding mechanisms, and cannot directly receive or manage non-standard data, making it costly and inefficient for travel agents to access and implement non-standard travel services.
Innovation Solution
A content management system that dynamically manages both standard and non-standard content using an extended record data structure with a non-standard data container, allowing seamless data exchange and storage independent of content type, eliminating the need for complex validation and encoding mechanisms by using auto-serialization properties and structure description files.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional travel management systems use standardized message exchange formats (TTY/AIRIMP) for content exchange, then reliability of data exchange is improved, but adaptability to handle non-GDS content deteriorates
Solution Approach 1:
The patent introduces an intermediary layer (the content management system with extended PNR data structure) between the standardized message exchange format and the diverse content types. This intermediary translates and adapts various content formats into a unified internal representation, maintaining reliability of standardized exchange while enabling adaptability to handle non-GDS content through the flexible extended data structure with dynamic field addition capability
2Manufacturing precision
If travel management systems implement complex validation and encoding mechanisms for standard content, then manufacturing precision of data handling is improved, but device complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-defining a comprehensive extended PNR data structure that anticipates various content types and formats. Structure description files are created in advance to describe the expected format and validation rules for different content types, allowing the system to handle diverse content with standardized precision without implementing complex runtime validation and encoding mechanisms for each specific case
3Manufacturing precision
If conventional systems require hard-coding and recompilation for new content types, then manufacturing precision is maintained, but productivity of system adaptation deteriorates
Solution Approach 1:
The patent implements dynamics by creating a flexible extended PNR data structure that can dynamically adapt to new content types without requiring system recompilation. The data structure allows runtime addition of new fields and attributes through configuration files and schema definitions, maintaining data structure integrity through predefined validation rules while enabling rapid integration of new content types through dynamic extension capabilities
4Adaptability or versatility
If travel agents directly connect to multiple non-GDS content providers, then adaptability to access diverse services is improved, but device complexity for each agent increases
Solution Approach 1:
The patent applies merging by consolidating access to multiple non-GDS content providers through a single unified travel management system interface. The extended PNR data structure serves as a common framework that can accommodate various content types from different providers, allowing travel agents to access diverse services through one standardized interface rather than maintaining separate connections and handling multiple different data formats independently
Data Source
AI summary
Methods, apparatus, and computer program products for exchanging content with a content management system comprising an extended record data structure. A plurality of records are maintained at the travel management system in an extended record data structure that includes first data containers containing standard data elements and second data containers containing non-standard data elements. Each non-standard data element is associated with a respective structure description file defining a structure of the attributes of the non-standard data element. A first data exchange message is generated at the travel management system and includes the structure description file of one of the non-standard data elements and a set of values corresponding to values of the attributes of the one of the non-standard data elements. The first data exchange message is transmitted according to a first data exchange format from the travel management system to the client device.