Location-Based Vehicle Parking System

A location-based vehicle parking system for efficiently managing vehicle parking permissions for a parking space. The location-based vehicle parking system generally includes determining the presence of a vehicle within a parking space by a parking sensor, communicating sensor data to a management server, communicating vehicle data to the management server by a permit device within the vehicle, and determining if the vehicle is authorized to park within the parking space. A communication is sent to an inspector to manually verify permissions for a vehicle in a parking space if not authorized.

CROSS REFERENCE TO RELATED APPLICATIONS

Not applicable to this application.

Not applicable to this application.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to a vehicle parking system and more specifically it relates to a location-based vehicle parking system for efficiently managing vehicle parking permissions for a parking space.

2. Description of the Related Art

Vehicle parking space management systems have been in use for years for managing parking spaces for vehicles. One example of a parking management system is conventional parking meters that a user pays a specified amount of money into for a specified period of time. Another example of a parking management system is a parking lot attendant that receives payment based upon the amount of time a vehicle was parked in the parking lot. Another example of a parking management system is where a person purchases a parking permit and visibly displays the parking permit in the window of the vehicle to indicate that the vehicle is authorized to park in the parking space.

One problem with the previously discussed parking management systems is that they are labor intensive and therefore costly to maintain. Another problem with the previously discussed parking management systems is that manual verification is required to determine whether a vehicle is authorized for a particular parking space resulting in increased expense and lost revenue from lack of enforcement.

Because of the inherent problems with the related art, there is a need for a new and improved location-based vehicle parking system for efficiently managing vehicle parking permissions for a parking space.

BRIEF SUMMARY OF THE INVENTION

The invention generally relates to a location-based vehicle parking system which includes determining the presence of a vehicle within a parking space by a parking sensor, communicating sensor data to a management server, communicating vehicle data to the management server by a permit device within the vehicle, and determining if the vehicle is authorized to park within the parking space. A communication is sent to an inspector to manually verify permissions for a vehicle in a parking space if not authorized.

DETAILED DESCRIPTION OF THE INVENTION

A. Overview of Invention

FIGS. 1 through 10illustrate the present invention. The location-based vehicle parking system generally includes determining the presence of a vehicle14within a parking space11by a parking sensor30, communicating sensor data to a management server40, communicating vehicle data to the management server40by a permit device50within the vehicle14, and determining if the vehicle14is authorized to park within the parking space11. A communication is sent to an inspector to manually verify permissions for a vehicle14in a parking space11if not authorized.

B. Management Server

The management server40may be comprised of any computer, Internet-based computer, cloud based computer, virtual computer, home computer or other computer system capable of receiving and transmitting data via IP networks and the telecommunication networks. The management server40may be comprised of any electronic system capable of receiving, storing, calculating and transmitting information (e.g. computer data, etc.).

The management server40is utilized in the present invention to receive, store and transmit organization account data and user account data. The management server40stores the organization accounts and user accounts in a database. The management server40may include a verification system20to verify whether a permit device50has the parking credentials required to park in a parking spot (alternatively the verification system20may be a separate computer).

C. Organization Accounts

For example, individual organizations (e.g. businesses, government agencies) that manage one or more parking spaces11(or a parking lot) can create their own individual organization accounts on the management server40through an organization computer15connected to the telecommunications network19to communicate with the management server40. A web-based interface is preferably utilized for the organization to create the organization account using basic information and space management information, however, various other types of organization account creation systems may be utilized (e.g. software application).

Information for the organization such as the organization name, organization login credentials, address, contact names, telephone numbers, e-mail address(es), website, payment information (if necessary), financial account information and the like may be included within the organization account data. Additional information about the organization may also be stored within the organization account as needed to operate the invention.

