Service escrowed transportable wireless event reporting system

- Numerex Corp.

A portable service escrowed event reporting system that may be sold through mass-market sales channels. Communications between a consumer and the provider of the event reporting system are not required in advance of the system being purchased by the consumer. After purchase of the system by the consumer, the system may be initialized. The service may have a finite amount of service associated with it when it is purchased. The consumer may choose to have the system report the occurrence of reportable events directly to them over a wireless network.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
PRIORITY APPLICATION

This application is a divisional of U.S. Non-provisional patent application Ser. No. 13/568,559, now U.S. Pat. No. 8,543,097, entitled “Service Escrowed Transportable Wireless Event Reporting System,” filed Aug. 7, 2012, which is a continuation of U.S. Non-provisional patent application Ser. No. 12/012,848, now U.S. Pat. No. 8,265,605, entitled “Service Escrowed Transportable Wireless Event Reporting System,” filed Feb. 6, 2008; which claims priority to U.S. Provisional Patent Application No. 60/899,780, filed on Feb. 6, 2007. The entire contents of each of the above priority documents are hereby incorporated herein by reference.

FIELD OF THE INVENTION

The present invention generally relates to a wireless event reporting system for home, office, or a temporary location that is suitable for mass-market distribution and configured for transport to different installation sites.

BACKGROUND OF THE INVENTION

Conventional event reporting systems are typically permanently fixed to a location, installed by a service company, and monitored over telephone or data communications services. These systems may have sensors or detectors permanently installed to detect reportable events, such as intrusion or environmental conditions, which preclude the system from being easily removed and used at another location. Further, conventional event reporting systems are typically limited to reporting reportable events to a service company (i.e., a monitoring agency) using fixed communications services, such as landline telephone service, Internet, or derived data channels. Therefore, as is usually the case, the consumer of the event reporting system may only receive a notice of reportable events if someone at the monitoring service company acts to contact the consumer. Accordingly, in conventional reporting and monitoring systems, the consumer does not have the option of having the reportable events reported directly to them by the event reporting system.

Further, because conventional event reporting systems are typically installed and monitored by a service company, consumers typically must agree to a service contract or otherwise communicate with the monitoring service company prior to the installation of the event reporting systems. For example, it is not uncommon for a consumer to schedule an “installation” time with the service company and/or make advance payment for monitoring services. Thus, with conventional event reporting systems, the consumer is required at some point of time to disclose his or her identity to the service company.

Additionally, as noted, conventional event reporting systems are installed by a service company, typically by using service technicians. This adds additional cost to the event reporting system and, once permanently installed, keeps the event reporting system from being easily moved to another location by the consumer. Because of this, the consumer may be reluctant to use a conventional event reporting system. For example, installation costs and other costs of the event reporting system may be cost prohibitive for some consumers. Additionally, if a consumer would like to monitor the security or environment of a space temporarily, they may not want to expend time or money on a permanent alarm system. In these instances, conventional event monitoring systems do not provide a viable option to meet consumers' demands. Accordingly, there currently exists a need in the art for a widely-available, service escrowed portable monitoring system that a consumer may conveniently purchase and install anywhere he or she chooses.

SUMMARY OF THE INVENTION

The portable monitoring system described herein may be sold and purchased through widely-available, mass-market channels. For example, the system may be sold in a blister-pack-type package at a retail outlet for purchase by consumers. The consumer may install the system in any location, including, but not limited to, a home, office, vehicle, or motel room. Unlike conventional systems, no communication between the consumer and the provider of the event monitoring service are required to use the system. Further, since the device may be purchased with escrowed service, no billing arrangements or contracts with a service provider are necessary.

After selecting the portable system, the consumer may proceed to setup the event reporting system in any location. The event reporting system may comprise a microprocessor based controller (hereafter referred to as “controller”) with short range wireless communications capability for communicating with wireless sensors and long range wireless communications capability, such as audio and data over cellular telephony. The event reporting system also comprises one or more event detectors for monitoring security intrusions or other environmental events (e.g., fire, carbon monoxide, etc). The event detectors can communicate detected reportable events via short range wireless capabilities or wired communication paths. Events that may be detected by a detector may be referred to hereinafter broadly as “reportable events.” The event reporting system may also comprise one or more human interfaces, such as an LCD screen or speaker for conveying information to the consumer, primarily during installation, and a keypad or microphone for conveying information from the consumer to the controller. Additionally, the event reporting system may comprise a human interface for conveying information to or from the consumer via a telecommunication path by tomes, email, data packets, or speech recognition and synthesis.

Once the event reporting system has been set up, the consumer may initialize and event monitoring service through the controller. For example, upon powering up, the controller may contact a remote monitoring station or other third-party host server over a wireless network. The controller may convey its identity to the remote monitoring station so that the escrowed service pre-associated with that identity may be activated for time, data volume, or both. The remote monitoring station may request information from the consumer, including, but not limited to, an identification for processing remote commands received from the consumer (e.g., a code that may be found with the packaging for the system or created by the system) and information for directly reporting reportable events to the consumer (e.g., a mobile device number). Also, the remote monitoring station may request information from the consumer to identify how the consumer desires to receive reportable event information, for example, a telephone number to be called for synthesized voice reporting or an email address for reporting event information as text.

After initialization, the event reporting system may detect, through the use of the sensors and detectors, the occurrence of any reportable event. If an event is detected, the event reporting system may contact the consumer directly or forward information to the remote monitoring station. If the consumer is contacted directly by the event reporting system, the message may be sent to the consumer via a wireless network in the form of a Short Message Service (“SMS”) or data connection over commercially available wireless communication service's data channels, including but not limited, to General Packet Radio Service (“GPRS”), 1XRTT, 1XEV-DO, 1XMC, 3XMC or WCDMA. Further, if an event is reported to the remote monitoring station, it may subsequently be forwarded to the consumer using one or more of the aforementioned commercially available wireless data services.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a functional block diagram of an operating environment for a portable event reporting system, according to an exemplary embodiment of the present invention.

FIG. 2 illustrates a logic flow diagram for using the portable event reporting system, according to an exemplary embodiment of the present invention.

FIG. 3 illustrates a logic flow diagram for initializing and using the portable event monitoring system, according to an exemplary embodiment of the present invention.

FIG. 4 illustrates a logic flow diagram for using the portable event reporting system to detect and report reportable events, according to an exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The inventive system comprises a transportable, wireless system that may be used at any location chosen by a consumer, including, but not limited to, a consumer's home, office, or temporary location. An exemplary embodiment of the present invention is designed for commercial distribution and may be sold through mass-market sales channels in appropriate packaging, such as in a blister-pack where the system can be seen by prospective consumers. Mass market sales channels may include, but are not limited to, supermarkets, convenience stores, and superstores.

The system, in one exemplary embodiment, may comprise a disposable controller. Further, the system may provide escrow event reporting (i.e., pre-paid event reporting services). One advantage of the escrowed event reporting system over conventional systems is that it does not require communications with a service provider prior to purchase; that is, the consumer may purchase the portable event reporting system without communicating with the provider to set up a billing identity or provide other identifying information. Furthermore, because the system is capable of being compact in size, wireless, and easy to install, a consumer may move the system to different locations, unlike the permanent setup associated with conventional systems.

