Patent Application
20220148427
© 2022 Citifyd, Inc. A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 37 CFR § 1.71(d).
This disclosure relates to vehicle parking payment processing and, in particular, to a dynamic vehicle parking management platform that is based on existing infrastructure and vehicle driver behavior to simplify parking fee payment transactions. The disclosed parking management platform implements wireless communication technologies to free vehicle drivers from inconveniences of manual parking fee payment while creating business and marketing opportunities for local merchants to develop as customers vehicle drivers parking their vehicles in areas nearby the merchants' stores.
Millions of drivers park their vehicles daily on city streets, in parking lots, or in garage facilities. Municipalities for many years have been collecting and typically still collect parking fees from vehicle drivers making payments through use of mechanical or electronic parking meters. Municipalities use parking fee revenues to enforce integrated on-street parking policy, usually related to traffic and mobility management policies. Since its first deployment in 1936, the mechanical parking meter has undergone many innovations and improvements. All such devices are, however, costly for municipalities to install and operate and are either difficult or inconvenient for the vehicle drivers to use. Private providers of surface parking lot and parking garage facilities are staffed by either an on-site attendant to process parking permit tickets and collect parking fees or roving parking control attendants to ensure parking fee payment compliance. The manual collection of parking permit tickets and fee payments is labor intensive and costly to private parking providers.
What is needed is a dynamic parking management platform that implements a parking fee payment and collection system that simplifies the process of fee-based parking by vehicle drivers and the duties of parking control personnel, as well as reduces the cost of operation and management of (1) metered and non-metered on-street parking to municipalities and (2) parking lots and garage facilities to private providers.
The disclosed dynamic parking management platform is implemented in hardware and software and is based on the existing infrastructure and behavior of the users (vehicle drivers) and parking service providers (municipalities and their parking enforcement officers; private providers and their parking facility attendants; private individuals). (The terms “user” and “vehicle driver” are used interchangeably throughout the descriptions presented herein.) The disclosed system enables dynamic pricing of parking fees and dynamic setting of parking time limits, and thereby implementation of different revenue models, and paperless issuance of different types of parking permits by the municipalities or private providers.
Main components of the parking management platform include a mobile communication device (e.g., smartphone) App of a parking service provider (e.g., municipality or private parking provider), a parking (i.e., backend) server on which the parking service provider stores parking account and transaction information, and an auxiliary electronic ticket or “E-Ticket” device. The user creates an account that resides on the parking server by downloading the App to the user's mobile communication device and carrying out the account formation process. Thereafter, the user receives, in the mail from, or at a conveniently located authorized source, an E-Ticket device in the form of a credit card size display or radio signal beacon-emitting capable device. The user performing procedural steps presented by the interface of the App operating on the user's mobile communication device can set up a parking payment account with the parking service provider, provide credit (or debit) card information, and check at any time a statement of parking activities. Setting up a parking payment account is a one-time operation, which takes place during an initial use of the App. The parking server credits the accounts of all parking service providers who have subscribed to parking server operator services. The vehicle driver uses the App to communicate with and actuate the E-Ticket device and the parking account established with and residing on the parking server to effect a parking fee payment transaction between the vehicle driver's credit card and the parking account.
In all cases of parking provider services, the App informs the vehicle driver about locations of different time-limited parking zones; locations of parking garages, parking lots, street parking areas, and privately owned parking areas (e.g., a homeowner's driveway); different garage facility, parking lot, and street parking rates before parking; and the amount of time remaining before expiration of parking time allowed under a time limit. The App also informs the vehicle driver about the location of the vehicle after parking; the amount of elapsed parking time; and, with a predetermined amount of parking time remaining (e.g., 10 minutes), the amount of walking time needed to return to the parked vehicle. The App can cause the E-Ticket device or the mobile communication device itself to emit a beacon that causes a parking garage barrier gate to open at the start of a parking session. The App also uses encryption technology to transfer data, activate and deactivate the E-Ticket device, and communicate to the parking server the amount of time the vehicle occupied the parking space.
The parking management platform implements a lock and key feature that affords a highly secure parking transaction. Secure parking transactions are achieved by the use of two separate devices, the E-Ticket device and the mobile communication device, operating in proximity to each other. When they are in proximity to each other, these two devices communicate over a short-range wireless communication link and exchange identification information to achieve secure device pairing that enables connection to the parking servers. Forming a connection with the parking servers enables a vehicle driver to carry out a parking related transaction. No parking related transaction can be performed when the E-Ticket and mobile communication devices are separated from each other by a distance that is outside the connectivity range of the short-range wireless communication link. A lost or stolen E-Ticket device or mobile communication device cannot, therefore, itself be used to perform a parking related transaction because no connection to the parking servers can be achieved.
The parking management platform enables an event based vehicle parking service. Operational features afforded by the vehicle parking service include Waitlist AutoBuy, which automatically purchases a parking space if one becomes available before an event; Waitlist Notification, which notifies a user when a parking space becomes available; Cancel and Buy, which allows a user to cancel a purchased event parking pass before a pre event deadline and later repurchase the same event parking pass; Transfer to Another Person, which allows transfer of a parking pass to another person; Transfer to Another Event, which allows transfer of an event parking pass for use at a future event; Redemption of Transferred Parking Pass, which allows a recipient of a transferred parking pass to redeem it without payment; and Attendance Confirmation, which allows a user to confirm attendance or to exchange, transfer, or cancel the event parking pass for a different event parking pass.
The parking management platform makes possible a service that frees a vehicle driver from all hassles and inconveniences of paying for on-street, surface lot, or garage facility parking. The parking fee payment service enabled by this parking management platform is implemented without (1) changes to the street parking infrastructure of and management process practiced by a municipality or (2) disruptive changes to private parking lot or garage facility operations. The disclosed parking management platform is configured such that municipalities could eventually eliminate most, if not all, of their parking meter machines.
Additional aspects and advantages will be apparent from the following detailed description of preferred embodiments, which proceeds with reference to the accompanying drawings.
System 10 also includes an auxiliary E-Ticket device 30, a block diagram of which is shown in greater detail in
A communication link 3630-38 between E-Ticket device 30 and barrier gate transceiver 38 may also be established by emission of a beacon signal from transceiver 38. This beacon signal is preferably implemented in the ZigBee® communication protocol because it exhibits higher security and lower power consumption as compared with the security level and power consumption of other currently available wireless personal area networks.
For implementations in which a beacon signal is not in use, E-Ticket device 30, by way of communication link 34, receives from mobile communication device 20 a start timer command to track vehicle parking time, information about maximum allocated parking time, and current parking time information for presentation on a display surface 44. When in use in a parked vehicle, E-Ticket device 30 remains stationary after its placement inside the parked vehicle and at a location (e.g., rests on the vehicle dashboard or against the vehicle window) in plain view of a parking patrol officer or parking service attendant tasked with reading parking time information presented on display surface 44. An option would be to integrate the functionality of E-Ticket device 30 by installing it into a vehicle dashboard instrument console, at a location where display surface 44 would be visible from outside the vehicle. Parking time information includes parking time remaining before expiration of the vehicle parking time allowed under the time limit specified for the parking area or any grace period provided after expiration of the vehicle parking time.
For implementations in which a beacon signal is in use, either E-Ticket 30 emits beacon signal for reception by barrier gate transceiver 38 or barrier gate transceiver 38 emits a beacon signal for reception by E-Ticket 30 to initiate the process of opening a parking entrance gate as a vehicle enters a gated parking lot or garage. The App operating on mobile communication device 20 could also cause emission of a beacon signal for acquisition by barrier gate transceiver 38 or enable reception of a beacon signal emitted by barrier gate transceiver 38 to establish a communication link 3620 to initiate the process of opening the parking entrance gate. Mobile communication device 20 cannot, however, establish communication link 3620 in the absence of connectivity with E-Ticket device 30. Unless they are in proximity to each other within the connectivity range of the wireless connection, E-Ticket device 30 and mobile communication device 20 cannot achieve a device pairing connection and, therefore, cannot produce signals that cooperate to initiate a parking transaction. This ensures, for example, that the barrier gate cannot be opened as a person carrying mobile communication device 20, and while leaving a parking lot or garage and leaving behind E-ticket device 30 in the parked vehicle, walks by barrier gate transceiver 38.
Each of the beacon signals emitted, or produced in response to beacon signals emitted by barrier gate transceiver 38, by E-Ticket 30 to establish communication link 3630-38 and mobile communication device 20 to establish communication link 3620 carries an identification number associated with the vehicle driver's parking account. The identification number is transmitted by way of wireless communication link 46 to parking servers 12 to verify the parking account, obtain all pertinent information, open the account, and start a timer to count the amount of parking time used. E-Ticket device 30 also counts the amount of elapsed parking time and presents it for observation on display surface 44. Parking servers 12 transmit through communication link 46 a gate opening signal to barrier gate transceiver 38, upon verification of the parking account, and parking fee information to mobile communication device 20.
E-Ticket 30 emits a beacon signal that is transmitted over communication link 3630-40 for reception also by communication device 40 to display to a parking patrol officer or parking service attendant the vehicle driver's account identification number and to transmit the vehicle driver's account identification number by a wireless radio communication link 48 to parking servers 12. Each of wireless communication links 46 and 48 communicates preferably, but not necessarily, through Internet Protocol (IP) technology. The beacon signal emission capability enables a parking patrol officer parking service attendant to obtain information about the vehicle parking time without having to view display surface 44 on E-Ticket 30. Using beacon signal emissions can eliminate a need for and cost of display surface 44 on E-Ticket 30. E-Ticket device 30 constructed without display surface 44 would be preferably equipped with light-emitting diodes (LEDs) functioning as indicators of operational status, parking time expiration, grace period operation, or other such status conditions.
The vehicle driver returning to the parking area uses the App operating on mobile communication device 20 to send to E-ticket device 30 a stop timer command and to signal parking servers 12 to stop the timer and obtain the total parking time. Parking servers 12 thereafter conclude the transaction by closing the parking account and applying the parking fee charge to the vehicle driver's credit card on file.
Microcontroller 42 coordinates the communication of information delivered to and received from mobile communication device 20, manages storage of information in memory sites 50, and processes information for display on display surface 44. E-Ticket device 30 has its own electrical power supply, including a battery 52, power control circuitry 54, and a voltage regulator 56. Communication signal interface 32 is preferably a ZigBee® wireless chipset, and a balun 58 provides an impedance match for the antenna in the module containing wireless chipset 32. A thermistor 60 monitors the ambient temperature of E-Ticket device 30 and enables microcontroller 42 to deactivate E-Ticket device 30 when it is exposed to extreme temperatures.
The following describes in detail the operation of system 10 when a vehicle driver undertakes to establish a parking transaction account on system 10, use system 10 to locate and pay for use of a parking area, and check parking activity on the parking transaction account record.
With reference to
With reference to
With reference to
With reference to
With reference to
A weak cellular telephone signal or other cause of temporary interruption of connectivity between mobile communication device 20 and parking servers 12 over wireless communication link 18 can result in a delay in parking transaction processing by parking servers 12. A vehicle driver timely making payment for parking could become a victim of the resulting delay in payment processing by parking servers 12 and be vulnerable to receiving an overdue parking time citation. An improperly issued parking citation can result from a parking patrol officer's using portable communication device 40 to perform over communication link 48 a search of parking servers 12 for parking transaction information. The result received from parking servers 12 would reflect not up-to-date and therefore inaccurate parking payment information caused by the payment processing delay. An improperly issued citation for an overdue parking time violation can, however, be reconciled because the vehicle driver's use of the App in the process of paying a parking charge is recorded in memory stores of mobile communication device 20. The App operates to maintain pendency of the vehicle driver's attempted payment transaction until connectivity to parking servers 12 is established and the parking payment process is completed. Parking servers 12 receive from mobile communication device 20 timestamp information demonstrating the vehicle driver's attempt at timely payment for parking. This timestamp information can be used to reconcile the delay and dismiss the parking violation.
With reference to
The operational procedures implemented in system 10 and the operation of E-Ticket device 30 afford flexibility that allows a municipality to offer a grace period (e.g., 10-15 minutes) after the expiration time for the vehicle driver to return to the vehicle before a parking violation is recorded. The municipality can charge a larger fee for this grace period, thereby generating more revenue for the municipality yet reducing the violation fine the vehicle driver would have incurred.
Recognizing the locations of the vehicle and mobile communication device 20, system 10 can calculate a return time the vehicle driver would need to walk back to the vehicle. System 10 can add to the remaining parking time the calculated return time as reminder time to allow the vehicle driver to return to the vehicle before the parking time has expired.
The App can also drop a pin and recognize the location of mobile communication device 20 to identify the vehicle location by GPS and assist the vehicle driver to find the vehicle as the driver attempts to return to the vehicle.
Upon activation, the App will also provide the vehicle driver with information about activities and business promotions within a short distance from (e.g., 1.5-mile radius) of the parking area. As shown in
With reference to
System 10 is also capable of an automatic start of a parking transaction based on separation distance of mobile communication device 20 and E-Ticket device 30 when connectivity between them is lost and navigation system 16 detects movement of mobile communication device 20 only. This is accomplished after initiation of a parking transaction, and when the pairing connectivity is lost and navigation system 16 detects movement of mobile communication device 20. Parking server 12 provides to mobile communication device 20 the start timer command and thereby starts a parking transaction.
With reference to
Display portion 82 has on its rear side a large slidable ON/OFF switch mechanism 86 that provides secure activation of E-Ticket device 30 by the vehicle driver.
To save power and thereby extend battery life, microcontroller 42 of E-Ticket device 30 at specified time intervals (e.g., one-minute intervals) momentarily turns on to advance its timer. Display surface 44 presents all information preferably on a bright white background for viewing at a glance, even in bright sunlight conditions.
The following describes, with reference to sequences of screenshots showing information displayed on mobile communication device 20 and display surface 44 of E-Ticket device 30, two scenarios of vehicle parking and parking fee payment processing by system 10.
E-Ticket device 30 has a completely dark display surface 44 during each of the first six procedural steps represented by
E-Ticket device 30 has a completely dark display surface during each of the first 19 process steps represented by
Each of
The disclosed parking management platform forms a basis for business-to-business commerce in marketing local sale of goods and services, as demonstrated by the following example.
A beacon-emitting device 102 positioned at a store entrance 104 or forming part of a wireless local area network broadcasts a beacon signal 106 that carries store identification information (“store ID”). (A store having multiple entrances would be equipped with one beacon-emitting device 102 at each store entrance.) A customer walking through store entrance 104 and carrying mobile communication device 20 starts the following process. Mobile communication device 20 receives beacon signal 106, which wakes up the App operating on mobile communication device 20. The App responds to beacon signal 106 by sending to parking servers 12 a ping signal carrying the store ID and thereby attributing to merchant 68 an instance of a customer visit to store 100. The above-described process is analogous to mouse click event attribution to a vendor whose online advertisement is acknowledged by a website visitor's mouse click.
The following parking validation scenario relates to attributing to a merchant an instance of a customer purchasing an item or service at store 100.
A customer making a purchase approaches a sales desk 108 inside store 100. A store clerk scans across a QR code reader a store-specific QR code that can indicate the purchase price paid and thereby assign a parking validation level. The QR code information is sent by a message through wireless communication link 66 to parking servers 12 to acknowledge a parking credit payable by merchant 68 for store 100.
As the vehicle approaches a parking attendant to enter a parking facility, or as the vehicle driver completes a transaction with a merchant and seeks to redeem a credit, the vehicle driver brings mobile communication device 20 in proximity (3-5 ft; 0.914-1.524 m) to the parking attendant or merchant's communication device 62, such as a smartphone or tablet computer. Using wireless communication technology, such as Bluetooth® or NFC, the vehicle driver's mobile communication device 20 transmits over a communication link 3662 a redemption or authorization code to attendant/merchant device 62.
Attendant/merchant device 62 uses the redemption or authorization code to authenticate and retrieve from backend servers 12 over wireless communication link 64 all pertinent information about the vehicle driver, transaction, and redemption. Upon authentication of the transaction and to authorize entry to a parking facility, backend servers 12 communicate with attendant/merchant device 62 over wireless communication link 64 and generate an authorization message for the attendant to allow the vehicle to enter the parking facility. In the case of redemption, again upon authentication of the transaction and the redemption code by backend servers 12, the vehicle driver's account 75 is credited for the redemption amount over wireless communication link 70 and the merchant account 68 is debited over wireless communication link 66 for that amount.
Backend servers 12 then send a notification over wireless communication link 18 to the vehicle driver's mobile communication device 20 informing the vehicle driver about the amount of credit to vehicle driver account 75.
Screen A shows the Home page. A user/vehicle driver (hereafter “vehicle driver”) activates a search for parking through Home page Screen A (link 3). The vehicle driver also has an ability to activate a search for parking through a Menu page Screen B from Home Screen A (link 1).
Screen B shows the Menu page. The vehicle driver can select different aspects of the parking transaction service from Menu page Screen B. Many follow-on screens can link to Menu page Screen B and return to the follow-on screens (links 1 and 2).
Screen C shows a Parking Time Selector (Filter), which allows the vehicle driver to specify the minimum amount of time needed to park. Thus, only relevant filtered parking spaces appear on the subsequent screens (link 4).
Screen D shows a Map of Parking Spaces/Location nearby the vehicle driver. Screen D shows, based on the minimum amount of parking time selected, the location and relevant filtered parking spaces nearby the vehicle driver.
Screen E shows a Parking Spaces/Location List. The vehicle driver can toggle between the Map Screen D and Screen E to view in list form parking spaces and their locations (link 5). The list shown on Screen E is organized based on the proximity of the Parking Spaces/Locations relevant to the vehicle driver, as shown on Screen D, or to the destination, as shown on Screen G. The parking transaction service organizes the list based on the closest to the farthest, or least expensive to the most expensive, relevant filtered space/location. The vehicle driver can also select to view the list as a default screen in a setting/customization menu. In any of these formats, if they are available, the vehicle driver also can toggle for access the relevant filtered nearby on-street parking time zones, such as shown on Screen R (link 17).
Screen F shows Parking Spaces/Location Designation Selection. If the vehicle driver needs a parking space located away from the existing location of the vehicle, the vehicle driver can enter a selected destination on a map shown in Screen F by bringing about a keyboard on Map Screen F (links 10 and 11).
Screen G shows a Parking Spaces/Location Map of the Destination. By entering a selected location on Screen F, the vehicle driver causes display on a map showing the selected destination and all relevant filtered parking spaces (private areas, garage facilities, and parking lots) around it. Based on settings by the vehicle driver, this information can be shown as a Map G or as a List E. In any of these formats, if they are available, the vehicle driver can also toggle (link 17) or access, the relevant filtered nearby on-street parking time zones as shown on Screen R.
Screens H, I, and J show Parking Space/Location Information. By touching the desired parking space/location icon, the vehicle driver can obtain detailed information about the parking space/location (links 6, 12, and 18). This information includes, but is not limited to, the address, parking rate/fee, and time limit, number of available parking spaces/locations, and enforcement methods and organizations, restrictions, requirements or instructions needed to park, and any photograph of the parking space/location to help identify the desired parking space/location.
Screen K is a Parking Space/Location Photograph. By touching the photograph (or map icon) on Screens H, I or J, the vehicle driver can toggle between a larger Photograph K or a map of the desired parking space/location (link 13).
Screens L, M, and N show Parking Space/Location Selection and directions. By tapping the information box of the desired location, the App provides the vehicle driver a map that identifies the desired space/location (using an icon). The vehicle driver can now choose to get directions to the identified space/location, as indicated on Screens O, P, or Q and link 8, 20, or 15, or just start the meter shown on Screen T and links 9, 16, 21 and 22 for the identified parking space/location.
Screens O, P, and Q are Parking Space/Location Maps showing Directions. By tapping the direction button on Screens L, M, or N, the vehicle driver causes the App to provide directions to the desired parking space/location (links 8, 20, and 15).
Screen R shows an On-Street Parking Time Zone Location Map. If available, the vehicle driver can toggle or access the relevant filtered on-street parking time zones around the destination (link 17).
Screen S shows selection of On-Street Parking Time Zone. In case of close proximity of several on-street parking time zones, the App provides the vehicle driver alternative time zones within the area around the destination. The vehicle driver can select the appropriate parking time zone relating to the parking space before activating the meter, which is shown on Screen T (link 22).
Screen T shows a Parking Meter Start Selector, which allows the user to start the meter for the selected parking space. The meter can be set to show the amount of time used (counting up) or time left (counting down), or, by touching the center selection of the meter on the App, to display the amount of money spent as of that moment, on the parking time elapsed (counting up).
Screen U shows Parking Meter Status and provides the vehicle driver an opportunity to consider Local Business Offers. Once the meter has started, the vehicle driver can continuously see the status of parking time and expenditure (link 23). At the moment the meter starts, the App also allows the vehicle driver to search around the location of the parking space for relevant offers from nearby businesses and merchants (the setting menu allows the vehicle driver to set the search radius size). Link 30 points to a local rewards flow diagram show in
Screen V shows a Parking Meter Expiration Alert. Based on the setting by the vehicle driver, system 10 sends a text alert to the vehicle driver's smartphone at certain time intervals (e.g., every 5 minutes) reminding the vehicle driver about the expiration of the parking space time (link 24). This alert also calculates and adds the amount of walking time to the location of the parked car to give the vehicle driver adequate time to remove the car from the parking space.
Screen W shows Parking Meter Status (Find Car) and (Pay Now). Once the vehicle driver decides to return the vehicle, the “Find Car” button shows a Map Screen Y (link 26) indicating the location and direction to the parked vehicle. The vehicle driver can pay for the time used (Pay Now button) and drive off (link 25). However, in certain instances, before payment is made, system 10 may present an opportunity to the vehicle driver to contribute money to a charity. The amount of the charitable contribution is added to the final parking payment and charged to the vehicle driver's account. The vehicle driver has the ability to cancel the charitable contribution before confirming final payment. Link 29 points to a fundraising flow diagram shown in
Screen X shows Final Parking Payment. Before a parking payment is charged to the vehicle driver's account, a final payment amount and details of the parking transaction are displayed for confirmation. The vehicle driver has the ability to cancel payment and continue parking (if more time is allowed by the parking provider), cancel any charitable contribution, or confirm final payment by tapping the “Confirm” button (link 27).
Screen Y shows a Find Parked Car Map for a vehicle driver needing directions to the parking space. The vehicle user's tapping the “Find Car” button on Screen W causes display of a map showing the location of and directions to the vehicle driver's parked car. The vehicle driver can then go to Screen W to activate payment (link 26).
Screen Z shows completion of Parking Payment Transaction. Once the vehicle driver confirms a parking transaction amount, a “Thank You” message appears on Screen Z showing the final transaction amount and the details of a transaction (link 28). At this time, an email and text with all transaction details are sent to the vehicle driver's account.
Screen U-A shows a Desired Activity (local). On Screen U-A, the vehicle driver can select an activity from a list of activity categories to do in one or both of the vicinity of the vehicle driver's parking space and current location, and check for special offers (local rewards) within the selected activity category. The vehicle driver also has the ability to go to Menu page Screen B (link U-1), which is shown in
Screen U-C shows a selection of Local Rewards and Offers. Once the vehicle driver has selected the desired activity category (link U-3), the vehicle driver can check from a list of nearby businesses the relevant information about, advertising by, and special offers from these businesses. The special offers include credits offered to the vehicle driver's parking transactions or credits as points to be used for other transactions. The relevant information about these businesses includes user ratings of them.
Screen U-D shows Directions to Selected Business/Location (Map). By tapping and selecting the desired offer, advertising, or information from the viewed list U-C (link U-4), the vehicle driver causes generation of a map with directions to the selected business. The map can also contain pictures and more information about the business or promotional offer.
Screen U-E shows presentation of a Redemption Number/Selected Business. To redeem the offer, the vehicle driver taps Screen U-D or a specified area of Screen U-D to generate a redemption code, which is one or both of a number and a barcode (link U-5). This redemption code is specific to the selected offer, the business (and its location) creating the offer, and the vehicle driver redeeming the offer. Screen U-E is also the place where the vehicle driver can select to jump/connect into the business' owned App, website, or other business-specific service.
Screens U-F and U-G show Offer Redemption/Crediting the vehicle driver. Once a transaction between the vehicle driver and the business takes place, the business can credit the vehicle driver by a) entering the redemption number into the system/App on a smart, connected device, such as a smartphone, tablet computer, or cash register, as shown on Screen U-F (link U-6), b) by scanning the generated barcode, as shown on Screen U-G (link U-7), and c) by communicating with the vehicle driver's smartphone by wireless technology (e.g., Bluetooth® or NFC) and retrieving the redemption code, at Screen U-G.
Screen U-H shows Transaction/Credit Notification to Vehicle Driver. Once one or both of a transaction has been completed and a credit has been applied to a vehicle driver's account, a text notification is sent to the vehicle driver's telephone number for confirmation, as shown on Fig. U-H (link U-8). An e-mail notification is also sent to the vehicle driver's e-mail account for further confirmation and record keeping.
Screen U-I shows Transaction/Credit Notification to Business. Once one or both of a transaction has been completed and a credit has been applied to a vehicle driver's account, a record of the transaction and credit is also applied to the list of such activities in the business' accounts, as shown on Screen U-I (link U-9).
Screen W-A shows an opportunity for the vehicle driver to make a Charitable/Nonprofit Contribution. On Screen W-A, the vehicle driver can select from among different contribution amounts a contribution amount that is to be credited to the charity or nonprofit organization displayed on Screen W-A. These fundraising campaigns have a limited duration and are replaced by other campaigns during the year. The vehicle driver selects the contribution amount, taps the “Add” button, and sees on Screen W-B the final parking fee plus the contribution amount (link W-1).
Screen W-B shows Final Parking and Charitable Contribution Payment. Before the final parking and charitable contribution payment is charged to the vehicle driver's account, final payment amount and details of the parking transaction are displayed on Screen W-B for confirmation. The vehicle driver has the ability to cancel this payment and continue parking (if more time is allowed by the parking provider), cancel any charitable amount (link W-2), or confirm final payment by tapping the “Confirm” button (link W-3).
Screen W-C shows the Final Parking Payment. A vehicle driver deciding to forego any charitable contribution simply taps on Screen W-A the “Next Time” button and views the final parking fee on Screen U-C (link W-4).
Screen W-D shows completion of Parking Payment Transaction. Once the vehicle driver confirms a parking transaction amount, a “Thank You” message appears on Screen W-D, showing the final transaction amount and details of the transaction (links W-3 and W-5). At this time, an e-mail and a text message providing all of the transaction details are sent to the vehicle driver's account.
The activities described with reference to
Screens O-A and O-D show Parking Space/Location Maps for, respectively, off-street and on-street zone parking. When the vehicle driver has selected the desired parking space/location in proximity to or a substantial distance from the destination, the vehicle driver may need directions to get to the selected off-street space, as shown on Screen O-A, or on-street zone, as shown on Screen O-D. In that case, the vehicle driver taps the direction button on one of Screens O-A and O-D, leaves the App of system 10, and is directed to a Google® map or Apple® map App (link O-1).
Screens O-B and O-E show Parking Space/Location Directions for, respectively, off-street and on-street zone parking. Google® and Apple® maps (or similar maps) have the ability to provide the vehicle driver visual and turn-by-turn directions that guide the vehicle driver to the destination.
Screens O-C and O-F show Return to App of system 10 for, respectively, off-street and on-street zone parking. Once the vehicle driver has reached the destination through the use of GPS, the map alerts the vehicle driver about reaching the destination. This prompts and creates a visual display/button on Screens O-C and O-F. This button, when actuated by tapping, takes the vehicle driver back to the App of system 10 to start the timer (link O-3). This feature creates a seamless transition between the two different Apps (i.e., between the App operating on system 10 and the Apps of Google® and Apple® maps), thereby eliminating the vehicle driver's need to close and open different Apps.
Screen O-G shows On-Street Parking Time Zone Selection. If the vehicle driver is parking the vehicle in an on-street zone, a parking time zone needs to be selected. To select the appropriate time zone, and in the case of close proximity of several on-street parking time zones, the App provides the vehicle driver alternative time zones within the on-street parking area. The vehicle driver can select the appropriate parking time zone relating to the selected parking space before activating the meter, which is shown on Screen O-H (link O-4).
Screens O-H and O-I show Parking Meter Start Selector and Status. Screen O-H allows the vehicle driver to start the meter for the selected parking space (link O-5). Once the meter has started, the vehicle driver can continuously see the status of the parking time and expenditure, as shown on Screen O-I, until the vehicle driver moves the vehicle from the parking space (link O-6).
The disclosed dynamic parking management platform enables implementation of an open parking space count for either an open surface parking lot (parking lot) or a parking garage facility (garage facility). Determining an open parking space count necessitates detecting that a vehicle has entered and exited the parking lot or garage facility. Detecting that a vehicle has entered a parking lot or garage facility is determined by the dispensing of a parking ticket to the driver of the vehicle upon its entering the parking lot or garage facility. Detecting that a vehicle has exited the parking lot cannot be currently accomplished because there is no account of the vehicle driven out of the parking lot. Detecting that a vehicle has left the garage facility is accomplished by detection of opening of a barrier gate placed at the garage facility exit.
IR reflectance sensors 124 and 126 are mounted on bollard 39 in spaced-apart relationship to each other along the direction of travel of a vehicle either entering or exiting the parking lot. IR reflectance sensors 124 and 126 are set at a height on bollard 39 to detect the luminosity of the vehicle passing by them. The outputs of magnetometer 122 and of IR reflectance sensors 124 and 126 are applied to a microcontroller 128. Microcontroller 128 is powered by a photovoltaic cell 130, which preferably is a PRT-0031PV cell available from SparkFun Electronics. Microcontroller 128 determines from the output signal of magnetometer 122 whether an object detected at bollard 39 is a vehicle, and if the detected object is a vehicle, determines from the order of occurrences of the output signals of IR reflectance sensors 124 and 126 whether the detected vehicle is entering or exiting the parking lot.
An IR emitter 132 provides to microcontroller 128 an output signal representing the ambient light (e.g., whether night or day) in the area of the parking lot. The output signal of IR emitter 132 provides environmental background light information that microcontroller 128 uses to adjust the luminosity information provided by IR reflectance sensors 124 and 126 and thereby enable detection of a vehicle irrespective of the darkness of its color.
The timing sequence of the output signals of IR reflectance sensors 124 and 126 indicates to microcontroller 128 whether a vehicle passing by them is entering or exiting the parking lot. Microcontroller 128 keeps a running count of parked vehicles and, given the total number of parking spaces representing the parking lot capacity, calculates an open parking space count. An initial or confirmation count of parked vehicles may be entered by means of an input device to controller 128 by a parking lot attendant counting periodically on-site the number of vehicles parked in the parking lot.
A cellular radio 134, preferably implemented with code division multiple access (CDMA) digital cellular technology, is coupled to microcontroller 128 and operates in a data mode to transmit over wireless communication link 46 to parking servers 12 any one or all of the open parking space count, number of vehicles parked in the parking lot at a given time, and time of entry or exit of a vehicle. Cellular radio 134 is preferably a cellular module SARA-G350/U260/U270 available from u-blox AG.
The use of vehicle detection system 120 in the implementation of the disclosed dynamic parking management platform enables vehicle parking space inventory management of parking spaces available in parking lots and facilities having different parking ticketing systems. The parking management platform can, therefore, inform vehicle drivers where open parking spaces are available, irrespective of whether they are available on-street, in parking lots, or in parking facilities or of the type of parking ticketing system used. The use of vehicle detection system 120 enables solution of providing a maximum number of available vehicle parking spaces in a given spatial region with use of the disclosed dynamic parking management platform in combination with parking ticketing systems of different types.
System 10 is capable of using E-Ticket device 30 as a beacon to assist a user carrying mobile communication device 20 to find a vehicle the user parked in a parking lot or garage facility. E-Ticket device 30 placed in the parked vehicle emits a beacon signal carrying an identification code that is recognizable by mobile communication device 20 carried by the user. Mobile communication device 20 is capable of measuring signal strength of a received signal. The beacon signal emitted by E-Ticket device 30 operates as a homing signal, which is acquired by mobile communication device 20 measuring changes in signal strength of the beacon signal to assist the user to locate the parked vehicle.
The foregoing parking validation scenarios demonstrate that use by merchant 68 of the parking management platform to control parking validation empowers merchant 68 to interact with potential customers in the vicinity of the store and thereby create flash sale opportunities. Moreover, the advertising model enables a parking service provider such as parking operator 76 or municipality 78 to operate as an advertising source, selling advertising for a fee based on attribution for the number of visits or purchases by a customer of the store operated by merchant 68.
The use of vehicle parking encourages customer interaction with a merchant in at least two ways. The first way is that the driver of the parked vehicle is in the vicinity of the store location and thereby increases the likelihood that the vehicle driver will visit the store. This is in contrast to the less likely consumer demand that predictive commerce analysis expects from newspaper discount coupons, about which the potential customer becomes aware at a location a long distance from the store location. The second way is that a vehicle parked at a nearby area to the store effectively functions as an anchor for the vehicle driver, as compared to a pedestrian passing by the store location. A person walking down a street has comparatively little incentive or mobility impediment to stop and enter any given store along the walking route.
The disclosed parking management platform also enables event-based parking such as, for example, reservation-based parking. A parking reservation would be fungible in that a parking reservation made by a first vehicle driver may be transferred to a second vehicle driver. This can be accomplished by changing the parking reservation record from the cellular telephone number of the first vehicle driver to that of the second vehicle driver or by e-mail transmission of the parking reservation from the first to the second vehicle driver. A vehicle driver would be able to reserve and make prepayment for a parking area for a specified time on a specified date. Private individuals could also establish a private operator's account on backend servers 12 to make available private home driveway parking at specified times on certain days at a specified cost. Such an arrangement represents one way in which the disclosed parking management platform enables sale of a parking service that makes productive the otherwise unused capacity of an asset.
Use of the disclosed parking management platform over time can enable formulation of estimates of parking area availability based on historical experience. A large number of vehicle drivers using system 10 over time would establish trend lines of vehicles parked at certain times of day at specific regions of a locality.
The following describes in detail operational features afforded by the event-based vehicle parking service briefly described above. Several features characterize the selling of an event-based parking space as implemented on the disclosed parking management platform. These features include Waitlist AutoBuy, which automatically purchases for a user a parking space if one becomes available before an event; Waitlist Notification, which notifies a user upon an occurrence of an available parking space and how long the user has to claim it; Cancel and Buy, which allows a user to cancel a purchased event parking pass before a pre-event deadline and later repurchase the same event parking pass; Transfer to Another Person, which allows a user to transfer a parking pass to another person; Transfer to Another Event, which allows a user to transfer an event parking pass for use at a future event; Redemption of Transferred Parking Pass, which allows a recipient of a transferred parking pass to redeem the transferred pass without paying for it; and Attendance Confirmation, which sends to a user at a pre-event time threshold an attendance status inquiry that allows a user to confirm attendance or to exchange, transfer, or cancel the event parking pass for a parking pass for a different event.
A sale of an event based parking space starts by a user opening the App operating on mobile communication device 20. (The App is identified as “Citifyd” in the drawings described below.) The activities associated with each of the seven features defined above are described with reference to extensively annotated flow diagrams showing the interaction between the App and parking or backend server 12 of system 10.
Screen 4 shows a text message and Screen 6 shows a push notification reminding the user of the user's opting to AutoBuy purchase a parking pass and informing the user that an event parking space has been purchased with, in the embodiment described, an option to cancel two hours before the event begins. The text message and push notification are sent at the same time.
Screen 5 shows an App-produced notification that appears when the user next opens the App after receipt of the text message. The notification provides Cancel Pass and I'll be there! actuators, giving the user an option to cancel the parking pass or confirm to backend server 12 user attendance at the event. The user, by tapping the I'll be there! actuator, produces Screen 5C, which is the Activated Pass Screen. Screen 5C shows an activated pass confirmation in response to the user's attendance acknowledgement given at Screen 5. Operation 3 by backend server 12 changes in its database the status of the parking pass to confirmed. The user, by tapping the Cancel Pass actuator on Screen 5, produces Screen 5A, which shows an inquiry double-checking the user's intention to cancel and recording of the cancellation in backend server 12. The user, by tapping a Yes, cancel actuator, produces Screen 5B, which confirms cancellation of the parking pass and informs the user of a refund of the price of purchase, less the cost of processing the cancellation, of the AutoBuy purchase of a parking space. Operation 4 of backend server 12 entails recording in its database the decision to cancel.
Screens 6 and 6A show, respectively, an AutoBuy push notification and an option to either cancel the parking pass or confirm attendance (and a need for the parking pass) at the event, when mobile communication device 20 is in its Lock Screen state. The user performing a SWIPE RIGHT gesture across Screen 6 launches Activated Pass Screen 5C to buy the parking pass and display it on the screen. The user performing a SWIPE LEFT gesture across Screen 6 launches Screen 6A, showing the cancel pass or confirmation of attendance option akin to that shown on Screen 5A. The user confirming attendance results in Operation 3 by backend server 12 to change its database to confirm the status of the parking pass, and the user canceling the parking pass causes Screen 5A to appear for processing as described above.
Screens 7 and 7A show, respectively, an AutoBuy push notification and an option to cancel the parking pass while mobile communication device 20 is operating on an application program other than the Citifyd App. The user tapping the notification activates Screen 7A, which presents a cancel pass actuator the user taps to launch the App to Screen 5A to initiate cancellation of the parking pass and an I'll be there actuator the user taps to launch the App to Screen 5C to display a vehicle parking pass.
Screen 4 of
Screens 6 and 6A of
Screen 7 of
Screens 1, 2, 3, and 4 show activity relating to a user canceling a purchase of an event parking pass. Screen 1 is an EVENTS screen showing, at the top of a list of events, a display of a purchased parking pass. The user performing a SWIPE LEFT gesture on the displayed purchased event produces TRANSFER and CANCEL features. Screen 2 shows Cancel and Transfer actuators, which visually overlay a right-hand side of the purchased event parking pass entry displayed. The user desiring to cancel the event parking pass taps the displayed Cancel actuator to produce the Cancel Pass dialogue shown in Screen 3. The Cancel feature is available to the user, and therefore the Cancel Pass dialogue appears, only when there are at least two hours remaining before the event start time. The Cancel Pass dialogue provides a No, Keep Pass actuator and a Yes, Cancel actuator, giving the user an opportunity to retract or continue the Cancel order. The Cancel Pass dialogue also informs the user of the amount of the parking pass fee that would be refunded upon cancellation. The user, by tapping the Yes, Cancel actuator, produces Screen 4, which is a cancellation confirmation dialogue confirming successful cancellation, stating the expected time of deposit of the refund, and informing of email transmission of a cancellation receipt. User selection of the Yes, Cancel actuator updates the database to backend server 12 to change event parking pass status from purchased and date of purchase to cancel and date of cancellation.
Screens 5, 6, 7, and 8 show activity relating to a user repurchasing a canceled event parking pass. Screen 5 is an EVENTS screen, showing the list of events, with the top-line event depicted in gray and marked Cancelled with the date of cancellation to indicate the unpurchased status of the event parking pass. The user performing a SWIPE LEFT gesture on the event marked Cancelled produces a Buy Again feature. Screen 6 shows for the Buy Again feature a Buy Pass Again? dialogue for repurchasing the same event parking pass for the previously selected garage. The Buy Pass Again? dialogue provides Cancel and Buy Again actuators, giving the user an opportunity to retract or continue the Buy Again order. The user, by tapping the Buy Again actuator, produces Screen 7, which presents a normal event parking pass purchase receipt. Screen 7 shows Events and View Pass actuators, which the user can tap to display the event list and the purchased event parking pass, respectively. The user, by tapping the Events actuator, produces Screen 8, which shows the event list. The event list shows, as the top-line entry, the repurchased event parking pass in a purchase color (indicated as orange in the flow diagrams described) with the new purchase date.
Screen 1 is an EVENTS screen, showing that a user has purchased an event parking pass, which is depicted in a list of events as a top-line event entry in the purchase color. The user performing a SWIPE LEFT gesture on the purchased event parking pass entry produces a Transfer Pass option actuator, which appears in Screen 2 at the right-hand side of the purchased event parking pass display. The user desiring to transfer the event parking pass taps the displayed Transfer Pass actuator to produce the Transfer Parking Pass dialogue shown in Screen 3. The Transfer Parking Pass dialogue provides an Exchange for another event actuator and a Send to another person actuator, giving the user the option of transferring the purchased parking pass for use by the user at a future event or transferring the purchased event parking pass to another person for the same event. (The former option is described below with reference to
Screen 6 shows an email message template (upper screen) and a text message template (lower screen) that provide a pre-filled message body so that the user need complete only the transferee's email address or telephone number information and tap the Send actuator. Screen 7 shows a Your Pass was successfully transferred dialogue to confirm that the event parking pass has been transferred. The user, by tapping the OK actuator in response to the pass transfer confirmation, produces Screen 8, which marks the transferred event parking pass entry with text stating Transferred and indicating the date of transfer. A SWIPE LEFT gesture performed by a user on the transferred event parking pass entry produces a Buy Again option actuator, which appears in Screen 9 at the right-hand side of the transferred parking pass entry. The user, by tapping the Buy Again actuator, starts the Buy Again feature, which is described above with reference to Screens 6, 7, and 8 of
Screens 1A and 1B relate to an In-App Reminder function, which is performed in situations in which the App is open on mobile communication device 20. Screen 1A shows a Citifyd App Check-in local notification, which appears when the user opens the App within four hours of the event start time on event day. The notification provides a Can't make it actuator and an I'll be there actuator. The user, by tapping the Can't make it actuator, launches the App to Screen 1B, which shows a Transfer Parking Pass dialogue asking whether the user wants to exchange the parking pass for a parking pass to another event or transfer the parking pass to another person. The Transfer Parking Pass dialogue provides an Exchange for another event actuator and a Send to another person actuator. The user, by tapping one of the two actuators, will enter the parking pass exchange flow (
Screens 2A, 2B, 3A, and 3B relate to push notification functions, with Screens 2A and 2B directed to Lock Screen push notification and Screens 3A and 3B directed to In-Other Apps push notification. The In-Other Apps push notification is given in situations in which an application program other than the App is open on mobile communication device 20.
Screen 2A shows a silent notification, which is sent to the user four hours before the event start time on event day. The user performing a SWIPE LEFT gesture launches the App to Screen 1A of the In-App Reminder, and the user performing a SWIPE RIGHT gesture directs the App to Screen 2B, which shows a Can't make it actuator and an I'll be there actuator. The user, by tapping the Can't make it actuator, launches the App to Screen 1B of the In-App Reminder. The user, by tapping the I'll be there actuator, launches the App to the parking pass screen (see Screen 5C in
Screen 3A shows an Are you going to your event tonight? notification, which is given if another application is open on mobile communication device 20. The user, by tapping the notification, causes production of a Can't make it actuator and an I'll be there actuator to appear below the notification, as shown in Screen 3B. The user, by tapping the Can't make it actuator, launches the App to Screen 1B of the In-App Reminder. The user, by tapping the I'll be there actuator, launches the App to the parking pass screen (see Screen 5C in
Screens 4A, 4B, and 4C relate to a text message notifications function provided to a user who opted to SMS communication in interaction with the App operating on mobile communication device 20.
It will be apparent to skilled persons that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the disclosure. The scope of the invention should, therefore, be determined only with reference to the following claims.
This is a continuation of U.S. patent application Ser. No. 15/416,985, filed Jan. 26, 2017, which claims benefit of U.S. Provisional Patent Application No. 62/287,282, filed Jan. 26, 2016.
| Number | Date | Country | |
|---|---|---|---|
| 62287282 | Jan 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15416985 | Jan 2017 | US |
| Child | 17581897 | US |
