INTERNET OF THINGS REFERENCE ARCHITECTURE Internet of Things

  • Slides: 47
Download presentation
INTERNET OF THINGS REFERENCE ARCHITECTURE

INTERNET OF THINGS REFERENCE ARCHITECTURE

Internet of Things Io. T is an infrastructure of interconnected physical entities, systems and

Internet of Things Io. T 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 Io. T The emerging “Internet of Things” is a series of consumer, industrial,

EMERGING Io. T 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

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

Heterogeneous Architectures

Heterogeneous Architectures

Reference Architecture For Io. T? Io. T devices are inherently connected – A model

Reference Architecture For Io. T? Io. T 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 Io. T devices are likely to be used for collecting and analyzing data – An architecture is need for managing the identity and access control for Io. T devices to ensure privacy

Generic Reference Model, technologies, Io. T-A, is a “generic” architectural reference model, by the

Generic Reference Model, technologies, Io. T-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 Io. Ts.

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

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

Io. T Reference Architecture – Goals and Objectives Reference Architecture Io. T RA outlines

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

Io. T RA Structure Clause Structure CM contains common entities and their relationships RM

Io. T RA Structure 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 Develops Reference Model Creates Architecture View Architecture view

Conceptual Model Build Concepts Overall Model

Conceptual Model Build Concepts Overall Model

Reference Model and Architecture Views Functional View Reference Model uses Domain Concept is based

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

Characteristics Grouping 1 st Level Auto-configuration Function and management capabilities separation Highly distributed systems

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

Characteristics Content-Awareness Io. T Service Characteristics Location-Awareness Time-Awareness Composability Discoverability Io. T Component Characteristics

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

Io. T Characteristics Compatibility Usability Robustness Security Protection of Personally Identifiable Information Legacy support

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

Io. T Characteristics Data - Volume, Velocity, Veracity, Variability and Variety Heterogeneity Other Characteristics

Io. T 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

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

Real-Time Capability Description Realtimeliness refers to a mode of operation where computation can control,

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 Io. T 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.

Io. T Conceptual Model CM defines the concepts of, and relationships among, the entities

Io. T Conceptual Model CM defines the concepts of, and relationships among, the entities within Io. T systems, in a generic, abstract and simple way. The overall model of Io. T entities and their relationships The key concepts in a typical Io. T 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 Io. T Concepts Entity Io. T-User Is a Human

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

CM – Entity and Domain Concepts Domain Contains Digital Entity Interacts with Entity Includes

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

CM – Domain Interactions Domain A Interacts with Domain B

CM – Domain Interactions Domain A Interacts with Domain B

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

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

CM → RM Transforming Concept into a Model

CM → RM Transforming Concept into a Model

Entity-based Io. T RM Io. T Users (Include Human, Devices/HMI) Application Service System Resource

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

Domain-based Io. T RM User Domain (UD) Operations & Management Domain (OMD) Application Service

Domain-based Io. T 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 30141 – All rights reserved

Domain Composition Cross-Domain Functions User Domain User Interface Business Services Security & Safety Management

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

CM, RM and RA Interplay and Relationship

CM, RM and RA Interplay and Relationship

Relationship between CM, RM and RA Io. T Domains are derived from the stakeholders,

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

Io. T RA System View Io. T Resource and Interchange Domain Human Users HMI

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

Functional Model

Functional Model

Functional Model – Information Flow

Functional Model – Information Flow

Communication View

Communication View

Io. T Architecture Models ITU-T

Io. T Architecture Models ITU-T

ITU-T Y. 2060 Model Network Layer Device Layer Generic Support Capabilities Specific Support Capabilities

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

ALLIANCE FOR INTERNET INNOVATION Reference Architecture OF THINGS

ALLIANCE FOR INTERNET INNOVATION Reference Architecture OF THINGS

AIOTI Model – Consolidated High Level Io. T Reference Architecture ❖ AIOTI WG 03

AIOTI Model – Consolidated High Level Io. T Reference Architecture ❖ AIOTI WG 03 Io. T Reference Architecture ➢ Consolidation of Io. T reference architecture from many sources, i. e. Io. T-A, IEEE P 2413, One. M 2 M, ITU-T, ISO/IEC JTC 1 ➢ Architectural views based on ISO/IEC/IEEE 42010 ❑ Domain Model User ❑ Functional Model Legend contingent on communication “symbolic” invokes Io. T Service associated Virtual Entity exposes Io. T Device models & tracks Interacts with “Things” AIOTI ALLIANCE FOR INTERNET OF THINGS INNOVATION

Industrial Internet Consortium Reference Architecture

Industrial Internet Consortium Reference Architecture

IIC Reference Architecture Stakeholders Business Viewpoint Biz vision, values, objectives & capabilities Biz Decision

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

Hierarchy: The Factory Entreprise Work Centers The Old World: Industrie 3. 0 • Hardware-based

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

Axis 1 – Hierarchy: The Factory The New World: Industrie 4. 0 Connected World

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 Smart Factory • Communication among all participants • Product is part of the network Smart Products Graphics © Anna Salari, designed by freepik

Reference Architectural Model Industry 4. 0 Next-generation Industrial Manufacturing Systems A Reference model for

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

INTEL Architecture

INTEL Architecture

Various Working Groups for Innovation and interoperability Working Group (Active Since) Charter Founding Members

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 ARM, Atmel, Bosch, Cooper, Dust smart objects, and allow existing infrastructure to be readily Networks, EDF, Ericsson, used without translation gateways or proxies Freescale et al Io. T-A (2010 -2013) Developed an architectural reference model to allow ALU, Hitachi, IBM, NEC, NXP, seamless integration of heterogeneous Io. T technologies into SAP, Siemens, and universities – a coherent architecture to realize ‘Internet of Things’ rather “Mission Accomplished late 2013” than ‘Intranet of Things’ one. M 2 M (2012) Develop technical specifications for a common M 2 M Service Leading ICT standards bodies Layer to allow connectivity between devices and various namely ETSI, ARIB, TTC, ATIS, M 2 M applications, to realize horizontally integrated Internet. TIA, CCSA and TTA of-Things All. Seen Alliance (2013) Collaborate for an open, universal Io. T software framework across devices and industry applications, based on All. Joyn open source project, originally developed by Qualcomm but now released to community developers Industrial Internet Consortium (Mar 2014) Accelerate development and adoption of intelligent industrial AT&T, Cisco, GE, Intel, IBM automation for public usecases Qualcomm, in collaboration with Linux Foundation

Various Working Groups for Innovation and interoperability Working Group (Active Since) Charter Founding Members

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

THANK YOU

THANK YOU