Title: Mobility Reference Model and Waveform Networking
1- Mobility Reference Model and Waveform Networking
- for Transformational Wireless Tactical Networks
By Ralph Martinez, PhD Chief Scientist BAE
SYSTEMS, CNIR Communications Information
Systems Reston, VA 20190 Ralph.martinez_at_baesystems
.com 16 June 2005
2Topics
- Transformation towards Network Centric Operations
Warfare (NCOW) - Current performance requirements for NCOW
wireless tactical networks, (Joint Tactical Radio
System) JTRS Clusters - Applying the ISO Reference Model to wireless
tactical networks will not meet the performance
requirements - Mobility Reference Model (MRM) for wireless
tactical networks - Need to change our design methodology paradigm
- Summary
- Discussion
3Transformation Towards Network Centric Operations
Warfare (NCOW) Our Workspace Systems of Systems
4Objective GoalInteroperability of GIG-BE and
Systems of Systems
- Satellite Network Segment
- Airborne Network Segment
- UAV Network Segment
- Ground Network Segment
- Maritime Network Segment
- Unmanned Ground Network Sensors
5CIS Business Core CompetenciesReston, VA
- CIS Systems Architecture Design Development
- Virtual Engineering thru Modeling and Simulation
- CIS Systems Integration Engineering of Large
Scale Systems of Systems - Requirements analysis/development and Operational
understanding/insight - CIS Advanced Networking, Network Management,
Security, Mobility, and Network Services - CIS Systems Program Management
6CNIRs Integrated Modeling SimulationVisualizat
ion and Analysis (MSVA)
Utilizes an integrated modeling, simulation, and
3D visualization environment that combines
detailed analytical communications simulation
capability with an operational simulation
capability
7Current performance requirements for NCOW
wireless tactical networks(Joint Tactical Radio
System) JTRS Clusters
- Functional Description Documents (FDD) for USAF
Airborne WNW Network (AMF JTRS),
Capabilities-based Requirements (per AF Memo 9
Sept 03, S. Goldstein) for the following - Small Tactical Aircraft Support Performance
Requirements - Number of platforms (2 to 200)
- Maximum Range (300 miles)
- Network Join Time lt 5 s
- Low latency lt2ms _at_100nm, 6ms _at_ 200nm, 30ms _at_
300nm - Total Network Throughput 10Mb/s
- Individual user throughput 2Mb/s _at_100nm
- Single platform rate 2Mb/s_at_100nm, 500kb/s_at_200nm,
220kb/s_at_300nm - Able to handle A-A and A-weapon communications
(lt4800knots) - Full duplex (simultaneous Tx and Rx)
- JTRS Wideband Networking Waveform (WNW) applies
to Cluster 1 and AMF - Soldier Radio Waveform (SRW) applies to Cluster 5
8Current DoD GIG QoS/CoS Working Group -
End-to-End Model for IA/QoS Latency
FIXED
TACTICAL
WAN
Wireless Tactical Network
End-to-End GIG
- The solution must apply to all elements of the
GIG (post / camp / station, WAN, tactical /
deployed) - Standards-based
- Easily implemented and managed
- Secure
- Minimize complexity
- Scalable, Adaptable and Dynamic
- Multiple network domains
- Each application session may require different
QoS or CoS metrics, based on that applications
end-to-end connectivity - Fixed-to-fixed
- Fixed-to-tactical
- Tactical-to-tactical
9HAIPE Messaging Over Black Network Using WNW
Protocol Stack Increases Latency
100.1.4.1
100.1.1.1
100.1.1.2
100.1.4.2
Red IP (Secret)
Red IP (Secret)
100.1.3.1
100.1.2.1
HAIPE
HAIPE
CSS
CSS
200.1.1.1
200.1.4.1
Black IP
Black IP
200.1.3.1
200.1.2.1
Architecture adds 60-107 bytes of overhead per IP
packet
This IP to subnet interface is still under
consideration
10Low Latency Throughput in Multiple Network
Domains with QoS and Information Assurance
Platform LAN
GIG-BE
JAN-TE Network
NM
Applications
Applications
Applications
Applications
Application
Application
NM
IP Routing
NM
IP Routing
IP Routing
Apps
Transport
Transport
Transport
Transport
Transport
Transport
Transport
Transport
Transport
Black IP
Black IP
Black IP
IP
Black IP
IP
Red IP
Red IP
Red IP
JAN-TE Subnet
JAN-TE JAN-TE Subnet Subnet
JAN-TE Subnet
IEEE 802.2
JAN-TE Subnet
802.2
IEEE 802.2
IEEE 802.2
IEEE 802.2
SiS
IEEE 802.3
IEEE 802.3
IEEE 802.3
IEEE 802.3
SiS
SiS
802.3
SiS SiS
Platform LAN
JAN-TE SiS
JAN-TE SiS
JAN-TE SiS
Platform LAN
Black Network
HAIPEized Message
COTS based Heterogeneous Networking Core
11Current JTRS communications use gateways within
network segments
12GIG GIG-BE Touches JTRS Mobility Networks
13Assertion Applying the ISO Reference Model to
wireless tactical networks will not meet the
performance requirements
- How did we get to this situation?
- Why the OSI Reference Model was developed in 1980
- System, network, and telecommunications Reference
Model since 1980 - Why the current OSI Reference Model will not work
for wireless tactical networks - TCP/IP performance shortcomings
- IEEE 802.11b performance
- JTRS WNW protocol stack is overhead heavy
- Software Communications Architecture (SCA) is the
core framework in the JTRS radio node, its
performance is largely unknown
14How Did We Get Into This Situation?
- Open Systems Interconnection (OSI) Reference
Model developed in the era of point-to-point
telecommunications systems - 7 Layer OSI Reference Model originally developed
by the ISO in 1980-1982 and adopted by the ITU in
1983 X.200 Recommendations - OSI Reference Model has guided the development
of telecommunications and networking systems for
the last 25 years - Defined generic layered functionality in order
to allow products from different vendors to
interoperate and to allow developers a common set
of layer interfaces - Adaptations to internetworking, QoS, network
management, security services, and applications - No consideration for node mobility
15Open Systems Interconnection (OSI) Networking
Environment Circa 1980
16Other Reference Models - DoD and ATM Reference
Models
17Middleware Protocol Reference Model - OMG
E-Mail
DBMS
WWW
Application Users
Middleware Protocols
CORBA Middleware Protocols
CORBA Security Services
TCP/IP
Transport Network Protocols
Any Network
LANs, WANs, MANs, Wireless, 100/10 BaseT, GigE,
802.11/xx, Satellite, Photonics, FSO
18OSI, DoD, and SARM Reference Models
19Why the OSI Reference Will Not Work for Mobility
Architectures and Networks
- Replication of functionality (error checking,
retransmissions, security) - No concept of mobility and link availability in
RF networks lower than wireline networks - RF environmental propagation and co-site
interference is significant, RF channel is
unreliable - Performance limitations for QoS and IA for
Real-Time Targeting over 4-7 protocol layers - No provision for cross-layer operations for QoS,
network aware applications, or spectrum awareness - TCP/IP increased functionality and support
protocols solve after-thought problems - JTRS Wideband Networking Waveform (WNW) and
protocol stack are too heavy for mobility
networks.
20IP and TCP Overhead(DARPA P. Marshall)
TX receives ACK msg and sends its own ACK msg
TX sends close connection message
TX receives ACK message
TX receives msg and sends ACK
TX sends msg requesting connection
Data Transfer
ACK
RX closes connection and sends msg
RX receives ACK msg
RX receives ACK msg
RX returns ACK message
RX returns message with ACK
Establishing TCP Connection
Closing TCP Connection
Payload 80 Bits Total Sent 2,272
Bits Transmissions 7 Effective 3.5
21802.11b Overhead (DARPA P. Marshall)
IP Header (no options)
Bit 0
63
127
159
447
IP
DATA
MAC
PHY
With No RTS/CTS (Short Header) Payload 80
Bits TCP Used 2,272 Bits 802.11 Sent 6,640
Bits Effective 1.2 Transmissions 14
With RTS/CTS Payload 80 Bits TCP Used 2,272
Bits 802.11 Sent 12,480 Bits
Effective 0.65 Transmissions 28
22 23Software Communications Architecture (SCA) with
Red/Black separation is a performance unknown in
JTRS nodes
Ref JTRS Cluster I Software Communications
Architecture, 2002
24Need to Research New JTRS System and Network
Architectures
- New architectures means redefining the
architecture of the radio - Need to define a new design paradigm, called
Waveform Networking, that addresses the
deficiencies with current architectures - To achieve performance and functionality, a new
component-based Mobility Reference Model is
developed - To achieve future cognitive and adaptive JTRS
architectures the radio node functionality needs
to be redefined - Current JTRS System, Network, and Radio
Architectures cannot meet the current
requirements
25Networks of Gateways in System Architecture
Level 1 and 2 networks Of gateways
provide Interoperability with legacy Systems
Clusters
Cluster radios Legacy systems
26JTRS Routing Architectures are changing
- JTRS Clusters are heading to new architectures,
but the radio node functionality is not robust
for cognitive functions - Describes different JTRS network configurations
- Addresses interface issues
- Architectures
- Stub Network
- Transit Network
- Multiple Gateway Transit Network
- Internal Routing Architecture
- Dual homed to network domains
- Need new functionality in the JTRS Radio
27Traditional Software Radio Architecture
- Superheterodyne design - still popular and widely
used today since 1930s. - Comprised of 3 stages Radio Frequency stage,
Immediate frequency (IF) stage, and Baseband
stage. - The diagram shows a 2-stage analog
superheterodyne radio
28Opticalizing the SDR Pipeline Control It
Software Defined Radio Architecture
SDR Baseline Architecture
Software
Data Network I/F
Hardware
Defined
Defined
subsystem
Voice Network I/F
subsystem
(IF Baseband
(RF Front End)
Multi-antenna arrays,
Processing)
Directional antennas,
Beam steering,
Smart antenna, etc.
Integrated Opto-RF SDR Architecture
Software Defined
Hardware Defined
Optical
subsystem
subsystem
Opto-RF
Switching
Processing
Software Defined
Hardware Defined
Interface
(ADC/DAC, Up/
subsystem
subsystem
(Forwarding
Down
Plane)
Conversion)
Software Defined
Hardware Defined
subsystem
subsystem
Management Control Plane
29Component-based SDR Architecture for JTRS
Generation-II Radio Nodes
Management
Management
Control Plane
Control Plane
Control Plane
Control Plane
Management Control Plane
Management Control Plane
Switching
Switching
Matrix
Matrix
Antenna
Antenna
Legend
Legend
Control Connection
Control Connection
Free Space Optics
Free Space Optics
Data Connection
Data Connection
Software interface
Software interface
30Switch-Centric Component-based ArchitectureInterf
aces to SCA
31Improvements Using G-II Radio Nodes
32Key Elements of the New JTRS Architecture CIJA
Generation II (G-II) Radio Nodes
- Configurable Interoperable JTRS Architectures
(CIJA) - Using JTRS G-II radio nodes with new
functionality - Mobility Reference Model (MRM) Component-based
implementation of radio architectures that
instantiates objects into message threads based
on application message requirements - Integrated Management Plane (IMP) Provides the
out of band management and control plane for the
CIJA and G-II nodes - G-II radio node architecture is optical
switch-based to allow connectivity to software
and hardware components in the CIJA - New suite of routing protocols that include base
station and mobility architecture and wireless
OSPF extensions - Spectrum-aware RF functions and Network-aware
applications both communication through the IMP - Opticalized components in the component-based
architectures
33Key Feature is the Mobility Reference Model (MRM)
SDR Components Implemented in Blades
Optical Switching Router
34Example of MRM thread in CIJA
Need a management control plane to coordinate
the components switch
35Integrated Management Plane (IMP) in theMRM for
CIJA
36Network Aware Applications
- Applications communicate to the Integrated
Management Plane (IMP) and receive knowledge of
the network condition - Application requests the bandwidth/spectrum and
message delivery requirements to the IMP - The MRM components are a part of the network and
hence they should have the ability to adjust
different parameters to optimize network
performance - The awareness mechanism can be used to optimize
network and device performance simultaneously - The complexity of the problem increases with the
number of radio interfaces and devices in the
network - The performance of the device depends to a large
extent on the configuration of the processing
chains - An adaptation mechanism is able to detect when
the chain is underperforming and tune necessary
parameters
37Spectrum-Aware Functions
- To support the reconfiguration of the dynamic
chain, the cognitive/adaptive management plane
must - Be aware of the available resources and configure
the switch to construct the chain - Plan a path that maintains SLA specified QoS
- Generate and use situational awareness
information from the RF spectrum - Estimate and monitor the performance of the RF
spectrum - Adapt by switching in a compensation element
along the path if need - Adapt by tuning various components to maximize
the performance
38Adaptation Process in the G-II Radio Nodes
BER, Delay, Impairments
Information Base
Gather Raw Data
Link Specifics
Situation Assessment
Trigger Search
- Link State Information
- Q parameter
- BER
- Channel Attenuation
- Channel Impairments
- Load
- Path Information
- End-to-End Delay
Link Specifics, Resource Information
Decision
- Statistical analysis of
- raw data
- Traffic Model
- Determine whether its
- necessary to readjust
- parameters
- Action(s) to be taken
- Hardware
- Path
- Feedback to specific
- functional blocks
39Example of Object Instantiation for Specific
Message Threads
IMP
Network
Aware
Adaptable
Apps
Protocols
Waveforms
Adaptive
UDP
Protocols
Cognitive
Smart
Spectrum
Antenna
Aware
Waveforms
Spectrum
WNW
Legacy Waveforms
802.xx
3G Waveforms
40New Design Paradigm Waveform Networking
- Waveform Networking combines the previously
separate disciplines of network protocol
engineering and RF and spectrum engineering
Network Protocol Engineering
RF Spectrum Engineering
- Data Communications
- TCP/IP Networks
- Internetworking
- Network Management
- QoS
- Traffic Engineering
- Congestion Control
- Network Security
-
- Communication Theory
- Encoding/Modulation
- ADC/DAC
- LPI/LPD
- Up/Down Frequency Conv
- Medium Access Control
- Time Division Multiplexing
- Power Amplifiers
Waveform Networking
- Smart Antennas
- Cognitive Radios
- Adaptive Mobility Protocols
- Network Aware Applications
- Spectrum Aware
- Mobility Reference Model
41Summary Drivers for Mobility Reference Model
- Performance Drivers
- Improve End-to-End Performance and
Interoperability with Legacy Systems - Implementation Flexibility
- Technology Drivers
- Component-based Processes established for each
application thread - Implement new SDR architectures and JTRS system
architectures - Business Case Drivers
- Open standards and interoperable with OSI
Reference Model networks - Implementation independence
- NCOIC, OMG, DMTF compliance for NCOW
- Interoperability Drivers
- Compatible with SCA and Interoperable with
TCP/IP (IPv6) - Must interoperate with the GIG interface and to
DoD legacy systems - Mobility Reference Model across different
mobility domains
42Summary How do we achieve Waveform Networking?
- Realization that we are applying
telecommunications and networking concepts that
are 25 years old - Performance is a key driver to multimedia
communications over limited RF spectrum - The 3G cellular industry has been successful in
departing from the OSI Reference Model - Train a new breed of engineer in Waveform
Networking - SWaPize the SDR processing functions and pipeline
- University curricula need to respond to the
Waveform Networking needs in industry