Smart and Sustainable Cities

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.

The document gives an overview of the requirements for communication from authorities/organizations to citizens in all types of emergencies. It collects operational and organizational requirements as a basis for a common notification service, including targeting of the area to be notified. This Work-item will revise the current TS to add parameterisation of the requirements and any additional requirements discovered.

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.

The Technical Specification defines the VRU related requirements (stage 2); as well as the functional architecture of the VRU system (stage 3). In addition it analyses the impact on existing standards (for instance the CAM European Standard)

Development of a Technical Specification for the broadcasting of dynamic information from a roadside unit / charging spot to Electric Vehicles (EV) related to the availability and capabilities of local EV Charging Spot(s).

The scope of the work item is to (a) analyse cooperative ITS services using public mobile cellular networks for communications between ITS stations in order to identify related functional requirements on the ITS architecture, (b) identify required amendments / modifications of existing standards on cooperative ITS in order to enable usage of public mobile cellular networks, (c) identify functionality to be specified in new ITS standards to be developed under M/453. The result is to be presented as an ETSI Technical Report. Starting from the architecture described in the published standard 'ITS Communication Architecture' EN 302 665 v1.1.1, and considering primarily the 'Basic Set of Applications' defined in ETSI TR 102 638, a critical assessment of the applicability of the 3G - 4G mobile network access to support the described application scenarios will be provided. This analysis aims to refer to technical standards developed by 3GPP and ETSI TC M2M as much as possible. This analysis is based on the ITS station architecture and also covers security aspects. Additional technical background provided by R&D projects such as CoCAR (http://www.aktiv-online.org/english/aktiv-cocar.html), CoCARx (the follow-on project including integration between LTE and DSRC access technologies), and CVIS (http://www.cvisproject.org/) is intended to be considered for the development of the Technical Report. Related standards from other SDOs working on cooperative ITS also will be considered as appropriate. This approach is coherent with the spirit of the 'Joint CEN and ETSI Response to Mandate M/453', with specific reference to clause 3.3. 'Standardisation for Co-operative systems covering other media' and clause 4.2.3. 'National R&D projects including national FOTs'.

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.

Wireless Access in Vehicular Environments (WAVE) is specified in the IEEE 1609 family of standards, within which certain identifiers are used. The use of these identifiers is described, and identifier values that have been allocated for use by WAVE systems are indicated.

The DNP3 protocol structure, functions, and interoperable application options (subset levels) are specified. The simplest application level is intended for low-cost distribution feeder devices, and the most complex for full-featured systems. The appropriate level is selected to suit the functionality required in each device. The protocol is suitable for operation on a variety of communication media consistent with the makeup of most electric power communication systems.