iot high level architecture (hla) aioti - etsi!20151014deliverables... · iot high level...

41
IoT High Level Architecture (HLA) AIOTI Edited by AIOTI WG3 Chairs Patrick Guillemin Jean-Pierre Desbenoit AIOTI WG3 IoT High Level Architecture Release 2 14 October 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), Ovidiu Vermesan (Sintef), Martin Serrano (Insight) Supporters: Arthur Van Der Wees (Arthurslegal) AIOTI WG3 IoT Standardisation - Release 2 1

Upload: docong

Post on 05-Aug-2018

226 views

Category:

Documents


0 download

TRANSCRIPT

IoT High Level Architecture (HLA) AIOTI

Edited by AIOTI WG3 Chairs Patrick Guillemin

Jean-Pierre Desbenoit

AIOTI WG3 IoT High Level Architecture ndash Release 2 14 October 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) Ovidiu Vermesan (Sintef) Martin

Serrano (Insight) Supporters Arthur Van Der Wees (Arthurslegal)

AIOTI WG3 IoT Standardisation - Release 2 1

Objectives

bull Provide an initial proposal for a high-level architecture to serve as basis of the discussion within WG3 and across AIOTI WGs

bull This proposal is aiming to be neutral but its development did consider existing SDOs work

bull An important objective is to allow any instantiation pertaining to LSP deployments

AIOTI WG3 IoT Standardisation - Release 2 2

Approach using ISOIECIEEE 42010

bull Follow ISOIECIEEE 42010

bull Define models for relevant architecture views and donrsquot mix everything in one model

bull Focus on what makes IoT specialvaluable

bull Thing in centre of value creation

bull IoT is not just things + connectivity infrastructure services

AIOTI WG3 IoT Standardisation - Release 2 3

Principles of ISOIECIEEE 42010 bull An architecture description expresses an architecture of a system of

interest

bull An architecture description contains of multiple views

bull Each view adheres to a viewpoint

bull Each view consists of models

bull ISOIECIEEE 42010 specifies minimal requirements for

bull architecture descriptions

bull architecture frameworks

bull architecture description languages

bull architecture viewpoints

AIOTI WG3 IoT Standardisation - Release 2 4

WG3 HLA bull Is consistent with 42010 but does not provide a complete

architectural description

bull Provides partial Domain and Functional Models ndash The Domain Model describes entities in the domain and the relationships

between them

ndash The Functional Model describes operations interfaces and interactions within the domain

bull Specific use-cases are shown to illustrate the functional model and to highlight privacy issues

bull The relationship to other IoT architectures is also highlighted

AIOTI WG3 IoT Standardisation - Release 2 5

Domain Model (possible example)

6 AIOTI WG3 IoT Standardisation - Release 2

The Thing in IoT

7 AIOTI WG3 IoT Standardisation - Release 2

Functional model three layers approach

Application layer

IoT layer

Network layer

8 AIOTI WG3 IoT Standardisation - Release 2

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Objectives

bull Provide an initial proposal for a high-level architecture to serve as basis of the discussion within WG3 and across AIOTI WGs

bull This proposal is aiming to be neutral but its development did consider existing SDOs work

bull An important objective is to allow any instantiation pertaining to LSP deployments

AIOTI WG3 IoT Standardisation - Release 2 2

Approach using ISOIECIEEE 42010

bull Follow ISOIECIEEE 42010

bull Define models for relevant architecture views and donrsquot mix everything in one model

bull Focus on what makes IoT specialvaluable

bull Thing in centre of value creation

bull IoT is not just things + connectivity infrastructure services

AIOTI WG3 IoT Standardisation - Release 2 3

Principles of ISOIECIEEE 42010 bull An architecture description expresses an architecture of a system of

interest

bull An architecture description contains of multiple views

bull Each view adheres to a viewpoint

bull Each view consists of models

bull ISOIECIEEE 42010 specifies minimal requirements for

bull architecture descriptions

bull architecture frameworks

bull architecture description languages

bull architecture viewpoints

AIOTI WG3 IoT Standardisation - Release 2 4

WG3 HLA bull Is consistent with 42010 but does not provide a complete

architectural description

bull Provides partial Domain and Functional Models ndash The Domain Model describes entities in the domain and the relationships

between them

ndash The Functional Model describes operations interfaces and interactions within the domain

bull Specific use-cases are shown to illustrate the functional model and to highlight privacy issues

bull The relationship to other IoT architectures is also highlighted

AIOTI WG3 IoT Standardisation - Release 2 5

Domain Model (possible example)

6 AIOTI WG3 IoT Standardisation - Release 2

The Thing in IoT

7 AIOTI WG3 IoT Standardisation - Release 2

