Updated README.md.

src/de/tud/kom/p2psim/impl/topology/views/fiveg/models/README.md

 # 5G Models
 
-This module allows to add models to each cell of the map.
+This module allows to add transmission models to each cell of the map to accomodate different behaviors of wireless network transmission technologies. It enables the user to define different models for **Latency**, **Bandwidth** and **Drop-Rate** (called *metrics*), for **Upload** and **Download** and for every **Segment**.
 
-...
+Whenever one of the metric for a client is requested every other metric is evaluated to check if one of them is overloaded such that no connection is possibile. The thresholds for the overload are defined in [`FiveGTopologyDatabase.Entry`](https://dev.kom.e-technik.tu-darmstadt.de/gitlab/simonstrator/simonstrator-peerfactsim/blob/nr/monitoring-model/src/de/tud/kom/p2psim/impl/topology/views/fiveg/ModelBasedSegmentDatabase.java#L182)
 
 ## Configuration / Setup
 
-TODO
+The models are enabled by changing the `Database` of the `FiveGTopologyView` to `ModelBasedSegmentDatabase`. For a minimal config the `ModelBasedSegmentDatabase` needs at least a model for each metric. Therefore the models are passed to the database. Each model has its specific defaults described [here](#models). In addition to that every models has parameters for `direction` (*UPLOAD*, *DOWNLOAD* or **BOTH**), `parameterType` (*BANDWIDTH*, *LATENCY* and *DROPRATE*), `segmentID` (to which segmentID this model is applied - **-1** means that it is applied to every segment) and debug (TRUE or **FALSE**). **Bold** values mark the defaults.
+
+## Examples
+
+> **IMPORTANT!** For every metric there needs to be one and *only one* default model.
+
+### General Setup
+
+Here the general setup for the model based segments is shown. The models are placed inside the database element.
+
+```xml
+<View class="de.tud.kom.p2psim.impl.topology.views.FiveGTopologyView" phy="UMTS" cloudGroups="Cloud">
+  <Database class="de.tud.kom.p2psim.impl.topology.views.fiveg.ModelBasedSegmentDatabase" enableVis="$ENABLE_VIS" gridSize="$CELL_GRID_SIZE">
+    <!-- Place model definitions here -->
+  </Database>
+</View>
+```
+
+### A default constant model for every metric
+
+```xml
+<Model class="de.tud.kom.p2psim.impl.topology.views.fiveg.models.ConstantModel" c="300" parameterType="BANDWIDTH" />
+<Model class="de.tud.kom.p2psim.impl.topology.views.fiveg.models.ConstantModel" c="5" parameterType="LATENCY" />
+<Model class="de.tud.kom.p2psim.impl.topology.views.fiveg.models.ConstantModel" c="0.1" parameterType="DROPRATE" />
+```
+
+For every cell the bandwidth is 300 EINHEIT!?, the latency 5 EINHEIT!? and droprate is 1% (0.1) in both directions.
+
+### Advanced setup
+
+```xml
+<Model class="de.tud.kom.p2psim.impl.topology.views.fiveg.models.ConstantModel" c="300" parameterType="BANDWIDTH" direction="UPLOAD" />
+<Model class="de.tud.kom.p2psim.impl.topology.views.fiveg.models.ConstantModel" c="10" parameterType="BANDWIDTH" direction="DOWNLOAD" />
+<Model class="de.tud.kom.p2psim.impl.topology.views.fiveg.models.LogarithmicModel" a="3" b="10" c="-5" d="-10" parameterType="LATENCY" />
+<Model class="de.tud.kom.p2psim.impl.topology.views.fiveg.models.ExponentialModel" parameterType="DROPRATE" />
+<Model class="de.tud.kom.p2psim.impl.topology.views.fiveg.models.CutoffModel" parameterType="BANDWIDTH" segmentID="123" debug="TRUE" />
+```
+
+Every cell has 300 EINHEIT!? upload bandwidth and 10 EINHEIT!? download bandwidth with a constant model. The latency of every cell is equal for up- and download and is based on a logarithmic model with $`a=3`$, $`b=10`$, $`c=-5`$ and $`d=-10`$. A default exponential model is applied on the latency. At last there is a cut-off model for the bandwidth for the segment with the ID `123`. It also shows the debug graph.
 
 ## Models