Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA
Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA
Local Area Networks (LANs) in Aircraft - FTP Directory Listing - FAA
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Other Control Sites<br />
Controller<br />
ATC Voice<br />
A<br />
Control Site<br />
E<br />
Remote Site<br />
<strong>Aircraft</strong><br />
Avionics<br />
Pilots<br />
Crew<br />
<strong>Aircraft</strong><br />
operator<br />
ATC Data<br />
AOC/AAC Data<br />
Public Internet<br />
B<br />
C<br />
D<br />
Control<br />
Site<br />
Equipment<br />
MMC<br />
Technicians<br />
F<br />
Remote<br />
Site<br />
Equipment<br />
MMC<br />
G<br />
G<br />
Technicians<br />
H<br />
Passengers<br />
<strong>Aircraft</strong><br />
Pilots<br />
Avionics<br />
Crew<br />
Passengers<br />
AAC = Airl<strong>in</strong>e Adm<strong>in</strong>istration Communication<br />
AOC = Airl<strong>in</strong>e Operational Communication<br />
ATC = Air Traffic Control<br />
MMC = Ma<strong>in</strong>tenance, monitor, and control<br />
Figure 2. Generic Future Communication System Physical Architecture [17]<br />
Advocates have identified undesirable security implications with the approach shown <strong>in</strong> figure 1,<br />
related to potentially expos<strong>in</strong>g avionics systems to passenger devices and systems. These<br />
advocates argue that the advantages achieved by remov<strong>in</strong>g the historic security air gap between<br />
avionics and passenger systems cannot justify the <strong>in</strong>creased risk to avionic systems posed by that<br />
connectivity. Consequently, they have identified an alternative target architecture, which is<br />
shown <strong>in</strong> figure 3.<br />
Exist<strong>in</strong>g<br />
Airborne Equipment<br />
<strong>Aircraft</strong> Control<br />
(possibly conta<strong>in</strong><strong>in</strong>g<br />
an IP Network)<br />
Non-IP communication<br />
<strong>in</strong>terface<br />
Non-IP communication<br />
<strong>in</strong>terface<br />
Nonessential<br />
IP<br />
network<br />
Passenger<br />
Internet<br />
Services<br />
Difference<br />
1<br />
Proposed Target<br />
Airborne Equipment<br />
<strong>Aircraft</strong> Control<br />
(conta<strong>in</strong><strong>in</strong>g an<br />
IP Network)<br />
IP IP communication<br />
<strong>in</strong>terface<br />
Nonessential<br />
IP<br />
network<br />
Passenger<br />
Internet<br />
Services<br />
Primary differences <strong>in</strong> proposed<br />
target environment:<br />
1. <strong>Aircraft</strong> Control, and<br />
Airl<strong>in</strong>e Information<br />
Services share a common<br />
network system.<br />
2. Specific <strong>Aircraft</strong> Control and<br />
Airl<strong>in</strong>e Information Services<br />
processes form distributed<br />
network relationships with<br />
NAS ground computers by<br />
us<strong>in</strong>g an IP-based air-to-ground<br />
l<strong>in</strong>k.<br />
Floppy<br />
Difference<br />
2<br />
However, the air gap between the<br />
<strong>Aircraft</strong> passengers and the avionics<br />
systems rema<strong>in</strong>s <strong>in</strong> tact.<br />
Airl<strong>in</strong>e Ground<br />
Airl<strong>in</strong>e Ground<br />
Systems &<br />
Systems & Internet<br />
Internet<br />
Airl<strong>in</strong>e Ground<br />
Systems<br />
Internet<br />
Figure 3. Alternative Notional <strong>Aircraft</strong> Architecture<br />
11