IEEE

The wireless access in vehicular environments (WAVE) architecture and services necessary for WAVE devices to communicate in a mobile vehicular environment are described in this guide. It is meant to be used in conjunction with the family of IEEE 1609 standards as of its publication date. These include IEEE Std 1609.2(TM), IEEE Standard Security Services for Applications and Management Messages; IEEE Std 1609.3(TM), Networking Services; IEEE Std 1609.4(TM), Multi- Channel Operation; IEEE Std 1609.11(TM), Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS); IEEE Std 1609.12(TM), Identifiers; and IEEE Std 802.11(TM) in operation outside the context of a basic service set.

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.

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.

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.

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.

The functions and features to be provided in intelligent electronic devices (IEDs) to accommodate critical infrastructure protection programs are defined in this standard. Security regarding the access, operation, configuration, firmware revision and data retrieval from an IED are addressed. Communications for the purpose of power system protection (teleprotection) are not addressed in this standard.

Cryptographic transform for protection of data in sector-level storage devices is specified in this standard.

Discovery, authentication, and authorization protocols between hosts and storage devices over multiple transports are defined in this standard.

Additional components of the IEEE 1900.4 system are defined in this amendment to enable mobile wireless access service in white space frequency bands without any limitation on used radio interface (physical and media access control layers, carrier frequency, etc.).

The scope of this standard is to define one medium access control (MAC) and several physical layer (PHY) specifications for wireless connectivity for fixed, portable, and moving stations (STAs) within a local area.

The performance and functional capability requirements for DER connected with the Area Electric Power Systems (Area EPS) are defined in IEEE Std 1547(TM). This amendment revises the ranges of allowable trip clearing time settings in Table 13 for DERs in abnormal operating performance category III to allow wider ranges that can broaden and simplify the adoption of the standard. In addition, the related informative Figure H.9 is revised accordingly.

The standard identifies gateways for field-bus networks, data storage for archiving and developing data sharing platforms, and application units as important system components for developing digital communities, i.e., building-scale and city-wide ubiquitous facility networking infrastructure. The standard defines a data exchange protocol that generalizes and interconnects these components (gateways, storage, application units) over the IPv4/v6-based networks. This enables integration of multiple facilities, data storage, application services such as central management, energy saving, environmental monitoring, and alarm notification systems.