Internet Protocol Aviation Usage

Download Report

Transcript Internet Protocol Aviation Usage

Multi-Domained, Multi-Homed
Mobile Networks
Mobile Platform Internet (MPI)
http://www.multicasttech.com/mpi/
mailing list:
[email protected]
Terry Davis – Boeing ([email protected])
Will Ivancic – NASA Glenn ([email protected])
1
Common Sectors
•
•
•
•
•
•
Aviation
Maritime
Trains
Trucking (Shipping)
Automotive
Others ???
2
How Do You Select and
Implement the Routing Path?
High Speed SatCom Network
•
•
•
•
•
Globally Available
Affected by Weather
Higher Bandwidth
High Latency
High Cost
Low Speed SatCom Network
Entertainment
Mobile Network
Command and
Control
Operations
•
•
•
•
•
Globally Available
Low Bandwidth
High Latency
Very High Cost
Redundant
Low Rate VHF
High Speed Terrestrial
• Reliable
• Low Latency
•
•
•
•
High Speed LOS Network
•
•
•
•
•
Globally Available
High Bandwidth
Low Latency
Lower Security
Moderate Cost
Internet
Destination Network
(for Entertainment)
How do you decide which path the data should take?
How do you cause the network(s) to route the data via this path?
Not Available when Mobile
High Bandwidth
Low latency
Lower Cost
Destination Network
(for Operations)
Destination Network
(for Command & Control)
3
Aviation Specific Issues
• Safety of Life / Safety of Flight
– Time-Critical command and control for Air Traffic Control
• Fast convergence time is essential!
• New radio link technologies are “uncertified” for Air Traffic
Control / Air Operations Communications (ATC/AOC)
• Regulatory requirements force network design
• Three independent network domains
– (required for regulatory, QoS, & security)
– Passenger & In-Flight-Entertainment
– Airline Operations
– Air Traffic Control
• Service providers may be authorized to carry one, two, or all
services.
• ATC will be a “closed network”
4
• Multiple security and authentication architectures
Aircraft
Airplane Communications
CLOSED
CLOSED Domain
Domain
PRIVATE
PRIVATE Domain
Domain
Control
Control the
theAircraft
Aircraft
Operate
Operatethe
theAircraft
Aircraft
Inform/Entertain
Inform/Entertain the
thePassengers
Passengers
Aircraft
Aircraft
Control
Control
Domain
Domain
Airline
Airline
Information
Information
Services
Services
Domain
Domain
Passenger
Passenger
Info.
Info. and
and
Entertain
Entertain
Services
Services
Domain
Domain
Air-Ground
Network Interface
VHF / HF /
SATCOM
Air-Ground
Network Interface
Wireless
LAN
PUBLIC
PUBLIC Domain
Domain
Air-Ground
Network Interface
SATCOM/
Cellular
Air-Ground
Broadband Network
(e.g., INMARSAT)
Airport Network
(e.g., Gatelink)
Passenger
Passenger
-owned
-owned
Devices
Devices
Passenger-accessed
Passenger-accessed
rd Party
33rd
Party Providers
Providers
Airline-Approved
Airline-Approved
rd Party
33rd
Party Providers
Providers
Airline
Airline
Air-Ground
Datalink Services
(e.g., ACARS)
Air
Air Traffic
Traffic Service
Service
Providers
Providers
5
In-Air Communication
• Multiple networks with varying criteria for utilizing
different links
– Aircraft Control Domain
– Airline Information Services Domain
– Passenger Information and Entertainment Services
Domain
• Often multiple links will be active to the same
domain simultaneously.
• May need to have connectivity to 10 or more
ISPs depending on what airports one flies into
– Need to autonomously connect to service providers
– Each airport controls the ISP contracts
6
ISO Aeronautics Telecommunication Network
(ATN) Island Routing Domain Confederation
Mobile RD
Mobile RD
Another
ATN Island
ATN Backbone RDC
ATN TRD
ATN TRD
Mobile RD
ATN Island RDC
ATN TRD
ATN ERD
ATN ERD
ERD – End Routing Domain
RD – Routing Domain
RDC – Routing Domain Confederation
TRD – Transit Routing Domain
 OSI IDRP Routing
• Controlled topology to ensure
rapid route prorogation
 Routing Protocols requires
