Cloud and Edge Computing

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

5G EC would play a key role on low latency services and traffic off-load services in 5G era. Several prominent factors would enlarge and complex the security risks to the network layer that supports 5G EC and even bring new security challenges to the network security operation. These factors would be the flexible network architectures of 5G, the variable deployment positions of EC, the various application scenarios, different types of users' private networks and access networks, etc. The boundaries among the telecommunication networks and the private networks would be more ambiguous, and the exposure surface would be expanded. Therefore, the security requirements and measures of the network layer including both of the telecommunication networks and the private networks would be recommended as telecommunication operators enjoying the benefit of EC.

This draft Recommendation analyses the potential deployment scheme and typical application scenarios of edge computing services, specifies the security threats and requirements specific to the edge computing services and thus establishes the security framework for the operator to safeguard its applications.

ISO/PAS 19450:2015 specifies Object-Process Methodology (OPM) with detail sufficient for enabling practitioners to utilise the concepts, semantics, and syntax of Object-Process Methodology as a modelling paradigm and language for producing conceptual models at various extents of detail, and for enabling tool vendors to provide application modelling products to aid those practitioners.

This document specifies functional requirements and architecture about the following items for resource interoperability among heterogeneous IoT platforms (e.g., oneM2M, GS1 Oliot, IBM Watson IoT, OCF IoTivity, and FIWARE, etc.) through the conversion of resource identifiers (IDs) and paths (e.g., uniform resource identifier (URI)): Requirements for interoperability of resource IDs in the heterogeneous IoT platforms; Functional architecture for converting IDs and paths of resources on heterogeneous platforms; and, Functional architecture for mapping and managing resource IDs among heterogeneous platforms.

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.

The document describes the common concepts, terminologies, characteristics, use cases and technologies (including data management, coordination, processing, network functionality, heterogeneous computing, security, hardware/software optimization) of edge computing for IoT systems applications. This document is also meant to assist in the identification of potential areas for standardization in edge computing for IoT. The document describes several use cases from different domains: Smart elevator, Smart video monitoring, Intelligent transport systems, Process control in smart factory, Virtual power plant, Automated crop monitoring and management system, Smart lightning system.

ISO/IEC 21823-3:2021 provides the basic concepts for IoT systems semantic interoperability, as described in the facet model of ISO/IEC 21823-1, including: (1) requirements of the core ontologies for semantic interoperability; (2) best practices and guidance on how to use ontologies and to develop domain-specific applications, including the need to allow for extensibility and connection to external ontologies; (3) cross-domain specification and formalization of ontologies to provide harmonized utilization of existing ontologies; (4) relevant IoT ontologies along with comparative study of the characteristics and approaches in terms of modularity, extensibility, reusability, scalability, interoperability with upper ontologies, and so on; and (5) use cases and service scenarios that exhibit necessities and requirements of semantic interoperability.

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 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 five architecture views from different perspectives.

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.