As noted above, the portable event reporting system does not require that a billing identity be established for the consumer. According to an exemplary embodiment, the transportable service escrowed event reporting system connects to a remote server, such as a remote monitoring station, when the product is powered on for the first time. By doing so, the remote monitoring station determines and activates the escrowed service for the system. Additionally, the escrowed service may be activated by the consumer entering a device identity, such as the International Mobile Equipment Identity (IMEI), a number unique to every GSM and UMTS wireless telephone, or Electronic Serial Number or MEID of CDMA and other wireless networks, by using a keypad and/or liquid crystal display (“LCD”) located on a controller of the system, or via speech recognition and voice synthesis using a microphone and speaker in the controller. Alternatively or additionally, the consumer may convey the system identity to activate the escrowed service by placing a telephone call to a remote host server capable of interacting through voice prompts or DTMF tones. For example, in one exemplary embodiment, the consumer may be provided the option of calling a 1-800 number that connects to a remote monitoring station to initialize the event reporting system after it has been purchased.

Because the event reporting system is designed to be portable, in an exemplary embodiment, all communications within the monitored premises, as well as the remote delivery of alarms, can be performed via wireless communications. For instance, in an exemplary embodiment, the controller may receive notice of reportable events through short range wireless event detectors, including, but not limited to, door/window opening detectors, glass breakage detectors, motion detectors, temperature detectors, and smoke detectors. These sensors and detectors may be implemented using industry-standard, short-range, wireless sensors. Wireless sensors typically communicate over a radio-frequency spectrum, such as those utilized by IEEE standards 802.14.4, 802.11 or 802.15.1, and do not utilize cellular telecommunications services; however, the controller and detectors may use any wired or wireless protocol to communicate, including any other short-range wireless communications known to one of ordinary skill in the art.

Upon the detection of a reportable event, the event reporting system may report the event either “direct” to the consumer or through an intermediary, such as a remote monitoring station. In an exemplary embodiment, direct alarm reporting can be implemented by a direct communication path to the consumer using a “controller to consumer” approach. For example, a reportable event can be communicated directly to the consumer through any one of several mediums including, but not limited to, email conveyed from the controller by via wireless telephone-based Short Messaging Service (SMS) or data connection protocols, such as email, and over commercially available wireless communication service's data channels, including but not limited to 1XRTT, 1XEV-DO, 1XMC, 3XMC or WCDMA or General Packet Radio Services (GPRS). Such messages are typically presented to the consumer on their cellular telephone screen, pager, personal digital assistant (“PDA”), or personal computer. Alternatively, direct alarm reporting can be achieved in the form of speech, where alarm information is converted into audio synthesized speech and conveyed from the controller to a consumer's predefined telephone number in the form of spoken words.

As mentioned above, alarm reporting may also be accomplished through an intermediary using the event monitoring system. In an exemplary embodiment, this intermediary may be the remote monitoring station, and the controller of the event reporting system may contact the remote monitoring station using alarm-industry, standard tone sequences within the audio channel of wireless telephony, or via data representations of either alarm industry data formats or proprietary protocols conveyed by the SMS or data channels of wireless telephony, such as described above.

The transportable service escrowed event reporting system may be configured when it is first turned on or subsequent thereto. Configuration of the system may be accomplished via an LCD screen and/or keypad located on the controller. Alternatively or additionally, configuration may occur by the consumer dialing a 1-800 number to provide information to the remote monitoring station, which may in turn provide pertinent information (e.g., a telephone number for reporting reportable events) to the controller through a network (as discussed below). Additionally, system reconfiguration may be accomplished via data messages conveyed from the consumer's wireless telephone in the form of SMS or other data messages, which may be carried by the data channels of the serving cellular system. Also, reconfiguration may be accomplished by calling a 1-800 number to access the remote monitoring station.

When configuration is accomplished remotely, it may be important to authenticate the consumer. Accordingly, in one exemplary embodiment, authentication of the consumer's identity can be accomplished by the system's recognition of the consumer's calling line ID (CLID), which may be previously registered through functions of the configuration LCD screen and keypad located on the controller or provided to the remote monitoring station. Thus, in order to authenticate the consumer, the consumer may be required when configuring the system to enter an identification that can be used to authenticate his or her identity or mobile device. This identification may comprise an identity for the event reporting system or another unique identification, such as a personal identification number (“PIN”) selected by the consumer.

Alternatively or additionally, system configuration and/or reconfiguration can be accomplished via data messages conveyed in the audio channel of the consumer's wireless telephone via DTMF tone sequences from the consumer's telephone. Similarly, system configuration/reconfiguration may be accomplished via speech recognition of words spoken by the consumer and conveyed from the consumer's cellular telephone over the voice channel of a telephone service. For example, a consumer may connect to the controller through a wireless network and speak a pass-code previously registered with the system in order to re-configure the system.

Turning to the several figures, in which like reference numerals represent like elements, FIG. 1 illustrates a representative operating environment of the transportable service escrowed event reporting system 100, according to an exemplary embodiment. As illustrated, the transportable service escrowed event reporting system 100 may comprise a microprocessor enabled controller 105 (which may or may not be disposable) and one or more event detectors 110a-c. The event detectors 110a-c may comprise any industry-standard, short-range wireless security or environmental sensors, such as, but not limited to, door/window opening detectors, glass breakage detectors, and motion detectors. According to an exemplary embodiment, the controller 105 and detectors 110a-c may be sold in any packaging suitable for mass-market distribution. One such packaging may be blister-type packaging, which may comprise a plastic packaging material surrounding the portable event reporting system 100. When packaged this way, the system 100 can be sold through mass-market sales channels, including, but not limited to, supermarkets, superstore, or via the Internet. This wide-spread availability of the portable event reporting system 100 is possible because, unlike conventional systems, service and billing information for the portable event reporting system 100 is not required prior to a consumer purchasing and installing the system 100 in his or her home or office (if at all).

As further illustrated in FIG. 1, the portable event reporting system 100 may connect to a remote monitoring station 125 over a network 115. In an exemplary embodiment, the network 115 may comprise any wireless data network, whereby messages may be exchanged using SMS and/or connection based protocols using commercially available wireless data connection capability such as that offered by GPRS or 1XRTT and their derivatives. The remote monitoring station 125 may comprise a third-party, who may or may not manufacture and provide the portable event reporting system 100 to the consumer.

In an exemplary embodiment, the portable event reporting system 100 contacts the remote monitoring station 125 automatically over the network 115 when it is powered on for the first time by the consumer. This may be done through a transceiver connected to or incorporated within the controller 105, and may allow alarm device 105 to establish an operational identity (if not pre-assigned to the device, as discussed below), such as an EMSI, Electronic Serial Number, or MEID, and also allows the consumer the opportunity to configure the portable event reporting system 100 and enter notification preferences for use with the system 100.

Connection through the network 115 may occur by using an identity pre-assigned to the controller 105. For example, an identity for a wireless provider may be assigned to the controller 105 during its manufacture. In this way, the controller 105 may automatically connect to the network 115 when it is first powered on by the consumer. Alternatively, however, the controller 105 may be provided an identity after it is powered on. In this exemplary embodiment, the consumer may call a number found on the product packaging for the controller 105 or system 100 to connect to a remote monitoring station (e.g., dialing a 1-800 number). The remote monitoring station 125 may then request that the consumer enter a unique identification for the device, such as the device's IMEI number, if GSM, or Electronic Serial Number or MEID if CDMA or other wireless technology, for initializing the controller 105.

After the identification has been entered, the remote monitoring station 125 may send a message to the controller via SMS or connection based wireless data communication 105 over the network 115, in which case the controller 105 may respond with information in order to establish the operational identity for the controller 105.

