Parking environment management system and method

ES 2 585 342 T3

DESCRIPTION

Parking environment management system and method

Field of the invention

The present invention relates generally to the application of parking regulations, and, more specifically, to a system and method for administering, managing, and monitoring parking programs.

Background of the invention

Both public and private administration parking programs continually face the seemingly insoluble problem of providing an increasing number of vehicles with parking services relative to an area having a limited number of parking spaces. Specifically, there is a growing effort to manage the problem in residential communities, where cities large and small are trying to provide local residents with a parking placard. This effort generally involves the use of parking programs designed to enforce a set of rules and regulations that control parking privileges in a particular location or area.

Traditional parking programs require enforcement of administrative parking laws and regulations by multiple enforcement agents, called Parking Enforcement Officers (PEOs). PEOs monitor an area and detect parking violations, typically by visual inspection of the offending vehicles (for example, identification of an illegally parked vehicle) or surrounding area (for example, observing a vehicle parked in front of a “No” sign park ”, the parking meter time expired, etc).

Other parking programs use authorizations to regulate and restrict parking privileges in an attempt to assure residents that local residents can find a place to park their vehicles on a street or on a lot. The objective of such authorization-based parking programs is to promote that individuals obtain a parking privilege authorization, or, alternatively, to move vehicles that do not have authorization, to a metered, time-limited parking lot or garage.

However, parking programs are very difficult and expensive to implement and manage. Inefficiencies in the administration of these parking programs and a lack of enforcement are rampant problems in today's parking programs, leading to a significant dilution of anticipated benefits.

For example, a small municipality that institutes a permit-based parking program may be faced with the task of issuing 20,000 to 500,000 permits per year, requiring a complete retrofit of the municipality's existing parking enforcement plan.

Although the issuance of permits contributes to the creation of parking regulations, the use of conventional permits has many disadvantages. Conventional clearances are typically expressed in the form of a sticker that is affixed to a vehicle window or a hang tag that hangs inside the vehicle (ie, from the rear view mirror). However, it is often difficult to determine authorization based on a visual inspection of the vehicle, due to various factors including the presence of tinted windows and / or the layout of the vehicle (eg, sloped parking). This places a significant burden on the person responsible for inspecting the vehicle to determine if the vehicle is legally parked, called a Parking Enforcement Officer (PEO), who must locate and read the authorization by visually inspecting the vehicle.

Furthermore, conventional authorizations are frequently stolen or “resold” (that is, sold by the authorized authorization holder to an unauthorized person). Without efficient means to track authorizations granted under a parking program, such misuse is extremely difficult to detect and stop.

In order to enforce vehicle parking laws, parking programs typically issue a ticket or request and place the request on the vehicle. In general, the owner and / or operator of the vehicle reviews the requirement, and has to find out what the amount of the fine is and the method of paying it. The owner / operator then goes through the steps of paying the fine and / or going to court to challenge the requirement. The application of the payment of fines is fortuitous because in many cases the owner of the vehicle does not pay the fine and accumulates requirements and fines. They can substantially increase the fines imposed on repeat violators who are called violators, who ignore such requirements.

WO2006 / 026515 describes a method and apparatus for monitoring and regulating street parking using RFID technology. Vehicle operators buy parking tickets including RFID tags and put them on their vehicles while they are parked. RFID tags are scanned, and a

ES 2 585 342 T3 central server if the RFID tag is missing or expired. The central server then notifies the application of the parking rules by sending a Parking Enforcement Officer to the place of the parked vehicle.

A conventional method of securing the payment of fines is to immobilize the vehicle by putting a clamp on the vehicle wheel. A lock is a device that is placed on the vehicle wheel to make it impossible to operate the vehicle since the wheel can no longer turn on the road due to the presence of the lock. However, such traps are typically cumbersome and heavy. For example, such traps are described in Japanese Patent JP 58076348, United Kingdom Design Patents 3008370 and 3007353, and United States 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.

Clamp systems of the type in use, while not popular with drivers, have been more widely accepted. Thus, parking enforcement personnel put the oversized and cumbersome trap on a vehicle wheel, immobilizing the vehicle. The offender returns to the vehicle and cannot use the vehicle. The offender is instructed by a sticker on the window to call the appropriate entity (eg, a law enforcement agency) for instructions on how to release and remove the stocks. The offender is instructed during the call to go to the police station, court or administrator, without his vehicle, to a pay position. The offender has to pay the fine for this infraction and all other pending infractions, if any. In this regard, trap systems catch violators who have numerous outstanding parking violations. More specifically, once a trap has been placed on an offender's vehicle, authorities can maintain control of the vehicle until all pending violations against the vehicle owner or operator have been paid.

It is clear that the use of the wheel lock with stocks is inconvenient for the offender who must try to obtain an alternative transport from wherever he has parked to the payment center, which could be at a certain distance and to whose center there is no readily available transport . Once the offender's account has been charged, he must return to his vehicle using another means of transport, while waiting for a parking enforcement person who travels in parallel to the offender who returns to his vehicle to remove the stocks. Such a person may or may not get to the offender's vehicle on time, which upsets the offender. This process can take hours or even days, spending a portion of the fine received by the issuing agency of requirement in the man-hours spent preparing the extraction of the stocks and the time necessary to remove the stocks and also leaving a cranky citizen.

Furthermore, it is costly for both the driver and the agency responsible for traffic law enforcement. In some cases, the stocks are used instead of towing the vehicle on private property to secure payment of parking violation fines. The tow truck operator cannot enter the private parking place for hours to settle the claim.

WO2004 / 034294 describes a system in which, when a vehicle user discovers that his vehicle has been immobilized through the use of an immobilizer device placed on a vehicle wheel, the user operates a terminal to make a payment and enters into the terminal an identifier of the immobilizer device. When the payment is validated, the user receives an unlock code to unlock the immobilizer device.

Therefore, a method and a system is needed to efficiently and effectively implement, manage, administer, monitor and execute a parking program.

Summary of the invention

A first aspect of the present invention provides a parking management system as defined in claim 1.

A second aspect of the present invention provides a method for resolving a violation, which method is defined in claim 9.

A third aspect of the present invention provides a resolution module for resolving a violation, the resolution module being that defined in claim 13.

According to an embodiment of the present invention, the detection, application and resolution modules of the parking management system can include an authorization management system, one or more RFID readers, and several parking authorizations each having a single tag. RFID and tag identifier (for example, a tag number including a string of alphanumeric characters). The authorization management system is configured to manage an authorization-based parking program, as described in detail in related US Patent Application Serial No. 11 / 281,841.

According to an embodiment of the present invention, the application component and the resolution components of the parking management system may include a trap-based application system including a

ES 2 585 342 T3 plurality of vehicle traps each having a unique RFID trap tag and trap tag identifier (for example, a tag number including a series of alphanumeric characters) readable by the one or more RFID readers and a stocks management system, as described in detail in related US Patent Application Serial No. 1 I / I 22,953.

According to an embodiment of the invention, the authorization management system, called the "PermitView" system, performs the efficient administration, management and implementation of the detection, application and resolution modules of a parking program based on authorizations (here called the "Parking program") that controls a parking environment based on authorizations.

According to one embodiment of the present invention, each authorization included in the parking program is assigned a unique RFID tag identifier (e.g., a tag number), which is stored on an RFID tag attached to or embedded in the authorization ( for example, in the form of an RFID chip). The RFID tag identifier is associated with information or data specifically related to said parking authorization, including, but not limited to, authorized vehicle data, authorization holder data, and parking privilege data (collectively referred to as the "parking authorization data"). hashtag").

According to one 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 authorization held by the parking program, to allow continuous management throughout the duration of the parking. authorization.

