CA2570579C

CA2570579C - Vehicle violation enforcement system and method

Info

Publication number: CA2570579C
Application number: CA 2570579
Authority: CA
Inventors: Patrick Moynihan; Lawrence Berman; Josiah Johnson; Cory D. Marchasin
Original assignee: IPT LLC
Current assignee: IPT LLC
Priority date: 2004-06-16
Filing date: 2005-05-12
Publication date: 2014-08-12
Anticipated expiration: 2025-05-12
Also published as: DE602005007038D1; US7731088B2; DK1781513T3; MXPA06014764A; ZA200700448B; AU2011201859B2; US20100123557A1; CN100564113C; US20050279820A1; AU2005262785B2; HK1102008A1; AU2011201859A1; AU2005262785A1; US7988046B2; PT1781513E; ES2308503T3; WO2006007079A1; ATE396093T1; JP2008502830A; EP1781513B1

Abstract

A PDA device (or a PC) is used by a summons issuing person to record the ID of a vehicle boot RFID tag and to transmit to the tag and to a host entity violation data such as summons number, license number, time and date stamp, issuing person ID, location of the vehicle, scofflaw data and so on preentered in the PDA, entered by the issuing person and also by a preferred communication network. This data may be entered into the PDA electronically via a communication network such as the internet or LAN system or manually via a keyboard and telephone communication. The host entity has a data base which is uploaded with this information and has correlation of RFID tag numbers to an unlock combination number for each boot. When the boot is attached to a vehicle, which is owned or driven by a scofflaw, this PDA data is transmitted to the host entity whose contact telephone number is attached to the vehicle being booted. The driver contacts the entity to pay the fine and receive in return the unlock combination. A deposit for the boot is also given in return for the combination. When the boot is returned, the deposit is returned to the driver. The driver thus can release and remove the boot within minutes of returning to the vehicle and can return the boot at his leisure.

Description

VEHICLE VIOLATION ENFORCEMENT SYSTEM AND METHOD
[0001] This invention relates to a system and method for enforcing vehicular parking violations via vehicle immobilizing boots.

[0002] Vehicular parking laws are typically enforced by issuing a summons and placing the summons on the vehicle. The owner of the vehicle reviews the summons on the vehicle, is then required to inquire as to the fine and pays the fine or appears in court to contest the summons. The enforcement of the payment of the fines is haphazard in that in many instances the vehicle owner does not pay the fine and accumulates summons and fines. The fines assessed may be increased substantially for repeat violators who are termed scofflaws, who ignore such summons.

[0003] One solution to insure payment of fines is to place a boot on the vehicle wheel. Such a boot is a device which is attached to the vehicle wheel to make operation of the vehicle impossible since the wheel is no longer able to roll on the pavement due to the presence of the boot. Such boots are commonly used and widely available. Such boots are typically cumbersome and heavy. For example, such boots are disclosed in Japanese patent JP 58076348, UK design 2216967 v1 patents 3008370 and 3007353, and US Pats. Nos. 1,489,272; 1,530,622;
3,907,072; 4,768,359; 5,134,868; 5,315,848; 5,372,018; and 5,673,574.

[0004] Boot systems of the type in use, while unpopular with motorist, have become more accepted. Thus, parking enforcement personnel place the oversize and cumbersome boot on a vehicle wheel, immobilizing the vehicle.
The offender returns to the vehicle and can not use the vehicle. The offender is prompted by a sticker on the window to call the appropriate entity, e.g., the police, the court or an administrator in order to learn how to have the boot removed. The offender is prompted during the call to make his way to the police station, court or administrator, without his vehicle, to a payment location.
The offender is required to pay the fine for this violation and all other outstanding violations, if any. In this regard, boot systems provide for catching scofflaws who have numerous outstanding parking violations. More specifically, once a boot is attached to a scofflaw's vehicle, the authorities can maintain control of the vehicle until all outstanding violations against the owner or operator of the vehicle are paid. Clearly, the use of the boot wheel lock is inconvenient to the offender who must try to obtain alternative transportation from what ever location from what ever location he may have parked to the payment center, which could be some distance away and to which center there is no readily available transportation. Once the offender's account is settled, he or she must return to this vehicle seeking further transportation, while in parallel to the offender returning to his vehicle, to wait a parking enforcement person to remove the boot, Such a person may or may not arrive at the offending vehicle in a timely manner, frustrating the offender. This process can take hours or even days, using up a portion of the collected fine by the summons issuing agency via the man hours spent in arranging for the removal of the boot and in the time necessary for removing the boot and also leaving a very disgruntled citizen. The present inventors recognize that such a system is not satisfactory. It Is costly for both the motorist and the agency responsible for enforcement of the traffic laws. In some cases, the boot is used in lieu of towing on private property to insure payment of parking violation fines. The tow operator may not get the private parking facility for hours to settle the claim.

