US 11,736,903 B2
Techniques for registering an internet protocol (IP) endpoint for emergency services calling
Daniel Pereira, Bolivia, NC (US); Larry Reeder, Denver, CO (US); Lydia Runnels, Cary, NC (US); and Adam Covati, Durham, NC (US)
Assigned to Bandwidth Inc., Raleigh, NC (US)
Filed by Bandwidth Inc., Raleigh, NC (US)
Filed on Mar. 8, 2023, as Appl. No. 18/118,896.
Application 18/118,896 is a continuation of application No. 17/576,368, filed on Jan. 14, 2022, granted, now 11,632,655.
Prior Publication US 2023/0232188 A1, Jul. 20, 2023
Int. Cl. H04W 4/029 (2018.01); H04W 76/50 (2018.01); H04M 7/00 (2006.01); H04W 4/20 (2018.01); H04W 4/14 (2009.01)
CPC H04W 4/029 (2018.02) [H04M 7/0075 (2013.01); H04W 4/14 (2013.01); H04W 4/20 (2013.01); H04W 76/50 (2018.02)] 13 Claims
OG exemplary drawing
 
1. A method executable by a server hosted by an emergency services provider server, the method comprising:
receiving a location registration request, via a telephony server responding to a non-emergency telecommunication session establishment request from a telephony endpoint, the request including telephony endpoint identification information and a mobile device telephone number;
determining that location data for the telephony endpoint is not registered with the emergency services provider server;
sending a short message service (SMS) message to the mobile device telephone number, the SMS message including an executable registration link that when executed on a mobile device receiving the SMS message causes the mobile device to retrieve location data of the mobile device;
receiving the location data of the mobile device;
registering, for purposes of subsequent emergency calling, the location data of the mobile device as the location data for the telephony endpoint with the emergency services provider server; and
authorizing the telephony endpoint for the non-emergency telecommunication session only if the telephony endpoint has a location registered with the emergency services provider server.