ETSI ISG CIM - Directory Listing / to ISG CIM Goals of this public presentation Introduce the scope and status of ETSI ISG CIM for exchanging Context Information Explain "what is an

Introduction to ISG CIM

CONTEXT INFORMATION MANAGEMENT

Contact Lindsay Frost, ETSI ISG CIM Chairman. [email protected]

Public description of ideas, to obtain feedback.

ETSI ISG CIM

https://portal.etsi.org/CIM

mailto:[email protected]



Goals of this public presentation

Introduce the scope and status of ETSI ISG CIMfor exchanging Context Information

Explain "what is an ETSI ISG (Industry Specification Group)"

Explain the wide spectrum of applications intended, e.g. SmartCity, SmartAgrifood, SmartIndustry

Highlight the main features/requirements

Get feedback on our ideas and design choices (so far)

Hear "best practise" :for Semantics, IoT, Open Data and Open Source from Standardisation, Academic and Industry communities

Get "buy in" of potential users and interworking partners

© ETSI 2017. All rights reserved 2


Scope and status of ETSI ISG CIMfor exchanging Context Information

3© ETSI 2017. All rights reserved


Who is ISG CIM?

Industry Standardisation Group of ETSI (www.etsi.org )• composed of ETSI and non-ETSI members cooperating with a specific

scope of work (terms of reference), no fees, low overhead

• IPR rules and infrastructure same as ETSI (physical and virtual meetings)

• documents are published by ETSI

• lifespan of the ISG is typically 2 years (get the job done fast)

• work independent of other Technical Groups ("green field" development)

Member and Participant Organisations (20170906)


British Telecommunications plc (UK) M

Climate Associates Ltd (UK) M

Convida Wireless LLC (US) M

DEKRA Testing and Certification S.A.U. (ES) M

Easy Global Market SAS (FR) M

eG4U (FR) M

FACHHOCHSCHULE NORDWESTSCHWEIZ (CH) P

FIM UPM (ES) M

FIWARE FOUNDATION (DE) M

Future Cities Catapult (UK) M

GSM Association (UK) P

HOP Ubiquitous S.L. (ES) P

IMEC vzw (BE) M

INTRACOM TELECOM SOLUTIONS SA (GR) P

Knowledge Harvesting, Inc. (US) P

Korea Electronics Technology Institute (KETI) (KR) P

Localidata (ES) P

National Cyber Security Centre (NCSC) (UK) M

NEC Europe Ltd (UK) M

Nokia (DE) M

Odin Solutions S.L. (ES) P

Orange S.A. (FR) M

Telefonica S.A. (ES) M

TNO (NL) M

Ubiwhere, Lda (PT) M

http://www.etsi.org/

http://www.btplc.com/

http://www.climate-associates.com/

http://www.convidawireless.com/

http://www.dekra-product-safety.com/wireless

http://www.eglobalmark.com/

https://www.eg4u.org/

http://www.fhnw.ch/

http://www.upm.es/

http://www.fiware.org/

http://www.futurecities.catapult.org.uk/

http://www.gsma.com/

http://www.hopu.eu/

http://www.imec.be/

http://www.intracom-telecom.com/

http://www.knowledgeharvesting.com/

http://www.keti.re.kr/eng

http://www.localidata.com/

https://www.ncsc.gov.uk/

http://uk.nec.com/

http://company.nokia.com/

http://www.odins.es/

http://www.orange.com/

http://www.telefonica.es/

http://www.tno.nl/

http://www.ubiwhere.com/


Terms of Reference

Develop technical specifications and reports to enable multiple organisations to develop interoperable software implementations of a cross-cutting Context Information Management (CIM) Layer.

Define standard API for Context Information Management (CIM-API) enabling close to real-time update/access to information from many different sources (not only IoT).

Enable applications to register context providers, update context, get actual and historic context information, subscribe for notifications on context changes.

Identify appropriate ontologies & data publishing platforms.



Cross-domain Use Cases: 1

Cross-domain use cases exploit information usually hidden within different domains/deployments/implementations:• Smart Lighting and Smart Parking so that lighting is only provided

when car parking is booked and used in order to save energy.

• Smart Parking and HealthCare to ensure that parking spaces are available for health professionals when required on-call.

• Smart Buildings and Smart Mobility to ensure that (solar) power is used to charge electric vehicles when there is excess supply.

