METHOD FOR PROVIDING AN EMERGENCY RESPONSE SERVICE AND EMERGENCY RESPONSE SERVICE SYSTEM

Description

[0001] The present invention relates to a method for providing an emergency response service and to an emergency response service system.

[0002] Currently, the Emergency Response Services in USA and Europe are in transition from legacy PSTN systems to the Next Generation 911 (NG911) based on the Internet Protocol (IP). The advantage of the NG911 is that it allows the support of different communication technologies such as wireless phones, text and picture messaging, video chat, social media, and Voice over Internet Protocol (VoIP) devices.

[0003] In this scenario, there are many opportunities for Internet of Things (IoT) implementations. Connected homes and enterprises as well as transportation utilities are becoming a reality with the large development of IoT sensors and monitoring devices. These devices can notify emergency situations, providing a bunch of data including the exact location of the incident.

[0004] However, to connect these private locations to the NG911 is a challenge. Each IoT device vendor develops its own communication protocol. To converge many devices in a single platform some IoT communication frameworks are available but nevertheless, these frameworks need to be enhanced with respect to each new vendor in the market.

[0005] The document WO 2014 / 018387 A2 relates to an i3 proxy module. An i3 proxy module is provided within a 911 service provider network (e.g., at the VoIP positioning center) to respond to a VoIP i2 SIP INVITE destined for a PSAP having i3 architecture. The i3 proxy module responds to the VoIP i2 SIP INVITE by generating a VoIP i3 SIP INVITE with PIDF-LO and routing the same to the i3 emergency services routing proxy (ESRP) within the i3 network. Thus, an i3 SIP INVITE with PIDF-LO is sent from an i3 proxy module associated with an i2-based VoIP positioning center (VPC). Thus, legacy originating service provider (OSP) carrier networks are now enabled to route an emergency call to a PSAP having an i3 ESInet architecture.

[0006] The document MARKAKIS EVANGELOS K ET AL, "EMYNOS: Next Generation Emergency Communication", IEEE COMMUNICATIONS MAGAZINE, IEEE SERVICE CENTER, PISCATAWAY, US, vol. 55, no. 1, doi:10.1109 / MCOM.2017.1600284CM, ISSN 0163-6804, (20170101), pages 139 - 145, (20170118), XP011639264 presents an EMYNOS project which aims to the design and implementation of a Next Generation platform capable of accommodating rich-media emergency calls that combine voice, text, and video, thus constituting a tool for coordinating communication among citizens, call centers and first responders.

[0007] The document Nena, "NENA Detailed Functional and Interface Standards for the NENA i3 Solution NENA Detailed Functional and Interface Standards for the NENA i3 Solution", (20160210), pages 1 - 363, URL: https: / / www.nena.org / resource / resmar / standards / NENA-STA-010.2_i3_Architectu.pdf, (20191205), XP055649621 describes how NG9-1-1 works after transition, including ongoing interworking requirements for IP-based and TDM-based PSAPs and origination networks..

[0008] Besides that, the emergency response services also would need a dedicated system to handle such information.

[0009] Therefore, the present invention is based on the object to provide a method for providing an emergency response service and an emergency response service system according to which more precise emergency data may be provided in the event of an emergency.

[0010] The object is solved by a method for providing an emergency response service having the features according to claim 1, and an emergency response service system having the features according to 14. Preferred embodiments of the invention are defined in the respective dependent claims.

[0011] Accordingly, a method for providing an emergency response service based on the Internet Protocol, IP, is provided according to the present invention, wherein an emergency call initiated by a subscriber due to an emergency situation is received by a SIP server together with location information, and wherein the SIP server associates the location information with the subscriber that initiated the emergency call, wherein the method comprises the steps of connecting at least one Internet of Things IoT device belonging to the subscriber to the SIP server; associating, in the SIP servers, the at least one IoT device to the location information; receiving at the SIP server, from the at least one IoT device, real time data associated with the emergency situation; and transmitting the real time data associated with the emergency situation to an emergency service routing proxy ESRP of an emergency IP network solution EsiNet.

