INTERNET OF THINGS
REFERENCE ARCHITECTURE
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.
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
AIOTI
ALLIANCE FOR INTERNET OF THINGS INNOVATION
Many related vertical and horizontal
activities
Heterogeneous Architectures
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
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.
ISO/IEC JTC 1/WG 10
Internet of Things Reference Architecture (IoT RA)
Reference
IoT Reference Architectur
Architecture – Goals e
and Objectives
IoT RA outlines
“what” the overall
structure approach
for the construction
of IoT systems and Conceptual Reference
indicates “how” Model Model
the architecture
and its domains or An abstract framework for
entities will It defines a common structure and
definitions describing the concepts understanding relationships among
operate and relationships with the IoT entities of an environment and for
systems developing consistent
specifications supporting that
environment
IoT RA
Structure
Clause Structure
CM contains
Characteristics
common
entities and Abstracted and generated to
their build
relationships Conceptual Model Reference Model
Develops
RM provides the
Create
basis to define s
different Architecture View
Architecture view
architectures
views
Conceptual Model
Conceptual
Model Build
Concepts Overall Model
Reference Model and
Architecture Views
Architecture Views
Functional View
is based on System View
Reference Model
Communication View
use
s Information View
Domain Concept
Usage View
Characteristics
Grouping 1st Level
Auto-configuration
Function and management capabilities
separation
Highly distributed systems
IoT System
Network communication
Characteristics
Network management and operation
Real-time capability
Self-description
Service subscription
Characteristics
Content-Awareness
IoT Service Characteristics Location-Awareness
Time-Awareness
Composability
Discoverability
IoT Component Modularity
Characteristics Network connectivity
Shareability
Unique identification
IoT Characteristics
Legacy support
Compatibility
Well defined components
Flexibility
Usability
Manageability
Accuracy
Robustness Reliability
Resilience
Availability
Confidentiality
Security
Integrity
Safety
Protection of Personally
Privacy
Identifiable Information
IoT Characteristics
Data - Volume, Velocity, Veracity, Variability and
Variety
Heterogeneity
Other Characteristics
Regulation compliance
Scalability
Trustworthiness
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, …
Real-Time Capability
Description
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.
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
CM – Overall Model for IoT
Concepts
Entity
IoT-
User
Is a Is a
Human Component Digital Entity Entity Identifier
Represents Has
Human Digital Virtual Physical
User User Entity Entity Tag
Interacts using Is contained within Contains Acts on
Monitors
Uses
Data
Is a
Applicatio
Service Source Sensor Actuator
n
Interacts with Interacts with
Interacts through Uses Interacts with Is a
Is a
Entity Component Component
Interacts through
Networ IoT- Connects IoT
k Gateway Device
Interacts through
CM – Entity and Domain Concepts
Domain
Contains Interacts with
Digital Entity
Includes
Entity
Contains Is a
Entity
Has
Physical Is a Nework
Entity Is a
Is a
Contains
IoT-User
CM – Domain Interactions
Domain A Domain B
Interacts
with
CM – Domain Composition
Domain A
Contains Contains
Domain B Domain C
CM → RM
Transforming Concept into a Model
Entity-based IoT RM
IoT Users
(Include Human, Devices/HMI)
Security and Privacy
Operation & Application Resource &
Network
Management Service Interchange
System System System Peer
Systems
IoT Gateway
(local services and
data)
IoT Devices
(Include sensors, actuators, and tags)
Physical Entity, including human Tags
© ISO/IEC CD 30141 – All rights reserved
Domain-based IoT RM
User Domain (UD)
Operations & Application Service Resource &
Management Domain Domain (ASD) Interchange Domain
(OMD) (RID)
Sensing & Controlling Domain (SCD)
Physical Entity Domain (PED)
© ISO/IEC CD 30141 – All rights reserved
Domain Composition
Inside-Domain Cross-Domain
Functions Functions
User Domain
Dynamic composition & Automated Interoperability
User Interface
Operation & IoT Resource &
Application
Management Service Domain
Interchange
Safety & Resilience
Domain domain
Life Cycle
Business API & Portal Resource Interchange
Managemen
Interoperability
Trust & Privacy
Support
Connectivity
t
Security
Access
Business Services Analytics
Security & Safety Control
Management
Regulation Logic & Rules Resource Management
Management
Local Modeling Asset Management Executor
Sensing &
Controllin Network Access
g Domain
Sensing Identification Actuation
Physical Entity
Domain
CM, RM and RA
Interplay and Relationship
Relationship between CM, RM
and RA
IoT Domains are derived from the
stakeholders, hardware and software: CM ->
RM -> RA
IoT RA IoT RA IoT RA
IoT RA IoT RA
IoT Conceptual Functiona Informati Communicati
Model System Usage
l on on
View View
View View View
IoT Reference
Model (Entity IoT Reference Model – Domain Based
Based)
IoT RA System View
IoT Resource and Interchange
Domain
Resource Access
Interchang
Manageme Manageme
e System
nt System nt System
Human
Users
Application Service
Domain
User Interface
Business Resource IoT Controlled
Service Service
Devices
Gatewa Physical Objects
System System Actuator
y
HMI
Local
Control Sensed Physical
Operation and System Objects
Management Domain Sensor
Digita
Physical Entity
l Regulation Sensing and
User Operation Domain
Management Control Domain
System
System
User Domain
Proximity
User Net Service Net Access Net
Net
Functional Model
Functional Model – Information
Flow
Communication View
IoT Architecture Models
ITU-T
ITU-T Y.2060 Model
Capabilities
Capabilities
Capabilities
Management
Capabilities
Capabilities
Capabilities
Security
Application IoT
Layer Applications
Service Support Generic Support Specific Support
& Application
Specific Management
Generic Management
Capabilities Capabilities
Support Layer
Networking Capabilities
Specific Security
Generic Security
Network
Layer
Transport Capabilities
Device
Device Generic
Generic Support
Support Specific
Specific Support
Support
Layer
Layer Capabilities
Capabilities Capabilities
Capabilities
ALLIANCE FOR INTERNET OF THINGS
INNOVATION
Reference Architecture
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
communicatio
n
“symbolic”
invokes
IoT Service associated Virtual
Entity
exposes
IoT Device
models &
tracks
“Things” Interacts with
AIOTI
ALLIANCE FOR INTERNET OF THINGS INNOVATION
Industrial Internet
Consortium
Reference Architecture
IIC Reference Architecture
Stakeholders Business Viewpoint
Biz vision, values, objectives &
Biz Decision capabilities
Makers
System Engineers
Product Managers
Why
Usage Viewpoint
System Engineers Usage activities
Functional Viewpoint
Product Managers Verb
What
System Architects Functional decomposition &
structures
Architects Noun Interfaces & interactions
Engineers
Developers Implementation Viewpoint
Integrators How Activity & functional to
Deployment technologies
Operations mapping
Hierarchy: The Factory
Entreprise The Old World: Industrie 3.0
Wor
k
• Hardware-based structure
Centers • Functions are bound to hardware
Station
• Hierarchy-based communication
• Product is isolated
Contro
l
Device
Field Device
Product
Graphics © Anna Salari, designed by freepik
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
Smart
hierarchy levels Factory
• Communication among all
participants
• Product is part of the
network
Smart
Products
Graphics © Anna Salari, designed by freepik
Reference Architectural Model Industry
Next-generation Industrial Manufacturing Systems
4.0
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
INTEL Architecture
Various Working Groups for
Innovation and interoperability
Working Group (Active
Charter Founding Members
Since)
Establish Internet Protocol (IP) as the network to
ARM, Atmel, Bosch, Cooper,
interconnect smart objects, and allow existing
IPSO Alliance (Sep 2008) Dust Networks, EDF, Ericsson,
infrastructure to be readily used without translation
Freescale et al
gateways or proxies
Developed an architectural reference model to allow ALU, Hitachi, IBM, NEC, NXP,
seamless integration of heterogeneous IoT SAP, Siemens, and
IoT-A (2010-2013)
technologies into a coherent architecture to realize universities – “Mission
‘Internet of Things’ rather than ‘Intranet of Things’ Accomplished late 2013”
Develop technical specifications for a common M2M
Leading ICT standards bodies
Service Layer to allow connectivity between devices
oneM2M (2012) namely ETSI, ARIB, TTC, ATIS,
and various M2M applications, to realize horizontally
TIA, CCSA and TTA
integrated Internet-of-Things
Collaborate for an open, universal IoT software
framework across devices and industry applications,
Qualcomm, in collaboration
AllSeen Alliance (2013) based on AllJoyn open source project, originally
with Linux Foundation
developed by Qualcomm but now released to
community developers
Industrial Internet Consortiu Accelerate development and adoption of intelligent
m AT&T, Cisco, GE, Intel, IBM
industrial automation for public usecases
(Mar 2014)
Various Working Groups for
Innovation and interoperability
Working Group (Active Since) Charter Founding Members
Develop an open specification for IoT that will make
ARM, BT, IBM, Intel,
HyperCat (May 2014) data available in a way that others could make use of it,
Living PlanIT, et al
through a thin interoperability layer.
Define interoperable device communication
Atmel, Broadcom, Dell,
Open Interconnect Consortium standards (for peer-to-peer, mesh & bridging, reporting
(Jul 2014)
Intel, Samsung and
& control etc.) across verticals, and provide an open
Wind River
source implementation
Create a standard interoperability architecture and IEEE; collaborating with
define commonly understood data objects, for oneM2M, ETSI and
IEEE P2413 (Jul 2014)
information sharing across IoT systems; Standardization other SDOs to evolve
targeted by 2016 joint standards
Create an open, secure, simple, power-
ARM, Freescale, Nest,
efficient protocol, based on robust mesh network that
Thread (2014) Samsung, Silicon Labs,
runs over standard 802.15.4 radios, and can support a
Yale
wide variety of home products
Proposed a new Light-weight M2M protocol standard,
OMA LWM2M (2014) based on client-server model for remote management OMA
of M2M devices and related service enablement
THANK YOU