• SmartMobility and Environment, using air-quality information to choose/route traffic paths (cars, trucks, bicycles...)



Cross-domain Use Cases: 2

Cross-domain use cases exploit information usually hidden within different domains/deployments/implementations:• E-Health and Smart Appliances to monitor appliances to check if they

have been ‘left on’ by the user (detection of abnormal events).

• SmartGov and User App and IoT: book a public meeting room, from unoccupied subset, using mobile app

• Aggregating information from different domains for SmartCity KPIs

• Enhancing Linked Data with provenance information, allowing discovery of data based on topic, licensing, scope, quality, timeliness...

• Automatic reporting of pesticide and nutrients usage by geo-location, to optimize yields and also report to Environmental Agency



Context Information Management Layer- exchanging information between domains -

8

Open

Data

User

Apps

IoT

Information

Systems

Context

Information

Management

Data

Publication

PlatformsCIM-API

[JSON-LD]

Context

Information

Models

Mca

Ap

plicati

on

s

EXAMPLE:

Citizen

Complaints

Photo-App

Application

Ap

plicati

on

sCIM-API

[JSON-LD]

WiFi 5G LPWAN

© ETSI 2017. All rights reserved

• information-

centric

• interoperable

• replicable

• joining verticals

• improving

regulatory

compliance by

standardisation

Cross-domain: info producers/consumers in OpenData, User Apps, IoT


Context Information Management Layer- for a wide range of stakeholders -

9

Open

Data

User

Apps

IoT

Information

Systems

Context

Information

Management

Data

Publication

PlatformsCIM-API

[JSON-LD]

Context

Information

Models

Mca

Ap

plicati

on

s

EXAMPLE:

Citizen

Complaints

Photo-App

Application

Ap

plicati

on

sCIM-API

[JSON-LD]

WiFi 5G LPWAN

Smart City

organisations

System

Integrators

Linked Data

experts

OpenSource

developers

Stakeholders

Public

Authorities

Citizens!


Farmers


What is Context Information ?

contextual information: any information that can be used to characterize the situation of one or more entities and which is considered relevant to the interaction between a user and a service (e.g. software application), and other data elements, including the user and the service themselves

• Accordingly, the subject of context information is one or more entities, however whether the additional information is contextual depends on the interaction between the user and the service (i.e. some information is completely irrelevant and hence not contextual for a situation).

• In particular, context information includes that which further characterizes a value associated with an entity, rather than directly the entity itself.



Activities of ISG CIM



Context Information Management Layer- ETSI documents under development -

Open

Data

User

Apps

IoT

Information

Systems

Context

Information

Management

Data

Publication

PlatformsCIM-API

[JSON-LD]

Context

Information

Models

Mca

Ap

plicati

on

s

EXAMPLE:

Citizen

Complaints

Photo-App

Application

Ap

plicati

on

sCIM-API

[JSON-LD]

WiFi 5G LPWAN

CIM-002-UC CIM-003-GAP

CIM-004-APIprelim

CIM-005-DPP

CIM

-001-A

B (

MI )

CIM-006-MOD0

CIM

-007-S

EC

(G

R C

IM 0

07)


https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=51347








ETSI Work Item Scopes

See: https://portal.etsi.org/tb.aspx?tbid=854&SubTB=854

DMI/CIM-001-AB (MI ) Annotated Bibliography

DGR/CIM-002-UC (GR CIM 002) Use Cases

DGR/CIM-003-GAP (GR CIM 003) Architecture and Gap Analysis

DGS/CIM-004-APIprelim (GS CIM 004) API

DGS/CIM-005-DPP (GS CIM 005) Data Publication Platforms

DGS/CIM-006-MOD0 (GS CIM 006) Information Model(s)

DGR/CIM-007-SEC (GR CIM 007) Security and Privacy

NOTE: Work Items are being handled in parallel, with frequent

cross-checks for consistency, in order to rapidly converge.


https://portal.etsi.org/tb.aspx?tbid=854&SubTB=854









State of the art and Gap Analysis



CIM-003-GAP (GR CIM 003)Architecture and Gap Analysis

GAP ANALYSIS

What are the stakeholder goals and requirements ?

What kind of information needs to be exchanged ?

What kinds of queries/filters must be possible ?

How to help existing systems interwork ?

15

CIM-003-GAP





