An End-to-End Modeling and Simulation Testbed (EMAST) to Support Detailed Quantitative Evaluations of GIG Transport Services 14 June 2005 Gary Comparetto (703) 983-6571 garycomp@mitre.org
Objective: Evaluate Various Aspects of End-to-End Communications via M&S 2 TC Satellites TCS MILSATCOM Access Network DoD Teleport GIG-BE WIN-T Strategic Networks SATCOM SATCOM (e.g., KaSat) & GBS Upper Echelon (Tier 2) Network C2V GPS WIN-T External Interfaces/ Interoperability DISN WIN-T POP Lower Echelon (Tier 1) Network Member of both Tier 1 and 2 networks WIN-T POP CONUS Soldier Network network links ENW network links Legacy network links Networked Data Link FCS External networks links UGS Network Lower Echelon (Tier 1) Network Legacy Networks E.g., EPLRS, SINCGARS,... Sensor Data Link Network EO/IR EO/IR Navy (details to be inserted) Air Force (details to be inserted) Army Tactical Networks (FCS, WIN-T, JTRS, JTRS, TCS) M&S: Modeling and Simulation
Technical Approach 3 Extend the Modeling and Simulation Environment (MSE) developed by MITRE over the past several years in support of the JTRS and DARPA FCS-C programs Single radio device type in a MANET wireless environment Representative operational scenarios Accounts for terrain-induced path attenuation Supports reproducibility and re-use of models and scenarios Develop an End-to-End M&S Testbed (EMAST) having the same capabilities as the MSE plus ability to support: Multiple radio device types (e.g., & ) Multiple networks (e.g., JTRS & WIN-T) Heterogeneous networks (i.e., wired and wireless)
What Is An M&S Environment? 4 For our purposes.. M&S Environment = simulation kernel + stuff The stuff includes middleware to support such things as: Scenario generation File manipulation and format translation Enhanced data collection External (a priori) processing It may also include other COTS tools In our case, the simulation kernel is OPNET and the stuff includes all of the above
M&S Environment (MSE) Overview (Being used to support JTRS ) 5 Key: Developed by MITRE Provided to Contractor Path attenuation data for each node pair as fcn(time), accounting for both terrain and foliage Contractor-Developed Comms Technology Provided to Gov t Pathloss.c <scenarioname>_path_loss.gdf INTEGRATE Node Laydown, Mobility, Traffic Profile Binary File COMTEST SDF, PDEF, & MDEF Files SDF Parser <scenarioname>.devices <scenarioname>.ef <scenarioname>.em.c <scenarioname>.thproc.gdf <scenarioname>.thsched.gdf <scenarioname>.trj files OPNET I/F Global Mgr Thread Mgr OE CE-AL OpFac Performance Data <scenarioname>_seed_xxx_oe_out.txt <scenarioname>_seed_xxx_tm_out.txt <scenarioname>_seed_xxx_summary_out.txt
M&S Environment (MSE) Overview (Being used to support JTRS ) 6 Key: Developed by MITRE Provided to Contractor Path attenuation data for each node pair as fcn(time), accounting for both terrain and foliage Contractor-Developed Comms Technology Provided to Gov t Pathloss.c <scenarioname>_path_loss.gdf INTEGRATE Node Laydown, Mobility, Traffic Profile Binary File COMTEST SDF, PDEF, & MDEF Files SDF Parser <scenarioname>.devices <scenarioname>.ef <scenarioname>.em.c <scenarioname>.thproc.gdf <scenarioname>.thsched.gdf <scenarioname>.trj files OPNET I/F Global Mgr Thread Mgr OE CE-AL OpFac Performance Data <scenarioname>_seed_xxx_oe_out.txt <scenarioname>_seed_xxx_tm_out.txt <scenarioname>_seed_xxx_summary_out.txt
EMAST Phase I 7 Integrated models developed by MITRE/FTMO in support of CERDEC Utilizing scenarios developed in support of JTRS and FCS-C programs Integration Models Repository Ka-SAT Surrogate INET Cloud Fixed P-to-P Integration Scenarios Repository Engine OPNET FDD Grids Joint_JHU Caspian Sea Balkan Boise SDF, PDEF, MDF, TPD files Pathloss.c SDF Parser I/F Global Mgr Thread Mgr OE CE-AL OpFac Extended capabilities of the MSE Performance Results
EMAST Capabilities 8 Phase I (Sept 04) Phase II (Sept 05) 10 to ~100 nodes Heterogeneous (wired & wireless) networks Multiple radios devices Operational scenarios Static and mobile groundbased, air-based, and satellite-based nodes OPNET-based version 9.1 Multicast traffic via flooding Transport TCP or UDP Stryker Force scenario >100 nodes OPNET-based version 10.5 Multicast traffic via PIM-SM Integrate PEP/SCPS models Support QoS (limited DiffServ) Support HAIPE (Spec vs2) Additional scenarios and analyses
What Can We Do With EMAST? 9 Investigate the performance capabilities and/or impact of any comms network technology that can be modeled in OPNET Measures of performance include E/E delay Throughput Completion rate All on a packet, IER or Thread basis Example investigations Modulation/coding and antenna design alternatives TDMA vs CSMA MAC layer design alternatives Unicast/multicast routing protocol design alternatives Impact of different transport mechanisms (TCP, UDP, SCPS, etc. and combinations) Impact of alternative QoS mechanisms or HAIPE
EMAST Proof-of-Concept (POC) Study 10 Purpose To validate the functionality of the EMAST Phase I capability To demonstrate the use of the EMAST Phase I capability within the context of a realistic application Leverage END-2-END (E2E) INTEROPERABILITY ANALYSIS report (DRAFT), June 2004 in defining study scenario Focus on the transport service
Key GiG Systems Involved in Stryker Brigade Thread* 11 5 Home Station Operational Cell (HSOC) 4 Teleport WIN-T 6 ` 3 Message Relay Global Information Grid Bandwidth Expansion (GIG -BE)/DISN Infrastructure Stryker Brigade C2V 7 Joint Task Force (JTF) Global Command and Control System (GCCS) ` Net-Centric Enterprise Services (NCES) 1 2 Discovery/IA Mapping/ Imagery 8 Joint Tactical Radio System (JTRS) Stryker Command Vehicle (CV) * Described in END-2-END (E2E) INTEROPERABILITY ANALYSIS report (DRAFT), June 2004 9 `
Key GiG Systems Involved in Stryker Brigade Fixed CONUS Thread* Wired Wired Wired Wired Fixed KaSAT 5 KaSAT Ka-Sat 12 Home Station Operational Cell (HSOC) 4 Teleport WIN-T 6 ` 3 Message Relay Global Information Grid Bandwidth Expansion (GIG -BE)/DISN Infrastructure Stryker Brigade C2V 7 Joint Task Force (JTF) Global Command and Control System (GCCS) ` Net-Centric Enterprise Services (NCES) 1 2 Discovery/IA Mapping/ Imagery 8 Joint Tactical Radio System (JTRS) Stryker Command Vehicle (CV) * Described in END-2-END (E2E) INTEROPERABILITY ANALYSIS report (DRAFT), June 2004 9 `
EMAST Phase I Stryker Force Scenario 13 Modify Boise scenario developed in support of FCS-C program 21 nodes Mobility Terrain-induced LOS blockage Add Washington DC CONUS component and internet cloud Unicast & Multicast traffic Data, voice, video, and multimedia traffic COMTEST OPNET
EMAST Phase I Stryker Force Scenario (Concluded) 14 Boise, Idaho Theatre Theatre_GEP GEP KaSAT/ /KaSAT Traffic Flow _UAV Rendezvous Point _UAV SBGD_4 SCV_6 / SCV_1 SCV_2 SCV_9 SCV_4 SBGD_5 SBGD_2 / SBGD_1 SBGD_7 SBGD_3 SBGD_6 Washington, D.C. SCV_8 / SCV_3 SCV_5 SCV_10 SCV_7 Internet Cloud CONUS_Gateway Fixed/KaSAT CONUS_GEP Leverage FCS-C Demo 3 Boise Scenario
Proof of Concept Study Thread* SATCOM 15 Wired assets 0 (0) Alert_SBGD (D) 7 (0) HR_map_req_CONUS (D) Wireless assets CONUS_GEP SBGD_6 8 (0) HR_map_data_SBGD (D) 2 (60) Weather_req (D) 1 (0) Alert (D) 4 (120) Sensor_req (D) 1 (0) Alert (D) 1 (0) Alert (D) 5 (0) Sensor_data (D) 3 (0) Weather_data (D) 6 (120) HR_map_req_SGBD (D) SCV_3 SCV_2 9 (0) HR_map_data_SCV_1 (D) SCV_1 * Notional extension of Mobilization Alert described in END-2-END (E2E) INTEROPERABILITY ANALYSIS report (DRAFT), June 2004 thread_done Seq#10 SCV: Stryker Command Vehicle SBGD: Stryker Brigade HQ req IERs are 8kbytes; all others are 100 kbytes
EMAST Phase I Stryker Force Analysis (% Completion Rate, E/E Delay, Throughput Ratio) 16 % Completion Rate 90 80 70 60 50 40 30 20 10 0 0 50 100 150 200 250 300 350 400 450 Total Offered Traffic Load - Expanded (kbps) E/E Delay (s) 35 30 25 20 15 10 5 0 0.00 50.00 100.00 150.00 200.00 250.00 300.00 350.00 400.00 450.00 Total Offered Traffic Load - Expanded (kbps) UDP TCP E/E Delay UDP E/E Delay TCP 0.80 0.75 Throughput Ratio 0.70 0.65 0.60 0.55 0.50 0.00 50.00 100.00 150.00 200.00 250.00 300.00 350.00 400.00 450.00 Total Offered Traffic Load - Expanded (kbps)
EMAST Status 17 EMAST Phase I completed 30 Sept 04 Proof-of-Concept Analysis completed 30 Nov 04 On schedule to complete Phase II by 30 Sept 05 >100 nodes OPNET-based version 10.5 Multicast traffic via PIM-SM Integrate PEP/SCPS models Support QoS (limited DiffServ) Support HAIPE (Spec vs2) Additional scenarios and analyses