Method of notifying a party of an emergency

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application is a continuation of co-pending U.S. patent application Ser. No. 09/995,142, filed Nov. 27, 2001.

BACKGROUND OF INVENTION

[0002] The present invention is directed generally to notification systems, and, more particularly, to an emergency notification system.

[0003] 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.

[0004] 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.

[0005] 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.

[0006] 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.

[0007] 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.

BRIEF SUMMARY OF THE INVENTION

[0008] 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.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] For the present invention to be clearly understood and readily practiced, the present invention will be described in conjunction with the following figures, wherein:

[0010]FIG. 1 is a block diagram of an Advanced Intelligent Network (AIN) for integration with a public switched telephone network;

[0011]FIG. 2 illustrates a prior art emergency notification system;

[0012]FIG. 3 illustrates an emergency notification system according to one embodiment of the present invention; and

[0013]FIGS. 4A and 4B illustrate an embodiment of a process flow of the emergency notification system of FIG. 3.

DETAILED DESCRIPTION OF THE INVENTION

[0014] 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.

[0015] 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.

[0016] 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.

[0017]FIG. 1 is a block diagram of an Advanced Intelligent Network (AIN) <b>10</b>. The AIN <b>10</b> 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) <b>12</b>. As illustrated in FIG. 1, the AIN <b>10</b> includes a Service Switching Point (SSP) <b>14</b>, a Signal Control Point (SCP) <b>16</b>, a database <b>18</b>, a Signal Transfer Point (STP) <b>20</b>, and a Service Node (SN) <b>22</b>.

[0018] 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 <b>10</b> illustrated in FIG. 1, the SSP <b>14</b> is a switch used to interconnect customer premises equipment via the PSTN <b>12</b>. The difference between the SSP <b>14</b> and the CO switch of a conventional telephone system is that the SSP <b>14</b> provides intelligent network functionality.

[0019] The SSP <b>14</b> has one or more subscriber lines <b>24</b> connected thereto. The subscriber lines <b>24</b> may be, for example, local loops comprising conventional twisted pair loop circuits connected between the SSP <b>14</b> and the customer premises, or the subscriber lines <b>24</b> may be trunk circuits, such as T-1 trunk circuits. The number of subscriber lines <b>24</b> connected to an SSP <b>14</b> may be on the order of ten thousand to one hundred thousand lines. The subscriber line <b>24</b> is connected to a terminating piece of customer premises equipment, represented in FIG. 1 by a landline telephone <b>26</b>. 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.

[0020] The SCP <b>16</b> is a server, associated with a database <b>18</b>, and provides instructions to the SSP <b>14</b> and the SN <b>22</b> as requested and required. The SCP <b>16</b> 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 <b>18</b> 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 <b>16</b>. The intelligent functionality of the SCP <b>16</b> may be realized by application programs, such as programmable Service Program Applications (SPA), which are executed by the SCP <b>16</b>. Although the AIN <b>10</b> illustrated in FIG. 1 only shows one database <b>18</b> associated with the SCP <b>16</b>, it is understood that more than one database <b>18</b> may be associated with the SCP <b>16</b>.

[0021] The STP <b>20</b> is a packet switch that routes signaling and control messages between the SSP <b>14</b> and the SCP <b>16</b>. As illustrated in FIG. 1, the STP <b>20</b> is in communication with the SSP <b>14</b> via communication link <b>28</b> and with the SCP <b>16</b> via communication link <b>30</b>. Communication links <b>28</b>, <b>30</b> may employ, for example, the Signaling System 7 (SS7) signaling protocol.

[0022] The SN <b>22</b> may provide an enhanced feature or service that requires an audio connection between the SN <b>22</b> and an answering machine connected to a subscriber line <b>24</b>, or between the SN <b>22</b> and a landline telephone <b>26</b> from which an emergency communication has been placed. The SN <b>22</b> 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 <b>16</b>, the intelligent functionality of the SN <b>22</b> may be realized by programmable applications executable by the SN <b>22</b>.

[0023] The SN <b>22</b> is in communication with the SSP <b>14</b> via communication link <b>34</b>, with the PSTN <b>12</b> via communication link <b>36</b>, and with the SCP <b>16</b> via communication link <b>38</b>. Communication links <b>34</b> and <b>36</b> 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 <b>38</b> 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).

[0024] The basic operation of the AIN <b>10</b> illustrated in FIG. 1 is described hereinbelow. When a call originating from the landline telephone <b>26</b> is received at the SSP <b>14</b> via the PSTN <b>12</b>, the SSP <b>14</b> generates a query to determine how the call should be processed. The query generated by the SSP <b>14</b> is transmitted via out-of-band signaling through the STP <b>20</b> to the SCP <b>16</b>.

