ETSI TR 118 518 V2.0.0 (2016-09)

oneM2M; Industrial Domain Enablement (oneM2M TR-0018 version 2.0.0 Release 2)

DTR/oneM2M-000018

General Information

• Status: Published
• Publication Date: 06-Sep-2016
• Technical Committee: oneM2M - oneM2M
• Current Stage: 12 - Completion
• Due Date: 10-Sep-2016
• Completion Date: 07-Sep-2016

Standards Content (Sample)

TECHNICAL REPORT
oneM2M;
Industrial Domain Enablement
(oneM2M TR-0018 version 2.0.0 Release 2)

oneM2M TR-0018 version 2.0.0 Release 2 2 ETSI TR 118 518 V2.0.0 (2016-09)

Reference
DTR/oneM2M-000018
Keywords
IoT, M2M
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 3 ETSI TR 118 518 V2.0.0 (2016-09)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Abbreviations . 7
4 Conventions . 8
5 Introduction to Industrial Domain . 8
5.1 Industrial Domain Overview . 8
5.2 Technology Trends in Industrial Domain . 9
6 Use Cases . 11
6.1 An Industrial Use Case for On-demand Data Collection for Factories . 11
6.1.1 Description . 11
6.1.2 Source . 11
6.1.3 Actors . 12
6.1.4 Pre-conditions . 12
6.1.5 Triggers . 12
6.1.6 Normal Flow . 12
6.1.7 High Level Illustration . 13
6.1.8 Potential Requirements . 13
6.2 Integrity of Data Collection Monitoring . 13
6.2.1 Description . 13
6.2.2 Source . 14
6.2.3 Actors . 14
6.2.4 Pre-conditions . 14
6.2.5 Triggers . 14
6.2.6 Normal Flow . 14
6.2.7 High Level Illustration . 15
6.2.8 Potential Requirements . 15
6.3 Data Process for Inter-factory Manufacturing . 16
6.3.1 Description . 16
6.3.2 Source . 16
6.3.3 Actors . 16
6.3.4 Pre-conditions . 16
6.3.5 Triggers . 16
6.3.6 Normal Flow . 17
6.3.7 Post-conditions . 17
6.3.8 High Level Illustration . 17
6.3.9 Potential Requirements . 17
6.4 Aircraft Construction and Maintenance . 18
6.4.1 Description . 18
6.4.2 Source . 18
6.4.3 Actors . 18
6.4.4 Pre-conditions . 19
6.4.5 Triggers . 19
6.4.6 Normal Flow . 19
6.4.7 High Level Illustration . 20
6.4.8 Potential Requirements . 20
6.5 Real Time Data Collection . 21
6.5.1 Description . 21
6.5.2 Source . 21
6.5.3 Actors . 21
6.5.4 Pre-conditions . 22
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 4 ETSI TR 118 518 V2.0.0 (2016-09)
6.5.5 Triggers . 22
6.5.6 Normal Flow . 22
6.5.7 Alternative flow . 22
6.5.8 Post-conditions . 22
6.5.9 High Level Illustration . 23
6.5.10 Potential Requirements . 23
6.6 Data Encryption in Industrial Domain . 23
6.6.1 Description . 23
6.6.2 Source . 24
6.6.3 Actors . 24
6.6.4 Pre-conditions . 25
6.6.5 Normal Flow . 25
6.6.6 Post-conditions . 25
6.6.7 High Level Illustration . 26
6.6.8 Potential Requirements . 26
6.7 Qos/QoI Monitoring in Industrial Domain . 26
6.7.1 Description . 26
6.7.2 Source . 27
6.7.3 Actors . 27
6.7.4 Pre-conditions . 27
6.7.5 Triggers . 27
6.7.6 Normal Flow . 28
6.7.7 Alternative flow . 28
6.7.8 Post-conditions . 28
6.7.9 High Level Illustration . 28
6.7.10 Potential Requirements . 28
7 Overview of Potential Requirements . 29
8 High Level Architecture . 30
8.1 Introduction . 30
8.2 Deployment Mapping Using IPE . 30
8.3 Deployment Mapping Using Peer-to-Peer Communication . 31
8.4 Conclusion . 32
9 Security Analysis . 32
9.1 Introduction . 32
9.2 Identification and Authentication . 32
9.3 Use Control . 33
9.3.1 Introduction. 33
9.3.2 Authorization . 33
9.3.3 Session Lock & Concurrent Session Control . 33
9.4 Data Confidentiality . 33
9.4.1 Introduction. 33
9.4.2 Light-weight Encryption . 33
9.4.3 Session Based Encryption . 34
9.5 System Integrity . 34
9.5.1 Introduction. 34
9.5.2 Communication Integrity . 34
9.5.3 Session Integrity . 34
9.6 Restricted Data Flow . 34
9.7 Conclusion . 34
10 Conclusion . 35
History . 36

