Scalable on-board open data network architecture

• US 8,341,298 B2
• Filed: 05/19/2006
• Issued: 12/25/2012
• Est. Priority Date: 12/02/2005
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Wilber, George F., Brossard, Regan K.
• Primary Examiner(s): NGUYEN, MINH CHAU
• Application Number:
  US11/419,448
• Publication Number:
  US 20070127460A1
• Time in Patent Office: 2,412 Days
• Field of Search: 709/249, 701/3, 370/241, 370/253
• US Class Current: 709/249
• CPC Class Codes: H04L 49/351 for local area network [LAN], e.g. Ethernet switches
• CPC Class Codes: H04L 49/354 for supporting virtual local area networks [VLAN]
• CPC Class Codes: H04L 49/602 Multilayer or multiprotocol switching, e.g. IP switching
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

An embodiment of an open data network system facilitates communication between applications related to operation of a vehicle, such as an aircraft, and re-use of components in different systems and implementations. A switch/router communicates data between on-board systems. A server communicates with the switch/router and provides at least one of processing services and storage services to the on-board systems via the switch/router. A network manager communicates with the switch/router to direct the switch/router in selectively allowing access between the on-board systems. In other embodiments, an avionics interface unit communicates with the switch/router and enable communications between at least one avionics system and at least one of the on-board systems. Other embodiments selectively enable on-board systems to communicate with a ground-based network to provide communications between the aircraft and a stakeholder in the operation of the aircraft while isolating flight-critical avionics and flight communications systems from the open data network.

Claims

1. An aircraft comprising:

a plurality of subnets for providing flight-critical services, non-flight-critical services, and passenger services;

a plurality of e-switches for selectively isolating the subnets; and

a computer system running a network manager for providing network management services via a network protocol to each of the plurality of subnets, wherein the network protocol enables selective secure isolation between the subnets and data connectivity between the subnets.

2. The aircraft of claim 1, wherein the subnets and computer system communicate via a protocol that includes an IP layer, a network services layer on the IP layer, a system services layer on the network services layer, and an applications layer on the system services layer.

3. The aircraft of claim 2, wherein the system services layer controls access of applications in the applications layer to provide the selective secure isolation.

4. The aircraft of claim 2, wherein the network services layer provides at least some of network management, IP services, degraded operation, network addressing, and wireless access.

5. The aircraft of claim 2, further comprising a hardware layer, wherein changes in the application layer and the hardware layer are performable independently of changes to other layers.

6. The aircraft of claim 2, wherein the application layer supports at least some of electronic flight bag (“

EFB”

) applications, cabin applications, airline applications, and passenger entertainment applications.

7. The aircraft of claim 1, further comprising an aircraft avionics system for providing at least some of the flight critical services.

8. The aircraft of claim 7, wherein the network protocol enables selective secure isolation to prevent accidental or deliberate interference with the avionics system.

9. The aircraft of claim 1, further comprising a router for dividing the network into subnets.

10. The aircraft of claim 9, wherein the network manager is operable to communicate with the e-switches and the router.

11. The aircraft of claim 1, further comprising a subnet for providing storage and processing to the other subnets.

12. The aircraft of claim 1, wherein the subnets include a flight deck subnet, maintenance subnet, avionics data interference subnet, cabin services subnet, passenger services subnet, and communications subnet.

13. The aircraft of claim 1, wherein each subnet includes a collection of elements that provide a particular aircraft service.

14. The aircraft of claim 1, wherein the network protocol enables selective secure data connectivity between the subnets by refusing unauthorized communications.

15. The aircraft of claim 1, further comprising at least one of a flight deck services system;

a maintenance services system; and

a cabin services system for providing at least some of the non-flight critical services.