[0025] The SCP <b>16</b> interprets the query based on information provided by the SSP <b>14</b> and information stored in the database <b>18</b> 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 <b>14</b> 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 <b>18</b> may include, for example, routing instructions associated with the dialed telephone number. Once the SCP <b>16</b> determines how the call is to be processed, it returns a message through the STP <b>20</b> to the SSP <b>14</b> instructing the SSP <b>14</b> 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 the SN <b>22</b>, the return message from the SCP <b>16</b> may include instructions for the SSP <b>14</b> to route the call to the SN <b>22</b>. In addition, the return message from the SCP <b>16</b> may simply be an indication that there is no entry in the database <b>18</b> 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.

[0026] Although the AIN <b>10</b> illustrated in FIG. 1 includes only one SSP <b>14</b>, one SCP <b>16</b>, one database <b>18</b>, one STP <b>20</b>, and one SN <b>22</b>, it is understood that the AIN <b>10</b> 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. For example, the AIN <b>10</b> may additionally include redundant SCP's and STP's to take over if the SCP <b>16</b> or the STP <b>20</b> should fail. Further, the AIN <b>10</b> may include regional STP's and regional SCP's in communication with, for example, the local STP <b>20</b>, for routing and servicing calls between different LECs.

[0027]FIG. 2 illustrates a system <b>40</b> employed by an emergency notification service, such as the Lucent family 911 notification service. The system <b>40</b> includes the AIN <b>10</b> as described hereinabove with regard to FIG. 1, and also includes a web server <b>42</b> and a Service Management System (SMS) <b>44</b>. The web server <b>42</b> is connected to the Internet <b>46</b>, and is in communication with the SMS <b>44</b> via communication link <b>48</b>. Communication link <b>48</b> may be, for example, a portion of the communication network that includes communication link <b>38</b>.

[0028] The SMS <b>44</b> is an operations support system used to facilitate the provisioning and administration of service data required by the SCP <b>16</b>. The SMS <b>44</b> 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 <b>16</b>. The SMS <b>44</b> includes programmable applications executable by the SMS <b>44</b> that provide access to the service management functions of the SMS <b>44</b> such as, for example, subscriber provisioning, and provide a direct interface to the SMS database. The SMS <b>44</b> is in communication with the SCP <b>16</b> via communication link <b>50</b>. Communication link <b>50</b> may be, for example, a portion of the communication network that includes communication link <b>38</b>.

[0029] When a customer subscribes to the emergency notification service, the service is provisioned at the SCP <b>16</b>. Information provisioned at the SCP <b>16</b> 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 <b>44</b>, which in turn passes the information to the SCP <b>16</b>, which then populates the database <b>18</b> with the information. Alternatively, the subscriber may provision the service remotely via the Internet <b>46</b> by providing the information to the web server <b>42</b>, which in turn passes the information to the SMS <b>44</b> for provisioning at the SCP <b>16</b> as described hereinbefore.

[0030] When a 911 call is placed from the customer's landline telephone <b>26</b>, the call is passed to the SSP <b>14</b> via the subscriber line <b>24</b> connecting the landline telephone <b>26</b> to the SSP <b>14</b>. The call activates a trigger defined at the SSP <b>14</b>, resulting in a query message being sent to the SCP <b>16</b> via the STP <b>20</b>. A trigger is an event associated with a particular subscriber line <b>24</b> that causes the SSP <b>14</b> to query the SCP <b>16</b> 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 <b>16</b> receives the query message and returns a response message to the SSP <b>14</b> via the STP <b>20</b>. The response message instructs the SSP <b>14</b> to process the 911 call as a switch-based feature. The SSP <b>14</b> 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.

[0031] In addition to returning the response message to the SSP <b>14</b>, the SCP <b>16</b> also uses the information provided by the query message to search the database <b>18</b> 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 <b>16</b> makes a TCP/IP connection request to the SN <b>22</b>. Once the TCP/IP connection is established between the SCP <b>16</b> and the SN <b>22</b>, the SCP <b>16</b> transmits information to the SN <b>22</b>. 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 <b>22</b>, the TCP/IP connection between the SCP <b>16</b> and the SN <b>22</b> is released.

[0032] The SN <b>22</b> will then begin placing outgoing calls to the designated telephone numbers in a sequential manner. As described hereinbefore, if the SN <b>22</b> reaches a live person at one of the designated telephone numbers, the SN <b>22</b> 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 <b>22</b> stops dialing the designated telephone numbers once the announcement has been played to a live person. If the SN <b>22</b> has not reached a live person after all of the designated numbers have been called, the SN <b>22</b> 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 <b>22</b> reaches an answering machine or a voice mail system at one of the designated telephone numbers, the SN <b>22</b> does not transmit the announcement.

