Enabling Things to Talk : : Designing IoT Solutions with the IoT Architectural Reference Model.

• Author: Bassi, Alessandro.
• TeilnehmendeR: Bauer, Martin.; Fiedler, Martin.; Kramp, Thorsten.; van Kranenburg, Rob.; Lange, Sebastian.; Meissner, Stefan.
• Place / Publishing House: Berlin, Heidelberg : : Springer Berlin / Heidelberg,, 2013.; ©2013.
• Year of Publication: 2013
• Edition: 1st ed.
• Language: English
• Physical Description: 1 online resource (352 pages)

This volume presents the results of a flagship European Commission project to map the conceptual reference model for the Internet of Things. It sets out an agreed IoT architecture of maximal interoperability, ready for use in real-world network development.

Table of Contents

Intro -- Foreword -- Acknowledgements -- Contents -- Chapter 1: Introduction to the Internet of Things -- Part I: General Concepts of the Architecture Reference Model (ARM) -- Chapter 2: The Need for a Common Ground for the IoT: The History and Reasoning Behind the IoT-A Project -- Chapter 3: The IoT Architectural Reference Model as Enabler -- 3.1 Using the IoT ARM -- 3.1.1 Cognitive Aid -- 3.1.2 Reference Model as a Common Ground -- 3.1.3 Generating Architectures -- 3.1.4 Identifying Differences in Derived Architectures -- 3.1.5 Achieving Interoperability -- 3.1.6 System Roadmaps and Product Life Cycles -- 3.1.7 Benchmarking -- 3.2 Architecture Development Process Based on the IoT ARM -- 3.2.1 Reference Model and Reference Architecture -- 3.2.2 Generating Architectures -- 3.2.3 Choice of Design and Development Methodology -- Chapter 4: IoT in Practice: Examples: IoT in Logistics and Health -- 4.1 Storyline of the IoT-A Use Case ``IoT in Retail and Logistics ́́-- 4.2 Introducing the ARM with a Recurring Example (Logistics) -- 4.3 Use of the ARM in the Scene ``Sensor-Based Quality Control ́́(Retail) -- 4.4 Storyline of the IoT-A Use Case ``IoT in Health and Home ́́-- 4.5 Use of the ARM in the Scene ``Remote Patient Notification ́́(Homecare) -- 4.6 Reverse Mapping of the ARM in the Scene ``In-Surgery Tracking of RFID-Tagged Stomach Towels ́́(Hospital) -- Part II: A Guidance to the Architecture Reference Model (ARM) -- Chapter 5: Guidance to the ARM: Overview -- 5.1 Chapter Structure -- 5.1.1 Chapter 6 ``A Process for Generating Concrete Architectures Process ́́-- 5.1.2 Chapter 7 ``IoT Reference Model ́́-- 5.1.3 Chapter 8 ``IoT Reference Architecture ́́-- 5.1.4 Chapter 9 ``Reference Manual ́́-- 5.1.5 Chapter 10 ``Concrete Architecture ́́-- 5.1.6 Chapter 11 ``Interactions ́́-- 5.1.7 Chapter 12 ``Testimonials ́́-- 5.2 ARM History and Evolution.

