USRE47482E1 - System and method for verifying whether a vehicle is equipped with a functional on-board unit - Google Patents

System and method for verifying whether a vehicle is equipped with a functional on-board unit Download PDF

Info

Publication number
USRE47482E1
USRE47482E1 US14/925,055 US201514925055A USRE47482E US RE47482 E1 USRE47482 E1 US RE47482E1 US 201514925055 A US201514925055 A US 201514925055A US RE47482 E USRE47482 E US RE47482E
Authority
US
United States
Prior art keywords
obu
license plate
location
vehicle
message
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
US14/925,055
Inventor
Andre Krijn Nieuwland
Gerardo Daalderop
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.)
Titan Intelligence Technology Ltd
Original Assignee
Telit Automotive Solutions NV
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
Application filed by Telit Automotive Solutions NV filed Critical Telit Automotive Solutions NV
Priority to US14/925,055 priority Critical patent/USRE47482E1/en
Assigned to TELIT AUTOMOTIVE SOLUTIONS NV reassignment TELIT AUTOMOTIVE SOLUTIONS NV ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NXP B.V.
Assigned to NXP B.V. reassignment NXP B.V. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DAALDEROP, GERARDO, NIEUWLAND, ANDRE
Assigned to HSBC BANK PLC reassignment HSBC BANK PLC SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TELIT AUTOMOTIVE SOLUTIONS NV
Assigned to TELIT AUTOMOTIVE SOLUTIONS NV reassignment TELIT AUTOMOTIVE SOLUTIONS NV RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: HSBC BANK PLC
Application granted granted Critical
Publication of USRE47482E1 publication Critical patent/USRE47482E1/en
Assigned to TITAN AUTOMOTIVE SOLUTIONS NV reassignment TITAN AUTOMOTIVE SOLUTIONS NV CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: TELIT AUTOMOTIVE SOLUTIONS NV
Assigned to TITAN INTELLIGENCE TECHNOLOGY LIMITED reassignment TITAN INTELLIGENCE TECHNOLOGY LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TITAN AUTOMOTIVE SOLUTIONS NV
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07B—TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B15/00—Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
    • G07B15/06—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems
    • G07B15/063—Arrangements for road pricing or congestion charging of vehicles or vehicle users, e.g. automatic toll systems using wireless information transmission between the vehicle and a fixed station
    • 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/017—Detecting movement of traffic to be counted or controlled identifying vehicles
    • G08G1/0175—Detecting movement of traffic to be counted or controlled identifying vehicles by photographing vehicles, e.g. when violating traffic rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0283—Price estimation or determination
    • G06Q30/0284—Time or distance, e.g. usage of parking meters or taximeters

