Constrained Application Protocol: Difference between revisions

Revision as of 07:43, 12 September 2012

Revision as of 19:30, 12 November 2012

Line 3:

'''Constrained Application Protocol''' (CoAP) is a software protocol intended to be used in very simple electronics devices that allows them to communicate interactively over the Internet. It is particularly targeted for small low power sensors, switches, valves and similar components that need to be controlled or supervised remotely, through standard Internet networks.

CoAP is an [[Applicationapplication layer]] protocol that is intended for use in resource-constrained internet devices, such as [[WSN]] nodes. CoAP is designed to easily translate to [[HTTP]] for simplified integration with the web, while also meeting specialized requirements such as [[multicast]] support, very low overhead, and simplicity.<ref>[https://datatracker.ietf.org/doc/draft-ietf-core-coap Internet Draft describing Constrained Application Protocol (CoAP)]</ref><ref>"[http://hinrg.cs.jhu.edu/joomla/images/stories/IPSN_2011_koliti.pdf Integrating Wireless Sensor Networks with the Web]" , Walter, Colitti 2011</ref> Multicast, low overhead, and simplicity are extremely important for [[Internet of Things]] (IoT) and [[Machine-to-Machine]] (M2M) devices, which tend to be deeply [[Embedded system|embedded]] and have much less memory and power supply than traditional internet devices have. Therefore, efficiency is very important. CoAP can run on most devices that support [[User Datagram Protocol|UDP]] or a UDP analogue.

The Internet Engineering Task Force ([[IETF]]) Constrained [[RESTful]] environments ([[CoRE]]) Working Group has done the major standardization work for this protocol. In order to make the protocol suitable to IoT and M2M applications, various new functionalities have been added.<ref>[https://datatracker.ietf.org/wg/core/ The CORE WG's IETF Area]</ref> This protocol is still under development.