[0012] By the inventive method, by integrating data of IoT devices into the emergency call and response process, more precise data may be provided as to the emergency situation. For example, an IoT device as a camera located in the branch office at a location where a fire broke out, is able to provide additional information on the emergency situation, as how severe the fire is, and where it is located exactly. Thus, the handling of an emergency may be improved significantly.

[0013] Also, according to the inventive method, an innovative solution is provided so as to unify the information provided by the IoT devices in order to integrate both NG911 systems and security monitoring and measurement devices from a location served by the emergency services.

[0014] Preferably, the SIP server is a SIP Proxy, a SIP Session Border Controller, an IP PBX or any other SIP entity.

[0015] Preferably, the IoT devices are security monitoring and measurement devices located in or close to a branch office of the subscriber. However, it is also possible that the IoT devices are located somewhere else, i.e., not within the branch office itself.

[0016] It is also advantageous, if the method further comprises a step of associating the location information to the subscriber.

[0017] According to a preferred embodiment of the invention, the location information is associated to the subscriber by assigning it to a single Destination Number DN or a range of DNs, a single IP number of an IP subnet, or to a physical port.

[0018] Also, the method may further comprise a step of associating the subscriber and the at least one IoT device.

[0019] Preferably, the at least one IoT device is a sensor and / or a monitoring device.

[0020] Moreover, according to another preferred embodiment, the method further includes a step of extending Presence Information Data Format PIDF for transporting data received from the at least one IoT device to the ESRP.

[0021] According to still another preferred embodiment of the invention, the PIDF-LO is used for transporting the location information of the at least one IoT device to the ESRP.

[0022] Preferably, the method further includes a step of automatically generating an emergency call from an IoT device event.

[0023] Further, the PIDF may comprise a contact element, in particular, an URL of the contact address indicating how a person or entity of at least one IoT device can be reached.

[0024] The PIDF may further comprise a timestamp element that designates the time at which the PIDF document was created.

[0025] Preferably, the PDIF document is an XML document.

[0026] Moreover, according to the present invention, an emergency response service system is provided, comprising at least one branch office connected to a VoIP network by a SIP server, the branch office being served by an Emergency IP Network Solution EsiNet, wherein the system is adapted to carry out the method specified above.

[0027] According to a preferred embodiment of the invention, at least one IoT device is connected to the SIP server, the at least one IoT device being connected to an IoT management system or to an IoT gateway.

[0028] The invention and embodiments thereof will be described below in further detail in connection with the drawing. Fig. 1schematically shows a scenario of a branch office with IoT monitoring devices connected to a local management according to an embodiment of the invention; Fig. 2A and Fig. 2Billustrate two approaches to connect the IoT devices to the SIP server according to an embodiment of the invention; Fig. 3illustrates how subscribers and IoT devices are associated in a SIP server; Fig. 4schematically shows another scenario of a branch office according to an embodiment of the invention; Fig. 5schematically illustrates another scenario for automatic emergency calls with extended PIDF providing callback contact information according to an embodiment of the invention; and Fig. 6schematically illustrates another embodiment for a scenario to provide emergency video calls.

[0029] Fig. 1 schematically shows a branch office 1 connected to the VoIP network 2 by a SIP Server, in this case a SIP Proxy 3. The SIP Proxy 3 is connected to Session Initiation Protocol (SIP) Service Provider that provides the access to the Public Switched Telephone Network (PSTN). All IoT devices 9, which in the embodiment shown here are security monitoring and measurement devices 11 are connected to a local management system 4 via an IoT network 8.

[0030] This location is served by the NG911 service, i.e., an Emergency IP Network Solution 5 (EsiNet). The EsiNet 5 is composed by the Border Control Function 6 (BCF) and the Emergency Service Routing Proxy 7 (ESRP).

[0031] SIP Proxies 3 are elements that route SIP requests to user agent servers (UAS) and SIP responses to user agent clients. A request may traverse several proxies on its way to a UAS. Each will make routing decisions, modifying the request before forwarding it to the next element. Responses will route through the same set of proxies traversed by the request in the reverse order.

