US20120220257A1 - E911 Call Blocking for Non-Initialized Wireless Telephones - Google Patents

E911 Call Blocking for Non-Initialized Wireless Telephones Download PDF

Info

Publication number
US20120220257A1
US20120220257A1 US13/465,780 US201213465780A US2012220257A1 US 20120220257 A1 US20120220257 A1 US 20120220257A1 US 201213465780 A US201213465780 A US 201213465780A US 2012220257 A1 US2012220257 A1 US 2012220257A1
Authority
US
United States
Prior art keywords
phone
call
mpc
simulated
calls
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/465,780
Inventor
Richard Dickinson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
TeleCommunication Systems Inc
Original Assignee
TeleCommunication Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by TeleCommunication Systems Inc filed Critical TeleCommunication Systems Inc
Priority to US13/465,780 priority Critical patent/US20120220257A1/en
Assigned to TELECOMMUNICATION SYSTEMS, INC. reassignment TELECOMMUNICATION SYSTEMS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DICKINSON, RICHARD
Publication of US20120220257A1 publication Critical patent/US20120220257A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16Communication-related supplementary services, e.g. call-transfer or call-hold
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/22Arrangements for supervision, monitoring or testing
    • H04M3/2281Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/38Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/436Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/5116Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2242/00Special services or facilities
    • H04M2242/04Special services or facilities for emergency applications

