Application Protocols for IoT
One of the significant aspects of the IoT is the data
exchange between Sensors, Servers, Databases,
Business Engines, and Content Consumers.
1. Message Queuing Telemetry Transport (MQTT):
MQTT or Message Queuing Telemetry Transport is
a publish-subscribe-based lightweight messaging
protocol. It is best suited for Internet of Things
(IoT) and Machine to Machine (M2M)
communication because of its small code
footprint, lower bandwidth requirements, and
lower power consumption on the device.
2. Advanced Message Queuing Protocol (AMQP):
The Advanced Message Queuing Protocol (AMQP)
is an open standard for passing business messages
between applications.
AMQP has a low success rate at low bandwidths,
but it increases as bandwidth increases.
3. ConstrainedApplicationProtocol(CoAP):
The Constrained Application Protocol (CoAP) is a specialized web transfer
protocol for use with constrained nodes and constrained networks in the
IoT.
4. Extensible Messaging and Presence Protocol (XMPP):
XMPP is the Extensible Messaging and
Presence Protocol, a set of open
technologies for instant messaging,
presence, multi-party chat, voice and video
calls, collaboration, lightweight middleware,
content syndication, and generalized routing
of XML data.
5. Very Simple Control Protocol (VSCP):
VSCP is an open-source standard protocol for M2M, IoT,
and other remote control and measurement
applications.
6.DataDistribution Service (DDS):
The Data Distribution Service (DDS) is a
middleware protocol and API standard for data-
centric connectivity from the Object Management
Group.
7. RESTful HTTP (REST):
The Representational State Transfer (REST) is not really a protocol but
an architectural style. REST uses the HTTP methods GET, POST, PUT, and
DELETE to provide a resource oriented messaging system where all
actions can be performed simply by using the synchronous
request/response HTTP commands.
8.OMA LightweightM2M (LWM2M):
LightweightM2M is primarily a device
management protocol, but it should be designed
to be able to extend to meet the requirements of
applications.
Thank You

ApplicationProtocols_Rukasar,Ayana.pptx

  • 1.
  • 2.
    One of thesignificant aspects of the IoT is the data exchange between Sensors, Servers, Databases, Business Engines, and Content Consumers.
  • 3.
    1. Message QueuingTelemetry Transport (MQTT): MQTT or Message Queuing Telemetry Transport is a publish-subscribe-based lightweight messaging protocol. It is best suited for Internet of Things (IoT) and Machine to Machine (M2M) communication because of its small code footprint, lower bandwidth requirements, and lower power consumption on the device.
  • 4.
    2. Advanced MessageQueuing Protocol (AMQP): The Advanced Message Queuing Protocol (AMQP) is an open standard for passing business messages between applications. AMQP has a low success rate at low bandwidths, but it increases as bandwidth increases.
  • 5.
    3. ConstrainedApplicationProtocol(CoAP): The ConstrainedApplication Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained networks in the IoT.
  • 6.
    4. Extensible Messagingand Presence Protocol (XMPP): XMPP is the Extensible Messaging and Presence Protocol, a set of open technologies for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.
  • 7.
    5. Very SimpleControl Protocol (VSCP): VSCP is an open-source standard protocol for M2M, IoT, and other remote control and measurement applications.
  • 8.
    6.DataDistribution Service (DDS): TheData Distribution Service (DDS) is a middleware protocol and API standard for data- centric connectivity from the Object Management Group.
  • 9.
    7. RESTful HTTP(REST): The Representational State Transfer (REST) is not really a protocol but an architectural style. REST uses the HTTP methods GET, POST, PUT, and DELETE to provide a resource oriented messaging system where all actions can be performed simply by using the synchronous request/response HTTP commands.
  • 10.
    8.OMA LightweightM2M (LWM2M): LightweightM2Mis primarily a device management protocol, but it should be designed to be able to extend to meet the requirements of applications.
  • 11.