[0032] An emergency call can be recognized by a SIP Proxy 3 by comparing the R-URI to pre-defined list of emergency numbers. A call to a number in this list triggers the server 3 to establish an outgoing call to the PSTN. SIP Proxies 3 may support the conveyance of location information, i.e., the Geo-location header field and the Presence Information Data Format Location Object (PIDF-LO) according to the RFC5491. This information can be transparently forwarded or included by the server in the SIP INVITE message sent to the PSTN.

[0033] The SIP proxy 3 is able to associate a location information to the subscribers under it in many ways: the location information may be assigned to a single Destination Number (DN) or range of DNs, single IP number or IP subnet, or for physical ports in case of analog subscribers. The location information may be configured in the SIP Proxy 3 database in terms of civic location or other representation described in the RFC5491.

[0034] In case an emergency situation occurs, for example, a subscriber A (not shown in the figure), in this office 1, will generate an emergency call. Once the SIP Proxy 3 determines that it is an emergency call, the server checks if the Presence Information Data Format Location Object (PIDF-LO) was received or must be included in the SIP INVITE message body and sends this message via the SIP trunk in order to reach the Emergency Service of the EsiNet 5.

[0035] However, a plurality of devices 9 are connected in this branch office 1. Thus, according to the embodiment illustrated in this scenario, the private IoT network 8 is connected to the SIP network via a SIP proxy 3 in order to take advantage of the IoT devices 9 in a branch office 1 in case of emergency situations. This includes: an association of subscribers and IoT devices 9 even if they are not in the same location; a definition of a method to unify the data format used to transmit the information collected from IoT devices 9 to the emergency services by usage of the PIDF object; a definition of a method to include the PIDF object with IoT device data in an emergency call; a definition of a method to generate automatic emergency calls from IoT device events; and / or a definition of a method to provide real time data from IoT devices 9 using Message Session Relay Protocol (MSRP) or video stream.

[0036] Fig. 2A and Fig. 2B illustrate two approaches to connect the IoT devices 9 to the SIP proxy according to an embodiment of the invention, whereby in Fig. 2A, the IoT management system 4 shown in Fig. 1, here, is replaced by an IoT gateway 10 connected to the SIP proxy 3. The communication between them can be achieved using SIP, Websocket, or any other communication protocol over IP. In Fig. 2B, the IoT devices 9 are connected directly to the SIP proxy 3. In this case, the SIP proxy 3 is enhanced with any one of the available frameworks to communicate with the security monitoring and measurement devices 11.

[0037] In both approaches, the SIP proxy 3 has access to the IoT devices 9 connected to it. By a unique identifier, for instance, the IP address, the SIP proxy 3 may associate IoT devices 9 to location information as it is also done for the subscribers. The location of the IoT devices 9 may be also received from the IoT Gateway 10.

[0038] Fig. 3 illustrates how subscribers and IoT devices 9 are associated in a SIP proxy 3 (see Fig. 1). The Presence Information Data Format (PIDF) defined by RFC3863 can be extended to transport IoT devices data to the EsiNet (for example EsiNet 5 shown in Fig. 1). The PIDF-LO used to transport the geo-location information is an example of extended PIDF. The PIDF format provides an unlimited number of tuple, device or person elements. Each IoT device 9 can be identified as a "device" element. Each device element is identified by a unique ID.

[0039] The PIDF optionally contains a "contact" element that is the URL of the contact address that shows how a person or entity responsible for this device can be reached. It is noted that in the emergency services context, some situations require callback to the emergency call originator. The PIDF optionally contains a "timestamp" element that designates the time at the PIDF document was created giving some idea of when the IoT device data was collected.

[0040] Each tuple, device or person element contains a single status element. The RFC3863 defines the status element as extensible, i.e., this element may contain any number of extension elements that can be defined to inform the status of each IoT device 9 according to their specificities. By categorizing the security monitoring and measurement devices, a set of relevant data can be defined in terms of status elements such as temperature, smoke presence, distance, alarm detected, etc. The PIDF document is an XML document; this extension may be defined in terms of the XML schema. For example:

[0041] A single PIDF document may provide the information on the location of subscribers and IoT devices 9 by the PIDF-LO as well as the status of these devices using this new PIDF extension. The same information may also be sent in multiple PIDF documents.