Definitions

  • This invention relates generally to wireless services. More particularly, it relates to E911 wireless services.
  • the FCC has mandated that all wireless telephones must be able to dial 9-1-1, even if other service is denied.
  • PSAPs Public Safety Answering Points
  • FIG. 3 shows conventional elements relating to routing of an E911 call from a cell phone.
  • a conventional wireless carrier's mobile switching center (MSC) 502 contacts a Mobile Positioning Center (MPC) 504 to ascertain proper routing of an E911 call.
  • the MPC 504 responds with routing information and the MSC 502 then routes the call to the correct PSAP 208 .
  • the MPC 504 stores the caller's call-back number and location in a dynamic database and relays that information to the PSAP 208 at the appropriate time.
  • uninitialized phones are identified only with a nonfunctional, simulated “callback” number that consists of a portion of the phone's electronic serial number (ESN).
  • ESN electronic serial number
  • the FCC has authorized wireless carriers to terminate service to these phones if the PSAP identifies the phone as a harrasser.
  • Some MSCs are capable of blocking single ESNs, while others are less flexible and must block all uninitialized phones. The effort to block these calls at the MSC 502 is time consuming and troublesome.
  • disadvantages of the current solutions include: (1) It requires time consuming manual intervention to block identified calls; (2) Once a call is blocked, it remains blocked until a technician manually restores service; and (3) Some wireless switches cannot block individual telephones.
  • a method of blocking an undesirable call from being routed to an intended recipient comprises associating a simulated callback phone number with the undesirable call.
  • a mobile positioning center (MPC) is queried for routing instructions for the undesirable call.
  • the simulated callback phone number is compared with a known list of callback phone numbers to be blocked. If a match is made by the comparing, routing of the undesirable call to the intended recipient is blocked at the mobile positioning center (MPC).
  • Apparatus for blocking an undesirable wireless call from being routed comprises a blocked phone number list maintained by a mobile positioning center (MPC).
  • a module compares a callback number associated with a received query for routing instructions to entries in the blocked phone number list. If a match is made between the callback number and an entry in the blocked phone number list, routing to an intended destination is refused.
  • FIG. 1 shows exemplary network elements relevant to call blocking for E911 harassment calls, in accordance with the principles of the present invention.
  • FIG. 2 shows exemplary messaging to accomplish call blocking for E911 harassment calls, in the exemplary system shown in FIG. 1 .
  • FIG. 3 shows conventional elements relating to routing of an E911 call from a cell phone.
  • calls from a phone identified as being a source of harassing or other undesirable phone calls are blocked at a mobile positioning center (MPC), rather than at the MSC as in conventional systems.
  • MPC mobile positioning center
  • a call record detail can be obtained from the MPC revealing a simulated “callback phone number” of the mobile phone identified to have made a harassing call.
  • the MPC then intercepts all future incoming calls from that phone corresponding to the simulated callback phone number, and routes this and any future calls therefrom to a recording that advises the harasser that the phone has been identified as a source of harassing phone calls and is now blocked.
  • the recording can also advise the caller how to restore service.
  • the MPC sets a timer to automatically restore service after a designated length of time.
  • FIG. 1 shows exemplary network elements relevant to call blocking for E911 harassment calls, in accordance with the principles of the present invention.
  • the disclosed wireless infrastructure is implemented to support subsequent 9-1-1 calls.
  • a mobile phone 173 communicates with a given cell site 174 .
  • the cell site 174 communicates with a mobile switching center (MSC) 202 in a wireless carrier's network.
  • the mobile switching center (MSC) 202 is the wireless equivalent to a landline end office.
  • the MSC 202 includes a simulated callback phone number module 202 a.
  • the simulated callback phone number module 202 a provides a simulated callback number for a given wireless phone calling 911.
  • the simulated callback number comprises “911” plus the last 7 digits of the ESN (totaling 10 digits). This format is typical per current industry standards, but can be modified in any manner that uniquely identifies the telephone.
  • An appropriate mobile positioning center 204 also communicates with the ALI database 210 and the coordinate routing database (CRDB) 212 .
  • the mobile positioning center (MPC) 204 is the call routing “mastermind” that maintains a database of cellular towers and which PSAPs should receive calls from which cellular tower.
  • the MSC 202 relies upon the MPC 204 to determine which selective router should receive the E911 call.
  • the MPC 204 also communicates with the PSAP 208 to inform the PSAP 208 of the caller's phone number and address.
  • FIG. 2 shows exemplary messaging to accomplish call blocking for E911 harassment calls, in the exemplary system shown in FIG. 1 .
  • an initial harassing call is placed from the uninitialized mobile phone 173 through a given cell site 174 .
  • the wireless harassment call is eventually designated as a harassing call, and handled appropriately.
  • the receiving cell site routes the 911 call to the MSC 202 .
  • the MSC 202 receives the call.
  • the simulated callback phone number module 202 a is activated, and in response appends a 10-digit simulated callback phone number to the E911 call (“911” plus the last 7 digits of the ESN of the unitialized phone.)
  • the MSC 202 queries the MPC 204 for call routing instructions for the E911 call, which at that point includes the 10-digit simulated callback phone number.
  • the query from the MSC 202 includes not only the simulated callback number (911+last 7 digits of the ESN), but also the cellular tower from where the call originated.
  • the MSC 202 queries the MPC 204 for call routing instructions, and provides to the MPC 204 the simulated callback number across dedicated data circuits 102 .
  • the query from the MSC 202 includes not only the simulated callback number (911+last 7 digits of the ESN), but also the cellular tower from where the call originated.
  • the MPC queries the Harrasser Number Data Base 216 to see if the simulated callback number is listed. In the absence of a match in the Harrasser Number Database 216 , the MPC 204 queries a coordinate routing database (CRDB) 212 , which determines that calls originiating from which cell towers should be routed to which PSAPs.
  • CRDB coordinate routing database
  • the MPC 204 upon determining the appropriate PSAP to receive the call, responds with appropriate call routing instructions. These instructions consist of a pseudo automatic number identifier (pANI) that relates to a specific trunk group 103 (e.g., CAMA or SS7 voice trunk) between the MSC 202 and the selective router 206 .
  • pANI pseudo automatic number identifier
  • This pANI is, e.g., a 10-digit number compatible with the existing selective router 206 that serves that PSAP 208 .
  • the ESRK is preferably unique to that PSAP 208 .
  • the MSC 202 directs the 911 call to the designated selective router 206 via the identified trunk group 103 .
  • the E911 call is routed to the appropriate public safety answering point (PSAP) via the selective router 206 , which has been provisioned to relate the specified pANI to a specific trunk group 104 that connects the selective router 206 to the intended PSAP 208 .
  • PSAP public safety answering point
  • step 104 upon receipt of the emergency call with the specified pANI, the selective router 206 delivers the call using existing E911 infrastructure to the PSAP 208 .
  • the selective router 206 previously provisioned as is otherwise conventional to recognize the pANI in the ANI field of the CAMA or SS7 voice call, routes the call to the appropriate PSAP.
  • the PSAP 208 receives the voice call and using the pANI, queries the ASI database 210 for the location and call-back information.
  • the ALI database 210 steers the pANI to the appropriate MPC 204 , which responds to the ALI query with the simulated “callback” number of the originating phone.
  • the E911 call continues on to an ANI/ALI controller 275 or similar device within the PSAP 208 , which communicates with an automatic location identifier (ALI) database 210 , and ultimately on to a PSAP workstation manned by appropriate emergency personnel.
  • the ALI database 210 is provisioned with the pANI so that queries using that pANI are routed to the MPC that initially issued the pANI.
  • the ANI/ALI controller 275 queries the ALI 210 for ALI data related to the pANI.
  • the ALI 210 routes the query to the MPC 204 via existing data circuits 105 .
  • the MPC 204 responds with the simulated callback number of the uninitialized phone.
  • TCP/IP data circuits 105 must be ordered and installed between the MPC 204 and the various ALI databases 210 .
  • Web based Graphical User Interface 107 with appropriate access restrictions must be installed at the Harrassment Number Database 216 .
  • This interface is used for the PSAPs to identify harassing telephones according to their simulated callback number.
  • this communications can be verbal, via fax, or other device between authorized personnel at the PSAP and personnel managing the Harrasser Number Database 216 .
  • step 106 the harasser harasses.
  • the harasser might merely breath heavily into the phone, whisper juvenile obscenities, whatever, and typically refuse to hang up.
  • step 107 the PSAP dispatcher terminates the call, and in accordance with the principles of the present invention, notifies the MPC 204 of the simulated “callback” number associated with a harassing or prank 911 phone call.
  • step 108 personnel at the MPC 204 list the reported simulated “callback” number in a suitable database of calls to be blocked from PSAPs in the future.
  • the database may be a separate, special database, or may be integrated within a larger database. This database is represented by the harasser number database 216 shown in FIGS. 1 and 2 .
  • personnel at the MPC 204 also assign a “timeout” period after which the simulated callback number that was listed in the harassing database is purged from the harassing database. At this point, the phone 173 would be free to call again, even as a harasser. However, given that a predefined period of time has elapsed since the last harassing call has been given from that phone 173 , it is unlikely that the original harasser would harass again from the phone 173 .
  • the timeout period may alternatively be automatically set without the need for operator intervention.
  • Secure IP interfaces may be made available to PSAP personnel who invoke the timeout period directly.
  • the callback number may be maintained in the blocked number database but de-activated or enabled in some way that maintains a record of the previous harassing 911 phone call made using that callback number. This allows normal operation of the wireless phone, but also a record of the undesirable harassing call made from that phone 173 .
  • step 109 the harasser might again dial 911.
  • the MSC 202 activates the simulated callback phone number module 202 a and appends a 10-digit simulated callback phone number to the 911 call.
  • the MSC 202 routes the call to the MPC 204 per otherwise conventional processes.
  • the MPC 204 compares the simulated callback phone number associated with the latest E911 call to entries in the harasser number database 216 .
  • the MPC 204 recognizes the simulated “callback” number in the special harassing 911 dialer's database 216 .
  • the MPC 204 responds with routing instructions to a 10-digit PSTN number of a pre-recorded announcement message element 279 instead of routing information to the otherwise designated PSAP 208 .
  • the pre-recorded message played by the recording element 279 can, of course, be programmed to say anything.
  • the pre-recorded message might state something like: “911 calls from this phone have been blocked because this phone has been identified by law enforcement authorities as a source of telephone harassment. To restore 911 service, please contact XYZ Wireless. Goodbye.”
  • step 111 after a given “timeout” period of time later (e.g., several hours, one or more days, etc. later), the relevant entry of the simulated callback number corresponding to the harassing 911 dialer's phone 173 is automatically purged from the harasser number database 216 , and normal 911 service is thus restored.
  • a record of the phone having been listed in the harasser number database 216 along with pertinent information such as when the harassing call was made, the location of the phone when the harassing call was made, etc. may be recorded for later review by appropriate personnel.
  • inventive blocking technology will work to block calls from any wireless phone presumably desired not to be routed to a PSAP.
  • the example of an uninitialized phone is used because uninitialized phones are the most commonly used type phones for harassment, and also are the most difficult to trace.
  • the present invention provides technology that results in the reduction of the waste of 911 emergency service resources caused by prank or harassing 911 calls made from uninitialized wireless devices.
  • the present invention might also be credited with the capability of saving lives that might otherwise be lost due to the delay or even failure of a legitimate 911 caller from a wireless device to reach 911 responders caused while the relevant PSAP 208 is tied up dealing with a prankster or harasser.
  • the principles of the present invention can also be implemented to route specific legitimate callers to specific 911 resources.
  • a person with a heart condition may purchase a special wireless phone solely for the purpose of dialing 911 in the event of a heart attack.
  • their phone number may be maintained in a special database similar to the harassing 911 caller's database 216 .
  • any/all 911 calls made from that particular phone with a phone number previously entered into the special database can be routed directly to a medical responder or other designated phone (e.g., their surgeon, etc.)