ETSI
oneM2M TR-0018 version 2.0.0 Release 2 5 ETSI TR 118 518 V2.0.0 (2016-09)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) has been produced by ETSI Partnership Project oneM2M (oneM2M).
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 6 ETSI TR 118 518 V2.0.0 (2016-09)
1 Scope
The present document collects the use cases of the industrial domain and the requirements needed to support the use
cases collectively. In addition it identifies the necessary technical work needed to be addressed while enhancing future
oneM2M specifications.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] oneM2M Drafting Rules.
NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.
[i.2] ETSI TS 118 111: "oneM2M; Common Terminology (oneM2M TS-0011)".
[i.3] IEC TC News, http://www.iec.ch/tcnews/2014/tcnews_0214.htm.
[i.4] http://www.is-inotek.or.jp/archive/05_Ishikuma_Smart_Manufacturing.pdf, Dec 2014.
[i.5] IIC website, http://www.industrialinternetconsortium.org/.
[i.6] IIC document 'Engineering: The First Steps', Sep 2014.
[i.7] IIC report 'Engineering Update: November 2014', Nov 2014.
[i.8] IEEE P2413 website, http://grouper.ieee.org/groups/2413/.
[i.9] IEEE P2413 presentation 'Standard for an Architectural Framework for the Internet of Things
(IoT)', Sep 2014.
[i.10] IEEE P2413 report 'oneM2M Specification Comment Collection', Oct 2014.
[i.11] SMLC website, https://smartmanufacturingcoalition.org/.
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 7 ETSI TR 118 518 V2.0.0 (2016-09)
[i.12] SMLC presentation, March 2014.
NOTE: Available at https://smartmanufacturingcoalition.org/sites/default/files/savannah_rivers_03-10-2014.pdf.
[i.13] Article "First European testbed for the Industrial Internet Consortium" in Bosch's ConnectedWorld
Blog http://blog.bosch-si.com/categories/manufacturing/2015/02/first-european-testbed-for-the-
industrial-internet-consortium/.
[i.14] ETSI TS 118 102: "oneM2M; Requirements (oneM2M TS-0002)".
[i.15] ETSI TS 118 101: "oneM2M; Functional Architecture (oneM2M TS-0001)".
[i.16] IEC 62443 series: "Industrial communication networks - Network and system security".
[i.17] ETSI TS 118 103: " oneM2M; Security Solutions (oneM2M TS-0003)".
[i.18] NIST Special Publications (SP)800-57: "Guidelines for Derived Personal Identity Verification
(PIV) Credentials".
[i.19] Draft Recommendation ITU-T X.iotsec-1: "Simple encryption procedure for Internet of Things
(IoT) environments".
[i.20] ETSI TR 118 518: "oneM2M; Industrial Domain Enablement (oneM2M TR-0018)".
[i.21] IEC TC 65: "Industrial-process measurement, control and automation".
[i.22] Reference Architecture Model Industrie 4.0 (RAMI4.0), July 2015.
NOTE: Available at
https://www.vdi.de/fileadmin/vdi_de/redakteur_dateien/gma_dateien/5305_Publikation_GMA_Status_Re
port_ZVEI_Reference_Architecture_Model.pdf
3 Abbreviations
For the purposes of the present document, the terms and definitions given in ETSI TS 118 111 [i.2] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in [i.2].
ACP Access Control Policy
AES Advanced Encryption Standard
CR Change Request
CSE Common Services Entity
DCS Distributed Control Systems
DMZ Demilitarized Zones
DoS Denial of Service
DSL Digital Subscriber Line
DTLS Datagram Transport Layer Security
FIPS Federal Information Processing StandardizationGPS Global Positioning System
GSM Global System for Mobile Communication
IACS Industrial Automation & Control System
ID Identifier
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronic Engineers
IIC Industrial Internet Consortium
IN Infrastructure NodeIPE Interworking Proxy application Entity
ISDN Integrated Services Digital Network
ITU-T International Telecommunication Union Telecommunication Standardization Sector
LAN Local Area Network
MIC Message Integrity Code
MN Middle Node
NSE Network Service EntityPLC Programmable Logic Controllers
QoI Quality of Information
QoS Quality of Service
RBAC Role-based Access Control
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 8 ETSI TR 118 518 V2.0.0 (2016-09)
SHA Secure Hash Algorithm
SL Security Level
SMB Standardization Management Board
SMLC Smart Manufacturing Leadership Coalition
SOA Service Oriented Architecture
TLS Transport Layer Security
UMTS Universal Mobile Telecommunications System
VPN Virtual Private Network
WiFi Wireless Fidelity
WLAN Wireless Local Area Network
XML eXtensible Markup Language
4 Conventions
The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be
interpreted as described in the oneM2M Drafting Rules [i.1].
5 Introduction to Industrial Domain
5.1 Industrial Domain Overview
In previous industrial domains, the information exchange from factory-to-factory or centre-to-factory needed support
from humans. Normally the exchange is non-synchronous, discrete, inefficient and unable to achieve the capacity to
respond rapidly to market changes.
Currently M2M technologies are considered to achieve the communication and interaction from machine-to-machine
without human support. It brings opportunities to achieve synchronous, continuous and effective information exchange
in manufacturing scenarios. Based on M2M, new manufacturing methods can be suitable to increase complex
requirements of future market needs.
Many industrial companies are aware of the potential power to update traditional manufacturing systems by introducing
M2M technologies. They are not restricted to the technical requirements, such as improving the performance of
productivity, quality, delivery, cost reduction and security, but also new opportunities to cooperate with other domains
for mass production, and the potential to build the new architecture for next generation industry. Figure 5-1-1 is an
example architecture.
Figure 5-1-1: Industrial Domain Architecture
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 9 ETSI TR 118 518 V2.0.0 (2016-09)
In figure 5-1-1, factories will be connected with manufacturing services via the M2M system(s). Generally, the gateway
in the factory will collect data from the factory and send it to manufacturing services in a management centre. The
service will be initiated by different management modules and sent to factories.
In addition, with the M2M system(s), the complex service can be sent to several factories synchronously, to enable
effective collaboration between factories. Every factory is expected be able to make accurate decisions and to operate
effectively, because it can work based on the results of data analysis and the data is from all the factories rather than
from only one. The management centre with manufacturing services is also expected to be able to make accurate
decisions by utilizing field data from all factories, and also via other support systems, such as cloud computing, to
improve efficiency of local or global services.
In the future, if more and more industry related domains, such as logistics and power management systems, can be
connected into the M2M system, resources (warehouses, trucks, ships, power, etc.) can be integrated efficiently.
Therefore more flexible services will be created to face this complex situation.
As the oneM2M architecture provides general Application Layer, Common Services Layer and the Underlying Network
Services Layer, and will be connected with other vertical systems, it is important to consider the integration of industrial
domain systems with the oneM2M architecture.
5.2 Technology Trends in Industrial Domain
To accelerate the update of manufacturing systems, many worldwide organizations have been established and have
started making efforts.
In June 2014, the IEC (International Electrotechnical Commission), Standardization Management Board (SMB) set up a
Strategy Group, SG8, to deal with a number of tasks related to Smart Manufacturing [i.3].
Table 5.2-1: Industrial Domain Research in IEC SMB SG8 [i.4]
• Develop a function model/reference architecture that helps to identify gaps
in standardization based on to-be-collected use cases.
Mission &
• Develop a common strategy for the implementation of Industry 4.0.
Scope
• Extend standards towards: environmental conditions, security, properties,
energy efficiency, product and functional safety.
• Industrial process measurement, control and automation.
Technical • Application: semantics relationships descriptive technologies.
Keywords
• Services: web services /SOA repositories /cloud dependable connections.
• Communication: data access real-time communications.

