Patent Grant
11330664
The present disclosure relates generally to emergency calls, enhanced 9-1-1 (E911) and next generation 9-1-1 (NG911) emergency networks, and more particularly, to determination and provision of location data and other data for emergency calls.
Despite advances that have been made in emergency network technology, emergency networks remain relatively ill-prepared and have not technologically advanced in step with the needs for the determination of the location of mobile devices as well as non-landline devices in emergency situations. Additionally, because of ubiquitous, yet constantly evolving communication technologies and applications, emergency networks are bombarded with emergency communications from a plethora of non-homogeneous sources. Traditionally, emergency networks received voice calls from landline telephones via a public switched telephone network (PSTN) from which determining the caller and the caller's location was relatively straightforward because PSTN telephones were at fixed locations and associated with a given subscriber. The advent of wireless communication introduced additional complexities due to the mobility of callers. With the further advent of mobile Internet connectivity, which enables “over-the-top” voice-over-Internet-protocol (VoIP) and other messaging application communications, further challenges were introduced with respect to locating callers.
Briefly, the present disclosure provides apparatuses, systems and methods of operation for obtaining emergency data including location data and other emergency data, and providing the emergency data to emergency networks independently from emergency call routing to the emergency networks. The emergency data may be obtained even in situations where emergency call routing to a particular emergency network is interrupted due to call routing network outages. The emergency data is sent to the emergency networks and may be displayed on emergency network entities of the emergency networks prior to the related emergency call routing completion to the emergency networks. In other words, emergency network entity operators can see emergency call data in advance of receiving the actual related emergency call. In some implementations, device identifiers are obtained from an emergency call data feed to an emergency network to relate emergency data with incoming emergency calls. The apparatuses, systems and methods of operation disclosed provide a map view on an emergency network entity, such as a workstation, showing location indicators from mobile devices from which emergency calls have been made.
One disclosed method includes: receiving emergency data related to emergency calls emanating from mobile devices, independently from emergency call routing to an emergency network; determining an emergency network that should receive the emergency data; providing the emergency data to the emergency network; and providing a map view to the emergency network entity of the emergency network using the emergency data and displaying location indicators corresponding to locations of mobile devices identified by the emergency data.
Another disclosed method includes: receiving emergency data related to emergency calls emanating from mobile devices, independently from emergency call routing to an emergency network; detecting emergency call data received at the emergency network; and providing a map view to an emergency network entity of the emergency network using the emergency data, the map view displaying location indicators corresponding to locations of mobile devices identified by the emergency call data received at the emergency network.
The method may further include: determining a portion of the emergency data corresponding to a group of emergency calls from mobile devices located in the emergency network's service zone; and sending the portion of the emergency data to the emergency network prior to detecting the emergency call data received at the emergency network for the group of emergency calls. The method may further include: determining emergency calls placed to the emergency network that have not yet been received by the emergency network by comparing emergency call data received at the emergency network with the emergency data; and providing an emergency call queue on a display of the emergency network entity using the comparison to visually distinguish emergency calls placed to the emergency network from emergency calls received by the emergency network. The method may perform determining a portion of the emergency data corresponding to a group of emergency calls from mobile devices located in the emergency network's service zone, by: determining that the location of each mobile device that placed an emergency call in the group of emergency calls is within the emergency network's service zone by checking a geofence database that defines the emergency network's service zone.
The method may further include: detecting the emergency call data by obtaining session initiation protocol (SIP) headers at a SIP gateway, by detecting an out-of-band signal on at least on trunked line to the emergency network, or both. The out-of-band signal may provide, for example, automatic location identifier (ALI) data. The method may further include: detecting emergency call data within computer aided dispatch (CAD) spill data sent to a dispatch workstation of the emergency network from an emergency call handling workstation of the emergency network. The method may further include: obtaining a dispatch workstation address from the CAD spill data; and providing the emergency data displayed on a display of a dispatch workstation identified by the CAD workstation address, where the dispatch workstation is the emergency network entity. The method may further include: determining an emergency type based on the emergency data; determining that additional emergency data is available based on the emergency type; and providing the additional emergency data to the emergency network entity. The method may further include: determining that multimedia data is available from a source in proximity to a mobile device location; establishing a multimedia streaming connection with the emergency network entity; and providing multimedia data to the emergency network entity over the multimedia streaming connection.
A disclosed apparatus includes: a network component, operative to support an Internet Protocol (IP) connection with a plurality of emergency network entities of an emergency network, and a remote emergency data manager; and a processor, operatively coupled to the network component. The processor is operative to: receive emergency data related to emergency calls emanating from mobile devices, independently from emergency call routing to the emergency network; detect emergency call data received at the emergency network; and provide a map view to an emergency network entity of the emergency network using the emergency data, the map view displaying location indicators corresponding to locations of mobile devices identified by the emergency call data received at the emergency network.
The processor may be further operative to determine a portion of the emergency data corresponding to a group of emergency calls from mobile devices located in the emergency network's service zone; and send the portion of the emergency data to the emergency network prior to detecting the emergency call data received at the emergency network for the group of emergency calls. The processor may be further operative to: determine emergency calls placed to the emergency network that have not yet been received by the emergency network by comparing emergency call data received at the emergency network with the emergency data; and provide an emergency call queue on a display of the emergency network entity using the comparison to visually distinguish emergency calls placed to the emergency network from emergency calls received by the emergency network. The processor may be further operative to determine a portion of the emergency data corresponding to a group of emergency calls from mobile devices located in the emergency network's service zone, by: determining that the location of each mobile device that placed an emergency call in the group of emergency calls is within the emergency network's service zone by checking a geofence database that defines the emergency network's service zone.
The processor may be further operative to: detect the emergency call data by obtaining session initiation protocol (SIP) headers at a SIP gateway, or by detecting an out-of-band signal on at least on trunked line to the emergency network, or both. The out-of-band signal may provide, for example, automatic location identifier (ALI) data.
The processor may be further operative to: detect emergency call data within computer aided dispatch (CAD) spill data sent to a dispatch workstation of the emergency network from an emergency call handling workstation of the emergency network. The processor may be further operative to: obtain a dispatch workstation address from the CAD spill data; and provide the emergency data displayed on a display of a dispatch workstation identified by the CAD workstation address, where the dispatch workstation is the emergency network entity. The processor may be further operative to: determine an emergency type based on the emergency data; determine that additional emergency data is available based on the emergency type; and provide the additional emergency data to the emergency network entity. The processor may be further operative to: determine that multimedia data is available from a source in proximity to a mobile device location; establish a multimedia streaming connection with the emergency network entity; and provide multimedia data to the emergency network entity over the multimedia streaming connection.
A disclosed system includes: emergency response logic that has a network component operative to establish an Internet connection to an emergency call handling workstation, a computer aided dispatch workstation (CAD) and a remote emergency data manager; and a processor, operatively coupled to the network component. The processor of the emergency response logic is operative to: detect computer aided dispatch (CAD) spill data sent to a CAD workstation from an emergency call handling workstation, in which the CAD spill data has at least one device identifier associated with an emergency call; send a query to the remote emergency data manager for location data using the at least one device identifier contained in the CAD spill data; receive location data in response to the query; and provide the location data to the CAD workstation on a map view within a browser window having an Internet protocol session with the remote emergency data manager.
The processor may be further operative to: detect a CAD workstation address in the CAD spill data; and provide the location data to the CAD workstation using the CAD workstation address. The emergency data manager is operative to: provide a graphical user interface to a plurality of CAD workstations via a web browser executing on each CAD workstation. The emergency data manager may be further operative to provide a unique map view to each CAD workstations based on the CAD workstation addresses detected in the CAD spill data. The emergency data manager may be further operative to provide the graphical user interfaces as a software-as-a-service graphical user interface. The emergency data manager may be further operative to provide an emergency call queue, where the emergency call queue for each CAD workstation is unique and is populated based on the CAD workstation address detected in the CAD spill data and the location data sent to the CAD workstation using the CAD workstation address. The emergency data manager may be further operative to provide the emergency call queue including emergency data obtained by the remote emergency data manager from mobile devices from which emergency calls have emanated. The emergency data manager may be further operative to provide the emergency call queue including selectable links to the emergency data.
Another disclosed method includes: receiving emergency data related to emergency calls emanating from mobile devices, independently from emergency call routing to an emergency call handling workstation; detecting automatic location identifier (ALI) data received by the emergency call handling workstation; and providing a map view to a dispatch workstation, the map view displaying location indicators corresponding to locations of mobile devices identified by the ALI data.
The method may further include providing the map view corresponding to a geographic dispatch area within which emergency calls are responded to by the dispatch workstation. The method may further include detecting the automatic location identifier (ALI) data within computer aided dispatch (CAD) spill data sent to the dispatch workstation from the emergency call handling workstation. The method may further include obtaining a dispatch workstation address from the CAD spill data; and providing the location data to a dispatch workstation identified by the CAD workstation address. The method may further include determining an emergency type from the CAD spill data; determining that additional emergency data is available based on the emergency type; and providing the additional emergency data to the CAD workstation. The method may further include: determining that multimedia data is available from a source in proximity to a mobile device location; establishing a multimedia streaming connection with the dispatch workstation; and providing multimedia data to the dispatch workstation over the multimedia streaming connection.
A disclosed apparatus includes: a network component, operative to support an Internet Protocol (IP) connection with a computer aided dispatch (CAD) workstation, and emergency call handling workstation, and a remote emergency data manager; and a processor, operatively coupled to the network component. The processor of the apparatus is operative to: detect automatic location identifier (ALI) data received by the emergency call handling workstation; obtain location data from the emergency data manager for mobile devices identified by the ALI data; and provide the location data to the CAD workstation for display in a map view displaying location indicators corresponding to locations of mobile devices identified by the ALI data. A disclosed system includes the apparatus and the remote emergency data manager. The emergency data manager is operative to: provide a map view to the CAD workstation within a web browser executing on the CAD workstation.
The apparatus processor may be further operative to: detect the automatic location identifier (ALI) data within computer aided dispatch (CAD) spill data sent to the dispatch workstation from the emergency call handling workstation. The processor may be further operative to: obtain a dispatch workstation address from the CAD spill data; and provide the location data to a dispatch workstation identified by the CAD workstation address. The processor may be further operative to: determine an emergency type from the CAD spill data; determine that additional emergency data is available from the emergency data manager based on the emergency type; and providing the additional emergency data from the emergency data manager to the CAD workstation.
The emergency data manager may be further operative to: determine that multimedia data is available from a source in proximity to a mobile device location; establish a multimedia streaming connection with the dispatch workstation; and provide multimedia data to the dispatch workstation over the multimedia streaming connection.
A disclosed system includes emergency response logic that has a network component, operative to establish an Internet connection to an emergency call handling workstation, a computer aided dispatch workstation (CAD) and a remote emergency data manager; and a processor, operatively coupled to the network component. The emergency response logic processor is operative to: detect computer aided dispatch (CAD) spill data sent to a CAD workstation from an emergency call handling workstation, the CAD spill data that has at least one device identifier associated with an emergency call; send a query to the remote emergency data manager for location data using the at least one device identifier contained in the CAD spill data; receive location data in response to the query; and provide the location data to the CAD workstation on a map view within a browser window having an Internet protocol session with the remote emergency data manager. The processor may be further operative to: detect a CAD workstation address in the CAD spill data; and provide the location data to the CAD workstation using the CAD workstation address.
The remote emergency data manager may be operative to: provide a graphical user interface to a plurality of CAD workstations via a web browser executing on each CAD workstation; provide a unique map view to each CAD workstations based on the CAD workstation addresses detected in the CAD spill data; and provide the graphical user interfaces as a software-as-a-service graphical user interface. The system remote emergency data manager may be further operative to: provide an emergency call queue, where the emergency call queue for each CAD workstation is unique and is populated based on the CAD workstation address detected in the CAD spill data and the location data sent to the CAD workstation using the CAD workstation address. The remote emergency data manager may be further operative to: provide the emergency call queue including emergency data obtained by the remote emergency data manager from mobile devices from which emergency calls have emanated. The remote emergency data manager may provide the emergency call queue including selectable links to the emergency data, and provide a web page tab opening in response to selection of a selectable link.
Turning now to the drawings wherein like numerals represent like components,
E911 and NG911 emergency networks are facilitated by an infrastructure which may include various distributed network entities such as, but not limited to, an Emergency Service Routing Proxy (ESRP) which routes IP based emergency calls to appropriate specific emergency networks of the emergency networks 170 based on, for example, a service area such as an emergency service zone. The ESRP operates as a Session Initiation Protocol (SIP) proxy for emergency calls originated using SIP. These distributed network entities may be cloud-based entities accessible via the Internet 190.
Each of the emergency networks 170 are owned and operated by emergency service providers (ESPs) which include various public and private ESPs such as a public safety answering point (PSAP), public safety services (PSS) as well as non-governmental, private ESPs. Put another way, an ESP is an organization that owns and operates an emergency network where the emergency network includes the infrastructure, network entities, communication devices and other equipment required to receive and handle emergency calls and emergency data and to provide emergency services within the ESP's service area, i.e. its emergency service zone. Emergency calls are routed to the emergency networks 170 via legacy 911 systems as well as from E911 and NG911 infrastructure which may include cloud-based network entities such as, but not limited to, cloud-based servers, routers, proxies, etc. that may be distributed and accessible via the Internet 190. Emergency calls may be routed to the emergency networks 170 from legacy 911 systems and equipment including trunked telephone lines from a public switched telephone network (PSTN), various wireless networks using trunked lines and Centralized Automatic Message Accounting (CAMA) and utilizing Signaling System No. 7 (SS7), CCITT number 7 (C7), and the like, etc. CAMA trunks include out-of-band signalizing with automatic number identification (ANI) or pseudo ANI assigned to a wireless emergency call by a wireless network. The emergency networks 170 receive an emergency call data feed 172 which provides location information for fixed wire telephones and mobile devices from which emergency calls have emanated, i.e. from which emergency calls have been made. In legacy 911 systems, the emergency call data feed 172 provides Automatic Location Information (ALI) in response to a query. Although E911 and NG911 IP based systems are still in the process of roll out, currently most emergency networks rely on legacy ALI data. In NG911 IP based systems the emergency call data feed 172 may be an XML based data feed, an HTTP data feed, SIP data feed or other suitable data feed format. Device identifiers present in an NG911 compliant SIP INVITE may also be used to establish an emergency call, and the emergency network may use the SIP INVITE device identifier to send and ALI query or use another modernized emergency call data feed 172 that utilizes XML, HTTP or SIP, etc.
In legacy 911 systems, after receiving an emergency call routed to an emergency network, the emergency network sends a query to an ALI database using the ANI information obtained in the out-of-band signaling related to the emergency call trunk in order to obtain a location for the emergency caller. The ALI database includes, or is associated with, a Master Street Address Guide (MSAG) database which provides street address information. The MSAG database is used during call routing to determine an appropriate PSAP to which an emergency call should be routed.
Additionally, if a phone number or ANI used to query the ALI database is not in the ALI database, an ALI Failure condition occurs. The emergency call in that case is routed to a default PSAP related to a general telephone switching group, and an operator has to speak with the caller to determine their location and which PSAP needs to respond based on that location information. If the caller is unable to speak, the operator would have no way of determining the caller's location.
In the case of wireless calls, the location information available for an emergency caller includes the wireless network transmission tower location at which the wireless network received the communication from the mobile device used to place the emergency call. Tower location is not sufficient to provide the emergency caller's actual location with enough accuracy to dispatch emergency responders. E911 Phase 2 location information uses radiolocation and/or GPS to get a more accurate location of the emergency caller's mobile device.
In
The emergency data manager 100 is operatively coupled to emergency networks 170 via operative coupling which may be implemented as network connections 175 through the Internet 190. The network connections 175 may include an Internet protocol (IP) connection between each of the emergency networks 170 and the emergency data manager 100 and may be connection oriented or connectionless. For example, the network connections 175 may include IP connections which may include a TCP (Transmission Control Protocol, also referred to as Transport Control Protocol) connection, a UDP (User Datagram Protocol) connection or a combination of both such as UDP over TCP, etc., or a combination of TCP and UDP connections, etc. An IP connection may further employ one or more TCP sockets or one or more WebSocket connections. The emergency networks 170 may have backhaul connections 173 to the Internet 190. The emergency data manager 100 may operate as an interface between the emergency networks 170, databases 120 and devices 160, to provide emergency data to the emergency networks 170. The emergency data manager 100 may also be capable of accessing the emergency call data feed 172 via several example mechanisms disclosed herein.
The emergency data manager 100 provides a Location Information Server (LIS) 130 that provides emergency caller device location information to the emergency networks 170. However, the location information provided by the LIS 130 is independent from the emergency call routing of emergency calls to the emergency networks 170. Because of this capability, the emergency networks 170 can receive emergency call data prior to completion of emergency call routing and call answering by the emergency network. In cases where wireless network outages occur, an emergency network may still obtain information from the emergency data manager 100 via the LIS 130. The LIS 130 provides initial device location at the initiation of an emergency call, as well as location updates as the device moves.
The emergency data manager 100 also provides an Additional Data Repository (ADR) server 140 which may include “Additional Data” such as additional data for the call, additional data for the caller and additional data for the location. The ADR server 140 provides IS-ADR capability (Identity Searchable Additional Data Repository) however it can provide services for all incoming emergency calls whether or not the emergency calls are SIP based.
The emergency data manager 100 is operative to retrieve various types of “emergency data” (which includes “additional data”) such as, but not limited to, location data, medical data, sensor data, camera data and other data, etc., determine the appropriate emergency network 170 authorized to receive specific emergency data, and provide that specific emergency data to the authorized emergency network. The emergency data manager 100 may, under some circumstances and for certain types of emergency data, store obtained emergency data in one or more databases such as database 150 which may be distributed databases. The ADR server 140 is operative to access database 150.
The emergency data manager 100 may communicate with, and retrieve and obtain data from, the various databases 120, and may also receive and store emergency data from the devices 160. The emergency data manager 100 is operative to determine the authorized emergency network using various mechanisms, one of which involves using a geofence database 101 which includes boundary information for some or all of the emergency networks 170 and also for national or regional emergency networks.
The various emergency networks 170 may include various public safety answering points (PSAPs). Each emergency network such as, but not limited to a PSAP, may include an emergency dispatch center and employ a computer aided dispatch (CAD) system. Each emergency network 170 includes various network entities such as at least one workstation, which may be a CAD system workstation, a call handling system workstation, an integrated call handling and CAD system workstation, or some other type of workstation, and which provides various graphical user interfaces (GUIs) on a display for use by emergency network personnel. The term “emergency network entity” refers to a hardware apparatus, including any necessary software or firmware, used to access or implement an emergency network such as, but not limited to, workstations, servers, routers, switches, laptops, desktop computers, etc. An emergency network entity hardware apparatus may therefore include software or firmware related to its emergency network function.
Each individual emergency network 170 may include an emergency call handling system which is operatively coupled to a PSTN (public switched telephone network) and various wireless networks 110 via appropriate backhaul connections 171 to a CPE (customer premises equipment). The PSTN and various wireless networks 110 provide, among other things, legacy emergency call routing of landline telephones and mobile telephones via, for example, CAMA trunks to the emergency networks 170.
The various emergency networks 170 are each operative to receive emergency calls 103 from a variety of devices 160 and a variety of device types. Each individual emergency network 170 may also receive emergency alerts 105 and establish emergency sessions 108 from the various devices 160 over the Internet 190 if those emergency networks are configured with the required capabilities. An emergency alert 105 may be sent as, for example, short message service (SMS) messages, SMS data messages, instant messages (IM), multi-media messages (MMS), email, or other formats of messages sent as Internet Protocol (IP) messages. For example, IP based messages may be sent using TCP, UDP, SIP, HTTP, or other mechanisms, etc. Emergency sessions 108 may also be established using these same, or other, IP protocols. An emergency session 108 refers to communication over an Internet connection between any the various types of devices 160 and an emergency network, where there is communication between one of the devices 160 and a particular emergency network of the emergency networks 170. One example of an emergency session 108 is a Voice-over-IP (VoIP) call using Session Initiation Protocol (SIP). Another example is an IP call using H.323 protocol, or some other communication protocol, etc. An emergency alert 105 is another example of an emergency session and may be, but is not limited to, data sent from a device 160 to a given one of the emergency networks 170. Because the emergency alert 105 will contain information that identifies the specific device 160 that sent the alert, the specific emergency network that received the emergency alert 105 may be able to respond to the device 160 by sending a response or acknowledgement message, or by making a call-back if the device 160 is for example, a mobile telephone such as a smartphone 107. The information that identifies a specific device 160 is referred to herein as a “device identifier.” That is, a “device identifier” refers to information allowing identification of the device or a user of the device, such as for example, a phone number associated with a user, an email address, physical address, coordinates, IMEI number, IMSI, TMSI, IP address, BSSID, SSID or MAC address, etc.
In one example of operation, an emergency alert 105 may be triggered by a device 160 in any of various ways such as, but not limited to, device fall detection, by the user pressing a soft button or a physical button (i.e. a “panic button”), a voice command, a gesture, or autonomously based on other sensor data such as via a smoke, carbon-monoxide, burglar alarm, or some other alarm, etc. In some situations, the user may confirm the emergency or provide authorization for sending the emergency alert 105.
Emergency data, such as enhanced location data, medical data, or other data, may be sent by device 160 in conjunction with an emergency alert 105, or may be sent as data updates 106 to a specific database of the various databases 120. The emergency data manager 100 facilitates getting the emergency data to an appropriate one of the emergency networks 170. The emergency data manager 100 is operative to communicate with the emergency networks 170 and to access and obtain emergency data and provide the emergency data to the emergency networks 170. For example, an emergency network may send an emergency data request to the emergency data manager 100 via the ADR server 140 such that the ADR server 140 may search or query the various databases 120 to obtain data sent by a device 160 at the time of, or prior to, sending an emergency alert 105. Alternatively, or additionally in some implementations, an emergency data request may be sent by the emergency data manager 100, over the IP connections 161, to the various databases 120 in response to an emergency alert 105 received by an emergency network.
The emergency data manager 100 or the emergency network may format stored emergency data or any received emergency data into a format that is compatible with industry standards for storing and sharing emergency data. For example, the emergency data may be formatted to be compatible with National Emergency Number Association (NENA) standards. Where emergency data is stored by the emergency data manager 100, emergency data requests may be sent to the emergency data manager 100 by the emergency networks 170 via, for example, HTTP GET requests. Emergency data requests may be sent from any one of the emergency networks 170 to the emergency data manager 100 and may utilize Location Information Server (LIS) protocol. For emergency data related to location, the data may include, but is not limited to, device generated location data (such as device 160 GPS chipset data), location information such as Location-by-Reference, Location-by-Value, etc. from, for example a, Location Information Server (LIS) or from other sources.
The various types of devices 160 that may communicate with the emergency networks 170 include, but are not limited to, desktop computers, laptop computers, tablets, mobile phones, smartphones 107, smartwatches 111 (or other health and medical tracking devices), medical bracelets 109, and various wired devices which may be Internet-of-Things (IoT) devices 113 which are operative to send and receive data from a wireless network such as, but not limited to, a 5th generation mobile network (5G network). A medical bracelet 109 may be a type of IoT device in some instances. The medical bracelet 109 may be operative to transmit an emergency alert 105 to an emergency network. Emergency calls may also be made from landline phones connected to a PSTN and medical bracelet 109 and/or health monitoring device, such as a medical bracelet 109, may use a wireless access point connected to the PSTN to place an emergency call 103 or send emergency alert 105. Each of the devices 160 may also be operative to send data updates 106 via the Internet 190 to the various databases 120. The databases 120 may contain protected data in that the data is subject to various statutorily defined protections, such as, but not limited to, HIPPA, GDPR, or other statutorily defined data protection and data privacy requirements. The databases 120 may include location databases 121, medical databases 123 and other databases 125 with various personally identifiable data related to device 160 users. The data contained in the databases 120 is referred to as “emergency data” and may be retrieved by the emergency data manager 100 via an IP connection 161.
The emergency data manager 100 is included within an emergency data management network 102 which may be a distributed network and which may include one or more servers, and one or more databases such as geofence database 101 and additional data database 150. The emergency data manager 100 may be implemented as a server having at least one processor, or may be implemented as a distributed system with multiple servers, processors, memory and databases, and may further provide cloud-based, software-as-a-service (SaaS) features and functions.
Each CAD workstation 220 includes one or more processors that are operative to execute one or more applications such as emergency response application 210. The workstation includes a display 221 operative to display one or more graphical user interfaces (GUIs). In the example of
The emergency response application 210 is operative to retrieve and display emergency data provided by the emergency data manager 100 and display the emergency data on the GUI 211 including a map view. The map view displays emergency data and provides location indicators showing the location of mobile devices from which emergency calls have emanated.
In accordance with the various embodiments, the GUI 211 may be implemented in various ways such as, for example, provided as a web browser interface, such as a cloud-based application interface (i.e. a software-as-a-service SaaS interface), or via a web browser plug-in, or may be associated with a stand-alone application running as executable instructions, executed by one or more processors on a CAD workstation 220, or other workstation, on which the GUI 211 is displayed, or by any other software implementation mechanism.
Emergency services personnel may receive appropriate emergency services information and view emergency data including the map view via the GUI 211, and may use the CAD software GUI 223 to place dispatch calls to emergency responders who receive the dispatch calls and emergency data on various emergency responder devices accordingly. Emergency responder devices may include, but are not limited to, desktop computers, laptop computers, tablets, mobile phones, smartphones, radios (i.e. walkie-talkies), in-vehicle computers, etc., all of which may be operative to display emergency data to the emergency responders. The devices may be operative to send emergency data requests to a respective emergency network and also authentication data.
Emergency calls are routed to the emergency network 200 by the ESInet ESRP or by legacy 911 selective routers to customer premises equipment CPE 206. That is, emergency calls coming in to the CPE 206 may be CAMA trunk line calls (i.e. legacy 911 calls 203) or IP based calls (i.e. E911/NG911 calls 202) or a combination of both depending on the emergency network 200 specific implementation. The CPE 206 may include collectively various network entities such as internal call routers, private branch exchange (PBX) and any needed gateways, such as a SIP gateway to convert SIP to trunked line or vice versa, to accommodate incoming E911, NG911 or legacy CAMA trunks. The CPE 206 with any such internal network entities is collectively considered an emergency network entity of the emergency network 200. The CPE 206 routes the incoming emergency calls to the call-handling workstations 205 and provides emergency call data from the emergency call data feed 201 according to the emergency network 200 internal call handling system. The calls may be provided to the call-handling workstations 205 as trunked calls or IP based calls accordingly, and data from the emergency call data feed 201 is delivered to call-handling software executing on the call-handling workstations 205.
For legacy 911 systems, the emergency call data feed 201 is an Automatic Number Identification and Automatic Location Identification (ANI/ALI) feed which provides caller-ID and location information to the call handling workstations 205. For E911 or NG911 IP based incoming emergency calls the emergency call data feed 201 may be an XML based data feed, an HTTP data feed, SIP data feed or other suitable data feed format. In some implementations, a device identifier is present in a SIP INVITE used to establish an emergency call, and the emergency network may use the SIP INVITE device identifier to send and ALI query.
Some emergency networks may lack some next generation emergency network capabilities as the emergency networks evolve and progress to add this capability. For mobile device calls, and calls placed by mobile applications such as “over-the-top” VoIP applications, the legacy ANI/ALI feed may not include location information or may have incorrect location information because the devices, the applications placing the call, or both, may not be in compliance with the requirements for E911 or NG911. For SIP calls, the call may be translated to trunked lines at various points during call routing at which point information from the SIP INVITE can be lost. Over-the-top VoIP applications may enable phone calls to an emergency network but may not comply with the requirements of an emergency call placed using the native dialer of the mobile phone or may fail in acquisition of a location object such as PIDF-LO. In other situations, wireless network outages or other network and power outages may prevent emergency calls from being routed to the emergency network from a wireless network experiencing outages. In some of these situations, the emergency data manager 100 may still receive emergency data from mobile devices even when emergency call routing to the emergency networks is disrupted because the emergency data is received by the emergency data manager 100 independently from the emergency call routing. The EDM portal GUI 211 may therefore display a map view with location indicators from mobile devices from which emergency calls have emanated even if the emergency calls were not able to be routed to the emergency network due to network outages or power outages, of if emergency call data is lost during routing of the emergency call.
In the example emergency network 200, as emergency calls come in through the CPE 206, they are routed to the call-handling workstations 205 and emergency response call takers answer the emergency calls. The call-handling workstations 205 may display information related to answered emergency calls such as any called ID and location data information supplied through the emergency call data feed 201 if available. The call taker may manually enter additional information related to the call in some situations. The information associated with the emergency call answered by the call taker at the call-handling workstations is then passed to one of the CAD workstations 220 such that emergency response personnel may be dispatched to the scene of the emergency. The EDM portal GUI 211 may be implemented on the call-handling workstations 205 in some emergency networks, so that the call takers may see the map view with the location indicator for the emergency call they are answering. Also, in some emergency network implementations, call-handling and CAD functions may be integrated in a single workstation.
In the example emergency network 200 shown in
The data in a CAD spill may include, but is not limited to, a device identifier, a type of emergency (i.e., fire, police, medical, etc.), severity, and location if location data is available from the emergency call data feed 201. The CAD spill data, including any location information that may have been provided in the emergency call data feed 201, may be displayed on a display 221 of an associated CAD workstation 220 via a CAD application which provides a CAD software GUI 223. As shown in
The emergency response application 210 executing on the CAD workstations 220 is operative to detect the CAD spill 207 received by a CAD workstation 220, and to use the relevant emergency call data feed 201 data within the CAD spill 207 data to send an emergency data query to the emergency data manager 100. The emergency response application 210 communicates with the emergency data manager 100 through data connections 215 over which data may be sent and received via the Internet 190. The emergency data manager 100 may be a cloud-based software-as-a-service (SaaS software) resident on a server that may be accessed through the Internet 190. The emergency response application 210 may be implemented as a stand-alone emergency response application residing on each CAD workstation 220, or may be an emergency response application plug-in for an associated web browser (i.e. a web browser plug-in) for communicating with the emergency data manager 100 SaaS software. The emergency data manager 100 may provide the emergency response application 210 as a cloud-based SaaS software application that may be accessed on any of the emergency network workstations using a web browser.
In other words, in some embodiments, the emergency response application 210 may be resident on the emergency data manager 100 and accessed via a web browser as an SaaS application, or may be implemented as a standalone emergency response application that communicates with the emergency data manager 100, or as a Web browser plug-in, any of which may provide the EDM portal GUI 211 enabling communication with the emergency data manager 100. In the Web browser plug-in implementation, a Web browser executing on the CAD workstation 220 communicates with the emergency data manager 100 and provides the GUI 211. In any implementation, communication is established between an emergency network entity, such as a workstation, and the emergency data manager 100 using an IP protocol stack and a network connection which may be a TCP connection and which may include one or more WebSocket connections. The connections may include cryptographic protocols such as TLS (Transport Layer Security) as well as other encryption and security measures.
The emergency response application 210 detects the addressed CAD spill 207 and uses the CAD spill 207 data via the emergency data manager 100 over the data connection 215 to determine if emergency data is available for mobile device identifiers in the emergency call data feed 201 data. In some implementations, this is accomplished by sending an emergency data query to the emergency data manager 100 where the emergency data query contains at least one mobile device identifier from the emergency call data feed 201 data.
The emergency data query may include the device identifier, any location data that may have been received through the emergency call data feed 201, and any other information such as emergency type, emergency severity, etc. The emergency data manager 100 is operative to receive device 160 location data, and other emergency data, from the various databases 120 which may include for example, but are not limited to, Android Mobile Location (AML) databases, Android Emergency Location Service (ELS) databases, and Hybridized Emergency Location (HELO) databases provided by iOS™ devices, and other mobile device location databases, etc. The emergency data manager 100 uses the data from the emergency call data feed 201 to identify emergency data associated with device identifiers and can match up data from the emergency call data feed 201 with other available emergency data to provide more complete and accurate information to the emergency networks. The match up of emergency call data feed 201 with data received by the emergency data manager 100 enable identification of emergency calls that have been routed to the emergency network 200. However, the emergency data manager 100 information is not limited to emergency calls that have been routed to the emergency network 200. The emergency data manager 100 is operative to provide an emergency call queue and a map view showing location indicators for devices from which emergency calls have emanated independently from the emergency call routing. In other words, the EDM portal GUI 211 can display an emergency call queue along with a map view having location indicators for all mobile devices from which emergency calls have emanated, i.e. from which emergency calls were made, that are within the emergency call routing area for the specific emergency network.
This capability may be implemented in various ways. In one example implementation, the emergency data manager 100 pushes all emergency data it receives to the emergency network to which the emergency data pertains. Each workstation, whether call-handling, CAD, etc., that displays the EDM portal GUI 211 will display an emergency call queue showing entries for all of the mobile devices whether nor not the emergency call was received and answered at the emergency network. Referring to
The initial emergency call queue may be displayed in a distinct color or font style such that the emergency network operators understand that the queue is for calls not yet received. As the emergency response application 210 detects emergency calls arriving at the emergency network CPE 206 by monitoring the addressed CAD spills 207, the emergency response application 210 can either change the distinct color or font style for queue entries related to calls that have been received by the emergency network 200 and make the change appear on the EDM portal GUI 211, and/or can change the appearance of queue entries based on the addressed CAD spill 207 at a specific CAD workstation 220 such that the EDM portal GUI 211 is individualized for emergency calls being handled at the specific CAD workstation 220. In another implementation, the emergency response application 210 can create a separate emergency call queue on the EDM portal GUI 211 that is specific to the workstation on which it is displayed. The specific emergency call queue can display, for example, only emergency call related to device identifiers received by the specific workstation in the addressed CAD spill 207.
The emergency response application 210 may send data from the emergency call data feed 201 to the emergency data manager 100 in a streaming manner, or as a data push operation, as the data is obtained from either the emergency call data feed 201 directly or from addressed CAD spill 207 data.
In response to receiving data from the emergency call data feed 201 whether sent in a data stream, as a push operation, or as an emergency data query sent by the emergency response application 210, the emergency data manager 100 provides, or returns in response to a query, emergency data which includes, but is not limited to, augmented device location information and other additional data. The emergency response application 210 receives augmented device location data and any other emergency data as additional data from the emergency data manager 100 and displays the emergency data in the EDM portal GUI 211 which may be displayed on a display of a CAD workstation 220. Augmented device location information in EDM portal GUI 211 may be shown on the same display 221 with unaltered device location information supplied by the emergency call data feed 201 in the CAD software GUI 223. A determination may be made of a location of the device based on a difference between the augmented device location and the unaltered device location information. In some implementations the emergency response application 210 is operative to receive and display a URL with the augmented device location information. The URL may be displayed within the CAD software GUI 223 or within the EDM portal GUI 211. The EDM portal GUI 211 may provide an emergency call queue, along with a map view, that provides URLs that may be selected (i.e. clicked) to open a web tab or new web page with further information stemming from the emergency data.
The processor 310 may be implemented as one or more microprocessors, ASICs, FPGAs, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or devices that manipulate signals based on operational instructions. Among other capabilities, the processor 310 is configured and operative to fetch and execute computer-readable instructions (i.e. executable instructions) stored in the memory 330. For example, the operating system 331 executable instructions, when executed by the at least one processor 310, may provide a kernel 351, libraries 353 (i.e. application programming interfaces or “APIs”), an application layer 350 or “user space” within which the various applications are executed, and an IP protocol stack 355. The applications 332 executable instructions, when executed by the at least one processor 310, enable data retrieval and data ingestion operations, a LIS 371, an ADR server 373 a geofence module 375, a mapping module 377, and one or more emergency network managers 379. Emergency network profiles 335, stored in memory 330, may be accessed by the various modules and the emergency network managers 379 to access information needed to communicate with various emergency networks. The emergency network managers 379 communicate with the other modules of application 370 via a set of APIs 378. The processor 310 may further execute a set of application agents 357 which facilitate communication between the IP protocol stack 355 and the application 370 via various APIs 358. The application agents 357 are operative to, among other things, provide API communication between the various applications 332 and the kernel 351.
The emergency data manager 100 may be implemented as a cloud server. The term “cloud server” as used herein, refers to a server, accessible by an Internet connection, that is operative to host one or more applications that may be accessed by a computing device using a web browser or an application resident on the computing device. One type of computing device that may access the applications is an emergency network entity such as, but not limited to, a workstation. The emergency data manager 100 is operative to provide a cloud-based application such as a software-as-a-service (SaaS) application accessible remotely using a computer or workstation connected to the Internet and operatively coupled to the emergency data manager 100. The emergency data manager 100 may be implemented as SaaS software executed using a platform-as-a-service (PaaS) that enables development and execution of cloud-based applications. Some or all of the emergency data manager 100 functions may be distributed functions that are distributed on multiple servers in order to increase availability and redundancy in the SaaS environment.
All of the components of the emergency data manager 100 are operatively coupled by an internal communication bus 301. As used herein, components may be “operatively coupled” when information can be sent between two such components, even though there may be one or more intermediate or intervening components between, or along the connection path. Therefore, any of the various components with the emergency data manager 100, and in other example network entities and devices described herein, may be understood herein to be operatively coupled to each other where appropriate, and to be executing on one or more processors that are further operatively coupled to a memory that stores executable instructions (also referred to as “software code” or “code”) for implementing the various components. Operative coupling may also exist between engines, system interfaces or components implemented as software or firmware executing on a processor and such “software coupling” may be implemented using libraries (i.e. application programming interfaces (APIs)) or other software interfacing techniques as appropriate. Such libraries or APIs provide operative coupling between various software implemented components of
All of the servers, components and modules described herein may be implemented as software or firmware (or as a combination of software and firmware) executing on one or more processors, and may also include, or may be implemented independently, using hardware such as, but not limited to, ASICs (application specific integrated circuits), DSPs (digital signal processors), hardwired circuitry (logic circuitry), or combinations thereof. That is, any of the components or modules disclosed herein may be implemented using an ASIC, DSP, FPGA executable instructions executing on a processor, logic circuitry, or combinations thereof. In other words, the components and modules may be implemented as hardware, software or by combinations thereof. Therefore, each of the servers, components and modules disclosed herein may be considered a type of apparatus that may be implemented and operate independently from the other components in the system. For example, any one of the LIS 371, ADR server 373, geofence module 375, mapping module 377, or emergency network managers 379 may be implemented using an ASIC, DSP, FPGA, executable instructions executing on a processor, logic circuitry, or combinations thereof.
The various embodiments also include computer readable memory that may contain executable instructions, for execution by at least one processor, that when executed, cause the at least one processor to operate in accordance with the emergency data manager 100 and other functionality herein described. The computer readable memory may be any suitable non-volatile, non-transitory, memory such as, but not limited to, solid-state storage (SSS), programmable chips such as EEPROMS, flash ROM (thumb drives), compact discs (CDs) digital video disks (DVDs), optical drives, etc., that may be used to load executable instructions or program code to other processing devices or electronic devices such as those that may benefit from the features and methods of operation herein described. The executable instructions may also include the various operating system environments and the kernel. For example, the memory 330, which is a non-volatile, non-transitory memory, may store executable instructions for execution by the at least one processor 310 that when executed, provide the LIS 371, ADR server 373, geofence module 375, mapping module 377, or emergency network managers 379.
In some implementations, the emergency data manager 100 is operatively coupled to a geofence database 101 which stores jurisdictional boundary data for various emergency networks 170 as well as for the national or regional emergency networks. The emergency data manager 100 is operative to store and retrieve emergency data from the various databases 120, and may function as an interface between emergency networks, the various databases 120 and devices 160 to receive and store emergency data. The stored emergency data can be transmitted or distributed to emergency networks and emergency responder devices before, during, or after emergencies. The emergency data manager 100 may receive emergency data from any of the devices 160 and such data may include, but is not limited to, locations, medical history, personal information, or contact information.
The emergency data manager 100 is operative to perform operations that include data ingestion and data retrieval. The emergency data manager 100 is operative to perform data ingestion by communication with the various databases 120 to obtain emergency data. The LIS 371 can perform location ingestion and supports interfaces operative to post or receive emergency locations. The LIS 371 may perform location ingestion using a REST API that is operative to receive an HTTP POST including location data when an emergency alert 105 is generated or when an emergency call 103 is received from a device 160 or from another server or database to which a device 160 has sent its location information. The location data may include a location generated concurrently or in response to the generation of the emergency alert 105, which may initiate an emergency call 103 or emergency session for requesting emergency assistance. This generated location data may be, for example, location data from a device 160 GPS chipset, such as GPS coordinates, or mobile device generated location data that is calculated by algorithms operating on the mobile device such as, but not limited to, triangulation. This data may also include data from a device 160 inertial-measurement-unit (IMU). The location data may be generated before an emergency alert 105 such as, for example, when a medical bracelet IMU detects that a patient has fallen. In another example, when an emergency call 103 is made from a device 160, the LIS 371 may receive a location recently generated by the device 160 GPS chipset, or by a device 160 triangulation algorithm, or other device 160 location mechanism, thereby ensuring that a location for the emergency is available as quickly as possible. The location data may include a device-based hybrid location generated by a device 160 which has sent an emergency alert 105 where the hybrid location data includes GPS data or is a combination of location determinations using one or more algorithms or one or more algorithms plus GPS data. A GPS chipset within the device 160 may generate the location data. The location data may also include a location data generated by a second device 160 that is communicatively coupled to the device 160 that sent the emergency alert 105. For example, a wearable device such as a medical bracelet or smartwatch, that does not include location capabilities, may use the location services location from a mobile phone with which it is paired. The LIS 371 may communicate with a device 160 via a mobile application installed on the device 160 or via firmware or an operating system of the device 160.
The location data generated by a device 160 prior to an emergency occurrence may be accessible by an authorized one (based on device 160 location) of the emergency networks 170 during an emergency. For example, a taxi company may have software that transmits the location of its cars or assets to the emergency data manager 100, or another server, preemptively. Thus, when an emergency arises, the location of the affected taxi can be made accessible quickly to send for help. Further, location data generated by a device 160 after an emergency has commenced may be made accessible to one of the emergency networks 170 during the on-going emergency. For example, updated location data of a hijacked taxi may be periodically transmitted to the emergency data manager 100 and made accessible to one or more of the emergency networks 170.
The ADR server 373 may provide an interface for posting or receiving static or dynamic emergency profile data. Such additional data may include, but is not limited to, medical data, personal data, demographic data, and health data, which may be obtained from the various databases 120. For example, medical data may include information relating to a person's medical history, such as medications the person is currently taking, past surgeries or preexisting conditions. Personal data may include a person's name, date of birth, height, weight, occupation, addresses such as home address and work address, spoken languages, etc. Demographic data may include a person's gender, ethnicity, age, etc. Health data may include information such as a person's blood type or biometrics such as heart rate, blood pressure or temperature. Additional data may further include data received from connected devices such as vehicles, IoT devices 113, and wearable devices such as medical bracelet 109, smartwatch 111 or other devices, etc. For example, intelligent vehicle systems may generate and send data regarding a crash, such as the speed at which the vehicle was moving just before the collision, where the vehicle was struck, the number of occupants, etc. The ADR server 373 interfaces may be implemented in whole or in part using a REST API, for example using JSON (JavaScript Object Notation).
In one example of operation, if an emergency call 103 is made from a mobile phone, or if an emergency alert 105 is sent, the mobile phone may receive a heart rate of the person who made the emergency call from a smartwatch 111 worn by the person and communicatively coupled to the cell phone via a Wi-Fi™ or Bluetooth™ connection or some other wireless connection. The mobile phone may therefore send the heart rate to the data ADR server 373, along with any other additional data, in an HTTP POST. The ADR server 373 may communicate with a device 160 via a mobile application installed on the device 160 or integrated into the firmware or operating system of the device 160. Additional data may also be sent to the ADR server 373 from a network server. The ADR server 373 may be accessed by any connected platform that receives data that might be relevant in an emergency. Connected platforms, such as the various databases 120, may therefore send additional data to the ADR server 373 at any time. A website, web application, or mobile application may communicate with the ADR server 373 and may allow device 160 users to create profiles to send additional data included in the profiles to the ADR server 373 every time a profile is created or updated.
The ADR server 373 may also include a multimedia ingestion module to provide an interface for posting or receiving data such as audio or video streams obtained during an emergency from a device 160 that is proximal to the emergency. In one example of operation, if an emergency alert 105 is generated by an intelligent vehicle system installed in a vehicle in response to the vehicle experiencing a collision, the emergency alert 105 is sent to one of the emergency networks 170 by the intelligent vehicle system or by another device 160 communicatively coupled to the intelligent vehicle system, such as a mobile phone coupled to the intelligent vehicle system via Bluetooth™. In response to generating the emergency alert 105, the intelligent vehicle system may additionally begin streaming audio and video from microphones and cameras installed inside or outside of the vehicle to the emergency data manager 100 through the ADR server 373. A mobile phone communicatively coupled to the intelligent vehicle system may additionally or alternatively stream audio or video from microphones and cameras integrated into the mobile phone to the emergency data manager 100 through the ADR server 373. One or more of the ADR server 373 multimedia ingestion modules or interfaces may be implemented wholly or partly using REST APIs that are accessed with an HTTP POST. Other ADR server 373 interfaces may include H.323 or some equivalent thereof.
After receiving the relevant data, the ADR server 373 can store the data in one or more databases operatively coupled to the emergency data manager 100 such as database 150. The emergency data manager 100 may be operatively coupled to databases such as, but not limited to, a location database, the geofence database 101, database 150, etc. The emergency data manager 100 databases may also be operatively coupled to, or otherwise accessible by, one of the emergency networks 170. The ADR server 373 is operative to tag or otherwise associate received data with an identifier of a user or specific device 160 associated with the data. For example, the ADR server 373 may tag received data with a user ID number, an email address, or a phone number (i.e. caller ID), a MAC address, or other device or user identification information, etc. The ADR server 373 may also tag received data based on the data source using, for example, a device name or type, an application name, user name, phone number, corporate account, or etc.
An individual or group of individuals may be associated with multiple identifiers. In an example of operation, if the LIS 371 receives a location generated by a phone associated with the phone number +1-555-555-5555, associated with John Doe, the data ADR server 373 may also receive a heart rate from a smartwatch associated with the email address jobndoe@email.com, which is an identifier that is also associated with John Doe. In this example, the LIS 371 tags the location with the phone number “+1-555-555-5555,” and with the email address “johndoe@email.com,” and the ADR server 373 tags the heart rate with the same identifiers, thereby associating both the location and the heart rate with John Doe in the emergency data manager 100 databases.
Ingestion data that enters the emergency data manager 100 may include various data fields and associated data entries within the data fields. The emergency data manager 100 maintains a list of expected data fields so that the data entries can be entered within a specific data field.
The LIS 371 may support interfaces implemented wholly or partly via a JSON REST API that is operative to receive a query or request such as, but not limited to, an HTTP GET request, from the emergency networks 170 or an ESP device. The LIS 371 data retrieval interface may provide a single GET endpoint for retrieving either the latest or paginated list of locations for a specific caller ID. For example, a phone number associated with a device 160 from which a location was received may be included in a header, body, or metadata of a request sent to the LIS 371. The LIS 371 may then retrieve a location or set of locations from the emergency data manager 100 databases and deliver the location or set of locations to the relevant authorized emergency network 170 or to an ESP device associated with the authorized emergency network. The LIS 371 may include a NG911 standards-based XML API for the retrieval of location data from the emergency data manager 100 databases. The LIS 371 may be operative to accept HELD requests from the emergency networks 170 or from ESP devices and to return location data for a specific caller ID or anonymous reference.
The ADR server 373 may include a data retrieval interface implemented as a JSON REST API for the retrieval of emergency or additional data. Additional data may include, but is not limited to, medical data, personal data, demographic data, health data or other data which may be protected data. Additional data may also include data received from connected devices 160 such as, but not limited to, vehicles, IoT devices, and wearable devices. The ADR server 373 may be operative to receive a query or request, such as an HTTP GET request, from an emergency network 170 or ESP device. The ADR server 373 may then, in response to a request, retrieve additional data associated with a specific or particular identifier of a user or a device 160 associated with the user, such as a phone number, and return the data to the emergency network 170 or ESP device.
The emergency data manager 100 determines which of the emergency networks 170 and associated ESP devices have authorization to receive particular types of emergency data. For example, a given emergency network or ESP device may, in certain circumstances, be granted access only to a particular subset of emergency data. For example, a police officer may only be given access to the location emergency data, while an EMT (emergency medical technician) may only be given access to an additional data emergency data. However, a given emergency network such as a national or regional emergency network, or associated ESP device, may be given differential access to the entirety of the emergency data, or to particular emergency data categories within the databases based on any factor or set of factors. A management portal may be provided by the emergency network managers 379 to determine which emergency data categories are returned from one of the emergency networks 170 to a particular emergency network or ESP device. Other data services corresponding to the various databases 120 may also be coordinated with respect to granting access to protected data. The emergency network profiles 335 stored in memory 330 may contain these settings related to release of data. The emergency network managers 379 also provide authentication and login capabilities for the various emergency networks and enable APIs 378 for communication between the emergency network entities and the LIS 371, ADR server 373, geofence module 375, and mapping module 377.
During an emergency, the emergency data manager 100 is operative to detect the emergency and/or otherwise identify the need to provide emergency data pertaining to the emergency. In response to detecting an emergency, the emergency data manager 100 is operative to identify any emergency data pertaining to the emergency stored within the databases 120, retrieve and transmit the pertinent emergency data to the appropriate emergency network 170. The emergency data manager 100 may act as a data pipeline that automatically pushes emergency data to emergency networks 170 that would otherwise be without access to emergency data that is critical to most effectively and efficiently respond to an emergency. Location data stored within, and/or obtained and provided by, the emergency data manager 100, enables emergency responders to arrive at the scene of an emergency faster, and the additional emergency data stored within, and/or obtained and provided by, the emergency data manager 100 enables emergency responders to be better prepared for the emergencies they face.
The emergency data manager 100 is operative to provide a cloud-based application to multiple emergency networks 170 by establishing network connections via the IP protocol stack 355, with various emergency network entities such as a call-handling workstation, CAD workstation etc. Other examples of emergency network entities include, but are not limited to, customer premises equipment (CPE) (private branch exchanges, SIP gateways, etc.), servers, desktop computers, laptops, routers, switches, etc. that are operative to send and receive data. The network connections may be transport control protocol (TCP) connections and may utilize WebSocket connections between the emergency data manager 100 and an emergency network entity.
In some implementations, a geofence module 375 is present and is operative to determine emergency network jurisdictional boundaries and to show the jurisdictional boundaries on a graphical user interface as a jurisdictional map view within the EDM portal GUI 211. The mapping module 377 is operative to generate the map view and to also post emergency data locations as location indicators on the map view. The mapping module 377 is operative to generate a map view with or without the geofence module 375. For example, the map view may be generated using location data based on emergency call locations for mobile device identifiers received by the LIS 371. When geofence data is available for a given emergency network, the geofence module 375 will provide the emergency network jurisdictional boundary to the mapping module 377 to further enhance the map view displayed. In that case, emergency data may be provided only to emergency networks when the location data is within the jurisdictional boundary of the specific emergency network. The map view is operative to provide and display location indicators that show the location of incoming emergency calls that the emergency network has not yet received, has received, or is in the process of receiving. The not yet received calls can be displayed based on location information received by the LIS 371 because the location data is received prior to completion of emergency call routing to the emergency network.
Emergency networks and their corresponding emergency network entities are associated with a given geographic boundary. Based on the geographic boundary for a respective emergency network, a jurisdictional map view customized for the respective emergency network may be generated and provided to emergency network entities such as workstations for display. Within the jurisdictional map view for the emergency network, location indicators for emergencies occurring within its geographic boundary may be displayed. The jurisdictional map view for a given emergency network may include one or more geofences associated with the respective emergency network and surrounding areas.
In an example of emergency data manager 100 operation, an emergency alert may be triggered by a given device 160, for example by a user pressing a soft button, a physical button, initiating a voice command, or gesture, or autonomously based on sensor data such as from a smoke alarm. In this example, the user may be prompted to confirm the emergency or otherwise provide authorization for sending the emergency alert. Emergency data, such as an enhanced location and additional data regarding the user, such as the user's medical history, may then be delivered by the device 160 to the emergency data manager 100 and stored in a database. The emergency data manager 100 may format the emergency data into a format that is compatible with industry standards for storing and sharing emergency data. For example, the emergency data may be formatted to be compatible with National Emergency Number Association (NENA) standards. The emergency data manager 100 may perform a push operation to push the emergency data to an emergency network entity. After the push operation, the emergency data manager 100 may delete any temporarily stored data if required for compliance with privacy laws, regulations and policies.
An emergency network 170, such as by a PSAP responding to an emergency alert, may obtain emergency data by sending a query to the emergency data manager 100. The query may be an emergency data request using, for example, an HTTP GET request. The emergency data request may also be in the form required by the Location Information Server (LIS) protocol and/or a protocol required by the ADR server 373. In response to the emergency data request, the emergency data manager 100 sends an appropriate response including relevant emergency data to the requesting party via an encrypted pathway. The emergency data request may be in the form of an HTTP-Enabled Location Delivery (HELD) and the response from the emergency data manager 100 may be in the form of a Presence Information Data Format Location Object (PIDF-LO) as defined by the Internet Engineering Task Force (IETF).
The emergency data request includes an authorization code, also referred to as an “authorization token”, in the body, header, or metadata of the request, and the emergency data manager 100 checks that the authorization code is active before providing a response to the requesting party. Authorization may be provided in the “Authorization” header of the emergency data request using HTTP Basic Authentication. For example, authorization may be a base64-encoded user name and password for an account associated with the requesting party. Emergency data requests are sent over public networks using API access keys or credentials. Transport Layer Security (TLS) may be used in the requests and responses from the emergency data manager 100 for encryption security.
The processor 410 may be implemented as one or more microprocessors, DSPs, ASICs, FPGAs, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or devices that manipulate signals based on operational instructions. Among other capabilities, the processor 410 is configured and operative to fetch and execute computer-readable instructions (i.e. executable instructions) stored in the memory 430. For example, the applications 432 executable instructions, when executed by the at least one processor 410, may provide an operating system, a dialer application 455, a short-message-service (SMS) application 456, an instant message (IM) application 457, a web browser 460, an email client 458 and one or more instant message (IM) and voice applications which may each provide IM and voice call capability separately or in combination. The operating system may include a kernel 451, libraries 452 (also referred to as “application programming interfaces” or APIs) and an application layer 450 or user space within which the various applications are executed, and an IP protocol stack 453. Application agents 470 may be present to provide connectivity and interoperability via various APIs 474 between various applications and the CAD application 480 and the emergency response application 400. The emergency response application 400 may communicate with the application agents 470 via an API 472 and the CAD application 480 may communicate with the application agents 470 via an API 471. An API 473 may facilitate communication between the CAD application 480 and the emergency response application 400 and enable data exchanges to the user interfaces, access to emergency call data, etc.
In the example workstation 220 of
The emergency response application 400 provides the GUI 211 on the workstation display 403, and displays augmented emergency data such as, but not limited to, augmented location data received from the emergency data manager 100. Communication is established between the emergency response application 400 and the emergency data manager 100 using the IP protocol stack 453 and a network connection is established which may be a TCP connection and which may include one or more WebSocket connections.
The emergency response logic 600 is operatively coupled to the CPE 206 and to the emergency data manager 100 and is operative to receive the emergency call data feed 201, and to split the emergency call data feed 201 into two legs; one feed leg 601 is provided to the CPE 206 internal call routing, and a second feed leg 603 is provided to the emergency data manager 100. The second feed leg 603 is sent over an IP connection between the emergency response logic 600 and the emergency data manager 100. The emergency response logic 600 is operative to receive augmented emergency data such as, but not limited to augmented location data, from the emergency data manager 100 in response to sending the second feed leg 603.
The emergency response logic 600 may also facilitate data pushes from the emergency data manager 100 to the emergency network internal network 230 such that an emergency call queue and/or emergency alert queue can be displayed on each of the workstations within the EDM portal GUI 211. The emergency response logic 600 may use the emergency call data feed 201 to determine the emergency calls from the emergency call queue that have actual been received at the CPE 206 and to change the queue entry color, font style, or create a second emergency call queue, etc., to distinguish emergency calls that are not yet routed or received from emergency calls that have arrived at the CPE 206 and/or answered by operators of the call-handling workstations 205. The emergency response logic 600 may also monitor addressed CAD spill 207 and customize the EDM portal GUI 211 on each CAD workstation 220 according to the call identifiers sent to it in its respective addressed CAD spill 207. Put another way, the emergency response logic 600 can customize the EDM portal GUI 211 on each CAD workstation 220 to show specific information that that particular CAD workstation 220 needs related to emergency calls its operator is handling.
In various implementations, the emergency data manager 100 uses device identifiers contained in the feed leg 603 and sends back augmented emergency data such as augmented location data. For example, the emergency data manager 100 LIS server receives location data from each of the devices 160 when any one of them initiates an emergency session with the emergency network 650. The emergency data manager 100 is operative to associate the received location data with the device identifiers in the second feed leg 603 and accordingly return augmented location data, as well as other emergency data that may be available related to the device identifier via the ADR server. The emergency response logic 600 receives and provides the augmented emergency data, including augmented location data 605, to the CAD workstations 220. In the example emergency network 650, each CAD workstation 220 receives all augmented data. The emergency data manager 100 obtains the emergency data independently from the emergency network 650 and therefore independently from the emergency call routing to the emergency network 650. The emergency data manager 100 may receive emergency data from mobile devices prior to completion of call routing to the emergency network. In other words, the emergency data manager 100 may receive emergency data related to in-progress mobile device emergency calls before those emergency calls are received and answered by the emergency network call-handling systems.
In another implementation, the emergency response application 210, which executes on each of the CAD workstations 220, may be operative to receive the augmented emergency data in addition to an addressed CAD spill 207 data received from the call-handling workstations 205, and determine which augmented data to display on the EDM portal GUI 211 based on the CAD spill 207 data received at the specific workstation. For example, the emergency response application 210 may determine what augmented emergency data to display on the EDM portal GUI 211, by comparing device identifiers in a respective addressed CAD spill 207 to the augmented emergency data device identifiers received from the emergency response logic 600. For example, CAD workstation #1 may receive the addressed CAD spill 207 from call-handling workstation #1 as shown in
In some implementations the augmented emergency data 605 may include, or may be provided via, a Uniform Resource Locator (URL) that may be provided as either a plain text URL or as a selectable web link, such as a Hypertext Transfer Protocol (HTTP) link. The URL may be inserted into the emergency call data feed 201 which is displayed on CAD software GUI 223, or displayed in the EDM portal GUI 211 or in both locations. The URL may be text only and not selectable, depending upon the implementation of the emergency call data feed 201 field displayed on the CAD software GUI 223.
In legacy systems using ANI/ALI as the emergency call data feed 201, the information elements sent over the network as well as data fields in the CAD software may provide for a limited number of text characters, such as 511 characters, and there may likewise be a limitation within an ANI/ALI display field within the CAD software GUI 223. In such cases, the URL may be shortened using a URL shortener service such that a reduced number of text characters is needed to display the URL. Because emergency response logic 600 adds the augmented emergency data 605 into the emergency call data feed 201 leg which is sent in the normal emergency network internal network 230 the CAD software receives it as it would normally receive the emergency call data feed 201 and displays it accordingly.
In some implementations the emergency call data feed 201 may support an XML ALI Query Service (AQS) and use an XML-based protocol that delivers XML ALI as a data stream that provides 2124 bytes that includes the legacy ALI data characters as well as characters required for XML tags and other XML data elements etc.
The CAD workstation 220 user may have several options to access the augmented emergency data 605 using the URL, or shortened URL as applicable. In one implementation, if the CAD software GUI 223 allows for display of HTTP links, the use may select the HTTP link which may then open another window or tab within the EDM portal GUI 211 via a default web browser. If the URL is displayed as plain text, the user may perform a copy and paste operation of the URL, copying from the CAD software GUI 223 display field and pasting it into the address field of another web browser page or tab, or may type in the URL manually.
Navigating to the URL by any of the above-described options will provide a web page that includes a display of the augmented emergency data 605. Because the URL enables a webpage, the augmented emergency data 605 is not limited to location data as would be the case with the character limitation of the ANI/ALI display field within the CAD software GUI 223. The web page can provide and display augmented emergency data 605 including for example, but not limited to, device-based location, sensor based location, location coordinates, WiFi™ access points, 5G access points, GPS coordinates, cell tower triangulation, barometric pressure, radio frequency signals, real-time sensor data, demographic data, pre-existing health information, emergency contacts, multimedia, social media information, weather data, environmental data, etc. The additional information may pertain to an individual emergency call or to a large-scale emergency event.
The URL is generated by the emergency data manager 100, and may be inserted into the emergency call data feed 201 by emergency response logic 600. Alternatively, the URL may be generated by the emergency response logic 600. The URL may be in any of various formats and may, for example, include the name or phone number of the emergency network to which the web link will be provided (e.g., www.CollierCounty911.5153402225.org). The URL may alternatively, or additionally include the phone number of a person who has dialed an emergency number (e.g., 9-1-1) in which case the phone number may be included in the emergency call data feed 201. The additional information provided by the webpage specified by the URL may also provide photographs or a video feed which may be recorded video or a live stream video. For example, where a witness of a car accident calls 9-1-1 and concurrently begins recording a video of the car accident on their mobile phone, the emergency data manager 100 may obtain the video information from a database and include the video as part of the augmented emergency data 605 accessible via the URL. In some implementations, the URL may direct the webpage to a database server external from the emergency data manager 100 or the emergency network. Therefore, the URL may be controlled by security or privacy protocols that disable the URL after some predetermined period of time, disable after access is completed, or limit access of the URL or sharing of the URL by only certain authorized emergency network entities or by a specified limited number of authorized users.
In another example use case, the URL may provide a map such as a floor plan within a building and identify the location of the device that placed an emergency call. The EDM portal GUI 211 may enable the CAD workstation 220 operator to send a text message to an emergency responder at the emergency scene such that the emergency responder could use their mobile device to access the webpage specified by the URL. Alternatively, the URL could be sent to all emergency responders who may be available to respond to a dispatch request.
The processor 805 is operatively coupled to a non-volatile, non-transitory memory 806 which stores executable instructions, that when executed by the processor 805 implement an XML module 807, a SIP module 808 and a web services module 809. Each of these modules is operative to receive emergency call data feeds in various formats such as the legacy ANI/ALI feed, or XML or SIP information in NG911 systems.
The at least one processor 805 is operative to send an emergency data query to the emergency data manager 100 via an IP connection, and to receive back augmented emergency data including augmented location data and/or received pushed emergency data from the emergency data manager 100. The at least one processor 805 is further operative to communicate with the network interface within the network switch or splitter 801, to communicate with the CAD workstations 220 to provide the augmented emergency data and to address data to each of the CAD workstations 220 based on a CAD workstation address.
The processor 805 may be a system-on-a-chip and may include non-volatile, non-transitory memory to store firmware, software instructions or both. The processor may also be implemented as an ASIC, one or more FPGAs, DSP, etc. or some combination thereof.
In operation block 1003, the emergency data manager 100 detects emergency call data received at the emergency network. This is accomplished by monitoring of the emergency call data feed 172 that is received by a CPE of the emergency network. In legacy systems the emergency call data feed 172 is an ANI/ALI feed. In E911 and NG911 systems, the emergency call data feed 172 may be an XML ALI feed, a SIP header feed, an HTTP feed or some other type of feed that is IP-based and that may, or may not, use out-of-band signaling on trunk calls such as CAMA trunks, but that receives the emergency call data as IP-based data. The emergency call data feed 172 may be monitored and accessed by software executing on a network entity of the specific emergency network where the network entity software communicates with the emergency data manager 100 to send emergency call data feed 172 data. In other implementations, emergency response logic, which may be a hardware device, or a combination of hardware and software/firmware etc., is operative to intercept or monitor the emergency call data feed 172 at the emergency network and to send information to the emergency data manager 100 by IP-bases communication between the emergency response logic and the emergency data manager 100.
In operation block 1005, the emergency data manager 100 provides a map view to an emergency network entity of the emergency network using the emergency data, that displays location indicators corresponding to locations of mobile devices identified by the emergency call data received at the emergency network. In this example, the map view may be customized to distinguish between emergency calls places by mobile devices but not yet received by the emergency network, and emergency calls that have been routed or routed and answered by a call taker at the emergency network. A call queue may have different style entries to distinguish there and may use font color, font size, font style, entry highlighting, color markers, blinking/flashing, or any other visually appearing differentiator that may be displayed, etc. In other implementations a first emergency call queue may show emergency calls that have already arrived at the emergency network and a second emergency call queue may show emergency calls that have been placed by mobile devices that have not yet completed call routing or that have not yet been answered at the emergency network. A call “not answered” means that a telephone line at the emergency network is ringing but the call taker responsible for that emergency call has not yet answered it, but for example picking up a phone in a traditional system or otherwise pressing an answer call button on a software based phone system, etc.
In one implementation, the emergency call data feed 172 may be monitored on the emergency network by a software application running on an emergency network entity such as a call-handling workstation, a CAD workstation, a combined call-handling and CAD workstation, etc. In other implementations the emergency call data feed 172 may be monitored using emergency response logic in accordance with the examples shown in
In some implementations that use the emergency response logic, the emergency response logic may perform one or more operations depending on specific implementations. One operation of the emergency response logic is to obtain emergency call data from the emergency call data feed 172 or from the emergency network itself by, for example, obtaining the emergency call data from a CAD spill. Another operation of the emergency response logic is to query the emergency data manager 100 using the emergency call data. Yet another operation of the emergency response logic, in some implementations, is to aid in customization of emergency network entity map displays and emergency call queues by identifying and distinguishing on the map display and the emergency call queue, calls that have not yet been received or answered by the emergency network versus emergency calls that were placed, and for which the emergency data manager 100 was able to provide advance knowledge emergency data that can be displayed in the emergency call queue and on the map display. The emergency response logic may also send augmented data to the CAD software by appropriate APIs such that the CAD software can display the augmented data within the appropriate emergency call data field.
Thus, in operation block 1103 the emergency response logic receives device identifiers from the emergency call data feed 172 and checks with the emergency data manager 100 for emergency data available that is related to some or all of the device identifiers. A URL is generated by either the emergency data manager 100 or the emergency response logic, and in operation block 1105 the URL is inserted by the emergency response logic into the emergency call data field that is provided to, and displayed by, an emergency network entity software application such as, but not limited to, a call-handling software application or a CAD software application. The emergency network entity software application displays the URL within the data field in which it would normally display such data. For example, in legacy systems in which a CAD software application would display ANI/ALI data, the emergency response logic injects the URL into the data on the emergency network and the CAD software application displays the URL within its ANI/ALI data field as it would normally display ANI/ALI data. The operator may click on the URL, or enter it into a web browser to access emergency data available from the emergency data manager 100. Thus, in operation block 1107, when the operation clicks the URL or enters it into a web browser, a web page user interface is provided in response that provides the emergency data from the emergency data manager 100.
The URL approach is particularly helpful in legacy 911 systems in which CAD software applications expect ALI data which is limited to a given number of characters. The emergency response logic may receive device identifiers from the ALI data received by the emergency network as discussed above. For example, the emergency call data feed 172 to an emergency network may be monitored, or CAD spill data transmitted from emergency call-handling workstations to CAD workstations may be monitored by the emergency response logic which receives the ALI data packets, extracts the device identifiers contained in the ALI data packets and sends a query to the emergency data manager using the device identifiers. In cases where the CAD software application permits insertion of active HTTP links, the URL will appear as an HTTP link in the ALI data field, and the CAD workstation operator may then select the HTTP link using the workstation mouse. Otherwise, the CAD workstation operator must cut and past the URL into a web browser.
In operation block 1205, emergency data related to device identifier is obtained. In operation block 1207, a CAD workstation address is identified from the CAD spill, and in operation block 1209 the obtained emergency data is provided to the identified CAD workstation. The method of operation then terminates as shown. This process may also be used to customize the CAD workstation's EDM portal GUI 211 as discussed above with respect to other examples.
However, if it is determined that no multimedia data is available in decision block 1309, then the method of operation proceeds to operation block 1313 and the CAD workstation is provided only with available non-multimedia emergency data related to device identifier. The method of operation then terminates as shown.
The webpages presented to the CAD workstation operators may be a floorplan map, a video, photographs, or any other data related to an emergency call made by a mobile device. The emergency response logic operative at the emergency network may be implemented as hardware or as a software component. The webpages may also be displayed on an emergency call-handling workstation or on some other emergency network workstation instead of, or in addition to a CAD workstation.
An example of emergency data sent by the emergency data manager 100 and displayed on the EDM portal GUI 211 is shown in
In the
The map view and emergency call queue may be customized for the specific workstation on which it is displayed using the emergency call data feed 172 such that the call queue displayed on an emergency network entity display corresponds to the emergency call being handled at that workstation, i.e. at that specific emergency network entity. In the examples provided previously, the emergency network may be configured such that a CAD workstation only displays the emergency calls related to device identifiers it has received in an addressed CAD spill. In other configurations, each CAD workstation may display all emergency calls coming in to the emergency network, and the CAD workstation operator may select the specific emergency calls of interest, i.e. the ones that are being handled by the specific CAD workstation operator. Thus, for example, the first emergency call queue 2005 may show all emergency calls that have been placed for which the emergency data manager 100 has received emergency data, even though these emergency call have not yet been routed to the emergency network (i.e. the emergency network has not yet received the emergency call). The second emergency call queue 2020 may be configured to show emergency calls that have been received at the CPE of the emergency network. This is accomplished by the emergency response logic, or an emergency response application executing on a network entity, detecting device identifiers in the emergency call data feed 172 to the emergency network and comparing the list of identifiers with emergency data already received by the emergency data manager 100. Alternatively, the second emergency call queue 2020 may be configured to show only those emergency calls that the specific emergency network entity, such as a call-handling workstation or CAD workstation or combined call-handling and CAD workstation have answered or have been assigned via a CAD spill. In that case, the emergency call entries 2021 would pertain only to the specific workstation at which the operator is handling those calls.
The emergency data manager 100 receives emergency data from emergency call as they are placed by mobile device users, i.e. as the emergency calls emanate from the specific mobile devices and the emergency data includes, but is not limited to, mobile device location and associated device identifier. The emergency data manager 100 may also respond to specific queries for emergency data by searching/querying for a specific device identifier using data field 2001. After receiving an emergency data query including a device identifier, the emergency data manager 100 retrieves or gathers emergency data associated with the device identifier from one or more databases which may include one or more locations, and a current location. Location indicators are provided on the EDM portal GUI 211 to show the various locations. For example, the current location indicator 2015 shows the current location of the caller, and historic location indicator 2009 and historic location indicator 2013 show past locations as the caller has traveled. By moving the cursor over a historic location indicator 2009, emergency data 2007 is displayed in an overlay showing time, date, and the phone number (i.e. device identifier) of the caller's device. The call queue 2005 is also displayed and the operator may select any call from the call queue 2005 to display further information. The field 2003 shows that calls in the call queue 2005 are for a specific jurisdictional boundary 2010 which corresponds to a geofence and which is also displayed on the EDM portal GUI 211 which corresponds to the emergency network's emergency service zone. However, some implementations may not include the geofence information and in those implementations, a jurisdictional boundary line may not be displayed on the map view. The emergency data 2007 textual description of a current or historical location may include an indoor location, an amount of time elapsed since the current or historical location was received, and an amount of time elapsed since the current or historical location was generated.
While various embodiments have been illustrated and described, it is to be understood that the invention is not so limited. Numerous modifications, changes, variations, substitutions and equivalents will occur to those skilled in the art without departing from the scope of the present invention as defined by the appended claims.
The present application claims priority to U.S. Provisional Patent Application No. 63/148,581, filed Feb. 11, 2021, entitled “Apparatus and Method For Obtaining Emergency Data Related To Emergency Sessions”, and further claims priority to U.S. Provisional Patent Application No. 63/133,045, filed Dec. 31, 2020 entitled “Apparatus, Systems and Methods For Providing Alarm and Sensor Data To Emergency Networks,” both of which are assigned to the same assignee as the present application, and all of which are hereby incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5379337 | Castillo et al. | Jan 1995 | A |
| 5479482 | Grimes | Dec 1995 | A |
| 5563931 | Bishop et al. | Oct 1996 | A |
| 5596625 | Leblanc | Jan 1997 | A |
| 5710803 | Kowal et al. | Jan 1998 | A |
| 5742666 | Alpert | Apr 1998 | A |
| 6014555 | Tendler | Jan 2000 | A |
| 6133853 | Obradovich et al. | Oct 2000 | A |
| 6167255 | Kennedy et al. | Dec 2000 | A |
| 6249674 | Verdonk | Jun 2001 | B1 |
| 6252943 | Johnson et al. | Jun 2001 | B1 |
| 6256489 | Lighter et al. | Jul 2001 | B1 |
| 6262655 | Yoshioka et al. | Jul 2001 | B1 |
| 6292687 | Lowell et al. | Sep 2001 | B1 |
| 6363138 | Aprile | Mar 2002 | B1 |
| 6459782 | Bedrosian et al. | Oct 2002 | B1 |
| 6477362 | Raith et al. | Nov 2002 | B1 |
| 6502030 | Hilleary | Dec 2002 | B2 |
| 6510315 | Arnson | Jan 2003 | B1 |
| 6556816 | Gafrick et al. | Apr 2003 | B1 |
| 6571092 | Faccin et al. | May 2003 | B2 |
| 6574323 | Manuel et al. | Jun 2003 | B1 |
| 6587545 | Antonucci et al. | Jul 2003 | B1 |
| 6594666 | Biswas et al. | Jul 2003 | B1 |
| 6600812 | Gentillin et al. | Jul 2003 | B1 |
| 6628933 | Humes | Sep 2003 | B1 |
| 6680998 | Bell et al. | Jan 2004 | B1 |
| 6707421 | Drury et al. | Mar 2004 | B1 |
| 6731610 | Sajikawa et al. | May 2004 | B2 |
| 6993118 | Antonucci et al. | Jan 2006 | B2 |
| 7054611 | Eisner et al. | May 2006 | B2 |
| 7058385 | Lauper | Jun 2006 | B2 |
| 7177400 | Eisner et al. | Feb 2007 | B2 |
| 7224773 | Croak et al. | May 2007 | B2 |
| 7271704 | Mcsheffrey et al. | Sep 2007 | B2 |
| 7313402 | Rahman | Dec 2007 | B1 |
| 7324801 | Droste et al. | Jan 2008 | B2 |
| 7349706 | Kim et al. | Mar 2008 | B2 |
| 7409044 | Leduc | Aug 2008 | B2 |
| 7409428 | Brabec et al. | Aug 2008 | B1 |
| 7436938 | Savaglio et al. | Oct 2008 | B2 |
| 7437143 | Williams | Oct 2008 | B1 |
| 7469138 | Dayar et al. | Dec 2008 | B2 |
| 7483519 | Binning | Jan 2009 | B2 |
| 7519351 | Malone, III et al. | Apr 2009 | B2 |
| 7519372 | Macdonald et al. | Apr 2009 | B2 |
| 7548158 | Titus et al. | Jun 2009 | B2 |
| 7565131 | Rollender | Jul 2009 | B2 |
| 7646854 | Anderson | Jan 2010 | B2 |
| 7676215 | Chin et al. | Mar 2010 | B2 |
| 7684782 | Ashley, Jr. et al. | Mar 2010 | B2 |
| 7848733 | Bull et al. | Dec 2010 | B2 |
| 7937067 | Maier et al. | May 2011 | B2 |
| 7949326 | Gallagher et al. | May 2011 | B2 |
| 8009810 | Seidberg et al. | Aug 2011 | B2 |
| 8041335 | Khetawat et al. | Oct 2011 | B2 |
| 8041341 | Malackowski et al. | Oct 2011 | B1 |
| 8045954 | Barbeau et al. | Oct 2011 | B2 |
| 8068881 | Schrager | Nov 2011 | B2 |
| 8102972 | Poremba | Jan 2012 | B2 |
| 8126424 | Piett et al. | Feb 2012 | B2 |
| 8150367 | Malladi et al. | Apr 2012 | B1 |
| 8165560 | Stenquist | Apr 2012 | B2 |
| 8165562 | Piett et al. | Apr 2012 | B2 |
| 8185087 | Mitchell, Jr. et al. | May 2012 | B2 |
| 8195121 | Dunn et al. | Jun 2012 | B2 |
| 8219135 | De et al. | Jul 2012 | B2 |
| 8244205 | Wu | Aug 2012 | B2 |
| 8249546 | Shah et al. | Aug 2012 | B1 |
| 8249547 | Fellner | Aug 2012 | B1 |
| 8289953 | Ray et al. | Oct 2012 | B2 |
| 8306501 | Moodbidri et al. | Nov 2012 | B2 |
| 8326260 | Bradish et al. | Dec 2012 | B1 |
| 8369488 | Sennett et al. | Feb 2013 | B2 |
| 8396970 | Black et al. | Mar 2013 | B2 |
| 8401565 | Sandberg et al. | Mar 2013 | B2 |
| 8417090 | Fleming | Apr 2013 | B2 |
| 8417212 | Cepuran et al. | Apr 2013 | B2 |
| 8442481 | Maier et al. | May 2013 | B2 |
| 8442482 | Maier et al. | May 2013 | B2 |
| 8472973 | Lin et al. | Jun 2013 | B2 |
| 8484352 | Piett et al. | Jul 2013 | B2 |
| 8489062 | Ray et al. | Jul 2013 | B2 |
| 8494868 | Saalsaa | Jul 2013 | B2 |
| 8509729 | Shaw | Aug 2013 | B2 |
| 8516122 | Piett et al. | Aug 2013 | B2 |
| 8538370 | Ray et al. | Sep 2013 | B2 |
| 8538468 | Daly | Sep 2013 | B2 |
| 8588733 | Ferguson et al. | Nov 2013 | B2 |
| 8594015 | Dunn et al. | Nov 2013 | B2 |
| 8606218 | Ray et al. | Dec 2013 | B2 |
| 8625578 | Roy et al. | Jan 2014 | B2 |
| 8626112 | Ray et al. | Jan 2014 | B2 |
| 8630609 | Ray et al. | Jan 2014 | B2 |
| 8644301 | Tamhankar et al. | Feb 2014 | B2 |
| 8649806 | Cuff et al. | Feb 2014 | B2 |
| 8682279 | Rudolf et al. | Mar 2014 | B2 |
| 8682281 | Dunn et al. | Mar 2014 | B2 |
| 8682286 | Dickinson et al. | Mar 2014 | B2 |
| 8712366 | Greene et al. | Apr 2014 | B2 |
| 8747336 | Tran | Jun 2014 | B2 |
| 8751265 | Piett et al. | Jun 2014 | B2 |
| 8755767 | Maier et al. | Jun 2014 | B2 |
| 8760290 | Piett et al. | Jun 2014 | B2 |
| 8761721 | Li | Jun 2014 | B2 |
| 8792867 | Negahban et al. | Jul 2014 | B1 |
| 8811935 | Faccin et al. | Aug 2014 | B2 |
| 8825687 | Marceau et al. | Sep 2014 | B2 |
| 8848877 | Seidberg et al. | Sep 2014 | B2 |
| 8866606 | Will et al. | Oct 2014 | B1 |
| 8868028 | Kaltsukis | Oct 2014 | B1 |
| 8880021 | Hawkins | Nov 2014 | B2 |
| 8890685 | Sookman et al. | Nov 2014 | B1 |
| 8918075 | Maier et al. | Dec 2014 | B2 |
| 8948732 | Negahban et al. | Feb 2015 | B1 |
| 8971839 | Hong | Mar 2015 | B2 |
| 8983424 | Binning | Mar 2015 | B2 |
| 8984143 | Serra et al. | Mar 2015 | B2 |
| 9008078 | Kamdar et al. | Apr 2015 | B2 |
| 9014657 | Rohde et al. | Apr 2015 | B2 |
| 9019870 | Khan et al. | Apr 2015 | B2 |
| 9020462 | Hodgson et al. | Apr 2015 | B2 |
| 9071643 | Saito et al. | Jun 2015 | B2 |
| 9077676 | Price et al. | Jul 2015 | B2 |
| 9078092 | Piett et al. | Jul 2015 | B2 |
| 9094816 | Maier et al. | Jul 2015 | B2 |
| 9129219 | Robertson et al. | Sep 2015 | B1 |
| 9167379 | Hamilton et al. | Oct 2015 | B1 |
| 9244922 | Marceau et al. | Jan 2016 | B2 |
| 9258680 | Drucker | Feb 2016 | B2 |
| 9277389 | Saito et al. | Mar 2016 | B2 |
| 9351142 | Basore et al. | May 2016 | B2 |
| 9369847 | Borghei | Jun 2016 | B2 |
| 9384491 | Briggs et al. | Jul 2016 | B1 |
| 9402159 | Self et al. | Jul 2016 | B1 |
| 9408051 | Finney et al. | Aug 2016 | B2 |
| 9420099 | Krishnan et al. | Aug 2016 | B1 |
| 9426638 | Johnson | Aug 2016 | B1 |
| 9497585 | Cooley et al. | Nov 2016 | B1 |
| 9503876 | Saito et al. | Nov 2016 | B2 |
| 9544260 | Cuff et al. | Jan 2017 | B2 |
| 9544750 | Self et al. | Jan 2017 | B1 |
| 9591467 | Piett et al. | Mar 2017 | B2 |
| 9609128 | Dahan et al. | Mar 2017 | B2 |
| 9629185 | Gluckman et al. | Apr 2017 | B1 |
| 9635534 | Maier et al. | Apr 2017 | B2 |
| 9648479 | Michaelis et al. | May 2017 | B2 |
| 9659484 | Mehta et al. | May 2017 | B1 |
| 9693213 | Self et al. | Jun 2017 | B2 |
| 9734721 | Stenneth et al. | Aug 2017 | B2 |
| 9736670 | Mehta et al. | Aug 2017 | B2 |
| 9756169 | Mehta et al. | Sep 2017 | B2 |
| 9805430 | Miasnik et al. | Oct 2017 | B2 |
| 9838858 | Anand et al. | Dec 2017 | B2 |
| 9877177 | Lesage et al. | Jan 2018 | B2 |
| 9924043 | Mehta et al. | Mar 2018 | B2 |
| 9936365 | Elam | Apr 2018 | B1 |
| 9942739 | Bozik et al. | Apr 2018 | B2 |
| 9986404 | Mehta et al. | May 2018 | B2 |
| 9992655 | Anand et al. | Jun 2018 | B2 |
| 9998507 | Mehta et al. | Jun 2018 | B2 |
| 10002375 | Scythes et al. | Jun 2018 | B1 |
| 10089854 | Hender et al. | Oct 2018 | B2 |
| 10136294 | Mehta et al. | Nov 2018 | B2 |
| 10140482 | Mehta et al. | Nov 2018 | B2 |
| 10140842 | Mehta et al. | Nov 2018 | B2 |
| 10142213 | Hart et al. | Nov 2018 | B1 |
| 10142469 | Klaban | Nov 2018 | B2 |
| 10142816 | Cavendish et al. | Nov 2018 | B2 |
| 10165431 | Bozik et al. | Dec 2018 | B2 |
| 10375558 | Katz et al. | Aug 2019 | B2 |
| 10419915 | Mehta et al. | Sep 2019 | B2 |
| 10425799 | Anand et al. | Sep 2019 | B2 |
| 10447865 | Mehta et al. | Oct 2019 | B2 |
| 10657799 | Mehta et al. | May 2020 | B2 |
| 10701541 | Mehta et al. | Jun 2020 | B2 |
| 10701542 | Martin et al. | Jun 2020 | B2 |
| 10708412 | Killpack | Jul 2020 | B1 |
| 10771951 | Mehta et al. | Sep 2020 | B2 |
| 10805786 | Pellegrini et al. | Oct 2020 | B2 |
| 10820181 | Horelik et al. | Oct 2020 | B2 |
| 10861320 | Martin et al. | Dec 2020 | B2 |
| 10911926 | Pellegrini et al. | Feb 2021 | B2 |
| 10922776 | Kumar et al. | Feb 2021 | B2 |
| 10977927 | Katz et al. | Apr 2021 | B2 |
| 20010051849 | Boone | Dec 2001 | A1 |
| 20020001367 | Lee | Jan 2002 | A1 |
| 20020027975 | Oxley | Mar 2002 | A1 |
| 20020057678 | Jiang et al. | May 2002 | A1 |
| 20020120698 | Tamargo | Aug 2002 | A1 |
| 20030069035 | Shurvinton | Apr 2003 | A1 |
| 20030109245 | McCalmont et al. | Jun 2003 | A1 |
| 20030195775 | Hampton et al. | Oct 2003 | A1 |
| 20040203569 | Jijina | Oct 2004 | A1 |
| 20040203572 | Aerrabotu et al. | Oct 2004 | A1 |
| 20040229620 | Zhao et al. | Nov 2004 | A1 |
| 20040266390 | Faucher et al. | Dec 2004 | A1 |
| 20050085215 | Kokko et al. | Apr 2005 | A1 |
| 20050104745 | Bachelder et al. | May 2005 | A1 |
| 20050111630 | Potorny et al. | May 2005 | A1 |
| 20050151642 | Tupler et al. | Jul 2005 | A1 |
| 20050190892 | Dawson et al. | Sep 2005 | A1 |
| 20050192746 | King et al. | Sep 2005 | A1 |
| 20050220277 | Blalock et al. | Oct 2005 | A1 |
| 20050222829 | Dumas | Oct 2005 | A1 |
| 20050239477 | Kim et al. | Oct 2005 | A1 |
| 20050242944 | Bankert et al. | Nov 2005 | A1 |
| 20050282518 | D'Evelyn et al. | Dec 2005 | A1 |
| 20050285181 | Yasui et al. | Dec 2005 | A1 |
| 20060085275 | Stokes et al. | Apr 2006 | A1 |
| 20060109960 | D'Evelyn et al. | May 2006 | A1 |
| 20060154642 | Scannell, Jr. | Jul 2006 | A1 |
| 20060217105 | Kumar P S et al. | Sep 2006 | A1 |
| 20060265195 | Woodard | Nov 2006 | A1 |
| 20060293024 | Benco et al. | Dec 2006 | A1 |
| 20070003024 | Olivier et al. | Jan 2007 | A1 |
| 20070030144 | Titus et al. | Feb 2007 | A1 |
| 20070030146 | Shepherd | Feb 2007 | A1 |
| 20070033095 | Hodgin et al. | Feb 2007 | A1 |
| 20070049287 | Dunn | Mar 2007 | A1 |
| 20070053308 | Dumas et al. | Mar 2007 | A1 |
| 20070058528 | Massa et al. | Mar 2007 | A1 |
| 20070060097 | Edge et al. | Mar 2007 | A1 |
| 20070161383 | Caci | Jul 2007 | A1 |
| 20070164872 | Monroe | Jul 2007 | A1 |
| 20070171854 | Chen et al. | Jul 2007 | A1 |
| 20070218895 | Saito et al. | Sep 2007 | A1 |
| 20070232328 | Kramarz-Von Kohout | Oct 2007 | A1 |
| 20080019268 | Rollins | Jan 2008 | A1 |
| 20080063153 | Krivorot et al. | Mar 2008 | A1 |
| 20080077474 | Dumas et al. | Mar 2008 | A1 |
| 20080081646 | Morin et al. | Apr 2008 | A1 |
| 20080166990 | Toiv | Jul 2008 | A1 |
| 20080194238 | Kwon | Aug 2008 | A1 |
| 20080253535 | Sherry et al. | Oct 2008 | A1 |
| 20080274721 | Stagnetto | Nov 2008 | A1 |
| 20080294058 | Shklarski | Nov 2008 | A1 |
| 20080309486 | McKenna et al. | Dec 2008 | A1 |
| 20090041206 | Hobby et al. | Feb 2009 | A1 |
| 20090134982 | Robertson et al. | May 2009 | A1 |
| 20090186596 | Kaltsukis | Jul 2009 | A1 |
| 20090214000 | Patel et al. | Aug 2009 | A1 |
| 20090257345 | King | Oct 2009 | A1 |
| 20090311987 | Edge et al. | Dec 2009 | A1 |
| 20090322513 | Hwang et al. | Dec 2009 | A1 |
| 20100002846 | Ray et al. | Jan 2010 | A1 |
| 20100003946 | Ray | Jan 2010 | A1 |
| 20100003964 | Khare et al. | Jan 2010 | A1 |
| 20100093305 | Reich et al. | Apr 2010 | A1 |
| 20100156626 | Story | Jun 2010 | A1 |
| 20100159871 | Tester | Jun 2010 | A1 |
| 20100159976 | Marocchi et al. | Jun 2010 | A1 |
| 20100161727 | Shaffer et al. | Jun 2010 | A1 |
| 20100166153 | Guleria et al. | Jul 2010 | A1 |
| 20100190468 | Scott et al. | Jul 2010 | A1 |
| 20100202368 | Hans | Aug 2010 | A1 |
| 20100238018 | Kelly | Sep 2010 | A1 |
| 20100261448 | Peters | Oct 2010 | A1 |
| 20100262668 | Piett et al. | Oct 2010 | A1 |
| 20100317317 | Maier et al. | Dec 2010 | A1 |
| 20110009086 | Poremba et al. | Jan 2011 | A1 |
| 20110029600 | Theimer | Feb 2011 | A1 |
| 20110071880 | Spector | Mar 2011 | A1 |
| 20110086607 | Wang et al. | Apr 2011 | A1 |
| 20110103266 | Andreasen et al. | May 2011 | A1 |
| 20110134897 | Montemurro et al. | Jun 2011 | A1 |
| 20110151829 | Velusamy et al. | Jun 2011 | A1 |
| 20110153368 | Pierre et al. | Jun 2011 | A1 |
| 20110201357 | Garrett et al. | Aug 2011 | A1 |
| 20110263219 | Hasenfang et al. | Oct 2011 | A1 |
| 20110263319 | Hamalainen et al. | Oct 2011 | A1 |
| 20120002792 | Chang | Jan 2012 | A1 |
| 20120028599 | Hatton et al. | Feb 2012 | A1 |
| 20120029970 | Stiles et al. | Feb 2012 | A1 |
| 20120040636 | Kazmi | Feb 2012 | A1 |
| 20120066139 | Guzman et al. | Mar 2012 | A1 |
| 20120092161 | West | Apr 2012 | A1 |
| 20120144019 | Zhu | Jun 2012 | A1 |
| 20120157795 | Chiu et al. | Jun 2012 | A1 |
| 20120202428 | Mirbaha et al. | Aug 2012 | A1 |
| 20120210325 | De Lind Van Wijngaarden et al. | Aug 2012 | A1 |
| 20120218102 | Bivens et al. | Aug 2012 | A1 |
| 20120256745 | Piett et al. | Oct 2012 | A1 |
| 20120257729 | Piett et al. | Oct 2012 | A1 |
| 20120258680 | Piett et al. | Oct 2012 | A1 |
| 20120289243 | Tarlow et al. | Nov 2012 | A1 |
| 20120295575 | Nam | Nov 2012 | A1 |
| 20120309341 | Ward | Dec 2012 | A1 |
| 20130005295 | Park et al. | Jan 2013 | A1 |
| 20130012155 | Forstall et al. | Jan 2013 | A1 |
| 20130030825 | Bagwandeen et al. | Jan 2013 | A1 |
| 20130052983 | Fletcher et al. | Feb 2013 | A1 |
| 20130065569 | Leipzig et al. | Mar 2013 | A1 |
| 20130082837 | Cosentino et al. | Apr 2013 | A1 |
| 20130084824 | Hursey | Apr 2013 | A1 |
| 20130102351 | Mo | Apr 2013 | A1 |
| 20130122932 | Patel et al. | May 2013 | A1 |
| 20130138791 | Thomas et al. | May 2013 | A1 |
| 20130183924 | Saigh et al. | Jul 2013 | A1 |
| 20130185368 | Nordstrom | Jul 2013 | A1 |
| 20130203373 | Edge | Aug 2013 | A1 |
| 20130203376 | Maier et al. | Aug 2013 | A1 |
| 20130222133 | Schultz et al. | Aug 2013 | A1 |
| 20130226369 | Yorio et al. | Aug 2013 | A1 |
| 20130237175 | Piett | Sep 2013 | A1 |
| 20130237181 | Ray | Sep 2013 | A1 |
| 20130260710 | Hr | Oct 2013 | A1 |
| 20130309994 | Hellwig et al. | Nov 2013 | A1 |
| 20130331055 | Mckown et al. | Dec 2013 | A1 |
| 20130331058 | Harvey | Dec 2013 | A1 |
| 20140031000 | Hanover | Jan 2014 | A1 |
| 20140045450 | Ballantyne et al. | Feb 2014 | A1 |
| 20140051379 | Ganesh et al. | Feb 2014 | A1 |
| 20140057590 | Romero | Feb 2014 | A1 |
| 20140086108 | Dunn et al. | Mar 2014 | A1 |
| 20140087680 | Luukkala et al. | Mar 2014 | A1 |
| 20140096195 | Morgan | Apr 2014 | A1 |
| 20140113606 | Morken et al. | Apr 2014 | A1 |
| 20140126356 | Lee et al. | May 2014 | A1 |
| 20140134969 | Jin et al. | May 2014 | A1 |
| 20140142979 | Mitsunaga | May 2014 | A1 |
| 20140148117 | Basore et al. | May 2014 | A1 |
| 20140148120 | Buck | May 2014 | A1 |
| 20140155017 | Fan et al. | Jun 2014 | A1 |
| 20140155018 | Fan et al. | Jun 2014 | A1 |
| 20140164505 | Daly et al. | Jun 2014 | A1 |
| 20140199959 | Hassan et al. | Jul 2014 | A1 |
| 20140213212 | Clawson | Jul 2014 | A1 |
| 20140222462 | Shakil et al. | Aug 2014 | A1 |
| 20140248848 | Mufti et al. | Sep 2014 | A1 |
| 20140253326 | Cho et al. | Sep 2014 | A1 |
| 20140257846 | Hermiz et al. | Sep 2014 | A1 |
| 20140302810 | Inha et al. | Oct 2014 | A1 |
| 20140324351 | Dannevik et al. | Oct 2014 | A1 |
| 20140359008 | Finney et al. | Dec 2014 | A1 |
| 20140368601 | Decharms | Dec 2014 | A1 |
| 20140370836 | Gladstone | Dec 2014 | A1 |
| 20140370839 | Hatton | Dec 2014 | A1 |
| 20140370841 | Roberts et al. | Dec 2014 | A1 |
| 20150011176 | Zhu | Jan 2015 | A1 |
| 20150029836 | Hans et al. | Jan 2015 | A1 |
| 20150031324 | Zentner et al. | Jan 2015 | A1 |
| 20150055453 | Chaki et al. | Feb 2015 | A1 |
| 20150055554 | Sedlacek et al. | Feb 2015 | A1 |
| 20150065082 | Sehgal | Mar 2015 | A1 |
| 20150081209 | Yeh et al. | Mar 2015 | A1 |
| 20150081927 | Xu et al. | Mar 2015 | A1 |
| 20150085997 | Biage | Mar 2015 | A1 |
| 20150087259 | Hinsen | Mar 2015 | A1 |
| 20150094095 | Johnson et al. | Apr 2015 | A1 |
| 20150099481 | Maitre et al. | Apr 2015 | A1 |
| 20150109125 | Kaib et al. | Apr 2015 | A1 |
| 20150111524 | South | Apr 2015 | A1 |
| 20150112883 | Orduna et al. | Apr 2015 | A1 |
| 20150137972 | Nepo et al. | May 2015 | A1 |
| 20150140936 | Sachs et al. | May 2015 | A1 |
| 20150172897 | Mariathasan et al. | Jun 2015 | A1 |
| 20150181401 | Dhandu et al. | Jun 2015 | A1 |
| 20150289121 | Lesage et al. | Oct 2015 | A1 |
| 20150304827 | Price et al. | Oct 2015 | A1 |
| 20150317392 | Fernandez | Nov 2015 | A1 |
| 20150317809 | Chellappan et al. | Nov 2015 | A1 |
| 20150319284 | Leonessi | Nov 2015 | A1 |
| 20150350262 | Rainisto et al. | Dec 2015 | A1 |
| 20150358794 | Nokhoudian et al. | Dec 2015 | A1 |
| 20150365319 | Finn et al. | Dec 2015 | A1 |
| 20160004224 | Pi | Jan 2016 | A1 |
| 20160026768 | Singh et al. | Jan 2016 | A1 |
| 20160057595 | Ahmed et al. | Feb 2016 | A1 |
| 20160065748 | Li et al. | Mar 2016 | A1 |
| 20160088455 | Bozik et al. | Mar 2016 | A1 |
| 20160173689 | Klaban | Jun 2016 | A1 |
| 20160210581 | Braun | Jul 2016 | A1 |
| 20160219084 | Abiezzi | Jul 2016 | A1 |
| 20160219397 | Mayor et al. | Jul 2016 | A1 |
| 20160227589 | Marshall et al. | Aug 2016 | A1 |
| 20160269535 | Balabhadruni et al. | Sep 2016 | A1 |
| 20160307436 | Nixon | Oct 2016 | A1 |
| 20160315923 | Riscombe-Burton et al. | Oct 2016 | A1 |
| 20160316493 | Davis et al. | Oct 2016 | A1 |
| 20160330769 | Edge | Nov 2016 | A1 |
| 20160337831 | Piett | Nov 2016 | A1 |
| 20160345171 | Kulkarni et al. | Nov 2016 | A1 |
| 20160353266 | Winkler et al. | Dec 2016 | A1 |
| 20160363931 | Yang et al. | Dec 2016 | A1 |
| 20160371973 | Holleczek et al. | Dec 2016 | A1 |
| 20170004427 | Bruchal et al. | Jan 2017 | A1 |
| 20170012815 | Nekrestyanov et al. | Jan 2017 | A1 |
| 20170046216 | Stenneth et al. | Feb 2017 | A1 |
| 20170078226 | Daly et al. | Mar 2017 | A1 |
| 20170099579 | Ryan et al. | Apr 2017 | A1 |
| 20170108862 | Mikkelsen | Apr 2017 | A1 |
| 20170124670 | Becker et al. | May 2017 | A1 |
| 20170124852 | Pauws et al. | May 2017 | A1 |
| 20170140637 | Thurlow et al. | May 2017 | A1 |
| 20170142568 | Saito et al. | May 2017 | A1 |
| 20170150335 | Self et al. | May 2017 | A1 |
| 20170161614 | Mehta et al. | Jun 2017 | A1 |
| 20170180963 | Cavendish et al. | Jun 2017 | A1 |
| 20170180966 | Piett et al. | Jun 2017 | A1 |
| 20170188218 | Corley et al. | Jun 2017 | A1 |
| 20170213251 | Nunally et al. | Jul 2017 | A1 |
| 20170238129 | Maier et al. | Aug 2017 | A1 |
| 20170238136 | Smith | Aug 2017 | A1 |
| 20170245113 | Hooker | Aug 2017 | A1 |
| 20170287085 | Smith et al. | Oct 2017 | A1 |
| 20170310827 | Mehta et al. | Oct 2017 | A1 |
| 20170316698 | Stenneth et al. | Nov 2017 | A1 |
| 20170323209 | Rinzler et al. | Nov 2017 | A1 |
| 20170325056 | Mehta et al. | Nov 2017 | A1 |
| 20170331954 | Kotnis et al. | Nov 2017 | A1 |
| 20170359712 | Meredith et al. | Dec 2017 | A1 |
| 20170374538 | Gellens et al. | Dec 2017 | A1 |
| 20180020091 | Self et al. | Jan 2018 | A1 |
| 20180039737 | Dempers et al. | Feb 2018 | A1 |
| 20180077282 | Herron et al. | Mar 2018 | A1 |
| 20180077553 | Gideon, III | Mar 2018 | A1 |
| 20180150928 | Dejewski et al. | May 2018 | A1 |
| 20180176271 | Laurent | Jun 2018 | A1 |
| 20180262544 | Mehta et al. | Sep 2018 | A1 |
| 20180352408 | Baer et al. | Dec 2018 | A1 |
| 20190020993 | Nguyen | Jan 2019 | A1 |
| 20190130719 | D'Amico | May 2019 | A1 |
| 20190149661 | Klaban | May 2019 | A1 |
| 20190166244 | Ravichandran | May 2019 | A1 |
| 20190166480 | Rauner | May 2019 | A1 |
| 20190174288 | Bozik et al. | Jun 2019 | A1 |
| 20190281165 | Mehta et al. | Sep 2019 | A1 |
| 20190320310 | Horelik et al. | Oct 2019 | A1 |
| 20190327597 | Katz et al. | Oct 2019 | A1 |
| 20190335310 | Anand et al. | Oct 2019 | A1 |
| 20200059776 | Martin et al. | Feb 2020 | A1 |
| 20200100084 | Martin et al. | Mar 2020 | A1 |
| 20200126174 | Halse et al. | Apr 2020 | A1 |
| 20200221279 | Mehta et al. | Jul 2020 | A1 |
| 20200274962 | Martin et al. | Aug 2020 | A1 |
| 20200314240 | Leavitt et al. | Oct 2020 | A1 |
| 20210006961 | King-Berkman et al. | Jan 2021 | A1 |
| 20210014659 | Mehta et al. | Jan 2021 | A1 |
| 20210037368 | Leavitt et al. | Feb 2021 | A1 |
| 20210110686 | Slavin et al. | Apr 2021 | A1 |
| 20210120394 | Martin et al. | Apr 2021 | A1 |
| 20210127228 | Baarman et al. | Apr 2021 | A1 |
| 20210204108 | Horelik et al. | Jul 2021 | A1 |
| 20210239489 | Gotschall | Aug 2021 | A1 |
| 20210266722 | Pellegrini et al. | Aug 2021 | A1 |
| 20210289334 | Martin et al. | Sep 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2662606 | Oct 2009 | CA |
| 2697986 | Sep 2010 | CA |
| 2773749 | Oct 2012 | CA |
| 2773881 | Oct 2012 | CA |
| 2790501 | Mar 2013 | CA |
| 2809421 | Sep 2013 | CA |
| 2646607 | Sep 2016 | CA |
| 2886535 | Oct 2016 | CA |
| 2697986 | May 2018 | CA |
| 104487976 | Apr 2015 | CN |
| 104539776 | Apr 2015 | CN |
| 106021508 | Oct 2016 | CN |
| 2161912 | Mar 2010 | EP |
| H10314133 | Dec 1998 | JP |
| H1170086 | Mar 1999 | JP |
| 2006319946 | Nov 2006 | JP |
| 2006334369 | Dec 2006 | JP |
| 2011223285 | Nov 2011 | JP |
| 2012222443 | Nov 2012 | JP |
| 20090019606 | Feb 2009 | KR |
| 20090092900 | Sep 2009 | KR |
| 20100055746 | May 2010 | KR |
| 101305286 | Sep 2013 | KR |
| 20140052780 | May 2014 | KR |
| 20140093568 | Jul 2014 | KR |
| 20150097031 | Aug 2015 | KR |
| 101602482 | Mar 2016 | KR |
| 101612423 | Apr 2016 | KR |
| 20160097933 | Aug 2016 | KR |
| 20170100422 | Sep 2017 | KR |
| WO0022593 | Apr 2000 | WO |
| WO0165763 | Sep 2001 | WO |
| WO0167419 | Sep 2001 | WO |
| WO2007109599 | Sep 2007 | WO |
| WO2012129561 | Sep 2012 | WO |
| WO2014025563 | Feb 2014 | WO |
| WO2014063121 | Apr 2014 | WO |
| WO2014074420 | May 2014 | WO |
| WO2014176646 | Nov 2014 | WO |
| WO2015127867 | Sep 2015 | WO |
| WO2015196155 | Dec 2015 | WO |
| WO2016044540 | Mar 2016 | WO |
| WO2017079354 | May 2017 | WO |
| WO2017083571 | May 2017 | WO |
| WO2017100220 | Jun 2017 | WO |
| WO2017106775 | Jun 2017 | WO |
| WO2017112820 | Jun 2017 | WO |
| WO2017189610 | Nov 2017 | WO |
| WO2017196753 | Nov 2017 | WO |
| WO2018039142 | Mar 2018 | WO |
| WO2019113129 | Jun 2019 | WO |
| WO2020172612 | Aug 2020 | WO |
| WO2020205033 | Oct 2020 | WO |
| WO2021034859 | Feb 2021 | WO |
| Entry |
|---|
| Tazaki. Floating Ground: An Architecture for Network Mobility and Ad Hoc Network Convergence. Thesis. Graduate School of Media and Governance Keio University 5322 Endo Fujisaw. |
| U.S. Census Bureau. Developers: Population Estimates APIs. Available at https://www.census.gov/data/developers/data-sets/popest-popproj/popest.html (2 pgs.) (Accessed Septembe. |
| Weather Company Data For IBM Bluemix APIs. Available at https://twcservice.mybluemix.net/rest-api/ (100 pgs) (Accessed Sep. 2017). |
| ArcGIS REST Services Directory. Folder: TIGERWeb. Available at https://tigerweb.geo.census.gov/arcgis/rest/services/TIGERweb. (1 pg.) (Accessed Sep. 2017). |
| Homeland Security Science and Technology. Using Social Media for Enhanced Situational Awareness and Decision Support. Virtual Social Medial Working Group and DHS First Respond. |
| Marcus et al. Twitinfo: Aggregating and Visualizing Microblogs for Event Exploration. ACM CHI Conference 2011 May 7-12, 2011, (10 pgs). |
| Meier. MatchApp: Next Generation Disaster Response App? iRevolution (12 pgs.) (Feb. 27, 2013). |
| National Emergency Number Association (Nena) Technical Committee Chairs: NENA Functional and Interface Standards for Next Generation 9-1-1 Version 1.0 (i3). (Dec. 18, 2017). Retr. |
| National Emergency Number Association (NENA). Social Networking in 9-1-1 PSAPs Information Document. Available at https://c.ymcdn.com/sites/www.nena.org/resource/resmgr/Standa. |
| Seattle Real Time Fire 911 Calls. Available at https://catalog.data.gov/dataset/seattle-real-time-fire-911-calls-6cdf3 (3 pgs.) (Accessed Sep. 2017). |
| Song. Next Generation Emergency Call System with Enhanced Indoor Positioning, Columbia University. Thesis [online] [retrieved Apr. 20, 2020 from https://scholar.google.co.kr/citat. |
| Number | Date | Country | |
|---|---|---|---|
| 63148581 | Feb 2021 | US | |
| 63133045 | Dec 2020 | US |
