Providing Integrated Ad Hoc Mobility
Download
Report
Transcript Providing Integrated Ad Hoc Mobility
Research Challenges for Military
Networking
Ken Young
[email protected]
(973) 829-4928
September 6, 2002
Talk Outline
Background on military networking challenges
– ARL CTA program
– DARPA AJCN program
– CECOM MOSAIC ATD
Networking technologies
– Node and domain autoconfiguration
– Routing
– Reliable transport
– Other challenges
Integration challenges
Transition challenges
Conclusions
Cornell Workshop 6 Sept 2002– 2
Current Battlefield Networks - Tactical
Internet
Brigade TOC
Division TOC
MSE
Brigade TOC
NTDR
Upper Echelon
Brigade TOC
Battalion
TOC
Battalion
TOC
Battalion
TOC
EPLRS (Enhanced Position
Location Reporting System)
SINCGARS (Single Channel
Ground and Airborne System)
Cornell Workshop 6 Sept 2002– 3
Future Battlefield Networking Concept
Sustaining
Base
OTM Enclave
Sensor Nets
OTM Enclave
Cornell Workshop 6 Sept 2002– 4
FCS Networking Implications
Mobile ad hoc networks must smoothly blend heterogeneous
physical layers
Self-organizing and self-managing network operations
Networking that accommodates directional antennas
Network sessions must be maintained while on-the-move
Network survivability with graceful degradation
High throughput for collaborative C4ISR to support networkcentric operations
QoS for real-time traffic with dynamic network topologies
Indirect routing and dynamic load balancing
Mitigation of MAC/routing/transport layer vulnerabilities
Topology control and predictive routing for mobile line-of-sight
backbones
Cornell Workshop 6 Sept 2002– 5
Survivable Wireless Mobile Networks
Objective: Dynamically self-configuring wireless network
technologies that enables secure, scaleable, energy-efficient,
and reliable communications
Research challenges
– Scalability to thousands of nodes
– Highly mobile nodes and infrastructure
– Severe bandwidth and energy constraints
– Decentralized networking and dynamic reconfiguration
– Accommodation of high bit-error-rate, wireless networks
– Seamless interoperability
Scientific barriers
– Understanding of trade-offs under bandwidth, energy, processing
capability, bit-error-rate, latency, and mobility constraints
– Understanding of interactions between cross-layer algorithms
– Limited modeling capability for scaling distributed algorithms
Cornell Workshop 6 Sept 2002– 6
Node/Network Autoconfiguration
Config Database
BB
MySQL
Network GUI
Config Server
YAP low-bandwidth
configuration reports
Local GUI
ACM:
DCDP:
DRCP:
L-GUI:
N-GUI:
YAP:
Interface
ACM
DCDP distributes
new configuration
Node
DRCP configures
subnet interfaces
Preconfigured
node capabilities
Adaptive Configuration Manager
Dynamic Configuration Distribution Protocol
Dynamic and Rapid Configuration Protocol
Display of local node capabilities and configuration
Display of network topology and configuration
Configuration database maintenance and access protocol
Cornell Workshop 6 Sept 2002– 7
Node/Network Autoconfiguration Performance
16
dense
14
sparse
12
Autoconfiguration
Time
10
8
6
4
2
0
100
200
300
400
500
600
700
800
Number of nodes
900
1000
3500
3000
Autoconfiguration
Overhead
Bandwidth (bytes/second)
Configuration Time (seconds)
18
2500
Subnet overhead (refresh=10s)
Subnet overhead (refresh=30s)
2000
Network overhead (refresh=10s)
Network overhead (refresh=30s)
1500
1000
500
0
100
200
300
400
500
600
700
Number of nodes
800
900
Cornell Workshop 6 Sept 2002– 8
Domain Autoconfiguration
Objective: Autoconfigured domains for scalable, survivable and
efficient routing, configuration, security and QoS in dynamic
networks
Mountainous terrain
Research issues
– Dynamically selecting border nodes
– Aggregating domain information
– Algorithms to dynamically decide domain
membership based on node mobility, roles,...
– Scalable and robust protocols to create and
maintain domains in dynamic networks
– Isolating and resolving faults and intrusions
using dynamic domain reconfiguration
Unstable links
Approach
Stable links
– Hierarchical topological domains built from
individual interfaces
– Independent domains for each function
XX XXX
Flat terrain
Cornell Workshop 6 Sept 2002– 9
MANET Routing Hierarchy
Backbone Network
Conventional Routing
JTRS WNW Subnet
MANET Routing
Dismount Radios
MANET Routing
Gateway/Border Router Nodes
MANET Routing Examples
• AODV
• DSR
• ZRP
• OLSR
• TBRPF
• LANMAR
• FSR
• WARP
• DRD
• TORA
• FSLS
• ....
Cornell Workshop 6 Sept 2002– 10
Dynamic Border Router
Enhanced autoconfiguration
technology to create and
maintain domains
-
Mountainous terrain
DBR automatically selected if node
has interfaces in multiple domains
Demonstration on small testbed
(AODV/RIP & AODV/AODV)
Transition to CECOM MOSAIC ATD
Unstable links
Automatically selected by ACM
-
Developing algorithms to dynamically
decide domain membership based on
node mobility, roles, link stability...
Stable links
XX XXX
Flat terrain
Cornell Workshop 6 Sept 2002– 11
Heterogeneous Domain Routing
Objective: Develop scalable and efficient routing protocols in
heterogeneous mobile wireless networks
Approach
– Configure/reconfigure the
Domain instances
network into more homogeneous
routing domains
Reverse route
– Design routing modules specific
notification
to each domain for intra-domain
routing
Challenges
– Characterizing performance of
routing strategies in dynamic
and Byzantine environments
Inter-domain
– Interactions of routing protocols routing
at the border nodes
– Developing inter-domain routing
protocols for routing among
border nodes
Static,
sparse
domain
Routing modules
Link failure
notification
Highly
dynamic
domain
Domain instances
Probabilistic
broadcast
Domain specific routing
Cornell Workshop 6 Sept 2002– 12
Bandwidth Broker Functional Components
IP-level topology
• Config. Database dynamically updates
Per Class Resource Information
• Provisioned and available link capacity
Bandwidth Broker
Call Status Information
Domain wide QoS policy info
• DiffServ functions in nodes
Policy Resource
Database Database
Configuration
Database
via
YAP Server
Admission Control
& Resource
NEs
Manager
Other BBs
QoS Resource Management within domain
•
•
Database initialization and update
QoS Resource configuration in nodes
Admission Control into the domain
•
•
Based on network state, policy & requests
Also call/session events across domains
Network Nodes (Routers)
Applications
via
Service Manager
(SM)
Reliable UDP
TCP congestion control
Reliable
UDPavoids
communication
problems
in wireless
environment
• Avoids TCP
congestion
control problems
Cornell Workshop 6 Sept 2002– 13
Some Comparative Performance Test Results
DiffServ/BB
Service
Class
Single
Class
No
DiffServ
107 VoIP calls
WRR
PLR
Util
AF4 - TCP
67%
AF3 - VoIP 0.64%
80%
PLR
30%
Util
PLR
Priority
Util
PLR
Util
0.9% 0.66%
70% 0.73% 80%
56% 0.68%
80% 1.01%
80%
AF2 - Video
0% ~90%
30% ~50% 0.56% ~90% 0.43% ~90%
AF1 - UDP
128-byte
0% 100%
30%
70% 0.67% 100% 12%
90%
33%
65%
70%
BE - UDP
1024-byte
0.15%
96%
87%
65% 86%
Cornell Workshop 6 Sept 2002– 14
Reliable Transport
Objective: Alternative transport protocols that increase end-to-end
performance, survivability, and reliability of FCS applications
Approach
port
– SCTP (RFC 2960) for FCS environment
Partial delivery for differentiated QoS of multiple
prioritized streams
Multi-homing and cross-stream data bundling to
provide load balancing and path selection
Denial-of-service-resistant connection
establishment
Application
SCTP
IP
Link
132 (IANA)
... IP addresses
...
Physical
– Analyze empirically using SCTP reference
implementations
– Evaluate performance tradeoffs under different
mobility conditions
– Define visionary progress of SCTP for FCS
Research Issues
– Performance during failover/changeover
– Performance/bandwidth impact of avoiding abort/restart transport connections
that support longer term applications
– Optimal flow control for providing different QoS for application streams using
same transport connection
Cornell Workshop 6 Sept 2002– 15
Improved Transport Layer Congestion Control
• Explore new transport layer
alternatives for survivable
wireless mobile networks
• Capitalize on opportunity to
influence SCTP standard
• Split Fast Retransmit
Changeover-Aware
Congestion Control (SFR
CACC) algorithm submitted
as IETF Internet Draft
• Exploit transport layer multihoming for uninterrupted
end-to-end communication
• Significantly enhances transport layer’s ability to support
persistent on-the-move sessions for FCS networks
Cornell Workshop 6 Sept 2002– 16
Other Networking Research Challenges
Data Link Layer
– Energy-efficient topology control and MAC
– Self-organizing subnets
Quality of Service
– Estimating bandwidth and delay on individual links
– Allocating bandwidth and delay to meet end to end objectives
– QoS coordination across layers (physical to application)
Multicast
– With mobility, QoS, etc.
– Reliable multicast
Security
–
–
–
–
Distributed dynamic trust establishment and key management
Efficient, robust message authentication
Intrusion detection and mitigation
Vulnerability assessment
Network Management
– Fault detection and localization
– Self-healing
– ....
Cornell Workshop 6 Sept 2002– 17
Integration Example – MOSAIC AMPS
Function
Configuration
Mobility
Management
Routing
Reliability
Visualization
Security
QoS
Protocol/
Subfunction
Entity
Subnetwork
DRCP
Network
DCDP
Management
ACM
SIP
Location
DDNS
DMA
Continuous connectivity
Mangler
Unicast
RIP
Ad hoc unicast
AODV
Multicast
HLIM
Ad hoc multicast
MAODV
Border router
DBR
Transport
SCTP
Reporting
YAP
Local
L-GUI
Network
N-GUI
Authentication, key exchange IKE
Integrity, privacy
IPSec
802.11
SQC
IP
DiffServ
Management
BB
Source
Telcordia
Telcordia
Telcordia
Telcordia
Linux
Telcordia
Telcordia
Zebra
Mad-hoc/NIST
Telcordia
U. Maryland
Telcordia
Siemens
Telcordia
Telcordia
Telcordia
freeswan
freeswan
Telcordia
Telcordia
Telcordia
Code
C++
C++
Java
Java
C
C
Java
C
C
C
C
C
C
Java
Java
Java
C
C
C
C
Java
Cornell Workshop 6 Sept 2002– 18
Transition Example - JTRS SCA 2.0 View
OE
Non-CORBA
Security
Applications
Non-CORBA
Modem
Applications
RF
Non-CORBA
Modem API
Modem
Modem
Applications Adapter
Modem API
AMPS
AMPS
AMPS
Non-CORBA
Security API
Link, Network
Applications
Security Security Security
Adapter Applications Adapter
Link, Network API
Applications
Core Framework (CF)
Commercial Off-the-Shelf
(COTS)
Non-CORBA
Host
Applications
Non-CORBA
Host API
Link, Network
Applications
Host
Host
Adapter Applications
Link, Network API
Security API
Core Framework IDL (“Logical Software Bus” via CORBA)
CORBA ORB &
Services
(Middleware)
CF
Services &
Applications
POSIX Operating System
CORBA ORB &
Services
(Middleware)
CF
Services &
Applications
POSIX Operating System
Network Stacks & Serial Interface Services
Network Stacks & Serial Interface Services
Board Support Package (Bus Layer)
Board Support Package (Bus Layer)
Black (Secure) Hardware Bus
Red (Non-Secure) Hardware Bus
Cornell Workshop 6 Sept 2002– 19
Transition Example - FCS
Cornell Workshop 6 Sept 2002– 20
Conclusions
Networking challenges at multiple layers; interactions between
layers key in wireless mobile networks
– Data link
– Network
– Transport
What’s most important? Current FCS LSI opinion is that highest
risk areas are:
– Mobility
– Heterogeneous QoS
– Scalability
Also many interesting research issues in the “seams”
– Integration
– Transition
Cornell Workshop 6 Sept 2002– 21