NASA Space Internet Workshop

TASC

End-to-End Network Modeling Using Terrestrial, Wireless and Satellite Components

Ray Williams - TASC

[email protected]

7 June 2004

NASA Space Internet Workshop

TASC

End-To-End Architecture/Model Methodology

Data Discovery, Storage, Manipulation and Modeling Develop Complex End-to-End Architectures in Minutes Model and Analyze the Complete Environment

– Terrestrial– Wireless– Satellite

Analysis and Visualization To Accurately Depict Relationships and Performance

– Satellite Tool Kit – Orbital Dynamics with Superior Interactivity– Integrated C4ISR Views with Popkin System Architect

Architecture, Requirements and Schedule

– GIS Tools/Methods and Associated Layers Day/Night Shading DTED and VMAP Terrain Data

– Discrete Event Network Modeling Tools Network Simulator (ns-2) Opnet (IT Guru, Modeler)

TASC

Data Discovery, Storage, Correlation/Transformation

Terrestrial– Topology and Individual Host Data Obtained from nMap, nTop,

Firewalk, Traceroute, tEthereal traces, Circuit Databases, …

Wireless– RF Point-to-Point, Area Coverage Obtained from CSPT, Others– RF Survey Data From Kismet, GPSMap, GPSD, …– Laser Through NWP-ARPS Extensions

Satellite– Orbital Parameters Taken from Two-Line-Element (TLEs), STK

Import, …

Requirements– Import of Customer Requirements Documents, DOORS,

RequisitePro, AP233

TASC

Terrestrial

Based on TCP/IP V4/6 LAN and WAN Links Object Based-Extendable

TASC

Wireless

Point-to-Point Line-of-Sight RF and Laser Communications Links Object-Based Extendable

TASC

Satellite

Anything You Can Do In STK, I Can Import By Using STK We Can Focus On The Communications Interface Is Object-Based Extendable

TASC

STK with it's Connect and Coverage Modules is Invaluable for Incorporating Satellite Objects into Network Scenarios

– Architecture Components Exported to STK via Connect– STK is Commanded to Compute Coverage Times and

Orbital Positions– STK Returns Values That Are Stored in a File That is

Parsed Using Perl And Those Events Are Inserted into

Time-Based Scenario File for Execution

STK As A Compute Engine

TASC

Our Automated Process

Network Simulator

Opnet

End-to-EndModel

Framework

IntegratedStatisticalAnalysis

Satellite Tool Kit

Cellular

802.11

IP Hosts

Routes

TASC

Alternate Data Uses

TASC

Model Inter-Relationships

Physical Layer Simulation Engines1. Spacecraft Modeling (Matlab, SystemView, other COTS, proprietary)2. Orbital & Geolocation Modeling (STK, other COTS, proprietary)3. Terminal Modeling (Matlab, SystemView, other COTS, proprietary)4. RF Spectrum Modeling (Matlab, SystemView, other COTS, proprietary)5. RF and Optical Meteorological/Propagation Modeling

(various COTS and proprietary)

Network Simulation Engine

Seven-LayerOSI Model

ApplicationPresentationSessionTransportNetworkData LinkPhysical

User Interface

RF/Optical Link Budget

Physical Layer Simulation Engines1. Spacecraft Modeling (Matlab, SystemView, other COTS, proprietary)2. Orbital & Geolocation Modeling (STK, other COTS, proprietary)3. Terminal Modeling (Matlab, SystemView, other COTS, proprietary)4. RF Spectrum Modeling (Matlab, SystemView, other COTS, proprietary)5. RF and Optical Meteorological/Propagation Modeling

(various COTS and proprietary)

Network Simulation EngineNetwork Simulation Engine






User InterfaceUser Interface

RF/Optical Link BudgetRF/Optical Link Budget

TASC

Issues With the Airborne/Space Link

Atmospheric Effects

Terrestrial Blockage &Propagation Effects

GEO 1 GEO 2

Fixed Terminal Mobile TerminalsTerrestrial Interference

Desired

Desired

Undesired

Space Weather &Ionospheric Effects

DesiredNGSO

Atmospheric Effects

Terrestrial Blockage &Propagation Effects

GEO 1 GEO 2

Fixed Terminal Mobile TerminalsTerrestrial Interference

Desired

Desired

Undesired

Space Weather &Ionospheric Effects

DesiredNGSO

TASC

Variability in Wireless/Space Communications

Figure 1 LEO-TRDSS RF Link Signal Strength

TASC

Weather Models

Simulation Modeling “Engines”1. Spacecraft2. Orbital & Geolocation 5. Meteorological & Propagation3. Ground Station 4. RF Spectrum5. Weather Interference(3 Distinct Thunderstorms ~12 Miles in Height)

TASC

Integrated Model Output1. Start of Network 2. Iridium 13 in Sight - Seattle to Washington Traffic

Re-Routing

3. Iridium 13 - Out of Sight San Diego to Norfolk Traffic Routed Over Ground

4. No Satellite links up

TASC

Acknowledgements Briefing is Based on the Paper Presented at the 2004

Society of Optical Engineers Conference (SPIE.org) at Orlando, FLA “End-to-End Network Models Encompassing Satellite, Terrestrial and Wireless Components”

Majority of Screenshots Acquired From The TASC Rapid Architecture Development and Evaluation System (TRADES)

TASC