[0005] The present inventors also recognize that at present there is a commercially available prior art electronic tagging device known as RFID
(radio frequency identification). This device is known to be programmable and which transmits information that is programmed, such as a tag identification number unique to each tag or other information as desirable for a given implementation.
Generally, an RFID tag includes a radio frequency (RF) transmitter, an RF
receiver, an RF modulator, and a memory. The memory retains a digital code manifesting the identification number of the tag that is unique to each tag.
The RF modulator extracts the digital code representing the identification number and other information as stored in the memory as a modulated signal which is applied to the RF transmitter. The RF receiver receives interrogation and control signals which manifest a request for the identification number and other information as may be restored in the memory. An interrogator unit transmits an interrogation signal to the tag to retrieve information stored in the tag. The interrogation unit may also transmit information to be stored in the tag and which information can be retrieved by an interrogator. For example, see US patent no. 6,265,973 which discloses such a tag system. A similar tag system is shown in Fig. 4 herein.

[0006] Of interest also is US Publication No. 2003 0222792 (Serial No.
10/158,493) which discloses a parking meter monitoring system employing PDAs (personal digital assistant), host computer systems employing computers such as personal computers and data bases, a communication network and RFID
transmitting and receiving devices for monitoring the status of parking meters.

[0007] A motor vehicular parking enforcement system according to an embodiment of the present invention comprises of vehicle wheel boot for immobilizing a parking violation vehicle, the boot having a lock encoded with a boot release code for releasing the boot from the wheel. An RFID tag having a unique ID is attached to the boot and which tag includes a memory and a transmitter/receiver communication arrangement for receiving, storing and transmitting first information which may include the tag unique ID. A handheld PDA device is included and includes an RFID reader and transmitter, the device is for entering, receiving, storing and transmitting second information at least to and from the tag including the tag ID and violation data of the parking violation.
Also included is a communications system for communicating the second information to an entity host computer system.

[0008] In one aspect, the device includes a camera for taking and transmitting a photograph of the violation vehicle to the entity host computer system.

[0009] In a further aspect, the system includes a summons issuing governing body data base (SDB) containing scofflaw data and wherein the host computer system includes a link to the communication system for communicating with the SDB to determine the scofflaw status of the violation vehicle and for communicating this status to the entity host computer system.

[00010] In a further aspect, the device includes a communication arrangement for communicating with a summons issuing governing body data base (SDB) containing scofflaw data for storing the scofflaw data in the device memory.

[00011] In a further aspect, the host system includes a communication link for communicating with the SDB to determine and store the scofflaw status of the violation vehicle in the host system memory.

[00012] In a further aspect, the entity host system includes a data base containing the boot release code corresponding to the unique RFID tag and a CPU for corresponding the release code to the boot unique ID for accessing and permitting the communication of the release code to the person associated with the violation vehicle in return for payment of all outstanding fine(s) due from the person.

[00013] In a further aspect, the PDA includes a key pad for entering summons data wherein the data entered includes the name and/or related information regarding the person issuing the summons for the violation, the date, the time, the location selected from codes stored in memory, the license number and state of the vehicle registration, the summons number, and a violation code.

[00014] In a further aspect, the PDA includes a modem for communicating to the host system summons and RFID tag data to the host system and for communicating to a municipality computer system containing scofflaw data for transferring scofflaw data to the PDA.

[00015] In a further aspect, further including a governing body data base of scofflaw data, a card reader/writer associated with the governing body data base for copying scofflaw data to a card associated with the reader/writer, the card for transferring the scofflaw data to the PDA.

[00016] In a still further aspect, the PDA includes a card reader for copying scofflaw data into the PDA from a memory card.