Further still, the controller 105 may be assigned a generic identity (i.e., an identity used for a group of controllers sold through mass-market sales channels) for use at its initial power up. In this exemplary embodiment, the controller may establish an operational identity by contacting the remote monitoring station 125 upon power-up using the generic identity. Following this contact, the remote monitoring station 125 may assign a different, unique operational identity to the controller 105 for any future communication between the controller 105 and the remote monitoring station 125.

Once the operational identity for the controller 105 has been determined, the system 100 may provide a wireless device unique identity number, such as the IMEI of a GSM device, or Electronic Serial Number or MEID if CDMA or other wireless technology, automatically to the remote monitoring station 125 to ensure the device is identified properly. Alternatively, as discussed above, the consumer may provide this information to the remote monitoring station 125 via a 1-800 number.

Further, the remote monitoring station 125 may prompt the consumer for information. This prompt may be sent over the network to the controller 105 or the prompt may be performed through the use of a 1-800 number the consumer uses to configure the system 100. In either case, the remote monitoring station 125 may request contact information specifying where reportable events should be reported. For example, the remote monitoring station 125 may request the consumer to “specify a number to call when a fire is detected” or “specify a number to call when a burglary is detected.” In one exemplary embodiment, the controller 105 may comprise a LCD screen and keypad that allows the consumer to configure and enter information into the portable event reporting system 100. Thus, using these components, the consumer may enter an identification that will allow him or her to communicate with the controller 105 remotely. This identification may comprise a pass-code, a mobile number through which calling line ID (“CLID”) can be checked, or another unique identifier. This pass-code may allow the consumer to validate himself or herself when remotely connecting to the system 100. For example, if a consumer wishes to re-configure the system 100, he or she may call the system 100 with a mobile device. The system 100 may have stored the number for the mobile device previously entered into the system 100 using the controller 105 keypad. In this way, the system 100 will recognize the CLID number for the mobile device and allow the consumer to change the configuration of the system 100 via data messages conveyed from the consumer's cellular telephone, such as through SMS messages or email via wireless channelized data communications such as GPRS or 1XRTT and their derivatives. Alternatively or additionally, when the consumer calls the portable system, he or she may speak or enter the pass-code or other identification information previously stored to use the system 100. This pass code may also comprise the identity of the one or more mobile devices that the consumer may authorize to re-configure the system 100.

In an exemplary embodiment, the transportable service escrowed event reporting system 100 may communicate with a consumer mobile device 120 over the network 115. Thus, when the consumer initializes the reporting service, the consumer may also be prompted by the controller 105 to enter a mobile number to contact the consumer when directly reporting reportable events. This way, when the system 100 is in a direct report mode, if the controller 105 receives a signal from one of the detectors 110 attached to it, it may automatically send a message to the consumer mobile device 120 over the network 115 using the number provided by the consumer.

Turning to FIG. 2, because the portable event reporting system 100 may be sold and marketed through mass-market channels, a consumer may simply visit a store and purchase a “kit” comprising the portable event reporting system 100, take the kit to the desired location, install it, and initialize the system. FIG. 2 illustrates an exemplary method for setting up the transportable service escrowed event reporting system 100. The process begins at step 205, where a consumer visits a store and purchases the transportable service escrowed event reporting system 100. For example, the consumer can buy the system 100 at a retail outlet, where the system may be packaged in a blister pack that houses all items required to support the consumer's alarm service. Further, according to an exemplary embodiment, the consumer may purchase the system 100 pre-packaged with communication services (i.e., pre-paid time or usage over a wireless network) that will support the controller's 105 initial set-up and basic operations. Further, new services may be acquired at a later date based on new purchases. For example, according to an exemplary embodiment, a tiered service level offering can be provided to the consumer. Basic service may cover set-up and a pre-set number of alarm event communications; advanced service may cover maintenance (in the form of a periodic testing of the radio messaging system by the remote monitoring station 125) and a pre-set number of alarm event communications; and premium service may cover regular tests of the radio messaging system (e.g., daily or every pre-set number of days) in combination with a pre-set number of alarm event communications. Each of these services would be sold with their own escrowed service (i.e., prepaid event reporting) and would require activation in a manner similar to that of the basic system in order to enable such advanced features.

As mentioned above, the portable event reporting system 100 may comprise a radio transceiver or transmitter (not illustrated) for communicating with the network 115. This radio transceiver or transmitter may be integrated within the controller or, in alternative embodiments, may be physically separate from, but connected to, the controller. For example, in one exemplary embodiment, the controller 105 may not have a transceiver, but instead may be tethered or ported with a consumer's mobile device to communicate over the network 115. In either embodiment, a transceiver may—upon system power-up by a consumer—initiate an automated configuration process with the server or remote monitoring station 125 to identify the system 100 and/or controller 105. Specifically, as discussed, the radio transceiver may forward its pre-assigned operational identity to the remote monitoring station 125 over the network 115 or it may receive an operational identity in response to a message sent by the remote monitoring station 125. For example, as mentioned, the remote monitoring station 125 may forward an operational identity to the controller 105 based on the consumer's interaction with a 1-800 telephone service related to the remote monitoring station 125. Further, the consumer may be allowed to reconfigure the radio and the alarm service through subsequent interactions with a 1-800 telephone service related to the remote monitoring station 125.

The system 100 may come pre-packaged with a certain number of event detectors 110. At step 210, the consumer installs the detectors 110 in appropriate places. As discussed, the detectors may comprise standard wireless detectors as known by one of ordinary skill in the art.

After the detectors are installed, the transportable service escrowed event reporting system 100 may be initialized at step 215. In an exemplary process, this initialization occurs when the controller 105 is turned on for the first time and the portable event reporting system 100 connects to the remote monitoring station 125 through the network 115 and establishes an operational identity (as previously discussed). According to an exemplary embodiment, the system 100 may be turned on by the consumer pulling a battery tab or by pressing a power button on the controller 105. The controller then automatically goes through the process of connecting to the remote monitoring station 110 (if already supplied an identity) or awaits a message from the remote monitoring station 110 (if not already supplied an identity).

After initialization, the system 100 may inform the consumer as to the communication status of the device (e.g., through a sound or blinking light indicating that the unit has properly connected to the remote monitoring station 125). Then, if so equipped, the consumer may be prompted by an LCD display on the controller 105 to enter information to configure the event reporting system at step 220. During this step, according to an exemplary embodiment, the event reporting system 100 may request that the consumer enter contact information into a keypad attached to the controller 105 in order to use the features of the system 100. Contact information may comprise, for example, a telephone number or email address for the consumer. The controller 105 may, in turn, forward the information collected from the consumer to the remote monitoring station 125. Additionally, certain information may be stored in memory connected to the controller 105. For example, a consumer may enter a preference for receiving reportable information by entering his or her telephone number. The controller may store that number locally so that it can route a message to the consumer relaying the occurrence of a reportable event over the network 115.

Alternatively or in addition to the above, the controller 105 may prompt the consumer (using an on-device display screen, voice prompt, or through packaging material) to configure the radio for reporting events by interacting with a 1-800 telephone service. In particular, the consumer may enter data via the 1-800 telephone to configure the system 100 to communicate event data to the consumer in a preferred format, such as via email to a designated email address or by phone to a mobile or landline phone number. For example, as described above, during the initial configuration of the system 100, a voice or display prompt on the controller 105 can prompt the consumer to enter the radio's serial number, which is known to be associated with a unique identifier assigned to the radio.