According to an embodiment of the present invention, the one or more parking zones of the authorization-based parking environment that are regulated under the parking program, here called the "zones", are monitored by one or more RFID readers, which can be a handheld device operated by a Parking Enforcement Officer (PEO) or a stationary reader. The RFID reader scans the parked vehicle, reads the RFID tag, and captures the RFID tag identifier. To determine if the vehicle is parked with authorization, the RFBD reader accesses the computer-accessible memory of the PermitView system and queries the tag data associated with the captured RFED tag identifier.

According to an embodiment of the present invention, the PermitView system makes an efficient determination of whether or not the scanned vehicle is parked within the privileges associated with authorization. In case the vehicle is parked outside of the parking privileges granted to said authorization, an appropriate enforcement action is executed, and it is registered by the PermitView system.

According to an embodiment of the present invention, the authorized vehicle data (eg color, make, model, year, license plate number, etc.) associated with the scanned RFID identifier is communicated to the RFID reader, for comparison with the data. of parked vehicle, to determine if the authorization is being used by an authorized vehicle, that is, a vehicle associated with the authorization.

According to an embodiment of the present invention, the PermitView system can be accessed, through a user interface, by several different users, such as authorization holders, authorization requesters, parking program managers, PermitView administrators, and the one or more readers. .

According to an embodiment of the present invention, one or more docking stations, adapted to dock one or more handheld RFID readers, can access the PermitView system. The docking stations communicate with the PermitView system to synchronize the data stored in the system and the data stored in the RFID reader. Additionally, one or more stationary RFID readers can connect to the system for data synchronization.

According to an embodiment of the present invention, the new concession authorizations are registered in the PermitView system, which acts as a clearinghouse for all authorizations managed under the parking program. The PermitView system then tracks and monitors the use of each authorization, for the duration of the authorization.

The PermitView system effectively enforces parking regulations, thereby creating a secure and structured parking environment that results in realization of benefits for the authorization holders and the parking program. According to one embodiment of the present invention, the trap-based delivery system performs immobilization of an offending vehicle using a vehicle trap (ie, the enforcement action). The stocks-based application system includes a stocks management system, called the "BootView" system, that performs the administration and management of stocks. In addition, the BootView system facilitates the operation of the release and return of the traps after the completion of the appropriate remedial action (eg payment of a fine).

Brief description of the drawings

ES 2 585 342 T3

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

Figure 1 is an illustration of a permit-based parking environment including a permit management system, in accordance with one embodiment of the present invention.

Figure 2 illustrates an exemplary process for managing an authorization-based parking environment, in accordance with one embodiment of the present invention.

Figure 3 illustrates an exemplary process performed by an authorization management system, in accordance with one embodiment of the present invention.

Figure 4 illustrates steps according to an exemplary privilege analysis, in accordance with one embodiment of the present invention.

Figure 5 is a schematic diagram depicting a trap-based application system according to one embodiment of the present invention.

Figure 6 is a diagrammatic illustration of a trap-based application system, according to one embodiment of the present invention.

Figure 7 is an illustration of a trap-based application system, according to one embodiment of the present invention.

Figure 8 is a schematic block diagram of an RFID interrogation tag and reader-transmitter system, in accordance with one embodiment of the present invention.

Figure 9 is an illustration of a parking management system, according to one embodiment of the present invention.

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

Detailed description of the invention

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., the identification of an illegally parked vehicle or a vehicle of interest), an execution module for executing an appropriate enforcement action, and a module resolution to facilitate the completion of a remedial action by the vehicle owner / operator.

According to one embodiment of the present invention, the detection module of the parking management system identifies a parking violation or vehicle of interest, collectively referred to as a "violation" by visual inspection of a vehicle or its surroundings (ie, a parking meter). by an individual (i.e. a Parking Enforcement Officer) and / or scanning an RFID tag associated with the vehicle to determine the parking privileges assigned to that vehicle, as described in detail below.

Once the violation is detected, the application module of the parking management system carries out the execution of one or more application actions. The "enforcement action" may include one or more of the following: 1) the issuance of a requirement or ticket, which may have an associated fine or sanction; and / or 2) vehicle locking (eg vehicle immobilization, vehicle removal, etc.).

After the execution of the enforcement action, the resolution module of the parking management system facilitates the performance of a remedial measure, by the vehicle owner / operator, corresponding to the enforcement action. For example, if a fine is issued and the vehicle is immobilized (the enforcement action), then the system assists the vehicle owner / operator in paying the fine, releasing the immobilization device (for example, a vehicle), and the return of the immobilization device (remedial measures).

According to an embodiment of the present invention, the resolution module is a human and / or computer based system including a payment processor configured to communicate with a user and process the payment of a fine associated with a parking violation, a processor of release configured to transmit an unlock code to an immobilization device used to enforce the parking violation, and a return processor configured to communicate return instructions to the user.

The parking management system that manages all the complete detection, application and resolution processes can include one or more computer-based systems and / or human-based systems.

ES 2 585 342 T3

According to an embodiment of the present invention, the parking environment managed by the parking management system of the present invention may include one or more parking zones or "zones", which are controlled by a parking program. The “parking program” includes the set of rules and regulations that control parking in the areas of the parking environment.

In accordance with one embodiment of the present invention, the detection module may include one or more parking enforcement officers who identify parking violations by visual inspection of the vehicle (i.e., an inspection of the license plate and / or registration sticker). vehicle) and / or the vehicle environment (for example, a parking meter, curb markings, signs relating to parking, etc.). Based on the visual inspection, the Parking Enforcement Officer can determine that the vehicle is currently in violation of the parking regulations in force or, alternatively, by running a license plate number check, determine that one or more multiple parking complaints against the vehicle and / or the vehicle owner (i.e. an offender).

According to an embodiment of the present invention, the parking management system can be used to manage a parking environment based on authorizations. The detection of a parking violation in the authorization-based parking environment can be performed using an authorization management system (here called the PermitView 1 system), one or more RFID readers 8 to scan vehicles located in one or more zones, and one or more parking authorizations 11 (as represented in figure 1) each including a unique RFID tag (called in figure 1 RFID TAG_1, RFID TAG_2, ... and RFID TAG_N, for a parking program that has an "N" number of authorizations). Those skilled in the art will appreciate that although the present invention is described including RFID reader technology, other reading devices and systems may be used in accordance with the invention.

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

Those skilled in the art will appreciate that the components of the PermitView 1 system may be located on a single computer, as depicted in FIG. 1, or on more than one communication connected computer. The term "connected with communication" is intended to include any type of connection, both wired and wireless, in which data can be communicated. The term "connected with communication" is intended to include a connection between devices and / or programs within a single computer or between devices and / or programs on separate computers. Those skilled in the art will appreciate that at least a portion of the PermitView 1 system can include human-based components. For example, the user interface 20 may be a call center or conventional office where persons (eg, authorization holders or applicants) can access the PermitView system 1 via telephone or in-person communication 5B, as depicted in Fig. Figure 1.

The PermitView 1 system can be a computer-executable application or program accessible by a number of user groups, where the characteristics of the user group dictate the level, amount, and type of access allowable to the PermitView 1 system. According to one embodiment of the present invention, the following primary user groups are defined: authorization holders and authorization requesters, parking program managers, PermitView administrators, and RFID readers. Each group of users accesses the PermitView system 1 through an appropriate user interface 20, which can be specially adapted and / or configured based on the specific group of users, as represented in figure 1. User interface 20 provides user group specific access to the PermitView 1 system, where the level of access is customized specifically for each user group.

The user group 'authorization holder / applicant' includes all persons who have or wish to have one or more authorizations related to one or more supervised zones under the parking program. As depicted in Figure 1, the authorization holder / requestor user group can access the PermitView 1 system through a user interface holder / authorization requestor portal 20 using a computer, here called a holder / requestor computer. authorization 5. Those skilled in the art will appreciate that the authorization holder / requester user group can also access the PermitView system 1 by other means, such as, for example, by telephone or in-person communication 5B, as depicted in Figure 1.

