GenetScope - NetSim 2 Software User`s Manual
Contents
1. Figure 34 Pane showing the complete Location database with functionality of adding removing updating any location 36 2 5 Defining Simulation Time Duration and Propagation model Once the Fixed stations Mobile stations master Channel list Locations database are set the scenario generation is almost complete The only thing remaining now is to specify the time and duration of simulation This can be specified from the Setup tab shown below The simulation start time is specified in 24 hour notation The duration is determined by specifying the End time of the simulation in 24 hour notation The GUI identifies the operational Sun Spot Number SSN based on the year month day The identified SSN is then used to gather ionospheric propagation data The user can either choose ICEPAC or VOACAP In case of no selection ICEPAC is chosen as default The analyst can enter any descriptive text concerning this simulation configuration T GENETSCOPE NetSim2 4 i Start Experimental Frame Run Simulate System Configuration Fixed Station Mobiles Frequencies Location SetUp simulation Start Time GMT 16 00 00 Sun Spot Number 33 5 simulation End Time GMT 1 00 00 Propagation Model ICEPAC Simulation Start Date 2 VOACAP 0012006 JUa Comments Description Enter descriptive text to pravide infarmatian abaut the scenario E af Write Configuration File Figure 35 Simu2. e mS cu J co Oo Lo pta pasta PSA PRESI PAST PASTA Pea AAA Soon OOO c ojmjjijoijoijoi pea PEA pes cm ot on Daja pta t Min eic I oo c DJ mm 2 DJ a oy oo io oo mo Oo I2 r2 1 1 E 455684 Jis 33 6 MsgLog base223 0 3 10 06 txt This log provides information about any messages that were attempted They are reported in this log if the station fails to deliver the message after repeated attempts too However it doesn t show the retries Only the final outcome is reported with the reason of failure If the message is delivere d then it is reported too Check the first message at 42 12 793 in 46 the figure below mirroring the link established thru AleLog and LinkingLog Close ChannelLog ALELog LinkingLog MobilesLog Log MessageLog LOALog MsgiD Dest sm Pr Lente Arrived _ Time Req Established DoneAt lfFailed Re 150000 1 150 yo 60 00 26 00 098 00 26 00 098 00 26 13 289 D0 27 13 486 VOICE suoni su mo BO 00 46 00 099 00 46 00 099 00 46 13 289 00 47 13 487 VOICE 150002 H J150 250 BB 01 06 00 101 01 06 00 101 01 06 13 289 01 07 19 487 DATA Some of the reasons if the message fails to deliver is absence of channel after re peated tries This is reported as NO CHANNEL In the above snapshot all the messages are reported delivered
3. Es WENT OF gt Qos ky DEFENSE INFORMATION SYSTEMS AGENCY ji A z JOINT INTEROPERABILITY TEST COMMAND sla a FORT HUACHUCA ARIZONA ON d GenetScope NETSIM 2 GenetScope NetSim 2 Software User s Manual July 2006 DRAFT Version 1 1 GenetScope NetSim 2 Software User s Manual July 2006 DRAFT Version 1 1 Prepared for Engineering Analysis Design and Development EADD Engineering and Sustainment Support Task HF Global Communications Systems HFGCS United States Air Force Tinker Air Force Base Prepared by Arizona Center for Integrated Modeling and Simulation ACIMS Department of Electrical and Computer Engineering University of Arizona Prepared Under the Direction of Joint Interoperability Test Command Fort Huachuca Arizona EXECUTIVE SUMMARY The NetSim 2 is an object oriented discrete event system modeling and simulation M amp S environment to support simulation and analysis of voice and data communication scenarios for High Frequency Global Communication Systems HFGCS The application runs on Java based platforms including both Windows and Linux and allows a user to model a wide range of HFGCS communications and connectivity operations through its own Graphic User Interfaces GUI NetSim 2 has been developed not only to improve the implementation of original Automatic Link Establishment ALE protocol in its predecessor NetSim 1 but to provide the advanced M amp S
4. This is the ALE radio log file and it shows which ALE radios are in which state during the course of simulation run The columns provide information in this sequence StationID Level AtTime OnChannel toDestination Status A typical snapshot of this log file is shown below JGR EI SCORE Mersim Experimental Frame Logs Analysis Performance Analysis Channel Log ALELog Linking Log MobilesLog Log Message Log Station ID Level At Time On channel To Destination Status 1 WT W664 S34 taU canning 01 05 55 503 ICh 2 ta Scanning 01 06 00 201 che ta 1 Listening before Calling 01 06 02 400 ChB to CALLING 01 06 02 503 Ch B ta Listening ta Call 01 06 09 262 ch t0 150 LINKING Response delay sending Response 01 06 10 838 che to LINKING ACK delay sending ACK 01 06 12 416 Ch t0 150 LINKED 01 5 13 18 Ch B ta LINKED 01 06 13 389 ch to VOICE_DATA 01 5 1 3 388 Ch B t0 150 VOICE_DATA 01 07 19 388 Ch to VOICE DATA 01 07 19 388 Ch B to LINKED 01 07 18 391 ch to 150 VOICE_DATA 01 07 19 391 Ch B to 140 LINKED I01 07 25 615 Ich 2 ita Listening before Sounding ID1 07 27 815 ICh 2 TENTI 01 07 32 127 ch 2 ta Reading Snd SNR dB 15 389 Score 29 01 07 34 275 Ch 1 ta Scanning si 01 07 50 567 ch7 to D Scanning 01 07 50 956 Chir ta Scanning I m E As can be seen above station 150 calls on channel 6 to station 1 at 01 06 02 400 s It engages in linking pro
5. ALE Activity Active SITE HAW i 1 Latitude 5401 Longitude 22 386 WW hei CRO Er pur _ i Delete JOG ru Keflivak vi AED p Location Lookup Update a HIK f sl EENG Start at iiim Vite I rr _ _ _ _ _ _ _ _ __ _ _ r _ r_r_rr_______PP____ e i irs a PLA mu p SSL HRS Le Es Ep a a SS OT ba E Nu a H L n EN a P Ll Frat ea LE L Message Traffic Ale Levels Ale Parameters Scanlist Gnd infrastructure Mu an A E en e e ml rer eg ere a E rz Peoria dL kn n ES ce fae edie wee MCC Lun NES irse vj OFF uae dize seconds Msgs hr Type Precedence JNR or Bytes LES hej JTY n IE C Voice n ve ICZ i Pu ir anion a Data v IKF r 3 Voice 1 Aion Random C3 Data es Voice Figure 15 Showing the related info about a fixed station when Lookup is pressed 3 Modify stations data If some changes are to be made by a user the station data can be updated by clicking the update button The user can delete any station using a delete button Users can make stations and save information of stations using a add button 4 Station info tabbed pane This pane is composed of five tabs named Message Traffic Ale Levels Ale Parameters Scan List and Gnd InfraStructure e Message Traffic This tab allows for setting up the traffic stream param
6. GENETSCOPE Figure 4 shows the block architecture of the simulation model The right hand box is the system phenomenon that contains the Automatic Link Establishment ALE STANAG 5066 protocols used for establishing links and exchanging data messages between mobile stations and fixed stations The left hand side box is the experimental frame that generates various scenarios and parameters under study The scenarios and parameters are fed into the model and performance characteristics are obtained from it which are then visualized and analyzed in real time as per the extended MVC architecture described in Section 5 1 Response time of a system is defined as the time taken by the system to display significant effect caused by any update in the configuration parameters A methodology using intermediate XML processing to automate much of the process of componentizing legacy simulation code will be reported soon 10 Experimental Frame Automatic Link Establishers ALE Pass station channel SNR data Receive Update Pass Messages E Ground Stations Establish Link Transmit Messages Figure 4 GENETSCOPE simulation architecture for SCOPE command SCOPE Architecture implementation using enhanced Mode View Controller paradigm The Figure 5 below shows the simulation architecture using the concepts laid out in the paper With reference to Figure 4 the lonosphere model used in the architecture is ICEPAC data It is worth stressi
7. Various logs are displayed More details are provide in Section 3 Log Analysis tab shows 6 log files Channel log ALE Log Linking Log Models Log Message Log LQA Log The internal engine reads and parses the textual log files then shows in the table format Print button is disabled in this version 41 Performance analysis tab was developed to answer to the user s possible question There are tentative five questions in this version The conversion textual log file to XML log file has been processed in this version The answer is derived from the XML Log files If user clicks the question the chart will be popped up In this version only one question Give Channel occupancy list for hour x will be working 42 3 SIMULATION LOGS Once the simulation is termainated it displays the logs and performance results in two new tabs i e Logs Analysis and Performance Analysis tab The simulation results in generation of log files stored in the application s LOGS configFile folder as txt files All the logs can be exported to Microsoft Exel for better analysis Logs are tab delimited The log file names are automatedly time stamped in the same manner as the scenario configuration file where the numbers have their usual meaning If the configuration file is named base223 0 3 10 06 cfg the six log files are stored in Logs base223 0 3 10 06 folder and are displayed in the GUI in Logs Analysis tab as follows 1 AleLog
8. antenna HTO samples sample09 Fixed station antenna samples sample05 Fixed station antenna 4 Rosette ROS samples sample32 1 Fixed station po EM Dipole DIR X X Samples sample23 Mobile ie VTM X Samples sample10 Mobile F 7 Whip bab a MN DEFAULT SWWHIP VOA Probe si DEFAULT SWWHIP VOA 2 Mobile aircraft 10 Other X X jUseinpt Notes 1 Use LTO antenna until a better antenna can be found 2 Use Whip Antenna until a better antenna can be found Fixed station antennas should be selectable by any system Fixed stations should offer antennas 1 4 and 10 as selections 1 4 LIMITATIONS The NetSim 2 environment requires PC with a Pentium 4 or greater processor with at least 512 MB RAM Recommended RAM is about 1GB Depending on the details required in log files especially EventLog the minimum hard disk capacity required for an individual simulation run is between the ranges 20 1000MB GenetScope model limitations 1 The current model developed in Phase of the project is bounded by the functionality in the older Netsim version designed by Dr Johnson in C It has been translated and developed using the DEVS theory and implemented in Java No new ALE functionality has been added in the current version 12 2 All the stations in any scenario work on default AFALE scanlist However provisions to program different scanlist have been added into
9. in the architecture section the Experimental frame gives the user to set the general design parameters guiding any scenario The user can specify top level design parameters like Level in a fixed station No of fixed stations No of mobile stations No of messages transmitted per hour Duration of voice calls Sounding interval SNR threshold GENETSCOPE NetSim2 Jag o 0oocm Start Experimental Frame Performance Analysis B Make Hew Confi Make Hew Configuration nea To a new To a new configuration file file Configuration File aa To anew configuration file basewithAnt cfg h Fixed Stations h 4 Description 10 15 20 basewithAnt ctg This is a basic scenario to learn the operations and functions of GenetScope NETSIMZ The Mobile Stations ho cenario is CONUS based providing two aircraft 50 100 150 200 250 300 on routine flights Traffic is base on voice messages at selected intervals Linking Message transmission and LOA data can be reviewed and analyzed after termination E ardpad The user can review each of th Simulate Configuration 20 30 40 50 60 70 80 90 100 after termination ar usa MS Ward to reviey during operations E h 0 7 nin a a file is Simulate Conti iguration EE eo i 60 Load Update ConfigurBtion 10 20 30 40 50 60 70 80 90 100 View reve Los Show Existing Logs Ground Stations 90 100 150 200 250
10. number of C130 is two i _ e plane Type might result in loss of flight detail Enter Details information rau may have to enter the flight details again Adding new planes ih current loaded configuration if loading an old file will not result in losing any information Figure 22 Main Mobile Station selection pane Step 2 Aircraft Details Zi This step allows for specification of call signs to the types of aircrafts chosen in the previous step The mobile stations are identified by these call signs for all the configuration and simulation from this step onwards sequence Mobile gt Aircraft Details gt Flight Detail 1 The values of Call Sign Start Time and Flight Details need to be filled in for the selected aircraft type Ex Call Sign Enter any name for the mobile station identification Ex Sam Steve Bon otart Time Enter the take off time Ex 120 minutes after the simulation start time 2 Click the Flight Detail button to fill out the details of the selected aircraft 3 The Flight Detail dialog with the Call Sign name is popped up Flight Detail Flight Detail Flight Detail Flight Detail 1 Fill out the name of 2 Fill out the 3 Push the Flight Call Sign start time Detail Button Figure 23 Pane showing the call sign and start up details of the chosen flight planes Step 3 Flight Details Clicking on Flight Details tab will
11. pop up a new dialog box that aids in configuration specifics about this particular mobile station The user can provide details about the message traffic originating from it its flight path ALE radio parameters the address list that is the prioritized in order of calling to fixed stations and frequency lists Showing following is the sequence in which they are configured Sequence Message Traffic gt Flight Path gt ALE gt Address List gt Scan List The five tabs are shown to be set up for the flight details Each tab is described in the following steps 28 1 Flight Path This tab provides the functionality to program the flight path of any particular mobile station The user is required to double click in the Locations column Duration hr pem Lookup Silent Location OK Figure 24 Pane showing the Flight Path planning configuration This will enable the text area in that cell Kindly enter one or two words descriptive of the location serving as waypoint shown in the left figure below Press tab key or Enter to search with this location name and press Lookup Location button Pressing the lookup button will popup the locations that contain that particular word In the right figure below all the location containing the word Dover from the left figure are listed as they exist in the locations database Select the exact location and press Ok amp Aircraft Details i Select Exact Location Duration Lacations
12. the configuration GUI The associated functionality will be implemented in the next version build of GenetScope possibly in Phase II of the project 3 The model is in developmental Beta stage and validation of simulation results with real time JITC data is undergoing Error reporting is highly recommended 4 No terrestrial networks have been introduced in the current version They are left for Phase III of the project 2 ENVIRONMENT SETUP About Clicking the About button will present the related information version and involved personnel associated with this project Help Clicking the Help button will open the pdf version of this document Manual in Internet Explorer window GENETSCOPE NetSim2 Developed at Arizona Center of Integrative Modeling and Simulation 13 Start Page Start Page contains Hi Frequency Global Communication Systems HFGCS logo a label that says Developed by Arizona Center for Integrative Modeling and Simulation and a button named start Push the start button to continue the environment setup or another tab named Experimental Frame is shown Click the Experimental Frame tab GENETSCOPE NetSim2 click here Developed at Arizona Center of Integrative Modeling and Simulation Figure 6 GenetScope Logo and starting the session 14 2 1 Developed at Arizona Center of Integrative Modeling and Simulation Figure 8 Appearance of Experimental Frame Tab after cli
13. the ALE radio off No traffic no sounding no listening li Silent S Turns ON the ALE radio No traffic no sounding li No Traffic N Turns off the traffic No traffic v Active A Fully operational Sounding Listening sending Traffic NOTE Be cautious about the sequencing of ALE modes while planning the Flight path All the mobile planes start as Silent S as default on which the user has no control over In the above example the sequence is SAAAS If the user plans to use O in the sequence S must follow O i e OS is an orderly pair The aircraft must first appear on the scene as Silent and then change its mode to Active or No Traffic or stay as Silent If user wishes to begin the Flight path by switching the radio silent and turning it ON after certain waypoints then the sequence formed is SOSAS or SOOSANS etc 30 E Duration hr This represents the time at which the aircraft arrives at this waypoint and changes its ALE mode For example in the example above the aircraft at 0 15 hr from the simulation start time arrives at Waypoint Dover DE and become Active Similarly the aircraft reaches second waypoint Falmouth ME after 2 hours of previous waypoint and remains Active 2 Mobile Message Traffic This section tab defines the traffic streams originating from this mobile station The description is same as fixed station Message Traffic tab described in earlier sections For ease the configuration proce
14. will be C ProgramFiles ACIMS GenetScope Netsim2 3 Click Start gt Programs gt ACIMS gt GenetScope Netsim2 OR GenetScope2 icon on the Desktop to start the application 5 2 Directory Structure The application is tightly integrated with the directory structure below The user is very strongly recommended to not change the structure of this directory Failure to do so might deem the application not executable The project directory contains the following subdirectories files 1 Readme 2 GS1 0W exe Main application 3 GS1 0 This folder contains basic application Config files 4 GenetScope Netsim2_Manual pdf Software User s manual 5 Configuration This folder all the generate or saved configuration scenario files with extension cfg The files can be opened in Wordpad for viewing and manual edition However it is not recommended to manually edit the Config files Three basic configuration files are available as described in the previous section The user can build on these files for reference a Sample Archives This directory contains the original three base files that must not be changed They are to be left as originals in case the user changes them in the parent folder The files stored in this sub folder will not be visible in the application GUI 6 inst_files This folder contains the required setup files for GenetScope application None of the files should be changed 7 itshfbc This folder contains the files required to run t
15. 10B and STANAG 5066 The transmit subsystem includes 4 kW solid state power amplifiers a high power transmit matrix and combination receive multicoupler antenna matrix A typical SCOPE Command station includes operator consoles HFNC circuit switching equipment DES DSN LCO HF radios ALEs RF matrixes RTs and antennas RXs T Xs A non blocking digital electronic switch DES connects the station to the local military and or commercial telecommunication services The switch features unlimited conferencing modular sizing digital switch network precedence function and capacity for up to 2016 user lines Radio Stations Control Systems Call Airersit Best Station Link Andrews AFB Command Post Find the Best 3 Stations si Send Tail Humber four Phone Humber Figure 2 Communication flow diagram for SCOPE command SCOPE Command uses a modular open system design to automatically manage and control all network operations including those at split site stations To achieve maximum flexibility the system uses commercially available standards based software and a multitasking operating system This approach permits 14 out of 15 network stations to operate lights out unmanned and to be economically controlled from a central location The control system also includes LAN software servers and routers to support unlimited LAN WAN Station StationSpec StationAspect Mobile Fixed Levels HFNC
16. 300 Refresh Repos amp ry Refresh configuration files ar l Gi LEN he PL IR m ru ram Figure 9 Basic operations related to saved Configuration files 16 GENETSCOPE NetSim avo mes Mobile Stations i i D Experimental Frame 10 20 30 40 50 60 70 80 90 100 Ke in Data Msg Simulate Configuration Load Update Confi ati xis blared 3 Voice Duration 10 20 30 40 50 60 70 80 90 100 Te Ground Stations Sound Interval Aircraft Sound Interval SHR Threshold Figure 10 Some parameters considered for Experimental Frame These values percolate to the individual fixed and mobile station configurations and the rest of the scenario is bounded by these top level design requirements Further the default values are set as per the following Level in Fixed Station 1 Fixed Station 14 Mobile Station 10 Msg Hr 2 Data Msg 10 KB Voice Duration 60 sec Ground Station Sound Interval 90 mins Aircraft Sound Interval 90 min SNR Threshold 6 dB Once the values are set push the Configure Experiment to store the values 17 a ee Moble Stations and functions of GenetScope NETSIMZ The 50 100 150 200 250 300 scenario is CONUS based providing two aircraft on routine flights Traffic is base on woice messages at selected internals Linking Message transmission and LOA data can be Msg 2 click here to go to a next step 90 100 reviewed and analyzed a
17. DES LCO DSN DLP ALEs ATs TXs RXs PAs AModems DModems n N n n n B n ALE RT Tx Rx PA AModem DModem Rules 1 if selecting Mobile from StationSpec then n 1 else if selecting Fixed then n Levels specified by number of Levels Figure 3 System Entity structure for SCOPE command system showing the fixed and mobile aircraft stations The program includes a Systems Integration Lab SIL and test bed facility located in Rockwell Collins Texas facility The SIL is used to predict the impact and risk that any changes or upgrades will have on system performance integrity or costs before actual implementation begins The SIL includes a fully functional SCOPE Command station for performing baseline design verification interface compatibility and functional verification tests Joint Interoperability Test Command JITC is the only government agency that is assigned the task to validate and authorize IT systems for military operations The HF SCOPE command system has also been evaluated by JITC In collaboration with Dr Eric Johnson a simulator was developed in the C language around 1997 that was validated and eventually used by both the government and the industry to conduct experiments and run scenarios The simulator was an exhaustive and comprehensive effort with respect to the details it implemented and served its purpose well However in today s circumstances the same simulator is obs
18. NG OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE License Information This software GenetScope NETSIM2 and associated DEVSJAVA are licensed to the United States Department of Defense Defense Information Systems Agency DISA Joint Interoperability Test Command JITC Disclaimer The software contained within was developed by an agency of the U S Government DISA JITC has no objection to the use of this software for any purpose subject to appropriate copyright protection in the U S No warranty expressed or implied is made by DISA JITC or the U S Department of Defense as to the accuracy suitability and functioning of the program and related material except for its intended purpose nor shall the fact of distribution constitute any endorsement by the Department of Defense The GenetScope NETSIM2 model and its JAVA code are unclassified 53
19. O is default in Fixed stations and Whip is default in mobile stations Number Type sign 3 Fixed station antenna Fixed station antenna Fixed station antenna Fixed station antenna Mobile aircraft Ed PITT e m Rosette DE um LEN UN D 10 gr Dipole Vertical Monopole c HH lt Probe Di NS E Other 2 go re O an EE RE BE BERE dz the Message Traffic AleLevels AleParameters ScanList Gnd InfraStructure Antenna Gain vs Azimuth of Number af Antenna Antenna Pointing selected Antenna ALE Radio Power Type Type Angle Mission Priority Angle Sets Watts TX RX degrees degrees Level 1 wooro Figure 17 Pane showing individual details of every level in the Fixed station e Ale Parameters These are the default ALE parameters that are being used for ALE protocol The user is not recommended to change these parameters unless the scenario demands studies related to ALE protocol itself For 24 convenience purposes these values can NOT be changed in the current version The only programmable value here is Sounding Interval which is specified in the Experimental Frame and is reflected here Message Traffic AleLevels AleParameters ScanList Gnd InfraStructure Dwell sec Sound Length sec Listen sec Noise dBw Inactivity timeout Sec sounding intend Gia 2 OF Wait for response sec Reset to Defaults Tu
20. OF 50 577 d 01 07 49 389 01 07 50 967 T 1 2 8 B 4 3 ri 8 With reference to the AleLog above the corresponding channel occupancy can be looked into more detail through this logfile 0 in Destination column implies that it is Sound Start and End time refer to the Transmission s beginning and completion 44 3 LQALog This particular log file is of most interest to the simulation run It reports the LQA scores by all the station on an hourly basis as the transmission are heard at its end The value shown in the table is the representation of Signal to Noise ration heard at that station during that hour It is in a table format where the receiver station constructs a table with Channels on x axis and heard stations on y axis The following image shows the LQA table for ALE 170 that resides at Station MCC and ALE 152 that resides as Station ADW at level 1 in a given scenario configuration at hour 1 of simulation run Gri EISGO PEs Nets eU ES Start Experimental Frame Logs Analysis Performance Analysis Channel Log ALE Log l Linking Log f MobilesLog Log i Message Log LOA Log Las Table from ALE 170 level 1 at station MCC at hourd A5 I I I i gee BOSE quu I RIE A 21 I I LOA Table from ALE 158 level 1 at station AED at hourt olg crc mmu 4 LinkingLog This log provides information about the links that were established over the course of simulation The figure below is se
21. OVER AFB USAF WHP 2 4 8 10 LI 14 I 19 AFALE NIPRNET SIPRNET CAPNET Running Simulation Run Simulate This tab provides four functionalities 1 Run Abstract Model This model is a high level abstract representation of the model and useful for quick estimation This is not operational in the current version Run Detailed Model Resume Simulation The second button simulates the configured detailed model Pressing the button once will start the simulation and change the button to inactive state It will also enable the third button Pause Pause his button interrupts the simulation in between Pressing this button once will render it inactive and activates the second and fourth button The second button shows Resume Simulation which on clicking resumes the simulation from that point onwards or the user can press Terminate button Terminate This button is only activated once Pause is pressed This protects the simulation engine from crashing when heavy processing is underway Pressing this button will remove the Run Simulate tab from the application and the gathered simulation results are stored in the Logs directory This button also terminates the current session and the user is led back to the Experimental Frame where he can start fresh with second simulation session that can involve creation of new configuration file running an old configuration file or reloading a saved configuration file The Run Simulate tab can be re est
22. Over Start at min The user can specify when this particular traffic stream will become operational from the start of simulation time This feature is currently NOT implemented in Version 1 0 Ale Parameters Sizetseconds Msgsilhr Type Precedence Start at or Bytes iir wo Voice tandom iw Data nh 1 2 Voice Fa l 1 r ic lam fon Data 2 Voice E Fa Message Traffic Ale Levels ScanList GndinfraStructure Gnd InfraStructure 2 Data Voice Figure 16 Pane showing various parameters needed for a traffic stream Ale Levels This tab will allow for configuring the ALE levels in the chosen fixed station The value is bounded by the Experimental frame The user is allowed to specify the details of each individual level in this pane It also provides information about the antennas used at each individual level The antenna parameters are defaulted in this version of Netsim 2 Following are the parameters considered Number of ALE Radio Sets the total number of levels maximum 16 levels Power Watts antenna power Antenna Type Antenna Pointing Angle degrees Mission Priority Angle degrees Gain db 29 The columns empty below are intended for future version of the Netsim 2 except the Antenna Type columns The current version does support antenna configurations and its effects on SNR Various antenna types can be described as follows If no selection is made LT
23. Size Seconds Misqsihr Type e a dM E ar Bytes e I Latitude Longitude Message Traffic amv i Voice _ iz 35 Data Eig E Voice andom Dat 1 The list of E Voice rl Een l en a se et Figure 14 Snapshot of Fixed Station configuration Pane showing various sub panels 2 Station info panel This panel displays station call ALE Activity Latitude Longitude Location and lookup Station call is entered by a user If any station on the list of stations is checked or unchecked the station call of the station is displayed on the text field ALE Activity is a combo box that contains the two values i e Active or Passive Latitude Longitude and Location can be typed by a user The Lookup button sets all the fields of station info panel and station info tabbed pane with all station information regarding the station call In order to view the information and configuration of any fixed station enter the three alphabet call sing of the fixed station in Station Call text field and press Lookup button This will show the details related to that particular station All the tabs in the Station Info tabbed pane will reflect the information associated with that station 21 amp GENETSCOPE NetSim2 DOK mex Ji tem fi Eee System Configuration After click the Lookup button 3 A i F ret II cies ij Location St ADV Es i GUA d Station Call IKF
24. ablished for a different configuration scenario once a running simulation is terminated 40 Various fields and information on the simulation pane is self explanatory E GENETSGOPE Netsimz SEE Experimental Frame _System Configuration Runi Simulate O Debugging mode _ Debugging mode Simulating configuration file config 19 53 8 2 06 SSH 33 Threshold SHR dB 20 Start Time GMT 16 00 00 Default Scanlist AFALE Prop Model YOACAP Ground Station sounding Interval min 90 End Time GMT 1 00 00 Obtained Statistics at hh mm ss 00 28 51 3 tom stat of simulation time Total transmissions Last Transmission at 00 28 19 535 25 Sound transmitted by 150 on channel 8 Total Heard Sounds Last Sound heard at 00 23 17 105 By station 150 Level 1 from station OFF on channel with LOA score of 50 27 Best SHR detected so far 35 0 dB on Channel 2 at 00 15 59 733 Total Messages includes retransmission Voice Transmitted 1 Delivered 1 Data Transmitted 0 Delivered 0 Total Stations Active Silent Ho Traffic Mobiles ah MOTE The Simulation Clock above should be continuously advancing If it is nat advancing for more than GO seconds the system is in locked in mode kindly run the simulation again in Debugging mode and repart it ta the ACIMS development center Figure 38 Real time Simulation Visualization Pane 2 8 Logs Analysis Tab This particular tab gets activated and shown when the user terminates the simulation
25. anual gives the system overview of NetSim 2 environment and documents the steps to setup and run experimentation of HFGCS network models The example communications scenarios are described for a user to run the system for exercise JAVA is registered trademark of Sun Microsystems Inc in the United States and other countries DEVSJAVA Copyright 2002 Arizona Board of Regents on behalf of The University of Arizona This page intentionally left blank 1 1 1 1 2 1 3 1 4 2 1 2 2 2 3 2 5 2 6 2 7 2 8 2 9 4 1 4 2 4 3 4 4 5 1 5 2 OVERVIEW ENVIRONMENT SETUP SIMULATION LOGS SCENARIO GENERATION APPENDIX TABLE OF CONTENTS PURPOSE 4t reete Mai sensi e uM e UE cM ARCHITECTURE AND BACKGROUND e eee eee eeeeeesssso eese esee e esee eeeeoao FEATURES eet LIMITATIONS abaco Experimental Bramerini Defining Fixed Stations Defining Mobiles Station ira Defining Simulation Time Duration and Propagation model eroniutheistoiM lir R nninco Simulation ila ansa ocv voee e vevp edo eve Co aree sua Devo sd deo dae odas Logs Analysis Tan uie ure eni oe Pede ite i d e nod Pertormance Analysis T3Dz ii uiii toit eaa dto irritanti Example L Base WICBATE crei Example 2 CONUS with Traffic ellenica idonea Example 3 Global with Trafic nia Developing Scenario Soni ae as ve aas aE A ran Installation Instrucetions ici io Directory Struetu
26. cedure and gets linked after 3 way 43 handshake and both stations get linked at 01 06 13 190 s Finally 150 starts the 1 minute Voice traffic and comes out of the linked phase and returns to scanning at 01 07 19 388 s ChannelLog This log provides information about the channel occupancy and activity over the simulation run The columns provide information in this sequence Channel Start Time End Time Src Destination Power It tells us about which channel has been used at what particular time and who are the two stations engaged in communication procedures A typical snapshot of this log is shown below e agr genus i Si Start Experimental Frame Logs Analysis Performance Analysis ChannelLog ALELog Linking Log MohilesL og Log Channal Start Time End Time HU T 00 4 FF Ira E 47 43 388 00 47 44 067 00 48 50 281 00 48 56 752 JB 00 50 39 579 00 50 46 040 M50 00 52 12 277 00 5218 738 00 52 14 603 00 52 24 064 g 00 52 56 027 00 53 02 488 00 53 13 469 36 0 00 56 41 597 00 56 48 058 h E 00 57 18 280 E 0 01 00 20 347 01 00 26 808 i 36 0 01 01 08 987 Di 01 15 448 01 03 46 456 mosar 8 oar hw 04 20 678 110 01 05 45 172 01 05 51 632 f8 i 01 0846 139 01 05 52 599 01 05 46 623 01 05 53 083 i 01 05 48 074 01 05 54 534 i ID 05 49 045 01 05 55 504 01 06 02 400 01 06 09 262 01 06 10 045 01 06 11 231 01 06 11 621 01 06 13 199 01 06 13 389 z 07 19 390 01 07 27 815 01 07 49 391 5
27. cking Start button Experimental Frame The Experimental Frame panel provides the facility to create a new configuration file or load an existing configuration file that is stored in the repository with its timestamp The configuration files have the extension of cfg and the filename contains the timestamp of its creation time More details about the configuration file naming and storing conventions can be seen in sections ahead The left section as shown in figure below provides four functionalities is 2 3 4 5 Create a new configuration file Simulate an already saved configuration directly without any modification to the configuration file Load an existing configuration file stored in repository as shown in the list in figure View Existing Logs for any configuration if the configuration has been simulated earlier Refresh the repository to show the recent additions in the repository during the current session In order to execute the functionalities above kindly follow the steps below Create a new configuration file 1 Click the button Make New Configuration as shown in figure This will prepare 15 the right section of the pane and load the default experimental frame parameter settings It will also make the button Configure Experiment in the right bottommost scroll down to see the button This button will be disabled otherwise Set the parameters as per scenario requirements As described
28. configuration file identified by its timestamp as suffix and is saved in the application s Configuration folder The file s name is automatically configured based on the timestamp e g config4 4 12 21 05 cfg where the numbers translate to 4 04am on 12 21 05 The sample shown below consists of 2 Fixed stations and 1 mobile station Others description details are not required as per the current document E dh 6 I Z 60 V 90 60 zi 5 16 00 00 LOG 00 3 33 V it d Enter descriptive text to provide information about the scenario with SSN 33 it it F MCO 380650 121 299 114 A WestCoast ALE 1 RT 1 PA 1 ANT 1 ASP VTM Bcast C 2 4 8 10 LI 14 17 192 AFALE C 3 6 9 12 16 Zl 2 2 NIPRNET C L 5 fi 13 L5 18 20 SIPENET G 90 Si 92 93 94 95 96 97 CAPNET D E HIK 21 317 157 957 114 A Hickam ALE in RT 1 PA 1 ANT 1 ASP ROS Beast C 2 4 8 10 T 14 17 19 AFALE C 3 6 9 12 16 21 22 NIPRNET C 1 5 7 ho 1 5 18 20 SIPRNET C 90 gi JA 93 94 95 96 Si CAPNET D F OFF 41 267 9 9450 114 A Orrutt ALE 1 RT IL PA 1 ANT d ASP LTO 39 Bcast iet ern Crue Ed 2 7 2 4 8 10 EL 14 L7 19 AFALE 3 6 9 12 16 21 22 NIPRNET 1 5 1 13 L5 18 20 SIPRNET 90 9T 92 93 94 95 96 97 CAPNET T1560 35 466 DO S CS 455684 0 3 60 10 V 3 msg hr to gnd 1 0 minutes ea 0 1 20 250 D I msg hr to gnd 20 minutes ea MCC HIK OFF AED JNR ADW hea 39 4056 asd A CITY OR USA TINKER APB USAF 4 0 39 1656 9952 v DOVER DE USA D
29. containing name Dover DOVER NJ USA PICATINNY ARSENAL USA DOVER DE USA DOVER AFB USAF DOVER UNITED KINGDOM zA Silent A Lookup Silent Location Silent Silent Figure 25 Put any keyword related to Figure 26 Pressing Lookup shows the desired waypoint and press either all places containing the keyword in Tab or Enter left figure 29 Pressing OK will populate the Latitude and Longitude for the entered Destination waypoint In order to add a location that fails to lookup you need to add it thru the Location tab under System Configuration settings tab Aircraft Details Speed ALE Location ikts State 66 75599 DOVER DE USA D 450 Active 43 716 70 933 FALMOUTH ME USA 450 Active I f Lookup FALMOUTH ME USA 450 Active s L Location DOVER DE USA o n sin EB OK Cancel Figure 27 Loaded waypoint with Latitude Longitude information from the database Brief overviews of other values associated with this tab are as follows A B Lat Long pre defined not editable Location pre defined not editable It is editable only for Lookup purposes as described above opeed The speed for the mobile aircraft is in nautical miles hour i Put Speed in the upper row ex 450 li Set up ALE mode in the lower row Except Silent ALE Mode Four modes are available for the aircraft at arrival of this waypoint location i Off O Turns
30. d value is 14 stations hence 14 rows ES Sam Ai Address List ScanList ci Add All Sites NOTE AlSiteswillbe coo 2 used by default if none are specified Figure 30 Pane showing the calling list of mobile station 6 Scan List The Scan list tab is identical to the tab mentioned earlier in Fixed station configuration section It is defaulted to AFALE scanlist Kindly refer to that section for more information about operation 33 i Sam Aircraft Details 3 The available channel is checked 1 Select one of the lists 2 The available channel is shown Figure 31 Pane showing various parts associated with configuration of the Scanlist When all the individual tabs have been programmed press OK button on the right bottom to load the information into the data structures This will close this frame and the control will return back to the Aircraft Details tab When all the aircraft details have been populated press Done button to save the information towards writing into the configuration file Pressing Done button will close the Aircraft details tab and the mobile station configurations are complete os Aircraft Details Call Sign Start Timecminy Flight Detail Sam E 20 Flight Detail Steve k 20 Bob i 20 Flight Detail 1 Press Done to save all the aircraft details Figure 32 Press Done when all the details have been entered thru Flight Detail Panes 34 2 4 Defining Channels and Locations Freq
31. don routine flights Traffic is base on woice messages atzelected internals Linking l Message transmission and LOA data can be reviewed and analyzed after termination with ordpad The user can reviem each of the logs after termination or use MS Word ta review logs during operations 3 Data Msg Simulate Configuration Load Update Configuration Load Update Configuration i Voice Duration 10 20 30 40 50 60 70 S80 50 100 Refresh Repository Ground Stations i E Figure 12 Appearance of Run Simulate tab Load an existing configuration file 1 scroll down the repository list in the left section Select the configuration file to load or update Click on the Load Update button in the left section of the pane The right section will reflect the stored values in the configuration file The Configure Experiment button will also get enabled at this point Press Configure Experiment to move to System configuration tab as described above The System Configuration will load the existing information contained in the selected file If you need to update the values for the experimental frame it should be done before clicking this button Refreshing Repository to show stored configuration files 1 2 Click on the button Refresh Repository to view the updated repository if you have saved created any new configuration files in the current session The list above will reflect the current status of reposi
32. dure in delineated again Use the first row is checked by default reflecting atleast one traffic stream You can program different traffic streams and uncheck the box for updating any existing configuration file Msg Size The value in the experiment frame is internally set up If you want to change put any value in the text box The value entered is either seconds or bytes depending on the value of traffic type under Type column Voice traffic is taken in seconds and Data traffic in bytes Msgs hr The value in the experiment frame is internally set up If you want to change put any value in the text box Type Voice or Data With Voice as traffic type it implies 2 calls per hour as shown in figure below and with Data it reflects number of data messages sent per hour Type The default value is shown as programmed in the Experimental Frame section The user can change this value on per station basis Precedence The user can select any of the five priority levels on per station basis The available priorities are Flash Over Flash Immediate Priority and Routine The default value is Flash Over Start at min The user can specify when this particular traffic stream will become operational from the start of simulation time This feature is currently NOT implemented in Version 1 0 3l amp Aircraft Details nhi D th mobileMsgTraffic fu M Sy Size sec or KB Figure 28 Pane showing the originating Traffic s
33. e value and the number that the user has selected in above combo boxes The user can go to the next process only when these two numbers exactly match One word of caution in the current version is that the user has to look into the flight details more closely if he is updating an already saved configuration file There exists no problem if the user is increasing the mobile station count but if he chooses to diminish the mobile station count he is recommended to verify the flight details and update too as a part of configuration process The ability to delete any selected mobile station from an existing configuration file will be added in the next Build z GENETSCOPE NetSim2 The selected Aircraft is C5 and a X the number of C5 is one About Help Frame System Configuration Start Experimen Fixed Station Mobiles Frequencies Location Setup Air Mobility Command Special Air Mission Air Combat Command Ground Based AME SAM ACC Radio System Cargo Tanker GBRS c le KC135 o AWACSES E Bs O race o C17 n KC10 E VC 25 CAP Air Force 1 _ B2 pe C130 l2 l Tactical E4B 0 B1 0 T PS Other Aircraft C32 T Fighte O 3 If all the numbers of aircraft has been selected n push c37 Enter Details Depart 2 The selected Aircraft is C130 and Intcconmentnmmbepotuirerrbis oS the
34. er may expand on one of the example scenarios or develop a new scenario with their specific objectives in mind One thing to remember is that the GenetScope NETSIM 2 model simulates each radio specified in the scenario sounding traffic the number of aircraft each add detail and thus the complexity of the simulation As such a very detailed scenario may take several many hours to run So practicality dictates the best practices in designing and developing a scenario The opposite also applies to short of a scenario may not provide any or enough detail to answer the questions posed by the user The simulation models the real world in both propagation and ALE functionality The JITC can provide assistance in developing scenarios or analyzing the results of a scenario One additional point to remember is that the log files used for analysis are named after the scenario so if you 49 modify the scenario but save it with the same name the files will be written over It is suggested that log files be moved to an archive directory The Configuration files may be renamed to be more descriptive and it is recommended that the comment field on the setup screen be used to define the scenario and any objectives These comments are saved with the configuration files 50 5 Appendix 5 1 Installation Instructions 1 Execute the GenetScope2 exe file by double clicking it 2 Specify a root folder for the files to get copied or the default folder
35. eters originating from this fixed station It will take the default values as set under the Experimental Frame section but user can override the internal details of the traffic stream Each row is a single traffic stream The user can program more than one traffic streams origination from the station The details of any single traffic stream can be programmed as under e Use the first row is checked by default reflecting atleast one traffic stream You can program different traffic streams and uncheck the box for updating any existing configuration file e Msg Size The value in the experiment frame is internally set up If you want to change put any value in the text box The value entered is either seconds 22 or bytes depending on the value of traffic type under Type column Voice traffic is taken in seconds and Data traffic in bytes Msgs hr The value in the experiment frame is internally set up If you want to change put any value in the text box Type Voice or Data With Voice as traffic type it implies 2 calls per hour as shown in figure below and with Data it reflects number of data messages sent per hour Type The default value is shown as programmed in the Experimental Frame section The user can change this value on per station basis Precedence The user can select any of the five priority levels on per station basis The available priorities are Flash Over Flash Immediate Priority and Routine The default value is Flash
36. framework Discrete Event System Specification DEVS for HF network models to be reusable and scaleable systematically by adding more complex functionalities and protocols throughout the future development cycle The earlier Netsim version developed in 1997 was used to analyze any given scenario whether of past or in future based on ICEPAC prediction data The current version aims to take a quantum leap by providing the capabilities to not only analyze any scenario but provide recommendation to re design the SCOPE command itself The underlying DEVS theoretical framework with its advanced features of real time simulation visualization and ability to configure simulation on the fly gives the analyst the power to understand the impact of any design parameter and how the system transitions to the new parameter set in real time without restarting the simulation This aids in changing the corresponding parameter in the deployed SCOPE command system as the analyst can study the transition effects This capability to study transition effects by changing the parameter set in real simulation time has been recently developed and is unique to the DEVS framework DEVS with its power of Experimental Frame helps focus the top level design issues like how many ground stations are best how many internal levels are minimally needed what is the capacity of the system or what is the threshold SNR that the system needs to continue to perform optimally This User s M
37. ftertermination with ardpad The user can review each of the logs after termination ar use MS Word to review logs during operations 3 Data Msg i 450 100 Simulate Configuration Load Update Configuration NS Load Update Configuration i Voice Duration O 10 20 30 40 50 60 70 80 90 100 Refresh Repository RE Ground Stations Sound Interval 50 100 150 200 750 300 Aircraft Sound Interval 40 100 150 2700 250 300 A7 21 15 9 3 3 9 15 21 27 1 Push the button BENE ce NN SNR Threshold Figure 11 Enabled Configure Experiment Button and appearance of System Configuration tab at the top This will result in appearance of a new tab named System Configuration The new tab will allow the detailed configuration of the complete scenario Simulating a saved configuration file 1 scroll down the repository list in the left section Select the configuration file to simulate 2 Click on the Simulate Configuration button di This will bring up the Run Simulate tab at the top 4 Click on the new appeared tab and proceed towards running the simulation 18 Configuration File Repository basito Select the tab to the config19 3 4 14 06 cfg Simulation pane Iken Stations li Description base cfg This is a basic scenario to learn the operations Mobile Stations and functions of GenetScope HETSIMZ The scenario is CONUS based providing two aircratt i
38. h Traffic was developed to examine the effects of increased traffic over the CONUS region Again areas like flight dynamics propagation and traffic levels were analyzed 48 All ground stations 14 Multiple Aircraft flying between locations CONUS Traffic 2 3 messages per hour of 1 to 5 minute duration Daylight with predicted SSN Again like the Base scenario a baseline was established and changes were compared to the basic data Changes to a particular scenario should be limited to only one or two of the variables with multiple changes it would be hard to determine what changes affected the output or result of the scenario By making multiple runs of the scenario with defined changes in the scenario the cause and effect of the changes can be more readily determined 4 3 Example 3 Global with Traffic Global with Traffic was developed to examine the network with aircraft and traffic dispersed around the globe The differences in propagation around the globe the ability of the network as a whole to support world wide traffic and effects of aircraft transiting between different coverage areas All ground stations 14 Multiple Aircraft flying between locations world wide Traffic 2 3 messages per hour of 1 to 5 minute duration Start 16 GMT with predicted SSN Like the previous examples specific objectives were established and the results were analyzed 4 4 Developing Scenario s In planning to develop a scenario the us
39. he scanlist As noted specific questions will result in a designed scenario s to answer those questions Once a scenario is built changes can be made to time traffic SSN or any of a number of variables to see the effects By comparing the user logs the user can determine the effects of even small changes to the scenario During the development of the simulation several basic scenarios were used to examine a number of particular validation issues Each of these scenarios s had a defined objective Each of the following examples are provided in the configuration directory 4 1 Example 1 BaseWithAnt Base was developed to examine the propagation conditions over the CONUS region flight dynamics ALE protocol and linking and basic traffic flow and management Given those objectives the scenario was setup as follows Six ground stations ADW OFF MCC JNR AED HIK Single Aircraft flying between Tinker AFB OK to Dover AFB DE Traffic 2 3 messages per hour of 1 to 5 minute duration Daylight with predicted SSN Different Antenna at different stations to check if all antenna configurations are working fine Once the basic objectives were established the scenario was developed ran analyzed modified ran analyzed etc Analysis was based on the basic first run and data obtained and changes in the scenario were then compared to determine the effects of the changes 4 2 Example 2 CONUS with Traffic CONUS wit
40. he ITSH propagation software for dynamic SNR values required by GenetScope application None of the files in the directory should be changed 8 Logs This folder contains the simulation logs for production runs If the user wishes to run the simulation again for the same configuration file it is very strongly recommended that the user save the simulation logs of the previous run as they will get overwritten The Logs folder contains various sub folders with the name of the Configuration file For example if the configuration file name is SI BaseWithAnt cfg the Logs folder will contain a folder called BaseWithAnt that will contain all the logs described earlier 5 3 Bug reports with contact information The GenetScope version 1 0 14 is in Beta status Problems like locked in might occur in which the simulation clock stops before the end of simulation time In the event of such occurrence the analyst is request to run the simulation again in Debug mode and send the log files to the ACIMS development center The log files along with usual log files that must be mailed are EventLog ExceptionLog ErrorLog Prop Log PONS The Email addresses are as follows Saurabh Mittal Lead Developer saurabh ece arizona edu Seahoon Cheon Team Member Cheon ece arizona edu Chungman Seo Team Member cseo ece arizona edu All the personnel above work at Arizona Center of Integrative Modeling and Simulation Rm 318 ECE Department Uni
41. lation setup tab for the scenario loaded configured 37 Entering Data Error Entering Data Error Once the time date are configured pressing the Write files button will result in a configuration file in cfg format saved in hard disk opened thru Wordpad application In addition to writing up the configuration file the configuration is also loaded to the simulation model to enable the simulation with current configured scenario Information will pop up displaying that the configuration is now complete validated according to the Experimental Frame settings and stored at what particular location Error Message Pa Error Message There is no SunSpot info above 2008 gt Thereis no SunSpot info below 1997 Decrease a SunSpot year CU Increase a SunSpot year Figure 36 Error messages if the user enters a month or year not supported by the Model Configuration Complete Stored at C inscape Configuratiomcanfig11 10 3 9 06 cf g Ready ta Simulate Click Run Simulate Tab Figure 37 Confirmation message notifying that configuration is complete stored and ready to be simulated Clicking on the Write Files button will add the Run Simulate tab at the top level indicated in the figure below At this juncture the scenario is completely configured saved in a dedicated folder for this simulation run and ready for simulation 38 2 6 Configuration File The process described in previous section results in saving a
42. lf explanatory with Qual reflecting the LQA score quality and Time taken the duration for ALE link establishment procedure execution 45 Print Channel Log ALE Log Linking Log MobilesLog Log Message Log LOA Log Source Destination Channel Start Time End Time Time Taken 50 1 B 38 00 76 00 200 00 26 13 191 12 99 1 LE 0000 H2 00 46 00 194 00 46 13 190 12 88 1 5 29 01 06 00 201 01 06 13 190 12 888 5 MobilesLog This log provides the information related to the flight path traversed by any mobil e plane with the time stamp The log can be sorted based on column CallSign to plot the trajectories of any specific mobile plane EA st ESTIS GU PES METTI Experimental Frame Logs Analysis Performance Analysis ChannelLog ALE Log Linking Log MobilesLogLog Message Log Call Sign Station ID Latitude Longitude At Time TE UU 479 588 455684 1 1 1 150 36 2600 11111 p83965 004712172 36260 p83965 JjJ004712412 36 260 83 865 00 47 13 247 93 907 00 47 43 672 93 907 00 47 43 913 93 907 OA AAA 8385 00 48 50 456 93 85 00 48 54 957 93 678 00 50 41 172 455884 93 678 00 50 41 412 00 50 41 697 00 50 42 065 00 50 42 248 6 325 93 678 005042251 5 382 93 678 00 50 43 100 00 50 45 672 93 506 00 52 14 539 150 4556084 pa 150 150 DI Lo c ho ce oo a I III IIIa CE EE Lola bela CHE bota bali bela aa III Peo Pea pm Peo ea Peo Pea a 1 Ta rs
43. ng that initial Netsim model written in C language has this database tightly coupled with the model In our present implementation we made it modular so that it can be replaced by any other database that could provide the channel propagation values through the ionosphere for ex VOACAP The DEVS Layer comprises both of model as well as the DEVS simulation environment The Experimental Frame layer contains the controls required to modify update the model as well as simulator as per enhanced MVC The simulation visualization is modular in construction and reflects the updates in Experimental Frame layer and the DEVS layer ICEPAC_DATA access 1 Net configuration 2 SNR updates based On position of station Simulation State DEVS Entity coupled Model DEVS Atmosphere Model Figure 5 Simulation architecture for SCOPE command network 1 3 FEATURES DEVS Layer The GUI of NetSim 2 is arranged in a tabbed notebook fashion separating each part of the system into its own page The major components are Fixed Sites Mobiles i e 11 aircraft Frequencies that will be used for communication and simulation parameters A fifth page provides a list of worldwide locations which can be selected as needed for placement of fixed communication sites or points as part of aircraft flight paths This version GenetScope 1 1 contains the Antenna configurations as shown below REM Sumber cS sign LTO X Samples sample32 station
44. olete due to the heterogeneous nature of today s network traffic in which E mail occupies a considerable percentage of traffic The simulator is now being upgraded at the ACIMS lab in order to make it more useful for current demands These demands stem from the possibility of expansion of current infrastructure of SCOPE command Questions arise such as how many stations need be added to service a required workload Also needing to be investigated are tradeoffs such as whether it is more economical to add more stations or increase the number of internal radio levels within stations to meet the anticipated demands Air traffic has increased manifold since 1997 along with the computing technology Consequently the transition effects need to be monitored more closely and the overall system response time needs to be documented The significant parameters have to be identified that have the most impact on system performance To more easily address such questions an effort is being made to modularize Johnson s 15K lines of code into component based structure depicted in Figure 3 Once componentized the components are made DEVS compliant resulting in a DEVS based simulation package to support the systems engineering needs of the SCOPE command As we need to study the effect of changes upgrades introduced to the existing SCOPE command system we built the Experimental Frame based on DEVS principles for our modular DEVS netsim simulation model named as
45. re s illa S 5 3 Bug reports with contact information eoo ese coetu alain Cai 53 CINA AIA ROIO SIA TT 53 License AN OMMOAMON sizione ie ee el Ce MEC litri i 53 Dili dio ne 53 This page intentionally left blank 1 OVERVIEW 1 1 PURPOSE The purpose of NetSim 2 is to provide a user friendly discrete event M amp S environment for a user to test the performance of the ALE system under various loads and specifications 1 2 ARCHITECTURE AND BACKGROUND SCOPE Command is a highly automated high frequency HF communication system that links US Air Force command and control C2 functions with globally deployed strategic and tactical airborne platforms SCOPE Command replaces existing USAF high power HF stations with a communication system featuring operational ease of use dependability and seamless end to end connectivity comparable to commercial telephone services The network consists of 15 worldwide HF stations Figure 1 interconnected through various military and commercial telecommunications media Figure 2 It increases overall operational and mission capabilities while reducing operation and maintenance costs Eu m Figure 1 Geographic locations of Fixed stations The HF radio equipments include Collin s Spectrum DSP Receiver Exciter Model RT 2200 The radios feature Automatic Link Establishment ALE and Link Quality Analysis LQA capability and are adaptable to future ECCM waveforms FSK MIL STD 188 1
46. rnaround sec Figure 18 figure showing default ALE protocol parameters Scan List This tab provides the user to select any available Scan list A scan list is defined as a set of frequencies being used by that particular station to communicate with other stations The defaulted choice is AFALE scan list There are four Scan list supported by Netsim 2 Each Scan list has unique channel list independent of other types and each channel internally translates to a single frequency If one of the radio boxes is clicked then text area displays the channel list of the radio box ALE Freq table shows the channel frequencies of each channel and check boxes that mean if checked the channel in the first row is used and if not the channel is available The channel used by a type can not be selected by other types Message Traffic AleLevels AleParameters ScanList Gnd InfraStructure ALE Freq AFALE Channel MHZ ALE NIPRNET 1 27870 vi C3 SIP 7 SIPRNET 2 23337 iv 5 CAPNET 3 20631 y Channel I 4 18003 vi 2481011141719 I 5 17976 vi B 17373 vi Update Figure 19 Figure showing scanlist operations at the station Gnd Infrastructure This panel is left for further development in the near future 25 Priority Times Day Figure 20 Ground infrastructure parameters to be considered in future 2 3 Defining Mobiles Station The second tab in the Sys
47. tem Configuration section allows for detailed configuration of mobile stations or aircrafts carrying ALE radio sets The main screen for Mobile stations shows various types of aircrafts that can participate in any particular scenario The user can select different types of aircrafts for the current scenario However the total number of aircrafts added is bounded by the number of mobiles specified in the Experimental Frame section In the event of mismatching the user is presented with warning messages as shown in figures below Aircraft Count invalid Eg Warning Reduce the number of aircraft as per Experimental Frame settings Warning Increase the number of aircraft as per Experimental Frame settings Figure 21 Warning message if mobile station count selected does not equal that of Experimental Frame count The user is recommended to verify the count from the Experimental Frame mobile station count and select that many stations from the Mobiles tab The total mobile station configuration is executed in three steps as described below 26 Step 1 Mobiles 1 Choose Mobiles tab to open Mobiles station setting 2 Choose the combo box which is next to the name of aircraft and then select the number of aircraft 3 After you have finished the selection push the button Enter Details In order to aid the user to verify if he has selected the correct number of mobile planes the pane above shows both the Experimental Fram
48. tions on the list are performed as under A Add i Click the lower row you want to add ii Push Add button ii Once the empty row will be shown put the value in the each box B Delete i Select the row you want to delete li Push Delete button C Save Once you edited all value push the Save button It will take for a while tal Frame System Configuration Location TER TET If you push add button 3335N 8551W ANNISTON Al USA the new row is created in 3347N B548W ANNISTON uN BODEN WORE the just upper row you 3223N 8612W MONTGOMERY j select 3221N 8658W SELMA AL mtm B6 42 HUNTSVILLE REP Be 35W HUNTSVILLE Al USA ARSHALL SPACE NASA 8621 W MONTGOMERY MAXWELL AFB USAF 6116M 4946W ANCHORAGE AK USA ELMENDORFAFB USAF eje ETIEN a AAD ANCHORAGE a a JAK nm n n a WGA n n a a ELAIQUARQRQN She n err iL PS Da a ld dia Ree int 5153M 17639 ADAK AK USA ADAKNS USN 5243N 17553E IS AK USA SHEMYAAFE USAF 5521N 13135WW KETCHIKAN AK USA KETCHIKAN CGE USCG B450N 147364 FAIRBANKS AK USA FT JONATHAN WAL USA 5703M 13512 SITKA AK USA BITKACOASB jusca 5440N 147 06W FAIRBANKS JAK USA EIELSON AFB USAF 5745N 15230 KODAK AK USA KODIAKCOAS USCG E 40N 114 380 YUMA Pri USA YUMA MCAS USMC ir 1 oi LEI Lin logi pinkie ico mar
49. tory 19 GENETSCOPE NetSim2 Experimental Frame Mobile Stations n Data Msg Simulate Configuration Load Update Configuration x Lead Updete Configuration i 2 Mnice Duration Refresh Repository Ground Stations Sound Interval Aircraft Sound Interval 1 Push the button SHR Threshold Figure 13 Refresh Button to refresh the contents of Repository to view recently created configuration files 2 2 Defining Fixed Stations The main page of System configuration begins with a Fixed Station tab The tab consists of four parts such as the list of stations station info panel station info tabbed pane and modification of stations data Before starting this panel the data structure of stations should be created and the values should be set 1 The list of stations The number of fixed stations is obtained from the previous step Default number of fixed station is 14 The stations with Checked checkboxes are active in the simulation while Unchecked stations are inactive User can check or uncheck the fixed stations 20 GENETSCOPE NetSim2 E mm About About Help Help Start Esa Semone sa 2 Station info panel Fixed Station Mobiles Frequencies Location SetUp ADV E 3 Modify stations data Ep Station Call ALE Activity Active SITE HAW j cro Esse E AED Location ra HIK nu PLA vj Mec HOFF
50. treams from mobile station with call sign Sam 3 Mobile Levels The user can specify the antenna that is onboard the mobile aircraft If no option is selected Whip antenna is selected by default ALE Addresslist ScanList sa Antenna Mumber ot 7 Antenna Pointing a ALE Radio Power Type Angle Mission atts TX RX Cancel 4 ALE The value set up in the Experimental Frame is reflected in the Sounding interval field in the panel Others are not required to be set up in the current version 32 i Aircraft Details Transmit Power Watts 100 The Sounding interval is Dwell sec 050 Sound length sec 100 reflected from the value setup in the Experimental Frame r3 II Listen sec Noise dB f ZE Inactivity timeout sec 20 00 Sounding Interval Minutes O Off Wait far response sec Ji SEE Reset to Defaults OK EN Figure 29 Pane showing ALE protocol parameters for mobile station radio Turnaround sec Address List This tab provides the user to configure the priorities of fixed stations when the mobile station wishes to make a call to ground station It is defaulted to the number of fixed stations selected during Experimental Frame configuration aligned in random order of priority The user can change this list as per scenario requirement Each of the row below is drop down combo box each having all 14 stations The defaulte
51. uency Channel database The frequencies available in the system are shown User can choose the Scan list in the Comments combo box There are currently 100 channels defined that correspond to 100 frequencies Various other constraints like power on which they operate restricted access and their categorization are also provided here This is the master channel table and each channel is configured to lie in atmost one scanlist The mapping is provided in Comments section where the user can specify whether the channel belongs to either of the following 1 NIPRNET 2 SIPRNET 3 CAPNET 4 Published 5 Discrete 6 Not in use GENETSCOPE NetSim2 LOI Tai re x ra NM E a rt Experimental Frame System Configuration S xu Ei ecd EIE e e Fixed Station Mobiles OL I uL Channel Fregikhzy Maximum Restricted Comments Power fatta iSIPRINET AF ALE INIPRNET AFALE SIPRAET IMIPRAET SIPRAET AFALE INIFPRNET Figure 33 Master Channel Frequency table and their classification in various Scanlists Locations This top level tab shows the location database used by the model The geographical locations specified here can be used to program the flight path of any mobile station The user can add delete any location and it is saved in the local database for future 35 use A location once deleted can not be retrieved back the location data is shown in the table The basic opera
52. versity of Arizona Tucson 85721 AZ WWW acims arizona edu 32 Credits The original NETSIM SC program and code were developed by Dr Eric Johnson New Mexico State University The GenetScope code was developed by the Arizona Center for Integrative Modeling and Simulation ACIMS at the University of Arizona Tucson Arizona Copyright Notice Copyright Arizona Board of Regents on behalf of The University of Arizona All Rights Reserved USE amp RESTRICTIONS This software i e DEVSJAVA with ID number UA1885 is disclosed to the Office of Technology Transfer of the University of Arizona Software is developed by University of Arizona TUCSON ARIZONA USA Copyright c 1996 2000 All rights reserved DEVSJAVA in part or in whole IS NOT transferable to any other party individual or entity without explicit permission from the University of Arizona s Office of Technology Transfer or Arizona Board of Regents NO WARRANTY THIS SOFTWARE IS PROVIDED AS IS AND WITHOUT WARRANTY OF ANY KIND EXPRESS IMPLIED OR OTHERWISE INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A SPECIAL PURPOSE IN NO EVENT SHALL THE ARIZONA BOARD OF REGENTS ON BEHALF OF THE UNIVERSITY OF ARIZONA BE LIABLE FOR ANY SPECIAL INCIDENTAL INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE DATA OR PROFITS WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE AND ON ANY THEORY OF LIABILITY ARISI
53. with their message type as eit her Voice or Data PropLog base223 0 3 10 06 txt The purpose of this log is to document the ICEPAC software access and Verify the returned values from ITSH software as and when they are used in the simulation model This is for exhaustive analysis of the simulation analysis in conjunction with above logs The details are not meant for the user and hence omitted Errog base223 0 3 10 06 txt This particular log focuses on the errors that might be reported during the simulation run This log is entirely for development purposes and for any feedbacks that designers might want the developers to know Eventog base223 0 3 10 06 txt This log is also meant for debugging and development purposes It is not required in production runs It is recommended that this log be not generated during the production runs as it is a huge log amount to few gigabytes for a typical simulation run lt accounts for ever single event that is generated and processed as the simulation proceeds forward Again for clarity purposes the details are not provided herein 47 4 Scenario Generation Hopefully the user of the simulation has an objective in building a particular scenario e What are the propagation conditions over the Atlantic during a specified time period e How many aircraft in a region are affected by the loss of a single ground station e What happened last year or next year when we change frequencies in t
Download Pdf Manuals
Related Search