Abstract

Calls from a phone identified as being a source of harassing or other undesirable phone calls are blocked at a mobile positioning center (MPC). Upon request by the PSAP, a call record detail can be obtained from the MPC revealing a simulated “callback phone number”. The MPC then intercepts all future incoming calls from that simulated callback phone number and routes them to a recording that advises the harasser that the phone has been identified as a harasser and is now blocked. The recording can also advise the caller how to restore service. In a preferred embodiment, the MPC sets a timer to automatically restore service after a designated length of time.

Description

  • This application claims priority from U.S. Provisional Appl. No. 60/684,554, filed May 26, 2005, entitled “E911 Call Blocking For Non-Initialized Wireless Telephones”, by Richard Dickinson, the entirety of which is expressly incorporated herein by reference.
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • This invention relates generally to wireless services. More particularly, it relates to E911 wireless services.
  • 2. Background of the Related Art
  • The FCC has mandated that all wireless telephones must be able to dial 9-1-1, even if other service is denied. This includes uninitialized phones (i.e., cellular phones that have not yet been activated by the wireless carrier). Uninitialized phones have no assigned phone number and are virtually untraceable. Because of this, they have become a popular way for mischief-makers to place hundreds or thousands of harassment calls to Public Safety Answering Points (PSAPs), thereby compromising the ability of the PSAPs to respond to real emergencies.
  • FIG. 3 shows conventional elements relating to routing of an E911 call from a cell phone.
  • In particular, as shown in FIG. 3, a conventional wireless carrier's mobile switching center (MSC) 502 contacts a Mobile Positioning Center (MPC) 504 to ascertain proper routing of an E911 call. The MPC 504 responds with routing information and the MSC 502 then routes the call to the correct PSAP 208. The MPC 504 stores the caller's call-back number and location in a dynamic database and relays that information to the PSAP 208 at the appropriate time.
  • Currently, uninitialized phones are identified only with a nonfunctional, simulated “callback” number that consists of a portion of the phone's electronic serial number (ESN). The FCC has authorized wireless carriers to terminate service to these phones if the PSAP identifies the phone as a harrasser. Some MSCs are capable of blocking single ESNs, while others are less flexible and must block all uninitialized phones. The effort to block these calls at the MSC 502 is time consuming and troublesome.
  • Thus, disadvantages of the current solutions include: (1) It requires time consuming manual intervention to block identified calls; (2) Once a call is blocked, it remains blocked until a technician manually restores service; and (3) Some wireless switches cannot block individual telephones.
  • Moreover, once blocked, the subsequent legitimate user of the phone is not advised that the phone has been blocked.
  • There is a need for improved technology for blocking E911 calls from a non-initialized wireless telephone deemed to have previously been used to make a harassing or illegitimate call to 9-1-1.
  • SUMMARY OF THE INVENTION
  • In accordance with the principles of the present invention, a method of blocking an undesirable call from being routed to an intended recipient comprises associating a simulated callback phone number with the undesirable call. A mobile positioning center (MPC) is queried for routing instructions for the undesirable call. The simulated callback phone number is compared with a known list of callback phone numbers to be blocked. If a match is made by the comparing, routing of the undesirable call to the intended recipient is blocked at the mobile positioning center (MPC).
  • Apparatus for blocking an undesirable wireless call from being routed according to yet another aspect of the invention comprises a blocked phone number list maintained by a mobile positioning center (MPC). A module compares a callback number associated with a received query for routing instructions to entries in the blocked phone number list. If a match is made between the callback number and an entry in the blocked phone number list, routing to an intended destination is refused.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 shows exemplary network elements relevant to call blocking for E911 harassment calls, in accordance with the principles of the present invention.
  • FIG. 2 shows exemplary messaging to accomplish call blocking for E911 harassment calls, in the exemplary system shown in FIG. 1.
  • FIG. 3 shows conventional elements relating to routing of an E911 call from a cell phone.
  • DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS
  • In accordance with the principles of the present invention, calls from a phone identified as being a source of harassing or other undesirable phone calls are blocked at a mobile positioning center (MPC), rather than at the MSC as in conventional systems. Upon request by the PSAP (e.g., a PSAP designated as servicing the location from which the harassing call originates or is registered in), a call record detail can be obtained from the MPC revealing a simulated “callback phone number” of the mobile phone identified to have made a harassing call. The MPC then intercepts all future incoming calls from that phone corresponding to the simulated callback phone number, and routes this and any future calls therefrom to a recording that advises the harasser that the phone has been identified as a source of harassing phone calls and is now blocked. The recording can also advise the caller how to restore service. In a preferred embodiment, the MPC sets a timer to automatically restore service after a designated length of time.
  • FIG. 1 shows exemplary network elements relevant to call blocking for E911 harassment calls, in accordance with the principles of the present invention. The disclosed wireless infrastructure is implemented to support subsequent 9-1-1 calls.
  • In particular, as shown in FIG. 1, a mobile phone 173 communicates with a given cell site 174. The cell site 174 communicates with a mobile switching center (MSC) 202 in a wireless carrier's network. The mobile switching center (MSC) 202 is the wireless equivalent to a landline end office.
  • Importantly, according to the invention, the MSC 202 includes a simulated callback phone number module 202 a. The simulated callback phone number module 202 a provides a simulated callback number for a given wireless phone calling 911. In the disclosed embodiments, the simulated callback number comprises “911” plus the last 7 digits of the ESN (totaling 10 digits). This format is typical per current industry standards, but can be modified in any manner that uniquely identifies the telephone.
  • An appropriate mobile positioning center 204 also communicates with the ALI database 210 and the coordinate routing database (CRDB) 212. The mobile positioning center (MPC) 204 is the call routing “mastermind” that maintains a database of cellular towers and which PSAPs should receive calls from which cellular tower. The MSC 202 relies upon the MPC 204 to determine which selective router should receive the E911 call. The MPC 204 also communicates with the PSAP 208 to inform the PSAP 208 of the caller's phone number and address.
  • FIG. 2 shows exemplary messaging to accomplish call blocking for E911 harassment calls, in the exemplary system shown in FIG. 1. In particular, as shown in FIG. 2, an initial harassing call is placed from the uninitialized mobile phone 173 through a given cell site 174. The wireless harassment call is eventually designated as a harassing call, and handled appropriately.
  • As shown in step 101 of FIG. 2, the receiving cell site routes the 911 call to the MSC 202. The MSC 202 receives the call.
  • In response to receipt of the E911 wireless call, the simulated callback phone number module 202 a is activated, and in response appends a 10-digit simulated callback phone number to the E911 call (“911” plus the last 7 digits of the ESN of the unitialized phone.)
  • The MSC 202 then queries the MPC 204 for call routing instructions for the E911 call, which at that point includes the 10-digit simulated callback phone number. Preferably, the query from the MSC 202 includes not only the simulated callback number (911+last 7 digits of the ESN), but also the cellular tower from where the call originated.
  • Thus, the MSC 202 queries the MPC 204 for call routing instructions, and provides to the MPC 204 the simulated callback number across dedicated data circuits 102. Preferably, the query from the MSC 202 includes not only the simulated callback number (911+last 7 digits of the ESN), but also the cellular tower from where the call originated. The MPC queries the Harrasser Number Data Base 216 to see if the simulated callback number is listed. In the absence of a match in the Harrasser Number Database 216, the MPC 204 queries a coordinate routing database (CRDB) 212, which determines that calls originiating from which cell towers should be routed to which PSAPs.
  • As shown in step 102, upon determining the appropriate PSAP to receive the call, the MPC 204 responds with appropriate call routing instructions. These instructions consist of a pseudo automatic number identifier (pANI) that relates to a specific trunk group 103 (e.g., CAMA or SS7 voice trunk) between the MSC 202 and the selective router 206. This pANI is, e.g., a 10-digit number compatible with the existing selective router 206 that serves that PSAP 208. The ESRK is preferably unique to that PSAP 208.
  • In step 103, the MSC 202 directs the 911 call to the designated selective router 206 via the identified trunk group 103. The E911 call is routed to the appropriate public safety answering point (PSAP) via the selective router 206, which has been provisioned to relate the specified pANI to a specific trunk group 104 that connects the selective router 206 to the intended PSAP 208.
  • In step 104, upon receipt of the emergency call with the specified pANI, the selective router 206 delivers the call using existing E911 infrastructure to the PSAP 208. The selective router 206, previously provisioned as is otherwise conventional to recognize the pANI in the ANI field of the CAMA or SS7 voice call, routes the call to the appropriate PSAP.
  • In step 105, per current existing technology, the PSAP 208 receives the voice call and using the pANI, queries the ASI database 210 for the location and call-back information. The ALI database 210 steers the pANI to the appropriate MPC 204, which responds to the ALI query with the simulated “callback” number of the originating phone.
  • Thus, the E911 call continues on to an ANI/ALI controller 275 or similar device within the PSAP 208, which communicates with an automatic location identifier (ALI) database 210, and ultimately on to a PSAP workstation manned by appropriate emergency personnel. The ALI database 210 is provisioned with the pANI so that queries using that pANI are routed to the MPC that initially issued the pANI. The ANI/ALI controller 275 queries the ALI 210 for ALI data related to the pANI. The ALI 210 routes the query to the MPC 204 via existing data circuits 105. The MPC 204 responds with the simulated callback number of the uninitialized phone.
  • TCP/IP data circuits 105 must be ordered and installed between the MPC 204 and the various ALI databases 210.
  • Web based Graphical User Interface 107 with appropriate access restrictions must be installed at the Harrassment Number Database 216. This interface is used for the PSAPs to identify harassing telephones according to their simulated callback number. Alternatively, this communications can be verbal, via fax, or other device between authorized personnel at the PSAP and personnel managing the Harrasser Number Database 216.
  • In step 106, the harasser harasses. For example, the harasser might merely breath heavily into the phone, whisper juvenile obscenities, whatever, and typically refuse to hang up.
  • In step 107, the PSAP dispatcher terminates the call, and in accordance with the principles of the present invention, notifies the MPC 204 of the simulated “callback” number associated with a harassing or prank 911 phone call.
  • In step 108, personnel at the MPC 204 list the reported simulated “callback” number in a suitable database of calls to be blocked from PSAPs in the future. The database may be a separate, special database, or may be integrated within a larger database. This database is represented by the harasser number database 216 shown in FIGS. 1 and 2.
  • In a preferred embodiment, personnel at the MPC 204 also assign a “timeout” period after which the simulated callback number that was listed in the harassing database is purged from the harassing database. At this point, the phone 173 would be free to call again, even as a harasser. However, given that a predefined period of time has elapsed since the last harassing call has been given from that phone 173, it is unlikely that the original harasser would harass again from the phone 173.
  • The timeout period may alternatively be automatically set without the need for operator intervention. Secure IP interfaces may be made available to PSAP personnel who invoke the timeout period directly.
  • As an alternative, rather than being purged, the callback number may be maintained in the blocked number database but de-activated or enabled in some way that maintains a record of the previous harassing 911 phone call made using that callback number. This allows normal operation of the wireless phone, but also a record of the undesirable harassing call made from that phone 173.
  • In step 109, the harasser might again dial 911. Again the MSC 202 activates the simulated callback phone number module 202 a and appends a 10-digit simulated callback phone number to the 911 call. Again the MSC 202 routes the call to the MPC 204 per otherwise conventional processes.
  • However, this time, as shown in step 110, the MPC 204 compares the simulated callback phone number associated with the latest E911 call to entries in the harasser number database 216. In the given scenario, this time the MPC 204 recognizes the simulated “callback” number in the special harassing 911 dialer's database 216. As a result, the MPC 204, this time, responds with routing instructions to a 10-digit PSTN number of a pre-recorded announcement message element 279 instead of routing information to the otherwise designated PSAP 208.
  • The pre-recorded message played by the recording element 279 can, of course, be programmed to say anything. As an example, the pre-recorded message might state something like: “911 calls from this phone have been blocked because this phone has been identified by law enforcement authorities as a source of telephone harassment. To restore 911 service, please contact XYZ Wireless. Goodbye.”
  • In step 111, after a given “timeout” period of time later (e.g., several hours, one or more days, etc. later), the relevant entry of the simulated callback number corresponding to the harassing 911 dialer's phone 173 is automatically purged from the harasser number database 216, and normal 911 service is thus restored. Of course, a record of the phone having been listed in the harasser number database 216 along with pertinent information such as when the harassing call was made, the location of the phone when the harassing call was made, etc., may be recorded for later review by appropriate personnel.
  • Note that the inventive blocking technology will work to block calls from any wireless phone presumably desired not to be routed to a PSAP. The example of an uninitialized phone is used because uninitialized phones are the most commonly used type phones for harassment, and also are the most difficult to trace.
  • The present invention provides technology that results in the reduction of the waste of 911 emergency service resources caused by prank or harassing 911 calls made from uninitialized wireless devices. In extreme emergencies where time saves lives, the present invention might also be credited with the capability of saving lives that might otherwise be lost due to the delay or even failure of a legitimate 911 caller from a wireless device to reach 911 responders caused while the relevant PSAP 208 is tied up dealing with a prankster or harasser.
  • The principles of the present invention can also be implemented to route specific legitimate callers to specific 911 resources. For example, a person with a heart condition may purchase a special wireless phone solely for the purpose of dialing 911 in the event of a heart attack. At the prior request of the caller, their phone number may be maintained in a special database similar to the harassing 911 caller's database 216. Then, in accordance with the principles of the present invention, any/all 911 calls made from that particular phone with a phone number previously entered into the special database can be routed directly to a medical responder or other designated phone (e.g., their surgeon, etc.)
  • 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 (2)

