VanetMobiSim – Vehicular Ad hoc Network mobility
extension to the CanuMobiSim framework
Copyright © 2005-2006 Institut Eurécom/Politecnico di Torino
Contact
Jérôme Härri
Institut Eurécom
Department of Mobile Communications
06904 SophiaAntipolis, France
E-mail: haerri@eurecom.fr
Marco Fiore
Politecnico di Torino
Dipartimento di Elettronica
Corso Duca degli Abruzzi 24, Torino, Italy
E-mail: marco.fiore@polito.it
1
Contents
1. Introduction ........................................................................................................................ 3
2. Installation .......................................................................................................................... 3
3. Format of Simulation Scenario ......................................................................................... 4
3.1 Specifying a Simulation Area .................................................................................... 4
3.2 Adding a Global Extension to Simulation ................................................................ 4
3.3 Adding a Node to Simulation ..................................................................................... 5
3.3.1 Specifying the Node’s Initial Position .............................................................. 5
3.4 Adding a Group of Nodes to Simulation .................................................................. 6
4. Globally Specified Extensions ........................................................................................... 7
4.1 Spatial Environment .................................................................................................. 7
4.1.1 Specifying Multi-lane Roads ............................................................................ 8
4.2 Traffic Lights ............................................................................................................. 8
4.3 Graph Representation of Movement Area .............................................................. 9
4.3.1 Specifying a Graph’s Vertex .......................................................................... 10
4.3.2 Specifying a Graph’s Edge ............................................................................ 10
4.4 Space Graph ............................................................................................................. 11
4.4.1 Specifying the Space Graph Clustering ........................................................ 12
4.4.1.1 Specifying a Cluster’s Characterization .............................................. 12
4.5 Producing an Image of the Spatial Model ............................................................. 13
4.6 Producing Simulator-Independent Mobility Traces............................................. 13
4.7 GDF Writer .............................................................................................................. 14
4.8 Parser for TIGER Data Sources ............................................................................ 14
4.8.1 Speed Limits File ............................................................................................ 15
4.8 Parser for GDF Data Sources ................................................................................. 16
5. Node-Specific Extensions (Mobility Models) .................................................................16
5.1 Simulating Node’s Motion using the IDM_IM ......................................................16
5.2 Simulating Node’s Motion using the IDM_LC Model ......................................... 17
2
1. Introduction
The Vehicular Ad Hoc Networks Mobility Simulator (VanetMobiSim) is a set of extensions to
CanuMobiSim, a framework for user mobility modeling used by the CANU (Communication in Ad
Hoc Networks for Ubiquitous Computing) Research Group [1], University of Stuttgart. The framework
includes a number of mobility models, as well as parsers for geographic data sources in various
formats, and a visualization module. The framework is easily extensible. It is based on the concept of
pluggable modules.
The set of extensions provided by VanetMobiSim consists mainly on a vehicular spatial model using
GDF-compliant data structures, and a set of vehicular-oriented mobility models. The vehicular spatial
model is composed of spatial elements, their attributes and the relationships linking these spatial
elements in order to describe vehicular areas. The spatial model is created from topological data
obtained in four different ways:
• User-defined – The user defines a set of vertices and edges composing the backbone of the
vehicular spatial model.
• Random – The backbone is randomly generated using the Voronoi tessellations.
• Geographic Data Files (GDF) – Backbone data is obtained from GDF files.
• TIGER/line Files – Similar to the previous one, but based on the TIGER/line files from the US
Census Bureau.
Any one of those methods MUST be loaded AFTER the Spatial Model, as it controls all data
describing the topology. Then, it adds vehicular specific spatial elements such as multi-lane and multi-
flow roads, stop signs and traffic lights.
The main component of the vehicular oriented model is the support of a microscopic level mobility
model named “Intelligent Driving Model with Intersection Management (IDM_IM)” describing
perfectly car-to-car and intersection managements. In the Intelligent Driving Model with Lane
Changing (IDM_LC), we also included an overtaking model (MOBIL), which interacts with IDM_IM
to manage lane changes and vehicle accelerations and decelerations. A Spatial Environment MUST be
loaded for user-oriented and vehicular oriented mobility models to work. A spatial Environment MAY
be loaded for all other mobility models specified in CanuMobiSim.
2. Installation
The framework’s binary files are compressed to a jar-archive. To start the application, you need the
JAVA Runtime Environment (v1.3 or later) [10] and the Xerces2 Java Parser library (v2.4 or later)
[19]. If you work with geographic data in AWML or GDF format, you also need the GeoTransform
package [7].
To launch the framework, change to the directory with framework’s files and type:
java -jar VanetMobiSim.jar [scenario.xml]
The framework simulates user mobility according to a simulation scenario. On exit, it returns one of
the following codes:
• 0 – successful execution,
• 1 – simulation aborted, error message is written to System.err
3
3. Format of Simulation Scenario
The simulation scenario for VanetMobiSim is similar to CanuMobiSim’s. It is defined in XML format.
In the notation below, tags or attributes appearing in square brackets (e.g.,
[<sample>] are optional.
3.1 Specifying a Simulation Area
A simulation area is specified using the <universe> tag.
<universe>
[<dimx>dimension</dimx>]
[<dimy>dimension</dimy>]
[<step>step</step>]
[<seed>seed</seed>]
[<extension>extension_parameters</extension>]
[<node>node_parameter</node>]
[<nodegroup>nodegroup_parameters</nodegroup>]
</universe>
•
dimx – specifies the x-dimension of the simulation are (in meters). Only used in the scenarios
with rectangular-bounded simulation areas.
•
dimy – specifies the y-dimension of the simulation are (in meters). Only used in the scenarios
with rectangular-bounded simulation areas.
•
step – specifies the duration of single simulation time-step (in s). If omitted, the value of 1 ms is
used.
• seed – specifies the seed of the random number generation used by VanetMobiSim.
•
extension – adds an instance of a global extension to the simulation.
• node – adds a node to the simulation.
•
nodegroup – adds a group of nodes to the simulation.
3.2 Adding a Global Extension to Simulation
An instance of global extension is added using the <extension> tag.
<extension class=”class_name” [name=”instance_name”]>
[extension_parameters]
</extension>
•
class – specifies the name of class to be instantiated. The class must be derived from
de.uni_stuttgart.informatik.canu.mobisim.core.ExtensionModule and be accessible by JVM.
•
name – specifies the name of class instance. Used to uniquely identify and reference the
instance in simulation. Most of extensions have their default name predefined.
4
Example:
<extension class="de.uni_stuttgart.informatik.canu.spatialmodel.simulations.TimeSimulation" param="3600.0"/>
3.3 Adding a Node to Simulation
A node is added to simulation using the
<node> tag.
<node [class=”class_name”] id=”node_id”>
[<position>position_parameters</position>]
[<type>type_of_node</position>]
[<extension>extension_parameters</extension>]
</node>
•
class – specifies the node’s class name. The class must be derived from
de.uni_stuttgart.informatik.canu.mobisim.core.Node and be accessible by the JVM. If omitted,
de.uni_stuttgart.informatik.canu.mobisim.core.Node is used\
•
id – specifies the node’s id. Used to uniquely identify and reference the node in simulation
•
position – specifies the node’s initial position
•
type – specifies the node’s type. The user can choose among four different types of nodes: ped-
car-truck-bus. If omitted, the value “any” is taken by default.
•
extension – adds an extension to the node (e.g., instance of mobility model).
Example:
< node id="#0">
<position random="true”/>
<type="ped”/>
<extension class="de.uni_stuttgart.informatik.canu.mobisim.mobilitymodels.RandomWaypointWalk">
<minspeed>0.56</minspeed>
<maxspeed>1.39</maxspeed>
<minstay>120</minstay>
<maxstay>600</maxstay >
</extension>
</node>
3.3.1 Specifying the Node’s Initial Position
The node’s initial position is specified using the <position> tag.
<position [graph=”graph_instance_name”] [random=”is_random”]>
[<x>x_value</x>]
[<y>y_value</y>]
</position>
•
graph – if the position belongs to the graph, specifies the name of graph instance (class
de.uni_stuttgart.informatik.canu.mobisim.extensions.Graph). Used by the graph-based mobility model.
•
random – specifies that the position must be chosen randomly. The value is of Boo-lean type. If
the position belongs to a graph, it will be chosen randomly from the graph vertices.
5
