The IIC Connectivity Framework for IIoT
•Als PPTX, PDF herunterladen•
1 gefällt mir•652 views
The document discusses connectivity frameworks and standards for industrial IoT systems. It provides an overview of the Industrial Internet Consortium's Connectivity Framework, which defines different levels of interoperability and analyzes popular connectivity technologies and standards. The framework guides practitioners in assessing their requirements and choosing the appropriate connectivity standard for their system based on factors like data usage, latency needs, device interchangeability requirements, and integration with other systems and software. Popular standards discussed include DDS, OPC-UA, oneM2M, MQTT, and HTTP.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie The IIC Connectivity Framework for IIoT
Ähnlich wie The IIC Connectivity Framework for IIoT (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
The IIC Connectivity Framework for IIoT
- 1. How the IIC’s Connectivity Framework Guides IIoT Connectivity Selection John Breitenbach, Field Applications Engineer
- 2. The Industrial IoT is Smart Machine Infrastructure ©2017 Real-Time Innovations, Inc. Industrial Internet of Things (IIoT)Consumer Internet of Things (CIoT)
- 3. Education Colleges & Universities Conferences & Workshops Laboritories Publication Schools Trade Schools Aerospace & Defense Air Force Arrmy Aviation Home Land Security Military Navy Space Flight Agriculture Farming Fishing Forestry Hydrology Life Sciences Ranching Weather Buildings & Facilities Apartments Building & Construction Building Maintenance Building Security Commercial Buildings Construction Engineering Home Housing Authorities HVAC Office Real Estate Consumer & Home Automotive Commercial Cooking Consumer Products Day Care Elder Care Entertainment Food and Beverage Food Trucks Grocery Home Products Hospitality Pet Care Pharmacies Photography Recreation Services Restaurants Sporting Events Street Vendors Tourism Travel Energy & Utilities Chemicals Electric Mining Oil & Gas Petro-Chemicals Power Renewable Sewer Water Environment Air Pollution Control Biodiversity Eco-construction Environmental Monitoring & Instrumentation Environmental Research & Development Heat & Energy Saving and Management Metrology Nature Protection Noise & Vibration Control Oceanography Recycled Materials Remediation & Clean Up of Soil & Groundwater Renewable Energy Production Waste Management & Recycling Waste Water Treatment Water Supply Finance & Banking Accounting Systems ATM Systems Credit Card Systems Point of Sales Retail Banking Public Sector City Civil Administration Disaster Prevention Education Emergency & Crisis Response Environment Fire Law Enforcement & Police Municipalities & Counties Public Safety Public Security Surveillance Transportation Waste Management Water Healthcare Assisted Care Clinical Trials Connected Medical Devices Continuous Patient Monitoring Dentistry Disease Diagnosis Home Healthcare Hospitals Life Sciences Medical Offices Medical Therapy Pharma Pharmacies Media & Communication Cable Providers Computers Entertainment Global Media Phones Satellite TV Telecommunications Carriers Televisions Video Recorders Wireless Services Manufacturing Apparel Beverage & Tobacco Product Chemicals Computer & Electronic Products Electrical Equipment & Components Fabricated Metal Products Factory Food Furniture & Related Products Industrial Automation Leather & Allied Products Machinery Nonmetallic Mineral Products Paper Petroleum & Coal Plastics & Rubber Products Primary Metal Manufacturing Printing & Related Support Activities Textile Mills Textiles Transportation Equipment Wood Products Mining & Metals Aluminum Coal Diamonds & Gemstones General Mining Gold Iron & Steel Nonferrous Metals Platinum & Precious Metals Near Space & New Space Closed Loop Ecological Systems Closed Loop Living Systems Constellation Controllers Consumer Traffic Analytics Ecological Planning Environmental Monitoring Hyper-Local Agriculture Hyper-Local Construction Hyper-Spectral Imaging In-Flight Satelite Servicing On-Site Materials Analytics and Inventory On-Site Materials Optimization Parametric City Planning Parametric Construction Planning Remote Maintenance and Diagnostics Space Based Planning Weather Pattern Analytics Transportation Aeronautics Airport Cargo Handling Cruise Industry Fleet Management Freight Management Logistics Mobility Pipelines Postal & Delivery Services Public Transportation Rail Roads Shipping Traffic Infrastructure Transportation Trucking Vehicle Wholesale & Distribution Retail Apparel Retailers Broadline Retailers Drug Retailers Food Retailers & Wholesalers Home Improvement Retailers Specialized Consumer Services Specialty Retailers The IIoT will have a multi-trillion-dollar impact across all industries ©2017 Real-Time Innovations, Inc.
- 4. The Industrial IoT Disruption The real value is a common architecture that connects sensor to cloud, interoperates between vendors, and spans industries ©2017 Real-Time Innovations, Inc.
- 5. Agenda • Intro to the IIC Communications Framework • Levels of interoperability • Frameworks, transports, and protocols • Choosing a standard (in theory…) • Choosing a standard (in practice!) ©2017 Real-Time Innovations, Inc. Confidential
- 6. Real-Time Innovations, Inc. How Can We Build IIoT Systems? Connectivity Architecture
- 7. Industrial Internet Consortium: 270+ Companies, 30+ Countries IIC Founding and Contributing Members The World’s Largest IoT Consortium The IIC created the IIoT market
- 8. The Industrial Internet Connectivity Framework – The industry’s only detailed analysis of IIoT Connectivity Technologies – Architecture – Assessment – Standards • DDS • OPC UA • OneM2M • HTTP • MQTT • CoAP – Examples & selection guidance – Years of work by many architects across industries, standards, & technologies ©2017 Real-Time Innovations, Inc.Released Feb 28, 2017
- 9. IICF Goals Clarity GuidanceFoundation 10 Guide map to the rich but often confusing landscape of IIoT connectivity Useful, practical, tangible guidance for requirements assessment, technology evaluation and selection Sets a stable long term foundation for IIoT interoperability
- 10. http://en.wikipedia.org/wiki/Conceptual_interoperability Levels of Interoperability Shared data context Shared data structure Shared opaque data
- 11. Technical Interoperability Example… 12 Messages Share opaque data (byte sequences)
- 12. Syntactic Interoperability Example… 13 Messages Data (State, Events, Streams) TempType value units id Share structured datatypes
- 13. Semantic Interoperability Example… 14 Messages Data (State, Events, Streams) Information (Data in Context) TempType Room value 72.4 units DEGREES_F id 202 TempType Patient value 37.1 units DEGREES_C id Breitenbach ? Share data-objects in context
- 14. Evolution of the IIoT Connectivity Stack 15 7-Layer OSI Stack Model (1994) 4-Layer Internet Stack Model (1989) Industrial IoT (2014) Transport Link Framework Distributed Data Interoperability and Management Physical Network IIoT Connectivity Stack Model (2017)
- 15. IIoT Connectivity Stack Model Participant X Connectivity Information Networking IICF Focus Information (Data in Context) Participant X Transport Link Framework Distributed Data Interoperability and Management Physical Network Participant Y Data (State, Events, Streams) Messages Packets Frames Bits Transport Link Framework Distributed Data Interoperability and Management Physical Network Technical Interoperability (bytes) Syntactic Interoperability (data structures) Semantic Interoperability (data context)
- 16. Connectivity Transport Layer • Above: Technical Interoperability – Share byte sequences – Opaque data • Below: Byte protocol – May observe byte flows & optimize byte sequence sharing and delivery • Any computing platform Information (Data in Context) Participant X Transport Link Framework Distributed Data Interoperability and Management Physical Network Participant Y Data (State, Events, Streams) Messages Packets Frames Bits Transport Link Framework Distributed Data Interoperability and Management Physical Network
- 17. Connectivity Transport Layer Transport Link Distributed Data Interoperability & Management Framework Connectivity Transport Functions Physical Network Messaging Protocol Endpoint Addressing Connectedness Prioritization Timing & Synchronization Security Communication Modes Technical Interoperability
- 18. Connectivity Framework Layer • Above: Syntactic Interoperability – Share structured datatypes – Common and unambiguous data format • Below: Opaque Data – May observe data flows & optimize datatype sharing and delivery • Any computing platform • Any programming environment Information (Data in Context) Participant X Transport Link Framework Distributed Data Interoperability and Management Physical Network Participant Y Data (State, Events, Streams) Messages Packets Frames Bits Transport Link Framework Distributed Data Interoperability and Management Physical Network
- 19. Connectivity Framework Layer Transport Link Distributed Data Interoperability & Management Framework Quality of Service Security Publish-Subscribe Request-Reply Discovery Data Resource Model Id and Addressing Data Type System Lifecycle (CRUD) Exception Handling State Management Connectivity Framework Functions Physical Network API Governance Syntactic Interoperability
- 20. Fundamental N2 Connectivity Challenge Reality Check Accept that there will be multiple connectivity technologies • Brownfield • Existing technologies • May be specific to verticals • Greenfield • Innovation O(N2)
- 21. Connectivity Core Standards Architecture • Connectivity Core Standards – Provide syntactic interoperability – Stable, deployed, open standard – Standard Core Gateways to all other CCS • Domain-Specific Connectivity Technologies – Connect via non-standard gateway to any connectivity core standard Few Core Standards Standard Core Gateways Many domain technologies
- 22. Real-Time Innovations, Inc. Selecting the right connectivity technology Assessment Template Worksheets Connectivity Standards
- 23. Assessment Template • Which layers(s) of the Connectivity Stack does it provide? • What Core Functions does it provide? • How does it rank against the Typical Considerations (of the layers spanned) ? • How does it impact system Architectural Qualities? • Does it fit Connectivity Core Standard Criteria? Transport Link Framework Distributed Data Interoperability and Management Physical Network
- 25. IICF Catalog of Connectivity Standards! • Frameworks • DDS • OPC-UA • oneM2M • Transports • HTTP • MQTT • CoAP 26 Assessment Template Worksheets
- 26. Connectivity Standards Manufacturing Origin TSN / Ethernet (802.1, 802.3) DDS Wireless PAN (802.15) Wireless 2G/3G/LTE (3GPP) Wireless LAN (802.11 Wi- Fi) Internet Protocol (IP) CoAP MQTT Web Services Wireless Wide Area (802.16) HTTPDDSI-RTPS oneM2M OPC-UA OPC-UA Bin Telecommunications Origin UDP TCPTCP Transport Link Framework Distributed Data Interoperability and Management Physical Network Healthcare TransportationManufacturing… … Energy & Utilities
- 27. Core Connectivity Frameworks * = work in progress = supported, = not supportedGREEN = Gating Criteria
- 28. IICF Architecture Process Use assessment template worksheet to determine your system requirements Pick the potential connectivity core standard best aligned with your system requirements Build a gateway for other domain- specific connectivity technologies 29 Manufacturing Origin TS N / Eth ern et (80 2.1 , 80 2.3 ) DDS Wi rel es s PA N (8 02. 15 ) Wire less 2G/3 G/LT E (3GP P) Wi rel es s LA N (8 02. 11 Wi - Fi) Internet Protocol (IP) C o A P M Q T T We b Ser vic es Wi rel es s Wi de Ar ea (80 2.1 6) HTTP DDSI-RTPS oneM2M OPC-UA OPC -UA Bin Telecommunicati ons Origin UDP TCP T C P Transport Link Framework Distributed Data Interoperability and Management Physical N e t w o r k Healthcare Transportatio n Manufacturin g … … Energy & Utilities
- 29. Real-Time Innovations, Inc. Choosing a Connectivity Standard ©2017 Real-Time Innovations, Inc. Confidential
- 30. B CA X Your application: Choose A or B or C Requirement 1, e.g. latency Requirement2,e.g.fan-out IIoT Connectivity Perception ©2017 Real-Time Innovations, Inc.
- 31. B CA X Clearly A Clearly B Interstellar space Your application: Choose B; it’s the best you’ll get IIoT Connectivity Reality ©2017 Real-Time Innovations, Inc. Requirement 1, e.g. latency Requirement2,e.g.fan-out
- 32. How to Choose? ©2017 Real-Time Innovations, Inc. System Aspect Example User Approach Standard Software Integration & Autonomy Software Architect integrating components Data-centric DDS Device interchangeability Device manufacturer selling devices to technicians Device- centric OPC-UA Web & Mobile User I/F App builder supporting back-end services RESTful Web services/HTTP ICT integration Wide-area wireless telecom integrator Common services layer oneM2M
- 33. DDS is Different! ©2015 Real-Time Innovations, Inc. Data-Centric DDS Shared Data Model DataBus Point-to-Point TCP Sockets Client/Server MQTT XMPP OPC CORBA Brokered ESB Daemon Publish/Subscribe Fieldbus CANbus ZeroMQ JMS Queuing AMQP Active MQ
- 34. Systems are About the Data Data Centricity Definition a) The interface is the data. b) The infrastructure understands that data. c) The system manages the data and imposes rules on how applications exchange data. ©2016 Real-Time Innovations, Inc. Confidential. Database Databus Data centric storage and search of old data Data centric sharing and filtering of future data Application Application Message centric Remote Objects SOAs Application Application Data
- 35. Choose DDS? • Are there severe consequences if offline for a few mins/secs/msecs? • Have you said “millisecond” or “microsecond” in the last 2 weeks? • Do you have more than 10 programmers? • Does your data have many destinations? • Are you building a next-generation IIoT design? ©2017 Real-Time Innovations, Inc. 3+ Yes? ©2017 Real-Time Innovations, Inc.
- 36. OPC UA • Device-Centric Object-Oriented Framework – Device models for common devices – Integrate devices into workcells – Client-server architecture – Browseable address space – New simple UDP pub-sub Motor Starter 01 Configuration Control Function Local Operation Multifunction Input DI0 ParameterSet Motor Parameters Motor Current Low Motor Current High Service Info Number of Starts Motor Starter 01 Parameter Set Control Function Local Operation Configuration Multifunction Input DIO Motor Current Low Motor Current High Number of Starts Motor Current Low Motor Current High Service Info Address Space ©2017 Real-Time Innovations, Inc.
- 37. Choose OPC UA? • Are you in in discrete manufacturing? • Are you building a device that will be integrated by non-software types? • Will your product be used in different applications in different systems, as opposed to a single (type of) system where you control the architecture? • Have you said the word “workcell” in the last two weeks? 3+ Yes? ©2017 Real-Time Innovations, Inc.
- 38. OneM2M • Common Service Layer Architecture – Services provided by telco – Platform Tier (cloud) applications can seamlessly connect to diverse IoT devices over many protocols • Targets home automation, large mobile systems • Typical uses – Register and connect to devices and applications – Charge an account for service – Manage application and devices – Monitor systems ©2017 Real-Time Innovations, Inc.
- 39. Choose OneM2M? • Do you know what “ICT” stands for, and is that you? • Is the cellular network your primary connection technology? • Are your target applications largely composed of moving parts? • Can the components of your system tolerate intermittent connections and loosely-controlled latencies? • Will your system leverage services provided by a communications provider such as a telco? 3+ Yes? ©2017 Real-Time Innovations, Inc.
- 40. MQTT: Collect Device Data Message Queuing Telemetry Transport (MQTT) Collect data from sensors For cloud MQTT does not qualify as a core connectivity standard because it has no standard type system
- 41. Choose MQTT? • Do you think of your application as data collection? • Is there little device-device communications? • Is interoperability not a consideration? • Do you have many small devices? • Is software a minor challenge? ©2017 Real-Time Innovations, Inc. 3+ Yes?
- 42. The real value is a common architecture that connects sensor to cloud, interoperates between vendors, and spans industries ©2017 Real-Time Innovations, Inc. You don’t compete against competitors. You compete against market transitions. – John Chambers The Industrial IoT Disruption
- 43. Get It! 1. Introduction 2. Connectivity Framework 3. Connectivity Reference Architecture 4. Connectivity Framework Layer 5. Connectivity Transport Layer 6. How to Assess a Connectivity Technology? 7. Connectivity Standards 8. Core Connectivity Standards 9. Other Connectivity Standards 10. Assessment Templates https://www.iiconsortium.org/IICF.htm FREE
- 44. Free eBook! • Introduces readers to the fundamentals of the Industrial IoT ©2017 Real-Time Innovations, Inc. Confidential FREE https://www.rti.com/resources/leading-applications
- 45. Real-Time Innovations, Inc. Thank You! John Breitenbach johnb@rti.com LinkedIn: www.linkedin.com/in/atlantex
Hinweis der Redaktion
- Nest is a thermal oscillator
- The IIC Vertical Taxonomy The IIoT is much larger than the Internet (that only really changed a few industries like banking and travel agencies). Its economic impact will be larger than the Internet, mobile phones & apps, and the cloud. Combined. It’s Big. Really big. Many things missing! Unmanned military vehicles. Hyperloop. Medical imaging. Emergency medicine & transport. Radiation therapy.
- There are some huge numbers out there. Cisco $19T. 50B devices. 2/3 of the world economy. The IoT may be hyped, but this isn’t just a technology like 3D printing or even Big Data. This is the revolution of our lives. It will change everything. Sensor to Cloud, Road to Hospital, Power to Plant Usable, performant, reliable, scalable. IIC is building the infrastructure that enables the IIoT to deliver on its promise. That inspires entire ecosystems.
- Its really a guide map addressing key questions, core functions, and typical considerations around IIoT connectivity May speak different languages in the different lands.
- IICF: Accelerating IIoT Clarity: It is a guide map to the rich but often confusing landscape of IIoT connectivity. Foundation: It defines the minimum expectations from IIoT connectivity and sets up a stable long term foundation for interoperability, critical for the next generation of IIoT capabilities. Guidance: It provides practical, useful, tangible guidance for IIoT connectivity requirements assessment, technology evaluation and selection.
- IIRA defines: Connectivity = Infrastructure for Communications Interoperability Example: Two people are integrable (level 1) if both are able to speak and listen; interoperable (level 2) if they speak the same language; and composable (level 3+) if they share similar educational background so that enables them to collaborate on specific tasks. Syntactic interoperability: make it easy to share types. Evolve those types. Be typesafe Semantic interoperability: select an existing or industry-specific model and use it. Generic data modeling is hard. Mandate all lower levels. Stop here. Above this is human work Level 0: Stand-alone systems. No Interoperability. Level 1: Technical Interoperability. A communication protocol exists for exchanging data between participating systems. On this level, a communication infrastructure is established allowing systems to exchange bits and bytes, and the underlying networks and protocols are unambiguously defined. Level 2: Syntactic Interoperability. A common structure to exchange information; i.e., a common data format is used. On this level, a common protocol to structure the data is used; the format of the information exchange is unambiguously defined. This layer defines structure. Level 3: Semantic Interoperability. The meaning of the data is shared; the content of the information exchange requests are unambiguously defined. This layer defines (word) meaning. There is a related but slightly different interpretation of the phrase semantic interoperability, which is closer to what is here termed Conceptual Interoperability, i.e. information in a form whose meaning is independent of the application generating or using it. Level 4: Pragmatic Interoperability is reached when the interoperating systems are aware of the methods and procedures that each system is employing. In other words, the use of the data – or the context of its application – is understood by the participating systems; the context in which the information is exchanged is unambiguously defined. This layer puts the (word) meaning into context. Level 5: Dynamic Interoperability: As a system operates on data over time, the state of that system will change, and this includes the assumptions and constraints that affect its data interchange.... Level 6: Conceptual Interoperability …
- This is a real on-the-wire trace! (using off the shelf tools)
- This is a real data-object trace! (using off the shelf tools)
- This is a hypothetical example of two possible semantic interpretations of the data.
- Framework & Transport Layer How to get interoperable data? What is the lingua franca? Get all parties to communicate! Assume, Networking layer already setup People know how to do this Recognize the other layers
- Role | Purpose
- Timing & Sync: PTP, NTP, TSN etc.
- Role | Purpose
- Data Resource Model = Meta-Model for modeling application data/resources Exception Handling = e.g. disconnects. Or when QoS cannot be met. System detects changes that cannot be healed.
- Connecting two systems requires matching many aspects, including protocol, data model, communication pattern, and “quality of service” parameters like reliability, data rate, or timing deadlines. Connect with a special-purpose “bridge”. Connecting N systems together in general requires (N-1)^2 bridges. Note: this is not scalability of the protocols themselves. This is translation between standards.
- 42 of them?
- Determine the right prescription Determine how a connectivity standards fits system requirements? Determine the alignment with connectivity core standards?
- Assessment Template Worksheet is is organized using IIRA Viewpoints
- Shows two sides of the coin: Reference model (hourglass) Implementation (standards, technologies) Why this list? Process: Start with a proposed connectivity core standards for the transport and the framework layer Pick from what exists and is used broadly across IIoT systems Use the IIoT connectivity considerations and requirements as a guide And then expand out to organize the other standards By vertical/use-case/applications/technology Scope it to standards relevant to IIoT systems Don’t try to be exhaustive in covering all the applicable standards Could become an intractable task with little practical utility Can be built up over time by the community using the assessment template
- IIoT Connectivity Core Standards Criteria applied to key connectivity framework standards. Look at the detailed assessment sheets for the specific details
- Out in interstellar space? Bring your towel!
- We got the biggest box! What about MQTT? Not a connectivity framework: no data model. Used only for collection
- What’s wrong with all of these? They are all about messages. The data is an afterthought. But distributed IIoT systems are all about the data. Data-Centric DDS is a fourth generation disruptive networking technology Point-to-Point. Doesn’t branch. Telephone, TCP Client/Server. Branches, but choke points File systems, Database, RPC, CORBA, DCOM Good if information is naturally centralized Single point failure, performance bottlenecks, slow failover Publish/Subscribe Messaging. Branches, no bottlenecks. No data model. Magazines, Newspaper, TV Excels at many-to-many communications Excels at distributing time-critical information Queuing Extends PS concept to abstract receptors that can sequence between endpoints for load balancing, etc. Publish/Subscribe Data Replication Libraries, Distributed databases Excels at managing state and integration Loosely coupled: low integration & lifecycle costs Supports edge-to-enterprise, embedded
- The interface is the data. There are no artificial wrappers or blockers to that interface like messages, or objects, or files, or access patterns. The infrastructure understands that data. This enables filtering/searching, tools, & selectivity. It decouples applications from the data and thereby removes much of the complexity from the applications. The system manages the data and imposes rules on how applications exchange data. This provides a notion of "truth". It enables data lifetimes, data model matching, CRUD interfaces, etc. Databases are data-centric storage. They fit all the above: a) Data tables directly describe data. Unstructured databases also provide direct data access. Applications interact only with the table, not with the location of the data in a file. b) The database provides an environment to search, match, and manage data. I can access data, or write a tool that manipulates the data without talking to whoever put the data there. SQL is a language that leverages this power. c) The database imposes ACID properties. The data won't get corrupted, etc. In a system, the data in the database is Truth. (what's the right value of this data?) DDS is a data-centric communications. a "databus". It also fits all of the above: a) IDL defines data types, and then you interact with those types. b) You can filter data, write tools, & select what you want directly. We also leverage an SGL-like capability. c) The databus imposes QoS rules. The notion of truth is very well defined. It includes timing (how old is this data? how fast will I get it?) In summary, data-centric systems manage state directly. Applications interact by directly accessing that state. Note that the method of storage or the pattern of interaction is orthogonal. If you want a sound bite, I had one in my 2012 webinar on "The single most important decision in designing your distributed system": Will the apps manage truth & the infrastructure exchange messages? Or Will the infrastructure manage truth& the apps exchange state?
- Reliability: Easy redundancy, no servers Performance: Peer-peer, ms or µs delivery Scale: Integrate software modules & teams Data control: Right data, right time, right place Architecture: Next generation IIoT, 3+ yrs lifetime
- Telemetry is the highly automated communications process by which measurements are made and other data collected at remote or inaccessible points and transmitted to receiving equipment for monitoring. (wikipedia) A hub-and-spoke architecture is natural for MQTT. All the devices connect to a data concentrator server, like IBM's new MessageSight appliance. You don't want to lose data, so the protocol works on top of TCP, which provides a simple, reliable stream. Since the data is used by the IT infrastructure, the entire system is designed to easily transport data into enterprise technologies like ActiveMQ and ESBs. Only 3 QoS settings.
- There are some huge numbers out there. Cisco $19T. 50B devices. 2/3 of the world economy. The IoT may be hyped, but this isn’t just a technology like 3D printing or even Big Data. This is the revolution of our lives. It will change everything. Sensor to Cloud, Road to Hospital, Power to Plant Usable, performant, reliable, scalable. IIC is building the infrastructure that enables the IIoT to deliver on its promise. That inspires entire ecosystems.