# IoT's Tiny Steps towards 5G: Telco's Perspective
## 2 Research Approach and Design
### Existing Classifications of IoT Applications
These devices should be of very low cost with very low energy consumption, enabling very long battery life [12]. At the same time, the amount of data generated by each device is normally very small, and very low latency is not a critical requirement [12]. Ultra-reliable MTC (uMTC) requires very high reliability and availability, and very low latency [9,12]. Low device cost and energy consumption are not as critical as they are for mMTC applications [12], and the number of devices and required data rates are relatively low [198]. \begin{table}
\begin{tabular}{c c c} \hline \hline
**Criteria for Classification** & **IoT Classes** & **References** \\ \hline \multirow{8}{*}{Domains} & (1) Transportation and logistics & \\  & (2) Healthcare & \\  & (3) Environment & \\  & (4) Personal and social & \\  & (5) Futuristic applications & \\  & (6) Food/water monitoring & \\  & (7) Living & \\  & (8) Manufacturing & \\   Domains & (9) Energy & [4, 10, 11, 12] \\  & (10) Building & \\  & (11) Industry & \\  & (12) City & \\  & (13) Security and safety & \\  & (14) Communication & \\  & (15) e-society & \\  & (16) Vehicular & \\  & (17) Sport and leisure & \\ \hline \multirow{4}{*}{Mobility and amount of dispersion} & (1) Fixed and concentrated & \\  & (2) Fixed and dispersed & \\  & (3) Mobile and concentrated & \\  & (4) Mobile and dispersed & \\ \hline \multirow{4}{*}{Delay tolerance} & (1) Elastic & \\  & (2) Hard real time & \\  & (3) Delay-adaptive & \\  & (4) Rate-adaptive & \\ \hline \multirow{4}{*}{Data reporting mode} & (1) Time-driven & \\  & (2) Query-driven & \\ \cline{1-1}  & (3) Event-driven & \\ \cline{1-1}  & (4) Continuous-based & \\ \cline{1-1}  & (5) Hybrid-driven & \\ \hline \multirow{4}{*}{Reliability, availability, and end-to-end latency} & (1) Monitoring-based and mission critical & \\ \cline{1-1}  & (2) Monitoring-based and non-mission critical & \\ \cline{1-1}  & (3) Control-oriented and mission critical & \\ \cline{1-1}  & (4) Control-oriented and non-mission critical & \\ \hline \hline Characteristics and requirements & mMTC and uMTC & [12] \\ \hline \end{tabular} Legend: IoT (Internet of Things), mMTC (massive Machine Type Communication), uMTC (ultra-reliable Machine Type Communication).  
\end{table} 
Table 2: Internet of Things (IoT) application classification—summary. The vision of a pervasive IoT requires the integration of various domains into a single and unified domain. It addresses the enabling technologies needed for these domains while taking into account the elements that form the third dimension like security, privacy, trust, and safety [11]. The current classification criteria and IoT application classes do not clearly differentiate IoT domains from IoT applications. IoT domains are usually viewed as a specific area of IoT applications that support a huge variety of use cases across industries impacting businesses and customers. Therefore, IoT domains overlap with IoT applications within existing IoT classifications. Moreover, IoT classification based on certain QoS parameters is difficult to apply from telco's perspective, because it is challenging to choose the most important parameter for the wide range of IoT applications. However, these problems need to be solved for upcoming 5G networks.