The PermitView administrator user group includes all persons authorized to maintain, manage, monitor, supervise, or otherwise control the PermitView 1 system. As shown in Figure 1, the PermitView administrator user group accesses the PermitView 1 system. through an administrator portal

PermitView of the user interface 20 using a computer, here called an administrator computer

ES 2 585 342 T3

PermitView 6.

The user group 'parking program manager' includes all persons authorized to maintain, manage, monitor, supervise or otherwise control the authorization-based parking program that is managed by the PermitView 1 system. As depicted in Figure 1, the parking program manager user group accesses the PermitView system 1 through a parking manager portal of user interface 20 using a computer, here called a parking manager computer 7. Those skilled in the art will appreciate that the parking program manager user group can access a 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 that it contains, in one or more zones. As depicted in Figure 1, the reader user group accesses the PermitView system 1 through a reader portal of the user interface 20 using a reader connected with communication 8.

According to one embodiment of the present invention, the authorization holder computer 5, the PermitView administrator computer 6, the authorization manager computer 7, and the reader 8 may include a web browser 5A, 6A, 7A, 8A, respectively. , which provides a portal to one or more web-based networks, such as, for example, Network / Internet 100. Each web browser 5A, 6A, 7A, 8A is communicatively connected to the PermitView system 1 via Network / Internet 100. Those skilled in the art will appreciate that any web browser is suitable for use in the present invention, including, but not limited to, FireFox, Microsoft® Internet Explorer, Netscape, Opera, WebTV®, and Mozilla ™.

According to a preferred embodiment, the reader 8 can be any suitable device or computer capable of reading an RFID tag. The reader 8 can be a handheld device operated by a PEO, or a stationary device. Those skilled in the art will appreciate that readers 8 can be passive, active, or semi-active. The reader 8 may include one or more software applications or programs (for example, RFID / barcode scanning and authorization evaluation software such as PermitFinder, report writing software, etc.) configured to perform the functions performed by the readers 8, including, but not limited to, data capture, data storage, and scan activity.

The reader 8 may be configured to access data stored on a computer or in a database using any suitable program or language, such as, for example, Microsoft Access, MsSQL, software-based server-side database system. Structured open source query, commercially available from, for example, Microsoft Corporation, plain text files (.txt), and / or other database technologies. The plain text file is key to extracting data from multiple sources and for use with a universal readable format. Readers 8 suitable for use with the present invention include, but are not limited to, the Symbol MC9000-GRFID device. Those skilled in the art will appreciate that parking authorization can include any readable device or medium, other than an RFID tag. Accordingly, the reader 8 can be any device capable of reading the readable device or medium that is associated with the parking authorization.

According to an embodiment of the present invention, one or more handheld docking stations 9, adapted for the docking of one or more handheld readers 8, can be connected with communication to the PermitView system 1 via the Network / Internet 100. It can be docked a handheld reader 8 on the handheld docking station 9 to synchronize the data stored in the PermitView system 1 with the data stored in the handheld reader 8.

According to one embodiment of the present invention, the handheld docking station 9 can communicate with the PermitView system 1 via the synchronization module 60. The synchronization module 60 can be a computer-executable module capable of downloading and / or uploading data to and from the one or more readers 8 docked in the docking station 9. Specifically, the synchronization module 60 can download / upload data including, but not limited to, valid authorization lists, software updates, PEO identification information, a list of scans performed by the PEO, a list of scan results including any enforcement action taken (for example, complaints filed; specific details regarding freezes, etc.), announcements and alerts for PEOs, a list of malfunction indications (described in more detail with respect to figure 2), etc. An exemplary synchronization module 60 suitable for use in the present invention is the SQL 2000 / CE synchronization tool.

According to one embodiment of the present invention, the data stored in the handheld reader 8 and in the PermitView system 1 can be synchronized in real time via a wireless connection between the reader 8 and the PermitView system 1.

In accordance with one embodiment of the present invention, the PermitView system 1 includes a report generator 30. The report generator 30 is a computer-executable module configured to generate reports relating to the

ES 2 585 342 T3 parking program. Those skilled in the art will appreciate that the report generator 30 can generate various reports, said reports including any information related to the parking schedule maintained by the PermitView 1 system.

Exemplary reports that may be generated include, but are not limited to, reports relating to: 1) financial information (eg, receipts from the parking program, 2) scan results; 3) specific PEO reports including information on PEO actions (eg number of scans, number of notices / communications, number of complaints, number of times the PEO was unable to take any action, etc); 4) authorization holder account information; 5) inventory of authorizations; 6) information on enforcement actions; 7) parked vehicle data; and 8) tag data.

User groups (authorization holders / applicants, parking program managers, readers, and / or PermitView administrators) can 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 appropriate information from the communication-connected computer-accessible memory, referred to the authorization database 50, generates the report, and provides the report to the requesting user group. , via user interface 20 or synchronization module 60. The term "computer-accessible memory" is intended to include any computer-accessible database or data storage device, whether volatile or non-volatile, electronic, optical, or otherwise, including, but not limited to, floppy disks, hard disks, CD-ROMs, DVDs, flash memories, ROMs and RAMs.

Those skilled in the art will appreciate that the report generator 30 may be configured to automatically run reports at one or more specific time intervals (eg, hourly, daily, weekly, monthly, yearly, etc.) according to a predetermined and customizable schedule. . For example, the report generator 30 can run a daily report detailing each violation that occurred in a specific area during the previous 24-hour period, and automatically distribute said report to the parking manager computer program 7 and / or the associated reader 8 with that area.

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

According to one embodiment of the present invention, when the handheld docking station 9 detects the coupling of a reader 8, it can automatically send a report request to the synchronization module 60. The synchronization module 60 can then send the request to the generator of 30 reports for compliance. For example, the handheld docking station 9 may be configured to automatically request a report including updated authorization holder information for a specific zone associated with a specific reader 8, each time the specific reader 8 is docked in the docking station. hand held 9.

Figure 2 illustrates an exemplary process flow for monitoring an authorization-based parking environment to determine whether the parked vehicle or vehicles have parking authorization. It is to be understood that the schematic representation provided in Figure 2 is exemplary in nature and alternative arrangements fall within the scope of the invention.

In step S1, a reader 8 scans a vehicle parked in an authorization-based parking zone managed by the PermitView system 1. Reader 8 scans the vehicle to determine if it includes a parking authorization that has a valid RFID tag. Those skilled in the art will appreciate that the authorization may be in the form of a sticker affixed to the vehicle or an item hung within the vehicle. Reader 8 may be a stationary reader or, as described herein in accordance with one embodiment of the present invention, a handheld reader operated by a PEO. According to an embodiment of the present invention, the RFID reader 8 is configured to detect and read an authorization and the corresponding RFID tag remotely. Furthermore, those skilled in the art will appreciate that the reader 8 can perform the scan while the reader 8 is in motion.

In step S2, the reader 8 determines whether an RFID tag is detected. If no tag is detected, the reader 8 and / or the PEO determines the reason for the tag detection failure, in step S3A.

During step S3A, if it is determined that the tag detection failure is due to a reader operator error, that is, the PEO, the vehicle is scanned again, in step S1. If the tag detection failure is due to reader malfunction, reader 8 is repaired or replaced.

Alternatively, during step S3A, it may be determined that the tag detection failure is due to tag malfunction or the absence of a tag. In any case, in step S4, the PEO identifies information related to the reviewed parked vehicle, called the "parked vehicle data" and enters the parked vehicle data into reader 8. The parked vehicle data may include, but is not limited to

