Content management in a travel management system

• US 10,042,871 B2
• Filed: 05/30/2014
• Issued: 08/07/2018
• Est. Priority Date: 05/30/2014
• Status: Active Grant

• Current Assignee: Amadeus S.A.S. (Amadeus Global Travel Distribution S.A.)
• Original Assignee: Amadeaus SAS
• Inventors: Fontebride, Vanessa, Charrat, Christel, Le Sinq, Ludovic, Francois, Marion, Gadeyne, Pierre
• Primary Examiner(s): Perveen, Rehana
• Assistant Examiner(s): Wong, Huen
• Application Number:
  US14/291,837
• Publication Number:
  US 20150347476A1
• Time in Patent Office: 1,530 Days
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/80 of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML content-based retrieval of web data G06F16/95
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events

Abstract

Methods, apparatus, and computer program products for managing content in a travel management system. A standard data element and a non-standard data element comprising the content are received from one or more content providers. A first data container for the standard data element and a second data container for the non-standard data element are created in an extended record data structure. The first data container includes a common record identifier and first data values for first attributes corresponding to the standard data element. The second data container includes the common record identifier and second data values corresponding to second attributes for the non-standard data element. The travel management system manages access to the first container and the second container in the extended record data structure based on the common record identifier.

Claims

1. A method of managing content in a travel management system, the method comprising:

receiving, from one or more content providers, a standard data element and a non-standard data element comprising the content;

receiving, from the one or more content providers, a first XSD structure description file, wherein one or more first XML tags complying with the first XSD structure description file describe an attribute structure of the non-standard data element and one or more second XML tags complying with the first XSD structure description file describe one or more auxiliary constraints associated with the non-standard data element;

creating a first data container for the standard data element in an extended record data structure, the first data container including a common record identifier and first data values for first attributes corresponding to the standard data element;

creating, based at least in part on the one or more first XML tags, a second data container for the non-standard data element in the extended record data structure, the second data container including the common record identifier and second data values corresponding to second attributes for the non-standard data element;

applying, based at least in part on the one or more second XML tags, the one or more auxiliary constraints to the second data container;

configuring a plurality of applications to use the second data container to access the non-standard data element, wherein the applications are executable by the travel management system in response to requests received by the travel management system;

managing access of each application to the first container and the second container in the extended record data structure based on the common record identifier, wherein the standard data element satisfies International Air Transport Association (IATA) constraints and is obtained from a global distribution system operating as the travel management system, and the non-standard data element fails to satisfy the IATA constraints and is obtained from a source other than the global distribution system;

transforming, through XSLT transformation, the first XSD structure description file into a second XSD structure description file using predefined mapping rules, wherein the first XSD structure description file and the second XSD structure file define corresponding attributes; and

creating, based at least in part on the second XSD structure description file, a third data container for the non-standard data element.

2. The method of claim 1 wherein the second data container comprises a plurality of keys and a plurality of values, each key corresponding to one of the second attributes of the non-standard data element.

3. The method of claim 2 wherein one of the keys of the second data container defines a type for each non-standard data element.

4. The method of claim 2 wherein the second data container is a business object model, the business object model being self-implemented.

5. The method of claim 4 wherein the second data container comprises a self-serialization mechanism for serializing itself into an application target format, and a library embedding serialization information for serializing or deserializing the second data container.

6. The method of claim 1 further comprising:

providing an application access to the second container by generating a generic container to which is assigned a unique generic type, the generic container containing the second data container.

8. The method of claim 6 further comprising:

providing the application access to the first data container by converting the standard data element into another non-standard data element and adding the converted standard data element to the generic container.

9. The method of claim 1 wherein the standard record data structure and the non-standard record data structure are stored in a shared storage area within the travel management system.

10. The method of claim 1 wherein the standard record data structure and the non-standard record data structure are stored in different storage areas within the travel management system.

11. The method of claim 1 wherein the content may be received by a plurality of chained applications at a content aggregator, the non-standard data element is transmitted between the chained applications through messages carrying self-serialization information, and the second data container is stored in the extended travel record when triggered by one of the applications.

7. The method of 6 further comprising:

introspecting the non-standard data element to permit the application to access the generic type assigned to the generic container.

12. An apparatus for managing content in a travel management system, the apparatus comprising:

at least one processor; and

a memory coupled to the at least one processor and including instructions that, when executed by the at least one processor, cause the apparatus to;

receive, from one or more content providers, a standard data element and a non-standard data element comprising the content;

