diff --git a/TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md b/TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md
index 0a3a6f66cf78ac0b24dbcfd4f6a2ce64cd0de1c7..42f865f97232d0f2ba5f39b31da6ad73f428c3d6 100644
--- a/TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md
+++ b/TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md
@@ -442,7 +442,91 @@ As mentioned above, the underlying distribution is largely transparent to the Co
 
 # 6 Assessment of additional functionality brought by NGSI-LD
 
-<mark>Based on the introduction in clause 5, description of the additional functionality that the integration of NGSI-LD API and its related functionality can bring to the oneM2M standard, including the resulting integrated use cases. </mark>
+## 6.1 Introduction
+
+Based on the general introduction of NGSI-LD in clause 5, clause 6 describes which advantages the integration of the NGSI-LD API into the oneM2M standard can bring to oneM2M applications. For this purpose, a number of use cases are analysed, highlighting the respective advantages for applications. Finally, the advantages are summarized with the goal of providing directions for further explorations of how the integration of NGSI-LD into oneM2M can be achieved, which is the focus of the following clauses.
+
+## 6.2 Use Case: Query parking sites in the vicinity (UC1)
+
+Use Case 1 (UC1) is about querying for parking sites within a given geographic area, e.g. around the current location of a car.
+Figure 6.2-1 visualizes this scenario.
+
+![UC1 - Query parking sites in the vicinity](media/UC1-query_parking_sites-visualization.png)
+
+**Figure 6.2-1: UC1 - Query parking sites in the vicinity**
+
+The basis for modelling the information required for this use case is the NGSI-LD compatible Smart Data Model<a href="#_ref_i.5">[i.5]</a> on Parking, which makes a distinction between OffStreetParking and OnStreetParking. As this distinction is not relevant for our use case, we restrict the example on a number of common NGSI-LD properties:
+- address
+- allowedVehicleType
+- availableSpotNumber
+- category
+- chargeType
+- location
+- ...
+
+The query for parking sites within a given geographic area, e.g. around the current location of a car: 
+```
+GET /ngsi-ld/v1/entities/?type=OnStreetParking,OffStreetParking&geoproperty=location&georel=near%3BmaxDistance==1000&geometry=Point&coordinates[-3.8040616,43.4631649]
+Accept: application/json
+Host: localhost:9090
+Link: <http://example.org/myContext.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"
+
+```
+It queries for all NGSI-LD Entities of type OnStreetParking or OffStreetParking, and geographically scopes it with the circle around the geographic point with coordinates -3.8040616,43.4631649 and a radius of 1000m.
+
+
+Excerpt of result:
+```
+[{
+    "id": "urn:ngsi-ld:OnStreetParking:santander:daoiz_velarde_1_5",
+    "type": "OnStreetParking",
+    "allowedVehicleType": {
+        "type": "Property",
+        "value": [
+            "car"
+        ]
+    },
+"availableSpotNumber": {
+        "type": "Property",
+        "value": 3,
+        "observedAt": "2018-09-12T12:00:00Z"
+    },
+    "category": {
+        "type": "Property",
+        "value": [
+            "blueZone",
+            "shortTerm",
+            "forDisabled"
+        ]
+    },
+    "chargeType": {
+        "type": "Property",
+        "value": [
+            "temporaryFee"
+        ]
+	...
+```
+
+The advantages for the application are the following:
+- Application can reuqest information by specifying what it needs ("parking sites in the vicinity")
+- Application gets result with a single request (unless paging is required due to number of results)
+- Application can gegographically scope the request
+
+In order to do this, the application needs to know the following:
+- Data model:
+  - type: OnStreetParking, OffStreetParking
+  - GeoProperty name: location
+- its current location
+- Root URL: localhost:9090
+
+## 6.3 Use Case: Query parking sites in the vicinity (UC2)
+
+## 6.4 Use Case: Retrieve or query agriculture parcel(s) modelled as composite digital twins (UC3)
+
+## 6.5 Use Case: Subscribe to be notified when temperature is above/below threshold in building (UC4)
+
+## 6.6 Summary of advantageous NGSI-LD functionalities
+
 
 # 7 Architectural integration of NGSI-LD into oneM2M