Definitions

  • Various exemplary embodiments disclosed herein relate generally to systems and methods for the payment of tolls along toll roads.
  • a toll road is a road for which a vehicle pays a toll or fee for each use of the road.
  • a verification system for verifying whether a vehicle is equipped with a functional on-board unit (OBU), including: a license plate recognition system configured to obtain a license plate number of the vehicle at a first location; a database of license plate numbers and OBU information, wherein the database includes a correspondence of license plate numbers and OBU information; a wireless communication system configured to send a trigger message to the OBU using the OBU information, and configured to receive a response from the OBU indicating a location of the OBU; and a verification module configured to determine whether the vehicle is equipped with the OBU, wherein the verification module determines that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
  • OBU functional on-board unit
  • the trigger message is sent wirelessly, and the response from the OBU is received wirelessly.
  • the trigger message is at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call.
  • the response from the OBU is at least one of a SMS message, a WIFI message, and a cellular message.
  • the verification system issues a citation to the registered owner of the license plate if the location reported by the OBU is not within a specified distance of the first location.
  • the verification system issues a citation to the registered owner of the license plate if the license plate number obtained by the license plate recognition system does not have corresponding OBU information in the database.
  • the verification system receives a toll payment from the OBU based upon a measured location of the vehicle.
  • Various exemplary embodiments further relate to a method for verifying whether a vehicle is equipped with a functional on-board unit (OBU), including: obtaining a license plate number of the vehicle at a first location; obtaining OBU information that corresponds to the license plate number; sending a trigger message to the OBU using the OBU information; receiving a response from the OBU indicating a location of the OBU; and determining that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
  • OBU functional on-board unit
  • the trigger message is sent wirelessly, and the response from the OBU is received wirelessly.
  • the trigger message is at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call.
  • the response from the OBU is at least one of a SMS message, a WIFI message, and a cellular data message.
  • the method further includes issuing a citation to the registered owner of the license plate if the location reported by the OBU is not within a specified distance of the first location.
  • the method further includes issuing a citation to the registered owner of the license plate if the OBU information cannot be obtained from the license plate number.
  • the method further includes receiving a toll payment from the OBU based upon a measured location of the vehicle.
  • Various exemplary embodiments further relate to a method for verifying whether a vehicle is equipped with a functional on-board unit (OBU), including: triggering the OBU to transmit a location of the OBU; updating a database with the location of the OBU, wherein the database includes a correspondence of license plate numbers and OBU information; obtaining a license plate number of the vehicle at a first location; obtaining the location of the OBU from the database by using the correspondence of license plate numbers and OBU information; and determining that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
  • OBU functional on-board unit
  • the OBU is triggered when the OBU connects to a new cellular base station. In some embodiments, the OBU is triggered by at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call. In some embodiments, the OBU transmits the location of the OBU wirelessly. In some embodiments, the OBU transmits the location of the OBU as at least one of a SMS message, a WIFI message, and a cellular data message. In some embodiments, the method further includes issuing a citation to the registered owner of the license plate if the location reported by the OBU is not within a specified distance of the first location.
  • FIG. 1 illustrates an embodiment of an on-board unit (OBU);
  • OBU on-board unit
  • FIG. 2 illustrates an embodiment of a verification system
  • FIG. 3 illustrates an embodiment of a verification method
  • FIG. 4 illustrates an alternative embodiment of a verification system
  • FIG. 5 illustrates an alternative embodiment of a verification method.
  • Toll roads may utilize a variety of payment systems.
  • a common payment system for toll roads is a toll booth.
  • the toll booth may collect a toll from vehicles using the toll road.
  • the toll may be collected by physically giving money to a toll booth attendant or by giving money to an automated machine at the toll booth.
  • the toll may be collected electronically by wireless transceivers at the toll booth.
  • a corresponding wireless transceiver within the vehicle may be triggered when the vehicle passes the wireless transceivers in the toll booth, and money may be deducted from an account associated with the wireless transceiver in the vehicle.
  • An alternative payment system for toll roads may utilize a terrestrial and/or satellite-based navigation system in lieu of, or in addition to, toll booths.
  • the navigation system may be, for example, a Global Positioning System (GPS), or Global Navigation Satellite System (GLONASS).
  • GPS Global Positioning System
  • GLONASS Global Navigation Satellite System
  • the navigation system may measure the location of a vehicle to determine if the vehicle is on a toll road.
  • the navigation system may also measure the distance a vehicle travels on the toll road.
  • An applicable toll for the vehicle may be calculated based in part upon the location and distance information from the navigation system. Other factors that may determine the applicable toll may include time and date information (e.g., time of day, day of the week, etc.) and vehicle information (e.g., vehicle weight, fuel type, speed of travel, etc.).
  • a toll road that utilizes a terrestrial and/or satellite-based navigation system may require that vehicles using the toll road are equipped with an on-board unit (OBU) that includes the systems necessary for the vehicle to determine its location and pay the applicable toll.
  • OBU on-board unit
  • a toll road that utilizes a terrestrial and/or satellite-based navigation system for the paying of tolls may not include toll booths. Therefore, it may be important to enforce that all vehicles using the toll road are equipped with a properly-functioning OBU, otherwise some vehicles may not pay the applicable toll.
  • FIG. 1 illustrates an embodiment of an OBU 100 .
  • the OBU 100 may include a positioning unit 102 and a billing/communication unit 104 .
  • the positioning unit 102 may determine a location of the OBU 100 .
  • the positioning unit 102 may utilize a terrestrial and/or satellite-based navigation system, such as, for example, GPS or GLONASS.
  • the billing/communication unit 104 may wirelessly communicate with a payment server (not shown) to pay a vehicle's toll.
  • the billing/communication unit 104 may utilize a wireless communication system such as, for example, Global System for Mobile Communications (GSM) or other cellular communication system.
  • GSM Global System for Mobile Communications
  • FIG. 2 illustrates an embodiment of a verification system 200 .
  • the verification system 200 may verify if a vehicle is equipped with a functioning OBU 100 .
  • the verification system may include a license plate recognition system 204 , a license plate/OBU database 206 , and an OBU communication system 208 .
  • the license plate recognition system 204 may obtain the license plate number of a vehicle using a toll road.
  • the license plate recognition system 204 may obtain the license plate number automatically through the use of a camera and recognition software. Alternatively, the license plate number may be manually entered into the license plate recognition system 204 by toll enforcement personnel.
  • the license plate recognition system 204 may use the license plate number to look up OBU information in the license plate/OBU database 206 .
  • the license plate/OBU database 206 may include multiple, cross-referenced databases, such as a license plate/vehicle owner database and an OBU/vehicle owner database.
  • An OBU communication system 208 may receive the OBU information that corresponds with the license plate number.
  • the OBU information may include information necessary to contact the billing/communication unit 104 of the OBU 100 , such as, for example, a GSM identification number.
  • the OBU communication system 208 may issue a citation to the registered owner of the license plate and/or alert toll enforcement personnel.
  • the OBU communication system 208 may send a request to the OBU 100 for the OBU 100 to report its current position.
  • the request may be received by the billing/communication unit 104 of the OBU 100 .
  • the request from the OBU communication system 208 may be in the form of a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or an incoming telephone call.
  • the request from the OBU communication system 208 may include a time-stamp.
  • the OBU 100 may respond to the request with vehicle identification information and vehicle location information.
  • the vehicle identification information may include, for example, license plate number, vehicle identification number (VIN), vehicle brand, vehicle type, vehicle color, fuel type, pollution class, vehicle weight, vehicle size, and/or presence of hazardous materials.
  • the vehicle location information may identify the location of the OBU 100 at a certain point in time. If the request from the OBU communication system 208 included a time-stamp, then the vehicle location information reported by the OBU 100 may correspond to a location of the vehicle at approximately the point in time of the time-stamp. If the request from the OBU communication system 208 did not include a time-stamp, then the vehicle location information reported by the OBU 100 may correspond to a location of the vehicle at approximately the point in time that the request was received.
  • the vehicle location information may include, for example, GPS coordinates, GLONASS coordinates, latitude/longitude, a region name, and/or a road name, as well as a time and date that the location was determined.
  • the response from the OBU 100 may be transmitted to the OBU communication system 208 using the billing/communication unit 104 of the OBU 100 .
  • the response from the OBU 100 may be transmitted in the form of a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or any other suitable message.
  • the response from the OBU 100 may be encrypted and/or signed to verify the integrity of the response.
  • the OBU 100 may respond to the request from the communication system 208 with additional information, such as integrity information, diagnostic information, and/or toll information.
  • the integrity information may indicate whether any components and/or software of the OBU 100 have been tampered with.
  • the diagnostic information may indicate whether any components and/or software of the OBU 100 are not operating correctly.
  • the toll information may indicate the current toll mode the OBU 100 is operating under (e.g., rush hour or off-peak).
  • the OBU communication system 208 may transmit the response from the OBU 100 to a verification module 210 .
  • the verification module 210 may be a module of the OBU communication system 208 , the license plate/OBU database 206 , the license plate recognition system 204 , or may be a separate, individual module.
  • the verification module 210 may use the response from the OBU 100 to verify if the location of the OBU 100 is within a certain range of the license plate recognition system 204 .
  • the verification module 210 may also verify that the vehicle identification information from the OBU 100 matches the information in the license plate/OBU database 206 .
  • the verification module 210 may use the response from the OBU 100 to determine if the OBU 100 is present in the vehicle that was checked by the license plate recognition system 204 .
  • the OBU 100 may be assumed to be present in the vehicle if the OBU 100 reports its location as near (for example, within 100 m) to the location where the license plate recognition system 204 obtained the license plate number of the vehicle. If the verification module 210 determines that the OBU 100 is not present in the vehicle, or if the OBU communication system 208 does not receive a response from the OBU 100 , then the OBU communication system 208 may record the license plate number and/or vehicle identification information, and issue a citation to the registered owner of the license plate.
  • the verification module 210 determines that the OBU 100 is not present in the vehicle, or if the OBU communication system 208 does not receive a response from the OBU 100 , then the OBU communication system 208 may alert toll enforcement personnel.
  • FIG. 3 illustrates an embodiment of a verification method 300 .
  • the verification method 300 may begin when a vehicle enters an OBU verification region at step 302 . Once in the OBU verification region, information about the vehicle such as, for example, the vehicle license plate number, may be obtained at step 304 . At step 306 , an OBU/vehicle database may be accessed that contains OBU information associated with vehicle information. At step 308 , the verification method 300 may determine if the vehicle has an associated OBU. If the vehicle does not have an associated OBU, then the verification method 300 may issue a citation to the registered owner of the license plate and/or alert toll enforcement personnel at step 310 .
  • the verification method 300 may use the OBU information in the OBU database to send a trigger to the OBU associated with the vehicle to report its location at step 312 .
  • the OBU associated with the vehicle may be triggered by sending a message over a wireless communication network, such as, for example, a GSM network.
  • the message may be, for example, a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or a cellular telephone call.
  • the verification method 300 may determine if the OBU associated with the vehicle sent a valid response to the trigger message.
  • the verification method 300 may issue a citation and/or alert toll enforcement personnel at step 310 . If a valid response is received from the OBU associated with the vehicle, then the verification method 300 may extract information from the response at step 316 .
  • the response from the OBU associated with the vehicle may include the location of the OBU at the approximate time the trigger message was received. If the trigger message included a time-stamp, then the response from the OBU associated with the vehicle may include the location of the OBU at the approximate time of the time-stamp.
  • the response may also include other information, such as vehicle information, time and date information, and/or other enforcement information (e.g., vehicle speed, number of passengers, seatbelt status, etc.).
  • the response from the OBU associated with the vehicle may be sent over a wireless communication network, such as, for example a GSM network.
  • the response may be, for example, a SMS message or a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.).
  • the verification method 300 may determine if the OBU is present in the vehicle and functioning properly at step 318 .
  • the verification method 300 may assume that the OBU is present in the vehicle and functioning properly if the OBU reports its location as near (for example, within 100 m) to the location where the vehicle information was obtained. If the verification method 300 determines that the OBU that sent the response is not present in the vehicle, then the verification method 300 may issue a citation and/or alert toll enforcement personnel at step 310 . If the verification method 300 determines that the OBU that sent the response is present in the vehicle and functioning properly, then the OBU associated with the vehicle may pay an applicable toll at step 320 . The applicable toll may be paid immediately upon calculation by the OBU, or may be paid at a later time. The verification method 300 ends at step 322 .
  • FIG. 4 illustrates an alternative embodiment of a verification system 400 .
  • the verification system 400 may verify if a vehicle is equipped with a functioning OBU 100 .
  • the verification system may include an OBU trigger 402 , a license plate recognition system 404 , a license plate/OBU database 406 , and an OBU communication system 408 .
  • the OBU trigger 402 may trigger the OBU 100 to report its current position.
  • the OBU trigger 402 may be a wireless checkpoint, such as, for example a cellular base station or a toll booth.
  • the trigger from the OBU trigger 402 may be received by the billing/communication unit 104 of the OBU 100 .
  • the trigger from the OBU trigger 402 may be in the form of a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), an incoming telephone call, or other wireless signals (e.g., infrared, radio-frequency, etc.).
  • the trigger from the OBU trigger 402 may include a time-stamp.
  • the OBU 100 may be triggered to report its position whenever the billing/communication unit 104 connects to a new cellular base station.
  • the OBU 100 may respond to the trigger with vehicle identification information and vehicle location information.
  • the vehicle identification information may include, for example, license plate number, vehicle identification number (VIN), vehicle brand, vehicle type, vehicle color, fuel type, pollution class, vehicle weight, vehicle size, and/or presence of hazardous materials.
  • the vehicle location information may identify the location of the OBU 100 at a certain point in time. If the trigger from the OBU trigger 402 included a time-stamp, then the vehicle location information reported by the OBU 100 may correspond to a location of the vehicle at approximately the point in time of the time-stamp. If the trigger from the OBU trigger 402 did not include a time-stamp, then the vehicle location information reported by the OBU 100 may correspond to a location of the vehicle at approximately the point in time that the trigger was received.
  • the vehicle location information may include, for example, GPS coordinates, GLONASS coordinates, latitude/longitude, a region name, and/or a road name, as well as a time and date that the location was determined.
  • the response from the OBU 100 may be transmitted to the OBU communication system 408 using the billing/communication unit 104 of the OBU 100 .
  • the response from the OBU 100 may be transmitted in the form of a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or any other suitable message.
  • the response from the OBU 100 may be encrypted and/or signed to verify the integrity of the response.
  • the OBU may respond to the trigger with additional information, such as integrity information, diagnostic information, and/or toll information.
  • the integrity information may indicate whether any components and/or software of the OBU 100 have been tampered with.
  • the diagnostic information may indicate whether any components and/or software of the OBU 100 are not operating correctly.
  • the toll information may indicate the current toll mode the OBU 100 is operating under (e.g., rush hour or off-peak).
  • the OBU communication system 408 may use the response from the OBU 100 to update the license plate/OBU database 406 .
  • information about the OBU 100 may be associated with the vehicle's license plate number and stored in the license plate/OBU database 406 .
  • the license plate/OBU database 406 may include multiple, cross-referenced databases, such as a license plate/vehicle owner database and an OBU/vehicle owner database.
  • the license plate/OBU database 406 may be updated to indicate the license plate numbers associated with the OBUs triggered by the OBU trigger 402 . In this way, the license plate/OBU database 406 may indicate the license plate numbers for vehicles that are known to be in a desired geographic region.
  • the license plate recognition system 404 may obtain the license plate number of a vehicle using a toll road.
  • the license plate recognition system 404 may obtain the license plate number automatically through the use of a camera and recognition software.
  • the license plate/OBU database 406 may aid the recognition software in obtaining the license plate number by indicating the license plate numbers of vehicles that are known to be in the region (for example, within 100 m) of the license plate recognition system 404 . In this way, the license plate recognition system 404 may predict which license plate numbers are likely to be in the camera's view. Alternatively, the license plate number may be manually entered into the license plate recognition system 404 by toll enforcement personnel.
  • the license plate recognition system 404 may transmit the license plate number to a verification module 410 .
  • the verification module 410 may be a module of the OBU communication system 408 , the license plate/OBU database 406 , the license plate recognition system 404 , or may be a separate, individual module.
  • the verification module 410 may use the license plate number to look up OBU information in the license plate/OBU database 406 .
  • the verification module 410 may use the license plate number and OBU information to verify if the vehicle is equipped with a functioning OBU 100 . If the license plate number indicates that the vehicle was already known to be in the region of the license plate recognition system 404 , then the verification module 410 may assume that the vehicle is equipped with a functioning OBU 100 .
  • the verification module 410 may issue a citation to the registered owner of the license plate and/or alert toll enforcement personnel. If toll enforcement personnel are alerted, the OBU 100 may be configured to periodically transmit position updates to aid the toll enforcement personnel in locating the vehicle.
  • FIG. 5 illustrates an alternative embodiment of a verification method 500 .
  • the verification method 500 may begin when a vehicle enters an OBU verification region at step 502 . Once in the OBU verification region, an OBU associated with the vehicle may be triggered to report its location at step 504 .
  • the verification method 500 may determine if the OBU associated with the vehicle sent a response to the trigger message. If no response is received from the OBU associated with the vehicle, then the verification method 500 may issue a citation and/or alert toll enforcement personnel at step 508 . If a response is received from the OBU associated with the vehicle, then the verification method 500 may extract information from the response at step 510 .
  • the response from the OBU associated with the vehicle may include the location of the OBU at the approximate time the trigger message was received. If the trigger message included a time-stamp, then the response from the OBU associated with the vehicle may include the location of the OBU at the approximate time of the time-stamp. The response may also include other information, such as vehicle information and time and date information.
  • the response from the OBU associated with the vehicle may be sent over a cellular communication network, such as, for example a GSM network.
  • the response may be, for example, a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or any other suitable message.
  • an OBU/vehicle database may be updated to indicate vehicles that are associated with the OBUs that responded to the trigger.
  • the verification method 500 may determine if the vehicle has an associated OBU by comparing the vehicle information obtained in step 514 to the updated information in the OBU/vehicle database. If the vehicle does not have an associated OBU, then the verification method 500 may issue a citation to the registered owner of the license plate and/or alert toll enforcement personnel at step 508 . If the vehicle has an associated OBU, then the OBU may pay an applicable toll at step 518 . The applicable toll may be paid immediately upon calculation by the OBU, or may be paid at a later time. The verification method 500 ends at step 520 .
  • various exemplary embodiments provide for a system and method for verifying if a vehicle is equipped with a functional OBU.
  • various exemplary embodiments of the invention may be implemented in hardware and/or firmware. Furthermore, various exemplary embodiments may be implemented as instructions stored on a tangible and non-transitory machine-readable storage medium, which may be read and executed by at least one processor to perform the operations described in detail herein.
  • a tangible and non-transitory machine-readable storage medium may include any mechanism for storing information in a form readable by a machine, such as a personal or laptop computer, a server, or other computing device.
  • a machine-readable storage medium may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and similar storage media.
  • any block diagrams herein represent conceptual views of illustrative circuitry embodying the principals of the invention.
  • any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in machine readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)
  • Traffic Control Systems (AREA)

