Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:iot-open:communications_and_communicating_sut:high_level_communication [2019/05/27 09:42] pczekalskien:iot-open:communications_and_communicating_sut:high_level_communication [2020/07/20 09:00] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +=====  ===== 
 +<box #5374d5></box>
 +<box #5374d5></box>
 ===== Host Layer Protocols ===== ===== Host Layer Protocols =====
 +<box #5374d5></box>
 +<box #5374d5></box>
 +
 The host layers protocols include session (SES), presentation (PRES) and application (APP) level, particularly APP (application) layer in the regular Internet communication is dominated by the HTTP protocol and XML-related derivatives, e.g. SoAP. Also, FTP protocol for file transfer is ubiquitous; it exists since the beginnings of the Internet. Most of them are somehow related to the text. They're referenced as "WEB" protocols. Although these protocols are frequently used by advanced and more powerful IoT devices, this is problematic to be implemented in the constrained IoT devices world. Event simplest HTTP header occupies at least 24 + 8 + 8 + 31 bytes without any payload! There is also a problem to cross firewall boundaries when communication between subnetworks of the IoT devices is expected to occur.  The host layers protocols include session (SES), presentation (PRES) and application (APP) level, particularly APP (application) layer in the regular Internet communication is dominated by the HTTP protocol and XML-related derivatives, e.g. SoAP. Also, FTP protocol for file transfer is ubiquitous; it exists since the beginnings of the Internet. Most of them are somehow related to the text. They're referenced as "WEB" protocols. Although these protocols are frequently used by advanced and more powerful IoT devices, this is problematic to be implemented in the constrained IoT devices world. Event simplest HTTP header occupies at least 24 + 8 + 8 + 31 bytes without any payload! There is also a problem to cross firewall boundaries when communication between subnetworks of the IoT devices is expected to occur. 
 Some IoT designed protocols are reviewed below. Some IoT designed protocols are reviewed below.
Line 26: Line 32:
 </figure> </figure>
  
-**MQTT Message**\\+===MQTT Message===
 MQTT is a text-based protocol and is data-agnostic. MQTT is a text-based protocol and is data-agnostic.
 A message is composed of a Topic (text) and a Payload (data).  A message is composed of a Topic (text) and a Payload (data). 
Line 59: Line 65:
 The payload (data) of the message is text as well, so in case one need to send binary data, it is necessary to encode it (e.g. Base64). The payload (data) of the message is text as well, so in case one need to send binary data, it is necessary to encode it (e.g. Base64).
  
-**MQTT Broker**\\+===MQTT Broker===
 MQTT Broker is a server for both publishers and subscribers. The connection is initiated from the client to the Broker, so assuming it is located outside of a firewall, it breaks firewall its boundaries. MQTT Broker is a server for both publishers and subscribers. The connection is initiated from the client to the Broker, so assuming it is located outside of a firewall, it breaks firewall its boundaries.
 The Broker provides QoS (Quality of Service), and it can retain message payload. There are three levels of MQTT Broker QoS (supplied in the message level). The Broker provides QoS (Quality of Service), and it can retain message payload. There are three levels of MQTT Broker QoS (supplied in the message level).
en/iot-open/communications_and_communicating_sut/high_level_communication.1558950170.txt.gz · Last modified: 2020/07/20 09:00 (external edit)
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0