ES 2 585 342 T3 limitation, the following information: 1) the make, model, year and color of the vehicle; 2) the vehicle's license plate number; 3) the position of the parked vehicle (for example, lot, street, and / or zone); and 4) the date, time and day of the week of the scan. Those skilled in the art will appreciate that the PEO can input the parked vehicle data into reader 8 using any suitable input means, such as, for example, a keyboard, a numeric keypad, and / or a voice recognition system.

The parked vehicle data is used to determine whether a valid tag is associated with the scanned vehicle, in step S5. For example, if, upon visual inspection of the vehicle, the PEO determines that there is no authorization / tag, or there is a tag / authorization but the tag is malfunctioning, the vehicle's license plate number can be checked in the PermitView 1 system. to determine if a valid tag is associated with the vehicle. If so, the PEO may send an indication or notice to the authorization holder regarding the holder's failure to properly present the authorization / label or the authorization malfunction, in step S5A. According to one embodiment of the present invention, the PermitView 1 system can track the number of such observations sent to a particular authorization holder, and, if the number exceeds a certain threshold (i.e., three previous alerts), a appropriate enforcement action (for example, issuing a complaint or immobilizing the vehicle). An enforcement action may include, but is not limited to, one or more of the following: 1) the issuance of a complaint or requirement; 2) the issuance of a notice or notice; 3) immobilization of the vehicle (ie, placement of stocks) and / or 4) no action.

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

Alternatively, if during step S2 a tag is detected, the reader 8 captures the unique RFID tag identifier, here called the "tag number" in step S3B, and identifies the parked vehicle data, in step S4. Those skilled in the art will appreciate that the tag number can be a string of any length of alphanumeric characters capable of uniquely identifying the particular authorization with which it is associated. According to one embodiment of the present invention, the tag number is stored on the RFID tag embedded or attached to the authorization.

Once the RFID tag number and the parked vehicle data have been captured, the reader 8 sends this data to the PermitView 1 system. Figure 3 illustrates at least a portion of the steps of the authorization management process performed by the PermitView 1 system. As shown in FIG. 3, the PermitView system 1 receives the tag number and the parked vehicle data from the reader 8 via the user interface 20, in step S1. The information is sent to the Privilege Module 40, which, in turn, retrieves the tag data associated with the tag number from the authorization database 50, in step SII.

According to one embodiment of the present invention, the "tag data" includes, but is not limited to, the following information: 1) authorized vehicle data; 2) data of the holder of the authorization; and / or 3) parking privilege data. "Authorized vehicle data" includes, but is not limited to, the make, model, color, year and / or license plate number of the vehicle or vehicles authorized under valid authorization. "Authorization holder data" includes, but is not limited to, the name, address, telephone number, email address and / or fax number of the authorization holder. The “parking privilege data” generally define the scope of the parking privileges or rights that the authorization holder has, including, but not limited to: a) one or more positions, zones, streets, lots, spaces, o areas where the vehicle can park; b) the term of the authorization and / or the expiration of the authorization; and / or c) the valid parking time (s) (ie weekend rights only; day rights only rights, seasonal rights, etc).

In step SIII, Privilege Module 40 performs the privilege analysis, described in detail below with respect to Figure 4. In step SIV, after performing the privilege analysis, Privilege Module 40 sends the results of the reader privilege analysis 8.

Returning to the process illustrated in Figure 2, at step S8, if it is determined that there is a violation based on the privilege analysis (see step S7) or, as described above, there is no valid tag associated with the parked vehicle ( See step S5), the appropriate application action to be taken is determined. Those skilled in the art will appreciate that the determination regarding the appropriate enforcement action can be made by the PermitView 1 system (as part of the privilege analysis), the PEO, or a parking schedule manager.

Figure 4 illustrates the steps involved in an exemplary privilege analysis, in accordance with one embodiment of the present invention. In general, the privilege analysis is performed by the PermitView 1 system, and includes, but is not limited to, a comparison of the parked vehicle data with the parking privilege data associated with the authorization assigned to the parked vehicle. In step SA, the Privilege Module 40 determines whether or not the parked vehicle data corresponds to the authorized vehicle data associated with the tag number scanned in the authorization database 50. If the data does not match, then there is misuse of the parking authorization, and a parking violation has occurred. For each parking violation that occurs, the authorization database 50 stores information related to the

ES 2 585 342 T3 parking violation, called "parking violation data". Parking violation data may include, but is not limited to, parked vehicle data (ie, information related to the offending vehicle); vehicle owner information (derived from license plate number), PEO information, type of enforcement action taken, etc. For example, an authorization that has been stolen or illegally transferred to an unauthorized vehicle will result in this type of mismatch, and a corresponding parking violation. According to one embodiment of the present invention, if authorization misuse is detected, the PermitView 1 system may place a temporary hold on the authorization, thereby indicating to the PEO (s) that the authorization is inactive or not. valid.

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

If the data matches, the Privilege Module 40 identifies the parking privilege data (ie, the scope of privileges) assigned to the authorization, in step SB. According to an embodiment of the present invention, the parking privilege data can be defined in the parking schedule at the time of issuance of the authorization, or at the time of a later update or edit. For example, a permit holder, John Smith, may have a permit that includes parking privileges for Zone “C” / Main Street, Hoboken, New Jersey / Monday-Friday / between 6 PM and 7 PM. the morning. In addition, the same authorization may also include privileges that allow John Smith, a student participating in the summer classes at Rutgers University, to park his vehicle in the campus parking lot “11” / zone “H” Vespacios “19-27 ”/ From June 15 to August 15. Together, these parking privileges form the parking privilege data associated with John Smith's parking authorization.

Referring to FIG. 4, in step SC, the Privilege Module 40 compares the parked vehicle data with the parking privilege data. Next, in step SD, it is determined whether the vehicle is parked within the scope of the privileges. If not, it is determined that a parking violation has occurred, and the parking violation data is recorded and stored in the authorization database 50. Those skilled in the art will appreciate that the parking violation determination can be made by the PermitView 1 system, the PEO, or a parking program manager.

In the above example, John Smith's vehicle is assumed to be parked in parking lot 9 / zone “B” / space 6 on June 17th. In step SC, this parked vehicle data is compared to the parking privilege data, resulting in a determination that a parking violation has occurred, in step SD. According to one embodiment of the present invention, the Privilege Module 40 communicates the results of the privilege analysis to the reader 8 for the execution of an appropriate application action. In addition, the parking violation data is stored in the authorization database 50.

Those skilled in the art will appreciate that the enforcement action can be taken in response to the detection of a parking violation and / or the identification of an offender. An offender is a person whose vehicle has a number of outstanding requests for parking violations that have been ignored. The number of pending violations to obtain the status of offender may vary according to the different number of requirements issued by the entities that control the issuance of requirements, such as a municipality, a city, a university or a corporation. For example, a violator may have two or more outstanding violations.

An exemplary enforcement action that can be executed by the parking management system is the administration of a fine (eg, a pecuniary fine). According to this embodiment, the parking management system includes a payment processing module that is configured to facilitate the payment of the fine (ie, the remedy measure). The payment processing module may be a computer-based system and / or a human-based system that provides a vehicle owner / operator with a means to pay the outstanding fine.

Another exemplary enforcement action includes immobilizing the offending vehicle. In accordance with this embodiment of the present invention, the application module includes a trap-based application system 1000 configured to perform vehicle immobilization. As depicted in FIG. 5, the exemplary application module includes a clamp-based application system 1000 including a one or more vehicle wheel clamps 12 used to immobilize a vehicle 14, one or more readers 8 configured to communicate with the vehicle. trap 12, and a trap management system 500 connected with communication to one or more readers 8 and / or the plurality of stocks 12 of the application system based on trap 1000.

