IoT High Level Architecture (HLA) AIOTI Edited by AIOTI WG3 Chairs Patrick Guillemin Jean-Pierre Desbenoit AIOTI WG3 IoT High Level Architecture – Release 1 18 September 2015 Contributors: Omar Elloumi (ALU), Jean-Pierre Desbenoit (Schneider Electric), Patrick Wetterwald (Cisco), Georgios Karagiannis (Huawei), Juergen Heiles (Siemens), Paul Murdock (Landis+Gyr), Marco Carugi (NEC Europe) Supporters: Arthur Van Der Wees (Arthurslegal) AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 Objectives Provide an initial proposal for a high-level architecture to serve as basis of the discussion within WG3 and across AIOTI WGs This proposal is aiming to be neutral but its development did consider existing SDOs work An important objective is to allow any instantiation pertaining to LSP deployments AIOTI WG3 IoT Standardisation - Release 1

Approach using ISO/IEC/IEEE 42010 Follow ISO/IEC/IEEE 42010 Define models for relevant architecture views and don’t mix everything in one model Focus on what makes IoT special/valuable Thing in centre of value creation IoT is not just things + connectivity  infrastructure services AIOTI WG3 IoT Standardisation - Release 1

Principles of ISO/IEC/IEEE 42010 An architecture description expresses an architecture of a system of interest An architecture description contains of multiple views Each view adheres to a viewpoint Each view consists of models ISO/IEC/IEEE 42010 specifies minimal requirements for: architecture descriptions architecture frameworks architecture description languages architecture viewpoints AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 WG3 HLA Is consistent with 42010 but does not provide a complete architectural description Provides partial Domain and Functional Models The Domain Model describes entities in the domain and the relationships between them The Functional Model describes operations, interfaces and interactions within the domain Specific use-cases are shown to illustrate the functional model and to highlight privacy issues The relationship to other IoT architectures is also highlighted AIOTI WG3 IoT Standardisation - Release 1

Domain Model (possible example) AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 The Thing in IoT AIOTI WG3 IoT Standardisation - Release 1

Functional model, three layers approach Application layer IoT capabilities layer Network layer AIOTI WG3 IoT Standardisation - Release 1

High level functional model Networks IoT Capabilities Entity App Entity 1 1 Application layer things 2 2 Thing representation (incl. semantic metadata) Location discovery Determinism 5 3 4 Identification, Analytics, Semantics (query, etc.) Security Device mgmt. IoT Capabilities layer 3 4 3 4 QoS, Determinism location, Network security, protection Network layer 1 Commands/data structure 3 Data plane 5 Horizontal services Interfaces to access IoT capabilities 4 Network control plane interfaces (location, QoS, etc) 2 Note1: The list of IoT capabilities listed in this slide are not exhaustive Note2: Network aspects are not the primary focus for this release of the HLA. AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 Example of instance (1): device to device communication in local network App Entity App Entity 1 3 4 3 4 Network Device Device (Switch) (Light) In this example the IoT capabilities layers is assumed to be covered by the App entity AIOTI WG3 IoT Standardisation - Release 1

Example of instance 2: smart meter, concentrator, Utility back-end server Smart meter Network IoT Capabilities Entity App Entity App Entity: meter data aggregation 1 1 2 IP VPN 2 2 Smart city data center IoT Capabilities Entity 3 4 5 3 4 3 4 AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 Relationship to IERC 1 1 Network IoT Capabilities Entity App Entity Application layer 2 2 5 3 4 IoT Capabilities layer 3 3 4 4 Network layer AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 Relationship to IoT-A 1 1 Network IoT Capabilities Entity App Entity Application layer 2 2 5 3 4 IoT Capabilities layer 3 3 4 4 Network layer The IoT-A domain model can be used for things and device representations (metadata) AIOTI WG3 IoT Standardisation - Release 1

Relationship to Siemens IoT Functional Model Network IoT Capabilities Entity App Entity 1 1 Application layer 2 2 5 3 4 IoT Capabilities layer Georgios: This slide integrates the Siemens IoT Functional Model into the proposed architecture 3 3 4 4 Network layer AIOTI WG3 IoT Standardisation - Release 1

Relationship to Semantic interoperability track AIOTI WG3 IoT Standardisation - Release 1

Relationship to semantics things Things representation IoT Capabilities Entity represents Data (e.g. temperature) Domain model Metadata Semantic description instantiates Other metada (e.g. digital right management and privacy related) AIOTI WG3 IoT Standardisation - Release 1

Example of semantic descripton using RDF IoT Capabilities Entity things Things representation Data (e.g. temperature) Metadata Semantic description Other metada (access control) represents Example of semantic descripton using RDF <rdf:RDF     <rdf:Description rdf:about="http://www.tno.com/saref#WASH_LG_123">         <rdf:type rdf:resource="http://www.tno.com/saref#WashingMachine"/>         <saref:hasManufacturer>LG</saref:hasManufacturer>         <saref:hasDescription>Very cool Washing Machine</saref:hasDescription>          <saref:hasLocation rdf:resource="http://www.tno.com/saref#Bathroom"/>         <msm:hasService rdf:resource="http://www.tno.com/saref#WashingService_123"/>     </rdf:Description>    <rdf:Description rdf:about="http://www.tno.com/saref#WashingService_123"> <rdf:type rdf:resource="http://www.tno.com/saref#WashingService"/>         <msm:hasOperation rdf:resource="http://www.tno.com/saref#WashingOperation_123"/>     </rdf:Description>    <rdf:Description rdf:about="http://www.tno.com/saref#WashingOperation_123"> <rdf:type rdf:resource="http://www.tno.com/saref#WashingOperation"/>         <hr:hasMethod>Create</hr:hasMethod>         <hr:hasURITemplate>/CSE1/WASH_LG_123/startStopContainer </hr:hasURITemplate>         <msm:hasInput rdf:resource="http://www.tno.com/saref#Action"/>     </rdf:Description> </rdf:RDF> AIOTI WG3 IoT Standardisation - Release 1

Relationship to SDO landscape AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 Animated slide Continua example Application layer IoT Capabilities layer Network layer LPWA AIOTI WG3 IoT Standardisation - Release 1

Privacy considerations Antonio Kung (TRIALOG) AIOTI WG3 IoT Standardisation - Release 1

Example of context aware application Sensor Smart Phone Back end server 1a 1b Connectivity and Networks (including SDN) IoT Capabilities Application things Minimize, Hide, Separate, Aggregate Inform, Control, enforce, demonstrate 1a Data / Protected data AIOTI WG3 IoT Standardisation - Release 1 1b Credential (e.g. ABC4Trust project) / Protected Data

Data controller and data processor duties things Sensor Smart Phone Back end server 1a 1b Connectivity and Networks (including SDN) IoT Capabilities Application Data Processors Minimize, Hide, Separate, Aggregate Inform, Control, enforce, demonstrate 1a Data / Protected data AIOTI WG3 IoT Standardisation - Release 1 1b Credential (e.g. ABC4Trust project) / Protected Data

Potential gaps in standards Antonio Kung (TRIALOG) AIOTI WG3 IoT Standardisation - Release 1

Architecture and Platforms Slide 25 shows one important artefact: Platforms Slide 25 also shows that interactions between platforms might be needed Application A calls a FIWARE API for a capability that is provided by a universAAL platform: examples include federated identities and authentication, data brokers, etc. Potential gap? AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 Example of platforms things Smart Phone Back end server Application Application 2 IoT Capabilities 1 1 Platform OneM2M Platform universAAL Platform FIWARE Platform universAAL Networks 1 Commands/data structure 2 interfaces to access IoT capabilities AIOTI WG3 IoT Standardisation - Release 1

AIOTI WG3 IoT Standardisation - Release 1 Next steps Link to landscape Instantiation to specific LSP Link to semantic introp Mapping to specific SDO architecture Share this document with other WGs for feedback AIOTI WG3 IoT Standardisation - Release 1