[0042] Considering the PIDF-LO is already supported by the NG911 services, the usage of the PIDF extension may easily integrate emergency services and IoT devices 9 for the following reasons. First of all, the EsiNet does not have to implement a dedicated service to support different protocols, message flows or data format used by the IoT devices 9. On the other hand, the call containing the monitoring data may be routed inside the EsiNet as a common emergency call. Besides the SIP protocol, the PIDF document may be sent in the body of any protocol capable to carry an XML document.

[0043] Fig. 4 illustrates a scenario according to another embodiment of the invention, whereby a method of enhanced emergency calls with extended PIDF is implemented. Here, the subscriber A is considered as being the originator 12 of the emergency call. Its IP address is within emergency subnet 10.1.21.0 previously configured. To this subnet two IoT devices 9 are associated: a smoke detector, IP address 10.1.21.100 and a smart locker, IP address 10.1.21.101. Both devices 9 are in the same subnet 10.1.21.0 and in this case, they have the same geo-location A of the subscriber A. Besides the location of the IoT devices 9, the SIP proxy 3 may consult relevant data provided by them. With this data, it creates an enhanced PIDF document, including the geo-location of subscriber originator 12 of the emergency call, the current snapshot data of IoT monitoring devices 11 associated to that subscriber, as indicated below.

[0044] Thus, this PIDF document is included in the SIP INVITE message sent to the EsiNet 5 via the SIP Service Provider. Once arrived in the EsiNet 5, this call can be routed as any other call with PIDF-LO.

[0045] Fig. 5 schematically illustrates another scenario for automatic emergency calls based on an IoT event using the extended PIDF providing callback contact information according to an embodiment of the invention. Here, once a critical event is notified by any of the security monitoring and measurement devices 11 in the branch office, the SIP proxy 3 calls a predefined destination that may be or not the emergency service, in order to provide information on the situation.

[0046] Considering, for example, the smoke detector, IP address 10.1.21.100, in the Figure 5, which is one of the security monitoring and measurement devices 11, this sensor is located within the subnet 10.1.21.0 with geo-location A, indicated by reference numeral 14. This sensor is also associated to the subscriber B, with geo-location B, indicated by reference numeral 13. Once the sensor detects some smoke, the SIP proxy 3 is notified and automatically calls the predefined destination, in this case the emergency service. The SIP INVITE message sent by the SIP proxy 3 includes the location (PIDF-LO) and data (new extended PIDF) of the smoke detector as well as the subscriber B contact as being responsible for this device.

[0047] When the call is answered, an Interactive Voice Response (IVR; not shown), the media server or other system application capable to play a voice message can be used to play an announcement to the called party. Alternatively, a text message can be sent via the Message Session Relay Protocol (MSRP). The EsiNet 5 already supports the MSRP.

[0048] With the PIDF data included in the SIP INVITE or other SIP method, the called party is able to callback subscriber B to provide additional assistance.

[0049] Fig. 6 illustrates schematically another embodiment for a scenario to provide emergency video calls. Here, the SIP proxy 3 may also send IoT device data via payload. This is especially applicable when it is intended to share real time data provided by devices such as cameras. Currently, security and monitoring systems send an alarm message to a central monitoring station. Even the emergency calls enhanced with the extended PIDF where additional information from the IoT devices 9 is included cannot be visually confirmed. Besides that, an emergency situation in which, for example, medical assistance is required, the possibility to see the situation in in real-time may help the responder to provide better assistance.

[0050] Thus, when the emergency call is generated by a device that is able to provide video calls such as cellphones, PC with webcams, etc, the video stream 16 may be transmitted to the emergency responder 17. Considering the Subscriber A in Fig. 6, indicated by reference numeral 15, the latter may generate an emergency call in order to obtain medical assistance. Subscriber A is an analog device and does not have any camera, however, in that room there is a surveillance IoT camera 9', 11' connected to the SIP proxy 3. The SIP proxy 3 knows that subscriber A and the IoT camera 9', 11' are associated; internally, the SIP proxy 3 creates a bridge between the audio stream 18 from the susbcriber A and the video stream 16 provided by the IoT camera 9', 11' generating a single media stream to the EsiNet 5 for which this is a common video call, routed normally inside the network.

