US-20260129122-A1 - 911 ADDRESS UPDATE

US20260129122A1US 20260129122 A1US20260129122 A1US 20260129122A1US-20260129122-A1

Abstract

Novel tools and techniques are provided for implementing 911 or enhanced 911 (“E911”) address update. In various embodiments, in response to a trigger event, a computing system may determine whether E911 address data associated with a customer that is stored in an E911 database requires updating. If so, the computing system may update the E911 database with address data associated with the customer that has been validated or verified (if available). Where no validated or verified address associated with the customer is available, the computing system may send a message to the customer to provide updated 911 or E911 address data; may receive, from a user device associated with the customer via an API over a network(s) operated by the service provider, updated 911 or E911 address data from the customer; and may update the E911 database with the received updated 911 or E911 address data from the customer.

Inventors

Bridget McAndrew
Anne Kempen
Sudhir Dadi
Corey Curtis
Michael Robles
Kevin Michelsen

Assignees

LEVEL 3 COMMUNICATIONS, LLC

Dates

Publication Date: 20260507
Application Date: 20251222

Claims (18)

1 . A method, comprising: in response to a trigger event, determining, using a computing system, that a set of 911 address data associated with a customer that is stored in a 911 database requires updating; determining, using the computing system, that any address data associated with the customer is not contained in at least one database accessible by the computing system or that any address data associated with the customer that is contained in the at least one database has not been validated or verified; sending, using the computing system, a message to the customer to provide updated 911 address data; receiving, using the computing system and from a user device associated with the customer via an application programming interface (“API”) over a network operated by a service provider, updated 911 address data from the customer; and in response to receiving updated 911 address data from the customer, updating, using the computing system, the 911 database with the received updated 911 address data from the customer, wherein, in response to the customer initiating a 911 emergency call, a third party vendor routes the 911 emergency call to a local public safety access point (“PSAP”) on behalf of the customer or the service provider, wherein the first address data associated with the customer is validated or verified by the third party vendor.
2 . The method of claim 1 , wherein the computing system comprises at least one of an API platform computing system, an API gateway, a customer interface server, an E911 address change server, a gateway controller, a network operations center (“NOC”), a cloud computing system, or a distributed computing system.
3 . The method of claim 1 , wherein the trigger event comprises one of: receiving an order to add, remove, or change telephone service associated with the customer; receiving an order to relocate at least one call device having a corresponding telephone number associated with the customer from a first area to a second area within a known geographic location associated with the customer; receiving an order to relocate at least one call device having a corresponding associated with the customer from a first area in a first location associated with the customer to a second area in a second location, the second location being in a geographically separate part of a region from the first location, wherein the region comprises one of a neighborhood, a campus, a section of a municipality, an entire municipality, a state, a collection of neighboring states, a country, or a continent; receiving an order to set up at least one work-from-home call device for a corresponding at least one employee of the customer, the at least one work-from-home call device having a corresponding telephone number associated with the customer; receiving a notification that a business telephone directory maintained by the customer has changed; receiving a notification that a telephone number associated with the customer is involved in a session initiation protocol (“SIP”)-based communication from a location different from any E911 addresses associated with the customer as stored in the 911 database, based on geo-location data; receiving a notification indicating a change in geo-location data associated with a telephone number associated with the customer that is involved in a SIP-based communication; receiving a notification that a telephone number associated with the customer is involved in a SIP-based communication from a location different from any E911 addresses associated with the customer as stored in the 911 database, based on Internet Protocol (“IP”) address data; receiving a notification indicating a change in IP address associated with a telephone number associated with the customer that is involved in a SIP-based communication; receiving a request from the customer to update at least one address in the 911 database; receiving a notification indicating that a third party vendor has changed at least one E911 address associated with the customer in at least one database; or receiving instructions to initiate an E911 address audit for the customer.
4 . The method of claim 3 , wherein the geo-location data comprises one of global positioning system (“GPS”) data, assisted GPS (“A-GPS”) data, global navigation satellite system (“GLONASS”) data, assisted GLONASS (“A-GLONASS”) data, Galileo global navigation satellite system (“GNSS”) data, BeiDou navigation satellite system (“BDS”) data, geographic information system (“GIS”) data, geocoded address data, cellular network radiolocation-based data, wireless phase one (“WPH1”) location data, or wireless phase two (“WPH2”) location data.
5 . The method of claim 1 , wherein determining whether the set of 911 address data associated with the customer requires updating comprises determining, using the computing system, whether the set of 911 address data requires updating based on one of: a transfer of telephone service for the customer from an unaffiliated service provider; a stated or detected change in geo-location data of at least one call device having a corresponding telephone number associated with the customer; a change in a business telephone directory maintained by the customer; a stated or detected change in Internet Protocol (“IP”) address of at least one call device having a corresponding telephone number associated with the customer; a stated or detected change in at least one 911 address associated with the customer in at least one database maintained by the third party vendor; at least one call device having a corresponding telephone number associated with the customer being set up as a work-from-home call device for an employee of the customer; a determined discrepancy between at least one database maintained by the third party vendor and at least one database maintained by the service provider; a request to update at least one address in the 911 database; results of an 911 address audit for the customer; or whether any changes to at least one address associated with the customer affect any address contained within the set of 911 address data.
6 . The method of claim 1 , further comprising: receiving, using the computing system, a passback of the first address data from the at least one database maintained by the third party vendor; and updating, using the computing system, the one or more address data associated with the customer contained in at least one database maintained by the service provider with the received first address data.
7 . The method of claim 1 , further comprising: mirroring, using the computing system, the first address data associated with the customer contained in the at least one database maintained by the third party vendor and one or more address data associated with the customer contained in at least one database maintained by the service provider.
8 . The method of claim 1 , wherein one or more of the 911 database or the at least one database each comprises at least one of an automatic location identification (“ALI”) database, a master street address guide (“MSAG”), a United States postal service (“USPS”) database, North American 9-1-1 Resource Database, a database associated with the service provider, or a database associated with a third party vendor.
9 . The method of claim 1 , wherein receiving the updated 911 address data from the customer comprises receiving, using the computing system and via the API over the network, updated 911 address data from the customer through a user interface (“UI”) displayed on the user device associated with the customer, wherein the UI comprises one of a portal-based UI, a webpage UI, or a software application (“app”) UI running on the user device.
10 . The method of claim 9 , wherein the UI provides the customer with at least one of: one or more options to update, enter, or save at least one 911 address associated with the customer, wherein each 911 address comprises a physical address that is provided to first responders in response to a 911 emergency call being initiated by the customer; one or more options to update, enter, or save at least one primary address associated with the customer, wherein each primary address comprises a street address; one or more options to update, enter, or save at least one secondary address associated with the customer, each secondary address comprises at least one of building number, floor, suite, or office number; one or more options to update, enter, or save at least one service address associated with the customer, wherein each service address comprises one of a physical address at which service is provided to the customer by a service provider associated with one of the computing system or the network or a billing address associated with the customer; one or more options to change at least one trigger event for updating at least one 911 address associated with the customer; one or more options to synchronize at least one 911 address associated with the customer across at least two databases; one or more options to notify the customer in the event of discrepancies in at least one 911 address associated with the customer that are found in two or more databases; one or more options to notify the customer when at least one 911 address associated with the customer has been updated, changed, or deleted; or one or more options to update, enter, or save one or more telephone numbers associated with at least one E911 address associated with the customer.
11 . The method of claim 1 , further comprising: validating, using the computing system, any address associated with the customer that is being added or changed against a standard address format prior to updating the 911 database, wherein the standard address format comprises one of an automatic location identification (“ALI”) database address format, a master street address guide (“MSAG”) address format, a United States Postal Service (“USPS”) database address format, or North American 9-1-1 Resource Database address format.
12 . The method of claim 1 , further comprising: receiving, using the computing system and from the user device associated with the customer via the API, a first request to validate at least one address associated with the customer; and in response to receiving the first request, validating, using the computing system, the at least one address against a standard address format, wherein the standard address format comprises one of an automatic location identification (“ALI”) database address format, a master street address guide (“MSAG”) address format, a United States Postal Service (“USPS”) database address format, or North American 9-1-1 Resource Database address format.
13 . The method of claim 1 , further comprising: receiving, using the computing system and from the user device associated with the customer via the API, a second request to obtain at least one current address associated with the customer from the 911 database; and in response to receiving the second request, retrieving, using the computing system and from the 911 database, the requested at least one current address, and sending, using the computing system and to the user device, the retrieved at least one current address.
14 . The method of claim 1 , further comprising: receiving, using the computing system and from the user device associated with the customer via the API, a fourth request to change at least one address associated with the customer in the 911 database, the fourth request comprising one or more telephone numbers associated with the customer and one or more updated addresses corresponding to each telephone number, each telephone number corresponding to the at least one address; in response to receiving the fourth request, validating, using the computing system, each updated address among the one or more updated addresses in the fourth request; and after the one or more updated addresses have been validated, replacing, using the computing system, the at least one address in the 911 database with the validated one or more updated addresses, and sending, using the computing system and to the user device, a message confirming that the at least one address has been updated with the one or more updated addresses.
15 . The method of claim 1 , further comprising: receiving, using the computing system and from the user device associated with the customer via the API, a status query regarding an 911 address change request; and in response to receiving the status request, determining, using the computing system, a current status of a process for changing the 911 address associated with the customer, and sending, using the computing system and to the user device, a message indicating the current status of the process for changing the 911 address associated with the customer.
16 . An apparatus, comprising: at least one processor; and a non-transitory computer readable medium communicatively coupled to the at least one processor, the non-transitory computer readable medium having stored thereon computer software comprising a set of instructions that, when executed by the at least one processor, causes the apparatus to: in response to a trigger event, determine that a set of 911 address data associated with a customer that is stored in a 911 database requires updating; determine that any address data associated with the customer is not contained in at least one database accessible by the computing system or that any address data associated with the customer that is contained in the at least one database has not been validated or verified; send a message to the customer to provide updated 911 address data; receive, from a user device associated with the customer via an application programming interface (“API”) over a network operated by a service provider, updated 911 or E911 address data from the customer; and in response to receiving updated 911 address data from the customer, update the 911 database with the received updated 911 address data from the customer, wherein, in response to the customer initiating a 911 emergency call, a third party vendor routes the 911 emergency call to a local public safety access point (“PSAP”) on behalf of the customer or the service provider, wherein the first address data associated with the customer is validated or verified by the third party vendor.
17 . A system, comprising: a computing system, comprising: at least one first processor; and a first non-transitory computer readable medium communicatively coupled to the at least one first processor, the first non-transitory computer readable medium having stored thereon computer software comprising a first set of instructions that, when executed by the at least one first processor, causes the computing system to: in response to a trigger event, determine that a set of 911 address data associated with a customer that is stored in a 911 database requires updating; determine that any address data associated with the customer is not contained in at least one database accessible by the computing system or that any address data associated with the customer that is contained in the at least one database has not been validated or verified send a message to the customer to provide updated 911 address data; receive, from a user device associated with the customer via an application programming interface (“API”) over a network operated by a service provider, updated 911 or E911 address data from the customer; and in response to receiving updated 911 address data from the customer, update the 911 database with the received updated 911 address data from the customer, wherein, in response to the customer initiating a 911 emergency call, a third party vendor routes the 911 emergency call to a local public safety access point (“PSAP”) on behalf of the customer or the service provider, wherein the first address data associated with the customer is validated or verified by the third party vendor.
18 . The system of claim 17 , wherein the computing system comprises at least one of an API platform computing system, an API gateway, a customer interface server, an E911 address change server, a gateway controller, a network operations center (“NOC”), a cloud computing system, or a distributed computing system.

