Solutions for voice over internet protocol (VoIP) 911 location services

US9544429B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9544429-B2
Application numberUS-201514842071-A
CountryUS
Kind codeB2
Filing dateSep 1, 2015
Priority dateDec 19, 2003
Publication dateJan 10, 2017
Grant dateJan 10, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a mobile VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Mid-call updating of location of a moving VoIP terminal is provided to a PSAP. The location of the VoIP is validated using HTTP based protocol by pushing location information to a VoIP location server, and comparing it against a geographic location database to confirm that a contained street address is valid.

First claim

Opening claim text (preview).

What is claimed is: 1. A method of providing location information for a VoIP emergency communication, comprising: attempting to obtain a current location of a wireless phone that initiated an established emergency Voice over Internet Protocol (VoIP) communication; assigning a default Emergency Services Location Key (ESLK) to said established emergency VoIP communication; and transmitting, from a physical location server, a Session Initiation Protocol (SIP) message including said assigned default Emergency Services Location Key (ESLK), to a VoIP switch. 2. The method of providing location information for a VoIP emergency communication according to claim 1 , wherein: said default ESLK is based on a pre-registered address of said wireless phone. 3. The method of providing location information for a VoIP emergency communication according to claim 1 , wherein said physical location server comprises: a physical VoIP location server. 4. The method of providing location information for a VoIP emergency communication according to claim 3 , further comprising: removing said physical VoIP location server from a call signaling path of said emergency VoIP communication after said emergency VoIP communication has been established and before said emergency VoIP communication is terminated. 5. The method of providing location of a Voice Over Internet Protocol (VoIP) terminal according to claim 3 , wherein: said current location of said wireless phone that initiated said established emergency VoIP communication is attempted from a public safety answering point (PSAP). 6. The method of providing location information for a VoIP emergency communication according to claim 1 , wherein said SIP message further comprises: a default callback phone number. 7. The method of providing location information for a VoIP emergency communication according to claim 6 , wherein: said default callback phone number is an admin number. 8. The method of providing location information for a VoIP emergency communication according to claim 6 , wherein: said default callback phone number is an admin phone number of a service provider. 9. The method of providing location information for a VoIP emergency communication according to claim 1 , wherein said SIP message further comprises: a phone number of an initiating VoIP handset. 10. The method of providing location information for a VoIP emergency communication according to claim 1 , wherein: said emergency VoIP communication is an E911 call. 11. The method of providing location information for a VoIP emergency communication according to claim 1 , further comprising: receiving a call termination event relating to said emergency VoIP communication within a SIP NOTIFY message initiated by said VoIP switch. 12. Apparatus for providing location information for a VoIP emergency communication, comprising: means for attempting to obtain a current location of a wireless phone that initiated an established emergency Voice over Internet Protocol (VoIP) communication; means for assigning a default Emergency Services Location Key (ESLK) to said established emergency VoIP communication; and means for transmitting, from a physical location server, a Session Initiation Protocol (SIP) message including said assigned default Emergency Services Location Key (ESLK), to a VoIP switch. 13. The apparatus for providing location information for a VoIP emergency communication according to claim 12 , wherein: said default ESLK is based on a pre-registered address of said wireless phone. 14. The apparatus for providing location information for a VoIP emergency communication according to claim 12 , wherein said physical location server comprises: a physical VoIP location server. 15. The apparatus for providing location information for a VoIP emergency communication according to claim 14 , further comprising: means for removing said physical VoIP location server from a call signaling path of said emergency VoIP communication after said emergency VoIP communication has been established and before said emergency VoIP communication is terminated. 16. The apparatus for providing location information for a VoIP emergency communication according to claim 12 , wherein said SIP message further comprises: a default callback phone number. 17. The apparatus for providing location information for a VoIP emergency communication according to claim 12 , wherein said SIP message further comprises: a phone number of an initiating VoIP handset. 18. The apparatus for providing location information for a VoIP emergency communication according to claim 12 , wherein: said emergency VoIP communication is an E911 call. 19. The apparatus for providing location information for a VoIP emergency communication according to claim 12 , further comprising: means for receiving a call termination event relating to said emergency VoIP communication within a SIP NOTIFY message initiated by said VoIP switch.

Assignees

Inventors

Classifications

  • across networks, e.g. mapping telephone numbers to data network addresses · CPC title

  • Details of addressing, directories or routing tables · CPC title

  • Location-based management or tracking services · CPC title

  • Communication route or path selection, e.g. power-based or shortest path routing · CPC title

  • Network layer protocols, e.g. mobile IP [Internet Protocol] · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9544429B2 cover?
An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a mobile VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice…
Who is the assignee on this patent?
Telecomm Systems Inc
What technology area does this patent fall under?
Primary CPC classification H04M3/42348. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jan 10 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).