In addition to the above, the consumer may also be prompted to enter an identification at step 220 so that the consumer can control the controller remotely. For instance, the consumer may enter a CLID identifying his or her mobile device so that messages from that mobile device number can be used to control the portable event reporting system 100. For instance, the system 100 can perform authentication of the consumer's identity by recognition of the CLID of the consumer's mobile telephone. However, in the alternative, the portable event reporting system 100 can perform authentication of the consumer's identity by interpreting data messages conveyed from the consumer's cellular telephone via DTMF tone sequences over the voice channel of the serving cellular system. Further, in yet another embodiment, the portable event reporting system 100 can perform authentication of the consumer's identity by speech recognition of words spoken by the consumer and conveyed by the telephone. The consumer's spoken words may, for example, constitute a pass-code ID previously registered by the consumer using the controller 105.

Another prompt can request for the consumer to enter his or her preferred contact mechanism (e.g., an e-mail address or telephone number) to be used for directly reporting the occurrence of a reportable event. Upon completion of date entry by the consumer, the controller 105 can initiate communications diagnostics and confirm the radio's ability to receive and transmit messages to a remote monitoring station 125. A prepaid data communications service can be provided at the outset of radio operations to facilitate the initial communications exchange (set-up operations) between the controller 105 and the remote monitoring station 125. In an exemplary embodiment, subsequent communications of reportable events can be supported by the consumer's purchase of additional prepaid wireless minutes or reporting credits (through the controller 105 or via a 1-800 number connecting to the remote monitoring station 125). Further, in another embodiment, the consumer may purchase the unit from a mass-market sales channel wherein the system 100 is capable of performing a finite number of communications (i.e., a certain amount of communication services used by the system 100 to report reportable events may be pre-paid when the system 100 is purchased by the consumer). It is noted that due to the service escrowed nature of the invention (i.e., it is capable of being a prepaid system), a monthly billing service relationship with the company related to the remote monitoring station 125 or provider of the portable event reporting system 100 is not required for operation of the radio or the alarm event service for a predetermined time or quantity of events. Thus, the portable event reporting system 100 offers the ability of a consumer to conveniently purchase a pre-paid event reporting system 100 that requires no information from the consumer prior to the purchase and use of the device (if at all).

The system 100 also provides the consumer the ability to select how he or she wishes to receive alerts, as illustrated at step 225. In one exemplary embodiment, the consumer may wish to receive direct reporting from the system 100. In that case, the system 100 will report the occurrence of reportable events through the wireless network 115 directly to the device specified by the consumer. Messages sent to notify the consumer of an occurrence of a reportable event may comprise any number of formats, including, but not limited to, text messages sent via SMS or connection based wireless data service such as GPRS or 1XRTT, such as e-mail sent over the wireless network. According to an exemplary embodiment, the specific format chosen for direct reporting may be specified by the consumer when configuring (or re-configuring) the system 100.

Instead of having reportable events reported directly, the consumer may alternatively choose to have the system 100 send report messages to a third-party intermediary. In an exemplary embodiment, this intermediary may comprise the remote monitoring station 125. Accordingly, if the consumer does not choose direct routing, then the system 100 will alert the remote monitoring station 125 or other third-party over the network 115 when it detects a reportable event. The remote monitoring station 125, in turn, may notify the consumer through any number of wireless formats including, but not limited to, SMS, connection based wireless data such as GPRS or 1XRTT, text-messaging, e-mail, or other medium specified by the consumer and within the capabilities of the transportable service escrowed event reporting system 100.

As discussed, the transportable service-escrowed event reporting system 100 may be sold by a company through mass-market channels without prior communications with the consumer. In an exemplary embodiment, the system 100 may come with a finite period of time that the product may be used to report reportable events. This length of time (or other finite usage of the system 100) may, optionally, be extended by the consumer purchasing additional time through the controller 105 or calling the remote monitoring station 125 via a 1-800 number. Additionally, in another exemplary embodiment, a consumer may extend the length of time the system 100 may be used to report reportable events by providing to the remote monitoring station 125 (through the controller or via a 1-800 number) information concerning one or more pre-paid usage cards, such as pre-paid cellular service cards. For example, according to one exemplary embodiment, a consumer may purchase a pre-paid cellular calling card (or pre-paid event reporting card) and enter the information for that card into the controller 105 to extend the capabilities of the system through cooperative business arrangements between the prepaid cellular service provider and the operator of the transportable service escrowed event reporting system 100. In this way, a consumer may purchase and use the event reporting system 100 without ever being required to establish a billing identity with the system 100 or the remote monitoring station 125.

FIG. 3 illustrates an exemplary process for initializing and using the portable event reporting system 100 through the use of a remote monitoring station 125. The process begins at step 305, where the remote monitoring station 125 receives an initialization command from the controller 105 of the event reporting system 100. In an exemplary embodiment, the remote monitoring station 125 must know the physical identity of the wireless event reporting system 100. In the GSM protocol, for example, this identity is known as the International Mobile Equipment Identity (“IMEI”), which is a unique identifier used for GSM and UMTS mobile network consumers. Thus, IMEI or another type of operational identity may be used as a unique address for the portable event reporting system for use on the network 115. The identity of the system 100 allows the remote monitoring station to detect the amount of pre-paid monitoring services the consumer is entitled to (if any) using the system. For example, certain portable systems 100 may be purchased with a finite amount of pre-paid reporting services. Therefore, when the identity of the system 100 is provided to the remote monitoring station 125, the remote monitoring station 125 may perform, at step 310, a look-up based on the identity to determine and transmit the amount of pre-paid reporting services to the system 100.

Further, once the remote monitoring station 125 receives an operational identity from the wireless event reporting system 100, in an exemplary embodiment, the remote monitoring station 125 can assign a sub-identifier to the controller 105 associated with the reporting wireless radio device (which may be a derivative of the operational identity). For example, upon initial power-up, the event reporting system 100 (through the use of a radio transmitter communicably attached to the controller 105) can transmit a message comprising the system's 100 IMEI to initiate the set-up process. This IMEI will be assigned to the portable event reporting system 100. The remote monitoring station 125 receives the IMEI and responds by assigning a telephone number to the radio associated with the IMEI. In an alternative embodiment, the remote monitoring station 125 can initiate the transmission of IMEI by the radio based on a consumer's entry of data in response to information provided by the consumer via a 1-800 telephone service.

Based on the receipt of this initialization, the remote monitoring station 125 establishes a connection with the system 100 over the network 115. Through this connection, information may be exchanged by the consumer and the remote monitoring station 125. For example, during initial configuration, the system 100 may prompt the consumer for information over the network 115. Information that may be pertinent to the event reporting system 100 includes, but is not limited to, the consumer's name and a mobile number where the consumer would like to receive messages related to reportable events. Thus, regardless of the information requested or sent to the remote monitoring station, in step 315, information may be provided to the remote monitoring station 125 directly through the system 100 (e.g., through interaction with the keypad and LCD on the controller 105). Alternatively, as discussed, a consumer may also provide information to the remote monitoring station 125 in step 315 via a telephone call to the host server of the remote monitoring station 125 or via an Internet website interaction (i.e., through the completion of a form at a web site).

Once the consumer has supplied information allowing the remote monitoring station 125 to activate a service escrowed account for the consumer, the remote monitoring station 125 may then monitor for communications from the portable event reporting system 100 at step 320. In this way, the remote monitoring station 125 may act as a monitoring center for reportable events. However, unlike conventional systems, the remote monitoring station will receive messages from the portable event reporting system 100 over a wireless network 115 and may forward messages to the consumer over the wireless network 115 based on the information provided by the consumer.

