HK1131459B

HK1131459B - Parking environment management system and method

Info

Publication number: HK1131459B
Application number: HK09109592.4A
Authority: HK
Inventors: Cory D. Marchasin; Patrick J. Moynihan; Josiah D. Johnson; Lawrence Berman
Original assignee: Ipt, Llc
Priority date: 2006-03-31
Filing date: 2007-03-30
Publication date: 2012-09-14

Description

Parking environment management system and method

Technical Field

The present invention relates generally to parking regulation enforcement and more particularly to systems and methods for supervising, managing and monitoring parking procedures.

Background

Public and private supervised parking programs have been striving to overcome problems that seem not to be easily solved: parking services are provided to a continuously increasing number of vehicles for areas having a limited number of parking spaces. In particular, there is an increasing effort to manage problems in residential communities, where cities and towns attempt to provide local residents with parking spots. This work typically involves the use of a parking program designed to implement a set of rules and regulations governing parking privileges in a particular area or zone.

Traditional parking procedures require the enforcement of regulatory parking laws and regulations by a number of law enforcement personnel, known as parking enforcement officers. The PEO typically monitors an area and oversees parking violations by visually inspecting the offending vehicle (e.g., the identification of the offending parked vehicle) or surrounding areas (e.g., observing the vehicle's location in front of a "no parking" sign, the expiration of a parking timer, etc.).

The use of still other parking programs can dictate and limit parking privileges in an attempt to ensure residents that local residents can find a location on the street or in a parcel to park. The purpose of such license-based parking programs is to encourage people to obtain a license for parking rights or to bill a licensee-less vehicle, limit time, or park in a garage.

However, parking programs are very difficult to implement and manage and expensive. The inefficiencies in supervising these parking programs and the lack of regulatory enforcement are faced with the generation of current parking programs, which results in significant dilution of the desired revenue.

For example, a small municipality that makes license-based parking programs may face the job of issuing 20000 to 500000 licenses per year, which requires a complete review of the municipality's existing parking regulation execution plans.

While issuing a license aids in the establishment of parking regulations, there are a number of disadvantages to using a conventional license. Conventional licenses are typically implemented as stickers that are affixed to the windows of the vehicle or hang tags that hang within the vehicle (i.e., from the rear view mirror). However, it is often difficult to determine whether a license is present based on a visual inspection of the vehicle for a number of factors, including the presence of tinted windows and/or the placement of the vehicle (e.g., angled parking). This creates a significant workload on the person responsible for inspecting the vehicle to determine if the vehicle is parked legitimately, called the Parking Enforcement Officer (PEO), who must locate and read the permit by visual inspection of the vehicle.

In addition, conventional licenses are frequently stolen or "scaled" (i.e., sold by an authorized license holder to an unauthorized person). Such abuse is extremely difficult to detect and terminate because there is no efficient way to track the regulatory licenses under the parking program.

To enforce parking laws, parking programs typically issue tickets or citations and place the citations on the vehicle. Typically, the vehicle owner and/or operator verifies the citation and is asked for a fine amount and a satisfactory method of processing. Next, the vehicle owner/operator takes action to pay the fine and/or attend a court to resist. The enforcement of the payment of the fine is non-mandatory, because in many cases the vehicle owner does not pay the fine and accumulates many summons and fines. For frequent offenders called scofflaw who ignore such summons, the penalty collected is basically incremented.

One conventional method of ensuring the payment of the fine is to immobilize the vehicle by placing a boot (boot) on the wheel. A boot is a device that is attached to a wheel and makes it impossible for the vehicle to travel because the wheel is no longer able to roll on the road surface due to the presence of the boot. Such latches are generally inconvenient and cumbersome. Such latches are disclosed, for example, in japanese patent JP 58076348, british design patents 3008370 and 3007353, and U.S. patent 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, all of which are incorporated herein by reference.

The use of such latching systems, while not preferred by motorists, has become increasingly popular. Therefore, parking enforcement officers place oversized and heavy latches on the wheels, making the vehicle unable to travel. If the offender returns to the vehicle, the vehicle cannot be used. The offender is prompted by a ticket on the window to call the appropriate entity (e.g., law enforcement) to obtain instructions on how to release and remove the boot. During the call, the offender is prompted to go to the police, court or supervisor to the fine payment department without driving in front. The offender needs to pay a fine for this violation, as well as all other outstanding violations, if any. In this regard, the latching system supports capturing scofflaw with multiple outstanding parking violations. More specifically, once the boot is attached to the scofflaw's vehicle, law enforcement may control the vehicle until a fine is paid for all outstanding violations by the vehicle owner or driver.

Clearly, the use of a boot lock is inconvenient for the offender who must attempt to take an alternative mode of transportation from his parking location to the fine payment center, possibly a distance to and from the fine payment center and no readily available mode of transportation. Once the offender's account is cleared, he or she must return to his vehicle in another mode of transportation to wait for the parking officer to remove the boot. The person may or may not arrive at the offending vehicle in time, which prevents the offender from retrieving the vehicle smoothly. This process can take hours or even days, consuming a portion of the fine received by the summons issuing agency due to the man-hours spent in scheduling the removal of the boot and the time required to remove the boot, while also incurring a very unsatisfactory criticism.

Moreover, it is costly for both the motorist and the authorities responsible for law enforcement of traffic laws. In some cases, a boot is used to ensure payment of parking violation fines instead of dragging a property of a private person. The trailer operator may not be able to reach a private parking facility in hours to address the complaint.

Accordingly, there is a need for a method and system for efficiently and effectively implementing, managing, supervising, monitoring and executing parking programs.

Disclosure of Invention

The above problems are solved and a technical solution is achieved in the art by a system and method for managing a parking environment. In accordance with an embodiment of the present invention, a parking management system includes a detection module for determining and detecting parking violations, a enforcement module for performing one or more enforcement actions, and a resolution module that facilitates performance of appropriate remedial actions in response to the enforcement actions.

According to an embodiment of the present invention, the detection module, enforcement module, and resolution module of the parking management system may include a permit management system, one or more RFID readers, and a plurality of parking permits, each parking permit having a unique RFID tag and tag identifier (e.g., a tag number comprising a series of alphabetic characters). The license management system is configured to manage license-based parking programs, which are described in detail in related U.S. patent application serial No. 11/281,841 and incorporated herein by reference.

In accordance with an embodiment of the present invention, the enforcement and resolution components of a parking management system may include a boot-based enforcement system that includes a plurality of vehicle boots each having a unique boot RFID tag and boot tag identifier (e.g., comprising a series of alphanumeric characters) readable by one or more RFID readers and the boot management system, as described in detail in related U.S. patent application Serial No. 11/122,953, and incorporated herein by reference.

In accordance with an embodiment of the present invention, a permit management system (referred to as a "PermitView" system) provides a detection module, a enforcement module, and a resolution module that efficiently supervises, manages, and implements a permit-based parking program (referred to herein as a "parking program") that manages a permit-based parking environment.

According to an embodiment of the invention, each permit included in the parking program is assigned a unique RFID tag identifier (e.g., a tag number) that is stored in an RFID tag attached to or embedded in the permit (e.g., in the form of an RFID chip). The RFID tag identifier is associated with information or data specific to the parking permit including, but not limited to, data for obtaining authorized vehicles, permit holder data, and parking rights data (commonly referred to as "tag data").

According to an embodiment of the present invention, the PermitView system includes a computer accessible memory for storing the RFID tag identifier and associated tag data for each permit maintained by the parking program to allow real-time management during the life of the permit.

According to an embodiment of the present invention, one or more parking areas (referred to herein as "zones") of a license-based parking environment controlled by a parking program are monitored by one or more RFID readers, which may be handheld devices or fixed readers operated by a parking enforcement Officer (parkingengineering Officer). The RFID reader scans the parked vehicle, reads the RFID tag, and captures the RFID tag identifier. To determine whether the vehicle is parked under the permit, the RFID reader accesses a computer accessible memory of the PermitView System and queries tag data associated with the captured RFID tag identifier.

According to embodiments of the present invention, a PermitView system efficiently determines whether a scanned vehicle is parked within the privileges associated with a permit. If the vehicle is parked outside the parking jurisdiction to which the permit was granted, appropriate enforcement actions are performed (e.g., issuing a citation, disabling the vehicle, and/or issuing a warning) and recorded by the PermitView System.

According to an embodiment of the present invention, data (e.g., color, make, model, year, license plate number, etc.) of the authorized vehicle associated with the scanned RFID identifier is transmitted to the RFID reader for comparison with the parked vehicle data to determine whether the authorized vehicle (i.e., the vehicle associated with the license) is using the license.

According to embodiments of the present invention, a plurality of different users (e.g., a permit holder, a permit applicant, a parking program manager, a permit viewing administrator, and one or more readers) may access the permit viewing system via a user interface.

According to embodiments of the present invention, one or more docking stations adapted to dock one or more handheld RFID readers may access the PermitView System. The docking station communicates with the PermitView System to synchronize data stored in the system with data stored on the RFID reader. In addition, one or more fixed RFID readers may be connected to the system for data synchronization.

According to an embodiment of the present invention, the newly issued permit is registered with the PermitView System, which acts as a clearinghouse for all permits managed pursuant to the parking program. The license viewing system can track and monitor the usage of each license over the expiration date of the license.

The PermitView system provides for the efficient implementation of parking regulations, creating a safe and structured parking environment that facilitates the benefits of permit holders and parking procedures.

In accordance with an embodiment of the present invention, a boot-based enforcement system provides for the use of a vehicle boot to disable an offending vehicle (i.e., enforcement action). Alternatively, the boot-based enforcement system may also provide fine surveillance as an enforcement action that accompanies the immobilization of the vehicle. Boot-based enforcement systems include boot management systems, known as "BootView" systems, that provide for the administration and management of boots. Moreover, the BootView system facilitates the execution of the release and return of the BootLock after appropriate remedial actions (e.g., the payment of a fine) are performed.

Drawings

The present invention will be more readily understood from the detailed description of exemplary embodiments presented below taken in conjunction with the attached drawings, in which:

FIG. 1 is a pictorial illustration of a permit-based parking environment including a permit management system in accordance with an embodiment of the present invention;

FIG. 2 illustrates an exemplary process for managing a license-based parking environment, according to an embodiment of the present invention;

FIG. 3 illustrates an exemplary process performed by a license management system according to an embodiment of the invention;

FIG. 4 illustrates steps according to an exemplary privilege analysis, according to an embodiment of the present invention;

FIG. 5 is a schematic diagram illustrating a boot-based enforcement system according to an embodiment of the present invention;

FIG. 6 is a schematic illustration of a boot-based enforcement system according to an embodiment of the present invention;

FIG. 7 is an illustration of a boot-based enforcement system according to an embodiment of the present invention;

FIG. 8 is a schematic block diagram of an RFID query reader-transmitter tag system in accordance with an embodiment of the present invention;

FIG. 9 is a diagrammatic view of a parking management system in accordance with an embodiment of the present invention.

It is to be understood that the drawings are for purposes of illustrating the concepts of the invention and may not be to scale.

Detailed Description

The present invention relates to a method and system for managing a parking environment. The parking management system includes a detection module for detecting a parking violation (i.e., identification of an illegally parked or associated vehicle), an enforcement module for performing a corresponding enforcement action, and a resolution module for facilitating performance of a remedial action by a vehicle owner/operator.

According to an embodiment of the present invention, the detection module of the parking management system identifies a parking violation or related vehicle, commonly referred to as a "violation," by visual inspection of the vehicle or its surroundings (i.e., the parking meter) by a human worker (i.e., a parking officer) and/or by scanning an RFID tag associated with the vehicle to determine the parking privileges assigned to the vehicle, as described in more detail below.

Once the violation is detected, a enforcement module of the parking management system provides for the performance of one or more enforcement actions. The "law enforcement action" may include any one or more of the following actions: 1) issuing a summons or billings with associated fines or penalties; and/or 2) seal the vehicle (e.g., disable the vehicle from traveling, tow the vehicle, etc.).

