Routing IP packets to an aircraft

• US 6,643,274 B2
• Filed: 08/01/2002
• Issued: 11/04/2003
• Est. Priority Date: 08/31/2001
• Status: Expired due to Term

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: DʼAnnunzio, Michael A.
• Primary Examiner(s): MARCELO, MELVIN C
• Application Number:
  US10/210,224
• Publication Number:
  US 20030048786A1
• Time in Patent Office: 460 Days
• Field of Search: 370/252, 370/316, 370/401, 370/402, 370/475, 709/238
• US Class Current: 370/316
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/033 by updating distance vector protocols
• CPC Class Codes: H04L 45/54 Organization of routing tables
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04W 40/248 Connectivity information update

Abstract

A system and method for routing IP packets to an aircraft eliminates the need for the exchange of routing information via dynamic routing protocols between the aircraft and ground station routers. An Internet protocol (IP) packet routing table is populated by converting a tail number of the aircraft into a destination subnet address for the aircraft. Forward channel information for a ground router is determined based on the tail number. The method further provides for adding a route entry to the routing table based on the forward channel information and the destination subnet address such that the route entry enables the ground router to delivery IP packets to the aircraft.

Claims

1. A method for populating an Internet protocol (IP) packet routing table, the method comprising the steps of:

converting a tail number of an aircraft into a destination subnet address for the aircraft;

determining forward channel information for a ground router based on the tail number; and

adding a route entry to the routing table based on the forward channel information and the destination subnet address such that the route entry enables the ground router to deliver IP packets to the aircraft.

2. The method of claim 1 further including the steps of:

retrieving an aircraft identifier from an aircraft configuration table based on the tail number;

determining a subnet class for the aircraft; and

converting the aircraft identifier into the destination subnet address in accordance with the subnet class.

3. The method of claim 1 further including the step of retrieving the forward channel information from a communications link table.

4. The method of claim 3 further including the step of retrieving a forward channel identifier from the communications link table.

5. The method of claim 4 further including the step of retrieving a next hop address from a ground switching configuration table based on the forward channel identifier.

6. The method of claim 3 further including the step of retrieving a preference metric from the communications link table.

7. The method of claim 1 further including the step of building the route entry based on a next hop address.

8. The method of claim 7 further including the step of building the route entry based on a destination subnet address.

9. The method of claim 7 further including the step of building the route entry based on a subnet mask.

10. The method of claim 7 further including the step of building the route entry based on a preference metric, the preference metric defining a relative preference of data transmitted over the forward channel versus data transmitted over other forward channels.

11. A method for maintaining an Internet protocol (IP) communications link table, the method comprising the steps of:

defining forward channel identifiers for a plurality of aircraft tail numbers;

defining preference metrics for the plurality of aircraft tail numbers such that each tail number, corresponding forward channel identifiers and corresponding preference metric represents an entry in the communications link table; and

dynamically updating the entries based on data from an airborne polling link.

12. The method of claim 11 further including the step of assigning preference metrics based on load balancing considerations.

13. The method of claim 11 further including the steps of:

transmitting a polling signal; and

adding an entry to the communications link table when a new tail number responds to the polling signal.

14. The method of claim 11 further including the step of removing an entry from the communications link table.

15. A method for populating an Internet protocol (IP) packet routing table, the method comprising the steps of:

retrieving an aircraft identifier from an aircraft configuration table based on the tail number;

determining a subnet class for the aircraft;

converting the aircraft identifier into a destination subnet address in accordance with the subnet class;

retrieving a forward channel identifier from a communications link table based on the tail number;

retrieving a next hop address from a ground switching configuration table based on the forward channel identifier;

retrieving a preference metric from the communications link table, the preference metric defining a relative preference of data transmitted over the forward channel versus data transmitted over other forward channels; and

building the route entry based on the next hop address and the preference metric.

16. The method of claim 15 further including the step of building the route entry based on the destination subnet address.

17. The method of claim 15 further including the step of building the route entry based on a subnet mask.

18. An Internet protocol (IP) database comprising:

an aircraft configuration table for linking a tail number of the aircraft to a corresponding aircraft identifier;

a communications link table for linking the tail number to forward channel information; and

a ground switching table for linking the forward channel information to a next hop address such that the database enables addition of a routing entry to a routing table.

19. The database of claim 18 wherein the forward channel information includes a forward channel identifier.

20. The database of claim 18 wherein the forward channel information includes a preference metric, the preference metric defining a relative preference of data transmitted over the forward channel versus data transmitted over other forward channels.