The cleat 12 includes a combination lock 18 that can be unlocked by entering an "unlock code" that can be a combination of characters (for example, numbers, letters, symbols, etc.) whose serial arrangement is unique for each lock 18. Attached to clamp 12 is a clamp 218 RFID tag or any other convenient attachment arrangement. The stock RFID tag 218 operates at radio frequencies known in the art and will be described in more detail below in connection with Figure 8. The stock 12 is

ES 2 585 342 T3 preferably light in weight to ensure easy portability. In accordance with one embodiment of the present invention, cleat 12 may have jaws 22, 24 that open and close around wheel 16 in response to the introduction of the appropriate combination to lock 18. Typically lock 18 is assigned a unique serial number and this serial number is the same as the unique ID code number assigned to the RFID tag in gauge 218. Each cleat RFID tag 218 in each of a plurality of cleats has a unique ID in the tag memory corresponding to the unique serial number of the cleat combination lock 18. Thus all the traps used by the trap 1000-based application system are identifiable by their unique RFID code and the preferably identical associated serial number of the corresponding lock 18.

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

According to one embodiment of the invention, the stocks management system 500, herein referred to as the "BootView" system 500, includes a stocks database 44, a payment processor, and a stocks release module. The BootView 500 system may include one or more computers and / or human-based processing components configured to perform efficient administration and management of the traps 12 of the trap 1000-based application system.

In accordance with one embodiment of the present invention, each lock 12 included in the parking program includes a unique lock RFID tag identifier (eg, a tag number), which is stored in the lock 218 RFID tag attached or embedded in clamp 12 (for example, in the form of an RFID chip). The trap RFID tag identifier is associated with information or data specifically related to that trap, including, but not limited to: 1) the code for blocking the trap (ie, the lock code); 2) the code to unlock the trap (ie the unlock code); 3) the type / manufacturer of the stocks; 4) serial number; 5) a default or override unlock code; 6) the currently active unlock code; 7) the position of the stocks (i.e. position tracked by GPS or other tracking system); 8) maintenance records; 9) diagnostic information such as battery level, accelerometer readings (ie, impact or shock), and / or temperature; and / or 10) current lock status (eg, locked or unlocked), collectively referred to as the "trap data."

According to one embodiment of the present invention, the trap database 44 is any suitable computer-accessible memory or data storage device, which is configured to store the trap RFID tag identifier and associated trap data for each trap 12 managed by the parking program, to allow current supervision and management of the stock 12. When the trap 12 is scanned or read by the reader 8, the reader 8 communicates the trap data to the BootView 500 system. The BootView 500 system communicates with the trap database 44 retrieving any stored desired trap data, such as, for example, the lock or unlock code, and communicates this information to the reader 8.

For example, upon detection of a parking violation, the PEO can scan a trap 12 using reader 8, determine the trap tag identifier, and communicate this information to the BootView 500 system. Upon receipt of the trap tag identifier trap, the BootView 500 may query the trap tag identifier in trap database 44 in order to retrieve the lock code associated with that trap. The BootView 500 system then communicates the lock code to reader 8 for use by the PEO upon locking trap 12, thus completing the execution of the vehicle immobilization. Those skilled in the art will appreciate that a similar process is followed in facilitating the release of trap 12, where the trap database 44 provides the unlock code to the BootView 500 system for transmission to reader 8.

According to one embodiment of the present invention, the trap 12 may include a GPS receiver that allows the position of the trap 12 to be determined by a GPS or other tracking system. The BootView 500 system can be communicated with the GPS system so that the BootView 500 system can identify the position of each of the stocks 12 of the trap 1000 based application system. Optionally, the position of cleat 12 may be transmitted to the BootView 500 directly from cleat 12 via a search signal over a search network.

In accordance with one embodiment of the present invention, if the trap 12 is not communicatively connected to the BootView 500 over a search network (as described in detail below), the trap 12 may be configured to periodically cycle and change its password code. unlocking according to a predefined but predictable algorithm. The algorithm is known and maintained by the BootView 500 system, thereby allowing the system to determine the current unlock code without direct communication with lock 12.

In accordance with one embodiment of the present invention, the BootView 500 system may be connected with communication

ES 2 585 342 T3 to the traps 12 of the trap 1000-based application system by any suitable means of communication, such as, for example, via a conventional telephone system 66 (shown in Figure 5).

According to one embodiment of the present invention, the reader 8 includes an RFID interrogator 216. The interrogator 216 communicates via a communication network 28 with the BootView 500 system or other traffic violator database of an administrative entity. The RFID interrogator 216 of reader 8 also communicates with the RFID tag of stock 218 of stock 12, as shown in Figure 8.

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

In Figure 8, antenna 222 may also receive data via a communications network 28, as depicted in Figure 5, or from other sources, such as a municipal traffic violation computer system 300. Violator data can also be communicated directly to the BootView 500 from the municipal computer system 300 via a network 28 or from a communication modem 36 of the reader 8, as shown in Figure 7, using a communication link to the network. 28 according to an embodiment of the present invention. Network 28 may include the Internet, a local area network (LAN), or intranet among others (not shown). Optionally, the BootView 500 system and the municipal computer system 300 can be integrated and maintained on the same computer or computers.

The PEO can receive and communicate the offender data from the municipal computer system 300 to the reader 8 via the modem 36 and network 28, to the trap RFID tag 218 using an RFID interrogator transmitter, described in detail below, and to the BootView 500 system via a telephone system such as a cellular phone (not shown).

In Figure 8, the RFID system includes an interrogator 214 that further includes a host controller 220 that generates an interrogation command signal that is transmitted by transmitter 226 and antenna 228 as signal 230. Controller 220 also transmits violator data. , and other information from reader memory entered by the requestor via antenna 228, keyboard 250, or a separate antenna as needed.

Data entered into reader 8 via keyboard 250, as depicted in Figure 8, by PEO 38, see Figures 5 and 7, includes data depicted in Figure 6, such as, for example, the name of the PEO or municipal official, the unique RFID tag number, the date, time and position of the request, the position can be selected from memory such as stored codes of cities, municipalities, etc., the registration number and registration status of the vehicle , the injunction number, the violation code, and the violator indicator indicating that the violator is a violator.

According to an embodiment of the present invention, the position can also be determined by a GPS receiver located in the reader 8. The data, such as the position of the reader 8, the installed receiver system, license information, PEO information ( which can be entered by a scanner from an officer ID card in some cases where available) can be entered in part via the keyboard 250. Optionally, if the reader 8 includes a GPS receiver, the position data can be obtained by means of a GPS tracking system. The BootView 500 system can provide violator data (i.e., a license plate number; make, model, and year of the offending vehicle; name and address of the person who has outstanding parking tickets) that can be automatically entered into the cards. Readers 8 using a modem or other communications device over network 28, as shown in Figure 5.

For 8 readers without a modem or equivalent communications device, communication with the BootView 500 system and / or the municipal computer system 300 can be done manually by cell phone or other telephone or communications device using a 66 phone system and then the various Data received from personnel at the host and municipal positions can be entered manually using the keyboard 250.

With reference to Figure 8, the 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 data appropriate to the reception of the signal 230, and a transmitter 244 to transmit information in memory 242 via a transmitting antenna 234. The interrogator 216 may selectively transmit an interrogation signal and / or first information to the tag which may include infringement data such as an infringement code, a request number, a date and time stamp, a position, a license plate number , and other data introduced to the reader 8. The trap RFID tag 218 transmits the RFID signal 232 containing second information in response to the receipt of an interrogation signal from the antenna 228 of the interrogator 216 to the antenna 236. This second information includes the tag ID and relevant violation data. which are transmitted to the interrogator 216 via the stock RFID tag antenna 234 218 to the interrogator antenna