After performing the enforcement action, a resolution module of the parking management system assists a vehicle owner/operator corresponding to the enforcement action in performing the remedial action. For example, if a fine is approved and the vehicle is disabled (law enforcement action), the system assists the vehicle owner/operator in paying the fine, disarming an immobilization device (e.g., vehicle boot) and returning to the disablement device (remedial action).

According to an embodiment of the invention, the resolution module is a computer-based and/or human-based system that includes a payment processor configured to communicate with a user and process payment of a fine associated with a parking violation, a cancellation processor configured to transmit an unlock code to an enforcement device for enforcement of the parking violation, and a return processor configured to transmit a return instruction to the user.

A parking management system that manages the overall end-to-end detection, enforcement, and resolution process may include one or more computer-based systems and/or human-based systems.

According to embodiments of the present invention, the parking environment managed by the parking management system of the present invention may include one or more parking areas or "zones" controlled by a parking program. The "parking program" includes a set of rules and regulations governing parking in multiple zones of a parking environment.

According to embodiments of the present invention, the detection module may include one or more parking enforcement officers that identify parking violations by visually inspecting the vehicle (i.e., inspecting the license plate number and/or registration sticker of the vehicle) and/or the vehicle surroundings (e.g., parking meters, curb markings, parking-related signs, etc.). Based on the visual inspection, the parking enforcement officer may determine that the vehicle is currently violating the regulatory parking regulations or that one or more parking tickets (i.e., scofflaw) have been issued to the vehicle and/or vehicle owner by performing an inspection of the license plate number.

According to embodiments of the present invention, a parking management system may be used to manage a license-based parking environment. The detection of parking violations in a permit-based parking environment may be performed using a permit management system (referred to herein as a PermitView System 1), one or more RFID readers 8 for scanning vehicles located in one or more zones, and one or more parking permits 11 (shown in FIG. 1), wherein the one or more parking permits 11 (shown in FIG. 1) each include a unique RFID TAG (referred to in FIG. 1 as RFID TAG _1, RFID TAG _2,. RFIAG.. and RFID TAG _ N representing a parking program with "N" number of permits). Those skilled in the art will recognize that while the present invention is described as including RFID reader technology, other reading devices and systems may also be used in accordance with the present invention.

According to an embodiment of the present invention, the PermitView System 1 is a computer-based system accessible by one or more users, including, but not limited to the following components: user interface 20, report generator 30, rights module 40, and license database 50. The term "computer" shall include any data processing device, such as a desktop computer, a laptop computer, a mainframe computer, a personal digital assistant, a server, a handheld device, or any other device capable of processing data. Optionally, the PermitView System 1 may include a synchronization module 60, according to an embodiment of the present invention.

Those skilled in the art will recognize that the components of the PermitView System 1 may be located on a single computer (as shown in FIG. 1) or on more than one communicatively connected computer. The term "communicatively connected" shall include any type of connection, whether wired or wireless, that can communicate data. The term "communicatively connected" shall include a connection between devices and/or programs within a single computer or a connection between devices and/or programs on separate computers. Those skilled in the art will recognize that at least a portion of the PermitView System 1 may comprise a human-based component. For example, the user interface 20 may be a call center or a conventional office where a person (e.g., a licensee or applicant) may access the PermitView System 1 via a telephone or in-person communication 5B, as shown in FIG. 1.

The PermitView System 1 may be a computer-executable application or program accessible by a plurality of user groups, wherein the characteristics of the user groups indicate the level, amount, and type of permissible access to the PermitView System 1. According to an embodiment of the invention, the following primary user groups are defined: a licensee and licensee applicant, a parking program manager, a permit viewing administrator, and an RFID reader. Each user group accesses the PermitView System 1 via a respective user interface 20 that is specifically tailored and/or configured based on the particular user group. The user interface 20 provides user group specific access to the PermitView System 1, with the level of access being customized specifically for each user group.

The "licensee/applicant" user group includes all persons having or attempting to acquire one or more licences associated with one or more zones supervised under a parking program. As shown in FIG. 1, a "licensee/applicant" user group can access the PermitView System 1 via the licensee/applicant portal of the user interface 20 using a computer, referred to as the licensee/applicant computer 5. Those skilled in the art will recognize that the "licensee/applicant" user group may also access the PermitView System 1 via other means, such as via telephone or in-person communication 5B, as shown in FIG. 1.

The "PermitView Administrator" user group includes all persons authorized to maintain, manage, monitor, supervise, or otherwise control the PermitView System 1. As shown in FIG. 1, a "license administrator" user group may access the PermitView System 1 via the license Administrator portal of the user interface 20 using a computer, referred to as the license Administrator computer 6.

