|
GROUP REPORT
Context Information Management (CIM);
Use Cases (UC)
Disclaimer
The present document has been produced and approved by the cross-cutting Context Information Management (CIM) ETSI
Industry Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.
---------------------- Page: 1 ----------------------
2 ETSI GR CIM 002 V1.1.1 (2018-09)
Reference
DGR/CIM-002-UC
Keywords
API, information model, interoperability, IoT,
smart city, use case
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI GR CIM 002 V1.1.1 (2018-09)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 Introduction . 8
4.1 Introduction to Context Information Management . 8
4.2 Information Sources . 10
4.3 Motivation for developing a Context Information Management System . 11
5 Methodology . 12
5.1 Approach to Documenting Use Cases . 12
5.1.1 Purpose . 12
5.1.2 Assumptions about a C3IM Architecture . 13
5.1.3 Use Case Sections . 13
5.2 Composing Use Cases . 15
5.3 Stakeholders . 15
5.4 Example Entity types. 16
5.4.0 Introduction. 16
5.4.1 Geospatial examples . 16
5.4.2 Provenance Data examples . 17
6 Simplified functional reference architecture . 17
7 Smart City Cross-cutting Use Cases . 18
7.1 Use Case 1 Sharing information between parking management systems and traffic management
applications. 18
7.1.1 Use Case 1 Introduction and Assumptions . 18
7.1.2 Use Case 1 Information Flow Diagram . 19
7.1.3 Use Case 1 Stakeholders . 19
7.1.4 Use Case 1 Agents and Data Source/Sink Entities . 20
7.1.5 Use Case 1 Scenario Descriptions and Data Flows . 21
7.1.5.1 Scenario "A": Routing to closest available parking space taking into account both real-time
availability of individual parking spaces across different parking providers AND street
congestion . 21
7.1.5.2 Scenario "B": exit from parking structure taking local traffic into account . 22
7.1.5.3 Scenario "C": Entry to Private Parking Space Rented on Temporary Basis . 23
7.1.5.4 Scenario "D": Smart Parking Facility Manager Queries . 23
7.1.5.5 Scenario "E": Reserved Parking for Care workers responding to in-home monitor alarm . 23
7.1.6 Use Case 1 Entities instances graph . 24
7.2 Use Case 2: Smart Street Lighting . 24
7.2.1 Use Case 2 Introduction and Assumptions . 24
7.2.2 Use Case 2 Information Flow Diagram . 25
7.2.3 Use Case 2 Stakeholders . 25
7.2.4 Use Case 2 Agents and Data Source/Sink Entities . 26
7.2.5 Use Case 2 Scenario Descriptions and Data Flows . 26
7.2.5.1 Scenario "A": Lighting Levels Depending on Traffic Presence . 26
7.2.5.2 Scenario "B": Lighting Levels Depending on Weather Conditions . 26
7.2.5.3 Scenario "C": Lighting Levels Depending on Traffic Management Decisions . 27
7.2.5.4 Scenario "D": Lighting Levels Depending on Crowdsourced Data . 27
ETSI
---------------------- Page: 3 ----------------------
4 ETSI GR CIM 002 V1.1.1 (2018-09)
7.2.6 Use Case 2 entity instances graph . 28
7.3 Use Case 3: Traffic Management & Pricing based on Air Quality, Congestion and other KPIs . 28
7.3.1 Use Case 3 Introduction . 28
7.3.2 Use Case 3 Information Flow Diagram . 29
7.3.3 Use Case 3 Stakeholders . 29
7.3.4 Use Case 3 Agents and Data Source/Sink Entities . 29
7.3.5 Use Case 3 Scenarios . 30
7.3.5.1 Scenario "A": Traffic Management to reduce Pollution Peak Levels . 30
7.3.5.2 Scenario "B": Traffic Management to reduce Pollution Peak Levels with price incentive . 30
7.3.5.3 Scenario "C": Traffic Routing to Avoid Polluted Routes . 31
7.3.5.4 Scenario "D": Access Price for downtown depends on Congestion and Size of Vehicle . 31
7.3.5.5 Scenario "E": Information Service on Pollution Levels and Pricing . 32
7.3.6 Use Case 3 Entities Instances Graph. 32
7.4 Use Case 4: Crowd Monitoring and Emergency Response . 32
7.4.1 Use Case 4 Introduction and Assumptions . 32
7.4.2 Use Case 4 Information Flow Diagram . 33
7.4.3 Use Case 4 Stakeholders . 33
7.4.4 Use Case 4 Agents and Data Source/Sink Entities . 34
7.4.5 Use Case 4 Scenario Descriptions and Data Flows . 34
7.4.5.1 Scenario "A": Population Evacuation taking into account resort crowd and external traffic info . 34
7.4.5.2 Scenario "B": First aid in resort during emergency taking into account resort crowd and available
resources . 35
7.4.6 Use Case 4 Entity instances graph . 35
7.5 Use Case 5: Management of Optical Fibre Network Deployment . 36
7.5.1 Use Case 5 Introduction and Assumptions . 36
7.5.2 Use Case 5 Information Flow Diagram . 37
7.5.3 Use Case 5 Stakeholders . 37
7.5.4 Use Case 5 Agents and Data Source/Sink Entities . 37
7.5.5 Use Case 5 Scenario Descriptions and Data Flows . 38
7.5.5.1 Scenario "A": Network Deployment Planning . 38
7.5.5.2 Scenario "B": Network In-Field Deployment . 38
7.5.6 Use Case 5 Entities instances graph . 39
8 Smart Agrifood Use Cases . 39
9 Smart Industry Use Cases. 40
Annex A: Selected "Vertical" Use Cases from the Literature . 41
Annex B: Authors & contributors . 43
History . 44
ETSI
---------------------- Page: 4 ----------------------
5 ETSI GR CIM 002 V1.1.1 (2018-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) cross-cutting Context
Information Management (CIM).
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 5 ----------------------
6 ETSI GR CIM 002 V1.1.1 (2018-09)
1 Scope
The present document discusses the concepts which are foundational for Cross-Cutting Context Information
Management (C3IM) and their application to a selection of Use Cases from the domains of Smart Cities, Smart
Agrifood and Smart Industry. These areas of application, together with the general area of Internet of Things (IoT)
technology and services, are expected to especially benefit from usage of cross-cutting (cross domain) context
information, and from a set of specifications for the APIs supporting C3IM.
The present document covers the following:
• A definition of terms relevant to cross-cutting Context Information Management (C3IM).
• An introduction to the notions of C3IM and the potential role of C3IM in enabling services in cross-cutting
inter-domain areas, for example Smart Cities, Smart Agrifood, and Smart Industry.
• A motivation for this project's key goal, i.e. defining an API for C3IM.
• A reference diagram illustrating possible architectures and functional entities involved in facilitating C3IM.
• A set of high level Use Cases which can potentially be supported using a C3IM system.
• A subset of detailed Use Cases (scenarios) illustrating potential information flows among functional entities.
• A summary of requirements extracted from the Use Case analysis.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] INSPIRE Data Specifications Drafting Team, 2008-03-18: "Deliverable D2.3: Definition of Annex
Themes and Scope".
NOTE: Available at
http://inspire.ec.europa.eu/reports/ImplementingRules/DataSpecifications/D2.3_Definition_of_Annex_Th
emes_and_scope_v3.0.pdf.
[i.2] INSPIRE: "European Data Portal -Training & Library - Use Cases".
NOTE: Available at https://www.europeandataportal.eu/en/training-library/library/training-materials.
[i.3] European Data Portal: "Re-using Open Data: A study on companies transforming Open Data into
economic and societal value", CapGemini, 20170117.
NOTE: Available at https://www.europeandataportal.eu/sites/default/files/re-using_open_data.pdf.
ETSI
---------------------- Page: 6 ----------------------
7 ETSI GR CIM 002 V1.1.1 (2018-09)
[i.4] "DIGITALEUROPE's views on the Artificial Intelligence, Machine Learning and Robotics",
Brussels, 10 May 2017 Published 20170510.
NOTE: Available at http://www.portugalglobal.pt/PT/Acoes/missoes/Documents/2017/belgica-2nd-innovation-
sessions-digital-europe.pdf.
[i.5] Pohl, Klaus: "Requirements engineering: fundamentals, principles, and techniques". Springer
Publishing Company, Incorporated, 2010.
[i.6] Library of Congress of USA: "PREMIS Data Dictionary for Preservation Metadata version 3.0".
NOTE: Available at http://www.loc.gov/standards/premis/v3/premis-3-0-datadictionary-only.pdf.
[i.7] W3C, PROV Model Primer. Working Group Note 30 April 2013.
NOTE: Available at http://www.w3.org/TR/2013/NOTE-prov-primer-20130430.
[i.8] ITS International: "Substantial savings from smarter street lighting", first published January 2015.
NOTE: Available at http://www.itsinternational.com/sections/general/features/substantial-savings-from-smarter-
street-lighting/.
[i.9] ETSI GS CIM 004 (V1.1.1) (04-2018): "Context Information Management (CIM); Application
Programming Interface (API)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
agent: system, software program or firmware that is a producer, consumer or manipulator of data in a use case
NOTE: That in some use cases, an agent may act on behalf of a human or legal stakeholder.
context: set of entities with which an entity has defined relationships, together with the categories (classes) and
properties of these entities, their relationships and their properties
context information: informational representation of a context
cross-cutting context information: context information that spans multiple distinct application domains
(Cross Cutting) Context Information Management (C3IM): following services provided by a platform: context
information registry, discovery, publication, mediation, modification or notification, and more generally mediation
between context information sources and context information users
NOTE: The acronym C3IM is used only in the present document as a shortcut for, cross cutting context
information management, rather than CIM to avoid confusion with acronyms uses by other SDOs
(e.g. ISO/IEC Common Information Model).
entity: something existing in the real world such as a person, a place such as a building or street corner, an object such
as a car or tree or refrigerator or any equipment or sensor, a document such as a book or legal document, which can be
represented in a context information management platform
NOTE: This is different from the sense in which the oneM2M specification uses the word "entity".
information model: set of types and associated constraints that formally define the classes(categories) used for context
information representation
NOTE: The information model constrains the specific representation of the structure, manipulation and integrity
aspects of the data stored in data management systems such as graph databases, whereby generic cross-
domain and specific domain-dependent terminologies/taxonomies are used for the information elements
and their instantiations.
ETSI
---------------------- Page: 7 ----------------------
8 ETSI GR CIM 002 V1.1.1 (2018-09)
property: description instance which associates a literal characteristic (e.g. a value in a common data type). to either an
Entity, a Relationship or another Property
relationship: description of a directed link between a subject which is either an Entity, a Property, or another
Relationship on the one hand, and an object, which is an Entity, on the other hand; for example "isAdjacent to",
"isContainedIn", "is ASubSystemOf", "isOwnedby", "isCreatedBy"
stakeholder: person, business or other legal entity who is involved in a service or process of a use case
situation: set of entities and services, and their dynamic states, interacting within a specific geo-temporal range
target domain: set of business activities (e.g. automobile traffic flow planning, energy distribution, etc.) within which
traditional use cases are defined
NOTE: The entities of a target domain may be shared with others (e.g. streets as city entities are shared between
traffic management and lighting management) and this is precisely where cross-cutting context
information comes into play.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ADSL Asymmetric Digital Subscriber Line
AI Artificial Intelligence
AIOTI Alliance for the Internet of Things Innovation
ALPR Automatic License Plate Recognition
API Application Programming Interface
ATM Automated Teller Machine
CAL Climate Associates Limited
EC European Commission
EGM Easy Global Market
EU European Union
EV Electric Vehicle
GHG Green House Gas
GPS Global Positioning System
HTTP Hypertext Transfer Protocol
HTTPS Hypertext Transfer Protocol Secure
ICD Implantable Cardioverter-Defibrillator
IoT Internet of Things
ISG Industry Specification Group
ISO International Organization for Standardization
KPI Key Performance Indicator
NEC Nippon Electric Company
NGSI Next Generation Service Interfaces
OWL Ontology Web Language
RDF Resource Description Format
SMS Short Message Service
UI User Interface
4 Introduction
4.1 Introduction to Context Information Management
As stated in the scope, the present document concerns the application of cross-cutting contextual information
management to a selection of Use Cases from the domains of Smart Cities, Smart Agrifood and Smart Industry. These
applications are expected to especially benefit from cross-cutting context information and from a set of specifications
for the APIs supporting C3IM.
ETSI
---------------------- Page: 8 ----------------------
9 ETSI GR CIM 002 V1.1.1 (2018-09)
Cross-cutting Context Information Management (C3IM) is provided by a C3IM platform. A C3IM platform collects
data from IoT devices, lower-level platforms managing such devices, crowdsourced devices, databases and other
sources, and provides as consolidated context information to applications via an API (defined in later documents as
NGSI-LD). The C3IM platform enables use-cases which link together disparate but related information. It is thought
that IoT services will be enriched when applications have access to a full set of context information, as defined in
clause 3. A C3IM system potentially enriches services by bringing together information from a wider set of
service-relevant sources than would otherwise be available to a traditional vertically integrated IoT application.
This is illustrated in figure 4.1-1. In the first figure, an IoT information source such as a sensor provides data to an
application. As an example, an IoT-enabled fitness tracker device reports heart rate and step counts to a user via a
cloud-based "runner fitness" service. The user is simply able to access current values and past statistics for these
measures. For best results and widest interoperability, the transfer of information from the sensor to the cloud
application needs to be accompanied by the semantics and context of the information (i.e. the numbers sent are "heart
rate", not "blood pressure" or some other measure).
The simple example makes clear that the protocol to exchange data should contain (or reference) all context information
needed to correctly interpret that data for a given service (the cloud application) and that the protocol should be
designed to function between widely different kinds of information sources and information "consumers". For widest
interoperability, nothing should be assumed.
Figure 4.1-1: Exchange of (context) information between a source and an application
In figure 4.1-2, the first information source is supplemented by additional contextually relevant information from a
variety of databases or other sources. The Application has access to a wider set of information and can provide a richer
service. To continue the example, an enhanced runner fitness service uses GPS location (from the user's phone sensor),
road inclination (from a municipal database), weather information (from a national government service web-API) and
traffic conditions on the road (from a web API of a popular map application). These are tied together by the application.
The user sees suggested running routes based upon his/her goals and local conditions, can track his/her progress and
speed, and sees graphs of heart rate against estimated calorie burn, speed, or road inclination.
Figure 4.1-2: Merging of several contextual information sources to enhance an application
Access to relevant context information from multiple target domains enables "cross-cutting" applications to present a
richer service to the user. To summarize, a C3IM system may utilize information of the following characteristics:
• information about or from one or more entities;
• static or dynamic information;
• information from database including open data;
ETSI
---------------------- Page: 9 ---------
...