1. REFERENCE ARCHITECTURE
INTERNET OF THINGS
REFERENCE ARCHITECTURE

2. Internet of Things
IoT is an infrastructure of interconnected physical entities, systems and information resources together with the intelligent services which can process and react information of both the physical world and the virtual world and can influence activities in the physical world.

3. EMERGING IoT
The emerging “Internet of Things” is a series of consumer, industrial, public sector and hybrid networks that are collectively use the Internet to create closed loop networks for connecting the cyber physical devices operational technology with sensors, controllers, gateways and services

4. Many related vertical and horizontal activities
AIOTI
ALLIANCE FOR INTERNET OF THINGS INNOVATION
Many related vertical and horizontal activities

5. Heterogeneous Architectures

6. Reference Architecture For IoT?
IoT devices are inherently connected – A model is needed to specify interactions with the devices
An architecture is needed to “tame” complexity and “achieve” scalability
Devices are expect to interact with themselves and the environment, continually – An architecture is need to achieve high-availability and support deployment across highly-heterogeneous computational platforms
Devices may not be designed for continuous “everyday” usage – An architecture is needed to support remote, automatic and managed updates of the IoT devices.
IoT devices are likely to be used for collecting and analyzing data – An architecture is need for managing the identity and access control for IoT devices to ensure privacy

7. Generic Reference Model, technologies,
IoT-A, is a “generic” architectural reference model, by the European Lighthouse Integrated Project, envisioned as foundations for reasoning about architectural principles and design guidelines for the emerging IoTs.

8. ISO/IEC JTC 1/WG 10
Internet of Things Reference Architecture (IoT RA)

9. IoT Reference Architecture – Goals and Objectives
IoT RA outlines “what” the overall structure approach for the construction of IoT systems and indicates “how” the architecture and its domains or entities will operate
Conceptual
Model
Reference
Model
An abstract framework for understanding relationships among entities of an environment and for developing consistent specifications supporting that environment
It defines a common structure and definitions describing the concepts and relationships with the IoT systems

10. IoT RA Structure CM contains common entities and their relationships
Clause Structure
CM contains common entities and their relationships
RM provides the basis to define different architectures views
Characteristics
Abstracted and generated to build
Conceptual Model
Reference Model
Develops
Creates
Architecture View
Architecture view

11. Conceptual Model
Conceptual Model
Build
Concepts
Overall Model

12. Reference Model and Architecture Views
Functional View
System View
is based on
Reference Model
Communication View
uses
Information View
Domain Concept
Usage View

13. IoT System Characteristics
Grouping
1st Level
IoT System Characteristics
Auto-configuration
Function and management capabilities separation
Highly distributed systems
Network communication
Network management and operation
Real-time capability
Self-description
Service subscription

14. Characteristics Content-Awareness IoT Service Characteristics
Location-Awareness
Time-Awareness
 IoT Component Characteristics
Composability
Discoverability
Modularity
Network connectivity
Shareability
Unique identification

15. IoT Characteristics Legacy support Compatibility
Well defined components
 Usability
Flexibility
Manageability
 Robustness
Accuracy
Reliability
Resilience
 Security
Availability
Confidentiality
Integrity
Safety
Protection of Personally Identifiable Information
 Privacy

16. IoT Characteristics
Other Characteristics
Data - Volume, Velocity, Veracity, Variability and Variety
Heterogeneity
Regulation compliance
Scalability
Trustworthiness

17. Autoconfiguration Characteristic
Description
Ability to automatically reconfigure a device based on the interworking of predefined rules
Relevance to IoT
Autoconfiguration is useful for IoT systems, as there are many and varied components that can change over time
It allows automatic maintenance and elimination of faulty components
DHCP, ZeroConf, UPnP, Bonjour, …

18. Real-Time Capability Description Relevance to IoT
Realtimeliness refers to a mode of operation where computation can control, monitor or respond in a timely manner to an external process when it occurs
Relevance to IoT
IoT systems may require stream processing, which requires acting on data events in progress in order to react “appropriately”
Example – Process control requires monitoring of and acting on a number of parameters, including temperature , flow, pressure or status of a device.

19. IoT Conceptual Model
CM defines the concepts of, and relationships among, the entities within IoT systems, in a generic, abstract and simple way.
The overall model of IoT entities and their relationships
The key concepts in a typical IoT system
The relationships between the entities, especially between digital entities and their physical entities
Identifies the actors and where they are located
Specifies how things and services collaborate via the network