Abstract

Various exemplary embodiments relate to a verification system and method for verifying whether a vehicle is equipped with a functional on-board unit (OBU). The system may include a license plate recognition system configured to obtain a license plate number of the vehicle at a first location; a database of license plate numbers and OBU information; a wireless communication system configured to send a trigger message to the OBU using the OBU information, and configured to receive a response from the OBU indicating a location of the OBU; and a verification module configured to determine whether the vehicle is equipped with the OBU. The database may include a correspondence of license plate numbers and OBU information. The verification module may determine that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.

Description

TECHNICAL FIELD
Various exemplary embodiments disclosed herein relate generally to systems and methods for the payment of tolls along toll roads.
BACKGROUND
A toll road is a road for which a vehicle pays a toll or fee for each use of the road.
SUMMARY
A brief summary of various exemplary embodiments is presented. Some simplifications and omissions may be made in the following summary, which is intended to highlight and introduce some aspects of the various exemplary embodiments, but not to limit the scope of the invention. Detailed descriptions of exemplary embodiments adequate to allow those of ordinary skill in the art to make and use the inventive concepts will follow in later sections.
Various exemplary embodiments relate to a verification system for verifying whether a vehicle is equipped with a functional on-board unit (OBU), including: a license plate recognition system configured to obtain a license plate number of the vehicle at a first location; a database of license plate numbers and OBU information, wherein the database includes a correspondence of license plate numbers and OBU information; a wireless communication system configured to send a trigger message to the OBU using the OBU information, and configured to receive a response from the OBU indicating a location of the OBU; and a verification module configured to determine whether the vehicle is equipped with the OBU, wherein the verification module determines that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
In some embodiments, the trigger message is sent wirelessly, and the response from the OBU is received wirelessly. In some embodiments, the trigger message is at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call. In some embodiments, the response from the OBU is at least one of a SMS message, a WIFI message, and a cellular message. In some embodiments, the verification system issues a citation to the registered owner of the license plate if the location reported by the OBU is not within a specified distance of the first location. In some embodiments, the verification system issues a citation to the registered owner of the license plate if the license plate number obtained by the license plate recognition system does not have corresponding OBU information in the database. In some embodiments, the verification system receives a toll payment from the OBU based upon a measured location of the vehicle.
Various exemplary embodiments further relate to a method for verifying whether a vehicle is equipped with a functional on-board unit (OBU), including: obtaining a license plate number of the vehicle at a first location; obtaining OBU information that corresponds to the license plate number; sending a trigger message to the OBU using the OBU information; receiving a response from the OBU indicating a location of the OBU; and determining that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
In some embodiments, the trigger message is sent wirelessly, and the response from the OBU is received wirelessly. In some embodiments, the trigger message is at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call. In some embodiments, the response from the OBU is at least one of a SMS message, a WIFI message, and a cellular data message. In some embodiments, the method further includes issuing a citation to the registered owner of the license plate if the location reported by the OBU is not within a specified distance of the first location. In some embodiments, the method further includes issuing a citation to the registered owner of the license plate if the OBU information cannot be obtained from the license plate number. In some embodiments, the method further includes receiving a toll payment from the OBU based upon a measured location of the vehicle.
Various exemplary embodiments further relate to a method for verifying whether a vehicle is equipped with a functional on-board unit (OBU), including: triggering the OBU to transmit a location of the OBU; updating a database with the location of the OBU, wherein the database includes a correspondence of license plate numbers and OBU information; obtaining a license plate number of the vehicle at a first location; obtaining the location of the OBU from the database by using the correspondence of license plate numbers and OBU information; and determining that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
In some embodiments, the OBU is triggered when the OBU connects to a new cellular base station. In some embodiments, the OBU is triggered by at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call. In some embodiments, the OBU transmits the location of the OBU wirelessly. In some embodiments, the OBU transmits the location of the OBU as at least one of a SMS message, a WIFI message, and a cellular data message. In some embodiments, the method further includes issuing a citation to the registered owner of the license plate if the location reported by the OBU is not within a specified distance of the first location.
BRIEF DESCRIPTION OF THE DRAWINGS
In order to better understand various exemplary embodiments, reference is made to the accompanying drawings, wherein:
FIG. 1 illustrates an embodiment of an on-board unit (OBU);
FIG. 2 illustrates an embodiment of a verification system;
FIG. 3 illustrates an embodiment of a verification method;
FIG. 4 illustrates an alternative embodiment of a verification system; and
FIG. 5 illustrates an alternative embodiment of a verification method.
 DETAILED DESCRIPTION