[00017] In a further aspect, a card reader/writer is attached to a computer associated with the scofflaw data base wherein the scofflaw data is uploaded to a memory card as needed.

[00018] In a further aspect, the host system includes a data base with all boot release codes and a CPU for accessing the release code from the host data base for all RFID tags and the corresponding unique RFID codes for which a summons is issued for a parking violation.

[00019] In a further aspect, the PDA includes a memory for storing entered current vehicle violation data and RFID read data including the unique RFID
code and a communication system for communicating the stored violation data including scofflaw data, the RFID read data and the current violation data to the host system.

[00020] In a further aspect, the host system also may include a communication link for communicating to a tow operator the status of the fine payment, the location of the parking violation vehicle and the unlock code for the boot for removal of the boot and towing of the parking violation vehicle by the tow operator.

[00021] A method for enforcing parking violations in a further aspect comprises the step of communicating the violation scofflaw status, the location and ID of a vehicle locking boot attached to a vehicle to a host system controlled by an entity representing a commons issuing controlling governing body. The method further includes the step of communicating the identification of the host system controlling entity to the driver of the parking violation vehicle for payment of the associated fine and for communicating the boot release code to the driver upon payment of the fine.

[00022] In a further aspect, the method includes the step of requiring the driver to pay a deposit in return for the driver receiving the boot release code and providing for the return of the deposit to the driver upon returning the boot to a boot collection depot or station.

[00023] In a further aspect, the method includes providing for the payment of the associated fine to the entity.

[00024] A method according to a further aspect includes attaching an RFID
tag with a unique code and memory to the boot, the boot having an unlock code;

attaching the boot to a vehicle in scofflaw violation of a plurality of parking laws;
communicating data manifesting the violation and scofflaw status of the vehicle, . . .
the unique code and location for the vehicle to the host system entity; and transmitting information to the person driving the scofflaw violation vehicle to enable the person to contact the entity for payment of the fine associated with the scofflaw violations.

[00025] A system for enforcing parking violations in a further aspect comprises a PDA for storing information including parking violation including scofflaw status of a parking violation vehicle, the location and unique ID of a vehicle locking boot attached to and for immobilizing the parking violation vehicle and for communicating this information to an entity host system.

[00026] The system also includes a communication system for communicating the identification of the entity to the driver of the parking violation vehicle for payment of the associated fine. The host system includes a computer and data base for storing the boot ID and boot release code for enabling the communication via the communication system of the boot release code to the driver upon payment of the fine.

[00027] In a further aspect, the boot includes an RFID tag having memory and a unique ID associated with the boot, the PDA having an RFID tag reader and including a memory and keypad for receiving and storing the scofflaw status of the violation vehicle and for recording the details of the violation data, the boot RFID tag ID and location of the boot.

[00028] In a further aspect, the system for enforcing includes a further communication system for permitting the entity and PDA to communicate to a summons issuing governing body data base to determine the scofflaw violation =
. . .
data status of the violation vehicle and for communication to an entity data base the details of the scofflaw violation data, the boot ID and location of the boot.

[00029] In a further aspect, the further communicating system is arranged to permit the PDA to communicate with the host system for transferring violation data stored in its memory.

[00030] In a further aspect, the PDA and boot include an RFID
reader and an RFID tag, respectively.

[00031] In a further aspect, an ID medium is included with the identity of the host entity contact information imprinted thereon for attachment to the violation vehicle.

[00032] In a further aspect, the host system includes a data base in which the boot RFID unique ID is correlated with a corresponding boot release code.

[00033] In a further aspect, the PDA includes a key pad for entering PDA
data and wherein the PDA data entered includes the name of the person issuing the summons for the violation, the RFID unique code, the date, the time, the location selected from codes stored in memory, the license number and state of the vehicle registration, the summons number, the violation code, and scofflaw status data.
In the Drawing:

[00034] FIGURE 1 is a schematic diagram showing a typical boot attached to a vehicle wheel and an embodiment of the system according to the present invention for release of the boot in return for payment of all outstanding fines.

[00035] FIGURE 2 is a more detailed schematic diagram of the system shown in FIG. 1;

[00036] FIGURE 3 is a further more detailed schematic diagram of the system shown in FIG 1; and [00037] FIGURE 4 is a block schematic diagram of an RFID interrogation reader-transmitter and tag system which may be used with the boot of Fig. 1.

