IP Library › Granted Patent US 11,875,282

Granted Patent B2

US 11,875,282 · App. 18/093,093 · Granted Jan 16, 2024

Device, system and method for mode-based synchronization of data records

Inventors: Gerard Yin (Biot, FR); Pierre-Philippe Di Costanzo (Biot, FR); Olivier Daniel Bernier (Biot, FR); Stephane Lecourtois (Biot, FR)

Assignee: AMADEUS S.A.S.

G06Q10/02 G06F16/2379 G06F16/27 G06Q20/0457 G06Q20/322 G06Q30/0633 G06Q50/14

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 11,875,282
App. No.: 18/093,093
Granted: Jan 16, 2024
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

A device, system and method for mode-based synchronization of data records is provided. Booking data is received, at one or more computing devices, from one of a first and second client device. When received from the first client device, in a first order mode for the booking data, the device(s): cause an order management system (OMS) to generate: order data at a first database; and cause a legacy system to generate a corresponding passenger name record (PNR) at a second database, the corresponding PNR being one-way synchronized to the order data. When received from the second client device, in a legacy mode for the booking data, the device(s): cause the legacy system to generate, a PNR and/or ticket data at the second database; and cause the OMS to generate corresponding order data at the first database, the corresponding order data being one-way synchronized to the PNR and/or the ticket data.

Claims (79)

1. A computing device comprising:

at least one controller configured to:

when booking data is received from a first client device in communication with an order management system (OMS), in a first order mode:

cause the OMS to generate order data;

cause a legacy system to generate corresponding passenger-related data one-way synchronized to the order data;

change the order data according to change data from a second client device in communication with the legacy system, the order data redirected from the legacy system to the OMS; and

one-way synchronize the corresponding passenger-related data with the order data as changed; and

when the booking data is received from the second client device, in a legacy mode:

cause the legacy system to generate passenger-related data;

cause the OMS to generate corresponding order data that is one-way synchronized to the passenger-related data;

change the respective order data according to respective change data from the first client device that is redirected from the OMS to the legacy system; and

one-way synchronize the corresponding order data with the passenger-related data as changed.

2. The computing device of claim 1 , wherein the first order mode and the legacy mode are particular to the booking data.

3. The computing device of claim 1 , wherein the order data and the corresponding order data are stored at a first database in communication with the OMS, and the corresponding passenger-related data and the passenger-related data are stored at a second database in communication with the legacy system.

4. The computing device of claim 1 , wherein the controller is further configured to:

one-way synchronize the corresponding passenger-related data with the order data as changed during a one-way synchronization from the OMS to the legacy system; and

one-way synchronize the corresponding order data with the passenger-related data as changed during a one-way synchronization from the legacy system to the OMS.

5. The computing device of claim 1 , wherein the at least one controller is further configured to, in the first order mode:

prevent a change to the corresponding passenger-related data based on the change data being received at the legacy system.

6. The computing device of claim 1 , wherein the at least one controller is further configured to, in the legacy mode:

prevent a change to the corresponding order data based on the respective change data being received at the OMS.

7. The computing device of claim 1 , wherein the at least one controller is further configured to:

when the booking data is received from the first client device, in a second order mode, cause the legacy system to generate corresponding ticket data one-way synchronized to the order data.

8. The computing device of claim 1 , wherein the at least one controller is further configured to, in the first order mode:

receive a request to switch from the first order mode to the legacy mode;

cause the legacy system to generate corresponding ticket data as a component of the corresponding passenger related-data; and

change the corresponding passenger related-data from being one-way synchronized to the order data, to the order data being one-way synchronized to the corresponding passenger related-data data.

9. The computing device of claim 1 , wherein the at least one controller is further configured to, in the first order mode:

receive, from the second client device, booking change data that is not supported by the OMS;

cause the legacy system to generate corresponding ticket data as a component of the corresponding passenger related-data;

change the corresponding passenger related-data from being one-way synchronized to the order data, to the order data being one-way synchronized to the corresponding passenger related-data;

cause the legacy system to change the corresponding passenger related-data according to the booking change data; and

one-way synchronize the order data with the corresponding passenger related-data as changed.

10. A method comprising:

receiving, at one or more computing devices, booking data, the booking data received from one of: a first client device in communication with an order management system (OMS); and a second client device in communication with a legacy system;

when the booking data is received from the first client device, in a first order mode, via the one or more computing devices:

causing the OMS to generate order data;

causing the legacy system to generate corresponding passenger-related data one-way synchronized to the order data;

changing the order data according to change data from the second client device, the order data redirected from the legacy system to the OMS; and

one-way synchronizing the corresponding passenger-related data with the order data as changed; and

when the booking data is received from the second client device, in a legacy mode, via the one or more computing devices:

causing the legacy system to generate passenger-related data;

causing the OMS to generate corresponding order data that is one-way synchronized to the passenger-related data;

changing the respective order data according to respective change data from the first client device that is redirected from the OMS to the legacy system; and

one-way synchronizing the corresponding order data with the passenger-related data as changed.

11. The method of claim 10 , wherein the first order mode and the legacy mode are particular to the booking data.

12. The method of claim 10 , wherein the order data and the corresponding order data are stored at a first database in communication with the OMS, and the corresponding passenger-related data and the passenger-related data are stored at a second database in communication with the legacy system.

13. The method of claim 10 , further comprising:

one-way synchronizing the corresponding passenger-related data with the order data as changed during a one-way synchronization from the OMS to the legacy system; and

one-way synchronizing the corresponding order data with the passenger-related data as changed during a one-way synchronization from the legacy system to the OMS.

14. The method of claim 10 , further comprising, in the first order mode:

preventing a change to the corresponding passenger-related data based on the change data being received at the legacy system.

15. The method of claim 10 , further comprising, in the legacy mode:

preventing a change to the corresponding order data based on the respective change data being received at the OMS.

16. The method of claim 10 , further comprising:

when the booking data is received from the first client device, in a second order mode, causing the legacy system to generate corresponding ticket data one-way synchronized to the order data.

17. The method of claim 10 , further comprising, in the first order mode:

receiving a request to switch from the first order mode to the legacy mode;

causing the legacy system to generate corresponding ticket data as a component of the corresponding passenger related-data; and

changing the corresponding passenger related-data from being one-way synchronized to the order data, to the order data being one-way synchronized to the corresponding passenger related-data data.

18. The method of claim 10 , further comprising, in the first order mode:

receiving, from the second client device, booking change data that is not supported by the OMS;

causing the legacy system to generate corresponding ticket data as a component of the corresponding passenger related-data;

changing the corresponding passenger related-data from being one-way synchronized to the order data, to the order data being one-way synchronized to the corresponding passenger related-data;

causing the legacy system to change the corresponding passenger related-data according to the booking change data; and

one-way synchronizing the order data with the corresponding passenger related-data as changed.

19. A non-transitory computer-readable medium storing a computer program, wherein execution of the computer program is for: