Upload
mariah-ellis
View
233
Download
0
Tags:
Embed Size (px)
Citation preview
IoT High Level Architecture (HLA) AIOTI
Edited by AIOTI WG3 ChairsPatrick 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 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 2
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 3
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 4
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 5
Domain Model (possible example)
AIOTI WG3 IoT Standardisation - Release 1 6
The Thing in IoT
AIOTI WG3 IoT Standardisation - Release 1 7
Functional model, three layers approach
Application layer
IoT capabilities layer
Network layer
AIOTI WG3 IoT Standardisation - Release 1 8
High level functional model
Networks
IoT Capabilities Entity
App Entity App Entity App Entity
things
1 1
2 2
3
1 Commands/data structure
2 Interfaces to access IoT capabilities
3 Data plane
4 Network control plane interfaces (location, QoS, etc)
Thing representation (incl. semantic metadata)Identification,Analytics, Semantics (query, etc.)
LocationdiscoveryDeterminismSecurityDevice mgmt.
5
5 Horizontal services
QoS, Determinismlocation,Network security, protection
Application layer
IoT Capabilitieslayer
Networklayer
Note1: The list of IoT capabilities listed in this slide are not exhaustiveNote2: Network aspects are not the primary focus for this release of the HLA.
4
3 4 3 4
AIOTI WG3 IoT Standardisation - Release 1 9
Example of instance (1): device to device communication in local network
Network
App Entity App Entity1
Device Device(Switch) (Light)
In this example the IoT capabilities layers is assumed to be covered by the App entity
3 4 3 4
AIOTI WG3 IoT Standardisation - Release 1 10
IP VPN
Network
IoT CapabilitiesEntity
App EntityApp Entity: meter data aggregation
App Entity1 1
2 2
3 4
Concentrator Utility Back-end server
Example of instance 2: smart meter, concentrator, Utility back-end
2
Smart meter
IoT CapabilitiesEntity
Smart city data center
3 4
3 4
5
AIOTI WG3 IoT Standardisation - Release 1 11
Relationship to IERC
Network
IoT Capabilities Entity
App Entity App Entity App Entity1 1
2 2
3 3 44
3 45
Application layer
IoT Capabilitieslayer
Networklayer
AIOTI WG3 IoT Standardisation - Release 1 12
Relationship to IoT-A
Network
IoT Capabilities Entity
App Entity App Entity App Entity1 1
2 2
3 3 44
3 45
Application layer
IoT Capabilitieslayer
Networklayer
The IoT-A domain model can be used for things and device representations (metadata)
AIOTI WG3 IoT Standardisation - Release 1 13
Relationship to Siemens IoT Functional Model
Network
IoT Capabilities Entity
App Entity App Entity App Entity1 1
2 2
3 3 44
3 45
Application layer
IoT Capabilitieslayer
Networklayer
AIOTI WG3 IoT Standardisation - Release 1 14
Relationship to Semantic interoperability track
AIOTI WG3 IoT Standardisation - Release 1 15
Relationship to semantics
IoT Capabilities Entity
thingsThings representation
Data (e.g. temperature
)
Metadata
Semantic description
Other metada (e.g. digital right
management and privacy related)
instantiates
Domain model
represents
AIOTI WG3 IoT Standardisation - Release 1 16
Example of semantic descripton using RDF
IoT Capabilities Entity
thingsThings representation
Data (e.g. temperature)
Metadata
Semantic description
Other metada (access control)
represents
<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 17
Relationship to SDO landscape
AIOTI WG3 IoT Standardisation - Release 1 18
Continua exampleAnimated slide
LPWA
AIOTI WG3 IoT Standardisation - Release 1 19
Privacy considerations
Antonio Kung (TRIALOG)
AIOTI WG3 IoT Standardisation - Release 1 20
Connectivity and Networks (including SDN)
IoTCapabilities
Application Application Application
things
Example of context aware applicationSensor Smart Phone Back end server
Minimize, Hide, Separate, Aggregate
Inform, Control, enforce,
demonstrate
Credential (e.g. ABC4Trust project)/ Protected Data
1b
1b1a
1a Data / Protected dataAIOTI WG3 IoT Standardisation - Release 1 21
Connectivity and Networks (including SDN)
IoTCapabilities
Application Application Application
things
Data controller and data processor dutiesSensor Smart Phone Back end server
Minimize, Hide, Separate, Aggregate
Inform, Control, enforce,
demonstrate
Credential (e.g. ABC4Trust project)/ Protected Data
1b
1b1a
1a Data / Protected data
DataController
DataProcessors
AIOTI WG3 IoT Standardisation - Release 1 22
Potential gaps in standards
Antonio Kung (TRIALOG)
AIOTI WG3 IoT Standardisation - Release 1 23
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 24
Networks
IoTCapabilities
Application Application
things
Example of platformsSmart Phone Back end server
PlatformOneM2M
PlatformuniversAAL
PlatformFIWARE
PlatformuniversAAL
1 Commands/data structure
1 1
2
2 interfaces to access IoT capabilitiesAIOTI WG3 IoT Standardisation - Release 1 25
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 26