How to Build the Connectivity Architecture for the Industrial Internet of Things (IoT)

How to Build the Connectivity Architecture for the Industrial Internet of Things (IoT)Rajive Joshi, Ph. D.

Principal Solution Architect

Real-Time Innovations Inc.

February 25, 2015

Outline

• Industrial IoT is different!– Why? How? What?

• Open Interoperable Connectivity Architecture – Role, Model, Rules, Patterns, Realization

• Building the Connected Architecture– Generic Use Case

– Architecture Mapping

– Implementation

Industrial Internet of Things (IoT) is different!

Why? How? What?

4

Industrial Internet of Things (IoT)Quiz! What’s common?

Industrial Internet of Things (IoT)Why are they different?

• Operate in the real-world

– Non-stop

• Failure has severe consequences

– Loss of life or property, often both

• Data timeliness is critical

– Right answer delivered too late becomes the wrong answer!

Industrial Internet of Things (IoT)How are they different?

Technical Factors

• Scalability

– Volume, Variety

• Performance

– Velocity, Timeliness

• Resilience

– Availability, Recovery, Durability

• Security

– Authentication, Authorization, Integrity, Confidentiality, Non-Repudiation

Business Factors

• Reliability– Chance of failure during

anticipated lifetime

• Safety– No unintended consequences

• Longevity– Incremental upgrades on an

ongoing basis

• Diversity– Independent developers

– Multiple technologies

___________________________________________________________ ___________________

Page 2 10/29/2013 Connecting With the IIoT Copyright © 2013 Moor Insights & Strategy

What’s the Difference? As mentioned in our previous IoT paper, IIoT end-points must be more robust than HIoT end-points. Sensors embedded in end-points are not much help if the data they generate can’t be collected and transmitted for analysis.

We call these co llection points “gateways.” Figure 2: Gateway Function in IoT

There are many vectors along which we can measure end-point “robustness.” Table 1 summarizes these vectors: Table 1: Near-term end-point differences between IIoT and HIoT

Attribute Industrial IoT (IIoT) Human IoT (HIoT)

Market Opportunity Brownfield Greenfield

Product Lifecycle Until dead or obsolete Whims of style and/or budget

Solution Integration Heterogeneous APIs Vertically integrated

Security Access Identity & privacy

Human Interaction Autonomous Reactive

Availability 0.9999 to 0.99999 (4–5 ‘9 ’s) 0.99 to 0.999 (2–3 ‘9’s)

Access to Internet Intermittent to independent Persistent to interrupted

Response to Failure Resilient, fail-in-place Retry, replace

Network Topology Federations of peer-to-peer Constellations of peripherals

Physical Connectivity

Legacy & purpose-built Evolving broadband & wireless

Example Gateways Commercial monitoring Echelon SmartServer

Consumer home automation Revolv Hub

Market Opportunity: “Brownfield” is a term borrowed from commercial real estate; it is used to denote a potential site for building development that had been previously developed for industrial or commercial use. IIoT uses brownfield to describe the opportunity to connect more than a century of in-service mechanical and electrical systems to the Internet and therefore to new cloud-based services and analytics back-ends. The equipment doesn’t need to be re purchased, it ju st needs new, connected sensors. HIoT devices come prepackaged with sensors, their sensors are difficult to impossible to replace or upgrade without replacing the whole device, and therefore an entire system represents new market development. Even in the case of wearables, like

Cloud

GatewayHub

Wireless

Collectively referred to as a

Gateway

Sensors

and

Actuators

Source:http://www.moorinsightsstrategy.com/wp-content/uploads/2013/10/Connecting-with-the-Industrial-Internet-of-Things-IIoT-by-Moor-Insights-Strategy.pdf

Architecture Style Data Driven, Publish-Subscribe

Human Driven,Request-Response

Moore Insights report 2014

Industrial Internet of Things (IoT)What’s different?

