# US 2018/0322422 A1 · Content exchange with a travel management system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0322422 A1
- Document ID: US20180322422A1
- Status: Published application
- Kind: A1
- Application number: 16/038,482
- Filed: 2018-07-18
- Published: 2018-11-08
- Earliest claimed: 2014-05-30
- Assignees: Amadeus S.A.S.
- Applicants: Amadeus S.A.S.
- Inventors: Vanessa Fontebride; Christel Charrat; Ludovic Le Sinq; Marion Francois; Pierre Gadeyne; Christian Ceelen
- Web page: https://patentgrep.com/patent/US20180322422A1

## CPC

- G06Q 10/02: Reservations, e.g. for tickets, services or events
- G06Q 50/14: Travel agencies
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

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.

## Claims

### Claim 1

A method of exchanging content with a travel management system, the method comprising:
maintaining, at the travel management system, a plurality of records in an extended record data structure that includes a data container containing data elements;
associating each record with a respective structure description file defining a structure of attributes associated with the data elements based upon predefined local mapping rules;
configuring a plurality of applications to use the data container to access the data elements, wherein the applications are executable by the travel management system in response to requests received by the travel management system;
associating a common record identifier with the content and managing access of each application to the records maintained in the extended record data structure based on the associated common record identifier; and
generating, at the travel management system, a first data exchange message including the structure description file of the data elements and a set of values corresponding to values of attributes of the data elements, wherein the data elements are accessed by at least one of the applications based on the common record identifier.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
transmitting the first data exchange message according to a first data exchange format from the travel management system to a client device; and
transforming the structure description file into a target structure description file using predefined mapping rules associated with the client device.

### Claim 3 (depends on 2)

The method of claim 2 wherein the predefined mapping rules relate to attributes required to generate a graphical user interface of the client device.

### Claim 4 (depends on 2)

The method of claim 2 wherein the first data exchange message comprises an XML message, the structure description file comprises an XSD schema, and the predefined mapping rules comprise XSLT style sheets.

### Claim 5 (depends on 1)

The method of claim 1 further comprising:
converting one of the data elements into a format consistent with a format of the data container; and
generating a second data exchange message from the structure description file associated with the converted data element and values of attributes of the converted data element; and
transmitting the second data exchange message according to a second data exchange format from the travel management system to a client device.

### Claim 6 (depends on 5)

The method of claim 5 further comprising:
updating one of the data elements by modifying the structure description file stored in the travel management system for a type of the data container.

### Claim 7 (depends on 6)

The method of claim 6 further comprising:
retrieving the modified structure description file associated with the updated data element based on the type of the data container.

### Claim 8 (depends on 1)

The method of claim 1 wherein the data container includes a set of keys for each attribute of the respective data element and a set of respective key values, and a type of the data element is stored as one of the keys for each attribute.

### Claim 9 (depends on 1)

The method of claim 1 wherein the data elements comprise first data elements obtained from a travel provider system or second data elements obtained from a source other than the travel provider system.

### Claim 10

An apparatus for exchanging content with 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:
maintain, at the travel management system, a plurality of records in an extended record data structure that includes a data container containing data elements;
associate each record with a respective structure description file defining a structure of attributes associated with the data elements based upon predefined local mapping rules;
configure a plurality of applications to use the data container to access the data elements, wherein the applications are executable by the travel management system in response to requests received by the travel management system;
associate a common record identifier with the content and managing access of each application to the records maintained in the extended record data structure based on the associated common record identifier; and
generate, at the travel management system, a first data exchange message including the structure description file of the data elements and a set of values corresponding to values of attributes of the data elements, wherein the data elements are accessed by at least one of the applications based on the common record identifier.

### Claim 11 (depends on 10)

The apparatus of claim 10 wherein the instructions, when executed by the at least one processor, cause the apparatus to:
transmit the first data exchange message according to a first data exchange format from the travel management system to a client device; and
transform the structure description file into a target structure description file using predefined mapping rules associated with the client device.

### Claim 12 (depends on 11)

The apparatus of claim 11 wherein the predefined mapping rules relate to attributes required to generate a graphical user interface of the client device.

### Claim 13 (depends on 11)

The apparatus of claim 11 wherein the first data exchange message comprises an XML message, the structure description file comprises an XSD schema, and the predefined mapping rules comprise XSLT style sheets.

### Claim 14 (depends on 10)

The apparatus of claim 10 wherein the instructions, when executed by the at least one processor, cause the apparatus to:
convert one of the data elements into a format consistent with a format of the data container; and
generate a second data exchange message from the structure description file associated with the converted data element and values of attributes of the converted data element; and
transmit the second data exchange message according to a second data exchange format from the travel management system to a client device.

### Claim 15 (depends on 14)

The apparatus of claim 14 wherein the instructions, when executed by the at least one processor, cause the apparatus to:
update one of the data elements by modifying the structure description file stored in the travel management system for a type of the data container.

### Claim 16 (depends on 15)

The apparatus of claim 15 wherein the instructions, when executed by the at least one processor, cause the apparatus to:
retrieve the modified structure description file associated with the updated data element based on the type of the data container.

### Claim 17 (depends on 10)

The apparatus of claim 10 wherein the data container includes a set of keys for each attribute of the respective data element and a set of respective key values, and a type of the data element is stored as one of the keys for each attribute.

### Claim 18 (depends on 10)

The apparatus of claim 10 wherein the data elements comprise first data elements obtained from a global distribution system or second data elements obtained from a source other than the global distribution system.

### Claim 19

A computer program product for exchanging content with 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:
maintain, at the travel management system, a plurality of records in an extended record data structure that includes a data container containing data elements;
associate each record with a respective structure description file defining a structure of attributes associated with the data elements based upon predefined local mapping rules;
configure a plurality of applications to use the data container to access the data elements, wherein the applications are executable by the travel management system in response to requests received by the travel management system;
associate a common record identifier with the content and managing access of each application to the records maintained in the extended record data structure based on the associated common record identifier; and
generate, at the travel management system, a first data exchange message including the structure description file of the data elements and a set of values corresponding to values of attributes of the data elements, wherein the data elements are accessed by at least one of the applications based on the common record identifier.