[0033] If the SN <b>22</b> has not reached a live person within the first hour, the SN <b>22</b> continues to call the designated telephone numbers according to the specified priority. However, if the SN <b>22</b> reaches an answering machine or a voice mail system after the first hour, the SN <b>22</b> 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 <b>22</b> 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 <b>22</b> stops dialing the designated telephone numbers.

[0034] One skilled in the art will recognize several shortcomings associated with the above-described system <b>40</b>. For example, all of the subscriber information needed to operate the notification service must be provisioned via the SMS <b>44</b>, adding cost and complexity to the system <b>40</b>. Furthermore, storing this information at the SCP <b>16</b> requires increased storage capacity at the SCP <b>16</b>, resulting in increased acquisition and maintenance costs. In addition, the SN <b>22</b> employed in the system <b>40</b> is a very expensive network element, often having an initial purchase price of approximately one-half million dollars.

[0035]FIG. 3 illustrates an emergency notification system according to one embodiment of the present invention. The system <b>60</b> includes a switch <b>62</b>, a database server <b>64</b>, a message server <b>66</b>, and a web server <b>68</b>. The system <b>60</b> also includes an STP <b>20</b> as described hereinbefore. The system <b>60</b> 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.

[0036] The switch <b>62</b> may be in communication with terminal equipment such as, for example, a landline telephone <b>26</b> associated with the subscriber via a subscriber line such as, for example, subscriber line <b>24</b>. According to one embodiment, the switch <b>62</b> may be a service switching point such as, for example, the SSP <b>14</b> as described hereinabove. The switch <b>62</b> 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 <b>62</b> may also be in communication with the STP <b>20</b> via communication link <b>28</b> and with the message server <b>66</b> via communication link <b>34</b>.

[0037] The database server <b>64</b> is in communication with the switch <b>62</b> via the STP <b>20</b> and communication links <b>28</b> and <b>30</b>, and may be a service control point similar to the SCP <b>16</b> described hereinbefore. The database server <b>64</b> may store call-processing instructions, and may supply instructions to the switch <b>62</b> concerning how to process an incoming call. For example, according to one embodiment, the database server <b>64</b> may supply the switch with instructions for processing an emergency communication received at the switch <b>62</b>. Although the database server <b>64</b> may be similar to the SCP <b>16</b>, the database server <b>64</b> is markedly different from the SCP <b>16</b> in that the database server <b>62</b> 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 <b>64</b> may be provided with less storage capacity and require less database maintenance than the SCP <b>16</b>. Accordingly, the database server <b>64</b> may have a lower initial cost than the SCP <b>16</b> and have lower maintenance costs associated therewith.

[0038] The database server <b>64</b> may also supply information associated with an incoming call to the message server <b>66</b>. For example, the database server <b>64</b> may supply the message server <b>66</b> with information associated with an emergency communication. Such information may have been provided to the database server <b>64</b> by the switch <b>62</b> and may include, for example, the name of the person associated with a subscriber line <b>24</b> 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 <b>62</b>.

[0039] The message server <b>66</b> is in communication with the database server <b>64</b> via communication link <b>70</b>, and may transmit a message after an emergency communication is received at the switch <b>62</b>. The message server <b>66</b> may be any type of low-cost computer suitable for transmitting an oral message and/or a textual message. Whereas the SN <b>22</b> employed in system <b>40</b> has an initial cost of approximately one-half million dollars, the message server <b>66</b> only has an initial cost of approximately ten-thousand dollars. According to one embodiment, the message server <b>66</b> may be a telephony server that may transmit an oral message. According to another embodiment, the message server <b>66</b> may be an electronic mail server that may transmit a textual message. Communication link <b>70</b> 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 <b>66</b> may also be in communication with the PSTN <b>12</b> via communication link <b>36</b>.

[0040] The web server <b>68</b> is in communication with the message server <b>66</b> via communication link <b>72</b>, and may supply the message server <b>66</b> with information associated with a subscriber to an emergency notification service. Communication link <b>72</b> may be, for example, a portion of the communication network that includes communication link <b>70</b>. The web server <b>68</b> may be connected to the Internet <b>46</b>, and the subscriber information may be remotely provisioned and maintained at the web server <b>68</b> via the Internet <b>46</b>. 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 <b>68</b>. Provisioning subscriber information directly to the web server <b>68</b> reduces the cost and complexity of the emergency notification system.

