Apparatus and method for providing weather and other alerts
Claim Score by NHIP
Abstract
An apparatus, including an alert device having a receiver, and method are provided for receiving alert information broadcast via particular telecommunication transmitters operating within a cellular, PCS, or other wireless telecommunications network, thereby allowing delivery of a message. The alert device includes a receiver for receiving digital messages in the form of broadcast messages on a digital control channel, a microcomputer having a monitoring circuit that monitors received digital messages for the presence of an alert code associated with alert messages regarding an alert condition, and a plurality of peripheral devices which produce various tones and flashing lights in response to the alert device's reception of an appropriate alert message. The alert device can be provisioned over the air to respond to particular preferred system providers and controlled user groups. The alert device can also control and external device to provide a warning to the user.

Term
Term ended
Projected expiry passed 30 May 2023, 3.3 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
16 claims: 5 independent, 11 dependent
- 1An apparatus for providing location-specific alert information associated with an alert condition relevant to a geographical area, the location-specific alert information being broadcast within the geographical area by at least one transmitter of a wireless bi-directional communication network having a plurality of communication channels and a plurality of transmitters which are each positioned to provide communication services to specific geographical areas serviced by the communication network, said apparatus comprising:a receiver adapted to receive transmissions on a communication channel of the plurality of communication channels of the wireless bi-directional communication network;a peripheral device operable to indicate an alert condition;and, a controller communicatively connected to said receiver and said peripheral device, said controller being operable to continuously monitor a communication channel of the wireless bi-directional communication network for the receipt of a transmission of location-specific alert information from a transmitter servicing a specific geographical area and to operate said peripheral device in response to the reception of a transmission of location-specific alert information;wherein said controller is further operable to monitor said communication channel of said wireless bi-directional network for the receipt of a preferred system provider message and to update a preferred system provider list, based at least in part, on the reception of the preferred system provider message.
- 2An apparatus for providing to a user alert information associated with an alert condition, the alert information being broadcast to by at least one transmitter of a wireless bi-directional communication network having a plurality of communication channels and a plurality of transmitters which are each positioned to provide communication services to persons in a particular respective geographical area serviced by the communication network, said apparatus comprising:a receiver adapted to receive transmissions on a communication channel of the plurality of communication channels of the wireless bi-directional communication network;a peripheral device operable to inform the user of the existence of a relevant alert condition;and, a controller communicatively connected to said receiver and said peripheral device, said controller being operable to continuously monitor a communication channel of the wireless bi-directional communication network for the receipt of a transmission of alert information from a transmitter and to operate said peripheral device in response to the reception of a transmission of alert information;wherein said controller is further operable to maintain a closed user group list used to filter out particular messages.
- 4An apparatus for providing location-specific alert information associated with an alert condition relevant to a geographical area, the location-specific alert information being broadcast within the geographical area by at least one transmitter of a wireless bi-directional communication network having a plurality of communication channels and a plurality of transmitters which are each positioned to provide communication services to specific geographical areas serviced by the communication network, said apparatus comprising:a receiver adapted to receive transmissions on a communication channel of the plurality of communication channels of the wireless bi-directional communication network;a peripheral device operable to indicate an alert condition;and, a controller communicatively connected to said receiver and said peripheral device, said controller being operable to continuously monitor a communication channel of the wireless bi-directional communication network for the receipt of a transmission of location-specific alert information from a transmitter servicing a specific geographical area and to operate said peripheral device in response to the reception of a transmission of location-specific alert information;wherein said controller is further operable to control an external device in response to the reception of a transmission of location-specific alert information.
- 7An apparatus for providing to a user alert information associated with an alert condition relevant to persons in the selected geographical area of the user, the alert information being broadcast to the selected geographical area by at least one transmitter of a wireless bi-directional communication network having a plurality of communication channels and a plurality of transmitters which are each positioned to provide communication services to persons in a particular respective geographical area serviced by the communication network, said apparatus comprising:a receiver adapted to receive transmissions on a communication channel of the plurality of communication channels of the wireless bi-directional communication network;a peripheral device operable to inform the user of the existence of a relevant alert condition;and, a controller communicatively connected to said receiver and said peripheral device, said controller being operable to continuously monitor a communication channel of the wireless bi-directional communication network for the receipt of a transmission of alert information from a transmitter servicing the selected geographical area of the user and to operate said peripheral device in response to the reception of a transmission of alert information;wherein said controller is further operable to detect the actuation of a standby button and perform a function based on the actuation of said standby button.
- 10Broadest claimClaim Score 57, average(NHIP)A method of operating a device having a receiver and a peripheral device to receive alert information pertaining to an alert condition which is broadcast by a wireless bi-directional communication network having a plurality of communication channels and to inform a user of the existence of the alert condition, the method comprising the steps of:selecting a communication channel from the plurality of communication channels of the wireless bi-directional communication network;monitoring the selected communication channel with the receiver for a transmission of a control message;reconfiguring the device in accordance with the control message, the reconfiguration influencing subsequent operation of the device;monitoring the selected communication channel with the receiver for a transmission including alert information pertaining to the alert condition;and, operating the peripheral device to notify the user of the alert condition upon detection of a transmission including alert information.
Independent claims5
116 paragraphs in 6 sections, as filed
CROSS REFERENCE TO RELATED APPLICATION
[0001] This patent application is a continuation-in-part of, U.S. patent application Ser. No. 10/016,307 filed on Dec. 10, 2001, which is a continuation-in-part of U.S. patent application Ser. No. 09/330,667 filed on Jun. 11, 1999 and issued as U.S. Pat. No. 6,329,904. This application also claims the benefit of the filing date of U.S. Pat. No. 6,329,904.
FIELD OF THE INVENTION
[0002] This invention relates generally to the field of alert systems and, in its preferred embodiments, to alert systems utilizing cellular, personal communication system, or wireless telecommunication technology to deliver an alert to an alert device.
BACKGROUND OF THE INVENTION
[0003] In recent decades, the science of meteorology has advanced rapidly, allowing increasingly accurate detection and prediction of severe and hazardous weather. Specifically, Doppler radar systems and high-resolution satellites have been developed which allow early detection of tornadoes and severe thunderstorms and accurate tracking of their paths. The National Weather Service (NWS) and National Oceanographic and Atmospheric Administration (NOAA) now routinely issue warnings in advance of most severe or tornadic storms, alerting individuals and saving lives. However, in order for these warnings, or “alerts” to be effective, they must be communicated to and received by their intended recipients.
[0004] Some local governments and municipalities utilize civil defense siren systems to provide warnings to persons within the localized range of the siren systems in case of severe weather, natural disaster, war or other emergency conditions. However, weather-related warnings are more commonly provided through the NOAA Weather Radio system, a nationwide network of radio stations operating twenty-four (24) hours per day to broadcast continuous weather information directly from the local offices of the National Weather Service. The NOAA Weather Radio system also broadcasts alerts for the Emergency Alert System (EAS), maintained by the Federal Communication Commission, in order to provide emergency warnings for all types of hazards, including, but not limited to, earthquakes, volcano erruptions, severe weather and nuclear war. The NOAA Weather Radio system has more than 450 transmitters, covering broad areas in each of the 50 states, adjacent coastal waters, Puerto Rico, the U.S. Virgin Islands, and the U.S. Pacific Territories. Unfortunately, reception of the Emergency Alert System warnings via the NOAA Weather Radio system generally requires a special radio receiver or scanner capable of picking up its emergency warning signals.
[0005] Tone-activated alert receivers are commonly used to monitor NOAA Weather Radio broadcasts, to provide warning of severe weather and to provide emergency and civil defense alerts. A tone-activated alert receiver constantly monitors the local NOAA Weather Radio broadcasts for a specific 1050 Hz emergency alert tone. In response to receiving an emergency alert tone, a tone-activated alert receiver produces an audible and/or visual alarm, and activates a radio tuned to the NOAA Weather Radio broadcast. Since each NOAA Weather Radio station transmits its signals to a relatively large geographical area, older tone-activated alert receivers suffer from the disadvantage of falsely responding to alerts when the condition to which the emergency alert pertains is only relevant to other geographical areas in the broadcast area of the particular NOAA Weather Radio station transmitting the alert tone.
[0006] Newer NOAA Weather Radio receivers, known as “SAME receivers”, incorporate a feature known as Specific Area Message Encoding (SAME) to decrease the frequency of false alerts. A SAME receiver recognizes a specific digital location code, in an emergency broadcast signal, which designates a specific locality for which alerts are relevant. Once programmed by a user to respond only to a specific digital location code for the area of the user, a SAME receiver switches into alarm mode only upon receipt of an emergency broadcast signal, which includes a SAME digital location code matching the preprogrammed digital code. Accordingly, SAME receivers are generally deployed in a particular, fixed location such as an individual's home or office. While these SAME receivers are useful in their fixed locations, they are not particularly useful if moved from the location for which they have been programmed. Additionally, like many individuals who cannot program a videocassette recorder (VCR), some individuals may find it difficult or inconvenient to program the SAME receiver.
[0007] As an alternative to SAME receivers, some persons are proposing that cellular or Personal Communication System (PCS) wireless telephone networks be employed to deliver emergency alerts to individuals having cellular or PCS wireless telephones because cellular and PCS telephone networks typically employ short-range, broadcast transceivers (or transmitters) which have coverage areas, or cells, of a reasonably small size, thereby enabling the delivery of emergency alerts to persons in selected areas served by particular broadcast transmitters. As proposed, delivery of emergency alert messages to selected local areas would be achieved by activating only those cellular or PCS broadcast transceivers providing coverage for the specific geographical area to which the emergency alert is relevant, instead of requiring the transmission, preprogramming, and recognition of a specific digital location code corresponding to the geographical area for which the emergency alert is relevant. However, until recently, wireless telephone networks have not had the capability of transmitting alphanumeric messages that would be required to effectively distribute emergency alert messages. In contrast, conventional paging systems have the capability of supporting alphanumeric messaging, but have coverage areas far to large to provide the level of geographical specificity required to deliver location specific, emergency alert messages.
[0008] New cellular and PCS telephone networks are currently being deployed, or have been deployed, throughout North America and Europe which are capable of transmitting alphanumeric messages and which have coverage areas providing sufficient geographical specificity to make them ideal vehicles for the delivery of location-specific, emergency alert messages. Using the newer cellular and PCS networks, a network operator can send messages to a cellular or PCS telephone present in any single cell or any group of cells serviced by the transceivers of the network. Accordingly, some persons have recently proposed that these cellular and PCS networks be used to transmit location-specific, emergency alert messages to the cellular or PCS telephone handsets of individual users by dialing the telephone number associated with each handset and, upon answer by the cellular or PCS handset, delivering the emergency alert message to the handset.
[0009] While cellular or PCS telecommunications systems may be an effective vehicle for conveying location-specific, emergency alert messages, such systems enable delivery of emergency alert messages to only those individuals who can figure out how get such messages via their wireless telephones. Currently, to get such messages, individuals must find their way through a myriad of icons (which many individuals cannot do) and then review all of their messages in order to identify the emergency alert messages from other messages. Further, the delivery of emergency alert messages via cellular or PCS telecommunications systems requires individuals to have their handsets nearby and turned-on (and not depleted of battery power). Unfortunately, individuals often turn-off their handsets, forget to recharge them, or leave their handsets, for instance, in the car while they are at home or work. As a result, a system that relies upon cellular or PCS handset receivers to receive emergency alert messages may fail to notify a large number of individuals of the existence of an emergency condition.
[0010] Other similar difficulties are inherent in the delivery of information or messages that relate to military or other operations (i.e., a different type of “alert”). For instance, if a branch of the military needs to inform its reservists to report for duty on Sunday instead of Saturday as the reservists were originally notified, it typically contacts each reservist individually by telephone to provide the reservist with such information, thereby requiring a substantial use of labor to perform such a task.
[0011] Therefore, there is a need in the industry for an apparatus and method whereby individuals may reliably receive cellular or PCS transmissions of location-specific alert information without requiring the use of a cellular or PCS telephone handset. Furthermore, there is a need for an apparatus and method whereby individuals may reliably receive cellular or PCS transmissions of location-specific alert information without requiring individuals to perform complex retrieval steps or inconvenient receiver programming steps.
SUMMARY OF THE INVENTION
[0012] Briefly described, the present invention comprises an alert apparatus and method for receiving a location-specific alert (i.e., an alert directed and relevant to a particular geographical area) and for informing a user, who may be visually or hearing impaired, of the existence and severity of the alert. More particularly, the present invention includes an alert apparatus and method which allow a user to receive data corresponding to an alert which has been broadcast via particular transmitters operating within a cellular, PCS, or wireless telephone communications network, thereby allowing receipt of a location-specific alert (and a textual message associated with the alert) without requiring the user to input, to the alert apparatus, data representative of or identifying the location of the apparatus. Further, the present invention includes an alert apparatus and method which produces high-decibel level audible sounds and high-intensity flashing strobe light corresponding to alerts of the most severe level and which produces low-decibel level audible sounds and low-intensity flashing light from a light-emitting diode corresponding to alerts of a less severe level.
[0013] In accordance with the preferred embodiment, the apparatus of the present invention comprises an alert device having a microcomputer that directs operation of the alert device according to the instructions of a computer software program stored therein. The alert device also includes a receiver that receives digital PCS transmissions broadcast over a PCS or cellular telecommunication network. The microcomputer has a central processing unit and a monitoring circuit communicatively connected to the central processing unit and receiver. The monitoring circuit is capable of setting the receiver to receive transmissions, if any, on radio channels identified by the central processing unit, of determining the signal strength associated with transmissions received on such radio channels, of identifying the presence of a digital control channel on a radio channel, and of communicating signal strength information, digital control channel information, and broadcast short messages, received by the receiver, to the central processing unit.
[0014] According to the preferred embodiment of the present invention, the alert device further comprises a plurality of peripheral devices and the microcomputer further comprises a peripheral device controller which connects to the plurality of peripheral devices. The plurality of peripheral devices includes a liquid crystal display, a high-level audio speaker, a low-level audio speaker, a high-intensity strobe light, and a low-intensity light-emitting diode. The microcomputer, via the peripheral device controller, controls the operation of the plurality of peripheral devices according to the severity of a condition identified by an alert. For instance, the microcomputer causes the production of audible sound from the high-level audio speaker at a high-decibel level and flashing of the high-intensity strobe light to warn a user of the existence of a “Level One” alert (i.e., the most severe or important alert condition). Similarly, the microcomputer causes the production of audible sound from the low-level audio speaker at a low-decibel level and flashing of the low-intensity light-emitting diode to warn a user of the existence of a “Level Two” alert (i.e., a less severe or less important alert condition). The microprocessor, via the peripheral device controller, also causes the display, on the liquid crystal display, of textual information received as part of an alert message.
[0015] The alert device, in accordance with the preferred embodiment, is operable to continuously monitor broadcasts from a cellular, PCS, or wireless telecommunications network. Accordingly, the alert device connects to an electrical outlet to receive electrical power for normal operation, but includes a battery backup and charging circuit to ensure operation of the alert device even in the event of a power failure. Furthermore, in the preferred embodiment, the alert device operates continuously when supplied with electrical power, has no on/off switch, and thus cannot easily be deactivated by a user unlike a cellular or PCS telephone handset. The alert device does, however, include a reset pushbutton that enables a user to temporarily deactivate, or stop, the audible and visual alarms once notified of an alert condition. In the preferred embodiment, the alert device is mountable to an electrical wall socket in a manner substantially similar to that of a conventional smoke detector. In an alternate embodiment, the alert device has an enclosure that enables the device to reside atop a table or other surface in a manner substantially similar to that of a weather radio. In an alternate preferred embodiment, the alert device includes a plurality of peripheral devices that are locatable at sites remote from the alert device.
[0016] In accordance with a method of the preferred embodiment of the present invention, the alert device operates according to the instructions of a computer software program residing in the microcomputer and performs a self-test when powered-up to determine whether the alert device is functioning properly. The alert device, through cooperation between the microcomputer, monitoring circuit, and receiver, then scans a factory-set, pre-identified set of radio channels comprising a range of channels used by compatible cellular or PCS telecommunication networks in order to identify the channel associated with the cellular or PCS transmitter which transmits on a digital control channel and which has the strongest signal strength at the location of the alert device. The alert device then locks onto and passively monitors the selected channel for digital alerts in the form of broadcast messages. Because the alert device passively monitors PCS network broadcasts, use of the alert device should not result in the user incurring periodic service charges from the network provider.
[0017] According to the method of the present invention, the alert device, upon detecting and receiving a broadcast message, identifies whether the broadcast message comprises an alert message. If so, the alert device then analyzes the alert message and determines the severity level of the alert identified by the alert message. If the alert is a “Level One” alert, the alert device operates, as described above, the high-level audio speaker to produce a highly obtrusive, high-decibel level sound substantially similar to that of a conventional smoke detector (i.e., a sound that would cause even the hardest of sleepers to awaken) and the high-intensity strobe light to produce flashing, high-intensity, bright light. If the alert is a “Level Two” alert, the alert device operates, as described above, the low-level audio speaker to produce a less-obtrusive, low-decibel level, “chirping” sound and the low-intensity light-emitting diode to produce less-intense, less-bright, flashing light. Regardless of the severity level of the alert, the alert device extracts textual message information, if any, from the alert message and displays the textual message information on the liquid crystal display to provide a user with a more detailed explanation as to the nature of the alert. Once the user is informed as to the existence and nature of the alert, the production of audible sounds and the generation of flashing light is terminable by the user through depression of the reset pushbutton protruding partially from the alert device.
[0018] In accordance with an alternate preferred embodiment of the present invention, the alert device is operable with an alert messaging system of a service provider which provides different levels of service (i.e., service levels or modes) to a user of the alert device in exchange for a subscription fee paid to the service provider by the user. The plurality of service levels or modes enable different classifications of alert messages to be related to and associated with the subscription status of a user (i.e., the service level selected by, subscribed to, and paid for by a user). Based upon the service level selected by the user and stored in a service level data element of the user's alert device, the user's alert device will provide that level of service to the user. For example and not limitation, a user may select a service level from any of the following levels: fully enabled; partially enabled; or, fully disabled. The user pays a subscription fee to the service provider in an amount determined by the selected service level, and the service provider causes a service level data element stored at the user's alert device to be set to a value indicating the service level or mode selected by the user. Once set, the user's alert device operates at the selected service level. In the fully enabled mode, the alert device reacts to all alert messages and provides the user with any received information pertaining to the corresponding alert. In the partially enabled mode, the alert device only reacts to the most severe alerts (i.e., “Level One” alerts) to provide subscribers with a minimal level of service and warnings. In the fully disabled mode, the alert device does not react to any alerts. Such operability allows a service provider of alert messages to establish and enforce compliance with a subscription system.
[0019] According to another alternate preferred embodiment of the present invention, the alert device is operable with an alert messaging system of a service provider which provides a service level that enables the user's alert device to receive and react to an advertisement that is present in the body of an alert message. In operation, the service provider causes a service level data element stored at the user's alert device to be set to a value indicating that the user's alert device is to display received advertisements on the device's display. Then, whenever the alert device receives a message having a service level with that value, the alert device extracts an advertisement from the body of the message and displays it on the alert device's display.
[0020] Accordingly, it is an object of the present invention to provide an apparatus and method for receiving location-specific alert information without requiring a user to input data representative of the user's location.
[0021] Another object of the present invention is to provide an apparatus and method for receiving location-specific alert information that is not limited to a fixed location.
[0022] Still another object of the present invention is to provide an apparatus for receiving location-specific alert information that can be moved from an old location to a new location without requiring reprogramming or the input of data representative of the new location.
[0023] Still another object of the present invention is to provide an apparatus for receiving location-specific alert information that self-identifies the strongest source of such alert information.
[0024] Still another object of the present invention is to provide an apparatus for receiving location-specific alert information that self-identifies the frequency on which the alert information is transmitted or broadcast.
[0025] Still another object of the present invention is to provide an apparatus and method for receiving location-specific alert information that identifies the different levels of severity associated with alerts.
[0026] Still another object of the present invention is to provide an apparatus and method for receiving location-specific alert information that produces different sensory outputs corresponding to the different levels of severity or importance of alerts.
[0027] Still another object of the present invention is to provide an apparatus and method for receiving location-specific alert information which operates continuously, unless moved by a user, at a particular location.
[0028] Still another object of the present invention is to provide an apparatus and method for receiving location-specific alert information which is continuously operable from an external electrical power source and which has an internal battery backup for use during power failures.
[0029] Still another object of the present invention is to provide an apparatus and method for receiving location-specific alert information which displays a textual message related to the alert for which the alert information pertains.
[0030] Other objects, features and advantages of the present invention will become apparent upon reading and understanding the present specification when taken in conjunction with the appended drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0031]FIG. 1 is a pictorial representation of an alert device in accordance with a preferred embodiment of the present invention.
[0032]FIG. 2 is a block diagram representation of the alert device of FIG. 1 displaying the major components thereof
[0033]FIG. 3 is a schematic representation of the program domain of the non-volatile program memory of the alert device of FIG. 1.
[0034]FIG. 4 is a schematic representation of the data domain of the non-volatile data memory of the alert device of FIG. 1.
[0035]FIG. 5 is a schematic representation of the data domain of the volatile data memory of the alert device of FIG. 1.
[0036]FIG. 6 is a pictorial representation of an exemplary PCS alert broadcast system in accordance with a preferred embodiment of the present invention.
[0037]FIG. 7 is a schematic representation of the data of a digital alert message in accordance with a preferred embodiment of the present invention.
[0038]FIGS. 8<i>a</i>-<i>d </i>are flowchart representations of a main portion of a computer software program of the alert device in accordance with a method of the preferred embodiment of the present invention.
[0039]FIGS. 9<i>a</i>-<i>b </i>are flowchart representations of a self-test routine of the computer software program of the alert device in accordance with a method of the preferred embodiment of the present invention.
[0040]FIG. 10 is a flowchart representation of a high-level alarm routine of the computer software program of the alert device in accordance with a method of the preferred embodiment of the present invention.
[0041]FIG. 11 is a flowchart representation of a low-level alarm routine of the computer software program of the alert device in accordance with a method of the preferred embodiment of the present invention.
[0042]FIG. 12 is a flowchart representation of a timer interrupt handling routine of the computer software program of the alert device in accordance with a method of the preferred embodiment of the present invention.
[0043]FIG. 13 is a flowchart representation of a reset interrupt handling routine of the computer software program of the alert device in accordance with a method of the preferred embodiment of the present invention.
[0044]FIG. 14 is a block diagram representation of a first portion of an alert device of a first alternate preferred embodiment displaying the major components thereof.
[0045]FIG. 15 is a block diagram representation of the first portion of the alert device of FIG. 14 and a plurality of remotely-located peripheral devices of a second portion of the alert device.
[0046]FIG. 16 is a flowchart representation of a startup service level check routine of a computer software program of an alert device in accordance with the method of a second alternate preferred embodiment of the present invention.
[0047]FIG. 17 is a flowchart representation of a service level adjustment routine of the computer software program of an alert device in accordance with the method of the second alternate preferred embodiment of the present invention.
[0048]FIG. 18 is a flowchart representation of a service level authentication routine of the computer software program of an alert device in accordance with the method of the second alternate preferred embodiment of the present invention.
DETAILED DESCRIPTION
[0049] Referring now to the drawings, in which like numerals represent like components throughout the several views, an alert device <b>20</b>, in accordance with an apparatus of the preferred embodiment of the present invention, is shown in pictorial form in FIG. 1 and in block diagram form in FIG. 2. The alert device <b>20</b> comprises an enclosure <b>22</b> and a microcomputer <b>24</b>, receiver <b>26</b>, diversity receive antenna <b>28</b>, power supply <b>30</b>, and backup battery <b>32</b> residing therein. Preferably, the enclosure <b>22</b> is manufactured from a durable plastic material and the alert device <b>20</b> is directly pluggable into an electrical wall outlet through use of an electrical plug <b>34</b> located on the back of the enclosure <b>22</b>, thereby avoiding the need for mounting hardware and the difficulties of mounting the enclosure <b>22</b> to a wall. According to the apparatus of the preferred embodiment, the receiver <b>26</b> is adapted to receive digital signals within the ranges of channels utilized for cellular, PCS, or other wireless communications in the area in which the alert device <b>20</b> is deployed. For example and not limitation, the receiver <b>26</b> is adapted to receive digital signals on channels having receive-side frequencies in the (i) 969 MHz to 994 MHz range, (ii) 1840 MHz to 1865 MHz range, (iii) 1930.72 MHz to 1945 MHz range, (iv) 1950.72 MHz to 1965 MHz range, or (v) 1975.72 MHz to 1990 MHz range. It is understood, however, that the scope of the present invention includes similar receivers which are adapted to receive cellular, PCS, or wireless digital signals in any frequency range.
[0050] The alert device <b>20</b> further comprises a plurality of peripheral devices <b>36</b> which electrically connect to the microcomputer <b>24</b>, and an external antenna <b>38</b> having a first portion which resides within the enclosure <b>22</b> and a second portion which extends outside of the enclosure <b>22</b>. An external antenna <b>38</b>, acceptable in accordance with the preferred embodiment, is a rubber-covered antenna commonly known as a “rubber duck antenna” which is often found in cellular, PCS, or wireless telephones.
[0051] The plurality of peripheral devices <b>36</b> includes a liquid crystal display <b>36</b><i>a </i>residing within the enclosure <b>22</b> adjacent to an opening <b>40</b> in the enclosure <b>22</b> that enables the liquid crystal display <b>36</b><i>a </i>to be visible from outside the enclosure <b>22</b>. Preferably, the liquid crystal display <b>36</b><i>a </i>is backlit to enhance the readability of the display <b>36</b><i>a</i>. The liquid crystal display <b>36</b><i>a </i>has signal strength indicator <b>37</b> located near the right side of the display <b>36</b><i>a</i>. The signal strength indicator <b>37</b> comprises a plurality of liquid crystal bars <b>39</b> arranged in a, generally, vertical direction which the microcomputer <b>24</b> energizes to darken the bars <b>39</b> and, thereby indicate the signal strength of the strongest channel received by the alert device <b>20</b> at the device's then-existing location. A stronger signal strength is indicated by energization and darkening of a larger number of bars <b>39</b>, while a weaker signal is indicated by energization and darkening of a smaller number of bars <b>39</b>.
[0052] The plurality of peripheral devices <b>36</b> also includes a high-level audio speaker <b>36</b><i>b </i>and a low-level audio speaker <b>36</b><i>c </i>which reside within the enclosure <b>22</b> at positions adjacent respective grill-like openings <b>42</b>, <b>44</b> in the enclosure <b>22</b> that allow audible sounds generated by the speakers <b>36</b><i>b</i>, <b>36</b><i>c </i>to exit the enclosure <b>22</b> to the environment surrounding the emergency alert device <b>20</b>. In accordance with the preferred embodiment, the high-level audio speaker <b>36</b><i>b </i>includes a speaker, substantially similar to those found in smoke detectors, which produces a high-decibel level continuous or pulsating tone that is sufficiently loud to awaken a sleeping person. The low-level audio speaker <b>36</b><i>c</i>, according to the preferred embodiment, includes a speaker which, when appropriately activated, emits a periodic “chirp-type” sound substantially similar to the sound emitted by the speakers employed in portable pagers.
[0053] The plurality of peripheral devices <b>36</b> additionally includes a high-intensity strobe light <b>36</b><i>d </i>and a low-intensity light emitting diode (LED) <b>36</b><i>e </i>which reside within the enclosure <b>22</b> and are visible, through a window-covered opening <b>46</b>, from outside the enclosure <b>22</b>. The high-intensity strobe light <b>36</b><i>d</i>, in accordance with the apparatus of the preferred embodiment, includes a conventional xenon flash tube which is pulsable in a periodic manner to produce a bright flash of light every one to two seconds when in use, thereby enabling the alert device <b>20</b> to draw the attention of a hearing impaired person. The low-intensity light emitting diode <b>36</b><i>e</i>, according to the apparatus of the preferred embodiment, includes a conventional, red light emitting diode that is pulsable in a manner similar to that employed with the high-intensity strobe light <b>36</b><i>d</i>. The plurality of peripheral devices <b>36</b> further includes a reset pushbutton <b>36</b><i>f </i>that extends through an opening in the enclosure <b>22</b> so as to be depressable by a user of the alert device <b>20</b>.
[0054] The microcomputer <b>24</b> comprises, preferably, a custom-manufactured device substantially similar to those microcomputers residing in cellular, PCS, or wireless telephones and includes, integrated therein, a central processing unit (CPU) <b>60</b>, a monitoring circuit <b>62</b>, a non-volatile program memory <b>64</b>, a non-volatile data memory <b>66</b>, a volatile data memory <b>68</b>, a peripheral device controller <b>70</b>, and a count-down timer <b>72</b>. The non-volatile program memory <b>64</b>, illustrated in FIG. 3, stores a computer software program <b>200</b> having a main portion <b>210</b>, a self-test routine <b>400</b>, a high-level alarm routine <b>500</b>, a low-level alarm routine <b>600</b>, a timer interrupt handling routine <b>700</b>, and a reset interrupt handling routine <b>800</b> which the CPU <b>60</b> executes, as described below, to cause the alert device <b>20</b> to operate in accordance with a method of the preferred embodiment of the present invention.
[0055] The non-volatile data memory <b>66</b>, illustrated in FIG. 4, stores values for the starting channel identifier <b>76</b> and the ending channel identifier <b>78</b> of the range of channels to be monitored, or scanned, by the receiver <b>26</b> for the presence of a digital control channel as described below. The non-volatile data memory <b>66</b> also stores the value of the test channel step-size <b>80</b> and a plurality of receive frequencies <b>82</b> corresponding in a one-to-one relationship with channels to be possibly monitored by the receiver <b>26</b> (i.e., so that receive frequency <b>82</b><i>a </i>corresponds to the first channel possible for monitoring, receive frequency <b>82</b><i>b </i>corresponds to the second channel possible for monitoring, and receive frequency <b>82</b><i>n </i>corresponds to the n<sup>th </sup>channel possible for monitoring. In accordance with the preferred embodiment, the non-volatile data memory <b>66</b> stores a plurality of receive frequencies <b>82</b> corresponding to the channels associated with the receive-side frequencies in (i) the 969 MHz to 994 MHz range, (ii) the 1840 MHz to 1865 MHz range, (iii) the 1930.72 MHz to 1945 MHz range, (iv) the 1950.72 MHz to 1965 MHz range, or (v) the 1975.72 MHz to 1990 MHz range. The non-volatile data memory <b>66</b> also stores a self-test time period <b>81</b> which defines the amount of time that the self-test routine <b>400</b> delays at various steps during execution.
[0056] The volatile data memory <b>68</b>, illustrated in FIG. 4, stores a plurality of channel identifers <b>84</b> and a plurality of signal strength values <b>86</b> organized in a list, or table, <b>88</b> of plurality of channel identifier/signal strength pairs <b>90</b>. Each channel identifier/signal strength pair <b>90</b> comprises a channel identifier <b>84</b> and a respective signal strength value <b>86</b> which represent a number identifying a digital control channel found and the associated signal strength value <b>86</b> (also referred to herein as “signal strength”) identified by the receiver <b>26</b> and monitoring circuit <b>62</b> as described below. The volatile data memory <b>66</b> also stores a test channel identifier <b>91</b> and a pointer <b>93</b> to the digital control channel selected as described below (also referred to herein as a “alert channel pointer <b>93</b>”).
[0057] According to the preferred embodiment of the present invention, the peripheral device controller <b>70</b> is an intelligent controller which produces, at appropriate times described below, signals necessary to cause operation of each peripheral device <b>36</b> of the plurality of peripheral devices <b>36</b> as described herein. For example and not limitation, the peripheral device controller <b>70</b> produces, when necessary, signals necessary to cause the high-level audio speaker <b>36</b><i>b </i>to generate an obtrusive tone which should wake the soundest of sleepers, the low-level audio speaker <b>36</b><i>c </i>to generate “chirping” sounds, and the high-intensity strobe light <b>36</b><i>d </i>and the low-intensity light-emitting diode <b>36</b><i>e </i>to flash. The peripheral device controller <b>70</b> also ceases, at appropriate times described below, the production of signals which cause operation, for instance, of the high-level audio speaker <b>36</b><i>b</i>, the low-level speaker <b>36</b><i>c</i>, the high-intensity strobe light <b>36</b><i>d</i>, and the low-intensity light-emitting diode <b>36</b><i>e. </i>
[0058] The count-down timer <b>72</b>, according to the preferred embodiment, comprises a timer which is programmable by the CPU <b>60</b> to start counting down time from an initial time provided to the count-down timer <b>72</b> by the CPU <b>60</b>. Upon reaching zero, the count-down timer <b>72</b> produces an interrupt signal which is communicated to the CPU <b>60</b>. The reset pushbutton <b>36</b><i>f </i>also produces an interrupt signal which is communicated to the CPU <b>60</b>.
[0059] The microcomputer <b>24</b>, as displayed in FIG. 2, further includes a bus <b>74</b> which interconnects the CPU <b>60</b> and the monitoring circuit <b>62</b>, non-volatile program memory <b>64</b>, non-volatile data memory <b>66</b>, volatile data memory <b>68</b>, peripheral device controller <b>70</b>, and count-down timer <b>72</b> for the communication of address, data, and control signals (including interrupt signals) therebetween. The monitoring circuit <b>62</b> communicatively connects to the receiver <b>26</b> through signal lines <b>92</b>. Receiver <b>26</b> electrically connects, via respective signal lines <b>94</b>, <b>96</b>, to the diversity receive antenna <b>28</b> and the external antenna <b>38</b>. The peripheral device controller <b>70</b> communicatively connects to the liquid crystal display <b>36</b><i>a</i>, the high-level audio speaker <b>36</b><i>b</i>, the low-level audio speaker <b>36</b><i>c</i>, the high-intensity strobe light <b>36</b><i>d</i>, the low-intensity light emitting diode (LED) <b>36</b><i>e</i>, and the reset pushbutton <b>36</b><i>f </i>through respective signal lines <b>98</b>, <b>100</b>, <b>102</b>, <b>104</b>, <b>106</b>, <b>108</b>.
[0060] The power supply <b>30</b> connects, via electrical conductors <b>110</b>, to electrical plug <b>34</b> for the receipt of alternating-current electrical power. The power supply <b>30</b> converts the alternating-current electrical power into direct-current electrical power at appropriate voltages. The power supply <b>30</b> also connects to the microcomputer <b>24</b>, the receiver <b>26</b>, and the plurality of peripheral devices <b>36</b>, where necessary (although not shown in FIG. 2), for the delivery of direct-current electrical power thereto at appropriate voltages. The power supply <b>30</b> includes a charging and switching circuit <b>112</b> therein which bi-directionally connects to the backup battery <b>32</b> through conductors <b>114</b>. During operation, whenever alternating-current electrical power is supplied to the alert device <b>20</b>, the charging and switching circuit <b>112</b> charges the backup battery <b>32</b>, if necessary, by delivering direct-current electrical power to the backup battery <b>32</b> through conductors <b>114</b>. Alternatively, whenever alternating-current electrical power is not supplied to the alert device <b>20</b> (for example, due to a utility or other power failure), the backup battery <b>32</b> supplies direct-current electrical power to the charging and switching circuit <b>112</b> through conductors <b>114</b> for subsequent delivery to the microcomputer <b>24</b>, the receiver <b>26</b>, and the plurality of peripheral devices <b>36</b>, where necessary.
[0061] In accordance with the apparatus of the preferred embodiment of the present invention, the receiver <b>26</b> further includes those receivers capable of receiving digital cellular, PCS, or wireless telecommunication signals corresponding to alert messages <b>130</b> (described below) broadcast from cellular, PCS, or wireless telecommunication transmitters <b>120</b> residing on towers <b>122</b> that are positioned to provide cellular, PCS, or wireless telecommunications services for respective, localized, and identifiable geographical areas <b>124</b> as illustrated pictorially in FIG. 6. A receiver <b>26</b> produces the alert messages <b>130</b>, prior to their reception, by an alert messaging system. An alert messaging system is, typically, operated by a governmental authority and comprises telecommunications equipment, computer hardware and computer software which: (i) receives an alert from a source, for instance, the Emergency Alert System or National Weather Service or Department of Defense, (ii) determines whether one or more alert messages <b>130</b> corresponding to the alert should be broadcast, (iii) identifies the appropriate telecommunications transmitters <b>120</b> (and, hence, the geographical areas <b>124</b>) to which the alert message(s) <b>130</b> should be delivered, (iv) builds and formats the alert message(s) <b>130</b> appropriately, and (v) communicates the alert message(s) <b>130</b> to a cellular, PCS, or wireless telecommunications network for routing of the alert message(s) <b>130</b> to the identified telecommunications transmitter(s) <b>120</b> which, subsequently, broadcast the alert message(s) <b>130</b> to their respective geographical area(s) <b>124</b>.
[0062] The alert messages <b>130</b> received by receiver <b>26</b> and acted upon, as described below, by the alert device <b>20</b> include, according to the preferred embodiment of the present invention, messages <b>130</b> which are encoded by the alert messaging system according to the Broadcast Short Messages System in the format of a PCS short message (illustrated by the schematic data representation of FIG. 7). Each alert message <b>130</b> includes a message header <b>132</b> indicating that the message <b>130</b> includes alert data and the general level of the alert. Preferably, the header <b>132</b> comprises eight (8) bytes of data, including a three (3) byte market code <b>134</b>, a two (2) byte zone code <b>136</b>, a two (2) byte alert level code <b>138</b>, and a one (1) byte date stamp <b>140</b>. The market code <b>134</b> includes data which identifies the regional market for which the alert message <b>130</b> is intended (i.e., the regional market includes a plurality of telecommunication transmitters <b>120</b> located in the geographical region identified by the regional market code). The zone code <b>136</b> comprises data which identifies the particular telecommunication transmitter <b>120</b> within the regional market that is to broadcast the alert message <b>130</b>. Together, the market code <b>134</b> and the zone code <b>136</b> are used by the cellular, PCS, or wireless telecommunications network, as described above, for routing and communication of the alert message <b>130</b> to the telecommunications transmitter(s) <b>120</b> and geographical area <b>124</b> identified as appropriate by the alert messaging system.
[0063] The alert level code <b>138</b> of each alert message <b>130</b> includes data which identifies the severity and type of the alert condition. The EAS AM & FM Handbook, published by the Federal Communication Commission of the United States divides the alerts sent out by the Emergency Alert System (“EAS”) (referred to herein as “emergency alerts”) into three (3) general levels of severity. A “Level Zero” emergency alert (i.e., signified by an alert message <b>130</b> in which the alert level code <b>138</b> has a value of four (4)) indicates the existence of no emergency alert conditions and that previous emergency alerts are no longer valid or no longer in effect. A “Level One” alert (i.e., signified by an alert message <b>130</b> in which the alert level code <b>138</b> has a value of five (5)) indicates the existence, in the geographical area <b>124</b> to which the alert message <b>130</b> pertains and is communicated, of an emergency situation posing an extraordinary threat to the safety of life or property such as, but not limited to, the existence, or imminent existence, of a tornado, flood, fire, discharge of hazardous materials, industrial explosion, or nuclear incident. A “Level Two” emergency alert (i.e., signified by an alert message <b>130</b> in which the alert level code <b>138</b> has a value of six (6)) indicates the issuance of a severe weather watch or that a particular emergency condition is possible in the geographical area <b>124</b> to which the emergency alert is communicated via telecommunication transmitters <b>120</b>.
[0064] According to the preferred embodiments, the alert level code <b>138</b>, when appropriate, contains values other than those values described above to indicate other types of alerts and the respective severity of such other types of alerts. For instance, a “Level One” military alert (i.e., signified by an alert message <b>130</b> in which the alert level code <b>138</b> has a value of seven (7)) indicates the existence, for the geographical area <b>124</b> to which the alert message <b>130</b> pertains and is communicated, of an extremely important military alert (as an example, an alert requiring that all active duty military personnel and reservists report to their bases immediately). A “Level Two” military alert (i.e., signified by an alert message <b>130</b> in which the alert level code <b>138</b> has a value of eight (8)) indicates the existence, for the geographical area <b>124</b> to which the alert message <b>130</b> pertains and is communicated, of a less-important military alert (as an example, an alert requesting that all reservists report on Sunday instead of Saturday). It is understood that the scope of the present invention includes other types and severities of alerts having different values for alert level code <b>138</b>.
[0065] Each alert message <b>130</b> further includes a text message string <b>142</b> which follows the message header <b>132</b>. The text message string <b>142</b>, preferably, includes a maximum of 160 ASCII text characters for display on the liquid crystal display <b>36</b><i>a </i>of the alert device <b>20</b> and provides more detailed information or instructions related to an alert condition. Because each alert message <b>130</b> is broadcast by one or more particular telecommunications transmitters <b>120</b> to alert devices <b>20</b> present in a specific, identifiable geographical area <b>124</b>, information relevant to that geographical area <b>124</b> is includable in the text message string <b>142</b>. For example and not limitation, when a tornado has been identified by meterologists as heading in a path toward, for instance, the Dunwoody, Georgia community, an alert message <b>130</b> sent and broadcast to that area includes a text message string <b>142</b> storing a message such as “TAKE IMMEDIATE COVER—A TORNADO STRIKE MAY BE IMMINENT IN THE DUNWOODY, GEORGIA AREA!”. Other typical alert message text strings <b>142</b> include, for example and not limitation, messages such as “SEVERE THUNDERSTORMS WELL MOVE INTO YOUR AREA WITHIN 30 MINUTES”, “FLASH FLOODS ARE POSSIBLE IN YOUR AREA”, “ALL ALERTS FOR YOUR AREA HAVE LAPSED”, “AN ESCAPED CONVICT IS ON THE LOOSE IN YOUR AREA—PLEASE LOCK ALL DOORS AND WINDOWS”, or other relevant messages.
[0066] The alert device <b>20</b> operates, in accordance with a preferred method of the present invention, as illustrated in FIGS. <b>8</b>-<b>13</b>. In response to a user plugging the electrical plug <b>34</b> into an electrical outlet, the alert device <b>20</b> initiates operation at step <b>212</b> where the CPU <b>60</b> of the microcomputer <b>24</b> begins to execute the instructions of the main portion <b>210</b> of the computer software program <b>200</b> residing in non-volatile program memory <b>64</b>, thereby causing the alert device <b>20</b> to function as set forth in FIG. 8. After performing various initialization tasks, the CPU <b>60</b> executes, at step <b>214</b>, the instructions of a self-test routine <b>400</b> (illustrated in FIG. 9) which tests the alert device's <b>20</b> ability to display messages on the liquid crystal display <b>36</b><i>a</i>, to produce appropriate tones on the high-level audio speaker <b>36</b><i>b </i>and the low-level audio speaker <b>36</b><i>c</i>, and to generate flashing light from the high-intensity strobe light <b>36</b><i>d </i>and the low-intensity light-emitting diode <b>36</b><i>e</i>. Upon completing execution of the instructions of the self-test routine <b>400</b>, operation of the alert device <b>20</b> advances to step <b>216</b>.
[0067] The CPU <b>60</b> reads from the non-volatile data memory <b>66</b>, at step <b>216</b>, the starting channel identifier <b>76</b> of the range of channels to be monitored, or scanned, by the receiver <b>26</b> for the presence of a digital control channel. The CPU <b>60</b> sets the test channel identifier <b>91</b> of volatile data memory <b>68</b> to the value of the starting channel identifier <b>76</b> and then sets the monitoring circuit <b>62</b> and receiver <b>26</b> to monitor, or scan, the test channel identified by the test channel identifier <b>91</b> by (i) identifying the receive frequency <b>82</b> corresponding to the test channel through performance of a table lookup operation using the test channel identifier <b>91</b> and the plurality of receive frequencies <b>82</b> stored in non-volatile data memory <b>66</b> and by (ii) communicating the looked-up receive frequency <b>82</b> to the monitoring circuit <b>62</b> via bus <b>74</b>. The monitoring circuit <b>62</b> then sets the frequency to be received by the receiver <b>26</b> by communicating the receive frequency <b>82</b> to the receiver <b>26</b> via signal lines <b>92</b>. The receiver <b>26</b> then commences reception of signals on the receive frequency <b>82</b> and provides output on signal lines <b>92</b> to the monitoring circuit <b>62</b>, including the signal strength of the channel currently being monitored by the receiver <b>26</b>.
[0068] Upon receiving output from the receiver <b>26</b>, the monitoring circuit <b>62</b>, at. step <b>220</b>, analyzes the output from the receiver <b>26</b> to determine whether a digital control channel is present on the test channel identified by the test channel identifier <b>91</b>. If so, the monitoring circuit <b>62</b> so informs the CPU <b>60</b> and the CPU <b>60</b> stores the test channel identifier <b>91</b> in the plurality of channel identifiers <b>84</b> of the volatile data memory <b>68</b> at step <b>222</b>. Then, at step <b>224</b>, the CPU <b>60</b> reads the signal strength value <b>86</b> from the monitoring circuit <b>62</b>, via bus <b>74</b>, and stores the signal strength value <b>86</b> in volatile data memory <b>68</b> in association with the test channel identifier <b>91</b> stored at step <b>222</b> (i.e., as one channel identifier/signal strength pair <b>90</b> of the plurality of channel identifier/signal strength pair <b>90</b>). If not, the CPU <b>60</b> determines, at step <b>226</b>, whether the test channel identifier <b>91</b> equals the ending channel identifier <b>78</b>. If the test channel identifier <b>91</b> does not equal the ending channel identifier <b>78</b>, the CPU <b>60</b> increments the test channel identifier <b>91</b> of volatile data memory <b>68</b> by the test channel step-size <b>80</b> of non-volatile data memory <b>66</b> at step <b>228</b> and loops back to step <b>218</b> in order to set the monitoring circuit <b>62</b> and receiver <b>26</b> to monitor, or scan, the test channel identified by the incremented test channel identifier <b>91</b>.
[0069] If, at step <b>226</b>, the CPU <b>60</b> determines that the test channel identifier <b>91</b> equals the ending channel identifier <b>78</b>, all of the channels have been monitored for the presence of a digital control channel and the CPU <b>60</b> then determines, at step <b>230</b>, whether any digital control channels have been found by reviewing the table <b>88</b> of the plurality of channel identifier/signal strength pairs <b>90</b> for the presence of channel identifiers <b>84</b> and signal stength values <b>86</b>. If the CPU <b>60</b> determines, at step <b>230</b>, that no digital control channels have been found (i.e., that table <b>88</b> contains no channel identifiers <b>84</b> and signal strength values <b>86</b>), the CPU <b>60</b> instructs, at step <b>232</b>, the peripheral device controller <b>70</b> to display “NO SERVICE AVAILABLE” on the liquid crystal display <b>36</b><i>a</i>. The CPU <b>60</b> then loops back to step <b>216</b>.
[0070] If the CPU <b>60</b> determines, at step <b>230</b>, that a digital control channel has been found, the CPU <b>60</b> then, at step <b>236</b>, analyzes and compares the signal strength values <b>86</b> stored in volatile data memory <b>68</b> to identify and select the digital control channel having the strongest signal strength value <b>86</b> (the digital control channel so identified being referred to herein as the “alert channel”). At step <b>238</b>, the CPU <b>60</b> stores the channel identifier <b>84</b> of the alert channel as the alert channel pointer <b>93</b> in volatile data memory <b>68</b>. Next, at step <b>240</b>, the CPU <b>60</b> sets the monitoring circuit <b>62</b> to monitor the alert channel by retrieving the receive frequency <b>82</b> corresponding to the alert channel (referred to herein as the “alert channel receive frequency”) using the alert channel pointer <b>93</b> and the plurality of receive frequencies <b>82</b> stored in non-volatile data memory <b>66</b> and by communicating the alert channel receive frequency to the monitoring circuit <b>62</b> via bus <b>74</b>. The monitoring circuit <b>62</b> then sets the receiver <b>26</b> to receive signals at the alert channel receive frequency, by communicating the alert channel receive frequency to the receiver <b>26</b> through signal lines <b>92</b>.
[0071] Advancing to step <b>242</b>, the CPU <b>60</b> causes the graphical display of the signal strength of the alert channel by instructing the peripheral device controller <b>70</b> to energize the appropriate bars <b>39</b> of the signal strength indicator <b>37</b> of the liquid crystal display <b>36</b><i>a</i>. By graphically displaying the signal strength of the alert channel, the alert device <b>20</b> enables a user to move the alert device <b>20</b> to other locations (for instance, in the user's house) and to visually see any change in signal strength, thereby further enabling a user to select a location for the alert device <b>20</b> at which the alert device <b>20</b> receives the maximum possible signal strength for the alert channel. Next, at step <b>244</b>, the CPU <b>60</b> instructs the peripheral device controller <b>70</b>, via bus <b>74</b>, to display the word “READY” in the alphanumeric portion of the liquid crystal display <b>36</b><i>a</i>. In response, the peripheral device controller <b>70</b> communicates an appropriate command to the liquid crystal display <b>36</b><i>a</i>, via signal lines <b>98</b>, causing the liquid crystal display <b>36</b><i>a </i>to display the word “READY”.
[0072] In accordance with the method of the preferred embodiment of the present invention, the monitoring circuit <b>62</b> continually monitors, at step <b>246</b>, the alert channel for the presence of a broadcast short message until the monitoring circuit <b>62</b> detects a broadcast short message. Upon detection of a broadcast short message, the monitoring circuit <b>62</b> notifies the CPU <b>60</b> of the receipt of the broadcast short message at step <b>248</b> and, in response, the CPU <b>60</b> reads the header <b>132</b> of the broadcast short message. The CPU <b>60</b>, at step <b>250</b>, analyzes the header <b>132</b> and determines whether the broadcast short message is an alert message <b>130</b> by comparing the format and data of the received broadcast short message to the format and data values known to the CPU <b>60</b> as corresponding to an alert message <b>130</b>. If the CPU <b>60</b> determines that the broadcast short message is not an alert message <b>130</b>, the CPU <b>60</b> branches back to step <b>246</b> to resume monitoring of the alert channel. If the CPU <b>60</b> determines that the broadcast short message is an alert message <b>130</b>, the CPU <b>60</b> identifies the alert level of the alert message <b>130</b> by extracting the alert level code <b>138</b> from the alert message <b>130</b> at step <b>252</b>.
[0073] Proceeding to step <b>254</b>, the CPU <b>60</b> determines whether the alert level code <b>138</b> corresponds to a “Level Zero” emergency alert (i.e., the alert level code <b>138</b> has a value of <b>4</b>). If the CPU <b>60</b> determines that the alert message <b>130</b> is a message for a “Level Zero” emergency alert, the CPU <b>60</b> communicates, at step <b>256</b>, a command to the peripheral device controller <b>70</b>, via bus <b>74</b>, instructing the peripheral device controller <b>70</b> to stop the production of all tones from all audio speakers <b>36</b><i>b</i>, <b>36</b><i>c</i>. In response, the peripheral device controller <b>70</b> ceases the generation and supply of signals on signal lines <b>100</b>, <b>102</b> in order to, respectively, terminate the production of tones from the high-level audio speaker <b>36</b><i>b </i>and the low-level audio speaker <b>36</b><i>c</i>. Then, at step <b>258</b>, the CPU <b>60</b> communicates a command to the peripheral device controller <b>70</b>, via bus <b>74</b>, instructing the peripheral device controller <b>70</b> to stop the flashing of the high-intensity strobe light <b>36</b><i>d </i>and the low-intensity light-emitting diode <b>36</b><i>e</i>. The peripheral device controller <b>70</b>, in response, ceases the generation and supply of signals on signal lines <b>104</b>, <b>106</b>, thereby stopping the flashing of the high-intensity strobe light <b>36</b><i>d </i>and the low-intensity light-emitting diode <b>36</b><i>e</i>. The CPU <b>60</b> then loops back to step <b>246</b> and resumes monitoring the alert channel.
[0074] If, at step <b>254</b>, the CPU <b>60</b> determines that the alert level code <b>138</b> does not correspond to a “Level Zero” emergency alert, the CPU <b>60</b> determines, at step <b>260</b>, whether the alert level code <b>138</b> corresponds to a “Level One” emergency alert. If so, the CPU <b>60</b> executes a call, at step <b>262</b>, to the high-level alarm routine <b>500</b> and begins execution according to the high-level alarm routine <b>500</b>, described below, in order to cause the production of a high-decibel level tone on the high-level audio speaker <b>36</b><i>b </i>and the flashing of the high-intensity strobe light <b>36</b><i>d</i>. Upon completion of the high-level alarm routine <b>500</b>, the CPU <b>60</b> loops back to step <b>246</b> and resumes monitoring of the alert channel. If the CPU <b>60</b> determines, at step <b>260</b>, that the alert level code <b>138</b> does not correspond to a “Level One” emergency alert, the CPU <b>60</b> continues operation with step <b>264</b>.
[0075] At step <b>264</b>, the CPU <b>60</b> determines whether the alert level code <b>138</b> corresponds to a “Level Two” emergency alert. If so, the CPU <b>60</b> executes a call, at step <b>266</b>, to the low-level alarm routine <b>600</b> and begins execution in accordance with the low-level alarm routine <b>600</b>, described below, in order to cause the production of a “chirping tone” on the low-level audio speaker <b>36</b><i>c </i>and the flashing of the low-intensity light-emitting diode <b>36</b><i>e</i>. Upon completion of the low-level alarm routine <b>600</b>, the CPU <b>60</b> loops back to step <b>246</b> and resumes monitoring of the alert channel. If the CPU <b>60</b> determines, at step <b>264</b>, that the alert level code <b>138</b> does not correspond to a “Level One” emergency alert, the CPU <b>60</b> continues operation with step <b>266</b>.
[0076] The CPU <b>60</b> determines, at step <b>268</b>, whether the alert level code <b>138</b> corresponds to a “Level One” military alert. If so, the CPU <b>60</b> executes a call, at step <b>270</b>, to the high-level alarm routine <b>500</b> and begins execution according to the high-level alarm routine <b>500</b>, described below, in order to cause the production of a high-decibel level tone on the high-level audio speaker <b>36</b><i>b </i>and the flashing of the high-intensity strobe light <b>36</b><i>d</i>. Upon completion of the high-level alarm routine <b>500</b>, the CPU <b>60</b> loops back to step <b>246</b> and resumes monitoring of the alert channel. If the CPU <b>60</b> determines, at step <b>268</b>, that the alert level code <b>138</b> does not correspond to a “Level One” military alert, the CPU <b>60</b> continues operation with step <b>272</b>.
[0077] At step <b>272</b>, the CPU <b>60</b> determines whether the alert level code <b>138</b> corresponds to a “Level Two” military alert. If so, the CPU <b>60</b> executes a call, at step <b>274</b>, to the low-level alarm routine <b>600</b> and begins execution in accordance with the low-level alarm routine <b>600</b>, described below, in order to cause the production of a “chirping tone” on the low-level audio speaker <b>36</b><i>c </i>and the flashing of the low-intensity light-emitting diode <b>36</b><i>e</i>. Upon completion of the low-level alarm routine <b>600</b>, the CPU <b>60</b> loops back to step <b>246</b> and resumes monitoring of the alert channel. If the CPU <b>60</b> determines, at step <b>272</b>, that the alert level code <b>138</b> does not correspond to a “Level One” emergency alert, the CPU <b>60</b> loops back to step <b>246</b> and resumes monitoring of the alert channel.
[0078]FIG. 9 displays the self-test routine <b>400</b>, in accordance with the method of the preferred embodiment of the present invention, which includes steps that the CPU <b>60</b> performs when the alert device <b>20</b> calls the self-test routine <b>400</b> at step <b>214</b> of the main portion <b>210</b> of the computer software program <b>200</b>. After performing initialization tasks at step <b>402</b>, the CPU <b>60</b> communicates, at step <b>404</b>, an instruction to the peripheral device controller <b>70</b>, via bus <b>74</b>, directing the peripheral device controller <b>70</b> to display the words “SELF-TEST IN PROGRESS” on the liquid crystal display <b>36</b><i>a</i>. The peripheral device controller <b>70</b> then communicates appropriate signals to the liquid crystal display <b>36</b><i>a </i>through signal lines <b>98</b>. In response, the liquid crystal display <b>36</b><i>a </i>displays the words “SELF-TEST IN PROGRESS”. Then, at steps <b>406</b> and <b>408</b>, the CPU <b>60</b> communicates instructions to the peripheral device controller <b>70</b> through bus <b>74</b> which direct the peripheral device controller <b>70</b> to generate appropriate signals on signal lines <b>100</b>, <b>104</b> which, respectively, cause the high-level audio speaker <b>36</b><i>b </i>to produce a high-decibel level tone and the high-intensity strobe light <b>36</b><i>d </i>to periodically flash. After delaying for the period of time stored in the self-test time period <b>81</b> of the non-volatile data memory <b>66</b> at step <b>410</b>, the CPU <b>60</b> communicates commands, at steps <b>412</b> and <b>414</b>, to the peripheral device controller <b>70</b> directing the peripheral device controller <b>70</b> to terminate the production of appropriate signals on respective signal lines <b>100</b>, <b>104</b> and, hence, stop the high-level audio speaker <b>36</b><i>b </i>from generating a high-decibel level tone and the high-intensity strobe light <b>36</b><i>d </i>from flashing.
[0079] Continuing at step <b>416</b>, the CPU <b>60</b> directs the peripheral device controller <b>70</b>, by the communication of a command therebetween over bus <b>74</b>, to initiate the production of a low-decibel level tone on the low-level audio speaker <b>36</b><i>c</i>. In response, the peripheral device controller <b>70</b> generates appropriate signals on signal lines <b>102</b> which cause the low-level audio speaker <b>36</b><i>c </i>to begin producing a low-decibel tone. Next, at step <b>420</b>, the CPU <b>60</b> sends an instruction to the peripheral device controller <b>70</b>, via bus <b>74</b>, instructing the peripheral device controller <b>70</b> to begin flashing of the low-intensity light-emitting diode <b>36</b><i>e</i>. The peripheral device controller <b>70</b>, in response, generates appropriate signals on signal lines <b>106</b> which cause the low-intensity light-emitting diode <b>36</b><i>e </i>to flash periodically. Upon delaying, at step <b>422</b> for a period of time equaling the self-test timer period <b>81</b> stored in non-volatile data memory <b>66</b>, the CPU <b>60</b> communicates commands to the peripheral device controller <b>70</b> over bus <b>74</b>, at steps <b>424</b> and <b>426</b>, which direct the peripheral device controller <b>70</b> to stop the production of the low-decibel level tone and flashing light. Responsive to the commands, the peripheral device controller <b>70</b> terminates the production of signals on respective signal lines <b>102</b>, <b>106</b>, thereby stopping the generation of the low-decibel level tone from the low-level audio speaker <b>36</b><i>c </i>and the flashing of the low-intensity light-emitting diode <b>36</b><i>e. </i>
[0080] The CPU <b>60</b>, at step <b>428</b>, transmits an instruction over bus <b>74</b> to the peripheral device controller <b>70</b> directing the peripheral device controller <b>70</b> to cause the display of the words “SELF-TEST SUCCESSFULLY COMPLETED” on the liquid crystal display <b>36</b><i>a</i>. The peripheral device controller <b>70</b> then generates appropriate signals on signal lines <b>98</b>, including signals representing the words “SELF-TEST SUCCESSFULLY COMPLETED”, to cause those words to appear on the liquid crystal display <b>36</b><i>a</i>. In response, the liquid crystal display <b>36</b><i>a </i>displays the words “SELF-TEST SUCCESSFULLY COMPLETED”. Next, the CPU <b>60</b> delays, at step <b>430</b>, for a period of time corresponding to the self-test time period <b>81</b> stored in the non-volatile data memory <b>66</b> before returning, at step <b>432</b>, to the execution in accordance with the main portion <b>210</b> of the computer software program <b>200</b>.
[0081]FIG. 10 displays the high-level alarm routine <b>500</b>, in accordance with the method of the preferred embodiment of the present invention, which includes steps that the CPU <b>60</b> performs when the alert device <b>20</b> calls the high-level alarm routine <b>500</b> at steps <b>262</b> and <b>270</b> of the main portion <b>210</b> of the computer software program <b>200</b>. After performing various initialization tasks at step <b>502</b>, the CPU <b>60</b> communicates a command, at step <b>504</b> and via bus <b>74</b>, to the peripheral device controller <b>70</b> instructing the peripheral device controller <b>70</b> to start producing a high-decibel level tone on the high-level audio speaker <b>36</b><i>b</i>. In response, the peripheral device controller <b>70</b> generates and supplies, through signal lines <b>100</b>, appropriate signals to the high-level audio speaker <b>36</b><i>b</i>, thereby causing the high-level audio speaker <b>36</b><i>b </i>to produce a continuous high-decibel level tone. In an alternate method of the present invention, the peripheral device controller <b>70</b> causes the high-level audio speaker <b>36</b><i>b </i>to produce non-continuous, high-decibel level tones.
[0082] At step <b>506</b>, the CPU <b>60</b> similarly communicates a command, via bus <b>74</b>, to the peripheral device controller <b>70</b> instructing the peripheral device controller <b>70</b> to start flashing the high-intensity strobe light <b>36</b><i>d</i>. The peripheral device controller <b>70</b>, in response, produces and supplies appropriate signals, via signal lines <b>104</b>, to the high-intensity strobe light <b>36</b><i>d</i>, thereby causing the high-intensity strobe light <b>36</b><i>d </i>to flash at a periodic rate. In an alternate method of the present invention, the peripheral device controller <b>70</b> causes the high-intensity strobe light <b>36</b><i>d </i>to flash in a non-periodic manner.
[0083] Continuing at step <b>508</b>, the CPU <b>60</b> extracts the text message string <b>142</b> from the alert message <b>130</b> and communicates the extracted text message string <b>142</b> (and a command to display the extracted text message string <b>142</b>) to the peripheral device controller <b>70</b> via bus <b>74</b>. The peripheral device controller <b>70</b> then communicates appropriate signals, including the extracted text message string <b>142</b>, to the liquid crystal display <b>36</b><i>a </i>through signal lines <b>98</b> in order to cause the extracted text message string <b>142</b> to appear on the liquid crystal display <b>36</b><i>a</i>. Upon display of the extracted text message string <b>142</b> on the liquid crystal display <b>36</b><i>a</i>, the CPU <b>60</b> sets, at step <b>510</b>, the count-down timer <b>72</b> by sending appropriate instructions to the count-down timer <b>72</b> via bus <b>74</b>, to begin counting down for, according to the preferred embodiments, a period of two (2) hours during which the extracted text message string <b>142</b> remains displayed on the liquid crystal display <b>36</b><i>a</i>. Then, at step <b>512</b>, the CPU <b>60</b> resumes execution in accordance with the main portion <b>210</b> of the computer software program <b>200</b> after the step which called for execution of the steps of the high-level alarm routine <b>500</b>.
[0084]FIG. 11 displays the low-level alarm routine <b>600</b>, in accordance with the method of the preferred embodiment of the present invention, which includes steps that the CPU <b>60</b> performs when the alert device <b>20</b> calls the low-level alarm routine <b>600</b> at steps <b>266</b> and <b>274</b> of the main portion <b>210</b> of the computer software program <b>200</b>. After performing various initialization tasks at step <b>602</b>, the CPU <b>60</b> communicates a command, at step <b>604</b> and via bus <b>74</b>, to the peripheral device controller <b>70</b> instructing the peripheral device controller <b>70</b> to start producing a low-decibel “chirping” tone on the low-level audio speaker <b>36</b><i>c</i>. In response, the peripheral device controller <b>70</b> generates and supplies, through signal lines <b>102</b>, appropriate signals to the low-level audio speaker <b>36</b><i>c</i>, thereby causing the low-level audio speaker <b>36</b><i>c </i>to produce a “chirping” low-decibel level tone. In an alternate method of the present invention, the peripheral device controller <b>70</b> causes the low-level audio speaker <b>36</b><i>c </i>to produce continuous, low-decibel level tone.
[0085] At step <b>606</b>, the CPU <b>60</b> similarly communicates a command, via bus <b>74</b>, to the peripheral device controller <b>70</b> instructing the peripheral device controller <b>70</b> to start flashing the low-intensity light-emitting diode <b>36</b><i>e</i>. The peripheral device controller <b>70</b>, in response, produces and supplies appropriate signals, via signal lines <b>106</b>, to the low-intensity light-emitting diode <b>36</b><i>e</i>, thereby causing the low-intensity light-emitting diode <b>36</b><i>e </i>to flash at a periodic rate. In an alternate method of the present invention, the peripheral device controller <b>70</b> causes the low-intensity light-emitting diode <b>36</b><i>e </i>to flash in a non-periodic manner.
[0086] Continuing at step <b>608</b>, the CPU <b>60</b> extracts the text message string <b>142</b> from the alert message <b>130</b> and communicates the extracted text message string <b>142</b> (and a command to display the extracted text message string <b>142</b>) to the peripheral device controller <b>70</b> via bus <b>74</b>. The peripheral device controller <b>70</b> then communicates appropriate signals, including the extracted text message string <b>142</b>, to the liquid crystal display <b>36</b><i>a </i>through signal lines <b>98</b> in order to cause the extracted text message string <b>142</b> to appear on the liquid crystal display <b>36</b><i>a</i>. Upon display of the extracted text message string <b>142</b> on the liquid crystal display <b>36</b><i>a</i>, the CPU <b>60</b> sets, at step <b>610</b>, the count-down timer <b>72</b> by sending appropriate instructions to the count-down timer <b>72</b> via bus <b>74</b>, to begin counting down for, according to the preferred embodiments, a period of two (2) hours during which the extracted text message string <b>142</b> remains displayed on the liquid crystal display <b>36</b><i>a</i>. Then, at step <b>612</b>, the CPU <b>60</b> resumes execution in accordance with the main portion <b>210</b> of the computer software program <b>200</b> after the step which called for execution of the steps of the low-level alarm routine <b>600</b>.
[0087]FIG. 12 displays the timer interrupt handling routine <b>700</b>, in accordance with the method of the preferred embodiment of the present invention, which includes steps that the CPU <b>60</b> performs when the count-down timer <b>72</b> completes counting down to zero and provides an asynchronous interrupt signal to the CPU <b>60</b> via bus <b>74</b>. After performing various initialization tasks at step <b>702</b>, the CPU <b>60</b> communicates a command, at step <b>704</b> and via bus <b>74</b>, to the peripheral device controller <b>70</b> instructing the peripheral device controller <b>70</b> to clear the liquid crystal display <b>36</b><i>a </i>and then display the word “READY” on the liquid crystal display <b>36</b><i>a</i>. The peripheral device controller <b>70</b> then communicates appropriate signals, including the word “READY”, to the liquid crystal display <b>36</b><i>a </i>through signal lines <b>98</b> in order to cause erasure of all text present on the liquid crystal display <b>36</b><i>a </i>and to cause the word “READY” to appear on the liquid crystal display <b>36</b><i>a</i>. In response, the liquid crystal display <b>36</b><i>a </i>erases all text and then displays the word “READY”. The CPU <b>60</b>, at step <b>706</b>, resumes execution in accordance with the main portion <b>210</b> of the computer software program <b>200</b>.
[0088]FIG. 13 displays the reset interrupt handling routine <b>800</b>, in accordance with the method of the preferred embodiment of the present invention, which includes steps that the CPU <b>60</b> performs when the reset pushbutton <b>36</b><i>f </i>is depressed by a user (i.e., to stop the generation of all sounds and all flashing light) and the peripheral device controller <b>70</b>, in response, provides an asynchronous interrupt signal to the CPU <b>60</b> via bus <b>74</b>. After performing various initialization tasks at step <b>802</b>, the CPU <b>60</b> communicates, at step <b>804</b>, a command to the peripheral device controller <b>70</b>, via bus <b>74</b>, instructing the peripheral device controller <b>70</b> to stop the production of all tones from all audio speakers <b>36</b><i>b</i>, <b>36</b><i>c</i>. In response, the peripheral device controller <b>70</b> ceases the generation and supply of signals on signal lines <b>100</b>, <b>102</b> in order to terminate the production of tones from the high-level audio speaker <b>36</b><i>b </i>and the low-level audio speaker <b>36</b><i>c</i>. Then, at step <b>806</b>, the CPU <b>60</b> communicates a command to the peripheral device controller <b>70</b>, via bus <b>74</b>, instructing the peripheral device controller <b>70</b> to stop the flashing of the high-intensity strobe light <b>36</b><i>d </i>and the low-intensity light-emitting diode <b>36</b><i>e</i>. The peripheral device controller <b>70</b>, in response, ceases the generation and supply of signals on signal lines <b>104</b>, <b>106</b>, thereby stopping the flashing of the high-intensity strobe light <b>36</b><i>d </i>and the low-intensity light-emitting diode <b>36</b><i>e</i>. After stopping the generation of all flashing light, the CPU <b>60</b>, at step <b>808</b>, resumes execution in accordance with the main portion <b>210</b> of the computer software program <b>200</b>.
[0089] It is understood that the term “PCS”, as used herein, refers to any short-range, geographically-distributed broadcast system similar to those commonly used in cellular or PCS mobile telecommunication networks and the like. It is also understood that the scope of the present invention includes alert devices which operate with other digital wireless telecommunication networks and which receive broadcast messages which are formatted and transmitted using formats, protocols, geographical identifiers, and severity indicators other than that defined by the Broadcast Short Messages System or by the EAS AM & FM Handbook.
[0090]FIG. 14 displays an alert device <b>20</b>′, in accordance with an apparatus of a first alternate preferred embodiment of the present invention, for use at installations where audible tones and flashing light must be delivered to persons located remotely from the site of the alert device <b>20</b>′. The alert device <b>20</b>′ is substantially similar to the alert device of the preferred embodiment, except that the alert device <b>20</b>′ further comprises an external peripheral interface <b>75</b>′ which connects to the peripheral device controller <b>70</b>′ and to pluralities of remote peripheral devices <b>37</b><i>a</i>′, <b>37</b><i>b</i>′, <b>37</b><i>c</i>′ (see FIG. 15). Each plurality of remote peripheral devices <b>37</b>′ comprises a remotely-located liquid crystal display <b>36</b><i>aa</i>′, a remotely-located high-level audio speaker <b>36</b><i>bb</i>′, a remotely-located low-level audio speaker <b>36</b><i>cc</i>′, a remotely-located high-intensity strobe light <b>36</b><i>dd</i>′, a remotely-located low-intensity light-emitting diode <b>36</b><i>ee</i>′, and a remotely-located reset pushbutton <b>36</b><i>ff</i>′ which connect to the external peripheral interface <b>75</b>′ via respective signal lines <b>99</b>′, <b>101</b>′, <b>103</b>′, <b>105</b>′, <b>107</b>′, <b>111</b>′.
[0091] According to the first alternate preferred embodiment of the present invention, the apparatus of the first alternate preferred embodiment, displayed in FIGS. 14 and 15, operates in accordance with a method of the first alternate preferred embodiment which is substantially similar to the method of the preferred embodiment, except that when tones, flashing light and textual displays are produced by the plurality of peripheral devices <b>36</b>′ located within or protruding from the enclosure <b>22</b>′ of the alert device <b>20</b>′, tones, flashing light and textual displays are also simultaneously produced from all of the peripheral devices of the pluralities of remote peripheral devices <b>37</b><i>a</i>′, <b>37</b><i>b</i>′, <b>37</b><i>c</i>′ in response to signals produced on signal lines <b>109</b>′ by the peripheral device controller <b>70</b>′ and communicated by the external peripheral interface <b>75</b>′ to the pluralities of remote peripheral devices <b>37</b><i>a</i>′, <b>37</b><i>b</i>′, <b>37</b><i>c</i>′. Similarly, when termination of the tones, flashing light and display of textual information produced by the plurality of peripheral devices <b>36</b>′ located within or protruding from the enclosure <b>22</b>′ of the alert device <b>20</b>′ occurs, termination of the tones, flashing light and display of textual information simultaneously occurs with respect to the pluralities of remote peripheral devices <b>37</b><i>a</i>′, <b>37</b><i>b</i>′, <b>37</b><i>c</i>′in response to signals produced on signal lines <b>109</b>′ by the peripheral device controller <b>70</b>′ and communicated by the external peripheral interface <b>75</b> to the pluralities of remote peripheral devices <b>37</b><i>a</i>′, <b>37</b><i>b</i>′, <b>37</b><i>c</i>′.
[0092] According to a second alternate preferred embodiment of the present invention, the alert device <b>20</b>″ may be adapted for use in a system wherein a service provider provides alert messages to subscribers (i.e., users) having alert devices and charges the users a periodic subscription fee. Specifically, alert device <b>20</b>″ supports operation at two or more service levels or modes that reflect and correspond to the subscription status of the user. The alert device <b>20</b>″, preferably, includes a default service level that is preprogrammed at the factory and which is later subject to modification in response to control signals received from an alert messaging system. This allows the service provider to remotely control and/or set the service level of a user's alert device <b>20</b>″ to coincide with the service level paid for by the user.
[0093] For example and not limitation, a service provider's alert messaging system may send an alert message, including a service level data field, which is received and interpreted by an alert device <b>20</b>″. The service level data field may be set to any of the following levels: (1) fully enabled; (2) partially enabled; or, (3) fully disabled. In the fully enabled mode, alert device <b>20</b>″ reacts to all alert messages and provides the user with any received information. In the partially enabled mode, alert device <b>20</b>″ only reacts to the most severe alerts (i.e., “Level One” alerts) to provide the user with a minimal level of service, warnings, and protection. In the fully disabled mode, alert device <b>20</b>″ will not react to any alert messages.
[0094] Preferably, a default service level is stored in a memory of each alert device <b>20</b>″ during manufacture of the alert device <b>20</b>″. For purposes of requiring subscription, the default service level is ideally set to the fully disabled level. As a consequence, a user must contact a service provider and establish a subscription to the service provider's notification or alert messaging service in order for the user's alert device <b>20</b>″ to react to alert messages as desired by the user. However, it may be desirable to set the default service level to a different service level for reasons of liability or to improve customer relations. For example, the default level might be set to the partially enabled level to ensure that even non-subscriber users are provided with critical information relating to high level emergencies (i.e., “Level Once” alerts), thereby reducing the manufacturer's liability. Alternatively, the default level might be set to the fully enabled level for a set period of time after initial activation, during which time the user's alert device <b>20</b>″ would operate at the full service level as an inducement to encourage the user to subscribe at the full service level.
[0095]FIG. 16 displays a startup service level check routine <b>900</b>, in accordance with the method of the second alternate preferred embodiment of the present invention. At step <b>902</b>, CPU <b>60</b>″ retrieves current service level data from non-volatile memory <b>66</b>″, which has previously been set during manufacture or modified remotely by the receipt of an updated service level from a service provider. After performing other startup tasks heretofore discussed, CPU <b>60</b>″ communicates a command, at step <b>904</b> and via bus <b>74</b>″ to the peripheral device controller <b>70</b>″, instructing the peripheral device controller <b>70</b>″ to clear the liquid crystal display <b>36</b><i>a</i>″ and then display an appropriate message. For example, if the service level is currently set to fully enabled, the displayed message may be “UNIT FULLY FUNCTIONAL”; if the service level is set to partially disabled, the displayed message is “PLEASE CONTACT SERVICE PROVIDER—MESSAGE <b>1</b>”, the low-intensity light-emitting diode <b>36</b><i>e </i>is made to flash, and the low-level audio speaker <b>36</b><i>c </i>is made to produce a “chirping” low-decibel level tone; and if the service level is set to Fully Disabled the displayed message is “PLEASE CONTACT SERVICE PROVIDER —MESSAGE <b>2</b>”, the high-intensity strobe light <b>36</b><i>d </i>is made to flash, and the high-level audio speaker <b>36</b><i>b </i>is made to produce a continuous high-decibel level tone. CPU <b>60</b>″ then proceeds to step <b>906</b> and monitors for incoming messages as previously discussed in relation to FIGS. <b>8</b>-<b>13</b>.
[0096] In order to alter the service level of a particular alert device <b>20</b>″, it is necessary to provide a mechanism wherein each individual alert device <b>20</b>″ may be individually identified and or selected from all other alert devices <b>20</b>″. According to the second alternate preferred embodiment, such identification or selection is accomplished by assigning each alert device <b>20</b>″ a unique electronic serial number (ESN) that is stored in non-volatile memory <b>66</b>″. The ESN is, preferably, either an 8 digit hexadecimal number or an 11 digit decimal number. The leading digits of the number (i.e., the first two for hexadecimal and the first three for decimal) indicate (i.e. uniquely identify) the manufacturer of the alert device <b>20</b>″. The remaining digits are a unique sequence of digits for each device, whereby each device of the manufacturer is uniquely identified.
[0097] In operation, the alert messaging system generates alert messages, as appropriate (i.e., when one or more subscribers change their subscription(s) to subscribe to a different service level than is currently in effect at their respective alert devices <b>20</b>″), instructing each appropriate alert device <b>20</b>″ to alter its service level. Preferably, service level alteration messages are identified by assigning a separate set of alert levels in the message header that correspond to the selected service level to which the identified devices are to be set. In the standard short message format, each service level alert message may include up to seventeen ESN's in the body of the message, thus allowing up to seventeen units to have their service levels adjusted by a single broadcast of a short message. It is understood that the scope of the present invention comprises all apparatus and methods for communicating and setting the service level of an alert device <b>20</b>″.
[0098] A service level adjustment routine <b>1000</b> is illustrated in FIG. 17 in accordance with the second alternate preferred embodiment of the present invention. At step <b>1002</b>, alert device <b>20</b>″ monitors the selected frequency for a message generated by the alert messaging system. Upon receipt of an alert message, CPU <b>60</b>″ of alert device <b>20</b>″ proceeds to step <b>1004</b> and examines the message to determine whether the message header includes an alert level corresponding to (i.e., identifying the message as) a service level adjustment message. If the message header does not include an alert level corresponding to a service level adjustment message, CPU <b>60</b>″ then ignores the message and returns to step <b>1002</b> to continue monitoring for alert messages.
[0099] If the message header includes an alert level corresponding to a service level adjustment message, CPU <b>60</b>″ then proceeds to scan the message body at step <b>1006</b> searching for an ESN that matches the ESN of the alert device <b>20</b>″ as stored in the device's non-volatile memory <b>66</b>″. If the ESN of the alert device <b>20</b>″ is not found in the body of the message, CPU <b>60</b>″ then returns to step <b>1002</b> and continues to monitor for additional messages. If, alternatively, the ESN of the device is found in the body of the message, CPU <b>60</b>″ proceeds to step <b>1008</b> and sets the value of the service level data stored in non-volatile memory <b>66</b>″ to match the service level encoded in the message header. CPU <b>60</b>″ then returns to step <b>1002</b> and continues to monitor for additional messages.
[0100]FIG. 18 illustrates a service level authentication routine <b>1100</b> wherein CPU <b>60</b>″ operates according to a received service level. At step <b>1102</b>, CPU <b>60</b>″ monitors for an alert message as previously described in relation to FIGS. <b>8</b>-<b>13</b>. Upon receipt of an alert message, CPU <b>60</b>″ proceeds to step <b>1104</b> and determines whether the alert message includes a header including alert level information. If no alert level information is included in the message header, CPU <b>60</b>″ returns to step <b>1102</b> and resumes monitoring for broadcast alert messages. If alert level information is included in the message header, CPU <b>60</b>″ then proceeds to step <b>1106</b> and compares the included alert level to the service level stored in non-volatile memory <b>66</b>″. If the included alert level is numerically equal to or greater than the stored service level, CPU <b>60</b>″ then proceeds to step <b>1108</b> and initiates the appropriate alert routine as previously described in relation to FIG. 10 or FIG. 11. If the included alert level is numerically less than the stored service level, CPU <b>60</b>″ ignores the alert message and returns to step <b>1102</b> to resume monitoring for additional alert messages.
[0101] In a third alternate preferred embodiment of the present invention, the alert device <b>20</b>′″ may be configured to support an additional alert level to be utilized for the reception of advertising messages for display on liquid crystal display <b>36</b><i>a</i>′″. This allows a service provider to offer a variety of additional billing and service plan options. For example, the service provider may allow full-rate subscriptions that do not provide advertising, or alternatively may offer reduced rate subscriptions that require that the alert device <b>20</b>′″ occasionally display advertising messages. In the latter case, the advertising revenue may offset a portion of the reduction in subscription fees.
[0102] In a system supporting advertising, upon receipt of an alert message, CPU <b>60</b>′″ also examines the message header as previously described in relation to FIG. 18. If the message header includes an alert level corresponding to an advertising alert (i.e., indicating that the message is an advertising alert message), CPU <b>60</b>′″ then communicates a command via bus <b>74</b>′″to the peripheral device controller <b>70</b>′″, instructing the peripheral device controller <b>70</b>′″ to clear the liquid crystal display <b>36</b><i>a</i>′″ and then to display thereon advertising text included in the message's body.
[0103] The present invention also operates to provide remote provisioning of the alert device <b>20</b> for preferred system providers. Each alert device <b>20</b> may maintain a preferred provider list. The preferred provider list is a list of acceptable service providers with each provider being a Public Land Mobile Network (PLMN) or other telecommunication provider. The preferred system provider list can be set at time of manufacturer of the alert device <b>20</b>. Subsequently, once the alert device <b>20</b> is deployed, the preferred provider list can be updated by receiving messages sent to the individual alert device <b>20</b> or through a broadcast message receivable by multiple alert devices <b>20</b>. In one embodiment, when the alert device <b>20</b> detects a control channel, the PLMN value on this control channel is compared to those in the preferred provider list. If there is a match, this control channel is suitable for this device. The opcodes listed below in Table 1 indicate another embodiment that can be used to deliver preferred system provider updates, and other control measures to the alert device <b>20</b>. Thus, if updates are received, they will be added to the internal preferred system provider list, which can be stored in non-volatile memory. Alternatively, the new additions can be stored in volatile memory and thus be cleared upon resetting or removing power from the alert device <b>20</b>. In either case, the revised preferred system provider list can be used in subsequent scans.
[0104] The present invention also operates to provide remote provisioning of the alert device <b>20</b> for Closed User Groups (CUG). Each alert device <b>20</b> may maintain a CUG list. The CUG list can be set at time of manufacturer of the alert device <b>20</b>. Subsequently, once the alert device <b>20</b> is deployed, the CUG list can be updated by receiving messages sent to the individual alert device <b>20</b> or through a broadcast message receivable by multiple alert devices <b>20</b>. Thus, the alert device <b>20</b> can receive over the air updates to its CUG list. The opcodes listed below in Table 1 indicate one embodiment that can be used to deliver CUG updates, and other control measures to the alert device <b>20</b>. If updates are received they will be added to its internal list and stored in non-volatile memory or volatile memory. The revised CUG list can be used when checking subsequent messages.
[0105] In one embodiment, the alert device <b>20</b> is a receive-only device that monitors the control channel of GSM cellular networks. The alert device <b>20</b> will react to two types of cell broadcast messages; general alerts and CUG alerts. General alerts are for all reception by all alert devices <b>20</b> that are within the range of the broadcast message. CUG alerts are only for those alert devices <b>20</b> that have a matching CUG ID in its internal list of CUGs.
[0106] The present invention also operates to provide the ability to display custom standby messages (such as DHS alert level) on the alert device <b>20</b>. Each broadcast message destined for an alert device <b>20</b> will include the following fields in the header: alert level and message ID. In one embodiment, the alert level is an eight-bit value and is sent in the Serial Number portion of the message. The eight-bit value will correspond to the message code. This is used to differentiate between different levels of alerts and therefore trigger different actions in the alert device <b>20</b>. This information can also be thought of as an opcode, such that based on the value of this opcode, the remaining contents of the message will be interpreted accordingly.
[0107] In addition, the message ID is a four-bit value and is also sent in the Serial Number potion of the message. The message ID is used to identify the message, such that if the message is received multiple times, the alert device <b>20</b> is able to determine that the message is a duplicate.
[0108] As an exemplary embodiment, Table 1 provides one typical assignment of opcode values. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="35PT" align="center" /><colspec colname="2" colwidth="56PT" align="left" /><colspec colname="3" colwidth="126PT" align="left" /><thead><row><entry namest="1" nameend="3" align="center">TABLE 1</entry></row><row><entry /></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Opcodes</entry><entry>Alert Level</entry><entry>Definition Of Alert Level</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>0x00</entry><entry>Level 0 Alert</entry><entry>Resets unit alerts. Displays text based</entry></row><row><entry /><entry /><entry>upon provisioning indicator.</entry></row><row><entry>0x01</entry><entry>Level 1 Alert</entry><entry>Causes unit to illuminate strobe, and</entry></row><row><entry /><entry /><entry>high decibel alarm.</entry></row><row><entry /><entry /><entry>Display shows body text of message</entry></row><row><entry /><entry /><entry>received.</entry></row><row><entry>0x02</entry><entry>Level 2 Alert</entry><entry>Causes unit to flash LED, and low</entry></row><row><entry /><entry /><entry>decibel alarm.</entry></row><row><entry /><entry /><entry>Display shows body text of</entry></row><row><entry /><entry /><entry>message received.</entry></row><row><entry>0x03</entry><entry>Level 3 Alert</entry><entry>Display shows body text of message</entry></row><row><entry /><entry /><entry>received, no audio but alert LED</entry></row><row><entry /><entry /><entry>illuminated.</entry></row><row><entry>0x81</entry><entry>Provisioning 1</entry><entry>Fully Enabled - sets provisioning indicator</entry></row><row><entry /><entry /><entry>to value of 1.</entry></row><row><entry /><entry /><entry>Unit is capable of receiving and reacting</entry></row><row><entry /><entry /><entry>to all alert levels.</entry></row><row><entry>0x82</entry><entry>Provisioning 2</entry><entry>Partially Disabled - sets provisioning</entry></row><row><entry /><entry /><entry>indicator to value of 2. Unit is capable</entry></row><row><entry /><entry /><entry>of receiving and reacting only to</entry></row><row><entry /><entry /><entry>level 0 or level 1 messages.</entry></row><row><entry>0x83</entry><entry>Provisioning 3</entry><entry>Fully Disabled - sets provisioning</entry></row><row><entry /><entry /><entry>indicator to value of 3. Unit is capable</entry></row><row><entry /><entry /><entry>of receiving and but not reacting to</entry></row><row><entry /><entry /><entry>level 1,2, or three alerts. The unit is</entry></row><row><entry /><entry /><entry>capable of receiving and reacting to</entry></row><row><entry /><entry /><entry>provisioning messages.</entry></row><row><entry>0xB0</entry><entry>Preferred</entry><entry>Update the preferred system list with</entry></row><row><entry /><entry>System List</entry><entry>the following system IDs</entry></row><row><entry /><entry>Update</entry></row><row><entry>0xC0</entry><entry>CUG Message</entry><entry>Cancels a previously sent CUG message</entry></row><row><entry /><entry>Cancel</entry></row><row><entry>0xC1</entry><entry>CUG Update</entry><entry>If the alert device's serial number is</entry></row><row><entry /><entry /><entry>contained in the following list, update the</entry></row><row><entry /><entry /><entry>CUG information to include the alert</entry></row><row><entry /><entry /><entry>device's receiver in the specified CUG</entry></row><row><entry>0xC2</entry><entry>Remove CUG</entry><entry>If the alert device's serial number is</entry></row><row><entry /><entry /><entry>contained in the following list of serial</entry></row><row><entry /><entry /><entry>numbers, the CUG indicated in this</entry></row><row><entry /><entry /><entry>message should be removed from the alert</entry></row><row><entry /><entry /><entry>device's list of CUGs</entry></row><row><entry>0xC8</entry><entry>CUG Message</entry><entry>The message contained in this trans-</entry></row><row><entry /><entry /><entry>mission should only be displayed on</entry></row><row><entry /><entry /><entry>alert devices containing the CUG</entry></row><row><entry /><entry /><entry>specified by the message.</entry></row><row><entry>0xCA</entry><entry>Cancel Global</entry><entry>If this message is received by an EARs</entry></row><row><entry /><entry>CUG</entry><entry>device which CUG contains the CUG</entry></row><row><entry /><entry /><entry>specified by the message, the EARs</entry></row><row><entry /><entry /><entry>device should remove the CUG from it's</entry></row><row><entry /><entry /><entry>list.</entry></row><row><entry>0xF0</entry><entry>ESN Specific</entry><entry>Only the alert device with the listed</entry></row><row><entry /><entry>Message</entry><entry>ESN should act upon this message.</entry></row><row><entry>0xFA</entry><entry>Additional</entry><entry>This Alert Level is used to indicate</entry></row><row><entry /><entry>opcode</entry><entry>that the first byte of the message is</entry></row><row><entry /><entry>contained in</entry><entry>actually an opcode that is to be used for</entry></row><row><entry /><entry>message fields</entry><entry>further message processing. This is being</entry></row><row><entry /><entry /><entry>done as a mechanism to include additional</entry></row><row><entry /><entry /><entry>functionality that is not being considered</entry></row><row><entry /><entry /><entry>at this time.</entry></row><row><entry>0xFB</entry><entry>Reserved</entry><entry>These bits are reserved for future use</entry></row><row><entry>0xFC</entry><entry>Reserved</entry><entry>These bits are reserved for future use</entry></row><row><entry>0xFD</entry><entry>Reserved</entry><entry>These bits are reserved for future use</entry></row><row><entry>0xFE</entry><entry>Reserved</entry><entry>These bits are reserved for future use</entry></row><row><entry>0xFF</entry><entry>Reserved</entry><entry>These bits are reserved for future use</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>
[0109] The current level of provisioning is stored within the alert device <b>20</b>. The alert device <b>20</b> will react to alert messages in a manner dependent upon the provisioning level. The provisioning level can be set at the time of manufacturer and can be updated over the air during operation by a cell broadcast message. The oceodes in Table 1 provide one embodiment for updating the provisioning level over the air.
[0110] The present invention also operates to provide remote provisioning of custom stand by messages. In one embodiment of this aspect of the invention, a special opcode can be used to indicate that a certain number of subsequent messages will contain a custom message to be loaded into the device and an alert level or event to which the device should be associated with. Thus, the alert device <b>20</b> can receive custom standby messages over the air. These standby messages can be stored in the memory of the alert device <b>20</b> for subsequent use. In another embodiment, the alert device can be programmed at the factory with a variety of additional messages, with only a subset of these messages being enabled. Subsequently, messages can be sent to the alert device <b>20</b> to enable and disable certain messages. In another embodiment, the alert device <b>20</b> can be programmed with a vocabulary. During operation, messages that identify certain words from the vocabulary can be sent to the alert device <b>20</b> to create custom standby messages.
[0111] The present invention also operates to provide the ability to signal an external device such as mattress shaker. In one embodiment of the invention, this capability is provided by an output signal from the alert device <b>20</b> that can be used to control the operation of an external device. The external device can include type of external alerting device, or some other external device that can be controlled to provide alert signaling or perform other tasks. One such device can be a vibrator that is either embedded within a mattress or place underneath the mattress. When the appropriate level of alarm is received, the external device can be actuated. In this example, the mattress of a bed can be caused to vibrate, thereby alerting a sleeping user.
[0112] The present invention also operates to provide ability to send messages to a single device (for troubleshooting purposes). In one embodiment, this accomplished by sending a message that is intended only for a specific alert device <b>20</b>. Each alert device <b>20</b> has a unique serial number (i.e., an electronic serial number or ESN). Using the <b>0</b>xF<b>0</b> opcode listed in Table 1, a message can be sent to a specific an alert device <b>20</b> having a specific serial number. Thus, all alert devices <b>20</b> that do not have that serial number, which incidentally will be all of the rest of the alert devices <b>20</b>, will not react to the message. Using this technique, specific alert messages can be sent to an alert device <b>20</b> to test the operation of the alert device <b>20</b>.
[0113] The present invention also operates to provide the ability to activate a backlight by pushing a standby button. Thus, if a user needs to view what is presently being displayed on the alert device <b>20</b>, the user can simply actuate the standby button to turn on the backlighting.
[0114] The present invention also operates to provide a standby button to cause a message to scroll back at top of list. Thus, if more text that what can be displayed on the alert device <b>20</b> is available, a user can actuate the standby button to allow the message to be redisplayed and thus, the user can view the available text.
[0115] The present invention also operates to provide the ability to display multiple messages, in order of priority and time received. If multiple messages have been received by the alert device <b>20</b>, in one embodiment, the alert device <b>20</b> can display the messages based on various factors, including but not limited to the priority of the message, the time the message was received, the appropriateness of the message, etc.
[0116] Whereas the invention has been described in detail with particular reference to its most preferred embodiments, it is understood that variations and modifications can be effected within the spirit and scope of the invention, as described herein before and as defined in the appended claims. The corresponding structures, materials, acts, and equivalents of all means or step plus function elements, if any, in the claims below are intended to include any structure, material, or acts for performing the functions in combination with other claim elements as specifically claimed.
Contents6
17 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| WO2009116796A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2011045796A1 | Cited by | United States of America | Pre-grant |
| US7358855B1 | Cited by | United States of America | Applicant |
| US2009251315A1 | Cited by | United States of America | Pre-grant |
| US9369295B2 | Cited by | United States of America | Applicant |
| KR101540481B1 | Cited by | Republic of Korea | Search report |
| US8712056B2 | Cited by | United States of America | Applicant |
| US9221385B2 | Cited by | United States of America | Applicant |
| US11202961B2 | Cited by | United States of America | Applicant |
| CN102698715A | Cited by | China | Search report |
| US9639233B2 | Cited by | United States of America | Applicant |
| US8204525B2 | Cited by | United States of America | Applicant |
| US9054817B2 | Cited by | United States of America | Search report |
| US8744419B2 | Cited by | United States of America | Applicant |
| US2011081973A1 | Cited by | United States of America | Pre-grant |
| US11170623B2 | Cited by | United States of America | Search report |
| US2007208765A1 | Cited by | United States of America | Pre-grant |
| US2007018822A1 | Cited by | United States of America | Pre-grant |
| EP1938629A1 | Cited by | European Patent Office (EPO) | Examiner |
| US9874993B2 | Cited by | United States of America | Applicant |
| US9264863B2 | Cited by | United States of America | Applicant |
| US9071451B2 | Cited by | United States of America | Applicant |
| EP2093909B1 | Cited by | European Patent Office (EPO) | Examiner |
| US2011028121A1 | Cited by | United States of America | Pre-grant |
| US2005027449A1 | Cited by | United States of America | Pre-grant |
| US10016684B2 | Cited by | United States of America | Applicant |
| US2007135108A1 | Cited by | United States of America | Pre-grant |
| WO2009116798A2 | Cited by | World Intellectual Property Organization (WIPO) | Search report |
| US8018333B2 | Cited by | United States of America | Applicant |
| WO2009116796A2 | Cited by | World Intellectual Property Organization (WIPO) | Search report |
| US2009175223A1 | Cited by | United States of America | Pre-grant |
| US8483652B2 | Cited by | United States of America | Search report |
| EP2093909A1 | Cited by | European Patent Office (EPO) | Examiner |
| US2006242652A1 | Cited by | United States of America | Pre-grant |
| US2014218204A1 | Cited by | United States of America | Pre-grant |
| US8917176B2 | Cited by | United States of America | Search report |
| EP3120339B1 | Cited by | European Patent Office (EPO) | Examiner |
| US9656165B2 | Cited by | United States of America | Applicant |
| US9698996B2 | Cited by | United States of America | Applicant |
| US8702506B2 | Cited by | United States of America | Applicant |
| US2013244564A1 | Cited by | United States of America | Pre-grant |
| US9210589B2 | Cited by | United States of America | Applicant |
| US9794860B2 | Cited by | United States of America | Applicant |
| US9973881B2 | Cited by | United States of America | Applicant |
| US2007041036A1 | Cited by | United States of America | Pre-grant |
| US8218463B2 | Cited by | United States of America | Applicant |
| US7725256B2 | Cited by | United States of America | Search report |
| US10462727B2 | Cited by | United States of America | Applicant |
| US8725061B2 | Cited by | United States of America | Search report |
| US8890707B2 | Cited by | United States of America | Applicant |
| WO2009116795A2 | Cited by | World Intellectual Property Organization (WIPO) | Search report |
| US10158970B2 | Cited by | United States of America | Applicant |
| US2011105151A1 | Cited by | United States of America | Pre-grant |
| US8890708B2 | Cited by | United States of America | Search report |
| US10075893B2 | Cited by | United States of America | Applicant |
| US9788329B2 | Cited by | United States of America | Applicant |
| US9161158B2 | Cited by | United States of America | Applicant |
| US2007244981A1 | Cited by | United States of America | Pre-grant |
| US9060335B2 | Cited by | United States of America | Applicant |
| US9660745B2 | Cited by | United States of America | Applicant |
| CN104043409A | Cited by | China | Search report |
| US9730016B2 | Cited by | United States of America | Search report |
| US9319842B2 | Cited by | United States of America | Applicant |
| US8751159B2 | Cited by | United States of America | Applicant |
| US10279261B2 | Cited by | United States of America | Applicant |
| US9118428B2 | Cited by | United States of America | Applicant |
| US2011207394A1 | Cited by | United States of America | Pre-grant |
| US8948721B2 | Cited by | United States of America | Search report |
| US2011181408A1 | Cited by | United States of America | Pre-grant |
| US2007226678A1 | Cited by | United States of America | Pre-grant |
| US7405668B2 | Cited by | United States of America | Search report |
| US2008055097A1 | Cited by | United States of America | Pre-grant |
| US2011169634A1 | Cited by | United States of America | Pre-grant |
| US2011103302A1 | Cited by | United States of America | Pre-grant |
| US8229390B2 | Cited by | United States of America | Applicant |
| US2010067451A1 | Cited by | United States of America | Pre-grant |
| CN101978712A | Cited by | China | Search report |
| US9632768B2 | Cited by | United States of America | Applicant |
| US8355410B2 | Cited by | United States of America | Applicant |
| US9607503B1 | Cited by | United States of America | Search report |
| US8385956B2 | Cited by | United States of America | Applicant |
| US10511393B2 | Cited by | United States of America | Applicant |
| US8515385B2 | Cited by | United States of America | Applicant |
| US8825097B2 | Cited by | United States of America | Applicant |
| US8777752B2 | Cited by | United States of America | Applicant |
| WO2007046800A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9930508B2 | Cited by | United States of America | Applicant |
| US8483616B1 | Cited by | United States of America | Applicant |
| US9992021B1 | Cited by | United States of America | Applicant |
| US10275111B2 | Cited by | United States of America | Applicant |
| US9544922B2 | Cited by | United States of America | Applicant |
| US8821293B2 | Cited by | United States of America | Applicant |
| US2012319860A1 | Cited by | United States of America | Pre-grant |
| US10558317B2 | Cited by | United States of America | Applicant |
| US8706076B2 | Cited by | United States of America | Search report |
| US8730010B2 | Cited by | United States of America | Applicant |
| US9895604B2 | Cited by | United States of America | Applicant |
| WO2009116795A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2007124395A1 | Cited by | United States of America | Pre-grant |
| CN104506266A | Cited by | China | Search report |
30 members in 9 offices
Priority claims8
| Document | Office | Kind | Date |
|---|---|---|---|
| 33066799 | United States of America | A | |
| 1630701 | United States of America | A | |
| 44928403 | United States of America | A | |
| 09330667 | – | – | – |
| 10016307 | – | – | – |
| US19990330667 | – | – | – |
| US20010016307 | – | – | – |
| US20030449284 | – | – | – |
Members30
| Document | Office | Kind | |
|---|---|---|---|
| CA2376773A1 | Canada | A1 | |
| WO0077755A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU6285099A | Australia | A | |
| US6329904B1 | United States of America | B1 | |
| EP1192612A1 | European Patent Office (EPO) | A1 | |
| MXPA01012915A | Mexico | A | |
| US6617964B1 | United States of America | B1 | |
| US2003193394A1 | United States of America | A1 | |
| EP1192612A4 | European Patent Office (EPO) | A4 | |
| US6867688B2 | United States of America | B2 | |
| US2005237183A1 | United States of America | A1 | |
| EP1746551A2 | European Patent Office (EPO) | A2 | |
| EP1746551A3 | European Patent Office (EPO) | A3 | |
| EP1192612B1 | European Patent Office (EPO) | B1 | |
| AT362155T | Austria | T | |
| DE69936070D1 | Germany | D1 | |
| DE69936070T2 | Germany | T2 | |
| US7339467B2 | United States of America | B2 | |
| US2009058665A1 | United States of America | A1 | |
| EP1746551B1 | European Patent Office (EPO) | B1 | |
| AT425526T | Austria | T | |
| DE69940578D1 | Germany | D1 | |
| EP1746551B8 | European Patent Office (EPO) | B8 | |
| EP2065861A1 | European Patent Office (EPO) | A1 | |
| ES2322912T3 | Spain | T3 | |
| CA2376773C | Canada | C | |
| US7872573B2 | United States of America | B2 | |
| EP2287816A1 | European Patent Office (EPO) | A1 | |
| EP2065861B1 | European Patent Office (EPO) | B1 | |
| AT531013T | Austria | T |
7 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Fee payment procedurePAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 2003193394
- Publication, EPODOC
- US2003193394
- Application
- 10449284
- Application, DOCDB
- 44928403
- Application, EPODOC
- US20030449284
Titles
- English
- Apparatus and method for providing weather and other alerts
Classification
- CPC, 2
- G08B27/006
- G01W1/00
- IPC, 2
- G01W1 00
- G08B27 00
- USPC, 2
- 340539280
- 340539100