@@ -163,10 +163,11 @@ Requirements with regards to an efficient communication are grouped and categori
oneM2M is most beneficially able to support an efficient communication in the area of the IoT Device Application, while other areas, like required support of "3GPP Connection Efficiency Features" can be considered out of scope of oneM2M, and hence out of scope of this WI.
With regards to "IoT Device Application Requirements", GSMA TS.34 <ahref="#_ref_1">[1]</a> differentiates further between:
1. Monolithic IoT Device Application Requirements: Those requirements are applicable for devices without an embedded Service layer and hence are out of scope oneM2M anyway.
2. Tiered IoT Device Applications Requirements: Those requirements are applicable for applications providing the required functionality according to GSMA TS.34 <ahref="#_ref_1">[1]</a> , cooperatively together with the embedded Service layer.
.
3. IoT Embedded Service Layer Requirements: Those requirements are applicable for the embedded Service layer, providing the required functionality according to GSMA TS.34 [i.1]
...
...
@@ -177,7 +178,8 @@ The considered Requirements out of GSMA TS.34 <a href="#_ref_1">[1]</a> in the
## 5.2 IoT Device Requirements
**Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href="#_ref_1">[1]</a> **
**Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href="#_ref_1">[1]</a>**
| Requirement ID | Description from GSMA TS 34 <ahref="#_ref_1">[1]</a> | Reference clause |
| ------ | ------ | ------ |
|TS.34_3.0_REQ_001|The IoT Device SHOULD conform to all IoT Device Application requirements defined in TS.34, section 4.| 5.4 |
...
...
@@ -199,6 +201,7 @@ The remainder of this section is organized by the components shown in figure 5.3
In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an application are captured in table 5.4-1.
**Table 5.4 1: Tiered IoT Device Requirements**
| Requirement ID | Description from GSMA TS 34 <ahref="#_ref_1">[1]</a> | Reference clause |
| ------ | ------ | ------ |
|TS.34_4.1_REQ_001|If data speed and latency is critical to the IoT Service the IoT Device Application should be able to retrieve mobile network speed and connection quality information from the IoT Embedded Service Layer in order to request the appropriate quality of content from the IoT Service Platform.|See clause 6.1 |