Table of contents
PEMEA Requirements for Tender Documents
PEMEA is a fast evolving suite of specifications with new capabilities being added to meet new needs. This document is designed to make it easy for agencies requiring PEMEA capabilities in new systems to specify precisely what they want, by way of clearly stating functionality with references to relevant documentation and standards. Agencies writing tender documents are encourage to reference, replicate or paraphrase aspects of this document as they see fit to best ensure that their new solutions will have the capabilities they need to support emergency services in the years to come.
PEMEA ETSI Technical Specification
The ETSI PEMEA specification TS 103 478 provides all the detailed technical information necessary to build PEMEA nodes. If just want to link your PSAP into the PEMEA network or add PEMEA into your new or existing App, then you may find it easier to go through a PEMEA provider. You can find out more about using PEMEA providers here
PEMEA UserInfo data format
PEMEA uses the IETF PIDF-LO (RFC 4119) data structure for conveying location information. Part of that specification allows Additional-Data to be sent by reference, and one of the Additional-Data sets is the SubscriberInfo (RFC 7852). There are no two ways about it, the SubscriberInfo is a horrible data structure. The PEMEA specification tried to profile it to help with implementation interoperability, but the truth of the matter is, that the format just isn’t really fit for purpose. So, during the course of project NEXES a new format called UserInfo was defined. This is a JSON structure that is easy to follow and meets all of the needs of PEMEA and PSAPs. The document describes how to use the format and how to convey the format using PEMEA.
PEMEA Real-Time Text (RTT) Specification
The PEMEA Real-Time Test (RTT) protocol enables a communication channel that allows PEMEA enabled internet applications and PEMEA enabled PSAPs to communicate via chat messages. The protocol defines how participants can send T.140 characters so that the conversation can be seen by all participants in real time.
The protocol allows for conference style communication, where multiple users can communicate in the same session. This allows PSAPs to add third-party users to the call.
Hearing impaired people are used to communicate with their acquaintances using chat with the most common internet applications, this specification allows them reach emergency services using the communication channels they are most used to.
PEMEA Service Discovery specification
This extension allows a PEMEA-enabled App to discover what PEMEA services are available in an area. This is crucial for people with disabilities, since not all PEMEA-enabled areas will initially support all PEMEA capabilities. Knowing what capabilities are available in advance of needing to make an emergency call means that the App and/or user can choose methods that they know will work and so save valuable time at the very start of the incident.
PEMEA Instant Messaging (IM) Specification
The PEMEA Instant Messaging (Chat) protocol enables a communication channel that allows PEMEA enabled internet applications and PEMEA enabled PSAPs to communicate via chat messages. The protocol defines not only text messages, but also replies to previous messages and translation of messages, which can be used to have automatically generated translations for the languages of the participants while maintaining the original text, and the users can decide to see translated messages or the original ones.
The protocol allows for conference style communication, where multiple users can communicate in the same session. This allows PSAPs to add third-party users to the call.
Hearing impaired people are used to communicate with their acquaintances using chat with the most common internet applications, this specification allows them reach emergency services using the communication channels they are most used to.
PEMEA Audio Video Specification
The PEMEA Audio Video extension enables a communication channel that allows PEMEA enabled internet applications and PEMEA enabled PSAPs to communicate via audio and video in the form of video calls. Audio and video streaming is something that users often use to communicate with their acquaintances as most common internet applications offer it. The video streaming allow PSAP operators to obtain a high high awareness of the situation in a very short period of time.
The protocol allows for conference style communication, where multiple users can communicate in the same session. This allows PSAPs to add third-party users to the call with the caller, such as a sign language interpreter.
The protocol also standardizes the control of session streams for moderator users. This allows PSAPs to control the streams of users participating in the conversation
PEMEA Cellular Network Info v1.1
PEMEA uses the cellular network identifiers from the HELD measurements specification (RFC 7105). However, these representations don’t include provisions for 5G and the way that they are used in TS 103 478 doesn’t provide enough information to meet PSAP demands. In consequence, the PEMEA Consortium has developed a new mechanism for representing cellular network information, that can be conveyed in the PEMEA EDS accesData element. This new mechanism is extensible and can support 6G and beyond.
PEMEA Close EDS
PEMEA allows AP nodes to specify URLs where they can be notified of certain operations from the PSAP that accepted the EDS. However, TS 103 478 does not define a mechanism to inform the AP that the PSAP is ending the communication. This can be done using the EDS schemas defined in TS 103 478 since they are extensible. The document describes how to use the onClosePost attribute from an AP so that it can be notified when the communication is ended by the PSAP answering it.
PEMEA Approval process
All entities, AP, PSPs, PSAPs and ASPs need to have a PEMEA identifier (PEMEA-ID) for compliancy purposes (PEMEA registration). The registration procedure described in this document is based on
a trusted process dependent on peer sponsorship.
GDPR and EENA PEMEA documentation
General Data Protection Regulation was put in place to protect the privacy of European citizens and it covers a lot of different aspects relating to a person, including information about the device they are using to communicate and how it connects to the network. The PEMEA GDPR conformance statement explains how various kinds of information are used and stored in the context of communications involving PEMEA. All PEMEA providers conform to the information in this document.
PEMEA_OPS_v10.3
This document describes the operational model of the PEMEA network. It describes the different concepts PEMEA operatives and how they fit into the overall PEMEA ecosystem.
It aims to explain how PSAPs can interconnect with the PEMEA network to receive emergency communications made from Internet applications.