The IIC (Industrial Internet Consortium) was founded in March 2014 to bring together the organizations and
technologies necessary to accelerate growth of the Industrial Internet by identifying, assembling and promoting best
practices [i.5].
Table 5.2-2: Industrial Domain Research in IIC [i.6] and [i.7]
• Productivity and efficiencies can be improved by production process governing
themselves with intelligent machines and devices.
• Real time data report from handheld digital device.
Mission &
• Wearable sensors track location of employees in case of emergency.
Scope
• Future scenarios: new steering instruments will interlink things to ensure the
entire value chain and trigger adjustments on the factory floor in case of chain
changing; raw materials will be programmed to record standard process and
their customer to realize automatic customization.
• Representative use case areas include connectivity, logistics, transportation,
and healthcare.
• Key capabilities system characteristics including resilience, safety and
security. (such as key system characteristic, intelligent and resilient control,
Technical
operations support, connectivity, integration and orchestration, security, trust
Keywords
and privacy, and business viewpoint).
• Data management and analytics.
• Security: endpoint security, secure communications and security management
and monitoring (currently focused on general security use case).

ETSI
oneM2M TR-0018 version 2.0.0 Release 2 10 ETSI TR 118 518 V2.0.0 (2016-09)
IEEE P2413 defines an architectural framework for the Internet of Things (IoT), which includes descriptions of various
IoT domains including the industrial domain and is sponsored by the IEEE-SA [i.8].
Table 5.2-3: Industrial Domain Research in IEEE P2413 [i.9] and [i.10]
• Ranges from the connected consumer to smart home & buildings, e-health,
Mission &
smart grids, next generation manufacturing and smart cities.
Scope
• Promote cross-domain interaction instead of being confined to specific
domains.
• Energy efficiency during data transmission.
Technical
• Areas of interest: industrial Internet, cross sector common areas, common
Keywords
architecture, security safety privacy.

