Label-based interworking approach

TR-0076-Integrating_NGSI-LD_API_in_oneM2M.md

@@ -890,11 +890,13 @@ As oneM2M and NGSI-LD follow different approaches, a mapping is needed. This can
 
 ### 7.3.2 IPE-driven Synchronization Approaches
 
+#### 7.3.2.1 Overview
+
 ![General interworking setup between a oneM2M system and an NGSI-LD Context Broker](media/CSE_IPE_NGSI-LD_Broker.png)
 
-**Figure 7.3.2-1: General interworking setup between a oneM2M system and an NGSI-LD Context Broker**
+**Figure 7.3.2.1-1: General interworking setup between a oneM2M system and an NGSI-LD Context Broker**
 
-Figure 7.3.2-1 shows the general interworking setup between a oneM2M system and an NGSI-LD Context Broker with an IPE implementing the interworking.
+Figure 7.3.2.1-1 shows the general interworking setup between a oneM2M system and an NGSI-LD Context Broker with an IPE implementing the interworking.
 
 Depending on the use case, oneM2M data needs synchronizing to NGSI-LD context broker or NGSI-LD data needs synchronizing to oneM2M. 
 * oneM2M to NGSI-LD: This can be used when services are already implemented and data are already being stored in the oneM2M platform. The goal is for users to get data of oneM2M services using the NGSI-LD API.	
@@ -902,6 +904,26 @@ Depending on the use case, oneM2M data needs synchronizing to NGSI-LD context br
 
 Synchronization approaches duplicate data, but enable more efficient information access.
 
+In the following, the aspects of the proposed interworking approaches in CIM 022 <a href="#_ref_i.6">[i.6]</a> that are relevant for the discussion in this document are sketched. For details, please refer to <a href="#_ref_i.6">[i.6]</a>.
+
+#### 7.3.2.2 Label-based, dynamic interworking subscribe_to_be_notified_when_temperature_is_above_or_below_threshold
+
+The first approach specified in CIM 022 <a href="#_ref_i.6">[i.6]</a> is a label-based, dynamic interworking scheme. The idea is that specific labels are introduced that are used to label resources in the oneM2M system as show in Table 7.3.2.2-1.
+
+**Table 7.3.2.2-1 Interworking mapping using labels**
+
+![Interworking mapping using labels](media/Interworking-Labels-1.png)
+
+The labels identify to which NGSI-LD Entity (_Iwked-Entity-ID_) and Entity Type (_Iwked-Entity-Type_) the information contained the labelled oneM2M resource belongs. If not all information is contained in the same resource, a list of additional oneM2M resource can be provided in _Iwked-Related-Resources_.
+
+The detailed information that is needed for the mapping of the NGSI-LD Attributes is provided as a list of mapping rules in _Iwked-mapping-rule_. The information that is contained in such a mapping rule is shown in Table 7.3.2.2-2.
+
+**Table 7.3.2.2-2 Interworking mapping using labels - mapping rule**
+
+![Interworking mapping using labels - mapping rule](media/Interworking-Labels-1.png)
+
+The IPE discovers the labelled resources, retrieves the information from the labeled and identified additional resources and uses the mapping rule to create the NGSI-LD entity information that is then updated in the NGSI-LD Context Broker. Thus, the approach is uni-directional, making information originally available in the oneM2M system also available in the NGSI-LD Context Broker.
+
 
 # 8 Mapping between the information stored in oneM2M resources and the NGSI-LD information model