US8510025B2 - Method and system for a traffic management network - Google Patents

Method and system for a traffic management network Download PDF

Info

Publication number
US8510025B2
US8510025B2 US12/752,778 US75277810A US8510025B2 US 8510025 B2 US8510025 B2 US 8510025B2 US 75277810 A US75277810 A US 75277810A US 8510025 B2 US8510025 B2 US 8510025B2
Authority
US
United States
Prior art keywords
node
data collection
traffic
traffic data
nodes
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US12/752,778
Other languages
English (en)
Other versions
US20100254282A1 (en
Inventor
Peter Chan
Neal J. Campbell
Tim Courtney
Eric Hauk
Afan Ottenheimer
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Iteris Inc
Original Assignee
TrafficCast International Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US12/752,778 priority Critical patent/US8510025B2/en
Application filed by TrafficCast International Inc filed Critical TrafficCast International Inc
Priority to NZ596146A priority patent/NZ596146A/en
Priority to EP10759461.6A priority patent/EP2415324B1/fr
Priority to AU2010232549A priority patent/AU2010232549B2/en
Priority to CN201080022468.0A priority patent/CN102450085B/zh
Priority to PCT/US2010/029757 priority patent/WO2010115083A2/fr
Assigned to TRAFFICCAST INTERNATIONAL, INC. reassignment TRAFFICCAST INTERNATIONAL, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CAMPBELL, NEAL J., CHAN, PETER, OTTENHEIMER, AFAN, COURTNEY, TIM, HAUK, ERIC
Publication of US20100254282A1 publication Critical patent/US20100254282A1/en
Priority to US13/584,141 priority patent/US9154982B2/en
Publication of US8510025B2 publication Critical patent/US8510025B2/en
Application granted granted Critical
Assigned to FIRST BUSINESS BANK reassignment FIRST BUSINESS BANK SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TRAFFICCAST INTERNATIONAL, INC.
Assigned to FIRST BUSINESS BANK reassignment FIRST BUSINESS BANK SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TRAFFICCAST INTERNATIONAL, INC.
Assigned to ITERIS, INC. reassignment ITERIS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TRAFFICCAST INTERNATIONAL, INC.
Assigned to CAPITAL ONE, NATIONAL ASSOCIATION reassignment CAPITAL ONE, NATIONAL ASSOCIATION SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ITERIS, INC
Assigned to ITERIS, INC. reassignment ITERIS, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: CAPITAL ONE, NATIONAL ASSOCIATION
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
    • G08G1/0116—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from roadside infrastructure, e.g. beacons
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
    • G08G1/012—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from other sources than vehicle or roadside beacons, e.g. mobile networks
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0125—Traffic data processing
    • G08G1/0133—Traffic data processing for classifying traffic situation
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0137—Measuring and analyzing of parameters relative to traffic conditions for specific applications
    • G08G1/0141—Measuring and analyzing of parameters relative to traffic conditions for specific applications for traffic information dissemination
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/052—Detecting movement of traffic to be counted or controlled with provision for determining speed or overspeed
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096708—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
    • G08G1/096716—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information does not generate an automatic action on the vehicle control
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096733—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place
    • G08G1/09675—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place where a selection from the received information takes place in the vehicle
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096766—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission
    • G08G1/096775—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission where the origin of the information is a central station
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies

Definitions

  • the field of the disclosure relates generally to traffic management systems. More specifically, the disclosure relates to a traffic management system that collects information using a network.
  • ISPs information service providers
  • the various types of ISPs include traffic and map systems such as Westwood One, Traffic.com/Navteq, Clear Channel Traffic; portal systems such as Yahoo!, Google, MapQuest/AOL, MicroSoft MSN; wireless carriers such as Verizon Wireless, Cingular Wireless, Sprint Nextel, T-Mobile; telematics and navigation systems—GM OnStar, Ford, Toyota, XM Satellite Radio, Sirius Satellite Radio, Garmin, TomTom, Magellen, Motorola, AAA; and media companies such as NBC, ABC, CBS, etc.
  • traffic and map systems such as Westwood One, Traffic.com/Navteq, Clear Channel Traffic
  • portal systems such as Yahoo!, Google, MapQuest/AOL, MicroSoft MSN
  • wireless carriers such as Verizon Wireless, Cingular Wireless, Sprint Nextel, T-Mobile
  • telematics and navigation systems GM OnStar, Ford, Toyota, XM Satellite Radio, Sirius Satellite Radio, Garmin, TomTom, Magellen, Motorola, AAA
  • media companies such as NBC
  • ISPs attempt to provide route-specific travel time information and dynamic route guidance information to individual users to influence the individual's travel choices including departure time, arrival time, route, destination, etc.
  • An individual traveler relies on the ISP's information and personal experiences and preferences to make individual decisions for their travel choices.
  • the traffic and travel time information can also be used for traffic studies, for monitoring traffic flow, or for detecting accidents.
  • Traffic information is typically collected by closed-circuit video cameras, observers or by axle counters.
  • Video cameras can be used by employees to determine general traffic flow and detect problems like accidents.
  • closed-circuit video systems are expensive to maintain and operate.
  • Observer based studies are comprehensive but expensive to conduct over long periods.
  • Axle counters can be deployed for long periods, but the counters must be collected for processing, Moreover, using current detection methods, travel times are inferred from speed detections which themselves are often derived from vehicle counts, yielding errors of up to 35-40%. Thus, improved systems and methods for collecting traffic data are needed.
  • a representative embodiment relates to a system for collecting vehicular traffic data.
  • the system for collecting vehicular traffic data includes at least one first node, at least one second node, and a central processing station.
  • the first node includes a cellular communications module and a first networking communications module connected to a first processor.
  • the second node includes a second networking communications module and a device detection module connected to a second processor.
  • the at least one first node and the at least one second node form a network.
  • the device detection module detects devices associated with vehicular traffic.
  • the central processing station can be linked to the at least one first node via the cellular communications module.
  • the at least one second node communicates information associated with the devices associated with traffic to the at least one first node.
  • the at least one first node communicates the information associated with the devices associated with traffic to the cellular communications module.
  • the apparatus includes a cellular communications module, a networking communications module, and a device detection module connected to a processor.
  • the device detection module detects devices associated with traffic.
  • the networking communications module communicates information associated with the devices associated with traffic to a central processing station.
  • FIG. 1 is a diagram of a traffic data collection node in accordance with a representative embodiment.
  • FIG. 2 is a diagram of a simplified traffic data collection node in accordance with a representative embodiment.
  • FIG. 3 is a functional diagram of the traffic data collection node of FIG. 1 in accordance with a representative embodiment.
  • FIG. 4 is a diagram of an overview of a traffic data collection node architecture in accordance with a representative embodiment.
  • FIG. 5 is a flowchart of operations performed by a MAC address detector in accordance with a representative embodiment.
  • FIG. 6 is a diagram of a MAC address detection packet in accordance with a representative embodiment.
  • FIG. 7 is a diagram of a cellular packet-based network in accordance with a representative embodiment.
  • FIG. 8 is a diagram of a clustered tree type mesh-cellular packet-based network in accordance with a representative embodiment.
  • FIG. 9 is a diagram of a daisy-chain type mesh-cellular packet-based network in accordance with a representative embodiment.
  • FIG. 10 is a diagram of a traffic management system in accordance with a representative embodiment.
  • FIG. 11 is an illustration of a traffic map in accordance with a representative embodiment.
  • the traffic data collection node 100 includes a computing module 110 , an energy storage device 130 , an energy controller 135 , a solar panel 140 , a Bluetooth antenna 150 , a cellular antenna 160 , and a network antenna 165 .
  • the traffic data collection node 100 can also optionally include a camera 170 , a microphone 180 , and a sensor 190 .
  • the computing module 110 , energy storage device 130 , and energy controller 130 are contained in a protective enclosure 120 .
  • the protective enclosure 120 can be a weatherproof fiberglass enclosure, for instance, a NEMA-4 rated enclosure. Other materials such as steel, plastic, or carbon fiber can be used. Some or all of the components, including the antennas, can be enclosed in the protective enclosure 120 .
  • the protective enclosure 120 can also include a mount for attaching the traffic data collection node 100 to telephone poles, road signs, barriers, etc.
  • the traffic data collection node 100 can be about the size of a brick, or smaller.
  • the traffic data collection node 100 can be deployed temporarily or permanently.
  • the traffic data collection node 100 should be placed within radio frequency (RF) proximity of the travel stream of the devices to be detected.
  • RF radio frequency
  • the traffic data collection node 100 can be attached to any existing structure, pole, or strut.
  • the traffic data collection node 100 can be placed directly on the ground, behind guardrails, or mounted to a post. Placement of the traffic data collection node 100 is limited only by practical concerns of safety and security of roadside equipment.
  • the computing module 110 can be a printed circuit board including processors, memory, input/output modules, hard disk drives, solid state drives, flash memory, transmitters, receivers, controllers, integrated antennas, and slots.
  • the slots can be used to add upgrade modules or other features such as detectors, machine vision processors, and speakers.
  • the computing module 110 can have varying degrees of integration.
  • Energy storage device 130 and solar panel 140 provide power to the traffic data collection node 100 .
  • Energy controller 135 controls recharging of the energy storage device 130 by solar panel 140 ; and regulates power to the computing module 110 and other components of the traffic data collection node 100 .
  • the energy storage device 130 can be a battery, for example a 12V, 20-30 aH lithium ion battery. However, the energy storage device 130 can also be a capacitor, fuel cell, or other energy storage device. Alternatively, power can be provided by a hardwired connection.
  • the solar panel 140 can be of various types and wattages, for example a 5 W or 10 W array.
  • the optional camera 170 can be color, black and white, or infra-red.
  • the camera can be used, for example, to take a snapshot or video of traffic.
  • the optional camera 170 can also include machine vision capabilities such the ability to identify and/or count objects.
  • the camera 170 could be used to identify license plates, a particular license plate, or a particular person.
  • the optional camera 170 can also be programmed to detect traffic jams and accidents.
  • the microphone 180 can be used to detect traffic volume, noise pollution levels, or noise level offenders.
  • the sensor 190 can be a light sensor, inductance sensor, temperature sensor, a global positioning system (GPS) module, biological/nuclear materials sensor or any other kind of sensor.
  • the sensor 190 can also be more than one or an array of sensors.
  • the sensor 190 can be part of a larger grid of sensors used to monitor weather, temperatures in a city, carbon monoxide levels, detect the threat of a biological materials release, or to detect or monitor the transport of other hazardous materials.
  • the Bluetooth antenna 150 , cellular antenna 160 , and network antenna 165 are antennas designed to transmit and receive signals for their corresponding technologies.
  • the cellular antenna 160 can be adapted to communicate with any cellular network.
  • the network antenna 165 is used to connect the traffic data collection node 100 to a network of traffic data collection nodes.
  • the network antenna 165 can be coupled to a ZigBee-type (IEEE 802.15.4) communications module.
  • a satellite transmitter or receiver could be included.
  • a wired network or communications link can be included, such as an Ethernet connection.
  • the traffic data collection node 100 can also include hardware (e.g., Bluetooth antenna 150 and network antenna 165 ) and software configured to connect the traffic data collection node 100 to various networks such as a mobile ad hoc network, a vehicular ad hoc network, an intelligent vehicular ad hoc network, or an internet-based mobile ad-hoc network.
  • a mobile ad hoc network (MANET), sometimes called a mobile mesh network, can be a self-configuring network of mobile devices connected by wireless links.
  • a vehicular ad hoc network (VANETs) can be used for communication among vehicles and between vehicles and roadside equipment.
  • An intelligent vehicular ad hoc network includes artificial intelligence that helps vehicles to behave in intelligent manners during vehicle-to-vehicle collisions, accidents, drunken driving etc.
  • Internet-based mobile ad hoc networks iMANET are MANETs that configure themselves over internet connections, for example, using a cellular network (e.g. using cellular antenna 160 ) internet connection.
  • the traffic data collection node 100 can be part of various network configurations. In one illustrative embodiment, the traffic data collection node 100 can collect information about other nodes, devices, vehicles, etc. that are networked with the traffic data collection node 100 . Alternatively, nodes of the traffic management network can be connected by a hard line such as an Ethernet cable.
  • the traffic data collection node 100 can include an embedded system architecture including custom embedded hardware design coupled with firmware.
  • the traffic data collection node 100 detects Bluetooth devices via the Bluetooth antenna 150 (for example, ver 2.1/2.0/1.2/1.1 and class1/2) of vehicles and pedestrians to provide real-time traffic flow to a central processing center.
  • the traffic data collection node 100 anonymously discovers Bluetooth Media Access Control (MAC) addresses, which serve as a unique identifier to a Bluetooth device.
  • MAC Bluetooth Media Access Control
  • a MAC address is a unique identifier assigned to a network adapter by its manufacturer for identification.
  • MAC addresses are anonymous identifiers.
  • MAC addresses are not associated with any specific user account (as is the case with cell phone probes) or any specific vehicle (as with automated toll tags).
  • the MAC address is not linked to a specific person through any type of central database but is assigned at the Bluetooth electronic chip manufacturer. Additionally, it is difficult to match a MAC address to the purchase of a device by a consumer.
  • the traffic management network thus minimizes, if not eliminates privacy concerns. In general, users concerned with privacy can set options in their Bluetooth device (often under “Discovery Mode” or ‘Visibility’) to ensure that the device will not be detectable.
  • the traffic data collection node 100 After discovering a MAC address, the traffic data collection node 100 places an associated time stamp on the discovered Bluetooth MAC addresses and stores the MAC addresses with time stamps in non-volatile memory. The data can then be sent to a central processing center using a packet-based cellular modem via the cellular antenna 160 . The data can also be passed through a wireless mesh based network via the network antenna 165 , where a central node collects data from a mesh network of traffic data collection nodes. A central traffic data collection node can then pass the data to a central processing center.
  • the traffic data collection node 100 can detect a signal strength of a signal associated with the MAC address.
  • the traffic data collection node 100 can use multiple signal strength measurements to determine the speed and direction of the device associated with the MAC address.
  • the traffic data collection node 100 can collect signal strength data and send it to another device for further processing.
  • traffic data collection node In order to reduce costs and power usage, various implementations of the traffic data collection node are possible. For example, some traffic data collection nodes only require basic features. For example, endpoint node devices could potentially become very simple devices that contain only a Bluetooth radio and a ZigBee radio.
  • the 8-bit microcontroller (used to house the ZigBee stack) that is built into the ZigBee radio can be used as a controller thereby replacing the ARM7 microcontroller in a standard traffic data collection node.
  • a simplified traffic data collection node can utilize a smaller solar panel and battery subsystem. Alternatively, the simplified traffic data collection node could rely solely on solar power.
  • the size and cost of a traffic data collection node can be reduced.
  • the simplified traffic data collection node can also serve as temporary, portable, low cost node.
  • the simplified traffic data collection node 200 can be, for instance, used as an end-node in a traffic data collection network.
  • the simplified traffic data collection node 200 includes a microcontroller 210 , a real-time clock 212 , a memory card 216 , an energy storage device 130 , a Bluetooth module 255 , a Bluetooth antenna 150 , a network module 262 , and a network antenna 165 .
  • the simplified traffic data collection node 200 can also optionally include a sensor 190 .
  • the microcontroller 210 , real-time clock 212 , memory card 216 , energy storage device 130 , Bluetooth module 255 , Bluetooth antenna 150 , network module 262 , and network antenna 165 are contained in a protective enclosure 120 .
  • the microcontroller 210 , real-time clock 212 , memory card 216 , energy storage device 130 , Bluetooth module 255 , Bluetooth antenna 150 , network module 262 , and network antenna 165 can be integrated onto a single printed circuit board including processors, memory, flash memory, transmitters, receivers, controllers, integrated antennas, and slots.
  • the slots can be used to add upgrade modules or other features such as detectors, machine vision processors, and speakers.
  • the simplified traffic data collection node 200 can have varying degrees of integration.
  • the microcontroller 210 and network module 262 can be integrated into the same integrated circuit.
  • the energy storage device 130 can be a battery, for example a 12V, 20-30 aH lithium ion battery.
  • the energy storage device 130 can also include a power supply controller that divides the voltage, for example to 1.8 V and 3.3 V.
  • the simplified traffic data collection node 200 is a low power implementation that can operate using the same battery for about 10 years.
  • sensor 190 can include a camera, a microphone, a global positioning system (GPS) module, a specialized sensor or detector.
  • GPS global positioning system
  • the simplified traffic data collection node 200 can be tailored for a particular implementation of a network.
  • a computing module 110 of the traffic data collection node 100 includes a microcontroller 310 , configuration/user interfaces 320 , monitoring interfaces 330 , a power supply interface 340 , and data communication and transport interfaces 350 . As discussed above, the computing module 110 can have various levels of integration.
  • an energy storage device 130 is integrated onto the printed circuit board of the computing module 110 .
  • the energy storage device 130 is a 6 V DC or 12 V DC battery.
  • the energy storage device 130 provides power to the power supply interface 340 .
  • the power supply interface 340 can be, for example, a switching power supply that converts the voltage of the energy storage device 130 to lower voltages for the components of the computing module 110 .
  • the power supply interface 340 can produce a 1.8 V and 3.3 V source to supply the board.
  • the microcontroller 310 is a processor that controls the traffic data collection node 100 .
  • the microcontroller 310 includes a computer-readable medium such as memory 317 that contains computer-readable instructions for operating the traffic data collection node 100 .
  • Microcontroller 310 executes the instructions for operating the traffic data collection node 100 .
  • memory 317 can be distinct from microcontroller 310 .
  • the microcontroller 310 is clocked by crystal 315 .
  • the microcontroller 310 is also connected to an expansion slot 319 .
  • the expansion slot(s) 319 can be used to add additional capabilities to traffic data collection node 100 ; for example a camera or auxiliary processing module can be added as discussed above.
  • the microcontroller 310 can be, for example, an ARM7 microcontroller such as the ARM7TDMI available from various manufacturers including Taiwan Semiconductor Manufacturing Company in Hsinchu, Taiwan.
  • the ARM7TDMI core is a 32-bit embedded RISC processor delivered as a hard macrocell that provides an acceptable combination of performance, power and area characteristics.
  • the ARM7TDMI core enables system designers to build embedded devices requiring small size, low power and high performance.
  • the ARM7TDMI core contains 128 kB of internal flash memory for firmware storage and 34 kB of internal SRAM for runtime storage.
  • the onboard memory reduces the need for any external discrete memory subsystems that traditional Bluetooth based systems require.
  • the microcontroller 310 interfaces with three subsystems: configuration/user interfaces 320 , monitoring interfaces 330 , and data communication and transport interfaces 350 .
  • the configuration/user interfaces 320 include an input/output interface 322 , a flash card interface 324 , a universal serial bus 326 , and a serial port 328 .
  • the input/output interface 322 can be any kind of communications port.
  • the input/output interface 322 can be a digital output for triggering a camera, a graphics interface, a digital or analog input coupled to a sensor, or an interface to an auxiliary input/output module.
  • the flash card interface 324 includes a flash card such as a MicroSD-type flash card.
  • the flash card interface 324 controls communications between the microcontroller 310 and a flash card.
  • the flash card interface 324 can be used for storing data such as discovered Bluetooth MAC addresses or instructions for operating the traffic data collection node 100 .
  • a MicroSD flash can be used to store a Bluetooth MAC address data and time stamp that can be retrieved later for further processing.
  • a user can retrieve data from the traffic data collection node 100 by removing and reading the flash card.
  • a user can update computer-readable instructions for operating the traffic data collection node 100 by replacing or updating the flash card.
  • the universal serial bus 326 and the serial port 328 can also be used to communicate with the microcontroller 310 .
  • the serial port 328 can be, for instance, a RS-232 or RS-485 type port.
  • the traffic data collection node 100 can be configured and serviced via universal serial bus 326 and/or the serial port 328 .
  • the universal serial bus 326 and the serial port 328 can also be used to attach peripheral devices and sensors such as cameras, temperature sensors, etc. as discussed above.
  • the monitoring interfaces 330 include a real-time clock 332 , a temperature monitor 336 , and an energy source monitor 338 .
  • the real-time clock 332 includes a crystal 331 and a backup battery 335 .
  • the crystal 331 is, for example, an independent local 32.768 khz crystal oscillator.
  • the backup battery 335 is, for example, a 3.3v lithium ion battery that provides power to the real-time clock 332 in the event that main power has been lost or the traffic data collection node 100 requires servicing.
  • Data, time and date stamps produced by the microcontroller 310 are maintained via the real-time clock 332 , which is clocked from the crystal 331 to reduce any potential clock integrity problems.
  • Firmware also provides the ability to synchronize the time and date of the real-time clock 332 with a remote network time-date server. As a result, time and date accuracy is maintained to insure accurate speed calculation.
  • the temperature monitor 336 monitors the internal temperature of the traffic data collection node 100 .
  • the temperature monitor 336 includes a temperature sensor or sensors. Data from the temperature monitor 336 are passed to the microcontroller 310 using, for example, a serial peripheral interface bus. The temperature data can then be sent to a central processing center for analysis.
  • the energy source monitor 338 can be, for example, a battery monitor.
  • the energy source monitor 338 monitors energy storage device 130 , for instance, a battery.
  • the energy source monitor 338 can be implemented as an 8-bit analog to digital converter built into the microcontroller 310 .
  • the battery health data can then be sent to a central processing center for analysis.
  • the energy storage device 130 is a fuel cell
  • the energy source monitor 338 can send a low fuel warning to the central processing center.
  • the data communication and transport interfaces 350 include a cellular modem 390 , a Bluetooth module 380 , a network module 370 , and an Ethernet module 360 .
  • the cellular modem 390 transmits and receives data from the microcontroller 310 via a cellular antenna 160 .
  • the cellular modem 390 can be a CDMA/GSM wireless module.
  • the cellular modem 390 enables communication between the traffic data collection node 100 and a central processing center.
  • the traffic data collection node 100 can send and receive data packets to and from the central processing center using a cellular phone network; thus, the traffic data collection node 100 does not have to be hardwired in order to collect and report data.
  • any computer can communicate with the traffic data collection node 100 via the packet-based cellular phone network.
  • the cellular modem 390 can also be used to remotely update the computer-readable instructions for operating the traffic data collection node 100 .
  • an over-the-air protocol can be used to reflash the software.
  • the cellular antenna 160 can be internal, integrated or external.
  • the cellular modem 390 connects to a GPRS/EDGE wide area network thus providing a robust data collection capability. Standardized cellular components can be used to create low-power and low-maintenance devices.
  • the Bluetooth module 380 primarily receives but can also transmit data from the microcontroller 310 via a Bluetooth antenna 150 .
  • the Bluetooth module 380 can be, for example, a BlueTooth Class 1 and/or Class 2 module, BlueCore4IC available from CSR, plc. of Cambridge, England.
  • the Bluetooth module 380 contains a 2.4 GHz Bluetooth radio, a Bluetooth baseband digital signal processor (DSP), and a Bluetooth firmware based stack implemented in an 8-bit microcontroller.
  • the microcontroller 310 interfaces to Bluetooth module 380 via a serial universal asynchronous receiver/transmitter (UART) interface.
  • the Bluetooth module 380 has the ability to perform Bluetooth device inquiries.
  • the microcontroller 310 can command the Bluetooth module 380 to perform a device inquiry.
  • the Bluetooth module 380 returns the Bluetooth devices discovered in real-time to the microcontroller 310 to be recorded and logged to the flash card mounted at the flash card interface 324 .
  • the Bluetooth module 380 can discover the MAC address of the car's Bluetooth transponder and return the MAC address to the microcontroller 310 .
  • the microcontroller 310 time stamps the MAC address and saves the data to a flash card mounted at the flash card interface 324 .
  • other devices can be detected, for example, the module can be designed to probe for Wi-Fi devices, cell phones, satellite phones, or any other device that transmits a unique or pseudo-unique discovery signal or that responds to wireless inquiries.
  • the network module 370 transmits and receives data from the microcontroller 310 via a network antenna 165 .
  • the network module 370 allows the traffic data collection node 100 to form a network with other traffic data collection nodes and other simplified traffic data collection nodes.
  • the network can be, for instance, a mesh network. Alternatively, other network configurations can be used.
  • the network module 370 is a ZigBee (IEEE 802.15.4) transponder operating on the 900 MHz Industrial-Scientific-Medical (ISM) band.
  • ZigBee mesh networking allows for linked data hops between receivers (traffic data collection nodes).
  • ZigBee is a low-cost, low-power, wireless mesh networking standard. The low cost allows the technology to be widely deployed in wireless control and monitoring applications, the low power-usage allows longer life with smaller batteries, and the mesh networking provides high reliability and larger range.
  • the traffic data collection node 100 can pass data to and from other the traffic data collection nodes.
  • other nodes can pass their data through the network to the central node for upload to a central processing center.
  • the number of nodes requiring an expensive cellular modem is substantially reduced.
  • the Ethernet module 360 transmits and receives data from the microcontroller 310 via a hardline such as a Cat-5 cable.
  • a hardline such as a Cat-5 cable.
  • the Ethernet module 360 enables communication between the traffic data collection node 100 and a central processing center.
  • any computer can communicate with the traffic data collection node 100 when the Ethernet module 360 is connected to an Internet access point.
  • the Ethernet module 360 can also be used to update (remotely or onsite) the computer-readable instructions for operating the traffic data collection node 100 .
  • the Ethernet module 360 can be replaced with a weatherproof coaxial-based hardline communications connection; for example, the traffic data collection node 100 can be connected to a cable television network or phone line.
  • the basic functions of the traffic data collection node can be executed by firmware.
  • FIG. 4 a diagram of an overview of a traffic data collection node architecture in accordance with a representative embodiment is shown.
  • the architecture of the traffic data collection node includes a hardware layer 410 , a hardware abstraction layer 420 , a real-time operating system (RTOS) layer 430 and an application layer 440 .
  • the hardware layer 410 represents the physical implementation of the traffic data collection node as discussed above.
  • the RTOS layer 430 consumes about ⁇ 50 kB of flash memory and 32 kB of runtime memory.
  • a hardware abstraction layer 420 is between the hardware layer 410 and the RTOS layer 430 that allows the real-time operating system to communicate with the hardware using device drivers.
  • the application layer 440 includes the following application components: a system health monitor 450 , a MAC address logger 460 , a MAC address detector 470 , a configuration interface 480 , and a data transport interface 490 .
  • the system health monitor 450 monitors the health of the system and signals an alert when the health of the system in danger, for instance, when the battery is about to die or when the system is overheating.
  • the MAC address detector 470 interacts with the driver (in the hardware abstraction layer 420 ) for the Bluetooth module and detects the MAC address of a device, such as a device in a car.
  • the MAC address detector 470 notifies the MAC address logger 460 that it transferred a new MAC address element to the MAC address logger 460 .
  • the MAC address logger 460 records MAC addresses detected along with an associated time stamp.
  • the configuration interface 480 handles the user configuration dialogs that occur over the driver (in the hardware abstraction layer 420 ) that handles the universal serial bus and the serial port.
  • the data transport interface 490 is responsible for handling the cellular modem, the network module, and the Ethernet module.
  • a flowchart of the operations performed by a MAC address detector in accordance with a representative embodiment is shown. Additional, fewer or different operations may be performed.
  • the MAC address detector initializes and begins the process of looking for Bluetooth devices.
  • the MAC address detector sends an inquiry command to a Bluetooth module of a traffic data collection node via a Bluetooth module device driver which is part of the hardware abstraction layer.
  • the MAC address detector 470 can look for Bluetooth devices periodically or look for Bluetooth devices as soon as resources are available. Alternatively, the MAC address detector 470 can change the rate it looks for Bluetooth devices based on time of date and prior results; thus, saving power.
  • the inquiry command orders the Bluetooth module to detect any discoverable Bluetooth devices within the range of the Bluetooth module's 2.4 GHz radio transceiver, which for class 1 devices is about 100 meters and for class 2 devices is about 10 meters.
  • the Bluetooth module attempts to find Bluetooth devices.
  • the Bluetooth module using its own hardware stack, operates independently of the microcontroller. When the Bluetooth module has a result, it interrupts the microcontroller.
  • an interrupt service routine operation 540 the real-time operating system services the interrupt and forwards the result to the MAC address detector.
  • the interrupt service routine operation 540 is preferably a high priority interrupt service routine. If the Bluetooth module did not find any Bluetooth devices, the MAC address detector returns to operation 520 . However, if a Bluetooth device is found, in a time stamp and data log operation 550 , the MAC address detector forwards the detected MAC addresses to the MAC address logger which then appends a time stamp to the detected MAC addresses and saves the data to a flash card.
  • the MAC address logger assembles the MAC address detection packet 600 and saves the MAC address detection packet 600 to the flash card.
  • the MAC address detection packet 600 includes a traffic data collection node id 610 , a detected address 620 , a time stamp 630 , and a checksum 640 .
  • the MAC address detection packet 600 can be any length, for example, 16 bytes.
  • the traffic data collection node id 610 is the 24 bit MAC address of the traffic data collection node that detected the Bluetooth device.
  • the detected address 620 is the 24 bit MAC address detected by the MAC address detector.
  • the time stamp 630 is the date, year, and time associated with the detection of the detected address 620 .
  • the checksum 640 is the checksum of the MAC address detection packet 600 .
  • the MAC address detection packet 600 can also include other fields such as data type, extension fields, destination address, and control flags.
  • the MAC address detection packet 600 can be encrypted and include features such as forward error correction.
  • a traffic data collection node When monitoring a road, a traffic data collection node will probably detect one MAC address per minute on average. Hence, the traffic data collection node accumulates about 16 bytes of data per minute, or about 960 bytes per hour, or about 23 Kbytes per day. Data from a traffic data collection node can be sent to the central processing center about once every 5 minutes with about a 80 byte payload.
  • a traffic management network includes a plurality of traffic data collection nodes.
  • the plurality of traffic data collection nodes of the traffic management network monitor and measure vehicular and pedestrian flows by measuring anonymous Bluetooth Media Access Control (MAC) addresses.
  • the plurality of traffic data collection nodes collect MAC addresses from mobile devices such as headsets and in-dash sync services in cars.
  • a MAC address is a unique identifier assigned to a network adapter by its manufacturer for identification.
  • the data generated using the traffic management network can be used to calculate high quality, high density travel times by sampling a portion of actual travel times from a traffic stream.
  • computers at a central processing station of the traffic management network match detected MAC addresses.
  • the matched MAC addresses have respective time stamps.
  • computers at the central processing station can determine the speed and direction of the device associated with the MAC address.
  • the traffic management network can be arranged in two configurations: a cellular packet-based network or a mesh-cellular packet-based network. Various combinations of the two approaches is possible. Alternatively, other networking configurations can be employed.
  • each traffic data collection node has a packet-based cellular modem (GSM or CDMA) which provides the individual traffic data collection nodes with Internet protocol (IP) based connectivity over a point-to-point-protocol (PPP) cellular link.
  • GSM packet-based cellular modem
  • IP Internet protocol
  • PPP point-to-point-protocol
  • a central processing center has the capability to communicate with each traffic data collection node “directly” over a standard TCP/IP based communication link.
  • a traffic data collection node can be a coordinator, router, or end-point device.
  • Coordinators collect data packets from other traffic data collection nodes in the traffic management network.
  • the coordinators send the data packets to a central processing server via a cellular packet-based modem, which provides the coordinator node with IP-(internet protocol) based connectivity over a point-to-point-protocol (PPP) cellular link.
  • Routers pass along data packets from other traffic data collection nodes in the traffic management network. End-points only send data packets to other traffic data collection nodes.
  • the cellular packet-based network 700 monitors, for example, traffic on a road 710 .
  • Traffic data collection nodes 732 , 734 , 736 and 738 are located near the road 710 so that when a vehicle 720 passes, the traffic data collection nodes 732 , 734 , 736 and 738 can detect a discoverable MAC address.
  • Each of the traffic data collection nodes 732 , 734 , 736 and 738 is wirelessly connected to one of cellular base stations 742 , 744 or 746 .
  • the cellular base stations 742 , 744 and 746 are connected to Internet 750 .
  • a central processing station 770 is also connected to the Internet 750 .
  • the traffic data collection nodes 732 , 734 , 736 and 738 pass collected data to the central processing station 770 using IP packets.
  • Each of the traffic data collection nodes 732 , 734 , 736 and 738 is assigned a static IP address. Alternatively, the nodes can be assigned an IP address dynamically using Dynamic Host Configuration Protocol (DHCP).
  • DHCP Dynamic Host Configuration Protocol
  • the traffic data collection nodes 732 , 734 , 736 and 738 When the traffic data collection nodes 732 , 734 , 736 and 738 are initialized, they each form a point-to-point-protocol (PPP) cellular link to the central processing station 770 . Since, each of the traffic data collection nodes 732 , 734 , 736 and 738 has its own link to the central processing station 770 , the nodes can be placed as far apart as desired. The nodes can periodically or continuously upload data to the central processing station 770 .
  • PPP Point-to-
  • Each of the nodes communicates to the central processing station 770 independently, though the central processing station 770 can coordinate data collection and other activities amongst the nodes. For example, when the vehicle 720 passes traffic data collection node 732 , traffic data collection node 732 detects the MAC address of vehicle 720 . Traffic data collection node 732 time stamps and stores the data as a MAC address detection packet. Traffic data collection node 732 then sends an IP packet, addressed to the central processing station 770 and containing MAC address detection packet, to the base station 742 . The IP packet may contain many MAC address detection packets. The base station 742 routes the IP packet to the Internet 750 . The IP packet arrives at the central processing station 770 . The central processing station 770 un-encapsulates the IP packet and processes the MAC address detection packet.
  • traffic data collection node 738 detects the MAC address of vehicle 720 .
  • Traffic data collection node 738 time stamps and stores the data as a MAC address detection packet.
  • Traffic data collection node 738 then sends an IP packet, addressed to the central processing station 770 and containing MAC address detection packet, to the base station 746 .
  • the IP packet may contain many MAC address detection packets.
  • the base station 746 routes the IP packet to the Internet 750 .
  • the IP packet arrives at the central processing station 770 .
  • the central processing station 770 un-encapsulates the IP packet and processes the MAC address detection packet.
  • each of the traffic data collection nodes 732 , 734 , 736 and 738 has its own link to the central processing station 770 .
  • the mesh-cellular packet-based network can take various forms, for instance, a clustered tree type configuration or a daisy-chain type configuration.
  • the mesh-cellular packet-based network reduces the number of cellular modems needed for communicating with the central processing station thereby reducing hardware costs and usage fees.
  • the traffic management network can be a clustered tree type configuration including coordinator nodes, router nodes, and endpoint nodes.
  • the traffic management network can be a daisy-chained type configuration including mostly coordinator nodes and router nodes.
  • the traffic data collection nodes of the clustered tree type mesh-cellular packet-based network 800 can be a coordinator node 810 , a router node 820 , 822 , 824 and 826 , or an end-point node 830 , 834 and 836 . All of the nodes can have the ability to detect BlueTooth addresses.
  • the coordinator node 810 is logically central to the network or sub-network and stores all information about the mesh network.
  • the coordinator node 810 can have a communication link, for example, a ZigBee-based networking link, to router nodes or end-point nodes.
  • the coordinator node 810 can be, for example, a traffic data collection node as described above.
  • the coordinator node 810 can preprocess data and perform local analysis on data points.
  • the coordinator node 810 and associated router nodes or end-point nodes can be spaced about 0.2 to 1 mile apart. In FIG. 8 , the coordinator node 810 has direct wireless connections to four router nodes 822 , 826 and 820 .
  • the coordinator node 810 is wirelessly connected to a cellular base station 840 .
  • the cellular base station 840 is connected to Internet 750 .
  • a central processing station 770 is also connected to the Internet 750 .
  • the coordinator node 810 passes collected data to the central processing station 770 using IP packets.
  • the coordinator node 810 is assigned a static IP address. Alternatively, a coordinator node can be assigned an IP address dynamically using DHCP.
  • PPP point-to-point-protocol
  • the router nodes 820 , 822 , 824 and 826 serve as intermediate nodes and are responsible for passing data to and from coordinator nodes, other router nodes, and endpoint nodes over a communication link, for example, a ZigBee based networking link.
  • the router nodes 820 , 822 , 824 and 826 can preprocess data and perform local analysis on data points. Some router nodes also contain the capability of utilizing a cellular packet-based modem to alert a central processing server 770 that a coordinator node has failed or is unreachable.
  • the router nodes 820 , 822 , 824 and 826 can be, for example, a traffic data collection node as described above.
  • the router nodes 820 , 822 , 824 and 826 and associated router nodes or end-point nodes can be spaced about 0.2 to 1 mile apart.
  • the end-point nodes 830 , 834 and 836 can contain just enough functionality to communicate with a single coordinator node or a single router node over a communication link, for example, a ZigBee based networking link.
  • the end-point nodes 830 , 834 and 836 can be, for example, a simplified traffic data collection node as described above.
  • the end-point nodes 830 , 834 and 836 pass data to the router nodes 820 , 822 , 824 and 826 or the coordinator node 810 .
  • the end-point nodes 830 , 834 and 836 can preprocess data and perform local analysis on data points.
  • end-point nodes 830 , 834 and 836 provide the ability to place a low-cost, low-powered simplified traffic data collection node in an urban city-type environment to provide high traffic resolution in an area where roads may be tightly clustered together.
  • the clustered tree type mesh-cellular packet-based network 800 can be self-forming and self-healing.
  • the coordinator node 810 , the router nodes 820 , 822 , 824 and 826 , and end-point nodes 830 , 834 and 836 are activated, they all attempt to self-form a mesh network by building links to each other.
  • the end-point nodes 830 , 834 and 836 attach to one of the router nodes 820 , 822 , 824 and 826 , for instance, whichever router node provides the best network connection.
  • the coordinator node 810 and the router nodes 820 , 822 , 824 and 826 attempt to build links to each other.
  • the clustered tree type mesh-cellular packet-based network 800 attempts to reduce the number of active cellular modems in the system while still maintaining adequate data bandwidth. Hence, the clustered tree type mesh-cellular packet-based network 800 can have more than one coordinator node. The clustered tree type mesh-cellular packet-based network 800 can re-link in order to balance data loads. Additionally, if the links in the clustered tree type mesh-cellular packet-based network 800 fail or become weak, the clustered tree type mesh-cellular packet-based network 800 self-heals when the nodes form new links or paths between each other that avoid the failing node or weak link.
  • the clustered tree type mesh-cellular packet-based network 800 monitors, for example, traffic on a road 710 .
  • the coordinator node 810 , the router nodes 820 , 822 , 824 and 826 , and the end-point nodes 830 , 834 and 836 are mostly located near the road 710 so that when a vehicle 720 passes, the coordinator node 810 , the router nodes 820 , 822 , 824 and 826 , and the end-point nodes 830 , 834 and 836 can detect a discoverable MAC address.
  • the end-point node 834 detects the MAC address of vehicle 720 .
  • the end-point node 834 time stamps and stores the data as a first MAC address detection packet.
  • the end-point node 834 sends the MAC address detection packet to router node 824 ; however, the end-point node 834 may only pass data to its associated router periodically.
  • Router node 824 sends the first MAC address detection packet to router node 822 .
  • Router node 822 sends the first MAC address detection packet to coordinator node 810 .
  • the coordinator node 810 then sends an IP packet, addressed to the central processing station 770 and containing the first MAC address detection packet, to the base station 840 .
  • the IP packet may contain many MAC address detection packets from various router nodes and end point nodes.
  • the base station 840 routes the IP packet to the Internet 750 .
  • the IP packet arrives at the central processing station 770 .
  • the central processing station 770 un-encapsulates the IP packet and processes the first MAC address detection packet.
  • the end-point node 836 detects the MAC address of vehicle 720 .
  • the end-point node 836 time stamps and stores the data as a second MAC address detection packet.
  • the end-point node 836 sends the second MAC address detection packet to router node 826 ; however, the end-point node 836 may only pass data to its associated router periodically.
  • Router node 826 sends the second MAC address detection packet to coordinator node 810 .
  • the coordinator node 810 then sends an IP packet, addressed to the central processing station 770 and containing the second MAC address detection packet, to the base station 840 .
  • the IP packet may contain many MAC address detection packets from various router nodes and end point nodes.
  • the base station 840 routes the IP packet to the Internet 750 .
  • the IP packet arrives at the central processing station 770 .
  • the central processing station 770 un-encapsulates the IP packet and processes the second MAC address detection packet.
  • the central processing station 770 can analyze the first MAC address detection packet and the second MAC address detection packet. For example, the central processing station 770 can use the data to monitor or analyze traffic conditions. In particular, the speed of the vehicle 720 can be calculated by knowing the positions of end-point node 834 and end-point node 836 and the time difference of the time stamps recorded the first MAC address detection packet and the second MAC address detection packet. The positions of end-point node 834 and end-point node 836 can be determined and recorded at installation, determined by global positioning system (GPS) modules included in the nodes, or determined using triangulation techniques in combination with the cellular network.
  • GPS global positioning system
  • the traffic data collection nodes of the daisy-chain type mesh-cellular packet-based network 900 can be a coordinator node 810 , a router node 920 , 921 , 922 , 923 , 924 , 925 , 926 , 927 and 929 , or an end-point node (not shown). All of the nodes can have the ability to detect BlueTooth addresses.
  • the coordinator node 810 is logically central to the network or sub-network and stores all information about the mesh network.
  • the coordinator node 810 can have a communication link, for example, a ZigBee based networking link, to router nodes or end-point nodes.
  • the coordinator node 810 can be, for example, a traffic data collection node as described above.
  • the coordinator node 810 can preprocess data and perform local analysis on data points.
  • the coordinator node 810 and associated router nodes or end-point nodes can be spaced about 0.2 to 1 mile apart.
  • the coordinator node 810 can be linked to more than one daisy chain. For example, coordinator node 810 is linked to the daisy chain associated with Highway ‘A’ 910 and the daisy chain associated with Highway ‘B’ 915.
  • the coordinator node 810 is wirelessly connected to a cellular base station 840 .
  • the cellular base station 840 is connected to Internet 750 .
  • a central processing station 770 is also connected to the Internet 750 .
  • the coordinator node 810 passes collected data to the central processing station 770 using IP packets.
  • the coordinator node 810 is assigned a static IP address. Alternatively, a coordinator node can be assigned an IP address dynamically using DHCP.
  • PPP point-to-point-protocol
  • the router nodes 920 , 921 , 922 , 923 , 924 , 925 , 926 , 927 and 929 serve as intermediate nodes and are responsible for passing data to and from coordinator nodes, other router nodes, and endpoint nodes over a communication link, for example, a ZigBee based networking link.
  • the router nodes 920 , 921 , 922 , 923 , 924 , 925 , 926 , 927 and 929 can preprocess data and perform local analysis on data points.
  • Some router nodes also contain the capability of utilizing a cellular packet-based modem to alert a central processing server 770 that a coordinator node has failed or is unreachable.
  • the router nodes 920 , 921 , 922 , 923 , 924 , 925 , 926 , 927 and 929 can be, for example, a traffic data collection node as described above.
  • the router nodes 920 , 921 , 922 , 923 , 924 , 925 , 926 , 927 and 929 and associated router nodes or end-point nodes can be spaced about 0.2 to 1 mile apart.
  • router nodes 924 and 929 are child router nodes. Router nodes 924 and 929 are intermediate nodes for the rest of the nodes in the daisy-chained configuration. Router nodes 924 and 929 can also backup the coordinator node 810 is case of failure by becoming coordinator nodes.
  • the daisy-chain type mesh-cellular packet-based network 900 is self-forming and self-healing.
  • the coordinator node 810 , and the router nodes 920 , 921 , 922 , 923 , 924 , 925 , 926 , 927 and 929 (and any end-point nodes) are activated, they all attempt to self-form a mesh network by building links to each other.
  • the coordinator node 810 and the router nodes 920 , 921 , 922 , 923 , 924 , 925 , 926 , 927 and 929 attempt to build links to each other.
  • the central processing station 770 can also direct the nodes to form a specific network configuration based on the node location, maps, predicted demand, etc.
  • the daisy-chain type mesh-cellular packet-based network 900 attempts to reduce the number of active cellular modems in the system while still maintaining adequate data bandwidth. Hence, the daisy-chain type mesh-cellular packet-based network 900 can have more than one coordinator node. The daisy-chain type mesh-cellular packet-based network 900 can re-link in order to balance data loads. Additionally, if the links in the daisy-chain type mesh-cellular packet-based network 900 fail or become weak, the daisy-chain type mesh-cellular packet-based network 900 self-heals when the nodes form new links or paths between each other that avoid the failing node or weak link.
  • the daisy-chain type mesh-cellular packet-based network 900 monitors, for example, traffic on Highway ‘A’ 910 .
  • the coordinator node 810 , the router nodes 921 , 922 , 923 , 924 , 925 , 926 and 927 are mostly located near Highway ‘A’ 910 so that when a vehicle 720 passes, the coordinator node 810 and the router nodes 921 , 922 , 923 , 924 , 925 , 926 and 927 can detect a discoverable MAC address.
  • the router node 921 detects the MAC address of vehicle 720 .
  • the router node 921 time stamps and stores the data as a first MAC address detection packet.
  • the router node 921 sends the MAC address detection packet to router node 922 ; however, the router node 921 may only pass data to its associated router periodically.
  • Router node 922 sends the first MAC address detection packet to router node 923 .
  • Router node 923 sends the first MAC address detection packet to router node 924 , which is a child router node.
  • Router node 924 sends the first MAC address detection packet to coordinator node 810 .
  • the coordinator node 810 then sends an IP packet, addressed to the central processing station 770 and containing the first MAC address detection packet, to the base station 840 .
  • the IP packet may contain many MAC address detection packets from various router nodes and end point nodes.
  • the base station 840 routes the IP packet to the Internet 750 .
  • the IP packet arrives at the central processing station 770 .
  • the central processing station 770 un-encapsulates the IP packet and processes the first MAC address detection packet.
  • the router node 927 detects the MAC address of vehicle 720 .
  • the router node 927 time stamps and stores the data as a second MAC address detection packet.
  • the router node 927 sends the second MAC address detection packet to router node 926 ; however, the router node 927 may only pass data to its associated router periodically.
  • Router node 926 sends the second MAC address detection packet to router node 925 .
  • Router node 925 sends the second MAC address detection packet to router node 924 , which is a child router node.
  • Router node 924 sends the second MAC address detection packet to coordinator node 810 .
  • the coordinator node 810 then sends an IP packet, addressed to the central processing station 770 and containing the second MAC address detection packet, to the base station 840 .
  • the IP packet may contain many MAC address detection packets from various router nodes and end point nodes.
  • the base station 840 routes the IP packet to the Internet 750 .
  • the IP packet arrives at the central processing station 770 .
  • the central processing station 770 un-encapsulates the IP packet and processes the second MAC address detection packet.
  • the central processing station 770 can analyze the first MAC address detection packet and the second MAC address detection packet. For example, the central processing station 770 can use the data to monitor or analyze traffic conditions. In particular, the speed of the vehicle 720 can be calculated by knowing the positions of router node 921 and router node 927 and the time difference of the time stamps recorded the first MAC address detection packet and the second MAC address detection packet. The positions of router node 921 and router node 927 can be determined and recorded at installation, determined by global positioning system (GPS) modules included in the nodes, or determined using triangulation techniques in combination with the cellular network.
  • GPS global positioning system
  • the traffic management network enables measurement of travel time and average vehicle speed with increased accuracy.
  • Road speed is derived from travel times and accuracy is assured from the volume of Bluetooth MAC addresses collected.
  • the origins and destinations (O-Ds) of BlueTooth devices associated with a moving object can be accurately measured at a reduced cost and with a larger sample size than possible using traditional methods.
  • Bluetooth traffic monitoring is economical than closed-circuit video cameras, observers or axle counters on a cost per data point basis.
  • the traffic management network can enable the mapping of information on routing decisions. Tracking Bluetooth MAC addresses can identify trends in how and when drivers select their route options. Computers at the central processing station can use information provided by the traffic management network to track travel times, originations and destinations for a variety of modes of transportation (vehicles, rail, and pedestrian) on freeways, arterials and sidewalks (since the Bluetooth devices are associated with people rather than vehicles).
  • the traffic management system 1000 can include a network 1015 , nodes 1010 , a cellular base station 1017 , Internet 1035 , a central processing station 1037 , and an application server 1060 .
  • the nodes 1010 can be located along or near a road 1022 .
  • Road 1022 can include, for example, on-ramp 1025 and off-ramp 1020 .
  • Road 1022 can also include a first signage 1045 , a second signage 1047 , and a traffic light 1055 .
  • the first signage 1045 and the second signage 1047 can be a traffic sign, a message board, a traffic signal, or an electronic billboard.
  • the nodes 1010 anonymously discover, for example, Bluetooth MAC addresses, as described above.
  • the particular node attempts to collect MAC addresses of wireless devices in the vehicle 1027 .
  • the nodes 1010 can collect the MAC addresses of cell phone 1040 and navigation device 1042 which are in vehicle 1027 .
  • the navigation device 1042 can be a global positioning satellite (GPS) unit that matches the unit's location to a map.
  • the nodes 1010 can be connected to the network 1015 , as described above.
  • the network 1015 can be a daisy-chain type mesh-cellular packet-based network, a clustered tree type mesh-cellular packet-based network, an Ethernet network, or any other network.
  • One or many of the nodes 1010 can be communicatively coupled to cellular base station 1017 .
  • each node 1010 can be communicatively coupled to cellular base station 1017 .
  • other devices such as first signage 1045 can also be connected to network 1015 .
  • the MAC addresses of the cell phone 1040 and navigation device 1042 can collected by nodes 1010 , be time stamped, and sent to central processing station 1037 through network 1015 , cellular base station 1017 and Internet 1035 , as discussed above.
  • the central processing station 1037 can use the MAC addresses, node locations, and time stamps to determine travel time, vehicle speed, and vehicle direction (directionality), as discussed above.
  • various conditions of the road can be determined such as traffic congestion and traffic speed.
  • the central processing station 1037 can determine that vehicles are not moving if the nodes 1010 do not detect progression of the cell phone 1040 and navigation device 1042 or that vehicles are moving too slowly if the time the cell phone 1040 and navigation device 1042 take to pass successive nodes implies traffic has slowed.
  • Information about vehicle travel time, vehicle speed, and vehicle direction can be shared with an application server 1060 over Internet 1035 .
  • the application server 1060 can be operated by a third party.
  • the application server 1060 can be used to aggregate traffic data, analyze traffic data, and provide enhanced services based on the traffic data.
  • the central processing station 1037 can pass vehicle travel time, vehicle speed, and vehicle direction associated with the crash 1030 to application server 1060 . Additional information can also be included such as an indication that the crash 1030 has occurred.
  • the application server 1060 can provide information to drivers regarding the crash 1030 .
  • the application server 1060 can send a message to first signage 1045 , via network 1015 , instructing the first signage 1045 to display a message such as “Accident Ahead. Please slow down.”
  • application server 1060 can reroute traffic.
  • the application server 1060 can send a message to second signage 1047 , via Internet 1035 , instructing the second signage 1047 to display a message such as “Accident Ahead. Temporary Detour. Please Exit” which causes drivers to take off-ramp 1020 , thereby decongesting the road 1022 .
  • the application server 1060 can also cause other signage to display driving instructions to complete a detour route.
  • the application server 1060 can send an email or text message describing the traffic conditions to cell phone 1040 .
  • the nodes 1010 can also send information, such as the accident warning, back to the cell phone 1040 and navigation device 1042 via network 1015 (e.g. over the Bluetooth link). For instance, users could register for a service that allows the nodes 1010 to pair with their Bluetooth devices.
  • application server 1060 can stop traffic from entering the road 1022 .
  • application server 1060 can send a message to a Department of Transportation (DOT) traffic management server 1050 , via Internet 1035 , informing the DOT that an accident has occurred at the location of crash 1030 .
  • the DOT traffic management server 1050 can control traffic light 1055 to prevent more vehicles from entering the on-ramp 1025 , thereby decongesting the road 1022 .
  • the application server 1060 and the DOT traffic management server 1050 can use the vehicle travel time, vehicle speed, and vehicle direction to deploy resources such as police, road crews, ambulances, plows, etc.
  • information regarding traffic conditions can be compiled for various end users.
  • application server 1060 can determine current or historical travel times for roads.
  • FIG. 11 an illustration of a traffic map 1110 in accordance with a representative embodiment is shown.
  • the traffic map 1110 can show a road system 1120 for a city (depicted as “Big City”).
  • the application server can use vehicle travel time, vehicle speed, and vehicle direction in combination with maps and posted speed limits to generate traffic map 1110 .
  • Traffic map 1110 can show the congestion of road system 1120 .
  • traffic map 1110 can show areas of light congestion 1130 , medium congestion 1140 , and high congestion 1150 .
  • Traffic map 1110 can show accident 1160 .
  • Information regarding the accident 1160 such as location, severity, and driver instructions, can be determined by the application server 1060 or provided by another source such as the DOT.
  • travel times 1170 can be calculated and displayed.
  • the traffic map 1110 can also display the location of certain vehicles.
  • the MAC address of a wireless device associated with a known vehicle 1180 can be stored by the application server 1060 .
  • MAC addresses are anonymous. However, if a user chooses to register the MAC address of his device with a database, the device (and the associated person or vehicle) can then be tracked.
  • the known vehicle 1180 passes a node 1010
  • the MAC address associated with the known vehicle 1180 , node identifier, and a time stamp can be sent to the central processing station 1037 for processing and then to application server 1060 .
  • the application server 1060 can match the MAC address with an identifier of the known vehicle 1180 .
  • MAC address “01:23:45:67:89:ab” could be associated with “city snow plow 19 .”
  • the map can display the location of “city snow plow 19 .”
  • a city can track its snow plows and manage resources, for instance, a manager can easily determine what roads have been plowed and need to be plowed.
  • any other vehicle can be matched with a particular MAC address.
  • police cars, ambulances, road crews, fleets of trucks, and/or employees can be associated with a MAC address and later tracked.
  • parents could track the location of their children by registering the MAC address of a child's cell phone in a database. When a teenager is out driving, the MAC address of the child's cell phone will be detected by nodes.
  • the application server 1060 can match the stored MAC address of the child's cell phone with incoming node data. When the application server 1060 detects a match, the application server 1060 can report the location of the child based on the detection at the node. Similarly, a parent can also monitor a child's driving speeds and travel habits.
  • traffic information such as the traffic map
  • the traffic information can be displayed and/or analyzed on a computer 1070 , a smart phone 1075 , the cell phone 1040 , or the navigation device 1042 .
  • the traffic information can be combined with other sources of information such as weather, news, resource deployment, and personal data (e.g. travel plans).
  • the navigation device 1042 can use the traffic information provided by application server 1060 to reroute travel plans entered by the user.
  • a user can check a website including the traffic map of FIG. 11 before leaving for work using the computer 1070 or smart phone 1075 .
  • users of the traffic management system can quickly receive and/or obtain current traffic information in order to adapt to changing road conditions.
  • a traffic management system can also monitor pedestrian traffic.
  • a traffic management system can be used to monitor congestion in a terminal such as an airport.
  • a traffic management system can be used to serve individualized advertisements using available signage.
  • a vehicle, or groups of vehicles, associated with a MAC address(es) that has not “stopped” for many hours may be targeted with a food advertisement sent to a nearby electronic billboard.
  • an application server can send an individualized advertisement to the billboard for display.
  • an individualized advertisement can be sent to a cell phone, navigation device, etc. based on the location of a node that detects the registered MAC address.
  • advertisers such as truck stops can send advertisements targeted to a profile of a user with a registered MAC address as the user passes near a specific location. For instance, the advertisement could be sent as the vehicle approaches the truck stop.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Chemical & Material Sciences (AREA)
  • Analytical Chemistry (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Atmospheric Sciences (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Traffic Control Systems (AREA)
US12/752,778 2009-04-02 2010-04-01 Method and system for a traffic management network Active 2032-03-02 US8510025B2 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
US12/752,778 US8510025B2 (en) 2009-04-02 2010-04-01 Method and system for a traffic management network
NZ596146A NZ596146A (en) 2009-04-02 2010-04-02 Method and system for a traffic management network
EP10759461.6A EP2415324B1 (fr) 2009-04-02 2010-04-02 Procédé et système concernant un réseau de gestion de trafic
AU2010232549A AU2010232549B2 (en) 2009-04-02 2010-04-02 Method and system for a traffic management network
CN201080022468.0A CN102450085B (zh) 2009-04-02 2010-04-02 用于交通管理网络的方法和系统
PCT/US2010/029757 WO2010115083A2 (fr) 2009-04-02 2010-04-02 Procédé et système concernant un réseau de gestion de trafic
US13/584,141 US9154982B2 (en) 2009-04-02 2012-08-13 Method and system for a traffic management network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US21170209P 2009-04-02 2009-04-02
US12/752,778 US8510025B2 (en) 2009-04-02 2010-04-01 Method and system for a traffic management network

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/584,141 Continuation-In-Part US9154982B2 (en) 2009-04-02 2012-08-13 Method and system for a traffic management network

Publications (2)

Publication Number Publication Date
US20100254282A1 US20100254282A1 (en) 2010-10-07
US8510025B2 true US8510025B2 (en) 2013-08-13

Family

ID=42826107

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/752,778 Active 2032-03-02 US8510025B2 (en) 2009-04-02 2010-04-01 Method and system for a traffic management network

Country Status (6)

Country Link
US (1) US8510025B2 (fr)
EP (1) EP2415324B1 (fr)
CN (1) CN102450085B (fr)
AU (1) AU2010232549B2 (fr)
NZ (1) NZ596146A (fr)
WO (1) WO2010115083A2 (fr)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120276847A1 (en) * 2011-04-29 2012-11-01 Navteq North America, Llc Obtaining vehicle traffic information using mobile Bluetooth detectors
US20130254379A1 (en) * 2011-09-16 2013-09-26 Qualcomm Incorporated Systems and methods for network quality estimation, connectivity detection, and load management
US20130275032A1 (en) * 2012-04-13 2013-10-17 Blue-Band LLC Traffic monitoring and notification system and associated methods
WO2017164721A1 (fr) 2016-03-23 2017-09-28 Boulmakoul Azedine Systeme de supervision et de controle du trafic
US9916755B1 (en) 2016-12-20 2018-03-13 Jayant Ratti On-demand roadway stewardship system
US9984544B2 (en) 2015-02-17 2018-05-29 Sap Se Device layout optimization for surveillance devices
US10037689B2 (en) * 2015-03-24 2018-07-31 Donald Warren Taylor Apparatus and system to manage monitored vehicular flow rate
US10356887B2 (en) * 2017-11-29 2019-07-16 Panasonic Intellectual Property Management Co., Ltd. Communications device
US11082871B1 (en) 2021-02-22 2021-08-03 Iteris, Inc. Bluetooth low-energy sensor data collection device
US11297688B2 (en) 2018-03-22 2022-04-05 goTenna Inc. Mesh network deployment kit
US11811642B2 (en) 2018-07-27 2023-11-07 GoTenna, Inc. Vine™: zero-control routing using data packet inspection for wireless mesh networks

Families Citing this family (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4591395B2 (ja) * 2006-03-31 2010-12-01 アイシン・エィ・ダブリュ株式会社 ナビゲーションシステム
MX2011001118A (es) * 2008-07-30 2011-05-23 Bitcarrier S L Sistema y procedimiento de monitorizacion de personas y/o vehiculos en entornos urbanos.
US9184490B2 (en) 2009-05-29 2015-11-10 Abbott Diabetes Care Inc. Medical device antenna systems having external antenna configurations
US20110093330A1 (en) * 2009-10-21 2011-04-21 International Business Machines Corporation Peer vehicle adaptive destination-based mobile advertising
JP5984815B2 (ja) * 2010-09-17 2016-09-06 トムソン ライセンシングＴｈｏｍｓｏｎ Ｌｉｃｅｎｓｉｎｇ 通信方法及び通信システム
US8976041B2 (en) 2010-09-30 2015-03-10 Siemens Industry, Inc. Traffic analysis using wireless receivers and vehicle detection devices
US20120208521A1 (en) * 2011-02-11 2012-08-16 Haeger Peter Antenna Mast and a Method of Providing a Further Function in an Antenna Mast
US8970438B2 (en) 2011-02-11 2015-03-03 Telefonaktiebolaget L M Ericsson (Publ) Method of providing an antenna mast and an antenna mast system
TWI452886B (zh) * 2011-08-07 2014-09-11 Mediatek Inc 映射統一參數的方法
US20130073193A1 (en) * 2011-09-19 2013-03-21 Cambridge Silicon Radio Limited Collaborative traffic monitoring
CN102572119B (zh) * 2011-10-31 2015-10-21 中兴通讯股份有限公司 一种移动终端及其省电方法
US9766993B2 (en) * 2012-05-18 2017-09-19 International Business Machines Corporation Quality of information assessment in dynamic sensor networks
US9165463B2 (en) 2012-06-26 2015-10-20 Microsoft Technology Licensing, Llc Ambient vehicle and pedestrian state detection for device notification
EP2680534B1 (fr) * 2012-06-28 2017-12-27 Harman Becker Automotive Systems GmbH Journalisation pour systèmes télématiques
US9968306B2 (en) * 2012-09-17 2018-05-15 Abbott Diabetes Care Inc. Methods and apparatuses for providing adverse condition notification with enhanced wireless communication range in analyte monitoring systems
CN102917384B (zh) * 2012-10-19 2015-03-25 宁波市北仑海伯精密机械制造有限公司 Zigbee网络中协调器的热备方法
US8923333B2 (en) * 2013-02-08 2014-12-30 Shoab A. Khan Cognitive hub for self-healing and self-forming network with hybrid communication technologies
EP2974182B1 (fr) * 2013-03-15 2020-09-16 FLIR Commercial Systems, Inc. Système d'analyse de trafic utilisant des périphériques réseau sans fil
US9842495B2 (en) * 2013-03-15 2017-12-12 Acyclica Inc. Traffic analysis system using wireless networking devices
GB201305131D0 (en) * 2013-03-20 2013-05-01 Tomtom Dev Germany Gmbh Methods and systems for detecting a closure of a navigable element
CN103179694B (zh) * 2013-03-27 2016-01-20 西安交通大学 一种人际互动关系数据采集方法
TWI490823B (zh) * 2013-05-02 2015-07-01 Wistron Neweb Corp 存取點認證裝置和方法
CN104470035A (zh) * 2013-09-17 2015-03-25 浙江中博光电科技有限公司 道路照明智能电源系统
WO2015053802A1 (fr) * 2013-10-07 2015-04-16 Hahn, Victor, C. Procédé de réduction du trafic automobile dans une ville ou dans une grande ville
CN104581792A (zh) * 2013-10-17 2015-04-29 新普斯有限公司 群蜂网络备援系统
WO2016010408A1 (fr) * 2014-07-18 2016-01-21 Fuentes Colomo Luis José Dispositif de vidéo
CN105846859B (zh) * 2015-01-12 2019-05-24 芋头科技（杭州）有限公司 一种嵌入式操作系统实现蓝牙从设备功能的系统及方法
US9483939B2 (en) * 2015-03-06 2016-11-01 Here Global B.V. Method and apparatus for providing traffic flow signaling
US9978284B2 (en) 2015-06-05 2018-05-22 Here Global B.V. Method and apparatus for generating vehicle maneuver plans
US10210753B2 (en) 2015-11-01 2019-02-19 Eberle Design, Inc. Traffic monitor and method
CN105528457B (zh) * 2015-12-28 2019-02-19 招商局重庆交通科研设计院有限公司 一种基于大数据技术的交通信息提取和查询方法
US10607482B2 (en) * 2015-12-31 2020-03-31 Robert Bosch Gmbh Intelligent distributed vision traffic marker and method thereof
US10803737B2 (en) 2015-12-31 2020-10-13 Robert Bosch Gmbh Wireless mesh network distributed vision traffic marker and method thereof
CN105828459A (zh) * 2016-05-13 2016-08-03 上海三思电子工程有限公司 场所车辆管理系统、车载终端及车辆
US10565864B2 (en) 2016-12-06 2020-02-18 Flir Commercial Systems, Inc. Localized traffic data collection
CN108765923B (zh) * 2018-04-23 2020-10-27 天津赞普科技股份有限公司 一种基于bs架构的警用组网调度指挥方法及系统
CN108665818A (zh) * 2018-05-18 2018-10-16 云南电网有限责任公司电力科学研究院 一种电力铁塔用电子广告牌
GB2578746A (en) * 2018-11-06 2020-05-27 Telensa Holdings Ltd Monitoring system

Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020085498A1 (en) 2000-12-28 2002-07-04 Koji Nakamichi Device and method for collecting traffic information
US6505114B2 (en) 2001-02-06 2003-01-07 Sergio Luciani Traffic monitoring system and method
US20040147223A1 (en) 2002-04-02 2004-07-29 Kwang Sun Cho System, apparatus and method for wireless mobile communications in association with mobile ad-hoc network support
US6785606B2 (en) 1999-04-19 2004-08-31 Dekock Bruce W. System for providing traffic information
US20070142037A1 (en) * 2005-12-16 2007-06-21 Cisco Technology, Inc. Method and system for wireless signaling of vehicular traffic
US20070257782A1 (en) 2006-05-08 2007-11-08 Drivecam, Inc. System and Method for Multi-Event Capture
US20080026771A1 (en) 2006-07-26 2008-01-31 Broadcom Corporation, A California Corporation Mobile terminal position information collection and reporting
US20080059050A1 (en) * 2006-08-31 2008-03-06 Hitachi, Ltd. Road congestion detection by distributed vehicle-to-vehicle communication systems
US20090112452A1 (en) * 2007-10-25 2009-04-30 Gm Global Technology Operations, Inc. Vehicle navigation system with real time traffic image display
US20090210141A1 (en) 2008-01-03 2009-08-20 Young Stanley E Monitoring a Mobile Device
US20090271100A1 (en) * 2005-12-08 2009-10-29 Electronics And Telecommunications Research Institute Apparatus and Method for Providing Traffic Jam Information, and Apparatus for Receiving Traffic Jam Information for Automobile
US20090309966A1 (en) * 2008-06-16 2009-12-17 Chao-Ho Chen Method of detecting moving objects
US20100004849A1 (en) * 2008-07-01 2010-01-07 Jeong Eun-Hee Mobile vehicle navigation method and apparatus thereof
US20100203834A1 (en) * 2007-06-28 2010-08-12 Telecom Italia S.P.A. Method and system for detecting a moving vehicle within a predetermined area
US20110156924A1 (en) 2009-10-29 2011-06-30 Siemens Corporation Estimation of travel times using bluetooth
US7979198B1 (en) * 2007-12-20 2011-07-12 Sprint Spectrum L.P. Vehicular traffic congestion monitoring through inter-vehicle communication and traffic chain counter
WO2011134647A1 (fr) 2010-04-29 2011-11-03 Deutsches Zentrum für Luft- und Raumfahrt e.V. Procédé et dispositif de génération d'informations de circulation routière

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5696503A (en) * 1993-07-23 1997-12-09 Condition Monitoring Systems, Inc. Wide area traffic surveillance using a multisensor tracking system
US6711493B1 (en) * 2002-12-09 2004-03-23 International Business Machines Corporation Method and apparatus for collecting and propagating information relating to traffic conditions
CN1710841B (zh) * 2004-06-16 2010-07-21 郑州捷安网络科技开发有限公司 列车车载无线自组网络通讯及列车状态实时监控系统
US20070061155A1 (en) * 2005-09-13 2007-03-15 Yiming Ji Universal Vehicle Communication & Management System
US7720581B2 (en) * 2005-10-11 2010-05-18 Toshiba America Research, Inc. Monitoring of vehicle conditions utilizing cellular broadcasts

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6785606B2 (en) 1999-04-19 2004-08-31 Dekock Bruce W. System for providing traffic information
US20020085498A1 (en) 2000-12-28 2002-07-04 Koji Nakamichi Device and method for collecting traffic information
US6505114B2 (en) 2001-02-06 2003-01-07 Sergio Luciani Traffic monitoring system and method
US20040147223A1 (en) 2002-04-02 2004-07-29 Kwang Sun Cho System, apparatus and method for wireless mobile communications in association with mobile ad-hoc network support
US20090271100A1 (en) * 2005-12-08 2009-10-29 Electronics And Telecommunications Research Institute Apparatus and Method for Providing Traffic Jam Information, and Apparatus for Receiving Traffic Jam Information for Automobile
US20070142037A1 (en) * 2005-12-16 2007-06-21 Cisco Technology, Inc. Method and system for wireless signaling of vehicular traffic
US20070257782A1 (en) 2006-05-08 2007-11-08 Drivecam, Inc. System and Method for Multi-Event Capture
US20080026771A1 (en) 2006-07-26 2008-01-31 Broadcom Corporation, A California Corporation Mobile terminal position information collection and reporting
US20080059050A1 (en) * 2006-08-31 2008-03-06 Hitachi, Ltd. Road congestion detection by distributed vehicle-to-vehicle communication systems
US20100203834A1 (en) * 2007-06-28 2010-08-12 Telecom Italia S.P.A. Method and system for detecting a moving vehicle within a predetermined area
US20090112452A1 (en) * 2007-10-25 2009-04-30 Gm Global Technology Operations, Inc. Vehicle navigation system with real time traffic image display
US7979198B1 (en) * 2007-12-20 2011-07-12 Sprint Spectrum L.P. Vehicular traffic congestion monitoring through inter-vehicle communication and traffic chain counter
US20090210141A1 (en) 2008-01-03 2009-08-20 Young Stanley E Monitoring a Mobile Device
US20130006510A1 (en) * 2008-01-03 2013-01-03 University Of Maryland Monitoring a Mobile Device
US20090309966A1 (en) * 2008-06-16 2009-12-17 Chao-Ho Chen Method of detecting moving objects
US20100004849A1 (en) * 2008-07-01 2010-01-07 Jeong Eun-Hee Mobile vehicle navigation method and apparatus thereof
US20110156924A1 (en) 2009-10-29 2011-06-30 Siemens Corporation Estimation of travel times using bluetooth
WO2011134647A1 (fr) 2010-04-29 2011-11-03 Deutsches Zentrum für Luft- und Raumfahrt e.V. Procédé et dispositif de génération d'informations de circulation routière

Non-Patent Citations (9)

* Cited by examiner, † Cited by third party
Title
"Bluetooth Traffic Monitoring Technology-Concept of Operation and Deployment Guidelines", Sep. 17, 2008, pp. 1-5, University of Maryland-Center for Advanced Transportation Technology.
"Concept of Operations", Traffax Inc., pp. 1-2, downloaded Mar. 16, 2009 via http://www.traffaxinc.com/concept.html.
"Product Description", Traffax, Inc., pp. 1-2, downloaded Mar. 16, 2009 via http://traffaxinc.com/product.html.
"Product Types", Traffax, Inc., pp. 1-2, downloaded Mar. 16, 2009 via http://www.traffaxinc.com/types.html.
"Traffax Inc. Introduces a Unique Line of Data Collection Equipment", Traffax Press Release, pp. 1-3, Feb. 9, 2009.
International Preliminary Report on Patentability for Intl. Pat. Appln. No. PCT/US2010/029757, mailed on Oct. 13, 2011, 6 pp.
International Search Report and Written Opinion for Intl. Pat. Appln. No. PCT/US2010/029757, mailed on Oct. 26, 2010, and received on Nov. 4, 2010.
Sugiura, Akihika, et al., "In Traffic Jam IVC-RVC System for ITS Using Bluetooth," IEEE Transactions on Intelligent Transportation Systems, vol. 6, No. 3, Sep. 2005, pp. 302-313.
Tarnoff, Philip J. et al., "The Continuing Evolution of Travel Time Data Information Collection and Processing", TRB Paper 09-2030, Jul. 31, 2008, pp. 1-14, Center for Advanced Transportation Technology.

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9014632B2 (en) * 2011-04-29 2015-04-21 Here Global B.V. Obtaining vehicle traffic information using mobile bluetooth detectors
US9478128B2 (en) 2011-04-29 2016-10-25 Here Global B.V. Obtaining vehicle traffic information using mobile bluetooth detectors
US20120276847A1 (en) * 2011-04-29 2012-11-01 Navteq North America, Llc Obtaining vehicle traffic information using mobile Bluetooth detectors
US20130254379A1 (en) * 2011-09-16 2013-09-26 Qualcomm Incorporated Systems and methods for network quality estimation, connectivity detection, and load management
US9736045B2 (en) * 2011-09-16 2017-08-15 Qualcomm Incorporated Systems and methods for network quality estimation, connectivity detection, and load management
US20130275032A1 (en) * 2012-04-13 2013-10-17 Blue-Band LLC Traffic monitoring and notification system and associated methods
US9171459B2 (en) * 2012-04-13 2015-10-27 Blue-Band LLC Traffic monitoring and notification system and associated methods
US9984544B2 (en) 2015-02-17 2018-05-29 Sap Se Device layout optimization for surveillance devices
US10037689B2 (en) * 2015-03-24 2018-07-31 Donald Warren Taylor Apparatus and system to manage monitored vehicular flow rate
WO2017164721A1 (fr) 2016-03-23 2017-09-28 Boulmakoul Azedine Systeme de supervision et de controle du trafic
US9916755B1 (en) 2016-12-20 2018-03-13 Jayant Ratti On-demand roadway stewardship system
EP4123616A1 (fr) 2016-12-20 2023-01-25 Ratti, Jayant Système de surveillance routière à la demande
US10356887B2 (en) * 2017-11-29 2019-07-16 Panasonic Intellectual Property Management Co., Ltd. Communications device
US11297688B2 (en) 2018-03-22 2022-04-05 goTenna Inc. Mesh network deployment kit
US11811642B2 (en) 2018-07-27 2023-11-07 GoTenna, Inc. Vine™: zero-control routing using data packet inspection for wireless mesh networks
US11082871B1 (en) 2021-02-22 2021-08-03 Iteris, Inc. Bluetooth low-energy sensor data collection device
US11843961B2 (en) 2021-02-22 2023-12-12 Iteris, Inc. Bluetooth low-energy sensor data collection device

Also Published As

Publication number Publication date
AU2010232549B2 (en) 2015-08-20
US20100254282A1 (en) 2010-10-07
CN102450085B (zh) 2014-12-24
WO2010115083A3 (fr) 2011-02-10
EP2415324A4 (fr) 2018-01-17
WO2010115083A2 (fr) 2010-10-07
EP2415324B1 (fr) 2023-09-13
AU2010232549A1 (en) 2011-11-24
NZ596146A (en) 2014-08-29
EP2415324A2 (fr) 2012-02-08
CN102450085A (zh) 2012-05-09

Similar Documents

Publication Publication Date Title
US8510025B2 (en) Method and system for a traffic management network
US9154982B2 (en) Method and system for a traffic management network
US7430218B2 (en) Apparatus and method for providing users with road traffic information using ad-hoc network
US6804602B2 (en) Incident-aware vehicular sensors for intelligent transportation systems
US6690292B1 (en) Method and system for monitoring vehicular traffic using a wireless communications network
US9159080B2 (en) Providing city services using mobile devices and a sensor network
Campolo et al. SMaRTCaR: An integrated smartphone-based platform to support traffic management applications
Geetha et al. IoT enabled intelligent bus transportation system
US9786161B2 (en) Methods and systems for estimating road traffic
US20060247844A1 (en) Intelligent traffic monitoring and guidance system
CN101816022B (zh) 检测预定区域内的运动车辆的方法和系统
US20110156924A1 (en) Estimation of travel times using bluetooth
WO2013146152A1 (fr) Publication et dissémination de données dynamiques
US10726717B2 (en) Anonymous wireless address matching for traffic information
US20140119251A1 (en) Information service system using direct communication between vehicles
US20170251541A1 (en) System and method for outdoor lighting operation and management using its protocols and connectivity infrastructure
Remias et al. Travel time observations using Bluetooth MAC address matching: A case study on the Rajiv Gandhi Roadway: Chennai, India
CN104424800A (zh) 基于电子不停车收费电子标签的浮动车交通信息采集方法及其系统
Widyantara et al. Internet of things for intelligent traffic monitoring system: a case study in denpasar
US20100004862A1 (en) Mobile environmental detector
Alam et al. Integration of smart parking in distributed ITS architecture
TW201025216A (en) Dynamic information revealing of public transit system and operation method thereof
US20060258360A1 (en) Method and apparatus to allow two way communication to provide time and location specific information
JP4239996B2 (ja) 位置情報収集システム及び当該システムに用いられる装置、方法、プログラム
CN107452206A (zh) 基于Wi-Fi技术的电动自行车/摩托车管理系统及方法

Legal Events

Date Code Title Description
AS Assignment

Owner name: TRAFFICCAST INTERNATIONAL, INC., WISCONSIN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHAN, PETER;CAMPBELL, NEAL J.;COURTNEY, TIM;AND OTHERS;SIGNING DATES FROM 20100501 TO 20100615;REEL/FRAME:024567/0084

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: FIRST BUSINESS BANK, WISCONSIN

Free format text: SECURITY INTEREST;ASSIGNOR:TRAFFICCAST INTERNATIONAL, INC.;REEL/FRAME:038290/0894

Effective date: 20160415

AS Assignment

Owner name: FIRST BUSINESS BANK, WISCONSIN

Free format text: SECURITY INTEREST;ASSIGNOR:TRAFFICCAST INTERNATIONAL, INC.;REEL/FRAME:038813/0335

Effective date: 20160415

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: ITERIS, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TRAFFICCAST INTERNATIONAL, INC.;REEL/FRAME:054715/0736

Effective date: 20201207

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2552); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

Year of fee payment: 8

AS Assignment

Owner name: CAPITAL ONE, NATIONAL ASSOCIATION, MARYLAND

Free format text: SECURITY INTEREST;ASSIGNOR:ITERIS, INC;REEL/FRAME:058770/0592

Effective date: 20220125

AS Assignment

Owner name: ITERIS, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CAPITAL ONE, NATIONAL ASSOCIATION;REEL/FRAME:061109/0658

Effective date: 20220909