@@ -56,12 +56,12 @@ b.) needs to read, understand and follow such guidelines.
This work aims to check and enhance oneM2M as an Embedded Service Layer in a way that the requirements formulated in GSMA TS.34 [i.1] are taken into account and Applications developed not considering requirements in GSMA TS.34 [i.1], do not create adverse effects in the network, because the oneM2M as Embedded Service Layer is shielding the network from badly behaving applications.
GSMA TS. 34 [i.1] is already referring towards an evolution of an IoT Service Architecture, where the IoT Device Applications are becoming disaggregated from an Embedded Service Layer. Such an Embedded Service Layer is providing several generic IoT functionalities (e.g. device management, security, location, application framework…). The common service layer specified by oneM2M complies to this IoT Service Architecture.
FIGURE
Applications being deployed on top of a common service layer are less critical to the network, because the common service layer takes over a protection role for the network. Inefficient or even harmful activities of applications would be prevented upfront and can’t hit the network. On the other hand, oneM2M provides functionality for the applications, e.g. scheduling transmissions according to the service needs.
The recommended evolved architecture in GSMA TS.34 [i.1] (refer Figure 1X) aligns well with the oneM2M architecture shown in Fig 1-1.
FIGURE
oneM2M with the CSE functionality in between the IoT Application and the network connectivity, is well suited to enforce the requirements being addressed in GSMA TS.34 [i.1], and hence protect the network from unwanted signalling floods and enforces an efficient communication, even if the Application (AE) has been created without GSMA TS.34 [i.1] knowledge or compliance.
This TR is analysing which functionalities recommended by GSMA TS.34 [i.1] being in scope of an Embedded Service Layer are already covered by oneM2M functionality (e.g. like in CDMH), and which GSMA TS.34 [i.1] functionality is missing from oneM2M, to identify it and enhance oneM2M accordingly to meet the GSMA TS.34 [i.1] recommendations.
...
...
@@ -143,7 +143,7 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in
## 5.1 Introduction
GSMA TS.34 [i.1] represents a guideline and giving requirements for whole IoT Device, as defined in Figure X to ensure an efficient connection.
FIGURE
![Figure 5.1-1: Generalised IoT Device Architecture according to GSMA TS.34 [i.1]](media/Fig3.png)
Requirements with regards to an efficient communication are grouped and categorized in TS.34 [i.1]. E.g. requirements are formulated for the following areas:
...
...
@@ -181,7 +181,7 @@ The considered Requirements out of GSMA TS.34 [i.1] in the context of oneM2M are
This clause is derived from GSMA TS.34 [i.1], clause 4. Two architectures are described in GSMA TS.34 [i.1], where the IoT Device application can be a monolithic application that meets all the requirements in clause 4.0 or an evolved architecture that separates the device application requirements into clause 4.1 and the IoT embedded service layer requirements into clause 4.2. This technical report addresses the evolved architecture.
The remainder of this section is organized by the components shown in figure 5.3-1.
FIGURE