Referring now to the drawings, in which like numerals refer to like components or steps, there are disclosed broad aspects of various exemplary embodiments.
Toll roads may utilize a variety of payment systems. A common payment system for toll roads is a toll booth. The toll booth may collect a toll from vehicles using the toll road. The toll may be collected by physically giving money to a toll booth attendant or by giving money to an automated machine at the toll booth. Alternatively, the toll may be collected electronically by wireless transceivers at the toll booth. A corresponding wireless transceiver within the vehicle may be triggered when the vehicle passes the wireless transceivers in the toll booth, and money may be deducted from an account associated with the wireless transceiver in the vehicle.
An alternative payment system for toll roads may utilize a terrestrial and/or satellite-based navigation system in lieu of, or in addition to, toll booths. The navigation system may be, for example, a Global Positioning System (GPS), or Global Navigation Satellite System (GLONASS). The navigation system may measure the location of a vehicle to determine if the vehicle is on a toll road. The navigation system may also measure the distance a vehicle travels on the toll road. An applicable toll for the vehicle may be calculated based in part upon the location and distance information from the navigation system. Other factors that may determine the applicable toll may include time and date information (e.g., time of day, day of the week, etc.) and vehicle information (e.g., vehicle weight, fuel type, speed of travel, etc.). The applicable toll may then be paid by a separate payment system. A toll road that utilizes a terrestrial and/or satellite-based navigation system may require that vehicles using the toll road are equipped with an on-board unit (OBU) that includes the systems necessary for the vehicle to determine its location and pay the applicable toll. A toll road that utilizes a terrestrial and/or satellite-based navigation system for the paying of tolls may not include toll booths. Therefore, it may be important to enforce that all vehicles using the toll road are equipped with a properly-functioning OBU, otherwise some vehicles may not pay the applicable toll.
FIG. 1 illustrates an embodiment of an OBU 100. The OBU 100 may include a positioning unit 102 and a billing/communication unit 104. The positioning unit 102 may determine a location of the OBU 100. The positioning unit 102 may utilize a terrestrial and/or satellite-based navigation system, such as, for example, GPS or GLONASS. The billing/communication unit 104 may wirelessly communicate with a payment server (not shown) to pay a vehicle's toll. The billing/communication unit 104 may utilize a wireless communication system such as, for example, Global System for Mobile Communications (GSM) or other cellular communication system.
FIG. 2 illustrates an embodiment of a verification system 200. The verification system 200 may verify if a vehicle is equipped with a functioning OBU 100. The verification system may include a license plate recognition system 204, a license plate/OBU database 206, and an OBU communication system 208. The license plate recognition system 204 may obtain the license plate number of a vehicle using a toll road. The license plate recognition system 204 may obtain the license plate number automatically through the use of a camera and recognition software. Alternatively, the license plate number may be manually entered into the license plate recognition system 204 by toll enforcement personnel. The license plate recognition system 204 may use the license plate number to look up OBU information in the license plate/OBU database 206. When a vehicle is equipped with an OBU 100, information about the OBU 100 may be associated with the vehicle's license plate number and stored in the license plate/OBU database 206. The license plate/OBU database 206 may include multiple, cross-referenced databases, such as a license plate/vehicle owner database and an OBU/vehicle owner database. An OBU communication system 208 may receive the OBU information that corresponds with the license plate number. The OBU information may include information necessary to contact the billing/communication unit 104 of the OBU 100, such as, for example, a GSM identification number. If the license plate/OBU database 206 does not have a record of the license plate number, or if the license plate/OBU database 206 indicates that the license plate number does not have any corresponding OBU information, then the OBU communication system 208 may issue a citation to the registered owner of the license plate and/or alert toll enforcement personnel.
The OBU communication system 208 may send a request to the OBU 100 for the OBU 100 to report its current position. The request may be received by the billing/communication unit 104 of the OBU 100. The request from the OBU communication system 208 may be in the form of a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or an incoming telephone call. The request from the OBU communication system 208 may include a time-stamp. The OBU 100 may respond to the request with vehicle identification information and vehicle location information. The vehicle identification information may include, for example, license plate number, vehicle identification number (VIN), vehicle brand, vehicle type, vehicle color, fuel type, pollution class, vehicle weight, vehicle size, and/or presence of hazardous materials. The vehicle location information may identify the location of the OBU 100 at a certain point in time. If the request from the OBU communication system 208 included a time-stamp, then the vehicle location information reported by the OBU 100 may correspond to a location of the vehicle at approximately the point in time of the time-stamp. If the request from the OBU communication system 208 did not include a time-stamp, then the vehicle location information reported by the OBU 100 may correspond to a location of the vehicle at approximately the point in time that the request was received. The vehicle location information may include, for example, GPS coordinates, GLONASS coordinates, latitude/longitude, a region name, and/or a road name, as well as a time and date that the location was determined. The response from the OBU 100 may be transmitted to the OBU communication system 208 using the billing/communication unit 104 of the OBU 100. The response from the OBU 100 may be transmitted in the form of a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or any other suitable message. The response from the OBU 100 may be encrypted and/or signed to verify the integrity of the response.
Additionally, the OBU 100 may respond to the request from the communication system 208 with additional information, such as integrity information, diagnostic information, and/or toll information. The integrity information may indicate whether any components and/or software of the OBU 100 have been tampered with. The diagnostic information may indicate whether any components and/or software of the OBU 100 are not operating correctly. The toll information may indicate the current toll mode the OBU 100 is operating under (e.g., rush hour or off-peak).
The OBU communication system 208 may transmit the response from the OBU 100 to a verification module 210. The verification module 210 may be a module of the OBU communication system 208, the license plate/OBU database 206, the license plate recognition system 204, or may be a separate, individual module. The verification module 210 may use the response from the OBU 100 to verify if the location of the OBU 100 is within a certain range of the license plate recognition system 204. The verification module 210 may also verify that the vehicle identification information from the OBU 100 matches the information in the license plate/OBU database 206. The verification module 210 may use the response from the OBU 100 to determine if the OBU 100 is present in the vehicle that was checked by the license plate recognition system 204. The OBU 100 may be assumed to be present in the vehicle if the OBU 100 reports its location as near (for example, within 100 m) to the location where the license plate recognition system 204 obtained the license plate number of the vehicle. If the verification module 210 determines that the OBU 100 is not present in the vehicle, or if the OBU communication system 208 does not receive a response from the OBU 100, then the OBU communication system 208 may record the license plate number and/or vehicle identification information, and issue a citation to the registered owner of the license plate. Alternatively or in addition, if the verification module 210 determines that the OBU 100 is not present in the vehicle, or if the OBU communication system 208 does not receive a response from the OBU 100, then the OBU communication system 208 may alert toll enforcement personnel.
FIG. 3 illustrates an embodiment of a verification method 300. The verification method 300 may begin when a vehicle enters an OBU verification region at step 302. Once in the OBU verification region, information about the vehicle such as, for example, the vehicle license plate number, may be obtained at step 304. At step 306, an OBU/vehicle database may be accessed that contains OBU information associated with vehicle information. At step 308, the verification method 300 may determine if the vehicle has an associated OBU. If the vehicle does not have an associated OBU, then the verification method 300 may issue a citation to the registered owner of the license plate and/or alert toll enforcement personnel at step 310.
If the vehicle has an associated OBU, then the verification method 300 may use the OBU information in the OBU database to send a trigger to the OBU associated with the vehicle to report its location at step 312. The OBU associated with the vehicle may be triggered by sending a message over a wireless communication network, such as, for example, a GSM network. The message may be, for example, a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or a cellular telephone call. At step 314, the verification method 300 may determine if the OBU associated with the vehicle sent a valid response to the trigger message. If no valid response is received from the OBU associated with the vehicle, then the verification method 300 may issue a citation and/or alert toll enforcement personnel at step 310. If a valid response is received from the OBU associated with the vehicle, then the verification method 300 may extract information from the response at step 316. The response from the OBU associated with the vehicle may include the location of the OBU at the approximate time the trigger message was received. If the trigger message included a time-stamp, then the response from the OBU associated with the vehicle may include the location of the OBU at the approximate time of the time-stamp. The response may also include other information, such as vehicle information, time and date information, and/or other enforcement information (e.g., vehicle speed, number of passengers, seatbelt status, etc.). The response from the OBU associated with the vehicle may be sent over a wireless communication network, such as, for example a GSM network. The response may be, for example, a SMS message or a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.).
After extracting the location information from the response of the OBU associated the vehicle, the verification method 300 may determine if the OBU is present in the vehicle and functioning properly at step 318. The verification method 300 may assume that the OBU is present in the vehicle and functioning properly if the OBU reports its location as near (for example, within 100 m) to the location where the vehicle information was obtained. If the verification method 300 determines that the OBU that sent the response is not present in the vehicle, then the verification method 300 may issue a citation and/or alert toll enforcement personnel at step 310. If the verification method 300 determines that the OBU that sent the response is present in the vehicle and functioning properly, then the OBU associated with the vehicle may pay an applicable toll at step 320. The applicable toll may be paid immediately upon calculation by the OBU, or may be paid at a later time. The verification method 300 ends at step 322.
FIG. 4 illustrates an alternative embodiment of a verification system 400. The verification system 400 may verify if a vehicle is equipped with a functioning OBU 100. The verification system may include an OBU trigger 402, a license plate recognition system 404, a license plate/OBU database 406, and an OBU communication system 408. The OBU trigger 402 may trigger the OBU 100 to report its current position. The OBU trigger 402 may be a wireless checkpoint, such as, for example a cellular base station or a toll booth. The trigger from the OBU trigger 402 may be received by the billing/communication unit 104 of the OBU 100. The trigger from the OBU trigger 402 may be in the form of a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), an incoming telephone call, or other wireless signals (e.g., infrared, radio-frequency, etc.). The trigger from the OBU trigger 402 may include a time-stamp. Alternatively, the OBU 100 may be triggered to report its position whenever the billing/communication unit 104 connects to a new cellular base station. The OBU 100 may respond to the trigger with vehicle identification information and vehicle location information. The vehicle identification information may include, for example, license plate number, vehicle identification number (VIN), vehicle brand, vehicle type, vehicle color, fuel type, pollution class, vehicle weight, vehicle size, and/or presence of hazardous materials. The vehicle location information may identify the location of the OBU 100 at a certain point in time. If the trigger from the OBU trigger 402 included a time-stamp, then the vehicle location information reported by the OBU 100 may correspond to a location of the vehicle at approximately the point in time of the time-stamp. If the trigger from the OBU trigger 402 did not include a time-stamp, then the vehicle location information reported by the OBU 100 may correspond to a location of the vehicle at approximately the point in time that the trigger was received. The vehicle location information may include, for example, GPS coordinates, GLONASS coordinates, latitude/longitude, a region name, and/or a road name, as well as a time and date that the location was determined. The response from the OBU 100 may be transmitted to the OBU communication system 408 using the billing/communication unit 104 of the OBU 100. The response from the OBU 100 may be transmitted in the form of a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or any other suitable message. The response from the OBU 100 may be encrypted and/or signed to verify the integrity of the response.
Additionally, the OBU may respond to the trigger with additional information, such as integrity information, diagnostic information, and/or toll information. The integrity information may indicate whether any components and/or software of the OBU 100 have been tampered with. The diagnostic information may indicate whether any components and/or software of the OBU 100 are not operating correctly. The toll information may indicate the current toll mode the OBU 100 is operating under (e.g., rush hour or off-peak).
The OBU communication system 408 may use the response from the OBU 100 to update the license plate/OBU database 406. When a vehicle is equipped with an OBU 100, information about the OBU 100 may be associated with the vehicle's license plate number and stored in the license plate/OBU database 406. The license plate/OBU database 406 may include multiple, cross-referenced databases, such as a license plate/vehicle owner database and an OBU/vehicle owner database. The license plate/OBU database 406 may be updated to indicate the license plate numbers associated with the OBUs triggered by the OBU trigger 402. In this way, the license plate/OBU database 406 may indicate the license plate numbers for vehicles that are known to be in a desired geographic region.
The license plate recognition system 404 may obtain the license plate number of a vehicle using a toll road. The license plate recognition system 404 may obtain the license plate number automatically through the use of a camera and recognition software. The license plate/OBU database 406 may aid the recognition software in obtaining the license plate number by indicating the license plate numbers of vehicles that are known to be in the region (for example, within 100 m) of the license plate recognition system 404. In this way, the license plate recognition system 404 may predict which license plate numbers are likely to be in the camera's view. Alternatively, the license plate number may be manually entered into the license plate recognition system 404 by toll enforcement personnel.
The license plate recognition system 404 may transmit the license plate number to a verification module 410. The verification module 410 may be a module of the OBU communication system 408, the license plate/OBU database 406, the license plate recognition system 404, or may be a separate, individual module. The verification module 410 may use the license plate number to look up OBU information in the license plate/OBU database 406. The verification module 410 may use the license plate number and OBU information to verify if the vehicle is equipped with a functioning OBU 100. If the license plate number indicates that the vehicle was already known to be in the region of the license plate recognition system 404, then the verification module 410 may assume that the vehicle is equipped with a functioning OBU 100. If the license plate/OBU database 406 does not have a record of the license plate number, or if the license plate/OBU database 406 indicates that the license plate number associated with the OBU 100 is not in the region of the license plate recognition system 404, then the verification module 410 may issue a citation to the registered owner of the license plate and/or alert toll enforcement personnel. If toll enforcement personnel are alerted, the OBU 100 may be configured to periodically transmit position updates to aid the toll enforcement personnel in locating the vehicle.
FIG. 5 illustrates an alternative embodiment of a verification method 500. The verification method 500 may begin when a vehicle enters an OBU verification region at step 502. Once in the OBU verification region, an OBU associated with the vehicle may be triggered to report its location at step 504. At step 506, the verification method 500 may determine if the OBU associated with the vehicle sent a response to the trigger message. If no response is received from the OBU associated with the vehicle, then the verification method 500 may issue a citation and/or alert toll enforcement personnel at step 508. If a response is received from the OBU associated with the vehicle, then the verification method 500 may extract information from the response at step 510. The response from the OBU associated with the vehicle may include the location of the OBU at the approximate time the trigger message was received. If the trigger message included a time-stamp, then the response from the OBU associated with the vehicle may include the location of the OBU at the approximate time of the time-stamp. The response may also include other information, such as vehicle information and time and date information. The response from the OBU associated with the vehicle may be sent over a cellular communication network, such as, for example a GSM network. The response may be, for example, a SMS message, a wireless data message (e.g., GPRS, UMTS, LTE, WIFI, etc.), or any other suitable message. At step 512, an OBU/vehicle database may be updated to indicate vehicles that are associated with the OBUs that responded to the trigger.
Information about the vehicle such as, for example, the vehicle license plate number, may be obtained at step 514. At step 516, the verification method 500 may determine if the vehicle has an associated OBU by comparing the vehicle information obtained in step 514 to the updated information in the OBU/vehicle database. If the vehicle does not have an associated OBU, then the verification method 500 may issue a citation to the registered owner of the license plate and/or alert toll enforcement personnel at step 508. If the vehicle has an associated OBU, then the OBU may pay an applicable toll at step 518. The applicable toll may be paid immediately upon calculation by the OBU, or may be paid at a later time. The verification method 500 ends at step 520.
According to the foregoing, various exemplary embodiments provide for a system and method for verifying if a vehicle is equipped with a functional OBU.
It should be apparent from the foregoing description that various exemplary embodiments of the invention may be implemented in hardware and/or firmware. Furthermore, various exemplary embodiments may be implemented as instructions stored on a tangible and non-transitory machine-readable storage medium, which may be read and executed by at least one processor to perform the operations described in detail herein. A tangible and non-transitory machine-readable storage medium may include any mechanism for storing information in a form readable by a machine, such as a personal or laptop computer, a server, or other computing device. Thus, a machine-readable storage medium may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and similar storage media.
It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principals of the invention. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in machine readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
Although the various exemplary embodiments have been described in detail with particular reference to certain exemplary aspects thereof, it should be understood that the invention is capable of other embodiments and its details are capable of modifications in various obvious respects. As is readily apparent to those skilled in the art, variations and modifications can be affected while remaining within the spirit and scope of the invention. Accordingly, the foregoing disclosure, description, and figures are for illustrative purposes only and do not in any way limit the invention, which is defined only by the claims.

