150 likes | 286 Vues
Join Kenneth Flynn, President of DCS, in an informative workshop focused on mobile ad hoc networking (MANET) software development. Explore the requirements, use cases, and tools for measuring and analyzing MANET performance. Discover how various applications—such as voice, video, and data transfer—can benefit from MANET-aware technologies. Delve into challenges in scripting and collaboration, alongside strategies to synchronize applications within emulated environments. This session provides a comprehensive look at the tools and methodologies necessary for successful MANET application performance analysis.
E N D
NRL Emulation WorkshopIntroduction Kenneth Flynn President, DCS
NRL Questions Requirements and Use Cases Tools Limitations/Trouble Spots Collaboration?
Who is DCS? • Custom software development firm specializing in “MANET software”: • Measure the performance of MANETs at the application layer • Measure the performance of applications on MANETs • Develop applications that run on MANETs • We live at the MANET-aware application layer
Use Cases • T-AIDR (Supporting CenGen) • 100-400 many-to-many node network • Various “surrogate” tactical applications • SA, Chat, File Transfer, Voice, Video • For our sanity (read cost), we need the same tools in: • Simulation • Emulation • Field
Tools • Emulated Network Stack (EMANE) • Surrogate Tactical Applications • Attila Testbed Control Tools (DCS) • Script execution for surrogate applications • Script coordination • Real-time monitoring and troubleshooting • Minotaur Analysis (DCS) • Data reduction and analysis
Trouble Spots Scripting
What We Did • Given a set of “scripts”, we can reliably: • Load applications • Execute the scripts • Collect the data • Reduce the data • Analyze the results and gain insight into network performance
But… Config Files! Every time I got a phone call from NJ asking for support, my family shouted:
What’s Wrong? • Need to synchronize applications as well as MANET emulation environment • Mobility • Application configurations • SA • Chat • Video • Voice • Etc. • Scripts
What’s Wrong? • Of course, the trouble is defining what a script actually is… • Mobility? • Application Traffic? • Configuration parameters for an application? • Commands sent to an application?
What is a Script? sendMessage( time, source, destination message_text, priority); sendMessage( time, source, destination message_text, priority); sendMessage( time, source, destination message_text, priority); Chats once per second
What is a Script? • We struggle with communicating about scripts • Even at powerpoint 50000’ level • For example: • “Chats once per second” • Precision in language is NOT enough • There’s just information not useful to the high level scenario designer that we need • Message content, reliability configuration, etc.
Applications Have Issues • Many possible scripts are invalid, but only because of application limitations • Cannot send voice more than once per eight seconds • Arbitrary limitation of our current tool (we’re working on it ) • Making sure this was not violated was several hours of work that had to be done for EACH SCENARIO
Collaboration • A layered open standard for scripts • Layering allows • Levels of detail • Mobility (scalable) • Individual Application Configuration • Individual Application Control • Serves different users/editors at different times • Warfighters • Scenario Designers • Application Integrators • Need to define these too….
Collaboration • I think this will be difficult • Number of stakeholders • Forest-tree issues: desire for different levels of detail • But with this, we can • Visualize and create scripts in different environments and tools for validation • Execute and compare in a variety of ways: • Simulation, Emulation, Field