http://www.moorinsightsstrategy.com/wp-content/uploads/2013/10/Connecting-with-the-Industrial-Internet-of-Things-IIoT-by-Moor-Insights-Strategy.pdf

http://www.moorinsightsstrategy.com/wp-content/uploads/2013/10/Connecting-with-the-Industrial-Internet-of-Things-IIoT-by-Moor-Insights-Strategy.pdf

Industrial Internet of Things (IoT)Common Pitfalls

Applying connectivity technologies meant for

human users

to

non-humans users*

*Time and again, people re-discover this!

Key Takeaways

• Industrial Internet of Things (IoT) is different!

– Why?

• Requirements

– How?

• Qualities: Technical and Business

– What ?

• Architecture and Techniques

Connectivity architecture must address the unique requirements of Industrial Internet Systems

Open Interoperable Connectivity Architecture

Role, Model, Rules, Patterns, Realization

Connectivity Architecture RoleInteroperability: Reduce Time to Integrate

Party A Party B

No standard exists, completely custom integration

Interfaces can be transformed/mapped

Interfaces use a common model

“Plug and Play” standard defined

Credit: Scott Neumann, UISol position paper

Data Centric Connectivity ArchitectureRule: Decouple apps from the Data

Data centricity enables interoperation, scale, integration

Messaging middleware

Databus

Unstructured filesDatabase

Data Centricity

Data Centricity

Connectivity Data Flow PatternsFundamental Building Blocks

Industrial IoT

• Stream

• Command

• Status

• Configuration

Conventional Enterprise IT

• Event

• Query

• Transaction

• Job

Architecture Style

Publish-Subscribe Request-Response

Activity Trigger

Data (State Change) Human (Decision)

DDS: The Connectivity Foundation for IIoTData-Centric Messaging Bus

• Data Distribution Service (DDS) is an open industry standard for data-centric connectivity

• From OMG, the world’s largest systems software standards organization– UML, DDS– Industrial Internet Consortium (IIC)

• DDS is Open & Multi-Vendor– Open Standard & Open Source– 12 implementations

Interoperability between source written

for different vendors

Interoperability between applications running on different

implementations

DDS-RTPS ProtocolReal-Time Publish-Subscribe

Distribution Fabric

DDS API

• ~800 Designs– Healthcare– Transportation– Communications– Energy– Industrial– Defense

• 15+ Standards & Consortia Efforts

DDS Industrial Internet ApplicationsCurrent Users

Connectivity Architecture using DDSConnect Everything, Everywhere

• Proximity• Platform• Language

• Physical network• Transport

protocol• Network

topology

DDS “DataBus”

Seamless data sharing regardless of:

Explicit Shared Data Model

with Controlled QoS

Connectivity Architecture using DDSInteroperability Between Subsystems

DDS Routing Service• Organize

– Hierarchy

• Bridge– Data models– Protocols– Security domains

• Isolate– Control export– Filter access– Translate models

Other protocols

Routing Service

Pluggable Adapters

Transformation Engine

System

Super System

SubsystemSubsystem

SubsystemSubsystem

Key Takeaways

• Connectivity Architecture Role– Interoperability to reduce integration time & effort

• Connectivity Architecture Model, Rules, Patterns – Decouple apps from data– Pick a core open connectivity standard– Use gateways to organize and bridge

• Connectivity Architecture Realization– Leverage the DDS open standard, popular in Industrial

Internet Systems, for integration of disparate connectivity protocols

– Leading DDS implementations provide all the connectivity fundamental building blocks

– Seamless data sharing from sensor to cloud

Building the Connected ArchitectureGeneric Use CaseArchitecture MappingImplementation

Connected HomeGadgets Service Provider Occupants

Cloud

Intelligent DeviceIntelligent Device

Intelligent Device

WANWAN

Many DevicesInternal LAN

Many Users

LANAt Home

• Fixed Network• Stable Addressing (relatively)• Ad-hoc components• Gateway

Cloud


Intelligent Device

WANWAN