[00038] In Fig. 1, violation enforcement system 10 includes a vehicle wheel boot 12 which is attached to a scofflaw's violation vehicle 14 wheel 16. A
scofflaw is a person whose vehicle has a number of outstanding summons for parking violations which have been ignored. The number of outstanding violations to achieve scofflaw status may vary for different number of summons issued by summons issuing governing bodies such as for example, a municipality, a city, a university or a corporation. For example, a scofflaw may have two or more outstanding violations.

[00039] The boot 12 includes a combination lock 18 which is unlocked by inserting a serial arrangement of a combination of numbers whose serial arrangement is unique for each lock. The boot 12 is unlocked by entering the correct combination of the combination encoded lock 18. Attached to the boot by bonding or any other convenient attachment arrangement is a radio frequency identification tag (RFID) 218. The tag operates at radio frequencies as known in this art and will be described below in greater detail in connection with Fig.
4.
The boot 12 is preferably light weight to insure easy portability. The boot 12 has jaws 22, 24 which pivot open and closed about the wheel 16 in response to entering the appropriate combination into the lock 18. Typically the lock 18 is assigned a unique serial number and this serial number is the same as the unique ID code number assigned the tag 218. Each tag 218 of each of a plurality of boots has a unique ID in the tag memory corresponding to the unique serial number of the boot combination lock 18. Thus all boots used by the system 10 are identifiable by their unique RFID code and the preferably identical associated serial number of the corresponding lock 18.

[00040] The system includes a personal digital assistant (PDA) 26. The PDA 26 includes an RFID interrogator 216. The interrogator 216 communicates via a communication system internal to or eternal to the interrogator 216 to a governing body traffic scofflaw data base and to the tag 218 as sown in Fig.
4.

[00041] In Fig. 4, RFID system 214 includes an interrogator 216 and an RFID tag 218. The interrogator 216 includes a host controller 220 to process received information from the RFID tag 218 via receiver/memory 224 and antenna 222 and from the PDA keyboard 250. A separate memory (not shown) may be included in the host controller for receiving and storing the keyboard imputted data separate from the tag inputted data.

[00042] In Fig. 4, The antenna 222 also can receive data via a communication network 28, Fig. 1, from other sources such as from the data base of a municipality traffic violation computer system 30 for receiving scofflaw data. The scofflaw data may also be communicated directly to the host computer system 32 from the municipal computer system 30 via network 28 or from a PDA
26 communication modem 36, Fig. 3, using a communication link to network 28 according to a given implementation. The network 28 may include the internet, a local area network (LAN) or the intranet among others (not shown). Not all PDA

units may have a communication modem 36, Fig. 3, or equivalent communication device.

[00043] The summons issuing person may receive and communicate the scofflaw data from the municipal computer system 30 to the PDA 26 via the modem 36 and network 28, to the RFID tag 218 using an RFID interrogator transmitter to be described below and to the host computer system 34 via a telephone system such as a cell phone (not shown).

[00044] In Fig. 4, the RFID system includes an interrogator 214 which further includes host controller 220 which generates an interrogation command signal which is transmitted by transmitter 226 and antenna 228 as signal 230.
The controller 220 also transmits scofflaw data, and other information in the PDA
memory entered by the summons issuing person via antenna 228, the keyboard 250 or a separate antenna as may be needed.

[00045] The data entered into the PDA memory via the keyboard 250, Fig.
4, by the summons issuing person 38, Figs. 1 and 3, includes data shown in Fig.
2 such as the name of the summons issuing person or municipal officer, the RFID unique tag number, the date, time and location of the summons, the location may be selected from memory as stored codes for cities, municipalities and so on, the license number and registration state of the vehicle the summons number, the violation code and scofflaw indicator which indicates the violator is a scofflaw. The location may also be determined by GPS/GIS system receiver =
located in the PDA. This data may be entered in part via the keyboard 250 such as the location, which may be entered automatically in the alternative via the GPS if the PDA has such a GPS receiver system installed, license information, officer information (which may be entered by a scanner from an officer ID card in some instances when available) whereas the scofflaw data may be entered automatically for those PDAs that include a modem or communication device for communicating with the network 28, Fig. 1. For those PDAs without a modem or equivalent communication device, communication with the entity host and municipality computer systems may be made manually by cell phone or other telephone or communication device via telephone system 40 and then the various data received from personnel at the host and municipality locations entered manually via the keyboard 250.

