Seminar On “ OMNET++ Network Simulator”

1. Presented By: Saurav K Bengani Guided By: Dr. Andrew yang Seminar On“OMNET++ Network Simulator”

2. Topics Covered • Introduction • The NED Language • Background Mathematics • Case Study • References

3. Introduction OMNeT++ is an object-oriented modular discrete event network simulator. It can be used for: • Traffic modeling of telecommunication networks. • Protocol modeling. • Modeling queuing networks. • Modeling multiprocessors and other distributed hardware systems. • Validating hardware architectures. • Evaluating performance aspects of complex software systems.

4. The NED Language The NED language facilitates the modular description of a network. This means that a network description may consist of a number of component descriptions channels, simple/compound module types). The channels, simple modules and compound modules of one network description can be reused in another network description. A NED description can contain the following components, in arbitrary number or order: • Import directives • Channel definitions • Simple and compound module definitions • Network definitions

5. Background Math An OMNeT++ model consists of the following parts: • NED language topology description (.ned files) which describe the module structure with parameters, gates etc. NED files can be written using any text editor or the GNED graphical editor. • Message definitions (.msg files). You can define various message types and add data fields to them. • OMNeT++ will translate message definitions into full-fledged C++ classes. • Simple modules sources. They are C++ files, with .h/.cc suffix.

6. Background Math The simulation system provides the following components: • Simulation kernel: This contains the code that manages the simulation and the simulation class. • Library: It is written in C++, compiled and put together to form a library (a file with .a or .lib extension) • User interfaces: OMNeT++ user interfaces are used in simulation execution, to facilitate debugging, demonstration, or batch execution of simulations. There are several user interfaces, written in C++, compiled and put together into libraries (.a or .lib files).

7. Case Study (OCO) Fig. The Simulation process

8. Case Study Cont… • Use an OMNET++ program called “position collection” to generate 200, 250, 300, 350, 400, 450…nodes randomly. The user selects a node to be the base station in each configuration. The program will simulate the position collection phase. After the simulation, a text file is generated. The file contains node IDs, the base ID, and energy. • The processing program will read the text file, perform all processing and then generate result files for OCO. These files describe which nodes are deployed, the mission of each node in the network, the energy level, etc. • The OMNET++ program called OCO read these files and apply appropriate algorithm(s) for the simulations. The results of the simulations are text files, which contain information such as the detected points, the energy level of each node, and the time before first dead node. • Finally, MATLAB programs are used to analyze and evaluate the simulation results.

9. Simulation Result Leach Method DC Method OCO Method The above simulation result shows the network architecture for 250 nodes using DC, LEACH and OCO approaches. OCO employs less no. of nodes and it is very efficient.

10. References • Jan Heijmans, Alex Paalvast, and Robert van der Leij. Network simulation using the JAR compiler for the OMNeT++ simulation system. Technical report, Technical University of Budapest, Dept. of Telecommunications, 1995. • Gábor Lencse. Graphical network editor for OMNeT++. Master’s thesis, Technical University of Budapest, 1994. In Hungarian. • R. L. Bagrodia and M. Takai. Performance evaluation of conservative algorithms in parallel simulation languages. 11(4):395–414, 2000.

11. Thank You! Queries?