ETSI GR CIM 002-2018 Context Information Management (CIM) Use Cases (UC) (V1 1 1).pdf

《ETSI GR CIM 002-2018 Context Information Management (CIM) Use Cases (UC) (V1 1 1).pdf》由会员分享，可在线阅读，更多相关《ETSI GR CIM 002-2018 Context Information Management (CIM) Use Cases (UC) (V1 1 1).pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GR CIM 002 V1.1.1 (2018-09) 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 partic

2、ipated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR CIM 002 V1.1.1 (2018-09)2 Reference DGR/CIM-002-UC Keywords API, information model, interoperability, IoT, smart city, use case ETSI 650 Route des Lucioles F-06921 Sophia Antipoli

3、s 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present docum

4、ent 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/o

5、r 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 sta

6、tus of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may

7、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 re

8、striction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizationa

9、l Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GR CIM 002 V1.1.1 (2018-09)3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g31 Scope 6g32 References 6g32.1

10、 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Introduction 8g34.1 Introduction to Context Information Management . 8g34.2 Information Sources . 10g34.3 Motivation for developing a Context Information Manageme

11、nt System . 11g35 Methodology 12g35.1 Approach to Documenting Use Cases 12g35.1.1 Purpose . 12g35.1.2 Assumptions about a C3IM Architecture 13g35.1.3 Use Case Sections . 13g35.2 Composing Use Cases 15g35.3 Stakeholders . 15g35.4 Example Entity types 16g35.4.0 Introduction. 16g35.4.1 Geospatial examp

12、les . 16g35.4.2 Provenance Data examples . 17g36 Simplified functional reference architecture 17g37 Smart City Cross-cutting Use Cases 18g37.1 Use Case 1 Sharing information between parking management systems and traffic management applications. 18g37.1.1 Use Case 1 Introduction and Assumptions . 18

13、g37.1.2 Use Case 1 Information Flow Diagram 19g37.1.3 Use Case 1 Stakeholders . 19g37.1.4 Use Case 1 Agents and Data Source/Sink Entities . 20g37.1.5 Use Case 1 Scenario Descriptions and Data Flows 21g37.1.5.1 Scenario “A“: Routing to closest available parking space taking into account both real-tim

14、e availability of individual parking spaces across different parking providers AND street congestion . 21g37.1.5.2 Scenario “B“: exit from parking structure taking local traffic into account 22g37.1.5.3 Scenario “C“: Entry to Private Parking Space Rented on Temporary Basis . 23g37.1.5.4 Scenario “D“

15、: Smart Parking Facility Manager Queries . 23g37.1.5.5 Scenario “E“: Reserved Parking for Care workers responding to in-home monitor alarm . 23g37.1.6 Use Case 1 Entities instances graph 24g37.2 Use Case 2: Smart Street Lighting . 24g37.2.1 Use Case 2 Introduction and Assumptions . 24g37.2.2 Use Cas

16、e 2 Information Flow Diagram 25g37.2.3 Use Case 2 Stakeholders . 25g37.2.4 Use Case 2 Agents and Data Source/Sink Entities . 26g37.2.5 Use Case 2 Scenario Descriptions and Data Flows 26g37.2.5.1 Scenario “A“: Lighting Levels Depending on Traffic Presence 26g37.2.5.2 Scenario “B“: Lighting Levels Dep

17、ending on Weather Conditions 26g37.2.5.3 Scenario “C“: Lighting Levels Depending on Traffic Management Decisions . 27g37.2.5.4 Scenario “D“: Lighting Levels Depending on Crowdsourced Data 27g3ETSI ETSI GR CIM 002 V1.1.1 (2018-09)4 7.2.6 Use Case 2 entity instances graph . 28g37.3 Use Case 3: Traffic

18、 Management 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, h

19、as 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 tra

20、denames 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 cons

21、titute 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 “sho

22、uld“, “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. E

23、TSI ETSI GR CIM 002 V1.1.1 (2018-09)6 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

24、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 follow

25、ing: 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 t

26、his projects 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) illust

27、rating 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 b

28、y 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 w

29、ere 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, 200

30、8-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_Themes_and_scope_v3.0.pdf. i.2 INSPIRE: “European Data Portal -Training Application Programming Interface (API)“. 3 D

31、efinitions 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

32、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 contex

33、t 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 medi

34、ation 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 Mo

35、del). 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 plat

36、form 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 specifi

37、c 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 ETSI G

38、R CIM 002 V1.1.1 (2018-09)8 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

39、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:

40、 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

41、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 A

42、symmetric 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 E

43、U 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 Groupg3ISO International Organization for Stan

44、dardization 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

45、, 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

46、set of specifications for the APIs supporting C3IM. ETSI ETSI GR CIM 002 V1.1.1 (2018-09)9 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

47、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 a

48、ccess 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

49、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 “hear