In addition, space management information associated with the organization account of the organization includes information about the parking spaces11to be managed such as the name of a parking lot/space, the location for each of the parking spaces11being managed (e.g. city, state, country, geographic coordinates), the size (e.g. area, width, length) for each of the parking spaces11being managed, any height restrictions for a parking space11, permissions for each of the parking spaces11, permits allowed for each of the parking spaces11, types of parking spaces11, vehicle14types allowed within the parking spaces11, length of time allowed for a vehicle14to park in the parking spot, time restrictions for the parking spaces11, the total number of parking spaces11in a parking lot, the number of parking spaces11being managed and the like may be included within the organization account data. The space management information also preferably includes information relating to parking sensors30corresponding to each of the parking spaces11to help identify which parking space11has a vehicle14present. The space management information may be associated with an organization account where the organization owns the parking spaces11or with a different organization that is managing the parking spaces11.

D. User Accounts

The organization managing the parking spaces may create individual user accounts on behalf of the user and/or individual users can create their own individual user accounts on the management server40through a user computer17(e.g. computer, mobile device, smart phone) connected to the telecommunications network19to communicate with the management server40. A web-based interface is preferably utilized for the user to create the user account, however, an application running on the user computer17may also be utilized to setup all of the user's preferences.

Information such as the user's name, user's login credentials, type of vehicle14, vehicle14size (e.g. length, width, height), vehicle14license plate, vehicle14color, home address, work address, e-mail address(es), website, payment information and the like may be included within the user account data. The user account further includes information about the permit devices50associated with the user that the user is allowed to utilize for parking a vehicle14and for which vehicles14each permit device50may be utilized within. The permit device50preferably includes a device identifier (e.g. serial number, code) that is electronically transmitted by the permit device50, wherein the device identifier is associated with the user account to identify both the permit device50and the user account.

In addition, the user account preferably includes information regarding parking permits the user can purchase in advance, has previously purchased or have been granted and other parking rights that are associated with the user and/or the permit device50collectively referred to as “parking permits”. The user is able to manage, purchase, apply for, cancel and otherwise manipulate the parking permits via the management server40as needed. Various types of parking permits for different parking lots and parking spaces11may be offered to the user when accessing the user interface for the management server40similar to conventional online purchases or applications. Alternatively, the user may apply for or purchase a parking permit directly from an organization and the organization may update the organization account to indicate that the user has a parking permit for the specific parking lot and/or parking spaces11.

FIG. 2of the drawings illustrates an example of a parking lot having a plurality of parking spaces11each having a generally rectangular shape with parking indicia13(e.g. painted lines) defining at least a portion of the boundaries of the parking spaces11. While parking lots typically are comprised of rows of parking spaces11, it can be appreciated that the parking lot may have various configurations or a parking lot may be comprised of single parking space11. Each parking space11preferably is assigned a parking identifier (e.g. serial number, code) that is utilized to identify each of the parking spaces11in the database of the management server40, wherein the parking identifier is stored within a sensor database of the management server40.

Each parking space11preferably includes a parking sensor30to detect the presence of a vehicle14in each respective parking space11. The parking sensor30may be positioned in various locations of an individual parking space11, however, it is preferable that the parking sensor30be positioned approximately 2 meters from the front end of the parking space11to be positioned under a parked vehicle14as illustrated inFIG. 2of the drawings. The parking sensor30may also detect the presence of the permit device50utilizing wireless communications between the parking sensor30and the permit device50(e.g. the permit device50emits a Bluetooth low energy signal that is detected by the parking sensor30).

