Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Discusses the various application layer protocols like CoAP and MQTT.This ppt also focusses on the compatibility between legacy protocols, web based, and IoT protocols.
Typology: Slides
1 / 10
This page cannot be seen from the preview
Don't miss anything!
How higher-layer IoT protocols are transported โ from traditional TCP/UDP transport mechanisms to lightweight application protocols engineered for constrained devices and lossy networks. IOT NETWORKING PROTOCOL DESIGN TRANSPORT LAYER
CHAPTER 1
Like a telephone call โ a session must be established before data flows. Guarantees delivery, sequencing, and flow control.
Like mailing a letter โ data is sent immediately with no delivery guarantee. Used by DNS, NTP, SNMP, DHCP, and real-time media.
CHAPTER 2
Constrained Connectivity Low Capability Rich Connectivity High Capability
Each category reflects a different level of device capability and network constraint โ from bare-metal Class 0 sensors to full IP-enabled smart devices running optimized IoT protocols.
TRANSPORT METHOD 1
Defined by IETF RFC 7228 , Class 0 devices are severely constrained in processing power, memory, and energy. They do not implement a full protocol stack โ no IP, TCP, UDP, or application layer. Implementing a robust protocol stack on Class 0 devices is often not just impractical โ it is physically impossible given available resources. These simple smart objects typically interact through an IoT data broker that handles all network communication on their behalf.
SCADA INTEGRATION
Both SCADA server and RTUs connect serially to routers. Routers encapsulate serial payloads over IP using raw TCP or UDP sockets.
Software on the SCADA server maps serial COM ports to IP ports, converting serial connections to TCP/IP raw socket connections.
The SCADA server natively supports raw socket connections โ no external router or redirector software required.
An IoT gateway translates between serial DNP3 on one side and DNP3-over-IP on the other, bridging legacy and modern infrastructure.
TRANSPORT METHOD 3 Generic Web-Based Protocols Web protocols ease IoT integration from prototyping to production. Developers with standard web skills can build IoT applications immediately. HTTP/HTTPS on Non-Constrained Networks On Ethernet, Wi-Fi, or cellular, verbose payloads (JSON, XML) travel over HTTP/HTTPS or WebSockets with minimal concern for bandwidth. Client vs. Server Role Devices that only push data (e.g., weather stations, smart scales) implement HTTP client- side only โ initiating connections but never accepting incoming ones. XMPP for Real-Time Interaction Extensible Messaging and Presence Protocol enables simple communication between people and IoT devices for voice, video, and chat integration.
Key Takeaways (^1) Match Transport to Constraint UDP's 8-byte overhead and connectionless design make it the default for LLNs. TCP's reliability comes at a cost often too high for constrained devices. (^2) Legacy Protocols Need Adaptation SCADA protocols like DNP3 and Modbus have been adapted to IP via raw socket tunneling, IP/serial redirectors, or protocol translation gateways. (^3) Web Protocols Bridge Familiarity and IoT HTTP/HTTPS and XMPP lower the barrier to IoT development but require optimization for truly constrained environments. (^4) CoAP Is Purpose-Built for IoT With a 4-byte header, REST semantics, and UDP-based reliability, CoAP is the definitive application protocol for constrained IoT deployments.