ES 2 585 342 T3

222. Signal 232 displays the RFID identification number and also violation data that can be stored in memory 242. Such violation data can be received from interrogator 216 under the control of controller 220 and stored in reader memory (not shown). previously entered, manually and / or also electronically from offender data downloaded from the BootView 500 system or the 300 municipal computer system. This data is transmitted by transmitter 226 under the control of controller 220. Keypad 250 may include keys to control the mode of operation of controller 220 with respect to issuing an interrogation command signal 230 or transmitting a data signal from infringement of first information 230 to be stored in the RFID tag of stock 218, as the case may be. The received violation data and unique RFID number are stored in memory 242 under the control of controller 240 and are 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 at the command of the keyboard 250 or by a signal received by it and said signal 230 is transmitted by the transmitter 226 and the antenna 228 as signal 230 to the antenna receiver 236 of the RFID tag from gauge 218.

The RFID clip 218 tag may be attached to the clip 12 in any convenient position by any suitable attachment device. Such a device may include attachment, attachment to a radio transparent housing that is permanently attached to the exterior of the trap, attached to an internal cavity of the trap, but exposed in a radiation transparent housing for reception and transmission of radio signals to and from the interrogator. , etc. An interrogator may also be included in the BootView 500 and / or the municipal computer system 300 to communicate with the RFID tag in stocks 218.

In Figure 5, the RFID handheld reader 8 is used to scan the trap RFID tag 218. The interrogator 216 records the scanned information of the tag's unique ID and date / time stamp in its memory. The remainder of the required data listed above and depicted in Figure 6 is entered as described above. Reader 8 is used, if equipped with a communication modem, to contact municipal computer system 300 to retrieve offender data that, if present, is entered into reader memory. Reader 8 is then used to transmit this information stored in reader 8 to the BootView 500 system and any associated databases.

Any commercially known RFID interrogator 216 and gauge RFID tag 218 can be used in reader 8 and gauge 12, and if necessary modified as described above. Furthermore, those skilled in the art will appreciate that a known reader 8 may be adapted to include an RFID interrogator 216, such as the TEK shielded RFID adapter. An employee identification card is preferably included for use by the issuer requesting to scan their employee number to the reader 8.

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

According to one embodiment of the present invention, as depicted in Figure 7, the BootView 500 system includes one or more computers or servers 42 including CPUs, memory, and one or more databases 44. According to one embodiment of the present invention, Municipal computer system 300 may include one or more computers or servers 46 and one or more databases 48. Optionally, the BootView 500 system and / or the municipal system 300 can include or be connected with communication to a data center of the traffic department 510 that includes stored violator data and that is included in the databases 48 of the municipal system 300 .

Although the BootView 500 system and the municipal computer system 300 are described as computers or servers that include high-speed hard drives, fast microprocessors, and large memories, conventional PCs can be used as an alternative. Such systems also include printers (not shown) to print the necessary data.

The BootView 500 system or the municipal system 300 can operate as configuration systems to configure the readers 8 and the tags with the appropriate data such as position codes in the reader 8, serial numbers and RFID tag numbers for the tags, etc. for use in the 1000 application-based application system. The readers 8 may also have pins for attachment to the BootView 500 system and the municipal system 300 to download configuration information data required and implemented with known devices (eg, file transfer server protocols). The storage devices used in the trap-based application system 1000 can be implemented using various data formats known in the art (eg, relational databases). Storage memories can be part of computer systems or implemented with separate devices. The stored data can be accessed using Microsoft Access or other suitable databases. The BootView 500 system and the municipal system 300 servers may be located in the same position as the storage devices in the respective systems. Communication between them is conventional. Network 28 can be wireless or wired and can be any known system including those listed above. Printers can be in the same positions as servers or in different positions and coupled by communication systems

Known ES 2 585 342 T3.

In operation, a PEO or request issuer 38, as shown in Figures 5 and 7, issues a request for parking to a vehicle that violates a parking rule, in step 54a of Figure 6. The PEO 38, using the reader 8, communicates through the network 28 (see figure 5) or through the telephone system 400, with the databases 48 of the municipal computer system (see figure 7), to know if the vehicle has Pending previous infractions, that is, it is an offender, as represented in step 54b of figure 6. This information is automatically downloaded to reader 8 through the network 28 or entered manually if it is by telephone, in step 56 of figure 6.

According to one embodiment of the present invention, the municipal computer system 300 may be maintained by a control entity, and includes the database 48 of violator data. Municipal computer system 300 may also include a memory card read / write device (not shown) associated with database 48 for copying offender data to a memory card associated with the read / write device. The card is used to transfer the offending data from database 48 to reader 8. Such cards, called compact flash memory cards, secure data (SD) cards, etc., are relatively small, but usually have a capacity relatively large memory (for example, a memory capacity of 16, 64, 128, or 256 megabytes). Such card readers, commonly used with digital cameras and other electronic systems, are widely available. The reader 8 also has such a card reader (not shown) for transferring offender data entered on the card from the database 43 of the municipal computer system 300, shown in Figure 7, to its memory.

If the vehicle has associated pending violations, the PEO 38 then enters the data, as depicted in Figure 6 and described above, into the reader 8 via the keyboard and over the network 28, if available. The emitter then places the clamp 12 on the vehicle wheel 16, as shown in step 60 of Figure 6.

According to one embodiment of the present invention, the RFID tag of strap 218 is embedded in the strap 12, and includes a unique ID code number that preferably corresponds to the serial number of the strap 12. At the same time, the tag ID and The corresponding combination of the clevis lock 18 can be stored in the database 44 communicatively connected to the BootView 500 system, as depicted in FIG. 7. This tag ID is mapped in database 44 to the corresponding combination code to unlock the trap 12 associated with said unique tag ID.

In Figure 6, the sender then communicates with the tag to load the tag ID and then with the BootView 500 system in step 58. The reader is then used to load the violation data including the unique RFID code, the date and time of the violation, the information about the violator indicating whether the violator is an violator, and optionally including the total fines attributed to the violations. pending offenses, vehicle make, vehicle registration number, registration status, can also be optionally loaded the request number and the violation code through the network 28 or by telephone, if the reader 8 does not have a modem or communications device to communicate with the network 28. These violation data are also transmitted to the RFID tag of stocks 218 by interrogator 216, as shown in step 60 of FIG. 6.

The trap-based application system 1000 can serve as the resolution module of the parking management system. The 1000 ring gauge based enforcement system assists the vehicle owner / operator in taking the appropriate remedial action which may include, but is not limited to, the payment of any outstanding fines, removal of the 12 ring gauge from the vehicle, and / or return of clamp 12 to an appropriate position.

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

