 |
Work Item Reference | ETSI Doc. Number |
STF | Technical Body in Charge |
Download Standard
|
||
| DGR/CIM-002-UC | GR CIM 002 | CIM | |||||
| Current Status (Click to View Full Schedule) |
Latest Version |
Cover Date | Standstill | Creation Date | |||
|
|
1.1.1 | 2018-09-07 | View Standstill Information | 2017-02-10 | |||
| Rapporteur | Technical Officer | Harmonised Standard | |||||
Gilles Privat
|
Patrick Guillemin
|
No | |||||
| Title |
Context Information Management (CIM); Use Cases (UC) CIM Use Cases |
||||||
|
Scope and Field of Application |
The purpose of this Group Report is to collect and analyse use cases and requirements for management of information coming from many different sources (not only IoT) and data models to allow applications to perform updates on context, register context providers, query information on current and historic context information and subscribe for receiving notifications on context changes. Where ever possible, material shall be collected (by reference) from prior art and existing standards and specifications in this area. Collection of use cases: There shall be no restrictions on inclusion of use cases due to inability to be supported by a particular (popular) data exchange architecture. Use cases may be excluded based on incompatibility with the ToR of the ISG CIM, ethical or policy frameworks of ETSI or the EU, etc. Each use case should be accompanied in the published report by a list of requirements (possibly chosen from an extensible checklist). The format for describing use cases should follow an agreed template to allow better comparison (and elimination of duplicates), preferably based on a format which has already demonstrated usefulness (e.g. in oneM2M, SmartM2M, or some major group). Analysis of use cases: Not every use case will be achievable using every possible architecture so part of the analysis should indicate such restrictions. In particular, use case compatibility with the architecture(s) discussed in Work Item GAP should be identified. Prioritization: Since the needs of various smart cities at various times will be diverse, prioritization of use cases may not be possible, however a decision matrix based on a list of weighted criteria, including illustration of cross-domain aspects, should be created. The 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. |
||||||
|
Supporting Organizations |
ORANGE, NEC EUROPE LTD, TELEFONICA S.A., IMEC, TNO, Climate Associates Limited, EGM - eglobalmarket, FUTURE CITIES CATAPULT | ||||||
