Smart and Sustainable Cities

The enhanced security management function for the protocol defined in IEEE 1888(TM), “Ubiquitous Green Community Control Network Protocol,” is described in this standard. Security requirements, system security architecture definitions, and a standardized description of authentication and authorization, along with security procedures and protocols, are specified. This standard can help avoid unintended data disclosure to the public and unauthorized access to resources, while providing enhanced integrity and confidentiality of transmitted data in the ubiquitous green community control network.

Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.

This guide describes recommended practices for the physical security of electric power substations. It is designed to address a number of threats, including unauthorized access to substation facilities, theft of material, and vandalism. It describes options for positive access control, monitoring of facilities, and delay/deter features which could be employed to mitigate these threats. This guide also establishes options for different levels of physical security for electric power substations. The guide does not establish recommendations based on voltage levels, size or any depiction of criticality of the substation. The user will make these decisions based on threat assessment and criticality assignment by the substation owner. Overt attacks against the substation for the purpose of destroying its capability to operate, such as explosives, projectiles, vehicles, etc. are beyond the scope of this guide.

This Recommendation introduces the concept of blockchain-based unified key performance indicator data management for smart sustainable cities (BKDMS), analyses its common characteristics and high-level requirements, defines a reference architecture of BKDMS and relevant common capabilities，gives a common data structure of KPIs according to the KPIs definition of the ITU-T Y.4900 series.The scope of this Recommendation does not include:• The KPIs definition.• The KPI data value and scope.• Specific technical implementation mechanism of blockchain.

ISO/TS 21089:2018 describes trusted end-to-end flow for health information and health data/record management. Health data is originated and retained, typically as discrete record entries within a trusted electronic health record (EHR), personal health record (PHR) or other system/device. Health data can include clinical genomics information.Health record entries have a lifespan (period of time managed by one or more systems) and within that lifespan, various lifecycle events starting with (1) originate/retain. Subsequent record lifecycle events may include (2) update (3) attest (4) disclose (5) transmit (6) receive (7) access/view, and more. A record entry instance is managed over its lifespan by the source system. If record entry content is exchanged, this instance may also be managed intact by one or more downstream systems. Consistent, trusted management of record entry instances is the objective of this document, continuously and consistently whether the instance is at rest or in motion, before/during/after each lifecycle event, across one or more systems.

This document specifies a generic business process framework for a smart city focusing solely on smart city-specific processes. Generic business processes common between smart cities and commercial organizations are be identified but not detailed.

This standard defines a method for data sharing, interoperability, and security of messages over a network, where sensors, actuators and other devices can interoperate, regardless of underlying communication technology. The backend of such a globally scalable, secure and interoperable network would be based on the eXtensible Messaging and Presence Protocol (XMPP), and rely on infrastructural components, or bridges, with standardized interfaces that provide real-time conversion of other IoT and M2M protocols, such as those based on CoAP (Constrained Application Protocol), HTTP (Hypertext Transfer Protocol), MQTT (Message Queuing Telemetry Transport Protocol), AMQP (Advanced Message Queuing Protocol), etc., and other interoperability interfaces, such as those provided by the IEEE 1451 Smart Transducer Interface, oneM2M, OMA LWM2M (Open Mobile Alliance Lightweight M2M), OIC (Open Internet Connection), UPnP (Universal Plug and Play), IPSO (Internet Protocol for Smart Objects) Alliance, etc. The standard utilizes the advanced capabilities of the XMPP protocol, such as providing globally authenticated identities, authorization, presence, life cycle management, interoperable communication, IoT discovery and provisioning. Descriptive meta-data about devices and operations will provide sufficient information for infrastructural components, services and end-users to dynamically adapt to a changing environment. Key components and needs of a successful Smart City infrastructure will be identified and addressed. This standard does not develop Application Programming Interfaces (APIs) for existing IoT or legacy protocols.

Blockchain is an emerging technology, its most important characteristics are traceable, un-erasable, immutable, and time-stamped. It is able to efficiently ensure integrity, authenticity, and auditability for all transactions. Blockchain has important impacts and benefits for data exchange and sharing in support of Internet of things (IoT) and smart cities and communities (SC&C). In most of the IoT and SC&C scenarios, it is necessary to ensure data processing, circulation, sharing and management for all trust operations. Blockchain technologies can meet these needs. Recommendation ITU-T Y.4560 specifies the requirements, functional models, a platform, and deployment modes of blockchain-based data exchange and sharing for supporting IoT and SC&C.

Along with the development of the Internet of things (IoT) and smart cities and communities (SC&C), various applications have different kinds of requirements for data management, and there are many challenges, especially in data representing, data processing, data service provisioning, and other aspects in a secure and effective manner. Meanwhile, blockchain as an emerging technology possesses the characteristics of trust, transparency, traceability and accountability. It has the potential capabilities to solve the existing issues in data management. Recommendation ITU-T Y.4561 specifies the requirements, generic reference model, common capabilities, and procedures of blockchain-based data management.

An object identifier (OID) is an identifier to name an object in a hierarchically assigned namespace. In the Internet of things (IoT), thousands of IoT resources will be intricately provided as fusion types of various services. For the thousands of IoT resources, object identifiers (OIDs) can provide a resolution framework with unlimited scalability. On the other hand, IoT resources need to secure their data, so the distributed ledger technology (DLT) can guarantee its integrity. In consequence, the convergence of DLT and OIDs provides a good solution for identifying secured data of IoT resources. Recommendation ITU-T Y.4476 therefore specifies a resolution framework for the transactions of a distributed ledger assigned to IoT resources. Recommendation ITU-T Y.4476 also describes the concepts, functional requirements, architecture and procedures of an OID-based resolution framework by using DLT.

This Recommendation defines the reference framework and high-level requirements of smart city platforms. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.

This work item focuses on identifying the necessary support provided by Multi-access Edge Computing for V2X applications. The work will be a study with the intent to collect and analyse the relevant V2X use cases (including the findings from external organisations), evaluate the gaps from the defined MEC features and functions, and identify the new requirements including new features and functions.When necessary, this may include identifying new multi-access edge services or interfaces, as well as changes to existing multi-access edge services or interfaces, data models, application rules and requirements. The work item will recommend the necessary normative work to close these gaps if identified.