Recursos para mi aprendizaje | Internet of Things
Chapter 1 A Review of IoT Technologies, Standards, Tools, Frameworks and Platforms
1.1 Introduction
• IoT is an exciting technology development that promises to embed sensors
into physical things (personal devices, industrial machines, vehicles, appliances,
and the like) and enable them to record, process, and communicate their status
data with other things or with Internet servers for further processing.
• Industrial IoT (IIoT) focuses on the IoT technologies that connect industrial
machines among themselves and to the Internet. This enables automated
instrumentation, reporting, and even manufacturing.
o Applications: smart factories, smart warehousing, predictive and remote
maintenance, freight, goods and transportation monitoring, smart utility
metering, smart grids, smart cities, smart farming, live stock monitoring,
asset tracking and performance management, etc.
• IoT and IIoT share the same basic building blocks
1.2 Related Work
• IIoT is the application of IoT technologies to industrial settings such as
manufacturing
o IIoT is a system comprising networked smart objects, cyber-physical
assets, associated information technologies, and optional cloud or edge
computing platforms.
o IIoT is closely related to Industry 4.0
• Industry 4.0 is an integrated adapted, optimized, service-oriented, and
interoperable manufacturing process which is correlated with algorithms, big
data, and high technologies
• Over the last few years, researchers have become more interested in
developing reference architectures for IoT and IIoT. Generic architectures
usually organize the components necessary for building IoT solutions in several
distinct layers.
o Examples:
▪ Lin et al. [21] present four-layer architecture: perception,
network, service, and application layers.
▪ Dhariwal and Mehta [25] propose a 3-layer architecture for a
smart hospital: a perception layer, a network layer, and an
application layer.
▪ Zhang et al. [26] propose a generic architecture [for
manufacturing] to attach sensors in a manufacturing
environment, capture data in real time during the production
process, process data, and provide real-time analysis and
feedback.
o Other researchers focus on IoT architectures from a specific
functionality perspective, such as energy-efficient IIoT [28] or secure
IoT.
o Industrial Internet Reference Architecture (IIRA) ia a standard-based
open architecture for IIoT systems applicable across many industries.
▪ Focused for broad industry applicability
▪ IIRA includes four viewpoints: business, usage, functional, and
implementation.
o Industrial Internet Connectivity Framework (IICF) organizes
connectivity technologies into a stack model and proposes achieving
interoperability among various standards
• Reference Architecture Model for Industrie 4.0 (RAMI 4.0) is a detailed
service-oriented architecture for manufacturing.
o Focused for manufacturing only
o Developed by Platform Industrie 4.0
o It focuses on several axes:
▪ factory (which defines how products and manufacturing systems
interact in an enterprise)
▪ product life cycle (which captures the development, production,
maintenance, usage and end of life stages of a product)
▪ architecture (based on six layers describing both the real and
digital world)
o While IIRA and RAMI 4.0 each have a different focus, efforts to
compare and map their components to each other are underway to
ensure interoperability between different IIoT systems.
• Major technology providers, such as IBM, are also active in the IoT
architecture area, proposing both general and specific reference architectures
for IoT and IIoT.
o IBM’s IoT reference architecture consists of five layers:
▪ User
▪ proximity network
▪ public network
▪ provider cloud,
▪ enterprise network
o Data Distribution Service (DDS) is the first open international
middleware standard directly addressing publish/subscribe
communications for real-time and embedded systems.
o The Internet of Things Consortium (IoTC) is focused on IoT ecosystem
interoperability and usability, data openness and security, and market
development
1.3 Analysis
• The following figures depict the necessary elements for an IoT end to-end
solution, which can be visualized as a stack consisting of
o a bottom layer describing the devices (hardware, firmware, and runtime
environment)
o a layer of communication standards (as shown in Fig. 1.1)
o layers of messaging protocol standards, back-end and front-end tools,
frameworks and platforms (as shown in Fig. 1.2)
1.3.1 IoT Devices
• IoT devices, or things in the IoT, are the first building block of the IoT
infrastructure.
o IoT hardware includes both embedded systems and boards (such as
Arduino, Raspberry Pi, Tessel, Espruino, and others) and stand-alone
devices (such as Samsung Gear or FitBit in the consumer-things
space)
▪ Embedded systems consist of a microcontroller, as well as
other parts (such as a power source, sensors for light, etc).
1.3.2 Communication Standards
• Communication standards are essential for enabling IoT devices to reliably
communicate with each other and with other entities on the Internet.
o One of the most widespread communication standards is Wi-Fi,
which is a wireless local area network (WLAN) standard defined by
IEEE 802.11 specification.
o Another standard is ZigBee, an IEEE-802.15.4 specification for
wireless personal area networks well-suited for low-power devices
o Bluetooth is another standard (based on IEEE 802.15.1
specifications) for data transfer between devices over short
distances.
o There is also the WiMAX/IEEE-802.16 standard, which is used for
example by Sigfox and LoRa and popular mobile standards like LTE.
▪ NB-IoT, which stands for Narrowband IoT, is a new wireless
standard used, among others, for smart gas and water meters
o Other emerging communication standards include LoRa, Sigfox,
WAVIoT, DASH7, LTE-M (LTE M2M), NB-LTE-M, Weightless,
6LoWPAN, etc.
Standar Frequenc Data rate Bandwidt Coverage Energy Pros Cons
d y range h needed
Wi-Fi 2.4–5.9 Variable; Variable, 50–100 m High Simple High
GHz 1.5–54 up to setup, energy
Mbps 450–600 robust usage
Mbps security,
transpare
nt
implement
ations
ZigBee 2.4 GHz 250 Kbps 2MHz 50 m Low Low- Short
power range
usage, up
to 254
devices
connected
Bluetoo Variable, Depends Up to 1 1–100 m Medium Widely Security
th 2402– on Mbps used concerns,
2480 standards one
MHz connectio
n at a time
WiMAX 2–11 GHz 124 Mbps Adjustable 30–50 km High Long poor
, 1.25M to range, bandwidth
20 MHz symmetric
al
bandwidth
LTE Variable usually Variable; Variable; Low High Limited
100 Mbps 100 Mbps 2–10 km speed connectivi
ty
NB-IoT LTE in- 250 Kbps 180 kHz less than Low Low- Less
band 22 km power coverage
usage
1.3.3 Messaging Protocol Standards
• Messaging protocols define the syntax and semantics of the data being
transferred between IoT devices and servers.
o MQTT (Message Queuing Telemetry Transport) is an IoT messaging
protocol by the independent Organization for the Advancement of
Structured Information Standards (OASIS).
▪ Highly efficient and scalable
▪ very small protocol overhead.
▪ implements a publish/subscribe messaging model on top of
the widely known TCP/IP standards.
▪ It is specifically designed for machine-to-machine (M2M)
▪ useful in the automobile industry
▪ MQTT-SN (MQTT for Sensor Networks) was developed
specifically for wireless sensor networks
o AMQP (Advanced Message Queuing Protocol) is an open standard
for a communication protocol between a client and a message
broker, or between various message brokers.
▪ Used by RabbitMQ, Apache ActiveMQ, Apache Qpid,
SwiftMQ, Microsoft Azure Service Bus, and Red Hat
Enterprise MRG.
o XMPP (eXtensible Messaging and Presence Protocol), formerly
known as Jabber, is an XML-based communication protocol
frequently used by instant messengers for chat applications.
o CoAP (Constrained Application Protocol) is often described as the
HTTP for IoT. It implements the request/response pattern
o HTTP (Hypertext Transfer Protocol), the bedrock of all protocols, is
still the first choice for request/response-based IoT communication
o OPCUA (Open Platform Communications Unified Architecture) is an
industrial M2M communication protocol based on AMPQ which can
securely and reliably transport machine data
o LWM2M (Lightweight M2M) is a messaging protocol designed by
the Open Mobile Alliance (OMA) based on CoAP for managing IoT
devices.
1.3.4 Communication Platforms
• For the protocols defined in the previous section (such as AMQP, MQTT,
and XMPP) to be implemented in practice, it is necessary to define the
procedures through which many IoT devices can communicate. Most
communication platforms use a broker model, which provides trusted
message prioritization, routing, filtering and delivery between a publisher
and a subscriber.
• examples of such brokers are:
o HiveMQ is an Enterprise MQTT Broker conceptualized for
commercial use. The broker supports the publish/subscribe MQTT
standard.
o Mosquitto—an open-source MQTT broker. alternative for HiveMQ
o Moquette: an open-source MQTT broker written in Java.
▪ Like Mosquitto, it also runs on IoT devices such as on a
Raspberry Pi
o Pivotal RabbitMQ, an open-source message broker.
o The Eclipse Paho project provides open-source client
implementations of MQTT and MQTT-SN messaging protocols
which are aligned with the new, existing, and future IoT applications.
1.3.5 Device Control, Integration, and Simulation Frameworks
• IoT solutions usually involve a diversity of IoT devices interacting with each
other and transmitting data to IoT-based applications. The device control,
integration, and simulation frameworks enable easy configuration of these
devices and efficient man agement of their operation. We present
examples of such frameworks below.
o openHAB (open Home Automation Bus) is Java-based framework
▪ integrates buildings automation components from different
manufacturers in a single device independent and protocol-
independent platform
o The Eclipse Edje project falls under the Apache license 2.0 and
provides a hard ware abstraction Java API (application programming
interface) for accessing hard ware features of microcontrollers such
as the general-purpose input/output (GPIO) interfaces [69].
Lo que falta es puro copy-paste y no me salió en el quiz, lo mejor
será Ctrl+F con el PDF. Buena suerte!
1.3.6 Tools and Frameworks for Modeling, Development, and Deployment
1.3.7 IoT Cloud Integration Platforms
1.4 Conclusions