Description

COPYRIGHT STATEMENT A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. FIELD The present disclosure relates, in general, to methods, systems, and apparatuses for implementing public safety service point (“PSAP”) operations and functionalities, and, more particularly, to methods, systems, and apparatuses for implementing 911 or enhanced 911 (“E911”) address update. BACKGROUND Traditionally, 911 or enhanced 911 (“E911”) address updates are performed by third party vendors on behalf of a service provider or a customer of the service provider. Such 911 or E911 address updates are typically performed by the third party vendor without any supervision or control by the service provider. As such, where a third party vendor updates, validates, or changes a customer's 911 or E911 address, such updated, validated, or changed address information may not always be passed back to the service provider. Also, a customer may not diligently update its 911 or E911 address with a public safety service point (“PSAP”) or with the service provider. Accordingly, two or more of the E911 database, the third party vendor database, and the service provider database may contain inconsistent 911 or E911 address information for the customer, which may lead to potential life-threatening issues with the wrong E911 address being relayed to first responders by local PSAPs during an emergency. Further, conventional 911 or E911 address updating is typically performed manually or using in-person calling, verification, and updating, or the like, resulting in 911 or E911 address updates that may take days or longer to take effect. Hence, there is a need for more robust and scalable solutions for implementing PSAP operations and functionalities, and, more particularly, to methods, systems, and apparatuses for implementing 911 or E911 address update. BRIEF DESCRIPTION OF THE DRAWINGS A further understanding of the nature and advantages of particular embodiments may be realized by reference to the remaining portions of the specification and the drawings, in which like reference numerals are used to refer to similar components. In some instances, a sub-label is associated with a reference numeral to denote one of multiple similar components. When reference is made to a reference numeral without specification to an existing sub-label, it is intended to refer to all such multiple similar components. FIG. 1 is a schematic diagram illustrating a system for implementing 911 or enhanced 911 (“E911”) address update, in accordance with various embodiments. FIGS. 2A and 2B are block flow diagrams illustrating a non-limiting example of an ecosystem and portions thereof that may be used for implementing 911 or E911 address update, in accordance with various embodiments. FIG. 3 is a system flow diagram illustrating a non-limiting example of a method for implementing 911 or E911 address update, in accordance with various embodiments. FIGS. 4A-4I are flow diagrams illustrating a method for implementing 911 or E911 address update, in accordance with various embodiments. FIG. 5 is a block diagram illustrating an exemplary computer or system hardware architecture, in accordance with various embodiments. FIG. 6 is a block diagram illustrating a networked system of computers, computing systems, or system hardware architecture, which can be used in accordance with various embodiments. DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS Overview Various embodiments provide tools and techniques for implementing public safety service point (“PSAP”) operations and functionalities, and, more particularly, to methods, systems, and apparatuses for implementing 911 or enhanced 911 (“E911”) address update. In various embodiments, in response to a trigger event, a computing system may determine whether a set of 911 or E911 address data associated with a customer that is stored in an E911 database requires updating. If so, the computing system may determine whether any address data associated with the customer is contained in at least one database accessible by the computing system and whether any address data associated with the customer that is contained in the at least one database has been validated or verified, where the at least one database is separate from the E911 database(s). Based on a determination that the at least one database contains first address data associated with the customer that has been validated or verified, the computing system may update the E911 database with the first address data associated with the customer that is contained in the at least one database and that has been validated or verified. Based on a determination that the at least one database d