Other IT standards

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

Concise Binary Object Representation (CBOR, RFC 7049) extends the JavaScript Object Notation (JSON, RFC 8259) data interchange format to include binary data and an extensibility model, using a binary representation format that is easy to parse correctly. It has been picked up by a number of IETF efforts (e.g., CORE, ANIMA GRASP) as a message format.

• The IETF CBOR working group will update RFC 7049 to deal with existing errata. Security issues and clarifications may be addressed, but changes to the document will ensure backward compatibility for widespread deployed codebases. The resulting document will be targeted at becoming an Internet Standard.
• This WG falls under the IETF applications and real-time area.

The IETF Binary Floor Control Protocol Bis (BFCPBIS) working group is chartered to specify a revision of BFCP (RFC 4582) to support both TCP and UDP as transports.

• The revision adds optional support for UDP to BFCP. The security when using UDP will be based on DTLS. The updated protocol will use an existing approach (e.g., stop and wait with a single outstanding transaction) to provide a reliable, congestion safe, and TCP friendly transport.
• The updated protocol will also be able to deliver server-initiated transactions reliably when needed. The WG will research the size of messages used and decide if fragmenting a request or response over multiple UDP packets is required. The new protocol will be backwards compatible with RFC 4582 when used in TCP mode.
• The BFCPBIS WG coordinates closely with the MMUSIC WG to create a revision of RFC 4583 specifying how BFCP is signaled in SDP so that it supports UDP as well as TCP transports.

Most of the WG's milestones for applications and real-time area have been achieved.

The Real-time Transport Protocol (RTP) is an Internet Standard. RTP and its associated profiles and payload formats provides for real-time transmission of audio and video over unicast and multicast transports.

The Audio/Video Transport Core Maintenance (avtcore) Working Group in IETF is chartered to:

• Maintain the core RTP/RTCP specifications and the AVP, SAVP, AVPF, and SAVPF profiles.
• Develop application-specific guidelines for the use of RTP/RTCP protocols with the AVP, SAVP, AVPF, and SAVPF profiles, and extensions to those protocols that are driven by application-specific needs.
• Specify and maintain payload formats for use with RTP, developing RTP payload formats for new media codecs, review and revise existing payload formats to advance those that are especially
  useful to Internet Standard, and declare others Historic.
• Evaluate and process proposals for RTP eXtended Report Block (XRBLOCK) definitions containing new metrics.

The WG's milestones span early 2019 to Mar 2020.

The OASIS eMIX TC works to define standards for exchanging energy characteristics, availability, and schedules to support the free and effective exchange of information. Better communication of actionable energy prices will help enable and expand efficient markets that satisfy the growing demand for lower-carbon, lower-energy buildings, net zero-energy systems, and supply-demand integration that take advantage of dynamic pricing. Businesses, homes, electric vehicles and the power grid will benefit from automated and timely communication of energy price, characteristics, quantities, and related information.
 
eMIX focuses on methods of exchanging market information consistent with the OASIS Blue approach, encompassing consistency, transparency, and security.
 
The eMIX TC works closely with the OASIS Energy Interoperation TC and the OASIS WS-Calendar TC, which respectively are developing Web services-based information and communication models for exchanging dynamic pricing, reliability, and emergency signals and information on energy market participation (such as bids), load predictability, and generation, and common schedule information.

The Energy Interoperation TC works to define interaction between Smart Grids and their end nodes, including Smart Buildings, Enterprises, Industry, Homes, and Vehicles. The TC develops data and communication models that enable the interoperable and standard exchange of signals for dynamic pricing, reliability, and emergencies. The TC's agenda also extends to the communication of market participation data (such as bids), load predictability, and generation information.