46 DESIGN WORLD — EE NETWORK 4 • 2020 eeworldonline.com | designworldonline.com
capabilities. The crosscutting functions
should be made available across many of
the system functional components.
oneM2M centers on the crosscutting
design approach. It supports a software
framework for linking IoT applications to
value-added services relating to network
connectivity, device security, transport
protocols, content serialization, IoT device
services and management and IoT semantic
ontologies. With these services, application
developers can focus on application-specifi c
functions without worrying about the
underlying technologies.The oneM2M common service layer
functions are:- Functions in the business, information
and application domains, along with cross-
cutting functions, industrial analytics, and
intelligent and resilient control. These are
also available in the IIRA standard. - The security functions considered in the IIRA
System Characteristics corresponds to the
security function in the oneM2M service layer. - Functions in the operations domain and
in the distributed data management in the
crosscutting functions in the IIRA map to
functions in the oneM2M common services
layer. These are registration, discovery,
device management in oneM2M common
services layer.- Functions belong to the IIRA distributed
data management map to the oneM2M
data management and repository. - In the IIRA map, functions in the
connectivity in the crosscutting function
in both the common services layer and
the devices (layer) correspond across the
network spans in the oneM2M horizontal
architecture. The IIRA connectivity functions
directly map to semantics, communication
management, network service exposure and
transaction management. - Functions in the control domain and
the physical systems in the IIRA map to
those belonging to things in the one M2M
horizontal layer.
- Functions belong to the IIRA distributed
Other functions in the oneM2M services
layer not mentioned may not be described
directly in the IIRA or they belong to its
lower layer functions.
A common IIRA architecture pattern
often consists of elements arranged in
three tiers—edge, platform and enterprise.
The edge tier includes an edge gateway
communicating with three devices through
a proximity network. Data and control
pathways use a service network to link the
platform and enterprise tiers.
An Application Entity (AE) is available
for each connected sensor and data source.
AEs use a standard application service logicin individual devices, gateways and sensors
to deliver a standard interface to manage
and interact with applications.
In a distributed architecture, oneM2M’s
common services layer resides in Common
Services Entities (CSEs). CSEs control when
communications occur, taking into account
any time sensitivity for the data. Developers
can embed CSE function in a gateway
to place common services closer to the
edge of an IoT installation. A complex IoT
installation can involve several gateway CSEs
interoperating with a cloud-based CSE.
Finally, an AE is needed for the domain
application in the enterprise tier. The AE will
interact with edge devices and sensors.
AEs and CSEs offer a standard way
for devices and sensors to function in a
network-agnostic manner. They hide the
complexity and heterogeneity of network
usage from applications, which helps simplify
implementation for application developers.INTERWORKING
According to IIC, the introduction of
machine-to-machine solutions into industrial
IoT applications is progressing in three
phases. Rather than a typical master/
slave architecture, users link multiple
proximal networks through cloud-based
data aggregation and supervisory
control systems. As the IoT market
matures, applications will use distributed
architectures. As large-scale deployments