44 DESIGN WORLD — EE NETWORK 4 • 2020 eeworldonline.com | designworldonline.com
- The IIRA functional viewpoint describes
domain and crosscutting functions for IIoT
systems end-to-end. oneM2M defi nes
functions common across industrial verticals.
It uses service abstraction within middle layer
services to hide device layer complexity and
bridge applications to devices. - A number of synergies between IIRA and
oneM2M show up in the implementation
viewpoint. Users can follow the IIRA
architecture patterns and use oneM2M
common services to support those patterns. - Functional components not covered by
the common service layer can be part of the
application layer components in oneM2M
and developed for a specifi c IIoT system.
oneM2M common services can be shared
by different industrial verticals, enabling
interoperability across these verticals.
From a system-usage analysis perspective,
the IIRA usage viewpoint provides a way
to analyze how the system is to be used to
achieve its objectives.ONEM2M
oneM2M is a global standard defi ning a
common service layer with a set of services
required by IoT systems regardless of
industry. These services help application
developers focus on building, deploying and
commercializing their IoT applications.
The oneM2M organization
has 200 active members. One
of its goals was to develop
a common service layer with
the IoT. This layer sits between
applications, networks, and aids
functions that are needed across
different industry segments.
This common service layer
functions as a layer between an
application’s business logic and
the communications network. It
helps connect end-point devices
and sensors. It also makes it easier
for users of oneM2M specifi cations
to integrate, design and manage
stack technologies of multiple IoT
applications within a company or in
different industry verticals.This service layer consists of a three-layer
architecture that consists of applications, a
common services layer (middleware), and
networks. The interfaces between these layers
have a standard format to enable a secure
means for connecting data producers and
data consumers. In particular, Machine-to-
Machine (M2M) and IoT applications will likely
need a common service layer such as this.
This layer’s functions include device
management, registration and security.
According to the IIC paper, the layer
“horizontally joins the middle layers of several
separate, heterogenous, vertical IoT solutions,
to share common capabilities and ensure re-
usability and economies of scale.”
A key aspect of this horizontal
architecture is enabling cross-silo
interoperability. Thus, individual IoT solutions
can share data and resources through
common service layer functions. One result is
that developers can easily share data between
applications and reduce dependence on
single-vendor products.
Both the oneM2M and IIC architectures
use similar technologies. They connect to
various communication systems such as the
web and RESTful services, Data Distribution
Service (DDS), OPC UA) and computational
technologies, such as cloud computing, big
data and machine learning. Thus, some of
the specifi cations’ elements map to each
other. But there are differences in focus and
approach. Here’s a closer look.IIC’S IIRA
The IIRA helps users rapidly install
interoperable IIoT systems. It identifi es and
highlights important architectural concerns,
concepts and patterns applicable within and
across industrial sectors that might interfere
with interoperability.
The IIRA suits system implementers,
where it functions as a starting point to
shorten system development. It makes use of
reusable, commercially available, or open-
source system building blocks. Many industrial
sectors can take advantage of IIRA, including
manufacturing, transportation, energy,
agriculture, healthcare and others. IIRA helps
reduce the cost of design and operations by
giving users a common language.
This standard addresses communication
architecture concerns with vocabulary,
structures, patterns and a methodology. It
adapts architectural concepts, constructs and
approaches from the ISO/IEC/IEEE 42010-
2011 Systems and Software Engineering—
Architecture Description standard. A goal
is to clarify how such a framework can help
create the reference architecture, and then
help create IIoT architectures.
According to the paper, architectural
concerns are identifi ed and classifi ed into
four viewpoints per the ISO/IEC/IEEE 42010-
2011 Systems and Software Engineering—
Architecture Description.INTERNET OF THINGS HANDBOOK