[0051] The call enhanced with video can also be applied to the emergency callback calls where the call is originated outside the branch office to a device in the branch office.

[0052] Thus, summarizing the above, according to the embodiments described above, private monitoring devices are connected to public the Emergency Response Service using capabilities already supported by the EsiNet. The EsiNet does not have to implement a dedicated service to support different protocols, message flows or data format used by the IoT devices. The call containing the monitoring data may be routed inside the EsiNet as a common emergency call. Besides the SIP protocol, the PIDF document may be sent in the body of any protocol capable to carry an XML document. Besides the public Emergency Services, the embodiments described above may be extended to any private security or monitoring service.Reference numerals

[0053] 1branch office 2VoIP network 3SIP server 4IoT management 5emergency IP Network (EasiNet) 6Border Control Function 7Emergency Service Routing Proxy 8IoT network 9IoT devices 10IoT gateway 11security monitoring and measurement devices 12originator of emergency call 13geo-location B 14geo-location A 15subscriber A 16video stream 17emergency responder 18audio stream

Claims

1. Method for providing an emergency response service based on the Internet Protocol, IP, wherein an emergency call initiated by a subscriber (15) due to an emergency situation is received by a Session Initiation Protocol, SIP, server (3) together with location information, and wherein the SIP server (3) associates the location information with the subscriber (15) that initiated the emergency call, wherein the method comprises the steps of - connecting at least one Internet of Things, IoT, device (9) belonging to the subscriber (15) to the SIP server (3); - associating, in the SIP server (3), the at least one IoT device (9) to the location information; - receiving at the SIP server (3), from the at least one IoT device (9), real time data associated with the emergency situation; and - transmitting the real time data associated with the emergency situation to an emergency service routing proxy, ESRP, of an emergency IP network solution, EsiNet. (5)2. Method according to claim 1, wherein the real time data is received from the at least one IoT device (9) using Message Session Relay Protocol, MSRP, or video stream.

3. Method according to claim 1 or claim 2, wherein the at least one IoT device (9) is a security monitoring and measurement device (11) located in or close to a branch office (1) of the subscriber (15).

4. Method according to any one of the preceding claims, wherein the method further comprises a step of associating the location information to the subscriber (15).

5. Method according to claim 4, wherein the location information is associated to the subscriber (15) by assigning it to a single Destination Number, DN, or a range of DNs, a single IP number of an IP subnet, or to a physical port.

6. Method according to any one of the preceding claims, wherein the method further comprises a step of associating the subscriber (15) and the at least one IoT device (9).

7. Method according to any one of the preceding claims, wherein the at least one IoT device (9) is a sensor and / or a monitoring device (11).

8. Method according to any one of the preceding claims, wherein the method further includes a step of extending Presence Information Data Format, PIDF, for transporting data received from the at least one IoT device (9) to the ESRP.

9. Method according to claim 8, wherein the PIDF-LO is used for transporting the location information of the at least one IoT device (9) to the ESRP.

10. Method according to any one of the preceding claims, wherein the method further includes a step of automatically generating an emergency call from an IoT device event.

11. Method according to any one of claims 8 to 10, wherein the PIDF comprises a contact element, in particular, an Uniform Resource Locator, URL, of the contact address indicating how a person or entity of at least one IoT device (9) can be reached.

12. Method according to any one of claims 8 to 11, wherein the PIDF further comprises a timestamp element that designates the time at which the PIDF document was created.

13. Method according to claim 12, wherein the PDIF document is an extensible Markup Language, XML, document.

14. Emergency response service system comprising at least one branch office (1) connected to a Voice over Internet Protocol, VoIP, network (2) by a SIP server (3), the branch office (1) being served by an Emergency IP Network Solution, EsiNet (5), wherein the system is adapted to carry out the method according to any one of the preceding claims.

15. Emergency response service system according to claim 14, wherein at least one IoT device (9) is connected to the SIP server (3), the at least one IoT device (9) being connected to an IoT management system or to an IoT gateway (10).