receive, from the one or more content providers, a first XSD structure description file, wherein one or more first XML tags complying with the first XSD structure description file describe an attribute structure of the non-standard data element and one or more second XML tags complying with the first XSD structure description file describe one or more auxiliary constraints associated with the non-standard data element;

create a first data container for the standard data element in an extended record data structure, the first data container including a common record identifier and first data values for first attributes corresponding to the standard data element;

create, based at least in part on the one or more first XML tags, a second data container for the non-standard data element in the extended record data structure, the second data container including the common record identifier and second data values corresponding to second attributes for the non-standard data element;

apply, based at least in part on the one or more second XML tags, the one or more auxiliary constraints to the second data container;

configure a plurality of applications to use the second data container to access the non-standard data element, wherein the applications are executable by the travel management system in response to requests received by the travel management system;

manage access of each application to the first container and the second container in the extended record data structure based on the common record identifier, wherein the standard data element satisfies International Air Transport Association (IATA) constraints and is obtained from a global distribution system operating as the travel management system, and the non-standard data element fails to satisfy the IATA constraints and is obtained from a source other than the global distribution system;

transform, through XSLT transformation, the first XSD structure description file into a second XSD structure description file using predefined mapping rules, wherein the first XSD structure description file and the second XSD structure file define corresponding attributes; and

create, based at least in part on the second XSD structure description file, a third data container for the non-standard data element.

13. The apparatus of claim 12 wherein the second data container comprises a plurality of keys and a plurality of values, each key corresponding to one of the second attributes of the non-standard data element.

14. The apparatus of claim 13 wherein one of the keys of the second data container defines a type for each non-standard data element.

15. The apparatus of claim 13 wherein the second data container is a business object model, the business object model being self-implemented.

16. The apparatus of claim 15 wherein the second data container comprises a self-serialization mechanism for serializing itself into an application target format, and a library embedding serialization information for serializing or deserializing the second data container.

17. The apparatus of claim 12 wherein the instructions, when executed by the at least one processor, further cause the apparatus to:

provide an application access to the second container by generating a generic container to which is assigned a unique generic type, the generic container containing the second data container.

18. The apparatus of claim 17 wherein the instructions, when executed by the at least one processor, further cause the apparatus to:

introspect the non-standard data element to permit the application to access the generic type assigned to the generic container.

19. The apparatus of claim 17 wherein the instructions, when executed by the at least one processor, further cause the apparatus to:

provide the application access to the first data container by converting the standard data element into another non-standard data element and adding the converted standard data element to the generic container.

20. The apparatus of claim 12 wherein the standard record data structure and the non-standard record data structure are stored in a shared storage area within the travel management system.

21. The apparatus of claim 12 wherein the standard record data structure and the non-standard record data structure are stored in different storage areas within the travel management system.

22. The apparatus of claim 12 wherein the content may be received by a plurality of chained applications at a content aggregator, the non-standard data element is transmitted between the chained applications through messages carrying self-serialization information, and the second data container is stored in the extended travel record when triggered by one of the applications.

23. A computer program product for managing content in a travel management system, the computer program product comprising:

a non-transitory computer readable storage medium; and

instructions stored on the non-transitory computer readable storage medium that, when executed by a processor, cause the processor to;

receive, from one or more content providers, a standard data element and a non-standard data element comprising the content;

receive, from the one or more content providers, a first XSD structure description file, wherein one or more first XML tags complying with the first XSD structure description file describe an attribute structure of the non-standard data element and one or more second XML tags complying with the first XSD structure description file describe one or more auxiliary constraints associated with the non-standard data element;

create a first data container for the standard data element in an extended record data structure, the first data container including a common record identifier and first data values for first attributes corresponding to the standard data element;

create, based at least in part on the one or more first XML tags, a second data container for the non-standard data element in the extended record data structure, the second data container including the common record identifier and second data values corresponding to second attributes for the non-standard data element;

apply, based at least in part on the one or more second XML tags, the one or more auxiliary constraints to the second data container;

configure a plurality of applications to use the second data container to access the non-standard data element, wherein the applications are executable by the travel management system in response to requests received by the travel management system;

manage access of each application to the first container and the second container in the extended record data structure based on the common record identifier, wherein the standard data element satisfies International Air Transport Association (IATA) constraints and is obtained from a global distribution system operating as the travel management system, and the non-standard data element fails to satisfy the IATA constraints and is obtained from a source other than the global distribution system;

transform, through XSLT transformation, the first XSD structure description file into a second XSD structure description file using predefined mapping rules, wherein the first XSD structure description file and the second XSD structure file define corresponding attributes; and

create, based at least in part on the second XSD structure description file, a third data container for the non-standard data element.