Standard

The purpose of a PICS is to identify those standardized functions which an IUT shall support, those which are optional and those which are conditional on the presence of other functions. It helps to identify which functions an IUT will support when performing conformance testing. It is possible that with different choices in an ICS proforma, several different sets of TPs will be necessary. In the following clauses assessments are made on whether requirements, features, components and other capabilities are required according to a referenced standard and in order to achieve compliance.

The Pan-European Mobile Emergency Application (PEMEA) architecture provides the requirements and architecture for a solution to provide emergency application interconnection. It specifies the protocols and procedures enabling interoperable implementations of the architecture and provides extension points to enable new communication mechanisms as they evolve.

The present document addresses the requirements for communications between the authorized representatives who can be involved in the responses and actions when handling an emergency. It describes the functional requirements for communications between the authorized representatives involved in the responses and actions when handling an emergency. The level of precision has been chosen to avoid interaction with the specific local, regional or national organizations and diagrams of relations between authorized representatives. It follows from this that adaptations will have to be done when implementing the present document at a local level. Furthermore, the scope of the present document also encompasses various types of services that can bring an added value to this basic scenario or add new scenarios, such as the services brought by other technologies e.g. IoT devices that support communications between authorities during emergencies.

Recent world events have created a heightened social focus on public protection and general public safety. Actions such as the Universal Service Directive requiring the European emergency call number (112) to be enhanced with the provision of caller location and the Seveso II Directive aimed at the prevention of major accidents involving dangerous substances highlight this focus. Special consideration may have to be given to the elderly, the disabled and the young people. An annotated bibliography of documents dealing with human factors can be found in ETSI SR 001 996. The provision of effective communication is one of the most important duties of a public authority towards its citizens. An important component required to meet this duty is the ability for Authorities to communicate with citizens during times of emergency. Authorities and emergency response teams need to warn and inform the public in times of crisis and therefore is required to have effective, high quality communication methods and systems to meet this need. The responsibility for emergency response or disaster-related communications is addressed differently from country to country. In most cases, the parties responsible for warning and informing the public follow the country's administrative structures with coordinators at both the local and national levels, as well as across multiple disciplines and departments. The present document catalogues the requirements on warning and informing the public as seen by the Emergency Services Community and looks at the technologies and methods available to do this, and also addresses IoT devices that act upon receiving a (specific) warning message.

Lightweight Messaging Protocol for Emergency Service accessibility (LMPE) extends a SIP SIMPLE based messaging service with session mode and facilities to redirect or transfer a chat. The mechanisms introduced in the present document differ from existing solutions like MSRP in a sense that no media plane is required. This reduces the functionality to chat, but requires less deployment effort and complexity (e.g. no intermediate services or relays in case of NAT), especially in a roaming use case. In addition, to further reduce complexity, the identification of a user is carried out via a device identifier only, such as a mobile phone number as with comparable chat services. In summary, it simplifies the implementation and thus can be used in simple mobile applications or even smart IoT devices and chatbots, which for example send or respond to messages automatically. The referred baseline specification (ETSI TS 103 479) already defines page mode messaging suitable for a single message exchange or a series of short messages similar to paging or SMS on a mobile device. Routing and mapping mechanisms (defined in ETSI TS 103 479 ) to determine the proper control room, are based on location information. Therefore a single message exchange is not practicable as caller location may change and lead to messages being routed to a different control room. The present document defines specific message types to group messages into sessions with routing and mapping only required at setup time. In addition the same principles are used to support supplementary services like chat redirect and transfer. Each mechanism is transparent to ETSI TS 103 479 [1] core services and requires only minor modifications to the PSAP interface.

This document specifies the big data reference architecture (BDRA). The reference architecture includes concepts and architectural views.
The reference architecture specified in this document defines two architectural viewpoints:

• a user view defining roles/sub-roles, their relationships, and types of activities within a big data ecosystem;
• a functional view defining the architectural layers and the classes of functional components within those layers that implement the activities of the roles/sub-roles within the user view.

The BDRA is intended to:

• provide a common language for the various stakeholders;
• encourage adherence to common standards, specifications, and patterns;
• provide consistency of implementation of technology to solve similar problem sets;
• facilitate the understanding of the operational intricacies in big data;
• illustrate and understand the various big data components, processes, and systems, in the context of an overall big data conceptual model;
• provide a technical reference for government departments, agencies and other consumers to understand, discuss, categorize and compare big data solutions; and
• facilitate the analysis of candidate standards for interoperability, portability, reusability, and extendibility

This document describes the framework of the big data reference architecture and the process for how a user of the document can apply it to their particular problem domain.

This extension has been created by investigating resources from potential stakeholders of the ontology, such as standardization bodies (e.g. Open Geospatial Consortium), associations (e.g. Spanish Federation of Municipalities and Provinces), IoT platforms (e.g. FIWARE) and European projects and initiatives (e.g. ISA2 programme, as reported in ETSI TR 103 506)

The present document specifies a conformance assessment methodology for consumer IoT devices, their relation to associated services and corresponding relevant processes against ETSI TS 103 645 [1] / ETSI EN 303 645,  Draft ETSI addressing the mandatory and recommended provisions as well as conditions and complements ETSI TS 103 645 / ETSI EN 303 645 by defining test cases and assessment criteria for each provision.

This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.

ISO/IEC 30106-1:2016 specifies an architecture for a set of interfaces which define the OO BioAPI. Components defined in this part of ISO/IEC 30106 include a framework, Biometric Service Providers (BSPs), Biometric Function Providers (BFPs) and a component registry.

ISO/IEC 30108-1:2015 defines the architecture, operations, data elements, and basic requirements for biometric identity assurance services, a framework for the implementation of generic, biometric-based identity services within a services-oriented environment. An identity in the context of BIAS comprises a subject, biographic data, and biometric data. Other parts are intended to define specific BIAS implementations (or bindings) within specific environments, for example, SOAP web services.