In order to facilitate the removal of the trap, the PEO 38 may provide information related to the removal of the trap 12 (i.e. instructions for performing the remedial measure), namely the contact information (for example , phone number of the entity that controls the BootView 500 system, to the owner / operator of the vehicle. In accordance with one embodiment of the present invention, the vehicle owner / operator may contact entity 62 via a conventional telephone system 66, as depicted in Figures 5, 6, and 7, or other suitable means of communication.

Owner / operator 64 gives entity 62 the request number (which may also be the stock serial number). Using this information, entity 62 queries its computer system database for the tag ID previously communicated by PEO 38 (ie, via reader 8, in person or by telephone). These events can take place within a number of minutes or hours of each other since typically the stocks will be set before the owner / operator returns to the vehicle. Once the entity has the tag id,

ES 2 585 342 T3 also has the offender data and associated fine information.

Alternatively, the entity can contact the municipality 48 database to obtain the information on fines, which is slower and not as desirable as having the information on fines immediately available. The entity may use the BootView 500 system and / or associated databases 44 to correlate offender data with fine data to determine the fine owed for any number of outstanding claims. However, preferably, this data is provided by the reader 8 downloaded directly from the municipal system 300, as shown in FIG. 5, or communicated directly to the BootView system 500 by telephone by the requestor.

As described above, an exemplary remedial measure facilitated by the 1000 trap-based management system is the payment of a fine. In accordance with one embodiment of the present invention, the BootView 500 includes a payment processor that is configured to facilitate payment of the penalty by the owner / operator. The payment processor may be communicatively connected to a communications network that allows the vehicle owner / operator to authorize payment of the fine over the phone by providing their credit card number or other payment information (for example, a credit card number). debit card), in step 70 of figure 6. The remedial measure may include the payment of a deposit for the stocks 12, to guarantee that the owner / operator will return the stocks 12 to the entity. Upon completion of the appropriate remedial action (ie payment of the outstanding fine), the entity can provide the owner / operator with the code required to unlock the trap 12. The unlock code can be provided by any means of communication appropriate, such as by phone. In addition, the owner / operator may be provided with other information about the remedial measure, such as, for example, an address to which the stocks 12 can be returned; after removing it from the vehicle.

According to one embodiment of the present invention, the release and / or removal of the trap can be facilitated by allowing the user to make the appropriate payment using electronic or card-based payment methods. For example, the user can pay for the release of the stocks using a conventional card issued by a gas station, such as an Exxon / Mobil Speedpass ™ card.

In step 72, when the stocks 12 is returned to the appropriate entity, agent, dealer, etc., the stocks tag is read to verify that the stocks returned corresponds to the stocks information associated with the owner / operator data received from the PEO. If you agree, the deposit is returned to the owner / operator. Advantageously, the entire resolution process (ie release of the trap) can take place in a relatively short period of time. In addition, the return of the stocks can be made at the convenience of the owner / operator.

In the event that the owner / operator chooses not to pay and does not contact the entity, the entity can send a garnishment notice to the municipality that issues the requirement. The term "municipality" is intended to include any control entity that establishes a parking program.

According to an embodiment of the present invention, the municipality can contact a towing service by telephone, in step 74, to take the offending vehicle to a storage location. To tow the vehicle, the crane operator has to remove the stocks, in step 76. The crane operator communicates with the entity's system 32 (for example, by telephone) to obtain the combination required to unlock the stocks, in step 74. According to an embodiment of the present invention, the crane operator can use a reader 8 to obtain the stocks tag ID and related violation data and communicate this information to the entity or municipality via the network 28 or by telephone to obtain the information. lock unlock combination. The crane operator then removes the stocks and takes the vehicle to a storage location, at step 76, and the stocks are returned, at step 72.

According to one embodiment of the present invention, the trap release code may be an offset number to avoid indiscriminate distribution of trap release codes. That is, the codes can be assigned as random numbers to each stocks. When so assigned, the numbers are then entered into the host and appropriate municipal databases where the traps are initially kept in check. If the stocks are distributed by the municipality, it assigns the release codes to each stocks, records the release code and stocks tag IDs, and transmits the codes to the entity corresponding to the unique tag IDs associated with each stocks . The traps preferably have a master override key to release the trap in the event of a technology failure of the release code.

Reader 8 may include software configured to read offender data stored in a municipal computer system database. Reader 8 may include a connector for mating with a receptacle into which such data can be transferred using control circuitry in municipal computer system 300. In addition, the municipal system 300 may alternatively also include a system for reading offender data directly to the trap tag without the need for reader 8 to do so. This direct data entry to the tag memory in the municipal computer system eliminates possible errors in the communication system transmission of such data through the reader to the tag.

Those skilled in the art will think that the described embodiments are offered by way of example, and that it can be done

ES 2 585 342 T3 modifications to the systems described. For example, reader 8 can include a digital camera whose data can also be communicated by reader 8 to RFID tag 218, and BootView 500 and / or municipal computer system 300. The described embodiments are offered by way of of example and not of limitation. The invention is intended to be defined by the appended claims and not by the disclosed embodiments.

In accordance with one embodiment of the present invention, an alphanumeric search network may be used for two-way communication between trap 12 and entity host computer system 62. Using the search network, entity host computer system 62 unlocks trap 12 to distance by transmitting the appropriate unlock code to ring gauge 12.

According to one embodiment of the present invention, the paging network may be used to communicate new unlock codes from trap 12 to entity host computer system 62. According to this embodiment, trap 12 may be equipped with an unlock code generator. that periodically generates an unlock code when it is successfully locked. The trap 12 transmits the unlock code to the entity host computer system 62 via the paging network. In the event that the transmission is unsuccessful, the code generator detects the transmission failure and defaults to a no-fault unlock mechanism, which can be a manual override (i.e. unlock with a key) or a code unlock by default. Alternatively, upon successful lockout 12, the BootView 500 can generate an unlock code and transmit the code to lock 12.

According to one embodiment of the present invention, the trap-based delivery system 1000 may include one or more trap docking stations configured for the coupling of one or more traps. The trap docking stations can be connected with communication to the BootView 500 system and the PermitView 1 system.

The cleat docking stations can be configured to perform one or more of the following actions: 1) recharge the cleat 12 power supply, 2) transmit usage and diagnostic data to the BootView 500 system; 3) reprogram microprograms stored in block 12; 4) communicate software updates from the BootView 500 system to trap 12; 5) update or change lock and unlock codes; and 6) print stocks / payment return receipts.

The stocks docking station can be communicated to the stocks by suitable means of communication and connection, such as, for example, a USB connection, Firewire, an Ethernet connection, a wireless connection (for example, Bluetooth or WiFi connections) , etc. Optionally, the cleat docking station can use a power over Ethernet connection to recharge the power source (eg, batteries) of the cleat 12. The stocks docking station can be protected against external factors such as weather, vandalism and hacking.

According to one embodiment of the invention, the single or multiple "return" positions may include a locker-type stocks docking station that is adapted to house and engage a plurality of stocks 12.

According to one embodiment of the present invention, the PermitView 1 system can be accessed by both existing and future authorization holders via the authorization holder / applicant portal of the user interface 20. The user interface 20 may include an authentication screen or input that instructs current authorization holders to provide input information (for example, a username and password). Those skilled in the art will appreciate that any suitable authentication system or method can be used in accordance with the present invention, such as, for example, ASP.Net WebForms based authentication. An authorization holder can access information related to their account, and perform various tasks related to the account, including, but not limited to, the following: 1) add / edit / delete / update authorized vehicle data; 2) add / edit / delete / update authorization data; 3) add / edit / delete / update authorization holder data; 4) make bill payments, renewal and / or complaint; and 5) review account information including previous notices / notices and / or complaints, etc.

According to an embodiment of the present invention, a person can access the PermitView 1 system to submit a new authorization request. The new authorization request may include, but is not limited to, data on the authorization holder, the vehicle or vehicles associated with the authorization, the scope of privileges requested, a means of payment, and / or the proof required for the issuance of an authorization. . The proof required to obtain an authorization may include, but is not limited to, proof of residency or eligibility for residential parking privileges (for example, a utility company invoice, an owner / operator license, a real estate tax receipt, etc), proof of employment for employee parking privileges, proof of enrollment for student parking privileges, proof of personal identification (for example, an owner / operator license, Social Security card, etc). According to one embodiment of the invention, this information can be electronically scanned and transmitted to the PermitView 1 system in any suitable file format, such as, for example, a portable document format (PDF).

Those skilled in the art will appreciate that an inventory of available and / or granted authorizations may be

ES 2 585 342 T3 managed, stored and maintained by the PermitView 1 system in a database, such as, for example, authorization database 40. Alternatively, the inventory may be stored in a separate database, called inventory database 7B in Figure 1, managed and maintained by the parking program manager via the parking manager computer 7. According to this embodiment, the PermitView system 1 can receive new requests and communicate them to the parking manager computer 7 for review and evaluation.