1. A method of blocking an undesirable call from being routed to an intended recipient, comprising:
associating a simulated callback phone number with said undesirable call;
querying a mobile positioning center (MPC) for routing instructions for said undesirable call;
comparing said simulated callback phone number with a known list of callback phone numbers to be blocked; and
if a match is made by said comparing, blocking routing of said undesirable call to said intended recipient at said mobile positioning center (MPC).
2-18. (canceled)
US13/465,780 2005-05-26 2012-05-07 E911 Call Blocking for Non-Initialized Wireless Telephones Abandoned US20120220257A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/465,780 US20120220257A1 (en) 2005-05-26 2012-05-07 E911 Call Blocking for Non-Initialized Wireless Telephones

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US68455405P 2005-05-26 2005-05-26
US11/440,084 US8175570B2 (en) 2005-05-26 2006-05-25 E911 call blocking for non-initialized wireless telephones
US13/465,780 US20120220257A1 (en) 2005-05-26 2012-05-07 E911 Call Blocking for Non-Initialized Wireless Telephones

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/440,084 Continuation US8175570B2 (en) 2005-05-26 2006-05-25 E911 call blocking for non-initialized wireless telephones

Publications (1)

Publication Number Publication Date
US20120220257A1 true US20120220257A1 (en) 2012-08-30