ISG CIM Metamodel: What kind of info do we need to express ?



ISG CIM Data Model instantiation example:- what information do we need to express?


Simple example:

Parking

WARNING: The symbols shown are for

discussion and are not necessarily final 17

c_Relationship

with c_Property

c_Relationship with

c_Relationship


ISG CIM Metamodel: UML view



ISG CIM Metamodel: Ontology view



ISG CIM Metamodel: Practical Guidelines


RETURNS ONLY ID

not infinite recursion


ISG CIM Metamodel: Instantiating ...



Developer Viewpoint



ISG CIM Metamodel: JSON-LD Representation- goal is a simple approach for developers -



ISG CIM API, REST Resources & Example


What is the response to this

example request?

GET /entities/Vehicle/P9876K

HTTP/1.1

accept: application/ld+json

link:

<http://example.org/Vehicle/context.js

onld>; rel="http://www.w3.org/ns/json-

ld#context"; type="application/ld+json”


Example response to a GET

GET /entities/Vehicle/P9876K HTTP/1.1accept: application/ld+jsonlink: <http://example.org/Vehicle/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json”

====================================

HTTP/1.1 200 OK...Content-Type: application/ld+json

26


Supported Architectures



Various Architectures possible using ISG CIM

28

Centralized DistributedFederated



29

Centralized

Some characteristics

• easier data

management

• context producers

are simpler

• all data needs to be

communicated

to a central entity

Conext

"Librarian"

Context

Producer

Context

Producer

Context

Producer

Context

Consumer

Context

Consumer

Context

Consumer

Update

Query

Subscribe/

Notify

Context

Producer &

Consumer



30

Distributed

Some characteristics

• data stays with

the source

• producers can

join ad hoc

• context sources

more complexContext

Source

Context

Source

Context

Source

Context

Consumer

Context

Consumer

Context

Consumer

Query

Subscribe/

Notify

Query

Subscribe/

Notify

Discover

Subscribe/

Notify

Discovery

Register

Discover

Subscribe/

Notify

Discovery

Registry

Server

Distribution

"Librarian"




Federated

Discover

Subscribe/

Notify

Discovery

Registry

Server

Federation

"Librarian"

Centralized

"Librarian"

Context

Producer

Context

Producer

Context

Producer

Centralized

"Librarian"

Context

Producer

Context

Producer

Context

Producer

Domains

Context

Source

Context

Source

Context

Source

Registry

Server

Distributed

"Librarian"

Register (coarse-

grained, scope-based)Query

Subscribe/

Notify


Supporting various Domains



Additional scenarios: KPIs example


An extensible system to model KPIs, including key properties like accuracy [527]


Additional scenarios: Provenance example


A provenance-aware quality ontology [567]


Interacting with other SDOs



IoT-related SDOs & Fora: "Formal" overview

ITU-T ITU-RJTC1

CEN CENELEC

De Jure SDOs PromotingDe Facto SDOs

UK Japan

...

National SDOs:

SG-20

Open-Source

AIOTI


Interacting with oneM2M Base Ontology


So

urc

e: O

ne

M2

M T

S-0

012-B

ase

_O

nto

log

y-V

3_

3_

0_

RE

VIS

ED

.do

cx

37


Servi

ce

Functio

n

Variab

le

(Value

)

ThingProp

erty

(Property)

Thi

ng

hasThingRel

ation

Stat

e

CIM-

Entity

Devic

e

consists

Of

subClas

sOf

hasServ

ice

exposesFunct

ion

Controlling

Function

Measuring

Function

hasFuncti

on

subClas

sOf

subClas

sOf

hasThingPro

perty

Operati

on

hasOpera

tion

…

…

OneM2M

Ontology

CIM CrossDomain

Ontology

CIM-

Relation

ship

hasSubStruct

ure

. . .ISG CIM

Cross-domain

Ontology

CIM-

Prope

rty

. . . . . .

Re-used

Ontologies 39

CIM-

Valu

e

CIM-006-MOD0

Mapping to oneM2M Base Ontology



Thank you ...

... so please join the effort to converge Context Information Management.

Contact for further information:[email protected]@neclab.eu(Lindsay Frost, Chairman of ETSI ISG CIM)[email protected](Cathy Mulligan, Vice-chairperson)

+ visit at: https://portal.etsi.org/CIM

40






References

