5.4 Tiered IoT Device Application Requirements

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 [1]	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
TS.34_4.1_REQ_002	The IoT Device Application should always be prepared to handle situations when communication requests fail, when such failure is reported by the IoT Embedded Service Layer.	See clause 6.2
TS.34_4.1_REQ_003	Each time there is a need to send data over the mobile network the IoT Device Application should classify the priority of each communication. For example, the IoT Device Application should distinguish between data that requires instantaneous transmission and delay tolerant data that could be aggregated and/or sent during non-peak hours. Such information about the priority of the communication should be communicated to the IoT Embedded Service Layer.	See below [UPDATE THIS]
TS.34_4.1_REQ_004	When an IoT Device Application does not need to perform regular data transmissions and it can tolerate some latency for its IoT Service, it should communicate this information to the IoT Embedded Service Layer so that it can use this information in its interactions with the network.	See below [UPDATE THIS]