Abstract

The introduction of the Industrial Internet of Things in the factory environment is one of the most important features of the fourth industrial revolution. The main aim is the integration of sensor and actuator devices, based on the Internet of Things, with the industrial applications used for factory processes. This goal may be reached only if interoperability between the communication protocols existing in the domains of industrial applications and the Internet of Things is achieved. Open Platform Communications Unified Architecture (OPC UA) is considered one of the main reference communication standards in Industry 4.0 among industrial applications. Within the Internet of Things domain, the oneM2M communication protocol has been defined for solving the current fragmentation of this domain in the information exchange between sensor and actuator devices. Interoperability between these two communication protocols may allow integration of the industrial applications with Internet of Things-based devices. The current state of the art does not present any interoperability solution to allow the information produced by oneM2M-based devices to be consumed by OPC UA industrial applications. In order to reach this aim, the paper proposes a novel solution based on the use of a standard interworking proxy. The paper will describe this solution and the relevant software implementation.

Highlights

  • The aim of this section is to give an overview of the state of the art about interoperability solutions between industrial applications and Internet of Things (IoT) domain, focusing on those based on Open Platform Communications Unified Architecture (OPC UA)

  • The oneM2M child-resources are represented as instances of ad hoc OPC UA ObjectTypes, which are defined in the research carried out, as the native ones were not able to represent some of the oneM2M resources; they will be described in the following

  • Each oneM2M resource is mapped in a OPC UA Node in a time that is independent of the number of oneM2M resources to be mapped; considering this number as the independent variable, the time complexity of the mapping procedure for each single oneM2M resource may be assumed as O (1)

Read more

Summary

Introduction

Publisher’s Note: MDPI stays neutral with regard to jurisdictional claims in published maps and institutional affiliations. Considering the OPC UA and the oneM2M communication protocols in the industrial and in the IoT domains, respectively, the current state of the art does not present any interoperability solution to allow the information produced by oneM2M IoT-based devices to be consumed by OPC UA-based industrial applications. Filling this gap is very important, as the definition of an interoperability solution such as that may be able to realize the aim of the IIoT as depicted before.

Related Work
Overview of the OPC UA and OneM2M Protocols
Information Model
OPC UA
Standard
Hierarchical
Data Access Services in OPC UA
Data Access Services in OneM2M
Methodology
Mapping OPC UA and OneM2M Information Models
ResourceObjectType
10. OPC UA
Case Study
Software
Software Implementation
Interworking Proposal
Section 55 described
Operations at Run-Time
OPCUA‐IPE Software Implementation
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call