A Taste of AIMES Use Cases

In order to support the development of the AIMES user and system requirements, the AIMES partners created a set of use cases that help to describe the use of next generation emergency calls.

In order to support the development of the AIMES user and system requirements, the AIMES partners created a set of use cases that help to describe the use of next generation emergency calls, involving rich multimedia and data exchange capabilities, to improve the efficiency and performance of emergency response interventions.

Use case: Hearing Citizen Sees a Traffic Accident

Robert is a 42-year old who lives in the downtown area of a big city. Robert has installed the local emergency app and configured it for use with voice calls (OTT) and PEMEA. He is also aware that video and text associated with the voice call are possible to enable during an emergency call.

During the morning rush hour traffic, Robert walks from his home to his office. This morning he sees an accident between a car and a pedestrian. Robert uses the emergency app to contact the emergency services and communicates with the 112 operator via voice. The driver is in shock, the 112 operator realises that this is a medical emergency, but wants to get a better overview of the situation. Hence, the 112 operator asks Robert to start a video call. Robert switches from the front camera to the back camera of the device. Robert is now able to show a live video feed from the location. The 112 operator decides to send two ambulances and a police car as the traffic is jammed up. The 112 operator can see Robert’s exact location via the GPS coordinates provided from Robert’s device, that are sent via the AIMES system to the PSAP.  While waiting for the ambulances to arrive at the scene, the 112 operator gives Robert visual instructions to stop the bleeding.

Use case: Hard of Hearing Lumberjack Starts Forest Fire

George is 53 years old and has almost lost his hearing. He can speak well, but in remote communication he cannot hear and needs text to supplement his hearing. He is a lumberjack working the tree felling machine at the edge of a deforestation. George has installed an emergency app which allows him to speak with the operator while the operator can respond with text. 

While felling trees, sparks from the machine cause the dry ground cover to catch on fire. George uses the fire extinguisher in the machine cabin to try to extinguish the flames. However, the dry surroundings enable the fire to spread faster than he can extinguish it, the wind is picking up and George needs the fire brigade.

George picks up his phone, opens the emergency app and calls the emergency services.

The operator answers with text, asking what the situation is. 

George says that there is a fire he cannot extinguish, roughly at his location (he is too deep into the forest for street names to be accurate enough). The emergency application is using the device’s GNSS to continuously send George’s position through the AIMES system to the PSAP.  

The operator confirms George’s exact location via the GNSS coordinates and asks what is burning and how severe it is.

George explains that he is a lumberjack and that the ground cover has caught fire, but it is spreading. He turns on the camera and switches to the back camera to show how the wind is blowing the flames towards the forest.

The operator grasps from the video that the situation is escalating quickly and informs the fire brigade that there is a risk of a forest fire and the need of more resources to the area and preparation of forest fire fighting personnel.

The 112 operator informs George that the fire brigade is on route and that George should leave the location for his safety.

Use case: NG112 and PEMEA Interoperability via Shared ESInet Components

Brian is visiting Romania and has his PEMEA App that supports a native chat communication service that does not require a corresponding voice call. One evening while wandering down a narrow laneway, Brian twists his ankle and falls heavily. Brian does not speak or read Romanian, so calling 112 using his phone is going to make things difficult and he is in a lot of pain.

Brian pulls out his phone and uses his PEMEA App to make an emergency chat call. Brian’s home AP knows that he wants to use chat as the primary communication mechanism and sets the no voice call capability in the EDS and then sends the message into the PEMEA network.

The message travels through the PEMEA network and into Romania via the Romanian ASP and then on to the PEMEA PSP that operates as a gateway into the secure emergency network. The PSP checks its white list to see if the source AP for the EDS is allowed to contact the Romanian PSAP. Lucky for Brian his AP is in the list. The PSP sends a LoST message to the ESInet’s ECRF to get the correct destination PSAP. The PSP then sends the EDS to the PEMEA Interface Module (PIM) inside the PSAP.

The PIM immediately recognizes that no voice call will be coming with the EDS because it sees that the no voice call chat capability has been requested. The PIM sends an onCapSupportPost immediately and then creates a chat room and invokes the chat function in the AP.

Brian’s preferred language is English and the AP notifies Brian in English that he is able to chat now. The PSAP call-taker comes online and enters the chat room. The call-taker types in Romanian but Brian gets English messages in his phone, while Brian types in English and the call-taker gets the messages in Romanian. The call-taker is able to determine where Brian is using the location update function provided by PEMEA, is able to determine that he speaks English and by asking him questions is able to determine what kind of help he needs. This saves a lot of time and makes sure that Brian is treated quickly and efficiently. 

Use Case: Smoke Sensor Issues Automated 112 Call

During the night, a short circuit in an electrical heater in the living room causes a fire. The fire consumes nearby drapes and extends to several places in the house. The smoke released becomes very heavy as it spreads in the ground floor and to the rooms in the upper floor, where the family is asleep, not taking notice of both the smoke and the fire.

When the smoke reaches the kitchen, the installed AIMES-enabled smoke sensors immediately detect it and an alarm is triggered. A loud sound, flashing lights and a mobile phone alert (text message with ringing tone and vibration) warns of the danger and awakes the family members that rush into safety in the outside of the house.

At the same time, the AIMES-enabled sensors use the WiFi connectivity to issue an automated call to 112 services, sending the house’s location and the sensor information about the emergency situation (e.g., fire alert; concentration level of smoke; air quality level; identification of the sensor’s owner), enabling the emergency services to quickly dispatch the appropriate response.

When the First Responders arrive at the scene, the fire has not yet expanded in the house and the fire brigade is able to salvage the house’s upper floor and roof, while ensuring that the neighbouring houses are also safe. The medical emergency team also treats the family members for smoke inhalation.

If the house would not have been equipped with smart AIMES-enabled smoke sensors, the emergency response would have been considerably delayed and not as well-informed on the emergency, seriously compromising a successful outcome for the family rescue and the protection of their property.