Turning to FIG. 4, an exemplary method for using the portable event reporting system 100 to detect and report reportable events is illustrated. The process begins at step 405, where one or more of the portable detectors 110 detects a reportable event. Upon detecting the event, the detector 110 sends a message, at step 410, to the controller 105 using a standard wireless protocol, e.g., via a radio-frequency channel. When the controller 105 receives the notice of the reportable event, it may choose, at step 415, how to alert the consumer. According to an exemplary embodiment, the system 100 may report the occurrence of an event to the consumer through either direct or intermediate reporting.

If the consumer has chosen a specific type of reporting, then the controller 105 proceeds as configured by the consumer. For example, if the consumer has chosen direct reporting, then the controller 105 follows step 420, by sending a message over the network 115 to the consumer's mobile device 120. However, if the consumer has chosen intermediate reporting, then the controller forwards the notice of the reportable event, at step 425, to the remote monitoring station 125 or other third-party host server. The remote monitoring station 125 may then contact the authorities, if necessary, or send a message to the consumer at step 430. According to an exemplary embodiment, the message from the remote monitoring station 125 may comprise an SMS or wireless data connection based messages, such as GPRS or 1XRTT and their derivatives.

In view of the foregoing, it will be understood that the present invention provides a portable event reporting system 100 suitable for marketing as a transportable service escrowed device for which no recurring billing identity is initially assigned to the product (if at all). The transportable service escrowed event reporting system can accomplish its initial communications through wireless interaction with a remote host server during initial power-up. In the alternative, the portable event reporting system 100 can accomplish its initial communications identity via automatic configuration through wireless interaction with a remote host server (e.g., remote monitoring station 125) initiated by the consumer placing a telephone call to a server capable of interaction through voice prompts or DTMF tones. For example, the consumer may call a “1-800” number and establish service with the provider of the portable event reporting system 100.

In contrast to conventional monitoring systems, the portable reporting system 100 can report an alarm directly to the consumer in certain exemplary embodiments. For example, the occurrence of a reportable event may be conveyed from the event reporting system 100 to the consumer in the form of discrete SMS messages presented on the screen of the consumer's wireless device. In the alternative, alarm reporting can be conveyed from the event reporting system 100 to the consumer via cellular telephone based data connection services utilizing General Packet Radio Service (GPRS), 1XRTT, 1XEV-DO, 1XMC, 3XMC or WCDMA data channels in the form of a discrete text message presented on the screen of the consumer's wireless device. For yet another aspect of the invention, alarm reporting to the consumer can be completed via email that is conveyed wirelessly from the event reporting system via either cellular telephone based Short Messaging Service (SMS) or General Packet Radio Services (GPRS), 1XRTT, 1XEV-DO, 1XMC, 3XMC or WCDMA wireless data channels for presentation on the consumer's cellular telephone screen, pager, PDA or personal computer. Further, alarm or event reporting to the consumer can also be completed in the form of spoken words created by conversion of alarm data into audio synthesized speech that can be conveyed to a consumer preset telephone number via a voice channel telephone call.

In addition to direct reporting reportable events, the system 100 may also be configured to report the occurrence of the reportable events to an intermediary. In an exemplary embodiment, alarm or event reporting can be supported through a third-party intermediary, such as a remote monitoring station, using proprietary or alarm industry standard tone sequences within the audio channel of cellular telephony, data representations of alarm industry data formats conveyed via the SMS data channel of cellular telephony, or data representations of alarm industry data formats conveyed via the connection based wireless data channel of GPRS, 1XRTT and their derivatives of cellular telephony.

While the portable event reporting system 100 has been described as comprising a controller 105 and event detectors 110, it is noted that the system 100 may be packages and sold in many different configurations. For example, in an alternative embodiment, a cell phone may operate as part of the portable event reporting system 100. That is, a cell phone may comprise or be communicably attached to the controller 105. In one exemplary embodiment, a cell phone comprising the controller 105 may be disposable, and the consumer may purchase one or more wireless event detectors separately or with the cell phone. In this embodiment, the cell phone may have a finite service life period (i.e., may be pre-paid). The phone may have software embedded within it for detection of reportable events transmitted by wireless event detectors. Detection of these reportable events, in an exemplary embodiment, may result in a wireless transmission through designated alert mechanisms, such as through email or a call to a phone number of the consumer. According to this exemplary embodiment, a consumer may buy the disposable phone package and one or more separate event sensors that communicate with the controller comprised with the cell phone. Alternatively, however, the cell phone may not be disposable and may comprise a cell phone already owned by a consumer. In this exemplary embodiment, a consumer may buy a software package that can be downloaded (or otherwise added) to an existing phone. For example, a consumer may purchase a replacement SIM card for insertion into an existing cell phone that would thereby allow the phone to function as the controller 105 within the operating environment of the portable event reporting system 100. Further, as described previously in another exemplary embodiment, a cell phone may be tethered or otherwise attached to the controller 105 to function as a transceiver for the system 100.

Although the portable event reporting system 100 has been described in exemplary form with a certain degree of particularity, it should be understood that the present disclosure has been made only by way of example, and that numerous changes and details of construction, as well as the combination and arrangement of parts or steps, may be resorted to without departing from the spirit of scope of the invention. Accordingly, the scope of the present invention is defined by the appended claims rather than the foregoing description.

Claims

1. A system comprising

a replacement SIM card that is configured for purchase by a consumer through a mass-market sales channel and for insertion by the consumer into an existing cell phone, the replacement SIM card operable to allow the existing cell phone to function as a controller within an operating environment of a portable event reporting system,
wherein the replacement SIM card provides the portable event reporting system with a pre-set number of prepaid alarm event communications.

2. The system of claim 1, wherein the system comprises the cell phone with the replacement SIM card inserted, and wherein the cell phone with the replacement SIM card inserted is operable to receive signals from wireless event detectors.

3. The system of claim 1, wherein the cell phone with the replacement SIM card inserted is operable to send a wireless transmission through a designated alert mechanism upon detection of a reportable event.

4. The system of claim 1, wherein the cell phone functioning as the controller with the replacement SIM card inserted comprises embedded software for detection of reportable events transmitted by wireless event detectors.

5. The system of claim 1, wherein the cell phone functioning as the controller with the replacement SIM inserted card has a finite service life period in accordance with services prepayment.

6. The system of claim 1, wherein the system comprises the cell phone, and

wherein the replacement SIM card is inserted in the cell phone.

7. The system of claim 1, wherein the cell phone with the replacement SIM card inserted is configured to connect to a remote operating station over a wireless network based on an assigned identity for the controller.

8. The system of claim 1, wherein the replacement SIM card is further configured to provide the consumer with event monitoring services via the existing cell phone while maintaining anonymity of the consumer to a provider of the event reporting services.

9. The system of claim 1, wherein the replacement SIM card is further configured for the consumer to use the system for event reporting without communication between the consumer and a provider of event monitoring service.

10. The system of claim 1, wherein the replacement SIM card is further operable to allow the system to provide event reporting without billing arrangements or contracts with a provider of event monitoring service.

11. The system of claim 1, wherein the replacement SIM card is packaged with a code for entry by the consumer to identify the system to a remote monitoring station for event monitoring service.

12. The system of claim 1, wherein the replacement SIM card is further operable to provide event reporting services through a service provider without establishing a billing identity for the consumer to the service provider.

13. The system of claim 1, wherein the replacement SIM card is further operable to allow the consumer to move the system to different event monitoring locations.

14. The system of claim 1, wherein the portable event reporting system comprises the controller, and

wherein the replacement SIM card is further configured so the consumer can purchase the SIM card and install the portable event reporting system prior to providing service and billing information for the portable event reporting system.

15. A system comprising:

a portable event reporting system comprising a controller;
a replacement SIM card that is configured for purchase by a consumer through a mass-market sales channel and for insertion by the consumer into an existing cell phone, the replacement SIM card operable to allow the existing cell phone to function as the controller within an operating environment of the portable event reporting system;
a software package that allows the existing cell phone to function as the controller when added to the existing cell phone; and
a number associated with the replacement SIM card for purchase by the consumer through the mass-market sales channel, the number associated with a specified amount of services to be deemed prepaid with the purchase by the consumer through the mass-market sales channel,
wherein the portable event reporting system is operable to transmit a wireless signal conveying the number to activate services for the portable event reporting system according to the specified amount of services.
Referenced Cited
U.S. Patent Documents
3581019 May 1971 Ryan
3886515 May 1975 Cottin et al.
3973200 August 3, 1976 Akerberg
4172969 October 30, 1979 Levine et al.
4219698 August 26, 1980 Birilli et al.
4263480 April 21, 1981 Levine
4284849 August 18, 1981 Anderson et al.
4342986 August 3, 1982 Buskirk et al.
4361730 November 30, 1982 Barber et al.
4371751 February 1, 1983 Hilligoss, Jr. et al.
4412292 October 25, 1983 Sedam et al.
4454027 June 12, 1984 Fenton
4486624 December 4, 1984 Puhl et al.
4492820 January 8, 1985 Kennard et al.
4644347 February 17, 1987 Lucas et al.
4644351 February 17, 1987 Zabarsky et al.
4646082 February 24, 1987 Engel et al.
4677653 June 30, 1987 Weiner et al.
4724425 February 9, 1988 Gerhart et al.
4734928 March 29, 1988 Weiner et al.
4750197 June 7, 1988 Denekamp et al.
4766548 August 23, 1988 Cedrone et al.
4783747 November 8, 1988 Komori et al.
4791658 December 13, 1988 Simon et al.
4807225 February 21, 1989 Fitch
4814763 March 21, 1989 Nelson et al.
4823123 April 18, 1989 Siwiak
4825193 April 25, 1989 Siwiak et al.
4825457 April 25, 1989 Lebowitz
4833701 May 23, 1989 Comroe et al.
4837800 June 6, 1989 Freeburg et al.
4839917 June 13, 1989 Oliver
4866445 September 12, 1989 Valero et al.
4868560 September 19, 1989 Oliwa et al.
4868859 September 19, 1989 Sheffer
4875038 October 17, 1989 Siwiak et al.
4875230 October 17, 1989 Blair
4882579 November 21, 1989 Siwiak
4887290 December 12, 1989 Dop et al.
4887291 December 12, 1989 Stillwell
4890315 December 26, 1989 Bendixen et al.
4891637 January 2, 1990 Siwiak et al.
4891638 January 2, 1990 Davis
4901340 February 13, 1990 Parker et al.
4905234 February 27, 1990 Childress et al.
4914651 April 3, 1990 Lusignan
4928096 May 22, 1990 Leonardo et al.
4940963 July 10, 1990 Gutman et al.
4972460 November 20, 1990 Sasuta
4979169 December 18, 1990 Almond et al.
4993059 February 12, 1991 Smith et al.
5005014 April 2, 1991 Jasinski
5010584 April 23, 1991 Seki
5020091 May 28, 1991 Krolopp et al.
5020093 May 28, 1991 Pireh
5027383 June 25, 1991 Sheffer
5029098 July 2, 1991 Levasseur
5031204 July 9, 1991 McKernan
5047763 September 10, 1991 Kuznicki et al.
5073919 December 17, 1991 Hagensick
5081667 January 14, 1992 Drori et al.
5087919 February 11, 1992 Odagawa et al.
5090051 February 18, 1992 Muppidi et al.
5117449 May 26, 1992 Metroka et al.
5121503 June 9, 1992 Davis
5124697 June 23, 1992 Moore
5131019 July 14, 1992 Sheffer et al.
5134644 July 28, 1992 Garton et al.
5142279 August 25, 1992 Jasinski et al.
5148473 September 15, 1992 Freeland et al.
5153582 October 6, 1992 Davis
5153902 October 6, 1992 Buhl et al.
5153903 October 6, 1992 Eastmond et al.
5159625 October 27, 1992 Zicker
5162790 November 10, 1992 Jasinski
5173933 December 22, 1992 Jabs et al.
5175758 December 29, 1992 Levanto et al.
5185779 February 9, 1993 Dop et al.
5196842 March 23, 1993 Gomez et al.
5206855 April 27, 1993 Schwendeman et al.
5207784 May 4, 1993 Schwartzendruber
5208756 May 4, 1993 Song
5210787 May 11, 1993 Hayes et al.
5218367 June 8, 1993 Sheffer et al.
5220599 June 15, 1993 Sasano et al.
5222123 June 22, 1993 Brown et al.
5230081 July 20, 1993 Yamada et al.
5239294 August 24, 1993 Flanders et al.
5239678 August 24, 1993 Grube et al.
5247567 September 21, 1993 Hirano
5254986 October 19, 1993 DeLuca
5255307 October 19, 1993 Mizikovsky
5265150 November 23, 1993 Helmkamp et al.
5278539 January 11, 1994 Lauterbach et al.
5278890 January 11, 1994 Beeson, Jr. et al.
5305217 April 19, 1994 Nakamura et al.
5307399 April 26, 1994 Dai et al.
5307509 April 26, 1994 Michalon et al.
5335278 August 2, 1994 Matchett et al.
5341410 August 23, 1994 Aron et al.
5363427 November 8, 1994 Ekstrom et al.
5365573 November 15, 1994 Sakamoto et al.
5369681 November 29, 1994 Boudreau et al.
5371781 December 6, 1994 Ardon
5371898 December 6, 1994 Grube et al.
5382970 January 17, 1995 Kiefl
5386209 January 31, 1995 Thomas
5396537 March 7, 1995 Schwendeman
5396539 March 7, 1995 Slekys et al.
5398277 March 14, 1995 Martin, Jr. et al.
5404392 April 4, 1995 Miller et al.
5432841 July 11, 1995 Rimer
5450329 September 12, 1995 Tanner
5453730 September 26, 1995 De/Grinis et al.
5454027 September 26, 1995 Kennedy et al.
5493722 February 20, 1996 Gunn et al.
5502761 March 26, 1996 Duncan et al.
5511072 April 23, 1996 Delprat
5511110 April 23, 1996 Drucker
5517547 May 14, 1996 Ladha et al.
5519756 May 21, 1996 Clift
5526401 June 11, 1996 Roach, Jr. et al.
5528664 June 18, 1996 Slekys et al.
5530736 June 25, 1996 Comer et al.
5533094 July 2, 1996 Sanmugam
5539810 July 23, 1996 Kennedy, III et al.
5544223 August 6, 1996 Robbins et al.
5544225 August 6, 1996 Kennedy, III et al.
5546444 August 13, 1996 Roach, Jr. et al.
5574975 November 12, 1996 Hill
5579372 November 26, 1996 Åström
5586177 December 17, 1996 Farris et al.
5594740 January 14, 1997 LaDue
5594945 January 14, 1997 Lewis et al.
5596573 January 21, 1997 Bertland
5603091 February 11, 1997 Linquist et al.
5610973 March 11, 1997 Comer
5619209 April 8, 1997 Horstein et al.
5625889 April 29, 1997 Chikkaswamy et al.
5629975 May 13, 1997 Tiedemann, Jr. et al.
5640139 June 17, 1997 Egeberg
5648966 July 15, 1997 Kondo et al.
5652564 July 29, 1997 Winbush
5652570 July 29, 1997 Lepkofker
5675371 October 7, 1997 Barringer
5678179 October 14, 1997 Turcotte et al.
5680551 October 21, 1997 Martino, II
5684858 November 4, 1997 Hartmann et al.
5686888 November 11, 1997 Welles, II et al.
5701302 December 23, 1997 Geiger
5722067 February 24, 1998 Fougnies et al.
5742668 April 21, 1998 Pepe et al.
5742905 April 21, 1998 Pepe et al.
5745867 April 28, 1998 Mills
5748104 May 5, 1998 Argyroudis et al.
5751789 May 12, 1998 Farris et al.
5754954 May 19, 1998 Cannon et al.
5758313 May 26, 1998 Shah et al.
5761621 June 2, 1998 Sainton
5767788 June 16, 1998 Ness
5768343 June 16, 1998 Dame et al.
5777605 July 7, 1998 Yoshinobu et al.
5781612 July 14, 1998 Choi et al.
5787149 July 28, 1998 Yousefi et al.
5787357 July 28, 1998 Salin
5790631 August 4, 1998 Minarczik et al.
5793306 August 11, 1998 Vershinin et al.
5794144 August 11, 1998 Comer et al.
5797097 August 18, 1998 Roach, Jr. et al.
5805997 September 8, 1998 Farris
5819184 October 6, 1998 Cashman
5822221 October 13, 1998 Groenteman
5822423 October 13, 1998 Jehnert et al.
5826195 October 20, 1998 Westerlage et al.
5835868 November 10, 1998 McElroy et al.
5844808 December 1, 1998 Konsmo et al.
5845203 December 1, 1998 LaDue
5845211 December 1, 1998 Roach, Jr.
5862201 January 19, 1999 Sands
5862480 January 19, 1999 Wild et al.
5862481 January 19, 1999 Kulkarni et al.
5873043 February 16, 1999 Comer
5875863 March 2, 1999 Jarvis et al.
5878351 March 2, 1999 Alanara et al.
5884216 March 16, 1999 Shah et al.
5889474 March 30, 1999 LaDue
5898917 April 27, 1999 Batni et al.
5901142 May 4, 1999 Averbuch et al.
5909651 June 1, 1999 Chander et al.
5913166 June 15, 1999 Buttitta et al.
5917449 June 29, 1999 Sanderford et al.
5917886 June 29, 1999 Halkio
5918172 June 29, 1999 Saunders et al.
5920822 July 6, 1999 Houde et al.
5923731 July 13, 1999 McClure
5924026 July 13, 1999 Krishnan
5933784 August 3, 1999 Gallagher et al.
5946629 August 31, 1999 Sawyer et al.
5946630 August 31, 1999 Willars et al.
5983197 November 9, 1999 Enta
5999808 December 7, 1999 LaDue
6011321 January 4, 2000 Stancu et al.
6012013 January 4, 2000 McBurney
6012014 January 4, 2000 Koyanagi et al.
6014089 January 11, 2000 Tracy et al.
6018657 January 25, 2000 Kennedy, III et al.
6021394 February 1, 2000 Takahashi
6025774 February 15, 2000 Forbes
6026345 February 15, 2000 Shah et al.
6032037 February 29, 2000 Jeffers
6049273 April 11, 2000 Hess
6067454 May 23, 2000 Foti
6070070 May 30, 2000 Ladue
6072862 June 6, 2000 Srinivasan
6078811 June 20, 2000 Lin et al.
6078820 June 20, 2000 Wells et al.
6081514 June 27, 2000 Raith
6081546 June 27, 2000 Williamson et al.
6088431 July 11, 2000 LaDue
6094578 July 25, 2000 Purcell et al.
6097951 August 1, 2000 Ernam et al.
6108537 August 22, 2000 Comer et al.
6108540 August 22, 2000 Sonti et al.
6111539 August 29, 2000 Mannings et al.
6122514 September 19, 2000 Spaur et al.
6125275 September 26, 2000 Comer et al.
6138034 October 24, 2000 Willey
6144722 November 7, 2000 Anderson et al.
6144859 November 7, 2000 LaDue
6148202 November 14, 2000 Wortham
6150955 November 21, 2000 Tracy et al.
6151507 November 21, 2000 Laiho et al.
6154648 November 28, 2000 Comer
6154658 November 28, 2000 Caci
6161020 December 12, 2000 Kim
6163701 December 19, 2000 Saleh et al.
6169895 January 2, 2001 Buhrmann et al.
6175732 January 16, 2001 McDaniel et al.
6181981 January 30, 2001 Varga et al.
6185198 February 6, 2001 LaDue
6195546 February 27, 2001 Leung et al.
6215404 April 10, 2001 Morales
6233450 May 15, 2001 Seppanen
6236357 May 22, 2001 Corwith
6249217 June 19, 2001 Forbes
6259781 July 10, 2001 Crouch et al.
6263212 July 17, 2001 Ross et al.
6282496 August 28, 2001 Chowdhary
6285868 September 4, 2001 LaDue
6285953 September 4, 2001 Harrison et al.
6292669 September 18, 2001 Meuronen et al.
6297768 October 2, 2001 Allen, Jr.
6298232 October 2, 2001 Marin et al.
6311056 October 30, 2001 Sandidge
6311060 October 30, 2001 Evans et al.
6330452 December 11, 2001 Fattouche et al.
6339731 January 15, 2002 Morris et al.
6353743 March 5, 2002 Karmel
6353745 March 5, 2002 Wehrend et al.
6363249 March 26, 2002 Nordeman et al.
6363254 March 26, 2002 Jones et al.
6363324 March 26, 2002 Hildebrant
6366791 April 2, 2002 Lin et al.
6369719 April 9, 2002 Tracy et al.
6370135 April 9, 2002 Gardner
6377210 April 23, 2002 Moore
6389289 May 14, 2002 Voce et al.
6393295 May 21, 2002 Butler et al.
6397056 May 28, 2002 Bugnon et al.
6405033 June 11, 2002 Kennedy, III et al.
6424828 July 23, 2002 Collins et al.
6424841 July 23, 2002 Gustafsson
6457038 September 24, 2002 Defosse
6476763 November 5, 2002 Allen, Jr.
6484035 November 19, 2002 Allen, Jr.
6487602 November 26, 2002 Thakker
6493556 December 10, 2002 Stinson
6493558 December 10, 2002 Bernhart et al.
6515997 February 4, 2003 Feltner et al.
6516197 February 4, 2003 Havinas et al.
6553336 April 22, 2003 Johnson et al.
6560456 May 6, 2003 Lohtia et al.
6567501 May 20, 2003 Pernu et al.
6570532 May 27, 2003 Mise et al.
6608553 August 19, 2003 Isobe
6618671 September 9, 2003 Dooley et al.
6622016 September 16, 2003 Sladek et al.
6625461 September 23, 2003 Bertacchi
6643511 November 4, 2003 Rune et al.
6665532 December 16, 2003 Boland et al.
6683881 January 27, 2004 Mijares et al.
6710738 March 23, 2004 Allen, Jr.
6714793 March 30, 2004 Carey et al.
6718177 April 6, 2004 Comer et al.
6718237 April 6, 2004 Murray et al.
6738647 May 18, 2004 Link, II
6741853 May 25, 2004 Jiang et al.
6741863 May 25, 2004 Chiang et al.
6745041 June 1, 2004 Allison et al.
6760580 July 6, 2004 Robinson et al.
6771949 August 3, 2004 Corliss
6782276 August 24, 2004 Lam et al.
6826397 November 30, 2004 Vasa
6828909 December 7, 2004 Script et al.
6856808 February 15, 2005 Comer et al.
6861947 March 1, 2005 Albert
6865191 March 8, 2005 Bengtsson et al.
6882843 April 19, 2005 Comer
6959192 October 25, 2005 Cannon et al.
6980887 December 27, 2005 Varga et al.
6982656 January 3, 2006 Coppinger et al.
7005997 February 28, 2006 Wiewiura
7010306 March 7, 2006 Tanibayashi et al.
7542721 June 2, 2009 Bonner et al.
7650144 January 19, 2010 Nakamura et al.
20010003093 June 7, 2001 Lundin
20010042121 November 15, 2001 Defosse et al.
20010047244 November 29, 2001 Harrison et al.
20010047410 November 29, 2001 Defosse
20010054083 December 20, 2001 Defosse
20020016829 February 7, 2002 Defosse
20020073333 June 13, 2002 Palka et al.
20020077077 June 20, 2002 Rezvani et al.
20020086636 July 4, 2002 Tracy et al.
20020110230 August 15, 2002 Leuca et al.
20020120728 August 29, 2002 Braatz et al.
20020142759 October 3, 2002 Newell et al.
20020153410 October 24, 2002 Santini
20020155844 October 24, 2002 Rankin et al.
20020160771 October 31, 2002 Massie et al.
20020164988 November 7, 2002 Vishwanathan et al.
20020177428 November 28, 2002 Menard et al.
20020194387 December 19, 2002 Defosse
20020196924 December 26, 2002 Dahari
20030003930 January 2, 2003 Allison et al.
20030009313 January 9, 2003 May et al.
20030021273 January 30, 2003 Fouquet et al.
20030022656 January 30, 2003 Hinnant, Jr. et al.
20030054830 March 20, 2003 Williams et al.
20030097474 May 22, 2003 Defosse et al.
20030101257 May 29, 2003 Godwin
20030101262 May 29, 2003 Godwin
20030104800 June 5, 2003 Zak
20030119489 June 26, 2003 Mohammed
20030119498 June 26, 2003 Haas et al.
20030129969 July 10, 2003 Rucinski
20030141990 July 31, 2003 Coon
20030158650 August 21, 2003 Abe et al.
20030182053 September 25, 2003 Swope et al.
20030190908 October 9, 2003 Craven
20030204391 October 30, 2003 May et al.
20040029598 February 12, 2004 Guggisberg
20040083173 April 29, 2004 Reddihough et al.
20040110493 June 10, 2004 Alvarez et al.
20040110544 June 10, 2004 Oyagi et al.
20040142707 July 22, 2004 Midkiff et al.
20040180678 September 16, 2004 Smith et al.
20040186739 September 23, 2004 Bolles et al.
20040203640 October 14, 2004 Molander et al.
20050037784 February 17, 2005 Cleary
20050102074 May 12, 2005 Kolls
20050181771 August 18, 2005 Cuddihy et al.
20050197106 September 8, 2005 Bristow et al.
20050200474 September 15, 2005 Behnke
20050213715 September 29, 2005 Winick
20060039389 February 23, 2006 Burger et al.
20060077053 April 13, 2006 Park et al.
20060181411 August 17, 2006 Fast et al.
20070057804 March 15, 2007 Appleyard et al.
20070247302 October 25, 2007 Martin
20070286181 December 13, 2007 Bushmitch et al.
20080020747 January 24, 2008 McQuaide
20080025487 January 31, 2008 Johan et al.
20080254766 October 16, 2008 Craven
20090042604 February 12, 2009 Ficquette
20090069047 March 12, 2009 Russell et al.
20090072988 March 19, 2009 Haywood
20100049849 February 25, 2010 Hershkovitz et al.
20100271198 October 28, 2010 Boling et al.
20110001812 January 6, 2011 Kang et al.
20110003577 January 6, 2011 Rogalski et al.
20110074570 March 31, 2011 Feldstein et al.
20110095883 April 28, 2011 Watts et al.
20130189946 July 25, 2013 Swanson
Foreign Patent Documents
0 123 456 October 1984 EP
0 123 562 July 1990 EP
0 345 818 December 1996 EP
0 837 341 April 1998 EP
0 855 824 July 1998 EP
0 924 918 June 1999 EP
0 959 600 November 1999 EP
2 363 289 December 2001 GB
4-96509 March 1992 JP
WO 92/14329 August 1992 WO
WO 94/05095 March 1994 WO
WO 95/24791 September 1995 WO
WO 95/25407 September 1995 WO
WO 95/26088 September 1995 WO
WO 96/03007 February 1996 WO
WO 96/10895 April 1996 WO
WO 96/37079 November 1996 WO
WO 96/38989 December 1996 WO
WO 97/36435 October 1997 WO
WO 97/38540 October 1997 WO
WO 97/45991 December 1997 WO
WO 98/06227 February 1998 WO
WO 98/19438 May 1998 WO
WO 98/19447 May 1998 WO
WO 98/27780 June 1998 WO
WO 99/26428 May 1999 WO
WO 99/60769 November 1999 WO
WO 00/03532 January 2000 WO
WO 00/17021 March 2000 WO
WO 00/28347 May 2000 WO
WO 00/36812 June 2000 WO
WO 01/63825 August 2001 WO
WO 01/63960 August 2001 WO
WO 01/72068 September 2001 WO
WO 01/80583 October 2001 WO
WO 02/35866 May 2002 WO
WO 02/089085 November 2002 WO
WO 03/019925 March 2003 WO
WO 2005/074430 August 2005 WO
WO 2006/014419 February 2006 WO
Other references
  • European Telecommunication Standards Institute; European Digital Cellular Telecommunications System (Phase 2); Technical Realization of the Short Message Service (SMS) Point to Point (PP) (GSM 03.40); European Telecommunication Standard; Oct. 1993; Draft pr ETS 300 536; pp. 1-103.
  • European Telecommunication Standards Institute; European Digital Cellular Telecommunications System (Phase 2); Technical Realization of Short Message Service Call Broadcast (SMSCB) (GSM 03.41); European Telecommunication Standard; Oct. 1993; Draft pr ETS 300 537; pp. 1-24.
  • Isochron Data Corporation; Connect With Your Vending Machines—and Watch Your Profits Soar; www.isochron.com/solutionsVC.htm; (2002); pp. 1-2.
  • Lee, William C. Y.; Mobile Cellular Telecommunications Systems; ISBN 0-07-037030-3; 1989; pp. 74-80.
  • Mouly et al.; The GSM System for Mobile Communications; ISBN: 2-9507190-0-7; © 1992; pp. 56-59.
Patent History
Patent number: 8855716
Type: Grant
Filed: Aug 21, 2013
Date of Patent: Oct 7, 2014
Patent Publication Number: 20130337870
Assignee: Numerex Corp. (Atlanta, GA)
Inventors: Michael Marett (Kennesaw, GA), Edward I. Comer (Brevard, NC)
Primary Examiner: Nathan Mitchell
Application Number: 13/971,935
Classifications
Current U.S. Class: Card Control Element (455/558)
International Classification: H04B 1/38 (20060101); G08B 25/08 (20060101); G06Q 30/02 (20120101); G08B 25/10 (20060101);