eeworldonline.com | designworldonline.com 4 • 2020 DESIGN WORLD — EE NETWORK 45These viewpoints are:
- The business viewpoint identifies stakeholders and their business vision,
value and objectives of an IIoT system. Business decision-makers, plant
managers and IT managers can use this perspective to better understand
and drive IIoT system development for business goals. - The usage viewpoint describes how the IIoT system will deliver the
intended business objectives. - The functional viewpoint focuses on the functional components and
structure to support the intended uses. It defines the domains most
important to consider in an IIoT system and clarifies the relationship
between them along with cross-cutting functions that must be
available across many of the system components. - The implementation viewpoint determines the technologies needed
to implement functional components, their communication schemes
and their lifecycle procedures.
The IIRA defines system characteristics as system properties and
behaviors. It bases its definitions on an IIoT system’s constituent sub-
systems, their interactions, and the environment in which they operate.
For example, one system characteristic might be trustworthiness,
which can include safety, security, privacy, reliability and resilience.
Other system characteristics examine how the IIRA functional
domains work with other systems ranging from edge to cloud as IIoT
architectures evolve.
Even though IIC and oneM2M take different approaches in
dealing with IoT and IIoT challenges, they share a common objective
of ensuring interoperability and reusability. The common goal is
to reduce the complexity and costs of designing, developing, and
deploying IoT systems.
ONEM2M ARCHITECTURE
A common method of implementing IoT in applications is to use silos
in a vertical solution stack. However, this method does not always
scale well or handle resource reuse well.
In an IoT application, if a device management function is
implemented for a narrowly defined use, this could easily prevent its
reuse for a second or third IoT application. The same logic applies to
other service enablers necessary for the deployment and management
of IoT applications.
oneM2M addresses this by using a horizontal model based
on a common services layer. This layer includes communications
management, device management and security functions. It makes
devices and their data discoverable and accessible to more than
a single parent application. One benefit of this approach is that it
doesn’t lock users with one vendor.
The common services layer is standard on oneM2M and includes
specifications for end-device and gateway entities. Users can deploy
native oneM2M systems, which comprise oneM2M compliant
end-devices communicating with one or more oneM2M platforms.
Users can also choose systems that include a mix of oneM2M and
proprietary devices. Such an approach may involve interworking proxy
gateways to manage non-oneM2M devices communicating with a
oneM2M platform.
Functionally, oneM2M defines fourteen common service functions
(CSFs). These relate to network connectivity, device security, transport
protocols, content serialization, IoT device services and management
and IoT semantic ontologies.
Developers can use each service to focus on application-specific
functions, such as turning a switch on or off. Abstraction techniques
can be used to mask the underlying technology specific details, and
allow the use of different communications stacks and protocols such
as HTTP, CoAP and MQTT. For example, a switch might use a fixed or
Wi-Fi network, a CoAP or HTTP transport. It might use a JSON or XML
serialization technique, an Open Connectivity Foundation (OCF) or
thread service, or an ontology based on Smart Appliances REFerence
(SAREF) or W3C’s Thing Description.
oneM2M offers security-related APIs to simplify security for
devices and applications to secure IoT devices and prevent and
mitigate attacks. This standard is constantly evolving to address new
IoT requirements.IIRA AND ONEM2M—WORKING TOGETHER
The IIRA organizes an IIoT system into functional domains and
crosscutting functions. The functional domains focus on major
system functions that support generic IIoT usages and IIoT systemIoT AND MANUFACTURING