Family

ID=37767322

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/440,084 Expired - Fee Related US8175570B2 (en) 2005-05-26 2006-05-25 E911 call blocking for non-initialized wireless telephones
US13/465,780 Abandoned US20120220257A1 (en) 2005-05-26 2012-05-07 E911 Call Blocking for Non-Initialized Wireless Telephones

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/440,084 Expired - Fee Related US8175570B2 (en) 2005-05-26 2006-05-25 E911 call blocking for non-initialized wireless telephones

Country Status (1)

Country Link
US (2) US8175570B2 (en)

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8918073B2 (en) * 2002-03-28 2014-12-23 Telecommunication Systems, Inc. Wireless telecommunications location based services scheme selection
US20030186699A1 (en) * 2002-03-28 2003-10-02 Arlene Havlark Wireless telecommunications location based services scheme selection
US8660573B2 (en) 2005-07-19 2014-02-25 Telecommunications Systems, Inc. Location service requests throttling
US8532266B2 (en) * 2006-05-04 2013-09-10 Telecommunication Systems, Inc. Efficient usage of emergency services keys
US8208605B2 (en) 2006-05-04 2012-06-26 Telecommunication Systems, Inc. Extended efficient usage of emergency services keys
US9413889B2 (en) * 2007-09-18 2016-08-09 Telecommunication Systems, Inc. House number normalization for master street address guide (MSAG) address matching
US8244204B1 (en) * 2007-12-11 2012-08-14 Cellco Partnership Timed override of incoming call restrictions to facilitate callback after an emergency call
US7983652B1 (en) 2008-01-10 2011-07-19 At&T Mobility Ii Llc Emergency call notification for network services
US8576991B2 (en) * 2008-03-19 2013-11-05 Telecommunication Systems, Inc. End-to-end logic tracing of complex call flows in a distributed call system
US7903587B2 (en) 2008-05-30 2011-03-08 Telecommunication Systems, Inc. Wireless emergency services protocols translator between ansi-41 and VoIP emergency services protocols
US20100046720A1 (en) * 2008-08-22 2010-02-25 Gerhard Geldenbott Point-in-poly routing for voice over internet protocol (VoIP) emergency calls with embedded geographic location information
US8688087B2 (en) 2010-12-17 2014-04-01 Telecommunication Systems, Inc. N-dimensional affinity confluencer
US8467381B1 (en) * 2011-04-13 2013-06-18 Securus Technologies, Inc. Crime reporting in a controlled-environment facility
WO2013048551A1 (en) * 2011-09-30 2013-04-04 Telecommunication Systems, Inc. Unique global identifier for minimizing prank 911 calls
US9264537B2 (en) 2011-12-05 2016-02-16 Telecommunication Systems, Inc. Special emergency call treatment based on the caller
WO2014028712A1 (en) 2012-08-15 2014-02-20 Telecommunication Systems, Inc. Device independent caller data access for emergency calls
US9332109B2 (en) * 2012-08-15 2016-05-03 Scott Alexander Strozier Software routine and methods for implementing routine to extend time to trace a phone call
US10498774B2 (en) 2017-03-24 2019-12-03 T-Mobile Usa, Inc. Systems and methods for improved E911 call handling
US10498892B2 (en) 2017-03-24 2019-12-03 T-Mobile Usa, Inc. Optimized call handling during E911 calls
US10084914B1 (en) * 2017-03-24 2018-09-25 T-Mobile Usa, Inc. Guard timer to optimize E911 call handling
US11095681B2 (en) * 2018-02-28 2021-08-17 Motorola Solutions, Inc. Method to handle the distributed denial-of-service attacks 911 answering centers
CN110011905B (en) * 2019-04-11 2021-09-14 腾讯科技(深圳)有限公司 Communication information processing method, device and equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040185823A1 (en) * 2003-03-17 2004-09-23 Chin Mary Wonmon Method for processing emergency calls initiated by wireless phones
US20040203575A1 (en) * 2003-01-13 2004-10-14 Chin Mary W. Method of recognizing fraudulent wireless emergency service calls
US7031714B1 (en) * 2001-11-14 2006-04-18 Sprint Spectrum L.P. Method and system for managing communication based on location
US20060135132A1 (en) * 2004-12-21 2006-06-22 Lucent Technologies, Inc. Storing anti-spam black lists
US7412049B1 (en) * 2002-05-31 2008-08-12 At&T Delaware Intellectual Property, Inc. System and method for real-time blocking of a telephone call

