# US 11,907,323 B2 · System and method for legacy-based access to non-legacy data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,907,323 B2 - Document ID: US11907323B2 - Status: Granted - Kind: B2 - Application number: 17/668,013 - Filed: 2022-02-09 - Published: 2022-06-02 - Granted: 2024-02-20 - Earliest claimed: 2019-12-23 - Assignees: Amadeus S.A.S. - Applicants: Amadeus S.A.S. - Inventors: Pierre Brun; Jean-Chafic Hays; Fabien Bernard Blondet; Veronique Dupuy; Ludovic Vouriot - Web page: https://patentgrep.com/patent/US11907323B2 ## CPC - G06F 16/907: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually - G06F 16/972: {Access to data in other repository systems, e.g. legacy data or dynamic Web page generation} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method for legacy-based access to non-legacy data includes: receiving, at an intermediation server, a non-legacy data object containing non-legacy content; generating a legacy data object containing the non-legacy content, for storage in a repository; storing, in association with the legacy data object, a non-legacy distribution channel indicator; adjusting a legacy processing mechanism at the repository according to the non-legacy distribution channel indicator; receiving from a client subsystem, via a legacy interface, a request for the non-legacy content; and in response to the request, retrieving and sending the legacy data object containing the non-legacy content, via the legacy interface. ## Claims ### Claim 1 A method for legacy-based access to non-legacy data, the method comprising: storing, in a repository, a plurality of legacy data objects each containing legacy content received via a legacy distribution channel; receiving, at an intermediation server via a non-legacy distribution channel distinct from the legacy distribution channel, a non-legacy data object containing non-legacy content for storage in the repository; in response to receiving the non-legacy data object: (i) generating a further legacy data object containing the non-legacy content, for storage in the repository, the further legacy object having a format corresponding to the legacy distribution channel; (ii) storing the further legacy data object in the repository with the plurality of legacy data objects; (iii) storing, in association with the further legacy data object, a non-legacy distribution channel indicator indicating that an origin of the further legacy data object is distinct from an origin of the legacy data objects containing legacy content; and (iv) in response to storing the further legacy data object and the non-legacy distribution channel indicator, modifying a legacy processing mechanism according to adjustment configuration data; receiving from a client subsystem, via a legacy interface, a request for the further legacy data object; and in response to the request: (i) selecting a further legacy processing mechanism corresponding to the request; (ii) selecting, based on the adjustment configuration data, an adjustment to the further legacy processing mechanism; and (iii) according to the adjustment, retrieving and sending the further legacy data object containing the non-legacy content, via the legacy interface. ### Claim 2 (depends on 1) The method of claim 1, wherein storing the non-legacy distribution channel indicator includes storing the non-legacy distribution channel indicator in a field of the further legacy data object. ### Claim 3 (depends on 1) The method of claim 1, wherein selecting the adjustment includes: determining that the further legacy data object is associated with the non-legacy distribution channel indicator; and in response to the determining, selecting an alternative processing mechanism distinct from the further legacy processing mechanism. ### Claim 4 (depends on 1) The method of claim 1, wherein the non-legacy content is obtained via New Distribution Capability (NDC) messaging, and wherein the legacy data objects are obtained via Global Distribution System (GDS) messaging. ### Claim 5 (depends on 1) The method of claim 1, wherein the legacy processing mechanism is a publication mechanism configured to transmit legacy content to a further subsystem. ### Claim 6 (depends on 1) The method of claim 1, wherein sending the further legacy data object includes sending the non-legacy distribution channel indicator. ### Claim 7 (depends on 1) The method of claim 1, wherein sending the further legacy data object includes sending the non-legacy content and omitting the non-legacy distribution channel indicator. ### Claim 8 (depends on 1) The method of claim 1, wherein modifying the legacy processing mechanism includes applying a non-legacy access restriction. ### Claim 9 An intermediation server, comprising: a memory storing a repository containing a plurality of legacy data objects each containing legacy content received via a legacy distribution channel; a communications interface; and a processor connected with the communications interface and the memory, the processor configured to: receive, via the communications interface via a non-legacy distribution channel distinct from the legacy distribution channel, a non-legacy data object containing non-legacy content for storage in the repository; in response to receiving the non-legacy data object: (i) generate a further legacy data object containing the non-legacy content, the further legacy object having a format corresponding to the legacy distribution channel; (ii) store the further legacy data object in the repository with the plurality of legacy data objects; (iii) store, in association with the further legacy data object, a non-legacy distribution channel indicator indicating that an origin of the further legacy data object is distinct from an origin of the legacy data objects containing legacy content; and (iv) in response to storing the further legacy data object and the non-legacy distribution channel indicator, modify a legacy processing mechanism according to adjustment configuration data; receive from a client subsystem, via a legacy interface, a request for the further legacy data object; and in response to the request: (i) select a further legacy processing mechanism corresponding to the request; (ii) select, based on the adjustment configuration data, an adjustment to the further legacy processing mechanism; and (iii) according to the adjustment, retrieve and send the further legacy data object containing the non-legacy content, via the legacy interface. ### Claim 10 (depends on 9) The intermediation server of claim 9, wherein the processor is configured, in order to store the non-legacy distribution channel indicator, to store the non-legacy distribution channel indicator in a field of the further legacy data object in the repository. ### Claim 11 (depends on 9) The intermediation server of claim 9, wherein the processor is configured, in order to select the adjustment, to: determine that the further legacy data object is associated with the non-legacy distribution channel indicator; and in response to the determination, select an alternative processing mechanism distinct from the further legacy processing mechanism. ### Claim 12 (depends on 9) The intermediation server of claim 9, wherein the non-legacy content is obtained via New Distribution Capability (NDC) messaging, and wherein the legacy data objects are obtained via Global Distribution System (GDS) messaging. ### Claim 13 (depends on 9) The intermediation server of claim 9, wherein the legacy processing mechanism is a publication mechanism configured to transmit legacy content to a further subsystem. ### Claim 14 (depends on 9) The intermediation server of claim 9, wherein the processor is configured to send the non-legacy distribution channel indicator with the further legacy data object. ### Claim 15 (depends on 9) The intermediation server of claim 9, wherein the processor is configured to send the non-legacy content and omit the non-legacy distribution channel indicator when sending the further legacy data object. ### Claim 16 (depends on 9) The intermediation server of claim 9, wherein the processor is configured, in order to modify the legacy processing mechanism, to apply a non-legacy access restriction. ### Claim 17 A non-transitory computer-readable medium storing computer-readable instructions executable by a processor of an intermediation server to: store, in a repository, a plurality of legacy data objects each containing legacy content received via a legacy distribution channel; receive, via a communications interface via a non-legacy distribution channel distinct from the legacy distribution channel, a non-legacy data object containing non-legacy content for storage in the repository; in response to receiving the non-legacy data object: (i) generate a further legacy data object containing the non-legacy content, the further legacy object having a format corresponding to the legacy distribution channel; (ii) store the further legacy data object in the repository with the plurality of legacy data objects; (iii) store, in association with the further legacy data object, a non-legacy distribution channel indicator indicating that an origin of the further legacy data object is distinct from an origin of the legacy data objects containing legacy content; and (iv) in response to storing the further legacy data object and the non-legacy distribution channel indicator, modify a legacy processing mechanism according to adjustment configuration data; receive from a client subsystem, via a legacy interface, a request for the further legacy data object; and in response to the request; (i) select a further legacy processing mechanism corresponding to the request; (ii) select, based on the adjustment configuration data, an adjustment to the further legacy processing mechanism; and (iii) according to the adjustment, retrieve and send the further legacy data object containing the non-legacy content, via the legacy interface. ### Claim 18 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the instructions are executable by the processor to: store the non-legacy distribution channel indicator by storing the non-legacy distribution channel indicator in a field of the further legacy data object. ### Claim 19 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the legacy processing mechanism is a publication mechanism configured to transmit legacy content to a further subsystem. ### Claim 20 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the instructions are executable by the processor to: modify the legacy processing mechanism by applying a non-legacy access restriction.