Extended Record Data Structure for Non-GDS Content Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional travel management systems are unable to directly receive and manage non-GDS content due to standardization constraints, limiting their ability to handle diverse travel services and requiring costly and complex manual conversions for data exchange.
Innovation Solution
A content management system that employs a centralized extended record data structure, allowing for the seamless management of both standard and non-standard record data structures, using a unified record identifier to treat them as a single data structure, and utilizing non-standard data containers with auto-serialization properties for dynamic content handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional PNR data structures are used to maintain standardization compliance, then reliability is improved, but adaptability deteriorates as non-GDS content cannot be directly received
Solution Approach 1:
The patent segments the PNR data structure into two distinct parts: a standardized segment that maintains IATA AIRIMP compliance and a non-standardized segment that enables flexible storage of non-GDS content. This segmentation allows the system to simultaneously satisfy standardization requirements while accommodating diverse content types from non-traditional providers.
Solution Approach 2:
The patent introduces an intermediary data structure that acts as a bridge between standardized GDS content and non-standardized non-GDS content. This intermediary layer enables the system to receive and process non-GDS content while maintaining compatibility with existing standardized systems, thus resolving the contradiction between reliability and adaptability.
2Adaptability or versatility
If manual conversion processes are implemented to handle non-GDS content, then adaptability is improved, but device complexity and loss of time increase
Solution Approach 1:
The patent implements self-service functionality where the system automatically receives, processes, and stores non-GDS content without requiring manual conversion interventions. The automated processing reduces both the complexity of conversion processes and the time required to handle non-GDS content, while maintaining adaptability.
Solution Approach 2:
The patent performs preliminary actions by pre-configuring the data structure to accommodate non-GDS content from the outset. This preliminary preparation eliminates the need for complex manual conversions later, as the system is already structured to receive and process diverse content types directly.
3Adaptability or versatility
If separate systems are used to access non-GDS content, then adaptability is improved, but device complexity and loss of time increase
Solution Approach 1:
The patent merges the functionality of separate systems into a unified PNR data structure that can handle both GDS and non-GDS content. This consolidation eliminates the need for multiple separate systems, reducing architectural complexity while maintaining the ability to access diverse content types through a single integrated platform.
Solution Approach 2:
The patent creates a universal data structure that serves multiple functions: it maintains standardized GDS content compliance while simultaneously accommodating non-GDS content from various providers. This multi-functional approach eliminates the need for separate specialized systems, reducing complexity while enhancing adaptability.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
There is provided a method of managing an extended record data structure (9) in a content management system (100). The record data structure comprises a standard record data structure (90) for storing records comprising standard data elements of predefined standard types in the form of standard data containers and a non-standard record data structure (91) for storing records comprising non-standard data elements having different types from said predefined standard types, in the form of non-standard data containers. Each record in the extended record data structure (9) comprises a record identifier, the records corresponding to related data elements in the extended record data structure (9) sharing a common record identifier, the method comprising, for each record created in the extended record data structure (9) for a data element having a given record identifier, creating an entry in an auxiliary data structure (92). The entry shares the given record identifier and comprises an auxiliary data container, the auxiliary data container comprising a set of attributes related to the data containers sharing the same record identifier in the record data structure. The method manages the extended record data structure (9) based on the data maintained in the auxiliary data structure (92).