Chapter 6: A Process for Generating Concrete Architectures -- 6.1 Process Steps to Generate IoT Architectures -- 6.2 Compatibility with Other Architecting Methodologies -- 6.3 IoT Architecture Generation and Related Activities -- 6.3.1 Physical Entity View -- 6.3.2 IoT Context View -- 6.4 Requirements Process and ``Other Views ́́-- 6.4.1 Requirements Process -- 6.4.2 View Derivation -- 6.5 IoT ARM Contributions to the Generation of Architectures -- 6.6 Minimum Set of Functionality Groups -- 6.7 Usage of Unified Requirements -- 6.7.1 Introduction -- 6.7.2 Using Unified Requirements -- 6.7.2.1 Requirement Elicitation -- 6.7.2.2 System Specification -- 6.8 Threat Analysis -- 6.8.1 Elements to Protect -- 6.8.2 Risk Sources -- 6.8.3 Risk Assessment -- 6.8.4 Discussion -- 6.9 Design Choices -- 6.9.1 Introduction -- 6.9.2 Design Choices Addressing Evolution and Interoperability -- 6.9.3 Design Choices Addressing Performance and Scalability -- 6.9.3.1 Replication -- 6.9.3.2 Prioritize Processing -- 6.9.3.3 Partition and Parallelize -- 6.9.3.4 Reduce Computational Complexity -- 6.9.3.5 Distribute Processing Over Time -- 6.9.3.6 Minimize Used of Shared Resources -- 6.9.3.7 Reuse Resources and Results -- 6.9.3.8 Scale Up or Scale Out -- 6.9.3.9 Degrade Gracefully -- 6.9.3.10 Use Asynchronous Processing -- 6.9.4 Design Choices Addressing Trust -- 6.9.4.1 Harden Root of Trust -- 6.9.4.2 Ensure High Quality of Data -- 6.9.4.3 Infrastructural Trust and Reputation Agents -- 6.9.4.4 Provide High System Integrity -- 6.9.4.5 Avoid Leap of Faith -- 6.9.5 Design Choices Addressing Security -- 6.9.5.1 Subject Authentication -- 6.9.5.2 Use Access Policies -- 6.9.5.3 Secure Communication Infrastructure -- 6.9.5.4 Secure Peripheral Networks (Link Layer Security, Secure Routing) -- 6.9.6 Design Choices Addressing Privacy -- 6.9.6.1 Pseudonymisation.

6.9.6.2 Avoid Transmitting Identifiers in Clear -- 6.9.6.3 Minimize Unauthorized Access to Implicit Information -- 6.9.6.4 Enable the User to Control the Privacy Settings -- 6.9.6.5 Privacy-Aware Identification -- 6.9.7 Design Choices Addressing Availability and Resilience -- 6.9.7.1 Use High Availability Clustering -- 6.9.7.2 Load Balancing -- Logging Transactions -- Design for Failure -- Allowing Component Replication -- Relaxing Transactional Consistency -- Backup and Disaster Recovery Strategy -- 6.9.8 Design Choices Conclusion -- Chapter 7: IoT Reference Model -- 7.1 Introduction -- 7.2 Interaction of All Sub-Models -- 7.3 Domain Model -- 7.3.1 Definition and Purpose -- 7.3.2 Main Abstractions and Relationships -- 7.3.2.1 Interpreting the Model Diagram -- 7.3.2.2 The Concepts of the IoT Domain Model -- 7.3.3 Detailed Explanations and Related Concepts -- 7.3.3.1 Devices and Device Capabilities -- 7.3.3.2 Resources -- 7.3.3.3 Services -- 7.3.3.4 Identification of Physical Entities -- 7.3.3.5 Context and Location -- 7.4 Information Model -- 7.4.1 Definition of the IoT Information Model -- 7.4.2 Modelling of Example Scenario -- 7.4.3 Relation of Information Model to Domain Model -- 7.4.4 Other Information-Related Models in IoT-A -- 7.5 Functional Model -- 7.5.1 Functional Decomposition -- 7.5.2 Functional Model Diagram -- 7.5.2.1 IoT Process Management -- 7.5.2.2 Service Organisation -- 7.5.2.3 Virtual Entity and IoT Service -- Virtual Entity -- IoT Service -- 7.5.2.4 Communication -- 7.5.2.5 Management -- 7.5.2.6 Security -- 7.6 Communication Model -- 7.6.1 IoT Domain Model Element Communications -- 7.6.1.1 User-Service / Service-Service Interactions -- 7.6.1.2 Service / Resource / Device Interactions -- 7.6.2 Communication Interoperability Aspects -- 7.6.3 Composed Modelling Options -- 7.6.3.1 Gateway Configuration -- 7.6.3.2 Virtual Configuration.