20. CM – Overall Model for IoT Concepts
IoT-User
Entity
Is a
Is a
Human User
Human
Digital User
Component
Virtual Entity
Digital Entity
Physical Entity
Entity
Tag
Identifier
Represents
Has
Interacts using
Is contained within
Contains
Acts on
Monitors
Application
Service
Data Source
Sensor
Actuator
Is a
Uses
Interacts with
Interacts with
Interacts through
Uses
Interacts with
Is a
Is a
Network
Entity
IoT-Gateway
Component
IoT Device
Component
Interacts through
Connects
Interacts through

21. CM – Entity and Domain Concepts
Contains
Interacts with
Digital
Entity
Entity
Includes
Contains
Is a
Entity
Has
Physical Entity
Is a
Nework
Is a
Is a
Contains
IoT-User

22. CM – Domain Interactions
Domain A
Domain B
Interacts with

23. CM – Domain Composition
Domain A
Contains
Contains
Domain B
Domain C

24. CM → RM
Transforming Concept into a Model

25. Entity-based IoT RM IoT Users (Include Human, Devices/HMI) Network
Security and Privacy
Network
Application Service System
Operation & Management System
Resource & Interchange System
Peer Systems
IoT Gateway
(local services and data)
IoT Devices
(Include sensors, actuators, and tags)
Physical Entity, including human
Tags
© ISO/IEC CD – All rights reserved

26. Domain-based IoT RM User Domain (UD)
Operations & Management Domain (OMD)
Application Service Domain (ASD)
Resource & Interchange Domain (RID)
Sensing & Controlling Domain (SCD)
Physical Entity Domain (PED)
© ISO/IEC CD – All rights reserved

27. Domain Composition Inside-Domain Functions Cross-Domain Functions
User Domain
Security
Safety & Resilience
Trust & Privacy
Connectivity
Interoperability
Dynamic composition & Automated Interoperability
User Interface
Operation & Management Domain
Application Service Domain
IoT Resource & Interchange domain
Life Cycle Management
Business Support
API & Portal
Resource Interchange
Business Services
Analytics
Access Control
Security & Safety Management
Regulation Management
Logic & Rules
Resource Management
Local Modeling
Asset Management
Executor
Sensing & Controlling Domain
Network Access
Sensing
Identification
Actuation
Physical Entity Domain

28. CM, RM and RA
Interplay and Relationship

29. Relationship between CM, RM and RA
IoT Domains are derived from the stakeholders, hardware and software: CM -> RM -> RA
IoT Conceptual Model
IoT RA
Functional
View
IoT RA
System
View
IoT RA
Information
View
IoT RA
Usage View
IoT RA
Communication
View
IoT Reference Model (Entity Based)
IoT Reference Model – Domain Based

30. IoT RA System View User Interface Devices
IoT Resource and Interchange Domain
Interchange System
Resource Management System
Access Management System
Human
Users
User Interface Devices
Application Service Domain
Business Service System
Resource Service System
Controlled Physical Objects
IoT Gateway
Actuator
HMI
Local Control System
Sensed Physical Objects
Operation and Management Domain
Operation System
Regulation Management System
Sensor
Digital
User
Physical Entity Domain
Sensing and Control Domain
User Domain
User Net
Service Net
Access Net
Proximity Net

31. Functional Model

32. Functional Model – Information Flow

33. Communication View

34. IoT Architecture Models
ITU-T

35. ITU-T Y.2060 Model Application Layer IoT Applications Service Support
Support Layer
Specific Support
Capabilities
Generic Support
Management Generic Management Capabilities
Capabilities Specific Management Capabilities
Security Generic Security Capabilities
Capabilities Specific Security Capabilities
Network
Layer
Networking Capabilities
Transport Capabilities
Device
Layer
Device
Layer
Generic Support
Capabilities
Generic Support
Capabilities
Specific Support
Capabilities
Specific Support
Capabilities

36. ALLIANCE FOR INTERNET OF THINGS INNOVATION
Reference Architecture