Many Users

LANField technician on-site

• Fixed Network• Stable Addressing (relatively)• Managed Components• Gateway

Connected EnergyTurbines Operations Operators

Connected HealthcarePatient Monitors Hospital Doctors

Cloud


Intelligent Device

WANWAN


Many Users

LANDoctor at the Hospital

• Mobile Network• Dynamic Addressing • Certified Components• Gateway

Connected CarsCar Service Provider Drivers

Cloud


Intelligent Device

WANWAN


Many Users

LANIn the Vehicle

• Mobile Network• Dynamic Addressing • Qualified Components• Gateway

Generic Connectivity Use CaseDevices Cloud Users

Cloud


Intelligent Device

WANWAN


Many Users

LANOccasionally

• Mobile Network• Dynamic Addressing • Ad-hoc Components• Gateway

Connectivity Architecture Mapping Choosing the right technology

Cloud


Intelligent Device

WANWAN


Many Users

LANOccasionally

?

?

?

?


Cloud


Intelligent Device

WANWAN


Many Users

LANOccasionally

DDS- Stateful interactions and many data flow

patterns (now, future)- Publish-Subscribe architecture style, data

driven- Scalability, Performance, Resilience,

Security Requirements- Disconnected & Intermittent Links- Mobile Networks (Cellular and WiFi)


Cloud


Intelligent Device

WANWAN


Many Users

LANOccasionally

Web (Web-Sockets, HTTP)- Stateless interactions, single data flow

pattern (query)- Request-Response architecture style,

human driven- Established Scalability, Security

infrastructure- Forgiving Performance, Resilience

requirements- Ubiquitous access from any (mobile)

device or thin client


Cloud


Intelligent Device

WANWAN


Many Users

LANOccasionally



driven- Scalability, Performance, Resilience,

Security Requirements- Reliability, Safety, Longevity requirements- Diversity of transports and platforms


Cloud


Intelligent Device

WANWAN


Many Users

LANOccasionally



driven- Request-Reponse architecture style,

human driven- Scalability, Performance, Resilience,

Security- Longevity of Services- Diversity of connectivity solutions


Cloud


Intelligent Device

WAN


Many Users

LANOccasionally


DDS Databus

WAN

DDS Databus

Connectivity Architecture Deployment View

Cloud


Intelligent Device

WAN


Many Users

LANOccasionally


DDS Databus, Domain 1

WAN


Domain 0

Connectivity Architecture Deployment View

Cloud


Intelligent Device

WAN


Many Users

LANOccasionally



WAN


UDP, ShmemDomain 0

TCP

UDP, Shmem

Connectivity Implementation ExampleDeployment View: Nodes

demo.rti.com

osx(Mac OS Laptop)

WAN

Many Users

LANOccasionally


WAN


UDP, Shmem

Domain 0TCP

UDP, Shmem

vm1 (Linux Virtual Machine)

android(Nexus 7 Tablet with LTE)

WAN

Domain 0TCP

iPhone(iOS)

Connectivity Implementation ExampleDeployment View: Components

demo.rti.com

osx(Mac OS Laptop)

WAN

Many Users

LANOccasionally


WAN


UDP, Shmem

Domain 0TCP

UDP, Shmem

vm1 (Linux Virtual Machine)

android(Nexus 7 Tablet with LTE)

WAN

Domain 0TCP

iPhone(iOS)

rtiddsprototyper

rtiddsprototyper

rtiddsprototyperShapesDemo

nodejs DDS Connector

Articulate Concept

1. Draw a diagram of the components and the interconnecting data-flows

Define Structure

2. Define the data types for the interconnecting data flows (in IDL or XML)

3. Define the system structure as a collection of data-oriented interfaces (in XML)

Configure Behavior

4. Select from built-in Quality of Service (QoS) profiles to match the data flow pattern; extend to match special cases.

5. Code component behaviors

35

Connectivity Implementation ExampleComponent Development Webinar

Build it Fast:

5 Steps from Concept to Working

Distributed System

https://event.on24.com/eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=679529&sessionid=1&key=3180A4645BFBEF94DAAC485DC6E10713&partnerref=eletter

http://www.slideshare.net/RealTimeInnovations/build-it-fast-5-steps-from-concept-to-working-distributed-system-webinar-2013-09-25

http://www.slideshare.net/RealTimeInnovations/build-it-fast-5-steps-from-concept-to-working-distributed-system-webinar-2013-09-25

Human AccessCloud Users


iOS Safari

http://demo.rti.com:7401/simple

Network MobilityDevices Cloud

• Switching between Cellular and Wi-Fi

– Seamless data sharing

– State managed by DDS

iOS Safari

Wi-Fi


Network MobilityDevices Cloud

• Switching between Cellular and Wi-Fi

– Seamless data sharing

– State managed by DDS

iOS Safari

Cellular (LTE) – Different IP Address Seamless Data Sharing


Elastic Cloud ApplicationsCloud Apps Cloud Apps

• Adding/removing/upgrading components

– Data is decoupled from components



Elastic Cloud ApplicationsCloud Apps Cloud Apps

• Adding/removing/upgrading components

– New components independently created to work on the data



Connectivity Technology TriageWhen to use what technology?

• Is there a human at one end?– No! Use DDS

• Device Device

• Device Cloud

– Yes! Use DDS or Web-Sockets• User Device Cloud

– Web-browser Use HTML5+Web-sockets

– App Use DDS or HTML5+Web-sockets

• Ok to use DDS between – Humans

– Non-humans

– Non-humans and Humans

• Is it over a WAN?

– Yes! Use TCP (with TLS)

• Device Cloud

– No! (LAN) Use UDP (with multicast, if available)

• Cloud App Cloud App (within the Cloud LAN)

• Switching between Cellular and WiFi networks

– Use DDS to manage state, independently of the network mobility and switching

– Use DDS Quality of Service (QoS) to control the how the state is distributed and managed

Connectivity Technology TriageWith DDS, which transport to use?

Key Takeways

• Generic Connectivity Use Case– Devices Cloud Users

• Devices Cloud (over WAN)– Use DDS over TCP

• Devices Devices– Use DDS over UDP (LAN) or TCP (WAN)

• Cloud Apps Cloud Apps (within LAN)– Use DDS over UDP

• Cloud Users (WAN)– Use DDS over TCP, or– Use Web-Sockets + HTML (over TCP)

Parting Thoughts

Review

• Industrial IoT is different!– Why? How? What?

• Open Interoperable Connectivity Architecture – Role, Model, Rules, Patterns, Realization

• Building the Connected Architecture– Generic Use Case

– Architecture Mapping

– Implementation

Connectivity Architecture Edge to Cloud: Databus Hierarchy

Unit DataBusUnit DataBus

IntelligentMachines

IntelligentSystems

IntelligentIndustrial Internet

Cloud

Enterprise LAN

IntelligentSystem of Systems

Unit LAN Segment

Sense Act

Think HMI

Intra-machine

Think HMI

Intra-machine

Sense Act

Think HMI

Intra-machine

46

47

Industrial Internet of Things (IoT)Quiz! Answer: They all use RTI’s Connext DDS

Thank YouRajive Joshi, Ph. DPrincipal Solution ArchitectReal-time Innovations [email protected]

mailto:[email protected]

Start using DDS Today!Download the FREE complete RTI Connext

DDS Pro package for Windows and Linux:

• Leading implementation of DDS• C, C++, C#/.NET and Java APIs• Tools to monitor, debug, test, visualize and

prototype distributed applications and systems• Adapters to integrate with existing applications and

IT systems

Date post:	14-Jul-2015
Category:	Software
Upload:	real-time-innovations-rti
View:	1,031 times
Download:	2 times

How to Build the Connectivity Architecture for the Industrial Internet of Things (IoT)

Software