[00046] In Fig. 4, the RFID tag 218 includes a receiving antenna 236 coupled to a controller 240 via a receiver 238, memory 242 coupled to the controller 240 which extracts appropriate data upon receipt of the signal 230, and a transmitter 244 for transmitting information in the memory 242 via transmitting antenna 234. The interrogator 216 can selectively transmit an interrogation signal and/or first information to the tag which may include violation data such as violation code, summons number, date and time stamp, location, license number and other data entered into the PDA. The tag 218 transmits the RFID signal 232 containing second information in response to receipt of an interrogation signal from the interrogator 216 antenna 228 to antenna 236. This second information includes the tag ID and the pertinent violation data which is transmitted to interrogator 216 via tag 218 antenna 234 to the interrogator antenna 222. The signal 232 manifests the RFID identification number and also violation data that may be stored in the memory 242. Such violation data may be received from the interrogator 216 under the control of controller 220 and stored in the PDA
memory (not shown) as previously entered, manually and/or also electronically from scofflaw data downloaded from the host or municipality computer system.
This data is transmitted by transmitter 226 under control of controller 220.
The keyboard 250 may include keys for controlling the mode of operation of the controller 220 as to issuing an interrogation command signal 230 or first information violation data transmission signal 230 to be stored in the tag 218, as the case may be. The received violation data and the RFID unique number is stored in memory 242 under control of controller 240 and released from memory and transmitted to antenna 234 in response to a control signal received by controller 240 via antenna 236 and signal 230.

[00047] To retrieve information from the tag, the host controller 220 generates an interrogation signal 230 upon command from the keyboard 250 or by a signal received thereby and which signal 230 is transmitted by transmitter 226 and antenna 228 as signal 230 to the RFID tag 218 receiving antenna 236.

[00048] The RFID tag 218 is affixed to the boot in any convenient location by any suitable attachment arrangement. Such an arrangement may include bonding, fixation in a radio transparent housing which is permanently secured to the boot exterior, secured in an internal boot cavity but exposed in a radiation transparent housing for reception and transmission of radio signals from and to the interrogator and so on. An interrogator may also be located at the host system 32 and/or municipality system 30 for entering or retrieving data from the tag 218.

[00049] In Fig. 1, the handheld RFID PDA reader interrogator 216 is used to scan the RFID tag 218. The interrogator 216 logs in its memory the scanned information the unique ID of the tag and the date/time stamp. The remainder of the data required as listed above and as shown in Fig. 2 is entered as described above. The PDA is used, if equipped with a communication modem, to contact the municipality computer system 30 to retrieve scofflaw data which if present, is entered into the PDA memory. The PDA is then used to transmit this information stored in the PDA to the host system 32 data base.

[00050] Any commercially known RFID interrogator 216 and ,tag 218 can be used in the PDA 26 and boot 12 and if necessary, modified as described above. Also, any known PDA can be adapted to include an RFID interrogator 216 such as the TEK protégé RFID adapter. Preferably an employee identification card is included for use by the summons issuer for scanning into the PDA his or her employee number.

[00051] The PDA 26 using the network 28 uploads the violation data stored in the PDA including the tag ID and so on to the host system 32.

[00052] In Fig. 3, the host system 32 includes servers 42 comprising CPUs and memory including data bases 44. The municipality system 30 comprises servers 46 and data bases 48. The municipality system 30 also includes a traffic . .
department data center 50 which has scofflaw data stored therein and which is included in the municipality system 30 data bases 48.

[00053] While the host system 32 and the municipality system 30 are described as servers which include high speed hard drives, fast microprocessors and large memories, conventional PCs may be used in the alternative. Such systems also include printers (not shown) for printing out the necessary data.

