The Opportunistic Protocol Simulator, Light (OPSLite, pronounced as oops light!!!) is a set of
simulation models in OMNeT++ to simulate opportunistic networks. It has a
modular architecture where different protocols relevant to opportunistic networks
can be developed and plugged in. OPSLite is a scaled-down, light-weight version of
OPS, available at Github.
The following sections provide details of the models available and about the installation. Unlike OPS which was purely a command-line simulator, OPSLite is meant to be run in the OMNeT++ IDE and as well as on the command-line.
OPSLite requires OMNeT++ (version 5.4.1) and the INET Framework (version 4.0.0). The OMNeT++ simulator and the IDE can be found at the OMNeT++ site. Once the simulator and the IDE is installed, INET (version 4) has to be installed. It can be either installed through the IDE itself or by downloading from the INET site. Here are the 2 important prerequisites.
Install and build OMNeT++ (version 5.4.1)
Run the OMNet++ IDE and create a new workspace
Install and build INET (version 4.0.0) in the newly created workspace using option -
Help -> Install Simulation Models...or another means (e.g., at workspace creation, using a downloaded archive, etc.). Refer to https://inet.omnetpp.org if needed.
Once OMNeT++ IDE and INET4 are installed and built, follows the following steps to install OPSLite.
Run the OMNeT++ IDE, and import OPSLite (
File -> Import... -> Git -> Projects from Git -> Clone URI) into the OMNeT++ workspace (where INET is also a project). You can find the URI at the top of this page/project, in the right corner.
Tick INET as a referenced project in OPSLite (Right-click,
Properties -> Project References). Tick the exact INET version installed (remove other ticks)
Build the OPSLite project using -
Project -> Build Project(there should NOT be any errors or warnings after building)
To run simulation, check the
omnetpp.ini and the
OPSLiteNetwork.ned given (in
simulations folder), to create your own
scenario. Here are the basic steps
Run the OMNeT++ IDE and select the workspace where INET4 and OPSLite is installed and built
omnetpp.inito suit your scenario parameters
Select the OPSLite folder (the top most folder of the OPSLite project) and run using -
Run -> Run As -> OMNeT++ Simulation
The architecture of a node uses a number of protocol layers which can be configured
based on the scenario considered. The node model is defined in the
Generally, an OPSNode has the following protocol layers.
+------------------------+ | +------------------+ | | |Application Layer | | | | | | | +--------+---------+ | | | | | +--------+---------+ | | | Opportunistic | | | | Networking Layer | | | +--------+---------+ | | | | | +--------+---------+ | | | Link Adaptation | | | | Layer | | | +--------+---------+ | | | | | +--------+---------+ | | | Link Layer | | | | +--------------+ | | | | | Mobility | | | | | +--------------+ | | | +--------+---------+ | +-----------|------------+ |
Each of the above layers can be configured through their parameters to behave as required. Here are the models associated with each layer.
Application Layer consist of the
KHeraldAppapplication that classifies data items as liked and non-liked and injects them uniformly over the simulation period.
Opportunistic Networking Layer conist of the
KEpidemicRoutingLayerwhich is used to forward data in an opportunistic network
Link Adaptation Layer is a simple pass-through layer (
KLinkAdaptLayer) intended to be extended in the future.
Link Layer consist of the
KWirelessInterfacemodel that performs simple wireless communications.
Mobility implements the movements of the mobile nodes in the scenarios. It can use any of the mobility models available in the INET4 Framework. In OPSLite,
omnetpp.iniis configured to use BonnMotion (
BonnMotionMobility) mobility model. Some sample traces with SLAW mobility (
trace-slaw-01.movements, ...) are available in the
The following picture shows an example configuration of a node as seen in the OMNeT++ IDE.
Based on the standard configuration, the raw results (vector and scalar) collected after a simulation run
are located in the
simulation/results folder. Below is a brief (high-level) procedure to create your charts
using the IDE.
- In the
simulation/resultsfolder, create an
New -> Analysis File (anf))
- Add the created results files (
*.sca) to the created file
- Create datasets with the data you want plotted in every graph
- Plot them using an appropriate chart type (Line, Bar, etc.)
For more information, check Chapter 10 of the IDE User Guide
Available Results (Statistics)
There are a set of network-level results collected in every simulation run. Here are those results.
Statistics from the Application Layer
likedDataBytesReceivedSum- Liked data bytes received by all nodes
nonLikedDataBytesReceivedSum- Non-liked data bytes received by all nodes
duplicateDataBytesReceivedSum- Duplicate (liked & non-liked) data bytes received by all nodes
likedDataBytesReceivableByAllNodesSum- Liked data bytes that are possible to be received by all nodes
nonLikedDataBytesReceivableByAllNodesSum- Non-liked data bytes that are possible to be received by all nodes
avgDataDelay- Average delivery delay of data (liked and non-liked) by all nodes
deliveryRatio- Delivery ratio of data (liked and non-liked) by all nodes
Statistics from the Forwarding Layer
dataBytesReceivedSum- Data bytes received by all nodes in the network
sumVecBytesReceivedSum- Summary vectors bytes received by all nodes
dataReqBytesReceivedSum- Data request bytes received by all nodes
totalBytesReceivedSum- Total bytes received by all nodes
cacheBytesRemovedSum- Cache removals in bytes by all nodes
cacheBytesAddedSum- Cache additions in bytes by all nodes
cacheBytesUpdatedSum- Cache updates in bytes by all nodes
Statistics from the Wireless Interface Layer
neighbourhoodSize- Size of nodes in the wireless neighbourhood
The following graph shows the progress of the Delivery Ratio (
deliveryRatio) for two mobility traces based on the
SLAW mobility model. The graph has been created using the statistics graphing capability in OMNeT++ IDE.
Important Model Parameters
The following list provides some of the most important parameters of the different models
in OPSLite. All these parameters are configurable using the
omnetpp.ini. Not all parameters
are listed here. Please check the respective model's
.ned file to see all the parameters.
numNodes- The total number of nodes in the network
- Network level statistics
dataGenerationInterval- Defines how often (in seconds) a data gets injected into the network
dataSizeInBytes- The payload size in bytes of a data packet
maximumCacheSize- The size of the cache maintained by each node in bytes
maximumHopCount- The maximum hops that a data packet is allowed to travel (be forwarded) before being discarded
wirelessRange- The wireless range of each node's wireless interface
bandwidthBitRate- Communication bit rate of the wireless interface
INET - Documentation
Results processing in OMNeT++ IDE - Chapter 10 of the IDE User Guide
INET Mobility Models - Node Mobility
Problem: IMobility headers not found
- Description: When building OPSLite, the compilation fails, complaining about the inability to find INET mobility headers.
- Solution: Since OPSLite uses the mobility headers of INET, the referenced projects section (
Properties -> Project References) has to point to the exact INET version installed in your workspace. Sometimes, INET is installed as
inet. So, make sure that the right INET entry is ticked. Untick all other unwanted projects.
Problem: Undefined symbols when building OPSLite on Windows
- Description: With OMNeT++ 5.4.1 IDE on Windows, the building fails with undefined symbols pointing to the IMobility interface used. We found this to be due to OMNeT++ being setup by default to use the
- Solution: Change the configure.user file to use gcc by setting "PREFER_CLANG=no" and rebuilding OMNeT++ and all the models installed (including INET). Check Install Guide for further information.
Questions or Comments
If you have any comments or suggestions, we will be very glad to hear them. Please write to us using any of the e-mail adresses below.