Human Factors (HF); Guidelines to identify Design-for-All aspects in ETSI deliverables
The present document will address the objectives asked for in EC Mandate M/473.
The present document will address the objectives asked for in EC Mandate M/473.
The report will assess the different citizen/consumer needs that smart city standardization in the ICT domain has to address (accessibility, usability, personalisation, interoperability, personal data protection, etc)
The EG will update the terminology list of EG 202 132 to include relevant terms for upcoming device and service features and will extend the list to include the 5 most frequently spoken languages in the EU and EFTA (English, French, German, Italian, Spanish). The scope of the EG will be limited to general and generic terms and will not, in any way, prevent manufacturers and service operators to introduce specific and/or proprietary terms for special or unique features that they wish to offer.
The production of a taxonomy of all disability, ageing and youth issues that could be addressed by UCI based systems and relating these to requirements for elements in the UCI additional information field and to PUA functionality. The work will include liaison with groups representing young, elderly and disabled people and with the eEurope Smartcard initiative.
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.
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.
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.
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.
ISO 24100:2010, 3.3. Intelligent transport systems::Basic principles for personal data protection in probe vehicle information services
Smart parking lots (SPLs) integrate parking information to enable the coordination of parking facilities within smart cities. SPLs work with other systems to provide various parking services. This Recommendation specifies the requirements and functional architecture for SPLs. The scope of this Recommendation includes: introduction of SPLs; requirements for SPL; Functional architecture of SPL. For use cases of SPL see Appendix I. 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.
My work in ITU addresses the priorities of the call pertaining to smart cities and communities, technologies and services for smart and efficient energy use, and citizen centric digital public services and EMC radiation.