[527] Kotoulas, Spyros. "Semantic and Reasoning Systems for Cities and Citizens." In Reasoning Web. Reasoning on the Web in the Big Data Era, pp. 369-387. Springer International Publishing, 2014. Accessed 20170821 at https://www.researchgate.net/profile/Spyros_Kotoulas/publication/300028433_Semantic_and_Reasoning_Systems_for_Cities_and_Citizens/links/5748547708ae2301b0b98152.pdf

[567] Baillie, Chris, Peter Edwards, and Edoardo Pignotti. "Qual: A provenance-aware quality model." Journal of Data and Information Quality (JDIQ) 5, no. 3 (2015): 12. Accessed 20170818 at http://aura.abdn.ac.uk/bitstream/handle/2164/6051/baillie_acm_jdiq_15.pdf?sequence=1


https://www.researchgate.net/profile/Spyros_Kotoulas/publication/300028433_Semantic_and_Reasoning_Systems_for_Cities_and_Citizens/links/5748547708ae2301b0b98152.pdf

http://aura.abdn.ac.uk/bitstream/handle/2164/6051/baillie_acm_jdiq_15.pdf?sequence=1


Appendix: Work Item Descriptions

42


CIM-002-UC

collect and analyse use cases and requirements for management of information coming from many different sources (not only IoT) and data models

allow applications to perform updates on context, register context providers, query information on current and historic context information and subscribe for receiving notifications

as possible, material shall be collected (by reference) from prior art and existing standards and specifications in this area

no restrictions on inclusion of use cases due to inability to be supported by a particular (popular) data architecture

use agreed template to allow better comparison, preferably based on e.g. in oneM2M, SmartM2M, or some major group.

20170327 43



CIM-002-UC

Analysis: indicate if use case compatibility with the architecture(s) discussed in Work Item GAP

Prioritization: use a decision matrix based on a list of weighted criteria, emphasizing cross-domain aspects

chosen subset of use cases will be used to guide later requirements for the Architecture and for the API specification(s)

A comprehensive global set of use cases is not required, just a set to define the problem space.

20170327 44



CIM-003-GAP

Goal: Identify a reference architecture and show positioning /compatibility to e.g. oneM2M.

initial focus should be on potential gaps in the OMA NGSI 9 and 10 abstract interface specifications.

Recommendations based on pro/con information, and referencing existing widely supported concepts.

An annex may be added to collect information on cross-domain Context Information Models, i.e. models that are common to several of the domains discussed in WI UC, together with the metamodels, definition languages and processes needed for the specification, curation, publication and evolution of Context Information Models.

20170327 45



CIM-003-GAP

There is a long list of issues to clarify and resolve, e.g.• handling of private vs public data,

• REST constraints,

• relationship of the CIM API to existing architectures like oneM2M,

• naming of entities,

• accounting of usage e.g. by feature and/or user group,

• security, public safety,

• timestamping and freshness of data,

• quality KPIs of data,

• managing multiple contexts,

• scalability.

• ...

20170327 46



CIM-004-APIprelim

Goal: (preliminary) definition of a standard API for Context Information Management enabling close to real-time access to information coming from many different sources (not only IoT).

define how such an API enables applications to perform updates on context, register context providers which can be queried to get updates on context, query information on current and historic context information and subscribe for receiving notifications on context changes.

The criteria for choice of the API characteristics shall be based on results in WI UC and WI GAP.

20170327 47



CIM-004-APIprelim

This Group Specification is labelled "preliminary" because it should be published widely in order to elicit comment and critique from the user communities and their comments will be used to modify and improve the later final API.

Accordingly a feedback process shall be described

This Group Specification shall be compatible with an example data model published at the same time (see Work Item CIM-005 MOD0), so that implementers of appropriate software can efficiently test and compare results and interoperability.

20170327 48



CIM-005-DPP

The purpose of this Group Specification is to analyse example data publications systems from the WI on Use Cases and identify requirements to be fulfilled by the CIM API for supporting open data publication, data privacy and/or authorization of access.

Part two of this work item will extend the analysis to e.g. enablers for multi-party access contracts. Such work may require external experts and may not be delivered within this preliminary specification.

20170327 49


Documents

ETSI ISG CIM - Directory Listing / to ISG CIM Goals of this public presentation Introduce the scope and status of ETSI ISG CIM for exchanging Context Information Explain "what is an