The SMLC (Smart Manufacturing Leadership Coalition) is a non-profit organization committed to the development and
deployment of Smart Manufacturing Systems. SMLC activities are built around industry-driven development,
application and scaling of a shared infrastructure that will achieve economic-wide impact and manufacturing innovation
[i.11].
Table 5.2-4: Industrial Domain Research in SMLC [i.12]
• To build a cloud-based, open-architecture platform that integrates existing
Mission &
and future plant level data, simulations and systems across manufacturing
Scope
seams and orchestrate business real time action.
• Cloud-based networked data.
• Enterprise real-time.
Technical
• Plant level data.
Keywords
• Information & action.
• Security.
Plattform Industrie 4.0 is the central alliance for the coordination of the digital structural transition in German industry
and unites all of the stakeholders from business, associations, trade unions and academia. Results so far have been
summarized under the title “Reference Architecture Model Industrie 4.0 (RAMI4.0)”. RAMI 4.0 provides a conceptual
superstructure for organizational aspects of Industrie 4.0, with emphasis on collaboration infrastructures and on
communication structures. It also introduces a concept of an administration shell that covers detailed questions on
semantic standards, technical integration and security challenges. RAMI4.0 will be published as DIN SPEC 91345 "
Reference Architecture Model Industrie 4.0” (RAMI4.0).
Table 5.2-5: Industrial Domain Research in Plattform Industrie 4.0 [i.22]
• Identify all relevant trends and developments in the manufacturing sector and
combine them to produce a common overall understanding of Industrie 4.0
Mission & • Develop ambitious but achievable joint recommendations for all stakeholders,
Scope
that serve as the basis for a consistent and reliable framework
• Identify where action is required on standards and norms and actively express
recommendations for national and international committee work
• Reference architectures, standards and norms
• Incorporate existing norms and standards in RAMI4.0 (Reference Architecture
Model Industrie 4.0). RAMI4.0 is an initial proposal for a solution-neutral
reference architecture model.
• Research and innovation
Technical
• Evaluate current case studies to identify research and innovation
Keywords
requirements from the industry perspective.
• Security of networked systems
• Resolve the outstanding issues concerning secure communication and secure
identities of value chain partners.
• Detect cyber attacks on production processes and their implications.

