# Management Platforms and Protocols for Internet of Things: A Survey
## 4 IoT Network Management Protocols
### LoWPAN Network Management Protocol (LNMP)  
The LNMP is a management architecture suitable for 6 LoWPAN networks [50]. With LNMP architecture is possible to reduce the cost communication and, therefore, increasing the lifespan of the network. The LNMP main characteristic is to allow interoperability with SNMP. In terms of communication and complexity, the SNMP is considered impracticable due to the limited device's resources.  
This architecture (Figure 12) allows the discovery of devices in a network with help of the coordinators in the monitoring and management. The SNMP is an application layer adapted protocol to run over IPv6, so uses this protocol to the adaptation layer 6 LoWPAN [51]. The popular solution NET-SNMP [52] includes the adapted IPv4 and IPv6 for IoT network.  
Figure 11: IEEE 1905 standard network management architecture.  
Exists two successive management operations that entities within the 6 LoWPAN performed. First, Network Discovery is executed to monitor the device state in the architecture. The second step, after discovered devices, is the management of available devices.  
To discover \"live\" devices manually, intense use of the resources is needed, and thus, the Network Discovery is a procedure created for an automated network state discovery, which is necessary given the WSN characteristics for their continued deployment. In this proposal [53], the Network Discovery uses the automated monitoring of the network state distributed by a 6 LoWPAN network. The coordinators responsible to maintain the information about device state and reporting of subordinate devices has the device discovery feature. Bandwidth is a scarce resource in a sensor network and this feature reduces communication costs. The sensing and processing are usually lower than the communication cost.  
It is desirable to monitor the device's status within the 6 LoWPAN in a standard management protocol, e.g., SNMP protocols. However, the bandwidth available is a factor limited for application layer payload [54]. Therefore, SNMP is inviable due complexity of transport and communication into 6 LoWPAN networks. Nonetheless, the reuse of network protocols is a goal of the 6 LoWPAN, especially because of the interoperability of devices with SNMP. The SNMP message is translated to a UDP-based query when arrives from an NMS. It contains identifiers objects that are retrieved by the Device Agent. Likewise, these objects are translated to SNMP format when arriving at the gateway.  
The data validity is the most important consideration to management architecture. The performance of the network management can be calculated with query-response delay and the increasing number of nodes. Likewise, another way is analysis the computation overhead with query load. The reliability introduces a delay of 25 ms to a query and reaches up 50%. Queries with five hops proposed a delay of 100 ms or more gave 100% reliability.  
_Pros: Reliability and supports 6 LoWPAN networks._  
_Cons: No mature protocol and hus delay due to protocol conversion._  
Use Case  
In this proposal [53], the Internet Lab Ajou University deployed an agent application over the 6 LoWPAN and a PAN coordinator connected to the gateway with PPP interface. The 6 LoWPAN environment composed of a gateway and IEEE802.15.4 devices, containing a PAN coordinator. The devices support Hilow [55] routing protocol. The Device Management agent access to 802.15.4 information base, 6 LoWPAN MIB, and IP MIB reduced.  
Figure 12: Illustration device level monitoring procedure for LNMP Protocol.