The "parking program manager" user group includes all persons authorized to maintain, manage, monitor, supervise or otherwise control the permit-based parking program being managed by the PermitView System 1. As shown in FIG. 1, a "parking program manager" user group accesses the PermitView System 1 via a parking manager portal of the user interface 20 using a computer, referred to as the parking manager computer 7. Those skilled in the art will recognize that the "parking program manager" user group may access the call center and/or office-based user interface 20 via telephone or in-person communication.

The "reader" user group includes any device, preferably an RFID device, adapted to scan vehicles or readable devices enclosed therein in one or more zones. As shown in FIG. 1, a reader user group accesses the PermitView System 1 via a reader portal of a user interface 20 using a communicatively connected reader 8.

According to embodiments of the present invention, the license holder computer 5, the license viewing administrator computer 6, the license administrator computer 7, and the reader 8 may each include a Web browser 5A, 6A, 7A, 8A that provides access to one or more Web-based networks (e.g., network/Internet 100). Each Web browser 5A, 6A, 7A, 8A is communicatively connected to the PermitView System 1 via the network/Internet 100. Those skilled in the art will recognize that any Web browser is suitable for use in the present invention, including but not limited to FireFox, Microsoft Internet Explorer、Netscape、Opera、WebTVAnd Mozilla^TM。

According to a preferred embodiment, the reader 8 may be any suitable device or computer capable of reading RFID tags. The reader 8 may be a handheld device or a fixture operated by the PEO. Those skilled in the art will recognize that reader 8 may be passive, active, or semi-active. The reader 8 may include one or more software applications or programs (e.g., RFID/barcode scanning and license authentication software such as permittinder, citation writing software, etc.) configured to perform functions performed by the reader 8, including but not limited to data capture, data storage, and scanning activity.

The reader 8 may be configured to access data stored in the database computer using any suitable program or language, such as Microsoft access, MsSQL, a server-side database system based on open source server query language programs, plain text files (.txt), and/or other database technologies available from, for example, Microsoft corporation. Plain text files are key to extracting data from multiple sources and using it through a universally readable format. Suitable readers 8 for use in connection with the present invention include, but are not limited to, Symbol MC9000-G RFID devices. One skilled in the art will recognize that the parking permit may include any readable device or component in addition to an RFID tag. Thus, the reader 8 may be any device capable of reading a readable device or component associated with a parking permit.

According to embodiments of the present invention, one or more handheld docking stations 9 adapted to connect to one or more handheld readers 8 may be communicatively connected to the PermitView System 1 via the network/Internet 100. The handheld reader 8 may dock in the handheld docking station 9 for synchronizing data stored in the PermitView System 1 with data stored on the handheld reader 8.

According to an embodiment of the present invention, the handheld docking station 9 may be communicatively connected to the PermitView System 1 via a synchronization Module 60. The synchronization module 60 may be a computer-executable module capable of downloading data from and/or uploading data to one or more readers 8 docked in the docking station 9. Specifically, the synchronization module 60 may download/upload data including, but not limited to, a list of valid licenses, software updates, PEO identification information, a list of scans performed by the PEO, a list of scan results including any law enforcement actions taken (e.g., issuing a citation; specific details regarding a ban, etc.), notifications and reminders for the PEO, a list of invalidation notifications (described in more detail in connection with FIG. 2), and the like. An exemplary synchronization module 60 suitable for use in the present invention is the SQL 2000/CE synchronization tool.

According to embodiments of the present invention, data stored on the handheld reader 8 and in the PermitView System 1 may be synchronized in real-time via a wireless connection between the reader 8 and the PermitView System 1.

According to an embodiment of the present invention, the PermitView System 1 includes a report Generator 30. Report generator 30 is a computer executable module configured to generate reports regarding parking procedures. Those skilled in the art will recognize that the report generator 30 may generate a variety of reports including any information regarding the parking program maintained by the PermitView System 1.

Exemplary reports that may be generated include, but are not limited to, reports on: 1) property information (e.g., accounts receivable for parking procedures); 2) scanning results; 3) PEO-specific reports, including PEO execution information (e.g., scan number, alarm/notification number, summons number, number of times the PEO failed to take action, etc.); 4) license holder account information; 5) a license inventory; 6) law enforcement action information; 7) parked vehicle data; and 8) tag data.

The user group (licensee/applicant, parking program manager, reader, and/or PermitView manager) may submit a request for a report to report generator 30 via user interface 20. Based on the report request, the report generator 30 retrieves the corresponding information from the communicatively connected computer accessible memory (the communicatively connected computer accessible memory refers to the license database 50), generates a report, and provides the report to the requesting user group via the user interface 20 or the synchronization module 60. The term "computer accessible memory" shall include any computer accessible data storage device or database, whether volatile or non-volatile, electronic, optical, or otherwise, including, but not limited to, floppy disks, hard disks, CD-ROMs, DVDs, flash memory, ROMs, and RAMs.

Those skilled in the art will recognize that the report generator 30 may be configured to automatically run reports at one or more specific time intervals (e.g., hourly, daily, weekly, monthly, yearly, etc.) according to a predetermined and customized schedule. For example, the report generator 30 may run a daily report detailing each violation occurring in a particular zone during the previous 24 hours and automatically deliver the report to the parking program manager computer 7 and/or the reader 8 associated with that zone.

According to an embodiment of the present invention, the report generator 30 may automatically receive report requests from the communicatively connected synchronization module 60 according to a predetermined schedule. For example, the synchronization module 60 may send a daily request for a report providing license data updates for communication with one or more readers 8 docked in the handheld docking station 9.

According to an embodiment of the invention, when the handheld docking station 9 detects docking of a reader 8, it may automatically send a report request to the synchronization module 60. The synchronization module 60 may then send a request to the report generator 30 to give satisfaction. For example, the handheld docking station 9 may be configured to automatically request a report containing updated license holder information for a particular zone associated with a particular reader 8 each time the particular reader 8 docks in the handheld docking station 9.

FIG. 2 illustrates an exemplary process for monitoring a license-based parking environment to determine whether a vehicle parked therein is parked under license. It is to be understood that the schematic representation provided in fig. 2 is exemplary in nature and that a number of alternative arrangements are within the scope of the present invention.

In step S1, the reader 8 scans vehicles parked in the license-based parking area managed by the PermitView System 1. The reader 8 scans the vehicle to determine if it contains a parking permit with a valid RFID tag. Those skilled in the art will recognize that the license may take the form of a sticker affixed to the vehicle or an item suspended within the vehicle. The reader 8 may be a fixed reader or a handheld reader operated by a PEO as described in accordance with an embodiment of the present invention. According to an embodiment of the present invention, the RFID reader 8 is configured to detect and read licenses and corresponding RFID tags from a distance. Further, those skilled in the art will also recognize that reader 8 may perform scanning while reader 8 is in motion.

In step S2, the reader 8 determines whether an RFID tag is detected. If the tag is not detected, the reader 8 and/or PEO determines the reason for the failure to detect the tag at step S3A.

During step S3A, if it is determined that the failure to detect the tag is due to a mistake by the reader operator (i.e., the PEO), the vehicle is scanned again at step S1. If the failure to detect the tag is due to a reader failure, the reader 8 is repaired or replaced.

Alternatively, during step S3A, it may be determined that the failure to detect a tag is due to a tag failure or tag loss. In either case, in step S4, the PEO identifies information about the checked parked vehicle (referred to as "parked vehicle data") and inputs the parked vehicle data into the reader 8. The parked vehicle data may include, but is not limited to, the following information: 1) the make, model, year and color of the vehicle; 2) the license plate number of the vehicle; 3) the location of the parked vehicle (e.g., parcel, street, and/or zone); and 4) the date, time, and day of week of the scan. Those skilled in the art will recognize that the PEO may enter parked vehicle data into the reader 8 using any suitable input means, such as a keyboard, keypad, and/or voice recognition system.

In step S5, the data for the parked vehicle is used to determine whether a valid tag is associated with the scanned vehicle. For example, if under a visual inspection of the vehicle, the PEO determines that there is no permit/label present, or that there is a label/permit present, but the label is invalid, the license plate number of the vehicle may be queried in the PermitView System 1 to determine if a valid label is associated with the vehicle. If so, in step S5A, the PEO may issue a notification or warning to the license holder that the holder failed to properly display the license/tab or that the license failed. According to embodiments of the present invention, the PermitView System 1 may track the number of such notices issued to a particular licensee, and if the number exceeds a certain threshold (i.e., three previous warnings), a corresponding enforcement action may be taken (e.g., issuing a citation or disabling the vehicle). The enforcement action may include, but is not limited to, one or more of the following: 1) issuing a summons or billings; 2) issue a notification or alert; 3) disable the vehicle (i.e., install the boot) and/or 4) no action.

If, during step S5, it is determined that no valid tag is associated with the parked vehicle, a determination is made in step S8 as to the corresponding enforcement action.

Alternatively, if during step S2, a tag is detected, the reader 8 captures a unique RFID tag identifier (referred to herein as a "tag number") in step S3B and identifies the parked vehicle data in step S4. One skilled in the art will recognize that the tag number may be any length string of alphanumeric characters capable of uniquely identifying the particular license with which it is associated. According to an embodiment of the present invention, the tag number is stored on an RFID tag embedded in or attached to the license.

Having captured the RFID tag number and parked vehicle data, the reader 8 sends this data to the PermitView System 1. FIG. 3 illustrates at least a portion of the steps of the license management process performed by the PermitView System 1. As shown in fig. 3, in step SI, the PermitView system 1 receives the tag number and the parked vehicle data from the reader 8 via the user interface 20. In step SII, this information is provided to the rights module 40, and the tag data associated with the tag number is retrieved from the license database 50 by the rights module 40.

According to embodiments of the present invention, "tag data" includes, but is not limited to, the following information: 1) obtaining authorized vehicle data; 2) license holder data; and/or 3) parking privilege data. "authorized vehicle data" includes, but is not limited to, make, model, color, year, and/or license plate number of one or more vehicles authorized under a valid license. "licensee data" includes, but is not limited to, the licensee's name, address, phone number code, email address, and/or fax number code. "parking rights data" generally defines the rights or scope of parking rights possessed by the permit holder, including but not limited to: a) one or more locations, areas, streets, lots, spaces or areas where the vehicle is permitted to park; b) terms of the license and/or expiration date of the license; and/or c) one or more valid parking hours (i.e., weekend-only rights, weekday-only rights, quarterly rights, etc.).

In step SIII, the rights module 40 performs a rights analysis, as described in detail below in conjunction with FIG. 4. In step VI, after the permission analysis is conducted, the permission module 40 transmits the result of the permission analysis to the reader 8.

Returning to the process of FIG. 2, in step S8, if it is determined that there is a violation based on the permission analysis (see step S7), or no valid tag is associated with the parked vehicle as described above (see step S5), a determination is made as to the corresponding enforcement action to be taken. Those skilled in the art will recognize that the determination regarding the corresponding law enforcement action may be made by the PermitView System 1 (as part of the privilege analysis), by the PEO, or by the parking program manager.

FIG. 4 illustrates steps involved in an exemplary privilege analysis according to an embodiment of the present invention. Generally, the permission analysis is performed by the PermitView System 1 and includes, but is not limited to, comparing the parked vehicle's data to the parking permission data associated with the permit assigned to the parked vehicle. In step SA, the authorization module 40 determines whether the parked vehicle data matches the authorized vehicle data associated with the scanned tag number in the license database 50. If the data does not match, there is an abuse of the parking permit and a parking violation has occurred. For each parking violation that occurs, the permit database 50 stores information about the parking violation, referred to as "parking violation data". The parking violation data may include, but is not limited to, data for parked vehicles (i.e., information about the offending vehicle); vehicle owner information (obtained from the license plate number), PEO information, the type of law enforcement action taken, etc. For example, a stolen or illegally assigned license to an unauthorized vehicle will produce this type of mismatch, and a corresponding parking violation. According to an embodiment of the invention, if an abuse license is detected, the PermitView System 1 may set a temporary disable (temporal hold) to the license, thereby informing the PEO that the license is invalid or otherwise invalid.

Alternatively, the PermitView system 1 may transmit authorized vehicle data associated with the scanned permit to the reader 8. Then, based on a visual inspection of the vehicle, the PEO can determine whether there is a mismatch between the parked vehicle data and the authorized vehicle data.

If the data match, then in step SB, the authorization module 40 identifies the parking authorization data (i.e., the scope of authorization) assigned to the permit. According to an embodiment of the present invention, the parking right data may be defined in the parking program at the time of issuing the license or at the time of subsequent update or editing. For example, the licensee john smith has parking rights including the region "C" main street between monday and friday 6PM to 7AM in jobusson, new jersey. In addition, the same license may also include permissions that allow john smith (students of the summer class of the university of Rutgers) to park their vehicle in the campus in the parcel zone "11"/the parcel zone "H"/the space "19-27/from 7 months 15 to 8 months 15. Collectively, these parking rights constitute the parking rights data associated with the parking permit of john smith.

Referring to fig. 4, in step SC, the authority module 40 compares the data of the parked vehicle with the parking authority data. Next, in step SD, a determination is made as to whether the vehicle is parked within the authority range. If not, then a parking violation is determined to have occurred and parking violation data is recorded and stored in the permit database 50. Those skilled in the art will recognize that parking violation determinations may be made by the PermitView System 1, the PEO, or the parking program manager.

In the example presented above, it is assumed that the vehicle of john smith is parked in parcel 9/parcel "B"/space 6 on day 7 and day 17. In step SC, this data of the parked vehicle is compared with the parking authority data, and in step SD, a determination is made that a parking violation has occurred. According to an embodiment of the invention, the rights module 40 communicates the results of the rights analysis to the reader 8 for performing the corresponding law enforcement action. Further, the parking violation data is also stored in the license database 50.

One skilled in the art will recognize that law enforcement actions may be performed in response to detecting a parking violation and/or identifying a scofflaw. A scofflaw is a person whose vehicle has a number of outstanding parking violation tickets that are not considered for consideration. The number of times an outstanding violation reaches the scofflaw status may vary depending on the different numbers of tickets issued by the ticket issuing regulatory agency (e.g., municipality, city, university, or corporation). For example, a scofflaw may have two or more outstanding violations.

One exemplary law enforcement action that may be performed by the parking management system is the administration of a fine (e.g., a fine punishment). According to this embodiment, the parking management system includes a payment processing module configured to facilitate payment of the fine (i.e., remedial action). The payment processing module may be a computer-based system and/or a human-based system that provides the vehicle owner/operator with a way to pay the outstanding fines.

Another exemplary enforcement action includes disabling the offending vehicle. According to this embodiment of the invention, the enforcement module includes a boot-based enforcement system 100 configured to perform the disabling of the vehicle. As shown in FIG. 5, the exemplary enforcement module includes a boot-based enforcement system 1000 that includes one or more wheel boots 12 for disabling the vehicle 14, one or more readers 8 configured to communicate with the boots 12, and a boot management system 500 communicatively connected to the one or more readers 8 and/or the plurality of boots 12 of the boot-based enforcement system 1000.

The boot 12 includes a combination lock 18 that is unlocked by inserting an "unlock code," which may be a combination of characters (e.g., numbers, letters, symbols, etc.) whose arrangement is unique for each lock 18. Attached to the boot 12 by binding or any other conventional attachment arrangement is a boot RFID tag 218. The boot RFID tag 218 operates at radio frequencies as is known in the art and will be described in more detail below in conjunction with fig. 8. The shackle 12 is preferably lightweight to ensure easy portability. According to an embodiment of the invention, the latch 12 may have clamping devices 22, 24, the clamping devices 22, 24 being pivotally opened and closed about the tire 16 in response to inputting a corresponding combination to the lock 18. Typically, the lock 18 is given a unique serial number, and the serial number is the same as the unique ID code number given to the boot RFID tag 218. Each boot RFID tag 218 of each of the plurality of boots has a unique ID in the tag memory that corresponds to the unique serial number of the boot combination lock 18. Thus, all boots used by boot-based enforcement system 1000 may be identified by their unique RFID codes and the preferably same associated serial number of the corresponding lock 18. .

As described above, the reader 8 may be a PEO operated handheld device (e.g., a PDA) or a stationary device. Those skilled in the art will recognize that reader 8 may be passive, active, or semi-active. The reader 8 may include one or more software applications or programs (e.g., RFID/bar code scanning software, citation writing software, etc.) configured to perform functions performed in the reader 8, including but not limited to data capture, data storage, and scanning activity. Suitable readers 8 for use in connection with the present invention include, but are not limited to, Symbol MC9000-G RFID devices.

According to one embodiment of the invention, the BootManager system 500 (referred to herein as the "BootView" system 500) includes the Bootdatabase 44, the fee payment processor, and the BootRelease module. The BootView system 500 may include one or more computer and/or human-based processing components configured to provide for the efficient administration and management of boots 12 of the boot-based enforcement system 1000.

According to an embodiment of the present invention, each boot 12 included in the parking program includes a unique boot RFID tag identifier (e.g., a tag number) that is stored in a boot RFID tag 218 attached to or embedded in the boot 12 (e.g., in the form of an RFID chip). The boot RFID tag identifier is associated with information or data specific to the boot, including but not limited to: 1) a code for locking the shackle (i.e., a locking code); 2) a code for unlocking the latch (i.e., an unlock code); 3) the type of latch/manufacturer; 4) a serial number; 5) a default or basic unlock code; 6) a currently valid unlock code; 7) the location of the boot (i.e., the location tracked by the GPS or other tracking system); 8) maintaining records; 9) diagnostic information such as battery charge, accelerometer readings (i.e., shock or vibration), and/or temperature; and/or 10) the current locked state (e.g., locked or unlocked), which are commonly referred to as "boot data".

According to an embodiment of the present invention, the boot database 44 is any suitable computer accessible memory or data storage device configured to store the boot RFID tag identifier and associated boot data for each boot 12 managed by the parking program to allow real-time monitoring and management of the boot 12. When the reader 8 scans or reads the scanned boot 12, the reader 8 transmits the boot data to the BootView system 500. The BootView system 500 communicates with the BootView database 44 to retrieve any desired boot data, such as a lock code or an unlock code, stored therein and communicates this information to the reader 8.

For example, after detecting a parking violation, the PEO may scan the boot 12 using the reader 8, determine the boot tag identifier, and communicate this information to the BootView system 500. Upon receiving the BootTab identifier, the BootView system 500 may query the BootTab identifier in the BootData 44 to retrieve the lock code associated with the BootID. Next, the BootView system 500 transmits the lock code to the reader 8 for use by the PEO in locking the boot 12, thereby completing the execution that disables the vehicle. Those skilled in the art will recognize that a similar process occurs after facilitating the performance of the release of the boot 12, wherein the boot database 44 provides the unlock code to the BootView system 500 for transmission to the reader 8.

According to an embodiment of the present invention, the boot 12 may include a GPS receiver that allows the location of the boot 12 to be determined by a GPS system or other tracking system. The BootView system 500 may be communicatively connected to a GPS system to allow the BootView system 500 to identify the location of each boot 12 of the boot-based enforcement system 1000. Alternatively, the location of the boot 12 can be communicated directly from the boot 12 to the BootView system 500 via a pager signal over a pager network.

According to an embodiment of the present invention, if the boot 12 is not communicatively connected to the BootView system 500 via a pager network (described in detail below), the boot 12 may be configured to periodically cycle through and change its unlock code according to a predefined and predictable algorithm. The algorithm is maintained by the BootView system 500 in a well-known manner, thereby enabling the system to determine the current unlock code without any direct communication with the boot 12.

According to embodiments of the present invention, the BootView system 500 may be communicatively connected to the boots 12 of the boot-based enforcement system 1000 via any suitable communication means, such as via a conventional telephone system 66 (shown in FIG. 5).

According to an embodiment of the present invention, reader 8 includes an RFID interrogator 216. The interrogator 216 communicates with the BootView system 500 or other regulatory agency's traffic scofflaw database via the communication network 28. The RFID interrogator 216 of the reader 8 also communicates with the boot RFID tag 218 of the boot 12, as shown in FIG. 8.

Referring to FIG. 8, the RFID system 214 includes an interrogator 216 and a boot RFID tag 218. Interrogator 216 includes a host controller 220 for processing information received from boot RFID tag 218 via receiver/memory 224 and antenna 222, and from keyboard 250 (or other input device) of reader 8. A separate memory (not shown) may be included in the host controller for receiving and storing keyboard input data separately from tag input data.

In fig. 8, the antenna 222 may also receive data via the communication network 28 (as shown in fig. 5) or from other sources (e.g., the municipality traffic violation computer system 300). According to embodiments of the invention, scofflaw data may also be transmitted directly to the BootView system 500 from the municipality computer system 300 or from the reader 8 communication modem 36 (shown in FIG. 7) via the network 28 using a communication link to the network 28. Network 28 may include the internet, a Local Area Network (LAN), an intranet (not shown), or the like. Alternatively, the BootView system 500 and the municipality computer system 300 may be queried and maintained on one or more of the same computers.

The PEO may receive scofflaw data from the municipality computer system 300 via the modem 36 and network 28 and transmit it to the reader 8, transmit it to the BootView system 500 using an RFID interrogator transmitter (described in detail below), and transmit it to the BootView system 500 via a telephone system, such as a cellular telephone (not shown).

In fig. 8, the RFID system includes an interrogator 214, the interrogator 214 including a host controller 220, the host controller 220 generating an interrogation command signal that is transmitted as a signal 230 through a transmitter 226 and an antenna 228. The controller 220 also transmits scofflaw data and other information entered into the reader memory by the ticket issuer via the antenna 228, the keyboard 250, or a separate antenna, as desired.

Referring to fig. 5 and 7, the data entered into the reader 8 by the PEO 38 via the keyboard 250 as shown in fig. 8 includes data as shown in fig. 6, such as the PEO or municipality's name, the RFID unique tag number, the date, time and location of the summons (which may be selected from memory as a stored code for a city, municipality, etc.), the license number and registration status of the vehicle, the summons number, the violation code, and a scofflaw indicator indicating that the offender is a scofflaw.

According to an embodiment of the present invention, the position may also be determined by a PGS receiver provided in the reader 8. Data such as the location of the reader 8, the installed receiver system, driver's license information, PEO information (which may be entered from the staff's ID card at a distance by the scanner when there is information) may be entered in part via the keyboard 250.

Alternatively, if the reader 8 includes a GPS receiver, the location data may be acquired via a GPS tracking system. The BootView system 500 may provide scofflaw data (i.e., the license plate number, make, model number, and year of the scofflaw vehicle; the name and address of the individual having the outstanding parking citation) which may be automatically entered into the reader 8 via the network 28 via a modem or other communication device, as shown in FIG. 5.

For those readers 8 that do not have a modem or equivalent communication device, communication with the BootView system 500 and/or the municipality computer system 300 may be made manually through the telephone system 66 via a cellular telephone or other telephone or communication device, and then various data manually entered through the keyboard 250 is received from personnel located at the host or municipality location.

Referring to FIG. 8, the boot RFID tag 218 includes a receiving antenna 236 coupled to a controller 240 via a receiver 238, a memory 242 coupled to the controller 240 that extracts corresponding data upon receipt of the signal 230, and a transmitter 244 for transmitting information in the memory 242 via the transmitting antenna 234. The interrogator 216 may optionally transmit an interrogation signal and/or first information to the tag that may contain violation data such as violation code, ticket number, date and time stamp, location, license number, and other data entered into the reader 8. The boot RFID tag 218 transmits an RFID signal 232 containing the second information in response to receiving an interrogation signal from the interrogator 216 antenna 228 to the antenna 236. This second information includes the tag ID and associated violation data that was communicated to interrogator 216 via boot RFID tag 218 antenna 234 to interrogator antenna 222. The signal 232 contains the RFID identification number and also violation data that may be stored in memory 242. Such violation data may be received from the interrogator 216 under the control of the controller 220 and stored in a reader memory (not shown), as would prior scofflaw data downloaded from the BootView system 500 or the municipality computer system 300, manually and/or also electronically. This data is transmitted by the transmitter 226 under the control of the controller 220. The keyboard 250 may include keys for controlling the mode of operation of the controller 220 for issuing the query command signal 230 or the first information violation data transmission signal 230 to be stored in the boot RFID tag 218, as the case may be. The received violation data and RFID unique number are stored in memory 242 under the 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.

To retrieve information from the tag, the host controller 220 generates an interrogation signal 230 based on a signal received from the keyboard 250 or therefrom, wherein the signal 230 is transmitted by the transmitter 226 and antenna 228 as the signal 230 to the receiving antenna 236 of the boot RFID tag 218.

The boot RFID tag 218 may be attached to the boot 112 at any convenient location by any suitable attachment arrangement. Such arrangements may include binding, affixing to a radio transparent housing permanently affixed to the exterior of the latch, affixing in an internal latch cavity but exposed in a radiolucent housing for receiving/transmitting radio signals from/to the interrogator, and so forth. An interrogator may also be included in the BootView system 500 and/or the municipality computer system 300 for communicating with the boot RFID tag 218.

In fig. 5, the boot RFID tag 218 is scanned using the handheld RFID reader 8. The interrogator 216 records in its memory the scanned information, the unique ID of the tag and the date/time stamp. The remaining data of the required data listed above and shown in fig. 6 is entered as described above. If equipped with a communications modem, the reader 8 is used to contact the municipality computer system 300 to retrieve scofflaw data (if present) and input it into the reader memory. The reader 8 is then used to transfer this information stored in the reader 8 to the BootView system 500 and any associated databases.

Any commercially known RFID interrogator 216 and boot RFID tag 218 may be used in the reader 8 and boot 12, which may be modified as described above if necessary. Those skilled in the art will also recognize that known readers 8 may be adapted to include an RFID interrogator 216, such as a TEK guarded human RFID adapter. Preferably, an employee identification card is included for use by the ticket issuing personnel to scan his or her employee number into the reader 8.

The reader 8 uploads the violation data stored in the reader 8 and including the tag ID, etc., to the BootView system 500 using the network 28.

According to an embodiment of the present invention, as shown in FIG. 7, the BootView system 500 includes one or more computers or servers 42, with the one or more computers or servers 42 including a CPU, memory, and one or more databases 44. According to an embodiment of the invention, the municipality computer system 300 may include one or more computers or servers 46 and one or more databases 48. Optionally, the BootView system 500 and/or the municipality system 300 may include or be communicatively coupled to a department of transportation data center 510, the department of transportation data center 510 including scofflaw data stored therein and included in the database 48 of the municipality system 300.

While the BootView system 500 and the municipality computer system 300 are described as computers or servers including high-speed hard drives, fast microprocessors, and large memories, conventional PCs may alternatively be used. Such systems also include a printer (not shown) for printing the necessary data.

The BootView system 500 or the municipality system 300 may operate as a setup system for setting up the readers 8 and tags for use in the boot-based enforcement system 1000 using appropriate data, such as the location code in the reader 8, the setup reader 8, the serial number, and the RFID tag number of the tag. The reader 8 may also have a jack for attaching to the BootView system 500 and the municipality system 300 to download the necessary setup information data, and the jack is implemented using well-known means (e.g., file transfer server protocol). The storage used in the boot-based enforcement system 1000 may be implemented using a variety of data formats known in the art, such as a relational database. The storage memory may be part of the computer system or implemented using a separate device. Access to the stored data may be accomplished using Microsoft Access or other suitable databases. The BootView system 500 and the municipality system 300 servers may be located in the same location as the storage devices of the respective systems. The communication between them is conventional. The network 28 may be wireless or wired and may be any known system including those mentioned above. The printer may be located at the same location as the server or at a different location and coupled by a well-known communication system.

In operation, at step 54a of FIG. 6, the PEO or ticket issuer 38 (shown in FIGS. 5 and 7) issues a parking ticket to a vehicle in violation of parking regulations. The PEO 38 uses the reader 8 to communicate with the municipality computer system database 48 (see FIG. 7) via the network 28 (see FIG. 5) or via the telephone system 400 to see if the vehicle has a previously unprocessed violation, i.e., is a scofflaw, as shown in step 54b of FIG. 6. This information is automatically downloaded to the reader 8 via the network 28 or manually entered if by telephone in fig. 6 to step 56.

According to an embodiment of the invention, the municipality computer system 300 may be maintained by a regulatory entity and include a database 48 of scofflaw data. The municipality computer system 300 may also include a memory card reader/writer (not shown) associated with the database 48 for copying scofflaw data into a memory card associated with the reader/writer. This card is used to transfer scofflaw data from the database 48 to the reader 8. Typically, such cards, referred to as compact flash memory cards, Secure Data (SD) cards, and the like, are relatively small, but have a relatively large storage capacity (e.g., 16, 64, 128, or 256 megabytes of storage capacity). Such card readers are commonly used with digital cameras and other electronic systems, and such cards are readily available. The reader 8 also has such a card reader (not shown) for transferring scofflaw data input onto the card from the database 43 of the municipality computer system 300 (as shown in figure 7) into its memory.

If the vehicle has an outstanding violation associated with it, the PEO 38 enters this data into the reader 8 via the keyboard and through the network 28 (if available) as shown in FIG. 6 and described above. The issuer then attaches the boot 12 to the wheel 16, as shown in step 60 of fig. 6.

According to an embodiment of the present invention, the boot RFID tag 218 is embedded in the boot 12 and includes a unique ID code number that preferably corresponds to the serial number of the boot 12. Meanwhile, the corresponding combination of the tag ID and the boot lock 18 may be stored in the database 44 communicatively connected to the BootView system 500, as shown in FIG. 7. This tag ID is correlated in the database 44 with the corresponding combination code for unlocking the boot 12 associated with the unique tag ID.

In FIG. 6, the issuer then communicates with the tag to upload the tag ID and then communicates with the BootView system 500 at step 58. At this point, the reader is used to upload violation data, including the RFID unique code, the date and time of the violation, scofflaw information listing whether the offender is a scofflaw, and optionally including the total fines accrued for the outstanding violations, the vehicle's license plate, vehicle license plate number, registration status, ticket number, and violation code, optionally also being uploaded via the network 28 or by telephone (if the reader 8 does not have a modem or communication device for communicating with the network 28). This violation data is also communicated to the boot RFID tag 218 via the interrogator 216, as shown in step 60 of FIG. 6.

The boot-based enforcement system 1000 may be used as a resolution module for a parking management system. The boot-based enforcement system 1000 assists the vehicle owner/operator in performing corresponding remedial actions that may include, but are not limited to, the payment of any outstanding fines, the removal of the boot 12 from the vehicle, and/or the return of the boot 12 to a corresponding location.

According to an embodiment of the invention, the resolution module is a computer-based system and/or a human-based system, including a payment processor configured to communicate with a vehicle owner/operator and process payment of a fine associated with a parking violation; a release processor configured to transmit an unlock code to a disable device (e.g., boot 12); and a return processor configured to transmit the return instruction to the user.

To facilitate the execution of the boot removal, the PEO 38 may provide information (i.e., instructions for performing remedial action) to the vehicle owner/operator related to the removal of the boot 12, i.e., contact information (e.g., a telephone number of an entity controlling the BootView system 500). According to embodiments of the present invention, the vehicle owner/operator may contact the entity 62 via a conventional telephone system 66 (shown in fig. 5,6, and 7) or other suitable communication means.

The owner/operator 64 provides a summons number (which may also be a boot serial number) to the entity 62. Using this information, the entity 62 queries its computer system database for the tag ID previously transmitted to it by the PEO 38 (i.e., via the reader 8, in person, or by telephone). These events may occur within minutes or hours of each other, as the boot will typically be attached before the owner/operator returns to the vehicle. Once an entity has a tag ID, it also has associated scofflaw data and fine information.

Alternatively, the entity may contact the municipality database 48 to obtain the fine information, which is more time consuming and does not have the fine information immediately available as desired. The entity can use the BootView system 500 and/or the associated database 44 to correlate scofflaw data with fine data to determine the fine due for any number of unprocessed tickets. Preferably, however, this data is provided by the reader 8 in a manner downloaded directly from the municipality system 300, as shown in FIG. 5, or transmitted by telephone directly to the BootView system 500 from the ticket issuing personnel.

As described above, one exemplary remedial action that is facilitated by the boot-based management system 1000 is the payment of a fine. According to an embodiment of the present invention, the BootView system 500 includes a fee payment processor configured to facilitate payment of the fine by the owner/operator. The payment processor may be communicatively connected to a communication network, which enables the vehicle owner/operator to authorize payment of the fine by providing his or her credit card number or other payment information (e.g., debit card number) over the telephone, at step 70 of FIG. 6. The remedial action may include paying a deposit of the boot 12 to ensure that the owner/operator returns the boot 12 to the entity. When the appropriate remedial action is performed (i.e., payment of the outstanding fine), the entity may provide the owner/operator with the code necessary to unlock the boot 12. The unlock code may be provided by any suitable means of communication, such as by telephone. In addition, other remedial action information may be provided to the owner/operator, such as an address to which the boot 12 is returned after the boot 12 is removed from the vehicle.

According to embodiments of the present invention, release and/or removal of a boot may be facilitated by allowing a user to provide a corresponding payment of a fine using an electronic or card-based payment method. For example, the user may use a conventional gas station-issued card (e.g., Exxon/Mobile Speedpass)^TMCard) to pay a fine to release the boot.

In step 72, when the boot 12 is returned to the corresponding entity, organization, processor (dealer), etc., the boot tag is read to verify that the boot information associated with the returned boot and the owner/operator data received from the PEO matches. If there is a match, the deposit is returned to the owner/operator. Advantageously, the entity resolution process (i.e., release of the boot) may occur in a relatively short period of time. Furthermore, the return latching may be performed at the convenience of the owner/operator.

If the owner/operator chooses not to pay the fine and does not contact the entity, the entity may send a mortgage notification to the municipality issuing the ticket. The term "municipality" shall include any regulatory body that enacts parking procedures.

According to an embodiment of the invention, in step 74, the municipality may contact a towing service via telephone to tow the offending vehicle into the parking lot. In step 76, the trailer operator needs to remove the boot in order to tow the vehicle. In step 74, the trailer operator communicates (e.g., via telephone) with the entity system 32 to obtain the necessary combination to unlock the boot. According to an embodiment of the present invention, the trailer operator may use the reader 8 to obtain the boot tag ID and associated violation data and communicate this information to the entity or municipality via the network 28 or by telephone in order to obtain the unlocked combination of the boot. The trailer operator then removes the boot and tows the vehicle to the garage at step 76 and returns the boot at step 72.

According to an embodiment of the present invention, the boot release code may be a scrolling number that prevents the boot release code from being issued at will. That is, these codes may be assigned to each boot as random numbers. When so assigned, the numbers are entered into the corresponding host and municipality databases in which control of the boot is initially maintained. If the boots are distributed by the municipality, it assigns a release code to each boot, records the release code and boot tag ID, and transmits these codes to the entity corresponding to the unique tag ID associated with each boot. The lock preferably has a master basic key for releasing the lock in case the release code technically fails.

The reader 8 may include a software program configured to read scofflaw data stored in a database of a municipality computer system. The reader 8 may include a connector for mating with a socket where such data may be transmitted using control circuitry at the municipality computer system 300. In addition, the municipality system 300 may also include an alternative system for reading scofflaw data directly to the boot tag without the need for the reader 8 to read. This direct input of data to the tag memory at the municipality computer system eliminates possible errors in the communication system transmitting such data to the tag via the reader.

One skilled in the art will recognize that the disclosed embodiments are provided by way of example and that modifications may be made to the disclosed system. For example, the reader 8 may include a digital camera, and the reader 8 may transmit its data to the BootView system 500 and/or the municipality computer system 300 as well as to the BootView RFID tag 218. The disclosed embodiments are provided by way of example and not limitation. It is intended that the invention be defined by the appended claims rather than by the disclosed embodiments.

According to embodiments of the present invention, two-way communication between the boot 12 and the entity host computer system 62 may be accomplished using an alphanumeric pager network. Using the pager network, the entity host computer system 62 remotely unlocks the boot 12 by transmitting a corresponding unlock code to the boot 12.

According to embodiments of the present invention, a pager network may be used to transfer the new unlock code from the boot 12 to the entity host computer system 62. According to this embodiment, the boot 12 may be equipped with an unlock code generator that periodically generates an unlock code upon successful locking. The boot 12 transmits the unlock code to the entity host computer system 62 via the pager network. If the transmission is unsuccessful, the code generator detects the transmission failure and by default employs a fail safe (failsafe) unlocking mechanism, which may be a manual override (i.e., unlocked with a key) or a default unlocking code. Alternatively, when the boot 12 is successfully locked, the BootView system 500 may generate an unlock code and transmit the code to the boot 12.

In accordance with an embodiment of the present invention, the boot-based enforcement system 1000 may include one or more boot docking stations configured to dock one or more boots. The BootConnection station may be communicatively connected to the BootView system 500 and the PermitView system 1.

The bootie docking station may be configured to perform one or more of the following actions: 1) charging the power supply of the latch 12; 2) communicating the usage and diagnostic data to the BootView system 500; 3) reprogramming the firmware stored in the boot 12; 4) communicating the software update from the BootView system 500 to the boot 12; 5) updating or changing the lock and unlock codes; and 6) printing a boot return/payment receipt.

The boot docking station may be communicatively connected to the boot via a suitable communication and connection means, such as a USB connection, Firewire, ethernet connection, wireless connection (e.g., bluetooth or WiFi connection), or the like. Alternatively, the latch docking station may use a power-over-ethenret (power-over-ethernet) connection to recharge the power source (e.g., battery) of the latch 12. The latched docking station can be protected from external factors such as weather, vandalism, and cracking.

According to one embodiment of the invention, the one or more "return" positions may comprise a drawer type latch docking station adapted to receive and dock a plurality of latches 12.

According to embodiments of the present invention, existing and future licensees can access the PermitView System 1 via the licensee/applicant portal of the user interface 20. The user interface 20 may include an authentication or login screen in which the existing licensee is prompted to provide login information (e.g., a username and password). Those skilled in the art will recognize that any suitable authentication system or method may be used in accordance with the present invention, such as asp. The licensee may access information about his or her account and perform a number of account-related tasks, including but not limited to the following: 1) add/edit/delete/update authorized vehicle data; 2) add/edit/delete/update license data; 3) add/edit/delete/update licensee data; 4) paying bills, renewal and/or tickets; and 5) checking account information containing previously issued alerts/notifications and/or tickets; and so on.

According to an embodiment of the present invention, a person may access the PermitView System 1 to submit a new license application. The new license application may include, but is not limited to, the license holder data, the vehicle or vehicles associated with the license, the requested scope of authority, the payment method, and/or the proof required to issue the license. The proof required to obtain the license may include, but is not limited to, proof of residence or qualification of residential parking privileges (e.g., utility bill, owner/operator's license, property tax bill, etc.), proof of employment of employee parking privileges, proof of admission of student parking privileges, proof of personal identification (e.g., owner/operator license, social security card, etc.). This information may be electronically scanned and transmitted to the PermitView System 1 in any suitable file format, such as Portable Document Format (PDF), according to one embodiment of the present invention.

Those skilled in the art will recognize that an inventory of available and/or issued licenses may be managed, stored, and maintained by the license viewing system 1 in a database, such as the license database 40. Alternatively, the inventory may be stored in a separate database (referred to as inventory database 7B in fig. 1) and managed and maintained by the parking program manager via parking manager computer 7. According to this embodiment, a new application may be received by the PermitView System 1 and transmitted to the parking manager computer 7 for review and evaluation. :

according to an embodiment of the present invention, the PermitView administrator may access the PermitView System 1 via the PermitView administrator portal of the user interface 20. Preferably, an increased or relatively high level of authentication is required for access via the administrator portal due to the type and amount of access the administrator has to the PermitView System 1.

According to embodiments of the present invention, one or more administrators may access the PermitView System 1 to perform a number of functions, including but not limited to: 1) setting and supervising a new parking program; 2) providing online support; 3) managing a user group; 4) setting parking permission data according to parameters of a parking program; 5) managing a license inventory; 6) processing the new license application; 7) managing alerts/notifications and summons issuance; 8) defining and providing reports for user groups; and 9) manage billing and invoicing processes.

According to an embodiment of the present invention, the parking program manager may access the PermitView System 1 via the parking program manager portal of the user interface 20. The parking program manager requires a unique level and type of access to the PermitView System 1 as compared to the other user groups. According to embodiments of the present invention, one or more administrators may access the PermitView System 1 to perform a number of functions, including but not limited to: 1) running a plurality of reports associated with the parking program; 2) setting and supervising a new parking program; 3) updating/editing existing license holder data; 4) managing a license inventory; and 5) tracking law enforcement action information.

FIG. 9 illustrates the parking management system for managing a boot-based and permit-based parking environment described in detail above, including the BootView system 500, the PermitView system 1, a plurality of boots 12 (each boot having a boot RFID tag), a plurality of permits (each permit having an RFID tag), and a plurality of readers 8 for transmitting and reading the RFID tags associated with the boots 12 and permits 11.

According to embodiments of the present invention, the PermitView system 1 may be used to manage a multi-space "pay-to-park" program and/or environment.