[00054] The host system 32 or the municipality system 30 can operate as set up systems for setting up the PDAs 'and tags with the appropriate data such as location codes in the PDA, serial nos. and RFID tag numbers for the tags and so on for use in the system 10. 'The PDAs may also have jacks for attachment to the host system 32 and municipality system 30 for downloading necessary set up information data and implemented with known devices (e.g., file transfer server protocols). The storage devices used in system 10 may be implemented using various data formats as known in this art (e.g., relational databases).
The storage memories may be part of the computer systems or implemented with separate devices. Access to the stored data may be by using Microsoft Access or other suitable databases. The host system and the municipality system servers are located in the same location as the storage devices of the respective systems. Communication therebetween is conventional. The network 28 may be wireless or wired and may be any known system including those noted above.
Printers may be at the same locations as the servers or different locations and coupled by known communication systems.

[00055] In operation, a summons issuer 38, Figs. 1 and 3 issues a parking summons to a vehicle in violation of a parking law, step 54a, Fig. 2. The issuer 38 using the PDA communicates via the network 28, Fig. 1 or telephone system 40, with the municipality computer system data bases 48, Fig. 3, to learn if the vehicle has prior outstanding violations, i.e., is a scofflaw, step 54b. This information is automatically downloaded to the PDA via the network 28 or entered manually if by telephone, step 56, Fig. 2.

[00056] The municipality computer system 30, a governing body, includes the data base 48, Fig. 3, of scofflaw data. The system 30 also, in an alternative embodiment, includes a memory card reader/writer (not shown) associated with the data base 48 for copying scofflaw data to a memory card associated with the reader/writer. The card is used to transfer the scofflaw data from the data base 48 to the PDA. Such cards are referred to as compact flash memory card, secure data (SD) card or other terms and are relatively small, but having high memory, e.g., 16, 64, 128 or 256 megabytes memory capacity, commonly used with digital cameras and other electronic systems. Such card readers are widely available. The PDA also has such a card reader (not shown) for transferring scofflaw data entered onto the card from the municipality computer system 30 data base 43, Fig. 3, into its memory.

[00057] If the vehicle (via its license plate registration number) has such violations, the issuer 38 then enters the data as shown in Fig. 2 at PDA 26 and described above into the PDA via the keyboard and by the network 28, if available. The issuer then attaches the boot 12 to the vehicle wheel 16, step 60.

=

[00058] The boot 12 RFID tag 218 is previously embedded with a unique ID
code number which preferably corresponds to the serial number of the boot 12.
At the same time the tag ID and corresponding combination of the boot lock 18 is already in the data base 44 of the host system entity data center 52, Fig. 3.
This tag ID is correlated in the host data base 44 with the corresponding combination code to unlock the boot 12 associated with that unique tag ID.

[00059] In Fig. 2, the issuer then communicates with the tag to upload the tag ID and then with the host system 32 at step 58. At this time the PDA is used to upload the violation data including the RFID unique code, the date and time of violation, the scofflaw information manifesting if the violator is a scofflaw and to optionally including the total fines attributed to the outstanding violations, optionally also uploaded can be the vehicle make, the vehicle license number, state of registration, the summons number and the violation code via the network 28 or by telephone, if the PDA 26 does not have a modem or communication device for communicating with the network 28. This violation data is also transmitted to the tag 218 via the interrogator 216, Fig. 4., at step 60, Fig.
2.

[00060] The summons issuer 38 also places a sticker on the vehicle with information as to how to remove the boot 12, namely, the telephone number of the entity 62 controlling the host computer system 32. The driver 64, Fig. 1, of the violation vehicle then calls the entity 62 via a conventional telephone system 66, Figs. 1, 2 and 3, step 68.

[00061] The entity 62 is given the summons number (which also may be the boot serial number) by the driver 64. Using this information, a person at the =
entity looks up in its computer system data base the tag ID as communicated to it previously by the summons issuer 38 PDA unit or by telephone from the issuer person. These events may occur within a number of minutes or hours of each other as typically the boot will be attached before the driver returns to the vehicle.
Once the entity has the tag ID it also has the associated scofflaw data and fine information. In the alternative, the entity can contact the municipality data base to obtain the fine information, which is more time consuming and not as desirable as having the fine information immediately available. The entity can use its data base to correlate scofflaw data with fine data to determine the fine due for any number of outstanding summons. However, preferably, this data is provided by the PDA as downloaded directly from the municipality system 30, Fig. 1, or as communicated directly to the host system 32 by telephone from the summons issuer.