Functional model three layers approach

Application layer

IoT layer

Network layer

8 AIOTI WG3 IoT Standardisation - Release 2

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Approach using ISOIECIEEE 42010

bull Follow ISOIECIEEE 42010

bull Define models for relevant architecture views and donrsquot mix everything in one model

bull Focus on what makes IoT specialvaluable

bull Thing in centre of value creation

bull IoT is not just things + connectivity infrastructure services

AIOTI WG3 IoT Standardisation - Release 2 3

Principles of ISOIECIEEE 42010 bull An architecture description expresses an architecture of a system of

interest

bull An architecture description contains of multiple views

bull Each view adheres to a viewpoint

bull Each view consists of models

bull ISOIECIEEE 42010 specifies minimal requirements for

bull architecture descriptions

bull architecture frameworks

bull architecture description languages

bull architecture viewpoints

AIOTI WG3 IoT Standardisation - Release 2 4

WG3 HLA bull Is consistent with 42010 but does not provide a complete

architectural description

bull Provides partial Domain and Functional Models ndash The Domain Model describes entities in the domain and the relationships

between them

ndash The Functional Model describes operations interfaces and interactions within the domain

bull Specific use-cases are shown to illustrate the functional model and to highlight privacy issues

bull The relationship to other IoT architectures is also highlighted

AIOTI WG3 IoT Standardisation - Release 2 5

Domain Model (possible example)

6 AIOTI WG3 IoT Standardisation - Release 2

The Thing in IoT

7 AIOTI WG3 IoT Standardisation - Release 2

Functional model three layers approach

Application layer

IoT layer

Network layer

8 AIOTI WG3 IoT Standardisation - Release 2

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Principles of ISOIECIEEE 42010 bull An architecture description expresses an architecture of a system of

interest

bull An architecture description contains of multiple views

bull Each view adheres to a viewpoint

bull Each view consists of models

bull ISOIECIEEE 42010 specifies minimal requirements for

bull architecture descriptions

bull architecture frameworks

bull architecture description languages

bull architecture viewpoints

AIOTI WG3 IoT Standardisation - Release 2 4

WG3 HLA bull Is consistent with 42010 but does not provide a complete

architectural description

bull Provides partial Domain and Functional Models ndash The Domain Model describes entities in the domain and the relationships

between them

ndash The Functional Model describes operations interfaces and interactions within the domain

bull Specific use-cases are shown to illustrate the functional model and to highlight privacy issues

bull The relationship to other IoT architectures is also highlighted

AIOTI WG3 IoT Standardisation - Release 2 5

Domain Model (possible example)

6 AIOTI WG3 IoT Standardisation - Release 2

The Thing in IoT

7 AIOTI WG3 IoT Standardisation - Release 2

Functional model three layers approach

Application layer

IoT layer

Network layer

8 AIOTI WG3 IoT Standardisation - Release 2

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

WG3 HLA bull Is consistent with 42010 but does not provide a complete

architectural description

bull Provides partial Domain and Functional Models ndash The Domain Model describes entities in the domain and the relationships

between them

ndash The Functional Model describes operations interfaces and interactions within the domain

bull Specific use-cases are shown to illustrate the functional model and to highlight privacy issues

bull The relationship to other IoT architectures is also highlighted

AIOTI WG3 IoT Standardisation - Release 2 5

Domain Model (possible example)

6 AIOTI WG3 IoT Standardisation - Release 2

The Thing in IoT

7 AIOTI WG3 IoT Standardisation - Release 2

Functional model three layers approach

Application layer

IoT layer

Network layer

8 AIOTI WG3 IoT Standardisation - Release 2

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Domain Model (possible example)

6 AIOTI WG3 IoT Standardisation - Release 2

The Thing in IoT

7 AIOTI WG3 IoT Standardisation - Release 2

Functional model three layers approach

Application layer

IoT layer

Network layer

8 AIOTI WG3 IoT Standardisation - Release 2

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

The Thing in IoT

7 AIOTI WG3 IoT Standardisation - Release 2

Functional model three layers approach

Application layer

IoT layer

Network layer

8 AIOTI WG3 IoT Standardisation - Release 2

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Functional model three layers approach

Application layer

IoT layer

Network layer

8 AIOTI WG3 IoT Standardisation - Release 2

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

High level functional model

Networks

IoT Entity

App Entity App Entity App Entity

things

1 1

2 2

3

1 Commandsdata structure

2 Interfaces to access IoT Entities

3 Data plane

4 Network control plane interfaces (location QoS etc)

Thing representation (incl semantic metadata)

Identification Analytics Semantics (query etc)

Location discovery Determinism Security Device mgmt