Family Cites Families (86)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4625081A (en) 1982-11-30 1986-11-25 Lotito Lawrence A Automated telephone voice service system
US7266186B1 (en) 1994-01-05 2007-09-04 Intellect Wireless Inc. Method and apparatus for improved paging receiver and system
US6456852B2 (en) 1997-01-08 2002-09-24 Trafficmaster Usa, Inc. Internet distributed real-time wireless location database
US6181736B1 (en) 1997-03-25 2001-01-30 Nxi Communications, Inc. Network communication system
US6128481A (en) 1997-10-22 2000-10-03 Telefonaktiebolaget L M Ericsson (Publ) System and method of routing emergency services calls in a radio telecommunications network
US6047182A (en) 1997-10-29 2000-04-04 Ericsson Inc. Channel resource utilization during a positioning handover
US6529722B1 (en) 1998-06-19 2003-03-04 Microdata System and method for enhanced 9-1-1 address development, maintenance and call routing using road access zones
US20070121601A1 (en) 1998-09-24 2007-05-31 Genesys Telecommunications Laboratories, Inc Integrating SIP Control Messaging into Existing Communication Center Routing Infrastructure
US7366157B1 (en) 1998-11-17 2008-04-29 Ericsson Inc. Methods and system for routing emergency calls through the internet
US6321091B1 (en) 1999-07-29 2001-11-20 Bryan Holland Portable locator system and method
US6529500B1 (en) 1999-08-26 2003-03-04 Verizon Laboratories Inc. Unified messaging notification
US20010040886A1 (en) 2000-01-07 2001-11-15 Ray Jimenez Methods and apparatus for forwarding audio content using an audio web retrieval telephone system
US6415018B1 (en) 2000-02-08 2002-07-02 Lucent Technologies Inc. Telecommunication system and method for handling special number calls having geographic sensitivity
US6650901B1 (en) 2000-02-29 2003-11-18 3Com Corporation System and method for providing user-configured telephone service in a data network telephony system
GB2361389B (en) 2000-04-15 2004-01-28 Ericsson Telefon Ab L M Telecommunications system
US7796998B1 (en) 2000-08-01 2010-09-14 At&T Intellectual Property, I, L.P. Method and system for delivery of a calling party's location
US6799049B1 (en) 2000-12-19 2004-09-28 Bellsouth Intellectual Property Corporation System and method for tracking movement of a wireless device
US6744858B1 (en) 2001-01-26 2004-06-01 Telcontrol, Inc. System and method for supporting multiple call centers
US6744856B2 (en) 2001-01-31 2004-06-01 Lucent Technologies Inc. Method and apparatus for servicing emergency calls from a data network
US6563910B2 (en) 2001-02-26 2003-05-13 Royal Thoughts, Llc Emergency response information distribution
KR100369803B1 (en) 2001-03-10 2003-02-05 삼성전자 주식회사 Packet voice call service method in wireless telecommunication network and network architecture therefor
US6427001B1 (en) 2001-06-07 2002-07-30 Bellsouth Intellectual Property Corporation System and method for notification of 911 telephone calls using a link monitoring system
US6996087B2 (en) 2001-07-31 2006-02-07 Lucent Technologies Inc. Communication system including an interworking mobile switching center for call termination
US6678357B2 (en) 2001-09-26 2004-01-13 Siemens Information And Communication Networks, Inc. Internet protocol (IP) emergency connections (ITEC) telephony
US7233781B2 (en) 2001-10-10 2007-06-19 Ochoa Optics Llc System and method for emergency notification content delivery
US6813264B2 (en) 2001-11-02 2004-11-02 Qualcomm, Incorporated System and method for routing voice over IP calls
US20030109245A1 (en) 2001-11-05 2003-06-12 Mccalmont Patti L Routing of emergency calls based on geographic location of originating telephone end office
US6771742B2 (en) 2001-11-05 2004-08-03 Intrado Inc. Geographic routing of emergency service call center emergency calls
KR100424462B1 (en) 2001-11-21 2004-03-26 삼성전자주식회사 Apparatus for displaying position information and direction in portable terminal and method same
US7136466B1 (en) 2002-05-30 2006-11-14 Bellsouth Intellectual Property Corporation DSL integrated call waiting
US20040203568A1 (en) 2002-07-20 2004-10-14 Kirtland Kenneth P. Computerized warning system interface and method
US8032149B2 (en) 2002-08-29 2011-10-04 Andrew Llc Tasking and reporting method and implementation for wireless appliance location systems
AU2003284191A1 (en) 2002-10-25 2004-11-23 Andrew Corporation System and method for geo-location of mobile appliances using diverse standard tasking and reporting
AU2002368323A1 (en) 2002-11-08 2004-06-07 Nokia Corporation Method, terminal device and system allowing for handling location services independently from a cellular communication system
US7617287B2 (en) 2002-11-27 2009-11-10 Rga Intl, Inc. Cellular messaging alert method and system
US6927727B2 (en) 2003-01-21 2005-08-09 Monica Cleghorn Internet protocol based 911 system
US20040176123A1 (en) 2003-01-30 2004-09-09 Chin Frances Mu-Fen Communicating with public safety answering points via character based messages
US8490129B2 (en) 2003-01-31 2013-07-16 Qwest Communications International Inc. Methods, systems and apparatus for selectively distributing urgent public information
US7194249B2 (en) 2003-01-31 2007-03-20 Qwest Communications International Inc. Methods, systems and apparatus for providing urgent public information
US8050281B2 (en) 2003-01-31 2011-11-01 Qwest Communications International Inc. Alert gateway, systems and methods
US7233799B2 (en) 2003-02-24 2007-06-19 Polaris Wireless, Inc. Location estimation of wireless terminals based on combinations of signal strength measurements and geometry-of-arrival measurements
US7171220B2 (en) 2003-03-14 2007-01-30 Meshnetworks, Inc. System and method for analyzing the precision of geo-location services in a wireless network terminal
US6963557B2 (en) 2003-03-29 2005-11-08 Intrado Inc. System and method for routing telephone calls involving internet protocol network
US7450566B2 (en) 2003-06-05 2008-11-11 Oracle International Corporation Apparatus and method for providing a unified telephony solution
US20040247090A1 (en) 2003-06-05 2004-12-09 Nurmela Wayne Denis Process for providing alert notification to communication devices
US7177623B2 (en) 2003-07-02 2007-02-13 The United States Of America As Represented By The Secretary Of The Army Localized cellular awareness and tracking of emergencies
US7716585B2 (en) 2003-08-28 2010-05-11 Microsoft Corporation Multi-dimensional graphical display of discovered wireless devices
US20070019614A1 (en) 2003-09-09 2007-01-25 Klaus Hoffmann Method for providing a user interaction dialogue (uid) prior to connection acceptance by the called user
US7027564B2 (en) 2003-09-22 2006-04-11 Foundry Networks, Inc. System, method and apparatus for supporting E911 emergency services in a data communications network
US7221928B2 (en) 2003-10-01 2007-05-22 Laird Mark D Mobile emergency notification system
US7440442B2 (en) 2003-10-21 2008-10-21 3Com Corporation IP-based enhanced emergency services using intelligent client devices
US7877275B2 (en) 2003-11-13 2011-01-25 General Motors Llc System and method for maintaining and providing personal information in real time
US6968044B2 (en) 2003-12-05 2005-11-22 Bellsouth Intellectual Property Corporation Telephone emergency response system and method
US7260186B2 (en) 2004-03-23 2007-08-21 Telecommunication Systems, Inc. Solutions for voice over internet protocol (VoIP) 911 location services
US6940950B2 (en) 2003-12-19 2005-09-06 Telecommunication Systems, Inc. Enhanced E911 location information using voice over internet protocol (VoIP)
US7369530B2 (en) 2004-01-30 2008-05-06 Scott Keagy Apparatus and method for interfacing packet-based phone services with emergency call centers
US20050169248A1 (en) 2004-02-04 2005-08-04 Nortel Networks Limited Method and apparatus for providing in-band location information in an emergency response network
US7386111B2 (en) 2004-02-10 2008-06-10 Vonage Network Inc. Method and apparatus for placing a long distance call based on a virtual phone number
US7177399B2 (en) 2004-02-27 2007-02-13 Nortel Network Limited Determining the geographical location from which an emergency call originates in a packet-based communications network
US7130385B1 (en) 2004-03-05 2006-10-31 Avaya Technology Corp. Advanced port-based E911 strategy for IP telephony
US7177398B2 (en) 2004-03-13 2007-02-13 Intrado Inc. Bi-directional messaging for an emergency services network
US7123693B2 (en) 2004-03-13 2006-10-17 Intrado Inc. Method and apparatus for increasing the reliability of an emergency call communication network
US20050261002A1 (en) 2004-05-19 2005-11-24 Wintecronics Co., Ltd. Tracking method and system to be implemented using a wireless telecommunications network
US7298328B2 (en) 2004-12-13 2007-11-20 Jackson Wang Systems and methods for geographic positioning using radio spectrum signatures
US8265587B2 (en) 2004-06-17 2012-09-11 West Corporation System and method for amending instructions for emergency auxiliary services following an emergency services request
US7260384B2 (en) 2004-07-29 2007-08-21 Sprint Spectrum L.P. Method and system for dynamic selection of voice mail system
US7787611B1 (en) 2004-09-17 2010-08-31 Cisco Technology, Inc. Packet telephony bridging server
US7333480B1 (en) 2004-09-20 2008-02-19 Nortel Networks Limited Localization of call routing for TDM sets in an IP network
US20060068753A1 (en) 2004-09-22 2006-03-30 Jim Karpen Emergency call handling system
US7480567B2 (en) 2004-09-24 2009-01-20 Nokia Corporation Displaying a map having a close known location
US7573982B2 (en) 2004-10-12 2009-08-11 Bellsouth Intellectual Property Corporation Methods and systems for managing a call session
US20070041513A1 (en) 2005-02-08 2007-02-22 Gende Michael F Emergency call identification, location and routing method and system
US7756253B2 (en) 2005-02-22 2010-07-13 At&T Intellectual Property Ii, Lp Methods and systems for providing foreign call back number compatibility for VoIP E9-1-1 calls
US7545916B2 (en) 2005-02-28 2009-06-09 At&T Intellectual Property I Methods of placing emergency calls using data networks
US20070003024A1 (en) 2005-06-22 2007-01-04 Cml Emergency Services Inc. Network emergency call taking system and method
US20060293024A1 (en) 2005-06-23 2006-12-28 Lucent Technologies Inc. Methods and apparatus for improved 911 support for VoIP service
US7706971B2 (en) 2005-07-21 2010-04-27 The Boeing Company System and method for data mapping and map discrepancy reporting
US20070036139A1 (en) 2005-08-09 2007-02-15 Ashish Patel System and method for authenticating internetwork resource requests
US7245900B1 (en) 2005-08-24 2007-07-17 Sprint Spectrum L.P. Method and system for using basic service set identifiers (BSSIDs) for emergency services routing
US8824454B2 (en) 2005-10-24 2014-09-02 West Corporation Peering network for parameter-based routing of special number calls
US20070160036A1 (en) 2006-01-10 2007-07-12 Smith David M Method and system for servicing enhanced 911 calls
US7702081B1 (en) 2006-02-21 2010-04-20 Sprint Communications Company L.P. Call back number provisioning for emergency call services
US8208461B2 (en) 2006-04-04 2012-06-26 Telecommunication Systems, Inc. SS7 MAP/Lg+ to SIP based call signaling conversion gateway for wireless VoIP E911
US9408046B2 (en) 2006-10-03 2016-08-02 Telecommunication Systems, Inc. 911 data messaging
US7743053B2 (en) * 2006-10-17 2010-06-22 Hewlett-Packard Development Company, L.P. Hybrid database query caching
US9025734B2 (en) 2008-07-03 2015-05-05 Centurylink Intellectual Property Llc PSAP capabilities defining system and method for handling emergency text messaging

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7031714B1 (en) * 2001-11-14 2006-04-18 Sprint Spectrum L.P. Method and system for managing communication based on location
US7412049B1 (en) * 2002-05-31 2008-08-12 At&T Delaware Intellectual Property, Inc. System and method for real-time blocking of a telephone call
US20040203575A1 (en) * 2003-01-13 2004-10-14 Chin Mary W. Method of recognizing fraudulent wireless emergency service calls
US20040185823A1 (en) * 2003-03-17 2004-09-23 Chin Mary Wonmon Method for processing emergency calls initiated by wireless phones
US20060135132A1 (en) * 2004-12-21 2006-06-22 Lucent Technologies, Inc. Storing anti-spam black lists

Also Published As

Publication number Publication date
US20070041516A1 (en) 2007-02-22
US8175570B2 (en) 2012-05-08

Similar Documents

Publication Publication Date Title
US8175570B2 (en) E911 call blocking for non-initialized wireless telephones
US8103242B2 (en) E911 call blocking for non-initialized wireless telephones
US10455396B2 (en) Method and apparatus for providing customization of public safety answering point information delivery
US9390615B2 (en) Emergency alert for voice over internet protocol (VoIP)
US7764769B2 (en) Integrated call handler and email systems and methods
US6754335B1 (en) Call center with location queuing and dispatching
US6721396B2 (en) Method and system of enhancing emergency call services
US20080101553A1 (en) Logging call data for failed emergency calls
US20060166704A1 (en) Method for alerting a subscriber of an emergency call request
US9401986B2 (en) Unique global identifier header for minimizing prank emergency 911 calls
WO2006060113A2 (en) Method and apparatus for providing push-to-talk based execution of an emergency plan
US9467559B2 (en) Special emergency call treatment based on the caller
US20150023477A1 (en) Extended Efficient Usage of Emergency Services Keys
JP2007507780A (en) Method and apparatus for utilizing 911 and E911 functions from a remote location
US8116722B2 (en) E911 call blocking for non-initialized wireless telephones
CN106912016B (en) Method for obtaining current position of emergency telephone calling party and emergency telephone service system
WO2008021838A2 (en) Integrated call handler and email systems and methods
US20150023478A1 (en) System and method for providing continued answering of special number calls when a primary psap is incapacitated
US20140146951A1 (en) System and method for providing continued answering of special number calls when a primary answering position is abandoned
US8913982B2 (en) System and method for effecting special treatment of emergency calls originating from a temporarily designated region
US20120178435A1 (en) System and method for perposterous cellular black box applications

Legal Events

Date Code Title Description
AS Assignment

Owner name: TELECOMMUNICATION SYSTEMS, INC., MARYLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DICKINSON, RICHARD;REEL/FRAME:028167/0875

Effective date: 20060524

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION