2024-09-20 | Work Programme | Version 2.3.3 |
Work Item Has Been STOPPED |
Work Item Reference | ETSI Doc. Number |
STF | Technical Body in Charge |
Standard Not Ready For Download |
|||
DGR/CIM-003-GAP | GR CIM 003 | CIM | |||||
Current Status (Click to View Full Schedule) |
Latest Version |
Cover Date | Standstill | Creation Date | |||
|
0.0.3 | View Standstill Information | 2017-02-10 | ||||
Rapporteur | Technical Officer | Harmonised Standard | |||||
Ernoe Kovacs | Patrick Guillemin | No | |||||
Title |
Context Information Management (CIM); Architecture and Standardization Gaps CIM GAP |
||||||
Scope and Field of Application |
The purpose of this Group Report is to Identify a reference architecture and show positioning/compatibility to e.g. oneM2M. The initial focus should be on potential gaps in the OMA NGSI 9 and 10 abstract interface specifications. Recommendations shall be accompanied by pro/con information. The intent is to reference as much as possible existing widely supported concepts. There is a long list of issues to clarify and resolve, partly illustrated by the following key topics (not prioritized): 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, cross-domain aspects, timestamping and freshness of data, quality KPIs of data, managing multiple contexts, scalability. 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. Such information is needed for later Work Items and may usefully be collected in parallel with the work of this WI The CIM API shall not have requirements concerning control of IoT devices or altering of their status, however reading the status of things is essential, using e.g. standardised IoT platforms or application gateways. This scope information will be shared with various SDOs as soon as possible, to clarify issues, to solicit input and to avoid duplication of efforts. This work item may be split into two or more deliverables for efficiency. |
||||||
Supporting Organizations |
ORANGE, NEC EUROPE LTD, TELEFONICA S.A., IMEC, TNO, AT4 wireless S.A., Climate Associates Limited, EGM - eglobalmarket, Fiware Foundation, FUTURE CITIES CATAPULT |
|
Keywords | Projects | Clusters | Frequencies | Mandates | Directives | |||||||||||||
API ARCHITECTURE GAP INFORMATION MODEL INTEROPERABILITY smart city |
Connecting Things |
||||||||||||||||||
Official Journal |
|
||||||||||||||||||
Remarks |
|
Displaying Item 9 of 73... |
Any comments or problems with this application? Please let us know... | ||