Conventional pay parking programs generally allow an individual to pay for parking in a particular parking space, area or zone for a desired allotted time. Typically, an individual pays at the meter by cash, credit card or debit card via a "multi-space" or "pay and display" parking meter or machine. Alternatively, the individual may pay via telephone communication to an established "pay by phone" or "park by phone" system. Typically, after payment, the individual prints a "receipt" or proof of the purchase and returns to his or her vehicle to affix the receipt to the vehicle, typically in a location viewable from outside the vehicle, such as on the dashboard or windshield of the vehicle.

To execute the program according to conventional systems, information relating to legally parked vehicles (i.e., information identifying those vehicles that have paid for and for which the time period has not expired) is collected into a "legally parked vehicle list," which is provided to the PEO via wireless communication to the PEO's handheld ticket writing device or, more generally, via a "report," which the PEO can access and print via the parking meter by entering a special code into the meter.

Next, the PEO compares the list of legitimate parking vehicles to the cars physically parked in the given area by visual inspection and takes appropriate enforcement action (e.g., issuing a ticket) for the vehicles parked in the parking space that are not listed in the report.

Moreover, conventional "multi-space" parking meter systems and programs typically require the motorist to walk to a multi-space parking meter associated with a parking lot (typically one meter per lot) in order to purchase parking time by cash, credit or debit card. Parking tiles using "multi-space" meters require each parking space to be visually marked with an identifier (e.g., a number and/or letter designation) by printing the identifier on the roadway, on the ground, or on a sidewalk at or near each individual parking space in a manner that clearly identifies each parking space in the tile. Likewise, the motorist needs to remember the identifier and accurately enter the identifier into the "multiple space" parking meter in order to purchase the time for that particular parking space.

According to an embodiment of the present invention, an individual may perform payment for a parking space in a paid parking environment using a payment means, such as an account number or a smart card associated with his or her license 11. This allows an individual to purchase time from a multi-space meter at the meter or through a telephone payment system, in the case of a "multi-space" meter, the individual may pay without having to pay attention to or remember the parking space identifier for the space in which he or she is parked because of the association of the payment method with the license 11 associated with the vehicle (i.e., associated with and attached to or displayed by the vehicle in the PermitView System 1). According to an embodiment of the present invention, an individual may process payment through a telephone parking system, having information related to the transaction processed by the PermitView System 1, and associated with his or her permit 11, and communicated by the PermitView System 1 to the respective PEO, to avoid interaction with the meter.

In accordance with an embodiment of the present invention, in the case of a "pay and display" meter, the individual need not return to his or her vehicle to place a receipt on the vehicle's windshield. This makes the individual more convenient, while providing a law enforcement method for law enforcement agencies.

According to embodiments of the present invention, the PermitView system facilitates the implementation of pay-and-show, pay-by-phone parking and pay-by-phone parking environments. Specifically, the legal parking list may be provided directly to the reader 8 by the PermitView System 1. Alternatively, the PermitView system 1 may provide a list of legitimate parking to a multi-space meter or pay and display meter communicatively connected to the reader 8 via, for example, a wireless connection. Advantageously, the processing of the legal parking list according to embodiments of the present invention eliminates the need for the PEO to interact with a meter to generate and retrieve a report, and further eliminates the need to visually inspect the absence of space in the report to determine if law enforcement action is required. Rather, the reader 8 may receive a list of legitimate parking from the PermitView System 1, scan the permit 11 for a parked vehicle in the environment, capture tag data associated with the permit 11, and compare the tag data to the list of legitimate parking to determine if law enforcement action is required.

According to embodiments of the present invention, payment for space may be performed by an individual using an account number or smart card associated with his or her license 11. When paid, data relating to the pay parking transaction (referred to as "pay parking data") is associated with his or her license 11 and a unique RFID tag identifier in the PermitView System 1. The paid parking data may include, but is not limited to, time and date of purchase, amount of time of parking purchased, authorization to automatically top up the account to extend parking time, information identifying the license 11 associated with the parked vehicle, and a "virtual timer" (i.e., a virtual clock that runs from the payment authorization time for the time period that the individual selects and pays).

The paid parking data is associated with the permit in the PermitView System 1, and the PermitView System 1 prepares a list of legitimate parking and provides this list to the reader 8 for reference by the PEO. The PEO can scan the permit 11 in a paid parking environment using the reader 8, and the reader 8 automatically checks the tag data associated with the scanned permit 11 against the list of legitimate parking received from the PermitView System 1, thereby obviating the need for the PEO to perform a visual check to detect a parking violation.

According to an embodiment of the present invention, the PermitView System 1 may determine that an individual is on a list of scofflaw when the individual attempts to process payment for a parking space in a paid parking environment. According to embodiments of the present invention, the list of scofflaw may be provided by one or more sources, such as municipalities or other governmental entities. The list of scofflaw may contain information identifying each individual who has an outstanding parking violation and has been designated as a "prohibited state," meaning that the individual is prohibited from parking in one or more zones governed by the parking program managed by the PermitView System 1. Likewise, when there is a prohibited-state individual or an associated vehicle attempting to process payment for a paid parking space, the PermitView System 1 may notify the individual of his or her prohibited state and inform the individual to prohibit parking because the outstanding violations were not resolved. In addition, the PermitView system 1 may prompt the individual to pay any outstanding fees or fines in order to override the prohibited status. Those skilled in the art will recognize that communication between the PermitView System 1 and the individual may occur via any suitable communication means, such as by telephone and/or via a multi-space meter or similar interactive display provided in a pay parking environment.

It is to be understood that the exemplary embodiments are merely illustrative of the present invention and that many variations of the above-described embodiments may be devised by those skilled in the art without departing from the scope of the invention. Accordingly, all such modifications are intended to be included within the scope of the appended claims and their equivalents.

Claims

1. A parking management system comprising:

a detection module for detecting a violation by a scofflaw, the detection module receiving data from a remote computer system and capturing a unique identifier associated with a parked vehicle, the detection module analyzing the data and the unique identifier to determine whether a violation by a scofflaw is occurring and issuing at least one enforcement action based on the violation by the scofflaw;

a law enforcement module for performing the at least one law enforcement action, the at least one law enforcement action including disabling the parked vehicle via the placement of a lock striker on a vehicle tire with a striker release code; and

a resolution module for facilitating performance of the remedial action, the resolution module including a payment module for receiving payment of a fine associated with the at least one enforcement action by the vehicle operator, a release module for communicating a boot release code to the operator upon payment of the fine to cause the parked vehicle to be released from being unable to travel, and a return module for communicating an instruction to return to the locked boot to the operator,

wherein the fine associated with the at least one law enforcement action further comprises a deposit of the returnable operator upon successful removal of the locking boot by the operator and return thereof to the parking management system.

2. The system of claim 1, wherein the locking boot includes a boot tag identifier.

3. The system of claim 2, wherein the parking management system includes a database for storing at least one of the boot tag identifier, a lock code, and an unlock code for the lock boot.

4. The system of claim 1, wherein the locking boot includes a Global Positioning System (GPS) receiver.

5. The system of claim 4, wherein the parking management system is configured to track the location of the boot using the GPS receiver.

6. The system of claim 1 wherein the parking management system is communicatively connected to the boot via a pager network.

7. The system of claim 6 wherein the parking management system unlocks the boot remotely by transmitting an unlock code to the boot via the pager network.

8. The system of claim 1, wherein the unique identifier is a license plate number of a vehicle.

9. A method for managing a parking program, the method comprising the steps of:

receiving data from a remote computer system and electronically reading a unique identifier associated with the parked vehicle;

analyzing the data and the unique identifier to determine whether an offending violation is occurring;

issuing at least one enforcement action in accordance with the scofflaw violation;

performing the at least one enforcement action, the at least one enforcement action including disabling the parked vehicle from traveling via the placement of a lock striker on a vehicle tire utilizing a striker release code; and

facilitating performance of a remedial action, at least one remedial action including payment of a fine by the vehicle operator in association with the at least one enforcement action, communication of a boot release code to the operator upon payment of the fine to cause the parked vehicle to be released from being unable to travel, and communication of an instruction to return to locking the boot to the operator by the return module,

10. The method of claim 9, wherein the unique identifier is a license plate number of a vehicle.

11. The method of claim 9, wherein the locking boot includes a boot RFID tag storing a boot tag identifier.

12. The method of claim 11, wherein the boot tag identifier is associated with a code for unlocking the boot.

13. The method of claim 9, further comprising:

parked vehicle data is received from a mobile device.