Database architecture for an air traffic information system

• US 20050080794A1
• Filed: 10/31/2003
• Published: 04/14/2005
• Est. Priority Date: 10/10/2003
• Status: Active Grant

• Current Assignee: SAAB Cars
• Original Assignee: Nav Canada
• Inventors: Penny, Keith, Zanin, Jeff, Ledingham, Robert, Aikins, Howard, Zak, Roman
• Granted Patent: US 7,263,518 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G08G 5/0013 with a ground station
• CPC Class Codes: G08G 5/0026 located on the ground
• CPC Class Codes: H04L 63/0209 Architectural arrangements, e.g. perimeter networks or demilitarized zones
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A database architecture for an air traffic information display system includes a data manager including a first interface, a first database server connected to the data manager via the first interface, a firewall connected to the first database server; and a second database server connected to the first database server via the firewall and including a stored procedure for copying data from the first database. The second database server is used for computations based upon the data transactions pulled from the first database server. Thereby off-loading the first database server so that it can be more responsive to the data manager with respect to current changes. The firewall between the two servers prevents the data in the first server from being corrupted by users of the system.

Claims

1. A database architecture for an air traffic information display system comprising:

a data manager including a first interface;

a first database server connected to the data manager via the first interface;

a firewall connected to the first database server; and

a second database server connected to the first database server via the firewall and including a stored procedure for copying data from the first database.

2. A system as claimed in claim 1 wherein the first database server includes first tables for current data and second tables for logging changes to current data.

3. A system as claimed in claim 2 wherein the first tables include a flight data table.

4. A system as claimed in claim 2 wherein the first tables include an airport system table.

5. A system as claimed in claim 2 wherein the first tables include a system table.

6. A system as claimed in claim 2 wherein the second tables include a flight data table.

7. A system as claimed in claim 2 wherein the second tables include an airport system table.

8. A system as claimed in claim 2 wherein the second tables include a system table.

9. A system as claimed in claim 1 wherein the first interface is ODBC.

10. A system as claimed in claim 1 wherein the second database server includes third tables for receiving updates from the second tables.

11. A system as claimed in claim 10 wherein the second database server includes fourth tables for logging copies of the third tables.

12. A system as claimed in claim 11 wherein the gateway database server includes fifth tables for storing movements.

13. A system as claimed in claim 12 wherein the second database server includes a module for calculating movements in dependence upon changes in the third tables.

14. A method of storing air traffic information comprising the steps of:

receiving a data update request;

changing the data in accordance with the request;

storing the changed data in a first database server; and

copying the changed data to a second database server separated from the first by a firewall.

15. A method as claimed in claim 14 wherein the step of storing includes storing the changed data in first tables.

16. A method as claimed in claim 14 wherein the step of storing includes storing a log of data change transactions in second tables.

17. A method as claimed in claim 15 wherein the first tables include a flight data table.

18. A method as claimed in claim 15 wherein the first tables include an airport system table.

19. A method as claimed in claim 15 wherein the first tables include a system table.

20. A method as claimed in claim 16 wherein the second tables include a flight data table.

21. A method as claimed in claim 16 wherein the second tables include an airport system table.

22. A method as claimed in claim 16 wherein the second tables include a system table.

23. A method as claimed in claim 14 wherein the step of copying includes storing updates from the second tables in third tables.

24. A method as claimed in claim 14 wherein the step of copying includes logging copies of the third tables in fourth tables.

25. A method as claimed in claim 14 wherein the step of copying includes calculating movements in dependence upon changes in the third tables.

26. A method as claimed in claim 25 wherein the step of calculating includes storing movements in fifth tables.