According to one embodiment of the present invention, a PermitView administrator can access the PermitView system 1 via the PermitView administrator portal from user interface 20. An increased or relatively higher level of authentication is preferably required for access via the user interface portal. administrator due to the type and amount of access the administrator has to the PermitView 1 system.

According to one embodiment of the present invention, the one or more administrators can access the PermitView 1 system to perform a number of functions, including, but not limited to: 1) configuring and managing new parking programs; 2) provide online support; 3) manage user groups; 4) set parking privilege data according to the parameters of the parking program; 5) manage the inventory of authorizations; 6) process new authorization requests; 7) manage the issuance of notices / notification and complaints; 8) define and provide reports to user groups; and 9) management of billing and collection processes.

According to one embodiment of the present invention, a parking program manager can access the PermitView system 1 through the parking manager portal program of the user interface 20. Compared to the other user groups, the parking program managers Parking requires a single level and type of access to the PermitView 1 system. According to one embodiment of the present invention, the one or more administrators can access the PermitView 1 system to perform various functions, including, but not limited to: 1) performing various reports related to the parking schedule; 2) configure and manage new parking programs; 3) update / edit actual authorization holder data; 4) manage authorization inventory; and 5) follow-up of application action information.

Figure 9 illustrates the parking management system for managing a trap and authorization-based parking environment, described in detail above, including the BootView 500 system, the PermitView 1 system, a plurality of traps 12 each having an RFID tag of trap, a plurality of clearances each having an RFID tag, and a plurality or readers 8 for communicating and reading the RFID tags associated with the stocks 12 and clearances 11.

In accordance with one embodiment of the present invention, the PermitView 1 system can be used to manage a multi-space "pay-per-park" program and / or environment. Conventional pay-per-parking programs generally allow a person to pay to park in a particular parking space, location, or zone for a desired period of time. Typically, the person makes payment using a "multi-space" or "pay and see" parking meter or cash machine, credit card, or debit card, at the parking meter itself. Alternatively, the person can make the payment by telephone communication with an established "pay by phone" or "parking by phone" system. Generally, after payment, the person prints a "receipt" or proof of purchase, and returns to their vehicle to put the receipt on the vehicle, typically in a position visible from outside the vehicle, such as the dashboard or windshield.

To apply these programs according to conventional systems, the information related to the vehicles that are legally parked (that is, information that identifies the vehicles that have been paid for and for which the time has not expired) is collected in a “list of legally parked vehicles ”delivered to a PEO, typically via wireless communication to the PEO handheld ticket issuer, or more commonly, through a “report” that the PEO can access and print through the parking meter by entering a special code on the parking meter.

The PEO then, by visual inspection, compares the list of legally parked vehicles with the physically parked cars in a given area, and takes an appropriate enforcement action (for example, issuing a ticket) against vehicles parked in a parking space. parking not listed in the report.

In addition, conventional "multi-space" parking meter systems and programs typically require the driver to walk to the multi-space parking meter associated with the parking spot, typically provided with one parking meter per lot, to purchase parking time using cash, credit card. credit or debit. Parking lots using “multi-space” parking meters have to visually mark each parking space with an identifier (for example, a number and / or letter designation), or by printing the identifier on the road, ground or sidewalk on or near each individual parking space in a way that clearly identifies each parking space on the lot. As such, the driver has to remember the identifier and enter the identifier exactly into the "multi-space" parking meter in order to buy time for that particular parking space.

ES 2 585 342 T3

According to an embodiment of the present invention, payment for a parking space in a pay-for-parking environment can be executed by the person using a means of payment such as an account number or smart card associated with his authorization 11. This allows that the person buys time from the multi-space parking meter, at the parking meter itself, or by paying over the phone system. In the case of “multi-space” parking meters, due to the association of the payment method and the authorization 11 associated with the vehicle (that is, associated with the vehicle in the PermitView 1 system and installed or displayed by the vehicle), the person can make the payment without having to write down or remember the parking space identifier of the space where you have parked. According to an embodiment of the present invention, the person can avoid interaction with the parking meter that processes a payment, by means of a telephone payment system, which has the information related to the transaction processing by the PermitView 1 system and associated with its authorization. 11, and communicated by the authorization vision system 1 to the appropriate PEO.

According to one embodiment of the present invention, in the case of "pay and view" parking meters, the person does not have to return to their vehicle to put the guard on the vehicle's dashboard. This is more convenient for the person while providing an improved enforcement method for the enforcement authority.

In accordance with one embodiment of the present invention, the PermitView 1 system facilitates the application of pay and view parking, parking by phone, and pay by phone environments. Specifically, the list of legally parked vehicles can be provided directly by the PermitView 1 system to reader 8. Alternatively, the PermitView system 1 may provide the list of legally parked vehicles to the multi-space parking meter or pay-and-view meter, which is communicatively connected to the reader 8, by, for example, a wireless connection. Advantageously, the processing of the list of legally parked vehicles according to an embodiment of the present invention eliminates the need for the PEO to interact with the parking meter to generate and obtain the report and also eliminates the need to visually inspect the spaces in the absence of the report to determine if application action is required. Instead, the reader 8 can receive the list of legally parked vehicles from the PermitView 1 system, scan the authorization (s) 11 of the vehicles parked in the environment, capture the tag data associated with the authorization 11, and compare Tag data with the list of legally parked vehicles to determine if enforcement action is required.

According to an embodiment of the present invention, payment for the space can be made by the person using an account number or smart card associated with his authorization 11. After payment, the data related to the parking payment transaction, called " payment data for parking ”, are associated with your authorization 11 and unique RFID tag identifier in the PermitView 1 system. Pay-to-park data may include, but is not limited to, the time and date of the purchase, the amount of parking time purchased, an authorization to automatically charge an account for an extension of the parking time, information identifying the authorization 11 associated with the parked vehicle, and a “virtual meter” (ie, a virtual clock that works from the time of the payment authorization during the period of time selected and paid for by the person).

The pay-to-park data is associated with the authorization 11 in the PermitView system 1, which prepares a list of legally parked vehicles and provides the list to the reader 8, for consideration by the PEO. The PEO can scan authorizations 11 in a pay-per-parking environment with the reader 8, which automatically checks the tag data associated with the scanned authorization 11 against the list of legally parked vehicles received from the PermitView system 1, thereby eliminating the need have the PEO perform a visual inspection for the purpose of detecting a parking violation.

In accordance with an embodiment of the present invention, when a person attempts to process a payment for a parking space in a pay-per-parking environment, the PermitView 1 system can determine that the person is on a violator list. According to one embodiment of the present invention, the list of offenders may be provided by one or more sources, such as a municipality or other administrative entity. The offender list can include information that identifies each person who has pending parking violations who have been assigned a “prohibited status,” meaning that the person is prohibited from parking in one or more zones controlled by a program. parking lot managed by the PermitView system 1. As such, when a person or associated vehicle that has a prohibited status attempts to process payment for a pay-to-park space, the PermitView 1 system can communicate their prohibited status to the person and inform the person that parking is prohibited to failure to resolve pending infractions. Additionally, the PermitView 1 system can instruct the person to pay any outstanding fees or fines to remove the prohibited status. Those skilled in the art will appreciate that communication between the PermitView 1 system and the person can be by any suitable means of communication, such as, for example, by telephone and / or by a multi-space parking meter or similar interactive display placed in the environment of payment for parking.

It is to be understood that the exemplary embodiments are merely illustrative of the invention and that those skilled in the art can devise many variations on the above-described embodiments without departing from the scope of the invention. Therefore, all such variations are intended to be included within the scope of the following claims and their equivalents.