# Management Platforms and Protocols for Internet of Things: A Survey
## 9 Performance Evaluation, Discussion, and Open Issues  
Main characteristics are based on studied management solutions, a qualitative study is performed to characterize management types and technologies used in the most relevant management protocols and platforms. Tables 5 and 6 summarize the main protocols characteristics considering their standardization resources, data, transport stacks, among others. The IoT Network Management protocols (Table 5) were originated by the IETF for management of connected devices. The SNMP protocol was the basis for the creation of other protocols such as IoT-PIC and LNMP. Its simplicity in data modeling makes it a fast and a simple configuration protocol. NETCONF was created to be the successor of SNMP using the XML standard for request and response messages. The secure connection transport on SNMP is relevant because its ease of configuration in some scenarios. With the emergence of SDNs, new network management protocols have been \begin{table}
\begin{tabular}{l l c c c c} \hline \hline  & **SNMP/LNMP** & **NETCONF** & **IoT-PIC/XMPP** & **OVSDB** & **IEEE 1905** \\ \hline Standard & IETF & IETF & IETF & IETF & IEEE \\ Resource & OIDs & Paths & URLs & URLs & URLs \\ Data & SMI & YANG & WSDL & JSON & WSDL \\ Modeling & & & & & \\ Encoding & BER & XML & XML & JSON & XML \\ Transport & UDP & SSH/TCP & HTTP, & HTTP, & HTTP, \\ Stack & & & Web API & SSL/TLS & Web API \\ \hline \hline \end{tabular}
\end{table} 
Table 5: Main characteristics comparison of the IoT Network Management protocols. Figure 29: Illustration of the Carriots architecture. proposed, such as OVSDB. It uses JSON technology to expose its devices and network data for the systematic integration of applications. The IoT Device Management protocols (Table 6) were developed with Internet standards by the IETF. The TLS protocol and SSL protocol are used to secure transport of the information in the network as HTTPS and SSH protocols. In reference to the data modeling and encoding, the OVSDB and COMAN protocols use current Web technologies, such as XML and JSON, that expose network and device information to access other applications through a user name and password. Table 7 summarizes a comparison among the most relevant IoT Network Management platforms, considering IMPReSS, OpenNMS, OpenDayLight, and Zabbix. All the platforms have Web user-interfaces and open-source technologies, except IMPReSS (which was finalized in 2016). OpenDaylight supports more IoT Network Management protocols compared to other previously researched solutions. Zabbix is a popular platform for monitoring and management networks and differ in XMPP and NETCONF protocol with OpenNMS. Table 8 summarizes a comparison among the most relevant IoT Device Management platforms, considering Xively, OneM2M, ManIoT, and other important solutions, regarding several important protocols and types of management approaches. Despite attending to most requirements, SmartThings believe that supporting widely used protocols and Web technologies is enough to mitigate the problem of heterogeneity devices. However, support for other protocols is an important requirement for Carriots and Xively platforms. Other requirements (like context-awareness and dynamic adaptation) are barely discussed. Context-awareness is an approach to the inclusion of semantic data in a platform, e.g., location and collection time. \begin{table}
\begin{tabular}{c c c c c c} \hline \hline  & **CoAP** & **OMA-DM L2M2M** & **OMA** & **TMP** & **CWMP** \\ \hline Standard & IETF & IETF & IETF & IETF & Broadband Forum \\ Resource & URLs & URLs & URLs & URLs & URLs \\ Data Modeling & JSON & XML, JSON & XML, JSON & WSDL & XML \\ Encoding & JSON & XML, JSON & XML, JSON & XML & WSDL \\ Transport & UDP & UDP & UDP & HTTP & HTTP \\ Stack & HTTPS & HTTPS & HTTPS & HTTPS & Web API & SSH/TCP \\ SSH/TCP & SSH/TCP & SSH/TCP & & & \\ \hline \hline \end{tabular}
\end{table} 
Table 6: Main characteristics comparison of the IoT Device Management protocols.