Patent Grant
8280355
1. Field of the Invention
The invention is related to the field of communications, and in particular, to a monitoring system that provides real-time data on the velocity of a mobile communication device.
2. Description of the Prior Art
Existing traffic monitoring systems use various sensors, such as radar devices and video cameras, to collect traffic data. Such monitoring systems are expensive to install and maintain. In addition, these systems only monitor a very limited portion of the nation's roadways.
Other existing traffic monitoring systems work with mobile telephone carriers to gather and analyze data on cellular tower handoff frequency. Unfortunately, this data is not anonymous. It contains personal information that can be tied back to individuals. Personal identifying information is disassociated from the data record only after it is already in the monitoring system. Thus, these systems raise privacy concerns that inhibit further deployment.
Another drawback of traffic monitoring systems that work in conjunction with mobile telephone carriers is the burden placed on cellular base stations. These monitoring systems require additional processing in the cellular base stations to deliver the handoff data in real-time. Alternatively, these monitoring systems deliver handoff data through batch reporting. While the batch reporting is less taxing on the cellular system, the value of the data is greatly diminished because real-time traffic reporting is not possible.
None of the existing traffic monitoring systems provide reliable, accurate, inexpensive, anonymous, real-time, nation-wide traffic reporting that does not excessively burden the cellular network.
A traffic monitoring system described herein solves the problems described above. The traffic monitoring system anonymously monitors the volume and velocity of traffic on roadways. The traffic monitoring system utilizes low-cost roadside radio frequency beacons that do not tax the cellular system. As a motorist passes one of the beacons, their wireless communication device receives a beacon identifier and generates a random anonymous code. The random anonymous code changes periodically and cannot be tied back to the motorist. The wireless communication device then transmits the beacon identifier and the random code to the traffic monitoring system. The traffic monitoring system processes the data received from the wireless communication device to determine the velocity of the motor vehicle. As the traffic monitoring system receives data from a plurality of wireless communication devices, it generates real-time reports on traffic volume and velocity.
Beacons 101-105 comprise wireless transmission control circuitry. Beacons 101-105 transmit beacon signals indicating beacon identifiers. The beacon identifiers uniquely identify each one of beacons 101-105 or their geographic location. Beacons 101-105 use Bluetooth, Wireless Fidelity (Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), Radio Frequency (RF), or some other form of wireless communication. Typically, the beacon signals have a limited range, so mobile communication device 115 only receives a given beacon signal when it is in range and proximate to the respective beacon.
Mobile communication device 115 comprises a telephone, an internet appliance, or some other wireless transceiver and control circuitry. Mobile communication device 115 generates a random code that is anonymous within monitoring system 100 and external systems. Mobile communication device 115 receives a beacon identifier when it is proximate to one of beacons 101-105, and in response, transmits a message comprising the beacon identifier and the random code. Although not required in all embodiments, mobile communication device 115 typically timestamps the message by placing the current time of day in the message indicating when the mobile communication device 115 is proximate to one of beacons 101-105.
Traffic monitor 106 comprises a computer system. Traffic monitor 106 receives the message from mobile communication device 115 and processes the message to determine the velocity of mobile communication device 115. Velocity determination entails dividing the distance between respective beacons by the time taken for mobile communication device 115 to travel between the beacons. Traffic monitor 106 may maintain a data structure that correlates the beacon identifiers to geographic locations or distances for use in velocity determination. In addition, the distance between two beacons may be determined over roadways instead of the direct distance (as the crow flies) between the beacons.
Beacons 101-104 and mobile communication device 115 are sequentially coupled by links 107-110 as mobile communication device 115 moves within proximity of each one of beacons 101-104, as indicated by the dashed arrows. Links 107-110 comprise Bluetooth, Wi-Fi, WiMAX, or any form of wireless communication that could transmit from beacons 101-104 to mobile communication device 115.
Mobile communication device 115 and traffic monitor 106 communicate over link 111. Link 111 comprises a wireless communication link using Wi-Fi, WiMAX, Code Division Multiple Access (CDMA), Global System for Mobile Communication (GSM), or some other form of wireless communication. Link 111 may be a direct wireless link or may comprise various intermediate systems and components. For example, link 111 might comprise a direct WiMAX link between mobile communication device 115 and traffic monitor 106, or link 111 might comprise a WiMAX link between mobile communication device 115 and a base station where the base station is coupled to traffic monitor 106 over the Internet.
Beacon 103 transmits a beacon signal indicating a third beacon identifier. Mobile communication device 115 receives the beacon signal indicating the third beacon identifier when device 115 is proximate to beacon 103. Mobile communication device 115 generates a new random code and transmits the third beacon identifier and the new random code to traffic monitor 106. Beacon 104 transmits a beacon signal indicating a fourth beacon identifier. Mobile communication device 115 receives the beacon signal indicating the fourth beacon identifier when device 115 is proximate to beacon 104. Mobile communication device 115 transmits the fourth beacon identifier and the new random code to traffic monitor 106. Traffic monitor 106 then processes the messages to determine the velocity of mobile communication device 115 between beacons 103-104.
Note that the change in the random code between beacons 102-103 prevented traffic monitor 106 from determining the velocity of mobile communication device 115 between beacons 102-103. However, traffic monitor 106 is able to determine the velocity of mobile communication device 115 at various points when the random code remains the same. Advantageously, the use of the changing random code allows the user to provide time and location data for velocity determination while remaining anonymous. The loss of velocity data at a few points may be acceptable for the increased anonymity provided by changing the ransom code. In alternative embodiments, the random code could always remain the same.
Traffic monitor 306 comprises communication interface 365, processing system 350, and user interface 370. Processing system 350 comprises storage system 355. Storage system 355 stores software 360. Processing system 350 is linked to communication interface 365 and user interface 370. Traffic monitor 306 could be comprised of a programmed general-purpose computer, although those skilled in the art will appreciate that programmable or special purpose circuitry and equipment may be used. Traffic monitor 306 may be distributed among multiple devices that together comprise elements 350-370.
Communication interface 320 and communication interface 365 communicate over link 311. Link 311 comprises a wireless communication link using Wi-Fi, WiMAX, CDMA, GSM, or some other form of wireless communication. Link 311 may be a direct wireless link or may comprise various intermediate systems and components.
Communication interface 325 is connected to beacon link 307 when mobile communication device 315 moves within proximity of one of the beacons (not shown). Typically, the beacons broadcast a beacon signal over a predetermined range (such as 30, 60, 90, 100, 300, or 500 feet) and communication interface 325 only receives the beacon signal when it is proximate to and in range of the transmitting beacon. Link 307 comprises Bluetooth, Wi-Fi, WiMAX, or any form of wireless communication that could transmit from the beacons to communication interface 325.
Communication interface 320 and communication interface 325 could comprise transceiver circuitry that provides Bluetooth, Wi-Fi, WiMAX, RF, CDMA, GSM or some other form of wireless communication. Communication interface 320 and communication interface 325 may be distributed among multiple communication devices. Processing system 335 could comprise a computer microprocessor, logic circuit, or some other processing device. Processing system 335 may be distributed among multiple processing devices. User interface 330 could comprise a keyboard, mouse, voice recognition interface, microphone and speakers, graphical display, touch screen, or some other type of user device. User interface 330 may be distributed among multiple user devices. Storage system 340 could comprise a memory drive, integrated circuit, disk, or some other memory device. Storage system 340 may be distributed among multiple memory devices.
In some embodiments, user interface 330 provides an application menu with various user options related to the traffic monitoring system. In some embodiments, the application menu comprises user options to reset the random code generated by mobile communication device 315, switch the monitoring system functionality on or off, and display velocity reports, real-time traffic reports, and maps comprising real-time traffic velocity data. For example, mobile communication device 315 may stop the reception of the beacon signals in response to a user input.
Processing system 335 retrieves and executes software 345 from storage system 340. Software 345 may comprise an operating system, utilities, drivers, networking software, and other software typically loaded onto a mobile communication device. Software 345 could comprise an application program, firmware, or some other form of machine-readable processing instructions. When executed by processing system 335, software 345 directs processing system 335 to operate as described herein.
Communication interface 365 could comprise a network interface, modem, port, transceiver, or some other communication device. Communication interface 365 may be distributed among multiple communication devices. Processing system 350 could comprise a computer microprocessor, logic circuit, or some other processing device. Processing system 350 may be distributed among multiple processing devices. User interface 370 could comprise a keyboard, mouse, voice recognition interface, microphone and speakers, graphical display, touch screen, or some other type of user device. User interface 370 may be distributed among multiple user devices. Storage system 355 could comprise a disk, tape, integrated circuit, server, or some other memory device. Storage system 355 may be distributed among multiple memory devices.
Processing system 350 retrieves and executes software 360 from storage system 355. Software 360 may comprise velocity determining software, an operating system, utilities, drivers, networking software, and other software typically loaded onto a computer system. Software 360 could comprise an application program, firmware, or some other form of machine-readable processing instructions. When executed by processing system 350, software 360 directs processing system 350 to operate as described herein.
RF transceivers 401-404 are connected to roadside mile markers. RF transceivers 401-404 transmit beacon signals indicating their respective Global Positioning System (GPS) coordinates. The beacon signals have a range of 300 feet. RF transceivers 401-404 use solar power.
Wireless telephone 415 is located in a transportation device, such as an automobile traveling on a highway. Wireless telephone 415 generates a random code that is anonymous within monitoring system 400 and external systems. Wireless telephone 415 receives a beacon identifier when it is within 300 feet of one of beacons 401-404 over wireless links 407-410, respectively. In response to receiving the beacon identifier, wireless telephone 415 transmits a message comprising the beacon identifier, the random code, and a timestamp indicating the current time of day. Wireless telephone 415 generates a new random code in response to previously transmitting a pre-determined number of messages with the old random code or in response to the lapse of a time period. For example, wireless telephone 415 may generate a new random code after every 10 messages or after every 10 minutes. The random codes could be generated by a pseudo-random number generator within wireless telephone 415.
Traffic monitor 406 comprises a computer system. Traffic monitor 406 receives the messages from wireless telephone 415 via base stations 420 and 421 and Internet 429. Traffic monitor 406 may timestamp the messages upon receipt. Traffic monitor 406 processes the messages received from wireless telephone 415 to determine the velocity of the wireless telephone 415.
Traffic monitor 406 processes similar messages from a plurality of other mobile communication devices (not shown) to determine the velocity and volume of traffic in a particular geographic area. Traffic monitor 406 generates real-time velocity and volume traffic reports and maps. Traffic monitor 406 transmits the reports and maps to wireless telephone 415 and the other mobile communication devices. Traffic monitor 406 could transmit the reports and maps to various locations over Internet 429.
When wireless telephone 415 is within 300 feet of RF transceiver 403, RF transceiver 403 transmits a signal indicating a third beacon identifier to wireless telephone 415. Wireless telephone 415 generates a new random code in response to previously transmitting the first and second messages with the old random code. Wireless telephone 415 then transmits a third message comprising the third beacon identifier, the new random code, and a timestamp to traffic monitor 406 via base station 421 and Internet 429. When wireless telephone 415 is within 300 feet of RF transceiver 404, RF transceiver 404 transmits a signal indicating a fourth beacon identifier to wireless telephone 415. Wireless telephone 415 transmits a fourth message comprising the fourth beacon identifier, the new random code, and a timestamp to traffic monitor 406 via base station 421 and Internet 429. Traffic monitor 406 then generates and transmits velocity reports, volume reports, real-time traffic reports, and maps comprising real-time traffic velocity and volume data to wireless telephone 415 via Internet 429 and base station 421.
The above description and associated figures teach the best mode of the invention. The following claims specify the scope of the invention. Note that some aspects of the best mode may not fall within the scope of the invention as specified by the claims. Those skilled in the art will appreciate that the features described above can be combined in various ways to form multiple variations of the invention. As a result, the invention is not limited to the specific embodiments described above, but only by the following claims and their equivalents.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5790052 | Grabow | Aug 1998 | A |
| 6055434 | Seraj | Apr 2000 | A |
| 6472978 | Takagi et al. | Oct 2002 | B1 |
| 6728629 | Oka et al. | Apr 2004 | B2 |
| 6842620 | Smith et al. | Jan 2005 | B2 |
| 7477903 | Wilcock et al. | Jan 2009 | B2 |
| 20030050754 | Edwards et al. | Mar 2003 | A1 |
| 20030069683 | Lapidot et al. | Apr 2003 | A1 |
| 20030078055 | Smith et al. | Apr 2003 | A1 |
| 20030187571 | Impson et al. | Oct 2003 | A1 |
| 20040049336 | Knockeart et al. | Mar 2004 | A1 |
| 20040149939 | Dickson et al. | Aug 2004 | A1 |
| 20050197767 | Nortrup | Sep 2005 | A1 |
| 20060106530 | Horvitz et al. | May 2006 | A1 |
| 20060187017 | Kulesz et al. | Aug 2006 | A1 |
| 20070027572 | Koyama et al. | Feb 2007 | A1 |
| 20070061155 | Ji et al. | Mar 2007 | A1 |