[00062] Having the fine information, the entity person advises the driver what the fine amount is. If the driver accepts at this time to pay the fine, he does this by telephone by giving the entity a credit card number to charge the fine at step 70. The payment also includes a deposit for the boot, for example, $500, to insure the driver returns the boot to the entity. This payment is made at step 70, Figs. 2 and 3. When the payment charge is approved by the card holder bank or financial institution, the entity then gives the driver the combination code to unlock the boot 12 by telephone and the address of the agency to return the boot. When the boot is returned at step 72 to the entity, or to an agent or dealer and so on, the boot tag is read by the entity, agent or dealer to insure this boot =
matches the driver data received by telephone. If there is a match, the deposit is returned to the driver. This entire proceeding between the driver and the entity to release the boot from the vehicle is a matter of a few minutes. The driver merely then has to drive to the agency at any time at his convenience to return the boot to obtain the refund of his deposit. This return may be done at the driver's convenience.

[00063] If the driver refuses to pay and does not contact the entity, the entity sends an impound notice to the municipality issuing the summons. In the drawings the term "municipality" is intended to represent any controlling governing body that issues summons for parking violations and may include private parties as well as political entities. The municipality then contacts a towing service via telephone, step 74, Fig. 3, for towing the violation vehicle to an impound site. To tow the vehicle, the tow operator needs to remove the boot, step 76. The tow operator communicates with the entity system 32 via telephone to obtain the required combination of the boot lock, step 74. In the alternative, the operator can use a PDA RFID interrogation tag reader to obtain the boot tag ID and related violation data and to communicate this information to either the entity or to the municipality via the network 28 or by telephone to obtain the unlock combination for the boot. The tow operator then removes the boot and tows the vehicle to an impound site, step 76, and the boot is returned, step 72.

[00064] The boot release code may be a scrolling number to prevent distribution of boot release codes indiscriminately. That is, the codes may be assigned as random numbers to the boots. When so assigned the numbers are then entered into the appropriate host and municipality data bases wherein control of the boots is initially maintained. If the boots are distributed by the municipality, then it assigns the release codes to each boot, records the release code and boot tag IDs and then transmits such codes to the entity with correspondence to the unique tag IDs associated with each boot. The boots preferably have a master override key to release the boot in case of technological failure of the release code.

[00065] While the PDA data is preferably entered manually, the PDA may also have software programming stored therein that enables the PDA to read the scofflaw data base data at the municipality computer system. The PDA has a connector for mating with a receptacle in which such data can be transferred using control circuitry at the municipality computer system 30, Fig. 1.
Additionally, the municipality system 30 may also include a system in the alternative for reading scofflaw data directly into the boot tag without a need for the PDA to do so. This direct input of data into the tag memory at the municipality computer system eliminates possible error in the communication system transmission of such data via the PDA to the tag.

[00066] It should be understood that the PDA may take many forms of electronic communication systems and may include personal computer systems (PC) such as laptops for example. Such laptops have appropriate software programs including RFID read/write capabilities. Access to the stored data may be made using Microsoft Access, or MsSQL, an open source server query language program based server side database system that is commercially =
available form Microsoft Corporation and that is widely used, plain text files (.txt) or other database technologies. The plain text file is key for extracting data from multiple sources and for use with a universal readable format.

[00067] It will occur to one of ordinary skill that the disclosed embodiments are given by way of example, and that modifications may be made to the disclosed systems. For example, the PDA may include a digital camera whose data may also be communicated by the PDA to the RFID tag and to the entity system 32 and/or to the municipality data base system 30. The disclosed embodiments are given by way of example and not limitation. It is intended that the invention is defined by the appended claims and not by the disclosed embodiments.

Claims

1. A motor vehicular parking enforcement system comprising:
a vehicle wheel boot for immobilizing a parking violation vehicle, the boot having a lock encoded with a boot release code for releasing the boot from the wheel;
an RFID tag having a unique ID attached to the boot including memory and a transmitter/receiver communication arrangement for receiving, storing and transmitting first information which may include the tag unique ID;
a handheld PDA device includes an RFID reader and transmitter, the device for entering, receiving, storing and transmitting second information at least to and from the tag including the tag unique ID and violation data of the parking violation; and a communications system for communicating the second information to an entity host computer system.

2. The enforcement system of claim 1 wherein the device includes a camera for taking and transmitting a photograph of the violation vehicle to the entity host computer system.

