Organizations use CoAP with limited hardware that has a low transmission rate because its lightweight. The protocol is HTTP-friendly, using two basic message types: request and response. Messages can be confirmable or non-confirmable. Data packets are small, so message losses are few
Along with physical and MAC layer protocols, we also need application layer protocols for IoT networks. These lightweight protocols need to be able to carry application messages, while simultaneously reducing power as far as possible.
OMA Lightweight M2M (LWM2M) is one such protocol. It defines the communication protocol between a server and a device. The devices often have limited capabilities and are thus referred to as constrained devices. The main aims of the OMA protocol are as follows:(1)Remote device management.(2)Transferring service data/information between different nodes in the LWM2M network.
All the protocols in this class treat all the network resources as objects. Such resources can be created, deleted, and remotely configured. These devices have their unique limitations and can use different kinds of protocols for internally representing information. The LWM2M protocol abstracts all of this away and provides a convenient interface to send messages between a generic LWM2M server and a distributed set of LWM2M clients.
This protocol is often used along with CoAP (Constrained Application Protocol). It is an application layer protocol that allows constrained nodes such as sensor motes or small embedded devices to communicate across the Internet. CoAP seamlessly integrates with HTTP, yet it provides additional facilities such as support for multicast operations. It is ideally suited for small devices because of its low overhead and parsing complexity and reliance on UDP rather than TCP.