US 11,909,915 B2
911 address update
Bridget McAndrew, Denver, CO (US); Anne Kempen, Denver, CO (US); Sudhir Dadi, Westminster, CO (US); Corey Curtis, Owasso, OK (US); Michael Robles, Arvada, CO (US); and Kevin Michelsen, Penfield, NY (US)
Assigned to Level 3 Communications, LLC, Broomfield, CO (US)
Filed by Level 3 Communications, LLC, Broomfield, CO (US)
Filed on Apr. 29, 2022, as Appl. No. 17/733,283.
Claims priority of provisional application 63/181,750, filed on Apr. 29, 2021.
Prior Publication US 2022/0353368 A1, Nov. 3, 2022
Int. Cl. H04M 3/51 (2006.01); H04W 4/029 (2018.01); G01S 19/01 (2010.01); H04W 4/90 (2018.01)
CPC H04M 3/5116 (2013.01) [G01S 19/01 (2013.01); H04W 4/029 (2018.02); H04W 4/90 (2018.02); H04M 2242/04 (2013.01); H04M 2242/30 (2013.01)] 19 Claims
OG exemplary drawing
 
1. A method, comprising:
in response to a trigger event, determining, using a computing system, whether a set of 911 or enhanced 911 (“E911”) address data associated with a customer that is stored in an E911 database requires updating;
based on a determination that the set of 911 or E911 address data associated with the customer requires updating, determining, using the computing system, 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, wherein the at least one database is separate from the E911 database;
based on a determination that the at least one database contains first address data associated with the customer that has been validated or verified, updating, using the computing system, 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 does not contain any address data associated with the customer 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 or E911 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 or E911 address data from the customer;
in response to receiving updated 911 or E911 address data from the customer, updating, using the computing system, the E911 database with the received updated 911 or E911 address data from the customer;
receiving, using the computing system and from the user device associated with the customer via the API, a first request to obtain a list of remote locations associated with a service identifier (“ID”) for the customer from a pipeline API; and
in response to receiving the first request, retrieving, using the computing system and from the pipeline API, information regarding remote locations associated with the service ID for the customer, compiling, using the computing system, the list of remote locations associated with the service ID for the customer, and sending, using the computing system and to the user device, the compiled list of remote locations.