Key Points
Resources
| Resource____________________________________________________ | Notes____________________________________________________________ |
|---|---|
| https://networklessons.com/cisco/evolving-technologies/iot-standards-and-protocols | IoT network and data standards |
| https://objectcomputing.com/products/opendds | OpenDDS basic concepts |
| https://objectcomputing.com/products/opendds/resources#tech | OpenDDS resources |
| https://objectcomputing.com/resources/publications/mnb/code-generation-with-opendds-part-i | OpenDDS code generation - part 1 ( OLD ) |
| http://mnb.ociweb.com/mnb/MiddlewareNewsBrief-201007.html | OpenDDS code generation - part 2 |
ELECROW CrowPi Raspberry Pi 4B 3B+ Learning Computer Sensor Kit for Learning Coding and Electronics(Basic Kit, RPI Not Included, Black) | |
Key Concepts
IoT Networking and Data Standards
https://networklessons.com/cisco/evolving-technologies/iot-standards-and-protocols
There are many protocols that have a direct or indirect role in IoT. We’ll focus on two protocol types in particular:
- Network protocols
- Data protocols
Network Protocols
The network protocols we use for IoT should be open standards because our IoT network has to support devices from multiple vendors. Proprietary protocols increase complexity because you then need devices that can translate between the different protocols.
The Internet Protocol (IP) is well established and we have been using IP for IT networks for a long time. This is one of the reasons why IP is also the main choice for IoT networks.
Using IPv6 is encouraged because there are no address space limitations as there are with IPv4. Solutions such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN) or IPv6 Routing Protocol for LLNs (RPL) don’t even support IPv4, only IPv6.
Data Protocols
We need to transfer data between our devices and other systems such as an IoT platform. Some devices have sensors that push data at a regular interval. Other sensors work with a pull model where you have to request the information. There are several data protocols we can use in IoT. Here are three popular protocols:
- Message Queuing Telemetry Transport (MQTT)
- Constrained Application Protocol (CoAP)
- Extensible Message and Presence Protocol (XMPP)
MQTT
MQTT is probably the most used protocol in IoT. It’s a lightweight message protocol that uses publish and subscribe operations to transmit data between a client and server. It uses TCP as the transport protocol.
Packets are tiny and require little bandwidth. MQTT uses a client-server model. The server is called a broker. There are two operations:
- Publish: a device (client) sends data to a broker (server).
- Subscribe: a device (client) wants to receive data from a broker (server).
CoAP
CoAP is also a lightweight protocol and was developed as a standard (RFC 7252). It’s based on a REST model. A server makes resources available under a URL and clients access these resources with GET, PUT, POST, and DELETE methods. It is easy to get started with CoAP because many developers are familiar with REST.
CoAP can carry different payload types including XML and JSON and uses UDP as the transport protocol.
XMPP
XMPP is an open standard (RFC6120) and is based on XML technology for real-time communication. It’s used for a range of applications including VoIP, instant messaging, and IoT.
XMPP has been around for a while and has proven scalability and security. There are many servers that have used XMPP for many years. Software is available for any programming language making it easy to get started. Because XMPP was originally an instant messaging protocol and uses XML, it has more overhead compared to a lightweight protocol like MQTT.
OpenDDS concepts
https://objectcomputing.com/products/opendds
OpenDDS was developed by Object Computing, Inc., working closely with key customers, users, and other researchers at various universities and other locations around the globe.
FEATURES
- Broad platform support, including real-time and non-real time operating systems on a variety of hardware platforms.
- Operating systems include Linux, Windows™, Mac OS™, VxWorks™, LynxOS™, and others
- Hardware platforms include the Intel Core Processor Family, ARM, Raspberry Pi, and others
- Complies with the OMG DCPS layer of the Data Distribution Service for Real-Time Systems (DDS) specification.
- A Pluggable Transport Layer that allows data transmission across a variety of transport protocols. OpenDDS currently implements simple TCP, UDP, reliable multicast, and unreliable multicast transports. In addition, application developers may implement their own custom transport protocols and plug them into OpenDDS.
- Interoperability with other DDS implementations through the RTPS transport.
- Support for Java bindings through JNI and the option of inclusion with JBoss (ESB) frameworks by means of a JMS wrapper.
BENEFITS
OpenDDS is free Open Source software (FOSS), which means no vendor lock-in and maximum user control. There are no license fees whatsoever.
Full source code available (also at no cost).
The OpenDDS Modeling Software Development Kit (SDK), built on top of the Eclipse Modeling Framework, simplifies the use of OpenDDS, leaving the developer free to devote more time to application issues rather than the details of internal middleware plumbing.
Efficient marshaling and demarshalling of user-defined data types.
Robust federated information repository that allows publishers and subscribers to discover one another, to support registration of participants and creation of topics, and to support publication of built-in topics for meta-data propagation.
Scalable, multi-threaded architecture.
Includes an easy-to-use run-time configuration framework that supports configuration via a combination of files, options, and application programming interfaces.
Opportunities
Challenges
Solutions
Details
Next Steps
Related articles
Link
| Link__________________________________________________________ | Notes_______________________________________________________________ |
|---|---|
| https://confluence.atlassian.com/confcloud/import-a-confluence-space-724765531.html | How to import space export xml zip file into Confluence Cloud |
Instructions - Move sites between Confluence instances
- How to Export a Space in Confluence Cloud to xml zip file
- How to Import a Space in Confluence Cloud from xml zip file