 |
Description  |
|
|
BACKGROUND OF THE INVENTION
1. Field of the Invention
The invention relates generally to smart cards, and more particularly to
smart card techniques for use in conjunction with the administration of
motor vehicle records.
2. Description of the Prior Art
Various prior art systems are directed towards improving one or more
aspects of motor vehicle record administration. One such system, proposed
by the Diebold Co., utilizes smart cards and a network of customer
machines situated at fixed locations. The system is used by motorists who
need to update their motor vehicle registrations, but do not wish to wait
in long lines at the state Department of Motor Vehicles office. Each smart
card stores a record setting forth motor vehicle registration parameters,
and these records are updated by inserting the smart card into a large,
stationary customer machine.
The use of stationary customer machines for the purpose of administering
motor vehicle records is impractical in that a prohibitively large number
of machines must be utilized to provide a reasonable level of service
throughout a state or metropolitan area. If an insufficient number of
machines are utilized, many vehicle owners will be situated closer to a
conventional motor vehicle registration station than to a machine, and
these owners are not very likely to drive the extra distance merely for
the privilege of dealing with the machine. Moreover, such machines are
expensive to manufacture and to maintain. An additional expense will have
to be borne by the state and/or the taxpayers, because the state motor
vehicle authority will have to purchase or lease the space on which the
machines are to be located.
A significant shortcoming of prior art systems is that only one category of
motor vehicle record is administered. For example, the Diebold system only
provides for the administration of records dealing with motor vehicle
ownership registration. It would be desirable to have a record
administration system which is equipped to handle all types of record
arising in connection with the ownership and operation of motor vehicles,
such as drivers license registration, automobile insurance renewal,
environmental inspection compliance, motor vehicle code violations,
parking garage fee payments, and the payment of highway tolls. However,
existing systems lack the data structures, process steps, and/or hardware
to implement a fully integrated motor vehicle record administration
system.
Another prior art system related to motor vehicle records is disclosed in
U.S. Pat. No. 4,970,655 issued to Winn et al. on Nov. 13, 1990 for an
Automatic Fee Collecting and Receipt Dispensing System. As with the
Diebold system, the Winn system utilizes a network of customer machines.
However, Winn does not utilize smart cards at all. Rather, the Winn
customer machine functions in a manner analogous to that of a conventional
vending machine, by dispensing customer-selected forms in exchange for
monetary consideration. The customer provides monetary consideration for
the forms by swiping a conventional credit or ATM card through a reader on
the machine. The forms that are processed by Winn concern motor vehicle
registration, and do not encompass other functions connected with the
ownership and operation of motor vehicles. Accordingly, motorists can
register their automobile ownership with the state, but the Winn system is
not equipped to deal with automobile insurance, toll payments, or traffic
violations.
For purposes of customer and administrative convenience, it would be
desirable to have a system which fully integrates a plurality of records
associated with automobile use and ownership. As stated above, present-day
motor vehicle record administration systems are generally
single-application systems equipped to process only one category of motor
vehicle records. However, in view of recent technological and legal
developments, such systems are in need of dramatic improvement. Along with
the increased use of electronic automation, the proliferation of insurance
and environmental regulations has dramatically increased the
record-keeping burden imposed on motorists. A present-day automobile
driver may be required to carry a drivers license card, one or more
vehicle registration cards, a proof-of-insurance card, a motor club card,
a toll-way authority pass card, a parking garage pass card, and an
environmental inspection certificate. The requirement to carry around all
of these cards is an inconvenience. These cards add weight and bulk to
wallets and purses. Time is wasted fumbling around trying to find a
desired card from among a myriad of other cards. Additionally, due to the
sheer number of cards, the cards are rendered increasingly vulnerable to
loss, misplacement, or theft; i.e., a card falling to the ground unnoticed
while its owner is frantically searching for another card; a card sliding
out of an already-overcrowded wallet; etc. Due to the relatively large
number of cards, the loss or misplacement of one of the cards may go
unnoticed until recovery of the card is difficult or impossible. What is
needed is a system for integrating various types of motor vehicle records
onto a single motorist identification card.
SUMMARY OF THE INVENTION
Smart card techniques are disclosed for integrating and administering
records related to the ownership and/or operation of motor vehicles. A
smart identification card stores and administers a plurality of motor
vehicle records corresponding to a single motorist. These motor vehicle
records include items selected from the group of motor vehicle
registration information, drivers license information, vehicle code
violations, automobile insurance information, parking garage entry times,
parking garage account balance, highway toll account balance, motor club
information, and environmental inspection information. Each smart
identification card is equipped to interact with any of a plurality of
computer databases through the utilization of a conventional
communications link in conjunction with a smart card scanner. Each of the
computer databases administers motor vehicle records.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 sets forth the data structures utilized by a preferred embodiment of
the smart identification card;
FIG. 2 is a hardware block diagram showing an illustrative operational
environment for the smart identification card of FIG. 1;
FIGS. 3 and 3A are a flowchart setting forth a procedure for use in
conjunction with the hardware shown in FIG. 2;
FIG. 4 is a hardware block diagram showing a smart identification card
system for use in connection with law enforcement operations;
FIG. 5 and 5a are flowcharts setting forth a procedure for use in
conjunction with the hardware shown in FIG. 4;
FIG. 6 is a hardware block diagram showing a first embodiment of a smart
identification card system for collecting highway tolls;
FIG. 7 is a flowchart setting forth a procedure for use in conjunction with
the hardware of FIG. 6;
FIG. 8 is a hardware block diagram showing a second embodiment of a smart
identification card system for collecting highway tolls;
FIG. 9 and 9a, 9b, 9c, 9d are flowcharts showing a procedure for use in
conjunction with the hardware FIG. 8;
FIG. 10 is a hardware block diagram illustrating a smart card
identification system for use at a parking facility;
FIG. 11 and 11a, 11b, 11c, 11d are flowcharts showing a procedure for using
in conjunction with the hardware of FIG. 10;
FIG. 12 is a hardware block diagram illustrating a smart card
identification system in the context of an automobile insurance provider;
and
FIG. 13 and 13a, 13b, 13c and 13d are flowcharts setting forth a procedure
for use in connection with the hardware of FIG. 12.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
FIG. 1 sets forth the data structures utilized by a preferred embodiment of
the smart identification card. The smart identification card of FIG. 1
provides a system which integrates a plurality of records related to the
ownership and/or operation of motor vehicles. Each smart identification
card is equipped to interact with any of a plurality of computer databases
through the utilization of a conventional communications link in
conjunction with a smart card scanner. Interactions between the smart
identification card and one or more computer databases provide for the
administration of the aforementioned records, as will be described in more
detail below with reference to FIG. 2.
Referring now to FIG. 1, a smart identification card stores and administers
motor vehicle records corresponding to a particular motorist. These motor
vehicle records include a plurality of item categories selected from the
group of motor vehicle registration information, drivers license
information, vehicle code violations, automobile insurance information,
parking garage entry times, parking garage account balance, highway toll
account balance, motor club information, and environmental inspection
information. For example, FIG. 1 includes a File Identifier
"A"--Cardholder Identity 131 field, which is used to store the drivers
license number 147 of the identification card holder. Similarly, File
Identifier "B"--Cardholder Identity 133 field is used to store the social
security number of the identification card holder.
Although the example of FIG. 1 uses two fields to store information related
to the identity of the identification card holder, this is shown for
illustrative purposes. Any convenient number of fields may be employed to
store information relating to the identity of the cardholder, so long as
at least one field contains sufficient information to uniquely identify a
particular cardholder from all other cardholders. The term "file
identifier" is employed because the drivers license number 147 stored in
the File Identifier "A"--Cardholder Identity 131 field may be used by a
centralized computer as an index for the purpose of locating a particular
record in a large database. Likewise, the File Identifier "B"--Cardholder
Identity 133 field may also be employed as an index to locate a particular
record in a centralized database external to the smart identification
card. In this manner, the memory reserves of the smart identification card
are economized, inasmuch as a relatively small file identifier stored in
the smart identification card may be used to refer to a relatively lengthy
record stored on a large mainframe computer.
The smart identification card of FIG. 1 contains a violation record file
identifier 135 which uniquely identifies a vehicle code violation file
stored in a centralized database maintained, for example, by a state
drivers license recording bureau. The vehicle code violation file
specified by the violation record file identifier 135 corresponds to the
motorist having the drivers license number 147 specified in File
Identifier "A"--Cardholder Identity 131 field, and the social security
number 149 specified in the File Identifier "B"--Cardholder Identity 133
field. One or more violation identifiers may optionally be associated with
the violation record file identifier 135. These violation identifiers
correspond to a particular motor vehicle code violation or a particular
category of motor vehicle code violation. For example, violation
identifier M 151 corresponds to a vehicle code section prohibiting speeds
in excess of 55 mph on state highways. Violation identifier N 153
corresponds to disobeying a traffic control device, i.e., by running
through a red light, and violation identifier) 155 corresponds to parking
in a handicapped zone.
Each violation identifier may optionally be associated with a date field
setting forth the date of the violation, and a status field setting forth
the legal status of the violation, i.e., awaiting trial, guilty verdict
rendered with judgment satisfied, guilty verdict rendered with judgment
not satisfied, and acquittal of all charges. The violation identifier may
be used as an index, whereby the violation identifier is associated with a
file in the state drivers license record bureau which contains more
detailed and specific information about a particular vehicle code
violation stored on the smart identification card. As will be described in
more detail below with reference to FIG. 4, the smart identification card
includes a data input device which is equipped to accept violation record
identifiers 135 and/or violation identifiers 151, 153, 155 from mobile
computers situated within police cars.
The smart identification card of FIG. 1 contains a toll account file
identifier 137 which is associated with a toll account balance 157. The
toll account identifier 137 is employed to uniquely identify a particular
highway toll collection authority. These toll collection authorities are
responsible for collecting tolls on one or more specific toll roads,
bridges, and/or tunnels, such as the New Jersey Turnpike, the Northwest
Tollway, the Coronado Bay Bridge, or the Lincoln Tunnel. Each toll account
identifier is associated with a toll account balance 157 specifying the
amount of money and/or the number of tolls remaining in the cardholder's
account. As will be described hereinafter with reference to FIGS. 6 and 7,
the toll account identifiers and toll account balances may be downloaded
into the smart card from a centralized computing device under the control
of a highway toll collection authority. Although the smart identification
card of FIG. 1 shows one toll account file identifier, this is done for
illustrative purposes only, it being understood that any convenient number
of toll account file identifiers and corresponding account balances may be
stored in the smart identification card.
A parking garage file identifier 139 is used to uniquely identify a
specific parking garage or parking garage authority, such as the Lindbergh
Field Parking Authority or the parking garage at Eighth and Walnut. Each
parking garage file identifier 139 is associated with a parking garage
account balance 159 specifying the amount of money, the amount of time,
and/or the number of parkings remaining in the cardholder's account. Each
parking garage file identifier 139 may also be associated with an optional
time of entry field setting forth the time and/or date at which the
cardholder entered the parking facility. The parking garage file
identifier 139, parking garage account balance 159, and any optional time
of entry fields may be downloaded into the smart identification card by a
computing device under the control of the parking garage authority, as
will be described in greater detail below with reference to FIGS. 10 and
11. Although the smart identification card of FIG. 1 includes one parking
garage file identifier 139, it is to be understood that the smart
identification card may contain any convenient number of parking garage
file identifiers 139.
An automobile insurance file identifier 141 uniquely specifies an insurance
company and an insurance policy file corresponding to the smart card
holder and stored in a centralized computer database under the control of
the specified insurance company. Each insurance policy file specifies a
particular insurance policy, and may optionally include information
concerning the terms of the policy, information related to the nature and
status of insurance claims, personal information related to the
policyholder, and information pertaining to motor vehicle code violations.
The interactions between the smart identification card and the insurance
company centralized computer database will be discussed at length below,
with reference to FIGS. 12 and 13.
Returning now to FIG. 1, automobile insurance identifier 141 is associated
with an automobile identification field 161 setting forth Automobile X,
which may be a 1988 Thunderbird. Automobile insurance file identifier 143
is associated with an automobile identification field 169 setting forth
Automobile Y, which may be a 1992 Crown Victoria. Each automobile
insurance file identifier 141,143 is also associated with a policy
expiration date field 163, 171, respectively, an insurance expiration flag
165, 173, respectively, and an insurance company telephone number field
167, 175, respectively. The policy expiration date fields 163, 171 set
forth the expiration dates of the respective insurance policies referred
to in automobile insurance identifiers 141 and 143.
Insurance expiration flags 165, 173 contains a first logic value, i.e.,
logic "one", when the insurance policy referred to in the corresponding
automobile insurance identifier has not yet expired, and a second logic
value, i.e., logic "zero", when the insurance policy has expired. The
insurance company telephone number 167, 175 field contains a telephone
number which is linked to the insurance company centralized computer
database, and which is provided by the insurance company for the purpose
of data communications. This telephone number may be accessed, for
example, from a conventional cellular or landline telephonic device
coupled to a modem.
A Department of Motor Vehicles Automobile Registration File Identifier 145
uniquely identifies a vehicle ownership registration file stored in a
centralized computer database and administered by the state Department of
Motor Vehicles. Such a file contains information related to the ownership
of a specific motor vehicle, such as the owner's name, address, telephone
number, age, and drivers license number; vehicle make, model, color, VIN
(Vehicle Identification Number), and year; and other pertinent
information.
Associated with Department of Motor Vehicles Automobile Registration File
Identifier 145 is a VIN# 177 field which sets forth the VIN of automobile
X (the 1988 Thunderbird), a registration expiration date 179 field which
sets forth the motor vehicle registration expiration date, a registration
expiration flag 181 (the registration expiration flag 181 is in a first
logic state, i.e., logic "one" if registration has not expired, and is in
a second logic state, i.e., logic "zero" if registration has expired), an
inspection due date 183 field setting forth the deadline for the next
upcoming environmental/safety inspection of the vehicle, and an inspection
overdue flag 185 (the inspection overdue flag 185 is in a first logic
state if the inspection date has already passed and the vehicle has not
yet been inspected, and in a second logic state if the inspection date has
not already passed and/or if the vehicle has already been inspected).
Although the example of FIG. 1 shows two Department of Motor Vehicles
Automobile Registration Identifiers 145, 146, note that any number of
Department of Motor Vehicles Automobile Registration File Identifiers 145,
146 may be stored on the smart identification card. As a practical matter,
every vehicle owned by the smart identification card holder has a
corresponding Department of Motor Vehicles Automobile Registration File
Identifier 145, 146. If a smart identification card holder owns two motor
vehicles, the smart identification card will contain two Department of
Motor Vehicles Automobile Registration File Identifiers 145, 146. If the
card holder owns six motor vehicles, then the smart identification card
will contain six Department of Motor Vehicles Automobile Registration File
Identifiers. Note that each Department of Motor Vehicles Automobile
Registration File Identifier 146 includes a VIN# of Automobile 148 field,
a registration expiration date 150 field, a registration expiration flag
152, an inspection due date 154 field, and an inspection overdue flag 156.
The data structures of FIG. 1 are directed to alleviating a
currently-existing situation whereby motorists must carry separate drivers
license cards, vehicle registration cards, proof-of-insurance cards, motor
club cards, tollway authority pass cards, parking garage pass cards, and
environmental inspection certificates. The data structures of FIG. 1
confer an additional benefit to motorists in cases where cards must be
periodically renewed. The hardship of having to appear in person to wait
in long lines for card renewals is eliminated, due to the fact that the
FIG. 1 data structures have been developed for record administration via
conventional communication links. In this manner, motorists can save time
by updating their motor vehicle records at remote locations. Additionally,
the inconvenience of having to carry around a multiplicity of cards to
operate a motor vehicle is dramatically reduced, if not eliminated
altogether. Excess weight, bulk, and confusion is eliminated from wallets
and purses. The time that would otherwise be spent fumbling around trying
to find a desired card from among a myriad of other cards is now time
saved. Since it is much easier to keep track of one card as opposed to
several cards, an integrated identification card is less vulnerable to
loss, misplacement, or theft, as might occur when a card falls to the
ground unnoticed while its owner is frantically searching for another
card, or when a card gradually slips out of a bulging, overcrowded wallet.
With an integrated identification card, it is very likely that the loss or
misplacement of the card would not unnoticed for very long.
FIG. 2 is a hardware block diagram showing an illustrative operational
environment for the smart identification card of FIG. 1. A smart
identification card 101 is adapted for interfacing with a smart card
scanner 105. Smart card scanner 105 includes a first communications
interface which is equipped to communicate with the smart identification
card 101. Such a first communications interface includes a smart card
holder which is positioned in proximity to the smart identification card
when data communications are desired. Accordingly, the smart card scanner
105 may hold the smart identification card in a substantially stationary
position while data communications are taking place, as contrasted with
conventional sweeper-type devices for credit cards, which are read-only
devices and do not provide for bi-directional data communications. The
design and construction of a suitable smart card scanner 105 is a matter
well known to those skilled in the art.
Smart card scanner 105 includes a second communications interface for
communicating with a computing device such as a computer terminal 107
and/or a microprocessor-based device. Computer terminal 107 may be a
conventional personal computer. The computer terminal 107 is coupled to a
user interface 109, which may include a conventional keyboard and a
conventional video display device. Computer terminal 107 is also coupled
to a conventional modem 111 adapted to communicate data over one or more
conventional landline telephone communications links 113, 121.
The computer terminal 107 includes a conventional memory device
(random-access memory --RAM, read-only memory --ROM, and/or a data storage
drive), into which is loaded a communications link table. The memory is
organized to include a file update buffer for storing one or more files
until such time as the file(s) is (are) transmitted from the computer
terminal over a communications link. The communications link table
contains a list of file identifiers. Each file identifier is associated
with a communications link specification setting forth a category of
communications link, and an access address for the communications link.
Illustrative categories of communication links include direct, dedicated,
real-time, hardwired links; conventional landline telephonic links;
conventional cellular telephonic links; point-to-point microwave links;
and the like. The access address sets forth information which is
sufficient to uniquely specify a given communications link. For example,
in the case of a conventional landline or cellular telephonic link, the
access address would include the telephone number of the link. In the case
of a direct, dedicated, real-time, hardwired link, the access address
would include a network address and/or the address of a communications
port which couples the hardwired link to the computer terminal.
Conventional landline telephone communications links 113, 121 are each
coupled to a corresponding centralized database computer such as first
centralized database computer 117 and second centralized database computer
125, respectively, via respective modems 115, 123. First centralized
database computer 117 administers database 119, and second centralized
database computer 125 administers database 127.
Taken together, smart card scanner 105, computer terminal 107, user
interface 109, and modem 111 may be conceptualized as a remotely-situated
user terminal. The system of FIG. 2 includes a second remotely-situated
user terminal adapted to communicate with smart identification card 102.
This second remotely-situated user terminal includes a conventional smart
card scanner 104, a conventional computer terminal 106, a conventional
user interface 108 for the computer terminal 106, a conventional modem
110, and a conventional cellular transceiver 122 adapted for
communications over a cellular communications link 129. The cellular
communications link 129 may be coupled via a cellular carrier to a
landline carrier which directs communications over a conventional landline
telephone line to modem 123. Alternatively, the cellular communications
link 129 may communicate with a cellular transceiver 124 coupled to modem
115.
The system of FIG. 2 may be advantageously utilized in the context of a
state motor vehicle inspection system. These systems typically provide
several vehicle inspection stations within a given metropolitan area. Such
inspections are often time-consuming because vehicle and personal
information must be manually gathered from the vehicle owner, usually by
means of a paper form. The vehicle must be inspected, and the results of
the inspection forwarded to a centralized state database along with the
information gathered from the vehicle owner.
In the example of FIG. 2, smart card scanner 105, computer terminal 107,
user interface 109, and modem 111 are situated at a first motor vehicle
inspection station in the Northern suburbs of a metropolitan area. Smart
card scanner 104, computer terminal 106, user interface 108, modem 110,
and cellular transceiver 122 are situated at a second motor vehicle
inspection station in the Western suburbs of a metropolitan area. Cellular
transceiver 124, modem 115, first centralized database computer 117, and
database 119 are situated at the state capital, hundreds of miles away
from the aforementioned metropolitan area. Modem 123, second centralized
database computer 125, and database 127 are located at the headquarters of
the Environmental Protection Agency in Washington, D.C.
FIGS. 3 and 3A are a flowchart setting forth a procedure for use in
conjunction with the hardware shown in FIG. 2. Program control begins at
block 201 where the computer terminal (FIG. 1, 107) prompts the user to
enter a password into the user interface (FIG. 1, 109). At block 203, a
test is performed to ascertain whether or not the smart card scanner (FIG.
1, 105) can read the smart identification card. If not, the program
branches to block 205, where the user interface prompts the user that the
smart identification card is unreadable, and the program then terminates.
The affirmative branch from block 203 leads to block 207, where the smart
card scanner scans the smart identification card and uploads one or more
file identifiers from the card. These file identifiers may include, for
example, the social security number and/or the drivers license number
stored on the smart identification card, as was previously described in
connection with FIG. 1. The smart card scanner downloads the file
identifiers to the computer terminal in block 209. At block 211, the
computer terminal searches a communications link table for the file
identifier which was downloaded in block 209. The computer terminal
retrieves the communications link specification associated with this file
identifier (block 213). At block 215, a test is performed to ascertain
whether or not the communications link specification sets forth a direct,
real-time communications link. If so, the program jumps ahead to block
235, where a series of operations is implemented as will be described in
greater detail below.
The negative branch from block 215 leads to block 217, where the computer
terminal places a call via the modem to a centralized database computer
over a telephonic (cellular and/or landline) communications link. Next,
the computer terminal checks to see whether or not there is an updated
file in the computer terminal file update buffer (block 219). A file will
be in the file update buffer if the routine of FIG. 3 has been previously
executed and, during such previous execution, an edited file was placed in
the file update buffer at block 233. If there is an updated file in the
file update buffer, the program progresses to block 221, and if there is
not an updated file in the file update buffer, the program skips ahead to
block 227.
At block 221, the file or files in the file update buffer are uploaded to
the centralized database computer via modems over the communications link.
The centralized database computer updates the database with the file(s)
which were uploaded from the file update buffer (block 223 ). At block
225, the file update buffer is cleared.
Block 227 is executed as program control transfers from block 225 or,
alternatively, if the negative branch of block 219 is followed. At block
227, the computer terminal downloads file identifiers to the centralized
database computer. The centralized database computer uploads, from the
database, the files corresponding to the file identifiers. These files are
uploaded to the computer terminal (block 229). These files may now be
displayed and/or edited on the computer terminal user interface. After
file editing, the edited files are stored in the file update buffer (block
233), and the program loops back to block 201.
The affirmative branch from block 215 leads to block 235 (FIG. 3A). At
block 235, the computer terminal establishes a direct, real-time
communications link with the centralized database computer. This
communications link may be a conventional hardwired data line such as, for
example, a T1 line. The computer terminal downloads the file identifiers
to the centralized database computer (block 237). The centralized database
computer uploads files corresponding to the file identifiers. These files
are uploaded to the computer terminal (block 239). The files may be
displayed and/or edited on the computer terminal user interface (block
241). The edited files are downloaded from the computer terminal to the
centralized database computer (block 243). The program then loops back to
block 201.
FIG. 4 is a hardware block diagram showing a smart identification card
system for use in connection with law enforcement operations. A law
enforcement vehicle, such as police car 427, is equipped with a mobile
computer terminal 409, to which is coupled a smart card scanner 405 and a
user interface 409. The smart card scanner 405, user interface 409, and
mobile computer terminal 407 are similar to smart card scanner 105 (FIG.
1), user interface 109, and computer terminal 107, respectively, with an
additional requirement that smart card scanner 405, user interface 409,
and mobile computer terminal 407 should be adapted to operate from a
conventional vehicular power supply of 13.8 volts (nominal). The mobile
computer terminal 407 is coupled to a modem 410 which interfaces with an
RF transceiver 411. Mobile computer terminal 407 may comprise, for
example, a laptop computer adapted for mounting in a law enforcement
vehicle. Mobile computer terminal 407 includes memory, which is any
desired combination of RAM, ROM, and/or data storage drives. Memory is
organized to include a file update buffer equipped to store one or more
flies for the purpose of editing and/or reading the file(s).
User interface 409 may comprise any desired combination of a video display,
an alphanumeric display, a voice synthesis circuit, a keyboard, a printer,
or the like. Smart card scanner 405 is adapted to perform read/write
operations on a smart card such as smart identification card 406. Smart
identification card 406 includes a smart card microprocessor 408.
RF transceiver 411 may be a conventional police radio transceiver which
operates on one or more federally-assigned frequencies in the public
service bands. Alternatively, RF transceiver 411 may be a conventional
cellular radio transceiver. RF transceiver 411 is coupled to a vehicular
antenna 414 of a conventional design which operates over the frequency
range or ranges covered by RF transceiver 411.
In the case where RF transceiver 411 is a conventional police radio
transceiver, antenna 414 communicates with base station antenna 417 over a
conventional electromagnetic communications link 415. The base station
antenna 417 may actually consist of one or more antennas, physically
located at one or more locations, which are used by the police department
to communicate with vehicles out in the field. The base station antenna is
coupled to RF transceiver 419, which is a conventional base station
transceiver equipped to operate on one or more federally-assigned public
service channels for communication with RF transceiver 411. RF transceiver
419 includes an integral data modulator/demodulator which demodulates
received data signals and converts these data signals into a form suitable
for transmission over data link 420. The data modulator/demodulator also
modulates signals received over data link 420 into a form suitable for
transmission over antenna 417.
Data link 420 may comprise a dedicated, hardwired communications link, a
conventional telephonic communications link, a microwave point-to-point
link, a combination of the aforementioned links, or the like. This link
connects RF transceiver 419 to a conventional modem 421, which modem may
be situated at a remote location relative to RF transceiver 419. The modem
421 is connected to a centralized database computer 423 which administers
database 425.
If RF transceiver 411 is a cellular transceiver, antenna 414 communicates
with cell site antenna 437 over a conventional cellular radio
communications path. Cell site antenna 437 is coupled to a conventional
cell site transceiver 439, which is equipped to provide a communications
path between RF transceiver 411 and a landline telephone system interface
441. The landline telephone system interface 441 provides a link between
cell site transceiver 439 and a conventional landline telephone system
central switching office 443. The central switching office 443 is adapted
to communicate over conventional telephonic links. A standard modem 445 is
coupled via a conventional telephonic link to the landline telephone
system central switching office 443. The modem 445 is coupled to a
centralized database computer 447 having a database 449. Cellsite
transceiver 439 is coupled to cell site antenna 437, which is the antenna
at the cell site accessed by the RF transceiver 411. Modem 445,
centralized database computer 447, and database 449 are conventional
devices.
FIG. 5 is a flowchart setting forth a procedure for use in conjunction with
the hardware configuration of FIG. 4. The procedure is applied when a law
enforcement officer stops a motorist who allegedly violated one or more
vehicle code provisions. The officer asks the alleged violator to provide
his or her smart identification card, and the procedure of FIG. 5 then
commences. At block 301, the mobile computer terminal in the police car
prompts the user (i.e., a law enforcement officer) to enter a password
into the user interface connected to the mobile computer terminal, and to
place a smart identification card into the smart card scanner. At block
305, the program tests to see whether the smart card scanner can read the
smart identification card. If not, the user interface connected to the
mobile computer terminal prompts the officer: the smart identification
card is not readable.
If the smart identification card is readable, program control progresses to
block 309, where the smart card scanner scans the smart identification
card and uploads one or more file identifiers (i.e., social security
number and/or drivers license number) from the smart identification card.
At block 311, the mobile computer terminal establishes an electromagnetic
communications link with a centralized database computer via modems and RF
transceivers, as was discussed in connection with FIG. 4. The mobile
computer terminal implements a test at block 305 to determine whether
there is an updated file in the mobile computer terminal file update
buffer. If there is an updated file in the file update buffer, the program
progresses to block 317, where the file(s) in the file update buffer are
uploaded from the buffer to the centralized database computer. The
centralized database computer then updates the database (block 319) with
the new files which were uploaded from the buffer in the previous step.
The file update buffer is cleared at block 321, and the program progresses
to block 325.
Block 325 is reached directly from block 321 or, alternatively, upon
execution of the negative branch at block 315. At block 325, the mobile
computer terminal downloads the file identifiers previously received from
the smart identification card to the centralized database computer. The
centralized database computer uploads any files corresponding to the file
identifiers to the mobile computer terminal (block 327). These file(s) are
placed into the file update buffer, and may now be displayed and/or edited
(block 329). The files may be displayed or edited using the mobile
computer terminal user interface. Typical files would include, for
example, drivers license number, drivers license information (height,
weight, etc.), the driving record corresponding to the drivers license
number, vehicle registration information, and/or automobile insurance
information.
Next, the mobile computer terminal prompts the officer to enter one or more
violation identifiers (block 331 ). Each violation identifier corresponds
to and uniquely specifies a particular vehicle code or other law
violation. The mobile computer terminal user interface may optionally
display or read for the officer a brief description of the violation
identifier so as to enable the officer to select the most appropriate
violation identifier(s) for a given situation. At block 335, the mobile
computer terminal user interface optionally accepts and stores the
signature of the alleged vehicle code violator as entered by the violator
on the mobile computer terminal user interface, or as stored on the smart
identification card of the alleged violator. At block 337, the mobile
computer terminal user interface prints out a ticket and optionally a
summons for the alleged violator. The edited files corresponding to the
alleged violator are stored in the file update buffer (block 339). The
mobile computer terminal downloads the violation identifiers to the smart
identification card microprocessor via the smart card scanner (block 341
). The smart identification card microprocessor stores the violation
identifiers in smart id | | |
