Standard

ISO/IEC 30141:2018 This document provides a standardized IoT Reference Architecture using a common vocabulary, reusable designs and industry best practices. It uses a top down approach, beginning with collecting the most important characteristics of IoT, abstracting those into a generic IoT Conceptual Model, deriving a high level system based reference with subsequent dissection of that model into the four architecture views (functional view, system view, networking view and usage view) from different perspectives.

This Recommendation describes a decentralized, IoT communication reference architecture based on ICN and blockchain.

ISO/IEC 21823-1:2019(E) provides an overview of interoperability as it applies to IoT systems and a framework for interoperability for IoT systems. This document enables IoT systems to be built in such a way that the entities of the IoT system are able to exchange information and mutually use the information in an efficient way. This document enables peer-to-peer interoperability between separate IoT systems. This document provides a common understanding of interoperability as it applies to IoT systems and the various entities within them.

This document provides system life cycle processes to implement and maintain trustworthiness in an IoT system or service by applying and supplementing ISO/IEC/IEEE 15288:2015. The system life cycle processes are applicable to IoT systems and services common to a wide range of application areas.

This document defines a structured description method, which describes the functionalities of IoT devices, including what functionalities an IoT device can provide, and how to use the functionalities of IoT device. In details, the contents: 1. Define concept of IoT Device Model: what is IoT Device Model, and how it works with underlying IoT communication protocols; 2. Specify structure of IoT Device Model: define the elements of Status, Profile, and Resource; Furthermore, specify the structure of Resource element, to describe the functionalities of IoT devices through Property, Service, and Event; 3. Specify construction method of IoT Device Model: how to build IoT device functionalities based on IoT Device Model; 4. Describe the device interoperability based on the IoT Device Model: IoT Device Model discovery, remote query, remote controlling, subscription and data uploading.

This document provides a collection of representative use cases of Digital Twin applications in a variety of domains.

The document defines a conceptual model for the building of use cases; specifies a use case template ontology, i.e. vocabulary as well as conventions for describing and representing use case contents; provides guidance on building use case templates and on extending a use case ontology to cover the targeted standard; provides examples of use case templates and use cases; and specifies an implementation scheme that will allow use cases to be stored and shared in a repository.

This document provides an overview of Digital Twin, describes the capabilities, range, characteristics and requirements, and establishes a well-defined conceptual model, reference model and reference architectural views including usage view, functional view, and network view. This document is applicable to all types of organizations (e.g., commercial enterprises, government agencies, not-for-profit organizations).

Based on ISO/IEC 21823-1, this document provides the basic concepts for IoT systems and digital twin systems behavioral and policy interoperability. This includes - requirements - guidance on how to identify points of interoperability - guidance on how to express behavioral and policy information on capabilities - guidance on how to achieve trustworthiness interoperability, and - use cases and examples .

This Recommendation defines the reference architectural framework and requirements of IoT and Smart City and Community services based on federated machine learning.

This draft Recommendation provides security guidelines for vehicular edge computing. Vehicular edge computing (VEC) is a model that supports the core cloud's capacity for decentralizing the concentration of computing resources in data centers. VEC also provides more localized storage and application services to road users, thereby making it possible to achieve lower latency delays, faster response times providing mobility support, location awareness, high availability, and Quality of Service for streaming real-time applications since the data processing is conducted closer to the vehicle. Vehicular edge computing faces many security challenges and issues since it requires providing faster service response time to end-users. This Recommendation provides security guidelines for vehicular edge computing based on an analysis of the threats and vulnerabilities identified within VEC. Further, it also provides use cases for a security system and relevant security requirements for use in for vehicular edge computing scenarios.

Edge computing is strongly related to 5G and UPF is the data connection point between the MEC system and 5G Network architecture. The sinking of 5G network user plane brings threats such as illegal eavesdropping, which may seriously threaten the data security in edge computing. The edge node has unique features itself and whether in the physical environment or the network, the data security will be an important problem that the edge nodes need to face. Therefore, the recommendation analyses the edge computing data security mainly from these two aspects and provides relative data security challenges and threats and data security guidelines for Edge Computing. This recommendation could help to address the data security issues in Edge Computing implementation