5

5 Horizontal services

QoS Determinism location Network security protection

Application

layer

IoT

layer

Network

layer

Note1 The list of IoT functions (in the IoT Entity) is not exhaustive

Note2 Network aspects are not the primary focus for this release of the HLA

4

3 4 3 4

AIOTI WG3 IoT Standardisation - Release 2 9

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Example of instance (1) device to device communication in local network

Network

App Entity App Entity 1

Device Device (Switch) (Light)

3 4 3 4

10 AIOTI WG3 IoT Standardisation - Release 2

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

IP VPN

Network

IoT

Entity

App Entity App Entity meter data aggregation

App Entity 1 1

2 2

3 4

Concentrator Utility Back-end server

Example of instance 2 smart meter concentrator Utility back-end

2

Smart meter

IoT

Entity

Smart city data center

3 4

3 4

5

11 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Relationship to IERC

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

12 AIOTI WG3 IoT Standardisation - Release 2

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Relationship to IoT-A

Network

IoT Entity

App Entity App Entity App Entity

1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

The IoT-A domain model can be used for things and device representations (metadata)

13 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Relationship to Siemens IoT Functional Model

Network

IoT Entity

App Entity App Entity App Entity 1 1

2 2

3 3 4 4

3 4 5

Application

layer

IoT

layer

Network

layer

14 AIOTI WG3 IoT Standardisation - Release 2

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Relationship to Semantic interoperability track

15 AIOTI WG3 IoT Standardisation - Release 2

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Relationship to semantics

IoT Entity

things Things representation

Data (eg temperature

)

Metadata

Semantic description

Other metada (eg digital right

management and privacy related)

instantiates

Domain model

represents

16 AIOTI WG3 IoT Standardisation - Release 2

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Example of semantic descripton using RDF

IoT Entity

things Things representation

Data (eg temperature)

Metadata

Semantic description

Other metada (access control)

represents

ltrdfRDF

ltrdfDescription rdfabout=httpwwwtnocomsarefWASH_LG_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingMachinegt

ltsarefhasManufacturergtLGltsarefhasManufacturergt

ltsarefhasDescriptiongtVery cool Washing MachineltsarefhasDescriptiongt

ltsarefhasLocation rdfresource=httpwwwtnocomsarefBathroomgt

ltmsmhasService rdfresource=httpwwwtnocomsarefWashingService_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingService_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingServicegt

ltmsmhasOperation rdfresource=httpwwwtnocomsarefWashingOperation_123gt

ltrdfDescriptiongt

ltrdfDescription rdfabout=httpwwwtnocomsarefWashingOperation_123gt

ltrdftype rdfresource=httpwwwtnocomsarefWashingOperationgt

lthrhasMethodgtCreatelthrhasMethodgt

lthrhasURITemplategtCSE1WASH_LG_123startStopContainer lthrhasURITemplategt

ltmsmhasInput rdfresource=httpwwwtnocomsarefActiongt

ltrdfDescriptiongt

ltrdfRDFgt

17 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Relationship to SDO landscape

18 AIOTI WG3 IoT Standardisation - Release 2

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Continua example

Application

layer

Network

layer

IoT

layer

Animated slide

LPWA

19 AIOTI WG3 IoT Standardisation - Release 2

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Relationship to SDO architectures

20 AIOTI WG3 IoT Standardisation - Release 2

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

ITU-T architecture

AIOTI WG3 IoT Standardisation - Release 2 21

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Mapping AIOTI HLA to ITU-T

AIOTI WG3 IoT Standardisation - Release 2 22

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Mapping AIOTI HLA to oneM2M

AIOTI WG3 IoT Standardisation - Release 2 23

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Mapping AIOTI HLA to IIC

AIOTI WG3 IoT Standardisation - Release 2 24

IoT Entity

App Entity

App Entity

App Entity

2 IoT

Entity

5

3 4

3 4

App Entity

App Entity

App Entity

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Relationship to NIST Big Data

25 AIOTI WG3 IoT Standardisation - Release 2

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

AIOTI WG3 IoT Standardisation - Release 1 26

things App Entity IoT Entity 1

Gap

Animated slide

App Entity App Entity

2

1

2

Mapping AIOTI HLA to NIST Big data

AIOTI WG3 IoT Standardisation - Release 2

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Privacy considerations

Antonio Kung (TRIALOG)

27 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Example of context aware application Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data 28 AIOTI WG3 IoT Standardisation - Release 2

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Connectivity and Networks (including SDN)

IoT layer

Application Application Application

things

Data controller and data processor duties

Sensor Smart Phone Back end server

Minimize Hide Separate Aggregate

Inform Control enforce