[0041]FIGS. 4A and 4B illustrate an embodiment of a process flow of the emergency notification system <b>60</b> of FIG. 3. After the subscriber information has been provisioned at the web server <b>68</b> via the Internet <b>46</b>, the emergency notification service becomes operational for the subscriber. The process begins at block <b>80</b>, where an emergency communication is originated from customer premises equipment. The customer premises equipment may be, for example, a landline telephone <b>26</b> connected to a subscriber line <b>24</b>.

[0042] From block <b>80</b>, the process proceeds to block <b>82</b>, where the switch <b>62</b> receives the emergency communication via the PSTN <b>12</b>. From block <b>82</b>, the process proceeds to block <b>84</b>, where the received emergency communication activates a trigger defined at the switch <b>14</b>. 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. From block <b>84</b>, the process proceeds to block <b>86</b>, where the activated trigger causes the switch <b>62</b> 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 <b>62</b>, etc. From block <b>86</b>, the process proceeds to block <b>88</b>, where the switch <b>62</b> transmits the query message to the STP <b>20</b> via communication link <b>28</b>. From block <b>88</b>, the process proceeds to block <b>90</b>, where the STP <b>20</b> receives the query message and transmits the query message to the database server <b>64</b> via communication link <b>30</b>. From block <b>90</b>, the process proceeds to block <b>92</b>, where the database server <b>64</b> receives the query message originated at the switch <b>62</b>.

[0043] From block <b>92</b>, the process proceeds to block <b>94</b>, where the database server <b>64</b> generates a response message to the query message and transmits the response message to the STP <b>20</b> via communication link <b>30</b>. The response message includes an instruction detailing how the switch <b>62</b> should process the emergency communication. For example, the response message may include an instruction for the switch <b>62</b> to process the emergency communication as a switch-based feature. From block <b>94</b>, the process proceeds to block <b>96</b>, where the STP <b>20</b> receives the response message from the database server <b>64</b> and transmits the response message to the switch <b>62</b> via communication link <b>28</b>. From block <b>96</b>, the process proceeds to block <b>98</b>, where the switch <b>62</b> receives and interprets the response message originated at the database server <b>64</b>. From block <b>98</b>, the process proceeds to block <b>100</b>, where the switch <b>62</b> routes the emergency communication to a Public Safety Answering Point (PSAP), where a PSAP operator processes the call in accordance with well-known procedures.

[0044] While the process is proceeding from block <b>92</b> to block <b>94</b>, the process also proceeds from block <b>92</b> to block <b>102</b>, where the database server <b>64</b> requests a TCP/IP connection be established between the database server <b>64</b> and the message server <b>66</b>. Once the TCP/IP connection has been established, the process proceeds from block <b>102</b> to block <b>104</b>, where the database server <b>64</b> transmits the identification information included in the query message to the message server <b>66</b> via communication link <b>70</b>. From block <b>104</b>, the process proceeds to block <b>106</b>, where the message server <b>66</b> receives the identification information, and requests that a TCP/IP connection be established between the message server <b>66</b> and the web server <b>68</b>. Once the TCP/IP connection has been established, the process proceeds from block <b>106</b> to block <b>108</b>, where the message server <b>66</b> transmits a query message to the web server <b>68</b> via communication link <b>72</b> 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 <b>108</b>, the process proceeds to block <b>110</b>, where the web server <b>68</b> receives the query message and at step <b>111</b> 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 <b>113</b>.

[0045] If the person has been provisioned as a subscriber to the emergency notification service, the process proceeds from block <b>111</b> to block <b>112</b>, where the web server <b>68</b> transmits the provisioned telephone numbers and electronic mail addresses to the message server <b>66</b> via communication link <b>72</b>. From block <b>112</b>, the process proceeds to block <b>114</b>, where the message server <b>66</b> 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 <b>12</b>, and/or transmitting textual messages to the provisioned electronic mail addresses over the Internet <b>46</b> via the web server <b>68</b>. 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.

[0046] For outgoing calls that are answered by a live person, an answering machine, or a voice mail system, the message server <b>66</b> 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 <b>66</b> has played the announcement, the message server <b>66</b> will stop calling that particular telephone number. If an outgoing call has not been answered at a provisioned telephone number, the message server <b>66</b> may continue to call the provisioned telephone number until the call has been answered and the announcement has been played.

[0047] Electronic mail messages transmitted by the message server <b>66</b> 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 <b>66</b> may transmit the electronic mail messages once to each provisioned electronic mail address. However, if the message server <b>66</b> receives an indication that the electronic mail message was not delivered successfully to a particular provisioned electronic mail address, the message server <b>66</b> may attempt to transmit the electronic mail message to the particular provisioned electronic mail address more than once.

[0048] 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.