U.S. patent application number 12/437782 was filed with the patent office on 2009-09-10 for toll fee system and method.
Invention is credited to Debbie Lemon, Benjamin P. Robinson.
Application Number | 20090228350 12/437782 |
Document ID | / |
Family ID | 35394807 |
Filed Date | 2009-09-10 |
United States Patent
Application |
20090228350 |
Kind Code |
A1 |
Robinson; Benjamin P. ; et
al. |
September 10, 2009 |
TOLL FEE SYSTEM AND METHOD
Abstract
A toll fee tracking system comprising a toll authority adapted
to collect data associated with at least one toll fee tracking
device and a toll rental entity adapted to communicate with the
toll authority and a third part entity. This Abstract is provided
to comply with rules requiring an Abstract that allows a searcher
or other reader to quickly ascertain subject matter of the
technical disclosure. This Abstract is submitted with the
understanding that it will not be used to interpret or limit the
scope or meaning of the claims.
Inventors: |
Robinson; Benjamin P.;
(Plano, TX) ; Lemon; Debbie; (Carrollton,
TX) |
Correspondence
Address: |
WINSTEAD PC
P.O. BOX 50784
DALLAS
TX
75201
US
|
Family ID: |
35394807 |
Appl. No.: |
12/437782 |
Filed: |
May 8, 2009 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11985985 |
Nov 19, 2007 |
|
|
|
12437782 |
|
|
|
|
11125521 |
May 10, 2005 |
7407097 |
|
|
11985985 |
|
|
|
|
60569779 |
May 10, 2004 |
|
|
|
60657235 |
Feb 28, 2005 |
|
|
|
Current U.S.
Class: |
705/13 ; 705/34;
705/40; 709/204 |
Current CPC
Class: |
G06Q 40/12 20131203;
G07B 15/04 20130101; G07B 15/063 20130101; G06Q 20/102 20130101;
G06Q 30/04 20130101 |
Class at
Publication: |
705/13 ; 705/34;
705/40; 709/204 |
International
Class: |
G06Q 50/00 20060101
G06Q050/00; G06Q 30/00 20060101 G06Q030/00; G06Q 20/00 20060101
G06Q020/00; G06F 15/16 20060101 G06F015/16 |
Claims
1. A computer readable medium comprising instructions for:
identifying a transponder; activating the transponder responsive to
a determination that an automatic toll payment service option has
been accepted by a customer; collecting toll usage data if the
identified transponder has a valid toll rental entity account;
retrieving the data responsive to a request for data-transfer
permission having been received by a toll authority from a toll
rental entity; updating the data; sending the updated data; and
sending an invoice with charges related to the updated data.
2. The computer readable medium of claim 1, wherein identifying the
transponder includes reading transponder data that includes at
least one of: vehicle-class-identifier, transaction time;
transaction date; lane traffic activity information; transponder
identification number; toll gate identification; vehicle travel
direction; and an amount of toll usage.
3. The computer readable medium of claim 1, comprising instructions
for processing data by the toll authority if the identified
transponder does not have said valid toll rental entity
account.
4. The computer readable medium of claim 1, wherein the request is
transmitted during at least one of: at predefined regular
intervals; continuously in real-time; and in near real-time.
5. The computer readable medium of claim 1, comprising instructions
for sending the data if the request for data-transfer permission
has not been received.
6. The computer readable medium of claim 1, comprising instructions
for charging a service fee and activating the transponder if the
transponder is being used for a first time.
7. The computer readable medium of claim 1, comprising instructions
for halting any transactions by the transponder after the sending
of the updated data.
8. The computer readable medium of claim 1, wherein the invoice
includes charges for at least one of: toll usage; and third party
entity services usage.
9. A toll rental entity server for communicating data between a
toll authority and a third party entity, the server comprising: a
first interface for communicating with said toll authority; at
least one database; a second interface for communicating with said
third party entity; said toll rental entity server further
comprising a processor communicably coupled to the first interface;
said toll rental entity server further comprising a plurality of
function modules communicably coupled to the processor; said at
least one database communicably coupled to the plurality of
function modules and to the second interface; said processor is
operable to receive the data, analyze the data and forward a
request message to at least one of the plurality of function
modules for performing a plurality of tasks; and wherein the
plurality of tasks performed by the at least one of the plurality
of function modules comprise: maintaining and updating toll rental
entity accounts; bill handling; payment handling; and error
handling.
10. A toll fee tracking system comprising: a toll authority
operable to collect data associated with at least one toll fee
tracking device; a toll rental entity operable to communicate with
said toll authority and a third party entity; wherein at least some
of the collected data is transferred from the toll authority to the
toll rental entity; and wherein at least some of the collected data
is transferred from the toll rental entity to the third party
entity responsive to a request for data-transfer permission from
the third party entity to the toll rental entity.
11. A method of toll fee tracking, the method comprising:
providing, to a customer, an automatic toll payment service option;
determining whether the automatic toll payment service option is
accepted by the customer; responsive to a determination that the
automatic toll payment service option has been accepted, activating
at least one toll fee tracking device during a rental period;
collecting, at a toll authority, data associated with the least one
toll fee tracking device; storing said data in at least one
database of said toll authority; transferring, from the toll
authority to a toll rental entity via a toll authority interface,
at least some of the collected and stored data in a toll rental
entity database responsive to a request for data-transfer
permission from the toll rental entity to the toll authority via
the toll authority interface; forwarding, from the toll rental
entity to a third party entity via a third party entity interface,
at least some of the transferred data; and charging the customer a
fee corresponding to toll usage and applicable service charges
based upon the forwarded data.
12. The method of claim 11, comprising, responsive to a
determination that the automatic toll payment service option has
been denied, deactivating the at least one toll fee tracking
device.
13. The method of claim 12, wherein the at least one toll fee
tracking device remains deactivated until the customer returns a
vehicle to the third party entity.
14. The method of claim 12, wherein the at least one toll fee
tracking device remains deactivated until the customer uses a toll
gate of the toll authority.
15. The method of claim 12, comprising transferring an automatic
toll payment service request message to the toll authority.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of and claims priority
from U.S. patent application Ser. No. 11/985,985, titled Toll Fee
System And Method, filed on Nov. 19, 2007. U.S. patent application
Ser. No. 11/985,985 is a continuation of and claims priority from
U.S. patent application Ser. No. 11/125,521, titled Toll Fee System
And Method, filed on May 10, 2005 now U.S. Pat. No. 7,407,097. U.S.
patent application Ser. No. 11/125,521 claims priority from and
incorporates by reference the entire disclosure of U.S. Provisional
Patent Application No. 60/569,779, which was filed on May 10, 2004.
U.S. patent application Ser. No. 11/125,521 further claims priority
from and incorporates by reference the entire disclosure of U.S.
Provisional Patent Application No. 60/657,235, which was filed on
Feb. 28, 2005. U.S. patent application Ser. No. 11/985,985, U.S.
Pat. No. 7,047,097, U.S. Provisional Patent Application No.
60/569,779, and U.S. Provisional Patent Application No. 60/657,235
are incorporated herein by reference.
BACKGROUND OF THE INVENTION
[0002] 1. Technical Field
[0003] The present invention relates generally to toll fee tracking
systems and methods and, more particularly, but not by way of
limitation, to toll fee tracking systems and methods for automatic,
non-contact, high-speed toll fee tracking of vehicular tolls
associated with a toll tracking device used by vehicle
operators.
[0004] 2. History of Related Art
[0005] The crowding of highways within metropolitan areas has
resulted in the development of additional traffic arteries known as
toll roads. Toll roads have become increasingly popular, however,
they require the payment of a toll fee for use by vehicular
occupants. The collection of tolls by conventional means has had a
negative effect upon highway throughput and safety. Congestion and
long backups on toll plazas are becoming more common. Such
conditions involve a significant economic cost, through lost time
and reduced productivity. Moreover, serious accidents at toll
plazas, caused by operators or mechanical failures, have also
increased in frequency.
[0006] Certain toll authorities have attempted to respond to these
problems by providing coin-operated toll collection devices, or by
instituting a toll-plate system in which toll-takers visually
inspect each incoming vehicle for an appropriate toll plate or
sticker. Coin operated toll collection systems, however, do little
to increase throughput, and are susceptible to fraud through the
use of counterfeit coins. Toll-plate systems suffer the same
deficiencies, requiring each vehicle to slow sharply while entering
the visual inspection area. In later years, a development ensued
that revolutionized toll road travel. This was the development of
the toll fee tracking device.
[0007] One example of a toll fee tracking device is set forth and
shown in U.S. Pat. No. 4,546,241 issued Oct. 8, 1985. This patent
relates to an electronic identification and recognition system that
includes a portable card having a circuit therein for generating
and transmitting an identifying signal. The identifying signal
includes predetermined frequency pulses. The card functions in
cooperation with a reader which radiates a radio frequency carrier
signal received by an antenna in the card. This signal is used both
to power the circuit of the card and to provide the basic frequency
signal which is modified to generate secondary frequency signals
which are transmitted back to the reader in a predetermined
sequence identifying the card.
[0008] Today, those individuals who frequently use toll roads are
now prone to the purchase of toll fee tracking device. The toll fee
tracking device allows the vehicular occupant to bypass the cash
only toll gate and, in many instances, the vehicle can maintain its
normal speed as it traverses the toll gate wherein the passage of
the toll fee tracking device is recorded. The popularity of the
toll fee tracking device has expanded to the point that the normal
user of the toll fee tracking device can be frustrated by the lines
at toll gates when the toll fee tracking device is not available.
Unavailability of a toll fee tracking device can be for numerous
reasons, not the least of which is the use of rental cars.
[0009] The rental car business is worldwide and continually
expanding. Toll fee tracking devices are not, however, as known to
the inventors hereof, available in rental cars. This is due, at
least in part, to the fact that the charges for the toll fee
tracking device are not typically generated in a manner allowing
billing of the toll fee tracking device event during the duration
of some car rentals. Typically toll fee tracking device invoices
are delivered on a monthly basis while the toll fee data is not
processed in a real-time. For business travelers, paying tolls in a
rental car usually involves waiting at a toll gate with a live
operator so that a receipt may be generated for later expense
report purposes. Monthly toll fee invoices to car rental agencies
reflecting use of a toll fee tracking device in a given vehicle
over a period of time would inherently create a plethora of
problems, not the least of which would be collection of toll fees
by a vehicle renter who has long since turned in his or her expense
report. Moreover, the current economic system for rental agencies
typically requires that the entire financial transaction be
completed at the time of turning in the rental car, unless some
damage has occurred relative to the use thereof. Therefore, there
is a need for a method and system facilitating use of, and
financial accountability for, a toll fee tracking device used by
vehicle operators such as, for example, rental car users.
SUMMARY OF THE INVENTION
[0010] A toll fee tracking system comprising a toll authority
adapted to collect data associated with at least one toll fee
tracking device and a toll rental entity adapted to communicate
with the toll authority and a third part entity.
[0011] A method for toll fee tracking, the method comprising
collecting, at a toll authority, data associated with at least one
toll fee tracking device. The method further includes storing the
data in at least one database of the toll authority and
communicating, via a toll rental entity, the data to a third party
entity.
[0012] A toll rental entity server for communicating data between a
toll authority and a third party entity, the server comprising a
first interface for communicating with the toll authority. The
server further includes at least one database and a second
interface for communicating with the third party entity. The
communication between said toll authority and the third party
entity occurs in real-time or near real-time.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] A more complete understanding of the present invention may
be obtained by reference to the following Detailed Description of
Illustrative Embodiments of the Invention, when taken in
conjunction with the accompanying Drawings, wherein:
[0014] FIG. 1 is a perspective view illustrating an exit of a toll
road in which an automatic toll collection system is installed;
[0015] FIG. 2 illustrates a control device installed on an
electronic toll collection lane;
[0016] FIG. 3 illustrates an electronic toll fee tracking device
installed in each vehicle;
[0017] FIG. 4 illustrates a schematic block diagram of the toll fee
tracking device;
[0018] FIG. 5A illustrates a block diagram of a toll fee system in
accordance with an embodiment of the present invention;
[0019] FIG. 5B illustrates a block diagram of a toll fee system in
accordance with an alternate embodiment of the present
invention;
[0020] FIG. 5C illustrates a block diagram of a wireless system
utilized in conjunction with the present invention;
[0021] FIG. 5D illustrates a block diagram of a wireless system
utilized in conjunction with an alternate embodiment of the present
invention;
[0022] FIG. 6A illustrates a detailed block diagram of a toll fee
system in accordance with an embodiment of the present
invention;
[0023] FIG. 6B illustrates a detailed block diagram of the toll fee
system in accordance with an alternate embodiment of the present
invention;
[0024] FIG. 7 illustrates a block diagram of a portion of the toll
fee system of the present invention;
[0025] FIG. 8 illustrates a status diagram of a toll fee tracking
device installed in each vehicle; and
[0026] FIG. 9 illustrates a process flow diagram in accordance with
the present invention.
DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS OF THE
INVENTION
[0027] Embodiment(s) of the invention will now be described more
fully with reference to the accompanying Drawings. The invention
may, however, be embodied in many different forms and should not be
construed as limited to the embodiment(s) set forth herein. The
invention should only be considered limited by the claims as they
now exist and the equivalents thereof.
[0028] FIG. 1 illustrates two Electronic Toll Collection (ETC)
lanes 102. In each of the ETC lanes 102, tolls are automatically
collected from each vehicle along the lanes 102 through radio
communication between a toll fee tracking device (e.g., a radio
frequency integrated device (RFID) transponder) installed in the
vehicle and a toll collection unit installed on each ETC lane 102.
The toll collection units are typically owned by a toll authority
and are situated on toll authority property. Those skilled in the
art will appreciate that the invention can be practiced in
connection with roadways having additional lanes, including
multi-lane divided highways, bridges, and tunnels. As one skilled
in the art will appreciate the invention can also be practiced in
connection with numerous other transport systems such as, for
example, railways and waterways.
[0029] On each ETC lane 102, a vehicle type identifying device 104,
a license plate monitor camera 106, an antenna 108, a vehicle
detector 110, and a display 112 are arranged. The vehicle type
identifying device 104 identifies the type of a vehicle passing
thereby. The license plate monitor camera 106 captures an image of
a license plate of the vehicle to read a license plate number out
of the image. The vehicle detector 110 may be, for example, a
photoelectric cell for optically sensing the presence of a vehicle
and generating a VEHICLE PRESENT signal.
[0030] The automatic toll collection system includes a control
device 200, as shown in FIG. 2, one for each ETC lane 102. The
control device 200 has a lane control computer 202 which controls
operations of the vehicle type identifying device 104, the license
plate monitor camera 106, and a toll collecting unit 204. The
control device 200 receives information signals from the vehicle
detector 110 indicating the passing of the vehicle. The lane
control computer communicates with a toll booth computer 206. The
toll booth computer 206 communicates with a network 208 for
transmission of information.
[0031] FIG. 3 illustrates a toll fee tracking device 300 installed
in each vehicle passing through either of the ETC lanes 102. As an
exemplary embodiment, a radio frequency integrated device (RFID)
transponder is utilized as the toll fee tracking device 300. Each
vehicle is identified using the RFID transponder 300. The RFID
transponder 300 includes a microchip attached to an antenna 302.
The antenna 302 may be, for example, incorporated into the
transponder 300 itself or a receptacle may be provided to attach to
a conventional window mounted antenna, similar to those employed in
connection with cellular telephone devices. The microchip contains
information that identifies a particular toll rental entity account
with a toll authority account. Each RFID transponder 300 is
identified by a unique identification number (e.g., transponder
Id). The RFID transponder 300 further includes circuitry for
establishing a radio communication between the RFID transponder 300
and the toll collecting unit through the antenna 302.
[0032] FIG. 4 illustrates a schematic block diagram 400 of the toll
fee tracking device 300 (i.e., the transponder) as illustrated in
FIG. 3. The transponder 300 includes an antenna 302, a transceiver
402, and a control circuit 405. The transceiver 402 establishes
radio communications between the transponder 300 and the toll
collection unit 204 (FIG. 2) through the antenna 302. The control
circuit 405 further includes a processor 405a, a mask ROM 405b, and
an EEPROM 405c. The processor 405a performs the various programs
stored in the mask ROM 405b. The EEPROM 405c stores therein
transponder identification number and status data. The processor
405a may be, for example, an 8086 microprocessor or an 8051
microcontroller, or any other processor capable of executing the
functions described above.
[0033] The transponder 300 may also includes a battery 407 and a
power supply circuit 408. The power supply circuit 408 supplies
power to the components of the transponder 300. For exemplary
purposes, a transponder 300 powered by a battery 407 is shown. The
RFID transponder 300 may be, for example, an active transponder or
a passive transponder. Passive transponders do not require a
battery to derive power for operation. Passive transponders derive
power to operate from the electric field generated by the passive
transponder. In addition, passive transponders are long lasting and
support multiple frequency ranges. However, active transponders
have a battery for deriving power for operation and support only
one frequency. According to exemplary embodiments of the present
invention, the RFID transponder 300 may be placed on interior
region of the vehicle, for example, on a windshield of the vehicle.
According to other exemplary embodiments of the present invention,
the RFID transponder 300 may be placed on an exterior region of the
vehicle, for example, on the roof or the license plate of the
vehicle.
[0034] FIG. 5A illustrates a block diagram 500A of a toll fee
system in accordance with an embodiment of the present invention.
The system 500A includes a toll authority 502, a toll rental entity
504, and a third party entity 506. The toll rental entity 504
interfaces with both a toll authority 502 and a third party entity
506. When a vehicle having a valid RFID transponder 300 passes
through a toll gate of the toll authority 502, the transponder 300
is read by the toll gate of the toll authority 502. The toll
authority 502 collects data such as an identifier and toll fee
assessed and allows access to at least a subset of the toll data.
The toll rental entity 504 or the third party entity 506 that
utilizes the toll rental entity 504 within the third party entity's
506 existing system may access at least a subset of the data
collected by the toll authority 502. The data which includes
information related to the fee charged to a particular transponder
300 may be passed from the toll rental entity 502 to the third
party entity 504 in real-time or near real-time such that the
vehicle operators are charged for any toll related charges. The
vehicle operator may be, for example, a rental vehicle operator, an
operator of a leased vehicle or the like. In short, the toll rental
entity 504 acts as a communication channel between the toll
authority 502 and the third party entity 506 for forwarding data
from the toll authority 502 to the third party entity 506 in a
real-time or near real-time fashion.
[0035] FIG. 5B illustrates an alternate embodiment of the toll fee
system 500B in accordance with an alternate embodiment of the
present invention. The toll rental entity 504 may be integrated
into an existing operating system of the third party entity 506.
The third party entity 506 may request data directly from the toll
authority 502. The third party entity 506 then utilizes the toll
rental entity 504 to store data and reconcile accounts in a similar
manner as that noted above with respect to FIG. 5A with the
exception of transmitting and requesting data between the
stand-alone toll rental entity 504 and the third party entity
606.
[0036] FIG. 5C illustrates a block diagram of a wireless system
utilized in conjunction with the present invention. Although all
portions of the system of FIGS. 5C and 5D (described in detail
below) are shown communicating via wireless links, it will
understood by one skilled in the art that one or more portions of
the system may be communicated via a wired network or other
technology. In a similar manner to that of FIGS. 5A and 5B,
communications between the toll authority 502, toll rental entity
504, and the third party entity 506 may be communicated via a
request and response scenario, or via a push/pull scenario. In both
scenarios, the data may be requested or sent in real-time or at
some predefined regular intervals.
[0037] Referring to FIG. 5C, the toll rental entity 504 may request
and pull data from the toll authority 502 via a wireless link. In
an alternate embodiment, the toll authority 502 may push/transmit
data from the toll authority 502 to the toll rental entity 504. The
toll rental entity 504 may then transmit the data to the third
party entity 506. In an alternate embodiment, the third party
entity 506 may request specific data from the toll rental entity
504, which may thereafter transmit the requested data to the third
party entity 506.
[0038] FIG. 5D illustrates a block diagram of a wireless system
utilized in conjunction with an alternate embodiment of the present
invention. As noted above with respect to FIG. 5C, toll data may be
requested and pulled from the toll authority 502 by the toll rental
entity 504. Alternatively, the toll authority 502 may push the toll
data to the toll rental entity 504. The toll rental entity 504 may
then transmit the data to the third party entity 506 to perform
other operations such as, for example, billing, account
reconciliation etc. Some or all the communications between the toll
authority 502, and the toll rental entity 504 and/or third party
entity 506 may be via, for example, a wireless telecommunications
network, wired networks, or other technology.
[0039] FIG. 6A illustrates a detailed block diagram of a toll fee
system 600A in accordance with an embodiment of the present
invention. The toll fee system 600A provides information and
records for accurate accounting of traffic activity and toll
transactions for all transponders 300 having valid toll rental
entity accounts. The toll fee system 600A performs various tasks
such as, for example, monitoring toll collection, transferring toll
collection data to various components of the system, and monitoring
traffic activity. The toll fee system 600A expedites the toll fee
process and completes the entire financial transaction at the time
the vehicle operator such as, for example, a rental vehicle user
returns the rental vehicle.
[0040] The toll fee system 600A maintains records of all toll
transactions for all transponders 300 having valid toll rental
entity accounts. These records are maintained and formatted for
real-time or near real-time transmission to various elements within
the toll fee system 600A. The toll fee system 600A includes a toll
authority 502, a toll rental entity 504, and a third party entity
506. The toll authority 502 includes a plurality of toll gates 508
which are equipped with transponder reader units. The toll
authority 502 further includes a processor 512 and a communications
link 513 for bi-directional data communications with the toll
rental entity 504. The processor 512 may be, for example, a
conventional microcomputer or minicomputer, depending upon the size
and the data-handling requirements of the toll fee system 600A. The
processor 512 is interconnected to the transponder reader units 508
and a database 514. The processor 512 gathers toll fee tracking
data from the transponder reader units 508 and stores the data into
the database 514. The data is structured and transferred to the
toll rental entity 504 using, for example, SOAP/XML. The database
can be, for example, an Oracle.TM. database, a MS Access.TM.
database, MS SQL, IBM DB2, and the like. The toll fee tracking data
may include, for example, vehicle-class-identifiers, transaction
time, transaction date, lane traffic activity information,
transponder identification number, toll gate identification,
vehicle travel direction and the amount of toll charged to the
user. For simplicity, only one processor 512 and one database 514
is shown, however, a plurality of processors and databases may be
employed by the toll authority 502.
[0041] The toll fee system 600A further includes a toll rental
entity 504. The toll rental entity 504 acts as a communication
channel between the toll authority 502 and the third party entity
506 for forwarding data from the toll authority 502 to the third
party entity 506 in a real-time or near real-time fashion. The toll
rental entity 504 may be, for example, a server capable of
performing the various tasks which will be described later with
respect to FIG. 7. The toll rental entity 504 includes a toll
authority interface 516, a toll rental entity database 518, and a
third party entity interface 520. The components 516, 518, and 520
as illustrated are for exemplary purposes. A detailed illustration
of the various components and their functions will be shown and
described later with respect to FIG. 7. The toll authority
interface 516 may be, for example, a processor similar to the one
disclosed earlier. The toll authority interface 516 is
interconnected to the toll rental entity database 518 which in turn
is connected to the third party entity interface 520. The toll
authority interface 516 is adapted to send a request message to the
processor 512 on the communications link 513. The request message
is transmitted from the toll authority interface. 516 to the
processor 512 to obtain toll fee tracking data. For example, the
request message may be transmitted at some predefined regular
interval (e.g., one every two minutes) or continuously in real-time
or near real-time. The processor 512 receives the request from the
toll authority interface 516 and grants permission for the data to
be pulled by the toll authority interface 516 residing within the
toll rental entity 504. The data pulled by the toll rental entity
504 is stored in a data storage device such as, for example, a
database 518 of the toll rental entity 504. The database can be,
for example, an Oracle.TM. database, a MS Access.TM. database, MS
SQL, IBM DB2, and the like. The toll authority interface 516 is
also adapted to receive data from the toll authority 502 and
convert the data into a format which is compatible for storage into
the toll rental entity database 518.
[0042] The toll fee system 600A further includes a third party
entity 506. The third party entity 506 includes a rental
point-of-sale (POS) system 522, a customer invoice unit 524, and a
third party entity processor 526. The third party entity interface
520 accesses the data from the database 518 and transmits the data
to the third party entity POS system 522 within the third party
entity 506. The data is then provided to the customer through a
customer invoice unit 524 where the customer is charged the fee
corresponding to the toll usage along with any relevant service
charges and/or taxes. The customer invoice unit 524 may be, for
example, a computer having printing capabilities. The customer
invoice may be, for example, a printed invoice, an invoice which
may be electronically transmitted to the customer, or the like. The
rental authority processor 526 may also send a request message to
the third party entity interface 520 requesting specific data
corresponding to a particular customer or data relating to a
particular time period. This data is transmitted to the rental POS
522 from the third party entity interface 520.
[0043] FIG. 6B illustrates a detailed block diagram of a toll fee
system 600B in accordance with an alternate embodiment of the
present invention. In this embodiment, the toll authority interface
516 resides within the toll authority 502. The toll authority
interface 516 interfaces with a toll rental entity listener 517
within the toll rental entity 504. The toll rental entity listener
517 is adapted to receive data from the toll authority interface
516 and convert the data into a format which is compatible for
storage into the toll rental entity database 518. In this
embodiment, there is no need to send a request message from the
toll rental entity 504 to obtain the data. The toll fee tracking
data is periodically or continuously pushed from the toll authority
interface 516 to the toll rental entity listener 517.
[0044] FIG. 7 illustrates a detailed block diagram of the toll
rental entity 504 of the toll fee system of FIGS. 6A and 6B. The
toll rental entity 504 may be, for example, a server for performing
data analysis and data dissemination. The toll rental entity server
504 may include a plurality of processors such as, for example, a
toll rental entity processor 702 and a batch processor 706. The
processors 702 and 706 may be, for example, software systems or
software components. In an embodiment of the present invention, the
toll rental entity processor 702 is adapted to receive toll data
from the toll authority 502 at some predefined regular intervals
(e.g., every two minutes). In an embodiment, data transmission
between the toll authority 502 and the toll rental entity server
504 may take place using, for example, XML, or any language
specific formats. In another embodiment, data transmission between
the toll authority 502 and the toll rental entity server 504 may
take place using connection oriented or connection less
communication protocols such as, for example, HTTP, TCP/IP, FTP
etc.
[0045] The toll data is received by the toll rental entity
processor 702. The toll rental entity processor 702 is adapted to
analyze and disseminate the toll data and forward a request to at
least one of the plurality of function modules 708, 710, 712, and
714. The request may be, for example, analyzing the toll data
associated with a particular transponder and calculating an amount
to be charged to a customer associated with the particular
transponder. This function may be performed by, for example,
function module 1708. The request may also include, for example,
maintaining and updating toll rental entity accounts. This function
may be performed by, for example, function module 710. The request
may also include, for example, bill handling for updating charges
associated with a particular transponder 300. This function may be
performed by, for example, function module 712. Other functions may
also be performed by the function modules 798, 710, 712, and 714
which may include, for example, payment handling, error handling,
and the like. The plurality of function modules 708, 710, 712, and
714 are associated with a plurality of databases 716, 718, 720, and
722, respectively. The databases 716, 718, 720, and 722 are adapted
to store data calculated by the function modules 708, 710, 712, and
714. The databases are connected to a third party entity interface
520 which is adapted to transmit information to the third party
entity 506. The databases 716, 718, 720 and 722 may be, for
example, Oracle.TM. databases, MS Access.TM. databases, MS SQL, IBM
DB2, and the like. The transmission of data from the toll authority
502, the toll rental entity server 504, and the third part
authority 506 takes place in a real-time or near real-time fashion.
In an alternate embodiment of the present invention, the batch
processor 706 is adapted to receive the toll data from the toll
authority using connection less communications protocols such as,
for example FTP. The toll data is received by the batch processor
706 at some predefined regular intervals (e.g., every hour). The
toll data is transferred from the batch processor to the toll
rental entity processor 702 for analysis and dissemination as
disclosed earlier.
[0046] FIG. 8 illustrates a status diagram of the RFID transponder
300 as illustrated in FIG. 3. The transponder 300 is in a ready
state 802 when a vehicle is ready to be rented to a customer. The
ready state 802 indicates that the transponder 300 has already been
assigned to a particular vehicle being operated by, for example, a
rental vehicle user.
[0047] When the customer rents the rental vehicle from the third
party entity 506, the customer has the option of accepting the
automatic toll payment service provided by the toll rental entity
504. If the customer denies the automatic toll payment service, the
transponder 300 goes into an inactive state 804. The transponder
300 remains in the inactive state 804 until the customer returns
the car to the third party entity 506 or the customer uses a toll
gate of the toll authority 502. Upon using the toll gate, the
transponder 300 goes into an active state 808. Once the customer
returns the car to the third party entity 506, the transponder 300
enters in a closed state 806 after which the status of the
transponder will be changed for another customer.
[0048] However, if the customer accepts the automatic toll payment
service, the transponder 300 goes into a ready state 802. When the
customer uses the toll service for the first time, the system
applies a minimum service charge and the status of the transponder
300 is changed to an active 808 state followed by the transponder
300 being changed to an in-use state 810.
[0049] In a situation when the transponder 300 is inactive and the
customer uses the automatic toll payment service, the system
applies a minimum service charge and updates the status of the
transponder to active state 808 and in-use state 810,
respectively.
[0050] When the customer returns the car to the third party entity
506, the third party entity 506 obtains transaction details of the
transponder 300 using the toll rental entity listener 517 within
the toll rental entity 504. Once the account is billed, the status
of the transponder is changed to closed state 806. The closed state
806 indicates that the rental vehicle has been returned to the
third party entity and the vehicle operator has been charged for
the services utilized. Now the transponder 300 is ready to be
reassigned. If for some reason the transponder 300 is
malfunctioning, the transponder 300 returns to the closed state 806
followed by the transponder 300 going into an expired state
812.
[0051] FIG. 9 illustrates in detail a process flow 900 in
accordance with the present invention. Although steps of the flow
900 are depicted in a particular sequence, it will be appreciated
by persons of ordinary skill in the art that certain steps of the
process need not necessarily follow a strict sequence but can be
rearranged and/or performed simultaneously. The flow starts at step
902. At step 904, transponder data is read by the transponder
readers 508 within the toll authority 502. The data may be, for
example, vehicle-class-identifiers, transaction time, transaction
date, lane traffic activity information, transponder identification
number, toll gate identification, vehicle travel direction and the
amount of toll usage to the user. At step 906, it is determined if
the transponder identification data corresponds to the transponder
identification data associated with the toll rental entity
transponder. If it is determined that the transponder
identification data does not corresponds to the transponder
identification data associated with a toll rental entity
transponder, the flow proceeds to step 910. At step 910, the data
is processed by the toll authority 502 and the flow returns to step
902.
[0052] However, if it is determined at step 906 that the
transponder identification data corresponds to the transponder
identification data associated with the toll rental entity
transponder, the process is continued at step 908. At step 908, the
data is collected at a database 514 within the toll authority
502.
[0053] At step 912, it is determined if a request to share the data
has been received by the processor 512 of the toll authority 502.
The request may be sent by the toll authority interface 516
residing within the toll rental entity 504. The request may be, for
example, a request message for allowing data to be pulled by the
toll rental entity 504. For example, the request message may be
transmitted at some predefined regular interval (e.g., one every
two minutes) or continuously in real-time or near real-time. If it
is determined that a request has been received by the processor 512
within the toll authority 502, the process is continued at step
916. At step 916, the data is pulled by the toll rental entity 504
and the process is continued at step 918. However, if it is
determined at step 912 that a request has not been received, the
process continues at step 914. At step 914, the toll authority
pushes the data to the toll rental entity and the process is
continued at step 918. At step 918, the data from steps 914 and 916
is stored in a database 518 within the toll rental entity 520.
[0054] At step 920, it is determined if a particular transponder
associated with a user 300 is being used for the first time. If it
is determined that the transponder is being used for the first
time, the flow continues at step 922. At step 922, the user is
charged a service fee and the process continues at step 923. At
step 932, the transponder 300 is activated and the process
continues at step 924. However, if it is determined at step 920
that the particular transponder 300 has been used before, the
process continues at step 924. At step 924, the toll data usage is
updated by processors within the toll rental entity 504. The
process is continued at step 926 where the data is pushed from the
toll rental entity 504 to the third party entity 506. At step 927,
the transponder 300 is closed for further transaction until it is
reassigned. At step 928, the user is provided with an invoice with
charges related to the toll usage along with the charges associated
with the use of the third party entity services such as, for
example, charges related to vehicle rental. The process ends at
step 930. The data transmission between the toll authority 502, the
toll rental entity 504, and the third party entity 506 occurs at
some predefined regular interval (e.g., one every two minutes) or
continuously in real-time or near real-time.
[0055] It should be emphasized that the terms "comprise",
"comprises", and "comprising", when used herein, are taken to
specify the presence of stated features, integers, steps, or
components, but do not preclude the presence or addition of one or
more other features, integers, steps, components or groups
thereof.
[0056] The previous Detailed Description is of embodiment(s) of the
invention. The scope of the invention should not necessarily be
limited by this Description. The scope of the invention is instead
defined by the following claims and the equivalents thereof.
* * * * *