Standardization in the area of Internet of Things and related technologies.
Standardization in the area of Internet of Things and related technologies.
The OASIS COEL specification provides a privacy-by-design framework for the collection and processing of behavioural data. It is uniquely suited to the transparent use of dynamic data for personalised digital services, IoT applications where devices are collecting information about identifiable individuals and the coding of behavioural data in identity solutions. The specification pseudonymises personal data at source and maintains a separation of different data types with clearly defined roles & responsibilities for all actors. All behavioural data are defined as event-based packets. Every packet is connected directly to an individual and can contain a summary of the consent they provided for the processing of the data.
A combination of a taxonomy of all human behaviours (the COEL model) and the event-based protocol provide a universal template for data portability. Simple interface specifications enforce the separation of roles and provide system-level interoperability.
This International Standard is aimed at organizations that provide services to communities in cities, and manage the resulting data, as well as decision-makers and policy developers in cities
This International Standard describes, and gives guidance on, a smart city concept model (SCCM) that can provide the basis of interoperability between component systems of a smart city, by aligning the ontologies in use across different sectors. It includes:
• concepts (e.g. ORGANIZATION, PLACE, COMMUNITY, ITEM, METRIC, SERVICE, RESOURCE).
• relationships between concepts (e.g. ORGANIZATION has RESOURCEs, EVENT at a PLACE).
The present document provides technical solutions for oneM2M authorization architecture, authorization procedures and access control policies. The present document also gives evaluations of these proposed technical solutions.
ETSI TS 118 103 [i.2] only defines a high level authorization architecture that describes its major components and general authorization procedure. The objective of the present document is to provide candidate security solutions related to authorization architecture, authorization procedures and access control policies. The present document provides security solutions in the following three aspects:
• Detailed design of authorization architecture: This part investigates the interfaces among authorization components (e.g. procedures and parameters), how these components could be distributed in different oneM2M entities (i.e. different CSEs), and how to implement Role Based Access Control (RBAC) and token based access control.
• Supporting user specified access control policies: This part investigates how the oneM2M authorization system could be an extensible system that can support user-defined access control mechanisms and/or access control policy languages.
• Investigating existing access control policy languages: This part investigates if some standardized access control policy languages could become oneM2M recommended access control policy description languages
The present document allows application developers to describe the status of devices as resources on oneM2M-based platform in various ways. Thus different application developers can create different resource trees even when they build the same kinds of applications. Moreover when handling the same kinds of devices from different vendors on M2M platforms, application developers may create disunited resource trees without common information model.
The present document collects the use cases of the industrial domain and the requirements needed to support the use cases collectively. In addition it identifies the necessary technical work needed to be addressed while enhancing future oneM2M specifications.
The present document is a study of the continuation and integration of some HGI Smart Home activities into oneM2M, following the (PT2) HGI announcement of its closure by June 2016. It includes the description of HGI SH deliverables versus the appropriate oneM2M deliverables for the integration of these HGI achievements.
It intends to be used as a liaison working document with HGI about the status progress of this continuation and integration and is expected to be useful for both HGI and oneM2M to check that all technical items from HGI SH Task Force expected to be integrated are appropriately handled by oneM2M.
The present document is a study of interworking between oneM2M Architecture and 3GPP Rel-13 architecture for Service Capability Exposure as defined in the release 13 version of ETSI TS 123 682 [i.5]. The key objective and value is analyzed and described. The document also investigates the potential solution in oneM2M by evaluating the existing technical solutions.
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.
The present document outlines the motivation for the deployment of IPv6 in enterprises, the objectives, the benefits, the risks, the challenges, the technology guidelines, the different choices that arise when designing IPv6-only or dual-stack enterprise network, step-by-step process, the addressing plan, and the milestones.
The present document outlines the motivation for IPv6 in IoT, the technical challenges to address IoT on constrained devices and networks, the impact on the IPv6 technology and protocols, the technology guidelines, the step by step process, the benefits, the risks, as applicable to IoT domains including: M2M, Energy, Industrial, Mining, Oil and gas, Smart city, Transportation (including EVs), etc.
IPv6-based IoT in this context refers to the connectivity network layers needed to support the communication between things. It is understood that a complete IoT system may use of an IoT architecture including but not necessarily an abstraction layer part of an IoT platform. The description of such IoT platform is out of the scope of the present document. 2