Claims (20)

What is claimed is:
1. A verification system for verifying whether a vehicle is equipped with a functional on-board unit (OBU), the verification system comprising:
a license plate recognition systema memory configured to obtainstore a license plate number of the vehicle; the license plate number obtained by a license plate recognition system at a first location;
a database of license plate numbers and OBU information, wherein the database includes a correspondence of license plate numbers and OBU information;
a wireless communication system operably connected to a wireless communication network, wherein the wireless communication system is configured to send a trigger message over the wireless communication network to the OBU using the OBU information corresponding to the license plate number to trigger the OBU to send a response, and configured to receive a the response over the wireless communication network from the OBU indicating a location of the OBU; and
a verification modulea processor operably connected to the wireless communication system to receive the OBU response from the wireless communication system and configured to determine whether the vehicle is equipped with the OBU, wherein the verification moduleprocessor determines that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
2. The verification system of claim 1, wherein the trigger message is sent wirelessly, and wherein the response from the OBU is received wirelessly.
3. The verification system of claim 1, wherein the trigger message is at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call.
4. The verification system of claim 1, wherein the response from the OBU is at least one of a SMS message, a WIFI message, and a cellular data message.
5. The verification system of claim 1, wherein the verification system issues a citation to the owner of the license plate if the location reported by the OBU is not within a specified distance of the first location.
6. The verification system of claim 1, wherein the verification system issues a citation to the owner of the license plate if the license plate number obtained by the license plate recognition system does not have corresponding OBU information in the database.
7. The verification system of claim 1, wherein the verification system receives a toll payment from the OBU based upon a measured location of the vehicle.
8. A method for verifying whether a vehicle is equipped with a functional on-board unit (OBU), comprising:
obtainingreceiving from a license plate recognition system, a license plate number of the vehicle; the license plate number obtained by a license plate recognition system at a first location;
obtaining OBU information that corresponds to the license plate number;
sending a trigger message to the OBU using the OBU information;
receiving a response from the OBU indicating a location of the OBU; and
determining that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
9. The method of claim 8, wherein the trigger message is sent wirelessly, and wherein the response from the OBU is received wirelessly.
10. The method of claim 8, wherein the trigger message is at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call.
11. The method of claim 8, wherein the response from the OBU is at least one of a SMS message, a WIFI message, and a cellular data message.
12. The method of claim 8, further comprising:
issuing a citation to the registered owner of the license plate if the location reported by the OBU is not within a specified distance of the first location.
13. The method of claim 8, further comprising:
issuing a citation to the registered owner of the license plate if the OBU information cannot be obtained from the license plate number.
14. The method of claim 8, further comprising:
receiving a toll payment from the OBU based upon a measured location of the vehicle.
15. A method for verifying whether a vehicle is equipped with a functional on-board unit (OBU), comprising:
triggering the OBU to transmit a location of the OBU;
updating a database with the location of the OBU, wherein the database includes a correspondence of license plate numbers and OBU information;
obtainingreceiving from a license plate recognition system, a license plate number of the vehicle; the license plate number obtained by a license plate recognition system at a first location;
obtaining the location of the OBU from the database by using the correspondence of license plate numbers and OBU information; and
determining that the vehicle is equipped with the OBU if the location reported by the OBU is within a specified distance of the first location.
16. The method of claim 15, wherein the OBU is triggered when the OBU connects to a new cellular base station.
17. The method of claim 15, wherein the OBU is triggered by at least one of a SMS message, a cellular data message, a WIFI message, and a cellular telephone call.
18. The method of claim 15, wherein the OBU transmits the location of the OBU wirelessly.
19. The method of claim 15, wherein the OBU transmits the location of the OBU as at least one of a SMS message, a WIFI message, and a cellular data message.
20. The method of claim 15, further comprising:
issuing a citation to the registered owner of the license plate if the location reported by the OBU is not within a specified distance of the first location.
US14/925,055 2012-02-06 2015-10-28 System and method for verifying whether a vehicle is equipped with a functional on-board unit Active 2032-07-25 USRE47482E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/925,055 USRE47482E1 (en) 2012-02-06 2015-10-28 System and method for verifying whether a vehicle is equipped with a functional on-board unit

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/366,852 US8570164B2 (en) 2012-02-06 2012-02-06 System and method for verifying whether a vehicle is equipped with a functional on-board unit
US14/925,055 USRE47482E1 (en) 2012-02-06 2015-10-28 System and method for verifying whether a vehicle is equipped with a functional on-board unit

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13/366,852 Reissue US8570164B2 (en) 2012-02-06 2012-02-06 System and method for verifying whether a vehicle is equipped with a functional on-board unit

