Ch. 7. Architecturen Standardization of WoT

1

Ch. 7. Architecture Standard-ization for WoT

Ch. 7. Architecturen Standardization of WoT

2

According to the WoT/IoT vision, every objects such as domestic appliances, actuators, and embedded systems of any kind in the near future will be concerned with each other and with the Inter-net.

7. 1. 1 Standards for M2M ETSI’s GSC M2M Standardization Task Force (MSTF) considers as

M2M any automated data exchange between machines including virtual machines such as software applications without or with limited human intervention.

The technical committee’s overall objective is creating open standards for M2M communications to foster the creation of a fu-ture network of objects and services.

The key elements of the ETSI M2M architecture are described be-low:• M2M devices• M2M area network (MAN)• M2M gateway

7.1 Platform Middleware for WoT

Ch. 7. Architecturen Standardization of WoT

3

• M2M communication networks• M2M application server

Ch. 7. Architecturen Standardization of WoT

4

7.1.2 Frameworks for WSN OGC SWE (Sensor Web Enablement) standardization effort

is intended to be a revolutionary approach for exploiting web-connected sensors such as flood gauges, air pollution monitors, satellite-borne earth-imaging device, and so forth.

The goal of SWE is creation of web-based sensor networks to make all sensors and repositories of sensor data discov-erable, accessible, and where applicable, controllable via the WWW.

SWE is a suite of standard encodings and web services that enable the following:• Discovery of sensors, processors, and observation.• Taking of sensors or models.• Access to observations and observation streams• Publish-subscribe capabilities for alerts• Robust sensor system and process descriptions

Ch. 7. Architecturen Standardization of WoT

5

7.1.3 Standards for SCADA ANSI/ISA-95 is an international standard for developing an au-

tomated interface between enterprise and control systems. The objectives of ISA-95 are to provide consistent terminology

that is a foundation for supplier and manufacturer communi-cation, to provide consistent information models, and to pro-vide a consistent operations model as a foundation for clarify-ing application functionality and how information is to be used.

OPC Unified Architecture

Ch. 7. Architecturen Standardization of WoT

6

7.1.4 Extensions on RFID standards The goal of CASAGRAS was to provide a framework of foun-

dation studies to assist the European Commission and the global community in defining and accommodating interna-tional issues and developments concerning RFID with par-ticular reference to the emerging IoT.

Ch. 7. Architecturen Standardization of WoT

7

7.2 Unified Multitier WoT Architecture 3GPP, OMA, may research projects and industrial products

aim to define and build a common middleware platform for WoT/IoT applications.

Tridium’s Niagara introduced the concept of a software framework that could normalize the data and behavior of di-verse devices, regardless of manufacturer or communication protocol, to enable the implementation of seamless, Inter-net-connected, web-based systems.

Ch. 7. Architecturen Standardization of WoT

8

7.2.1 SOA/EAI vs. SODA/MAI A service-oriented architecture (SOA) is a set of principles

and methodologies for designing and developing software in the form of interoperable services, usually over Internet.

EAI (enterprise application integration) is an integration framework composed of a collection of technologies and ser-vices which form a middleware to enable integration of sys-tems and applications across the enterprise.

The combination of the existing SOA (Internet) and EAI (in-tranet) technologies is good foundation for WoT/IoT applica-tions.

EAI can be extended for MAI (M2M application integration) within an intranet.

SOA can be used for WoT/IoT integration over the Internet and extranet.

Service-oriented device architecture (SODA) is proposed to enable device connection to an SOA

Ch. 7. Architecturen Standardization of WoT

9

Ch. 7. Architecturen Standardization of WoT

10

7.2.2 OSGi: The Universal Middleware The OSGi is a module system and service platform for the

Java programming language that implements a complete and dynamic component model.

Ch. 7. Architecturen Standardization of WoT

11

7.2.3 WoT Framework Based on Data Standards Multitiered IoT middleware

Ch. 7. Architecturen Standardization of WoT

12

The unified IoT middleware framework

Ch. 7. Architecturen Standardization of WoT

13

7.3 WoT Portal and Business Intelligent

Ch. 7. Architecturen Standardization of WoT

14

Ch. 7. Architecturen Standardization of WoT

15

There is no fundamental difference between IoT security and the traditional ICT system security.

A few challenges face the development of IoT in addition to traditional ICT security issues.• The heterogeneous, multi-hop, distributed networking environments

make the passing and translation of security credentials and the end-to-end security functionalities a very difficult mission across the four cate-gories of networks, that is, the long- and short-range wireless, and the long and short wired networks.

• These cryptographic suites were designed with the expectation that sig-nificant resource (e.g., processor speed and memory) would be avail-able.

• The joining and leaving of devices into the IoT systems and the grouping of the mobile devices over dynamic networks also add complexity to the authentication and authorization process.

7.4 Challenges of IoT Information Security