7.6.4 Channel Model for IoT Communication -- 7.7 Trust, Security, Privacy -- 7.7.1 Trust -- 7.7.2 Security -- 7.7.2.1 Communication Security -- 7.7.2.2 Application Security: System Safety and Reliability -- 7.7.3 Privacy -- 7.7.4 Contradictory Aspects in IoT-A Security -- 7.8 Conclusion -- Chapter 8: IoT Reference Architecture -- 8.1 Short Definition of Architectural Views and Perspectives -- 8.2 Architectural Views -- 8.2.1 Usage of Views and Perspectives in the IoT Reference Architecture -- 8.2.2 Functional View -- 8.2.2.1 Devising the Functional View -- 8.2.2.2 IoT Process Management -- 8.2.2.3 Service Organisation -- 8.2.2.4 Virtual Entity -- 8.2.2.5 IoT Service -- 8.2.2.6 Communication -- 8.2.2.7 Security -- 8.2.2.8 Management -- 8.2.2.9 Mapping of Functional View to the Red Thread Example -- 8.2.3 Information View -- 8.2.3.1 Information Description -- Description of Virtual Entities -- Viewpoint for Modelling entityType Hierarchies -- Service Descriptions -- Associations Between Virtual Entities and Services -- 8.2.3.2 Information Handling -- 8.2.3.3 Information Handling by Functional Components -- General Information Flow Concepts -- Push -- Subscribe/Notify -- Publish/Subscribe -- Information Flow Through Functional Components -- User Requests Information from IoT Service -- User Gets Information from Virtual Entity-Level Service -- Service Gets Sensor Value from Device -- Sensor Information Storage -- IoT Service Resolution -- VE Resolution -- 8.2.3.4 Information Life Cycle -- 8.2.4 Deployment and Operation View -- 8.2.4.1 Deployment Example -- 8.3 Perspectives -- 8.3.1 Evolution and Interoperability -- 8.3.2 Performance and Scalability -- 8.3.3 Trust, Security and Privacy -- 8.3.3.1 Trust -- 8.3.3.2 Security -- 8.3.3.3 Privacy -- 8.3.4 Availability and Resilience -- 8.4 Conclusion -- Chapter 9: The IoT ARM Reference Manual.

9.1 Usage of the IoT Domain Model -- 9.1.1 Identification of Main Concept Instances -- 9.1.2 Modelling of Non-IoT-Specific Aspects -- 9.1.3 Identifiers and Addresses -- 9.1.4 Granularity of Concepts -- 9.1.5 Common Patterns -- 9.1.5.1 Augmented Entities -- 9.1.5.2 Multiple Virtual Entities -- 9.1.5.3 Smart Phones and Other Mobile User Devices -- 9.1.5.4 IoT Interactions -- 9.1.5.5 Simple Mediated Interactions -- 9.1.5.6 M2M Interaction -- 9.1.6 Examples for IoT Domain Model Concepts -- 9.1.6.1 User -- Application -- Human User -- 9.1.6.2 Physical Entity -- Environment -- Living Being -- Structural Asset -- 9.1.6.3 Resource -- On-Device Resource -- Network Resource -- 9.1.6.4 Service -- Interacting Services -- Service Associated with a Virtual Entity -- Service Accessing a Resource -- 9.1.6.5 Device -- Devices -- Hierarchical Devices -- 9.1.6.6 Deployment Configurations -- 9.1.7 Generating a Specific IoT Domain Model -- 9.2 Usage of the IoT Information Model -- 9.3 Usage of the IoT Communication Model -- 9.3.1 Guidelines for Using the IoT Communication Model -- 9.4 Usage of Perspectives -- Chapter 10: Interactions -- 10.1 Management-Centric Scenarios -- 10.1.1 Configuration of the System When Adding a Device -- 10.1.2 Changing the Device Configuration -- 10.2 Service-Centred Scenarios -- 10.2.1 Discovering Relevant Services Using IoT Service Resolution and VE Resolution -- 10.2.2 Managing Service Choreography -- Chapter 11: Toward a Concrete Architecture -- 11.1 Objective and Scope -- 11.2 Physical Entity View and IoT Context View -- 11.2.1 Physical Entity View -- 11.2.2 IoT Context View -- 11.2.2.1 Business Goals Revisited -- Pay-and-Display Machines (PDM) -- Today: Parking Ticket Identification -- Enhancement: Pay-by-License Plate -- Control Center -- Today: PDMs Monitoring Centre -- Enhancement: Connection to Web, and to the Registry Office.

Registry Office.