scope:

The present document is divided into two parts. The first part provides the requirements and functional architecture while the second part provides the protocol and procedures for implementing the Pan-European Mobile Emergency Application (PEMEA). The first part identifies the key functional entities involved in the emergency application architecture, the interfaces between each functional entity, and the requirements on each interface. The second part defines the data exchanges, message, protocols and procedures used across each of the identified PEMEA interfaces.

It is recognized that many existing application implementations combine the functional entities identified in the present document into a single entity. The most common example of combined functional entities is the combined Application Provider (AP) and PSAP Service Provider (PSP), these are common because it is often the PSAP that writes or engages a third-party to write a local emergency application that interfaces directly with the PSAP. The present document does not seek to disallow integrated node implementations, however, it does not define how additional applications or application providers using proprietary application programming interfaces (APIs) and protocols can provide PEMEA extended features, such solutions are left to the integrated node providers.