Website build mosaic-website/main-38
diff --git a/contribution/index.html b/contribution/index.html
index fe3315e..e142356 100644
--- a/contribution/index.html
+++ b/contribution/index.html
@@ -822,11 +822,25 @@
     <div class="col-md-12">
       <h2 id="issues">Issues</h2>
 <p>You are more than welcomed to report bugs or suggest enhancements on our 
-<a href="https://github.com/eclipse/mosaic" target="_blank" rel="noopener">GitHub repository</a>.
+
+
+
+
+<a href="https://github.com/eclipse/mosaic" target="_blank" rel="noopener">
+    GitHub repository
+</a>
+.
 Before creating a new issue, please check if the problem or feature was not reported already by someone else.</p>
 <p>When reporting bugs, please follow the guidelines
 proposed by 
-<a href="https://bugs.eclipse.org/bugs/page.cgi?id=bug-writing.html" target="_blank" rel="noopener">Eclipse</a>:</p>
+
+
+
+
+<a href="https://bugs.eclipse.org/bugs/page.cgi?id=bug-writing.html" target="_blank" rel="noopener">
+    Eclipse
+</a>
+:</p>
 <ul>
 <li>Be precise</li>
 <li>Be clear - explain it so others can reproduce the bug</li>
@@ -846,9 +860,23 @@
 <ul>
 <li>Create a user account for the Eclipse Foundation. If you don&rsquo;t already have such an account, please register
 
-<a href="https://dev.eclipse.org/site_login/createaccount.php" target="_blank" rel="noopener">on the Eclipse web site</a>.</li>
+
+
+
+
+<a href="https://dev.eclipse.org/site_login/createaccount.php" target="_blank" rel="noopener">
+    on the Eclipse web site
+</a>
+.</li>
 <li>Sign the 
-<a href="https://www.eclipse.org/legal/CLA.php" target="_blank" rel="noopener">Contributor License Agreement</a> (see <code>My Account/Contributor License Aggreement</code> tab in your profile.)</li>
+
+
+
+
+<a href="https://www.eclipse.org/legal/CLA.php" target="_blank" rel="noopener">
+    Contributor License Agreement
+</a>
+ (see <code>My Account/Contributor License Aggreement</code> tab in your profile.)</li>
 <li>Add your GitHub username to your Eclipse Foundation profile.</li>
 </ul>
 <h2 id="contribute">Contribute</h2>
@@ -856,7 +884,14 @@
 To share contributions with us,  create a GitHub pull request following the steps below. All your commits
 have to be <em>Signed-off</em> (<code>-s</code>) using the email address used for your Eclipse account.
 More details can be found 
-<a href="https://wiki.eclipse.org/Development_Resources/Contributing_via_Git" target="_blank" rel="noopener">here</a>.</p>
+
+
+
+
+<a href="https://wiki.eclipse.org/Development_Resources/Contributing_via_Git" target="_blank" rel="noopener">
+    here
+</a>
+.</p>
 <pre><code>git commit -s -m &quot;This is a message&quot;  
 </code></pre>
 <p>Make your changes by following those steps:</p>
@@ -900,7 +935,14 @@
 However, the look of our codebase needs to be consistent and therefore the following conventions must be followed.</p>
 <h3 id="code-style">Code Style</h3>
 <p>Eclipse MOSAIC follows the 
-<a href="https://github.com/google/styleguide" target="_blank" rel="noopener">Google Java Style Guide</a>. Please stick to those conventions to
+
+
+
+
+<a href="https://github.com/google/styleguide" target="_blank" rel="noopener">
+    Google Java Style Guide
+</a>
+. Please stick to those conventions to
 get your contribution accepted.</p>
 <ul>
 <li>No tab characters, 4-space indentation!</li>
@@ -1041,7 +1083,14 @@
  */
 </code></pre>
 <p>If this is your first contribution, please also add your Copyright information to 
-<a href="https://github.com/eclipse/mosaic/blob/main/NOTICE.md" target="_blank" rel="noopener">NOTICE.md</a>.</p>
+
+
+
+
+<a href="https://github.com/eclipse/mosaic/blob/main/NOTICE.md" target="_blank" rel="noopener">
+    NOTICE.md
+</a>
+.</p>
 
     </div>
     
diff --git a/docs/api_docs/index.html b/docs/api_docs/index.html
index 8489e46..cab7011 100644
--- a/docs/api_docs/index.html
+++ b/docs/api_docs/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
diff --git a/docs/building_scenarios/index.html b/docs/building_scenarios/index.html
index a622976..24b59cb 100644
--- a/docs/building_scenarios/index.html
+++ b/docs/building_scenarios/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1093,11 +1101,39 @@
 </code></pre>
 <p>While the <code>*.net.xml</code> is a mandatory file to be placed within the <code>sumo</code> directory, the <code>*.rou.xml</code> is automatically generated
 by the SumoAmbassador when the simulation is started. More information about the configuration of SUMO can be found
-<a href="/mosaic/docs/simulators/application_simulator#configuration" title="here">here</a>.</p>
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/#configuration">
+    here
+</a>
+.</p>
 <h2 id="applications-and-mapping">Applications and Mapping</h2>
 <div class="alert alert-tip">
   <div>
-<p>Read the detailed documentation of the <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/" title="Mapping Configuration">Mapping Configuration</a>.</p>
+<p>Read the detailed documentation of the <a href="/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>.</p>
   </div>
 </div>
 <h3 id="vehicles">Vehicles</h3>
@@ -1197,9 +1233,44 @@
     ]
 }
 </code></pre>
-<p>More information on the mapping configuration can be found (<a href="/mosaic/docs/simulators/application_simulator#configuration" title="here">here</a>.</p>
+<p>More information on the mapping configuration can be found (
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/#configuration">
+    here
+</a>
+.</p>
 <p>For more information about how SUMO traffic lights work please refer to 
-<a href="https://sumo.dlr.de/docs/Simulation/Traffic_Lights.html" target="_blank" rel="noopener">SUMO Traffic Lights</a>.</p>
+
+
+
+
+<a href="https://sumo.dlr.de/docs/Simulation/Traffic_Lights.html" target="_blank" rel="noopener">
+    SUMO Traffic Lights
+</a>
+.</p>
 <!--
 For Phabmacs, one should create a separate configuration file containing the description of traffic light groups and traffic light programs. 
 
@@ -1315,11 +1386,95 @@
 -->
 <p>The <code>application</code> folder furthermore needs a generated database file <code>&lt;scenarioName&gt;.db</code> . This database file
 contains information about the road network (road topology) and all routes the vehicles can drive on. This file
-is usually generated by the tool <code>scenario-convert</code>, which is described <a href="/mosaic/docs/building_scenarios/scenario_convert" title="here">here</a> in detail.</p>
+is usually generated by the tool <code>scenario-convert</code>, which is described 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/scenario_convert/">
+    here
+</a>
+ in detail.</p>
 <h2 id="communication-simulator">Communication Simulator</h2>
 <p>The configuration of the communication parameters are usually not dependent from the location of the road network. Therefore,
-most of the required files can be extracted from other scenarios, such <a href="/mosaic/tutorials/barnim_basic/" title="Barnim">Barnim</a> or
-<a href="/mosaic/tutorials/tiergarten/" title="Tiergarten">Tiergarten</a>.
+most of the required files can be extracted from other scenarios, such 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/barnim_basic/">
+    Barnim
+</a>
+ or
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/tiergarten/">
+    Tiergarten
+</a>
+.
 Depending on the simulator you will need to configure the geographic extend of the simulation
 area. You can find that data in the traffic simulators network file, e.g. SUMOs <code>*.net.xml</code> contains this
 information in the <code>convBoundary</code> attribute of the location tag.</p>
@@ -1330,10 +1485,122 @@
 <li>The <strong>SNS</strong> also comes without an additional expansion definition.</li>
 </ul>
 <p>Further information on the communication simulators can be found in:
-<br><a href="/mosaic/docs/simulators/network_simulator_sns" title="Eclipse MOSAIC SNS">Eclipse MOSAIC SNS</a>
-<br><a href="/mosaic/docs/simulators/network_simulator_cell" title="Eclipse MOSAIC Cell">Eclipse MOSAIC Cell</a>
-<br><a href="/mosaic/docs/simulators/network_simulator_omnetpp" title="OMNeT&#43;&#43;">OMNeT&#43;&#43;</a>
-<br><a href="/mosaic/docs/simulators/network_simulator_ns3" title="ns-3">ns-3</a></p>
+<br>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_sns/">
+    Eclipse MOSAIC SNS
+</a>
+
+<br>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_cell/">
+    Eclipse MOSAIC Cell
+</a>
+
+<br>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_omnetpp/">
+    OMNeT++
+</a>
+
+<br>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_ns3/">
+    ns-3
+</a>
+</p>
 
           </div>
 
diff --git a/docs/building_scenarios/index.xml b/docs/building_scenarios/index.xml
index 997e049..0e4b45f 100644
--- a/docs/building_scenarios/index.xml
+++ b/docs/building_scenarios/index.xml
@@ -20,8 +20,8 @@
       <description>&lt;div class=&#34;alert alert-extended&#34;&gt;
   &lt;span class=&#34;extended-icon&#34; style=&#34;background-image: url(/mosaic/img/alert-extended.svg)&#34;&gt;&lt;/span&gt;
   &lt;div&gt;
-  &lt;p&gt;The tool &lt;strong&gt;scenario-convert&lt;/strong&gt; is part of &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/download/#overview&#34; title=&#34;MOSAIC Extended&#34;&gt;MOSAIC Extended&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
-&lt;p&gt;However, you can use scenario-convert &lt;strong&gt;for free&lt;/strong&gt; to generate scenarios which are executable with Eclipse MOSAIC. &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/https://www.dcaiti.tu-berlin.de/research/simulation/download/&#34; title=&#34;Get it here&#34;&gt;Get it here&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
+  &lt;p&gt;The tool &lt;strong&gt;scenario-convert&lt;/strong&gt; is part of &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/download#overview&#34;&gt;MOSAIC Extended&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
+&lt;p&gt;However, you can use scenario-convert &lt;strong&gt;for free&lt;/strong&gt; to generate scenarios which are executable with Eclipse MOSAIC. &lt;strong&gt;&lt;a href=&#34;https://www.dcaiti.tu-berlin.de/research/simulation/download/&#34;&gt;Get it here&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
 &lt;div style=&#34;text-align: center;&#34;&gt;
@@ -41,11 +41,43 @@
 routes or  build own routes via route generation tools (e.g. DUAROUTER by SUMO).&lt;/p&gt;
 &lt;p&gt;This chapter intends to highlight the most common workflows for the work with &lt;code&gt;scenario-convert&lt;/code&gt;.
 We will be using 
-    &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz.osm&#34; title=&#34;steglitz.osm&#34;&gt;steglitz.osm&lt;/a&gt; OSM-file for most of the
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz.osm&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    steglitz.osm
+&lt;/a&gt;
+ OSM-file for most of the
 use cases So feel free to follow along with the steps to get a better understanding on how the &lt;code&gt;scenario-convert&lt;/code&gt;-script functions.&lt;/p&gt;
 &lt;div class=&#34;alert alert-note&#34;&gt;
   &lt;div&gt;
-&lt;p&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/#reference-documentation-for-scenario-convert%22&#34; title=&#34;Here&#34;&gt;Here&lt;/a&gt; you can find a complete reference to all options scenario-convert offers.&lt;/p&gt;
+&lt;p&gt;&lt;a href=&#34;#reference-documentation-for-scenario-convert&#34;&gt;Here&lt;/a&gt; you can find a complete reference to all options scenario-convert offers.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
 
@@ -129,8 +161,22 @@
 &lt;li&gt;First the &lt;code&gt;steglitz.db&lt;/code&gt; will be created using the &lt;code&gt;steglitz.osm&lt;/code&gt;-file.&lt;/li&gt;
 &lt;li&gt;The &lt;code&gt;steglitz.db&lt;/code&gt; will be used to create &lt;code&gt;steglitz.con.xml&lt;/code&gt;, &lt;code&gt;steglitz.edg.xml&lt;/code&gt; and &lt;code&gt;steglitz.nod.xml&lt;/code&gt;, which are files used by SUMO.&lt;/li&gt;
 &lt;li&gt;
-&lt;a href=&#34;https://sumo.dlr.de/wiki/NETCONVERT&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;SUMO Netconvert&lt;/a&gt; is used to create &lt;code&gt;steglitz.net.xml&lt;/code&gt;, which is a 
-&lt;a href=&#34;https://sumo.dlr.de/wiki/Networks/SUMO_Road_Networks&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;network representation&lt;/a&gt; in SUMO.&lt;/li&gt;
+
+
+
+
+&lt;a href=&#34;https://sumo.dlr.de/wiki/NETCONVERT&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    SUMO Netconvert
+&lt;/a&gt;
+ is used to create &lt;code&gt;steglitz.net.xml&lt;/code&gt;, which is a 
+
+
+
+
+&lt;a href=&#34;https://sumo.dlr.de/wiki/Networks/SUMO_Road_Networks&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    network representation
+&lt;/a&gt;
+ in SUMO.&lt;/li&gt;
 &lt;li&gt;Now the SUMO-configuration &lt;code&gt;steglitz.sumo.cfg&lt;/code&gt; is written.&lt;/li&gt;
 &lt;li&gt;Afterwards the &lt;code&gt;mapping_config.json&lt;/code&gt; and &lt;code&gt;scenario_config.json&lt;/code&gt; are created and all files are moved to the right place.
 In the &lt;code&gt;scenario_config.json&lt;/code&gt; values like the center coordinate will automatically be set using data from the SUMO related files.&lt;/li&gt;
@@ -306,7 +352,19 @@
 &lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;java -jar scenario-convert.jar --osm2mosaic -i steglitz.osm -o --generate-routes
 --route-begin-node-id 267350668 --route-end-node-id 313139970 --number-of-routes 3
 &lt;/code&gt;&lt;/pre&gt;
-&lt;p&gt;See &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/#reference-documentation-for-scenario-convert&#34; title=&#34;below&#34;&gt;below&lt;/a&gt; for all command line options.&lt;/p&gt;
+&lt;p&gt;See 
+
+
+
+
+
+  
+  
+
+&lt;a href=&#34;#reference-documentation-for-scenario-convert&#34;&gt;
+    below
+&lt;/a&gt;
+ for all command line options.&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Conlusion&lt;/strong&gt;&lt;br&gt;
 This wraps up one of the main workflows with the scenario-convert-script.
 A quick reminder on what we achieved:&lt;/p&gt;
@@ -317,17 +375,112 @@
 &lt;li&gt;Calculated routes between two coordinates.&lt;/li&gt;
 &lt;/ul&gt;
 &lt;p&gt;With all of this you can now start further developing your scenario. For a more detailed description on the next steps
-please have a look &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/&#34; title=&#34;here (Simulation Scenarios)&#34;&gt;here (Simulation Scenarios)&lt;/a&gt; and
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/&#34; title=&#34;here (Application Development)&#34;&gt;here (Application Development)&lt;/a&gt;.&lt;br&gt;
+please have a look 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/&#34;&gt;
+    here (Simulation Scenarios)
+&lt;/a&gt;
+ and
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/&#34;&gt;
+    here (Application Development)
+&lt;/a&gt;
+.&lt;br&gt;
 While this is the &amp;lsquo;happy world&amp;rsquo; workflow it is often necessary to manually adapt routes and
 insert them into your scenario. The following workflow
 will explain how that is done and you will also get a more detailed overview of the scenario-convert-functions.&lt;/p&gt;
 &lt;h2 id=&#34;importing-routes-to-your-scenario&#34;&gt;Importing Routes to your scenario&lt;/h2&gt;
 &lt;p&gt;As mentioned above your routes won&amp;rsquo;t always be created by the scenario-convert script. We generated some routes
 for the steglitz-scenario using SUMO&amp;rsquo;s 
-&lt;a href=&#34;http://sumo.dlr.de/wiki/DUAROUTER&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;duarouter&lt;/a&gt;, which you can find
 
-    &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz.rou.xml&#34; title=&#34;here&#34;&gt;here&lt;/a&gt;. We&amp;rsquo;ll start with only the &lt;code&gt;steglitz.osm&lt;/code&gt; and
+
+
+
+&lt;a href=&#34;http://sumo.dlr.de/wiki/DUAROUTER&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    duarouter
+&lt;/a&gt;
+, which you can find
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz.rou.xml&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    here
+&lt;/a&gt;
+. We&amp;rsquo;ll start with only the &lt;code&gt;steglitz.osm&lt;/code&gt; and
 &lt;code&gt;steglitz.rou.xml&lt;/code&gt; files:&lt;/p&gt;
 &lt;pre&gt;&lt;code class=&#34;language-plaintext&#34;&gt;└─ &amp;lt;working-directory&amp;gt;
    ├─ steglitz.osm
@@ -411,9 +564,73 @@
 &lt;p&gt;A list of all attached files in this chapter:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;
-    &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz.osm&#34; title=&#34;Steglitz OSM-file&#34;&gt;Steglitz OSM-file&lt;/a&gt;&lt;/li&gt;
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz.osm&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    Steglitz OSM-file
+&lt;/a&gt;
+&lt;/li&gt;
 &lt;li&gt;
-    &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz.rou.xml&#34; title=&#34;Steglitz Route-file&#34;&gt;Steglitz Route-file&lt;/a&gt;&lt;/li&gt;
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz.rou.xml&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    Steglitz Route-file
+&lt;/a&gt;
+&lt;/li&gt;
 &lt;/ul&gt;
 &lt;h2 id=&#34;reference-documentation-for-scenario-convert&#34;&gt;Reference documentation for scenario-convert&lt;/h2&gt;
 &lt;h3 id=&#34;usage-of-scenario-convert&#34;&gt;Usage of scenario-convert&lt;/h3&gt;
@@ -519,7 +736,14 @@
 in order to define speeds for ways, which do not have a maxspeeds-tag defined. For this purpose use the
 option &lt;code&gt;--osm-speeds-file &amp;lt;FILE&amp;gt;&lt;/code&gt;. In the speed properties file, for each way type a speed value can
 be defined, according to the OSM 
-&lt;a href=&#34;http://wiki.openstreetmap.org/wiki/Key:highway&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&lt;code&gt;highway&lt;/code&gt;&lt;/a&gt; key.&lt;/p&gt;
+
+
+
+
+&lt;a href=&#34;http://wiki.openstreetmap.org/wiki/Key:highway&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    &lt;code&gt;highway&lt;/code&gt;
+&lt;/a&gt;
+ key.&lt;/p&gt;
 &lt;pre&gt;&lt;code&gt;# the unit the speed values are defined in [kmh, ms]
 speed.unit = kmh
 
@@ -568,9 +792,93 @@
       <guid>https://www.eclipse.org/mosaic/docs/building_scenarios/scenario_configuration/</guid>
       <description>&lt;p&gt;This chapter aims to give you a brief overview of additional simulators and visualizers that can be used with Eclipse MOSAIC.
 We will continue with the tutorial-style explanations following up on the Steglitz-example from the
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/scenario_convert&#34; title=&#34;previous chapter&#34;&gt;previous chapter&lt;/a&gt;. For more detailed explanations of the configurations have a
-look at &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/&#34; title=&#34;this chapter&#34;&gt;this chapter&lt;/a&gt;.&lt;br&gt;
-If you already played with the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/barnim_basic/&#34; title=&#34;Barnim&#34;&gt;Barnim&lt;/a&gt;-tutorial you probably noticed, that it contains far
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/scenario_convert/&#34;&gt;
+    previous chapter
+&lt;/a&gt;
+. For more detailed explanations of the configurations have a
+look at 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/&#34;&gt;
+    this chapter
+&lt;/a&gt;
+.&lt;br&gt;
+If you already played with the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/barnim_basic/&#34;&gt;
+    Barnim
+&lt;/a&gt;
+-tutorial you probably noticed, that it contains far
 more folders in the scenario structure compared to the Steglitz example. Those additional directories contain
 configurations for various simulators.&lt;/p&gt;
 &lt;pre&gt;&lt;code class=&#34;language-plaintext&#34;&gt;└─ Barnim
@@ -601,9 +909,69 @@
    └─ scenario_config.json .................. Basic configuration of the simulation scenario
 &lt;/code&gt;&lt;/pre&gt;
 &lt;p&gt;If you have a look in the 
-    &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz_mapping_config.json&#34; title=&#34;mapping_config.json&#34;&gt;mapping_config.json&lt;/a&gt;,
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz_mapping_config.json&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    mapping_config.json
+&lt;/a&gt;
+,
 you can see that the scenario-convert script automatically assigns cars to the three routes created. You can use this
-file as a blueprint for your own scenario, have a look &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/#applications-and-mapping&#34; title=&#34;here&#34;&gt;here&lt;/a&gt;
+file as a blueprint for your own scenario, have a look 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/#applications-and-mapping&#34;&gt;
+    here
+&lt;/a&gt;
+
 to get more details on possible adaptions.&lt;br&gt;
 Below is a short video of the scenario displayed in the SUMO-GUI. We marked the three different routes the cars
 follow.&lt;/p&gt;
@@ -623,11 +991,39 @@
 
 
 &lt;video controls &gt;
-  &lt;source src=&#34;https://www.eclipse.org/mosaic/docs/building_scenarios/images/steglitz_routes.mp4&#34; type=&#34;video/mp4&#34;&gt;
+  &lt;source src=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/images/steglitz_routes.mp4&#34; type=&#34;video/mp4&#34;&gt;
 &lt;/video&gt;
 &lt;h2 id=&#34;communication-simulators-cell-ns3-omnetpp-sns&#34;&gt;Communication Simulators (cell, ns3, omnetpp, sns)&lt;/h2&gt;
 &lt;p&gt;We won&amp;rsquo;t implement any functionality for the steglitz example here but rather have a look at the
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/barnim_basic/&#34; title=&#34;Barnim&#34;&gt;Barnim&lt;/a&gt;-tutorial. In the &lt;code&gt;scenario_config.json&lt;/code&gt; of the Barnim scenario you can see where the
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/barnim_basic/&#34;&gt;
+    Barnim
+&lt;/a&gt;
+-tutorial. In the &lt;code&gt;scenario_config.json&lt;/code&gt; of the Barnim scenario you can see where the
 communication simulators are activated:&lt;/p&gt;
 &lt;pre&gt;&lt;code class=&#34;language-json&#34;&gt;&amp;quot;federates&amp;quot;: {
     &amp;quot;cell&amp;quot;: false,
@@ -636,12 +1032,152 @@
     &amp;quot;sns&amp;quot;: true
 }
 &lt;/code&gt;&lt;/pre&gt;
-&lt;p&gt;Our &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/&#34; title=&#34;tutorials&#34;&gt;tutorials&lt;/a&gt; and &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/additional_examples/&#34; title=&#34;additional examples&#34;&gt;additional examples&lt;/a&gt; demonstrate use cases for
+&lt;p&gt;Our 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/&#34;&gt;
+    tutorials
+&lt;/a&gt;
+ and 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/additional_examples/&#34;&gt;
+    additional examples
+&lt;/a&gt;
+ demonstrate use cases for
 communication usages and you should have a look at them if you are uncertain where to start. Furthermore we
-recommend copying the configuration-files for the simulator you are going to use from the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/barnim_basic/&#34; title=&#34;Barnim scenario&#34;&gt;Barnim scenario&lt;/a&gt;. It
+recommend copying the configuration-files for the simulator you are going to use from the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/barnim_basic/&#34;&gt;
+    Barnim scenario
+&lt;/a&gt;
+. It
 contains the most complete configurations and is well maintained.&lt;br&gt;
-If you are an expert with one of the external network simulators (&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_ns3&#34; title=&#34;ns3&#34;&gt;ns3&lt;/a&gt;,
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_omnetpp&#34; title=&#34;OMNeT&amp;#43;&amp;#43;&#34;&gt;OMNeT&amp;#43;&amp;#43;&lt;/a&gt;) the Barnim scenario will also give
+If you are an expert with one of the external network simulators (
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_ns3/&#34;&gt;
+    ns3
+&lt;/a&gt;
+,
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_omnetpp/&#34;&gt;
+    OMNeT++
+&lt;/a&gt;
+) the Barnim scenario will also give
 you an overview on how to configure those.&lt;/p&gt;
 &lt;h2 id=&#34;other-simulators&#34;&gt;Other Simulators&lt;/h2&gt;
 &lt;p&gt;Here we&amp;rsquo;ll discuss two simulators integrated with Eclipse MOSAIC and their use-cases, namely the &lt;code&gt;Event Server&lt;/code&gt; and the
@@ -651,16 +1187,108 @@
 an event server is used to simulate an icy area, which is then noticed by the sensor of a weather server RSU.&lt;br&gt;
 Every defined event requires a type, a defined geographical area (e.g. circular, rectangular), the strength and a time frame. Have a look
 at the 
-    &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/eventserver_config.json&#34; title=&#34;eventserver_config.json&#34;&gt;eventserver_config.json&lt;/a&gt; to see how this can be
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/eventserver_config.json&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    eventserver_config.json
+&lt;/a&gt;
+ to see how this can be
 configured. If you want to use the event server make sure to have it enabled in the &lt;code&gt;scenario_config.json&lt;/code&gt;.&lt;/p&gt;
 &lt;h3 id=&#34;battery&#34;&gt;Battery&lt;/h3&gt;
 &lt;p&gt;The battery simulator is used to simulate electric vehicles. It offers a lot of customization, because you can
 dynamically load your own battery, vehicle and environment models. Have a look a the 
-    &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/battery_config.json&#34; title=&#34;battery_config.json&#34;&gt;battery_config.json&lt;/a&gt;, taken from the Barnim scenario.
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/battery_config.json&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    battery_config.json
+&lt;/a&gt;
+, taken from the Barnim scenario.
 The three models used are included with Eclipse MOSAIC and you can freely use them.&lt;/p&gt;
 &lt;h2 id=&#34;output&#34;&gt;Output&lt;/h2&gt;
 &lt;p&gt;There are various options to generate output results of your simulations (see the
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/visualization/filevis&#34; title=&#34;visualization chapter&#34;&gt;visualization chapter&lt;/a&gt;).&lt;/p&gt;
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/visualization/filevis/&#34;&gt;
+    visualization chapter
+&lt;/a&gt;
+).&lt;/p&gt;
 &lt;p&gt;The first step is to create a file called &lt;code&gt;output_config.xml&lt;/code&gt; in a new directory called &lt;code&gt;output&lt;/code&gt;.
 If you used the scenario-convert tool the file should be generated automatically.&lt;/p&gt;
 &lt;pre&gt;&lt;code class=&#34;language-plaintext&#34;&gt;└─ steglitz
@@ -683,8 +1311,7 @@
 &lt;federate id=&#34;output&#34; active=&#34;true&#34;/&gt;
 ```
 
-Now we have to configure the statistics visualizer itself. This 
-    &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/files/steglitz_visualizer_config.xml&#34; title=&#34;visualizer_config.xml&#34;&gt;visualizer_config.xml&lt;/a&gt; contains the basic
+Now we have to configure the statistics visualizer itself. This [visualizer_config.xml](/docs/building_scenarios/files/steglitz_visualizer_config.xml) contains the basic
 configuration in order to calculate the average travel times for the vehicles. If you want to make adaptions, please
 refer to [statistics visualizer](/docs/visualization/statistics).  
 Go ahead and run the simulation one more time. Afterwards the log-directory should contain a file called 
diff --git a/docs/building_scenarios/scenario_configuration/index.html b/docs/building_scenarios/scenario_configuration/index.html
index a1df2fb..c323b08 100644
--- a/docs/building_scenarios/scenario_configuration/index.html
+++ b/docs/building_scenarios/scenario_configuration/index.html
@@ -33,7 +33,7 @@
   
     
   
-  <meta name="description" content="This chapter aims to give you a brief overview of additional simulators and visualizers that can be used with Eclipse MOSAIC. We will continue with the tutorial-style explanations following up on the Steglitz-example from the previous chapter.">
+  <meta name="description" content="This chapter aims to give you a brief overview of additional simulators and visualizers that can be used with Eclipse MOSAIC. We will continue with the tutorial-style explanations following up on the Steglitz-example from the previous chapter  .">
 
   
   <link rel="alternate" hreflang="en-us" href="https://www.eclipse.org/mosaic/docs/building_scenarios/scenario_configuration/">
@@ -249,7 +249,7 @@
   <meta property="og:site_name" content="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
   <meta property="og:url" content="https://www.eclipse.org/mosaic/docs/building_scenarios/scenario_configuration/">
   <meta property="og:title" content="Additional Scenario Configuration | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
-  <meta property="og:description" content="This chapter aims to give you a brief overview of additional simulators and visualizers that can be used with Eclipse MOSAIC. We will continue with the tutorial-style explanations following up on the Steglitz-example from the previous chapter."><meta property="og:image" content="https://www.eclipse.org/mosaic/images/logo.svg">
+  <meta property="og:description" content="This chapter aims to give you a brief overview of additional simulators and visualizers that can be used with Eclipse MOSAIC. We will continue with the tutorial-style explanations following up on the Steglitz-example from the previous chapter  ."><meta property="og:image" content="https://www.eclipse.org/mosaic/images/logo.svg">
   <meta property="twitter:image" content="https://www.eclipse.org/mosaic/images/logo.svg"><meta property="og:locale" content="en-us">
   
     
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1017,9 +1025,93 @@
           <div class="article-style">
             <p>This chapter aims to give you a brief overview of additional simulators and visualizers that can be used with Eclipse MOSAIC.
 We will continue with the tutorial-style explanations following up on the Steglitz-example from the
-<a href="/mosaic/docs/building_scenarios/scenario_convert" title="previous chapter">previous chapter</a>. For more detailed explanations of the configurations have a
-look at <a href="/mosaic/docs/building_scenarios/" title="this chapter">this chapter</a>.<br>
-If you already played with the <a href="/mosaic/tutorials/barnim_basic/" title="Barnim">Barnim</a>-tutorial you probably noticed, that it contains far
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/scenario_convert/">
+    previous chapter
+</a>
+. For more detailed explanations of the configurations have a
+look at 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/">
+    this chapter
+</a>
+.<br>
+If you already played with the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/barnim_basic/">
+    Barnim
+</a>
+-tutorial you probably noticed, that it contains far
 more folders in the scenario structure compared to the Steglitz example. Those additional directories contain
 configurations for various simulators.</p>
 <pre><code class="language-plaintext">└─ Barnim
@@ -1050,9 +1142,69 @@
    └─ scenario_config.json .................. Basic configuration of the simulation scenario
 </code></pre>
 <p>If you have a look in the 
-    <a href="/mosaic/docs/building_scenarios/files/steglitz_mapping_config.json" title="mapping_config.json">mapping_config.json</a>,
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/files/steglitz_mapping_config.json" target="_blank" rel="noopener">
+    mapping_config.json
+</a>
+,
 you can see that the scenario-convert script automatically assigns cars to the three routes created. You can use this
-file as a blueprint for your own scenario, have a look <a href="/mosaic/docs/building_scenarios/#applications-and-mapping" title="here">here</a>
+file as a blueprint for your own scenario, have a look 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/#applications-and-mapping">
+    here
+</a>
+
 to get more details on possible adaptions.<br>
 Below is a short video of the scenario displayed in the SUMO-GUI. We marked the three different routes the cars
 follow.</p>
@@ -1072,11 +1224,39 @@
 
 
 <video controls >
-  <source src="/docs/building_scenarios/images/steglitz_routes.mp4" type="video/mp4">
+  <source src="/mosaic/docs/building_scenarios/images/steglitz_routes.mp4" type="video/mp4">
 </video>
 <h2 id="communication-simulators-cell-ns3-omnetpp-sns">Communication Simulators (cell, ns3, omnetpp, sns)</h2>
 <p>We won&rsquo;t implement any functionality for the steglitz example here but rather have a look at the
-<a href="/mosaic/tutorials/barnim_basic/" title="Barnim">Barnim</a>-tutorial. In the <code>scenario_config.json</code> of the Barnim scenario you can see where the
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/barnim_basic/">
+    Barnim
+</a>
+-tutorial. In the <code>scenario_config.json</code> of the Barnim scenario you can see where the
 communication simulators are activated:</p>
 <pre><code class="language-json">&quot;federates&quot;: {
     &quot;cell&quot;: false,
@@ -1085,12 +1265,152 @@
     &quot;sns&quot;: true
 }
 </code></pre>
-<p>Our <a href="/mosaic/tutorials/" title="tutorials">tutorials</a> and <a href="/mosaic/tutorials/additional_examples/" title="additional examples">additional examples</a> demonstrate use cases for
+<p>Our 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/">
+    tutorials
+</a>
+ and 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/additional_examples/">
+    additional examples
+</a>
+ demonstrate use cases for
 communication usages and you should have a look at them if you are uncertain where to start. Furthermore we
-recommend copying the configuration-files for the simulator you are going to use from the <a href="/mosaic/tutorials/barnim_basic/" title="Barnim scenario">Barnim scenario</a>. It
+recommend copying the configuration-files for the simulator you are going to use from the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/barnim_basic/">
+    Barnim scenario
+</a>
+. It
 contains the most complete configurations and is well maintained.<br>
-If you are an expert with one of the external network simulators (<a href="/mosaic/docs/simulators/network_simulator_ns3" title="ns3">ns3</a>,
-<a href="/mosaic/docs/simulators/network_simulator_omnetpp" title="OMNeT&#43;&#43;">OMNeT&#43;&#43;</a>) the Barnim scenario will also give
+If you are an expert with one of the external network simulators (
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_ns3/">
+    ns3
+</a>
+,
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_omnetpp/">
+    OMNeT++
+</a>
+) the Barnim scenario will also give
 you an overview on how to configure those.</p>
 <h2 id="other-simulators">Other Simulators</h2>
 <p>Here we&rsquo;ll discuss two simulators integrated with Eclipse MOSAIC and their use-cases, namely the <code>Event Server</code> and the
@@ -1100,16 +1420,108 @@
 an event server is used to simulate an icy area, which is then noticed by the sensor of a weather server RSU.<br>
 Every defined event requires a type, a defined geographical area (e.g. circular, rectangular), the strength and a time frame. Have a look
 at the 
-    <a href="/mosaic/docs/building_scenarios/files/eventserver_config.json" title="eventserver_config.json">eventserver_config.json</a> to see how this can be
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/files/eventserver_config.json" target="_blank" rel="noopener">
+    eventserver_config.json
+</a>
+ to see how this can be
 configured. If you want to use the event server make sure to have it enabled in the <code>scenario_config.json</code>.</p>
 <h3 id="battery">Battery</h3>
 <p>The battery simulator is used to simulate electric vehicles. It offers a lot of customization, because you can
 dynamically load your own battery, vehicle and environment models. Have a look a the 
-    <a href="/mosaic/docs/building_scenarios/files/battery_config.json" title="battery_config.json">battery_config.json</a>, taken from the Barnim scenario.
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/files/battery_config.json" target="_blank" rel="noopener">
+    battery_config.json
+</a>
+, taken from the Barnim scenario.
 The three models used are included with Eclipse MOSAIC and you can freely use them.</p>
 <h2 id="output">Output</h2>
 <p>There are various options to generate output results of your simulations (see the
-<a href="/mosaic/docs/visualization/filevis" title="visualization chapter">visualization chapter</a>).</p>
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/filevis/">
+    visualization chapter
+</a>
+).</p>
 <p>The first step is to create a file called <code>output_config.xml</code> in a new directory called <code>output</code>.
 If you used the scenario-convert tool the file should be generated automatically.</p>
 <pre><code class="language-plaintext">└─ steglitz
@@ -1132,8 +1544,7 @@
 <federate id="output" active="true"/>
 ```
 
-Now we have to configure the statistics visualizer itself. This 
-    <a href="/mosaic/docs/building_scenarios/files/steglitz_visualizer_config.xml" title="visualizer_config.xml">visualizer_config.xml</a> contains the basic
+Now we have to configure the statistics visualizer itself. This [visualizer_config.xml](/docs/building_scenarios/files/steglitz_visualizer_config.xml) contains the basic
 configuration in order to calculate the average travel times for the vehicles. If you want to make adaptions, please
 refer to [statistics visualizer](/docs/visualization/statistics).  
 Go ahead and run the simulation one more time. Afterwards the log-directory should contain a file called 
diff --git a/docs/building_scenarios/scenario_convert/index.html b/docs/building_scenarios/scenario_convert/index.html
index 6838194..c6248be 100644
--- a/docs/building_scenarios/scenario_convert/index.html
+++ b/docs/building_scenarios/scenario_convert/index.html
@@ -903,6 +903,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -915,6 +919,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1026,8 +1034,8 @@
             <div class="alert alert-extended">
   <span class="extended-icon" style="background-image: url(/mosaic/img/alert-extended.svg)"></span>
   <div>
-  <p>The tool <strong>scenario-convert</strong> is part of <strong><a href="/mosaic/download/#overview" title="MOSAIC Extended">MOSAIC Extended</a></strong>.</p>
-<p>However, you can use scenario-convert <strong>for free</strong> to generate scenarios which are executable with Eclipse MOSAIC. <strong><a href="/mosaic/https://www.dcaiti.tu-berlin.de/research/simulation/download/" title="Get it here">Get it here</a>.</strong></p>
+  <p>The tool <strong>scenario-convert</strong> is part of <strong><a href="/download#overview">MOSAIC Extended</a></strong>.</p>
+<p>However, you can use scenario-convert <strong>for free</strong> to generate scenarios which are executable with Eclipse MOSAIC. <strong><a href="https://www.dcaiti.tu-berlin.de/research/simulation/download/">Get it here</a>.</strong></p>
   </div>
 </div>
 <div style="text-align: center;">
@@ -1047,11 +1055,43 @@
 routes or  build own routes via route generation tools (e.g. DUAROUTER by SUMO).</p>
 <p>This chapter intends to highlight the most common workflows for the work with <code>scenario-convert</code>.
 We will be using 
-    <a href="/mosaic/docs/building_scenarios/files/steglitz.osm" title="steglitz.osm">steglitz.osm</a> OSM-file for most of the
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/files/steglitz.osm" target="_blank" rel="noopener">
+    steglitz.osm
+</a>
+ OSM-file for most of the
 use cases So feel free to follow along with the steps to get a better understanding on how the <code>scenario-convert</code>-script functions.</p>
 <div class="alert alert-note">
   <div>
-<p><a href="/mosaic/#reference-documentation-for-scenario-convert%22" title="Here">Here</a> you can find a complete reference to all options scenario-convert offers.</p>
+<p><a href="#reference-documentation-for-scenario-convert">Here</a> you can find a complete reference to all options scenario-convert offers.</p>
   </div>
 </div>
 
@@ -1135,8 +1175,22 @@
 <li>First the <code>steglitz.db</code> will be created using the <code>steglitz.osm</code>-file.</li>
 <li>The <code>steglitz.db</code> will be used to create <code>steglitz.con.xml</code>, <code>steglitz.edg.xml</code> and <code>steglitz.nod.xml</code>, which are files used by SUMO.</li>
 <li>
-<a href="https://sumo.dlr.de/wiki/NETCONVERT" target="_blank" rel="noopener">SUMO Netconvert</a> is used to create <code>steglitz.net.xml</code>, which is a 
-<a href="https://sumo.dlr.de/wiki/Networks/SUMO_Road_Networks" target="_blank" rel="noopener">network representation</a> in SUMO.</li>
+
+
+
+
+<a href="https://sumo.dlr.de/wiki/NETCONVERT" target="_blank" rel="noopener">
+    SUMO Netconvert
+</a>
+ is used to create <code>steglitz.net.xml</code>, which is a 
+
+
+
+
+<a href="https://sumo.dlr.de/wiki/Networks/SUMO_Road_Networks" target="_blank" rel="noopener">
+    network representation
+</a>
+ in SUMO.</li>
 <li>Now the SUMO-configuration <code>steglitz.sumo.cfg</code> is written.</li>
 <li>Afterwards the <code>mapping_config.json</code> and <code>scenario_config.json</code> are created and all files are moved to the right place.
 In the <code>scenario_config.json</code> values like the center coordinate will automatically be set using data from the SUMO related files.</li>
@@ -1312,7 +1366,19 @@
 <pre><code class="language-bash">java -jar scenario-convert.jar --osm2mosaic -i steglitz.osm -o --generate-routes
 --route-begin-node-id 267350668 --route-end-node-id 313139970 --number-of-routes 3
 </code></pre>
-<p>See <a href="/mosaic/#reference-documentation-for-scenario-convert" title="below">below</a> for all command line options.</p>
+<p>See 
+
+
+
+
+
+  
+  
+
+<a href="#reference-documentation-for-scenario-convert">
+    below
+</a>
+ for all command line options.</p>
 <p><strong>Conlusion</strong><br>
 This wraps up one of the main workflows with the scenario-convert-script.
 A quick reminder on what we achieved:</p>
@@ -1323,17 +1389,112 @@
 <li>Calculated routes between two coordinates.</li>
 </ul>
 <p>With all of this you can now start further developing your scenario. For a more detailed description on the next steps
-please have a look <a href="/mosaic/docs/building_scenarios/" title="here (Simulation Scenarios)">here (Simulation Scenarios)</a> and
-<a href="/mosaic/docs/develop_applications/" title="here (Application Development)">here (Application Development)</a>.<br>
+please have a look 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/">
+    here (Simulation Scenarios)
+</a>
+ and
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/develop_applications/">
+    here (Application Development)
+</a>
+.<br>
 While this is the &lsquo;happy world&rsquo; workflow it is often necessary to manually adapt routes and
 insert them into your scenario. The following workflow
 will explain how that is done and you will also get a more detailed overview of the scenario-convert-functions.</p>
 <h2 id="importing-routes-to-your-scenario">Importing Routes to your scenario</h2>
 <p>As mentioned above your routes won&rsquo;t always be created by the scenario-convert script. We generated some routes
 for the steglitz-scenario using SUMO&rsquo;s 
-<a href="http://sumo.dlr.de/wiki/DUAROUTER" target="_blank" rel="noopener">duarouter</a>, which you can find
 
-    <a href="/mosaic/docs/building_scenarios/files/steglitz.rou.xml" title="here">here</a>. We&rsquo;ll start with only the <code>steglitz.osm</code> and
+
+
+
+<a href="http://sumo.dlr.de/wiki/DUAROUTER" target="_blank" rel="noopener">
+    duarouter
+</a>
+, which you can find
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/files/steglitz.rou.xml" target="_blank" rel="noopener">
+    here
+</a>
+. We&rsquo;ll start with only the <code>steglitz.osm</code> and
 <code>steglitz.rou.xml</code> files:</p>
 <pre><code class="language-plaintext">└─ &lt;working-directory&gt;
    ├─ steglitz.osm
@@ -1417,9 +1578,73 @@
 <p>A list of all attached files in this chapter:</p>
 <ul>
 <li>
-    <a href="/mosaic/docs/building_scenarios/files/steglitz.osm" title="Steglitz OSM-file">Steglitz OSM-file</a></li>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/files/steglitz.osm" target="_blank" rel="noopener">
+    Steglitz OSM-file
+</a>
+</li>
 <li>
-    <a href="/mosaic/docs/building_scenarios/files/steglitz.rou.xml" title="Steglitz Route-file">Steglitz Route-file</a></li>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+
+    
+    
+      
+        
+          
+            
+            
+            
+          
+        
+      
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/files/steglitz.rou.xml" target="_blank" rel="noopener">
+    Steglitz Route-file
+</a>
+</li>
 </ul>
 <h2 id="reference-documentation-for-scenario-convert">Reference documentation for scenario-convert</h2>
 <h3 id="usage-of-scenario-convert">Usage of scenario-convert</h3>
@@ -1525,7 +1750,14 @@
 in order to define speeds for ways, which do not have a maxspeeds-tag defined. For this purpose use the
 option <code>--osm-speeds-file &lt;FILE&gt;</code>. In the speed properties file, for each way type a speed value can
 be defined, according to the OSM 
-<a href="http://wiki.openstreetmap.org/wiki/Key:highway" target="_blank" rel="noopener"><code>highway</code></a> key.</p>
+
+
+
+
+<a href="http://wiki.openstreetmap.org/wiki/Key:highway" target="_blank" rel="noopener">
+    <code>highway</code>
+</a>
+ key.</p>
 <pre><code># the unit the speed values are defined in [kmh, ms]
 speed.unit = kmh
 
diff --git a/docs/develop_applications/communication/index.html b/docs/develop_applications/communication/index.html
index 803d7ec..7850a7f 100644
--- a/docs/develop_applications/communication/index.html
+++ b/docs/develop_applications/communication/index.html
@@ -33,7 +33,7 @@
   
     
   
-  <meta name="description" content="Eclipse MOSAIC has different classes, which allow you to define the network type and the specific area where the communication should occur. Communication can be achieved with external network simulators (, ns-3) or one of the built-in communication simulators SNS or Eclipse MOSAIC Cell.">
+  <meta name="description" content="Eclipse MOSAIC has different classes, which allow you to define the network type and the specific area where the communication should occur. Communication can be achieved with external network simulators (, ns-3  ) or one of the built-in communication simulators SNS  or Eclipse MOSAIC Cell  .">
 
   
   <link rel="alternate" hreflang="en-us" href="https://www.eclipse.org/mosaic/docs/develop_applications/communication/">
@@ -249,7 +249,7 @@
   <meta property="og:site_name" content="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
   <meta property="og:url" content="https://www.eclipse.org/mosaic/docs/develop_applications/communication/">
   <meta property="og:title" content="Communication in Applications | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
-  <meta property="og:description" content="Eclipse MOSAIC has different classes, which allow you to define the network type and the specific area where the communication should occur. Communication can be achieved with external network simulators (, ns-3) or one of the built-in communication simulators SNS or Eclipse MOSAIC Cell."><meta property="og:image" content="https://www.eclipse.org/mosaic/images/logo.svg">
+  <meta property="og:description" content="Eclipse MOSAIC has different classes, which allow you to define the network type and the specific area where the communication should occur. Communication can be achieved with external network simulators (, ns-3  ) or one of the built-in communication simulators SNS  or Eclipse MOSAIC Cell  ."><meta property="og:image" content="https://www.eclipse.org/mosaic/images/logo.svg">
   <meta property="twitter:image" content="https://www.eclipse.org/mosaic/images/logo.svg"><meta property="og:locale" content="en-us">
   
     
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1031,8 +1039,92 @@
           <div class="article-style">
             <p>Eclipse MOSAIC has different classes, which allow you to define the network type and the specific area where the
 communication should occur. Communication can be achieved with external
-network simulators (<a href="/mosaic/docs/simulators/network_simulator_omnetpp" title=""></a>, <a href="/mosaic/docs/simulators/network_simulator_ns3" title="ns-3">ns-3</a>) or one of the built-in communication simulators <a href="/mosaic/docs/simulators/network_simulator_sns" title="SNS">SNS</a>
-or <a href="/mosaic/docs/simulators/network_simulator_cell" title="Eclipse MOSAIC Cell">Eclipse MOSAIC Cell</a>. Furthermore, for a better understanding it is important to consider the network types of Eclipse MOSAIC in more
+network simulators (<a href="/mosaic/docs/simulators/network_simulator_omnetpp" title=""></a>, 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_ns3/">
+    ns-3
+</a>
+) or one of the built-in communication simulators 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_sns/">
+    SNS
+</a>
+
+or 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_cell/">
+    Eclipse MOSAIC Cell
+</a>
+. Furthermore, for a better understanding it is important to consider the network types of Eclipse MOSAIC in more
 detail.</p>
 <ul>
 <li>Cellular Communication</li>
@@ -1404,9 +1496,9 @@
 <div class="alert alert-note">
   <div>
 <p>In order to use the Multihop approach in OMNeT++ and ns-3 provided by Eclipse MOSAIC, its necessary to implement a
-routing protocol in network simulators (<a href="/mosaic/docs/simulators/network_simulator_omnetpp" title="OMNeT&#43;&#43;">OMNeT++</a>,
-<a href="/mosaic/docs/simulators/network_simulator_ns3" title="ns-3">ns-3</a>). But the built in communication simulator
-<a href="/mosaic/docs/simulators/network_simulator_sns" title="SNS">SNS</a> includes a simple routing protocol “Flooding”.</p>
+routing protocol in network simulators (<a href="/docs/simulators/network_simulator_omnetpp">OMNeT++</a>,
+<a href="/docs/simulators/network_simulator_ns3">ns-3</a>). But the built in communication simulator
+<a href="/docs/simulators/network_simulator_sns">SNS</a> includes a simple routing protocol “Flooding”.</p>
   </div>
 </div>
 <h3 id="ad-hoc-topocast">Ad-hoc Topocast</h3>
diff --git a/docs/develop_applications/event_scheduler/index.html b/docs/develop_applications/event_scheduler/index.html
index 286cc8e..92dddd2 100644
--- a/docs/develop_applications/event_scheduler/index.html
+++ b/docs/develop_applications/event_scheduler/index.html
@@ -33,7 +33,7 @@
   
     
   
-  <meta name="description" content="The different modules of the Application Simulator communicate over events that are triggered at a specific simulation time. The following classes and interfaces model theses events.
+  <meta name="description" content="The different modules of the Application Simulator  communicate over events that are triggered at a specific simulation time. The following classes and interfaces model theses events.
 Event The class Event contains the information that is necessary to process an event.">
 
   
@@ -250,7 +250,7 @@
   <meta property="og:site_name" content="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
   <meta property="og:url" content="https://www.eclipse.org/mosaic/docs/develop_applications/event_scheduler/">
   <meta property="og:title" content="Event Scheduling | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
-  <meta property="og:description" content="The different modules of the Application Simulator communicate over events that are triggered at a specific simulation time. The following classes and interfaces model theses events.
+  <meta property="og:description" content="The different modules of the Application Simulator  communicate over events that are triggered at a specific simulation time. The following classes and interfaces model theses events.
 Event The class Event contains the information that is necessary to process an event."><meta property="og:image" content="https://www.eclipse.org/mosaic/images/logo.svg">
   <meta property="twitter:image" content="https://www.eclipse.org/mosaic/images/logo.svg"><meta property="og:locale" content="en-us">
   
@@ -901,6 +901,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -913,6 +917,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1020,7 +1028,35 @@
           <h1>Event Scheduling</h1>
 
           <div class="article-style">
-            <p>The different modules of the <a href="/mosaic/docs/simulators/application_simulator#eclipse-mosaic-application-simulator" title="Application Simulator">Application Simulator</a>
+            <p>The different modules of the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/#eclipse-mosaic-application-simulator">
+    Application Simulator
+</a>
+
 communicate over events that are triggered at a specific simulation time. The following classes and interfaces model theses events.</p>
 <h3 id="event">Event</h3>
 <p>The class <code>Event</code> contains the information that is necessary to process an event. An event describes when it should be processed and which information is processed. Moreover an event has an assigned priority.</p>
@@ -1038,7 +1074,14 @@
 <li><code>Event newTime(long time)</code>: allows the creation of a new event with a new execution time based</li>
 <li><code>String getResourceSimpleClassName()</code>: returns the class name of the resource as String.</li>
 <li><code>int compareTo(Event event)</code>: implements the standardized Java interface 
-<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Comparable.html" target="_blank" rel="noopener">Comparable</a>.  Toorder the events, first the time of the event is evaluated. In case the times are equal, the priority of the events is compared.</li>
+
+
+
+
+<a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Comparable.html" target="_blank" rel="noopener">
+    Comparable
+</a>
+.  Toorder the events, first the time of the event is evaluated. In case the times are equal, the priority of the events is compared.</li>
 </ul>
 <h3 id="interface-eventmanager">Interface EventManager</h3>
 <p>The interface <code>EventManager</code> defines the method <code>void addEvent(Event event)</code> that needs to be implemented to add an event to the execution.</p>
diff --git a/docs/develop_applications/index.html b/docs/develop_applications/index.html
index ab29472..3179e30 100644
--- a/docs/develop_applications/index.html
+++ b/docs/develop_applications/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1016,7 +1024,35 @@
           <h1>Basics in Application Development</h1>
 
           <div class="article-style">
-            <p>Applications in Eclipse MOSAIC are simulated by the <a href="/mosaic/docs/simulators/application_simulator" title="Application Simulator">Application Simulator</a>. Such
+            <p>Applications in Eclipse MOSAIC are simulated by the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/">
+    Application Simulator
+</a>
+. Such
 an application is programmed in Java and follows an event-based execution flow. Thereby, certain methods of the application are called by
 the Application Simulator upon corresponding events (the application &ldquo;reacts&rdquo;). To actively gain execution at some later point in time, an
 application can also schedule a generic event itself. When the application is executing, it has access to a set of methods, allowing to
@@ -1032,7 +1068,35 @@
 <p>What is required to get my own application to run in Eclipse MOSAIC?
 In Eclipse MOSAIC it is very easy to build your own application. First, it needs to inherit from the <code>AbstractApplication</code>
 class (see following section). Secondly, the application must be mapped to
-a vehicle (or RSU, or traffic light, &hellip;) via the mapping configuration (see section <a href="/mosaic/docs/building_scenarios/#applications-and-mapping" title="mapping">mapping</a>). Finally,
+a vehicle (or RSU, or traffic light, &hellip;) via the mapping configuration (see section 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/#applications-and-mapping">
+    mapping
+</a>
+). Finally,
 the application must be compiled as a Jar-File and placed into the application directory of your
 scenario.</p>
 </li>
@@ -1051,7 +1115,14 @@
 </ul>
 <h2 id="create-a-hello-world-application-based-on-maven">Create a ’Hello world’ application based on Maven</h2>
 <p>For this example you need to install 
-<a href="https://maven.apache.org/download.cgi" target="_blank" rel="noopener">Maven</a> which is used
+
+
+
+
+<a href="https://maven.apache.org/download.cgi" target="_blank" rel="noopener">
+    Maven
+</a>
+ which is used
 to resolve required MOSAIC dependencies and to compile your application Java code into a Jar file.
 Follow the steps to build an example application:</p>
 <ol>
@@ -1262,7 +1333,35 @@
 this.getOs().stop(distance, duration, Stop.StopMode.PARK);
 </code></pre>
 <h3 id="navigation">Navigation</h3>
-<p>The navigation of vehicles (i.e. calculation of routes) is handled completely by the <a href="/mosaic/docs/simulators/application_simulator#eclipse-mosaic-application-simulator" title="Application Simulator">Application Simulator</a>. Each vehicle is equipped
+<p>The navigation of vehicles (i.e. calculation of routes) is handled completely by the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/#eclipse-mosaic-application-simulator">
+    Application Simulator
+</a>
+. Each vehicle is equipped
 with a navigation system which provides all required information and functions for navigational purposes:</p>
 <ul>
 <li>Retrieve the current position and heading of the vehicle.</li>
diff --git a/docs/develop_applications/index.xml b/docs/develop_applications/index.xml
index 9eec930..a84b6a5 100644
--- a/docs/develop_applications/index.xml
+++ b/docs/develop_applications/index.xml
@@ -19,8 +19,92 @@
       <guid>https://www.eclipse.org/mosaic/docs/develop_applications/communication/</guid>
       <description>&lt;p&gt;Eclipse MOSAIC has different classes, which allow you to define the network type and the specific area where the
 communication should occur. Communication can be achieved with external
-network simulators (&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_omnetpp&#34; title=&#34;&#34;&gt;&lt;/a&gt;, &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_ns3&#34; title=&#34;ns-3&#34;&gt;ns-3&lt;/a&gt;) or one of the built-in communication simulators &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_sns&#34; title=&#34;SNS&#34;&gt;SNS&lt;/a&gt;
-or &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_cell&#34; title=&#34;Eclipse MOSAIC Cell&#34;&gt;Eclipse MOSAIC Cell&lt;/a&gt;. Furthermore, for a better understanding it is important to consider the network types of Eclipse MOSAIC in more
+network simulators (&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_omnetpp&#34; title=&#34;&#34;&gt;&lt;/a&gt;, 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_ns3/&#34;&gt;
+    ns-3
+&lt;/a&gt;
+) or one of the built-in communication simulators 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_sns/&#34;&gt;
+    SNS
+&lt;/a&gt;
+
+or 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_cell/&#34;&gt;
+    Eclipse MOSAIC Cell
+&lt;/a&gt;
+. Furthermore, for a better understanding it is important to consider the network types of Eclipse MOSAIC in more
 detail.&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;Cellular Communication&lt;/li&gt;
@@ -392,9 +476,9 @@
 &lt;div class=&#34;alert alert-note&#34;&gt;
   &lt;div&gt;
 &lt;p&gt;In order to use the Multihop approach in OMNeT++ and ns-3 provided by Eclipse MOSAIC, its necessary to implement a
-routing protocol in network simulators (&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_omnetpp&#34; title=&#34;OMNeT&amp;#43;&amp;#43;&#34;&gt;OMNeT++&lt;/a&gt;,
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_ns3&#34; title=&#34;ns-3&#34;&gt;ns-3&lt;/a&gt;). But the built in communication simulator
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_sns&#34; title=&#34;SNS&#34;&gt;SNS&lt;/a&gt; includes a simple routing protocol “Flooding”.&lt;/p&gt;
+routing protocol in network simulators (&lt;a href=&#34;https://www.eclipse.org/mosaic/docs/simulators/network_simulator_omnetpp&#34;&gt;OMNeT++&lt;/a&gt;,
+&lt;a href=&#34;https://www.eclipse.org/mosaic/docs/simulators/network_simulator_ns3&#34;&gt;ns-3&lt;/a&gt;). But the built in communication simulator
+&lt;a href=&#34;https://www.eclipse.org/mosaic/docs/simulators/network_simulator_sns&#34;&gt;SNS&lt;/a&gt; includes a simple routing protocol “Flooding”.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
 &lt;h3 id=&#34;ad-hoc-topocast&#34;&gt;Ad-hoc Topocast&lt;/h3&gt;
@@ -571,7 +655,35 @@
       <link>https://www.eclipse.org/mosaic/docs/develop_applications/event_scheduler/</link>
       <pubDate>Sun, 11 Aug 2019 00:00:00 +0000</pubDate>
       <guid>https://www.eclipse.org/mosaic/docs/develop_applications/event_scheduler/</guid>
-      <description>&lt;p&gt;The different modules of the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/application_simulator#eclipse-mosaic-application-simulator&#34; title=&#34;Application Simulator&#34;&gt;Application Simulator&lt;/a&gt;
+      <description>&lt;p&gt;The different modules of the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/application_simulator/#eclipse-mosaic-application-simulator&#34;&gt;
+    Application Simulator
+&lt;/a&gt;
+
 communicate over events that are triggered at a specific simulation time. The following classes and interfaces model theses events.&lt;/p&gt;
 &lt;h3 id=&#34;event&#34;&gt;Event&lt;/h3&gt;
 &lt;p&gt;The class &lt;code&gt;Event&lt;/code&gt; contains the information that is necessary to process an event. An event describes when it should be processed and which information is processed. Moreover an event has an assigned priority.&lt;/p&gt;
@@ -589,7 +701,14 @@
 &lt;li&gt;&lt;code&gt;Event newTime(long time)&lt;/code&gt;: allows the creation of a new event with a new execution time based&lt;/li&gt;
 &lt;li&gt;&lt;code&gt;String getResourceSimpleClassName()&lt;/code&gt;: returns the class name of the resource as String.&lt;/li&gt;
 &lt;li&gt;&lt;code&gt;int compareTo(Event event)&lt;/code&gt;: implements the standardized Java interface 
-&lt;a href=&#34;https://docs.oracle.com/javase/8/docs/api/java/lang/Comparable.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Comparable&lt;/a&gt;.  Toorder the events, first the time of the event is evaluated. In case the times are equal, the priority of the events is compared.&lt;/li&gt;
+
+
+
+
+&lt;a href=&#34;https://docs.oracle.com/javase/8/docs/api/java/lang/Comparable.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    Comparable
+&lt;/a&gt;
+.  Toorder the events, first the time of the event is evaluated. In case the times are equal, the priority of the events is compared.&lt;/li&gt;
 &lt;/ul&gt;
 &lt;h3 id=&#34;interface-eventmanager&#34;&gt;Interface EventManager&lt;/h3&gt;
 &lt;p&gt;The interface &lt;code&gt;EventManager&lt;/code&gt; defines the method &lt;code&gt;void addEvent(Event event)&lt;/code&gt; that needs to be implemented to add an event to the execution.&lt;/p&gt;
@@ -633,7 +752,35 @@
       <guid>https://www.eclipse.org/mosaic/docs/develop_applications/road_traffic/</guid>
       <description>&lt;p&gt;Each scenario to be simulated with Eclipse MOSAIC requires a database which contains information about the road infrastructure and routes the
 vehicles drive on. This information is used by various federates. For example, the SUMO federate needs to know initial routes for vehicles,
-and the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/application_simulator&#34; title=&#34;Application Simulator&#34;&gt;Application Simulator&lt;/a&gt; requires detailed information about the road
+and the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/application_simulator/&#34;&gt;
+    Application Simulator
+&lt;/a&gt;
+ requires detailed information about the road
 infrastructure to provide applications with methods for route calculation. For this purpose, an embedded SQLite database is
 used which is placed in the &lt;code&gt;application&lt;/code&gt; folder of the scenario. This database consists of the following tables:&lt;/p&gt;
 &lt;h3 id=&#34;database-tables&#34;&gt;Database tables&lt;/h3&gt;
diff --git a/docs/develop_applications/road_traffic/index.html b/docs/develop_applications/road_traffic/index.html
index ba3ab4b..2c8270a 100644
--- a/docs/develop_applications/road_traffic/index.html
+++ b/docs/develop_applications/road_traffic/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1014,7 +1022,35 @@
           <div class="article-style">
             <p>Each scenario to be simulated with Eclipse MOSAIC requires a database which contains information about the road infrastructure and routes the
 vehicles drive on. This information is used by various federates. For example, the SUMO federate needs to know initial routes for vehicles,
-and the <a href="/mosaic/docs/simulators/application_simulator" title="Application Simulator">Application Simulator</a> requires detailed information about the road
+and the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/">
+    Application Simulator
+</a>
+ requires detailed information about the road
 infrastructure to provide applications with methods for route calculation. For this purpose, an embedded SQLite database is
 used which is placed in the <code>application</code> folder of the scenario. This database consists of the following tables:</p>
 <h3 id="database-tables">Database tables</h3>
diff --git a/docs/extending_mosaic/application_ambassador_details/index.html b/docs/extending_mosaic/application_ambassador_details/index.html
index c29b282..f0c6304 100644
--- a/docs/extending_mosaic/application_ambassador_details/index.html
+++ b/docs/extending_mosaic/application_ambassador_details/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1066,7 +1074,35 @@
 Map, until a <code>VehicleMovements</code> message, belonging to that vehicle is processed. The vehicle will then be added by the <code>UnitSimulator</code>
 like any other node.</p>
 <h3 id="other-messages-and-time-advance">Other Messages and Time Advance</h3>
-<p>Apart from the ones for node creation, there are many other messages (see <a href="/mosaic/docs/extending_mosaic/interactions" title="Interaction">Interaction</a>),
+<p>Apart from the ones for node creation, there are many other messages (see 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/extending_mosaic/interactions/">
+    Interaction
+</a>
+),
 signaling events to the Application Simulator. For most of them, an event in the future will be programmed, such that the implied action is
 carried out at that simulation time. The processing of the events happens when the RTI calls the <code>advanceTime()</code> method on the ambassador.
 Upon this, Application Simulator will obtain a list of all events up to the new time and let the processor of the event process them. Every
@@ -1084,7 +1120,18 @@
 <tr>
 <td style="text-align:left"><code>VehicleUpdates</code></td>
 <td style="text-align:left">Signals that a vehicle has moved.  The <code>Vehicle</code> object, which is a subclass of <code>SimulationUnit</code>, that corresponds to the moved vehicle will be updated to contain the new position. The new information is encapsulated in a <code>VehicleInfo</code> object, containing different vehicle data. To update the data, an event is scheduled at the given time and processed upon time advance. Vehicles not yet added to the simulation (see 
-<a href="#node-creation">Node Creation</a>), are added by calling <code>addVehicleIfNotYetAdded()</code>.</td>
+
+
+
+
+
+  
+  
+
+<a href="#node-creation">
+    Node Creation
+</a>
+), are added by calling <code>addVehicleIfNotYetAdded()</code>.</td>
 </tr>
 <tr>
 <td style="text-align:left"><code>MessageReceiption</code></td>
diff --git a/docs/extending_mosaic/delay_models/index.html b/docs/extending_mosaic/delay_models/index.html
index f171025..b930c50 100644
--- a/docs/extending_mosaic/delay_models/index.html
+++ b/docs/extending_mosaic/delay_models/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
diff --git a/docs/extending_mosaic/index.html b/docs/extending_mosaic/index.html
index 432a238..21f8666 100644
--- a/docs/extending_mosaic/index.html
+++ b/docs/extending_mosaic/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1069,7 +1077,14 @@
 Consequently, the Time Management is necessary for coordinating the simulation and synchronizing
 participating federates. It assures that each federate processes its events in correct order.</p>
 <p>According to 
-<a href="https://ieeexplore.ieee.org/abstract/document/977259" target="_blank" rel="noopener">Fujimoto</a> the time management in a federated environment
+
+
+
+
+<a href="https://ieeexplore.ieee.org/abstract/document/977259" target="_blank" rel="noopener">
+    Fujimoto
+</a>
+ the time management in a federated environment
 includes two key components: Interaction (Message) order and time stamps. Note that we usually use the word &lsquo;intercation&rsquo; when
 talking about communication between federates, &lsquo;message&rsquo; will be used in the context of (V2X)-communication.</p>
 <p>The Interaction Order service is completely implemented in Eclipse MOSAIC with the following design rationale:
@@ -1157,9 +1172,23 @@
 are removed.</p>
 <h3 id="distributed-federation-management">Distributed Federation Management</h3>
 <p>To administrate simulators on remote hosts, the Federation Management uses the 
-<a href="https://www.ssh.com/ssh/" target="_blank" rel="noopener">Secure Shell (SSH)</a>
+
+
+
+
+<a href="https://www.ssh.com/ssh/" target="_blank" rel="noopener">
+    Secure Shell (SSH)
+</a>
+
 protocol to send commands and the associated 
-<a href="https://www.ssh.com/ssh/sftp/" target="_blank" rel="noopener">Secure File Transfer Protocol (SFTP)</a> to transfer binaries.
+
+
+
+
+<a href="https://www.ssh.com/ssh/sftp/" target="_blank" rel="noopener">
+    Secure File Transfer Protocol (SFTP)
+</a>
+ to transfer binaries.
 After a process is started remotely, a mapping between ambassador, its process id, and the host on which
 is running are stored. Finally, when the federate is resigned, the remotely running process is killed and all
 binaries are removed.</p>
diff --git a/docs/extending_mosaic/index.xml b/docs/extending_mosaic/index.xml
index af19ff3..fbd01b2 100644
--- a/docs/extending_mosaic/index.xml
+++ b/docs/extending_mosaic/index.xml
@@ -89,7 +89,14 @@
 &lt;p&gt;Coupling a multitude of different simulators and properly syncing them is a non-trivial task and requires a lot of effort in order to
 function correctly. If you have read up on High Level Architecture before
 (have a look 
-&lt;a href=&#34;https://en.wikipedia.org/wiki/High_Level_Architecture&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;here&lt;/a&gt; and at the linked references) you might notice, that the
+
+
+
+
+&lt;a href=&#34;https://en.wikipedia.org/wiki/High_Level_Architecture&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    here
+&lt;/a&gt;
+ and at the linked references) you might notice, that the
 previous flowchart does not completely reflect the proposed mechanisms. For instance, the &lt;code&gt;isTimeRegulating&lt;/code&gt; flag has no effect, when the
 &lt;code&gt;isTimeConstrained&lt;/code&gt; flag is not set.&lt;br&gt;
 So at some points you might stumble upon federates, which have their &lt;code&gt;isTimeConstrained&lt;/code&gt; and &lt;code&gt;isTimeRegulating&lt;/code&gt; flags set to different
@@ -251,7 +258,35 @@
 &lt;h2 id=&#34;mapping&#34;&gt;mapping&lt;/h2&gt;
 &lt;p&gt;All interactions in this package are concerned with adding/registering simulation-units to the simulation.
 While most of the introductions are handled by the &lt;code&gt;Mapping&lt;/code&gt;- or &lt;code&gt;Application&lt;/code&gt;-ambassador, some of them
-are handled by the ambassadors for the traffic simulators (see &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/lust/&#34; title=&#34;LuST&#34;&gt;LuST&lt;/a&gt;-scenario).
+are handled by the ambassadors for the traffic simulators (see 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/lust/&#34;&gt;
+    LuST
+&lt;/a&gt;
+-scenario).
 In this case the interactions are used to initialize the scenario.&lt;/p&gt;
 &lt;table&gt;
 &lt;thead&gt;
@@ -727,7 +762,35 @@
 Map, until a &lt;code&gt;VehicleMovements&lt;/code&gt; message, belonging to that vehicle is processed. The vehicle will then be added by the &lt;code&gt;UnitSimulator&lt;/code&gt;
 like any other node.&lt;/p&gt;
 &lt;h3 id=&#34;other-messages-and-time-advance&#34;&gt;Other Messages and Time Advance&lt;/h3&gt;
-&lt;p&gt;Apart from the ones for node creation, there are many other messages (see &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/extending_mosaic/interactions&#34; title=&#34;Interaction&#34;&gt;Interaction&lt;/a&gt;),
+&lt;p&gt;Apart from the ones for node creation, there are many other messages (see 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/extending_mosaic/interactions/&#34;&gt;
+    Interaction
+&lt;/a&gt;
+),
 signaling events to the Application Simulator. For most of them, an event in the future will be programmed, such that the implied action is
 carried out at that simulation time. The processing of the events happens when the RTI calls the &lt;code&gt;advanceTime()&lt;/code&gt; method on the ambassador.
 Upon this, Application Simulator will obtain a list of all events up to the new time and let the processor of the event process them. Every
@@ -745,7 +808,18 @@
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;VehicleUpdates&lt;/code&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;Signals that a vehicle has moved.  The &lt;code&gt;Vehicle&lt;/code&gt; object, which is a subclass of &lt;code&gt;SimulationUnit&lt;/code&gt;, that corresponds to the moved vehicle will be updated to contain the new position. The new information is encapsulated in a &lt;code&gt;VehicleInfo&lt;/code&gt; object, containing different vehicle data. To update the data, an event is scheduled at the given time and processed upon time advance. Vehicles not yet added to the simulation (see 
-&lt;a href=&#34;#node-creation&#34;&gt;Node Creation&lt;/a&gt;), are added by calling &lt;code&gt;addVehicleIfNotYetAdded()&lt;/code&gt;.&lt;/td&gt;
+
+
+
+
+
+  
+  
+
+&lt;a href=&#34;#node-creation&#34;&gt;
+    Node Creation
+&lt;/a&gt;
+), are added by calling &lt;code&gt;addVehicleIfNotYetAdded()&lt;/code&gt;.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;MessageReceiption&lt;/code&gt;&lt;/td&gt;
@@ -887,14 +961,28 @@
 +--------------------------------------+  /
 &lt;/code&gt;&lt;/pre&gt;
 &lt;p&gt;A more detailed description can be found here: 
-&lt;a href=&#34;http://sumo.dlr.de/wiki/TraCI/Protocol&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;http://sumo.dlr.de/wiki/TraCI/Protocol&lt;/a&gt;&lt;/p&gt;
+
+
+
+
+&lt;a href=&#34;http://sumo.dlr.de/wiki/TraCI/Protocol&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    http://sumo.dlr.de/wiki/TraCI/Protocol
+&lt;/a&gt;
+&lt;/p&gt;
 &lt;h4 id=&#34;commands&#34;&gt;Commands&lt;/h4&gt;
 &lt;p&gt;Each TraCI command is identified by an command identifier. For example, the command 0xC4 is used to
 change the state of a vehicle. Most of the commands need further specification, such as the parameter of
 the vehicle which is required to be changed. Those parameters are usually accessed by variable identifiers
 (e.g. 0x40 addresses the speed of an entity). A full list of commands and variables supported by TraCI can
 be found here: 
-&lt;a href=&#34;http://sumo.dlr.de/wiki/TraCI&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;http://sumo.dlr.de/wiki/TraCI&lt;/a&gt;&lt;/p&gt;
+
+
+
+
+&lt;a href=&#34;http://sumo.dlr.de/wiki/TraCI&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    http://sumo.dlr.de/wiki/TraCI
+&lt;/a&gt;
+&lt;/p&gt;
 &lt;p&gt;Here is an example of a command message to change the speed of the vehicle &amp;ldquo;veh_0&amp;rdquo; to 14m/s:&lt;/p&gt;
 &lt;pre&gt;&lt;code&gt; 0                 7 8                 15                23 24               31
 +-----------------------------------------------------------------------------+
@@ -934,7 +1022,14 @@
 parameters which are later passed dynamically to the command. Here, the command is specified as &lt;code&gt;0xC4&lt;/code&gt; (= change vehicle state) and the variable as &lt;code&gt;0x04&lt;/code&gt; (= speed of the entity). Furthermore, two parameters are
 defined: The first string parameter represents the ID of the vehicle, the second double parameter defines
 the speed value to be set (according to 
-&lt;a href=&#34;http://sumo.dlr.de/wiki/TraCI/Change_Vehicle_State&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;http://sumo.dlr.de/wiki/TraCI/Change_Vehicle_State&lt;/a&gt;).
+
+
+
+
+&lt;a href=&#34;http://sumo.dlr.de/wiki/TraCI/Change_Vehicle_State&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    http://sumo.dlr.de/wiki/TraCI/Change_Vehicle_State
+&lt;/a&gt;
+).
 Note, the order of the specified command contents is from crucial importance. E.g. the &lt;code&gt;command&lt;/code&gt; must
 always be specified before the &lt;code&gt;variable&lt;/code&gt;, and the variable before all parameters.&lt;/p&gt;
 &lt;p&gt;All parameters defined in the constructor (here: &lt;code&gt;[String, Double]&lt;/code&gt; ), need to be assigned with values
@@ -1178,7 +1273,35 @@
 points for application messages for the communication stack for the following reasons. The communication
 oriented models of INETMANET have their focus more on the framing for communication and less on
 the real content. That means that content is often modeled with dummy payloads where only the length is
-of interest. In contrast, V2X applications which are simulated in the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/application_simulator&#34; title=&#34;Application Simulator&#34;&gt;Application Simulator&lt;/a&gt;.
+of interest. In contrast, V2X applications which are simulated in the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/application_simulator/&#34;&gt;
+    Application Simulator
+&lt;/a&gt;
+.
 Rely on the correct transmission of contents. Hence, the modules &lt;code&gt;VSimRTIReliableApp&lt;/code&gt; and &lt;code&gt;VSimRTIUnreliableApp&lt;/code&gt;
 are introduced to bridge this gap. They are triggered by the Eclipse MOSAIC ScenarioManager
 to send new messages to lower layers and forward messages themselves back to the ScenarioManager
@@ -1353,7 +1476,35 @@
 this is used by the Eclipse MOSAIC ScenarioManager to report the &lt;code&gt;RECEIVE_V2X_MESSAGES&lt;/code&gt;.&lt;/p&gt;
 &lt;h4 id=&#34;eclipse-mosaic-omnet-federate-development&#34;&gt;Eclipse MOSAIC OMNeT++ Federate Development&lt;/h4&gt;
 &lt;p&gt;This section provides a description how to set up the &lt;strong&gt;OMNeT++ IDE&lt;/strong&gt; for the Eclipse MOSAIC OMNeT++ Federate Development.&lt;/p&gt;
-&lt;p&gt;At this point it is awaited, that the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_omnetpp&#34; title=&#34;OMNeT&amp;#43;&amp;#43; Federate&#34;&gt;OMNeT&amp;#43;&amp;#43; Federate&lt;/a&gt; is successfully installed.&lt;/p&gt;
+&lt;p&gt;At this point it is awaited, that the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_omnetpp/&#34;&gt;
+    OMNeT++ Federate
+&lt;/a&gt;
+ is successfully installed.&lt;/p&gt;
 &lt;h5 id=&#34;prepare-omnet-ide&#34;&gt;Prepare OMNeT++ IDE&lt;/h5&gt;
 &lt;ol&gt;
 &lt;li&gt;
@@ -1684,7 +1835,7 @@
 
 
 &lt;video controls &gt;
-  &lt;source src=&#34;../images/omnetpp-ide-rebuild-federate.mp4&#34; type=&#34;video/mp4&#34;&gt;
+  &lt;source src=&#34;https://www.eclipse.org/mosaic/images/omnetpp-ide-rebuild-federate.mp4&#34; type=&#34;video/mp4&#34;&gt;
 &lt;/video&gt;
 &lt;hr&gt;
 &lt;h5 id=&#34;configure-debug-configuration&#34;&gt;Configure Debug Configuration&lt;/h5&gt;
diff --git a/docs/extending_mosaic/interactions/index.html b/docs/extending_mosaic/interactions/index.html
index 1687e78..32d8744 100644
--- a/docs/extending_mosaic/interactions/index.html
+++ b/docs/extending_mosaic/interactions/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1027,7 +1035,35 @@
 <h2 id="mapping">mapping</h2>
 <p>All interactions in this package are concerned with adding/registering simulation-units to the simulation.
 While most of the introductions are handled by the <code>Mapping</code>- or <code>Application</code>-ambassador, some of them
-are handled by the ambassadors for the traffic simulators (see <a href="/mosaic/tutorials/lust/" title="LuST">LuST</a>-scenario).
+are handled by the ambassadors for the traffic simulators (see 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/lust/">
+    LuST
+</a>
+-scenario).
 In this case the interactions are used to initialize the scenario.</p>
 <table>
 <thead>
diff --git a/docs/extending_mosaic/omnetpp_details/index.html b/docs/extending_mosaic/omnetpp_details/index.html
index 436d86a..6f17764 100644
--- a/docs/extending_mosaic/omnetpp_details/index.html
+++ b/docs/extending_mosaic/omnetpp_details/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1102,7 +1110,35 @@
 points for application messages for the communication stack for the following reasons. The communication
 oriented models of INETMANET have their focus more on the framing for communication and less on
 the real content. That means that content is often modeled with dummy payloads where only the length is
-of interest. In contrast, V2X applications which are simulated in the <a href="/mosaic/docs/simulators/application_simulator" title="Application Simulator">Application Simulator</a>.
+of interest. In contrast, V2X applications which are simulated in the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/">
+    Application Simulator
+</a>
+.
 Rely on the correct transmission of contents. Hence, the modules <code>VSimRTIReliableApp</code> and <code>VSimRTIUnreliableApp</code>
 are introduced to bridge this gap. They are triggered by the Eclipse MOSAIC ScenarioManager
 to send new messages to lower layers and forward messages themselves back to the ScenarioManager
@@ -1277,7 +1313,35 @@
 this is used by the Eclipse MOSAIC ScenarioManager to report the <code>RECEIVE_V2X_MESSAGES</code>.</p>
 <h4 id="eclipse-mosaic-omnet-federate-development">Eclipse MOSAIC OMNeT++ Federate Development</h4>
 <p>This section provides a description how to set up the <strong>OMNeT++ IDE</strong> for the Eclipse MOSAIC OMNeT++ Federate Development.</p>
-<p>At this point it is awaited, that the <a href="/mosaic/docs/simulators/network_simulator_omnetpp" title="OMNeT&#43;&#43; Federate">OMNeT&#43;&#43; Federate</a> is successfully installed.</p>
+<p>At this point it is awaited, that the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_omnetpp/">
+    OMNeT++ Federate
+</a>
+ is successfully installed.</p>
 <h5 id="prepare-omnet-ide">Prepare OMNeT++ IDE</h5>
 <ol>
 <li>
@@ -1608,7 +1672,7 @@
 
 
 <video controls >
-  <source src="../images/omnetpp-ide-rebuild-federate.mp4" type="video/mp4">
+  <source src="/images/omnetpp-ide-rebuild-federate.mp4" type="video/mp4">
 </video>
 <hr>
 <h5 id="configure-debug-configuration">Configure Debug Configuration</h5>
diff --git a/docs/extending_mosaic/simulator_coupling/index.html b/docs/extending_mosaic/simulator_coupling/index.html
index 06f7fec..518f5f2 100644
--- a/docs/extending_mosaic/simulator_coupling/index.html
+++ b/docs/extending_mosaic/simulator_coupling/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1086,7 +1094,14 @@
 <p>Coupling a multitude of different simulators and properly syncing them is a non-trivial task and requires a lot of effort in order to
 function correctly. If you have read up on High Level Architecture before
 (have a look 
-<a href="https://en.wikipedia.org/wiki/High_Level_Architecture" target="_blank" rel="noopener">here</a> and at the linked references) you might notice, that the
+
+
+
+
+<a href="https://en.wikipedia.org/wiki/High_Level_Architecture" target="_blank" rel="noopener">
+    here
+</a>
+ and at the linked references) you might notice, that the
 previous flowchart does not completely reflect the proposed mechanisms. For instance, the <code>isTimeRegulating</code> flag has no effect, when the
 <code>isTimeConstrained</code> flag is not set.<br>
 So at some points you might stumble upon federates, which have their <code>isTimeConstrained</code> and <code>isTimeRegulating</code> flags set to different
diff --git a/docs/extending_mosaic/sumo_ambassador_details/index.html b/docs/extending_mosaic/sumo_ambassador_details/index.html
index 70d9ce3..05737c5 100644
--- a/docs/extending_mosaic/sumo_ambassador_details/index.html
+++ b/docs/extending_mosaic/sumo_ambassador_details/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1137,14 +1145,28 @@
 +--------------------------------------+  /
 </code></pre>
 <p>A more detailed description can be found here: 
-<a href="http://sumo.dlr.de/wiki/TraCI/Protocol" target="_blank" rel="noopener">http://sumo.dlr.de/wiki/TraCI/Protocol</a></p>
+
+
+
+
+<a href="http://sumo.dlr.de/wiki/TraCI/Protocol" target="_blank" rel="noopener">
+    http://sumo.dlr.de/wiki/TraCI/Protocol
+</a>
+</p>
 <h4 id="commands">Commands</h4>
 <p>Each TraCI command is identified by an command identifier. For example, the command 0xC4 is used to
 change the state of a vehicle. Most of the commands need further specification, such as the parameter of
 the vehicle which is required to be changed. Those parameters are usually accessed by variable identifiers
 (e.g. 0x40 addresses the speed of an entity). A full list of commands and variables supported by TraCI can
 be found here: 
-<a href="http://sumo.dlr.de/wiki/TraCI" target="_blank" rel="noopener">http://sumo.dlr.de/wiki/TraCI</a></p>
+
+
+
+
+<a href="http://sumo.dlr.de/wiki/TraCI" target="_blank" rel="noopener">
+    http://sumo.dlr.de/wiki/TraCI
+</a>
+</p>
 <p>Here is an example of a command message to change the speed of the vehicle &ldquo;veh_0&rdquo; to 14m/s:</p>
 <pre><code> 0                 7 8                 15                23 24               31
 +-----------------------------------------------------------------------------+
@@ -1184,7 +1206,14 @@
 parameters which are later passed dynamically to the command. Here, the command is specified as <code>0xC4</code> (= change vehicle state) and the variable as <code>0x04</code> (= speed of the entity). Furthermore, two parameters are
 defined: The first string parameter represents the ID of the vehicle, the second double parameter defines
 the speed value to be set (according to 
-<a href="http://sumo.dlr.de/wiki/TraCI/Change_Vehicle_State" target="_blank" rel="noopener">http://sumo.dlr.de/wiki/TraCI/Change_Vehicle_State</a>).
+
+
+
+
+<a href="http://sumo.dlr.de/wiki/TraCI/Change_Vehicle_State" target="_blank" rel="noopener">
+    http://sumo.dlr.de/wiki/TraCI/Change_Vehicle_State
+</a>
+).
 Note, the order of the specified command contents is from crucial importance. E.g. the <code>command</code> must
 always be specified before the <code>variable</code>, and the variable before all parameters.</p>
 <p>All parameters defined in the constructor (here: <code>[String, Double]</code> ), need to be assigned with values
diff --git a/docs/getting_started/index.html b/docs/getting_started/index.html
index 2932129..cc03edd 100644
--- a/docs/getting_started/index.html
+++ b/docs/getting_started/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1022,7 +1030,14 @@
 <li><strong>Download the <code>eclipse-mosaic-20.0.zip</code> bundle from the mirror above.</strong></li>
 <li>Extract the package to an arbitrary path. This installation path is referenced as <code>&lt;mosaic-root&gt;</code> throughout the entire document.</li>
 <li><strong>Install additional software</strong> required by the simulation (see below), e.g. 
-<a href="https://www.eclipse.org/sumo" target="_blank" rel="noopener">Eclipse SUMO</a></li>
+
+
+
+
+<a href="https://www.eclipse.org/sumo" target="_blank" rel="noopener">
+    Eclipse SUMO
+</a>
+</li>
 </ol>
 <h3 id="folder-content">Folder Content</h3>
 <pre><code class="language-plaintext">└─ &lt;mosaic-root&gt;
@@ -1056,7 +1071,14 @@
 <tbody>
 <tr>
 <td style="text-align:center"><strong>
-<a href="https://adoptopenjdk.net/?variant=openjdk8&amp;jvmVariant=hotspot" target="_blank" rel="noopener">Java</a></strong></td>
+
+
+
+
+<a href="https://adoptopenjdk.net/?variant=openjdk8&amp;jvmVariant=hotspot" target="_blank" rel="noopener">
+    Java
+</a>
+</strong></td>
 <td style="text-align:center">yes</td>
 <td style="text-align:center">7 and below<br/> <em>not supported</em></td>
 <td style="text-align:center"><strong>8</strong> <br/> <em>supported</em></td>
@@ -1071,7 +1093,14 @@
 </tr>
 <tr>
 <td style="text-align:center"><strong>
-<a href="https://www.eclipse.org/sumo" target="_blank" rel="noopener">Eclipse SUMO</a></strong></td>
+
+
+
+
+<a href="https://www.eclipse.org/sumo" target="_blank" rel="noopener">
+    Eclipse SUMO
+</a>
+</strong></td>
 <td style="text-align:center">yes*</td>
 <td style="text-align:center">0.32.0 and below<br/> <em>not supported</em></td>
 <td style="text-align:center"><strong>1.0.1 - 1.8.0</strong> <br/> <em>supported</em></td>
@@ -1079,7 +1108,14 @@
 </tr>
 <tr>
 <td style="text-align:center"><strong>
-<a href="https://omnetpp.org/download/old" target="_blank" rel="noopener">OMNeT++</a></strong></td>
+
+
+
+
+<a href="https://omnetpp.org/download/old" target="_blank" rel="noopener">
+    OMNeT++
+</a>
+</strong></td>
 <td style="text-align:center">optional</td>
 <td style="text-align:center">below 5.5<br/> <em>not supported</em></td>
 <td style="text-align:center"><strong>5.5</strong> <br/> <em>supported</em></td>
@@ -1087,7 +1123,14 @@
 </tr>
 <tr>
 <td style="text-align:center"><strong>
-<a href="https://inet.omnetpp.org/Download.html" target="_blank" rel="noopener">INET</a></strong></td>
+
+
+
+
+<a href="https://inet.omnetpp.org/Download.html" target="_blank" rel="noopener">
+    INET
+</a>
+</strong></td>
 <td style="text-align:center">optional</td>
 <td style="text-align:center">below 4.1<br/> <em>not supported</em></td>
 <td style="text-align:center"><strong>4.1</strong> <br/> <em>supported</em></td>
@@ -1095,7 +1138,14 @@
 </tr>
 <tr>
 <td style="text-align:center"><strong>
-<a href="https://www.nsnam.org/releases/ns-3-28" target="_blank" rel="noopener">ns-3</a></strong></td>
+
+
+
+
+<a href="https://www.nsnam.org/releases/ns-3-28" target="_blank" rel="noopener">
+    ns-3
+</a>
+</strong></td>
 <td style="text-align:center">optional</td>
 <td style="text-align:center">below 3.28<br/> <em>not supported</em></td>
 <td style="text-align:center"><strong>3.28</strong> <br/> <em>supported</em></td>
diff --git a/docs/getting_started/index.xml b/docs/getting_started/index.xml
index 566e5ff..19b6ddf 100644
--- a/docs/getting_started/index.xml
+++ b/docs/getting_started/index.xml
@@ -29,7 +29,35 @@
 &lt;/code&gt;&lt;/pre&gt;
 &lt;h3 id=&#34;example&#34;&gt;Example&lt;/h3&gt;
 &lt;p&gt;The following call starts the example scenario &amp;ldquo;Barnim&amp;rdquo; in Eclipse MOSAIC on a Windows machine and opens a
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/visualization/&#34; title=&#34;Visualization in your browser&#34;&gt;Visualization in your browser&lt;/a&gt;:&lt;/p&gt;
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/visualization/&#34;&gt;
+    Visualization in your browser
+&lt;/a&gt;
+:&lt;/p&gt;
 &lt;pre&gt;&lt;code class=&#34;language-dos&#34;&gt;mosaic.bat -s Barnim -v
 &lt;/code&gt;&lt;/pre&gt;
 
@@ -110,7 +138,35 @@
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;-v&lt;/code&gt;&lt;br&gt;&lt;code&gt;--start-visualizer&lt;/code&gt;&lt;/td&gt;
-&lt;td style=&#34;text-align:left&#34;&gt;Opens a page in your default browser which visualizes all vehicle movements of the simulation on a map. This option only works, if your scenario is configured with the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/visualization/&#34; title=&#34;Websocket Visualizer&#34;&gt;Websocket Visualizer&lt;/a&gt;.&lt;/td&gt;
+&lt;td style=&#34;text-align:left&#34;&gt;Opens a page in your default browser which visualizes all vehicle movements of the simulation on a map. This option only works, if your scenario is configured with the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/visualization/&#34;&gt;
+    Websocket Visualizer
+&lt;/a&gt;
+.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;-h&lt;/code&gt;&lt;br&gt;&lt;code&gt;--help&lt;/code&gt;&lt;/td&gt;
@@ -146,7 +202,35 @@
 Therefore, these logs are very helpful to retrace and understand the individual states during the simulation time. The generated log
 files can be found in the &lt;code&gt;&amp;lt;mosaic-root&amp;gt;/logs/log-&amp;lt;timestamp&amp;gt;&lt;/code&gt; directory.&lt;/p&gt;
 &lt;p&gt;Moreover, Eclipse MOSAIC offers uniformly formatted and visually prepared results using various
-&lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/visualization/&#34; title=&#34;Output Generator&#34;&gt;Output Generator&lt;/a&gt;&lt;/strong&gt; implementations. For  example, the &lt;code&gt;FileOutputGenerator&lt;/code&gt; generates
+&lt;strong&gt;
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/visualization/&#34;&gt;
+    Output Generator
+&lt;/a&gt;
+&lt;/strong&gt; implementations. For  example, the &lt;code&gt;FileOutputGenerator&lt;/code&gt; generates
 detailed outputs of e.g. vehicle positions, speeds, or message exchanges.
 In the scenarios brought by the latest release, this output mechanism is already configured.&lt;/p&gt;
 &lt;h2 id=&#34;scenario-configuration&#34;&gt;Scenario Configuration&lt;/h2&gt;
@@ -182,7 +266,35 @@
 &lt;/code&gt;&lt;/pre&gt;
 &lt;p&gt;This way, simulators can be easily added or removed from the simulation. Each of the coupled simulators is configured in the directory
 of the &lt;code&gt;scenario_config.json&lt;/code&gt; file. The release bundle comes with a set of tutorial scenarios, which are described in detail
-in the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/&#34; title=&#34;Tutorials section&#34;&gt;Tutorials section&lt;/a&gt;.&lt;/p&gt;
+in the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/tutorials/&#34;&gt;
+    Tutorials section
+&lt;/a&gt;
+.&lt;/p&gt;
 </description>
     </item>
     
@@ -223,7 +335,14 @@
 simulation depending on your simulation focus.&lt;/p&gt;
 &lt;p&gt;Eclipse MOSAIC uses &lt;em&gt;LOGback&lt;/em&gt; as logging framework. &lt;em&gt;LOGback&lt;/em&gt; offers a lot of parameters to adapt the output to your needs. Please refer to
 
-&lt;a href=&#34;https://logback.qos.ch/manual/layouts.html#ClassicPatternLayout&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;this site&lt;/a&gt; for a detailed overview of all
+
+
+
+
+&lt;a href=&#34;https://logback.qos.ch/manual/layouts.html#ClassicPatternLayout&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    this site
+&lt;/a&gt;
+ for a detailed overview of all
 parameters you can use in the &lt;code&gt;logback.xml&lt;/code&gt; file.&lt;/p&gt;
 &lt;p&gt;Please note that you can adjust the output to your needs by setting different log levels (&lt;code&gt;ERROR&lt;/code&gt;, &lt;code&gt;INFO&lt;/code&gt;,
 &lt;code&gt;DEBUG&lt;/code&gt; etc.) for each component in the file at &lt;code&gt;&amp;lt;mosaic-root&amp;gt;/etc/logback.xml&lt;/code&gt;. This might also influence
diff --git a/docs/getting_started/results/index.html b/docs/getting_started/results/index.html
index e98807e..4dec33c 100644
--- a/docs/getting_started/results/index.html
+++ b/docs/getting_started/results/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1043,7 +1051,14 @@
 simulation depending on your simulation focus.</p>
 <p>Eclipse MOSAIC uses <em>LOGback</em> as logging framework. <em>LOGback</em> offers a lot of parameters to adapt the output to your needs. Please refer to
 
-<a href="https://logback.qos.ch/manual/layouts.html#ClassicPatternLayout" target="_blank" rel="noopener">this site</a> for a detailed overview of all
+
+
+
+
+<a href="https://logback.qos.ch/manual/layouts.html#ClassicPatternLayout" target="_blank" rel="noopener">
+    this site
+</a>
+ for a detailed overview of all
 parameters you can use in the <code>logback.xml</code> file.</p>
 <p>Please note that you can adjust the output to your needs by setting different log levels (<code>ERROR</code>, <code>INFO</code>,
 <code>DEBUG</code> etc.) for each component in the file at <code>&lt;mosaic-root&gt;/etc/logback.xml</code>. This might also influence
diff --git a/docs/getting_started/run_mosaic/index.html b/docs/getting_started/run_mosaic/index.html
index f120525..a441a8f 100644
--- a/docs/getting_started/run_mosaic/index.html
+++ b/docs/getting_started/run_mosaic/index.html
@@ -901,6 +901,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -913,6 +917,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1030,7 +1038,35 @@
 </code></pre>
 <h3 id="example">Example</h3>
 <p>The following call starts the example scenario &ldquo;Barnim&rdquo; in Eclipse MOSAIC on a Windows machine and opens a
-<a href="/mosaic/docs/visualization/" title="Visualization in your browser">Visualization in your browser</a>:</p>
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/">
+    Visualization in your browser
+</a>
+:</p>
 <pre><code class="language-dos">mosaic.bat -s Barnim -v
 </code></pre>
 
@@ -1111,7 +1147,35 @@
 </tr>
 <tr>
 <td style="text-align:left"><code>-v</code><br><code>--start-visualizer</code></td>
-<td style="text-align:left">Opens a page in your default browser which visualizes all vehicle movements of the simulation on a map. This option only works, if your scenario is configured with the <a href="/mosaic/docs/visualization/" title="Websocket Visualizer">Websocket Visualizer</a>.</td>
+<td style="text-align:left">Opens a page in your default browser which visualizes all vehicle movements of the simulation on a map. This option only works, if your scenario is configured with the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/">
+    Websocket Visualizer
+</a>
+.</td>
 </tr>
 <tr>
 <td style="text-align:left"><code>-h</code><br><code>--help</code></td>
@@ -1147,7 +1211,35 @@
 Therefore, these logs are very helpful to retrace and understand the individual states during the simulation time. The generated log
 files can be found in the <code>&lt;mosaic-root&gt;/logs/log-&lt;timestamp&gt;</code> directory.</p>
 <p>Moreover, Eclipse MOSAIC offers uniformly formatted and visually prepared results using various
-<strong><a href="/mosaic/docs/visualization/" title="Output Generator">Output Generator</a></strong> implementations. For  example, the <code>FileOutputGenerator</code> generates
+<strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/">
+    Output Generator
+</a>
+</strong> implementations. For  example, the <code>FileOutputGenerator</code> generates
 detailed outputs of e.g. vehicle positions, speeds, or message exchanges.
 In the scenarios brought by the latest release, this output mechanism is already configured.</p>
 <h2 id="scenario-configuration">Scenario Configuration</h2>
@@ -1183,7 +1275,35 @@
 </code></pre>
 <p>This way, simulators can be easily added or removed from the simulation. Each of the coupled simulators is configured in the directory
 of the <code>scenario_config.json</code> file. The release bundle comes with a set of tutorial scenarios, which are described in detail
-in the <a href="/mosaic/tutorials/" title="Tutorials section">Tutorials section</a>.</p>
+in the 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/">
+    Tutorials section
+</a>
+.</p>
 
           </div>
 
diff --git a/docs/index.html b/docs/index.html
index 0b2beb8..326e6ad 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -892,6 +892,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -904,6 +908,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -988,14 +996,106 @@
           <div class="article-style">
             <p>This online documentation provides detailed information for the latest release of Eclipse MOSAIC. Some details may
 deviate, however, as we constantly keep this documentation in sync with the current main branch of our
-<a href="https://github.com/eclipse/mosaic" target="_blank"><i class="fab fa-github"></i> GitHub repository</a>.</p>
-<p>This documentation is accompanied by our <strong><a href="/mosaic/tutorials/" title="tutorials">tutorials</a></strong>. Generally, it is recommended to read
-the documentation first, especially the sections on <a href="/mosaic/docs/getting_started/" title="How To Get Started">How To Get Started</a> and
-<a href="/mosaic/docs/simulators/" title="Simulator Overview">Simulator Overview</a>. For external simulators like Eclipse SUMO, OMNeT++ / INET or ns-3,
+
+
+
+
+
+<a href="https://github.com/eclipse/mosaic" target="_blank" rel="noopener">
+    <i class="fab fa-github"></i> GitHub repository</a>
+</a>
+.</p>
+<p>This documentation is accompanied by our <strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/">
+    tutorials
+</a>
+</strong>. Generally, it is recommended to read
+the documentation first, especially the sections on 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/getting_started/">
+    How To Get Started
+</a>
+ and
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/">
+    Simulator Overview
+</a>
+. For external simulators like Eclipse SUMO, OMNeT++ / INET or ns-3,
 the according project websites contain more exhaustive information, of course.</p>
 <div class="alert alert-note">
   <div>
-<p>Our <strong><a href="/mosaic/tutorials/" title="tutorials">tutorials</a></strong> are intended for step-by-step practical learning. It should be possible to
+<p>Our <strong><a href="/tutorials">tutorials</a></strong> are intended for step-by-step practical learning. It should be possible to
 start them right away without prior experience with Eclipse MOSAIC. However, for several aspects, the documentation should be
 consulted at least in parallel.</p>
   </div>
@@ -1087,7 +1187,7 @@
                 <span class="title">
                     <span class="counter">7.&nbsp;</span>
                     MOSAIC Configuration
-                </span><span class="subtitle">Technical documentation, such as Javadoc.</span><span class="link-wrap">
+                </span><span class="subtitle">Complete documentation of configuration files.</span><span class="link-wrap">
                     <a href="/mosaic/docs/mosaic_configuration/" title="MOSAIC Configuration" class="mosaic-btn mosaic-btn-secondary btn-bottom">Learn more</a>
                 </span>
             </span>
diff --git a/docs/mosaic_configuration/cell_config/index.html b/docs/mosaic_configuration/cell_config/index.html
new file mode 100644
index 0000000..9e102fe
--- /dev/null
+++ b/docs/mosaic_configuration/cell_config/index.html
@@ -0,0 +1,1722 @@
+<!DOCTYPE html><html lang="en-us" >
+
+
+
+
+  
+
+
+<head>
+
+  <meta charset="utf-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="generator" content="Source Themes Academic 4.8.0">
+
+  
+
+  
+  
+  
+  
+  
+    
+    
+    
+  
+  
+
+  <meta name="author" content="Fraunhofer FOKUS">
+
+  
+  
+  
+    
+  
+  <meta name="description" content="">
+
+  
+  <link rel="alternate" hreflang="en-us" href="https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_config/">
+
+  
+
+
+  
+  
+  
+  <meta name="theme-color" content="#68145C">
+  
+
+  
+  
+  
+  <script src="/mosaic/js/mathjax-config.js"></script>
+  
+
+  
+  
+  
+  
+    
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/academicons/1.8.6/css/academicons.min.css" integrity="sha512-MCWBwPSput2UWNwyznVFLbD2iUc1e5VsdD1zahsWVzkDSUzyHhMZ4kCS3wgYSRm0mU+glwD/Q9lSJrDPwbUL2A==" crossorigin="anonymous">
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.0-1/css/all.min.css" integrity="sha512-ZYg+hQvLlM0W9C3P6vTpes5LmJ66G2EsroxDNzwD6qiulckldb29eD9I672HL2X+LH5nRhY1sQqZLJGB+aUUPg==" crossorigin="anonymous">
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/fancybox/3.5.7/jquery.fancybox.min.css" integrity="sha512-H9jrZiiopUdsLpg94A333EfumgUBpO9MdbxStdeITo+KEIMaNfHNvwyjjDJb+ERPaRS6DpyRlKbvPUasNItRyw==" crossorigin="anonymous">
+
+    
+    
+    
+      
+    
+    
+      
+      
+        <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/styles/atom-one-light.min.css" crossorigin="anonymous" title="hl-light">
+        <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/styles/atom-one-light.min.css" crossorigin="anonymous" title="hl-dark" disabled>
+      
+    
+
+    
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/leaflet/1.5.1/leaflet.css" integrity="sha512-xwE/Az9zrjBIphAcBb3F6JVqxf46+CDLwfLMHloNu6KEQCAWi6HcDUbeOfBIptF7tcCzusKFjFw2yuvEpDL9wQ==" crossorigin="anonymous">
+    
+
+    
+
+    
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/lazysizes/5.2.2/lazysizes.min.js" integrity="sha512-TmDwFLhg3UA4ZG0Eb4MIyT1O1Mb+Oww5kFG0uHqXsdbyZz9DcvYQhKpGgNkamAI6h2lGGZq2X8ftOJvF/XjTUg==" crossorigin="anonymous" async></script>
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/3.1.0/es5/tex-chtml.min.js" integrity="sha512-uwL1UtpYdWra2iqJlAW8Ts0s9Os6IxWLDJDF/BnWdhDmT7DEMFba3GPsFwmV3QiTNcUyl2GB5vsgycB/MOvo9g==" crossorigin="anonymous" async></script>
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+
+  
+
+  
+  
+  
+  <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:400,400i,700,700i%7CRoboto+Mono&display=swap">
+  
+
+  
+  
+  
+  
+  <link rel="stylesheet" href="/mosaic/css/academic.css">
+
+  
+
+
+
+
+  
+
+
+  
+  
+
+  
+  <link rel="alternate" href="/mosaic/docs/mosaic_configuration/cell_config/index.xml" type="application/rss+xml" title="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
+  
+
+  <link rel="manifest" href="/mosaic/index.webmanifest">
+  <link rel="icon" type="image/png" href="/mosaic/images/icon_hu6bdfb97c7e23190c70e41ca0e15a9fce_30436_32x32_fill_lanczos_center_2.png">
+  <link rel="apple-touch-icon" type="image/png" href="/mosaic/images/icon_hu6bdfb97c7e23190c70e41ca0e15a9fce_30436_192x192_fill_lanczos_center_2.png">
+
+  <link rel="canonical" href="https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_config/">
+
+  
+  
+  
+  
+  
+  
+  
+    
+    
+  
+  
+  <meta property="twitter:card" content="summary">
+  
+  <meta property="og:site_name" content="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
+  <meta property="og:url" content="https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_config/">
+  <meta property="og:title" content="Cell Simulator – Basic Configuration | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
+  <meta property="og:description" content=""><meta property="og:image" content="https://www.eclipse.org/mosaic/images/logo.svg">
+  <meta property="twitter:image" content="https://www.eclipse.org/mosaic/images/logo.svg"><meta property="og:locale" content="en-us">
+  
+    
+  
+
+  
+
+
+
+
+  
+
+
+  
+
+
+
+
+
+  <title>Cell Simulator – Basic Configuration | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility</title>
+
+</head>
+
+<body id="top" data-spy="scroll" data-offset="70" data-target="#TableOfContents" class=" page-mosaic page-docs page-mosaic_configuration page-cell_config ">
+
+  <aside class="search-results" id="search">
+  <div class="container">
+    <section class="search-header">
+
+      <div class="row no-gutters justify-content-between mb-3">
+        <div class="col-10 col-md-3">
+          <div class="logo" style="background-image: url(/mosaic/img/logos/mosaic/EclipseMOSAIC-Logo-RGB-positiv.svg)"></div>
+        </div>
+        <div class="col-2 col-md-4 col-search-close">
+          <a class="js-search" href="#"><i class="fas fa-times-circle text-muted" aria-hidden="true"></i></a>
+        </div>
+      </div>
+
+      <div id="search-box">
+        
+        <input name="q" id="search-query" placeholder="Search..." autocapitalize="off"
+        autocomplete="off" autocorrect="off" spellcheck="false" type="search">
+        
+      </div>
+
+    </section>
+    <section class="section-search-results">
+
+      <div id="search-hits">
+        
+      </div>
+
+    </section>
+  </div>
+</aside>
+
+
+  
+
+
+
+
+
+
+  
+
+
+
+  
+
+
+<nav class="navbar navbar-expand-lg navbar-light compensate-for-scrollbar" id="navbar-main">
+  <div class="container">
+
+    <div class="d-none d-lg-inline-flex">
+      <a style="visibility:visible;" class="navbar-brand" href="/mosaic/"><img src="/mosaic/images/logo.svg" alt="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility"></a>
+    </div>
+
+
+    
+    <button type="button" class="navbar-toggler" data-bs-toggle="collapse" data-bs-target="#navbar-content-mobile" aria-controls="navbar" aria-expanded="false" aria-label="Toggle navigation">
+      <span><i class="fas fa-bars"></i></span>
+    </button>
+    
+
+    
+    <div class="navbar-brand-mobile-wrapper d-inline-flex d-lg-none">
+      <a class="navbar-brand" href="/mosaic/"><img src="/mosaic/images/logo.svg" alt="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility"></a>
+    </div>
+    
+
+    
+    
+    <div id="navbar-content" class="navbar-collapse main-menu-item collapse justify-content-start">
+
+    
+    <ul class="navbar-nav d-md-inline-flex">
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/about/"><span>About</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/news/"><span>News</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link  active" href="/mosaic/docs/"><span>Documentation</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/tutorials/"><span>Tutorials</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/download/"><span>Download</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/community/"><span>Community</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+    </ul>
+  </div>
+
+    <ul class="nav-icons navbar-nav flex-row ml-auto d-flex pl-md-2">
+      
+      <li class="nav-item">
+        <a class="nav-link js-search" href="#" aria-label="Search"><i class="fas fa-search" aria-hidden="true"></i></a>
+      </li>
+      
+
+      
+
+      
+      <li class="nav-item ">
+        <a href="https://github.com/eclipse/mosaic" target="blank">
+          <i class="fab fa-github" aria-hidden="true"></i>
+        </a>
+      </li>
+      
+
+      
+
+    </ul>
+
+    
+    
+    <div id="navbar-content-mobile" class="navbar-collapse main-menu-item collapse justify-content-start d-lg-none">
+
+    
+      <ul class="navbar-nav d-inline-flex">
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/about/"><span>About</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/news/"><span>News</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link  active" href="/mosaic/docs/"><span>Documentation</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/tutorials/"><span>Tutorials</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/download/"><span>Download</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/community/"><span>Community</span></a>
+        </li>
+
+        
+        
+
+      
+
+        
+      </ul>
+    </div>
+
+  </div>
+</nav>
+
+
+  
+
+<div class="docs container">
+  <div class="row flex-xl-nowrap">
+    <div class="docs-sidebar col-12 col-md-3 col-xl-3">
+      
+
+
+
+
+
+  
+    
+  
+
+
+
+
+
+<div class="docs-version">
+  
+  
+  
+  <a class="" data-bs-toggle="tooltip" data-bs-placement="bottom" title="The documentation corresponds to the latest version of Eclipse MOSAIC 20.1-SNAPSHOT." href="https://github.com/eclipse/mosaic">
+    <i class="fab fa-github"></i>&nbsp;Eclipse MOSAIC 20.1-SNAPSHOT
+  </a>
+</div>
+
+<form class="docs-search d-flex align-items-center">
+  <button class="btn docs-toggle d-md-none p-0 mr-3" type="button" data-bs-toggle="collapse" data-bs-target="#docs-nav" aria-controls="docs-nav" aria-expanded="false" aria-label="Toggle section navigation">
+    <span><i class="fas fa-bars"></i></span>
+  </button>
+
+  
+  <input name="q" type="search" class="form-control" placeholder="Search..." autocomplete="off">
+  
+</form>
+
+<nav class="collapse docs-links" id="docs-nav">
+  
+  
+    
+    
+    
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/getting_started/">Getting Started</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/getting_started/">Download</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/getting_started/run_mosaic/">Run Eclipse MOSAIC</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/getting_started/results/">Simulation Results</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/visualization/">Visualization</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/visualization/">WebSocket Visualizer</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/visualization/filevis/">File Output</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/visualization/statistics/">Statistics Output</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/visualization/itef/">ITEF</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/visualization/phabmap/">PHABMap</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/simulators/">Simulators</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/simulators/">Overview</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/application_simulator/">Application Simulator</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/traffic_simulator_sumo/">Traffic - Eclipse SUMO</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/network_simulator_omnetpp/">Network - OMNeT&#43;&#43;</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/network_simulator_ns3/">Network - ns-3</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/network_simulator_sns/">Network - SNS</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/network_simulator_cell/">Network - Cell</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/environment_simulator/">Environment Simulator</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/battery_simulator/">Battery Simulator</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/vms_simulator/">VMS Simulator</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/building_scenarios/">Building Scenarios</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/building_scenarios/">Simulation Scenarios</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/building_scenarios/scenario_convert/">Scenario Convert</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/building_scenarios/scenario_configuration/">Additional Scenario Configuration</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/develop_applications/">Create Applications</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/develop_applications/">Basics</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/develop_applications/communication/">V2X Communication</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/develop_applications/event_scheduler/">Event Scheduling</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/develop_applications/road_traffic/">Scenario Database</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/extending_mosaic/">Extending Eclipse MOSAIC</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/">Core Concepts</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/simulator_coupling/">Simulator Coupling</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/interactions/">Interactions</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/application_ambassador_details/">Application Ambassador</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/sumo_ambassador_details/">Sumo Ambassador</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/omnetpp_details/">OMNeT&#43;&#43; Federate</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/delay_models/">Delay Models</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/mosaic_configuration/">MOSAIC Configuration</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/">Configuration Files</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/environment_config/">Environment Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/sns_config/">SNS Configuration</a>
+        </li>
+        
+        <li class="active">
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_region_config/">Cell Region Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/sumo_config/">SUMO Configuration</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/api_docs/">API Documentation</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/api_docs/">Javadoc</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="nav-bottom">
+      <img src="/mosaic/img/logos/mosaic/EclipseMOSAIC-Medallion-RGB-single-navy.svg">
+    </div>
+  
+</nav>
+
+    </div>
+
+    
+    <div class="docs-toc d-none d-xl-block col-xl-2">
+      <ul class="nav toc-top">
+        <li><a href="#" id="back_to_top" class="docs-toc-title">Contents</a></li>
+      </ul>
+
+      <nav id="TableOfContents">
+  <ul>
+    <li><a href="#cell">Cell</a></li>
+    <li><a href="#bandwidthmeasurement">bandwidthMeasurement</a>
+      <ul>
+        <li><a href="#bandwidthmeasurementtransmissionmode">bandwidthMeasurement.transmissionMode</a></li>
+      </ul>
+    </li>
+  </ul>
+</nav>
+
+      
+    </div>
+    
+
+    <style>
+      @media (min-width:1140px) {
+        .docs-sidebar {
+          flex: 0 1 320px;
+        }
+        .docs-toc {
+          flex: 0 1 280px;
+        }
+        main.docs-content.no-docs-toc {
+          padding-bottom: 0 !important;
+          max-width: calc(100% - 320px) !important;
+          flex: 0 1 calc(100% - 320px);
+          width: 100%;
+        }
+        main.docs-content {
+          padding-bottom: 0 !important;
+          max-width: calc(100% - 600px) !important;
+          flex: 0 1 calc(100% - 600px);
+          width: 100%;
+        }
+      }
+      @media (max-width: 770px) {
+        main.docs-content {
+          max-width: 100% !important;
+          width: 100%;
+        }
+      }
+      @media (min-width: 771px) and(max-width: 1139px) {
+        main.docs-content.no-docs-toc {
+          padding-bottom: 0 !important;
+          max-width: calc(100% - 320px) !important;
+          width: 100%;
+        }
+      }
+    </style>
+    <main class="docs-content col-12 col-md-9 col-xl-auto py-md-3 pl-md-4" role="main">
+
+      <article class="article">
+
+        <div class="docs-article-container">
+          <h1>Cell Simulator – Basic Configuration</h1>
+
+          <div class="article-style">
+            <div class="alert alert-tip">
+  <div>
+  <p>You can use a <a href="/mosaic/docs/mosaic_configuration/#readable-units" title="Readable Unit">Readable Unit</a> anywhere where you
+have the option of:</p>
+<ul>
+<li><code>number</code> <strong>or</strong> <code>string</code></li>
+<li><code>integer</code> <strong>or</strong> <code>string</code></li>
+</ul>
+  </div>
+</div>
+<hr>
+<p>📃 <strong>Corresponding configuration file: <code>cell/cell_config.json</code></strong></p>
+<hr>
+<p><a name="reference-cell"></a></p>
+<h2 id="cell">Cell</h2>
+<p>This schema describes the JSON file structure for the cell configuration, which provides general configuration for the ambassador, such as paths to the regions and network configuration files.</p>
+<p><strong>Properties</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th>Type</th>
+<th>Description</th>
+<th>Required</th>
+<th>Boundaries</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>bandwidthMeasurementInterval</td>
+<td><code>number</code></td>
+<td>Interval in which the bandwidth is aggregated, given in seconds.</td>
+<td>No</td>
+<td>[1, +$\infty$]</td>
+<td><code>1</code></td>
+</tr>
+<tr>
+<td>bandwidthMeasurementCompression</td>
+<td><code>boolean</code></td>
+<td>If enabled, the export files with bandwidth measurements will be compressed using gzip compression.</td>
+<td>No</td>
+<td>None</td>
+<td><code>false</code></td>
+</tr>
+<tr>
+<td>networkConfigurationFile</td>
+<td><code>string</code></td>
+<td>Relative path to the network configuration file.</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td><code>network.json</code></td>
+</tr>
+<tr>
+<td>regionConfigurationFile</td>
+<td><code>string</code></td>
+<td>Relative path to the region configuration file.</td>
+<td>No</td>
+<td>None</td>
+<td><code>regions.json</code></td>
+</tr>
+<tr>
+<td>bandwidthMeasurements</td>
+<td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-bandwidthmeasurement">
+    <code>bandwidthMeasurement[]</code>
+</a>
+</td>
+<td>Measure the bandwidth between regions.</td>
+<td>No</td>
+<td>None</td>
+<td>None</td>
+</tr>
+</tbody>
+</table>
+<hr>
+<p><a name="reference-bandwidthmeasurement"></a></p>
+<h2 id="bandwidthmeasurement">bandwidthMeasurement</h2>
+<p>Object to define the bandwidth measurement between regions.</p>
+<p><strong>Properties</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th>Type</th>
+<th>Description</th>
+<th>Required</th>
+<th>Boundaries</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>fromRegion</td>
+<td><code>string</code></td>
+<td>Measure the bandwidth of messages which originate in this region (use wildcard * for all regions).</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>toRegion</td>
+<td><code>string</code></td>
+<td>Measure the bandwidth of messages which target in this region (use wildcard * for all regions).</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>transmissionMode</td>
+<td><code>string</code></td>
+<td>Defines the transmission mode which is observed.</td>
+<td>✓ Yes</td>
+<td>Enum
+
+
+
+
+
+  
+  
+
+<a href="#restriction-bandwidthmeasurementtransmissionmode">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
+<td>None</td>
+</tr>
+<tr>
+<td>applicationClass</td>
+<td><code>string</code></td>
+<td>The application Class.</td>
+<td>No</td>
+<td>None</td>
+<td><code>*</code></td>
+</tr>
+</tbody>
+</table>
+<p><strong>Further property restrictions:</strong><br>
+<a name="restriction-bandwidthmeasurementtransmissionmode"></a></p>
+<h3 id="bandwidthmeasurementtransmissionmode">bandwidthMeasurement.transmissionMode</h3>
+<ul>
+<li><strong>Allowed values</strong>:
+<ul>
+<li><code>UplinkUnicast</code></li>
+<li><code>DownlinkUnicast</code></li>
+<li><code>DownlinkMulticast</code></li>
+</ul>
+</li>
+</ul>
+
+          </div>
+
+          
+
+
+
+          
+          <div class="article-widget">
+            
+<div class="post-nav prev-next-pages col-12">
+  <div class="row">
+    <div class="post-nav-item col-6">
+      
+        
+      
+    </div>
+
+    <div class="post-nav-item col-6 align-self-end">
+      
+        
+          
+          
+          
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+          
+        
+      
+    </div>
+  </div>
+</div>
+
+          </div>
+          
+        </div>
+
+        
+          
+
+          
+
+          
+
+          
+  
+  
+
+
+        
+
+
+        <footer class="site-footer">
+  <div class="row">
+  
+    
+      <div class="col-sm-4 mb-3 mb-md-0">
+        <b>Eclipse MOSAIC</b>
+        
+          <ul>
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/download/" title="Download Eclipse MOSAIC" >
+                    
+                      Download Eclipse MOSAIC
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/docs/" title="Documentation" >
+                    
+                      Documentation
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/tutorials/" title="Tutorials" >
+                    
+                      Tutorials
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/community/#projects" title="Projects" >
+                    
+                      Projects
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/publications/" title="Publications" >
+                    
+                      Publications
+                    
+                  </a>
+                </li>
+              
+            
+          </ul>
+        
+      </div>
+    
+  
+    
+      <div class="col-sm-4 mb-3 mb-md-0">
+        <b>Community</b>
+        
+          <ul>
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/community/" title="Eclipse MOSAIC Community" >
+                    
+                      Eclipse MOSAIC Community
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/contribution/" title="How to contribute" >
+                    
+                      How to contribute
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://github.com/eclipse/mosaic" title="Github"  target="_blank" rel="noopener">
+                    
+                      Github
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/get_in_contact/" title="Contact &amp; Mailing list" >
+                    
+                      Contact & Mailing list
+                    
+                  </a>
+                </li>
+              
+            
+          </ul>
+        
+      </div>
+    
+  
+    
+      <div class="col-sm-4 mb-3 mb-md-0">
+        <b>Eclipse Foundation</b>
+        
+          <ul>
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/" title="About Eclipse Foundation"  target="_blank" rel="noopener">
+                    
+                      About Eclipse Foundation
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/legal/privacy.php" title="Privacy Policy"  target="_blank" rel="noopener">
+                    
+                      Privacy Policy
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/legal/termsofuse.php" title="Website terms of use"  target="_blank" rel="noopener">
+                    
+                      Website terms of use
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/legal/copyright.php" title="Copyright"  target="_blank" rel="noopener">
+                    
+                      Copyright
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/legal" title="Legal"  target="_blank" rel="noopener">
+                    
+                      Legal
+                    
+                  </a>
+                </li>
+              
+            
+          </ul>
+        
+      </div>
+    
+  
+
+
+
+
+
+
+
+
+
+
+
+  </div>
+  <div class="row justify-content-center mt-3 position-relative">
+    <p class="powered-by text-center font-italic mb-0 pb-0">
+      Powered by the
+      <a href="https://sourcethemes.com/academic/" target="_blank" rel="noopener">Academic theme</a> for
+      <a href="https://gohugo.io" target="_blank" rel="noopener">Hugo</a>.
+      <br>
+      Header image &#169; fanjianhua/ iStock
+    </p>
+    
+  </div>
+</footer>
+
+
+
+      </article>
+    </main>
+  </div>
+</div>
+
+
+      
+
+    
+    
+    
+      <script src="https://code.jquery.com/jquery-3.4.1.min.js" integrity="sha384-vk5WoKIaW/vJyUAd9n/wmopsmNhiy+L2Z+SBxGYnUkunIxVxAv/UtMOhba/xskxh" crossorigin="anonymous"></script>
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/2.6.0/umd/popper.min.js" integrity="sha512-BmM0/BQlqh02wuK5Gz9yrbe7VyIVwOzD1o40yi1IsTjriX/NGF37NyXHfmFzIlMmoSIBXgqDiG1VNU6kB5dBbA==" crossorigin="anonymous"></script>
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery.imagesloaded/4.1.4/imagesloaded.pkgd.min.js" integrity="sha512-S5PZ9GxJZO16tT9r3WJp/Safn31eu8uWrzglMahDT4dsmgqWonRY9grk3j+3tfuPr9WJNsfooOR7Gi7HL5W2jw==" crossorigin="anonymous"></script>
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery.isotope/3.0.6/isotope.pkgd.min.js" integrity="sha512-Zq2BOxyhvnRFXu0+WE6ojpZLOU2jdnqbrM1hmVdGzyeCa1DgM3X5Q4A/Is9xA1IkbUeDd7755dNNI/PzSf2Pew==" crossorigin="anonymous"></script>
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/fancybox/3.5.7/jquery.fancybox.min.js" integrity="sha512-uURl+ZXMBrF4AwGaWmEetzrd+J5/8NRkWAvJx5sbPSSuOb0bZLqf+tOzniObO00BjHa/dD7gub9oCGMLPQHtQA==" crossorigin="anonymous"></script>
+
+      
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/mermaid/8.4.8/mermaid.min.js" integrity="sha512-1tS1YUns336Mtxl+vkaLcADPwE1CPNVy3WEf7nrI7DGMMb6/FAVBgL2IzAWVBkB6vVuK94s2zVoiXcw1QZ9S1g==" crossorigin="anonymous" title="mermaid"></script>
+      
+
+      
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/highlight.min.js" integrity="sha512-1LdB3V708w6G4QRl7NsVdTr7MDibyRXr9stQZ+EGjEE0ZPMZkA//ir7kCWmFyxdAJNIRXdR/ZeJmCV0boyiCXw==" crossorigin="anonymous"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/java.min.js"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/json.min.js"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/xml.min.js"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/shell.min.js"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/dos.min.js"></script>
+        
+      
+
+    
+
+    
+    
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/leaflet/1.5.1/leaflet.js" integrity="sha512-GffPMF3RvMeYyc1LWMHtK8EbPv0iNZ8/oTtHPx9/cc2ILxQ+u905qIwdpULaqDkyBKgOaB57QTMg7ztg8Jm2Og==" crossorigin="anonymous"></script>
+    
+
+    
+    
+    <script>const code_highlighting = true;</script>
+    
+
+    
+    
+    <script>const isSiteThemeDark = false;</script>
+    
+
+    
+    
+    
+    
+    
+    
+    <script>
+      const search_config = {"indexURI":"/mosaic/index.json","minLength":1,"threshold":0.3};
+      const i18n = {"no_results":"No results found","placeholder":"Search...","results":"results found"};
+      const content_type = {
+        'post': "Posts",
+        'project': "Projects",
+        'publication' : "Publications",
+        'talk' : "Talks"
+        };
+    </script>
+    
+
+    
+    
+    <script src="https://cdnjs.cloudflare.com/ajax/libs/anchor-js/4.1.1/anchor.min.js" integrity="sha512-aZotBPy6dqn8yVaLJwSrkJ+QxuxV695A4dgodAMvTU5JyNi5mhrr+LeaD3GSS+lx1SMFKNs0tu5ZMJEgNZQP2Q==" crossorigin="anonymous"></script>
+    <script>
+      anchors.add();
+    </script>
+    
+
+    
+    
+    <script id="search-hit-fuse-template" type="text/x-template">
+      <div class="search-hit" id="summary-{{key}}">
+      <div class="search-hit-content">
+        <div class="search-hit-name">
+          <a href="{{relpermalink}}">{{title}}</a>
+          <div class="article-metadata search-hit-type">{{type}}</div>
+          <p class="search-hit-description">{{snippet}}</p>
+        </div>
+      </div>
+      </div>
+    </script>
+    
+
+    
+    
+    <script src="https://cdnjs.cloudflare.com/ajax/libs/fuse.js/3.2.1/fuse.min.js" integrity="sha512-o38bmzBGX+hD3JHWUFCDA09btWaqrNmoJ3RXLlrysA7PP01Kgs4UlE4MhelE1v5dJR3+cxlR4qQlotsW7jKsnw==" crossorigin="anonymous"></script>
+    <script src="https://cdnjs.cloudflare.com/ajax/libs/mark.js/8.11.1/jquery.mark.min.js" integrity="sha512-mhbv5DqBMgrWL+32MmsDOt/OAvqr/cHimk6B8y/bx/xS88MVkYGPiVv2ixKVrkywF2qHplNRUvFsAHUdxZ3Krg==" crossorigin="anonymous"></script>
+    
+
+    
+    
+
+    
+    
+
+    
+    
+
+    
+    
+    
+    
+    
+    
+    
+    
+    
+      
+    
+    
+    
+    
+    <script type="application/javascript" src="/mosaic/js/academic.min.0992ad8b8d033c3858bb90b03966346a.js"></script>
+
+    
+
+<script type="application/javascript" src="/mosaic/js/mosaic-wg-cards.js"></script>
+
+
+
+
+    <script>
+      var tooltipTriggerList = [].slice.call(document.querySelectorAll('[data-bs-toggle="tooltip"]'))
+      tooltipTriggerList.map(function (tooltipTriggerEl) {
+        return new window.bootstrap.Tooltip(tooltipTriggerEl)
+      })
+    </script>
+
+
+  
+  
+
+  
+<div id="modal" class="modal fade" role="dialog">
+  <div class="modal-dialog">
+    <div class="modal-content">
+      <div class="modal-header">
+        <h5 class="modal-title">Cite</h5>
+        <button type="button" class="close" data-dismiss="modal" aria-label="Close">
+          <span aria-hidden="true">&times;</span>
+        </button>
+      </div>
+      <div class="modal-body">
+        <pre><code class="tex hljs"></code></pre>
+      </div>
+      <div class="modal-footer">
+        <a class="btn btn-outline-primary my-1 js-copy-cite" href="#" target="_blank">
+          <i class="fas fa-copy"></i> Copy
+        </a>
+        <a class="btn btn-outline-primary my-1 js-download-cite" href="#" target="_blank">
+          <i class="fas fa-download"></i> Download
+        </a>
+        <div id="modal-error"></div>
+      </div>
+    </div>
+  </div>
+</div>
+
+</body>
+</html>
diff --git a/docs/mosaic_configuration/cell_config/index.xml b/docs/mosaic_configuration/cell_config/index.xml
new file mode 100644
index 0000000..1b1a8ee
--- /dev/null
+++ b/docs/mosaic_configuration/cell_config/index.xml
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>Cell Simulator – Basic Configuration | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility</title>
+    <link>https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_config/</link>
+      <atom:link href="https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_config/index.xml" rel="self" type="application/rss+xml" />
+    <description>Cell Simulator – Basic Configuration</description>
+    <generator>Source Themes Academic (https://sourcethemes.com/academic/)</generator><language>en-us</language>
+    <image>
+      <url>https://www.eclipse.org/mosaic/images/logo.svg</url>
+      <title>Cell Simulator – Basic Configuration</title>
+      <link>https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_config/</link>
+    </image>
+    
+  </channel>
+</rss>
diff --git a/docs/mosaic_configuration/cell_network_config/index.html b/docs/mosaic_configuration/cell_network_config/index.html
index 85c9633..ff332e4 100644
--- a/docs/mosaic_configuration/cell_network_config/index.html
+++ b/docs/mosaic_configuration/cell_network_config/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -907,6 +911,10 @@
           <a href="/mosaic/docs/mosaic_configuration/sns_config/">SNS Configuration</a>
         </li>
         
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
         <li class="active">
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
@@ -953,7 +961,7 @@
 
       <nav id="TableOfContents">
   <ul>
-    <li><a href="#cnetworkscheme">CNetworkScheme</a></li>
+    <li><a href="#network">Network</a></li>
     <li><a href="#globalnetwork">globalNetwork</a></li>
     <li><a href="#globalnetworkuplink">globalNetwork.uplink</a></li>
     <li><a href="#delay">delay</a></li>
@@ -1040,8 +1048,10 @@
   </div>
 </div>
 <hr>
-<p><a name="reference-cnetworkscheme"></a></p>
-<h2 id="cnetworkscheme">CNetworkScheme</h2>
+<p>📃 <strong>Corresponding configuration file: <code>cell/network.json</code></strong></p>
+<hr>
+<p><a name="reference-network"></a></p>
+<h2 id="network">Network</h2>
 <p>Schema describing the JSON file structure for the network configuration. It is is used to define the properties of the global network. If defined as a number, then the default unit is Gb. Alternatively this can be defined as a string to specify the unit of measurement (e.g. &lsquo;3 MB&rsquo;).</p>
 <p><strong>Properties</strong></p>
 <table>
@@ -1075,7 +1085,18 @@
 <tr>
 <td>globalNetwork</td>
 <td>
-<a href="#reference-globalnetwork"><code>globalNetwork</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-globalnetwork">
+    <code>globalNetwork</code>
+</a>
+</td>
 <td>Object to define all coverage properties of one region of the radio access network (ran-part). Such a configuration consists of one uplink-module and one downlink-module. In this context, uplink and downlink always refer to the direction TOWARDS and respectively FROM the GEO entity.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1084,7 +1105,18 @@
 <tr>
 <td>servers</td>
 <td>
-<a href="#reference-server"><code>server</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-server">
+    <code>server</code>
+</a>
+</td>
 <td>List of configured servers.</td>
 <td>No</td>
 <td>None</td>
@@ -1112,7 +1144,18 @@
 <tr>
 <td>uplink</td>
 <td>
-<a href="#reference-globalnetwork.uplink"><code>globalNetwork.uplink</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-globalnetwork.uplink">
+    <code>globalNetwork.uplink</code>
+</a>
+</td>
 <td>Object to define the uplink of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1121,7 +1164,18 @@
 <tr>
 <td>downlink</td>
 <td>
-<a href="#reference-globalnetwork.downlink"><code>globalNetwork.downlink</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-globalnetwork.downlink">
+    <code>globalNetwork.downlink</code>
+</a>
+</td>
 <td>Object to define the downlink of a network. The downlink supports two individual paths: Point-to-point communication (unicast) and Point-to-multipoint communication (multicast).</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1149,7 +1203,18 @@
 <tr>
 <td>delay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1158,7 +1223,18 @@
 <tr>
 <td>transmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1189,11 +1265,44 @@
 <p><strong>Additionally ONE of the following property definitions apply:</strong></p>
 <ul>
 <li>
-<a href="#reference-gammaDelay">gammaDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-gammaDelay">
+    gammaDelay
+</a>
+</li>
 <li>
-<a href="#reference-constantDelay">constantDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-constantDelay">
+    constantDelay
+</a>
+</li>
 <li>
-<a href="#reference-simpleRandomDelay">simpleRandomDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-simpleRandomDelay">
+    simpleRandomDelay
+</a>
+</li>
 </ul>
 <hr>
 <p><a name="reference-gammadelay"></a></p>
@@ -1218,7 +1327,18 @@
 <td>The type of delay.</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-gammadelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-gammadelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1273,7 +1393,18 @@
 <td>The type of delay.</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-constantdelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-constantdelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1319,7 +1450,18 @@
 <td>The type of delay.</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-simplerandomdelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-simplerandomdelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1413,7 +1555,18 @@
 <tr>
 <td>unicast</td>
 <td>
-<a href="#reference-unicast"><code>unicast</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-unicast">
+    <code>unicast</code>
+</a>
+</td>
 <td>Point-to-point communication (unicast).</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1422,7 +1575,18 @@
 <tr>
 <td>multicast</td>
 <td>
-<a href="#reference-multicast"><code>multicast</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-multicast">
+    <code>multicast</code>
+</a>
+</td>
 <td>Point-to-multipoint communication (multicast).</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1458,7 +1622,18 @@
 <tr>
 <td>delay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1467,7 +1642,18 @@
 <tr>
 <td>transmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1495,7 +1681,18 @@
 <tr>
 <td>delay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1504,7 +1701,18 @@
 <tr>
 <td>transmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1547,7 +1755,18 @@
 <tr>
 <td>uplink</td>
 <td>
-<a href="#reference-server.uplink"><code>server.uplink</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-server.uplink">
+    <code>server.uplink</code>
+</a>
+</td>
 <td>Object to define uplink properties of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity.</td>
 <td>No</td>
 <td>None</td>
@@ -1556,7 +1775,18 @@
 <tr>
 <td>downlink</td>
 <td>
-<a href="#reference-server.downlink"><code>server.downlink</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-server.downlink">
+    <code>server.downlink</code>
+</a>
+</td>
 <td></td>
 <td>No</td>
 <td>None</td>
@@ -1567,7 +1797,18 @@
 <p><strong>The following additional properties are allowed:</strong></p>
 <ul>
 <li>
-<a href="#reference-undefined">undefined</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-undefined">
+    undefined
+</a>
+</li>
 </ul>
 <hr>
 <p><a name="reference-server-uplink"></a></p>
@@ -1589,7 +1830,18 @@
 <tr>
 <td>delay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1598,7 +1850,18 @@
 <tr>
 <td>transmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1609,7 +1872,18 @@
 <p><strong>The following additional properties are allowed:</strong></p>
 <ul>
 <li>
-<a href="#reference-undefined">undefined</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-undefined">
+    undefined
+</a>
+</li>
 </ul>
 <hr>
 <p><a name="reference-server-downlink"></a></p>
@@ -1630,7 +1904,18 @@
 <tr>
 <td>unicast</td>
 <td>
-<a href="#reference-unicast"><code>unicast</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-unicast">
+    <code>unicast</code>
+</a>
+</td>
 <td>Point-to-point communication (unicast).</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1641,7 +1926,18 @@
 <p><strong>The following additional properties are allowed:</strong></p>
 <ul>
 <li>
-<a href="#reference-undefined">undefined</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-undefined">
+    undefined
+</a>
+</li>
 </ul>
 
           </div>
diff --git a/docs/mosaic_configuration/cell_region_config/index.html b/docs/mosaic_configuration/cell_region_config/index.html
index 23a1d76..d6449fa 100644
--- a/docs/mosaic_configuration/cell_region_config/index.html
+++ b/docs/mosaic_configuration/cell_region_config/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -953,7 +961,7 @@
 
       <nav id="TableOfContents">
   <ul>
-    <li><a href="#cregionschema">CRegionSchema</a></li>
+    <li><a href="#regions">Regions</a></li>
     <li><a href="#mobilenetworkproperties">mobileNetworkProperties</a></li>
     <li><a href="#georectangle">geoRectangle</a></li>
     <li><a href="#geopoint">geoPoint</a></li>
@@ -1039,8 +1047,10 @@
   </div>
 </div>
 <hr>
-<p><a name="reference-cregionschema"></a></p>
-<h2 id="cregionschema">CRegionSchema</h2>
+<p>📃 <strong>Corresponding configuration file: <code>cell/regions.json</code></strong></p>
+<hr>
+<p><a name="reference-regions"></a></p>
+<h2 id="regions">Regions</h2>
 <p>Schema describing the JSON file structure for the regional networks configuration. It is is used to extend the network with regional information, which enables the emulation of mobile networks. If configured very granular, these regions can reflect cells as used in the real world. Though for most use-cases it is sufficient to approximate the behaviour by defining larger regions.</p>
 <p><strong>Properties</strong></p>
 <table>
@@ -1058,7 +1068,18 @@
 <tr>
 <td>regions</td>
 <td>
-<a href="#reference-mobilenetworkproperties"><code>mobileNetworkProperties[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-mobilenetworkproperties">
+    <code>mobileNetworkProperties[]</code>
+</a>
+</td>
 <td>An array of regional network configruations.</td>
 <td>No</td>
 <td>None</td>
@@ -1094,7 +1115,18 @@
 <tr>
 <td>area</td>
 <td>
-<a href="#reference-georectangle"><code>geoRectangle</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-georectangle">
+    <code>geoRectangle</code>
+</a>
+</td>
 <td>Object to define an immutable pair of two different geoPoints. Together they form a rectangular area.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1111,7 +1143,18 @@
 <tr>
 <td>uplink</td>
 <td>
-<a href="#reference-mobilenetworkproperties.uplink"><code>mobileNetworkProperties.uplink</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-mobilenetworkproperties.uplink">
+    <code>mobileNetworkProperties.uplink</code>
+</a>
+</td>
 <td>Object to define the uplink of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1120,7 +1163,18 @@
 <tr>
 <td>downlink</td>
 <td>
-<a href="#reference-mobilenetworkproperties.downlink"><code>mobileNetworkProperties.downlink</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-mobilenetworkproperties.downlink">
+    <code>mobileNetworkProperties.downlink</code>
+</a>
+</td>
 <td>Object to define the downlink of a network. The downlink supports two individual paths: Point-to-point communication (unicast) and Point-to-multipoint communication (multicast).</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1148,7 +1202,18 @@
 <tr>
 <td>nw</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
 <td>Object to define geographical point coordinates.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1157,7 +1222,18 @@
 <tr>
 <td>se</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
 <td>Object to define geographical point coordinates.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1220,7 +1296,18 @@
 <tr>
 <td>delay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1229,7 +1316,18 @@
 <tr>
 <td>transmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1252,11 +1350,44 @@
 <p><strong>Additionally ONE of the following property definitions apply:</strong></p>
 <ul>
 <li>
-<a href="#reference-gammaDelay">gammaDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-gammaDelay">
+    gammaDelay
+</a>
+</li>
 <li>
-<a href="#reference-constantDelay">constantDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-constantDelay">
+    constantDelay
+</a>
+</li>
 <li>
-<a href="#reference-simpleRandomDelay">simpleRandomDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-simpleRandomDelay">
+    simpleRandomDelay
+</a>
+</li>
 </ul>
 <hr>
 <p><a name="reference-gammadelay"></a></p>
@@ -1281,7 +1412,18 @@
 <td>Type of Gamma delay.</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-gammadelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-gammadelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1336,7 +1478,18 @@
 <td>Type of the constant delay</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-constantdelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-constantdelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1382,7 +1535,18 @@
 <td>Type of the delay.</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-simplerandomdelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-simplerandomdelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1476,7 +1640,18 @@
 <tr>
 <td>unicast</td>
 <td>
-<a href="#reference-unicast"><code>unicast</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-unicast">
+    <code>unicast</code>
+</a>
+</td>
 <td>Object to define point-to-point communication.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1485,7 +1660,18 @@
 <tr>
 <td>multicast</td>
 <td>
-<a href="#reference-multicast"><code>multicast</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-multicast">
+    <code>multicast</code>
+</a>
+</td>
 <td>Object to define point-to-multipoint communication.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1521,7 +1707,18 @@
 <tr>
 <td>delay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1530,7 +1727,18 @@
 <tr>
 <td>transmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1558,7 +1766,18 @@
 <tr>
 <td>delay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1567,7 +1786,18 @@
 <tr>
 <td>transmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
diff --git a/docs/mosaic_configuration/environment_config/index.html b/docs/mosaic_configuration/environment_config/index.html
index 138d23c..734a49e 100644
--- a/docs/mosaic_configuration/environment_config/index.html
+++ b/docs/mosaic_configuration/environment_config/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -953,7 +961,7 @@
 
       <nav id="TableOfContents">
   <ul>
-    <li><a href="#cenvironmentscheme">CEnvironmentScheme</a></li>
+    <li><a href="#environment-events">Environment Events</a></li>
     <li><a href="#event">event</a></li>
     <li><a href="#eventtype">eventType</a></li>
     <li><a href="#eventlocation">eventLocation</a></li>
@@ -1028,8 +1036,10 @@
   </div>
 </div>
 <hr>
-<p><a name="reference-cenvironmentscheme"></a></p>
-<h2 id="cenvironmentscheme">CEnvironmentScheme</h2>
+<p>📃 <strong>Corresponding configuration file: <code>environment/environment_config.json</code></strong></p>
+<hr>
+<p><a name="reference-environment-events"></a></p>
+<h2 id="environment-events">Environment Events</h2>
 <p>Schema describing the JSON file structure for the environment configuration. It is is used to define which events are evaluated by the simulator. Entities entering the areas of the events, are notified by the &lsquo;EnvironmentSensorUpdates&rsquo; interaction</p>
 <p><strong>Properties</strong></p>
 <table>
@@ -1047,7 +1057,18 @@
 <tr>
 <td>events</td>
 <td>
-<a href="#reference-event"><code>event[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-event">
+    <code>event[]</code>
+</a>
+</td>
 <td>List of events.</td>
 <td>No</td>
 <td>None</td>
@@ -1075,7 +1096,18 @@
 <tr>
 <td>type</td>
 <td>
-<a href="#reference-eventtype"><code>eventType</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-eventtype">
+    <code>eventType</code>
+</a>
+</td>
 <td>Object to define the type of an event.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1084,7 +1116,18 @@
 <tr>
 <td>location</td>
 <td>
-<a href="#reference-eventlocation"><code>eventLocation</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-eventlocation">
+    <code>eventLocation</code>
+</a>
+</td>
 <td>Object to define the event location configuration, which is either a GeoArea (e.g. rectangle, circle, or polygon) or a specific street segment.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1093,7 +1136,18 @@
 <tr>
 <td>time</td>
 <td>
-<a href="#reference-eventtime"><code>eventTime</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-eventtime">
+    <code>eventTime</code>
+</a>
+</td>
 <td>Object to define the temporal properties of an event.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1156,7 +1210,18 @@
 <tr>
 <td>area</td>
 <td>
-<a href="#reference-area"><code>area</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-area">
+    <code>area</code>
+</a>
+</td>
 <td>Object to define the area in which the event is located in.</td>
 <td>No</td>
 <td>None</td>
@@ -1195,7 +1260,18 @@
 <td>The type of the area.</td>
 <td>No</td>
 <td>Enum
-<a href="#restriction-areatype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-areatype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 </tbody>
@@ -1203,11 +1279,44 @@
 <p><strong>Additionally ANY of the following property definitions apply:</strong></p>
 <ul>
 <li>
-<a href="#reference-geoCircle">geoCircle</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geoCircle">
+    geoCircle
+</a>
+</li>
 <li>
-<a href="#reference-geoRectangle">geoRectangle</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geoRectangle">
+    geoRectangle
+</a>
+</li>
 <li>
-<a href="#reference-geoPolygon">geoPolygon</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geoPolygon">
+    geoPolygon
+</a>
+</li>
 </ul>
 <p><strong>Further property restrictions:</strong><br>
 <a name="restriction-areatype"></a></p>
@@ -1241,7 +1350,18 @@
 <tr>
 <td>center</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
 <td>Object to define geographical point coordinates.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1312,7 +1432,18 @@
 <tr>
 <td>a</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
 <td>Object to define geographical point coordinates.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1321,7 +1452,18 @@
 <tr>
 <td>b</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
 <td>Object to define geographical point coordinates.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1349,7 +1491,18 @@
 <tr>
 <td>vertices</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint[]</code>
+</a>
+</td>
 <td>Set of points representing the vertices of a polygon.</td>
 <td>No</td>
 <td>None</td>
diff --git a/docs/mosaic_configuration/index.html b/docs/mosaic_configuration/index.html
index a497088..561b1f4 100644
--- a/docs/mosaic_configuration/index.html
+++ b/docs/mosaic_configuration/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1012,41 +1020,266 @@
 <table>
 <thead>
 <tr>
-<th>Simulator/Ambassador</th>
 <th>Configuration File</th>
 <th>Documentation</th>
 </tr>
 </thead>
 <tbody>
 <tr>
-<td><a href="/mosaic/docs/simulators/application_simulator#eclipse-mosaic-mapping" title="Mapping">Mapping</a></td>
+<td><code>scenario_config.json</code></td>
+<td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/mosaic_configuration/scenario_config/">
+    Scenario Configuration
+</a>
+</td>
+</tr>
+<tr>
 <td><code>mapping/mapping_config.json</code></td>
-<td>&gt; <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/" title="Mapping Configuration">Mapping Configuration</a></td>
+<td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">
+    Mapping Configuration
+</a>
+</td>
 </tr>
 <tr>
-<td><a href="/mosaic/docs/simulators/environment_simulator" title="Environment">Environment</a></td>
 <td><code>environment/environment_config.json</code></td>
-<td>&gt; <a href="/mosaic/docs/mosaic_configuration/environment_config/" title="Environment Simulator Configuration">Environment Simulator Configuration</a></td>
+<td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/mosaic_configuration/environment_config/">
+    Environment Simulator Configuration
+</a>
+</td>
 </tr>
 <tr>
-<td><a href="/mosaic/docs/simulators/network_simulator_sns" title="Simple Network Simulator">Simple Network Simulator</a></td>
 <td><code>sns/sns_config.json</code></td>
-<td>&gt; <a href="/mosaic/docs/mosaic_configuration/sns_config/" title="SNS Configuration">SNS Configuration</a></td>
+<td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/mosaic_configuration/sns_config/">
+    SNS Configuration
+</a>
+</td>
 </tr>
 <tr>
-<td><a href="/mosaic/docs/simulators/network_simulator_cell" title="Cell">Cell</a></td>
+<td><code>cell/cell_config.json</code></td>
+<td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/mosaic_configuration/cell_config/">
+    Cell Simulator configuration
+</a>
+</td>
+</tr>
+<tr>
 <td><code>cell/regions.json</code></td>
-<td>&gt; <a href="/mosaic/docs/mosaic_configuration/cell_region_config/" title="Regions configuration">Regions configuration</a></td>
+<td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/mosaic_configuration/cell_region_config/">
+    Cell Regions configuration
+</a>
+</td>
 </tr>
 <tr>
-<td><a href="/mosaic/docs/simulators/network_simulator_cell" title="Cell">Cell</a></td>
 <td><code>cell/network.json</code></td>
-<td>&gt; <a href="/mosaic/docs/mosaic_configuration/cell_network_config/" title="Network configuration">Network configuration</a></td>
+<td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/mosaic_configuration/cell_network_config/">
+    Cell Network configuration
+</a>
+</td>
 </tr>
 <tr>
-<td><a href="/mosaic/docs/simulators/traffic_simulator_sumo" title="SUMO">SUMO</a></td>
 <td><code>sumo/sumo_config.json</code></td>
-<td>&gt; <a href="/mosaic/docs/mosaic_configuration/sumo_config/" title="SUMO Ambassador Configuration">SUMO Ambassador Configuration</a></td>
+<td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/mosaic_configuration/sumo_config/">
+    SUMO Ambassador Configuration
+</a>
+</td>
 </tr>
 </tbody>
 </table>
diff --git a/docs/mosaic_configuration/mapping_ambassador_config/index.html b/docs/mosaic_configuration/mapping_ambassador_config/index.html
index db67fc2..b1c27ea 100644
--- a/docs/mosaic_configuration/mapping_ambassador_config/index.html
+++ b/docs/mosaic_configuration/mapping_ambassador_config/index.html
@@ -895,6 +895,10 @@
           <a href="/mosaic/docs/mosaic_configuration/">Configuration Files</a>
         </li>
         
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
         <li class="active">
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -953,9 +961,9 @@
 
       <nav id="TableOfContents">
   <ul>
-    <li><a href="#cmappingambassadorscheme">CMappingAmbassadorScheme</a>
+    <li><a href="#mapping">Mapping</a>
       <ul>
-        <li><a href="#cmappingambassadorschemetypedistributions">CMappingAmbassadorScheme.typeDistributions</a></li>
+        <li><a href="#mappingtypedistributions">Mapping.typeDistributions</a></li>
       </ul>
     </li>
     <li><a href="#config">config</a></li>
@@ -973,7 +981,7 @@
       </ul>
     </li>
     <li><a href="#geocircle">geoCircle</a></li>
-    <li><a href="#geopoint">geoPoint</a></li>
+    <li><a href="#geopoint">GeoPoint</a></li>
     <li><a href="#matrixmapper">matrixMapper</a></li>
     <li><a href="#odpoint">odPoint</a></li>
     <li><a href="#rsu">rsu</a></li>
@@ -1043,8 +1051,10 @@
   </div>
 </div>
 <hr>
-<p><a name="reference-cmappingambassadorscheme"></a></p>
-<h2 id="cmappingambassadorscheme">CMappingAmbassadorScheme</h2>
+<p>📃 <strong>Corresponding configuration file: <code>mapping/mapping_config.json</code></strong></p>
+<hr>
+<p><a name="reference-mapping"></a></p>
+<h2 id="mapping">Mapping</h2>
 <p>This schema describes the JSON file structure for the mapping configuration, which is used to define simulation entities.</p>
 <p><strong>Properties</strong></p>
 <table>
@@ -1062,7 +1072,18 @@
 <tr>
 <td>config</td>
 <td>
-<a href="#reference-config"><code>config</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-config">
+    <code>config</code>
+</a>
+</td>
 <td>Object to define additional configuration options for the mapping</td>
 <td>No</td>
 <td>None</td>
@@ -1071,7 +1092,18 @@
 <tr>
 <td>prototypes</td>
 <td>
-<a href="#reference-prototype"><code>prototype[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-prototype">
+    <code>prototype[]</code>
+</a>
+</td>
 <td>Array of prototypes, which can complete the definitions of other objects. This can be used to re-use certain configurations. All possible properties of objects are available. Only the ones needed will be used (for example an RSU does not have a length, so this property would be ignored).</td>
 <td>No</td>
 <td>None</td>
@@ -1080,7 +1112,18 @@
 <tr>
 <td>typeDistributions</td>
 <td>
-<a href="#reference-typedistribution"><code>typeDistribution</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-typedistribution">
+    <code>typeDistribution</code>
+</a>
+</td>
 <td>Object to define the distribution of prototypes to reuse in vehicle spawners. A typeDistribution is referenced by it&rsquo;s attribute name, which can be set to any valid string.</td>
 <td>No</td>
 <td>None</td>
@@ -1089,7 +1132,18 @@
 <tr>
 <td>vehicles</td>
 <td>
-<a href="#reference-vehicle"><code>vehicle[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-vehicle">
+    <code>vehicle[]</code>
+</a>
+</td>
 <td>Array of vehicles to be spawned in the simulation. This property describes the vehicles populatingthe simulation. It is possible to create a single vehicle (maxNumberVehicles should be &lsquo;1&rsquo; in that case) or a streamof one or multiple vehicles. The type(s) are defined in the field types. When more than one type is defined theweights in the prototype can be used to balance them against each other.</td>
 <td>No</td>
 <td>None</td>
@@ -1098,7 +1152,18 @@
 <tr>
 <td>matrixMappers</td>
 <td>
-<a href="#reference-matrixmapper"><code>matrixMapper[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-matrixmapper">
+    <code>matrixMapper[]</code>
+</a>
+</td>
 <td>Array of items to define additional traffic that will be spawned using OD-matrices.</td>
 <td>No</td>
 <td>None</td>
@@ -1107,7 +1172,18 @@
 <tr>
 <td>rsus</td>
 <td>
-<a href="#reference-rsu"><code>rsu[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-rsu">
+    <code>rsu[]</code>
+</a>
+</td>
 <td>Array of Road Side Units (RSUs). For RSUs only applications can be defined along with the position.</td>
 <td>No</td>
 <td>None</td>
@@ -1116,7 +1192,18 @@
 <tr>
 <td>servers</td>
 <td>
-<a href="#reference-server"><code>server[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-server">
+    <code>server[]</code>
+</a>
+</td>
 <td>Array of servers. Servers are a form of units that have no geographical location. The network properties of a server can be defined in the network.json-configuration in the cell-module.</td>
 <td>No</td>
 <td>None</td>
@@ -1125,7 +1212,18 @@
 <tr>
 <td>tmcs</td>
 <td>
-<a href="#reference-tmc"><code>tmc[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-tmc">
+    <code>tmc[]</code>
+</a>
+</td>
 <td>Array of Traffic Management Centers (TMCs). TMCs are specialized forms of servers having direct access to data collected by induction loops and lane area detectors. The network properties of a TMC can be defined in the network.json-configuration in the cell-module.</td>
 <td>No</td>
 <td>None</td>
@@ -1134,7 +1232,18 @@
 <tr>
 <td>trafficLights</td>
 <td>
-<a href="#reference-trafficlights"><code>trafficLights[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-trafficlights">
+    <code>trafficLights[]</code>
+</a>
+</td>
 <td>Array of prototypes for traffic lights. Since it is a traffic light only applications can be defined. Traffic light prototypes can be distributed among all traffic lights of an application by weight or assigned to specific traffic lights by using the ID of traffic light groups as reference.</td>
 <td>No</td>
 <td>None</td>
@@ -1143,7 +1252,18 @@
 <tr>
 <td>chargingStations</td>
 <td>
-<a href="#reference-chargingstation"><code>chargingStation[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-chargingstation">
+    <code>chargingStation[]</code>
+</a>
+</td>
 <td>Array of electric vehicle charging stations based on ETSI TS 101 556-1. An infrastructure which provides one or several electric vehicle charging spots to supply electric energy for charging electric vehicles.</td>
 <td>No</td>
 <td>None</td>
@@ -1152,8 +1272,8 @@
 </tbody>
 </table>
 <p><strong>Further property restrictions:</strong><br>
-<a name="restriction-cmappingambassadorschemetypedistributions"></a></p>
-<h3 id="cmappingambassadorschemetypedistributions">CMappingAmbassadorScheme.typeDistributions</h3>
+<a name="restriction-mappingtypedistributions"></a></p>
+<h3 id="mappingtypedistributions">Mapping.typeDistributions</h3>
 <ul>
 <li><strong>Type of each property</strong>: <code>array</code></li>
 </ul>
@@ -1335,7 +1455,18 @@
 <td>Class of the vehicle. The classes are used in lane definitions and allow/disallow the use of lanes for certain vehicle types (e.g. a taxi lane).</td>
 <td>No</td>
 <td>Enum
-<a href="#restriction-prototypevehicleclass"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-prototypevehicleclass">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1381,7 +1512,18 @@
 <p><strong>The following additional properties are allowed:</strong></p>
 <ul>
 <li>array[
-<a href="#reference-prototype">prototype</a>]</li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-prototype">
+    prototype
+</a>
+]</li>
 </ul>
 <hr>
 <p><a name="reference-vehicle"></a></p>
@@ -1446,7 +1588,18 @@
 <td>The depart speed mode determines the vehicle&rsquo;s speed at insertion.</td>
 <td>No</td>
 <td>Enum
-<a href="#restriction-vehicledepartspeedmode"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-vehicledepartspeedmode">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td><code>MAXIMUM</code></td>
 </tr>
 <tr>
@@ -1455,7 +1608,18 @@
 <td>The lane selection mode chooses the lane for the next departing vehicle.</td>
 <td>No</td>
 <td>Enum
-<a href="#restriction-vehiclelaneselectionmode"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-vehiclelaneselectionmode">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td><code>DEFAULT</code></td>
 </tr>
 <tr>
@@ -1464,7 +1628,18 @@
 <td>Adjusts the departure time of individual vehicles.</td>
 <td>No</td>
 <td>Enum
-<a href="#restriction-vehiclespawningmode"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-vehiclespawningmode">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td><code>CONSTANT</code></td>
 </tr>
 <tr>
@@ -1502,7 +1677,18 @@
 <tr>
 <td>types</td>
 <td>
-<a href="#reference-prototype"><code>prototype[1-*]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-prototype">
+    <code>prototype[1-*]</code>
+</a>
+</td>
 <td>List of possible vehicle types to be spawned. In this list you can simply refer to an existing prototype by its name attribute to include everything defined there. You can also overwrite every attribute of the prototype. If you don&rsquo;t have an existing prototype the definitions found here will be used as the prototype definition itself.</td>
 <td>No</td>
 <td>None</td>
@@ -1519,7 +1705,18 @@
 <tr>
 <td>destination</td>
 <td>
-<a href="#reference-geocircle"><code>geoCircle</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geocircle">
+    <code>geoCircle</code>
+</a>
+</td>
 <td>Object to define an immutable pair of a geoPoint center position and a radius in meters.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1528,7 +1725,18 @@
 <tr>
 <td>origin</td>
 <td>
-<a href="#reference-geocircle"><code>geoCircle</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geocircle">
+    <code>geoCircle</code>
+</a>
+</td>
 <td>Object to define an immutable pair of a geoPoint center position and a radius in meters.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1601,7 +1809,18 @@
 <tr>
 <td>center</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
 <td>Object to define geographical point coordinates.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1619,7 +1838,7 @@
 </table>
 <hr>
 <p><a name="reference-geopoint"></a></p>
-<h2 id="geopoint">geoPoint</h2>
+<h2 id="geopoint">GeoPoint</h2>
 <p>Object to define geographical point coordinates.</p>
 <p><strong>Properties</strong></p>
 <table>
@@ -1672,7 +1891,18 @@
 <tr>
 <td>points</td>
 <td>
-<a href="#reference-odpoint"><code>odPoint[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-odpoint">
+    <code>odPoint[]</code>
+</a>
+</td>
 <td>Array of odPoints that can be referenced from the OD-matrix.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1681,7 +1911,18 @@
 <tr>
 <td>types</td>
 <td>
-<a href="#reference-prototype"><code>prototype[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-prototype">
+    <code>prototype[]</code>
+</a>
+</td>
 <td>Array of prototypes to define the vehicles that should be spawned.</td>
 <td>No</td>
 <td>None</td>
@@ -1733,7 +1974,18 @@
 <tr>
 <td>position</td>
 <td>
-<a href="#reference-geocircle"><code>geoCircle</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geocircle">
+    <code>geoCircle</code>
+</a>
+</td>
 <td>Object to define an immutable pair of a geoPoint center position and a radius in meters.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1761,7 +2013,18 @@
 <tr>
 <td>position</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
 <td>Object to define geographical point coordinates.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1974,7 +2237,18 @@
 <tr>
 <td>position</td>
 <td>
-<a href="#reference-geopoint"><code>geoPoint</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
 <td>Object to define geographical point coordinates.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -2015,7 +2289,18 @@
 <tr>
 <td>chargingSpots</td>
 <td>
-<a href="#reference-chargingspot"><code>chargingSpot[]</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-chargingspot">
+    <code>chargingSpot[]</code>
+</a>
+</td>
 <td>List of the electric vehicle charging spots associated with this electric vehicle charging station.</td>
 <td>✓ Yes</td>
 <td>None</td>
diff --git a/docs/mosaic_configuration/scenario_config/index.html b/docs/mosaic_configuration/scenario_config/index.html
new file mode 100644
index 0000000..f188472
--- /dev/null
+++ b/docs/mosaic_configuration/scenario_config/index.html
@@ -0,0 +1,1920 @@
+<!DOCTYPE html><html lang="en-us" >
+
+
+
+
+  
+
+
+<head>
+
+  <meta charset="utf-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="generator" content="Source Themes Academic 4.8.0">
+
+  
+
+  
+  
+  
+  
+  
+    
+    
+    
+  
+  
+
+  <meta name="author" content="Fraunhofer FOKUS">
+
+  
+  
+  
+    
+  
+  <meta name="description" content="">
+
+  
+  <link rel="alternate" hreflang="en-us" href="https://www.eclipse.org/mosaic/docs/mosaic_configuration/scenario_config/">
+
+  
+
+
+  
+  
+  
+  <meta name="theme-color" content="#68145C">
+  
+
+  
+  
+  
+  <script src="/mosaic/js/mathjax-config.js"></script>
+  
+
+  
+  
+  
+  
+    
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/academicons/1.8.6/css/academicons.min.css" integrity="sha512-MCWBwPSput2UWNwyznVFLbD2iUc1e5VsdD1zahsWVzkDSUzyHhMZ4kCS3wgYSRm0mU+glwD/Q9lSJrDPwbUL2A==" crossorigin="anonymous">
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.0-1/css/all.min.css" integrity="sha512-ZYg+hQvLlM0W9C3P6vTpes5LmJ66G2EsroxDNzwD6qiulckldb29eD9I672HL2X+LH5nRhY1sQqZLJGB+aUUPg==" crossorigin="anonymous">
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/fancybox/3.5.7/jquery.fancybox.min.css" integrity="sha512-H9jrZiiopUdsLpg94A333EfumgUBpO9MdbxStdeITo+KEIMaNfHNvwyjjDJb+ERPaRS6DpyRlKbvPUasNItRyw==" crossorigin="anonymous">
+
+    
+    
+    
+      
+    
+    
+      
+      
+        <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/styles/atom-one-light.min.css" crossorigin="anonymous" title="hl-light">
+        <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/styles/atom-one-light.min.css" crossorigin="anonymous" title="hl-dark" disabled>
+      
+    
+
+    
+    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/leaflet/1.5.1/leaflet.css" integrity="sha512-xwE/Az9zrjBIphAcBb3F6JVqxf46+CDLwfLMHloNu6KEQCAWi6HcDUbeOfBIptF7tcCzusKFjFw2yuvEpDL9wQ==" crossorigin="anonymous">
+    
+
+    
+
+    
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/lazysizes/5.2.2/lazysizes.min.js" integrity="sha512-TmDwFLhg3UA4ZG0Eb4MIyT1O1Mb+Oww5kFG0uHqXsdbyZz9DcvYQhKpGgNkamAI6h2lGGZq2X8ftOJvF/XjTUg==" crossorigin="anonymous" async></script>
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/3.1.0/es5/tex-chtml.min.js" integrity="sha512-uwL1UtpYdWra2iqJlAW8Ts0s9Os6IxWLDJDF/BnWdhDmT7DEMFba3GPsFwmV3QiTNcUyl2GB5vsgycB/MOvo9g==" crossorigin="anonymous" async></script>
+      
+    
+      
+
+      
+      
+
+      
+    
+      
+
+      
+      
+
+      
+    
+
+  
+
+  
+  
+  
+  <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:400,400i,700,700i%7CRoboto+Mono&display=swap">
+  
+
+  
+  
+  
+  
+  <link rel="stylesheet" href="/mosaic/css/academic.css">
+
+  
+
+
+
+
+  
+
+
+  
+  
+
+  
+  <link rel="alternate" href="/mosaic/docs/mosaic_configuration/scenario_config/index.xml" type="application/rss+xml" title="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
+  
+
+  <link rel="manifest" href="/mosaic/index.webmanifest">
+  <link rel="icon" type="image/png" href="/mosaic/images/icon_hu6bdfb97c7e23190c70e41ca0e15a9fce_30436_32x32_fill_lanczos_center_2.png">
+  <link rel="apple-touch-icon" type="image/png" href="/mosaic/images/icon_hu6bdfb97c7e23190c70e41ca0e15a9fce_30436_192x192_fill_lanczos_center_2.png">
+
+  <link rel="canonical" href="https://www.eclipse.org/mosaic/docs/mosaic_configuration/scenario_config/">
+
+  
+  
+  
+  
+  
+  
+  
+    
+    
+  
+  
+  <meta property="twitter:card" content="summary">
+  
+  <meta property="og:site_name" content="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
+  <meta property="og:url" content="https://www.eclipse.org/mosaic/docs/mosaic_configuration/scenario_config/">
+  <meta property="og:title" content="Scenario Configuration | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility">
+  <meta property="og:description" content=""><meta property="og:image" content="https://www.eclipse.org/mosaic/images/logo.svg">
+  <meta property="twitter:image" content="https://www.eclipse.org/mosaic/images/logo.svg"><meta property="og:locale" content="en-us">
+  
+    
+  
+
+  
+
+
+
+
+  
+
+
+  
+
+
+
+
+
+  <title>Scenario Configuration | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility</title>
+
+</head>
+
+<body id="top" data-spy="scroll" data-offset="70" data-target="#TableOfContents" class=" page-mosaic page-docs page-mosaic_configuration page-scenario_config ">
+
+  <aside class="search-results" id="search">
+  <div class="container">
+    <section class="search-header">
+
+      <div class="row no-gutters justify-content-between mb-3">
+        <div class="col-10 col-md-3">
+          <div class="logo" style="background-image: url(/mosaic/img/logos/mosaic/EclipseMOSAIC-Logo-RGB-positiv.svg)"></div>
+        </div>
+        <div class="col-2 col-md-4 col-search-close">
+          <a class="js-search" href="#"><i class="fas fa-times-circle text-muted" aria-hidden="true"></i></a>
+        </div>
+      </div>
+
+      <div id="search-box">
+        
+        <input name="q" id="search-query" placeholder="Search..." autocapitalize="off"
+        autocomplete="off" autocorrect="off" spellcheck="false" type="search">
+        
+      </div>
+
+    </section>
+    <section class="section-search-results">
+
+      <div id="search-hits">
+        
+      </div>
+
+    </section>
+  </div>
+</aside>
+
+
+  
+
+
+
+
+
+
+  
+
+
+
+  
+
+
+<nav class="navbar navbar-expand-lg navbar-light compensate-for-scrollbar" id="navbar-main">
+  <div class="container">
+
+    <div class="d-none d-lg-inline-flex">
+      <a style="visibility:visible;" class="navbar-brand" href="/mosaic/"><img src="/mosaic/images/logo.svg" alt="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility"></a>
+    </div>
+
+
+    
+    <button type="button" class="navbar-toggler" data-bs-toggle="collapse" data-bs-target="#navbar-content-mobile" aria-controls="navbar" aria-expanded="false" aria-label="Toggle navigation">
+      <span><i class="fas fa-bars"></i></span>
+    </button>
+    
+
+    
+    <div class="navbar-brand-mobile-wrapper d-inline-flex d-lg-none">
+      <a class="navbar-brand" href="/mosaic/"><img src="/mosaic/images/logo.svg" alt="Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility"></a>
+    </div>
+    
+
+    
+    
+    <div id="navbar-content" class="navbar-collapse main-menu-item collapse justify-content-start">
+
+    
+    <ul class="navbar-nav d-md-inline-flex">
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/about/"><span>About</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/news/"><span>News</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link  active" href="/mosaic/docs/"><span>Documentation</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/tutorials/"><span>Tutorials</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/download/"><span>Download</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+      
+      
+      
+      
+
+      
+      
+      
+      
+      
+      
+
+      <li class="nav-item">
+        <a class="nav-link " href="/mosaic/community/"><span>Community</span></a>
+      </li>
+
+      
+      
+
+      
+
+      
+    </ul>
+  </div>
+
+    <ul class="nav-icons navbar-nav flex-row ml-auto d-flex pl-md-2">
+      
+      <li class="nav-item">
+        <a class="nav-link js-search" href="#" aria-label="Search"><i class="fas fa-search" aria-hidden="true"></i></a>
+      </li>
+      
+
+      
+
+      
+      <li class="nav-item ">
+        <a href="https://github.com/eclipse/mosaic" target="blank">
+          <i class="fab fa-github" aria-hidden="true"></i>
+        </a>
+      </li>
+      
+
+      
+
+    </ul>
+
+    
+    
+    <div id="navbar-content-mobile" class="navbar-collapse main-menu-item collapse justify-content-start d-lg-none">
+
+    
+      <ul class="navbar-nav d-inline-flex">
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/about/"><span>About</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/news/"><span>News</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link  active" href="/mosaic/docs/"><span>Documentation</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/tutorials/"><span>Tutorials</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/download/"><span>Download</span></a>
+        </li>
+
+        
+        
+
+        
+
+        
+        
+        
+          
+        
+
+        
+        
+        
+        
+        
+        
+
+        <li class="nav-item">
+          <a class="nav-link " href="/mosaic/community/"><span>Community</span></a>
+        </li>
+
+        
+        
+
+      
+
+        
+      </ul>
+    </div>
+
+  </div>
+</nav>
+
+
+  
+
+<div class="docs container">
+  <div class="row flex-xl-nowrap">
+    <div class="docs-sidebar col-12 col-md-3 col-xl-3">
+      
+
+
+
+
+
+  
+    
+  
+
+
+
+
+
+<div class="docs-version">
+  
+  
+  
+  <a class="" data-bs-toggle="tooltip" data-bs-placement="bottom" title="The documentation corresponds to the latest version of Eclipse MOSAIC 20.1-SNAPSHOT." href="https://github.com/eclipse/mosaic">
+    <i class="fab fa-github"></i>&nbsp;Eclipse MOSAIC 20.1-SNAPSHOT
+  </a>
+</div>
+
+<form class="docs-search d-flex align-items-center">
+  <button class="btn docs-toggle d-md-none p-0 mr-3" type="button" data-bs-toggle="collapse" data-bs-target="#docs-nav" aria-controls="docs-nav" aria-expanded="false" aria-label="Toggle section navigation">
+    <span><i class="fas fa-bars"></i></span>
+  </button>
+
+  
+  <input name="q" type="search" class="form-control" placeholder="Search..." autocomplete="off">
+  
+</form>
+
+<nav class="collapse docs-links" id="docs-nav">
+  
+  
+    
+    
+    
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/getting_started/">Getting Started</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/getting_started/">Download</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/getting_started/run_mosaic/">Run Eclipse MOSAIC</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/getting_started/results/">Simulation Results</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/visualization/">Visualization</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/visualization/">WebSocket Visualizer</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/visualization/filevis/">File Output</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/visualization/statistics/">Statistics Output</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/visualization/itef/">ITEF</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/visualization/phabmap/">PHABMap</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/simulators/">Simulators</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/simulators/">Overview</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/application_simulator/">Application Simulator</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/traffic_simulator_sumo/">Traffic - Eclipse SUMO</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/network_simulator_omnetpp/">Network - OMNeT&#43;&#43;</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/network_simulator_ns3/">Network - ns-3</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/network_simulator_sns/">Network - SNS</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/network_simulator_cell/">Network - Cell</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/environment_simulator/">Environment Simulator</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/battery_simulator/">Battery Simulator</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/simulators/vms_simulator/">VMS Simulator</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/building_scenarios/">Building Scenarios</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/building_scenarios/">Simulation Scenarios</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/building_scenarios/scenario_convert/">Scenario Convert</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/building_scenarios/scenario_configuration/">Additional Scenario Configuration</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/develop_applications/">Create Applications</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/develop_applications/">Basics</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/develop_applications/communication/">V2X Communication</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/develop_applications/event_scheduler/">Event Scheduling</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/develop_applications/road_traffic/">Scenario Database</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/extending_mosaic/">Extending Eclipse MOSAIC</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/">Core Concepts</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/simulator_coupling/">Simulator Coupling</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/interactions/">Interactions</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/application_ambassador_details/">Application Ambassador</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/sumo_ambassador_details/">Sumo Ambassador</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/omnetpp_details/">OMNeT&#43;&#43; Federate</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/extending_mosaic/delay_models/">Delay Models</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/mosaic_configuration/">MOSAIC Configuration</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/">Configuration Files</a>
+        </li>
+        
+        <li class="active">
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/environment_config/">Environment Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/sns_config/">SNS Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_region_config/">Cell Region Configuration</a>
+        </li>
+        
+        <li >
+          <a href="/mosaic/docs/mosaic_configuration/sumo_config/">SUMO Configuration</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="docs-toc-item">
+      <a class="docs-toc-link" href="/mosaic/docs/api_docs/">API Documentation</a>
+      <ul class="nav docs-sidenav">
+        
+        <li >
+          <a href="/mosaic/docs/api_docs/">Javadoc</a>
+        </li>
+        
+      </ul>
+      
+
+    </div>
+    
+    <div class="nav-bottom">
+      <img src="/mosaic/img/logos/mosaic/EclipseMOSAIC-Medallion-RGB-single-navy.svg">
+    </div>
+  
+</nav>
+
+    </div>
+
+    
+    <div class="docs-toc d-none d-xl-block col-xl-2">
+      <ul class="nav toc-top">
+        <li><a href="#" id="back_to_top" class="docs-toc-title">Contents</a></li>
+      </ul>
+
+      <nav id="TableOfContents">
+  <ul>
+    <li><a href="#scenario">Scenario</a>
+      <ul>
+        <li><a href="#scenariofederates">Scenario.federates</a></li>
+      </ul>
+    </li>
+    <li><a href="#simulation">simulation</a></li>
+    <li><a href="#projection">Projection</a></li>
+    <li><a href="#geopoint">GeoPoint</a></li>
+    <li><a href="#cartesianoffset">CartesianOffset</a></li>
+    <li><a href="#network-addressing">Network Addressing</a></li>
+  </ul>
+</nav>
+
+      
+    </div>
+    
+
+    <style>
+      @media (min-width:1140px) {
+        .docs-sidebar {
+          flex: 0 1 320px;
+        }
+        .docs-toc {
+          flex: 0 1 280px;
+        }
+        main.docs-content.no-docs-toc {
+          padding-bottom: 0 !important;
+          max-width: calc(100% - 320px) !important;
+          flex: 0 1 calc(100% - 320px);
+          width: 100%;
+        }
+        main.docs-content {
+          padding-bottom: 0 !important;
+          max-width: calc(100% - 600px) !important;
+          flex: 0 1 calc(100% - 600px);
+          width: 100%;
+        }
+      }
+      @media (max-width: 770px) {
+        main.docs-content {
+          max-width: 100% !important;
+          width: 100%;
+        }
+      }
+      @media (min-width: 771px) and(max-width: 1139px) {
+        main.docs-content.no-docs-toc {
+          padding-bottom: 0 !important;
+          max-width: calc(100% - 320px) !important;
+          width: 100%;
+        }
+      }
+    </style>
+    <main class="docs-content col-12 col-md-9 col-xl-auto py-md-3 pl-md-4" role="main">
+
+      <article class="article">
+
+        <div class="docs-article-container">
+          <h1>Scenario Configuration</h1>
+
+          <div class="article-style">
+            <div class="alert alert-tip">
+  <div>
+  <p>You can use a <a href="/mosaic/docs/mosaic_configuration/#readable-units" title="Readable Unit">Readable Unit</a> anywhere where you
+have the option of:</p>
+<ul>
+<li><code>number</code> <strong>or</strong> <code>string</code></li>
+<li><code>integer</code> <strong>or</strong> <code>string</code></li>
+</ul>
+  </div>
+</div>
+<hr>
+<p>📃 <strong>Corresponding configuration file: <code>scenario_config.json</code></strong></p>
+<hr>
+<p><a name="reference-scenario"></a></p>
+<h2 id="scenario">Scenario</h2>
+<p>Schema describing the JSON file structure for the main scenario configuration.</p>
+<p><strong>Properties</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th>Type</th>
+<th>Description</th>
+<th>Required</th>
+<th>Boundaries</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>simulation</td>
+<td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-simulation">
+    <code>simulation</code>
+</a>
+</td>
+<td>Basic properties of the simulation scenario.</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>federates</td>
+<td><code>object</code></td>
+<td>Defines the list of ambassadors/simulators which are used by the simulation. For each simulator (referenced by its id) a boolean value must be given, which enables or disables the simulator.</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+</tbody>
+</table>
+<p><strong>Further property restrictions:</strong><br>
+<a name="restriction-scenariofederates"></a></p>
+<h3 id="scenariofederates">Scenario.federates</h3>
+<ul>
+<li><strong>Type of each property</strong>: <code>boolean</code></li>
+</ul>
+<hr>
+<p><a name="reference-simulation"></a></p>
+<h2 id="simulation">simulation</h2>
+<p>Basic properties of the simulation scenario.</p>
+<p><strong>Properties</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th>Type</th>
+<th>Description</th>
+<th>Required</th>
+<th>Boundaries</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>id</td>
+<td><code>string</code></td>
+<td>The id or name of the simulation scenario.</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>duration</td>
+<td><code>string</code><br><code>number</code></td>
+<td>The duration of the simulation. If defined as a number, then the unit to be applied is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. &lsquo;300 s&rsquo;)</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>randomSeed</td>
+<td><code>integer</code></td>
+<td>The random seed to apply. This influences the application mapping, the communication models, and any use of randomness inside of applications. If not set, the random number generator will be initialized without a seed resulting in different results for each run. Note that several other simulators (e.g. SUMO) come with their own random number generators which are not affected by this property.</td>
+<td>No</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>projection</td>
+<td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-projection">
+    <code>projection</code>
+</a>
+</td>
+<td>Configures the projection used to transform geographical coordinates (WGS84) to local cartesian coordinates used by various simulators (e.g. SUMO, or OMNeT++). The projection is based on UTM and must be adapted to the used traffic network.</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>network</td>
+<td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-network">
+    <code>network</code>
+</a>
+</td>
+<td>Defines the subnets (e.g. 10.0.0.0) used for generating IP addresses for each unit in the simulation. Each type of unit is configured with its own subnet. A default configuration is used, when left out from the configuration.</td>
+<td>No</td>
+<td>None</td>
+<td><code>default network</code></td>
+</tr>
+</tbody>
+</table>
+<hr>
+<p><a name="reference-projection"></a></p>
+<h2 id="projection">Projection</h2>
+<p>Configures the projection used to transform geographical coordinates (WGS84) to local cartesian coordinates used by various simulators (e.g. SUMO, or OMNeT++). The projection is based on UTM and must be adapted to the used traffic network.</p>
+<p><strong>Properties</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th>Type</th>
+<th>Description</th>
+<th>Required</th>
+<th>Boundaries</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>centerCoordinates</td>
+<td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-geopoint">
+    <code>geoPoint</code>
+</a>
+</td>
+<td>Geographic coordinates of the rough center of the map / playground used in this scenario. This is just used to determine the UTM zone used for any further projection.</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>cartesianOffset</td>
+<td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-cartesianoffset">
+    <code>cartesianOffset</code>
+</a>
+</td>
+<td>A cartesian offset which is added to the UTM transformation. In most cases, this must be the exact offset which can be found in the <code>location.netOffset</code> of the <code>*.net.xml</code> of the scenario.</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+</tbody>
+</table>
+<hr>
+<p><a name="reference-geopoint"></a></p>
+<h2 id="geopoint">GeoPoint</h2>
+<p>Geographic coordinates of the rough center of the map / playground used in this scenario. This is just used to determine the UTM zone used for any further projection.</p>
+<p><strong>Properties</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th>Type</th>
+<th>Description</th>
+<th>Required</th>
+<th>Boundaries</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>longitude</td>
+<td><code>number</code></td>
+<td>East-west position of a point on earth.</td>
+<td>✓ Yes</td>
+<td>[-180, 180]</td>
+<td>None</td>
+</tr>
+<tr>
+<td>latitude</td>
+<td><code>number</code></td>
+<td>North-south position of a point on earth.</td>
+<td>✓ Yes</td>
+<td>[-90, 90]</td>
+<td>None</td>
+</tr>
+</tbody>
+</table>
+<hr>
+<p><a name="reference-cartesianoffset"></a></p>
+<h2 id="cartesianoffset">CartesianOffset</h2>
+<p>A cartesian offset which is added to the UTM transformation. In most cases, this must be the exact offset which can be found in the <code>location.netOffset</code> of the <code>*.net.xml</code> of the scenario.</p>
+<p><strong>Properties</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th>Type</th>
+<th>Description</th>
+<th>Required</th>
+<th>Boundaries</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>x</td>
+<td><code>number</code></td>
+<td>The value to add to the X coordinate after UTM transformation</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+<tr>
+<td>y</td>
+<td><code>number</code></td>
+<td>The value to add to the Y coordinate after UTM transformation</td>
+<td>✓ Yes</td>
+<td>None</td>
+<td>None</td>
+</tr>
+</tbody>
+</table>
+<hr>
+<p><a name="reference-network"></a></p>
+<h2 id="network-addressing">Network Addressing</h2>
+<p>Defines the subnets (e.g. 10.0.0.0) used for generating IP addresses for each unit in the simulation. Each type of unit is configured with its own subnet. A default configuration is used, when left out from the configuration.</p>
+<p><strong>Properties</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th>Type</th>
+<th>Description</th>
+<th>Required</th>
+<th>Boundaries</th>
+<th>Default</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>netMask</td>
+<td><code>string</code></td>
+<td>The net mask used for IP generation.</td>
+<td>No</td>
+<td>None</td>
+<td><code>255.0.0.0</code></td>
+</tr>
+<tr>
+<td>vehicleNet</td>
+<td><code>string</code></td>
+<td>The subnet used for assigning IPs to vehicles.</td>
+<td>No</td>
+<td>None</td>
+<td><code>10.0.0.0</code></td>
+</tr>
+<tr>
+<td>rsuNet</td>
+<td><code>string</code></td>
+<td>The subnet used for assigning IPs to road side units.</td>
+<td>No</td>
+<td>None</td>
+<td><code>11.0.0.0</code></td>
+</tr>
+<tr>
+<td>tlNet</td>
+<td><code>string</code></td>
+<td>The subnet used for assigning IPs to traffic lights.</td>
+<td>No</td>
+<td>None</td>
+<td><code>12.0.0.0</code></td>
+</tr>
+<tr>
+<td>csNet</td>
+<td><code>string</code></td>
+<td>The subnet used for assigning IPs to charging stations.</td>
+<td>No</td>
+<td>None</td>
+<td><code>13.0.0.0</code></td>
+</tr>
+<tr>
+<td>serverNet</td>
+<td><code>string</code></td>
+<td>The subnet used for assigning IPs to servers.</td>
+<td>No</td>
+<td>None</td>
+<td><code>14.0.0.0</code></td>
+</tr>
+<tr>
+<td>tmcNet</td>
+<td><code>string</code></td>
+<td>The subnet used for assigning IPs to traffic management centers.</td>
+<td>No</td>
+<td>None</td>
+<td><code>15.0.0.0</code></td>
+</tr>
+</tbody>
+</table>
+
+          </div>
+
+          
+
+
+
+          
+          <div class="article-widget">
+            
+<div class="post-nav prev-next-pages col-12">
+  <div class="row">
+    <div class="post-nav-item col-6">
+      
+        
+      
+    </div>
+
+    <div class="post-nav-item col-6 align-self-end">
+      
+        
+          
+          
+          
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+            
+          
+          
+        
+      
+    </div>
+  </div>
+</div>
+
+          </div>
+          
+        </div>
+
+        
+          
+
+          
+
+          
+
+          
+  
+  
+
+
+        
+
+
+        <footer class="site-footer">
+  <div class="row">
+  
+    
+      <div class="col-sm-4 mb-3 mb-md-0">
+        <b>Eclipse MOSAIC</b>
+        
+          <ul>
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/download/" title="Download Eclipse MOSAIC" >
+                    
+                      Download Eclipse MOSAIC
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/docs/" title="Documentation" >
+                    
+                      Documentation
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/tutorials/" title="Tutorials" >
+                    
+                      Tutorials
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/community/#projects" title="Projects" >
+                    
+                      Projects
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/publications/" title="Publications" >
+                    
+                      Publications
+                    
+                  </a>
+                </li>
+              
+            
+          </ul>
+        
+      </div>
+    
+  
+    
+      <div class="col-sm-4 mb-3 mb-md-0">
+        <b>Community</b>
+        
+          <ul>
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/community/" title="Eclipse MOSAIC Community" >
+                    
+                      Eclipse MOSAIC Community
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/contribution/" title="How to contribute" >
+                    
+                      How to contribute
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://github.com/eclipse/mosaic" title="Github"  target="_blank" rel="noopener">
+                    
+                      Github
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                
+                <li>
+                  <a href="/mosaic/get_in_contact/" title="Contact &amp; Mailing list" >
+                    
+                      Contact & Mailing list
+                    
+                  </a>
+                </li>
+              
+            
+          </ul>
+        
+      </div>
+    
+  
+    
+      <div class="col-sm-4 mb-3 mb-md-0">
+        <b>Eclipse Foundation</b>
+        
+          <ul>
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/" title="About Eclipse Foundation"  target="_blank" rel="noopener">
+                    
+                      About Eclipse Foundation
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/legal/privacy.php" title="Privacy Policy"  target="_blank" rel="noopener">
+                    
+                      Privacy Policy
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/legal/termsofuse.php" title="Website terms of use"  target="_blank" rel="noopener">
+                    
+                      Website terms of use
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/legal/copyright.php" title="Copyright"  target="_blank" rel="noopener">
+                    
+                      Copyright
+                    
+                  </a>
+                </li>
+              
+            
+              
+                
+                
+                  
+                    
+                  
+                
+                <li>
+                  <a href="https://www.eclipse.org/legal" title="Legal"  target="_blank" rel="noopener">
+                    
+                      Legal
+                    
+                  </a>
+                </li>
+              
+            
+          </ul>
+        
+      </div>
+    
+  
+
+
+
+
+
+
+
+
+
+
+
+  </div>
+  <div class="row justify-content-center mt-3 position-relative">
+    <p class="powered-by text-center font-italic mb-0 pb-0">
+      Powered by the
+      <a href="https://sourcethemes.com/academic/" target="_blank" rel="noopener">Academic theme</a> for
+      <a href="https://gohugo.io" target="_blank" rel="noopener">Hugo</a>.
+      <br>
+      Header image &#169; fanjianhua/ iStock
+    </p>
+    
+  </div>
+</footer>
+
+
+
+      </article>
+    </main>
+  </div>
+</div>
+
+
+      
+
+    
+    
+    
+      <script src="https://code.jquery.com/jquery-3.4.1.min.js" integrity="sha384-vk5WoKIaW/vJyUAd9n/wmopsmNhiy+L2Z+SBxGYnUkunIxVxAv/UtMOhba/xskxh" crossorigin="anonymous"></script>
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/2.6.0/umd/popper.min.js" integrity="sha512-BmM0/BQlqh02wuK5Gz9yrbe7VyIVwOzD1o40yi1IsTjriX/NGF37NyXHfmFzIlMmoSIBXgqDiG1VNU6kB5dBbA==" crossorigin="anonymous"></script>
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery.imagesloaded/4.1.4/imagesloaded.pkgd.min.js" integrity="sha512-S5PZ9GxJZO16tT9r3WJp/Safn31eu8uWrzglMahDT4dsmgqWonRY9grk3j+3tfuPr9WJNsfooOR7Gi7HL5W2jw==" crossorigin="anonymous"></script>
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery.isotope/3.0.6/isotope.pkgd.min.js" integrity="sha512-Zq2BOxyhvnRFXu0+WE6ojpZLOU2jdnqbrM1hmVdGzyeCa1DgM3X5Q4A/Is9xA1IkbUeDd7755dNNI/PzSf2Pew==" crossorigin="anonymous"></script>
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/fancybox/3.5.7/jquery.fancybox.min.js" integrity="sha512-uURl+ZXMBrF4AwGaWmEetzrd+J5/8NRkWAvJx5sbPSSuOb0bZLqf+tOzniObO00BjHa/dD7gub9oCGMLPQHtQA==" crossorigin="anonymous"></script>
+
+      
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/mermaid/8.4.8/mermaid.min.js" integrity="sha512-1tS1YUns336Mtxl+vkaLcADPwE1CPNVy3WEf7nrI7DGMMb6/FAVBgL2IzAWVBkB6vVuK94s2zVoiXcw1QZ9S1g==" crossorigin="anonymous" title="mermaid"></script>
+      
+
+      
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/highlight.min.js" integrity="sha512-1LdB3V708w6G4QRl7NsVdTr7MDibyRXr9stQZ+EGjEE0ZPMZkA//ir7kCWmFyxdAJNIRXdR/ZeJmCV0boyiCXw==" crossorigin="anonymous"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/java.min.js"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/json.min.js"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/xml.min.js"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/shell.min.js"></script>
+        
+        <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.1/languages/dos.min.js"></script>
+        
+      
+
+    
+
+    
+    
+      <script src="https://cdnjs.cloudflare.com/ajax/libs/leaflet/1.5.1/leaflet.js" integrity="sha512-GffPMF3RvMeYyc1LWMHtK8EbPv0iNZ8/oTtHPx9/cc2ILxQ+u905qIwdpULaqDkyBKgOaB57QTMg7ztg8Jm2Og==" crossorigin="anonymous"></script>
+    
+
+    
+    
+    <script>const code_highlighting = true;</script>
+    
+
+    
+    
+    <script>const isSiteThemeDark = false;</script>
+    
+
+    
+    
+    
+    
+    
+    
+    <script>
+      const search_config = {"indexURI":"/mosaic/index.json","minLength":1,"threshold":0.3};
+      const i18n = {"no_results":"No results found","placeholder":"Search...","results":"results found"};
+      const content_type = {
+        'post': "Posts",
+        'project': "Projects",
+        'publication' : "Publications",
+        'talk' : "Talks"
+        };
+    </script>
+    
+
+    
+    
+    <script src="https://cdnjs.cloudflare.com/ajax/libs/anchor-js/4.1.1/anchor.min.js" integrity="sha512-aZotBPy6dqn8yVaLJwSrkJ+QxuxV695A4dgodAMvTU5JyNi5mhrr+LeaD3GSS+lx1SMFKNs0tu5ZMJEgNZQP2Q==" crossorigin="anonymous"></script>
+    <script>
+      anchors.add();
+    </script>
+    
+
+    
+    
+    <script id="search-hit-fuse-template" type="text/x-template">
+      <div class="search-hit" id="summary-{{key}}">
+      <div class="search-hit-content">
+        <div class="search-hit-name">
+          <a href="{{relpermalink}}">{{title}}</a>
+          <div class="article-metadata search-hit-type">{{type}}</div>
+          <p class="search-hit-description">{{snippet}}</p>
+        </div>
+      </div>
+      </div>
+    </script>
+    
+
+    
+    
+    <script src="https://cdnjs.cloudflare.com/ajax/libs/fuse.js/3.2.1/fuse.min.js" integrity="sha512-o38bmzBGX+hD3JHWUFCDA09btWaqrNmoJ3RXLlrysA7PP01Kgs4UlE4MhelE1v5dJR3+cxlR4qQlotsW7jKsnw==" crossorigin="anonymous"></script>
+    <script src="https://cdnjs.cloudflare.com/ajax/libs/mark.js/8.11.1/jquery.mark.min.js" integrity="sha512-mhbv5DqBMgrWL+32MmsDOt/OAvqr/cHimk6B8y/bx/xS88MVkYGPiVv2ixKVrkywF2qHplNRUvFsAHUdxZ3Krg==" crossorigin="anonymous"></script>
+    
+
+    
+    
+
+    
+    
+
+    
+    
+
+    
+    
+    
+    
+    
+    
+    
+    
+    
+      
+    
+    
+    
+    
+    <script type="application/javascript" src="/mosaic/js/academic.min.0992ad8b8d033c3858bb90b03966346a.js"></script>
+
+    
+
+<script type="application/javascript" src="/mosaic/js/mosaic-wg-cards.js"></script>
+
+
+
+
+    <script>
+      var tooltipTriggerList = [].slice.call(document.querySelectorAll('[data-bs-toggle="tooltip"]'))
+      tooltipTriggerList.map(function (tooltipTriggerEl) {
+        return new window.bootstrap.Tooltip(tooltipTriggerEl)
+      })
+    </script>
+
+
+  
+  
+
+  
+<div id="modal" class="modal fade" role="dialog">
+  <div class="modal-dialog">
+    <div class="modal-content">
+      <div class="modal-header">
+        <h5 class="modal-title">Cite</h5>
+        <button type="button" class="close" data-dismiss="modal" aria-label="Close">
+          <span aria-hidden="true">&times;</span>
+        </button>
+      </div>
+      <div class="modal-body">
+        <pre><code class="tex hljs"></code></pre>
+      </div>
+      <div class="modal-footer">
+        <a class="btn btn-outline-primary my-1 js-copy-cite" href="#" target="_blank">
+          <i class="fas fa-copy"></i> Copy
+        </a>
+        <a class="btn btn-outline-primary my-1 js-download-cite" href="#" target="_blank">
+          <i class="fas fa-download"></i> Download
+        </a>
+        <div id="modal-error"></div>
+      </div>
+    </div>
+  </div>
+</div>
+
+</body>
+</html>
diff --git a/docs/mosaic_configuration/scenario_config/index.xml b/docs/mosaic_configuration/scenario_config/index.xml
new file mode 100644
index 0000000..e560c25
--- /dev/null
+++ b/docs/mosaic_configuration/scenario_config/index.xml
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>Scenario Configuration | Eclipse MOSAIC – A Multi-Domain and Multi-Scale Simulation Framework for Connected and Automated Mobility</title>
+    <link>https://www.eclipse.org/mosaic/docs/mosaic_configuration/scenario_config/</link>
+      <atom:link href="https://www.eclipse.org/mosaic/docs/mosaic_configuration/scenario_config/index.xml" rel="self" type="application/rss+xml" />
+    <description>Scenario Configuration</description>
+    <generator>Source Themes Academic (https://sourcethemes.com/academic/)</generator><language>en-us</language>
+    <image>
+      <url>https://www.eclipse.org/mosaic/images/logo.svg</url>
+      <title>Scenario Configuration</title>
+      <link>https://www.eclipse.org/mosaic/docs/mosaic_configuration/scenario_config/</link>
+    </image>
+    
+  </channel>
+</rss>
diff --git a/docs/mosaic_configuration/sns_config/index.html b/docs/mosaic_configuration/sns_config/index.html
index 5e4d8f4..74f35ef 100644
--- a/docs/mosaic_configuration/sns_config/index.html
+++ b/docs/mosaic_configuration/sns_config/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -953,7 +961,7 @@
 
       <nav id="TableOfContents">
   <ul>
-    <li><a href="#csnsscheme">CSnsScheme</a></li>
+    <li><a href="#sns">SNS</a></li>
     <li><a href="#adoctransmissionmodel">adocTransmissionModel</a>
       <ul>
         <li><a href="#adhoctransmissionmodeltype">adhocTransmissionModel.type</a></li>
@@ -1037,8 +1045,10 @@
   </div>
 </div>
 <hr>
-<p><a name="reference-csnsscheme"></a></p>
-<h2 id="csnsscheme">CSnsScheme</h2>
+<p>📃 <strong>Corresponding configuration file: <code>sns/sns_config.json</code></strong></p>
+<hr>
+<p><a name="reference-sns"></a></p>
+<h2 id="sns">SNS</h2>
 <p>Schema describing the JSON file structure for the sns configuration.</p>
 <p><strong>Properties</strong></p>
 <table>
@@ -1072,7 +1082,18 @@
 <tr>
 <td>adhocTransmissionModel</td>
 <td>
-<a href="#reference-adhoctransmissionmodel"><code>adhocTransmissionModel</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-adhoctransmissionmodel">
+    <code>adhocTransmissionModel</code>
+</a>
+</td>
 <td>Object to define an adhoc transimssion model.</td>
 <td>No</td>
 <td>None</td>
@@ -1081,17 +1102,50 @@
 <tr>
 <td>singlehopDelay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>No</td>
 <td>None</td>
 <td>
-<a href="#reference-constantdelay">constantDelay</a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-constantdelay">
+    constantDelay
+</a>
+</td>
 </tr>
 <tr>
 <td>singlehopTransmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1122,23 +1176,67 @@
 <td>Type of the transmission model. The simple model assumes, that all receivers can be reached even though this might not be the case in reality.</td>
 <td>No</td>
 <td>Enum
-<a href="#restriction-adoctransmissionmodeltype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-adoctransmissionmodeltype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
 <td>simpleMultihopDelay</td>
 <td>
-<a href="#reference-delay"><code>delay</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-delay">
+    <code>delay</code>
+</a>
+</td>
 <td>Object to define a delay model.</td>
 <td>No</td>
 <td>None</td>
 <td>
-<a href="#reference-constantdelay">constantDelay</a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-constantdelay">
+    constantDelay
+</a>
+</td>
 </tr>
 <tr>
 <td>simpleMultihopTransmission</td>
 <td>
-<a href="#reference-transmission"><code>transmission</code></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#reference-transmission">
+    <code>transmission</code>
+</a>
+</td>
 <td>Object to define the properties of a transmission.</td>
 <td>✓ Yes</td>
 <td>None</td>
@@ -1164,11 +1262,44 @@
 <p><strong>Additionally ONE of the following property definitions apply:</strong></p>
 <ul>
 <li>
-<a href="#reference-gammaDelay">gammaDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-gammaDelay">
+    gammaDelay
+</a>
+</li>
 <li>
-<a href="#reference-constantDelay">constantDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-constantDelay">
+    constantDelay
+</a>
+</li>
 <li>
-<a href="#reference-simpleRandomDelay">simpleRandomDelay</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-simpleRandomDelay">
+    simpleRandomDelay
+</a>
+</li>
 </ul>
 <hr>
 <p><a name="reference-gammadelay"></a></p>
@@ -1193,7 +1324,18 @@
 <td>Type of Gamma delay.</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-gammadelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-gammadelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1248,7 +1390,18 @@
 <td>Type of the constant delay</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-constantdelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-constantdelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
@@ -1294,7 +1447,18 @@
 <td>Type of the delay.</td>
 <td>✓ Yes</td>
 <td>Enum
-<a href="#restriction-simplerandomdelaytype"><i class="fas fa-info-circle"></i></a></td>
+
+
+
+
+
+  
+  
+
+<a href="#restriction-simplerandomdelaytype">
+    <i class="fas fa-info-circle"></i>
+</a>
+</td>
 <td>None</td>
 </tr>
 <tr>
diff --git a/docs/mosaic_configuration/sumo_config/index.html b/docs/mosaic_configuration/sumo_config/index.html
index df5f7db..d2f6805 100644
--- a/docs/mosaic_configuration/sumo_config/index.html
+++ b/docs/mosaic_configuration/sumo_config/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -953,9 +961,9 @@
 
       <nav id="TableOfContents">
   <ul>
-    <li><a href="#csumoscheme">CSumoScheme</a>
+    <li><a href="#sumo">SUMO</a>
       <ul>
-        <li><a href="#csumoschemeadditionalvehicletypeparameters">CSumoScheme.additionalVehicleTypeParameters</a></li>
+        <li><a href="#sumoadditionalvehicletypeparameters">SUMO.additionalVehicleTypeParameters</a></li>
       </ul>
     </li>
     <li><a href="#additionalvehicletype">additionalVehicleType</a></li>
@@ -1021,8 +1029,10 @@
   </div>
 </div>
 <hr>
-<p><a name="reference-csumoscheme"></a></p>
-<h2 id="csumoscheme">CSumoScheme</h2>
+<p>📃 <strong>Corresponding configuration file: <code>sumo/sumo_config.json</code></strong></p>
+<hr>
+<p><a name="reference-sumo"></a></p>
+<h2 id="sumo">SUMO</h2>
 <p>Schema describing the JSON file structure for the SUMO configuration.</p>
 <p><strong>Properties</strong></p>
 <table>
@@ -1128,8 +1138,8 @@
 </tbody>
 </table>
 <p><strong>Further property restrictions:</strong><br>
-<a name="restriction-csumoschemeadditionalvehicletypeparameters"></a></p>
-<h3 id="csumoschemeadditionalvehicletypeparameters">CSumoScheme.additionalVehicleTypeParameters</h3>
+<a name="restriction-sumoadditionalvehicletypeparameters"></a></p>
+<h3 id="sumoadditionalvehicletypeparameters">SUMO.additionalVehicleTypeParameters</h3>
 <ul>
 <li><strong>Type of each property</strong>: <code>additionalVehicleType</code></li>
 </ul>
@@ -1140,7 +1150,18 @@
 <p><strong>The following additional properties are allowed:</strong></p>
 <ul>
 <li>
-<a href="#reference-additionalParameter">additionalParameter</a></li>
+
+
+
+
+
+  
+  
+
+<a href="#reference-additionalParameter">
+    additionalParameter
+</a>
+</li>
 </ul>
 <hr>
 <p><a name="reference-additionalparameter"></a></p>
diff --git a/docs/simulators/application_simulator/index.html b/docs/simulators/application_simulator/index.html
index be508c4..366475c 100644
--- a/docs/simulators/application_simulator/index.html
+++ b/docs/simulators/application_simulator/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1041,7 +1049,35 @@
 <p>This simulator does not need to be installed. It is delivered as part of the Eclipse MOSAIC installation package.</p>
 <h3 id="overview">Overview</h3>
 <p>Each simulation unit (e.g. vehicle, RSU, traffic light ..) can have different applications (depending on their application
-<a href="/mosaic/docs/simulators/application_simulator#eclipse-mosaic-mapping" title="Mapping">Mapping</a>. The applications
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/#eclipse-mosaic-mapping">
+    Mapping
+</a>
+. The applications
 for the units are basically compiled JAVA classes, which <strong>extend</strong> the abstract class <code>AbstractApplication</code>. Those
 classes have to be deployed as pre-compiled JAR files into the <code>application</code> folder of the simulated scenario.</p>
 
@@ -1121,7 +1157,35 @@
 application simulator. The following table lists all interfaces usable for application implementation, the type of unit as well as
 important other interfaces it implements. Interface specific public methods which have to be implemented by the user are listed in the
 &ldquo;Provides&rdquo; column. The elementary interface (<code>Application</code>) provides the methods <code>onStartup()</code>, <code>onShutdown()</code>. Implementation details
-are given in <a href="/mosaic/docs/develop_applications/" title="Development of applications">Development of applications</a>.</p>
+are given in 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/develop_applications/">
+    Development of applications
+</a>
+.</p>
 <table>
 <thead>
 <tr>
@@ -1419,11 +1483,67 @@
 ]
 </code></pre>
 <p>For more information, explained for detailed examples with different mapping options regarding traffic lights, please refer to
-<a href="/mosaic/docs/building_scenarios/#traffic-lights" title="Simulation Scenarios - Traffic Lights">Simulation Scenarios - Traffic Lights</a>.</p>
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/#traffic-lights">
+    Simulation Scenarios - Traffic Lights
+</a>
+.</p>
 <p><strong>Servers</strong></p>
 <p>The <code>servers</code>-array can be used to specify server units, which can be used to communicate with other units via the cell module.
 Capacity configurations for servers should be done when enabling the <code>CellModule</code>. Delay and transmission models are configured
-in the <code>network.json</code> of the cell module (see <a href="/mosaic/docs/simulators/network_simulator_cell" title="here">here</a>).</p>
+in the <code>network.json</code> of the cell module (see 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_cell/">
+    here
+</a>
+).</p>
 <blockquote>
 <p>Note: The <code>group</code> parameter in the mapping configuration has to match with the id in the network configuration in order to
 properly function.</p>
@@ -1605,7 +1725,7 @@
 </table>
 <div class="alert alert-tip">
   <div>
-<p>Read the detailed documentation of the <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/" title="Mapping Configuration">Mapping Configuration</a>.</p>
+<p>Read the detailed documentation of the <a href="/docs/mosaic_configuration/mapping_ambassador_config">Mapping Configuration</a>.</p>
   </div>
 </div>
 <h3 id="unit-identifiers">Unit Identifiers</h3>
diff --git a/docs/simulators/battery_simulator/index.html b/docs/simulators/battery_simulator/index.html
index 347eef1..ceb0b1f 100644
--- a/docs/simulators/battery_simulator/index.html
+++ b/docs/simulators/battery_simulator/index.html
@@ -903,6 +903,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -915,6 +919,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1023,7 +1031,7 @@
             <div class="alert alert-extended">
   <span class="extended-icon" style="background-image: url(/mosaic/img/alert-extended.svg)"></span>
   <div>
-<p>The <strong>Battery Simulator</strong> is part of <a href="/mosaic/download/#overview" title="MOSAIC Extended">MOSAIC Extended</a>.<br>
+<p>The <strong>Battery Simulator</strong> is part of <a href="/download#overview">MOSAIC Extended</a>.<br>
 For further information on licenses, feel free to contact us via <strong><a href="mailto:mosaic@fokus.fraunhofer.de"><a href="mailto:mosaic@fokus.fraunhofer.de">mosaic@fokus.fraunhofer.de</a></a></strong>.</p>
   </div>
 </div>
diff --git a/docs/simulators/environment_simulator/index.html b/docs/simulators/environment_simulator/index.html
index 9c3cba4..bd03532 100644
--- a/docs/simulators/environment_simulator/index.html
+++ b/docs/simulators/environment_simulator/index.html
@@ -901,6 +901,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -913,6 +917,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1024,7 +1032,7 @@
 <h3 id="configuration">Configuration</h3>
 <div class="alert alert-tip">
   <div>
-<p>Read the detailed documentation of the <a href="/mosaic/docs/mosaic_configuration/environment_config/" title="Environment Configuration">Environment Configuration</a>.</p>
+<p>Read the detailed documentation of the <a href="/docs/mosaic_configuration/environment_config">Environment Configuration</a>.</p>
   </div>
 </div>
 <p>The root node of the configuration is a list of environment events. Each event require the type of the event, a rectangle area, a
diff --git a/docs/simulators/index.html b/docs/simulators/index.html
index e5b33b2..1324e1e 100644
--- a/docs/simulators/index.html
+++ b/docs/simulators/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1025,7 +1033,35 @@
 <tbody>
 <tr>
 <td><strong>Application Simulation</strong></td>
-<td><strong><a href="/mosaic/docs/simulators/application_simulator" title="MOSAIC Application">MOSAIC Application</a></strong></td>
+<td><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/">
+    MOSAIC Application
+</a>
+</strong></td>
 <td>Application prototyping and simulation.</td>
 </tr>
 <tr>
@@ -1035,7 +1071,35 @@
 </tr>
 <tr>
 <td><strong>Traffic / Vehicle Simulation</strong></td>
-<td><strong><a href="/mosaic/docs/simulators/traffic_simulator_sumo" title="Eclipse SUMO">Eclipse SUMO</a></strong></td>
+<td><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/traffic_simulator_sumo/">
+    Eclipse SUMO
+</a>
+</strong></td>
 <td>Microscopic Traffic simulation.</td>
 </tr>
 <tr>
@@ -1050,22 +1114,134 @@
 </tr>
 <tr>
 <td><strong>Network / Communication Simulation</strong></td>
-<td><strong><a href="/mosaic/docs/simulators/network_simulator_omnetpp" title="OMNeT&#43;&#43;">OMNeT&#43;&#43;</a></strong></td>
+<td><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_omnetpp/">
+    OMNeT++
+</a>
+</strong></td>
 <td>Event-based network simulator for ITS-G5 and cellular communication.</td>
 </tr>
 <tr>
 <td></td>
-<td><strong><a href="/mosaic/docs/simulators/network_simulator_ns3" title="ns-3">ns-3</a></strong></td>
+<td><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_ns3/">
+    ns-3
+</a>
+</strong></td>
 <td>Event-based network simulator for ITS-G5 and cellular communication.</td>
 </tr>
 <tr>
 <td></td>
-<td><strong><a href="/mosaic/docs/simulators/network_simulator_sns" title="MOSAIC Simple Network Simulator">MOSAIC Simple Network Simulator</a></strong></td>
+<td><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_sns/">
+    MOSAIC Simple Network Simulator
+</a>
+</strong></td>
 <td>Simulator for ITS-G5 ad-hoc communication using simplified models.</td>
 </tr>
 <tr>
 <td></td>
-<td><strong><a href="/mosaic/docs/simulators/network_simulator_cell" title="MOSAIC Cell">MOSAIC Cell</a></strong></td>
+<td><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_cell/">
+    MOSAIC Cell
+</a>
+</strong></td>
 <td>Simulator for cellular communication.</td>
 </tr>
 <tr>
@@ -1075,7 +1251,35 @@
 </tr>
 <tr>
 <td><strong>Environment Simulation</strong></td>
-<td><strong><a href="/mosaic/docs/simulators/environment_simulator" title="MOSAIC Environment">MOSAIC Environment</a></strong></td>
+<td><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/environment_simulator/">
+    MOSAIC Environment
+</a>
+</strong></td>
 <td>Environmental event simulation.</td>
 </tr>
 <tr>
@@ -1085,7 +1289,35 @@
 </tr>
 <tr>
 <td><strong>E-Mobility Simulation</strong></td>
-<td><strong><a href="/mosaic/docs/simulators/battery_simulator" title="MOSAIC Battery">MOSAIC Battery</a></strong></td>
+<td><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/battery_simulator/">
+    MOSAIC Battery
+</a>
+</strong></td>
 <td>Electric vehicle simulation.</td>
 </tr>
 </tbody>
diff --git a/docs/simulators/index.xml b/docs/simulators/index.xml
index 6f5df66..448402d 100644
--- a/docs/simulators/index.xml
+++ b/docs/simulators/index.xml
@@ -38,7 +38,35 @@
 &lt;p&gt;This simulator does not need to be installed. It is delivered as part of the Eclipse MOSAIC installation package.&lt;/p&gt;
 &lt;h3 id=&#34;overview&#34;&gt;Overview&lt;/h3&gt;
 &lt;p&gt;Each simulation unit (e.g. vehicle, RSU, traffic light ..) can have different applications (depending on their application
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/application_simulator#eclipse-mosaic-mapping&#34; title=&#34;Mapping&#34;&gt;Mapping&lt;/a&gt;. The applications
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/application_simulator/#eclipse-mosaic-mapping&#34;&gt;
+    Mapping
+&lt;/a&gt;
+. The applications
 for the units are basically compiled JAVA classes, which &lt;strong&gt;extend&lt;/strong&gt; the abstract class &lt;code&gt;AbstractApplication&lt;/code&gt;. Those
 classes have to be deployed as pre-compiled JAR files into the &lt;code&gt;application&lt;/code&gt; folder of the simulated scenario.&lt;/p&gt;
 
@@ -118,7 +146,35 @@
 application simulator. The following table lists all interfaces usable for application implementation, the type of unit as well as
 important other interfaces it implements. Interface specific public methods which have to be implemented by the user are listed in the
 &amp;ldquo;Provides&amp;rdquo; column. The elementary interface (&lt;code&gt;Application&lt;/code&gt;) provides the methods &lt;code&gt;onStartup()&lt;/code&gt;, &lt;code&gt;onShutdown()&lt;/code&gt;. Implementation details
-are given in &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/&#34; title=&#34;Development of applications&#34;&gt;Development of applications&lt;/a&gt;.&lt;/p&gt;
+are given in 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/&#34;&gt;
+    Development of applications
+&lt;/a&gt;
+.&lt;/p&gt;
 &lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
@@ -416,11 +472,67 @@
 ]
 &lt;/code&gt;&lt;/pre&gt;
 &lt;p&gt;For more information, explained for detailed examples with different mapping options regarding traffic lights, please refer to
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/#traffic-lights&#34; title=&#34;Simulation Scenarios - Traffic Lights&#34;&gt;Simulation Scenarios - Traffic Lights&lt;/a&gt;.&lt;/p&gt;
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/#traffic-lights&#34;&gt;
+    Simulation Scenarios - Traffic Lights
+&lt;/a&gt;
+.&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Servers&lt;/strong&gt;&lt;/p&gt;
 &lt;p&gt;The &lt;code&gt;servers&lt;/code&gt;-array can be used to specify server units, which can be used to communicate with other units via the cell module.
 Capacity configurations for servers should be done when enabling the &lt;code&gt;CellModule&lt;/code&gt;. Delay and transmission models are configured
-in the &lt;code&gt;network.json&lt;/code&gt; of the cell module (see &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_cell&#34; title=&#34;here&#34;&gt;here&lt;/a&gt;).&lt;/p&gt;
+in the &lt;code&gt;network.json&lt;/code&gt; of the cell module (see 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_cell/&#34;&gt;
+    here
+&lt;/a&gt;
+).&lt;/p&gt;
 &lt;blockquote&gt;
 &lt;p&gt;Note: The &lt;code&gt;group&lt;/code&gt; parameter in the mapping configuration has to match with the id in the network configuration in order to
 properly function.&lt;/p&gt;
@@ -602,7 +714,7 @@
 &lt;/table&gt;
 &lt;div class=&#34;alert alert-tip&#34;&gt;
   &lt;div&gt;
-&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/mosaic_configuration/mapping_ambassador_config/&#34; title=&#34;Mapping Configuration&#34;&gt;Mapping Configuration&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/docs/mosaic_configuration/mapping_ambassador_config&#34;&gt;Mapping Configuration&lt;/a&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
 &lt;h3 id=&#34;unit-identifiers&#34;&gt;Unit Identifiers&lt;/h3&gt;
@@ -712,7 +824,14 @@
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Website&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;
-&lt;a href=&#34;https://www.eclipse.org/sumo/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://www.eclipse.org/sumo/&lt;/a&gt;&lt;/td&gt;
+
+
+
+
+&lt;a href=&#34;https://www.eclipse.org/sumo/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    https://www.eclipse.org/sumo/
+&lt;/a&gt;
+&lt;/td&gt;
 &lt;td&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
@@ -760,7 +879,7 @@
 &lt;/code&gt;&lt;/pre&gt;
 &lt;div class=&#34;alert alert-tip&#34;&gt;
   &lt;div&gt;
-&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/mosaic_configuration/sumo_config/&#34; title=&#34;SUMO Configuration&#34;&gt;SUMO Configuration&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/docs/mosaic_configuration/sumo_config&#34;&gt;SUMO Configuration&lt;/a&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
 &lt;p&gt;Next to &lt;code&gt;sumo_config.json&lt;/code&gt;, the following configuration files are required for every SUMO simulation scenario:&lt;/p&gt;
@@ -821,7 +940,14 @@
 These are the Mobility Framework and the &lt;strong&gt;INET&lt;/strong&gt; Framework. As INET provides all models necessary for simulating Vehicle-2-X communication,
 it is selected for the integration to Eclipse MOSAIC.&lt;/p&gt;
 &lt;p&gt;For more information on the &lt;strong&gt;INET&lt;/strong&gt; extension you should look closer on the 
-&lt;a href=&#34;https://inet.omnetpp.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;website&lt;/a&gt;.&lt;/p&gt;
+
+
+
+
+&lt;a href=&#34;https://inet.omnetpp.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    website
+&lt;/a&gt;
+.&lt;/p&gt;
 &lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
@@ -845,8 +971,22 @@
 &lt;td&gt;&lt;strong&gt;Supported version(s)&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;OMNeT++ 5.5 &lt;br&gt;INET 4.1&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;
-&lt;a href=&#34;http://www.omnetpp.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;http://www.omnetpp.org&lt;/a&gt; &lt;br&gt; 
-&lt;a href=&#34;https://inet.omnetpp.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://inet.omnetpp.org&lt;/a&gt;&lt;/td&gt;
+
+
+
+
+&lt;a href=&#34;http://www.omnetpp.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    http://www.omnetpp.org
+&lt;/a&gt;
+ &lt;br&gt; 
+
+
+
+
+&lt;a href=&#34;https://inet.omnetpp.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    https://inet.omnetpp.org
+&lt;/a&gt;
+&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
 &lt;/table&gt;
@@ -862,12 +1002,34 @@
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;
-&lt;a href=&#34;#installation-for-users&#34;&gt;USER&lt;/a&gt;&lt;/td&gt;
+
+
+
+
+
+  
+  
+
+&lt;a href=&#34;#installation-for-users&#34;&gt;
+    USER
+&lt;/a&gt;
+&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;This installation type addresses those who only want to use the &lt;strong&gt;OMNeT++&lt;/strong&gt; network simulator for simulations.&lt;br&gt;Network configurations can also be adjusted.&lt;br&gt;&lt;br&gt;If you install the federate with this installation type, &lt;strong&gt;OMNeT++ 5.5&lt;/strong&gt; and &lt;strong&gt;INET 4.1&lt;/strong&gt; will automatically be installed inside &lt;code&gt;&amp;lt;mosaic&amp;gt;/bin/fed/omnetpp&lt;/code&gt; during the installation.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;
-&lt;a href=&#34;#installation-for-developers&#34;&gt;DEVELOPER&lt;/a&gt;&lt;/td&gt;
+
+
+
+
+
+  
+  
+
+&lt;a href=&#34;#installation-for-developers&#34;&gt;
+    DEVELOPER
+&lt;/a&gt;
+&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;The installation for developers addresses those who want to make changes or extend the MOSAIC OMNeT++ Federate.&lt;br&gt;&lt;br&gt;This installation type awaits that &lt;strong&gt;OMNeT++ 5.5&lt;/strong&gt; and &lt;strong&gt;INET 4.1&lt;/strong&gt; are already installed on your system and&lt;br&gt;- &lt;code&gt;PATH&lt;/code&gt; contains &lt;code&gt;/path/to/omnetpp/bin&lt;/code&gt;&lt;br&gt;- &lt;code&gt;LD_LIBRARY_PATH&lt;/code&gt; contains &lt;code&gt;/path/to/omnetpp/lib&lt;/code&gt; and &lt;code&gt;/path/to/inet/src&lt;/code&gt;&lt;br&gt;- &lt;code&gt;C_INCLUDE_PATH&lt;/code&gt; contains &lt;code&gt;/path/to/omnetpp/include&lt;/code&gt; and &lt;code&gt;/path/to/inet/src&lt;/code&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
@@ -876,7 +1038,7 @@
   &lt;div&gt;
 &lt;p&gt;If you already have &lt;strong&gt;OMNeT++ 5.5&lt;/strong&gt; and &lt;strong&gt;INET 4.1&lt;/strong&gt; installed on your
 system, but you simply want to use &lt;strong&gt;OMNeT++&lt;/strong&gt; for simulations with Eclipse MOSAIC without developing further the MOSAIC
-OMNeT++ Federate, you may also choose the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_omnetpp#installation-for-developers&#34; title=&#34;installation for developers&#34;&gt;installation for developers&lt;/a&gt;
+OMNeT++ Federate, you may also choose the &lt;a href=&#34;https://www.eclipse.org/mosaic/docs/simulators/network_simulator_omnetpp#installation-for-developers&#34;&gt;installation for developers&lt;/a&gt;
 to avoid multiple installations of &lt;strong&gt;OMNeT++&lt;/strong&gt; and &lt;strong&gt;INET&lt;/strong&gt; on your system.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
@@ -902,19 +1064,40 @@
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;strong&gt;OMNeT++&lt;/strong&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;5.5&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;
-&lt;a href=&#34;https://omnetpp.org/download/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://omnetpp.org/download/&lt;/a&gt;&lt;/td&gt;
+
+
+
+
+&lt;a href=&#34;https://omnetpp.org/download/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    https://omnetpp.org/download/
+&lt;/a&gt;
+&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;strong&gt;INET&lt;/strong&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;4.1&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;
-&lt;a href=&#34;https://github.com/inet-framework/inet/releases&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://github.com/inet-framework/inet/releases&lt;/a&gt;&lt;/td&gt;
+
+
+
+
+&lt;a href=&#34;https://github.com/inet-framework/inet/releases&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    https://github.com/inet-framework/inet/releases
+&lt;/a&gt;
+&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;strong&gt;MOSAIC OMNeT++ Federate&lt;/strong&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;20.0&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;
-&lt;a href=&#34;https://github.com/mosaic-addons/omnetpp-federate/releases&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://github.com/mosaic-addons/omnetpp-federate/releases&lt;/a&gt;&lt;/td&gt;
+
+
+
+
+&lt;a href=&#34;https://github.com/mosaic-addons/omnetpp-federate/releases&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    https://github.com/mosaic-addons/omnetpp-federate/releases
+&lt;/a&gt;
+&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
 &lt;/table&gt;
@@ -940,14 +1123,28 @@
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;--omnetpp&lt;/code&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;&amp;lt;PATH_TO_OMNET_TGZ&amp;gt;&lt;/code&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;Provide the archive containing the OMNeT++ source. You can obtain it from 
-&lt;a href=&#34;https://omnetpp.org/download/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://omnetpp.org/download/&lt;/a&gt;&lt;/td&gt;
+
+
+
+
+&lt;a href=&#34;https://omnetpp.org/download/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    https://omnetpp.org/download/
+&lt;/a&gt;
+&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:center&#34;&gt;&lt;code&gt;-i&lt;/code&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;--inet&lt;/code&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;&amp;lt;PATH_TO_INET_TGZ&amp;gt;&lt;/code&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;Provide the archive containing the inet source code. You can obtain it from 
-&lt;a href=&#34;https://inet.omnetpp.org/Download.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://inet.omnetpp.org/Download.html&lt;/a&gt;. If not given, the inet-source files are downloaded by this installation script.&lt;/td&gt;
+
+
+
+
+&lt;a href=&#34;https://inet.omnetpp.org/Download.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    https://inet.omnetpp.org/Download.html
+&lt;/a&gt;
+. If not given, the inet-source files are downloaded by this installation script.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td style=&#34;text-align:center&#34;&gt;&lt;code&gt;-f&lt;/code&gt;&lt;/td&gt;
@@ -1015,7 +1212,35 @@
 &lt;/code&gt;&lt;/pre&gt;
 &lt;p&gt;For the installation type &lt;code&gt;DEVELOPER&lt;/code&gt; the parameter &lt;code&gt;-f&lt;/code&gt; is required.&lt;br&gt;
 The installation script should terminate with &lt;code&gt;SUCCESS: The MOSAIC OMNeT++ Federate was successfully installed.&lt;/code&gt; otherwise the installation failed.&lt;/p&gt;
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/extending_mosaic/omnetpp_details&#34; title=&#34;Extending MOSAIC OMNeT&amp;#43;&amp;#43; Federate&#34;&gt;Extending MOSAIC OMNeT&amp;#43;&amp;#43; Federate&lt;/a&gt;
+&lt;p&gt;
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/extending_mosaic/omnetpp_details/&#34;&gt;
+    Extending MOSAIC OMNeT++ Federate
+&lt;/a&gt;
+&lt;/p&gt;
 &lt;h3 id=&#34;omnet-federate-configuration&#34;&gt;OMNeT++ Federate Configuration&lt;/h3&gt;
 &lt;p&gt;To use OMNeT++ as network simulator in an Eclipse MOSAIC simulation, open &lt;code&gt;&amp;lt;scenarioName&amp;gt;/scenario_config.json&lt;/code&gt; and enable OMNeT++:&lt;/p&gt;
 &lt;pre&gt;&lt;code class=&#34;language-json&#34;&gt;&amp;quot;federates&amp;quot;: {
@@ -1225,7 +1450,35 @@
 &lt;/ol&gt;
 &lt;p&gt;&lt;strong&gt;In order to start the simulation, the following steps need to be performed:&lt;/strong&gt;&lt;/p&gt;
 &lt;ol&gt;
-&lt;li&gt;Set up the &lt;code&gt;confWifi.xml&lt;/code&gt;-file in the scenario folder (see section &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_ns3#configuration&#34; title=&#34;Configuration&#34;&gt;Configuration&lt;/a&gt;). An example confWifi.xml - file is shipped with the Tiergarten scenario.&lt;/li&gt;
+&lt;li&gt;Set up the &lt;code&gt;confWifi.xml&lt;/code&gt;-file in the scenario folder (see section 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/simulators/network_simulator_ns3/#configuration&#34;&gt;
+    Configuration
+&lt;/a&gt;
+). An example confWifi.xml - file is shipped with the Tiergarten scenario.&lt;/li&gt;
 &lt;li&gt;For reasonable result logging, the logger-configuration in &lt;code&gt;mosaic/etc/logback.xml&lt;/code&gt; has to be adapted to support the ns-3 ambassador and federate.&lt;/li&gt;
 &lt;li&gt;At last ns-3 has to be activated in the &lt;code&gt;mosaic_config.xml&lt;/code&gt; and the simulation can be started.&lt;/li&gt;
 &lt;/ol&gt;
@@ -1371,7 +1624,34 @@
 &lt;tr&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;&lt;code&gt;singlehopDelay&lt;/code&gt;&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;A delay configuration for the direct communication between two nodes. (
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/extending_mosaic/delay_models/&#34;&gt;See here&lt;/a&gt;)&lt;/td&gt;
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/extending_mosaic/delay_models/&#34;&gt;
+    See here
+&lt;/a&gt;
+)&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;Delay&lt;/td&gt;
 &lt;td style=&#34;text-align:left&#34;&gt;`ConstantDelay       |&lt;/td&gt;
 &lt;/tr&gt;
@@ -1423,7 +1703,7 @@
 &lt;/code&gt;&lt;/pre&gt;
 &lt;div class=&#34;alert alert-tip&#34;&gt;
   &lt;div&gt;
-&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/mosaic_configuration/sns_config/&#34; title=&#34;SNS Configuration&#34;&gt;SNS Configuration&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/docs/mosaic_configuration/sns_config&#34;&gt;SNS Configuration&lt;/a&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
 &lt;h2 id=&#34;transmission-logic&#34;&gt;Transmission Logic&lt;/h2&gt;
@@ -1566,7 +1846,18 @@
 &lt;/p&gt;
 &lt;p&gt;The realistic model accounts for possible transmission failures more accurately. The easiest case is that the sender itself is inside
 of the destination area&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; and will start a 
-&lt;a href=&#34;#flooding-transmission&#34;&gt;Flooding Transmission&lt;/a&gt; within this area (see figure below).
+
+
+
+
+
+  
+  
+
+&lt;a href=&#34;#flooding-transmission&#34;&gt;
+    Flooding Transmission
+&lt;/a&gt;
+ within this area (see figure below).
 
 
 
@@ -1602,7 +1893,18 @@
 &lt;/figure&gt;
 &lt;/p&gt;
 &lt;p&gt;In case the sending entity is outside of the destination area, a 
-&lt;a href=&#34;#approaching-transmission&#34;&gt;Forwarding Transmission&lt;/a&gt; has to
+
+
+
+
+
+  
+  
+
+&lt;a href=&#34;#approaching-transmission&#34;&gt;
+    Forwarding Transmission
+&lt;/a&gt;
+ has to
 be executed first. This is can also be described as an &lt;em&gt;AnyCast&lt;/em&gt;, since the goal of this transmission is to reach &lt;em&gt;any&lt;/em&gt; entity
 inside the destination area. We try to achieve this by building a &amp;ldquo;chain&amp;rdquo; of entities, that will forward the message to the destination
 are (see figure below).
@@ -1641,8 +1943,30 @@
 &lt;/figure&gt;
 &lt;/p&gt;
 &lt;p&gt;The SNS however never uses 
-&lt;a href=&#34;#approaching-transmission&#34;&gt;Forwarding Transmissions&lt;/a&gt; individually, rather they are combined with a 
-&lt;a href=&#34;#flooding-transmission&#34;&gt;Flooding Transmission&lt;/a&gt;, which
+
+
+
+
+
+  
+  
+
+&lt;a href=&#34;#approaching-transmission&#34;&gt;
+    Forwarding Transmissions
+&lt;/a&gt;
+ individually, rather they are combined with a 
+
+
+
+
+
+  
+  
+
+&lt;a href=&#34;#flooding-transmission&#34;&gt;
+    Flooding Transmission
+&lt;/a&gt;
+, which
 will simulate a way, that GeaCasts can be implemented in reality. The figure below depicts this behaviour.
 
 
@@ -1695,9 +2019,23 @@
 &lt;h3 id=&#34;sophisticatedadhoctransmissionmodel&#34;&gt;&lt;code&gt;SophisticatedAdhocTransmissionModel&lt;/code&gt;&lt;/h3&gt;
 &lt;p&gt;This model offers are more realistic simulation of adhoc transmissions, using an implementation of a greedy-forwarding and flooding
 algorithm (see 
-&lt;a href=&#34;https://en.wikipedia.org/wiki/Geographic_routing&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;here (greedy forwarding)&lt;/a&gt; &amp;amp;
 
-&lt;a href=&#34;https://en.wikipedia.org/wiki/Flooding_%28computer_networking%29&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;here (flooding)&lt;/a&gt;). For TopoCasts this model behaves very
+
+
+
+&lt;a href=&#34;https://en.wikipedia.org/wiki/Geographic_routing&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    here (greedy forwarding)
+&lt;/a&gt;
+ &amp;amp;
+
+
+
+
+
+&lt;a href=&#34;https://en.wikipedia.org/wiki/Flooding_%28computer_networking%29&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    here (flooding)
+&lt;/a&gt;
+). For TopoCasts this model behaves very
 similarly to the &lt;code&gt;SimpleAdhocTransmissionModel&lt;/code&gt;, since TopoCasts are always configured with only one hop.
 For GeoCasts however, this model follows the flowchart above, trying to &amp;ldquo;approach&amp;rdquo; a destination area if it can&amp;rsquo;t be reached directly.&lt;/p&gt;
 &lt;h4 id=&#34;approaching-greedy-forwarding&#34;&gt;Approaching (Greedy forwarding)&lt;/h4&gt;
@@ -2103,7 +2441,14 @@
 &lt;h4 id=&#34;flooding&#34;&gt;Flooding&lt;/h4&gt;
 &lt;p&gt;The implementation of Flooding is fairly equivalent as described on
 
-&lt;a href=&#34;https://en.wikipedia.org/wiki/Flooding_%28computer_networking%29&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;wikipedia&lt;/a&gt;. Each entity forwards the message to all entities
+
+
+
+
+&lt;a href=&#34;https://en.wikipedia.org/wiki/Flooding_%28computer_networking%29&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
+    wikipedia
+&lt;/a&gt;
+. Each entity forwards the message to all entities
 in its communication range. Entities, that already received the message won&amp;rsquo;t receive it again; this is different from many real-life
 implementations, where messages are send to all reachable entities except the sender. However, since the simulation has total
 knowledge of all simulated entities, it is easier to overcome a lot of the disadvantages, that flooding faces
@@ -2115,9 +2460,65 @@
 messages using that topology. Also, the aforementioned &amp;ldquo;Face-Routing&amp;rdquo; could be of interest. Additionally, the calculation
 of delays could be made more realistic.&lt;/p&gt;
 &lt;h2 id=&#34;accessing-sns-functionality-from-your-applications&#34;&gt;Accessing SNS-functionality from your applications&lt;/h2&gt;
-&lt;p&gt;In order for your scenario to enable the SNS follow the steps &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/scenario_configuration#communication-simulators-cell-ns3-omnetpp-sns&#34; title=&#34;here&#34;&gt;here&lt;/a&gt;.
+&lt;p&gt;In order for your scenario to enable the SNS follow the steps 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/building_scenarios/scenario_configuration/#communication-simulators-cell-ns3-omnetpp-sns&#34;&gt;
+    here
+&lt;/a&gt;
+.
 An overview of how to configure AdHoc-modules and usage of the API for Routing and Message-Building functions,
-can be found &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/communication&#34; title=&#34;here&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
+can be found 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/communication/&#34;&gt;
+    here
+&lt;/a&gt;
+.&lt;/p&gt;
 &lt;section class=&#34;footnotes&#34; role=&#34;doc-endnotes&#34;&gt;
 &lt;hr&gt;
 &lt;ol&gt;
@@ -2173,7 +2574,7 @@
 file.&lt;/p&gt;
 &lt;div class=&#34;alert alert-tip&#34;&gt;
   &lt;div&gt;
-&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/mosaic_configuration/cell_network_config/&#34; title=&#34;Network&#34;&gt;Network&lt;/a&gt; and &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/mosaic_configuration/cell_region_config/&#34; title=&#34;Regions Configuration&#34;&gt;Regions Configuration&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_network_config&#34;&gt;Network&lt;/a&gt; and &lt;a href=&#34;https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_region_config&#34;&gt;Regions Configuration&lt;/a&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
 &lt;h3 id=&#34;installation&#34;&gt;Installation&lt;/h3&gt;
@@ -2203,8 +2604,8 @@
   &lt;div&gt;
   &lt;p&gt;Read the detailed documentations of:&lt;/p&gt;
 &lt;ul&gt;
-&lt;li&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/mosaic_configuration/cell_network_config/&#34; title=&#34;Cell Network Configuration&#34;&gt;Cell Network Configuration&lt;/a&gt;&lt;/li&gt;
-&lt;li&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/mosaic_configuration/cell_region_config/&#34; title=&#34;Cell Region Configuration&#34;&gt;Cell Region Configuration&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_network_config&#34;&gt;Cell Network Configuration&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_region_config&#34;&gt;Cell Region Configuration&lt;/a&gt;&lt;/li&gt;
 &lt;/ul&gt;
   &lt;/div&gt;
 &lt;/div&gt;
@@ -2409,7 +2810,35 @@
 through the transport over the cellular network.&lt;/p&gt;
 &lt;p&gt;The cellular simulator offers various modes to estimate the delay of the transmissions. The type of
 estimation is specified with by &lt;code&gt;delayType&lt;/code&gt; for the uplink and downlink for each region. You may also refer to the
-&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/extending_mosaic/delay_models&#34; title=&#34;Delay-Chapter&#34;&gt;Delay-Chapter&lt;/a&gt;.&lt;/p&gt;
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/extending_mosaic/delay_models/&#34;&gt;
+    Delay-Chapter
+&lt;/a&gt;
+.&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;code&gt;delay.type = ’ConstantDelay’&lt;/code&gt;: The message is transmitted with the latency being exactly equal to delay.&lt;/li&gt;
 &lt;li&gt;&lt;code&gt;delay.type = ’SimpleRandomDelay’&lt;/code&gt;: The latency can assume different (randomly generated and uniformly distributed) values between
@@ -2435,12 +2864,12 @@
 &lt;p&gt;The Geocaster evaluates the message headers for cellular messages, which are created by the communicating applications in the
 Application Simulator.&lt;/p&gt;
 &lt;p&gt;It supports the following addressing and casting schemes.&lt;/p&gt;
-&lt;p&gt;&lt;strong&gt;&lt;code&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/communication#cellular-topocast&#34; title=&#34;CellTopocast&#34;&gt;CellTopocast&lt;/a&gt;&lt;/code&gt;&lt;/strong&gt; is the normal unicast, where the Geocaster simply resolves
+&lt;p&gt;&lt;strong&gt;&lt;code&gt;[CellTopocast](/docs/develop_applications/communication#cellular-topocast)&lt;/code&gt;&lt;/strong&gt; is the normal unicast, where the Geocaster simply resolves
 the single receiver via theIPResolver. Hence, the CellTopocast directly routes the message further. Currently, Topocast doesn&amp;rsquo;t allow
 broadcast or anycast addresses, but any transmission protocols (tcp, udp).&lt;/p&gt;
-&lt;p&gt;&lt;strong&gt;&lt;code&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/communication#cellular-geocast&#34; title=&#34;CellGeoUnicast&#34;&gt;CellGeoUnicast&lt;/a&gt;&lt;/code&gt;&lt;/strong&gt; addresses every node in the destination area individually.
+&lt;p&gt;&lt;strong&gt;&lt;code&gt;[CellGeoUnicast](/docs/develop_applications/communication#cellular-geocast)&lt;/code&gt;&lt;/strong&gt; addresses every node in the destination area individually.
 In this way it takes a geographic address and results in a loop to generate multiple unicasts.&lt;/p&gt;
-&lt;p&gt;&lt;strong&gt;&lt;code&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/develop_applications/communication#cellular-geobroadcast&#34; title=&#34;CellGeoBroadcast&#34;&gt;CellGeoBroadcast&lt;/a&gt;&lt;/code&gt;&lt;/strong&gt;, which is basically MBMS, uses one broadcast to all
+&lt;p&gt;&lt;strong&gt;&lt;code&gt;[CellGeoBroadcast](/docs/develop_applications/communication#cellular-geobroadcast)&lt;/code&gt;&lt;/strong&gt;, which is basically MBMS, uses one broadcast to all
 nodes in the destined regions.The MBMS uses the different transmission mode of multicast in the downlink. CellGeoUnicast as well as
 CellGeoBroadcast require broadcast, but don’t allow tcp (as ack for broadcasts is denied).&lt;/p&gt;
 </description>
@@ -2461,7 +2890,7 @@
 &lt;h3 id=&#34;configuration&#34;&gt;Configuration&lt;/h3&gt;
 &lt;div class=&#34;alert alert-tip&#34;&gt;
   &lt;div&gt;
-&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/docs/mosaic_configuration/environment_config/&#34; title=&#34;Environment Configuration&#34;&gt;Environment Configuration&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Read the detailed documentation of the &lt;a href=&#34;https://www.eclipse.org/mosaic/docs/mosaic_configuration/environment_config&#34;&gt;Environment Configuration&lt;/a&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
 &lt;p&gt;The root node of the configuration is a list of environment events. Each event require the type of the event, a rectangle area, a
@@ -2506,7 +2935,7 @@
       <description>&lt;div class=&#34;alert alert-extended&#34;&gt;
   &lt;span class=&#34;extended-icon&#34; style=&#34;background-image: url(/mosaic/img/alert-extended.svg)&#34;&gt;&lt;/span&gt;
   &lt;div&gt;
-&lt;p&gt;The &lt;strong&gt;Battery Simulator&lt;/strong&gt; is part of &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/download/#overview&#34; title=&#34;MOSAIC Extended&#34;&gt;MOSAIC Extended&lt;/a&gt;.&lt;br&gt;
+&lt;p&gt;The &lt;strong&gt;Battery Simulator&lt;/strong&gt; is part of &lt;a href=&#34;https://www.eclipse.org/mosaic/download#overview&#34;&gt;MOSAIC Extended&lt;/a&gt;.&lt;br&gt;
 For further information on licenses, feel free to contact us via &lt;strong&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;mosaic@fokus.fraunhofer.de&lt;/a&gt;&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
@@ -2583,7 +3012,7 @@
       <description>&lt;div class=&#34;alert alert-extended&#34;&gt;
   &lt;span class=&#34;extended-icon&#34; style=&#34;background-image: url(/mosaic/img/alert-extended.svg)&#34;&gt;&lt;/span&gt;
   &lt;div&gt;
-&lt;p&gt;The &lt;strong&gt;VMS Simulator&lt;/strong&gt; is part of &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/download/#overview&#34; title=&#34;MOSAIC Extended&#34;&gt;MOSAIC Extended&lt;/a&gt;&lt;/strong&gt;.&lt;br&gt;
+&lt;p&gt;The &lt;strong&gt;VMS Simulator&lt;/strong&gt; is part of &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/download#overview&#34;&gt;MOSAIC Extended&lt;/a&gt;&lt;/strong&gt;.&lt;br&gt;
 For further information on licenses, feel free to contact us via &lt;strong&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;mosaic@fokus.fraunhofer.de&lt;/a&gt;&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
diff --git a/docs/simulators/network_simulator_cell/index.html b/docs/simulators/network_simulator_cell/index.html
index 97e0233..7dc13fd 100644
--- a/docs/simulators/network_simulator_cell/index.html
+++ b/docs/simulators/network_simulator_cell/index.html
@@ -901,6 +901,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -913,6 +917,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1058,7 +1066,7 @@
 file.</p>
 <div class="alert alert-tip">
   <div>
-<p>Read the detailed documentation of the <a href="/mosaic/docs/mosaic_configuration/cell_network_config/" title="Network">Network</a> and <a href="/mosaic/docs/mosaic_configuration/cell_region_config/" title="Regions Configuration">Regions Configuration</a>.</p>
+<p>Read the detailed documentation of the <a href="/docs/mosaic_configuration/cell_network_config">Network</a> and <a href="/docs/mosaic_configuration/cell_region_config">Regions Configuration</a>.</p>
   </div>
 </div>
 <h3 id="installation">Installation</h3>
@@ -1088,8 +1096,8 @@
   <div>
   <p>Read the detailed documentations of:</p>
 <ul>
-<li><a href="/mosaic/docs/mosaic_configuration/cell_network_config/" title="Cell Network Configuration">Cell Network Configuration</a></li>
-<li><a href="/mosaic/docs/mosaic_configuration/cell_region_config/" title="Cell Region Configuration">Cell Region Configuration</a></li>
+<li><a href="/docs/mosaic_configuration/cell_network_config">Cell Network Configuration</a></li>
+<li><a href="/docs/mosaic_configuration/cell_region_config">Cell Region Configuration</a></li>
 </ul>
   </div>
 </div>
@@ -1294,7 +1302,35 @@
 through the transport over the cellular network.</p>
 <p>The cellular simulator offers various modes to estimate the delay of the transmissions. The type of
 estimation is specified with by <code>delayType</code> for the uplink and downlink for each region. You may also refer to the
-<a href="/mosaic/docs/extending_mosaic/delay_models" title="Delay-Chapter">Delay-Chapter</a>.</p>
+
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/extending_mosaic/delay_models/">
+    Delay-Chapter
+</a>
+.</p>
 <ul>
 <li><code>delay.type = ’ConstantDelay’</code>: The message is transmitted with the latency being exactly equal to delay.</li>
 <li><code>delay.type = ’SimpleRandomDelay’</code>: The latency can assume different (randomly generated and uniformly distributed) values between
@@ -1320,12 +1356,12 @@
 <p>The Geocaster evaluates the message headers for cellular messages, which are created by the communicating applications in the
 Application Simulator.</p>
 <p>It supports the following addressing and casting schemes.</p>
-<p><strong><code><a href="/mosaic/docs/develop_applications/communication#cellular-topocast" title="CellTopocast">CellTopocast</a></code></strong> is the normal unicast, where the Geocaster simply resolves
+<p><strong><code>[CellTopocast](/docs/develop_applications/communication#cellular-topocast)</code></strong> is the normal unicast, where the Geocaster simply resolves
 the single receiver via theIPResolver. Hence, the CellTopocast directly routes the message further. Currently, Topocast doesn&rsquo;t allow
 broadcast or anycast addresses, but any transmission protocols (tcp, udp).</p>
-<p><strong><code><a href="/mosaic/docs/develop_applications/communication#cellular-geocast" title="CellGeoUnicast">CellGeoUnicast</a></code></strong> addresses every node in the destination area individually.
+<p><strong><code>[CellGeoUnicast](/docs/develop_applications/communication#cellular-geocast)</code></strong> addresses every node in the destination area individually.
 In this way it takes a geographic address and results in a loop to generate multiple unicasts.</p>
-<p><strong><code><a href="/mosaic/docs/develop_applications/communication#cellular-geobroadcast" title="CellGeoBroadcast">CellGeoBroadcast</a></code></strong>, which is basically MBMS, uses one broadcast to all
+<p><strong><code>[CellGeoBroadcast](/docs/develop_applications/communication#cellular-geobroadcast)</code></strong>, which is basically MBMS, uses one broadcast to all
 nodes in the destined regions.The MBMS uses the different transmission mode of multicast in the downlink. CellGeoUnicast as well as
 CellGeoBroadcast require broadcast, but don’t allow tcp (as ack for broadcasts is denied).</p>
 
diff --git a/docs/simulators/network_simulator_ns3/index.html b/docs/simulators/network_simulator_ns3/index.html
index 223e68c..c871302 100644
--- a/docs/simulators/network_simulator_ns3/index.html
+++ b/docs/simulators/network_simulator_ns3/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1157,7 +1165,35 @@
 </ol>
 <p><strong>In order to start the simulation, the following steps need to be performed:</strong></p>
 <ol>
-<li>Set up the <code>confWifi.xml</code>-file in the scenario folder (see section <a href="/mosaic/docs/simulators/network_simulator_ns3#configuration" title="Configuration">Configuration</a>). An example confWifi.xml - file is shipped with the Tiergarten scenario.</li>
+<li>Set up the <code>confWifi.xml</code>-file in the scenario folder (see section 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_ns3/#configuration">
+    Configuration
+</a>
+). An example confWifi.xml - file is shipped with the Tiergarten scenario.</li>
 <li>For reasonable result logging, the logger-configuration in <code>mosaic/etc/logback.xml</code> has to be adapted to support the ns-3 ambassador and federate.</li>
 <li>At last ns-3 has to be activated in the <code>mosaic_config.xml</code> and the simulation can be started.</li>
 </ol>
diff --git a/docs/simulators/network_simulator_omnetpp/index.html b/docs/simulators/network_simulator_omnetpp/index.html
index 3bdfcc7..acd8026 100644
--- a/docs/simulators/network_simulator_omnetpp/index.html
+++ b/docs/simulators/network_simulator_omnetpp/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1019,7 +1027,14 @@
 These are the Mobility Framework and the <strong>INET</strong> Framework. As INET provides all models necessary for simulating Vehicle-2-X communication,
 it is selected for the integration to Eclipse MOSAIC.</p>
 <p>For more information on the <strong>INET</strong> extension you should look closer on the 
-<a href="https://inet.omnetpp.org" target="_blank" rel="noopener">website</a>.</p>
+
+
+
+
+<a href="https://inet.omnetpp.org" target="_blank" rel="noopener">
+    website
+</a>
+.</p>
 <table>
 <thead>
 <tr>
@@ -1043,8 +1058,22 @@
 <td><strong>Supported version(s)</strong></td>
 <td>OMNeT++ 5.5 <br>INET 4.1</td>
 <td style="text-align:left">
-<a href="http://www.omnetpp.org" target="_blank" rel="noopener">http://www.omnetpp.org</a> <br> 
-<a href="https://inet.omnetpp.org" target="_blank" rel="noopener">https://inet.omnetpp.org</a></td>
+
+
+
+
+<a href="http://www.omnetpp.org" target="_blank" rel="noopener">
+    http://www.omnetpp.org
+</a>
+ <br> 
+
+
+
+
+<a href="https://inet.omnetpp.org" target="_blank" rel="noopener">
+    https://inet.omnetpp.org
+</a>
+</td>
 </tr>
 </tbody>
 </table>
@@ -1060,12 +1089,34 @@
 <tbody>
 <tr>
 <td style="text-align:left">
-<a href="#installation-for-users">USER</a></td>
+
+
+
+
+
+  
+  
+
+<a href="#installation-for-users">
+    USER
+</a>
+</td>
 <td style="text-align:left">This installation type addresses those who only want to use the <strong>OMNeT++</strong> network simulator for simulations.<br>Network configurations can also be adjusted.<br><br>If you install the federate with this installation type, <strong>OMNeT++ 5.5</strong> and <strong>INET 4.1</strong> will automatically be installed inside <code>&lt;mosaic&gt;/bin/fed/omnetpp</code> during the installation.</td>
 </tr>
 <tr>
 <td style="text-align:left">
-<a href="#installation-for-developers">DEVELOPER</a></td>
+
+
+
+
+
+  
+  
+
+<a href="#installation-for-developers">
+    DEVELOPER
+</a>
+</td>
 <td style="text-align:left">The installation for developers addresses those who want to make changes or extend the MOSAIC OMNeT++ Federate.<br><br>This installation type awaits that <strong>OMNeT++ 5.5</strong> and <strong>INET 4.1</strong> are already installed on your system and<br>- <code>PATH</code> contains <code>/path/to/omnetpp/bin</code><br>- <code>LD_LIBRARY_PATH</code> contains <code>/path/to/omnetpp/lib</code> and <code>/path/to/inet/src</code><br>- <code>C_INCLUDE_PATH</code> contains <code>/path/to/omnetpp/include</code> and <code>/path/to/inet/src</code></td>
 </tr>
 </tbody>
@@ -1074,7 +1125,7 @@
   <div>
 <p>If you already have <strong>OMNeT++ 5.5</strong> and <strong>INET 4.1</strong> installed on your
 system, but you simply want to use <strong>OMNeT++</strong> for simulations with Eclipse MOSAIC without developing further the MOSAIC
-OMNeT++ Federate, you may also choose the <a href="/mosaic/docs/simulators/network_simulator_omnetpp#installation-for-developers" title="installation for developers">installation for developers</a>
+OMNeT++ Federate, you may also choose the <a href="/docs/simulators/network_simulator_omnetpp#installation-for-developers">installation for developers</a>
 to avoid multiple installations of <strong>OMNeT++</strong> and <strong>INET</strong> on your system.</p>
   </div>
 </div>
@@ -1100,19 +1151,40 @@
 <td style="text-align:left"><strong>OMNeT++</strong></td>
 <td style="text-align:left">5.5</td>
 <td style="text-align:left">
-<a href="https://omnetpp.org/download/" target="_blank" rel="noopener">https://omnetpp.org/download/</a></td>
+
+
+
+
+<a href="https://omnetpp.org/download/" target="_blank" rel="noopener">
+    https://omnetpp.org/download/
+</a>
+</td>
 </tr>
 <tr>
 <td style="text-align:left"><strong>INET</strong></td>
 <td style="text-align:left">4.1</td>
 <td style="text-align:left">
-<a href="https://github.com/inet-framework/inet/releases" target="_blank" rel="noopener">https://github.com/inet-framework/inet/releases</a></td>
+
+
+
+
+<a href="https://github.com/inet-framework/inet/releases" target="_blank" rel="noopener">
+    https://github.com/inet-framework/inet/releases
+</a>
+</td>
 </tr>
 <tr>
 <td style="text-align:left"><strong>MOSAIC OMNeT++ Federate</strong></td>
 <td style="text-align:left">20.0</td>
 <td style="text-align:left">
-<a href="https://github.com/mosaic-addons/omnetpp-federate/releases" target="_blank" rel="noopener">https://github.com/mosaic-addons/omnetpp-federate/releases</a></td>
+
+
+
+
+<a href="https://github.com/mosaic-addons/omnetpp-federate/releases" target="_blank" rel="noopener">
+    https://github.com/mosaic-addons/omnetpp-federate/releases
+</a>
+</td>
 </tr>
 </tbody>
 </table>
@@ -1138,14 +1210,28 @@
 <td style="text-align:left"><code>--omnetpp</code></td>
 <td style="text-align:left"><code>&lt;PATH_TO_OMNET_TGZ&gt;</code></td>
 <td style="text-align:left">Provide the archive containing the OMNeT++ source. You can obtain it from 
-<a href="https://omnetpp.org/download/" target="_blank" rel="noopener">https://omnetpp.org/download/</a></td>
+
+
+
+
+<a href="https://omnetpp.org/download/" target="_blank" rel="noopener">
+    https://omnetpp.org/download/
+</a>
+</td>
 </tr>
 <tr>
 <td style="text-align:center"><code>-i</code></td>
 <td style="text-align:left"><code>--inet</code></td>
 <td style="text-align:left"><code>&lt;PATH_TO_INET_TGZ&gt;</code></td>
 <td style="text-align:left">Provide the archive containing the inet source code. You can obtain it from 
-<a href="https://inet.omnetpp.org/Download.html" target="_blank" rel="noopener">https://inet.omnetpp.org/Download.html</a>. If not given, the inet-source files are downloaded by this installation script.</td>
+
+
+
+
+<a href="https://inet.omnetpp.org/Download.html" target="_blank" rel="noopener">
+    https://inet.omnetpp.org/Download.html
+</a>
+. If not given, the inet-source files are downloaded by this installation script.</td>
 </tr>
 <tr>
 <td style="text-align:center"><code>-f</code></td>
@@ -1213,7 +1299,35 @@
 </code></pre>
 <p>For the installation type <code>DEVELOPER</code> the parameter <code>-f</code> is required.<br>
 The installation script should terminate with <code>SUCCESS: The MOSAIC OMNeT++ Federate was successfully installed.</code> otherwise the installation failed.</p>
-<a href="/mosaic/docs/extending_mosaic/omnetpp_details" title="Extending MOSAIC OMNeT&#43;&#43; Federate">Extending MOSAIC OMNeT&#43;&#43; Federate</a>
+<p>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/extending_mosaic/omnetpp_details/">
+    Extending MOSAIC OMNeT++ Federate
+</a>
+</p>
 <h3 id="omnet-federate-configuration">OMNeT++ Federate Configuration</h3>
 <p>To use OMNeT++ as network simulator in an Eclipse MOSAIC simulation, open <code>&lt;scenarioName&gt;/scenario_config.json</code> and enable OMNeT++:</p>
 <pre><code class="language-json">&quot;federates&quot;: {
diff --git a/docs/simulators/network_simulator_sns/index.html b/docs/simulators/network_simulator_sns/index.html
index 6c99c7c..2df2d67 100644
--- a/docs/simulators/network_simulator_sns/index.html
+++ b/docs/simulators/network_simulator_sns/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1051,7 +1059,34 @@
 <tr>
 <td style="text-align:left"><code>singlehopDelay</code></td>
 <td style="text-align:left">A delay configuration for the direct communication between two nodes. (
-<a href="/mosaic/docs/extending_mosaic/delay_models/">See here</a>)</td>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/extending_mosaic/delay_models/">
+    See here
+</a>
+)</td>
 <td style="text-align:left">Delay</td>
 <td style="text-align:left">`ConstantDelay       |</td>
 </tr>
@@ -1103,7 +1138,7 @@
 </code></pre>
 <div class="alert alert-tip">
   <div>
-<p>Read the detailed documentation of the <a href="/mosaic/docs/mosaic_configuration/sns_config/" title="SNS Configuration">SNS Configuration</a>.</p>
+<p>Read the detailed documentation of the <a href="/docs/mosaic_configuration/sns_config">SNS Configuration</a>.</p>
   </div>
 </div>
 <h2 id="transmission-logic">Transmission Logic</h2>
@@ -1246,7 +1281,18 @@
 </p>
 <p>The realistic model accounts for possible transmission failures more accurately. The easiest case is that the sender itself is inside
 of the destination area<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup> and will start a 
-<a href="#flooding-transmission">Flooding Transmission</a> within this area (see figure below).
+
+
+
+
+
+  
+  
+
+<a href="#flooding-transmission">
+    Flooding Transmission
+</a>
+ within this area (see figure below).
 
 
 
@@ -1282,7 +1328,18 @@
 </figure>
 </p>
 <p>In case the sending entity is outside of the destination area, a 
-<a href="#approaching-transmission">Forwarding Transmission</a> has to
+
+
+
+
+
+  
+  
+
+<a href="#approaching-transmission">
+    Forwarding Transmission
+</a>
+ has to
 be executed first. This is can also be described as an <em>AnyCast</em>, since the goal of this transmission is to reach <em>any</em> entity
 inside the destination area. We try to achieve this by building a &ldquo;chain&rdquo; of entities, that will forward the message to the destination
 are (see figure below).
@@ -1321,8 +1378,30 @@
 </figure>
 </p>
 <p>The SNS however never uses 
-<a href="#approaching-transmission">Forwarding Transmissions</a> individually, rather they are combined with a 
-<a href="#flooding-transmission">Flooding Transmission</a>, which
+
+
+
+
+
+  
+  
+
+<a href="#approaching-transmission">
+    Forwarding Transmissions
+</a>
+ individually, rather they are combined with a 
+
+
+
+
+
+  
+  
+
+<a href="#flooding-transmission">
+    Flooding Transmission
+</a>
+, which
 will simulate a way, that GeaCasts can be implemented in reality. The figure below depicts this behaviour.
 
 
@@ -1375,9 +1454,23 @@
 <h3 id="sophisticatedadhoctransmissionmodel"><code>SophisticatedAdhocTransmissionModel</code></h3>
 <p>This model offers are more realistic simulation of adhoc transmissions, using an implementation of a greedy-forwarding and flooding
 algorithm (see 
-<a href="https://en.wikipedia.org/wiki/Geographic_routing" target="_blank" rel="noopener">here (greedy forwarding)</a> &amp;
 
-<a href="https://en.wikipedia.org/wiki/Flooding_%28computer_networking%29" target="_blank" rel="noopener">here (flooding)</a>). For TopoCasts this model behaves very
+
+
+
+<a href="https://en.wikipedia.org/wiki/Geographic_routing" target="_blank" rel="noopener">
+    here (greedy forwarding)
+</a>
+ &amp;
+
+
+
+
+
+<a href="https://en.wikipedia.org/wiki/Flooding_%28computer_networking%29" target="_blank" rel="noopener">
+    here (flooding)
+</a>
+). For TopoCasts this model behaves very
 similarly to the <code>SimpleAdhocTransmissionModel</code>, since TopoCasts are always configured with only one hop.
 For GeoCasts however, this model follows the flowchart above, trying to &ldquo;approach&rdquo; a destination area if it can&rsquo;t be reached directly.</p>
 <h4 id="approaching-greedy-forwarding">Approaching (Greedy forwarding)</h4>
@@ -1783,7 +1876,14 @@
 <h4 id="flooding">Flooding</h4>
 <p>The implementation of Flooding is fairly equivalent as described on
 
-<a href="https://en.wikipedia.org/wiki/Flooding_%28computer_networking%29" target="_blank" rel="noopener">wikipedia</a>. Each entity forwards the message to all entities
+
+
+
+
+<a href="https://en.wikipedia.org/wiki/Flooding_%28computer_networking%29" target="_blank" rel="noopener">
+    wikipedia
+</a>
+. Each entity forwards the message to all entities
 in its communication range. Entities, that already received the message won&rsquo;t receive it again; this is different from many real-life
 implementations, where messages are send to all reachable entities except the sender. However, since the simulation has total
 knowledge of all simulated entities, it is easier to overcome a lot of the disadvantages, that flooding faces
@@ -1795,9 +1895,65 @@
 messages using that topology. Also, the aforementioned &ldquo;Face-Routing&rdquo; could be of interest. Additionally, the calculation
 of delays could be made more realistic.</p>
 <h2 id="accessing-sns-functionality-from-your-applications">Accessing SNS-functionality from your applications</h2>
-<p>In order for your scenario to enable the SNS follow the steps <a href="/mosaic/docs/building_scenarios/scenario_configuration#communication-simulators-cell-ns3-omnetpp-sns" title="here">here</a>.
+<p>In order for your scenario to enable the SNS follow the steps 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/scenario_configuration/#communication-simulators-cell-ns3-omnetpp-sns">
+    here
+</a>
+.
 An overview of how to configure AdHoc-modules and usage of the API for Routing and Message-Building functions,
-can be found <a href="/mosaic/docs/develop_applications/communication" title="here">here</a>.</p>
+can be found 
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/develop_applications/communication/">
+    here
+</a>
+.</p>
 <section class="footnotes" role="doc-endnotes">
 <hr>
 <ol>
diff --git a/docs/simulators/traffic_simulator_sumo/index.html b/docs/simulators/traffic_simulator_sumo/index.html
index 0e76269..02036a1 100644
--- a/docs/simulators/traffic_simulator_sumo/index.html
+++ b/docs/simulators/traffic_simulator_sumo/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1038,7 +1046,14 @@
 <tr>
 <td><strong>Website</strong></td>
 <td>
-<a href="https://www.eclipse.org/sumo/" target="_blank" rel="noopener">https://www.eclipse.org/sumo/</a></td>
+
+
+
+
+<a href="https://www.eclipse.org/sumo/" target="_blank" rel="noopener">
+    https://www.eclipse.org/sumo/
+</a>
+</td>
 <td></td>
 </tr>
 <tr>
@@ -1086,7 +1101,7 @@
 </code></pre>
 <div class="alert alert-tip">
   <div>
-<p>Read the detailed documentation of the <a href="/mosaic/docs/mosaic_configuration/sumo_config/" title="SUMO Configuration">SUMO Configuration</a>.</p>
+<p>Read the detailed documentation of the <a href="/docs/mosaic_configuration/sumo_config">SUMO Configuration</a>.</p>
   </div>
 </div>
 <p>Next to <code>sumo_config.json</code>, the following configuration files are required for every SUMO simulation scenario:</p>
diff --git a/docs/simulators/vms_simulator/index.html b/docs/simulators/vms_simulator/index.html
index 370cd4b..1bce360 100644
--- a/docs/simulators/vms_simulator/index.html
+++ b/docs/simulators/vms_simulator/index.html
@@ -901,6 +901,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -913,6 +917,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1008,7 +1016,7 @@
             <div class="alert alert-extended">
   <span class="extended-icon" style="background-image: url(/mosaic/img/alert-extended.svg)"></span>
   <div>
-<p>The <strong>VMS Simulator</strong> is part of <strong><a href="/mosaic/download/#overview" title="MOSAIC Extended">MOSAIC Extended</a></strong>.<br>
+<p>The <strong>VMS Simulator</strong> is part of <strong><a href="/download#overview">MOSAIC Extended</a></strong>.<br>
 For further information on licenses, feel free to contact us via <strong><a href="mailto:mosaic@fokus.fraunhofer.de"><a href="mailto:mosaic@fokus.fraunhofer.de">mosaic@fokus.fraunhofer.de</a></a></strong>.</p>
   </div>
 </div>
diff --git a/docs/visualization/filevis/index.html b/docs/visualization/filevis/index.html
index e8e2e44..da547da 100644
--- a/docs/visualization/filevis/index.html
+++ b/docs/visualization/filevis/index.html
@@ -899,6 +899,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -911,6 +915,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
diff --git a/docs/visualization/index.html b/docs/visualization/index.html
index a41e294..ac843b0 100644
--- a/docs/visualization/index.html
+++ b/docs/visualization/index.html
@@ -896,6 +896,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -908,6 +912,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
diff --git a/docs/visualization/index.xml b/docs/visualization/index.xml
index 3e7d392..41a09f7 100644
--- a/docs/visualization/index.xml
+++ b/docs/visualization/index.xml
@@ -198,7 +198,7 @@
       <description>&lt;div class=&#34;alert alert-extended&#34;&gt;
   &lt;span class=&#34;extended-icon&#34; style=&#34;background-image: url(/mosaic/img/alert-extended.svg)&#34;&gt;&lt;/span&gt;
   &lt;div&gt;
-&lt;p&gt;The &lt;strong&gt;Statistics Output Generator&lt;/strong&gt; is part of &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/download/#overview&#34; title=&#34;MOSAIC Extended&#34;&gt;MOSAIC Extended&lt;/a&gt;&lt;/strong&gt;.&lt;br&gt;
+&lt;p&gt;The &lt;strong&gt;Statistics Output Generator&lt;/strong&gt; is part of &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/download#overview&#34;&gt;MOSAIC Extended&lt;/a&gt;&lt;/strong&gt;.&lt;br&gt;
 For further information on licenses, feel free to contact us via &lt;strong&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;mosaic@fokus.fraunhofer.de&lt;/a&gt;&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
@@ -324,7 +324,7 @@
       <description>&lt;div class=&#34;alert alert-extended&#34;&gt;
   &lt;span class=&#34;extended-icon&#34; style=&#34;background-image: url(/mosaic/img/alert-extended.svg)&#34;&gt;&lt;/span&gt;
   &lt;div&gt;
-&lt;p&gt;&lt;strong&gt;ITEF&lt;/strong&gt; is part of &lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/download/#overview&#34; title=&#34;MOSAIC Extended&#34;&gt;MOSAIC Extended&lt;/a&gt;.&lt;br&gt;
+&lt;p&gt;&lt;strong&gt;ITEF&lt;/strong&gt; is part of &lt;a href=&#34;https://www.eclipse.org/mosaic/download#overview&#34;&gt;MOSAIC Extended&lt;/a&gt;.&lt;br&gt;
 For further information on licenses, feel free to contact us via &lt;strong&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;mosaic@fokus.fraunhofer.de&lt;/a&gt;&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
@@ -447,7 +447,7 @@
       <description>&lt;div class=&#34;alert alert-extended&#34;&gt;
   &lt;span class=&#34;extended-icon&#34; style=&#34;background-image: url(/mosaic/img/alert-extended.svg)&#34;&gt;&lt;/span&gt;
   &lt;div&gt;
-&lt;p&gt;The 3D visualization &lt;strong&gt;PHABMap&lt;/strong&gt; is part of &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/mosaic/download/#overview&#34; title=&#34;MOSAIC Extended&#34;&gt;MOSAIC Extended&lt;/a&gt;&lt;/strong&gt;.&lt;br&gt;
+&lt;p&gt;The 3D visualization &lt;strong&gt;PHABMap&lt;/strong&gt; is part of &lt;strong&gt;&lt;a href=&#34;https://www.eclipse.org/mosaic/download#overview&#34;&gt;MOSAIC Extended&lt;/a&gt;&lt;/strong&gt;.&lt;br&gt;
 For further information on licenses, feel free to contact us via &lt;strong&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;&lt;a href=&#34;mailto:mosaic@fokus.fraunhofer.de&#34;&gt;mosaic@fokus.fraunhofer.de&lt;/a&gt;&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
   &lt;/div&gt;
 &lt;/div&gt;
diff --git a/docs/visualization/itef/index.html b/docs/visualization/itef/index.html
index 8e0e742..102adf6 100644
--- a/docs/visualization/itef/index.html
+++ b/docs/visualization/itef/index.html
@@ -903,6 +903,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -915,6 +919,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1000,7 +1008,7 @@
             <div class="alert alert-extended">
   <span class="extended-icon" style="background-image: url(/mosaic/img/alert-extended.svg)"></span>
   <div>
-<p><strong>ITEF</strong> is part of <a href="/mosaic/download/#overview" title="MOSAIC Extended">MOSAIC Extended</a>.<br>
+<p><strong>ITEF</strong> is part of <a href="/download#overview">MOSAIC Extended</a>.<br>
 For further information on licenses, feel free to contact us via <strong><a href="mailto:mosaic@fokus.fraunhofer.de"><a href="mailto:mosaic@fokus.fraunhofer.de">mosaic@fokus.fraunhofer.de</a></a></strong>.</p>
   </div>
 </div>
diff --git a/docs/visualization/phabmap/index.html b/docs/visualization/phabmap/index.html
index 7e69b11..208933f 100644
--- a/docs/visualization/phabmap/index.html
+++ b/docs/visualization/phabmap/index.html
@@ -903,6 +903,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -915,6 +919,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1000,7 +1008,7 @@
             <div class="alert alert-extended">
   <span class="extended-icon" style="background-image: url(/mosaic/img/alert-extended.svg)"></span>
   <div>
-<p>The 3D visualization <strong>PHABMap</strong> is part of <strong><a href="/mosaic/download/#overview" title="MOSAIC Extended">MOSAIC Extended</a></strong>.<br>
+<p>The 3D visualization <strong>PHABMap</strong> is part of <strong><a href="/download#overview">MOSAIC Extended</a></strong>.<br>
 For further information on licenses, feel free to contact us via <strong><a href="mailto:mosaic@fokus.fraunhofer.de"><a href="mailto:mosaic@fokus.fraunhofer.de">mosaic@fokus.fraunhofer.de</a></a></strong>.</p>
   </div>
 </div>
diff --git a/docs/visualization/statistics/index.html b/docs/visualization/statistics/index.html
index 60d7825..9d9cf52 100644
--- a/docs/visualization/statistics/index.html
+++ b/docs/visualization/statistics/index.html
@@ -903,6 +903,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/scenario_config/">Scenario Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/mapping_ambassador_config/">Mapping Configuration</a>
         </li>
         
@@ -915,6 +919,10 @@
         </li>
         
         <li >
+          <a href="/mosaic/docs/mosaic_configuration/cell_config/">Cell Basic Configuration</a>
+        </li>
+        
+        <li >
           <a href="/mosaic/docs/mosaic_configuration/cell_network_config/">Cell Network Configuration</a>
         </li>
         
@@ -1016,7 +1024,7 @@
             <div class="alert alert-extended">
   <span class="extended-icon" style="background-image: url(/mosaic/img/alert-extended.svg)"></span>
   <div>
-<p>The <strong>Statistics Output Generator</strong> is part of <strong><a href="/mosaic/download/#overview" title="MOSAIC Extended">MOSAIC Extended</a></strong>.<br>
+<p>The <strong>Statistics Output Generator</strong> is part of <strong><a href="/download#overview">MOSAIC Extended</a></strong>.<br>
 For further information on licenses, feel free to contact us via <strong><a href="mailto:mosaic@fokus.fraunhofer.de"><a href="mailto:mosaic@fokus.fraunhofer.de">mosaic@fokus.fraunhofer.de</a></a></strong>.</p>
   </div>
 </div>
diff --git a/download/index.html b/download/index.html
index bca9855..0458683 100644
--- a/download/index.html
+++ b/download/index.html
@@ -817,7 +817,7 @@
     
     
     <div class="title col-md-12 justify-content-center">
-      <div class="col-md-10 section-heading">
+      <div class="col-md-12 section-heading">
         <h1>Versions and Features</h1>
         
       </div>
@@ -881,19 +881,103 @@
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/extending_mosaic/" title="Runtime Infrastructure">Runtime Infrastructure</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/extending_mosaic/">
+    Runtime Infrastructure
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/extending_mosaic/interactions" title="Interactions Library">Interactions Library</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/extending_mosaic/interactions/">
+    Interactions Library
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/tutorials/" title="Tutorials">Tutorials</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/tutorials/">
+    Tutorials
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
@@ -905,55 +989,307 @@
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/application_simulator" title="Application Modelling">Application Modelling</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/application_simulator/">
+    Application Modelling
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/traffic_simulator_sumo" title="Eclipse SUMO">Eclipse SUMO</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/traffic_simulator_sumo/">
+    Eclipse SUMO
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/network_simulator_omnetpp" title="OMNeT&#43;&#43;">OMNeT&#43;&#43;</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_omnetpp/">
+    OMNeT++
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/network_simulator_ns3" title="ns-3">ns-3</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_ns3/">
+    ns-3
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/network_simulator_cell" title="Cellular Communication">Cellular Communication</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_cell/">
+    Cellular Communication
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/network_simulator_sns" title="ITS-G5 Communication">ITS-G5 Communication</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/network_simulator_sns/">
+    ITS-G5 Communication
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/environment_simulator" title="Environment">Environment</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/environment_simulator/">
+    Environment
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/battery_simulator" title="Battery / Charging">Battery / Charging</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/battery_simulator/">
+    Battery / Charging
+</a>
+</strong></td>
 <td style="text-align:center">-</td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/simulators/vms_simulator" title="Variable Message Signs">Variable Message Signs</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/simulators/vms_simulator/">
+    Variable Message Signs
+</a>
+</strong></td>
 <td style="text-align:center">-</td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
@@ -977,31 +1313,171 @@
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/visualization/" title="Browser Visualization">Browser Visualization</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/">
+    Browser Visualization
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/visualization/filevis" title="File Output">File Output</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/filevis/">
+    File Output
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/visualization/statistics" title="Statistics Output">Statistics Output</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/statistics/">
+    Statistics Output
+</a>
+</strong></td>
 <td style="text-align:center">-</td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/visualization/phabmap" title="3D Visualization">3D Visualization</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/phabmap/">
+    3D Visualization
+</a>
+</strong></td>
 <td style="text-align:center">-</td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/visualization/itef" title="ITEF">ITEF</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/visualization/itef/">
+    ITEF
+</a>
+</strong></td>
 <td style="text-align:center">-</td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
@@ -1013,7 +1489,35 @@
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/getting_started/run_mosaic" title="Command Line Tool">Command Line Tool</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/getting_started/run_mosaic/">
+    Command Line Tool
+</a>
+</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
@@ -1025,7 +1529,35 @@
 </tr>
 <tr>
 <td style="text-align:left"></td>
-<td style="text-align:left"><strong><a href="/mosaic/docs/building_scenarios/scenario_convert" title="Scenario Convert">Scenario Convert</a></strong></td>
+<td style="text-align:left"><strong>
+
+
+
+
+
+  
+  
+
+    
+
+    
+    
+      
+      
+      
+      
+    
+
+    
+    
+
+    
+  
+
+<a href="/mosaic/docs/building_scenarios/scenario_convert/">
+    Scenario Convert
+</a>
+</strong></td>
 <td style="text-align:center">(✓)**</td>
 <td style="text-align:center"><strong>✓</strong></td>
 </tr>
diff --git a/index.html b/index.html
index 207d581..aa35fa3 100644
--- a/index.html
+++ b/index.html
@@ -254,7 +254,7 @@
   <meta property="og:description" content=""><meta property="og:image" content="https://www.eclipse.org/mosaic/images/logo.svg">
   <meta property="twitter:image" content="https://www.eclipse.org/mosaic/images/logo.svg"><meta property="og:locale" content="en-us">
   
-    <meta property="og:updated_time" content="2021-01-18T00:00:00&#43;00:00">
+    <meta property="og:updated_time" content="2021-02-26T00:00:00&#43;00:00">
   
 
   
@@ -1970,6 +1970,107 @@
     
     
     
+    <a href="/mosaic/post/remote-operated-driving/" >
+      <img src="/mosaic/post/remote-operated-driving/featured_hua5059d34082940a9059a5f1fddb1ee87_343662_370x0_resize_lanczos_2.png" alt="Testing Remote-Operated Driving virtually with Eclipse MOSAIC">
+    </a>
+    
+  </div>
+  <div class="col-12 d-block d-md-none mb-3">
+    
+    
+    
+    <a href="/mosaic/post/remote-operated-driving/" >
+      <img src="/mosaic/post/remote-operated-driving/featured_hua5059d34082940a9059a5f1fddb1ee87_343662_540x0_resize_lanczos_2.png" alt="Testing Remote-Operated Driving virtually with Eclipse MOSAIC">
+    </a>
+    
+  </div>
+
+  <div class="col-12 col-md-8 mb-3 mb-md-0">
+
+    <h3 class="article-title mb-2 mt-0">
+      <a href="/mosaic/post/remote-operated-driving/" >Testing Remote-Operated Driving virtually with Eclipse MOSAIC</a>
+    </h3>
+
+    
+    <div class="article-style">
+      Remote-Operated Driving is the bridge technology from human towards fully automated driving. In situations outside the driving domain of a highly-automated vehicle, e.g. if data is missing or the autonomous function is unsure to make a certain decision, remote-operation is the key.
+    </div>
+    
+
+    <div class="stream-meta">
+
+      
+
+      
+        
+
+
+<div class="article-metadata">
+
+  
+  
+
+  
+  <span class="article-date">
+    
+    
+      
+    
+    Feb 26, 2021
+  </span>
+  
+
+  
+
+  
+  <span class="middot-divider"></span>
+  <span class="article-reading-time">
+    2 min read
+  </span>
+  
+
+  
+  
+  
+
+  
+  
+
+</div>
+
+      
+    </div>
+
+    
+
+  </div>
+</div>
+
+      
+    
+      
+        
+
+
+
+
+
+
+
+
+
+
+
+
+  
+
+
+
+<div class="row mb-4">
+  <div class="col-4 d-none d-md-block">
+    
+    
+    
     <a href="/mosaic/post/traffic-control/" >
       <img src="/mosaic/post/traffic-control/featured_huc4014d89d7629e7fdbcf07b90b7364d7_254652_370x0_resize_lanczos_2.png" alt="Studying Traffic Control Algorithms in MOSAIC">
     </a>
@@ -2048,107 +2149,6 @@
 
       
     
-      
-        
-
-
-
-
-
-
-
-
-
-
-
-
-  
-
-
-
-<div class="row mb-4">
-  <div class="col-4 d-none d-md-block">
-    
-    
-    
-    <a href="/mosaic/post/release-20-0/" >
-      <img src="/mosaic/post/release-20-0/featured_hu2856af723d2b3e6f45f2d38655ae39d9_95582_370x0_resize_q90_lanczos.jpg" alt="First release of Eclipse MOSAIC">
-    </a>
-    
-  </div>
-  <div class="col-12 d-block d-md-none mb-3">
-    
-    
-    
-    <a href="/mosaic/post/release-20-0/" >
-      <img src="/mosaic/post/release-20-0/featured_hu2856af723d2b3e6f45f2d38655ae39d9_95582_540x0_resize_q90_lanczos.jpg" alt="First release of Eclipse MOSAIC">
-    </a>
-    
-  </div>
-
-  <div class="col-12 col-md-8 mb-3 mb-md-0">
-
-    <h3 class="article-title mb-2 mt-0">
-      <a href="/mosaic/post/release-20-0/" >First release of Eclipse MOSAIC</a>
-    </h3>
-
-    
-    <div class="article-style">
-      The initial contribution is accomplished! With the autumn version, the committer team from Fraunhofer FOKUS and DCAITI is proud to release Eclipse MOSAIC 20.0 to the open source community. With the runtime infrastructure, core libraries and various implementations of simulators or couplings to existing ones, Eclipse MOSAIC includes the essential feature collection for simulation and virtual testing of connected and automated mobility solutions.
-    </div>
-    
-
-    <div class="stream-meta">
-
-      
-
-      
-        
-
-
-<div class="article-metadata">
-
-  
-  
-
-  
-  <span class="article-date">
-    
-    
-      
-    
-    Oct 19, 2020
-  </span>
-  
-
-  
-
-  
-  <span class="middot-divider"></span>
-  <span class="article-reading-time">
-    1 min read
-  </span>
-  
-
-  
-  
-  
-
-  
-  
-
-</div>
-
-      
-    </div>
-
-    
-
-  </div>
-</div>
-
-      
-    
 
     
     <div class="see-all">
@@ -2241,7 +2241,7 @@
   </div>
 
   <div class="text col-12 col-md-9">
-    <a href="https://fokus.fraunhofer.de/en">Fraunhofer FOKUS</a> and <a href="https://www.dcaiti.tu-berlin.de/">DCAITI (Daimler Center for Automotive IT
+    <a href="https://www.fokus.fraunhofer.de/asct">Fraunhofer FOKUS</a> and <a href="https://www.dcaiti.tu-berlin.de/">DCAITI (Daimler Center for Automotive IT
 Innovations)</a> developed this simulation platform, formerly known as VSimRTI,
 to support research in the field of connected and automated mobility for more than 12 years.
   </div>
diff --git a/index.json b/index.json
index e40cb60..0facba8 100644
--- a/index.json
+++ b/index.json
@@ -1 +1 @@
-[{"authors":["fokus"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"cbf22d51976246e8f80b5f6a1df3bf83","permalink":"https://www.eclipse.org/mosaic/author/fraunhofer-fokus/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mosaic/author/fraunhofer-fokus/","section":"authors","summary":"","tags":null,"title":"Fraunhofer FOKUS","type":"authors"},{"authors":null,"categories":null,"content":"Applications in Eclipse MOSAIC are simulated by the Application Simulator. Such an application is programmed in Java and follows an event-based execution flow. Thereby, certain methods of the application are called by the Application Simulator upon corresponding events (the application \u0026ldquo;reacts\u0026rdquo;). To actively gain execution at some later point in time, an application can also schedule a generic event itself. When the application is executing, it has access to a set of methods, allowing to trigger actions like sensing messages or controlling the vehicle, influencing the current simulation (the application \u0026ldquo;acts\u0026rdquo;).\nDeveloping Applications Developing custom applications in Eclipse MOSAIC is rather easy. The best way to learn it is by looking at the source code of actual applications. For this purpose, we provide the source code of all tutorial applications and further examples.\nFor an easy understanding of the application API, the following questions and their answers should help:\n  What is required to get my own application to run in Eclipse MOSAIC? In Eclipse MOSAIC it is very easy to build your own application. First, it needs to inherit from the AbstractApplication class (see following section). Secondly, the application must be mapped to a vehicle (or RSU, or traffic light, \u0026hellip;) via the mapping configuration (see section mapping). Finally, the application must be compiled as a Jar-File and placed into the application directory of your scenario.\n  How can I access vehicle functions from within the application, such as sending V2X messages? Every applications has access to the OperatingSystem of the underlying unit which allows to change its state or to initiate actions, such as sending messages to other vehicles.\n  How can I react to events during the simulation, such as receiving V2X messages? For each application you decide, which events the application should listen to. For example, if your application needs to react upon incoming V2X messages, it simply implements the CommunicationApplication interface. In the following section you can find all available interfaces applications can implement.\n  Create a ’Hello world’ application based on Maven For this example you need to install Maven which is used to resolve required MOSAIC dependencies and to compile your application Java code into a Jar file. Follow the steps to build an example application:\n Create a new folder HelloWorldApp: └─ HelloWorldApp ├─ src | └─ main | └─ java | └─ HelloWorldApp.java └─ pom.xml   Place a pom.xml with the following content: \u0026lt;?xml version=\u0026quot;1.0\u0026quot; encoding=\u0026quot;UTF-8\u0026quot;?\u0026gt; \u0026lt;project xmlns=\u0026quot;http://maven.apache.org/POM/4.0.0\u0026quot; xmlns:xsi=\u0026quot;http://www.w3.org/2001/XMLSchema-instance\u0026quot; xsi:schemaLocation=\u0026quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd\u0026quot;\u0026gt; \u0026lt;modelVersion\u0026gt;4.0.0\u0026lt;/modelVersion\u0026gt; \u0026lt;groupId\u0026gt;org.eclipse.mosaic.app\u0026lt;/groupId\u0026gt; \u0026lt;artifactId\u0026gt;HelloWorldApp\u0026lt;/artifactId\u0026gt; \u0026lt;version\u0026gt;0.0.1\u0026lt;/version\u0026gt; \u0026lt;packaging\u0026gt;jar\u0026lt;/packaging\u0026gt; \u0026lt;dependencies\u0026gt; \u0026lt;dependency\u0026gt; \u0026lt;groupId\u0026gt;org.eclipse.mosaic\u0026lt;/groupId\u0026gt; \u0026lt;artifactId\u0026gt;mosaic-application\u0026lt;/artifactId\u0026gt; \u0026lt;version\u0026gt;20.0\u0026lt;/version\u0026gt; \u0026lt;/dependency\u0026gt; \u0026lt;/dependencies\u0026gt; \u0026lt;/project\u0026gt;   Create a new application in src/main/java/HelloWorldApp.java: import org.eclipse.mosaic.fed.application.app.AbstractApplication; import org.eclipse.mosaic.fed.application.app.api.VehicleApplication; import org.eclipse.mosaic.fed.application.app.api.os.VehicleOperatingSystem; import org.eclipse.mosaic.lib.objects.vehicle.VehicleData; import org.eclipse.mosaic.lib.util.scheduling.Event; public class HelloWorldApp extends AbstractApplication\u0026lt;VehicleOperatingSystem\u0026gt; implements VehicleApplication { @Override public void onStartup() { getLog().info(\u0026quot;Hello World!\u0026quot;); } @Override public void onVehicleUpdated(VehicleData previousVehicleData, VehicleData updatedVehicleData) { getLog().info(\u0026quot;Driving {} m/s.\u0026quot;, updatedVehicleData.getSpeed()); } @Override public void onShutdown() { getLog().info(\u0026quot;Good bye!\u0026quot;); } @Override public void processEvent(Event event) { // ... } }   Build the application using maven: mvn clean install   Copy the JAR file from target/HelloWorldApp-0.0.1.jar to the application directory of your simulation scenario. Use the fully qualified name HelloWorldApp in the mapping_config.json to load the application onto vehicles.  Application Interfaces You may have noticed that the HellowWorldApp extends from the class [...].AbstractApplication\u0026lt;OS\u0026gt;. In order to define the type of unit your application can run on, you need to speficy the operating system by choosing one of the following:\n VehicleOperatingSystem - for applications mapped to normal vehicles. ElectricVehicleOperatingSystem - for applications for vehicles with electro mobility features. RoadSideUnitOperatingSystem - for applications mapped to RSUs. TrafficLightOperatingSystem - for applications mapped to traffic lights. TrafficManagementCenterOperatingSystem - for applications mapped to TMCs. ChargingStationOperatingSystem - for applications mapped to charging stations.  See package: org.eclipse.mosaic.fed.application.app.api.os.*\nFurthermore, your application can implement the following 7 interfaces in order to get informed on specific events:\n VehicleApplication - get informed when information about the vehicles state is updated. ElectricVehicleApplication - get informed on electric vehicle specific events. CommunicationApplication - react on incoming V2X messages. MosaicApplication - get informed on Eclipse MOSAIC internal events. TrafficLightApplication - get noticed when the traffic light program is changed. ChargingStationApplication - react on state changes of the charging station. TrafficManagementCenterApplication - get informed on state changes of road infrastructure.  See package: org.eclipse.mosaic.fed.application.app.api.*\n Basic Functions and Concepts for Applications The following section describes how applications are implemented.\nEvent hooks Applications are implemented by reacting to specific events. Those events are, amongst others:\n The simulation has started: All static units (e.g. road side units) are set up (onStartup() is called) Once a vehicle has been added to the simulation, all its configured applications are initialized (onStartup() is called) The data of the vehicle has changed, e.g. after the traffic simulator has finished one simulationstep (onVehicleUpdated() is called). A unit has received a V2X message from another entity (onMessageReceived is called). A unit which has send a V2X message via a ITS-G5 topocast receives an acknowledgement (onAcknowledgementReceived() is called).  Another example:\n#mermaid-1603209753374{font-family:\"trebuchet ms\",verdana,arial;font-size:16px;fill:#333;}#mermaid-1603209753374 .error-icon{fill:#552222;}#mermaid-1603209753374 .error-text{fill:#552222;stroke:#552222;}#mermaid-1603209753374 .edge-thickness-normal{stroke-width:2px;}#mermaid-1603209753374 .edge-thickness-thick{stroke-width:3.5px;}#mermaid-1603209753374 .edge-pattern-solid{stroke-dasharray:0;}#mermaid-1603209753374 .edge-pattern-dashed{stroke-dasharray:3;}#mermaid-1603209753374 .edge-pattern-dotted{stroke-dasharray:2;}#mermaid-1603209753374 .marker{fill:#333333;}#mermaid-1603209753374 .marker.cross{stroke:#333333;}#mermaid-1603209753374 svg{font-family:\"trebuchet ms\",verdana,arial;font-size:16px;}#mermaid-1603209753374 .actor{stroke:hsl(259.6261682243,59.7765363128%,87.9019607843%);fill:#ECECFF;}#mermaid-1603209753374 text.actor \u0026gt; tspan{fill:black;stroke:none;}#mermaid-1603209753374 .actor-line{stroke:grey;}#mermaid-1603209753374 .messageLine0{stroke-width:1.5;stroke-dasharray:none;stroke:#333;}#mermaid-1603209753374 .messageLine1{stroke-width:1.5;stroke-dasharray:2,2;stroke:#333;}#mermaid-1603209753374 #arrowhead path{fill:#333;stroke:#333;}#mermaid-1603209753374 .sequenceNumber{fill:white;}#mermaid-1603209753374 #sequencenumber{fill:#333;}#mermaid-1603209753374 #crosshead path{fill:#333;stroke:#333;}#mermaid-1603209753374 .messageText{fill:#333;stroke:#333;}#mermaid-1603209753374 .labelBox{stroke:hsl(259.6261682243,59.7765363128%,87.9019607843%);fill:#ECECFF;}#mermaid-1603209753374 .labelText,#mermaid-1603209753374 .labelText \u0026gt; tspan{fill:black;stroke:none;}#mermaid-1603209753374 .loopText,#mermaid-1603209753374 .loopText \u0026gt; tspan{fill:black;stroke:none;}#mermaid-1603209753374 .loopLine{stroke-width:2px;stroke-dasharray:2,2;stroke:hsl(259.6261682243,59.7765363128%,87.9019607843%);fill:hsl(259.6261682243,59.7765363128%,87.9019607843%);}#mermaid-1603209753374 .note{stroke:#aaaa33;fill:#fff5ad;}#mermaid-1603209753374 .noteText,#mermaid-1603209753374 .noteText \u0026gt; tspan{fill:black;stroke:none;}#mermaid-1603209753374 .activation0{fill:#f4f4f4;stroke:#666;}#mermaid-1603209753374 .activation1{fill:#f4f4f4;stroke:#666;}#mermaid-1603209753374 .activation2{fill:#f4f4f4;stroke:#666;}#mermaid-1603209753374:root{--mermaid-font-family:\"trebuchet ms\",verdana,arial;}#mermaid-1603209753374 sequence{fill:apa;}RTIApplicationSimulatorApplication1Application2VehicleRegistrationonStartup()onStartup()VehicleUpdatesonVehicleUpdated()onVehicleUpdated()VehicleUpdatesonVehicleUpdated()onVehicleUpdated()sendV2xMessage()V2xMessageTransmissionV2xMessageReceiptiononMessageReceived()VehicleUpdates (remove)onShutdown()onShutdown()RTIApplicationSimulatorApplication1Application2   Example sequence of onStartup, onUpdate, onMessageReceived and onShutdown of two applications.\nA onStartup() method, which enables the ITS-G5 communication module of the unit, could be implemented the following:\n@Override public void onStartup() { getOs().getAdHocModule().enable(new AdHocModuleConfiguration() .addRadio().channel(AdHocChannel.CCH).power(50).create() ); }  A onMessageReceived() method, which reacts upon a DENM message, could be implemented as:\n@Override public void onMessageReceived(ReceivedV2xMessage receivedV2xMessage) { final V2xMessage msg = receivedV2xMessage.getMessage(); if (msg instanceof Denm) { Denm denm = (Denm)msg; GeoPoint eventLocation = denm.getEventLocation(); //TODO you can add further implementation here } }  Trigger own Events It is possible to trigger own events at specific times within the application. For this purpose, the application has access to an own event manager. Each event requires a simulation timestamp when it should be called, and an event processor.\nThe following code triggers an event in 10 seconds after the application has been initialied:\n@Override public void onStartup() { Event event = new Event(getOs().getSimulationTime() + 10 * TIME.SECOND, this); getOs().getEventManager().addEvent(event); } @Override public void processEvent(Event event) { getLog().info(\u0026quot;Event has been triggered\u0026quot;); // TODO }  To address a specific method to process the event, Java lambda expressions could be used:\n@Override public void onStartup() { Event event = new Event(getOs().getSimulationTime() + 10 * TIME.SECOND, this::mySpecificMethod); getOs().getEventManager().addEvent(event); } public void mySpecificMethod(Event event) { getLog().info(\u0026quot;Event has been triggered\u0026quot;); // TODO }  Using the Operating System Each application has access to the operating system of its unit. Depending on the type of unit, the operating system provides different methods. For example, an application which is mapped on vehicles, has access to the VehicleOperatingSystem by calling this.getOperatingSystem() (or this.getOs() to keep it short). The following examples show a bit of the capabilities the VehicleOperatingSystem provides:\nGet the current simulation time (in nanoseconds):\nlong time = this.getOs().getSimulationTime();  Return the name of the unit (e.g. \u0026ldquo;veh_0\u0026rdquo;):\nString nameOfUnit = this.getOs().getId();  Get access to vehicle data, such as speed, position, heading, and the like:\ndouble speed = this.getOs().getVehicleData().getSpeed(); GeoPoint position = this.getOs().getVehicleData().getPosition();  Change parameters of the vehicle during the simulation, such as its maximum speed:\nthis.getOs().requestVehicleParametersUpdate() .changeMaxSpeed(10) // m/s .changeMaxAcceleration(2.4) .apply();  Get the current lane index of the vehicle and change lane to left (within 5000 ms):\nint laneIndex = this.getOs().getRoadPosition().getLaneIndex(); int newLaneIndex = Math.max(0, laneIndex - 1); this.getOs().changeLane(newLaneIndex, 5000);  Sending a V2X message via ITS-G5 singlehop broadcast:\nMessageRouting routing = this.getOs().getAdHocModule().createMessageRouting().topoBroadCast(); V2xMessage message = new MyV2xMessage(routing); this.getOs().getAdHocModule().sendV2xMessage(message);  Park the vehicle in 200 meters at the right side of the road for 3 minutes:\ndouble distance = 200; double duration = 3 * 60 * 1000; IRoadPosition stopPosition = RoadPositionFactory.createAlongRoute( getOs().getNavigationModule().getRoadPosition(), getOs().getNavigationModule().getCurrentRoute(), 0, distance ); this.getOs().stop(distance, duration, Stop.StopMode.PARK);  Navigation The navigation of vehicles (i.e. calculation of routes) is handled completely by the Application Simulator. Each vehicle is equipped with a navigation system which provides all required information and functions for navigational purposes:\n Retrieve the current position and heading of the vehicle. Get the target of the vehicle. Calculate various routes from the current position to an arbitrary target. Choose a suitable route out of existing ones from the current position to an arbitrary target. Switch onto a specific route.  In order to provide routing functionality, a map model based on Open Street Map data is used, which needs to be transformed before the simulation using scenario-convert. The map data including initial routes for vehicles is provided with the database file which needs to be located in mosaic/scenarios/\u0026lt;scenario_name\u0026gt;/application/\u0026lt;scenario_name\u0026gt;.db\nConfiguration If the database needs to be located somewhere else, the path can be specified in mosaic/scenarios/\u0026lt;scenario_name\u0026gt;/application/application_config.json:\n{ ... \u0026quot;navigationConfiguration\u0026quot;: { \u0026quot;databaseFile\u0026quot;: \u0026quot;path/to/scenario.db\u0026quot; } }  The following snippet show, how the navigation system can be used within an application:\n//get navigation module INavigationModule navigationModule = getOs().getNavigationModule(); //choose current target as target position RoutingPosition targetPosition = new RoutingPosition(navigationModule.getTargetPosition()); //set routing parameters to fastest route search RoutingParameters params = new RoutingParameters().costFunction(IRoutingCostFunction.Fastest); //calculate routes RoutingResponse response = navigationModule.calculateRoutes(targetPosition, params); //switch to best route if (response.getBestRoute() != null) { boolean routeSwitched = navigationModule.switchRoute(response.getBestRoute()); ... }  Access SUMO TraCI from applications If SUMO is used as a traffic simulator and a special functionality is required, the sendSumoTraciRequest function in the OperatingSystem can be used.\nThe function expects a string (a unique identifier which will be assigned to the response) and a byte array (representing the complete Traffic Control Interface (TraCI) request including the header). The message identifier can be an empty string.\nIn all cases the command will trigger a response. The application can receive the response from the method onSumoTraciResult. This method will receive a SumoTraciResult object. This response contains the specified identifier. The application must handle the identification process of the response itself.\n Be careful when using this interface and the TraCI commands. The commands are delivered to TraCI without any prior checks.\n   You can find the example application SumoTraciInteractionApp in the additional examples bundle on the DCAITI website.\n   Debugging of applications To debug an application, remote debugging needs to be used. The following steps need to be performed in order to debug the application:\n Open the application in your IDE. Modify your mosaic.sh or mosaic.bat by adding debug parameters to the java call:\njava -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=4100 ... Add a new debug profile in your IDE for remote debugging. Make sure to correctly configure port 4100 (or whichever port you provided in step 2). Launch Eclipse MOSAIC with the argument -w 0 to disable the watchdog timer otherwise it will interfere with debugging. Connect your debugger in your IDE with the running simulation.  ","date":1565049600,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1565049600,"objectID":"f3e4e878d3a3df21f512128da34ee9b3","permalink":"https://www.eclipse.org/mosaic/docs/develop_applications/","publishdate":"2019-08-06T00:00:00Z","relpermalink":"/mosaic/docs/develop_applications/","section":"docs","summary":"Applications in Eclipse MOSAIC are simulated by the Application Simulator. Such an application is programmed in Java and follows an event-based execution flow. Thereby, certain methods of the application are called by the Application Simulator upon corresponding events (the application \u0026ldquo;reacts\u0026rdquo;).","tags":null,"title":"Basics in Application Development","type":"docs"},{"authors":null,"categories":null,"content":" ","date":1593471600,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1593471600,"objectID":"73996a350495164dd7fb2b4e81c403df","permalink":"https://www.eclipse.org/mosaic/docs/api_docs/","publishdate":"2020-06-30T00:00:00+01:00","relpermalink":"/mosaic/docs/api_docs/","section":"docs","summary":" ","tags":null,"title":"Javadoc of Eclipse MOSAIC source code","type":"docs"},{"authors":null,"categories":null,"content":"To run a simulation, a federation of simulators has to be created. This federation consists of one federate for each participating simulator. In the upper part of Figure 1, the inner structure of a federate is illustrated. It consists of the original simulator that is connected to its federate ambassador and an instance of an Eclipse MOSAIC ambassador. The federates run on top of the Eclipse MOSAIC Runtime Infrastructure (lower part of Figure 1) which offers services for federation-, interaction- and time management. The communication between the federates and the runtime infrastructure is enabled by ambassadors. More precisely, a federate that wants to access services of the RTI can use a designated RTI-Ambassador that provides access to the provided services. In the opposite direction, i.e. if the runtime infrastructure wants to invoke operations on the federate implementation, a federate ambassador is used. Each federate ambassador implements the same interface that is used by Eclipse MOSAIC to control the simulator and to provide interactions from other federates.\n Schematic illustration of Eclipse MOSAIC Runtime Infrastructure    Time Management The main problem in executing a federation is the synchronization of its federates. Each federate is a discrete-event simulator with an ordered event list from which sequentially the first event is processed. Consequently, the Time Management is necessary for coordinating the simulation and synchronizing participating federates. It assures that each federate processes its events in correct order.\nAccording to Fujimoto the time management in a federated environment includes two key components: Interaction (Message) order and time stamps. Note that we usually use the word \u0026lsquo;intercation\u0026rsquo; when talking about communication between federates, \u0026lsquo;message\u0026rsquo; will be used in the context of (V2X)-communication.\nThe Interaction Order service is completely implemented in Eclipse MOSAIC with the following design rationale: Each request of a federate to execute a local event is mapped to a global event within the Time management. Such an event consists of three attributes: simulation time, priority, and lookahead time. The simulation time defines the time in the simulation at which the event has to be processed. The priority allows defining an order of events that are scheduled at the same time. The third attribute, the lookahead time, describes an idle period following after an event. It is used to signalize that no further event will be scheduled and no interaction will be sent within this period. All events are scheduled by storing them in an event list in ascending order according to their simulation time. In case of equal simulation times, they are ordered in descending order to their priority. A time management cycle consists of three steps.\n  The federate invokes a time management service to request its logical time to advance. While Time Advance Request (TAR) is more suitable for time-stepped simulators, Next Event Request (NER) is the preferred primitive for event-driven federates.\n  The RTI delivers certain interactions to the federate. Each federate receives the interactions in the processInteraction() method.\n  The RTI completes the cycle by invoking a federate defined procedure called Time Advance Grant to indicate the federate’s logical time has been advanced. Eclipse MOSAIC supports the sequential and the parallel conservative mechanism for advancing time.\n   Interaction Management The exchange of data among federates is offered by the Interaction Management using interactions. Eclipse MOSAIC and its federates are decoupled through a publish-subscribe paradigm provided by the Interaction Management. A published interaction is forwarded to each subscriber directly after it has been published. However, a receiving federate is not allowed to advance its time based on an interaction but must request a time advancement if necessary. An interaction consists of its creation time, an identifier describing its type, and optional data. Interactions to exchange traffic, network, vehicle, and sensor data are predefined. These interactions are used to define a standardized communication behaviour.\nSubscribe Interaction Before a federate can receive interactions, it has to subscribe to them. The Interaction Management offers two different ways to subscribe to certain interactions. A federate can either define a interaction type only to receive all interactions of this type or, additionally, define conditions to filter interactions by their content. If a federate is not longer interested in subscribed interactions, it can rescind its interest.\nPublish Interaction Each federate is allowed to publish any interaction at any valid time of the simulation. After a interaction is published, the Interaction Management forwards the interaction to each federate that has subscribed to this type of interaction. A federate receiving a interaction can ignore it or request to advance its local time to handle this interaction.\n Federation Management The Federation Management is responsible for the administration of participating federates. This includes deploying, starting, stopping, and undeploying federates in a distributed system. Before running a simulation, the Federation Management creates an empty federation. After that, federates join the federation. Already joined federates can be removed from a federation, if they are not necessary for the rest of the simulation. After a simulation is finished, the Federation Management frees used resources.\nCreate Federation Creates an empty federation. After a federation is created, it is possible to join federates.\nJoin Federation A joining simulator is defined by a unique name and a FederateHandle. This handle contains the information whether start-up and deployment of the simulator are required to be handled by the Federation Management. In this case, further deployment and start-up information are included.\nStop Federation After a simulation is finished, all joined federates are resigned and their used resources are freed. All references are removed and necessary tasks to stop and undeploy the federate are executed.\nImplementation Details When a simulator is about to join a federation, a FederateHandle is passed to the Federation Manage- ment. A handle includes a Federate Ambassador that is responsible for all communication with the RTI as well as all identifiers for interactions it wants to subscribe to. Additionally, it contains two flags indicating how the simulator is started and if the simulator needs to be deployed by the Federation Management. For the deployment, the handle consists a reference to the directory including all binaries and host parameters consisting of an address and a directory in which the simulator shall be deployed. To start a simulator a start-command is included.\nIf the simulator is running, its ambassador is registered for coordinating the simulator during the sim- ulation run. Afterwards, the Federation Management initiates the subscription to interactions on behalf of an ambassador. Otherwise, before the ambassador is registered, the Federation Management starts and, if necessary, deploys the simulator on a local or a remote machine and connects it to its ambassador. The connection is created by redirecting the output of the started simulator to its ambassador. Based on the incoming data, the Federate Ambassador is responsible for configuring its communication with the simulator.\nLocal Federation Management In case a simulator is to be deployed on a local machine, its binaries are copied into the simulation directory that is defined within the host parameters. Afterwards, using the start-command the simulator is started in a new process and its output is redirected to the ambassador. Additionally, a mapping between ambassador and process reference is stored. Finally, when the federate is resigned, the ambassador is called to shut down its corresponding simulator. Finally, the mapped process is killed and all copied files are removed.\nDistributed Federation Management To administrate simulators on remote hosts, the Federation Management uses the Secure Shell (SSH) protocol to send commands and the associated Secure File Transfer Protocol (SFTP) to transfer binaries. After a process is started remotely, a mapping between ambassador, its process id, and the host on which is running are stored. Finally, when the federate is resigned, the remotely running process is killed and all binaries are removed.\n","date":1565049600,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1565049600,"objectID":"1c65951f20f713cdbe7d5eea3c44701f","permalink":"https://www.eclipse.org/mosaic/docs/extending_mosaic/","publishdate":"2019-08-06T00:00:00Z","relpermalink":"/mosaic/docs/extending_mosaic/","section":"docs","summary":"To run a simulation, a federation of simulators has to be created. This federation consists of one federate for each participating simulator. In the upper part of Figure 1, the inner structure of a federate is illustrated.","tags":null,"title":"Core Concepts","type":"docs"},{"authors":null,"categories":null,"content":"On the following pages we provide a complete documentation of configuration files:\n   Simulator/Ambassador Configuration File Documentation     Mapping mapping/mapping_config.json \u0026gt; Mapping Configuration   Environment environment/environment_config.json \u0026gt; Environment Simulator Configuration   Simple Network Simulator sns/sns_config.json \u0026gt; SNS Configuration   Cell cell/regions.json \u0026gt; Regions configuration   Cell cell/network.json \u0026gt; Network configuration   SUMO sumo/sumo_config.json \u0026gt; SUMO Ambassador Configuration    Readable Units Our configuration files accept readable units for some fields. If a field or attribute can be filled with values of type number or string (e.g. the maxSpeed of a vehicle in the Mapping configuration), you can write a number which then will be interpreted as the type as described in the documentation. Besides, you are able to input a readable text like e.g. \u0026quot;10 km\u0026quot; or \u0026quot;35 mph\u0026quot; which than will be converted automatically to the default unit. Following, you find a few examples:\n table { width: auto; min-width: 65%; }      String Input Number Input Default Unit     Distance       \u0026quot;10 km\u0026quot; 10000.0 m    \u0026quot;10 cm\u0026quot; 0.1 m    \u0026quot;0.5m\u0026quot; 0.5 m    \u0026quot;1 meter\u0026quot; 1.0 m   Speed       \u0026quot;10 km/h\u0026quot; 2.77 m/s    \u0026quot;10 m/s\u0026quot; 10.0 m/s    \u0026quot;35 mph\u0026quot; 15.6464 m/s   Time       \u0026quot;10 ms\u0026quot; 10_000_000 ns    \u0026quot;20 ns\u0026quot; 20 ns    \u0026quot;0.5h\u0026quot; 1_800_000_000_000 ns    \u0026quot;0.5 hours\u0026quot; 1_800_000_000_000 ns     The dashes _ in e.g. 1_800_000_000_000 are only used for better readability in this documentation.\n  ","date":1557010800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1557010800,"objectID":"2ca6385333935d934f7fedd14cf2c1c6","permalink":"https://www.eclipse.org/mosaic/docs/mosaic_configuration/","publishdate":"2019-05-05T00:00:00+01:00","relpermalink":"/mosaic/docs/mosaic_configuration/","section":"docs","summary":"On the following pages we provide a complete documentation of configuration files:\n   Simulator/Ambassador Configuration File Documentation     Mapping mapping/mapping_config.json \u0026gt; Mapping Configuration   Environment environment/environment_config.","tags":null,"title":"Eclipse MOSAIC Configuration Files","type":"docs"},{"authors":null,"categories":null,"content":"Download Eclipse MOSAIC from DCAITI mirror   Download the eclipse-mosaic-20.0.zip bundle from the mirror above. Extract the package to an arbitrary path. This installation path is referenced as \u0026lt;mosaic-root\u0026gt; throughout the entire document. Install additional software required by the simulation (see below), e.g. Eclipse SUMO  Folder Content └─ \u0026lt;mosaic-root\u0026gt; ├─ etc | ├─ hosts.json .................. Configuration of the execution host, e.g. temporary directory. | ├─ logback.xml ................. Configuration of log files and levels. | └─ runtime.json ................ Configuration of all Ambassadors and Federates coupled with the MOSAIC ├─ lib ............................. Directory with all Java compiled libraries required for MOSAIC. ├─ logs ............................ Directory with log files. ├─ scenarios ....................... Directory containing all simulation scenarios. ├─ tools ........................... Additional tools, like the HTML Visualizer. ├─ CONTRIBUTING.md ├─ LICENSE ├─ mosaic.bat ...................... Start script for Windows systems. └─ mosaic.sh ....................... Start script for GNU/Linux systems.  Additional Software Each simulation with Eclipse MOSAIC requires additional software. As MOSAIC is written in JAVA, first of all, a JAVA runtime environment (JRE) needs to be installed for your operating system. Furthermore, each simulation requires additional simulators to be installed, for example the traffic simulation tool Eclipse SUMO or the communication simulators OMNeT++ / INET or ns-3.\nThe following table gives an overview of supported environments and simulators. Please make sure that you install those versions only.\n   Component Required  Version       Java yes 7 and below not supported 8  supported 11 and above  limited supported           Eclipse SUMO yes* 0.32.0 and below not supported 1.0.1 - 1.8.0  supported above 1.8.0  not tested    OMNeT++ optional below 5.5 not supported 5.5  supported 5.6 and above  not supported    INET optional below 4.1 not supported 4.1  supported 4.2 and above  not supported    ns-3 optional below 3.28 not supported 3.28  supported above 3.28  not tested    * All provided scenarios require SUMO to be installed. However, if a different traffic or vehicle simulator is coupled, SUMO is not certainly required.\nUpdate Eclipse MOSAIC In order to update Eclipse MOSAIC to a new version, please perform the following steps manually:\n Backup your personal simulation scenarios from MOSAIC\u0026rsquo;s scenarios directory. Remove your old MOSAIC installation completely. Install MOSAIC by extracting the current binary archive from above. Copy your simulation scenarios back to MOSAIC\u0026rsquo;s scenarios directory. Take care of possible updates of the used software and simulators from third party (see the Compatibility Matrix above).  ","date":1557010800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1557010800,"objectID":"0d7696d24c78e212b3f7477df55bfbb6","permalink":"https://www.eclipse.org/mosaic/docs/getting_started/","publishdate":"2019-05-05T00:00:00+01:00","relpermalink":"/mosaic/docs/getting_started/","section":"docs","summary":"Download Eclipse MOSAIC from DCAITI mirror   Download the eclipse-mosaic-20.0.zip bundle from the mirror above. Extract the package to an arbitrary path. This installation path is referenced as \u0026lt;mosaic-root\u0026gt; throughout the entire document.","tags":null,"title":"Download Eclipse MOSAIC","type":"docs"},{"authors":null,"categories":null,"content":"The runtime infrastructure of Eclipse MOSAIC couples different simulators and can\u0026rsquo;t be run alone and, therefore, it requires pre-installed simulators. Each simulator coupled with the RTI of MOSAIC usually covers a specific domain (e.g. traffic, communication, application, electricity, or other).\nEach of the simulators must implement an interface, the so-called Ambassador. The ambassador communicates with the actual simulator, which is represented by the Federate. For some cases, if the simulator is directly coupled with the RTI (e.g. Application, or cell), the ambassador also represents the federate. This architecture allows a simple coupling of own simulators.\n#mermaid-1603209753374{font-family:\"trebuchet ms\",verdana,arial;font-size:16px;fill:#333;}#mermaid-1603209753374 .error-icon{fill:#552222;}#mermaid-1603209753374 .error-text{fill:#552222;stroke:#552222;}#mermaid-1603209753374 .edge-thickness-normal{stroke-width:2px;}#mermaid-1603209753374 .edge-thickness-thick{stroke-width:3.5px;}#mermaid-1603209753374 .edge-pattern-solid{stroke-dasharray:0;}#mermaid-1603209753374 .edge-pattern-dashed{stroke-dasharray:3;}#mermaid-1603209753374 .edge-pattern-dotted{stroke-dasharray:2;}#mermaid-1603209753374 .marker{fill:#333333;}#mermaid-1603209753374 .marker.cross{stroke:#333333;}#mermaid-1603209753374 svg{font-family:\"trebuchet ms\",verdana,arial;font-size:16px;}#mermaid-1603209753374 .label{font-family:\"trebuchet ms\",verdana,arial;color:#333;}#mermaid-1603209753374 .label text{fill:#333;}#mermaid-1603209753374 .node rect,#mermaid-1603209753374 .node circle,#mermaid-1603209753374 .node ellipse,#mermaid-1603209753374 .node polygon,#mermaid-1603209753374 .node path{fill:#ECECFF;stroke:#9370DB;stroke-width:1px;}#mermaid-1603209753374 .node .label{text-align:center;}#mermaid-1603209753374 .node.clickable{cursor:pointer;}#mermaid-1603209753374 .arrowheadPath{fill:#333333;}#mermaid-1603209753374 .edgePath .path{stroke:#333333;stroke-width:1.5px;}#mermaid-1603209753374 .flowchart-link{stroke:#333333;fill:none;}#mermaid-1603209753374 .edgeLabel{background-color:#e8e8e8;text-align:center;}#mermaid-1603209753374 .edgeLabel rect{opacity:0.5;background-color:#e8e8e8;fill:#e8e8e8;}#mermaid-1603209753374 .cluster rect{fill:#ffffde;stroke:#aaaa33;stroke-width:1px;}#mermaid-1603209753374 .cluster text{fill:#333;}#mermaid-1603209753374 div.mermaidTooltip{position:absolute;text-align:center;max-width:200px;padding:2px;font-family:\"trebuchet ms\",verdana,arial;font-size:12px;background:hsl(80,100%,96.2745098039%);border:1px solid #aaaa33;border-radius:2px;pointer-events:none;z-index:100;}#mermaid-1603209753374:root{--mermaid-font-family:\"trebuchet ms\",verdana,arial;}#mermaid-1603209753374 flowchart{fill:apa;}TraCIProtobufEclipse MOSAIC RTIEclipse SUMOOMNeT++ApplicationAmbassadorSumoAmbassadorOmnetppAmbassador   The following simulators are coupled already with MOSAIC:\n table th:first-of-type { width: 26%; }     Domain Simulator Name Description     Application Simulation MOSAIC Application Application prototyping and simulation.        Traffic / Vehicle Simulation Eclipse SUMO Microscopic Traffic simulation.    PHABMACS Sub-microscopic vehicle simulation with 3D visualization. Documentation will be published soon.        Network / Communication Simulation OMNeT\u0026#43;\u0026#43; Event-based network simulator for ITS-G5 and cellular communication.    ns-3 Event-based network simulator for ITS-G5 and cellular communication.    MOSAIC Simple Network Simulator Simulator for ITS-G5 ad-hoc communication using simplified models.    MOSAIC Cell Simulator for cellular communication.        Environment Simulation MOSAIC Environment Environmental event simulation.        E-Mobility Simulation MOSAIC Battery Electric vehicle simulation.    ","date":1557010800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1557010800,"objectID":"7998013f795ff6ddbb68d3d1e213effe","permalink":"https://www.eclipse.org/mosaic/docs/simulators/","publishdate":"2019-05-05T00:00:00+01:00","relpermalink":"/mosaic/docs/simulators/","section":"docs","summary":"The runtime infrastructure of Eclipse MOSAIC couples different simulators and can\u0026rsquo;t be run alone and, therefore, it requires pre-installed simulators. Each simulator coupled with the RTI of MOSAIC usually covers a specific domain (e.","tags":null,"title":"Simulators Overview","type":"docs"},{"authors":null,"categories":null,"content":"This section provides information on creating own simulation scenarios. A scenario is generally a folder structure that reflects the different components usually found in a simulation. Each of the folders contains various configuration files which in total describe the simulation setup, including the movements of the vehicles, the definition of the road network, communication properties, and the like.\nThe following file structure shows the minimum setup of a typical simulation scenario in Eclipse MOSAIC:\n└─ \u0026lt;scenarioName\u0026gt; ├─ application | └─ \u0026lt;scenarioName\u0026gt;.db................ Scenario database file ├─ mapping | └─ mapping_config.json ............. Mapping configuration file ├─ sumo | └─ \u0026lt;scenarioName\u0026gt;.net.xml .......... SUMO network file | └─ \u0026lt;scenarioName\u0026gt;.sumocfg .......... SUMO configuration file └─ scenario_config.json ............... Basic configuration of the simulation scenario  In addition to those files, each simulator need to be provided with their custom configuration files.\nMain Configuration The main configuration file of a scenario is scenario_config.json. In this file basic properties are configured, such as the name of the scenario, the random seed, and activated simulators. Such a file looks like the following:\n{ \u0026quot;simulation\u0026quot;: { \u0026quot;id\u0026quot;: \u0026quot;Barnim\u0026quot;, \u0026quot;duration\u0026quot;: \u0026quot;1000s\u0026quot;, \u0026quot;randomSeed\u0026quot;: 268965854, \u0026quot;projection\u0026quot;: { \u0026quot;centerCoordinates\u0026quot;: { \u0026quot;latitude\u0026quot;: 52.511289, \u0026quot;longitude\u0026quot;: 13.3167457 }, \u0026quot;cartesianOffset\u0026quot;: { \u0026quot;x\u0026quot;: -385769.05, \u0026quot;y\u0026quot;: -5819239.29 } }, \u0026quot;network\u0026quot;: { \u0026quot;netMask\u0026quot;: \u0026quot;255.255.0.0\u0026quot;, \u0026quot;vehicleNet\u0026quot;: \u0026quot;10.1.0.0\u0026quot;, \u0026quot;rsuNet\u0026quot;: \u0026quot;10.2.0.0\u0026quot;, \u0026quot;tlNet\u0026quot;: \u0026quot;10.3.0.0\u0026quot;, \u0026quot;csNet\u0026quot;: \u0026quot;10.4.0.0\u0026quot;, \u0026quot;serverNet\u0026quot;: \u0026quot;10.5.0.0\u0026quot;, \u0026quot;tmcNet\u0026quot;: \u0026quot;10.6.0.0\u0026quot; } }, \u0026quot;federates\u0026quot;: { \u0026quot;application\u0026quot;: true, \u0026quot;environment\u0026quot;: false, \u0026quot;cell\u0026quot;: false, \u0026quot;ns3\u0026quot;: false, \u0026quot;omnetpp\u0026quot;: false, \u0026quot;sns\u0026quot;: false, \u0026quot;sumo\u0026quot;: true, \u0026quot;visualizer\u0026quot;: true } }  The following fields needs to be configured:\n id - The name of the scenario duration - The duration of the simulation in seconds. randomSeed - The seed to initialze the random number generator with in order to have deterministic results. If not set, a random seed is taken. projection - Configures the coordinate transformation from geographic coordinates to cartesian coordinates. Having a correct setting here is crucial to get correct results that map to real world coordinates so the simulation results can be visualized in some way. The center coordinate will be used to determine the correct UTM zone, the cartesianOffset can be determined by having a look at the traffic simulators network file, e.g. SUMOs *.net.xml contains this information in the netOffset attribute of the location tag. network - Within this config the address resolution scheme is specified. The subnets for all unit types are described here. Usually, default configuration should be sufficient. However, if you have many vehicles in your scenario the IP address space would be to small to provide enough addresses. In such cases, the netMask and all subnets have to be configured accordingly. Last but not least, the federate tags define which simulators are active in the simulation.  Traffic Simulator Configuration The generated files for the used traffic simulator are placed into the folder named after that simulator, e. g. sumo . For example, the \u0026lt;scenarioName\u0026gt;.sumocfg describes the main configuration of the SUMO simulator, which should refer to a network file and a route file:\n\u0026lt;configuration\u0026gt; \u0026lt;input\u0026gt; \u0026lt;net-file value=\u0026quot;MyScenario.net.xml\u0026quot; /\u0026gt; \u0026lt;route-files value=\u0026quot;MyScenario.rou.xml\u0026quot; /\u0026gt; \u0026lt;/input\u0026gt; \u0026lt;/configuration\u0026gt;  While the *.net.xml is a mandatory file to be placed within the sumo directory, the *.rou.xml is automatically generated by the SumoAmbassador when the simulation is started. More information about the configuration of SUMO can be found here.\nApplications and Mapping  Read the detailed documentation of the Mapping Configuration.\n  Vehicles Usually you want the simulated vehicles to be equipped with some kind of applications that influence the vehicle\u0026rsquo;s behavior. To do that you copy the jar files of your applications to the folder \u0026lt;scenarioName\u0026gt;/application . Having the applications in place you will have to create a mapping_config.json file in the folder \u0026lt;scenarioName\u0026gt;/mapping .\nThe following file would spawn 1 vehicle every five seconds (720 veh/hour divided by 3600 sec) until it reaches the max number of vehicles: 500. All the vehicles would be equipped with an application sending CA-messages periodically.\n{ \u0026quot;prototypes\u0026quot;:[ { \u0026quot;name\u0026quot;: \u0026quot;Car\u0026quot;, \u0026quot;accel\u0026quot;: 2.6, \u0026quot;decel\u0026quot;: 4.5, \u0026quot;maxSpeed\u0026quot;: 80.0, \u0026quot;applications\u0026quot;: [ \u0026quot;org.eclipse.mosaic.fed.application.app.etsi.VehicleCamSendingApp\u0026quot; ] } ], \u0026quot;vehicles\u0026quot;:[ { \u0026quot;startingTime\u0026quot;: 0.0, \u0026quot;targetFlow\u0026quot;: 720, \u0026quot;maxNumberVehicles\u0026quot;: 500, \u0026quot;route\u0026quot;: \u0026quot;3\u0026quot;, \u0026quot;types\u0026quot;: [ { \u0026quot;name\u0026quot;: \u0026quot;Car\u0026quot; } ] } ] }  Traffic lights If you want to simulate traffic lights equipped with applications, traffic lights should be defined in the simulator specific configuration file and also added to the mapping configuration file. The applications can be equipped by explicitly specifying them as \u0026ldquo;applications\u0026rdquo;\n{ \u0026quot;trafficLights\u0026quot;: [ { \u0026quot;tlGroupId\u0026quot;: \u0026quot;Bismarkstr_Krummestr\u0026quot;, \u0026quot;applications\u0026quot;: [ \u0026quot;org.eclipse.mosaic.app.tutorial.TrafficLightApp\u0026quot; ] } ] }  or by referring to previously defined prototypes:\n{ \u0026quot;prototypes\u0026quot;:[ { \u0026quot;name\u0026quot;: \u0026quot;Car\u0026quot;, \u0026quot;accel\u0026quot;: 2.6, \u0026quot;decel\u0026quot;: 4.5, \u0026quot;maxSpeed\u0026quot;: 80.0, \u0026quot;applications\u0026quot;: [ \u0026quot;org.eclipse.mosaic.fed.application.app.etsi.VehicleCamSendingApp\u0026quot; ] }, { \u0026quot;name\u0026quot;: \u0026quot;TrafficLight\u0026quot;, \u0026quot;applications\u0026quot;: [ \u0026quot;org.eclipse.mosaic.app.tutorial.TrafficLightApp\u0026quot; ] } ], \u0026quot;vehicles\u0026quot;:[ { \u0026quot;startingTime\u0026quot;: 0.0, \u0026quot;targetFlow\u0026quot;: 720, \u0026quot;maxNumberVehicles\u0026quot;: 500, \u0026quot;route\u0026quot;: \u0026quot;3\u0026quot;, \u0026quot;types\u0026quot;: [ { \u0026quot;name\u0026quot;: \u0026quot;Car\u0026quot; } ] } ], \u0026quot;trafficLights\u0026quot;: [ { \u0026quot;tlGroupId\u0026quot;: \u0026quot;Bismarkstr_Krummestr\u0026quot;, \u0026quot;name\u0026quot;: \u0026quot;TrafficLight\u0026quot; } ] }  Please note that traffic light name and traffic light itself in the mapping file stand for a traffic light group controlling a whole junction. Traffic light group can consist of many individual traffic lights controlling an exact lane. The value of the \u0026ldquo;tlGroupId\u0026rdquo; key MUST coincide with the name of the traffic light group in the traffic simulator related configuration file (with tlLogic id for SUMO and with junction id for Phabmacs).\nFor SUMO, the description of traffic light groups and their programs can be found in \u0026lt;scenarioname\u0026gt;.net.xml:\n\u0026lt;tlLogic id=\u0026quot;26704448\u0026quot; type=\u0026quot;static\u0026quot; programID=\u0026quot;1\u0026quot; offset=\u0026quot;0\u0026quot;\u0026gt; \u0026lt;phase duration=\u0026quot;39\u0026quot; state=\u0026quot;GGrG\u0026quot;/\u0026gt; \u0026lt;phase duration=\u0026quot;6\u0026quot; state=\u0026quot;yyry\u0026quot;/\u0026gt; \u0026lt;phase duration=\u0026quot;39\u0026quot; state=\u0026quot;rrGG\u0026quot;/\u0026gt; \u0026lt;phase duration=\u0026quot;6\u0026quot; state=\u0026quot;rryy\u0026quot;/\u0026gt; \u0026lt;/tlLogic\u0026gt;  Corresponding mapping_config.json:\n{ ... \u0026quot;trafficLights\u0026quot;: [ { \u0026quot;tlGroupId\u0026quot;: \u0026quot;26704448\u0026quot;, \u0026quot;name\u0026quot;: \u0026quot;TrafficLight\u0026quot; } ] }  More information on the mapping configuration can be found (here.\nFor more information about how SUMO traffic lights work please refer to SUMO Traffic Lights.\nThe application folder furthermore needs a generated database file \u0026lt;scenarioName\u0026gt;.db . This database file contains information about the road network (road topology) and all routes the vehicles can drive on. This file is usually generated by the tool scenario-convert, which is described here in detail.\nCommunication Simulator The configuration of the communication parameters are usually not dependent from the location of the road network. Therefore, most of the required files can be extracted from other scenarios, such Barnim or Tiergarten. Depending on the simulator you will need to configure the geographic extend of the simulation area. You can find that data in the traffic simulators network file, e.g. SUMOs *.net.xml contains this information in the convBoundary attribute of the location tag.\n For OMNeT++, it concerns the values of constraintArea in the omnetpp.ini For the Eclipse MOSAIC Cell simulator, the expansions do not need to be configured directly. However, the areas of the configured regions (in regions.json) have to be in line with the scenario location. The SNS also comes without an additional expansion definition.  Further information on the communication simulators can be found in: Eclipse MOSAIC SNS Eclipse MOSAIC Cell OMNeT\u0026#43;\u0026#43; ns-3\n","date":1557010800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1557010800,"objectID":"911d7d211da284d47641d647331b899d","permalink":"https://www.eclipse.org/mosaic/docs/building_scenarios/","publishdate":"2019-05-05T00:00:00+01:00","relpermalink":"/mosaic/docs/building_scenarios/","section":"docs","summary":"This section provides information on creating own simulation scenarios. A scenario is generally a folder structure that reflects the different components usually found in a simulation. Each of the folders contains various configuration files which in total describe the simulation setup, including the movements of the vehicles, the definition of the road network, communication properties, and the like.","tags":null,"title":"Simulation Scenarios","type":"docs"},{"authors":null,"categories":null,"content":"To get a simple and instant impression of a simulation or to get an idea of how fast it runs or where a simulation is located, the WebSocket Visualizer was created. It runs in the browser and shows an OpenLayers Map with markers, indicating the positions of all vehicles, as well as overall the simulation progresses.\n Red vehicles are sending messages and green vehicles are receiving messages at that specific point of time in the simulation.   To start the visualization, simply open the tools/web/visualizer.html in your browser. As soon as the page has finished loading all of its content, it starts trying to connect to the WebSocket created by the Eclipse MOSAIC simulation. The WebSocket is also enabled by default for the tutorial scenario Barnim. For more details see the file Barnim/output/output_config.xml.\n\u0026lt;?xml version=\u0026quot;1.0\u0026quot; encoding=\u0026quot;UTF-8\u0026quot;?\u0026gt; \u0026lt;configuration\u0026gt; \u0026lt;output id=\u0026quot;websocket\u0026quot; enabled=\u0026quot;true\u0026quot; loader=\u0026quot;org.eclipse.mosaic.fed.output.generator.websocket.WebsocketVisualizerLoader\u0026quot;\u0026gt; \u0026lt;synchronized\u0026gt;true\u0026lt;/synchronized\u0026gt; \u0026lt;port\u0026gt;46587\u0026lt;/port\u0026gt; \u0026lt;subscriptions\u0026gt; \u0026lt;subscription id=\u0026quot;VehicleUpdates\u0026quot; enabled=\u0026quot;true\u0026quot;/\u0026gt; \u0026lt;subscription id=\u0026quot;V2xMessageReception\u0026quot; enabled=\u0026quot;true\u0026quot;/\u0026gt; \u0026lt;subscription id=\u0026quot;V2xMessageTransmission\u0026quot; enabled=\u0026quot;true\u0026quot;/\u0026gt; \u0026lt;subscription id=\u0026quot;VehicleRegistration\u0026quot; enabled=\u0026quot;true\u0026quot;/\u0026gt; \u0026lt;subscription id=\u0026quot;RsuRegistration\u0026quot; enabled=\u0026quot;true\u0026quot;/\u0026gt; \u0026lt;subscription id=\u0026quot;TrafficLightRegistration\u0026quot; enabled=\u0026quot;true\u0026quot;/\u0026gt; \u0026lt;/subscriptions\u0026gt; \u0026lt;/output\u0026gt; \u0026lt;/configuration\u0026gt;  As soon, as the simulation is running, you should see vehicle markers moving around and indicating if they are sending V2X messages (green) or receiving V2X message (red).\nThe status bar at the bottom of the page indicates the current connection/simulation state. There are four possible states:\n Connecting - Trying to connect to the WebSocket opened by Eclipse MOSAIC. Simulating - Periodically fetching simulation data and updating markers accordingly. Simulation finished - The simulation has finished. Error - An error occurred. Either there was a problem caused by the WebSocket itself, or a timeout occurred while trying to connect to the WebSocket.  After the simulation has finished, you can click on the reconnect button and then run the simulation again. You can also start the visualization at each simulation run, using the command line parameter -v. In that case, Eclipse MOSAIC will automatically open the tools/web/visualizer.html in your default browser once the simulation starts.\n By default, the WebSocket Visualizer does not work on Microsoft Edge. UWP (UniversalWindows Platform) apps onWindows 10 do not have direct network access but are subject to a network isolation for security reasons, preventing localhost loopback by default. WhileMicrosoft Edge itself does allow localhost access, it treats localhost as an Internet site, which leads to restrictions e.g. for IPC over IP. To prevent this, an exception for Edgemust be added to the network isolation via the following command in an elevated command prompt:\nCheckNetIsolation LoopbackExempt -a -n=\u0026quot;Microsoft.MicrosoftEdge_8wekyb3d8bbwe\u0026quot;    ","date":1557010800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1557010800,"objectID":"4ceda5b87ab93856c1c3520fdb9ecfb3","permalink":"https://www.eclipse.org/mosaic/docs/visualization/","publishdate":"2019-05-05T00:00:00+01:00","relpermalink":"/mosaic/docs/visualization/","section":"docs","summary":"To get a simple and instant impression of a simulation or to get an idea of how fast it runs or where a simulation is located, the WebSocket Visualizer was created.","tags":null,"title":"WebSocket Visualizer","type":"docs"},{"authors":null,"categories":null,"content":" You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCMappingAmbassadorScheme This schema describes the JSON file structure for the mapping configuration, which is used to define simulation entities.\nProperties\n    Type Description Required Boundaries Default     config  config Object to define additional configuration options for the mapping No None None   prototypes  prototype[] Array of prototypes, which can complete the definitions of other objects. This can be used to re-use certain configurations. All possible properties of objects are available. Only the ones needed will be used (for example an RSU does not have a length, so this property would be ignored). No None None   typeDistributions  typeDistribution Object to define the distribution of prototypes to reuse in vehicle spawners. A typeDistribution is referenced by it\u0026rsquo;s attribute name, which can be set to any valid string. No None None   vehicles  vehicle[] Array of vehicles to be spawned in the simulation. This property describes the vehicles populatingthe simulation. It is possible to create a single vehicle (maxNumberVehicles should be \u0026lsquo;1\u0026rsquo; in that case) or a streamof one or multiple vehicles. The type(s) are defined in the field types. When more than one type is defined theweights in the prototype can be used to balance them against each other. No None None   matrixMappers  matrixMapper[] Array of items to define additional traffic that will be spawned using OD-matrices. No None None   rsus  rsu[] Array of Road Side Units (RSUs). For RSUs only applications can be defined along with the position. No None None   servers  server[] Array of servers. Servers are a form of units that have no geographical location. The network properties of a server can be defined in the network.json-configuration in the cell-module. No None None   tmcs  tmc[] Array of Traffic Management Centers (TMCs). TMCs are specialized forms of servers having direct access to data collected by induction loops and lane area detectors. The network properties of a TMC can be defined in the network.json-configuration in the cell-module. No None None   trafficLights  trafficLights[] Array of prototypes for traffic lights. Since it is a traffic light only applications can be defined. Traffic light prototypes can be distributed among all traffic lights of an application by weight or assigned to specific traffic lights by using the ID of traffic light groups as reference. No None None   chargingStations  chargingStation[] Array of electric vehicle charging stations based on ETSI TS 101 556-1. An infrastructure which provides one or several electric vehicle charging spots to supply electric energy for charging electric vehicles. No None None    Further property restrictions:\n\nCMappingAmbassadorScheme.typeDistributions  Type of each property: array   \nconfig Object to define additional configuration options for the mapping\nProperties\n    Type Description Required Boundaries Default     start number Defines the point in time (in seconds) to start spawning vehicles. If not set (default), all vehicles will be spawned according to the vehicles configuration. No [0, +$\\infty$] None   end number Defines the point in time (in seconds) to end spawning vehicles. If not set (default), all vehicles will be spawned according to the vehicles configuration or until the simulation ends. No [0, +$\\infty$] None   scaleTraffic number Scales the traffic by the given factor. E.g. 2.0 would double the number of spawned vehicles No [0, +$\\infty$] 1   adjustStartingTimes boolean If set to true and if the parameter start is set, the starting times of each spawner is adjusted accordingly, so that we shouldn\u0026rsquo;t wait in case that the simulation starting time and spawner starting time are widely spread out. All spawners before start will be completely ignored then. No None false   randomizeFlows boolean If set to true, all flow definitions defined by vehicle spawners with more than one vehicle resulting in slightly randomized departure times. The specified targetFlow of the vehicle spawner is kept. No None false   randomizeStartingTimes boolean If set to true, the starting times of all vehicle spawner definitions are randomized by +-60seconds. No None false   randomizeWeights boolean If set to true, the configured weights of all types are slightly randomized by +-1% of the sum of all weights. No None false     \nprototype Object to define a prototype, which can complete the definitions of other objects. This can be used to re-use certain configurations. All possible properties of objects are available. Only the ones needed will be used (for example an RSU does not have a length, so this property would be ignored).\nProperties\n    Type Description Required Boundaries Default     name string The name of this prototype is used to match it against other objects. ✓ Yes None None   group string The group name is used for (statistical) evaluation purposes with the StatisticOutput and ITEF. It allows to summarize multiple prototype entities. No None None   accel number Acceleration in m/s^2. No (0, +$\\infty$] None   decel number Deceleration in m/s^2. No (0, +$\\infty$] None   length string\nnumber Length of the vehicle. If defined as a number, then the default unit is m. Alternatively this can be defined as a string to specify the unit of measurement (e.g. \u0026lsquo;500 cm\u0026rsquo;). No (0, +$\\infty$] None   maxSpeed string\nnumber Maximal speed. If defined as a number, then the default unit is m/s. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;50 kmh\u0026rsquo;). No (0, +$\\infty$] None   minGap string\nnumber Distance in meter between front bumper of a vehicle and the back bumper of its leader in a traffic jam. If defined as a number, then the default unit is m. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;300 cm\u0026rsquo;). No (0, +$\\infty$] None   sigma number Driver imperfection. This is a parameter of the car-following model. No [0, 1] None   tau number Driver reaction time in seconds. This is a parameter of the car-following model. No [0, +$\\infty$] None   weight number The weight is used to distribute objects between multiple types. All weights do NOT have to add up to 1 or 100. (Example: A vehicle spawner defining a traffic stream contains two prototypeDeserializers with the weights being 4 and 6. The resulting traffic stream will consist to 40% of the one type and 60% of the other) No [0, +$\\infty$] None   vehicleClass string Class of the vehicle. The classes are used in lane definitions and allow/disallow the use of lanes for certain vehicle types (e.g. a taxi lane). No Enum  None   applications string[] The applications to be used for this object. No None None    Further property restrictions:\n\nprototype.vehicleClass  Allowed values:  Unknown Car LightGoodsVehicle HeavyGoodsVehicle PublicTransportVehicle EmergencyVehicle WorksVehicle ExceptionalSizeVehicle VehicleWithTrailer HighSideVehicle MiniBus Taxi ElectricVehicle AutomatedVehicle Bicycle Motorcycle HighOccupancyVehicle     \ntypeDistribution Object to define the distribution of prototypes to reuse in vehicle spawners. A typeDistribution is referenced by it\u0026rsquo;s attribute name, which can be set to any valid string.\nThe following additional properties are allowed:\n array[ prototype]   \nvehicle Object to define vehicles to be spawned in the simulation. This property describes the vehicles populating the simulation. It is possible to create a single vehicle (maxNumberVehicles should be \u0026lsquo;1\u0026rsquo; in that case) or a stream of one or multiple vehicles. The types (or type) are defined in the field types. When more than one type is defined the weights in the prototype can be used to balance them against each other.\nProperties\n    Type Description Required Boundaries Default     startingTime number Time at which the first vehicle will be created. No [0, +$\\infty$] 0   maxTime number Simulation time in seconds at which no more vehicles will be created. No [0, +$\\infty$] None   targetFlow number Density of vehicles per hour. Vehicles will be spawned uniformly. No [0, +$\\infty$] 600   maxNumberVehicles number Maximum number of vehicles to be created from this source. No [0, +$\\infty$] None   departSpeed string\nnumber The speed at which the vehicle is supposed to depart. If defined as a number, then the default unit is m/s. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;10 kmh\u0026rsquo;). Depending on the simulator this value may only be used if departSpeedMode is set to PRECISE. No None None   departSpeedMode string The depart speed mode determines the vehicle\u0026rsquo;s speed at insertion. No Enum  MAXIMUM   laneSelectionMode string The lane selection mode chooses the lane for the next departing vehicle. No Enum  DEFAULT   spawningMode string Adjusts the departure time of individual vehicles. No Enum  CONSTANT   deterministic boolean Determines if selection of a vehicles type when spawning follows a deterministic or stochastic model. When set to true the spawning-process will choose exactly the same types with every execution. When set to false the order of types may be different and selected weights will be reached more slowly. No None true   pos number Position within the route where the vehicle(s) should be spawned. No [0, +$\\infty$] 0   route string Route that the vehicle(s) should use. If an origin and a destination are specified this route will be treated as a preference (i.e. it will be selected if it connects the two points in question). No None None   lanes number[] Array of numbers to define the lanes to be used. The vehicles will be evenly distributed among the given lanes. When no value is given lane zero will be used for all vehicles. No None None   types  prototype[1-*] List of possible vehicle types to be spawned. In this list you can simply refer to an existing prototype by its name attribute to include everything defined there. You can also overwrite every attribute of the prototype. If you don\u0026rsquo;t have an existing prototype the definitions found here will be used as the prototype definition itself. No None None   typeDistribution string Identifier of the typeDistribution which defines the distribution of vehicle types. No None None   destination  geoCircle Object to define an immutable pair of a geoPoint center position and a radius in meters. ✓ Yes None None   origin  geoCircle Object to define an immutable pair of a geoPoint center position and a radius in meters. ✓ Yes None None    Further property restrictions:\n\nvehicle.departSpeedMode  Allowed values:  PRECISE RANDOM MAXIMUM     vehicle.laneSelectionMode  Allowed values:  DEFAULT ROUNDROBIN ROUNDROBIN_HIGHWAY HIGHWAY RANDOM FREE ALLOWED BEST FIRST     vehicle.spawningMode  Allowed values:  CONSTANT GROW POISSON SHRINK GROW_AND_SHRINK GROW_EXPONENTIAL SHRINK_EXPONENTIAL GROW_AND_SHRINK_EXPONENTIAL     \ngeoCircle Object to define an immutable pair of a geoPoint center position and a radius in meters.\nProperties\n    Type Description Required Boundaries Default     center  geoPoint Object to define geographical point coordinates. ✓ Yes None None   radius number Radius of the circle. ✓ Yes [0, +$\\infty$] None     \ngeoPoint Object to define geographical point coordinates.\nProperties\n    Type Description Required Boundaries Default     longitude number East-west position of a point on earth. ✓ Yes [-180, 180] None   latitude number North-south position of a point on earth. ✓ Yes [-$\\infty$, 90] None     \nmatrixMapper Object to define a mapper for an Origin-Destination (OD) matrix. The mapper contains a list of points (with varying radius) and a matrix (arrays) of flow values. It creates a series of conventional vehicles spawners from the specified data.\nProperties\n    Type Description Required Boundaries Default     points  odPoint[] Array of odPoints that can be referenced from the OD-matrix. ✓ Yes None None   types  prototype[] Array of prototypes to define the vehicles that should be spawned. No None None   deterministic boolean If deterministic is true the spawning-process will be exactly the same with every execution. If left false the order is different and the selected weights will be reached slower than in the deterministic mode. No None true   odValues array[] Values for the OD-matrix. Unit should be vehicles/hour. ✓ Yes None None     \nodPoint Object to define a point that can be referenced from an OD-matrix.\nProperties\n    Type Description Required Boundaries Default     name string The name of the point. This identifier is used to reference the odPoint. ✓ Yes None None   position  geoCircle Object to define an immutable pair of a geoPoint center position and a radius in meters. ✓ Yes None None     \nrsu Object to define a Road Side Unit (RSU). For RSUs only applications can be defined along with the position.\nProperties\n    Type Description Required Boundaries Default     position  geoPoint Object to define geographical point coordinates. ✓ Yes None None   name string Used to be matched with a prototype. If a prototype name matches this name, all properties not set in this object will be overwritten by those defined in the prototype. No None None   group string The group name is used for (statistical) evaluation purposes with the StatisticOutput and ITEF. It allows to summarize multiple rsu entities. No None None   applications string[] Array of strings that specifies the applications to be used for this object. If none are specified, none are used No None None     \nserver Object to define a server. Servers are a form of units that have no geographical location. The network properties of a server can be defined in the network.json-configuration in the cell-module.\nProperties\n    Type Description Required Boundaries Default     name string Used to be matched with a prototype. If a prototype name matches this name, all properties not set in this object will be overwritten by those defined in the prototype. No None None   group string The group name is used to match with configurations in the network.json-configuration in the cell-module. No None None   applications string[] The applications to be used for this object. If none are specified, none are used. No None None     \ntmc Object to define a Traffic Management Center (TMCs). TMCs are specialized forms of server directly communicating with induction loops and lane area detectors. The network properties of a TMC can be defined in the network.json-configuration in the cell-module.\nProperties\n    Type Description Required Boundaries Default     name string Used to be matched with a prototype. If a prototype name matches this name, all properties not set in this object will be overwritten by those defined in the prototype. No None None   group string The group name is used to match with configurations in the network.json-configuration in the cell-module. No None None   applications string[] The applications to be used for this object. If none are specified, none are used. No None None   inductionLoops string[] The induction loops the TMC shall be matched with. If none are specified, none are used. No None None   laneAreaDetectors string[] The lane area detectors the TMC shall be matched with. If none are specified, none are used. No None None     \ntrafficLights Object to define a prototype for a traffic light. Since it is a traffic light only applications can be defined. Traffic light prototypes can be distributed among all traffic lights of an application by weight or assigned to specific traffic lights by using the ID of traffic light groups as reference.\nProperties\n    Type Description Required Boundaries Default     name string Used to be matched with a prototype. If a prototype name matches this name, all properties not set in this object will be overwritten by those defined in the prototype. No None None   tlGroupId string The ID of a traffic light group. This property is used to map applications to specific traffic lights. No None None   group string The group name is used for (statistical) evaluation purposes with the StatisticOutput and ITEF. It allows to summarize multiple trafficLights entities. No None None   weight number The weight is used to distribute traffic lights between multiple default types. If tlGroupId is not set, then the default value is 1, otherwise 0. All weights do NOT have to add up to 1 or 100. No [0, +$\\infty$] None   applications string[] The applications to be used for this object. If none are specified, none are used No None None     \nchargingStation Object to define an electric vehicle charging station based on ETSI TS 101 556-1. An infrastructure which provides one or several electric vehicle charging spots to supply electric energy for charging electric vehicles.\nProperties\n    Type Description Required Boundaries Default     position  geoPoint Object to define geographical point coordinates. ✓ Yes None None   operator string The EV charging station operator (e.g. energy provider) identification. ✓ Yes None None   group string The group name is used for (statistical) evaluation purposes with the StatisticOutput and ITEF. It allows to summarize multiple charginStation entities. No None None   access string Access restrictions, e.g. open to all or restricted to some communities, free of access or paying access. ✓ Yes None None   name string Used to be matched with a prototype. If a prototype name matches this name, all properties not set in this object will be overwritten by those defined in the prototype. No None None   chargingSpots  chargingSpot[] List of the electric vehicle charging spots associated with this electric vehicle charging station. ✓ Yes None None   applications string[] The application to be used for this object. No None None     \nchargingSpot Object to define an electric vehicle charging spot based on ETSI TS 101 556-1. A set of 1 to 4 parking places arranged around a pole, where it is possible to charge an electric vehicle.\nProperties\n    Type Description Required Boundaries Default     id number Unique identifier of the charging spot. No None None   type integer The type of this electric vehicle charging spot in compliance with current standards, including IEC 62196-2. ✓ Yes [1, 3] None   parkingPlaces integer Number of available parking places, i.e. 1 to 4 parking places arranged around a pole. ✓ Yes [1, 4] None    ","date":-62135596800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":-62135596800,"objectID":"0545c9520e50f302ba5eb1100e12a695","permalink":"https://www.eclipse.org/mosaic/docs/mosaic_configuration/mapping_ambassador_config/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mosaic/docs/mosaic_configuration/mapping_ambassador_config/","section":"docs","summary":"You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCMappingAmbassadorScheme This schema describes the JSON file structure for the mapping configuration, which is used to define simulation entities.","tags":null,"title":"Mapping Ambassador Configuration","type":"docs"},{"authors":null,"categories":null,"content":" You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCEnvironmentScheme Schema describing the JSON file structure for the environment configuration. It is is used to define which events are evaluated by the simulator. Entities entering the areas of the events, are notified by the \u0026lsquo;EnvironmentSensorUpdates\u0026rsquo; interaction\nProperties\n    Type Description Required Boundaries Default     events  event[] List of events. No None None     \nevent Object to define a single event configuration.\nProperties\n    Type Description Required Boundaries Default     type  eventType Object to define the type of an event. ✓ Yes None None   location  eventLocation Object to define the event location configuration, which is either a GeoArea (e.g. rectangle, circle, or polygon) or a specific street segment. ✓ Yes None None   time  eventTime Object to define the temporal properties of an event. ✓ Yes None None     \neventType Object to define the type of an event.\nProperties\n    Type Description Required Boundaries Default     sensorType string Represents the type of sensor value this event is emitting (e.g. Ice, Snow, or an arbitrary Obstacle). The value can be set to any valid string. ✓ Yes None None   value integer Used for assigning a value to the event. It can be used as the strength of an event, the amount of free parking spots in a parking lot, etc. No None 1     \neventLocation Object to define the event location configuration, which is either a GeoArea (e.g. rectangle, circle, or polygon) or a specific street segment.\nProperties\n    Type Description Required Boundaries Default     area  area Object to define the area in which the event is located in. No None None   roadSegmentId string The ID of the road segment the event is located on (Connection ID or road ID). No None None     \narea Object to define the area in which the event is located in.\nProperties\n    Type Description Required Boundaries Default     type string The type of the area. No Enum  None    Additionally ANY of the following property definitions apply:\n  geoCircle  geoRectangle  geoPolygon  Further property restrictions:\n\narea.type  Allowed values:  Rectangle Circle Polygon     \ngeoCircle Object to define an immutable pair of a geoPoint center position and a radius in meters.\nProperties\n    Type Description Required Boundaries Default     center  geoPoint Object to define geographical point coordinates. ✓ Yes None None   radius number Radius of the circle in m. ✓ Yes [0, +$\\infty$] None     \ngeoPoint Object to define geographical point coordinates.\nProperties\n    Type Description Required Boundaries Default     longitude number East-west position of a point on earth. ✓ Yes [-180, 180] None   latitude number North-south position of a point on earth. ✓ Yes [-$\\infty$, 90] None     \ngeoRectangle Object to define an immutable pair of two different GeoPoints. Together they form a rectangular area.\nProperties\n    Type Description Required Boundaries Default     a  geoPoint Object to define geographical point coordinates. ✓ Yes None None   b  geoPoint Object to define geographical point coordinates. ✓ Yes None None     \ngeoPolygon Object to define a set of GeoPoints. Together the points for a polygonal area.\nProperties\n    Type Description Required Boundaries Default     vertices  geoPoint[] Set of points representing the vertices of a polygon. No None None     \neventTime Object to define the temporal properties of an event.\nProperties\n    Type Description Required Boundaries Default     start string\nnumber Start time of the event. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 minutes\u0026rsquo;) ✓ Yes None None   end string\nnumber End time of the event. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 minutes\u0026rsquo;) ✓ Yes None None    ","date":-62135596800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":-62135596800,"objectID":"611e7a762ba0dd0c4095ae8e1eef3bf3","permalink":"https://www.eclipse.org/mosaic/docs/mosaic_configuration/environment_config/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mosaic/docs/mosaic_configuration/environment_config/","section":"docs","summary":"You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCEnvironmentScheme Schema describing the JSON file structure for the environment configuration.","tags":null,"title":"Environment Configuration","type":"docs"},{"authors":null,"categories":null,"content":" You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCSnsScheme Schema describing the JSON file structure for the sns configuration.\nProperties\n    Type Description Required Boundaries Default     maximumTtl integer The threshold for the amount of hops for a transmission. This is an additional, hard threshold, which can\u0026rsquo;t be exceeded. No [0, +$\\infty$] 10   singlehopRadius number Default radius in m to be used if an AdhocConfiguration doesn\u0026rsquo;t specify a radius. No None 509.4   adhocTransmissionModel  adhocTransmissionModel Object to define an adhoc transimssion model. No None None   singlehopDelay  delay Object to define a delay model. No None  constantDelay   singlehopTransmission  transmission Object to define the properties of a transmission. ✓ Yes None None     \nadocTransmissionModel Object to define an adhoc transimssion model.\nProperties\n    Type Description Required Boundaries Default     type string Type of the transmission model. The simple model assumes, that all receivers can be reached even though this might not be the case in reality. No Enum  None   simpleMultihopDelay  delay Object to define a delay model. No None  constantDelay   simpleMultihopTransmission  transmission Object to define the properties of a transmission. ✓ Yes None None    Further property restrictions:\n\nadhocTransmissionModel.type  Allowed values:  SimpleAdhocTransmissionModel SophisticatedAdhocTransmissionModel     \ndelay Object to define a delay model.\nAdditionally ONE of the following property definitions apply:\n  gammaDelay  constantDelay  simpleRandomDelay   \ngammaDelay Object to define a model for GammaRandomDelay or GammaSpeedDelay. GammaRandomDelay bases directly on the Gamma distribution (b=2,p=2) with minimum and expected value. Due to the nature of the Gamma distribution, the resulting delays can be far higher than the expected value. GammaSpeedDelay bases on the GammaRandomDelay and includes an additional speed penalty according to the current speed of the vehicle.\nProperties\n    Type Description Required Boundaries Default     type string Type of Gamma delay. ✓ Yes Enum  None   minDelay number\nstring Minimum delay for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None   expDelay number\nstring Expected delay for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\ngammaDelay.type  Allowed values:  GammaRandomDelay GammaSpeedDelay     \nconstantDelay Object to define a model for constant delay, which delivers always the same delay.\nProperties\n    Type Description Required Boundaries Default     type string Type of the constant delay ✓ Yes Enum  None   delay number\nstring The delay. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\nconstantDelay.type  Allowed values:  ConstantDelay     \nsimpleRandomDelay Object to define a model for a radnomised delay. Delivers number-of-steps different uniformly distributed delays in the interval defined by min and max (e.g. minDelay=30ms, maxDelay=60ms, steps=4 -\u0026gt; possible delays={30,40,50,60}ms.).\nProperties\n    Type Description Required Boundaries Default     type string Type of the delay. ✓ Yes Enum  None   steps integer Number of possible delays between min and max. ✓ Yes [0, +$\\infty$] None   minDelay number\nstring Minimum delay in nanoseconds for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None   maxDelay number\nstring Maximum delay in nanoseconds for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\nsimpleRandomDelay.type  Allowed values:  SimpleRandomDelay     \ntranmission Object to define the properties of a transmission.\nProperties\n    Type Description Required Boundaries Default     lossProbability number Probability of packet retransmission (in case of configured retries \u0026gt; 0) or packet loss (retries = 0) for the packet retransmission/loss model. A value of 0 equals a lossfree transmission. ✓ Yes [0, 1] 0   maxRetries integer Maximum Number of retransmissions. No [0, +$\\infty$] None    ","date":-62135596800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":-62135596800,"objectID":"99fcd63e0ade62d27eee7393fc38c764","permalink":"https://www.eclipse.org/mosaic/docs/mosaic_configuration/sns_config/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mosaic/docs/mosaic_configuration/sns_config/","section":"docs","summary":"You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCSnsScheme Schema describing the JSON file structure for the sns configuration.","tags":null,"title":"SNS Configuration","type":"docs"},{"authors":null,"categories":null,"content":" You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCNetworkScheme Schema describing the JSON file structure for the network configuration. It is is used to define the properties of the global network. If defined as a number, then the default unit is Gb. Alternatively this can be defined as a string to specify the unit of measurement (e.g. \u0026lsquo;3 MB\u0026rsquo;).\nProperties\n    Type Description Required Boundaries Default     defaultDownlinkCapacity integer\nstring This downlink capacity value will be used for node-specific capacity calculation, if it wasn\u0026rsquo;t set in the cell configuration. If defined as a number, then the default unit is Gb. Alternatively this can be defined as a string to specify the unit of measurement (e.g. \u0026lsquo;3 MB\u0026rsquo;). No None 100 Gb   defaultUplinkCapacity integer\nstring This uplink capacity value will be used for node-specific capacity calculation, if it wasn\u0026rsquo;t set in the cell configuration. No None 100 Gb   globalNetwork  globalNetwork Object to define all coverage properties of one region of the radio access network (ran-part). Such a configuration consists of one uplink-module and one downlink-module. In this context, uplink and downlink always refer to the direction TOWARDS and respectively FROM the GEO entity. ✓ Yes None None   servers  server List of configured servers. No None None     \nglobalNetwork Object to define all coverage properties of one region of the radio access network (ran-part). Such a configuration consists of one uplink-module and one downlink-module. In this context, uplink and downlink always refer to the direction TOWARDS and respectively FROM the GEO entity.\nProperties\n    Type Description Required Boundaries Default     uplink  globalNetwork.uplink Object to define the uplink of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity. ✓ Yes None None   downlink  globalNetwork.downlink Object to define the downlink of a network. The downlink supports two individual paths: Point-to-point communication (unicast) and Point-to-multipoint communication (multicast). ✓ Yes None None     \nglobalNetwork.uplink Object to define the uplink of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity.\nProperties\n    Type Description Required Boundaries Default     delay  delay Object to define a delay model. ✓ Yes None None   transmission  transmission Object to define the properties of a transmission. ✓ Yes None None   capacity integer\nstring The capacity. ✓ Yes None None   maxCapacity number The maximal capacity when no transmission is ongoing. No None None     \ndelay Object to define a delay model.\nAdditionally ONE of the following property definitions apply:\n  gammaDelay  constantDelay  simpleRandomDelay   \ngammaDelay Object to define a model for GammaRandomDelay or GammaSpeedDelay. GammaRandomDelay bases directly on the Gamma distribution (b=2,p=2) with minimum and expected value. Due to the nature of the Gamma distribution, the resulting delays can be far higher than the expected value. GammaSpeedDelay bases on the GammaRandomDelay and includes an additional speed penalty according to the current speed of the vehicle.\nProperties\n    Type Description Required Boundaries Default     type string The type of delay. ✓ Yes Enum  None   minDelay number\nstring Minimum delay for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to specify the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None   expDelay number\nstring Expected delay for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to specify the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\ngammaDelay.type  Allowed values:  GammaRandomDelay GammaSpeedDelay     \nconstantDelay Object to define a model for constant delay, which delivers always the same delay.\nProperties\n    Type Description Required Boundaries Default     type string The type of delay. ✓ Yes Enum  None   delay number\nstring The delay. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to specify the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\nconstantDelay.type  Allowed values:  ConstantDelay     \nsimpleRandomDelay Object to define a model for a radnomised delay. Delivers number-of-steps different uniformly distributed delays in the interval defined by min and max (e.g. minDelay=30ms, maxDelay=60ms, steps=4 -\u0026gt; possible delays={30,40,50,60}ms.).\nProperties\n    Type Description Required Boundaries Default     type string The type of delay. ✓ Yes Enum  None   steps integer Number of possible delays between min and max. ✓ Yes [0, +$\\infty$] None   minDelay number\nstring Minimum delay in nanoseconds for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to specify the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None   maxDelay number\nstring Maximum delay in nanoseconds for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to specify the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\nsimpleRandomDelay.type  Allowed values:  SimpleRandomDelay     \ntranmission Object to define the properties of a transmission.\nProperties\n    Type Description Required Boundaries Default     lossProbability number Probability of packet retransmission (in case of configured retries \u0026gt; 0) or packet loss (retries = 0) for the packet retransmission/loss model. A value of 0 equals a lossfree transmission. ✓ Yes [0, 1] None   maxRetries integer Maximum Number of retransmissions. No [0, +$\\infty$] 0     \nglobalNetwork.downlink Object to define the downlink of a network. The downlink supports two individual paths: Point-to-point communication (unicast) and Point-to-multipoint communication (multicast).\nProperties\n    Type Description Required Boundaries Default     unicast  unicast Point-to-point communication (unicast). ✓ Yes None None   multicast  multicast Point-to-multipoint communication (multicast). ✓ Yes None None   capacity integer\nstring Shared capacity between unicast and multicast. ✓ Yes None None     \nunicast Point-to-point communication (unicast).\nProperties\n    Type Description Required Boundaries Default     delay  delay Object to define a delay model. ✓ Yes None None   transmission  transmission Object to define the properties of a transmission. ✓ Yes None None     \nmulticast Point-to-multipoint communication (multicast).\nProperties\n    Type Description Required Boundaries Default     delay  delay Object to define a delay model. ✓ Yes None None   transmission  transmission Object to define the properties of a transmission. ✓ Yes None None   usableCapacity number The usableCapacity configures the ratio of the overall downlink capacity allowed to be used. ✓ Yes [0, 1] None     \nserver Properties\n    Type Description Required Boundaries Default     id string Network-Id for identification. ✓ Yes None None   uplink  server.uplink Object to define uplink properties of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity. No None None   downlink  server.downlink  No None None    The following additional properties are allowed:\n  undefined   \nserver.uplink Object to define uplink properties of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity.\nProperties\n    Type Description Required Boundaries Default     delay  delay Object to define a delay model. ✓ Yes None None   transmission  transmission Object to define the properties of a transmission. ✓ Yes None None    The following additional properties are allowed:\n  undefined   \nserver.downlink Properties\n    Type Description Required Boundaries Default     unicast  unicast Point-to-point communication (unicast). ✓ Yes None None    The following additional properties are allowed:\n  undefined  ","date":-62135596800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":-62135596800,"objectID":"8514240e2ce1a88f4228c2d190adaea8","permalink":"https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_network_config/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mosaic/docs/mosaic_configuration/cell_network_config/","section":"docs","summary":"You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCNetworkScheme Schema describing the JSON file structure for the network configuration.","tags":null,"title":"Cell Simulator – Network Configuration","type":"docs"},{"authors":null,"categories":null,"content":" You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCRegionSchema Schema describing the JSON file structure for the regional networks configuration. It is is used to extend the network with regional information, which enables the emulation of mobile networks. If configured very granular, these regions can reflect cells as used in the real world. Though for most use-cases it is sufficient to approximate the behaviour by defining larger regions.\nProperties\n    Type Description Required Boundaries Default     regions  mobileNetworkProperties[] An array of regional network configruations. No None None     \nmobileNetworkProperties Object to define a network with specific geograpgical extensions. It applies for all regions except the global network, which covers the remaining space. The CMobileNetworkProperties only needs to be employed, when geographic information are accessed.\nProperties\n    Type Description Required Boundaries Default     id string Network-Id for identification. No None None   area  geoRectangle Object to define an immutable pair of two different geoPoints. Together they form a rectangular area. ✓ Yes None None   polygon object The area of the network as a polygon. ✓ Yes None None   uplink  mobileNetworkProperties.uplink Object to define the uplink of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity. ✓ Yes None None   downlink  mobileNetworkProperties.downlink Object to define the downlink of a network. The downlink supports two individual paths: Point-to-point communication (unicast) and Point-to-multipoint communication (multicast). ✓ Yes None None     \ngeoRectangle Object to define an immutable pair of two different geoPoints. Together they form a rectangular area.\nProperties\n    Type Description Required Boundaries Default     nw  geoPoint Object to define geographical point coordinates. ✓ Yes None None   se  geoPoint Object to define geographical point coordinates. ✓ Yes None None     \ngeoPoint Object to define geographical point coordinates.\nProperties\n    Type Description Required Boundaries Default     lon number East-west position of a point on earth. ✓ Yes [-180, 180] None   lat number North-south position of a point on earth. ✓ Yes [-$\\infty$, 90] None     \nmobileNetworkProperties.uplink Object to define the uplink of a network. The uplink direction only allows point-to-point communication (unicast). It is composed of the three nested models for delay, transmission configuration and capacity.\nProperties\n    Type Description Required Boundaries Default     delay  delay Object to define a delay model. ✓ Yes None None   transmission  transmission Object to define the properties of a transmission. ✓ Yes None None   capacity integer\nstring The capacity of the uplink. ✓ Yes None None     \ndelay Object to define a delay model.\nAdditionally ONE of the following property definitions apply:\n  gammaDelay  constantDelay  simpleRandomDelay   \ngammaDelay Object to define a model for GammaRandomDelay or GammaSpeedDelay. GammaRandomDelay bases directly on the Gamma distribution (b=2,p=2) with minimum and expected value. Due to the nature of the Gamma distribution, the resulting delays can be far higher than the expected value. GammaSpeedDelay bases on the GammaRandomDelay and includes an additional speed penalty according to the current speed of the vehicle.\nProperties\n    Type Description Required Boundaries Default     type string Type of Gamma delay. ✓ Yes Enum  None   minDelay number\nstring Minimum delay for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None   expDelay number\nstring Expected delay for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\ngammaDelay.type  Allowed values:  GammaRandomDelay GammaSpeedDelay     \nconstantDelay Object to define a model for constant delay, which delivers always the same delay.\nProperties\n    Type Description Required Boundaries Default     type string Type of the constant delay ✓ Yes Enum  None   delay number\nstring The delay, given in ns if defined as a number. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\nconstantDelay.type  Allowed values:  ConstantDelay     \nsimpleRandomDelay Object to define a model for a radnomised delay. Delivers number-of-steps different uniformly distributed delays in the interval defined by min and max (e.g. minDelay=30ms, maxDelay=60ms, steps=4 -\u0026gt; possible delays={30,40,50,60}ms.).\nProperties\n    Type Description Required Boundaries Default     type string Type of the delay. ✓ Yes Enum  None   steps integer Number of possible delays between min and max. ✓ Yes [0, +$\\infty$] None   minDelay number\nstring Minimum delay in nanoseconds for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None   maxDelay number\nstring Maximum delay in nanoseconds for the Gamma distribution. If defined as a number, then the default unit is ns. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;3 seconds\u0026rsquo;) ✓ Yes None None    Further property restrictions:\n\nsimpleRandomDelay.type  Allowed values:  SimpleRandomDelay     \ntranmission Object to define the properties of a transmission.\nProperties\n    Type Description Required Boundaries Default     lossProbability number Probability of packet retransmission (in case of configured retries \u0026gt; 0) or packet loss (retries = 0) for the packet retransmission/loss model. A value of 0 equals a lossfree transmission. ✓ Yes [0, 1] 0   maxRetries integer Maximum Number of retransmissions. No [0, +$\\infty$] None     \nmobileNetworkProperties.downlink Object to define the downlink of a network. The downlink supports two individual paths: Point-to-point communication (unicast) and Point-to-multipoint communication (multicast).\nProperties\n    Type Description Required Boundaries Default     unicast  unicast Object to define point-to-point communication. ✓ Yes None None   multicast  multicast Object to define point-to-multipoint communication. ✓ Yes None None   capacity integer\nstring The capacity of the downlink. ✓ Yes None None     \nunicast Object to define point-to-point communication.\nProperties\n    Type Description Required Boundaries Default     delay  delay Object to define a delay model. ✓ Yes None None   transmission  transmission Object to define the properties of a transmission. ✓ Yes None None     \nmulticast Object to define point-to-multipoint communication.\nProperties\n    Type Description Required Boundaries Default     delay  delay Object to define a delay model. ✓ Yes None None   transmission  transmission Object to define the properties of a transmission. ✓ Yes None None   usableCapacity number The usableCapacity configures the ratio of the overall downlink capacity allowed to be used. ✓ Yes [0, 1] None    ","date":-62135596800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":-62135596800,"objectID":"363f152566a6299e87f2b3255e9dfe57","permalink":"https://www.eclipse.org/mosaic/docs/mosaic_configuration/cell_region_config/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mosaic/docs/mosaic_configuration/cell_region_config/","section":"docs","summary":"You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCRegionSchema Schema describing the JSON file structure for the regional networks configuration.","tags":null,"title":"Cell Simulator – Region Configuration","type":"docs"},{"authors":null,"categories":null,"content":" You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCSumoScheme Schema describing the JSON file structure for the SUMO configuration.\nProperties\n    Type Description Required Boundaries Default     updateInterval string\nnumber The Interval after which positions are published. If defined as a number, then the default unit is ms. Alternatively this can be defined as a string to include the unit of measurement (e.g. \u0026lsquo;1 s\u0026rsquo;). Define the size of one simulation step in sumo. No None 1000   sumoConfigurationFile string Name of the main SUMO scenario configuration (*.sumocfg). If this member equals null, the SUMO ambassador will try to find a \u0026lsquo;.sumocfg\u0026rsquo; file. No None None   exitOnInsertionError boolean If too many vehicles try to enter the simulation, SUMO might skip some vehicles and tries to enter them later again. This behavior can lead to wrong simulation results. This parameter defines, if the ambassador should try to continue the simulation in such cases. Quit SUMO, if an error occurs while inserting a new vehicle (e.g. due to high vehicle densities) (recommended: true). No None true   additionalSumoParameters string Add additional parameters to the SUMO start command. Set a particular seed for the random number generator. By using different values you can have different but still reproducible simulation runs. Ignore possible waiting times by setting time-to-teleport to 0. This avoids unmoved vehicles (in our case also RSUs) being removed from simulation. No None --time-to-teleport 0 --seed 100000   trafficFlowMeasurementWindowInS integer Defines the time window in seconds in which vehicle counts on induction loops should be aggregated to traffic flow. The value should be given in veh/h. No [1, +$\\infty$] 300   timeGapOffset number This offset is added to all time-gap related parametrizations of vehicles (e.g. declaring vehicle types to SUMO, changing time-gap/reaction time during simulation). This could be helpful as IDM should be parametrized with lower time gaps to achieve specific time gap values. No None 0   subscribeToAllVehicles boolean If set to true all vehicles will be subscribed. If set to false only vehicles with applications mapped to them will be subscribed. No None true   subscriptions string[] An optional list of subscriptions for each vehicle in the simulation. The less subscriptions given, the faster the simulation. Per default (if this list is set to null), all subscriptions are activated. Please note, that some components expect specific information, such as the road position. If this information is not subscribed, these components may fail. No None None   trafficSignLaneWidth number The default lane width to be used when adding traffic signs per lane (only relevant when using SUMO-GUI) No [0.1, +$\\infty$] 3.2   highlights string[] Configure to highlight a vehicle in the GUI if it\u0026rsquo;s performing a route or lane change, e.g. for debugging purposes (only relevant when using SUMO-GUI). No None None   additionalVehicleTypeParameters object Allows to configure specialised vType parameters, which can\u0026rsquo;t be configured via mapping (e.g. parameters for the lane change model of vehicles). The key of this object has to match with the name of a protype defined in the mapping configuration. No None None    Further property restrictions:\n\nCSumoScheme.additionalVehicleTypeParameters  Type of each property: additionalVehicleType   \nadditionalVehicleType Object to define a specialised vType.\nThe following additional properties are allowed:\n  additionalParameter   \nadditionalParameter The vehicle parameter.\n","date":-62135596800,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":-62135596800,"objectID":"04f8a0e4239211b6023ba30854186581","permalink":"https://www.eclipse.org/mosaic/docs/mosaic_configuration/sumo_config/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mosaic/docs/mosaic_configuration/sumo_config/","section":"docs","summary":"You can use a Readable Unit anywhere where you have the option of:\n number or string integer or string     \nCSumoScheme Schema describing the JSON file structure for the SUMO configuration.","tags":null,"title":"SUMO Configuration","type":"docs"},{"authors":null,"categories":null,"content":"This online documentation provides detailed information for the latest release of Eclipse MOSAIC. Some details may deviate, however, as we constantly keep this documentation in sync with the current main branch of our  GitHub repository.\nThis documentation is accompanied by our tutorials. Generally, it is recommended to read the documentation first, especially the sections on How To Get Started and Simulator Overview. For external simulators like Eclipse SUMO, OMNeT++ / INET or ns-3, the according project websites contain more exhaustive information, of course.\n Our tutorials are intended for step-by-step practical learning. It should be possible to start them right away without prior experience with Eclipse MOSAIC. However, for several aspects, the documentation should be consulted at least in parallel.\n   The search allows jumping directly to specific topics in the documentation.\n  1.\u0026nbsp; Getting Started Download and installation.Learn more    2.\u0026nbsp; Visualization Visualize and evaluate simulation results.Learn more    3.\u0026nbsp; Simulators Configure external and integrated simulators.Learn more    4.\u0026nbsp; Building Scenarios Build your own simulation scenarios.Learn more    5.\u0026nbsp; Create Applications Develop applications for the Application Simulator.Learn more    6.\u0026nbsp; Extending Eclipse MOSAIC Extend Eclipse MOSAIC.Learn more    7.\u0026nbsp; MOSAIC Configuration Technical documentation, such as Javadoc.Learn more    8.\u0026nbsp; API Documentation Technical documentation, such as Javadoc.Learn more     ","date":1596672000,"expirydate":-62135596800,"kind":"section","lang":"en","lastmod":1596672000,"objectID":"4cdd37113783e47641dd300543c94e1b","permalink":"https://www.eclipse.org/mosaic/docs/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mosaic/docs/","section":"docs","summary":"This online documentation provides detailed information for the latest release of Eclipse MOSAIC. Some details may deviate, however, as we constantly keep this documentation in sync with the current main branch of our  GitHub repository.","tags":null,"title":"Eclipse MOSAIC Documentation","type":"docs"},{"authors":null,"categories":null,"content":"Eclipse MOSAIC has different classes, which allow you to define the network type and the specific area where the communication should occur. Communication can be achieved with external network simulators (, ns-3) or one of the built-in communication simulators SNS or Eclipse MOSAIC Cell. Furthermore, for a better understanding it is important to consider the network types of Eclipse MOSAIC in more detail.\n Cellular Communication Ad-hoc Communication  Depending on the needs of the application, there are different approaches to solve the communication issue in Eclipse MOSAIC simulations. However, a distinction must be made between inter vehicle communication and Vehicle-to-X communication. Also, it is possible to modify the selected communication mode dependent on requirements.\nGenerally, the following modes are available based on network:\nCellular Communication\n Geobroadcast Geocast Topocast  Ad-hoc Communication\n Geobroadcast Geocast Topobroadcast Topocast   Cellular Communication The cellular network is known from wireless mobile communication and the principle is to divide the entire geographic area into several smaller parts called \u0026ldquo;cells\u0026rdquo;. Each cell has a fixed-location transceiver with a coverage ratio.\nEclipse MOSAIC enables the communication with all the existing vehicles via Geobroadcast mode or direct communication via Geocast in a specific area (circular, rectangular). In contrast, the Topocast mode is not restricted to a specific area.\nCellular Geobroadcast The principle function of the Geobroadcast is to communicate with all entities within a geographical area. Eclipse MOSAIC offers the possibility to configure a specific geographical area which can be either a circular or a rectangular area.\nThe following figure illustrates a vehicle veh_2 which is communicating with the other vehicles(veh_1, veh_3) within a radius R.\n Illustration of Geobroadcast in a spezific circular area   A circular communication area can be defined with the geoBroadCast(GeoCircle geoCircle) from an Eclipse MOSAIC application, as shown below:\nGeoCircle transmissionArea = new GeoCircle(GeoPoint.latlon(52.5, 13.2), 3000); MessageRouting routing = getOs().getCellModule().createMessageRouting().geoBroadCast(transmissionArea); getOs().getCellModule().sendV2XMessage(new MyV2XMessage(routing));  A rectangular destination area can be defined similarly:\nGeoPoint pointA = GeoPoint.latlon(52.51355, 13.22000); GeoPoint pointB = GeoPoint.latlon(52.52000, 13.21000); GeoRectangle transmissionArea = new GeoRectangle(pointA, pointB); MessageRouting routing = getOs().getCellModule().createMessageRouting().geoBroadCast(transmissionArea); getOs().getCellModule().sendV2XMessage(new MyV2XMessage(routing));  Cellular Geocast Compared to Geobroadcasting, a Geocast addresses a receiver with an unique address. Addressing can be in the form of an IP-Address or a receiver-ID (e.g. veh_0). Again, the communication area can be configured as circular or rectangular.\nAssume, the veh_1 has a message which is addressed to veh_2. In order to send the message, veh_1 first examines whether the vehicle with ID veh_2 is located within the transmission area. If this is the case, the message will be transmitted. In figure below is this situation illustrated.\n Cellular Geocast to address a receiver within a defined area   The following methods are provided for the configuring the transmission area (Circle or Rectangle) and the addressing to the receiver(hostname or ip address).\n geoCast(GeoCircle geoCircle, String receiverName)  geoCast(GeoRectangle geoRectangle, String receiverName) geoCast(GeoCircle geoCircle, byte[] ipAddress) geoCast(GeoRectangle geoRectangle, byte[] ipAddress)  GeoCircle transmissionArea = new GeoCircle( GeoPoint.latlon(52.5, 13.2), 3000); String receiverName = \u0026quot;veh_0\u0026quot;; MessageRouting routing = getOs().getCellModule().createMessageRouting().geoCast(transmissionArea, receiverName); getOs().getCellModule().sendV2XMessage(new MyV2XMessage(routing));  Cellular Topocast Compared to Geocast or Geobroadcast, the Topocast is totally independent of geographical conditions and the addressing can be in the form of an IP-Address or a receiver-ID.\nThe next figure illustrates how the veh_0 is communicating with veh_1 in Topocast mode.\n Topocast mode for direct addressing without geographical constraints   The code example below shows how we can configure the requirements of the communication in Topocast mode.\nString receiverName = \u0026quot;veh_0\u0026quot;; MessageRouting routing = getOs().getCellModule().createMessageRouting().topoCast(receiverName); getOs().getCellModule().sendV2XMessage(new MyV2XMessage(routing));  Setting Protocol types By default, all cell messages use UDP, however you can set the protocol using the protocol(...) method of the MessageRoutingBuilder:\nString receiverName = \u0026quot;veh_0\u0026quot;; MessageRouting routing = getOs().getCellModule().createMessageRouting() .protocol(Protocoltype.TCP) .topoCast(receiverName); getOs().getCellModule().sendV2XMessage(new MyV2XMessage(routing));   Ad-hoc Communication The Ad-hoc network does not rely on a pre-existing infrastructure. Provided that vehicles are equipped with Ad-hoc modules, they are able to communicate with each other dynamically. In case of a sufficient number of Ad-hoc equipped vehicles, a message can be transferred via hops quickly over a long distance.\nEclipse MOSAIC also enables the communication via a specific Ad-hoc channel within the wireless Ad-hoc network. However, the Ad-hoc channels for vehicular communication are limited and standardized by the IEEE 802.11p. The licensed frequency band 5.9 GHz (5.85-5.925 GHz) for Intelligent Transportation Systems(ITS) will be used as Ad-hoc channels.\nThe following table shows the possible channels on the 5.9 GHz band used for V2X communication.\n   Channel Number 0 1 2 3 4 5 6     Channel Name SCH1 SCH2 SCH3 CCH SCH4 SCH5 SCH6   Frequency Band 5.86 5.87 5.88 5.89 5.9 5.91 5.92    Configuring AdHoc Capabilities The first step to enable your application to use Ad hoc capabilities, is to make sure it extends the AbstractSimulationUnit-class or one of its child-classes (e.g. VehicleUnit, ChargingStationUnit) found in package org.eclipse.mosaic.fed.application.ambassador.simulation. Additionally, if you want your application to act upon the reception or transmission of messages, make sure it implements the interface CommunicationApplication.\nOnce this is done, make sure to configure and enable the AdHoc-module in your application. Below is an example configuration taken from the Tiergarten-tutorial. Instead of configuring the .power(...)[mW] it is also possible to configure a .distance(...)[m].\n// Example of AdHocConfiguration (see TiergartenVehicle.java) @Override public void onStartup() { getOs().getAdHocModule().enable(new AdHocModuleConfiguration() .addRadio() .channel(AdHocChannel.CCH) .power(50) .create()); }  Ad-hoc Topobroadcast In Topobroadcast mode, the communication between vehicles is regardless of the geographic conditions. However, the communicating entities must be operated on the same Ad-hoc channel and there are two options to use the Topobroadcast:\n Singlehop Multihop  Singlehop approach in Topobroadcast For Singlehop, it is not necessary to specify the number of hops explicitly which indicates the lifespan of a message, because in Singlehop, any message has a lifespan of hop = 1. Moreover, Eclipse MOSAIC allows to use the default method topoBroadCast() which automatically assigns a Control Channel (CCH) for the simulation entity and a lifespan based on the Singlehop principle. Alternatively you can use the non-default method topoBroadCast(AdHocChannel) in order to specify the Ad-hoc channel.\nBelow are some configuration examples of the default addressing method topoBroadCast() and non-default addressing method topoBroadCast(AdHocChannel).\nMessageRouting routing = getOs().getAdHocModule().createMessageRouting().topoBroadCast(); getOs().getAdHocModule().sendV2XMessage(new MyV2XMessage(routing));  AdHocChannel commonChannel = AdHocChannel.SCH1; MessageRouting routing = getOs().getAdHocModule().createMessageRouting().topoBroadCast(commonChannel); getOs().getAdHocModule().sendV2XMessage(new MyV2XMessage(routing));  The following figure shows a simplified model based on the Singlehop principle. The veh_1 sends messages to all simulation entites(RSU, veh_2) that are using the same Ad-hoc channel. After transmission, the message can no longer be forwarded by the receiver.\n Overview Singlehop with specified Ad-hoc channel   Multihop approach in Topobroadcast In Multihop, the lifespan (amount of hops) of a message can be specified, allowing larger communication distances.\nThe following figure shows a Multihop example with a data package D (M, h = 2) from the vehicle veh_0 which contains a message M and a hop number h = 2. Assuming that a lot of simulation entities are using the same Ad-hoc channel the message can be forwarded over a along distance. After each forward the hop number will be incremented by 1. Since the hop amount was set to 2, the forwarding will stop after 2 increments.\n Overview Multihop principle   The next code snippet shows a configuration example with an Ad-hoc channel and a message lifespan hops = 2.\nAdHocChannel commonChannel = AdHocChannel.SCH1; int hops = 2; MessageRouting routing = getOs().getAdHocModule().createMessageRouting().topoBroadCast(commonChannel, hops); getOs().getAdHocModule().sendV2XMessage(new MyV2XMessage(routing));   In order to use the Multihop approach in OMNeT++ and ns-3 provided by Eclipse MOSAIC, its necessary to implement a routing protocol in network simulators (OMNeT++, ns-3). But the built in communication simulator SNS includes a simple routing protocol “Flooding”.\n  Ad-hoc Topocast In addition to the Topobroadcast, the communication in Topocast mode will be addressed explicitly to the recipient and the addressing can be done either through receiver name (vehicle-ID e.g. veh_0) or the IP-Address of the vehicle.\nfinal byte[] ipv4Address = {127,36,50,4}; AdHocChannel commonChannel = AdHocChannel.SCH1; int hops = 2; MessageRouting routing = getOs().getAdHocModule().createMessageRouting().topoCast(ipv4Address, hops, commonChannel); getOs().getAdHocModule().sendV2XMessage(new MyV2XMessage(routing));  Ad-hoc Geobroadcast In contrast to Cellular Network above, the simulation entities act as active communication part (transmitter and receiver) and all simulation entities within range are getting messages in Geobroadcast mode.\nAs example in the following illustration, The vehicles veh_0, veh_2, veh_3 and the RSU are Ad-hoc equipped and there is no vehicle in the communication range of RSU, therefore a hop is not possible to next vehicle veh_0. But the vehicles veh_2 and veh_3 are able to communicate with each other.\n Principle of Ad-hoc Geobroadcast mode   With the methods\n geoBroadCast(GeoCircle geoCircle) geoBroadCast(GeoRectangle geoRectangle)  of the Eclipse MOSAIC class AdHocMessageRoutingBuilder ,we are able, to configure the required area as a circle or a rectangle.\nGeoPoint center = GeoPoint.latlon(52.5, 13.2); GeoCircle adHocModule = new GeoCircle(center, 3000); MessageRouting routing = getOs().getAdHocModule().createMessageRouting().geoBroadCast(adHocModule); getOs().getAdHocModule().sendV2XMessage(new MyV2XMessage(routing));  Analogous to the examples above, we can also configure the transmission area as a rectangle.\nThe next code snippet illustrates a possible configuration with a rectangular transmission area and a specified Ad-hoc channel.\nGeoPoint pointA = GeoPoint.latlon(52.51355, 13.22000); GeoPoint pointB = GeoPoint.latlon(52.52000, 13.21000); final double radius = 3000.0; GeoRectangle transmissionArea = new GeoRectangle(pointA, pointB); MessageRouting routing = getOs().getAdHocModule().createMessageRouting().geoBroadCast(transmissionArea, AdHocChannel.SCH1); getOs().getCellModule().sendV2XMessage(new MyV2XMessage(routing));  Ad-hoc Geocast The class AdHocMessageRoutingBuilder only has one method for Geocasting mode, geoCast(DestinationAddress destinationAddress, AdHocChannel adHocChannel). Communication is possible if the IP-address of receiver is known and both (receiver and transmitter) are on the same Ad-hoc channel.\n In this context the name Geocast is misleading, because a geological condition is not necessary.\n  As you can see in the next picture, the RSU uses the Ad-hoc channel SCH1 and several vehicles use different Ad-hoc channels. Assuming the RSU tries to send a message to veh_1 and has knowledge about the IP-Address of veh_1, if the vehicle veh_1 also uses the same channel SCH1, the transmission will be completed successfully.\n Ad-hoc Geocast communication between entities using the same channel   Below you can see a possible configuration.\nfinal byte[] ipv4Address = {127,36,50,4}; DestinationAddress destAddress = new DestinationAddress(ipv4Address); AdHocChannel commonChannel = AdHocChannel.SCH1; MessageRouting routing = getOs().getAdHocModule().createMessageRouting().geoCast(destAddress, commonChannel); getOs().getAdHocModule().sendV2XMessage(new MyV2XMessage(routing));  CAM - Implementation A Cooperative Awareness Messages (CAM) consists of four parts:\n Header with generic information MessageBody ServiceList TaggedValue list  First, generic information like protocol version, creation time stamp are submitted. Normally this data set follows a network beacon, which already contains data like position and speed. Nevertheless, this functionality must be implemented in the network layer, that means in the network simulator. At the moment this is not supported and is therefore compensated in the next message part, the message body. The body can contain either RSU or Vehicle awareness data. In the first case, only the RSU type is submitted, but this probably changes with a new CAM specification. In the second case, we provide date like vehicle width, length, position, speed, type and heading. The specification is not completely implemented, especially acceleration data and light, brake status are missing. The third part of the CAM specification, the service list, is also not implemented. This will probably change, when a list of services is defined by the ETSI. Last but not least a message contains a tagged list, a key value map with optional data. This is fully implemented and is used for our traffic light CAM messages, which provide the traffic light status in such a list.\nUser defined tagged values If you are required to exchange custom data within CAMs, the field UserTaggedValue can be used. For adding such data to the CAM, the application needs to implement the method beforeGetAndResetUserTaggedValue() from the CommunicationApplication interface. If a CAM is about to be sent, the custom data can be set using the getOs().setUserTaggedValue(byte[]) method. The receiver can simple access the data by accessing the field directly from the received CAM message:\nbyte[] value = cam.getUserTaggedValue (); if (value != null) { // read user tagged value} }  Timing Requirements CAMs are generated by the CAM Management and passed to lower layers when any of following rules apply:\n maximum time interval between CAM generations: $1s$; minimum time interval between CAM generations: $0.1s$; generate CAM when absolute difference between current heading (towards North) and last CAM heading \u0026gt; $4 deg$; generate CAM when distance between current position and last CAM position \u0026gt; $5m$ generate CAM when absolute difference between current speed and last CAM speed \u0026gt; $1ms$; These rules are checked latest every $100ms$;  ","date":1557010800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1557010800,"objectID":"d32a5f22c5ae5d143ef2bc4c35a326c8","permalink":"https://www.eclipse.org/mosaic/docs/develop_applications/communication/","publishdate":"2019-05-05T00:00:00+01:00","relpermalink":"/mosaic/docs/develop_applications/communication/","section":"docs","summary":"Eclipse MOSAIC has different classes, which allow you to define the network type and the specific area where the communication should occur. Communication can be achieved with external network simulators (, ns-3) or one of the built-in communication simulators SNS or Eclipse MOSAIC Cell.","tags":null,"title":"Communication in Applications","type":"docs"},{"authors":null,"categories":null,"content":"The different modules of the Application Simulator communicate over events that are triggered at a specific simulation time. The following classes and interfaces model theses events.\nEvent The class Event contains the information that is necessary to process an event. An event describes when it should be processed and which information is processed. Moreover an event has an assigned priority.\nAttributes of Event The class Event contains the following attributes:\n long time: defines the time when the execution of the event is triggered. long nice: defines the priority of the event. When multiple events are scheduled for the sametime, the events are ordered in ascending order. List\u0026lt;EventProcessor\u0026gt; processors: is a list of components that shall process the event. Object resource: is an object that contains additional information designated for the processor of the event. The resource can be any object.  Methods of Event  Event(): There are multiple constructors for Event with different parameters. Every constructor sets default values for the attributes that are not defined by the arguments of the constructor. Event newTime(long time): allows the creation of a new event with a new execution time based String getResourceSimpleClassName(): returns the class name of the resource as String. int compareTo(Event event): implements the standardized Java interface Comparable. Toorder the events, first the time of the event is evaluated. In case the times are equal, the priority of the events is compared.  Interface EventManager The interface EventManager defines the method void addEvent(Event event) that needs to be implemented to add an event to the execution.\nInterface EventScheduler The interface EventScheduler extends the interface EventManager and is used for classes that trigger events.\nMethods of EventScheduler  boolean isEmpty(): returns true if the scheduler contains no elements, otherwise it returns false. long getNextEventTime(): returns the time of the next event. long getScheduledTime(): returns the time when the last event has been executed. List\u0026lt;Event\u0026gt; scheduleEvents(long time): returns a list of objects that are scheduled for a certain simulation time. Set\u0026lt;Event\u0026gt; getAllEvents(): returns a set of all events that are considered by the scheduler.  EventSchedulerImpl The class EventSchedulerImpl is an implementation of the interface EventScheduler.\nInterface EventProcessor The interface EventProcessor defines how the execution module gets the events. The execution module therefore has to implement the following methods:\n void processEvent(Event event): The module processes the event. boolean canProcessEvent(): returns true when the module is currently able to process new events, otherwise it returns false.  InterceptedEvent Class EventInterceptor In some situation it is useful to intercept events before they actually reach the intended processors. By intercepting the events it is possible to apply further monitoring and to filter which events the event processors receive. The class EventInterceptor is used to construct objects of the type InterceptedEvent. In the constructor it is possible to specify an EventManager that manages the intercepted events. Moreover, objects of the type EventProcessor can be specified that shall process the intercepted events.\nClass InterceptedEvent The class InterceptedEvents extends the class Event. It is used to provide type safe allocations of events that shall be intercepted.\n","date":1565481600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1565481600,"objectID":"77fcc6d6f359287fbc8c37d7e6c54048","permalink":"https://www.eclipse.org/mosaic/docs/develop_applications/event_scheduler/","publishdate":"2019-08-11T00:00:00Z","relpermalink":"/mosaic/docs/develop_applications/event_scheduler/","section":"docs","summary":"The different modules of the Application Simulator communicate over events that are triggered at a specific simulation time. The following classes and interfaces model theses events.\nEvent The class Event contains the information that is necessary to process an event.","tags":null,"title":"Event Scheduling","type":"docs"},{"authors":null,"categories":null,"content":"Each scenario to be simulated with Eclipse MOSAIC requires a database which contains information about the road infrastructure and routes the vehicles drive on. This information is used by various federates. For example, the SUMO federate needs to know initial routes for vehicles, and the Application Simulator requires detailed information about the road infrastructure to provide applications with methods for route calculation. For this purpose, an embedded SQLite database is used which is placed in the application folder of the scenario. This database consists of the following tables:\nDatabase tables    Database Name Description     Node Contains all Nodes of the road network such as junctions and nodes describing the geometry of a road. Each node is identified by an unique ID (long).(refer to http://wiki.openstreetmap.org/wiki/Node)   Way Provides various properties for each way of the road network.(refer to http://wiki.openstreetmap.org/wiki/Way   WayConsistsOf Provides a list of nodes for each way of the road network.   Connection Contains a list of all connections of the road network including the way it originally is part of. Each connection describes an directed edge between two junctions in the road network.   ConnectionConsistsOf Provides a list of nodes each connection consists of.   Restriction Provides information about turn restrictions. Each turn restriction is described by a from-connection, a via-node, and a to-connection. This data is used for route calculation purposes.   TrafficSignals Contains detailed information about traffic lights and their signalling program. Currently not used.   Route Contains a list of all routes known for the simulation scenario. All routes referenced in the Mapping configuration must be presentin this table.   Building Corner Wall Provides information about buildings alongside the road network, e.g. for visualization purposes or sophisticated communication simulation models.   Version Contains the version of the Eclipse MOSAIC installation which was initially used to create the database.    Road network model This section describes the model of the road network used by various components of Eclipse MOSAIC. In the next figure various nodes and connections can be seen. A node is either a junction or describes the geometry of a road. A connection is a directed edge between two junction nodes. That also means, that two separate connections exists for a road segment which can be traversed in both directions. Each connection consists of at least two nodes (start and end junction node). Between those nodes, other nodes can exist which describe the curvature of the road segment. Furthermore, each connection has a reference to its originating way, which may consist of various connections. A way contains further properties, such as the maximum speed or the type of the road.\n Nodes and connections of the road network   Nodes and ways are identified by unique IDs derived from the base OSM network file. Connections, however, are not part of the OSM standard and their identifiers are generated during the import. Each connection ID consists of three parts (using the string pattern aaa_bbb_ccc):\n aaa - ID of the originating way bbb - ID of the node the connection starts at. ccc - ID of the node the connection ends in.   ID of connection in road network   Some components of Eclipse MOSAIC need to identify further parts of the road network, such as one edge between two nodes, or one specific lane of one edge. Therefore, the following objects are identified as following:\nEdges are described by one start and one end node. The identifier of an edge consists of two parts (using the string pattern aaa_bbb_ccc_ddd):\n aaa_bbb_ccc - ID the connection the edge belongs to. ddd - ID of the node the edge starts at.   Structure of the Edge-ID   Lanes are described by an edge and a lane index. The identifier of a lane consists of two parts (using the string pattern aaa_bbb_ccc_ddd_e):\n aaa_bbb_ccc_ddd - ID the edge the lane belongs to. e - Index of the lane, starting by 0 (leftmost lane).   Structure of the Lane-ID   ","date":1565049600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1565049600,"objectID":"1d92f8a189d6829395465481d4b2ddad","permalink":"https://www.eclipse.org/mosaic/docs/develop_applications/road_traffic/","publishdate":"2019-08-06T00:00:00Z","relpermalink":"/mosaic/docs/develop_applications/road_traffic/","section":"docs","summary":"Each scenario to be simulated with Eclipse MOSAIC requires a database which contains information about the road infrastructure and routes the vehicles drive on. This information is used by various federates.","tags":null,"title":"Scenario Database","type":"docs"},{"authors":null,"categories":null,"content":"","date"