Standard

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.

ISO/TS 17975:2015, 3.1. Health informatics::Principles and data requirements for consent in the Collection, Use or Disclosure of personal health information

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.

IEC 60664-1:2020 deals with insulation coordination for equipment having a rated voltage up to AC 1 000 V or DC 1 500 V connected to low-voltage supply systems. This document applies to frequencies up to 30 kHz. It applies to equipment for use up to 2 000 m above sea level and provides guidance for use at higher altitudes. It provides requirements for technical committees to determine clearances, creepage distances and criteria for solid insulation. It includes methods of electrical testing with respect to insulation coordination. The minimum clearances specified in this document do not apply where ionized gases are present. Special requirements for such situations can be specified at the discretion of the relevant technical committee. This document does not deal with distances:– through liquid insulation. – through gases other than air. – through compressed air.This edition includes the following significant technical changes with respect to the previous edition:update of the Scope, Clauses 2 and 3,addition of 1 500 V DC into tables,new structure for Clauses 4 and 5,addition of Annex G with a flowchart for clearances,addition of Annex H with a flowchart for creepage distances,update of distances altitude correction in a new Table F.10.

The scope of this Technical Report is to provide test methods and metrics for validating separation distances of robot applications using Speed and Separation Monitoring (SSM) in accordance with ANSI/RIA R15.06 and RIA TR R15.606. This Technical Report also provides guidance on determining how speeds and positions of robot systems, workpieces, and obstacles should be measured, and under what conditions such measurements should be made.This document is informative in nature and is not a standard. The use of the word “shall” and “should” in a particular statement indicates the relative importance of specific criteria or features indicated in ANSI/RIA R15.06, RIA TR R15.606, and RIA R15.08.