37. AIOTI Model – Consolidated High Level IoT Reference Architecture
AIOTI WG03 IoT Reference Architecture
Consolidation of IoT reference architecture from many sources, i.e. IoT-A, IEEE P2413, OneM2M, ITU-T, ISO/IEC JTC1
Architectural views based on ISO/IEC/IEEE 42010
Domain Model ❑ Functional Model
User
Legend
contingent on communication
“symbolic”
invokes
IoT Service associated
Virtual Entity
exposes
IoT Device
models & tracks
Interacts with
“Things”
AIOTI
ALLIANCE FOR INTERNET OF THINGS INNOVATION

38. Industrial Internet Consortium
Reference Architecture

39. IIC Reference Architecture
Business Viewpoint
Biz vision, values, objectives & capabilities
Stakeholders
Biz Decision Makers
System Engineers
Product Managers
System Architects
Architects
Engineers
Developers
Integrators
Deployment
Operations
Why
What
How
Usage Viewpoint
Usage activities
Functional Viewpoint
Functional decomposition & structures
Interfaces & interactions
Verb
Noun
Implementation Viewpoint
Activity & functional to technologies
mapping

40. Hierarchy: The Factory
The Old World: Industrie 3.0
Hardware-based structure
Functions are bound to hardware
Hierarchy-based communication
Product is isolated
Entreprise
Work Centers
Station
Control
Device
Field Device
Product
Graphics © Anna Salari, designed by freepik

41. Axis 1 – Hierarchy: The Factory
The New World: Industrie 4.0
Connected World
Flexible systems and machines
Functions are distributed throughout the network
Participants interact across hierarchy levels
Communication among all participants
Product is part of the network
Smart Factory
Smart
Products
Graphics © Anna Salari, designed by freepik

42. Reference Architectural Model Industry 4.0
Next-generation Industrial Manufacturing Systems
A Reference model for all participants involved in Industry 4.0 discussions
Basic RAMI is extended by security capabilities – Security is built into each layer and each dimension

43. INTEL Architecture

45. Various Working Groups for Innovation and interoperability
Working Group (Active Since)
Charter
Founding Members
IPSO Alliance (Sep 2008)
Establish Internet Protocol (IP) as the network to interconnect smart objects, and allow existing infrastructure to be readily used without translation gateways or proxies
ARM, Atmel, Bosch, Cooper, Dust Networks, EDF, Ericsson, Freescale et al
IoT-A ( )
Developed an architectural reference model to allow seamless integration of heterogeneous IoT technologies into a coherent architecture to realize ‘Internet of Things’ rather than ‘Intranet of Things’
ALU, Hitachi, IBM, NEC, NXP, SAP, Siemens, and universities – “Mission Accomplished late 2013”
oneM2M (2012)
Develop technical specifications for a common M2M Service Layer to allow connectivity between devices and various M2M applications, to realize horizontally integrated Internet-of-Things
Leading ICT standards bodies namely ETSI, ARIB, TTC, ATIS, TIA, CCSA and TTA
AllSeen Alliance (2013)
Collaborate for an open, universal IoT software framework across devices and industry applications, based on AllJoyn open source project, originally developed by Qualcomm but now released to community developers
Qualcomm, in collaboration with Linux Foundation
Industrial Internet Consortium (Mar 2014)
Accelerate development and adoption of intelligent industrial automation for public usecases
AT&T, Cisco, GE, Intel, IBM

46. Various Working Groups for Innovation and interoperability
Working Group (Active Since)
Charter
Founding Members
HyperCat (May 2014)
Develop an open specification for IoT that will make data available in a way that others could make use of it, through a thin interoperability layer.
ARM, BT, IBM, Intel, Living PlanIT, et al
Open Interconnect Consortium
(Jul 2014)
Define interoperable device communication standards (for peer-to-peer, mesh & bridging, reporting & control etc.) across verticals, and provide an open source implementation
Atmel, Broadcom, Dell, Intel, Samsung and Wind River
IEEE P2413 (Jul 2014)
Create a standard interoperability architecture and define commonly understood data objects, for information sharing across IoT systems; Standardization targeted by 2016
IEEE; collaborating with oneM2M, ETSI and other SDOs to evolve joint standards
Thread (2014)
Create an open, secure, simple, power-efficient protocol, based on robust mesh network that runs over standard radios, and can support a wide variety of home products
ARM, Freescale, Nest, Samsung, Silicon Labs, Yale
OMA LWM2M (2014)
Proposed a new Light-weight M2M protocol standard, based on client-server model for remote management of M2M devices and related service enablement
 OMA

47. THANK YOU