(PRIYA) Rajgurunagar Call Girls Just Call 7001035870 [ Cash on Delivery ] Pun...
Build Safe & Secure Distributed Systems - RTI Boston Roadshow- 2014 09 30
1. Your systems. Working as one.
Build Safe & Secure Distributed Systems
How to Architect Scalable Systems for the Industrial Internet using Open Standards
21. Gateway
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 (49–5 ‘ ’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
Legacy & purpose-built Evolving broadband &
Connectivity
wireless
Example Gateways Commercial monitoring
Echelon SmartServer
Consumer home automation
Revolv Hub
Interaction Style Event Driven, Publish-Subscribe Request / Response
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
http://www.moorinsightsstrategy.com/wp-content/uploads/2013/10/Connecting-with-the-Industrial-Internet-of-Things-IIoT-by-Moor-Insights-Strategy.pdf
Moore Insights report 2014
32. Why Distribution Middleware?
1.0 Common Services
1.0 Common Services
RDR IFF ESM SAFE
RDR IFF ESM SAFE
DIA NAV MCP IPCC
DIA NAV MCP IPCC
DWC
Grouping the modules into functional clusters does nothing to change that reality
and ease software integration
UNCLASSIFIED
Hawkeye has functionally
oriented software modules
Each module talks to many
other modules
RIP TRK MSI
WAC TDA
L4 L11 L16 SEN DSC
HMI ACIS
MUX
FIL TDM
Adding new
functionality
cascades integration
re-work across many
other modules
CEC
8.0 Training
5.0 Communications
2.0 Sensors
3.0 Fusion
4.0 BMC2
7.0 Visualization
6.0 Sensor Control
RIP CEC TRK MSI
WAC TDA RAIDER
CHAT
SEN DSC
Distributed Data Framework
L4 L11 L16 IPv6
HMI ACIS T4O
MUX
FIL TDM aADNS TIS
Changing the communication between the modules can ease integration, when the
new ‘Publish Subscribe’ approach is used – each module publishes its output w/o
regard to who is receiving it, in contrast to the point-to-point approach of traditional
inter-process communication
It’s about an architecture that can assimilate evolving functionality,
rather than remaining set in time
111. Service
Plugin
Purpose Interactions
Authentication Authenticate the principal that is
joining a DDS Domain.
Handshake and establish
shared secret between
participants
The principal may be an
application/process or the user
associated with that
application or process.
Participants may messages to
do mutual authentication and
establish shared secret
Access Control Decide whether a principal is
allowed to perform a protected
operation.
Protected operations include
joining a specific DDS domain,
creating a Topic, reading a
Topic, writing a Topic, etc.
Cryptography Perform the encryption and
decryption operations. Create &
Exchange Keys. Compute digests,
compute and verify Message
Authentication Codes. Sign and
verify signatures of messages.
Invoked by DDS middleware
to encrypt data, compute and
verify MAC, compute & verify
Digital Signatures
Logging Log all security relevant events Invoked by middleware to log
Data Tagging Add a data tag for each data