US 8,102,972 B2Grant
Emergency services selective router interface translator
Issue Date:2012-01-24
•9 Claims
•7 Drawing Sheets
Abstract
A selective router interface translator for placement between legacy selective routers and their location databases translates location queries from legacy selective router interfaces to newer protocol location databases using newer protocol interfaces, e.g., a NENA V8 protocol query to an Emergency Routing DataBase (ERDB), or a Location to Service Translation (LoST) protocol query to a LoST server. In this way existing selective routers may remain as they are today, yet be flexible enough to allow the databases they query to be developed to new standards. The disclosed selective router interface translator includes a NENA V3 protocol to LoST protocol translator to translate a NENA V3 query for location of an emergency caller into a LoST protocol query. The selective router interface translator also comprises an ALI to ERDB protocol translator to translate an ALI query for location of an emergency caller into an ERDB protocol query.
Metadata
Assignee
- TeleCommunication Systems, Inc.
Inventor
- Todd Poremba
Application Information
Application Number:US 12/457,274
Filing Date:2009-06-05
Priority Date:2008-06-05
Art Unit:2614
Classifications
IPC:
H04M11/04
Patent Drawings (7 sheets)
Description
[0001] This application claims priority from U.S. Provisional Application No. 61/129,108, filed Jun. 5, 2008 entitled “Selective Router Interface Translation to Standard Protocols” to Todd Poremba, the entirety of which is explicitly incorporated herein by reference.
Background of the Invention
[0002] 1. Field of the Invention
[0003] This invention relates generally to emergency services. More particularly, it relates to selective router (a.k.a., 9-1-1 Tandem) protocol conversion to NENA 08-001 V8 or IETF location to service translation (LoST) protocol.
[0004] 2. Background of the Related Art
[0005] In conventional emergency networks, a 9-1-1 call is placed, and forwarded by an end office to a 9-1-1 selective router. The selective router receives the call, and routes the call to a 9-1-1 trunk line to an associated public safety answering point (PSAP) appropriate for the current location of the caller.
[0006] Conventional selective routers define their own interfaces for querying databases for routing information. Developing standards specify a standard protocol for querying databases that store routing information.
[0007] FIG. 4A shows a conventional selective router operable to route an emergency call to a PSAP based on a current location of a caller obtained from a Location Information Server (LIS).
[0008] In particular, as shown in FIG. 4A , an end user device 10 places an emergency 9-1-1 call, which is routed to a legacy selective router 200 having a particular interface to an appropriate database to obtain the current location of the emergency caller 10, in this case we'll call it proprietary interface A to a Location Information System (LIS) 500. The LIS 500 provides a subscriber record that is typically the registered address (e.g., billing address) entered by the subscriber of the service when initially registering for wireline service. NOTE: A LIS may also have an interface to a service providers mobile environment so that queries for the location of a mobile user are determined at that moment of the emergency call.
[0009] FIG. 4B shows a conventional selective router operable to route an emergency call to a PSAP based on a current location of a caller obtained from an Emergency Routing DataBase (ERDB).
[0010] In particular, as shown in FIG. 4B , an end user device 11 places an emergency 9-1-1 call, this location serviced by a selective router 300 that has it's own method of obtaining a current location of the caller, e.g., to an Automatic Location Identification (ALI) server. The conventional ALI server provides a means of identifying a caller's address in an E911 emergency call.
[0011] Conventionally, companies that sell databases that store routing information also typically develop interfaces to permit the existing selective routers to query those databases.
Summary of the Invention
[0012] In accordance with the principles of the present invention, a selective router interface translator comprises a NENA V3 protocol interface for communication with a location information server (LIS). A Location to Service Translation (LoST) protocol interface communicates with a LoST server. A NENA V3 protocol to LoST protocol translator translates a NENA V3 query for location of an emergency caller received over the NENA V3 protocol interface into a LoST protocol query for transmission over the LoST protocol interface.
[0013] In accordance with another aspect of the invention, a selective router interface translator comprises an automatic location identifier (ALI) interface for communication with an ALI. A NENA V8 protocol interface communicates with an Emergency Routing DataBase (ERDB). An ALI to ERDB protocol translator translates an ALI query for location of an emergency caller received over the ALI interface into an ERDB protocol query for transmission over the ERDB interface.
Brief Description of the Drawings
[0014] Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings:
[0015] FIG. 1 depicts a selective router interface translator, in accordance with the principles of the present invention.
[0016] FIG. 2A shows a selective router interface translator in an emergency services network operable to route an emergency call to the proper public safety answering point (PSAP) based on a current location of the caller obtained from a Location to Service Translation (LOST) server via a location information server (LIS), in accordance with the principles of the present invention.
[0017] FIG. 2B shows a selective router interface translator in an emergency services network operable to route an emergency call to the proper public safety answering point (PSAP) based on a current location of the caller obtained from an automatic location information (ALI) server via an Emergency Routing DataBase (ERDB) server, in accordance with the principles of the present invention.
[0018] FIG. 3 shows a selective router interface translator in an emergency services network operable to route an emergency call to the proper public safety answering point (PSAP) based on a current location of the caller obtained from either an automatic location information (ALI) server or a Location Information Server (LIS) via either a Location to Service Translation (LoST) server or an Emergency Routing DataBase (ERDB) server, in accordance with the principles of the present invention.
[0019] FIG. 4A shows a conventional selective router operable to route an emergency call to a PSAP based on a current location of a caller obtained from a Location Information Server (LIS).
[0020] FIG. 4B shows a conventional selective router operable to route an emergency call to a PSAP based on a current location of a caller obtained from an Emergency Routing DataBase (ERDB).
Detailed Description of Illustrative Embodiments
[0021] The present inventor has appreciated in the context of selective routers that routing databases being planned today will only accept queries over a National Emergency Number Association (NENA) V8 interface, or using Location to Service Translation (LOST) protocol. The NENA V8 interface supports queries from a Voice Positioning Center (VPC) to an Emergency Routing DataBase (ERDB).
[0022] The present invention provides a selective router interface translator for placement between legacy selective routers and their location databases. In this way existing selective routers may remain as they are today, yet be flexible enough to allow the databases they query to be developed to new standards.
[0023] FIG. 1 depicts a selective router interface translator, in accordance with the principles of the present invention.
[0024] In particular, as shown in FIG. 1 , a selective router interface translator 100 preferably includes a National Emergency Number Association (NENA) V3 protocol to Location to Service Translation (LoST) protocol query translator 101, and/or an Automatic Location Identification (ALI) query to NENA V8 protocol query translator 102.
[0025] FIG. 2A shows a selective router interface translator in an emergency services network operable to route an emergency call to the proper public safety answering point (PSAP) based on a current location of the caller obtained from a location information server (LIS) via a Location to Service Translation (LOST) server, in accordance with the principles of the present invention. Location information is obtained from a LIS, while routing instructions are determined via a LoST server.
[0026] In particular, as shown in step A1 of FIG. 2A , an end user 10 dials “9-1-1” and their voice provider reaches the selective router 200 for their geographical area.
[0027] In step A2, the selective router 200 receives the telephone number (TN) of the emergency caller 10, and must look up the TN in an appropriate database to determine which egress trunk group from the selective router 200 to use to complete the emergency call between the emergency caller 10 and the appropriate public safety answering point (PSAP) 20.
[0028] In accordance with the invention, a telephone number query goes out the existing proprietary interface from the selective router 200 to a selective router interface translator 100.
[0029] In step A3, the selective router interface translator 100 receives the telephone number query from the selective router 200. The selective router interface translator 100 then queries the relevant database that stores location information associated with that telephone number. In this example of FIG. 2A , the relevant database that stores location information is a Location Information Server (LIS) 500 that is queried over a NENA V3 interface. In step A4, using the current location information received back from the LIS query of step A3, the selective router interface translator 100 forms an Internet Engineering Task Force (IETF) Location to Service Translation (LoST) protocol query to determine the appropriate routing for the selective router 200.
[0030] In step A5, the selective router interface translator 100 converts the routing information it receives from the IETF LoST query and converts it to the proprietary format used by the selective router 200 that originally queried.
[0031] In step A6, the selective router 200 receives a response to its query and is then able to select the appropriate circuit to complete the call between the emergency caller 10 and the appropriate PSAP 20 routed via the selective router 200.
[0032] FIG. 2B shows a selective router interface translator in an emergency services network operable to route an emergency call to the proper public safety answering point (PSAP) based on a current location of the caller obtained from an automatic location information (ALI) server via an Emergency Routing DataBase (ERDB) server, in accordance with the principles of the present invention.
[0033] In particular, as shown in step B1 of FIG. 2B , an end user 11 dials “9-1-1” and their voice provider reaches the selective router 300 for their geographical area.
[0034] In step B2, the selective router 300 receives the telephone number (TN) of the emergency caller 11, and must look up the TN in an appropriate database to determine which egress trunk group from the selective router 300 to use to complete the emergency call between the emergency caller 11 and the appropriate public safety answering point (PSAP) 21.
[0035] In accordance with the invention, a telephone number query goes out the existing proprietary interface from the selective router 300 to a selective router interface translator 100.
[0036] In step B3, the selective router interface translator 100 receives the telephone number query from the selective router 300. The selective router interface translator 100 then queries the relevant database that stores location information associated with that telephone number. In this example of FIG. 2A , the relevant database that stores location information is an Automatic Location Information (ALI) server 250 that can be queried using NENA E2, PSAP-to-ALI Message (PAM) format, or NENA PSAP to ALI format (described in NENA 04-001).
[0037] In step B4, using the current location information received back from the ALI query of step B3, the selective router interface translator 100 forms a NENA V8 protocol query to an Emergency Routing DataBase (ERDB) 600 to determine the appropriate routing for the selective router 300. An Emergency Routing DataBase (ERDB) 600 is used during a 9-1-1 call to determine routing by providing routing instructions based on location rather than telephone number;
[0038] identifies the emergency services zone (ESZ)/Emergency Service Number (ESN) for the 9-1-1 call location (PSAP); and provides an MSAG Valid Address of the 9-1-1 caller.
[0039] In step B5, the selective router interface translator 100 converts the routing information it receives from the NENA V8 query and converts it to the proprietary format used by the selective router 300 that originally queried.
[0040] In step B6, the selective router 200 receives a response to its query and is then able to select the appropriate circuit to complete the call between the emergency caller 11 and the appropriate PSAP 21 routed via the selective router 300.
[0041] In this way, the present invention provides interaction of existing selective routers with a NENA 08-001 Emergency Routing Database (ERDB) or an IETF Location to Service Translation Server (LoST Server).
[0042] FIG. 3 shows a selective router interface translator in an emergency services network operable to route an emergency call to the proper public safety answering point (PSAP) based on a current location of the caller obtained from either a Location Information Server (LIS) or an automatic location information (ALI) server via either a Location to Service Translation (LoST) server or an Emergency Routing DataBase (ERDB) server, in accordance with the principles of the present invention.
[0043] While FIGS. 2A and 2B show isolated examples of specific selective routers and their relevant location databases and interfaces thereto, FIG. 3 shows that the preferred selective router interface translator has the flexibility to be implemented with any of a plurality of different interface protocol types from respective selective routers. In particular, as shown in FIG. 3 , exemplary messaging translation is provided between existing selective router interfaces 200, 300 and 400 to either a NENA V8 interface or an IETF LoST protocol interface, in accordance with the principles of the present invention.
[0044] The present invention has particular applicability by LECs and/or 9-1-1 service providers operating a selective router.
[0045] Those who would benefit from the invention include operators of current selective routers can adopt the newer routing databases without have to pay for or implement one of the newer protocols for querying a routing database. This extends the life of the current selective router infrastructure operated by local exchange carriers (LECs) and other 9-1-1 service providers.
[0046] While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.
Claims
What is claimed is:
1. A selective router interface translator, comprising:
a NENA V3 protocol interface for communication with a location information server (LIS);
a Location to Service Translation (LoST) protocol interface for communication with a LoST server; and
a NENA V3 protocol to LoST protocol translator to translate a NENA V3 query for location of an emergency caller received over said NENA V3 protocol interface into a LoST protocol query for transmission over said LoST protocol interface.
2. The selective router interface translator according to claim 1, further comprising:
an automatic location identifier (ALI) interface for communication with an ALI;
a NENA V8 protocol interface for communication with an Emergency Routing DataBase (ERDB); and
an ALI to ERDB protocol translator to translate an ALI query for location of an emergency caller received over said ALI interface into an ERDB protocol query for transmission over said ERDB interface.
3. The selective router interface translator according to claim 2, wherein said ALI interface comprises:
a NENA E2 protocol format interface.
4. The selective router interface translator according to claim 2, wherein said ALI interface comprises:
a PSAP-to-ALI Message (PAM) protocol format interface.
5. The selective router interface translator according to claim 2, wherein said ALI interface comprises:
a NENA Public Safety Answering Point (PSAP) to ALI protocol format interface.
6. A selective router interface translator, comprising:
an automatic location identifier (ALI) interface for communication with an ALI;
a NENA V8 protocol interface for communication with an Emergency Routing DataBase (ERDB); and
an ALI to ERDB protocol translator to translate an ALI query for location of an emergency caller received over said ALI interface into an ERDB protocol query for transmission over said ERDB interface.
7. The selective router interface translator according to claim 6, wherein said ALI interface comprises:
a NENA E2 protocol format interface.
8. The selective router interface translator according to claim 6, wherein said ALI interface comprises:
a PSAP-to-ALI Message (PAM) protocol format interface.
9. The selective router interface translator according to claim 6, wherein said ALI interface comprises:
a NENA Public Safety Answering Point (PSAP) to ALI protocol format interface.
Patent Citations (97)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5712900(A) | 1998-01-01 | Maupin | Applicant |
| US5937344(A) | 1999-08-01 | Zicker | Applicant |
| US6134316(A) | 2000-10-01 | Kallioniemi | Applicant |
| US6275937(B1) | 2001-08-01 | Hailpern | Applicant |
| US6321092(B1) | 2001-11-01 | Fitch | Applicant |
| US6330313(B1) | 2001-12-01 | Hunt | Applicant |
| US6526026(B1) | 2003-02-01 | Menon | Applicant |
| US6587691(B1) | 2003-07-01 | Granstam | Applicant |
| US6795444(B1) | 2004-09-01 | Vo | Applicant |
| US6898274(B1) | 2005-05-01 | Galt | Applicant |
| US6985747(B2) | 2006-01-01 | Chithambaram | Applicant |
| US7031724(B2) | 2006-04-01 | Ross | Applicant |
| US7106717(B2) | 2006-09-01 | Rousseau | Applicant |
| US7177397(B2) | 2007-02-01 | McCalmont | Applicant |
| US7177399(B2) | 2007-02-01 | Dawson | Applicant |
| US7330899(B2) | 2008-02-01 | Wong | Applicant |
| US7436785(B1) | 2008-10-01 | McMullen | Applicant |
| US2002/0055924(A1) | 2002-05-01 | Liming | Applicant |
| US2002/0099802(A1) | 2002-07-01 | Marsh | Applicant |
| US2002/0118650(A1) | 2002-08-01 | Jagadeesan | Applicant |
| US2002/0123354(A1) | 2002-09-01 | Nowak | Applicant |
| US2002/0154221(A1) | 2002-10-01 | Ishimaru | Applicant |
| US2003/0012148(A1) | 2003-01-01 | Peters | Applicant |
| US2003/0081752(A1) | 2003-05-01 | Trandal | Applicant |
| US2003/0115261(A1) | 2003-06-01 | Mohammed | Applicant |
| US2003/0125021(A1) | 2003-07-01 | Tell | Applicant |
| US2003/0125493(A1) | 2003-07-01 | Phelan | Applicant |
| US2003/0201931(A1) | 2003-10-01 | Durst | Applicant |
| US2003/0222901(A1) | 2003-12-01 | Houck | Applicant |
| US2004/0041729(A1) | 2004-03-01 | Rowitch | Applicant |
| US2004/0043775(A1) | 2004-03-01 | Kennedy | Applicant |
| US2004/0064500(A1) | 2004-04-01 | Kolar | Applicant |
| US2004/0107143(A1) | 2004-06-01 | Niemi | Applicant |
| US2004/0157175(A1) | 2004-08-01 | Matsumoto | Applicant |
| US2004/0176123(A1) | 2004-09-01 | Chin | Applicant |
| US2004/0181689(A1) | 2004-09-01 | Kiyoto | Applicant |
| US2004/0203919(A1) | 2004-10-01 | Ross | Applicant |
| US2004/0204847(A1) | 2004-10-01 | Yanai | Applicant |
| US2005/0039135(A1) | 2005-02-01 | Othmer | Applicant |
| US2005/0083923(A1) | 2005-04-01 | Kimata | Applicant |
| US2005/0136885(A1) | 2005-06-01 | Kaltsukis | Applicant |
| US2005/0148351(A1) | 2005-07-01 | Reding | Applicant |
| US2005/0148353(A1) | 2005-07-01 | Hicks | Applicant |
| US2005/0181805(A1) | 2005-08-01 | Gallagher | Applicant |
| US2005/0186948(A1) | 2005-08-01 | Gallagher | Applicant |
| US2005/0188078(A1) | 2005-08-01 | Kotzin | Applicant |
| US2005/0195954(A1) | 2005-09-01 | Klein | Applicant |
| US2005/0213537(A1) | 2005-09-01 | Ingimundarson | Applicant |
| US2005/0265318(A1) | 2005-12-01 | Khartabil | Applicant |
| US2005/0271051(A1) | 2005-12-01 | Holloway | Applicant |
| US2005/0272424(A1) | 2005-12-01 | Gallagher | Applicant |
| US2005/0272449(A1) | 2005-12-01 | Gallagher | Applicant |
| US2005/0287979(A1) | 2005-12-01 | Rollender | Applicant |
| US2005/0289097(A1) | 2005-12-01 | Trossen | Applicant |
| US2006/0026288(A1) | 2006-02-01 | Acharya | Applicant |
| US2006/0058049(A1) | 2006-03-01 | McLaughlin | Applicant |
| US2006/0073812(A1) | 2006-04-01 | Punaganti | Applicant |
| US2006/0079236(A1) | 2006-04-01 | Del Pino | Applicant |
| US2006/0135177(A1) | 2006-06-01 | Winterbottom | Applicant |
| US2006/0154665(A1) | 2006-07-01 | Svensson | Applicant |
| US2006/0184617(A1) | 2006-08-01 | Nicholoas | Applicant |
| US2006/0188083(A1) | 2006-08-01 | Breen | Applicant |
| US2006/0189303(A1) | 2006-08-01 | Rollender | Applicant |
| US2006/0205383(A1) | 2006-09-01 | Rollender | Applicant |
| US2006/0236258(A1) | 2006-10-01 | Othmer | Applicant |
| US2007/0003024(A1) | 2007-01-01 | Olivier | Applicant |
| US2007/0008885(A1) | 2007-01-01 | Bonner | Applicant |
| US2007/0022011(A1) | 2007-01-01 | Altberg | Applicant |
| US2007/0027997(A1) | 2007-02-01 | Polk | Applicant |
| US2007/0070980(A1) | 2007-03-01 | Phelps | Applicant |
| US2007/0121601(A1) | 2007-05-01 | Kikinis | Applicant |
| US2007/0162228(A1) | 2007-07-01 | Mitchell | Applicant |
| US2007/0202844(A1) | 2007-08-01 | Wilson | Applicant |
| US2007/0206568(A1) | 2007-09-01 | Silver | Applicant |
| US2007/0206613(A1) | 2007-09-01 | Silver | Applicant |
| US2007/0238448(A1) | 2007-10-01 | Gallagher | Applicant |
| US2007/0242660(A1) | 2007-10-01 | Xu | Applicant |
| US2007/0263610(A1) | 2007-11-01 | Mitchell | Applicant |
| US2007/0293205(A1) | 2007-12-01 | Henderson | Applicant |
| US2008/0037715(A1) | 2008-02-01 | Prozeniuk | Applicant |
| US2008/0063153(A1) | 2008-03-01 | Krivorot | Applicant |
| US2008/0065775(A1) | 2008-03-01 | Polk | Applicant |
| US2008/0081646(A1) | 2008-04-01 | Morin | Applicant |
| US2008/0117859(A1) | 2008-05-01 | Shahidi | Applicant |
| US2008/0186164(A1) | 2008-08-01 | Emigh | Applicant |
| US2008/0228926(A1) | 2008-09-01 | Shiratzky et al. | Applicant |
| US2008/0253535(A1) | 2008-10-01 | Sherry et al. | Examiner |
| US2008/0267172(A1) | 2008-10-01 | Hines | Applicant |
| US2008/0273670(A1) | 2008-11-01 | Dickinson | Examiner |
| US2009/0094270(A1) | 2009-04-01 | Alirez et al. | Examiner |
| US2009/0129396(A1) | 2009-05-01 | Bakker | Applicant |
| US2009/0237210(A1) | 2009-09-01 | Ciesla | Applicant |
| US2009/0284348(A1) | 2009-11-01 | Pfeffer | Applicant |
| US2010/0003954(A1) | 2010-01-01 | Greene | Applicant |
| US2010/0142386(A1) | 2010-06-01 | Snapp | Applicant |
| US2010/0272242(A1) | 2010-10-01 | Croy et al. | Examiner |
| US2011/0149953(A1) | 2011-06-01 | Helgeson et al. | Examiner |
Non-Patent Literature (2)
- International Search Report issued in PCT/US2009/002752, dated Jul. 6, 2009.Applicant
- International Search Report in PCT/US/2010/01938 dated Sep. 30, 2010.Applicant