IT in general

The goal of this work item is to study the issues relevant for the localization of multilingual applications, regarded from all relevant stakeholders' perspectives. Based on the studies performed, this Technical Report will provide conclusions, recommendations and guidance addressing the issues related to the localization of user context dependent multilingual communications for interactive applications. The aim of the work will be on ensuring the accuracy of the texts generated by the applications, therewith simplifying the work of developers, publishers, translators and interaction designers

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

Specifies general definitions for low-speed serial data communication up to 125 kbit/s for road vehicle applications. The object is to define the general architecture of the communication network and the content of the data link layer and the physical layer for transmission between the different types of electronic modules on board road vehicles. Parts 2, 3 and 4 are entirely independent.

Direct-current (dc) charging is a method of charging that facilitates rapid energy transfer from the electric grid to plug-in vehicles. This method of charging allows significantly more current to be drawn by the vehicle versus lower rated alternating-current (ac) systems. A combination of vehicles that can accept high-current dc charge and the dc supply equipment that provides it has led to the use of terminology such as “fast charging,” “fast charger,” “dc charger,” “quick charger,” etc. DC charging and ac charging vary by the location at which ac current is converted to dc current. For typical dc charging, the current is converted at the off-board charger, which is separate from the vehicle. For ac charging, the current is converted inside the vehicle, by means of an on-board charger. The location of the ac to dc conversion equipment, or converter, shapes the complexity of the equipment design. Regarding ac charging, as previously mentioned, the conversion is on board the vehicle. This allows the original equipment maker (OEM) designed systems to control the charging operation in its entirety. The on-board charger (converter) and battery controller solution is under direct control of the vehicle manufacturer. For dc charging, an entirely new challenge exists for OEMs. The dc charger is now external to the vehicle and requires the vehicle engineers to control an external power device. For the reason of necessary interoperability, standards such as IEEE Std 2030.1.1 are provided to assist developers.

This standard specifies the general requirements that a fully automated vehicle shall meet in order to drive on public roads. This standard serves as a comprehensive checklist of all the use cases, scenarios, and worst conditions that a fully automated vehicle certified by the public body shall address on public roads in order to protect the safety of the public including passengers, pedestrians, and other traffic participants.

This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions.

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 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.

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'.

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 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)

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.