The parking sensor30is able to detect the presence of a vehicle14in the associated parking space11for the parking sensor30without mistaking a human or pet walking through the parking space11as a vehicle14. Furthermore, the parking sensor30preferably does not notify the management server40of a vehicle14parked in the parking space11until after a period of time (e.g. 5 seconds or more) that a vehicle14is stationary within the parking space11and/or within a specific distance of the parking sensor30(e.g. less than 2 feet from the parking sensor30when the parking sensor30is positioned at the front end of the parking a space as illustrated inFIG. 2of the drawings. The parking sensor30may detect the presence of the vehicle14utilizing various types of object presence detection systems such as but not limited to proximity sensors (e.g. RF radiation, light, optical, sound, capacitive, magnetic, inductive proximity sensors), motion sensors (e.g. infrared, ultrasonic, microwave sensors, video), a weight sensor in the parking surface12of the parking space11and the like.

The parking sensors30preferably communicate with the management server40via a telecommunications network19to indicate that a vehicle14is parked in the parking space11. The parking sensors30may access the telecommunications network19directly or via a gateway device32(e.g. wireless router). The parking sensors30may be in communication with the gateway device32via a wired connection or wireless connection (e.g. Wi-Fi, Bluetooth and the like). The parking sensors30may include a wired connection to an electrical power supply, a battery and/or a solar power system for providing electrical power to the parking sensors30.

F. Permit Device

The permit device50may be comprised of any type of electronic device (e.g. computer) for practicing the various aspects of the present invention. For example, the permit device50can be a personal computer (e.g. APPLE® based computer, an IBM based computer, or compatible thereof) or tablet computer (e.g. IPAD®). The permit device50may also be comprised of various other electronic devices capable of sending and receiving electronic data including but not limited to smartphones, mobile phones, telephones, personal digital assistants (PDAs), mobile electronic devices, handheld wireless devices, two-way radios, smart phones, communicators, video viewing units, television units, television receivers, cable television receivers, pagers, communication devices, and digital satellite receiver units.

The permit device50is an electronic device that is adapted for communicating with the management server40, the scanner70, the gateway device32in the parking lot, parking sensors30and/or other devices. The permit device50includes memory that may be reprogrammed as needed by the management server40or other computer (e.g. changing the device identifier, adding/removing parking permits, changing rules from the parking provider). The permit device50further preferably receives signals from a navigation system (e.g. a satellite navigation system such as the Global Positioning System) so the permit device50can determine the physical location of the permit device50and the vehicle14the permit device50is associated with.

The permit device50is preferably an electronic device that is portable and removable from a vehicle14as desired by a user so the permit device50may be used in more than one vehicle14as desired. However, the permit device50may be directly and permanently connected to the vehicle14(e.g. part of the electrical system of the vehicle14). The permit device50is preferably positionable in a visible location of the vehicle14to allow for manual inspections by a parking inspector, however, the permit device50may be located in non-visible locations of the vehicle14(e.g. under the hood, beneath the vehicle14, in the trunk, on the roof of the vehicle14).

FIGS. 3athrough3cillustrate an exemplary permit device50comprised of a housing52having a first portion54having an opening55and second portion56that is connectable to the first portion54to form a housing52having an interior space to store the electrical components of the permit device50. A plurality of latches51or other attachment members extending from the first portion54allow for removable connection of the first portion54to the second portion56. By releasing the latches51, the user is able to remove and/or replace a permit card60within the housing52as needed. The housing52is preferably comprised of a thin and generally rectangular structure as illustrated inFIG. 3aof the drawings. Various other configurations for the housing52may be utilized capable of being attached to a window16without obstructing the view of the driver.

The housing52is preferably attachable to a window16(e.g. windshield) of a vehicle14utilizing an attachment device53.FIGS. 3aand3billustrate an exemplary attachment device53comprised of a length of adhesive tape that surrounds the face of the first portion54of the housing52, wherein the adhesive tape secures to the interior surface of the window16of the vehicle14thereby exposing through the opening55the solar panel64and any permit indicia (e.g. a permit number, name of the user, parking lot identifier, parking space11identifier and the like) to assist in the visual inspection of the parking permit by an inspector or other parking enforcement personnel.

A faceplate58is preferably positioned within the housing52with a portion exposed via the opening55. The faceplate58is positioned over the permit card60to cover the electronics of the permit card60and provide a pleasing visual appearance that may be changed by the user or the business providing the parking permit. The face plate may have various types of indicia such as the name of the parking lot, identification of the parking space11(e.g. Lot B, Space #32), indication of the wireless technology used (e.g. NFC for near field communication). The faceplate58is a flat structure having an aperture that allows for the solar panel64to extend through thereby exposing the solar panel64through the opening55of the housing52as illustrated inFIGS. 3aand3bof the drawings.

The permit device50preferably includes a permit card60, wherein an exemplary permit card60is illustrated inFIGS. 3a,3band4of the drawings. The permit card60preferably includes all or a significant portion of the electronics used for the permit device50. The permit card60may be removed and/or replaced by the user or the business as needed. The permit card60is portable to allow for placement in different housings52mounted in different vehicles14that the user operates.

The permit card60may be comprised of a printed circuit board (PCB) or other electronic device. As shown inFIG. 4, the permit card60includes a microprocessor67that receives, calculates, stores and transmits data. The microprocessor67includes memory that stores the device identifier, a user identifier and other parking related information. The information stored within the permit card60may be transmitted to the management server40, the scanner70, the gateway device32, a organization computer15and/or a user computer17.

The permit card60further preferably includes RFID capability that allows for the scanner70to identify the device identifier and user information by scanning the permit device50. The RFID device86within the permit card60may be active or passive. Furthermore, the RFID device86(including the memory within the RFID device86) is preferably in bidirectional communication with the microprocessor67so that the RFID memory may be reprogrammed by the microprocessor67as needed to update a device identifier, user information or other related data.

The permit card60further preferably includes an energy storage device65(e.g. battery) that is electrically connected to the microprocessor67and other components of the permit card60to provide electrical power. The energy storage device65may be removable and/or rechargeable. The energy storage device65is preferably electrically recharged by a solar panel64with a power manager63as further shown inFIG. 4of the drawings. Recharging by the solar panel64prevents the user from having to periodically replace the energy storage device65and extends the useful life thereof. The power manager63controls the charging of the energy storage device65to ensure proper charging.

The permit card60further preferably includes a GPS receiver82that receives signals from a GPS satellite system18. The GPS receiver82is in communication with the microprocessor67to provide location and/or time information to the microprocessor67to assist in identifying the location of the permit device50. Various types of other navigation technologies such as land-based location towers may be used to identify the location of the permit device50and vehicle14of the user.

The permit card60also includes an RF transceiver84that communicates wirelessly with the gateway device32and/or the telecommunications network19acting as a communications gateway between the permit device50and the management server40. The RF transceiver84may communication via various wireless technologies such as but not limited to Wi-Fi, Bluetooth and the like.

8. Indicator Light and Buttons.

The permit card60preferably includes an indicator light62to indicate the status of the permit device50(e.g. green light indicates “On”, red light indicates “Off”, blinking green light indicates the permit device50is communicating with the management server40, blinking red light indicates the permit device50has detected the vehicle14is parked and is checking for a connecting with a local gateway device32). The permit card60further preferably includes at least one button66to allow for the user to manually power the permit device50on or off along with other basic functions. The permit card60may also include a display screen electrically connected to the microprocessor67to display various types of information to the user utilizing the permit device50. The indicator light62and the button66are both electrically connected to the microprocessor67as illustrated inFIG. 4.

The permit card60and therefore the permit device50further preferably includes an accelerometer80which is in communication with the microprocessor67. The accelerometer80is utilized as a low-power system to determine when a vehicle14has parked and therefore the permit device50should leave a “sleep mode” which requires a small amount of electrical power and enter an “active mode” which requires additional electrical power.

The accelerometer80detects movement of the permit device50(which in turn is detecting movement of the vehicle14the permit device50is positioned within) and when there is movement present the permit device50determines that the vehicle14is moving and therefore not parked. When the accelerometer80does not detect movement, the permit device50determines that the vehicle14is not moving and therefore is parked.

To prevent the permit device50from unnecessarily being activated to active mode constantly, there is preferably a minimum delay period of time (e.g. 20 seconds or more) where the accelerometer80does not detect movement before activating the permit device50from sleep mode to active mode. The amount of minimum delay period of time may be adjusted by the user, organization or other third-party by programming the microprocessor67.

When the vehicle14is determined by the microprocessor67and/or the accelerometer80to be moving (i.e. not parked), non-essential electronic devices are deactivated to conserve electrical energy within the energy storage device65. For example, when the vehicle14is parked, the GPS receiver82, the RF transceiver84and the RFID device86are preferably deactivated to prevent unnecessary power consumption. However, when the vehicle14is determined by the microprocessor67and/or the accelerometer80to be parked, then the GPS receiver82, the RF transceiver84and the RFID are activated.

Alternatives to the accelerometer80may be utilized such as communication between the permit device50and the speed sensors of the vehicle14, the GPS receiver82and the like. However, all of these technologies require additional electrical power consumption and are not preferred since they require either a larger energy storage device65, direct electrical powering of the permit device50and/or increased replacement of the energy storage device65. For example, the GPS receiver82may be activated to detect whether the vehicle14is moving or not similar to the accelerometer80(including using the minimum delay period of time).

The scanner70is preferably a handheld and portable device that is used by an inspector or other personnel managing the parking lot to manually inspect a vehicle14parked in a parking space11that has not been automatically verified by the management server40. Independent verification of the vehicle14prior to parking enforcement actions being taken is important to prevent an authorized vehicle14from receiving a wrongful parking enforcement action (e.g. ticket, towing) simply because the permit device50was not able to communicate with the management server40or other issue.

The scanner70may be comprised of any electronic device capable of wirelessly communicating with the permit device50to acquire the identification of the permit device50. Various wireless technologies may be utilized for the scanner70to communicate with the permit device50such as but not limited to near field communications (NFC), Bluetooth and the like.

Once the identification of the permit device50is acquired, the identification data and any other data acquired from the permit device50is then communicated to the management server40via the telecommunications network19from the scanner70for verification by the management server40. Alternatively, the scanner70may communicate the data acquired to the management server40“offline” periodically. If the management server40verifies that the permit device50is authorized for the parking space11, the management server40communicates to the scanner70which is then displayed on a display screen of the scanner70that the vehicle14is authorized to park within the parking space11(if not authorized, the scanner70will display to the inspector that the vehicle14is not authorized). Alternatively the management server40may only indicate which parking space11the vehicle14with the permit device50is allowed to park within and the inspector then independently determines if the vehicle14is authorized to park within the parking space11. If the vehicle14is not authorized to park within the parking space11, the inspector then may take appropriate action such as ticketing the vehicle14, towing the vehicle14, securing wheel clamps and the like.

H. Telecommunications Network

The present invention may be utilized upon any telecommunications network19capable of transmitting data including voice data and other types of electronic data. Examples of suitable telecommunications networks19for the present invention include but are not limited to global computer networks (e.g. Internet), wireless networks, cellular networks, satellite communications networks, cable communication networks (via a cable modem), microwave communications network, local area networks (LAN), wide area networks (WAN), campus area networks (CAN), metropolitan-area networks (MAN), and home area networks (HAN). The present invention may communicate via a single telecommunications network19or multiple telecommunications networks19concurrently. Various protocols may be utilized by the electronic devices for communications such as but not limited to HTTP, SMTP, FTP and WAP (Wireless Application Protocol). The present invention may be implemented upon various wireless networks such as but not limited to 3G, 4G, LTE, CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, REFLEX, IDEN, TETRA, DECT, DATATAC, and MOBITEX. The present invention may also be utilized with online services and internet service providers.

The Internet is an exemplary telecommunications network19for the present invention. The Internet is comprised of a global computer network having a plurality of computer systems around the world that are in communication with one another. Via the Internet, the computer systems are able to transmit various types of data between one another. The communications between the computer systems may be accomplished via various methods such as but not limited to wireless, Ethernet, cable, direct connection, telephone lines, and satellite.

I. Operation of Invention

In use, a plurality of parking sensors30are positioned with respect to each of the parking spaces11to be managed as illustrated inFIGS. 1 and 2of the drawings. In an alternative embodiment, the present invention does not utilize parking sensors30to detect the presence of a vehicle14within the parking space11and instead relies upon the permit device50to communicate with the management server40to verify the parking credentials for the permit device50and corresponding user.

The user acquires the permit device50and acquires the necessary parking permit(s) which are required by the user to park within the desired parking spaces11. The user then positions the permit device50in the window16of the vehicle14and preferably attaches the permit device50to the interior of the windshield of the vehicle14as illustrated inFIG. 1of the drawings. The user drives the vehicle14as they normally would wherein the accelerometer80detects movement of the vehicle14and therefore determines that the vehicle14is not parked.

2. Detection of Vehicle by Parking Sensor.

Once the user identifies a parking space11to park in, the user drives the vehicle14into the parking space11and stops the vehicle14as shown inFIG. 2of the drawings. The parking sensor30associated with the parking space11detects the parking of the vehicle14in the corresponding parking space11and after such detection notifies the management server40that a vehicle14is parked within the parking space11thereby activating a verification system20for the management server40to determine if the vehicle14is identifiable and has the required parking credentials to park within the parking space11. In particular, after detection of the vehicle14, the parking sensor30transmits sensor data which includes a sensor identifier (e.g. Sensor #123456789) to identify the parking sensor30, a sensor time stamp indicating the time (e.g. 12:43 pm) the vehicle14was parked in the parking space11and/or date (e.g. Nov. 1, 2013) the vehicle14was parked in the parking space11.

The sensor data may also include additional data such as an image of the vehicle14recorded by a camera within the parking sensor30, weather conditions (e.g. temperature), ambient light conditions and related information. Once the management server40is notified via the sensor data that a vehicle14is in a managed parking space11, the management server40attempts to determine if the vehicle14is allowed to park in the parking space11or not.

3. Detection of Parking of Vehicle by Permit Device.

Concurrently with the detection of the vehicle14by the parking sensor30, the permit device50determines that the vehicle14is parked because of the lack of motion of the vehicle14(i.e. determines the motion state of the permit device50using the accelerometer80and/or the GPS receiver82). As illustrated inFIG. 7, after no motion is detected for a period of time greater than X (e.g. 20 seconds), the microprocessor67determines if a gateway device32is present to communicate the vehicle data to such as via the RF transceiver84. Once the vehicle14is determined to be parked by the permit device50, a permit time stamp is saved recording the time and date for when the vehicle14was determined to be parked.

If the microprocessor67determines that a gateway device32is not present, then the permit device50remains in sleep mode to conserve electrical power. Alternatively, if the permit device50is activated and attempts to communicate with a local gateway device32associated with the parking lot and fails to communicate with a gateway device32within X attempts (e.g.9attempts) then the permit device50is deactivated to sleep mode as shown inFIG. 8of the drawings.

If a gateway device32is present and/or if the permit device50includes an RF transceiver84that is capable of directly communicating with the telecommunications network19(e.g. a transceiver capable of communicating with a cellular telephone system), then the permit device50is activated to active mode thereby activating the location sensing system to determine the location of the vehicle14and the communication system to allow for communication with the management server40. In particular, the GPS receiver82within the permit device50is activated to determine the location of the vehicle14and the current time. The vehicle data is communicated from the permit device50to the management server40by the RF transceiver84. The vehicle data transmitted to the management server40includes the permit time stamp (e.g. 12:44 pm), the permit identifier (e.g. Permit #987654321) and the location of the vehicle14. Once the vehicle data has been properly transmitted, the permit device50preferably goes back into a lower energy consumption sleep mode until the vehicle14is moving again.

If the management server40receives the vehicle data within a required amount of time, the management server40then compares the vehicle data provided by the permit device50with the sensor data provided by the parking sensor30to verify if the vehicle14is authorized to park within the parking space11. In particular, the management server40utilizes the sensor data to identify the parking space11(including location of the parking space11) and then compares the vehicle data (including the location of the vehicle14) to determine if the vehicle14is parked in (or near) the parking space11. If an exact match is not found solely by location, the management server40may also compare vehicle data that is near (e.g. within 30 feet) of the parking space11and compare the sensor time stamp with the permit time stamp to determine if they are close enough (e.g. within 5 minutes of one another) to be a match.

If an exact match is found for a permit device50and the parking space11(or a permit device50is determined to be close enough physically and the time stamps are close enough), then the management server40assumes that the permit device50is the device that is within the vehicle14that parked within the parking space11. The management server40then determines if the permit device50(and the corresponding user) has the proper parking credentials to park within the parking space11. If the management server40determines that the user is allowed to park within the parking space11, the management server40then updates its records accordingly and waits for the vehicle14to be detected exiting the parking space11.

If the permit device50is not verified to be allowed in the parking space11or if no permit device50is determined to be associated with the parking space11, the management server40notifies an inspector via a message (e.g. automated telephone call, e-mail, text message) that a potentially unauthorized vehicle14is parked in the parking space11. The management server40further notifies the inspector of the location of the parking space11and the time the vehicle14parked within the parking space11. The inspector then manually inspects the vehicle14and the corresponding permit device50to determine what action, if any, is required as discussed below.

5. Detection of Vehicle Exiting the Parking Space.

When the vehicle14is moved from the parking space11, the accelerometer80detects the movement and switches the permit device50from the sleep mode to the active mode. The permit device50communicates through the gateway device32that the vehicle14is moving and is leaving the parking space11at the exit date and exit time (along with the device identifier). The management server40records the same within the database and the user may be billed accordingly if a charge applies for the time for parking in the parking space11. In addition, the parking sensor30detects the vehicle14exiting the parking space11and also notifies the management server40to act as a secondary verification system20by submitting the exit time and exit date detected (along with the sensor identifier) so the management server40may verify that the vehicle14has left the parking space11. If only the permit device50detects that the vehicle14has left but not the parking sensor30, a manual inspection may be requested to determine if the vehicle14has left or not to avoid fraud issues.

If the management server40does not receive vehicle data from a vehicle14located within the parking space11associated with the parking sensor30that sent the sensor data to the management server40that a vehicle14had parked in the parking space11within a period of time (e.g. 9 minutes), the management server40then notifies an inspector or other personnel that a vehicle14is parked in the corresponding parking space11without being verified by the management server40and a manual inspection is required. The inspector or other personnel travels to the parking space11and performs a visual inspection to see if the permit device50indicates that the vehicle14is allowed in the parking space11. The inspector further uses the scanner70to acquire the device identifier and user information from the permit device50which is then communicated to the management server40(or alternative viewed by the inspector for manual verification). The inspector takes the necessary actions if the vehicle14is not authorized for the parking space11(e.g. ticketing, towing, wheel clamp). If the vehicle14is authorized, the inspector notifies the management server40that the vehicle14is authorized along with identifying the permit device50.

Any and all headings are for convenience only and have no limiting effect. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. All publications, patent applications, patents, and other references mentioned herein are incorporated by reference in their entirety to the extent allowed by applicable law and regulations.

The invention is described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to example embodiments of the invention. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, respectively, can be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some embodiments of the invention. These computer-executable program instructions may be loaded onto a general-purpose computer, a special-purpose computer, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, embodiments of the invention may provide for a computer program product, comprising a computer usable medium having a computer-readable program code or program instructions embodied therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks. Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, can be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.

The present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof, and it is therefore desired that the present embodiment be considered in all respects as illustrative and not restrictive. Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains and having the benefit of the teachings presented in the foregoing description and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although methods and materials similar to or equivalent to those described herein can be used in the practice or testing of the present invention, suitable methods and materials are described above. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.