3. The enforcement system of claim 1 further including a summons issuing governing body data base (SDB) containing scofflaw data and wherein the host computer system includes a link to the communication system for communicating with the SDB to determine the scofflaw status of the violation vehicle and for communicating this status to the entity host computer system.

4. The enforcement system of claim 1 wherein the device includes a communication arrangement for communicating with a summons issuing governing body data base (SDB) containing scofflaw data for storing the scofflaw data in the device memory.

5. The enforcement system of claim 4 wherein the host system includes a communication link for communicating with the SDB to determine and store the scofflaw status of the violation vehicle in the host system memory.

6. The enforcement system of claim 1 wherein the entity host system includes a data base containing the boot release code corresponding to the unique RFID
tag ID, the host system including a CPU for corresponding the release code to the boot unique ID for accessing and permitting the communication of the release code to the person associated with the violation vehicle in return for payment of all outstanding fine(s) due from the person.

7. The enforcement system of claim 1 wherein the PDA includes a key pad for entering summons data wherein the data entered includes the name and/or related information regarding the person issuing the summons for the violation, the date, the time, the location selected from codes stored in memory, the license number and state of the vehicle registration, the summons number, and a violation code.

8. The enforcement system of claim 1 wherein the PDA includes a modem for communicating to the host system summons and RFID tag data to the host system and for communicating to a municipality computer system containing scofflaw data for transferring scofflaw data to the PDA.

9. The enforcement system of claim 1 wherein the host system includes a data base with all boot release codes and a CPU for accessing the release code from the host data base for all RFID tags and the corresponding unique RFID codes for which a summons is issued for a parking violation.

10. The enforcement system of claim 1 wherein the PDA includes a memory for storing entered current vehicle violation data representing the summons being issued for the current violation and RFID read data including the unique RFID
code and a communication system for communicating the stored violation data including scofflaw data from past vehicle violations that have been ignored, the RFID read data and the current violation data to the host system.

11. The enforcement system of claim 1 wherein the host system includes a communication link for communicating to a tow operator the status of the fine payment, the location of the parking violation vehicle and the unlock code for the boot for removal of the boot and towing of the parking violation vehicle by the tow operator.

12. A system for enforcing parking violations comprising:
a PDA for storing information including parking violation including scofflaw status of a parking violation vehicle, the location and unique ID of a vehicle locking boot attached to and for immobilizing the parking violation vehicle and for communicating this information to an entity host system; and a communication system for communicating the identification of the entity to the driver of the parking violation vehicle for payment of the associated fine:
the host system including a computer and data base for storing a boot ID
and boot release code for enabling the communication via the communication system of the boot release code to the driver upon payment of the fine.

13. The system of claim 12 wherein the boot includes an RFID tag having memory and a unique ID associated with the boot, the PDA having an RFID tag reader and including a memory and keypad for receiving and storing the scofflaw status of the violation vehicle and for recording the details of the violation data, the boot RFID tag ID and location of the boot.

14. The system of claim 12 including a further communication system for permitting the entity and PDA to communicate to a summons issuing governing body data base to determine the scofflaw violation data status of the violation vehicle and for communication to an entity data base the details of the scofflaw violation data, the boot ID and location of the boot.

15. The system of claim 14 wherein the further communicating system is arranged to permit the PDA to communicate with the host system for transferring violation data stored in its memory.

16. The system of claim 12 wherein the PDA and boot include respective RFID
reader and RFID tag.

17. The system of claim 12 including an ID medium with the identity of the host entity contact information imprinted thereon for attachment to the violation vehicle.

18. The system of claim 12 wherein the host system includes a data base in which the boot RFID unique ID is correlated with a corresponding boot release code.

19. The system of claim 12 wherein the PDA includes a key pad for entering PDA data and wherein the PDA data entered includes the name of the person issuing the summons for the violation, the RFID unique code, the date, the time, the location selected from codes stored in memory, the license number and state of the vehicle registration, the summons number, the violation code, and scofflaw status data.

20. The system of claim 12 further including a governing body data base of scofflaw data, a card reader/writer associated with the governing body data base for copying scofflaw data to a card associated with the reader/writer, the card for transferring the scofflaw data to the PDA.

21. The system of claim 20 wherein the PDA includes a card reader for copying scofflaw data into the PDA.