ETSI
oneM2M TR-0018 version 2.0.0 Release 2 11 ETSI TR 118 518 V2.0.0 (2016-09)
Based on the information above and the current oneM2M architecture, the technology trends below are becoming more
and more important:
• Data management and analytics:
In some industrial organizations, data management and data analytics are independent layers for data processing (such
as filtering and catalogue management) and data analytics. Since large amounts of data are generated in industrial
scenarios, further functionality design for data management and data analytics CSFs may need to be considered in
oneM2M.
• Real-time command and control:
M2M technologies enable real-time response manufacturing practices in complex supplier networks. Realizing real-
time command and control by highly available and time critical technologies will bring benefits to process automation
and the optimization of supply chains. Use cases with real-time command and control features may need to be
considered in oneM2M. Additionally, requirements from these use cases may need to be taken into consideration.
• Connectivity:
Since connectivity in the industrial domain needs to co-exist and evolve with legacy protocols, legacy connectivity
(both wired and wireless) and legacy wiring, connectivity for manufacturing processes needs to be considered and this
may have an impact on NSE functionalities.
• Security:
Increased networking and wireless technologies are the main security concerns for industrial companies. Undoubtedly,
the risk trade-off will not stop companies from manufacturing evolution. Thus a renewed risk for management and
ensuring security for the industrial domain may need to be considered.
Meanwhile more trends, such as web services over M2M devices and protocols in industrial domain, will be further
tracked and analyzed.
6 Use Cases
6.1 An Industrial Use Case for On-demand Data Collection for
Factories
6.1.1 Description
In factories, a lot of data are created from Programmable Logic Controllers (PLCs) every second, and data are utilized
to monitor production lines. This data is available via industrial bus systems, e.g. Real-time Ethernet. In order to
monitor remotely, data is gathered by the M2M service platform that needs to interface with such industrial bus systems
via M2M gateways. However, it is difficult to gather all data to the M2M service platform because sometimes more
than 1mega bit data is created per second. In such cases, only necessary data is gathered depending on situations and
filtering / pre-processing of the raw data needs to be performed at the gateways.
This use case proposes that the oneM2M System offers pre-processing capabilities, e.g. rule-based collection policies
(averages, thresholds, etc. …). These rules (e.g. in XML format) are called “"data catalogues”".
6.1.2 Source
• REQ-2014-0487R03: A use case for industry: On-demand data collection for factories.
• REQ-2015-0551: CR to ETSI TR 118 518 [i.20] Use Case 6.1.
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 12 ETSI TR 118 518 V2.0.0 (2016-09)
6.1.3 Actors
• PLC: It controls sensors and devices in a production line according to embedded programs. It also has
interface to Real-time Ethernet. It broadcasts data related to the production line to Real-time Ethernet.
• M2M Gateway: It provides an interface from the Real-time Ethernet to the oneM2M System. An application
on the gateway collects necessary data from Real-time Ethernet according to the configuration called data
catalogue, and send collected/pre-processed data to M2M service platform.
• M2M service platform: It stores data gathered from gateway(s), and provide data to applications. It also
manages data catalogue in gateway(s).
• Application: An M2M Application in the Infrastructure Domain that monitors production lines by using
collected data in M2M service platform, and send change request of data catalogue depending on situations.
• Real-time Ethernet: A technology standardized in IEC TC 65 [i.21]. Ethernet is used at the physical layer, but
upper protocol is designed for industry purpose. In this use case, broadcast protocol is assumed. On top of
Ethernet cable, data is broadcast with ID. Address configuration is not necessary here.
• Internet connection: M2M service platform and gateway(s) are connected by the Internet physically.
6.1.4 Pre-conditions
• PLCs and the gateway are connected to the Real-time Ethernet. PLCs broadcast data to the Real-time Ethernet.
The Gateway is configured to pick up necessary data from the Real-time Ethernet.
• On top of the internet, a VPN connection is established between the M2M service platform and the gateway(s).
• The data catalogue is managed by the M2M service platform.
6.1.5 Triggers
• Data catalogue is configured for the gateway to pick up data in the Real-time Ethernet.
6.1.6 Normal Flow
• The Gateway picks up the broadcasted data. It picks up only data that matches conditions described in the data
catalogue. If data does not match the conditions, the gateway ignores the data.
• The Gateway sends the collected data to the M2M service platform.
• The M2M service platform receives the data and stores it.
• The application utilizes the data. For example, it monitors the status of the production line.
• If the application user finds some problems in a production line, he/she changes the data catalogue in the M2M
service platform to collect all data related to the production line and sends the data catalogue to the targeted
gateway.
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 13 ETSI TR 118 518 V2.0.0 (2016-09)
6.1.7 High Level Illustration
Figure 6.1.7-1: High-level Illustration of On-demand Data Collection for Factories
6.1.8 Potential Requirements
1) The gateway shall be able to collect data from the field area network (e.g. industrial bus systems) according to
the data collection policy stored in the gateway.
2) The data collection policy shall be manageable (configured, updated, deleted, etc.) by M2M Applications on
the M2M service platform.
6.2 Integrity of Data Collection Monitoring
6.2.1 Description
In factories, a lot of data is created from PLCs every second and data is utilized to monitor production lines. This data is
available via industrial bus systems, e.g. Real-time Ethernet.
This type of data is called time series data which is a sequence of data points, typically consisting of successive
measurements made over a time interval.
In order to monitor remotely, data is gathered by the oneM2M service platform that needs to interface with such
industrial bus systems via the M2M gateway (MN).
When some of the data is lost due to various reasons, such as, damage of production line, temporal network delay,
continuous network capacity overload and so on, action will be required immediately for safety reasons. In addition,
some considerations may be necessary, such as switching to a new network service with larger capacity, changing to the
backup network or adjusting data collecting policy to address the original cause of data loss. Other considerations may
be effective when remote monitoring application queries the oneM2M platform about the condition of network traffic,
e.g. temporal delay, continuous capacity overflow, or connection failure.
ETSI
oneM2M TR-0018 version 2.0.0 Release 2 14 ETSI TR 118 518 V2.0.0 (2016-09)
Similar to the remote monitoring application, the MN in each factory receives the results of analysis or some
commands, which could be lost due to for example, failure in analysis process, temporal network delay, or continuous
network capacity overflow. The MN can detect the loss when the analysis results or the commands are in the form of
time series data, or it can detect potential loss by monitoring the condition of network traffic. When temporal network
delay or continuous network capacity overflow occurs, analysis results or commands may be lost. This loss also
requires immediate decision and addressing at the root cause.
This use case proposes that the oneM2M System shall be able to provide the capability to collect, store time series data
as well as monitor the integrity of the data.
Additionally, the oneM2M System shall be able to provide the capability to monitor the condition of network traffic.
6.2.2 Source
• REQ-2015-0522R04: Integrity of Data Collection Monitoring.
6.2.3 Actors
• PLC: It controls sensors and devices in a production line according to embedded programs. It also has
interface to Real-time Ethernet. It broadcasts data related to the production line to Real-time Ethernet.
• MN: It provides an interface from the
...