Publications (1)

Publication Number Publication Date
USRE47482E1 true USRE47482E1 (en) 2019-07-02

Family

ID=47739042

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/366,852 Ceased US8570164B2 (en) 2012-02-06 2012-02-06 System and method for verifying whether a vehicle is equipped with a functional on-board unit
US14/925,055 Active 2032-07-25 USRE47482E1 (en) 2012-02-06 2015-10-28 System and method for verifying whether a vehicle is equipped with a functional on-board unit

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US13/366,852 Ceased US8570164B2 (en) 2012-02-06 2012-02-06 System and method for verifying whether a vehicle is equipped with a functional on-board unit

Country Status (3)

Country Link
US (2) US8570164B2 (en)
EP (1) EP2624219A3 (en)
CN (1) CN103247080B (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103522935B (en) * 2013-09-24 2015-10-28 浙江吉利控股集团有限公司 A kind of method that recognition of license plate is reminded and device
CN104900052B (en) * 2014-03-06 2019-11-12 富顶精密组件（深圳）有限公司 Traffic surveillance and control system
CN104766384A (en) * 2015-04-25 2015-07-08 吕曦轩 No-parking network charging system based on vehicle license plate recognition technology
NO341801B1 (en) * 2016-01-04 2018-01-22 Apace Resources As System and Method for charging means of transport
CN106326945A (en) * 2016-08-09 2017-01-11 北京万集科技股份有限公司 Secondary issuing system and method for OBU (on-board unit)
CN107967722A (en) * 2017-12-15 2018-04-27 北京万集科技股份有限公司 Current charging method, device, storage medium and the processor of highway
US10964127B2 (en) * 2018-01-12 2021-03-30 Ford Global Technologies, Llc Method and apparatus for managed vehicular toll payments
CN110189425A (en) * 2019-05-27 2019-08-30 武汉万集信息技术有限公司 Multilane free-flow vehicle detection method and system based on binocular vision
CN110517360A (en) * 2019-07-19 2019-11-29 西安艾润物联网技术服务有限责任公司 Parking fee method of payment, system and device
CN113115308B (en) * 2021-03-10 2023-02-28 北京万集智能网联技术有限公司 Secondary issuing method and authentication method for vehicle-mounted unit and related product
EP4163884A1 (en) * 2021-10-08 2023-04-12 Toll Collect GmbH Method and system for automatic control in a toll system

Citations (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6140941A (en) * 1997-01-17 2000-10-31 Raytheon Company Open road cashless toll collection system and method using transponders and cameras to track vehicles
EP1088286A2 (en) 1998-06-18 2001-04-04 MANNESMANN Aktiengesellschaft Roadside control device for a toll apparatus installed in a motor vehicle
EP1200938A1 (en) 1999-08-04 2002-05-02 Vodafone AG Control unit for verifying proper functioning of toll devices installed in vehicles
JP2002133581A (en) 2000-10-27 2002-05-10 Nippon Telegr & Teleph Corp <Ntt> Road monitoring system and method
US20020084889A1 (en) * 1998-07-30 2002-07-04 Joseph T. Bolavage Interrogating tags on multiple frequencies and synchronizing databases using transferable agents
US6868313B2 (en) 2003-08-08 2005-03-15 Reino Koljonen Automobile license tag scanning system
EP1519322A2 (en) 2003-09-27 2005-03-30 Jonathan Wallach Payment system and method
US20050197976A1 (en) * 2004-03-03 2005-09-08 Tuton James D. System and method for processing toll transactions
US20060063563A1 (en) * 2004-09-18 2006-03-23 Kaufman Richard D Cell phone system with automatic ringer/vibrate/silent/operating mode settings based on entering/exiting public areas and theaters
CN1828686A (en) 2006-04-13 2006-09-06 王江年 Vehicle overload managing system
US20060258367A1 (en) 2005-05-16 2006-11-16 Chiang Tung C Using cell phones and wireless cellular systems with location capability for toll paying and collection
US20060278705A1 (en) * 2003-02-21 2006-12-14 Accenture Global Services Gmbh Electronic Toll Management and Vehicle Identification
US7161563B2 (en) 2001-12-17 2007-01-09 General Motors Corporation Electronic vehicle registration and license plate
CN1932920A (en) 2005-09-15 2007-03-21 现代奥途纳特株式会社 Vehicle driver guarding system using vehicle telematics service and control method thereof
EP1783692A2 (en) 2005-10-06 2007-05-09 Siemens Aktiengesellschaft Enforcement with reduced turnaround times
EP1860615A2 (en) 2006-05-26 2007-11-28 Siemens Aktiengesellschaft Method for checking the operation of a mobile detection unit
US20080068180A1 (en) * 2006-09-11 2008-03-20 Powell Steven W Radio frequency identification tag embedded in the windshields of vehicle for wirelessly determining vehicle identification, location and toll collection
US7385525B2 (en) * 2005-07-07 2008-06-10 Mark Iv Industries Corporation Dynamic timing adjustment in an electronic toll collection system
CN101251954A (en) 2008-04-01 2008-08-27 郭建国 Vehicle GPS positioning distance measuring and vehicle electronic license tag information terminal
US20090016819A1 (en) * 2007-07-09 2009-01-15 Patrick Vu Electronic barrier and enforcement system and method
CN101350109A (en) 2008-09-05 2009-01-21 交通部公路科学研究所 Method for locating and controlling multilane free flow video vehicle
CN201207221Y (en) 2008-03-14 2009-03-11 康华武 Automatic checking system for road vehicle identity
CN201226156Y (en) 2008-04-28 2009-04-22 交通部公路科学研究所 Novel highway charging system without parking
US7705750B2 (en) * 2005-03-22 2010-04-27 Kapsch Trafficcom Ab System for use in stations for road tolls
US7774228B2 (en) * 2006-12-18 2010-08-10 Rent A Toll, Ltd Transferring toll data from a third party operated transport to a user account
JP2011113508A (en) 2009-11-30 2011-06-09 Toshiba Corp Toll collection system of toll road
WO2011073899A1 (en) * 2009-12-16 2011-06-23 Nxp Bv Data processing apparatus
US20130018705A1 (en) * 2011-03-07 2013-01-17 Intelligent Imaging Systems, Inc. Vehicle traffic and vehicle related transaction control system
US20130124306A1 (en) * 2011-11-14 2013-05-16 Google Inc. Voucher code redemption via sms
US20130170711A1 (en) * 2012-01-04 2013-07-04 Cyclops Technologies, Inc. Edge detection image capture and recognition system
US9269197B2 (en) * 2009-11-23 2016-02-23 Kapsch Trafficcom Ag Method and device for generating toll information in a road-toll system

Patent Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6140941A (en) * 1997-01-17 2000-10-31 Raytheon Company Open road cashless toll collection system and method using transponders and cameras to track vehicles
EP1088286A2 (en) 1998-06-18 2001-04-04 MANNESMANN Aktiengesellschaft Roadside control device for a toll apparatus installed in a motor vehicle
US20020084889A1 (en) * 1998-07-30 2002-07-04 Joseph T. Bolavage Interrogating tags on multiple frequencies and synchronizing databases using transferable agents
EP1200938A1 (en) 1999-08-04 2002-05-02 Vodafone AG Control unit for verifying proper functioning of toll devices installed in vehicles
JP2002133581A (en) 2000-10-27 2002-05-10 Nippon Telegr & Teleph Corp <Ntt> Road monitoring system and method
US7161563B2 (en) 2001-12-17 2007-01-09 General Motors Corporation Electronic vehicle registration and license plate
US20060278705A1 (en) * 2003-02-21 2006-12-14 Accenture Global Services Gmbh Electronic Toll Management and Vehicle Identification
US6868313B2 (en) 2003-08-08 2005-03-15 Reino Koljonen Automobile license tag scanning system
EP1519322A2 (en) 2003-09-27 2005-03-30 Jonathan Wallach Payment system and method
US20050197976A1 (en) * 2004-03-03 2005-09-08 Tuton James D. System and method for processing toll transactions
US20060063563A1 (en) * 2004-09-18 2006-03-23 Kaufman Richard D Cell phone system with automatic ringer/vibrate/silent/operating mode settings based on entering/exiting public areas and theaters
US7705750B2 (en) * 2005-03-22 2010-04-27 Kapsch Trafficcom Ab System for use in stations for road tolls
US20060258367A1 (en) 2005-05-16 2006-11-16 Chiang Tung C Using cell phones and wireless cellular systems with location capability for toll paying and collection
US7385525B2 (en) * 2005-07-07 2008-06-10 Mark Iv Industries Corporation Dynamic timing adjustment in an electronic toll collection system
CN1932920A (en) 2005-09-15 2007-03-21 现代奥途纳特株式会社 Vehicle driver guarding system using vehicle telematics service and control method thereof
EP1783692A2 (en) 2005-10-06 2007-05-09 Siemens Aktiengesellschaft Enforcement with reduced turnaround times
CN1828686A (en) 2006-04-13 2006-09-06 王江年 Vehicle overload managing system
EP1860615A2 (en) 2006-05-26 2007-11-28 Siemens Aktiengesellschaft Method for checking the operation of a mobile detection unit
US20080068180A1 (en) * 2006-09-11 2008-03-20 Powell Steven W Radio frequency identification tag embedded in the windshields of vehicle for wirelessly determining vehicle identification, location and toll collection
US7774228B2 (en) * 2006-12-18 2010-08-10 Rent A Toll, Ltd Transferring toll data from a third party operated transport to a user account
US20090016819A1 (en) * 2007-07-09 2009-01-15 Patrick Vu Electronic barrier and enforcement system and method
CN201207221Y (en) 2008-03-14 2009-03-11 康华武 Automatic checking system for road vehicle identity
CN101251954A (en) 2008-04-01 2008-08-27 郭建国 Vehicle GPS positioning distance measuring and vehicle electronic license tag information terminal
CN201226156Y (en) 2008-04-28 2009-04-22 交通部公路科学研究所 Novel highway charging system without parking
CN101350109A (en) 2008-09-05 2009-01-21 交通部公路科学研究所 Method for locating and controlling multilane free flow video vehicle
US9269197B2 (en) * 2009-11-23 2016-02-23 Kapsch Trafficcom Ag Method and device for generating toll information in a road-toll system
JP2011113508A (en) 2009-11-30 2011-06-09 Toshiba Corp Toll collection system of toll road
US9015497B2 (en) * 2009-12-16 2015-04-21 Telit Automotive Solutions Nv Data processing apparatus
WO2011073899A1 (en) * 2009-12-16 2011-06-23 Nxp Bv Data processing apparatus
US20130018705A1 (en) * 2011-03-07 2013-01-17 Intelligent Imaging Systems, Inc. Vehicle traffic and vehicle related transaction control system
US20130124306A1 (en) * 2011-11-14 2013-05-16 Google Inc. Voucher code redemption via sms
US20130170711A1 (en) * 2012-01-04 2013-07-04 Cyclops Technologies, Inc. Edge detection image capture and recognition system

Also Published As

Publication number Publication date
US8570164B2 (en) 2013-10-29
EP2624219A2 (en) 2013-08-07
EP2624219A3 (en) 2017-01-11
CN103247080A (en) 2013-08-14
CN103247080B (en) 2016-03-23
US20130201011A1 (en) 2013-08-08

Similar Documents

Publication Publication Date Title
USRE47482E1 (en) System and method for verifying whether a vehicle is equipped with a functional on-board unit
US20210049725A1 (en) Vehicle traffic and vehicle related transaction control system
EP1993075B1 (en) Route Usage Evaluation
US11847586B2 (en) Method and apparatus for determining a road usage charge
CA2850250C (en) Vehicle traffic and vehicle related transaction control system
US8797181B2 (en) Control devices and methods for a road toll system
WO2012112877A1 (en) System and method for gps lane and toll determination and asset position matching
US9934682B2 (en) Systems and methods for monitoring roadways using magnetic signatures
CN103679825A (en) Method for electronically processing a traffic offense and onboard-unit therefor
US20200258383A1 (en) Systems and Methods for Monitoring Roadways
EP3002735A1 (en) Method and communication system of a public module interface of a data exchange system using NFC technology
US11620629B2 (en) Sensor device and system for communicating information
US20020120590A1 (en) Electronic taximeter
WO2017063052A1 (en) Automatic detection of a toll for a vehicle
KR102507929B1 (en) Terminal device, rear server, vehicle-mounted transponder, judgment system, judgment method, and program
Donath et al. Technology enabling near-term nationwide implementation of distance based road user fees
CN107067479A (en) A kind of system for vehicle of charging
US20240152980A1 (en) Method and apparatus for determining a road usage charge
Porter et al. Performance evaluation of an RFID-based vehicle-miles-travelled revenue collection system

Legal Events

Date Code Title Description
AS Assignment

Owner name: NXP B.V., NETHERLANDS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NIEUWLAND, ANDRE;DAALDEROP, GERARDO;SIGNING DATES FROM 20120130 TO 20120131;REEL/FRAME:039474/0481

Owner name: TELIT AUTOMOTIVE SOLUTIONS NV, BELGIUM

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NXP B.V.;REEL/FRAME:039474/0517

Effective date: 20140331

AS Assignment

Owner name: HSBC BANK PLC, UNITED KINGDOM

Free format text: SECURITY INTEREST;ASSIGNOR:TELIT AUTOMOTIVE SOLUTIONS NV;REEL/FRAME:040007/0201

Effective date: 20161013

AS Assignment

Owner name: TELIT AUTOMOTIVE SOLUTIONS NV, BELGIUM

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:HSBC BANK PLC;REEL/FRAME:048466/0594

Effective date: 20190227

AS Assignment

Owner name: TITAN AUTOMOTIVE SOLUTIONS NV, BELGIUM

Free format text: CHANGE OF NAME;ASSIGNOR:TELIT AUTOMOTIVE SOLUTIONS NV;REEL/FRAME:051857/0882

Effective date: 20190523

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8

AS Assignment

Owner name: TITAN INTELLIGENCE TECHNOLOGY LIMITED, HONG KONG

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TITAN AUTOMOTIVE SOLUTIONS NV;REEL/FRAME:058686/0883

Effective date: 20211112