demonstrate

Credential (eg ABC4Trust project) Protected Data

1b

1b 1a

1a Data Protected data

Data Controller

Data Processors

AIOTI WG3 IoT Standardisation - Release 2 29

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Potential gaps in standards

Antonio Kung (TRIALOG)

30 AIOTI WG3 IoT Standardisation - Release 2

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Architecture and Platforms

bull Slide 25 shows one important artefact Platforms

bull Slide 25 also shows that interactions between platforms might be needed

bull 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

bull Potential gap

31 AIOTI WG3 IoT Standardisation - Release 2

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Networks

IoT layer

Application Application

things

Example of platforms Smart Phone Back end server

Platform OneM2M

Platform universAAL

Platform FIWARE

Platform universAAL

1 Commandsdata structure

1 1

2

2 interfaces to access IoT entities

AIOTI WG3 IoT Standardisation - Release 2 32

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Applicability of AIOTI HLA to Smart City use cases - examples

33 AIOTI WG3 IoT Standardisation - Release 2

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

34

Smart Parking device network and applications

Device (and gateways)

bull Batterie operated sensing devices provide street parking occupancy information to a cellular gateway (few blocks) Parking operators report occupancy bull Cellular gateways provide connectivity to a (MNO) network bull Smart parking meter (payment enforcement)

Network

bull Wirless or wireline networks (SMS or mobile data connectivity) bull Meshed RF (by means of relays) for sensor network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parking and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

35

3G network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Meshed RF network

Mobile network

IoT E

AE =App Entity

IoT E =IoT Entity

AE

AE

AE

IoT E

AE

IoT E

AE

AE

AE

AE

3G network

IoT E

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

36

Smart Recharging of Fully Electric Vehicles (FEVs) and Smart Mobility device network and applications

Device ServersGateways

bull Smart recharging spot with sensing and actuator capabilities bull Cellular gateways provide connectivity to a (MNO) network bull Smart rechargingparking meter (payment enforcement) bull Smart nomadic device bull Smart FEV bull Server for Public transport schedule fed in bull Server for parking location with recharging facility availability management bull Server for UtilityGrid provision management bull Public FEV recharging spots (on highway) bull Aggregation server to broadcast the EV recharging spots bull Location based service content server

Network

bull Wirless or wireline networks (IPv6 based networks SMS or mobile data connectivity) bull LTE D2D IEEE 80211p bull Power distribution network

Applications

bull Android and iOS applications (leveraging existing developments) for locating parkingrecharging spots and mobile payments bull Pay by phone bull Enforcement applications (and devices) bull SMS reminders etc

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

37

3GLTE network

A possible solution

User device

Pay by phone

Locate (reserve)

Text reminders

Enforcement device

Locate cars that overstayed

(time limited areas)

Drivehand-held scanners

AE

Mobile network

(LTE D2D

IEEE 80211p)

AE =App Entity

IoT E =IoT Capabilities Entity

AE

AE

AE

AE

3GLTE network

IoT E

Public transport schedule feed-in

Parking recharging location availability management server

Public FEV recharging spots

Data aggregation server for broadcasting EV recharging spot data

Location based service content server

3GLTE network

Utility Provider

AE

= power distribution network

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E

AE

IoT E AE

IoT E

AE

IoT E

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

Annex Zoom on IoT-A domain model

38 AIOTI WG3 IoT Standardisation - Release 2

Alexander Bassi

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

IoT-A Domain

Model

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

IoT-A Domain Model

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things

IoT-A Domain Model

bull From an IoT Domain Model point of view Devices are only technical artefacts meant to provide an interface between the digital and the physical worlds For this reason Devices must be able to operate both in the physical and digital world and the IoT Domain Model only focuses on their capability to provide observation and modification of the physical environment from the digital environment If other properties of Devices were relevant the Device would be modelled as an entity itself

bull Resources are software components that provide some functionality When associated with a Physical Entity they either provide some information about or allow changing some aspects in the digital or physical world pertaining to one or more Physical Entities

bull Services are the mechanism by which needs and capabilities are brought together IoT Services provide well-defined and standardised interfaces hiding the complexity of accessing a variety of heterogeneous Resources The interaction with a Physical Entity can be accomplished via one or more Services associated with the corresponding Virtual Entity This association becomes important in the process of look-up and discovery An IoT Service can thus be defined as a type of Service enabling interactions with the real world

bull Augmented Entity is the composition of one Virtual Entity and the Physical Entity it is associated to in order to highlight the fact that these two concepts belong together The Augmented Entity is what actually enables everyday objects to become part of digital processes thus the Augmented Entity can be regarded as constituting the ldquoThingrdquo in the Internet of Things