US20140314213A1 - Method Of Notifying A Party Of An Emergency - Google Patents
Method Of Notifying A Party Of An Emergency Download PDFInfo
- Publication number
- US20140314213A1 US20140314213A1 US14/186,164 US201414186164A US2014314213A1 US 20140314213 A1 US20140314213 A1 US 20140314213A1 US 201414186164 A US201414186164 A US 201414186164A US 2014314213 A1 US2014314213 A1 US 2014314213A1
- Authority
- US
- United States
- Prior art keywords
- provisioned
- subscriber
- emergency
- identification information
- program product
- 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.)
- Granted
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
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5116—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
-
- 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
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5183—Call or contact centers with computer-telephony arrangements
- H04M3/5191—Call or contact centers with computer-telephony arrangements interacting with the Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13163—Fault alarm
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1325—Priority service
-
- 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
Definitions
- the present invention is directed generally to notification systems, and, more particularly, to an emergency notification system.
- Lucent Technologies Inc. the family 911 notification service offered by Lucent Technologies Inc., Murray Hill, N.J.
- Each subscriber to the service may select up to five telephone numbers, each associated with a particular person, that they wish to be called if a 911 call is placed from a landline telephone associated with the subscriber.
- the selected telephone numbers may be given a priority from first to fifth and may be associated with landline telephones and/or wireless telephones.
- the service operates in the manner described hereinbelow.
- the service After a 911 call has been placed from a landline telephone associated with a subscriber, the service calls the selected telephone numbers in a sequential order according to the specified priority. If the family 911 notification service reaches a live person at one of the selected telephone numbers, the service plays an announcement. The announcement informs the person that the incoming call is from the family 911 notification service and that a 911 call was placed. The announcement also informs the person as to the time that the 911 call was placed and the telephone number that the 911 call was placed from. The service stops calling the selected telephone numbers once the information has been provided to a live person. If the service has not reached a live person after all of the selected telephone numbers have been called, the service waits for five minutes before beginning to call the selected telephone numbers again. This process repeats itself for the first hour following the placement of the 911 call. During the first hour, if the service reaches an answering machine or a voice mail system at one of the selected telephone numbers, the service does not play an announcement.
- the service If the service has not reached a live person within the first hour, the service continues to call the selected telephone numbers according to the specified priority. However, if the service reaches an answering machine or a voice mail system after the first hour, the service plays a slightly different announcement. This announcement informs the answering machine or voice mail system that the incoming call is from the family 911 notification service and that the service has been trying to reach the person associated with the selected telephone number to notify them that a 911 call has been placed. This announcement also informs the answering machine or the voice mail system as to the time that the 911 call was placed and the telephone number from which the 911 call was placed. The service stops dialing the selected telephone numbers once an announcement has been played to an answering machine or a voice mail system. If the service has not reached a live person, an answering machine, or a voice mail system within the first twenty-four hours following the placement of the 911 call, the service stops dialing the selected telephone numbers.
- Lucent's family 911 notification service There are several shortcomings associated with Lucent's family 911 notification service. For example, the means used to provision the selected telephone numbers add complexity and cost to the service, the hardware used to implement the service is relatively expensive to acquire and maintain, and the service only offers oral notification that a 911 call has been placed. Thus, there exists a need for an emergency notification system that overcomes the limitations, shortcomings, and disadvantages of the emergency notification system described hereinabove.
- the present invention meets the identified need, as well as other needs, as will be more fully understood following a review of this specification and the accompanying drawings.
- the present invention is directed to an emergency notification system.
- the system includes a first server for receiving an emergency communication from a telecommunications network and for transmitting a message to a subscriber of the emergency notification system; and a second server in communication with the first server, the second server for supplying the first server with information associated with a subscriber.
- FIG. 1 is a block diagram of an Advanced Intelligent Network (AIN) for integration with a public switched telephone network;
- AIN Advanced Intelligent Network
- FIG. 2 illustrates a prior art emergency notification system
- FIG. 3 illustrates an emergency notification system according to one embodiment of the present invention.
- FIGS. 4A and 4B illustrate an embodiment of a process flow of the emergency notification system of FIG. 3 .
- calling party is used herein generally to refer to the person or unit that initiates a telecommunication.
- the calling party may also be referred to herein as “caller.”
- called party is used herein generally to refer to the person or unit that answers or responds to the call or communication. In some cases the calling party or the called party may not be a person, but may be a device such as an answering machine, a voice mail system, etc.
- communication is used herein to include all messages or calls that may be exchanged between a calling party and a called party, including voice, data and video messages.
- communication is used synonymously herein with the term “call” unless a distinction is noted.
- subscriber is used herein to generally refer to a subscriber of the described emergency notification service.
- the present invention is directed to an emergency notification system.
- the emergency notification system utilizes the intelligent functionality of an Advanced Intelligent Network (AIN).
- AIN is a network used to provide enhanced voice and data services and dynamic routing capabilities to a conventional telephone network.
- AIN With AIN, the actual voice call is still transmitted over a circuit-switched network but the signaling and control takes place on a separate packet-switched network.
- FIG. 1 is a block diagram of an Advanced Intelligent Network (AIN) 10 .
- the AIN 10 may be employed by a Local Exchange Carrier (LEC), and may be utilized by the LEC to allow the LEC to provide call processing features and services that are not embedded within conventional switching circuits of a conventional telephone system such as, for example, the Public Switched Telephone Network (PSTN) 12 .
- PSTN Public Switched Telephone Network
- the AIN 10 includes a Service Switching Point (SSP) 14 , a Signal Control Point (SCP) 16 , a database 18 , a Signal Transfer Point (STP) 20 , and a Service Node (SN) 22 .
- SSP Service Switching Point
- SCP Signal Control Point
- STP Signal Transfer Point
- SN Service Node
- central office (CO) switches are used to interconnect customer premises equipment (i.e., terminal equipment such as telephones, modems, or answering machines that are connected to the telephone network and reside on the customer's premises).
- customer premises equipment i.e., terminal equipment such as telephones, modems, or answering machines that are connected to the telephone network and reside on the customer's premises.
- the SSP 14 is a switch used to interconnect customer premises equipment via the PSTN 12 .
- the difference between the SSP 14 and the CO switch of a conventional telephone system is that the SSP 14 provides intelligent network functionality.
- the SSP 14 has one or more subscriber lines 24 connected thereto.
- the subscriber lines 24 may be, for example, local loops comprising conventional twisted pair loop circuits connected between the SSP 14 and the customer premises, or the subscriber lines 24 may be trunk circuits, such as T-1 trunk circuits.
- the number of subscriber lines 24 connected to an SSP 14 may be on the order of ten thousand to one hundred thousand lines.
- the subscriber line 24 is connected to a terminating piece of customer premises equipment, represented in FIG. 1 by a landline telephone 26 .
- the terminating equipment may be any other type of communications unit such as, for example, a telecopier, a personal computer, a modem, an answering machine, or a private branch exchange (PBX) switching system.
- PBX private branch exchange
- the SCP 16 is a server, associated with a database 18 , and provides instructions to the SSP 14 and the SN 22 as requested and required.
- the SCP 16 may be an intelligent database server such as, for example, an Intelligent Network Service Control Point available from Lucent Technologies Inc., Murray Hill, N.J.
- the database 18 is for storing customer information used in providing enhanced calling services, such as the service provided by the emergency notification system of the present invention, and may reside at the SCP 16 .
- the intelligent functionality of the SCP 16 may be realized by application programs, such as programmable Service Program Applications (SPA), which are executed by the SCP 16 .
- SPA programmable Service Program Applications
- the STP 20 is a packet switch that routes signaling and control messages between the SSP 14 and the SCP 16 . As illustrated in FIG. 1 , the STP 20 is in communication with the SSP 14 via communication link 28 and with the SCP 16 via communication link 30 . Communication links 28 , 30 may employ, for example, the Signaling System 7 (SS7) signaling protocol.
- SS7 Signaling System 7
- the SN 22 may provide an enhanced feature or service that requires an audio connection between the SN 22 and an answering machine connected to a subscriber line 24 , or between the SN 22 and a landline telephone 26 from which an emergency communication has been placed.
- the SN 22 may be any type of AIN-compliant service node, and may be, for example, a Compact Services Node (CSN) available from Lucent Technologies Inc., Murray Hill, N.J. Similar to the SCP 16 , the intelligent functionality of the SN 22 may be realized by programmable applications executable by the SN 22 .
- CSN Compact Services Node
- the SN 22 is in communication with the SSP 14 via communication link 34 , with the PSTN 12 via communication link 36 , and with the SCP 16 via communication link 38 .
- Communication links 34 and 36 may be, for example, an Integrated Service Digital Network (ISDN) Primary Rate Interface (PRI), an ISDN Basic Rate Interface (BRI), or a T-1 trunk circuit.
- ISDN Integrated Service Digital Network
- PRI Primary Rate Interface
- BRI ISDN Basic Rate Interface
- T-1 trunk circuit may be, for example, a portion of a communication network such as, for example, a Local Area Network (LAN), a Metropolitan Area Network (MAN), or a Wide Area Network (WAN).
- LAN Local Area Network
- MAN Metropolitan Area Network
- WAN Wide Area Network
- the basic operation of the AIN 10 illustrated in FIG. 1 is described hereinbelow.
- the SSP 14 When a call originating from the landline telephone 26 is received at the SSP 14 via the PSTN 12 , the SSP 14 generates a query to determine how the call should be processed.
- the query generated by the SSP 14 is transmitted via out-of-band signaling through the STP 20 to the SCP 16 .
- the SCP 16 interprets the query based on information provided by the SSP 14 and information stored in the database 18 to determine whether some customized call feature or enhanced service should be implemented for the particular call, or whether conventional dial-up telephone service should be provided.
- the information provided by the SSP 14 may include, for example, the originating telephone number, the name of the calling party, and the telephone number dialed by the calling party.
- the information stored in the database 18 may include, for example, routing instructions associated with the dialed telephone number.
- the return message from the SCP 16 may include instructions for the SSP 14 to route the call to the SN 22 .
- the return message from the SCP 16 may simply be an indication that there is no entry in the database 18 that indicates anything other than conventional telephone service should be provided for the call.
- the query and return messages may be formatted, for example, according to conventional SS7 TCAP (Transaction Capabilities Application Part) formats.
- the AIN 10 illustrated in FIG. 1 includes only one SSP 14 , one SCP 16 , one database 18 , one STP 20 , and one SN 22 , it is understood that the AIN 10 may further include an additional number of these components as well as other network components that are not included in FIG. 1 for purposes of clarity.
- the AIN 10 may additionally include redundant SCP's and STP's to take over if the SCP 16 or the STP 20 should fail.
- the AIN 10 may include regional STP's and regional SCP's in communication with, for example, the local STP 20 , for routing and servicing calls between different LECs.
- FIG. 2 illustrates a system 40 employed by an emergency notification service, such as the Lucent family 911 notification service.
- the system 40 includes the AIN 10 as described hereinabove with regard to FIG. 1 , and also includes a web server 42 and a Service Management System (SMS) 44 .
- the web server 42 is connected to the Internet 46 , and is in communication with the SMS 44 via communication link 48 .
- Communication link 48 may be, for example, a portion of the communication network that includes communication link 38 .
- the SMS 44 is an operations support system used to facilitate the provisioning and administration of service data required by the SCP 16 .
- the SMS 44 includes a network server and a database, and may be used to centralize and manage the service logic and customer data residing at the SCP 16 .
- the SMS 44 includes programmable applications executable by the SMS 44 that provide access to the service management functions of the SMS 44 such as, for example, subscriber provisioning, and provide a direct interface to the SMS database.
- the SMS 44 is in communication with the SCP 16 via communication link 50 .
- Communication link 50 may be, for example, a portion of the communication network that includes communication link 38 .
- the service is provisioned at the SCP 16 .
- Information provisioned at the SCP 16 may include the name of the customer, the customer's landline telephone number, and the telephone numbers that the customer wishes to be called when a 911 call originates from the customer's landline telephone number.
- the customer may designate up to five telephone numbers that the customer wishes to be called when a 911 call originates from the customer's landline telephone number.
- a system administrator may provision the service by entering the information via the SMS 44 , which in turn passes the information to the SCP 16 , which then populates the database 18 with the information.
- the subscriber may provision the service remotely via the Internet 46 by providing the information to the web server 42 , which in turn passes the information to the SMS 44 for provisioning at the SCP 16 as described hereinbefore.
- a 911 call When a 911 call is placed from the customer's landline telephone 26 , the call is passed to the SSP 14 via the subscriber line 24 connecting the landline telephone 26 to the SSP 14 .
- the call activates a trigger defined at the SSP 14 , resulting in a query message being sent to the SCP 16 via the STP 20 .
- a trigger is an event associated with a particular subscriber line 24 that causes the SSP 14 to query the SCP 16 for instructions as to how to process the call.
- a trigger may be an originating trigger for a call originating from the customer premises or a terminating trigger for a call terminating at the customer premises.
- the query message includes a caller ID message giving the customer's telephone number, and the date and time that the 911 call was made.
- the caller ID message may also include the name of the customer.
- the SCP 16 receives the query message and returns a response message to the SSP 14 via the STP 20 .
- the response message instructs the SSP 14 to process the 911 call as a switch-based feature.
- the SSP 14 then routes the 911 call to a Public Safety Answering Point (PSAP), where a PSAP operator verifies or obtains the caller's location, determines the nature of the emergency, and decides the appropriate emergency response.
- PSAP Public Safety Answering Point
- the PSAP operator may dispatch help directly, or may transfer the caller to a secondary PSAP from which help will be dispatched. Secondary PSAP's are typically located at fire dispatch areas, municipal police force headquarters, or ambulance dispatch centers.
- the SCP 16 In addition to returning the response message to the SSP 14 , the SCP 16 also uses the information provided by the query message to search the database 18 to determine if the customer is a subscriber to the family 911 notification service. If the customer is subscribed to the service, the calling of the designated telephone numbers is initiated. If the calling is initiated, the SCP 16 makes a TCP/IP connection request to the SN 22 . Once the TCP/IP connection is established between the SCP 16 and the SN 22 , the SCP 16 transmits information to the SN 22 . The information includes the telephone number from which the 911 call was made, the time and date of the 911 call, and the designated telephone numbers to be notified for the subscriber. Once the information has been received at the SN 22 , the TCP/IP connection between the SCP 16 and the SN 22 is released.
- the SN 22 will then begin placing outgoing calls to the designated telephone numbers in a sequential manner. As described hereinbefore, if the SN 22 reaches a live person at one of the designated telephone numbers, the SN 22 announces that the incoming call is from the family 911 notification service, that a 911 call was placed, the telephone number from which the 911 call was placed, and the time that the 911 call was placed. The SN 22 stops dialing the designated telephone numbers once the announcement has been played to a live person. If the SN 22 has not reached a live person after all of the designated numbers have been called, the SN 22 waits for five minutes before beginning to call the designated telephone numbers again. This process repeats itself for the first hour following the placement of the 911 call. During the first hour, if the SN 22 reaches an answering machine or a voice mail system at one of the designated telephone numbers, the SN 22 does not transmit the announcement.
- the SN 22 If the SN 22 has not reached a live person within the first hour, the SN 22 continues to call the designated telephone numbers according to the specified priority. However, if the SN 22 reaches an answering machine or a voice mail system after the first hour, the SN 22 transmits an announcement that the incoming call is from the family 911 notification service, that the service has been trying to reach the person associated with the designated telephone number to notify them that a 911 call has been placed, the telephone number from which the 911 call was placed, and the time that the call was placed. The SN 22 stops dialing the designated telephone numbers once this announcement has been played to an answering machine or a voice mail system. If the service has not reached a live person, an answering machine, or a voice mail system within the first twenty-four hours following the placement of the 911 call, the SN 22 stops dialing the designated telephone numbers.
- FIG. 3 illustrates an emergency notification system according to one embodiment of the present invention.
- the system 60 includes a switch 62 , a database server 64 , a message server 66 , and a web server 68 .
- the system 60 also includes an STP 20 as described hereinbefore.
- the system 60 is used to provide an emergency notification service that transmits a message that an emergency communication was placed from terminal equipment associated with a subscriber to the service.
- the switch 62 may be in communication with terminal equipment such as, for example, a landline telephone 26 associated with the subscriber via a subscriber line such as, for example, subscriber line 24 .
- the switch 62 may be a service switching point such as, for example, the SSP 14 as described hereinabove.
- the switch 62 may include an originating trigger such as, for example, an N11 trigger, and the N11 trigger may be, for example, a 911 trigger.
- the switch 62 may also be in communication with the STP 20 via communication link 28 and with the message server 66 via communication link 34 .
- the database server 64 is in communication with the switch 62 via the STP 20 and communication links 28 and 30 , and may be a service control point similar to the SCP 16 described hereinbefore.
- the database server 64 may store call-processing instructions, and may supply instructions to the switch 62 concerning how to process an incoming call.
- the call processing instructions may be in the form of a computer program product including a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit.
- the database server 64 may supply the switch with instructions for processing an emergency communication received at the switch 62 .
- the database server 64 may be similar to the SCP 16 , the database server 64 is markedly different from the SCP 16 in that the database server 62 does not maintain the provisioned subscriber information (i.e., subscriber name, subscriber telephone number, telephone numbers to be called, etc.) associated with the emergency notification service. Therefore, the database server 64 may be provided with less storage capacity and require less database maintenance than the SCP 16 . Accordingly, the database server 64 may have a lower initial cost than the SCP 16 and have lower maintenance costs associated therewith.
- the database server 64 may have a lower initial cost than the SCP 16 and have lower maintenance costs associated therewith.
- the database server 64 may also supply information associated with an incoming call to the message server 66 .
- the database server 64 may supply the message server 66 with information associated with an emergency communication.
- information may have been provided to the database server 64 by the switch 62 and may include, for example, the name of the person associated with a subscriber line 24 from which the emergency communication originated, the telephone number from which the emergency communication originated, and the date and time that the emergency communication was received at the switch 62 .
- the message server 66 is in communication with the database server 64 via communication link 70 , and may transmit a message after an emergency communication is received at the switch 62 .
- the message server 66 may be any type of low-cost computer suitable for transmitting an oral message and/or a textual message.
- the message server may include a processing circuit executing processing instructions stored on a computer program product including a storage medium readable by the processing. Whereas the SN 22 employed in system 40 has an initial cost of approximately one-half million dollars, the message server 66 only has an initial cost of approximately ten-thousand dollars.
- the message server 66 may be a telephony server that may transmit an oral message.
- the message server 66 may be an electronic mail server that may transmit a textual message.
- Communication link 70 may be, for example, a portion of a communication network such as, for example, a Local Area Network (LAN), a Metropolitan Area Network (MAN), or a Wide Area Network (WAN).
- the message server 66 may also be in communication with the PSTN 12 via communication link 36 .
- the web server 68 is in communication with the message server 66 via communication link 72 , and may supply the message server 66 with information associated with a subscriber to an emergency notification service.
- Communication link 72 may be, for example, a portion of the communication network that includes communication link 70 .
- the web server 68 may be connected to the Internet 46 , and the subscriber information may be remotely provisioned and maintained at the web server 68 via the Internet 46 .
- Such subscriber information may include, for example, the subscriber's name, a telephone number associated with the subscriber, designated telephone numbers, and designated electronic mail addresses.
- Designated telephone numbers may be provisioned to receive a notification in the form of an oral message, and designated electronic mail addresses may be provisioned to receive a notification in the form of a textual message, if an emergency communication is placed from terminal equipment associated with the subscriber. More than five telephone numbers and more than five electronic mail addresses may be provisioned at the web server 68 . Provisioning subscriber information directly to the web server 68 reduces the cost and complexity of the emergency notification system.
- FIGS. 4A and 4B illustrate an embodiment of a process flow of the emergency notification system 60 of FIG. 3 .
- the emergency notification service becomes operational for the subscriber.
- the process begins at block 80 , where an emergency communication is originated from customer premises equipment.
- the customer premises equipment may be, for example, a landline telephone 26 connected to a subscriber line 24 .
- the process proceeds to block 82 , where the switch 62 receives the emergency communication via the PSTN 12 .
- the process proceeds to block 84 , where the received emergency communication activates a trigger defined at the switch 14 .
- the trigger may be an originating trigger such as, for example, an N11 trigger, and the N11 trigger may be, for example, a 911 trigger.
- the process proceeds to block 86 , where the activated trigger causes the switch 62 to generate a query message to determine how the emergency communication should be processed.
- the query message may include identification information such as, for example, the telephone number that the emergency communication originated from, the name of the person associated with the telephone number, and the date and time the emergency communication was received at the switch 62 , etc.
- the process proceeds to block 88 , where the switch 62 transmits the query message to the STP 20 via communication link 28 . From block 88 , the process proceeds to block 90 , where the STP 20 receives the query message and transmits the query message to the database server 64 via communication link 30 . From block 90 , the process proceeds to block 92 , where the database server 64 receives the query message originated at the switch 62 .
- the process proceeds to block 94 , where the database server 64 generates a response message to the query message and transmits the response message to the STP 20 via communication link 30 .
- the response message includes an instruction detailing how the switch 62 should process the emergency communication.
- the response message may include an instruction for the switch 62 to process the emergency communication as a switch-based feature.
- the process proceeds to block 96 , where the STP 20 receives the response message from the database server 64 and transmits the response message to the switch 62 via communication link 28 .
- the process proceeds to block 98 , where the switch 62 receives and interprets the response message originated at the database server 64 .
- the process proceeds to block 100 , where the switch 62 routes the emergency communication to a Public Safety Answering Point (PSAP), where a PSAP operator processes the call in accordance with well-known procedures.
- PSAP Public Safety Answering Point
- the process proceeds from block 102 to block 104 , where the database server 64 transmits the identification information included in the query message to the message server 66 via communication link 70 .
- the process proceeds to block 106 , where the message server 66 receives the identification information, and requests that a TCP/IP connection be established between the message server 66 and the web server 68 .
- the process proceeds from block 106 to block 108 , where the message server 66 transmits a query message to the web server 68 via communication link 72 to determine whether the person associated with the telephone number that the emergency communication originated from has been provisioned as a subscriber to the emergency notification service. From block 108 , the process proceeds to block 110 , where the web server 68 receives the query message and at step 111 determines whether the person has been provisioned as a subscriber to the service. If the person has not been provisioned as a subscriber to the emergency notification service, the process ends at step 113 .
- the process proceeds from block 111 to block 112 , where the web server 68 transmits the provisioned telephone numbers and electronic mail addresses to the message server 66 via communication link 72 . From block 112 , the process proceeds to block 114 , where the message server 66 receives the provisioned telephone numbers and electronic mail addresses, and starts the notification process by placing outgoing calls to the provisioned telephone numbers via the PSTN 12 , and/or transmitting textual messages to the provisioned electronic mail addresses over the Internet 46 via the web server 68 .
- the outgoing calls may be placed simultaneously or in a sequential order specified by the subscriber, and the electronic mail messages may be transmitted simultaneously or in a sequential order specified by the subscriber.
- the outgoing calls are placed concurrently with the transmission of the electronic mail messages.
- the message server 66 may play an announcement that the call is from an emergency notification service, that the service has received an emergency communication originated from a telephone number associated with the subscriber, the name of the subscriber, and the date and time the emergency communication was received. Once an outgoing call has been answered at a provisioned telephone number, and the message server 66 has played the announcement, the message server 66 will stop calling that particular telephone number. If an outgoing call has not been answered at a provisioned telephone number, the message server 66 may continue to call the provisioned telephone number until the call has been answered and the announcement has been played.
- Electronic mail messages transmitted by the message server 66 to the provisioned electronic mail addresses may include a textual message notifying the person associated with the electronic mail address that the message is from an emergency notification service, that the service has received an emergency communication originated from a telephone number associated with the subscriber, the name of the subscriber, and the date and time the emergency communication was received.
- the message server 66 may transmit the electronic mail messages once to each provisioned electronic mail address. However, if the message server 66 receives an indication that the electronic mail message was not delivered successfully to a particular provisioned electronic mail address, the message server 66 may attempt to transmit the electronic mail message to the particular provisioned electronic mail address more than once.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Marketing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Emergency Management (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 13/584,906, filed Aug. 14, 2012, the entire contents of which are incorporated herein by reference, which is a continuation of U.S. patent application Ser. No. 12/608,035, filed Oct. 29, 2009, now U.S. Pat. No. 8,259,909, the entire contents of which are incorporated herein by reference, which is a continuation of U.S. patent application Ser. No. 11/272,286, filed Nov. 9, 2005, now U.S. Pat. No. 7,627,092, the entire contents of which are incorporated herein by reference, which is a continuation of U.S. patent application Ser. No. 10/457,684, filed Jun. 9, 2003, now U.S. Pat. No. 7,016,477, the entire contents of which are incorporated herein by reference, which is a continuation of U.S. patent application Ser. No. 09/995,142, filed Nov. 27, 2001, now U.S. Pat. No. 6,792,081, the entire contents of which are incorporated herein by reference.
- The present invention is directed generally to notification systems, and, more particularly, to an emergency notification system.
- In today's society, there are increasing numbers of people who work at locations other than their homes. In many instances, there are young children who spend considerable amounts of time at home without adult supervision while their parents are working. Such situations can be very stressful to a working parent because of the uncertainty of knowing exactly what the unsupervised children may be doing. There are also a growing number of exactly people who have elderly parents living alone. Understandably, there are many people who, for various reasons, desire to be notified as soon as possible if an emergency call is placed from a location that concerns them.
- One service that has attempted to address this desire is the family 911 notification service offered by Lucent Technologies Inc., Murray Hill, N.J. Each subscriber to the service may select up to five telephone numbers, each associated with a particular person, that they wish to be called if a 911 call is placed from a landline telephone associated with the subscriber. The selected telephone numbers may be given a priority from first to fifth and may be associated with landline telephones and/or wireless telephones. The service operates in the manner described hereinbelow.
- After a 911 call has been placed from a landline telephone associated with a subscriber, the service calls the selected telephone numbers in a sequential order according to the specified priority. If the family 911 notification service reaches a live person at one of the selected telephone numbers, the service plays an announcement. The announcement informs the person that the incoming call is from the family 911 notification service and that a 911 call was placed. The announcement also informs the person as to the time that the 911 call was placed and the telephone number that the 911 call was placed from. The service stops calling the selected telephone numbers once the information has been provided to a live person. If the service has not reached a live person after all of the selected telephone numbers have been called, the service waits for five minutes before beginning to call the selected telephone numbers again. This process repeats itself for the first hour following the placement of the 911 call. During the first hour, if the service reaches an answering machine or a voice mail system at one of the selected telephone numbers, the service does not play an announcement.
- If the service has not reached a live person within the first hour, the service continues to call the selected telephone numbers according to the specified priority. However, if the service reaches an answering machine or a voice mail system after the first hour, the service plays a slightly different announcement. This announcement informs the answering machine or voice mail system that the incoming call is from the family 911 notification service and that the service has been trying to reach the person associated with the selected telephone number to notify them that a 911 call has been placed. This announcement also informs the answering machine or the voice mail system as to the time that the 911 call was placed and the telephone number from which the 911 call was placed. The service stops dialing the selected telephone numbers once an announcement has been played to an answering machine or a voice mail system. If the service has not reached a live person, an answering machine, or a voice mail system within the first twenty-four hours following the placement of the 911 call, the service stops dialing the selected telephone numbers.
- There are several shortcomings associated with Lucent's family 911 notification service. For example, the means used to provision the selected telephone numbers add complexity and cost to the service, the hardware used to implement the service is relatively expensive to acquire and maintain, and the service only offers oral notification that a 911 call has been placed. Thus, there exists a need for an emergency notification system that overcomes the limitations, shortcomings, and disadvantages of the emergency notification system described hereinabove.
- The present invention meets the identified need, as well as other needs, as will be more fully understood following a review of this specification and the accompanying drawings. The present invention is directed to an emergency notification system. The system includes a first server for receiving an emergency communication from a telecommunications network and for transmitting a message to a subscriber of the emergency notification system; and a second server in communication with the first server, the second server for supplying the first server with information associated with a subscriber.
- For the present invention to be clearly understood and readily practiced, the present invention will be described in conjunction with the following figures, wherein:
-
FIG. 1 is a block diagram of an Advanced Intelligent Network (AIN) for integration with a public switched telephone network; -
FIG. 2 illustrates a prior art emergency notification system; -
FIG. 3 illustrates an emergency notification system according to one embodiment of the present invention; and -
FIGS. 4A and 4B illustrate an embodiment of a process flow of the emergency notification system ofFIG. 3 . - It is to be understood that the figures and descriptions of the present invention have been simplified to illustrate elements that are relevant for a clear understanding of the present invention, while eliminating, for purposes of clarity, other elements of a conventional telecommunications network. For example, certain operating system details and modules of certain of the intelligent platforms of the network are not described herein. Those of ordinary skill in the art will recognize, however, that these and other elements may be desirable in a typical telecommunications network. However, because such elements are well known in the art, and because they do not facilitate a better understanding of the present invention, a discussion of such elements is not provided herein.
- The term “calling party” is used herein generally to refer to the person or unit that initiates a telecommunication. The calling party may also be referred to herein as “caller.” The term “called party” is used herein generally to refer to the person or unit that answers or responds to the call or communication. In some cases the calling party or the called party may not be a person, but may be a device such as an answering machine, a voice mail system, etc. The term “communication” is used herein to include all messages or calls that may be exchanged between a calling party and a called party, including voice, data and video messages. The term “communication” is used synonymously herein with the term “call” unless a distinction is noted. The term “subscriber” is used herein to generally refer to a subscriber of the described emergency notification service.
- The present invention is directed to an emergency notification system. According to one embodiment, the emergency notification system utilizes the intelligent functionality of an Advanced Intelligent Network (AIN). The AIN is a network used to provide enhanced voice and data services and dynamic routing capabilities to a conventional telephone network. With AIN, the actual voice call is still transmitted over a circuit-switched network but the signaling and control takes place on a separate packet-switched network. Before describing details of the system of the present invention, a high-level description of an AIN is provided.
-
FIG. 1 is a block diagram of an Advanced Intelligent Network (AIN) 10. The AIN 10 may be employed by a Local Exchange Carrier (LEC), and may be utilized by the LEC to allow the LEC to provide call processing features and services that are not embedded within conventional switching circuits of a conventional telephone system such as, for example, the Public Switched Telephone Network (PSTN) 12. As illustrated inFIG. 1 , the AIN 10 includes a Service Switching Point (SSP) 14, a Signal Control Point (SCP) 16, adatabase 18, a Signal Transfer Point (STP) 20, and a Service Node (SN) 22. - In a conventional telephone system, central office (CO) switches are used to interconnect customer premises equipment (i.e., terminal equipment such as telephones, modems, or answering machines that are connected to the telephone network and reside on the customer's premises). For the AIN 10 illustrated in
FIG. 1 , theSSP 14 is a switch used to interconnect customer premises equipment via thePSTN 12. The difference between theSSP 14 and the CO switch of a conventional telephone system is that theSSP 14 provides intelligent network functionality. - The
SSP 14 has one ormore subscriber lines 24 connected thereto. The subscriber lines 24 may be, for example, local loops comprising conventional twisted pair loop circuits connected between theSSP 14 and the customer premises, or thesubscriber lines 24 may be trunk circuits, such as T-1 trunk circuits. The number ofsubscriber lines 24 connected to anSSP 14 may be on the order of ten thousand to one hundred thousand lines. Thesubscriber line 24 is connected to a terminating piece of customer premises equipment, represented inFIG. 1 by alandline telephone 26. Alternatively, the terminating equipment may be any other type of communications unit such as, for example, a telecopier, a personal computer, a modem, an answering machine, or a private branch exchange (PBX) switching system. - The
SCP 16 is a server, associated with adatabase 18, and provides instructions to theSSP 14 and theSN 22 as requested and required. TheSCP 16 may be an intelligent database server such as, for example, an Intelligent Network Service Control Point available from Lucent Technologies Inc., Murray Hill, N.J. Thedatabase 18 is for storing customer information used in providing enhanced calling services, such as the service provided by the emergency notification system of the present invention, and may reside at theSCP 16. The intelligent functionality of theSCP 16 may be realized by application programs, such as programmable Service Program Applications (SPA), which are executed by theSCP 16. Although the AIN 10 illustrated inFIG. 1 only shows onedatabase 18 associated with theSCP 16, it is understood that more than onedatabase 18 may be associated with theSCP 16. - The
STP 20 is a packet switch that routes signaling and control messages between theSSP 14 and theSCP 16. As illustrated inFIG. 1 , theSTP 20 is in communication with theSSP 14 viacommunication link 28 and with theSCP 16 viacommunication link 30. Communication links 28, 30 may employ, for example, the Signaling System 7 (SS7) signaling protocol. - The
SN 22 may provide an enhanced feature or service that requires an audio connection between theSN 22 and an answering machine connected to asubscriber line 24, or between theSN 22 and alandline telephone 26 from which an emergency communication has been placed. TheSN 22 may be any type of AIN-compliant service node, and may be, for example, a Compact Services Node (CSN) available from Lucent Technologies Inc., Murray Hill, N.J. Similar to theSCP 16, the intelligent functionality of theSN 22 may be realized by programmable applications executable by theSN 22. - The
SN 22 is in communication with theSSP 14 viacommunication link 34, with thePSTN 12 viacommunication link 36, and with theSCP 16 viacommunication link 38. Communication links 34 and 36 may be, for example, an Integrated Service Digital Network (ISDN) Primary Rate Interface (PRI), an ISDN Basic Rate Interface (BRI), or a T-1 trunk circuit.Communication link 38 may be, for example, a portion of a communication network such as, for example, a Local Area Network (LAN), a Metropolitan Area Network (MAN), or a Wide Area Network (WAN). - The basic operation of the AIN 10 illustrated in
FIG. 1 is described hereinbelow. When a call originating from thelandline telephone 26 is received at theSSP 14 via thePSTN 12, theSSP 14 generates a query to determine how the call should be processed. The query generated by theSSP 14 is transmitted via out-of-band signaling through theSTP 20 to theSCP 16. - The
SCP 16 interprets the query based on information provided by theSSP 14 and information stored in thedatabase 18 to determine whether some customized call feature or enhanced service should be implemented for the particular call, or whether conventional dial-up telephone service should be provided. The information provided by theSSP 14 may include, for example, the originating telephone number, the name of the calling party, and the telephone number dialed by the calling party. The information stored in thedatabase 18 may include, for example, routing instructions associated with the dialed telephone number. Once theSCP 16 determines how the call is to be processed, it returns a message through theSTP 20 to theSSP 14 instructing theSSP 14 how the call should be processed. The instructions may be to take some special action as a result of a customized calling service or enhanced feature. For example, for an enhanced calling feature requiring the capabilities of theSN 22, the return message from theSCP 16 may include instructions for theSSP 14 to route the call to theSN 22. In addition, the return message from theSCP 16 may simply be an indication that there is no entry in thedatabase 18 that indicates anything other than conventional telephone service should be provided for the call. The query and return messages may be formatted, for example, according to conventional SS7 TCAP (Transaction Capabilities Application Part) formats. - Although the AIN 10 illustrated in
FIG. 1 includes only oneSSP 14, oneSCP 16, onedatabase 18, oneSTP 20, and oneSN 22, it is understood that the AIN 10 may further include an additional number of these components as well as other network components that are not included inFIG. 1 for purposes of clarity. For example, the AIN 10 may additionally include redundant SCP's and STP's to take over if theSCP 16 or theSTP 20 should fail. Further, the AIN 10 may include regional STP's and regional SCP's in communication with, for example, thelocal STP 20, for routing and servicing calls between different LECs. -
FIG. 2 illustrates asystem 40 employed by an emergency notification service, such as the Lucent family 911 notification service. Thesystem 40 includes the AIN 10 as described hereinabove with regard toFIG. 1 , and also includes aweb server 42 and a Service Management System (SMS) 44. Theweb server 42 is connected to theInternet 46, and is in communication with theSMS 44 viacommunication link 48.Communication link 48 may be, for example, a portion of the communication network that includescommunication link 38. - The
SMS 44 is an operations support system used to facilitate the provisioning and administration of service data required by theSCP 16. TheSMS 44 includes a network server and a database, and may be used to centralize and manage the service logic and customer data residing at theSCP 16. TheSMS 44 includes programmable applications executable by theSMS 44 that provide access to the service management functions of theSMS 44 such as, for example, subscriber provisioning, and provide a direct interface to the SMS database. TheSMS 44 is in communication with theSCP 16 via communication link 50. Communication link 50 may be, for example, a portion of the communication network that includescommunication link 38. - When a customer subscribes to the emergency notification service, the service is provisioned at the
SCP 16. Information provisioned at theSCP 16 may include the name of the customer, the customer's landline telephone number, and the telephone numbers that the customer wishes to be called when a 911 call originates from the customer's landline telephone number. The customer may designate up to five telephone numbers that the customer wishes to be called when a 911 call originates from the customer's landline telephone number. A system administrator may provision the service by entering the information via theSMS 44, which in turn passes the information to theSCP 16, which then populates thedatabase 18 with the information. Alternatively, the subscriber may provision the service remotely via theInternet 46 by providing the information to theweb server 42, which in turn passes the information to theSMS 44 for provisioning at theSCP 16 as described hereinbefore. - When a 911 call is placed from the customer's
landline telephone 26, the call is passed to theSSP 14 via thesubscriber line 24 connecting thelandline telephone 26 to theSSP 14. The call activates a trigger defined at theSSP 14, resulting in a query message being sent to theSCP 16 via theSTP 20. A trigger is an event associated with aparticular subscriber line 24 that causes theSSP 14 to query theSCP 16 for instructions as to how to process the call. A trigger may be an originating trigger for a call originating from the customer premises or a terminating trigger for a call terminating at the customer premises. The query message includes a caller ID message giving the customer's telephone number, and the date and time that the 911 call was made. The caller ID message may also include the name of the customer. TheSCP 16 receives the query message and returns a response message to theSSP 14 via theSTP 20. The response message instructs theSSP 14 to process the 911 call as a switch-based feature. TheSSP 14 then routes the 911 call to a Public Safety Answering Point (PSAP), where a PSAP operator verifies or obtains the caller's location, determines the nature of the emergency, and decides the appropriate emergency response. For example, the PSAP operator may dispatch help directly, or may transfer the caller to a secondary PSAP from which help will be dispatched. Secondary PSAP's are typically located at fire dispatch areas, municipal police force headquarters, or ambulance dispatch centers. - In addition to returning the response message to the
SSP 14, theSCP 16 also uses the information provided by the query message to search thedatabase 18 to determine if the customer is a subscriber to the family 911 notification service. If the customer is subscribed to the service, the calling of the designated telephone numbers is initiated. If the calling is initiated, theSCP 16 makes a TCP/IP connection request to theSN 22. Once the TCP/IP connection is established between theSCP 16 and theSN 22, theSCP 16 transmits information to theSN 22. The information includes the telephone number from which the 911 call was made, the time and date of the 911 call, and the designated telephone numbers to be notified for the subscriber. Once the information has been received at theSN 22, the TCP/IP connection between theSCP 16 and theSN 22 is released. - The
SN 22 will then begin placing outgoing calls to the designated telephone numbers in a sequential manner. As described hereinbefore, if theSN 22 reaches a live person at one of the designated telephone numbers, theSN 22 announces that the incoming call is from the family 911 notification service, that a 911 call was placed, the telephone number from which the 911 call was placed, and the time that the 911 call was placed. TheSN 22 stops dialing the designated telephone numbers once the announcement has been played to a live person. If theSN 22 has not reached a live person after all of the designated numbers have been called, theSN 22 waits for five minutes before beginning to call the designated telephone numbers again. This process repeats itself for the first hour following the placement of the 911 call. During the first hour, if theSN 22 reaches an answering machine or a voice mail system at one of the designated telephone numbers, theSN 22 does not transmit the announcement. - If the
SN 22 has not reached a live person within the first hour, theSN 22 continues to call the designated telephone numbers according to the specified priority. However, if theSN 22 reaches an answering machine or a voice mail system after the first hour, theSN 22 transmits an announcement that the incoming call is from the family 911 notification service, that the service has been trying to reach the person associated with the designated telephone number to notify them that a 911 call has been placed, the telephone number from which the 911 call was placed, and the time that the call was placed. TheSN 22 stops dialing the designated telephone numbers once this announcement has been played to an answering machine or a voice mail system. If the service has not reached a live person, an answering machine, or a voice mail system within the first twenty-four hours following the placement of the 911 call, theSN 22 stops dialing the designated telephone numbers. - One skilled in the art will recognize several shortcomings associated with the above-described
system 40. For example, all of the subscriber information needed to operate the notification service must be provisioned via theSMS 44, adding cost and complexity to thesystem 40. Furthermore, storing this information at theSCP 16 requires increased storage capacity at theSCP 16, resulting in increased acquisition and maintenance costs. In addition, theSN 22 employed in thesystem 40 is a very expensive network element, often having an initial purchase price of approximately one-half million dollars. -
FIG. 3 illustrates an emergency notification system according to one embodiment of the present invention. The system 60 includes aswitch 62, adatabase server 64, amessage server 66, and aweb server 68. The system 60 also includes anSTP 20 as described hereinbefore. The system 60 is used to provide an emergency notification service that transmits a message that an emergency communication was placed from terminal equipment associated with a subscriber to the service. - The
switch 62 may be in communication with terminal equipment such as, for example, alandline telephone 26 associated with the subscriber via a subscriber line such as, for example,subscriber line 24. According to one embodiment, theswitch 62 may be a service switching point such as, for example, theSSP 14 as described hereinabove. Theswitch 62 may include an originating trigger such as, for example, an N11 trigger, and the N11 trigger may be, for example, a 911 trigger. Theswitch 62 may also be in communication with theSTP 20 viacommunication link 28 and with themessage server 66 viacommunication link 34. - The
database server 64 is in communication with theswitch 62 via theSTP 20 andcommunication links SCP 16 described hereinbefore. Thedatabase server 64 may store call-processing instructions, and may supply instructions to theswitch 62 concerning how to process an incoming call. The call processing instructions may be in the form of a computer program product including a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit. For example, according to one embodiment, thedatabase server 64 may supply the switch with instructions for processing an emergency communication received at theswitch 62. Although thedatabase server 64 may be similar to theSCP 16, thedatabase server 64 is markedly different from theSCP 16 in that thedatabase server 62 does not maintain the provisioned subscriber information (i.e., subscriber name, subscriber telephone number, telephone numbers to be called, etc.) associated with the emergency notification service. Therefore, thedatabase server 64 may be provided with less storage capacity and require less database maintenance than theSCP 16. Accordingly, thedatabase server 64 may have a lower initial cost than theSCP 16 and have lower maintenance costs associated therewith. - The
database server 64 may also supply information associated with an incoming call to themessage server 66. For example, thedatabase server 64 may supply themessage server 66 with information associated with an emergency communication. Such information may have been provided to thedatabase server 64 by theswitch 62 and may include, for example, the name of the person associated with asubscriber line 24 from which the emergency communication originated, the telephone number from which the emergency communication originated, and the date and time that the emergency communication was received at theswitch 62. - The
message server 66 is in communication with thedatabase server 64 viacommunication link 70, and may transmit a message after an emergency communication is received at theswitch 62. Themessage server 66 may be any type of low-cost computer suitable for transmitting an oral message and/or a textual message. The message server may include a processing circuit executing processing instructions stored on a computer program product including a storage medium readable by the processing. Whereas theSN 22 employed insystem 40 has an initial cost of approximately one-half million dollars, themessage server 66 only has an initial cost of approximately ten-thousand dollars. According to one embodiment, themessage server 66 may be a telephony server that may transmit an oral message. According to another embodiment, themessage server 66 may be an electronic mail server that may transmit a textual message.Communication link 70 may be, for example, a portion of a communication network such as, for example, a Local Area Network (LAN), a Metropolitan Area Network (MAN), or a Wide Area Network (WAN). Themessage server 66 may also be in communication with thePSTN 12 viacommunication link 36. - The
web server 68 is in communication with themessage server 66 viacommunication link 72, and may supply themessage server 66 with information associated with a subscriber to an emergency notification service.Communication link 72 may be, for example, a portion of the communication network that includescommunication link 70. Theweb server 68 may be connected to theInternet 46, and the subscriber information may be remotely provisioned and maintained at theweb server 68 via theInternet 46. Such subscriber information may include, for example, the subscriber's name, a telephone number associated with the subscriber, designated telephone numbers, and designated electronic mail addresses. Designated telephone numbers may be provisioned to receive a notification in the form of an oral message, and designated electronic mail addresses may be provisioned to receive a notification in the form of a textual message, if an emergency communication is placed from terminal equipment associated with the subscriber. More than five telephone numbers and more than five electronic mail addresses may be provisioned at theweb server 68. Provisioning subscriber information directly to theweb server 68 reduces the cost and complexity of the emergency notification system. -
FIGS. 4A and 4B illustrate an embodiment of a process flow of the emergency notification system 60 ofFIG. 3 . After the subscriber information has been provisioned at theweb server 68 via theInternet 46, the emergency notification service becomes operational for the subscriber. The process begins atblock 80, where an emergency communication is originated from customer premises equipment. The customer premises equipment may be, for example, alandline telephone 26 connected to asubscriber line 24. - From
block 80, the process proceeds to block 82, where theswitch 62 receives the emergency communication via thePSTN 12. Fromblock 82, the process proceeds to block 84, where the received emergency communication activates a trigger defined at theswitch 14. The trigger may be an originating trigger such as, for example, an N11 trigger, and the N11 trigger may be, for example, a 911 trigger. Fromblock 84, the process proceeds to block 86, where the activated trigger causes theswitch 62 to generate a query message to determine how the emergency communication should be processed. The query message may include identification information such as, for example, the telephone number that the emergency communication originated from, the name of the person associated with the telephone number, and the date and time the emergency communication was received at theswitch 62, etc. Fromblock 86, the process proceeds to block 88, where theswitch 62 transmits the query message to theSTP 20 viacommunication link 28. Fromblock 88, the process proceeds to block 90, where theSTP 20 receives the query message and transmits the query message to thedatabase server 64 viacommunication link 30. Fromblock 90, the process proceeds to block 92, where thedatabase server 64 receives the query message originated at theswitch 62. - From
block 92, the process proceeds to block 94, where thedatabase server 64 generates a response message to the query message and transmits the response message to theSTP 20 viacommunication link 30. The response message includes an instruction detailing how theswitch 62 should process the emergency communication. For example, the response message may include an instruction for theswitch 62 to process the emergency communication as a switch-based feature. Fromblock 94, the process proceeds to block 96, where theSTP 20 receives the response message from thedatabase server 64 and transmits the response message to theswitch 62 viacommunication link 28. Fromblock 96, the process proceeds to block 98, where theswitch 62 receives and interprets the response message originated at thedatabase server 64. Fromblock 98, the process proceeds to block 100, where theswitch 62 routes the emergency communication to a Public Safety Answering Point (PSAP), where a PSAP operator processes the call in accordance with well-known procedures. - While the process is proceeding from
block 92 to block 94, the process also proceeds fromblock 92 to block 102, where thedatabase server 64 requests a TCP/IP connection be established between thedatabase server 64 and themessage server 66. Once the TCP/IP connection has been established, the process proceeds fromblock 102 to block 104, where thedatabase server 64 transmits the identification information included in the query message to themessage server 66 viacommunication link 70. Fromblock 104, the process proceeds to block 106, where themessage server 66 receives the identification information, and requests that a TCP/IP connection be established between themessage server 66 and theweb server 68. Once the TCP/IP connection has been established, the process proceeds fromblock 106 to block 108, where themessage server 66 transmits a query message to theweb server 68 viacommunication link 72 to determine whether the person associated with the telephone number that the emergency communication originated from has been provisioned as a subscriber to the emergency notification service. Fromblock 108, the process proceeds to block 110, where theweb server 68 receives the query message and atstep 111 determines whether the person has been provisioned as a subscriber to the service. If the person has not been provisioned as a subscriber to the emergency notification service, the process ends atstep 113. - If the person has been provisioned as a subscriber to the emergency notification service, the process proceeds from
block 111 to block 112, where theweb server 68 transmits the provisioned telephone numbers and electronic mail addresses to themessage server 66 viacommunication link 72. Fromblock 112, the process proceeds to block 114, where themessage server 66 receives the provisioned telephone numbers and electronic mail addresses, and starts the notification process by placing outgoing calls to the provisioned telephone numbers via thePSTN 12, and/or transmitting textual messages to the provisioned electronic mail addresses over theInternet 46 via theweb server 68. Depending on how the subscriber has provisioned the service, the outgoing calls may be placed simultaneously or in a sequential order specified by the subscriber, and the electronic mail messages may be transmitted simultaneously or in a sequential order specified by the subscriber. According to one embodiment, the outgoing calls are placed concurrently with the transmission of the electronic mail messages. - For outgoing calls that are answered by a live person, an answering machine, or a voice mail system, the
message server 66 may play an announcement that the call is from an emergency notification service, that the service has received an emergency communication originated from a telephone number associated with the subscriber, the name of the subscriber, and the date and time the emergency communication was received. Once an outgoing call has been answered at a provisioned telephone number, and themessage server 66 has played the announcement, themessage server 66 will stop calling that particular telephone number. If an outgoing call has not been answered at a provisioned telephone number, themessage server 66 may continue to call the provisioned telephone number until the call has been answered and the announcement has been played. - Electronic mail messages transmitted by the
message server 66 to the provisioned electronic mail addresses may include a textual message notifying the person associated with the electronic mail address that the message is from an emergency notification service, that the service has received an emergency communication originated from a telephone number associated with the subscriber, the name of the subscriber, and the date and time the emergency communication was received. Themessage server 66 may transmit the electronic mail messages once to each provisioned electronic mail address. However, if themessage server 66 receives an indication that the electronic mail message was not delivered successfully to a particular provisioned electronic mail address, themessage server 66 may attempt to transmit the electronic mail message to the particular provisioned electronic mail address more than once. - Although the present invention has been described and illustrated in detail herein with respect to certain embodiments, it is clearly understood that the same is by way of example and is not to be taken by way of limitation. It will be appreciated by those of ordinary skill in the art that numerous modifications and variations of the present invention may be implemented without departing from the spirit and scope of the present invention as described in the appended claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/186,164 US9270823B2 (en) | 2001-11-27 | 2014-02-21 | Method of notifying a party of an emergency |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/995,142 US6792081B1 (en) | 2001-11-27 | 2001-11-27 | Emergency notification system |
US10/457,684 US7016477B2 (en) | 2001-11-27 | 2003-06-09 | Method of notifying a party of an emergency |
US11/272,286 US7627092B2 (en) | 2001-11-27 | 2005-11-09 | Method of notifying a party of an emergency |
US12/608,035 US8259909B2 (en) | 2001-11-27 | 2009-10-29 | Method of notifying a party of an emergency |
US13/584,906 US8660241B2 (en) | 2001-11-27 | 2012-08-14 | Method of notifying a party of an emergency |
US14/186,164 US9270823B2 (en) | 2001-11-27 | 2014-02-21 | Method of notifying a party of an emergency |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/584,906 Continuation US8660241B2 (en) | 2001-11-27 | 2012-08-14 | Method of notifying a party of an emergency |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140314213A1 true US20140314213A1 (en) | 2014-10-23 |
US9270823B2 US9270823B2 (en) | 2016-02-23 |
Family
ID=36073975
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/457,684 Expired - Lifetime US7016477B2 (en) | 2001-11-27 | 2003-06-09 | Method of notifying a party of an emergency |
US11/272,286 Expired - Lifetime US7627092B2 (en) | 2001-11-27 | 2005-11-09 | Method of notifying a party of an emergency |
US12/608,035 Expired - Fee Related US8259909B2 (en) | 2001-11-27 | 2009-10-29 | Method of notifying a party of an emergency |
US13/584,906 Expired - Fee Related US8660241B2 (en) | 2001-11-27 | 2012-08-14 | Method of notifying a party of an emergency |
US14/186,164 Expired - Fee Related US9270823B2 (en) | 2001-11-27 | 2014-02-21 | Method of notifying a party of an emergency |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/457,684 Expired - Lifetime US7016477B2 (en) | 2001-11-27 | 2003-06-09 | Method of notifying a party of an emergency |
US11/272,286 Expired - Lifetime US7627092B2 (en) | 2001-11-27 | 2005-11-09 | Method of notifying a party of an emergency |
US12/608,035 Expired - Fee Related US8259909B2 (en) | 2001-11-27 | 2009-10-29 | Method of notifying a party of an emergency |
US13/584,906 Expired - Fee Related US8660241B2 (en) | 2001-11-27 | 2012-08-14 | Method of notifying a party of an emergency |
Country Status (1)
Country | Link |
---|---|
US (5) | US7016477B2 (en) |
Families Citing this family (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6665388B2 (en) * | 2000-12-20 | 2003-12-16 | Bellsouth Intellectual Property Corporation | System and method for monitoring incoming communications to a telecommunications device |
US8868659B2 (en) | 2001-05-15 | 2014-10-21 | Avaya Inc. | Method and apparatus for automatic notification and response |
US7016477B2 (en) | 2001-11-27 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Method of notifying a party of an emergency |
US7099677B2 (en) * | 2001-11-29 | 2006-08-29 | Bellsouth Intellectual Property Corp. | Smart call delivery GIS integration |
CN100591264C (en) * | 2003-10-23 | 2010-02-24 | 皇家飞利浦电子股份有限公司 | Heart monitor with remote alarm capability |
US20050176403A1 (en) * | 2004-01-15 | 2005-08-11 | Dimitrios Lalos | System and method for providing an emergency response via a wireless system |
US7734731B2 (en) * | 2004-03-18 | 2010-06-08 | Avaya Inc. | Method and apparatus for a publish-subscribe system with third party subscription delivery |
US20050209990A1 (en) * | 2004-03-18 | 2005-09-22 | Ordille Joann J | Method and apparatus for a publish-subscribe system with access controls |
CN1330125C (en) * | 2004-09-14 | 2007-08-01 | 中兴通讯股份有限公司 | Common data monitor method based on wired intelligent net |
US20080088428A1 (en) * | 2005-03-10 | 2008-04-17 | Brian Pitre | Dynamic Emergency Notification and Intelligence System |
US20060242652A1 (en) * | 2005-04-25 | 2006-10-26 | Thomas Stearn | Configurable alert notification system and method |
US7773729B2 (en) * | 2005-04-28 | 2010-08-10 | Techradium, Inc. | Digital notification and response system with real time translation and advertising features |
US8023621B2 (en) | 2006-01-17 | 2011-09-20 | LReady, Inc. | Dynamic family disaster plan |
US20070219812A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Subscription-based multi-person emergency shelter method |
US20070219810A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Personal profile-based private civil security subscription method |
US20070239480A1 (en) * | 2006-03-30 | 2007-10-11 | Moore Barrett H | Subscription-based catastrophe-triggered medical services facilitation method |
US20070219421A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Privately Provisioned Survival Supplies Delivery Method |
US20080195426A1 (en) * | 2006-03-17 | 2008-08-14 | Moore Barrett H | Subscription-Based Mobile Shelter Method |
US20070223658A1 (en) * | 2006-03-17 | 2007-09-27 | Moore Barrett H | Method and Apparatus to Facilitate Deployment of One or More Private Civil Security Resources |
US20070219426A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Subscription-Based Private Civil Security Resource Customization Method |
US20070225993A1 (en) * | 2006-03-17 | 2007-09-27 | Moore Barrett H | Method for Civilly-Catastrophic Event-Based Transport Service and Vehicles Therefor |
US20070276681A1 (en) * | 2006-03-17 | 2007-11-29 | Moore Barrett H | Method Of Providing Bearer Certificates For Private Civil Security Benefits |
US20070288561A1 (en) * | 2006-05-23 | 2007-12-13 | Beckhusen Fred K | Hyperlink-based notification system method |
US8170930B2 (en) | 2006-07-20 | 2012-05-01 | Metavante Corporation | System and method for automated notification |
WO2008033305A2 (en) * | 2006-09-11 | 2008-03-20 | Telecommunication Systems, Inc. | Automatic emergency call notification to pre-designated personal emergency contacts |
US20090100509A1 (en) * | 2007-08-14 | 2009-04-16 | Wendy Wolfsberger | Emergency notification system |
US10070294B2 (en) * | 2007-09-07 | 2018-09-04 | West Corporation | Processing and reporting situational information to emergency service providers |
US8284921B2 (en) * | 2007-10-01 | 2012-10-09 | Blackboard Connect Inc. | Method for dispersing the transmission of mass notifications |
US8477914B1 (en) * | 2010-12-06 | 2013-07-02 | Cox Communications, Inc. | Automated communication escalation |
US10769923B2 (en) | 2011-05-24 | 2020-09-08 | Verna Ip Holdings, Llc | Digitized voice alerts |
US8970400B2 (en) | 2011-05-24 | 2015-03-03 | Verna Ip Holdings, Llc | Unmanned vehicle civil communications systems and methods |
US8265938B1 (en) | 2011-05-24 | 2012-09-11 | Verna Ip Holdings, Llc | Voice alert methods, systems and processor-readable media |
US9736302B2 (en) | 2012-09-10 | 2017-08-15 | Tools/400 Inc. | Emergency 9-1-1 portal and application |
US10142469B2 (en) | 2012-09-10 | 2018-11-27 | Tools/400 Inc. | Emergency 9-1-1 portal and application |
US9112996B2 (en) | 2012-09-10 | 2015-08-18 | Tools/400 Inc. | Emergency 9-1-1 portal and application |
US10516780B2 (en) | 2012-09-10 | 2019-12-24 | Tools/400 Inc. | Emergency 9-1-1 portal and application |
US9438731B2 (en) | 2012-09-10 | 2016-09-06 | Tools/400 Inc. | Emergency 9-1-1 portal and application |
FI20145785A (en) | 2014-09-09 | 2016-03-10 | Solarch Oy | PROCEDURE, SYSTEM AND SERVICE PRODUCT FOR EMERGENCY MANAGEMENT |
JP5892634B1 (en) * | 2015-05-27 | 2016-03-23 | クェスタ株式会社 | Sound amplifier activation device, sound amplification amplifier and remote broadcasting system |
US10498774B2 (en) * | 2017-03-24 | 2019-12-03 | T-Mobile Usa, Inc. | Systems and methods for improved E911 call handling |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
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 |
US20010009577A1 (en) * | 1998-12-15 | 2001-07-26 | 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 (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5452350A (en) | 1992-03-09 | 1995-09-19 | Advantis | Subscriber call routing processing system |
US5590188A (en) | 1992-11-09 | 1996-12-31 | Iex Corporation | Rules-based call routing |
WO1995001063A1 (en) | 1993-06-28 | 1995-01-05 | Bellsouth Corporation | Mediation of open advanced intelligent network interface for public switched telephone network |
US5727057A (en) | 1994-12-27 | 1998-03-10 | Ag Communication Systems Corporation | Storage, transmission, communication and access to geographical positioning data linked with standard telephony numbering and encoded for use in telecommunications and related services |
US5740237A (en) | 1995-09-14 | 1998-04-14 | Bellsouth Corporation | Method and system for a singular activation of a redirection service without general activation of the service |
US6038451A (en) | 1997-06-18 | 2000-03-14 | Integrated Telecom Solutions, Inc. | Location based method of and system for forwarding wireless telephone calls |
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 |
US6208854B1 (en) | 1998-05-14 | 2001-03-27 | Ameritech Corporation | System and method for routing a call to a called party's landline or wireless communication unit |
US6301349B1 (en) | 1998-06-04 | 2001-10-09 | Bellsouth Intellectual Property Corporation | Method and system to connect an unanswered forwarded communication directly to a voice mail service |
US6442241B1 (en) * | 1999-07-15 | 2002-08-27 | William J. Tsumpes | Automated parallel and redundant subscriber contact and event notification system |
US6671350B1 (en) * | 1999-08-12 | 2003-12-30 | Life Sciences & Technology Inc. | Multiple identification access codes for a single data file |
US6829478B1 (en) * | 1999-11-19 | 2004-12-07 | Pamela G. Layton | Information management network for automated delivery of alarm notifications and other information |
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 |
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 |
US6738456B2 (en) * | 2001-09-07 | 2004-05-18 | Ronco Communications And Electronics, Inc. | School observation and supervisory 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 |
US6792081B1 (en) * | 2001-11-27 | 2004-09-14 | Bellsouth Intellectual Property Corporation | Emergency notification system |
US7016477B2 (en) | 2001-11-27 | 2006-03-21 | Bellsouth Intellectual Property Corporation | Method of notifying a party of an emergency |
-
2003
- 2003-06-09 US US10/457,684 patent/US7016477B2/en not_active Expired - Lifetime
-
2005
- 2005-11-09 US US11/272,286 patent/US7627092B2/en not_active Expired - Lifetime
-
2009
- 2009-10-29 US US12/608,035 patent/US8259909B2/en not_active Expired - Fee Related
-
2012
- 2012-08-14 US US13/584,906 patent/US8660241B2/en not_active Expired - Fee Related
-
2014
- 2014-02-21 US US14/186,164 patent/US9270823B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
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 |
US20010009577A1 (en) * | 1998-12-15 | 2001-07-26 | Ameritech Corporation | Emergency telephone call notification service system and method |
Also Published As
Publication number | Publication date |
---|---|
US8660241B2 (en) | 2014-02-25 |
US20120307984A1 (en) | 2012-12-06 |
US20030194061A1 (en) | 2003-10-16 |
US20060062354A1 (en) | 2006-03-23 |
US9270823B2 (en) | 2016-02-23 |
US8259909B2 (en) | 2012-09-04 |
US7016477B2 (en) | 2006-03-21 |
US7627092B2 (en) | 2009-12-01 |
US20100046719A1 (en) | 2010-02-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9270823B2 (en) | Method of notifying a party of an emergency | |
US6792081B1 (en) | Emergency notification system | |
US6608886B1 (en) | Method and apparatus for establishing a connection between first and second communication devices | |
US8767938B2 (en) | Telephone network control system and method | |
US8681947B2 (en) | Telephone emergency response systems and methods | |
US7388949B2 (en) | System and method for audio caller identification service | |
US6201856B1 (en) | Emergency telephone call notification service system and method | |
US6236722B1 (en) | Method and system for using TCAP signaling for improved call setup from a virtual switching point | |
US6055305A (en) | Method and apparatus for providing network-based customized call treatment | |
US6798868B1 (en) | Call notification service for use with call waiting | |
US6067347A (en) | Providing enhanced services through double SIV and personal dial tone | |
US6754325B1 (en) | Caller control of call forwarding services | |
US7079638B1 (en) | System and method for privacy screening with special information tones | |
AU745026B2 (en) | System and method for providing a busy signal to a communication | |
US7221739B1 (en) | Callback function for messaging platform in public telephone system | |
US6041112A (en) | Method for transferring switch-based information to an external network element | |
CN1295399A (en) | Method, network facility and exchange center for transmitting single message to called party | |
US6829342B2 (en) | System and method for handling voice calls and data calls | |
US7139382B1 (en) | System and method for restricting incoming calls | |
US6834103B1 (en) | Caller control of call waiting services | |
US7539289B2 (en) | Selective deactivation of a voicemail system | |
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 | |
CA2288340A1 (en) | Integrated ain busy call return/ain call forward on busy feature | |
MXPA00000406A (en) | System and method for providing a busy signal to a communication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BELLSOUTH INTELLECTUAL PROPERTY CORPORATION, DELAW Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CONTRACTOR, SUNIL H.;REEL/FRAME:032266/0994 Effective date: 20020410 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20200223 |