US20040096042A1 - Emergency telephone call notification service system and method - Google Patents
Emergency telephone call notification service system and method Download PDFInfo
- Publication number
- US20040096042A1 US20040096042A1 US10/641,902 US64190203A US2004096042A1 US 20040096042 A1 US20040096042 A1 US 20040096042A1 US 64190203 A US64190203 A US 64190203A US 2004096042 A1 US2004096042 A1 US 2004096042A1
- Authority
- US
- United States
- Prior art keywords
- telephone
- scp
- subscriber
- call
- emergency
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M11/00—Telephonic communication systems specially adapted for combination with other electrical systems
- H04M11/04—Telephonic communication systems specially adapted for combination with other electrical systems with alarm systems, e.g. fire, police or burglar alarm systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/04—Special services or facilities for emergency applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13098—Mobile subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13103—Memory
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13141—Hunting for free outlet, circuit or channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13176—Common channel signaling, CCS7
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13204—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13336—Store & forward, messaging systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13345—Intelligent networks, SCP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1337—Operator, emergency services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13389—LAN, internet
Definitions
- a transmitting device with a panic button that is worn by a user that, when activated, transmits a signal to a base unit attached to a telephone.
- the base unit automatically calls a predetermined list of telephone numbers and plays a prerecorded message.
- Another system discloses attaching an emergency call monitor to a user's telephone. When an emergency call is made, the monitor waits until the call is complete and then automatically dials out to a messaging service that calls predetermined numbers and plays a prerecorded message.
- emergency call detection equipment is attached to a telephone switch and reacts to 911 telephone calls by activating a calling service to contact a predetermined list of telephone numbers.
- FIG. 1 illustrates an emergency telephone call notification system according to a presently preferred embodiment.
- FIG. 2 is a diagram illustrating a contact list stored at the SCP show in FIG. 1.
- FIG. 3 is a flow chart illustrating a method of providing an emergency telephone call notification service on the system of FIG. 1 according to a presently preferred embodiment.
- FIG. 4 is a flow chart illustrating a preferred method of contacting designated contact numbers, the method for use in the system of FIG. 1.
- FIG. 1 illustrates a telecommunications system 10 according to a preferred embodiment.
- the system preferably includes a subscriber telephone 12 in communication with a first advanced intelligent network (AIN) capable service switching point (SSP) 14 over a voice/information line 16 .
- the first SSP 14 is in communication over a voice/information line with a public safety access point (PSAP) 18 .
- PSAP 18 is preferably an emergency call receiving station having one or more emergency dispatchers to handle and route emergency telephone calls to the appropriate agency.
- the PSAP 18 is accessible from the subscriber telephone 12 by dialing a predetermined telephone number such as 911.
- the first SSP 14 includes an AIN emergency telephone number trigger recognition capability for recognizing dialed digits of any of a number of emergency telephone numbers.
- the first SSP 14 is configured to recognize an N11 trigger when a 911 telephone number is dialed.
- the system 10 also includes one or more service control points (SCP) 20 .
- SCP 20 is an AIN network element containing logic and data necessary to provide functionality required for the execution of a desired communication service.
- An SCP 20 generally permits separation of service logic from switching functionality such that additional services maybe developed without the need to provision software in each individual SSP.
- a suitable SCP 20 is the Advantage SCP manufactured by Lucent Technologies.
- the SCP 20 includes a designated contact number list 21 (FIG. 2) stored in memory corresponding to each subscriber telephone number that subscribes to the emergency telephone number notification service described below.
- the contact list 21 includes a list of subscriber telephone numbers 23 and a list of the contact telephone numbers 25 associated with each subscriber telephone number.
- each subscriber is permitted four contact numbers.
- a subscriber may be represented by a range of telephone numbers so that each telephone number in the range of numbers is associated with the same set of contact numbers.
- a subscriber may be a company having a range of consecutive telephone numbers where the same contact numbers are desired for all of the numbers in the range.
- the contact numbers may also be for communication devices or services other than a standard plain old telephone service (POTS) telephone.
- POTS plain old telephone service
- the contact numbers may be for cellular telephones, paging services, or other communication devices and services.
- the SCP 20 communicates with SSP's, such as the first SSP 14 , over a data channel via at least one service transfer point (STP).
- the system 10 may include local STP's (LSTP) 22 and a regional STP (RSTP) 24 .
- the LSTP's 22 and RSTP 24 are connected via data channels and also connect the SCP to the SSP's via data channels.
- a suitable data signal extended for use with the STPs is the American National Standards Institute (ANSI) signalling system No. 7 (SS 7 ).
- SS 7 American National Standards Institute
- a suitable SCP/SSP communication protocol is the AIN 0 . 1 SCP/SSP protocol set forth in Bellcore Technical Reference TR-NWT-001285, entitled AIN Switch-Service Control Point Application Protocol Interface Generic Requirements, Issue 1, August 1992.
- the SCP 20 also communicates with one or more compact service nodes (CSN) 26 or other type of service node/intelligent peripheral.
- CSN compact service nodes
- the SCP 20 communicates directly with each CSN 26 over a wide area network (WAN) 28 such as CONet using transfer control protocol/internet protocol (TCP/IP).
- WAN wide area network
- TCP/IP transfer control protocol/internet protocol
- Other networks capable of running TCP/IP are also suitable for facilitating communication between each CSN and an SCP.
- the SCP may communicate with the CSN 26 via one or more STPs and an SSP.
- Each CSN 26 is a network element of the AIN that contains resources to exchange information with an end user and perform other functions such as call origination and tone generation.
- the CSN 26 provides special resources for interactions between the end user and the network such as dual tone multi-frequency (DTMF) recognition, playing pre-recorded announcements and tone generation.
- DTMF dual tone multi-frequency
- a service node/intelligent peripheral platform suitable for use as a CSN is manufactured by Lucent Technologies.
- each CSN 26 is configured to communicate emergency call notices to numbers stored in the SCP database 21 and transmitted to the CSN 26 over the WAN 28 or other communication link.
- the CSN 26 includes a caller ID generator 31 utilizing standard caller ID logic and containing a caller ID message to send to the contact telephones 36 associated with a particular subscriber number.
- the CSN 26 contains a plurality of emergency notification message templates 33 stored in memory. Each of the templates 33 may have a general voice or text message for transmission to the contact telephones 36 . Information regarding the particular emergency telephone call made by the subscriber is insertable into the appropriate message template.
- the CSN 26 is in communication with a second SSP 30 via data 32 and voice 34 lines.
- the system 10 further includes one or more contact telephones 36 connected to a third SSP 38 .
- Each contact telephone is associated with a designated contact telephone number in the designated contact list 21 stored at the SCP 20 .
- the contact telephones 36 are shown as communicating with an SSP separate from the SSPs connected to the subscriber and the CSN's, different configurations are contemplated wherein the subscriber telephone 12 , contact telephones 36 and CSN's 26 are all connected to the same SSP or other combinations of SSPs.
- the CSN preferably contains a port identity transfer control protocol/user defined protocol (TCP/UDP) address along with an internet protocol (IP) address identified by a socket.
- TCP/UDP port identity transfer control protocol/user defined protocol
- IP internet protocol
- This virtual port (socket) number is identified and assigned on the CSN 26 .
- a CSN 26 is in communication with a SSP 30 over both data and voice lines utilizing ISDN-BRI connectivity.
- SS 7 TCAP messaging is utilized between the SSP's and the SCP.
- FIG. 3 a preferred embodiment of the method of implementing an emergency telephone number notification service is described below with relation to the system show in FIG. 1.
- the SSP 14 When a subscriber 12 goes off-hook (picks up the telephone receiver), the SSP 14 presents a dial tone to the subscriber and subscriber dials a telephone number (at steps 38 , 40 and 42 ). The first SSP 14 receives these dialed digits and examines the dialed digits to see if they correspond with an AIN trigger. If the dialed digits are an emergency telephone number, such as 911, the SSP recognizes an N11 trigger and contacts the SCP 20 for instructions (at step 44 ). If no N11 trigger is recognized, the telephone call is processed and sent off to the designated destination.
- an emergency telephone number such as 911
- the TCP/IP message sent by the SCP includes the subscriber's telephone number, a time when the subscriber called 911, a list of contact numbers associated with that subscriber number, and dialing instructions.
- the dialing instructions may already reside on the CSN and the SCP simply forwards the contact numbers and emergency telephone call information.
- the SCP returns a message to the first SSP 14 allowing the 911 call to terminate at the PSAP 18 .
- the CSN 26 pursuant to the instructions received from the SCP 20 , begins making telephone calls via the second SSP 30 to the designated contact numbers on the list (at step 56 ).
- the contact telephones 36 are connected to a third SSP 38 that is in communication with the second SSP 30 over interoffice trunk lines 39 .
- the contact telephones 36 may be connected to any switch or may be connected to an intermediary communications device, such as a PBX, that is in communication with a switch.
- the CSN 26 dials the first number on the contact list received from the SCP 20 (at step 58 ). In dialing each number, the CSN also transmits a caller ID message from the caller ID generator 31 indicating that the call is an emergency notification call. Preferably, the CSN invokes standard caller ID logic and uses a pseudo caller ID message such as “911 Notify” rather than the number of the 911 caller.
- the CSN proceeds to dial the next contact number (at step 60 ) if there is an answer at any particular contact number, the CSN invokes answer verification logic which, in a preferred embodiment, consists of playing an announcement in response to detecting an answer (at step 62 ).
- the announcement is a pre-recorded message assembled from the appropriate one of the message templates 33 stored at the CSN 26 stating that the call is a message from the 911 Notification Service.
- the answer verification logic at the CSN may include a live answer detector where the answering party is requested to either press a key on the telephone pad or orally respond. In this way, the CSN can determine whether a person or answering device answers the call. The CSN then waits for a response and checks to see if there is a touch-tone or voice response (at step 64 ).
- the CSN 26 receives no response and an answering machine or voice mail system is detected then an announcement is played for recordal on the answering machine or voice mail and a timer in the answer verification logic at the CSN will keep track of the number of calls made to a given contact number and the time interval between each repeated call.
- the CSN will place subsequent telephone calls to the contact number every five minutes (at steps 66 , 68 ).
- the announcement left on the answering machine preferably includes information related to the subscriber telephone number and of time and day when the emergency telephone call was made from that number. Additionally, the message left on the answering machine or voice mail is preferably only left one time. Subsequent answers by answering machine or voice mail system will not trigger the announcement again.
- the CSN will continue placing calls at a greater interval of time for up to 24 hours after the original emergency telephone call was made by the subscriber.
- the interval of contacting the telephone number on the contact list would be increased to every 15 minutes.
- the CSN may be instructed to leave an announcement every hour that the notification system is trying to reach the person at the number and repeating the information that an emergency call was placed from a particular number at a given time and day (at step 70 ).
- the CSN 26 may play an announcement indicating that the emergency call was placed from the subscriber telephone 12 at a particular time/day and will automatically attempt to connect the person answering the notification call to the subscriber telephone (at steps 72 , 74 ). Additional messages indicating the system is attempting to connect the call may be played while the contact person is waiting on hold.
- the CSN 26 may simply play an announcement indicating that the line is busy and that the contact person should try later or may repeat the attempt to connect the contact person to the subscriber telephone number a predetermined number of times (at steps 76 , 78 ).
- the SCP may instruct the CSN to dial all of the contact numbers simultaneously to reach as many of the subscriber's chosen contact group as quickly as possible.
- the system and method described above provides the advantage of an automated emergency telephone notification implemented on existing hardware such as AIN network elements. No additional hardware is required.
- AIN communication protocols may be implemented to easily adapt and configure AIN network elements to allow for expeditious contact of designated parties while not interfering with the emergency telephone call placed by the subscriber.
- the system and method described above may be used with emergency telephone call systems such standard 911, enhanced 911, or other custom emergency telephone call systems.
Abstract
A system and method for emergency telephone call notification. The system includes an AIN capable switch, a service control point (SCP) having a database of designated contact numbers associated with a service subscriber telephone number, and an intelligent peripheral (IP) in communication with the SCP for contacting the designated contact numbers. The method includes the steps of recognizing an N11 trigger and the SCP initiating telephone calls, via the IP, to each of the contact numbers corresponding to the telephone number of the subscriber making the emergency telephone call.
Description
- In an emergency situation, people need to quickly contact the appropriate agency (police, fire department, ambulance, poison control, etc.). Many communities provide a single telephone number, such as 911, which connects a caller to a central dispatcher to gather information and relay the call to the appropriate destination. In addition to locating and contacting the appropriate agency, the caller may also wish to notify other parties that an emergency situation exists.
- Several systems and methods for providing auxiliary notification have been proposed. One system discloses a transmitting device with a panic button that is worn by a user that, when activated, transmits a signal to a base unit attached to a telephone. The base unit automatically calls a predetermined list of telephone numbers and plays a prerecorded message. Another system discloses attaching an emergency call monitor to a user's telephone. When an emergency call is made, the monitor waits until the call is complete and then automatically dials out to a messaging service that calls predetermined numbers and plays a prerecorded message. In yet another system, emergency call detection equipment is attached to a telephone switch and reacts to 911 telephone calls by activating a calling service to contact a predetermined list of telephone numbers.
- One drawback of these emergency telephone call notification systems is the need for specialized equipment in addition to the standard telephone system equipment. Also, many existing notification systems have limited flexibility and only a few basic features.
- Accordingly, there is a need for an improved system and method of communicating emergency telephone call notices to designated parties that provides flexible and efficient use of existing infrastructure.
- FIG. 1 illustrates an emergency telephone call notification system according to a presently preferred embodiment.
- FIG. 2 is a diagram illustrating a contact list stored at the SCP show in FIG. 1.
- FIG. 3 is a flow chart illustrating a method of providing an emergency telephone call notification service on the system of FIG. 1 according to a presently preferred embodiment.
- FIG. 4 is a flow chart illustrating a preferred method of contacting designated contact numbers, the method for use in the system of FIG. 1.
- As described in greater detail below, a preferred system and method for providing an emergency telephone call notification service utilizes advanced intelligent network infrastructure to avoid the need to add or maintain additional hardware to support the service. FIG. 1 illustrates a
telecommunications system 10 according to a preferred embodiment. The system preferably includes asubscriber telephone 12 in communication with a first advanced intelligent network (AIN) capable service switching point (SSP) 14 over a voice/information line 16. Thefirst SSP 14 is in communication over a voice/information line with a public safety access point (PSAP) 18. The PSAP 18 is preferably an emergency call receiving station having one or more emergency dispatchers to handle and route emergency telephone calls to the appropriate agency. In one embodiment, the PSAP 18 is accessible from thesubscriber telephone 12 by dialing a predetermined telephone number such as 911. - The
first SSP 14 includes an AIN emergency telephone number trigger recognition capability for recognizing dialed digits of any of a number of emergency telephone numbers. In a preferred embodiment, thefirst SSP 14 is configured to recognize an N11 trigger when a 911 telephone number is dialed. - The
system 10 also includes one or more service control points (SCP) 20. AnSCP 20 is an AIN network element containing logic and data necessary to provide functionality required for the execution of a desired communication service. AnSCP 20 generally permits separation of service logic from switching functionality such that additional services maybe developed without the need to provision software in each individual SSP. Asuitable SCP 20 is the Advantage SCP manufactured by Lucent Technologies. In a preferred embodiment, theSCP 20 includes a designated contact number list 21 (FIG. 2) stored in memory corresponding to each subscriber telephone number that subscribes to the emergency telephone number notification service described below. Thecontact list 21 includes a list ofsubscriber telephone numbers 23 and a list of thecontact telephone numbers 25 associated with each subscriber telephone number. - Other than specific system memory limitations and telephone company policy, there may be any number of contact numbers per subscriber. In one embodiment, each subscriber is permitted four contact numbers. In another embodiment, a subscriber may be represented by a range of telephone numbers so that each telephone number in the range of numbers is associated with the same set of contact numbers. For example, a subscriber may be a company having a range of consecutive telephone numbers where the same contact numbers are desired for all of the numbers in the range. Additionally, the contact numbers may also be for communication devices or services other than a standard plain old telephone service (POTS) telephone. For example, the contact numbers may be for cellular telephones, paging services, or other communication devices and services.
- The
SCP 20 communicates with SSP's, such as thefirst SSP 14, over a data channel via at least one service transfer point (STP). Thesystem 10 may include local STP's (LSTP) 22 and a regional STP (RSTP) 24. The LSTP's 22 andRSTP 24 are connected via data channels and also connect the SCP to the SSP's via data channels. A suitable data signal extended for use with the STPs is the American National Standards Institute (ANSI) signalling system No. 7 (SS7). A suitable SCP/SSP communication protocol is the AIN 0.1 SCP/SSP protocol set forth in Bellcore Technical Reference TR-NWT-001285, entitled AIN Switch-Service Control Point Application Protocol Interface Generic Requirements, Issue 1, August 1992. - The
SCP 20 also communicates with one or more compact service nodes (CSN) 26 or other type of service node/intelligent peripheral. In one embodiment, theSCP 20 communicates directly with each CSN 26 over a wide area network (WAN) 28 such as CONet using transfer control protocol/internet protocol (TCP/IP). Other networks capable of running TCP/IP are also suitable for facilitating communication between each CSN and an SCP. In other embodiments, the SCP may communicate with the CSN 26 via one or more STPs and an SSP. - Each CSN26 is a network element of the AIN that contains resources to exchange information with an end user and perform other functions such as call origination and tone generation. The CSN 26 provides special resources for interactions between the end user and the network such as dual tone multi-frequency (DTMF) recognition, playing pre-recorded announcements and tone generation. A service node/intelligent peripheral platform suitable for use as a CSN is manufactured by Lucent Technologies. Although the
system 10 illustrated in FIG. 1 shows a certain number of network elements (SCPs, CSNS, STPs, and SSPs), those of ordinary skill in the art understand that the presently preferred system and method may include more complex networks having a plurality of the interconnected network elements. Preferably, each CSN 26 is configured to communicate emergency call notices to numbers stored in theSCP database 21 and transmitted to the CSN 26 over theWAN 28 or other communication link. In one embodiment, the CSN 26 includes acaller ID generator 31 utilizing standard caller ID logic and containing a caller ID message to send to thecontact telephones 36 associated with a particular subscriber number. In another embodiment, the CSN 26 contains a plurality of emergencynotification message templates 33 stored in memory. Each of thetemplates 33 may have a general voice or text message for transmission to thecontact telephones 36. Information regarding the particular emergency telephone call made by the subscriber is insertable into the appropriate message template. The CSN 26 is in communication with asecond SSP 30 viadata 32 andvoice 34 lines. Although the CSN's 26 in FIG. 1 are connected to a different SSP than thesubscriber 12, the CSN's may also be connected to the same SSP as the subscriber. - The
system 10 further includes one ormore contact telephones 36 connected to athird SSP 38. Each contact telephone is associated with a designated contact telephone number in the designatedcontact list 21 stored at the SCP 20. Again, although thecontact telephones 36 are shown as communicating with an SSP separate from the SSPs connected to the subscriber and the CSN's, different configurations are contemplated wherein thesubscriber telephone 12, contacttelephones 36 and CSN's 26 are all connected to the same SSP or other combinations of SSPs. In order to implement the emergency telephone call notification service, the CSN preferably contains a port identity transfer control protocol/user defined protocol (TCP/UDP) address along with an internet protocol (IP) address identified by a socket. This virtual port (socket) number is identified and assigned on the CSN 26. Preferably, a CSN 26 is in communication with aSSP 30 over both data and voice lines utilizing ISDN-BRI connectivity. SS7 TCAP messaging is utilized between the SSP's and the SCP. - Referring now to FIG. 3, a preferred embodiment of the method of implementing an emergency telephone number notification service is described below with relation to the system show in FIG. 1. When a
subscriber 12 goes off-hook (picks up the telephone receiver), theSSP 14 presents a dial tone to the subscriber and subscriber dials a telephone number (atsteps first SSP 14 receives these dialed digits and examines the dialed digits to see if they correspond with an AIN trigger. If the dialed digits are an emergency telephone number, such as 911, the SSP recognizes an N11 trigger and contacts theSCP 20 for instructions (at step 44). If no N11 trigger is recognized, the telephone call is processed and sent off to the designated destination. When an N11 trigger is encountered and theSSP 14 contacts theSCP 20, an info_analyze query is sent to theSCP 20 containing the calling party ID as well as standard SS7 call information (at step 26). TheSCP 20 receives the info_analyze query and determines whether or not the calling party ID is associated with an emergency telephone notification service subscriber (at step 48). The SCP preferably performs this step by comparing the calling party ID with the information stored in thesubscriber list 21 at theSCP 20. - If the calling party ID is not recognized by the SCP as a subscriber to the emergency telephone call notification service, the SCP sends an analyzed_route message back to the SSP and the SSP routes the call based on standard 911 routing data to the appropriate 911 operator at a PSAP18 (at
steps 50, 52). The analyzed_route message includes a called party ID, a calling party ID and a primary trunk group. If the SCP does recognize the calling party ID as a subscriber to the emergency telephone call notification service, theSCP 20 calls on enhanced 911 (E911) logic residing in memory at theSCP 20 and establishes a communication link, such as a TCP/IP link over theWAN 28, to a CSN 26 (at step 54). Preferably, the TCP/IP message sent by the SCP includes the subscriber's telephone number, a time when the subscriber called 911, a list of contact numbers associated with that subscriber number, and dialing instructions. In one alternative embodiment, the dialing instructions may already reside on the CSN and the SCP simply forwards the contact numbers and emergency telephone call information. - As soon as the CSN responds and confirms receipt of the instructions, the SCP returns a message to the
first SSP 14 allowing the 911 call to terminate at thePSAP 18. Finally, theCSN 26, pursuant to the instructions received from theSCP 20, begins making telephone calls via thesecond SSP 30 to the designated contact numbers on the list (at step 56). As shown in FIG. 1, thecontact telephones 36 are connected to athird SSP 38 that is in communication with thesecond SSP 30 overinteroffice trunk lines 39. In other embodiments, thecontact telephones 36 may be connected to any switch or may be connected to an intermediary communications device, such as a PBX, that is in communication with a switch. - As shown in FIG. 4, one preferred method of contacting telephone numbers listed on the contact list associated with a subscriber number is shown. The
CSN 26 dials the first number on the contact list received from the SCP 20 (at step 58). In dialing each number, the CSN also transmits a caller ID message from thecaller ID generator 31 indicating that the call is an emergency notification call. Preferably, the CSN invokes standard caller ID logic and uses a pseudo caller ID message such as “911 Notify” rather than the number of the 911 caller. If there is no answer at the first contact number, the CSN proceeds to dial the next contact number (at step 60) if there is an answer at any particular contact number, the CSN invokes answer verification logic which, in a preferred embodiment, consists of playing an announcement in response to detecting an answer (at step 62). Preferably, the announcement is a pre-recorded message assembled from the appropriate one of themessage templates 33 stored at theCSN 26 stating that the call is a message from the 911 Notification Service. In one embodiment, the answer verification logic at the CSN may include a live answer detector where the answering party is requested to either press a key on the telephone pad or orally respond. In this way, the CSN can determine whether a person or answering device answers the call. The CSN then waits for a response and checks to see if there is a touch-tone or voice response (at step 64). - If the
CSN 26 receives no response and an answering machine or voice mail system is detected then an announcement is played for recordal on the answering machine or voice mail and a timer in the answer verification logic at the CSN will keep track of the number of calls made to a given contact number and the time interval between each repeated call. In one embodiment, the CSN will place subsequent telephone calls to the contact number every five minutes (atsteps 66, 68). The announcement left on the answering machine preferably includes information related to the subscriber telephone number and of time and day when the emergency telephone call was made from that number. Additionally, the message left on the answering machine or voice mail is preferably only left one time. Subsequent answers by answering machine or voice mail system will not trigger the announcement again. Additionally, if an answering machine or voice mail system is encountered after the first hour of attempting to place the emergency notification call, the CSN will continue placing calls at a greater interval of time for up to 24 hours after the original emergency telephone call was made by the subscriber. In one embodiment the interval of contacting the telephone number on the contact list would be increased to every 15 minutes. In another embodiment, the CSN may be instructed to leave an announcement every hour that the notification system is trying to reach the person at the number and repeating the information that an emergency call was placed from a particular number at a given time and day (at step 70). - If a response (touch tone or voice) is received from a person answering at the contact number dialed by the CSN, the
CSN 26 may play an announcement indicating that the emergency call was placed from thesubscriber telephone 12 at a particular time/day and will automatically attempt to connect the person answering the notification call to the subscriber telephone (atsteps 72, 74). Additional messages indicating the system is attempting to connect the call may be played while the contact person is waiting on hold. If thesubscriber telephone 12 from which the emergency telephone call was originally placed is busy, or no answer is received, theCSN 26 may simply play an announcement indicating that the line is busy and that the contact person should try later or may repeat the attempt to connect the contact person to the subscriber telephone number a predetermined number of times (atsteps 76, 78). In another embodiment, the SCP may instruct the CSN to dial all of the contact numbers simultaneously to reach as many of the subscriber's chosen contact group as quickly as possible. - The system and method described above provides the advantage of an automated emergency telephone notification implemented on existing hardware such as AIN network elements. No additional hardware is required. Furthermore, in a preferred embodiment AIN communication protocols may be implemented to easily adapt and configure AIN network elements to allow for expeditious contact of designated parties while not interfering with the emergency telephone call placed by the subscriber. Preferably, the system and method described above may be used with emergency telephone call systems such standard 911, enhanced 911, or other custom emergency telephone call systems.
- It is intended that the foregoing detailed description be regarded as illustrative rather than limiting, and that it be understood that the following claims, including all equivalents, are intended to define the scope of this invention.
Claims (21)
1. In a telecommunications system having at least one subscriber telephone in communication with an advanced intelligent network (AIN) capable switch, at least one intelligent peripheral (IP) in communication with the AIN capable switch, at least one service control point (SCP) in communication with the switch, and a public safety answering point (PSAP) in communication with the SCP and the switch, a method of notifying at least one designated telephone number that an emergency telephone call has been made from the subscriber telephone, the method comprising the steps of:
recognizing an emergency telephone call at the switch;
the switch informing the SCP of the emergency telephone call;
the SCP instructing the IP to dial the at least one designated telephone number; and
the IP informing the at least one designated telephone number of the emergency telephone call from the subscriber telephone.
2. The method of claim, wherein the emergency telephone call is a 911 telephone call.
3. The method of claim 2 , wherein the step of recognizing an emergency telephone call trigger further comprises recognizing an N11 trigger.
4. The method of claim 1 , wherein the SCP further comprises a database having a list of subscriber telephones and a list of at least one designated telephone number associated with each of the subscriber telephones in the list of subscriber telephones, and wherein the step of the SCP instructing the IP to dial the at least one designated telephone number comprises the SCP retrieving a first of the at least one telephone number associated with the subscriber telephone number and instructing the IP to contact the first of the at least one telephone numbers that an emergency telephone call has been placed from the subscriber telephone.
5. The method of claim 1 , wherein the SCP further comprises a database having a list of subscriber telephone numbers and a list of at least one designated telephone number associated with each of the subscriber telephone numbers, and wherein the step of the SCP instructing the IP to dial the at least one designated telephone number comprises the SCP retrieving all of the telephone numbers associated with the subscriber telephone number and instructing the IP to contact all of the designated telephone numbers simultaneously.
6. The method of claim 1 , wherein the step of the IP informing the at least one designated telephone number further comprises the step of the IP supplying a caller ID message to the at least one designated telephone number indicating an incoming call from an emergency call notification service.
7. The method of claim 1 , wherein the step of the IP informing at least one designated telephone number further comprises playing a prerecorded message if a person answers the emergency call notification call.
8. The method of claim 1 further comprising a step of automatically placing a call from the at least one designated telephone number to the subscriber telephone if a person answers the at least one designated telephone number.
9. An emergency call notification system comprising:
a subscriber telephone;
an AIN capable switch in communication with a public service access point (PSAP) and the subscriber telephone, the AIN switch configured to recognize an emergency telephone call;
a service control point (SCP) in communication with the switch, the SCP comprising a database having a list of emergency call notification service subscribers, the SCP configured to determine if an emergency telephone call was made by an emergency call notification service subscriber and correlate the emergency call notification service subscriber number with a list of at least one designated contact number for the emergency call notification service subscriber; and
an intelligent peripheral (IP) in communication with the SCP, the IP responsive to an instruction from the SCP to contact the at least one designated contact number.
10. The system of claim 9 further comprising means for automatically connecting a designated contact number answered by a person to the emergency call notification service subscriber number.
11. The system of claim 10 further comprising a caller ID generator comprising a predesignated message stored in memory.
12. The system of claim 10 wherein the IP comprises answer verification logic.
13. The system of claim 11 wherein the answer verification logic comprises a call repetition timer.
14. The system of claim 11 wherein the answer verification logic further comprises a live answer detector.
15. The system of claim 11 wherein the answer verification logic comprises a prerecorded message for transmission to an answering machine.
16. The system of claim 9 , wherein the IP is in communication with the SCP via a wide area network.
17. The method of claim 1 , wherein the step of the SCP instructing the IP comprises sending a message via a wide area network connection to the IP.
18. The method of claim 17 , wherein the message comprises a TCP/IP message.
19. The method of claim 1 , wherein the step of the IP informing the at least one designated number comprises the IP dialing a first of the at least one designated numbers and waiting a predetermined number of rings before trying to contact a next one of the at least one designated numbers.
20. The system of claim 9 , wherein the IP further comprises a plurality of prerecorded message templates.
21. In a telecommunications system having at least one subscriber telephone in communication with an advanced intelligent network (AIN) capable switch, at least one intelligent peripheral (IP) in communication with the AIN capable switch, at least one service control point (SCP) in communication with the switch, and a public safety answering point (PSAP) in communication with the SCP and the switch, a method of notifying at least one designated telephone number that an emergency telephone call has been made from the subscriber telephone, the method comprising the steps of:
recognizing an emergency telephone call trigger corresponding to an emergency telephone call at the switch;
notifying the SCP of the emergency telephone call;
instructing the IP to dial the at least one designated telephone number;
informing the at least one designated telephone number of the emergency telephone call from the subscriber telephone; and
automatically placing a call from the at least one designated telephone number to the subscriber telephone if a person answers the at least one designated telephone number.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/641,902 US20040096042A1 (en) | 1998-12-15 | 2003-08-14 | Emergency telephone call notification service system and method |
US12/643,609 US8705703B2 (en) | 1998-12-15 | 2009-12-21 | Emergency telephone call notification service system and method |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/211,636 US6201856B1 (en) | 1998-12-15 | 1998-12-15 | Emergency telephone call notification service system and method |
US09/784,589 US6735285B2 (en) | 1998-12-15 | 2001-02-15 | Emergency telephone call notification service system and method |
US10/641,902 US20040096042A1 (en) | 1998-12-15 | 2003-08-14 | Emergency telephone call notification service system and method |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/784,589 Continuation US6735285B2 (en) | 1998-12-15 | 2001-02-15 | Emergency telephone call notification service system and method |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/643,609 Continuation US8705703B2 (en) | 1998-12-15 | 2009-12-21 | Emergency telephone call notification service system and method |
Publications (1)
Publication Number | Publication Date |
---|---|
US20040096042A1 true US20040096042A1 (en) | 2004-05-20 |
Family
ID=22787751
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/211,636 Expired - Lifetime US6201856B1 (en) | 1998-12-15 | 1998-12-15 | Emergency telephone call notification service system and method |
US09/784,589 Expired - Fee Related US6735285B2 (en) | 1998-12-15 | 2001-02-15 | Emergency telephone call notification service system and method |
US10/641,902 Abandoned US20040096042A1 (en) | 1998-12-15 | 2003-08-14 | Emergency telephone call notification service system and method |
US12/643,609 Expired - Fee Related US8705703B2 (en) | 1998-12-15 | 2009-12-21 | Emergency telephone call notification service system and method |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/211,636 Expired - Lifetime US6201856B1 (en) | 1998-12-15 | 1998-12-15 | Emergency telephone call notification service system and method |
US09/784,589 Expired - Fee Related US6735285B2 (en) | 1998-12-15 | 2001-02-15 | Emergency telephone call notification service system and method |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/643,609 Expired - Fee Related US8705703B2 (en) | 1998-12-15 | 2009-12-21 | Emergency telephone call notification service system and method |
Country Status (1)
Country | Link |
---|---|
US (4) | US6201856B1 (en) |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2005062582A1 (en) * | 2003-12-19 | 2005-07-07 | Motorola, Inc. | Method of operating a mobile communication device and mobile communication system during an emergency situation |
US20050249193A1 (en) * | 2004-05-10 | 2005-11-10 | Robert Epley | Methods, apparatus and computer program products for associating local telephone numbers with emergency phone calls in a packet switched telephone system |
US20060159067A1 (en) * | 2005-01-20 | 2006-07-20 | Yen-Fu Chen | Single point of contact personal communication system |
US20070036139A1 (en) * | 2005-08-09 | 2007-02-15 | Ashish Patel | System and method for authenticating internetwork resource requests |
US20070165612A1 (en) * | 2006-01-10 | 2007-07-19 | Research In Motion Limited | System and method for managing call routing in a network environment including IMS |
US7519678B1 (en) * | 2002-11-22 | 2009-04-14 | Verizon Laboratories, Inc. | Internet messaging notification methods and systems |
US20100177771A1 (en) * | 2006-01-10 | 2010-07-15 | Research In Motion Limited | System and Method for Originating a Call Via a Circuit-Switched Network from a User Equipment Device |
US20100290608A1 (en) * | 2009-05-18 | 2010-11-18 | Avaya Inc. | System and method for sending data using caller id |
US20110044325A1 (en) * | 2006-02-06 | 2011-02-24 | Research In Motion Limited | System and Method for Effectuating a SIP Call in a Network Environment Including IMS |
US8542678B2 (en) | 2006-08-11 | 2013-09-24 | Blackberry Limited | System and method for managing call continuity in IMS network environment |
US8625762B1 (en) * | 2007-06-13 | 2014-01-07 | Accudata Technologies, Inc. | Providing additional information to called parties |
US10397387B2 (en) | 2007-06-13 | 2019-08-27 | I D You, Llc | Providing audio announcement to called parties |
US10455083B2 (en) | 2007-06-13 | 2019-10-22 | Accudata Technologies, Inc. | Method and system for providing additional information to called parties |
US10542138B2 (en) | 2007-06-13 | 2020-01-21 | First Orion Corp. | Information provided to parent regarding a called for child protection |
US10827060B2 (en) | 2007-06-13 | 2020-11-03 | First Orion Corp. | Delivering additional information to receiving parties for text messaging based Caller ID |
US10958781B2 (en) | 2007-06-13 | 2021-03-23 | First Orion Corp. | Providing audio content to a device |
USRE48967E1 (en) | 2006-02-06 | 2022-03-08 | Blackberry Limited | System and method for originating a call via a circuit-switched network from a user equipment device |
US11297180B2 (en) | 2007-06-13 | 2022-04-05 | First Orion Corp. | Method and system for providing additional information to called parties |
US11375060B2 (en) | 2007-10-17 | 2022-06-28 | First Orion Corp. | IP-enabled information delivery |
US11811966B2 (en) | 2007-10-17 | 2023-11-07 | First Orion Corp. | IP-enabled information delivery |
Families Citing this family (66)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020176545A1 (en) * | 1998-08-10 | 2002-11-28 | Peter Schweitzer | Apparatus and method for broadcasting an emergency warning over a telephone network |
US6201856B1 (en) * | 1998-12-15 | 2001-03-13 | Ameritech Corporation | Emergency telephone call notification service system and method |
IT1313372B1 (en) * | 1999-09-23 | 2002-07-23 | Cit Alcatel | METHOD OF TRANSMITTING VOICE MESSAGES OR SIMILAR DEFINED GEOGRAPHICAL AREAS BY TELEPHONE. |
US6594345B1 (en) * | 1999-09-30 | 2003-07-15 | Bellsouth Intellectual Property Corporation | Targeted disaster warning system and apparatus |
US7092501B2 (en) | 1999-10-12 | 2006-08-15 | Sbc Properties, L.P. | Method and apparatus for providing prepaid local telephone services |
US6574480B1 (en) * | 1999-12-10 | 2003-06-03 | At&T Corp. | Method and apparatus for providing intelligent emergency paging |
US6553106B1 (en) * | 1999-12-27 | 2003-04-22 | Avaya Technology Corp. | Alphanumeric messaging system |
US6744873B1 (en) * | 2000-01-15 | 2004-06-01 | William E. McCracken | Telephone accessory device |
US6504909B1 (en) * | 2000-11-13 | 2003-01-07 | William C. Cook | Reverse registration method in a system for the automatic notification that a call to an emergency service has occurred |
US6775356B2 (en) * | 2000-11-13 | 2004-08-10 | Angelo Salvucci | Real-time incident and response information messaging INA system for the automatic notification that an emergency call has occurred from a telecommunication device |
US6745021B1 (en) * | 2000-11-21 | 2004-06-01 | Alcatel | System, controller and method for alerting mobile subscribers about emergency situations |
US7099332B2 (en) * | 2000-12-29 | 2006-08-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Emergency calling with a VoIP device in a VLAN environment |
US7099439B2 (en) | 2001-02-26 | 2006-08-29 | Classco Inc. | Loop test apparatus and method |
US8868659B2 (en) * | 2001-05-15 | 2014-10-21 | Avaya Inc. | Method and apparatus for automatic notification and response |
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 |
US7286648B1 (en) * | 2001-09-28 | 2007-10-23 | At&T Bls Intellectual Property, Inc. | Emergency locator system |
US6608886B1 (en) * | 2001-11-27 | 2003-08-19 | Bellsouth Intellectual Property Corporation | Method and apparatus for establishing a connection between first and second communication devices |
US7016477B2 (en) * | 2001-11-27 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Method of notifying a party of an emergency |
US6792081B1 (en) * | 2001-11-27 | 2004-09-14 | Bellsouth Intellectual Property Corporation | Emergency notification system |
US7099677B2 (en) * | 2001-11-29 | 2006-08-29 | Bellsouth Intellectual Property Corp. | Smart call delivery GIS integration |
US6731743B2 (en) * | 2001-12-18 | 2004-05-04 | Sbc Properties, L.P. | AIN query redirection |
US7418087B2 (en) * | 2002-01-04 | 2008-08-26 | Classco Inc. | Telephone network messaging |
US6693545B2 (en) | 2002-01-31 | 2004-02-17 | International Business Machines Corporation | Personal alarm device transmitting telephone number for alarm confirmation and inquiry |
US6707888B1 (en) * | 2002-05-06 | 2004-03-16 | Sprint Communications Company, L.P. | Location evaluation for callers that place emergency telephone calls over packet networks |
US8495163B2 (en) * | 2004-03-18 | 2013-07-23 | Avaya, Inc. | Method and apparatus for a publish-subscribe system with templates for role-based view of subscriptions |
US20040152441A1 (en) * | 2002-07-10 | 2004-08-05 | Wong Wai-See Candy | Wireless handset emergency location provisioning system (wireless HELPS) |
US7076235B2 (en) * | 2002-12-03 | 2006-07-11 | Sony Ericsson Mobile Communications Ab | Automatic notification of personal emergency contacts from a wireless communications device |
WO2004084532A1 (en) * | 2003-03-17 | 2004-09-30 | Spector & Associates, Inc. | Apparatus and method for broadcasting messages to selected group (s) of users |
US7012544B2 (en) * | 2003-04-09 | 2006-03-14 | Cube Investments Limited | Address and/or alarm indicator sign |
US7895263B1 (en) * | 2003-06-25 | 2011-02-22 | Everbridge, Inc. | Emergency and non-emergency telecommunications geo-notification system |
US8102974B2 (en) * | 2003-07-01 | 2012-01-24 | Avaya Inc. | Method and apparatus for event notification based on the identity of a calling party |
US7126472B2 (en) * | 2003-07-22 | 2006-10-24 | Mark W Kraus | System and method of providing emergency response to a user carrying a user device |
US7529544B1 (en) | 2004-02-23 | 2009-05-05 | Sprint Spectrum L.P. | Method and system for initiating a communication with a network entity to communicate information regarding a fixed wireless device |
US20050271186A1 (en) * | 2004-06-02 | 2005-12-08 | Audiopoint, Inc. | System, method and computer program product for interactive voice notification |
US20060049934A1 (en) * | 2004-09-07 | 2006-03-09 | Bellsouth Intellectual Property Corporation | Methods and systems for utilizing a data network for the communication of emergency alerts |
US8380158B2 (en) * | 2004-12-06 | 2013-02-19 | Edward A. McCulloch | System and method for vital communications connectivity |
US20060222150A1 (en) * | 2005-03-31 | 2006-10-05 | Sbc Knowledge Ventures, L.P | Emergency call notification and response |
US20060282293A1 (en) * | 2005-06-10 | 2006-12-14 | True Sandra L | System and method for providing automated notification of hospital admissions |
US7706792B1 (en) * | 2005-08-10 | 2010-04-27 | At&T Mobility Ii Llc | Intelligent customer care support |
WO2007073760A1 (en) * | 2005-12-27 | 2007-07-05 | Telefonaktiebolaget L M Ericsson (Publ) | Method and system for facilitating establishment of an ip-link in a telecommunications system |
US7920679B1 (en) | 2006-02-02 | 2011-04-05 | Sprint Communications Company L.P. | Communication system and method for notifying persons of an emergency telephone call |
US20100311442A1 (en) * | 2006-04-18 | 2010-12-09 | Natan Epstein | Wireless messaging system |
US20070288561A1 (en) * | 2006-05-23 | 2007-12-13 | Beckhusen Fred K | Hyperlink-based notification system method |
WO2008033305A2 (en) * | 2006-09-11 | 2008-03-20 | Telecommunication Systems, Inc. | Automatic emergency call notification to pre-designated personal emergency contacts |
US8548419B1 (en) | 2006-09-15 | 2013-10-01 | At&T Mobility Ii Llc | Utilization of SMS and/or cellular broadcast to receive multimedia alerts |
US7764946B1 (en) * | 2006-09-15 | 2010-07-27 | Cingular Wireless Ii, Llc | Geographic distribution of SMS alerts |
US8098798B2 (en) * | 2006-10-31 | 2012-01-17 | Alcatel Lucent | Logging call data for failed emergency calls |
US8774798B2 (en) * | 2007-08-28 | 2014-07-08 | At&T Mobility Ii Llc | Determining capability to provide dynamic local time updates in a prepaid terminating call |
US8190118B2 (en) | 2008-03-26 | 2012-05-29 | At&T Mobility Ii Llc | Integration of emergency alert information |
US8467795B2 (en) * | 2010-03-18 | 2013-06-18 | Verizon Patent And Licensing Inc. | Location-based routing of IMS calls through femtocells |
US9111430B2 (en) | 2010-06-30 | 2015-08-18 | Mark Kraus | Security system for a building |
US8600008B2 (en) | 2010-06-30 | 2013-12-03 | Mark Kraus | System and method of providing an emergency contact party line |
US8811588B2 (en) * | 2011-12-20 | 2014-08-19 | Motorola Mobility Llc | Method and system for managing multiple simultaneously placed calls |
US9305273B2 (en) * | 2011-12-31 | 2016-04-05 | Verizon Patent And Licensing Inc. | Telephone number use analysis for grouping of consecutive telephone numbers based on assignment status |
US9173185B1 (en) | 2012-04-10 | 2015-10-27 | Sprint Spectrum L.P. | Methods and systems for managing registration signaling based on off-time duration |
US9386148B2 (en) | 2013-09-23 | 2016-07-05 | Ooma, Inc. | Identifying and filtering incoming telephone calls to enhance privacy |
US10769931B2 (en) | 2014-05-20 | 2020-09-08 | Ooma, Inc. | Network jamming detection and remediation |
US9633547B2 (en) | 2014-05-20 | 2017-04-25 | Ooma, Inc. | Security monitoring and control |
US10553098B2 (en) | 2014-05-20 | 2020-02-04 | Ooma, Inc. | Appliance device integration with alarm systems |
US11330100B2 (en) | 2014-07-09 | 2022-05-10 | Ooma, Inc. | Server based intelligent personal assistant services |
US9781063B2 (en) * | 2014-10-07 | 2017-10-03 | At&T Mobility Ii Llc | System and method for alerting a list of multiple recipients of a user's request for assistance |
US11171875B2 (en) | 2015-05-08 | 2021-11-09 | Ooma, Inc. | Systems and methods of communications network failure detection and remediation utilizing link probes |
US10911368B2 (en) | 2015-05-08 | 2021-02-02 | Ooma, Inc. | Gateway address spoofing for alternate network utilization |
US10009286B2 (en) | 2015-05-08 | 2018-06-26 | Ooma, Inc. | Communications hub |
US10771396B2 (en) | 2015-05-08 | 2020-09-08 | Ooma, Inc. | Communications network failure detection and remediation |
US9635174B1 (en) | 2016-07-06 | 2017-04-25 | Sorenson Ip Holdings, Llc | Video relay service, communication system, and related methods for connecting users with N11 services in a video relay service environment |
Citations (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3662111A (en) * | 1970-08-13 | 1972-05-09 | Morton K Rubinstein | Automatic telephone care device |
US4371751A (en) * | 1980-04-07 | 1983-02-01 | Newart Electronic Sciences, Inc. | Automatic telephonic user emergency message transmitting apparatus |
US4417100A (en) * | 1981-07-06 | 1983-11-22 | Metro-Tel Corp. | Emergency dialer system |
US4492820A (en) * | 1980-10-24 | 1985-01-08 | Salt Lake Communications, Inc. | Telephone alarm system |
US4510350A (en) * | 1982-03-11 | 1985-04-09 | Almicro Electronics Inc. | Personal alarm apparatus including wrist supported transmitter and receiver/telephone interface circuit |
US4743892A (en) * | 1987-01-08 | 1988-05-10 | Family Communications, Inc. | On-site personal monitoring system |
US5077788A (en) * | 1989-07-06 | 1991-12-31 | Taro, Inc. | System and method for processing telephone communication |
US5128979A (en) * | 1991-02-06 | 1992-07-07 | Lifeline Systems Inc. | Monitored personal emergency response system |
US5161180A (en) * | 1990-10-19 | 1992-11-03 | Chavous Robert O | Call interceptor for emergency systems |
US5161278A (en) * | 1991-12-12 | 1992-11-10 | Erwin Tomm | Handle connector with anti-loosening lock |
US5166972A (en) * | 1988-11-15 | 1992-11-24 | Mitel Corporation | Group emergency call system |
US5195126A (en) * | 1991-05-09 | 1993-03-16 | Bell Atlantic Network Services, Inc. | Emergency alert and security apparatus and method |
US5315636A (en) * | 1991-06-28 | 1994-05-24 | Network Access Corporation | Personal telecommunications system |
US5333173A (en) * | 1991-10-15 | 1994-07-26 | Bell Atlantic Network Services, Inc. | Personal checkup service and equipment |
US5339351A (en) * | 1992-06-02 | 1994-08-16 | Hoskinson John D | Emergency response system |
US5418844A (en) * | 1992-04-17 | 1995-05-23 | Bell Atlantic Network Services, Inc. | Automatic access to information service providers |
US5598460A (en) * | 1996-02-09 | 1997-01-28 | Tendler Cellular, Inc. | Emergency back-up system for enhancing reliability or rescue |
US5659605A (en) * | 1994-06-22 | 1997-08-19 | Bell Atlantic Network Services, Inc. | Method and apparatus for providing soft dial tone using office equipment designators |
US5787429A (en) * | 1996-07-03 | 1998-07-28 | Nikolin, Jr.; Michael A. | Potential hazard and risk-assessment data communication network |
US5805670A (en) * | 1996-03-19 | 1998-09-08 | Life Safety Solutions, Inc. | Private notification system for communicating 9-1-1 information |
US5859897A (en) * | 1996-07-16 | 1999-01-12 | At&T Corp. | Telephone calling card and service |
US5995848A (en) * | 1997-07-21 | 1999-11-30 | Telefonaktiebolaget Lm Ericsson | System and method of completing calls to busy mobile subscribers in a radio telecommunications network |
US6151385A (en) * | 1998-07-07 | 2000-11-21 | 911 Notify.Com, L.L.C. | System for the automatic notification that a 9-1-1 call has occurred |
US6201856B1 (en) * | 1998-12-15 | 2001-03-13 | Ameritech Corporation | Emergency telephone call notification service system and method |
US6295346B1 (en) * | 1998-07-13 | 2001-09-25 | At&T Corp. | Automated emergency notification system |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06189354A (en) | 1991-03-29 | 1994-07-08 | Kigyo Tsushin Syst Eng Kk | Emergency telephone adaptor |
WO1995015051A1 (en) | 1993-11-29 | 1995-06-01 | Greater Harris County 9-1-1 Emergency Network | Integrated data collection and transmission for emergency calls |
US5859987A (en) * | 1995-09-29 | 1999-01-12 | Intel Corporation | Method and apparatus for providing multiple configuration reset modes for an intelligent bridge |
US6963557B2 (en) * | 2003-03-29 | 2005-11-08 | Intrado Inc. | System and method for routing telephone calls involving internet protocol network |
US7627091B2 (en) * | 2003-06-25 | 2009-12-01 | Avaya Inc. | Universal emergency number ELIN based on network address ranges |
US8233474B2 (en) * | 2009-03-31 | 2012-07-31 | Extreme Networks | Communication of location information for an IP telephony communication device |
-
1998
- 1998-12-15 US US09/211,636 patent/US6201856B1/en not_active Expired - Lifetime
-
2001
- 2001-02-15 US US09/784,589 patent/US6735285B2/en not_active Expired - Fee Related
-
2003
- 2003-08-14 US US10/641,902 patent/US20040096042A1/en not_active Abandoned
-
2009
- 2009-12-21 US US12/643,609 patent/US8705703B2/en not_active Expired - Fee Related
Patent Citations (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3662111A (en) * | 1970-08-13 | 1972-05-09 | Morton K Rubinstein | Automatic telephone care device |
US4371751A (en) * | 1980-04-07 | 1983-02-01 | Newart Electronic Sciences, Inc. | Automatic telephonic user emergency message transmitting apparatus |
US4492820A (en) * | 1980-10-24 | 1985-01-08 | Salt Lake Communications, Inc. | Telephone alarm system |
US4417100A (en) * | 1981-07-06 | 1983-11-22 | Metro-Tel Corp. | Emergency dialer system |
US4510350A (en) * | 1982-03-11 | 1985-04-09 | Almicro Electronics Inc. | Personal alarm apparatus including wrist supported transmitter and receiver/telephone interface circuit |
US4743892A (en) * | 1987-01-08 | 1988-05-10 | Family Communications, Inc. | On-site personal monitoring system |
US5166972A (en) * | 1988-11-15 | 1992-11-24 | Mitel Corporation | Group emergency call system |
US5077788A (en) * | 1989-07-06 | 1991-12-31 | Taro, Inc. | System and method for processing telephone communication |
US5161180A (en) * | 1990-10-19 | 1992-11-03 | Chavous Robert O | Call interceptor for emergency systems |
US5128979A (en) * | 1991-02-06 | 1992-07-07 | Lifeline Systems Inc. | Monitored personal emergency response system |
US5195126A (en) * | 1991-05-09 | 1993-03-16 | Bell Atlantic Network Services, Inc. | Emergency alert and security apparatus and method |
US5315636A (en) * | 1991-06-28 | 1994-05-24 | Network Access Corporation | Personal telecommunications system |
US5333173A (en) * | 1991-10-15 | 1994-07-26 | Bell Atlantic Network Services, Inc. | Personal checkup service and equipment |
US5161278A (en) * | 1991-12-12 | 1992-11-10 | Erwin Tomm | Handle connector with anti-loosening lock |
US5418844A (en) * | 1992-04-17 | 1995-05-23 | Bell Atlantic Network Services, Inc. | Automatic access to information service providers |
US5339351A (en) * | 1992-06-02 | 1994-08-16 | Hoskinson John D | Emergency response system |
US5659605A (en) * | 1994-06-22 | 1997-08-19 | Bell Atlantic Network Services, Inc. | Method and apparatus for providing soft dial tone using office equipment designators |
US5598460A (en) * | 1996-02-09 | 1997-01-28 | Tendler Cellular, Inc. | Emergency back-up system for enhancing reliability or rescue |
US5805670A (en) * | 1996-03-19 | 1998-09-08 | Life Safety Solutions, Inc. | Private notification system for communicating 9-1-1 information |
US5787429A (en) * | 1996-07-03 | 1998-07-28 | Nikolin, Jr.; Michael A. | Potential hazard and risk-assessment data communication network |
US5859897A (en) * | 1996-07-16 | 1999-01-12 | At&T Corp. | Telephone calling card and service |
US5995848A (en) * | 1997-07-21 | 1999-11-30 | Telefonaktiebolaget Lm Ericsson | System and method of completing calls to busy mobile subscribers in a radio telecommunications network |
US6151385A (en) * | 1998-07-07 | 2000-11-21 | 911 Notify.Com, L.L.C. | System for the automatic notification that a 9-1-1 call has occurred |
US6295346B1 (en) * | 1998-07-13 | 2001-09-25 | At&T Corp. | Automated emergency notification system |
US6201856B1 (en) * | 1998-12-15 | 2001-03-13 | Ameritech Corporation | Emergency telephone call notification service system and method |
US6735285B2 (en) * | 1998-12-15 | 2004-05-11 | Sbc Properties, L.P. | Emergency telephone call notification service system and method |
Cited By (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7519678B1 (en) * | 2002-11-22 | 2009-04-14 | Verizon Laboratories, Inc. | Internet messaging notification methods and systems |
WO2005062582A1 (en) * | 2003-12-19 | 2005-07-07 | Motorola, Inc. | Method of operating a mobile communication device and mobile communication system during an emergency situation |
US7586902B2 (en) * | 2004-05-10 | 2009-09-08 | At&T Intellectual Property I, L.P. | Methods, apparatus and computer program products for associating local telephone numbers with emergency phone calls in a packet switched telephone system |
US20050249193A1 (en) * | 2004-05-10 | 2005-11-10 | Robert Epley | Methods, apparatus and computer program products for associating local telephone numbers with emergency phone calls in a packet switched telephone system |
US8547968B2 (en) | 2004-05-10 | 2013-10-01 | At&T Intellectual Property I, L.P. | Methods, apparatus and computer program products for associating local telephone numbers with emergency phone calls in a packet switched telephone systems |
US8223750B2 (en) | 2004-05-10 | 2012-07-17 | At&T Intellectual Property I, L.P. | Methods, apparatus and computer program products for associating local telephone numbers with emergency phone calls in a packet switched telephone system |
US20090290577A1 (en) * | 2004-05-10 | 2009-11-26 | At&T Intellectual Property I, L.P. | Methods, apparatus and computer program products for associating local telephone numbers with emergency phone calls in a packet switched telephone system |
US20080292065A1 (en) * | 2005-01-20 | 2008-11-27 | Yen-Fu Chen | Single Point of Contact Personal Communication System |
US8243910B2 (en) | 2005-01-20 | 2012-08-14 | International Business Machines Corporation | Single point of contact personal communication system |
US7672440B2 (en) | 2005-01-20 | 2010-03-02 | International Business Machines Corporation | Single point of contact personal communication system |
US20060159067A1 (en) * | 2005-01-20 | 2006-07-20 | Yen-Fu Chen | Single point of contact personal communication system |
US20070036139A1 (en) * | 2005-08-09 | 2007-02-15 | Ashish Patel | System and method for authenticating internetwork resource requests |
US8345671B2 (en) | 2006-01-10 | 2013-01-01 | Research In Motion Limited | System and method for managing call routing in a network environment including IMS |
US20070165612A1 (en) * | 2006-01-10 | 2007-07-19 | Research In Motion Limited | System and method for managing call routing in a network environment including IMS |
US20100272100A1 (en) * | 2006-01-10 | 2010-10-28 | Research In Motion Limited | System and Method for Managing Call Routing in a Network Environment Including IMS |
US8989179B2 (en) | 2006-01-10 | 2015-03-24 | Blackberry Limited | System and method for originating a call via a circuit-switched network from a user equipment device |
US8369319B2 (en) | 2006-01-10 | 2013-02-05 | Research In Motion Limited | System and method for originating a call via a circuit-switched network from a user equipment device |
US7769000B2 (en) * | 2006-01-10 | 2010-08-03 | Research In Motion Limited | System and method for managing call routing in a network environment including IMS |
US20100177771A1 (en) * | 2006-01-10 | 2010-07-15 | Research In Motion Limited | System and Method for Originating a Call Via a Circuit-Switched Network from a User Equipment Device |
USRE48967E1 (en) | 2006-02-06 | 2022-03-08 | Blackberry Limited | System and method for originating a call via a circuit-switched network from a user equipment device |
US20110044325A1 (en) * | 2006-02-06 | 2011-02-24 | Research In Motion Limited | System and Method for Effectuating a SIP Call in a Network Environment Including IMS |
US8599838B2 (en) | 2006-02-06 | 2013-12-03 | Blackberry Limited | System and method for effectuating a SIP call in a network environment including IMS |
US8542678B2 (en) | 2006-08-11 | 2013-09-24 | Blackberry Limited | System and method for managing call continuity in IMS network environment |
US8625762B1 (en) * | 2007-06-13 | 2014-01-07 | Accudata Technologies, Inc. | Providing additional information to called parties |
US11102346B2 (en) | 2007-06-13 | 2021-08-24 | First Orion Corp. | Providing additional information to called parties |
US20160261741A1 (en) * | 2007-06-13 | 2016-09-08 | Accudata Technologies, Inc. | Providing additional information to called parties |
US9807231B2 (en) * | 2007-06-13 | 2017-10-31 | Accudata Technologies, Inc. | Providing additional information to called parties |
US10397387B2 (en) | 2007-06-13 | 2019-08-27 | I D You, Llc | Providing audio announcement to called parties |
US10404843B2 (en) | 2007-06-13 | 2019-09-03 | I D You, Llc | Providing audio announcement to called parties |
US10455083B2 (en) | 2007-06-13 | 2019-10-22 | Accudata Technologies, Inc. | Method and system for providing additional information to called parties |
US10542138B2 (en) | 2007-06-13 | 2020-01-21 | First Orion Corp. | Information provided to parent regarding a called for child protection |
US10805446B2 (en) | 2007-06-13 | 2020-10-13 | First Orion Corp. | Providing audio announcement to called parties |
US10827060B2 (en) | 2007-06-13 | 2020-11-03 | First Orion Corp. | Delivering additional information to receiving parties for text messaging based Caller ID |
US10958781B2 (en) | 2007-06-13 | 2021-03-23 | First Orion Corp. | Providing audio content to a device |
US11876926B2 (en) | 2007-06-13 | 2024-01-16 | First Orion Corp. | Providing audio content to a device |
US20210385326A1 (en) * | 2007-06-13 | 2021-12-09 | Accudata Technologies, Inc. | Providing additional information to called parties |
US11729310B2 (en) | 2007-06-13 | 2023-08-15 | First Orion Corp. | Delivering additional information to receiving parties for text messaging based caller ID |
US11297180B2 (en) | 2007-06-13 | 2022-04-05 | First Orion Corp. | Method and system for providing additional information to called parties |
US11582334B2 (en) | 2007-06-13 | 2023-02-14 | First Orion Corp. | Providing audio announcement to called parties |
US11388279B2 (en) | 2007-06-13 | 2022-07-12 | First Orion Corp. | Providing audio announcement to called parties |
US11553081B2 (en) | 2007-06-13 | 2023-01-10 | First Orion Corp. | Providing audio content to a device |
US11375060B2 (en) | 2007-10-17 | 2022-06-28 | First Orion Corp. | IP-enabled information delivery |
US11811966B2 (en) | 2007-10-17 | 2023-11-07 | First Orion Corp. | IP-enabled information delivery |
US20100290608A1 (en) * | 2009-05-18 | 2010-11-18 | Avaya Inc. | System and method for sending data using caller id |
US8861695B2 (en) * | 2009-05-18 | 2014-10-14 | Avaya Inc. | System and method for sending data using caller ID |
Also Published As
Publication number | Publication date |
---|---|
US20110002448A1 (en) | 2011-01-06 |
US6201856B1 (en) | 2001-03-13 |
US20010009577A1 (en) | 2001-07-26 |
US8705703B2 (en) | 2014-04-22 |
US6735285B2 (en) | 2004-05-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6201856B1 (en) | Emergency telephone call notification service system and method | |
US6122357A (en) | Providing enhanced services through double SIV and personal dial tone | |
US5953399A (en) | PBX selective caller identification authentication | |
US7388949B2 (en) | System and method for audio caller identification service | |
US6968044B2 (en) | Telephone emergency response system and method | |
US6167119A (en) | Providing enhanced services through SIV and personal dial tone | |
US6628772B1 (en) | Method for providing enhanced directory assistance upon command using out-of-band signaling | |
US6704405B1 (en) | Personal dial tone service with personalized call waiting | |
CA2173167C (en) | Intelligent call forwarding | |
US6101242A (en) | Monitoring for key words with SIV to validate home incarceration | |
US5327489A (en) | Method and apparatus for monitoring a network for customer signaling during the term of a call | |
CN1072421C (en) | Telecommunications follow me services | |
US5926537A (en) | Generating a distinctive ring tone for a calling party subscriber within a telecommunications network | |
US5832061A (en) | System and method incorporating a mover's mailbox in an intelligent network | |
US6067347A (en) | Providing enhanced services through double SIV and personal dial tone | |
US7023978B2 (en) | Telephone voice messaging system and method using off-hook immediate trigger | |
KR20010059199A (en) | Method for serving a personal automatic response service in an intelligent exchange system | |
WO1996013115A1 (en) | Cellular payphone signalling method and apparatus | |
WO2002100119A1 (en) | Method and apparatus for setting up a connection by means of a call back function of a voice mail service and a voice mail system provided with a call back function for setting up a connection | |
JPH0834618B2 (en) | Call path setting method | |
JPS62269462A (en) | Personal calling system in automatic exchange |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |