Patent Grant
9153135
1. Technical Field
The present invention relates to mobile devices and communication methods, and more particularly to mobile computing devices configured to work with dynamic networks to warn of events of interest.
2. Description of the Related Art
Mobile computing devices are often installed or used in automobiles or other vehicles. Most of these vehicles contain one or more computers that perform control and monitoring functions of the vehicle's systems and also provide information about conditions or events having to do with the operation of the vehicle.
The mobile computing devices are often underutilized. It would be advantageous to have the additional computing resources in vehicles employed for beneficial uses.
A warning system and method include a memory device configured to store one or more condition criteria. A monitoring device is configured to monitor a status of the one or more condition criteria. The monitoring device is triggered by a triggering event related to the status to generate a warning signal responsive to the triggering event. A mobile computing device is configured to communicate with the monitoring device and an external network to receive the warning signal and output a warning message on the external network to one or more designated entities.
A warning system includes a vehicle including: a memory device to store one or more condition criteria; a monitoring device configured to monitor a status of the one or more condition criteria, the monitoring device being triggered by a triggering event related to the status to generate a warning signal responsive to the triggering event; and a transceiver configured to communicate with a local network. A mobile computing device is configured to communicate with the vehicle using the local network and to communicate with an external network. The mobile computing device is also configured to receive the warning signal and output a warning message on the external network to one or more designated entities.
A warning notification method includes storing one or more condition criteria in a memory device; monitoring a status of the one or more condition criteria; generating a warning signal responsive to a triggering event related to the status; and using a mobile computing device, communicating between the monitoring device and an external network to receive the warning signal and output a warning message on the external network to one or more designated entities.
These and other features and advantages will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings.
The disclosure will provide details in the following description of preferred embodiments with reference to the following figures wherein:
In accordance with the present principles, mobile computing devices, such as a cellular phone, are employed in collaboration with a vehicle's computer to determine when a certain threshold condition has been met or has occurred. When the condition is met, a driver or other subscribed system or systems may be notified via email, wired, or wireless communications of events of interest. Some of these events may include an impending dangerous situation or emergency that has occurred or is about to occur.
The mobile device, in collaboration with the vehicle's sensors, can declare an emergency or unsafe situation. The mobile device may employ information obtained from the vehicle, such as hard braking, radar detection, collision sensors, accelerometers, etc. to determine that an emergency exists or that there is an impending emergency situation. A network may be formed on the basis of connectivity and common interests. The user may set the threshold of the event, the event type, priority, and contact information for various classifications of events. Additionally, those parameters can be set by a designated policy and enforced by a service or a corporate policy. The policy can be enforced using an external service, based upon a vehicle's location, or based upon a corporate policy or local laws. The policy can preferably be dictated by location and/or local governance.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Referring now to the drawings in which like numerals represent the same or similar elements and initially to
Sensors 104 may include sensors to determine information obtained from the vehicle, such as hard braking, radar detection, collision sensors, accelerometers, etc. Sensors 104 may include sensors to determine if an emergency exists or that there is an impending emergency situation. Sensors 104 may include sensors that monitor a condition of a human within the vehicle. The condition being monitored may be a direct measurement, e.g., measuring a status of a user's pace maker, measuring a drivers position (slumped or sleeping, etc.) or an indirect measurement, e.g., based on system parameters inferring that the driver is unfit to drive.
A local network 130 may be formed on the basis of connectivity and common interests. The user may set the threshold of the event, the event type, priority, and contact information for various classifications of events. Additionally, those parameters can be set by a designated policy and enforced by a service, based on location or based on a corporate or other policy. The policy can be dictated by location and/or local governance. Network 130 may be as simple as providing communication with a mobile device 112, such as cellular telephone, a personal digital assistant, a net book, a computer or other portable device. Network 130 may also include other users, e.g., nearby vehicles, portable devices and the like. The network participants may be determined by a policy or a set of conditions for participation in the network (e.g., proximity, speed, direction, etc.).
Mobile device 112 includes a processor 120, a transceiver 114, a user interface 116 and memory 118. Mobile device 112 and computer 102 are configured to be able to set up a network 130 therebetween to enable communication with each other and with other external networks 132.
It should be understood that the functions described for the vehicle computer 102 may be shared with or carried out by the mobile device 112. A user or a policy mandate describes events of interest based on classification, threshold, and various other criteria. The user criteria and/or policies may be stored in memory 106, memory 118 or at a service provider. The policies may be enforced by a network service provider of the external network 132 and additionally may be affected by or controlled by a context (e.g., speed over 65 miles per hour) or location (e.g., as determined by a global positioning system (GPS)). Based on the classification of such a determination, the mobile device 112 contacts a designated authority or system, such as police, fire, a service truck, or might even notify a spouse.
For example, a minor driver with permission to use a vehicle has the vehicle computer 102 configured to alert a parent by email or other means using the mobile device 112 whenever the vehicle exceeds the speed of 60 miles per hour or goes to an impermissible location. In this instance, a parent may set a user condition using an interface 110 on computer 102, using the interface 116 on the mobile device 112, or by programming the condition through the external network 132 (e.g., using the Internet and a service provider). The computer 102 monitors the speed and/or position of the vehicle using a sensor 104 or using the vehicular devices already in place (speedometer, GPS, etc.). The sensors 104 report the condition or event has occurred to the computer 102, which conveys this information to the mobile device 112 using transceivers 108 and/or 114. The mobile device 112 calls, emails or otherwise notifies the parent or any other individuals on a notification list.
In another aspect, an emergency might be caused by a failing medical device such as a pacemaker. In this instance, sensors 104 may be configured to monitor operations of a pacemaker for a driver. Should a malfunction of the pacemaker occur, the driver and/or any other individual on a notify list may be notified by mobile device 112. The notifications would be sent to the subscribing parties notifying them of the malfunction or other matter. In addition, a position of the vehicle may also be disclosed so that the vehicle may be located by friends and family or emergency personnel.
In another embodiment, the system 50 or components thereof may be configured to interact with other environments. For example, sensing for emergency/critical situations may be performed in stationary environments. For example, if a phone detects a sequence of beeps or other audio sound from a smoke detector in a hotel room or home, the phone can send out a warning of pending fire/heat. The warning may be sent to notify entities on an appropriate notification list.
In another embodiment, the mobile device 112 initiates and/or participates in a social network that permits other mobile users to participate. This allows a mobile device 112, such as a phone, to notify other devices (phones) or interested subscribers of impending problems, such as traffic jams, accidents, or radar traps. It should be understood that this is a dynamic social network, unlike Twitter™. This dynamic social network is preferably an ad-hoc dynamic network that users can join and leave all the time. There may also be an option to join the network without an implicit membership, e.g., in a ‘listen only’ mode. In such a mode, the user can get updates or information without disclosing any information.
In one embodiment, the social network may include all cars following a particular car at a distance not to exceed, e.g., 0.2 miles, or all phones belonging to health professionals within one mile of a particular phone, or the like. These networks would constantly evolve and would remain silent almost all of the time, consuming few resources.
In one example, the vehicle 100 slows to 5 miles per hour on an interstate with a speed limit of 65 miles per hour. This triggers the computer 102 or the mobile device 112 to search for access for a local network of vehicles on the same interstate within one mile of a position of the vehicle 100. The mobile devices or vehicle computers may have a preselected channel or plurality of channels configured for such communications. Once other devices that meet the criteria are recognized, information may be exchanged. For example, if a vehicle has stalled, the vehicle may output a stalled vehicle indication signal, which can be transmitted in a local area. The indication signal may be received by computer 102 or device 112 and displayed on a display 134 of the vehicle 100 or displayed on a display 115 of the mobile device 112. The message may be further propagated by mobile device 112, may be delivered to entities on a notification list, e.g., by email, text message, etc.
In one embodiment, the transceiver 108 of vehicle 100 may be a cellular transceiver that is built in. For example, the vehicle 100 may conduct cellular communications in the context of a cell phone in the contest of a cellular radio. The transceiver 108 may provide service via satellite as well. In one embodiment, if the vehicle is stolen, the transceiver 108 may be employed to alert a notification list of its location. The location can be determined based on GPS, using cellular location, etc. The request for location may be sent out over the external network 132.
Referring to
The service provider can determine the positions of other vehicles in the circle 210 using power information or other location systems for the mobile device and/or vehicle computer systems. If GPS information is supported, service provider can further limit the warning to travelers heading in a same direction as vehicle 201 (e.g., vehicles 204 and 205). Vehicles 202 and 203 may be filtered from receiving the warning message since these vehicles are heading in a different direction. The service provider may employ other filters to ensure that the policies and selections of the users are carried out.
In another scenario, vehicle 201 may be in an accident. Vehicle sensors (104) may generate a signal that the vehicle 201 has been in a collision. The user has selected a 1.0 mile radius of a circle 212 to inform emergency vehicles/personnel of the accident. The service provider of the external network servicing the area can locate emergency personnel within the circle 212 and send a warning and information, e.g., the vehicle's location and the seriousness of the accident. In addition, the emergency personnel can indicate that they are reporting to the scene so that the driver, other drivers and other emergency personnel can employ this information.
Referring to
In block 306, monitoring the status may include monitoring a vehicle using an on-board computer system. In block 308, monitoring the status may include employing one or more sensors for determining the status of the system. The sensors may be configured to measure at least one of a condition of a vehicle, a condition of a driver of the vehicle and a traffic condition related to the vehicle. Other conditions may also be monitored including those that are not related to the use or status of a vehicle. For example, an emergency event in a hotel or other location.
In block 310, a warning signal is generated responsive to a triggering event related to the status. For example, the triggering event may include exceeding a threshold, determining an accident has occurred, determining a fire or emergency has occurred, etc. In block 312, using a mobile computing device, communication between the monitoring device and an external network may be provided. The communication is enabled so that the mobile computing device receives the warning signal and outputs a warning message on the external network to one or more designated entities.
The mobile computing device includes a wireless communication device and the external network preferably includes a cellular network, although other networks may be employed, e.g., a cable network, home networks, a satellite network, etc. The external network may include one or more service providers that manage system policies. The policies may be employed to limit communications to user designated entities, to control and set up communication links and channels and to provide a way for appropriately distributing warning messages in accordance with user choices.
The designated entities are preferably selected in advance by a user and stored in the memory. These may include the names and contact information for friends, family, medical personnel, other systems, other users, etc. In particularly useful embodiments, the designated entities may include users which achieve user-defined limitations, e.g., other drivers in a 0.2 mile area, northbound travelers on interstate 95, etc.
Having described preferred embodiments for a mobile computing device emergency warning system and method (which are intended to be illustrative and not limiting), it is noted that modifications and variations can be made by persons skilled in the art in light of the above teachings. It is therefore to be understood that changes may be made in the particular embodiments disclosed which are within the scope of the invention as outlined by the appended claims. Having thus described aspects of the invention, with the details and particularity required by the patent laws, what is claimed and desired protected by Letters Patent is set forth in the appended claims.
This application is a Continuation application of co-pending U.S. patent application Ser. No. 13/004,462 filed on Jan. 11, 2011, incorporated herein by reference in its entirety. This application is related to commonly assigned application: “PREVENTION OF TEXTING WHILE OPERATING A MOTOR VEHICLE”, Ser. No. 13/004,490, filed on Jan. 11, 2011 and incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5081667 | Drori et al. | Jan 1992 | A |
| 5103474 | Stoodley et al. | Apr 1992 | A |
| 5218367 | Sheffer et al. | Jun 1993 | A |
| 5482314 | Corrado et al. | Jan 1996 | A |
| 6049711 | Ben-Yehezkel et al. | Apr 2000 | A |
| 6184801 | Janky | Feb 2001 | B1 |
| 6337641 | Yoshioka et al. | Jan 2002 | B1 |
| 6405213 | Layson et al. | Jun 2002 | B1 |
| 6526352 | Breed et al. | Feb 2003 | B1 |
| 6529723 | Bentley | Mar 2003 | B1 |
| 6535743 | Kennedy et al. | Mar 2003 | B1 |
| 6553262 | Lang et al. | Apr 2003 | B1 |
| 6603405 | Smith | Aug 2003 | B2 |
| 6674362 | Yoshioka et al. | Jan 2004 | B2 |
| 6690302 | Inomata | Feb 2004 | B1 |
| 6694234 | Lockwood et al. | Feb 2004 | B2 |
| 6728605 | Lash et al. | Apr 2004 | B2 |
| 6847889 | Park et al. | Jan 2005 | B2 |
| 7023332 | Saito et al. | Apr 2006 | B2 |
| 7221928 | Laird et al. | May 2007 | B2 |
| 7515066 | Watanabe | Apr 2009 | B2 |
| 7639148 | Victor | Dec 2009 | B2 |
| 7876205 | Catten et al. | Jan 2011 | B2 |
| 7893818 | Smoyer et al. | Feb 2011 | B2 |
| 8005490 | Miyake | Aug 2011 | B2 |
| 8098132 | Scalisi et al. | Jan 2012 | B2 |
| 8290480 | Abramson et al. | Oct 2012 | B2 |
| 8396002 | Marshall-Wilson | Mar 2013 | B2 |
| 20010040504 | Gehlot | Nov 2001 | A1 |
| 20010040506 | Boulay et al. | Nov 2001 | A1 |
| 20020044049 | Saito et al. | Apr 2002 | A1 |
| 20020161495 | Yamaki | Oct 2002 | A1 |
| 20020173881 | Lash et al. | Nov 2002 | A1 |
| 20020198660 | Lutter et al. | Dec 2002 | A1 |
| 20030009270 | Breed | Jan 2003 | A1 |
| 20030095038 | Dix | May 2003 | A1 |
| 20030128123 | Sumiya et al. | Jul 2003 | A1 |
| 20030212480 | Lutter et al. | Nov 2003 | A1 |
| 20050033504 | Rennels | Feb 2005 | A1 |
| 20050071085 | Root et al. | Mar 2005 | A1 |
| 20050162284 | Hanebrink | Jul 2005 | A1 |
| 20050179518 | Kawamura et al. | Aug 2005 | A1 |
| 20050203698 | Lee | Sep 2005 | A1 |
| 20050222730 | Taipale | Oct 2005 | A1 |
| 20050222752 | Sokola et al. | Oct 2005 | A1 |
| 20060020380 | Saito et al. | Jan 2006 | A1 |
| 20060059364 | Fontijn | Mar 2006 | A1 |
| 20070135978 | Kim et al. | Jun 2007 | A1 |
| 20070156311 | Elcock et al. | Jul 2007 | A1 |
| 20080122595 | Yamamichi et al. | May 2008 | A1 |
| 20080133230 | Herforth | Jun 2008 | A1 |
| 20080238642 | Mauti | Oct 2008 | A1 |
| 20080258890 | Follmer et al. | Oct 2008 | A1 |
| 20080297336 | Lee | Dec 2008 | A1 |
| 20090096599 | Kranz | Apr 2009 | A1 |
| 20090109037 | Farmer | Apr 2009 | A1 |
| 20090174572 | Smith | Jul 2009 | A1 |
| 20090256690 | Golenski | Oct 2009 | A1 |
| 20100097239 | Campbell et al. | Apr 2010 | A1 |
| 20100151838 | Wormald et al. | Jun 2010 | A1 |
| 20100156617 | Nakada et al. | Jun 2010 | A1 |
| 20110063098 | Fischer et al. | Mar 2011 | A1 |
| 20110063138 | Berkobin et al. | Mar 2011 | A1 |
| 20110065375 | Bradley | Mar 2011 | A1 |
| 20110140913 | Montenero | Jun 2011 | A1 |
| 20110207476 | Qahwash et al. | Aug 2011 | A1 |
| 20110304446 | Basson et al. | Dec 2011 | A1 |
| 20120075118 | Basir | Mar 2012 | A1 |
| 20120126974 | Phillips et al. | May 2012 | A1 |
| 20120221677 | Kim et al. | Aug 2012 | A1 |
| 20130106618 | Wormald et al. | May 2013 | A1 |
| 20130214939 | Washlow et al. | Aug 2013 | A1 |
| Entry |
|---|
| Office Action dated Jan. 3, 2013 for U.S. Appl. No. 13/603,585. |
| Office Action dated May 23, 2013 for U.S. Appl. No. 13/603,585. |
| Office Action dated Oct. 23, 2012 for U.S. Appl. No. 13/004,490. |
| Final Office Action dated Apr. 30, 2013 for U.S. Appl. No. 13/004,490. |
| Office Action dated Aug. 1, 2013 for U.S. Appl. No. 13/004,490. |
| Final Office Action dated Dec. 17, 2013 for U.S. Appl. No. 13/603,585. |
| Number | Date | Country | |
|---|---|---|---|
| 20120326860 A1 | Dec 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13004462 | Jan 2011 | US |
| Child | 13602866 | US |
