HLA Project Overview ACIMS Lab Prepared by: Saurabh Mittal

1. HLA Project OverviewACIMS LabPrepared by: Saurabh Mittal

2. To Start with… • Basic ideas on • Designing network environments with common parameters (e.g. mean distance, probability of connection, quantized or periodic updates, etx.) • Modeling various components within these networks • Preliminary design of router completed • Basic tests conducted (eg. Ensuring packet routing etx..)

3. Layered Architectural Framework Experimental Frame Layer DEVS Simulation Layer (nodes and links being simulated as per DEVS Formalism) Traffic Generator Parameter Controller / Evaluator Topology Designer Visualizer Network Modeling Layer Topology Sub-layer Routing Sub-layer Area encompassing components designed using DEVS Formalism

4. DEVS Modeling & Simulation HLA Network Framework Development of DEVS: • Modeling API for components in Application Layer • Routers • Links • Message Passing and other specialized features related to Application Layer components

5. System Entity Structure (SES) for Net-Framework

6. updates Improvise Router (network) Node for HLA implementation • Develop the router node as shown below and create a network Network Node Real-time Routing Engine Routing Capability Inside every network Node (taken form earlier Version of simulation-based Router) Message Passing to be implemented Routing/Lookup Table Forwarding Engine M/M/1 queuing system that routes packets based on the information from the forwarding engine. The queuing system characterizes the RTI capabilities Payload Traffic Generator Traffic generator Generating packets Of different classes RTI Ambassador Updates to specific destinations

7. HLA / RTI Implementation • Centralized and De-centralized versions of network HLA/RTI under consideration • Different experiments devised to gather information about • Thruput • Network delay • Link utilization • Transducers being implemented within components (links+routers) to gather individual data in an automated manner.

8. Conceptual Centralized HLA/RTI network • Network components • Centralized RTI Executive node • Receives packets being published • Broadcasts packets being subscribed • HLA Router • Generates traffic containing packets of different ‘classes’ • Links

9. Centralized HLA/RTI Network RTI Executive - a part of the Network - routers publish messages of different ‘classes’ to RTI - broadcasts messages to every other node - those subscribed to particular ‘class’ of messages, attend to it, others ignore Metrics - end-to-end Delay - average link utilization - thruput - queuing time at RTIExec ‘RouterNode’ ‘HLA Router’ ‘HLA Router’ ‘HLA Router’

10. HLA Router DEVS Network in simView RTI Executive RTI Exec Router links 4 5 1 RTI Exec links 6 0 HLA Routers 3 2 DEVS Demowith RTI Executive Example Topology being modeled Run networkHLAwithRTIExec.java

11. Publish-Subscribe functionality public class Publish extends entity { ///stores classNames in string format private ArrayList classes; private ArrayList classesString; private ArrayList classesDouble; public Publish() public Publish(String name) public void publishMsgOfClass(String msgClass) public void publishMsgOfClasses(ArrayList classes_) public int getPublishedClassCount() public String getClass(int i) public boolean isClassOfMsgPresent(String msgClass) public void removePublishedClass(String msgClass) } • Each federate • Publishes packets to ‘classes’ • Subscribes to particular ‘classes’ If there is RTI Executive present • Packets are published to destination RTI Exec • Packets are broadcasted to other federates thru it • Packets can be multicasted to only those federates who subscribe to those classes If there in NO RTI Executive present • Point-to-point network • Packets generated to specific destinations • Similar is the ‘Subscribe’ class • Benefits: • Can communicate in more than • One data-type as opposed to just ‘Strings’ • Better functionality and encapsulation • by creating a Publish or Subscribe object

12. DEMO 1 LINK PANEL Run networkHLAwithRTIExec.java main function • Visualization of constructed DEVS Network in real-time manner . • Adjusting of network parameters for observing behavior of the network • Modular GUI development and GUI created at run-time during the time the network gets created • EASY to IMAGINE what you want to achieve with your network ROUTER PANEL Real-time Simulation Controller

13. FAST Mode DEVS simulation inside devsNetworkHLA.java public void simulate(){ s.s("inside devsNetworkHla.java simulate()"); coordinator c = new coordinator(this); c.initialize(); c.simulate(1000); } Snapshot of OUTPUT PACKET RECEIVED AT : HLA Router_node_8 Packet_from_0_to_8_cost_5.0_type_0_Class_b_nextHop_8 ------ PACKET HAS REACHED ITS DESTINATION with the info: I am NOT SUBSCRIBED TO THIS CLASS: Class b ...ignoring Packet_from_0_to_8_cost_5.0_type_0_Class_b_nextHop_8 ------ PACKET RECEIVED AT : HLA Router_node_3 Packet_from_8_to_3_cost_5.0_type_0_Class_d_nextHop_3 ------ PACKET HAS REACHED ITS DESTINATION with the info: I am NOT SUBSCRIBED TO THIS CLASS: Class c ...ignoring Packet_from_1_to_0_cost_5.0_type_0_Class_c_nextHop_0 ------ PACKET HAS REACHED ITS DESTINATION with the info: I am NOT SUBSCRIBED TO THIS CLASS: Class b ...ignoring Packet_from_0_to_8_cost_5.0_type_0_Class_b_nextHop_8 ------ PACKET HAS REACHED ITS DESTINATION with the info: I am NOT SUBSCRIBED TO THIS CLASS: Class d ...ignoring Packet_from_1_to_3_cost_5.0_type_0_Class_d_nextHop_3 ------ Terminated Normally at ITERATION 1001 ,time: 2.191101580114225 DEMO 2 Topology Designer • Attractive GUI • Change dynamically, • Number of nodes • Distance between nodes • Link Properties • Connection-density • Integrate with Demo 2 in progress • Run ListSelect.java main function

14. Simulated Topological setup Each Federate publishing 3 types of packets and subscribed to 3 different class of packets. The receiver federate attends only to the subscribed packets and ignores other packets. Experiment No. 1 Experiment No. 2 3 3 4 4 5 2 5 2 1 1 6 0 0 HLA Routers connected in P2P network and communicating without RTI Executive HLA Routers connected in P2P network and communicating THRU RTI Executive

15. P2P Run Time to Stabilize Thruput of Network INCREASE in Thruput Further INCREASE in Thruput Increase in Queue Lengths of Network due to Increase in Load Plot of Link Max Q length v/s Time Plot of Latency Max v/s Time Plot of Avg Thruput v/s Time Time to Stabilize after updating RTI Delay UPDATED Link Capacities Packets in Links UPDATED Load Packets in Routers

16. Centralized HLA: Broadcast Mode T= 4.461 sec RESPONSE Time SNAPSHOT Time Thruput Stabilization for RTI Links Resulting Q Length for RTI Length during Stabilization Packets in Links

17. RESPONSE Time Centralized HLA-Multicast mode Resulting Q Length for RTI Length during Stabilization Thruput Stabilization for RTI Links SNAPSHOT Time Link Capacity Reduced to accommodate Stabilized load

18. Other Simulation Experiments • Various other case studies were conducted • Benchmarking and Tuning of this DEVS model based on reported results for RTI latency • Details can be looked in the Project report.

19. Thanks for your Attention !!!