IT in general

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.

Total Conversation, as defined in ITU-T F.703, is a combination of three media in a conversational call: video, real-time text and audio. Total conversation services and terminals are deployed in the Internet in a number of countries in Europe, and adopted by people with disabilities who, for example, need video for sign language or real-time text for a text based conversation or as complement to a voice conversation. The objective of this Work Item is to define requirements, based on the backgroung described in TR 103 170, for using Total Conversation for emergency services and make access of emergency services possible to people with disabilities. The Work Item will mainly address the PSAP organisations and potential impact on overall organisations of emergency services. For example it should address functional requirements regarding the interface to the PSAP, the connection to external supporting services, the transferring and sharing of the call between call handling organisations, the call logging and call recording, call back aspects and specific call routing and location information provision aspects for these calls.
Due consideration of present ongoing standardisation work (e.g. 3GPP) and appropriate liaisons with relevant groups (e.g. EGEA) will be organised as required during the progress of this Work Item.

The purpose of this work item is to prepare the requirements for communications involving IoT devices in all types of emergency situations (e.g. communications of individuals with authorities/organisations, between authorities/organisations, from authorities/organisations to the individuals, amongst individuals). The work will start with a study of the state of the art across the IoT domain scope. It will include an analysis of use cases for emergency services, taking into account the work already done in other projects, such as oneM2M and 3GPP. It will conclude with an analysis of the impacts of these use cases on the existing specifications and of what needs to be standardized.

Identification of use cases for visually impaired people for e-access to ICT products and services but also use cases to allow users to interact with machines or equipment (e.g. users terminal, user interface) via dedicated devices (M2M communications) in order to define appropriate protocols (NFC or similar)
The intention is not to define technical solutions but to forward the requirements to the appropriate TBs

The EN will contain normative specifications related to the accessibility of websites and mobile applications and their compliance with the essential requirements of perceivability, operability, understandability and robustness defined in the Web and Mobile Accessibility Directive

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.

Recommendation ITU-T Y.4211 specifies accessibility requirements for smart public transport services. The concept of accessibility in public transport services has been mainly concerned with eliminating physical barriers such as adopting accessible trains and buses that allow wheelchair accessibility by mechanical lowering-entrance floors. In smart public transport services, the use of Internet of things (IoT), when properly designed, may increase accessibility of public transport services by providing access of information and physical accessibility. The IoT can be used to create tools for persons with many types of disability and specific needs, including physical, visual, hearing and cognitive disabilities. In order for the smart transport services to appropriately provide accessible services, information about accessibility profiles must be agreed upon in advance. Such accessibility profiles should basically include information on accessibility needs while travelling on public transport services.

The objective of Recommendation ITU-T Y.4119 is to identify requirements of an Internet of things (IoT)-based automotive emergency response system (AERS) for aftermarket devices and to provide a capability framework of the AERS.In particular, the scope of this Recommendation includes:– Overview of the AERS– Requirements of the AERS– Capability framework of the AERSAERS for original equipment manufacturer (OEM) pre-installed devices, such as the pan-European eCall [b-CEN EN 16072], is out of scope of this Recommendation.NOTE – AERS can be considered as a third party service provider (TPSP) system [b-CEN EN 16102] in the pan-European eCall.Also, the operation of the emergency authority (EA) is out of scope of this Recommendation.

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.

Cryptographic and data authentication procedures for storage devices that support length expansion, such as tape drives, are specified. Such procedures include the following cryptographic modes of operation for the AES block cipher: CCM, GCM, CBC-HMAC, and XTS-HMAC.

EME2-AES and XCB-AES wide-block encryption with associated data (EAD) modes of the NIST AES block cipher, providing usage guidelines and test vectors, are described. A wide block encryption algorithm behaves as a single block cipher with a large plaintext input and ciphertext output, but uses a narrow block cipher [in this case Advanced Encryption Standard (AES)] internally. These encryption modes are oriented toward random access storage devices that do not provide authentication, but need to reduce the granularity of a potential attack.