ownership/coordination of
infrastructure
• Injecting routes
7
• Not deployed due to cost
BGP/OSPF for Air Traffic
Control
E-BGP requires
If you don’t own the
Air
BGP
Ground
configuration with each
infrastructure, you
Autonomous Systems.
probably will not be
This is a scalability
allowed to inject routes!
problem.
BGP/OSPF
OSPF
Mobile-1
AREA 1
BGP
BGP/OSPF
OSPF
Mobile-2
AREA 0
BGP/OSPF
OSPF
AREA N
BGP
BGP/OSPF
Mobile-N
This may work for ATC, but not for AOC or Passenger Services
(AOC is a closed network and will not propagate routes to the world)
8
Multiplexing at the Radio
ATC
ATC
NEMO-1
MUX
NEMO-1
Satellite
AOC
AOC
NEMO-2
MUX
NEMO-2
WiFi
HA
Passenger
Passenger
NEMO-3
HA
MUX
NEMO-3
VHF
HA
If one requires a separate nemo
router for each domain, then, failure
to Multiplex requires a radio for each
interface!
9
Antenna Systems
Note, this picture does not show:
• Satellite links
• Passenger service links
• Gate links (WiFi)
• Gate links (umbilical cord)
10
Communication
and Display
Air Traffic
Management
LAN
Operations
LAN
(Avionics)
Mobile
Network 1
Mobile
Network 2
Sensor Controller
(Optional Display)
Multiplexing
at the Router
SATCOM
AERO-1
SATCOM
AERO-HH
VHF
Voice/DATA
Mobile
Router
NEM0-1
NEMO-2
NEMO-3
HF
Voice/DATA
INMARSAT
Swift 64
High-Rate
Satellite
WiFi Max
Mobile
Network 3
Passenger
Services
GateLink
Cellular
Future Links
11
Global HAHA for NEMO
VPNPrimary
Endpoint
X
VPN
Endpoint
Secondary
Home Agent
Home Agent
Secondary Home Agent
provides pseudo route optimization
which is useful over long distances
Beware of VPN tunnels.
If security is not considered up front, it may negate route optimization! 
12
Global HaHa
• Draft allows for
– Distribute HAs at IP layer
• HA to HA communications at layer 3 to get rid of home link in
configurations where it is not needed
– MIP proxy for local mobility management
• to allow a mobile router to bind locally as it is roaming far away
from any of its own home agents
– Pseudo route optimization in the infrastructure
• No Security
• Concerns
– How is routing accomplished to get to appropriate HA?
– How many home agents will aviation need?
– How fast can one switch to a new home agent?
13
Monami6 for Aeronautics
14
Multiple Links to Aircraft
• Failover for safety-of-life critical control
traffic
• Separation of governmental control, airline
corporate, and passenger network traffic
– Differing priorities on same link
– Differing link forwarding selection according to
policy
15
Policy-Based Routing,
All Links Active
P-DATA
AOC
Mobile
Router
P-DATA
High speed link
P-DATA
P-DATA
Home
Agent
int1
ATC
Low latency link
AOC
AOC
P-DATA
Routing
Policy
ATC
int2
int3
P-DATA
Reliable link
ATC
ATC
AOC
Routing
Policy
16
Policy-Based Routing,
Critical Link Active
P-DATA
AOC
Mobile
Router
High speed link
P-DATA
Home
Agent
int1
ATC
Low latency link
AOC
P-DATA
int3
Routing
Policy
ATC
int2
Reliable link
ATC
ATC
Routing
Policy
17
Policy-Based Routing,
Passengers Link Active
P-DATA
AOC
Mobile
Router
High speed link
P-DATA
P-DATA
AOC
int1
ATC
P-DATA
ATC
Home
Agent
P-DATA
Low latency link
P-DATA
int3
Routing
Policy
AOC
int2
Reliable link
ATC
Routing
Policy
18
Multiple Care-of Addresses
• Some governments provide VHF/UHF airto-ground network infrastructure
• Multiple commercial service providers for
satellite and other links
Multiple HAs
• Removes potential single-point-of-failure
for safety-of-life traffic
19
Within Monami6 ...
• Assume an aircraft has a NEMO MR with X links
and care-of addresses, and Y geographically
distributed home agents
– X*Y bidirectional tunnels
– But only a few active at one time
• At MR, downlink tunnel selection (CoA and HA
pair) based on policy for traffic class of each
packet
• At HA, uplink tunnel selection (CoA) based on
policy
• Different security mechanisms for each tunnel
based on policy
20
Desires
• Multiple CoA option works for NEMO
– GOOD based on draft-ietf-monami6multiplecoa-00
• Support use of flow binding option for
NEMO HA-MR tunnel selection
– draft-soliman-monami6-flow-binding-02 is
currently worded very mobile-node (not
NEMO) centric, although seems to work well
for NEMO too
21
Recommendations / Desires
22
Recommendations / Desires
• Need Route Optimization for Large Mobile
Platforms that move over large geographical
areas.
– Global HAHA is a potential
– Other proposals also should be considered
• Including work being done in IRTF MOBOPTS
• It is highly desirable to have multiple NEMOs in
a single router (multi-domained nemos)
– What are the security implications of this?
• Need to examine Security Architecture relative to
mobility mechanisms
– If we are not careful, security may undo route
optimization.
– Ensure the IKEv2 and revised IPsec architecture are
23
considered
Recommendations / Desires
• Aspects of MANET Autoconfiguration may be
applicable to traditional routing for large mobile
systems regarding the air/ground interface
addressing.
• MONAMI6 currently appears to be handling the
needs of large mobile platforms.
• It would be advantageous if the filtering
mechanisms and policy-base routing for
monami6 worked with a hybrid
nemo/mip/traditional routing configurations.
24
Non-IETF (?) Issues or Not?
• Automated access to networks –
particularly access to radio systems
(Internet Docking for Mobile Networks)
• Implementation solutions are a
combination of architecture, protocol and
policy. Is it appropriate to have an
“Informational document” for large mobile
platforms?
25
Mobile Platform Internet (MPI)
• Web Page:
– http://www.multicasttech.com/mpi/
• To Join to the mailing list, E-mail to:
– [email protected]
26