WO2008132520A1

WO2008132520A1 - Method and system for the central collection, management and communication of information about parking spaces

Info

Publication number: WO2008132520A1
Application number: PCT/GR2008/000025
Authority: WO
Inventors: Andreas Prodromidis
Original assignee: Andreas Prodromidis
Priority date: 2007-04-27
Filing date: 2008-04-16
Publication date: 2008-11-06
Also published as: GR20070100249A

Abstract

A method and system for the central collection, management and communication of the necessary information to aid drivers to find, in real-time, a parking place when they have reached or are very close to their destination: it facilitates their collaboration with nearby drivers that are ready to depart and are willing to hold their parking space. Drivers communicate their requirements, via mobile communication devices, to a central system that undertakes the appropriate pairing of arriving and departing drivers, providing them with the necessary instructions for the handover of the parking space. The central system promotes collaboration by charging arriving drivers with a centrally set reservation amount and by refunding a substantially similar amount to departing drivers. Arriving drivers may additionally request departing drivers to extend their wait time for an extra credit amount. The system and method can also be used for reaching drivers if needed.

Description

TITLE OF THE INVENTION

Method and system for the central collection, management and communication of information about parking spaces.

FIELD OF THE INVENTION

This invention concerns a method and a system which aid drivers in their search to find, in real-time, a parking place when they have reached or are very close to their destination. The invention promotes and facilitates the collaboration of these drivers with nearby drivers that are ready to vacate their parking space by getting the departing drivers to hold their parking space for the arriving ones. The present invention describes a method and system for the central collection, management and communication of the necessary information to accommodate this exchange.

BACKGROUND OF THE INVENTION One approach attempting to address the problem of locating parking spaces is described in patent application WO 2006/ 106369Al, titled "System for locating free parking places by means of mobile communication devices", and published on October 12^th 2006. This patent application describes a sequence of cameras and sensors that monitor a pre-determined set of parking spaces and check whether they are available or occupied. Each of these devices informs a central database system regarding the status of each space through a wireless network. According to this patent application, the central database system allows each driver to be informed about available parking spaces in the area which interests him/her, through a mobile phone or other relevant device.

The primary difficulty in utilizing the above invention on a broad scale service (so as to make it practical and useful), lies in its dependence on the installation and functioning of devices along all streets and parking garages and lots. The high investment and maintenance costs of this (including providing power to these devices), in conjunction with the fact that all such devices are vulnerable to accidents, weather conditions, or other type of destructions, make it difficult to implement. Moreover, it presupposes the ability to install cameras and sensors (which may be forbidden or the landplaning requirements may not exist), assumes adequate lighting and depends on parking spaces that are big enough and outlined so that every kind of vehicle can fit. Finally it does not account for the possibility of another driver being ahead and occupying the parking space which had been assigned (by the above system) to another driver. Another, more pragmatic approach is described in patent application US 2007/0008181Al, titled "System and method for optimizing the utilization of space", and published on January 11^th 2007. This patent application describes a service through which users, drivers or garage owners, broadcast information related to the exact time of departure and specific location a parking space, that other drivers interested in the particular parking space (location-wise and time-wise), may find and book through a monetary transaction or bid, set by the departing users. While this approach removes most of the limitations and obstacles present in other methods and systems, it is geared towards facilitating users into yielding / finding a parking space at a future moment, i.e., not in real-time when users are ready to depart from their a parking space or have arrived at their destination.

More specifically, the methods and provisions of the above patent cannot support well drivers in offering or finding a parking space at substantially the time they are ready to leave or have arrived near their destination. In the context of street parking, for example, these particular methods are tuned to facilitate users that plan ahead their trip and can estimate with good (or even exact) accuracy their time of departure / arrival. This is evident from the following provisions: o A user needs to arrive at a parking space the latest at a time set previously by the user yielding that space. A slight delay means for the former means he/she misses the parking space; o Biddings and auctions presuppose ample time for tenders to be meaningful and hence successful. In a real-time scenario, this cannot be applied; o The search system where users sift through parking space options cannot function in real-time or provide reliable options. The dynamic real-time nature of the changing parking conditions render each view (of current parking space options) presented to the user obsolete very rapidly. Instead it is proper for reserving a parking space that will become available in the not-very-near future.

Pre-scheduling a parking space handover poses additional limitations in its application and operation: asking users to always synchronize their arrival and departure times is not always feasible, due to traffic obstacles, unforeseen events or simply bad timing. The unavoidable, even narrow, misses between two drivers would prompt to low peer rating and unrealized revenue for drivers, leading to an erosion of confidence and user collaboration, and ultimately to failed service. (Note: The success of such service depends on getting many people use it.)

SUMMARY OF THE INVENTION

It is the intent of this invention to aid drivers to find a suitable parking place when they have reached or are very close to their destination: it facilitates their collaboration with nearby drivers that are ready to depart but are willing to hold their parking space for the arriving drivers. The present invention describes a method and system for the central collection, management and communication of the necessary information to accommodate this exchange.

Such information includes the location and size of the ready-to-be-released parking space of the driver about to depart, as well as the current location and vehicle size of the driver seeking to imminently find a parking space. Given this information, departing and arriving drivers are matched centrally in real-time in the best possible pairs, based on their geographic and time proximity and the suitability of the arriving driver's vehicle size to fit in the departing driver's parking space. Drivers about to depart are subsequently asked to delay, for a reasonable short period of time, their departure to allow their paired driver to reach and occupy their position. To encourage the information sharing between drivers, the invention describes a payment scheme, set centrally, whereby drivers submit a payment when they receive instructions to proceed to a parking space that is reserved for them, and are refunded a substantially similar amount when they offer a parking space and are willing to hold it for a reasonable short time for their paired driver to arrive. Alternatively, instead of monetary means, the same effect can be used via any type of tokens: A driver receives a token when offering a parking space and grants it when finding one.

The refund is issued upon confirmation of the arrival of the driver seeking to occupy the parking space. In this invention this is accomplished by getting the departing driver to send specific characteristics of the arriving driver's vehicle that uniquely identify the vehicle and confirm the actual arrival of the driver seeking the parking space to the location of the departing driver. Hence, the departing driver avoids having to further collaborate and depend on the arriving driver to receive his/her refund.

Arriving drivers may additionally request departing drivers to extend their wait time for an extra credit amount, to allow smoother handover of the parking space. In essence, this invention also introduces and outlines a new market enabling drivers to buy-and-sell time. In effect, drivers occupying parking spaces have the option to "sell" their extended wait time to drivers seeking to occupy parking spaces.

Drivers communicate information regarding their intention, location and space requirements via mobile phones or other wireless portable devices, preferably location- aware. The collection, processing, matching and overall management of such information, including accounting, setting and receiving payments, interfacing with external payment- providing services, as well as the generation and communication of instructions occurs at the central system. In this invention, collaborating drivers form a virtual community whereby they exchange information to make it easier and faster to locate parking spaces. The method and system described are general enough to be applied in street parking, with or without a parking- meter, public or private parking garages, parking lots, etc. At the same time, they bypass the capital costs and complexities of having to install special sensors and cameras to streets and parking facilities. Instead they build upon existing technologies (e.g. GPS, GIS, Mobile maps, SMS, Wireless protocols, payment systems, etc.) and describe a real-time parking space-finding service through which a driver may get information of an accommodating (proximity-wise and space-wise) about-to-be vacant parking space. Moreover, they are designed to overcome the possibility the about-to-be vacant parking space be overtaken by another driver (given that the driver that is about to depart will wait until the paired-driver arrives).

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 illustrates an architectural view of the logical elements that carry out the Membership Registration Application process.

Figure 2 illustrates an architectural view of the logical elements that carry out the steps for vacating and occupying a parking space, as per the various embodiments described herein. DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The preferred embodiment of this invention is comprised of the following:

1. "Registration Gateway" accepting membership registration requests. A "Registration Gateway" can be built on a Web server, Interactive- Voice-Response

(IVR) server, SMS/IMS/MMS Gate server, Email server, call center server, or other comparable platform

2. "Membership Registration Application" server validating the membership registration data 3. "Member Database" server, maintaining all data pertaining to members and their vehicles.

4. "Communications Gateway", capable of receiving/sending information, e.g. via SMS, iMode, WAP, etc., from/to drivers as they cooperate in exchanging parking spaces. A "Communications Gateway" can be built on a Web server, IVR server, SMS/IMS/MMS Gate server, Email server, call center server, or other comparable platform.

5. "Parking Space Matching & Central Control" server for comparing and managing the requests of drivers about to vacate a parking space with the requests of other drivers seeking to imminently occupy. The server matches these requests in pairs, the best possible way, based on geographic and time proximity of the arriving and departing drivers and the ability of the arriving driver's vehicle to fit in the departing driver's parking space.

6. "Pending Requests Database" server for maintaining all pending requests from drivers ready to vacate or seeking to imminently occupy a parking space. 7. "Transactions Database" server for maintaining all transaction data. Such data include, but are not limited to, driver and vehicle IDs, request ID, transaction type (e.g., register request, occupy request, vacate request, cancel request, etc.), transaction date and time data, transaction amount, etc.

8. "Account Validation and Payment Processing" server for the validation of identification and payment account information of drivers and for debiting and crediting their accounts, either via direct or indirect connection to a Bank, or interbank payments network, or a Telecommunication company, or an Internet Service Provider, or Telecommunication Service Provider, etc. It is used to encourage the information sharing between drivers, and especially those preparing to vacate a parking space. This can be achieved by debiting drivers a payment amount when they receive instructions to proceed to a parking space reserved for them, and refunding them the same amount, minus relevant commission fees, if any, when they hand over a parking place.

9. "Communication Devices" for the communication of drivers with the above servers, via the Communications Gateway. Indicative such devices are mobile phones, mobile computers, PDAs, (Personal Digital Assistants), special vehicle- mounted devices, devices than have been specially constructed to support this invention, location-aware mobile communication devices, which may or may not be equipped with software developed to facilitate and automate the communication between drivers and the above servers. Such communication can be achieved in many ways made, including but not limited to messages (e.g., SMS), multimedia messages (e.g., MMS), instance messaged (IM), electronic mail, TCP/IP, Intenet- based protocols (e.g., HTTP, WAP, iMode), Mobile Communication Protocols (e.g., GPRS, DSM, UMTS), voice (e.g., IVR, VoIP). These Communication Devices are used from the drivers for one or more of the following: a. Submit of a registration application to become a member of the virtual community of collaborating drivers. b. Receipt of the approval / rejection of above application c. Submit of request to vacate or occupy a parking space d. Receipt of instructions to wait a short period of time (e.g., 2-3 minutes) for the arrival of the paired driver, together with instructions on how to uniquely identify the paired driver, e.g. via the vehicle's brand, color, last two letter or digit of the license plate or VIN - for the case of the departing driver e. Receipt of instructions to proceed to a specific location to occupy the parking space of the paired driver, the remaining time until the paired driver departs, e.g., 2-3 minutes, together with instructions on how to uniquely identify the paired driver, e.g. via the vehicle's brand, color, last two letter or digit of the license plate or VIN - for the case of the arriving driver. f. Receipt of notification of not finding an appropriate match g. Send of confirmation code, by the driver vacating a parking space, proving the arrival of the paired driver h. Communication for corrections / clarifications / account, transaction status and updates. The preferred embodiment can be further described using Figures 1 and 2:

Figure 1 describes a user applying to become a member of the virtual community of drivers that collaborate to find parking spaces. The user provides the necessary registration data including, but not limited to:

1. Personal data (e.g., name and address), 2. Contact information (e.g. mobile phone number, email),

3. Information about the vehicles used by the user (e.g., type, brand, model, size, license plate, VIN) 4. Preferred method of payment (e.g., credit card, bank account, mobile phone number, etc.)

Such information is provided through a Communication Device (1) via a wired or wireless network, such as Internet, mobile phone network, land phone lines, fax, or other comparable means.

The Registration Gateway (2) receives the application and checks whether it contains all necessary data. It then forwards it to the Membership Registration Application server (3) for further validation and processing. This server validates user information via the Account Validation & Payment Processing server (4) which directly or indirectly interfaces with a bank, interbank network, mobile phone service provider, etc. It then generates a unique member ID per user and a unique vehicle ID per registered vehicle (or a unique global ID per vehicle) and stores them, together with the application data in the Member Database server (5). Finally, it generates an application acceptance report that includes the member ID and the unique vehicle ID per registered vehicle (or the unique global ID per vehicle) and returns it to the Registration Gateway (2). In turn, the Registration Gateway (2) forwards the acceptance report to the Communication Device (1) of the new member.

Figure 2 describes the process whereby a member driver, having reached or being close to his/her destination, takes advantage of the invention disclose herein, first to find another nearby member driver that is about to vacate his/her parking place and second, to collaborate with him/her in order to reserve his/her parking space.

The driver wishing to imminently find a parking space uses a Communication Device (7) to send via SMS, Internet, special software, etc., a request to occupy a parking space, with the following information:

1. Member ID 2. Vehicle ID, used to determine the size characteristics of the vehicle

3. Indent to find a parking space

4. Current location, sent automatically by the locate-aware Communication Device or provided by the driver.

Alternatively, the Member ID and Vehicle ID may compose a unique ID. The Communications Gateway (8) receives the request and checks it for its validity. It then stores it in the Pending Requests Database server (9) and also forwards it in the Parking Space Matching & Central Control server (10) where it is matched against the pending requests of drivers ready to vacate their parking space. The matching criteria include the following: 1. The geographical distance between the driver seeking a parking space and the driver departing from a parking space. (It is also used to corroborate that the designated parking space is within walking distance of the target destination of the driver).

2. The ability of the driver seeking a parking space to reach the location of the vacating driver on time, by comparing the estimated time of arrival of the first driver against the remaining of the reasonably short period of wait time (e.g. 2-3 minutes) the second driver is asked to wait.

3. Size of the vehicle of the driver seeking a parking space against the size of the vehicle or parking space (if known) of the departing. In the event a request cannot be matched instantly, it remains as pending to be compared against new parking space vacating requests. In contrast, in case of successful pairing, both drivers receive at their Communication Devices instructions to collaborate. Specifically: o The driver seeking a parking space receives instructions with the exact location of the parking space, the time until the space is reserved and information on how to uniquely identify the paired driver, e.g. via the vehicle's brand, color, last two letter or digit of the license plate or VIN. o The driver that is about to depart receives instructions with the estimated wait time together with information on how to uniquely identify the paired driver, e.g. via the vehicle's brand, color, last two letter or digit of the license plate or VIN. Next, the Parking Space Matching and Central Control server (10) debits the account of the driver seeking the parking space for the reservation amount, set by the server, via the Account Validation and Payment Processing server (4) and logs the transaction data in the Transaction Database server (6). Finally, it sends to the Communication Device (7) of this driver a notice regarding the debit of his/her account, via the Communications Gateway (8). In the meanwhile, the driver that sent the request to occupy the parking space proceeds to the designated location to meet the driver that waits, as per the received instructions. The total time it takes the driver to arrive cannot be longer than the time the parking space is reserved, after which the reservation may be retracted.

Once the driver arrives at the designated location, the paired driver that is about to vacate the parking space sends to the Parking Matching and Central Control server (10), via the

Communication Device (7) and the Communications Gateway (8), the confirmation code proving the arrival of the paired driver. The confirmation code is assembled by the driver based on a predefined formatting and assembling scheme (e.g., received with the instructions or upon the driver's registration or introduction in the virtual community). For example, the code may be two or three specific letters or digits from the license place or

VIN of the arrived driver's vehicle.

The Parking Space Matching and Central Control server (10) cross-checks the received confirmation code against the corresponding data maintained in the Member Database server (5) for the particular arriving vehicle. Next, it credits the departing driver's account for the relinquishing amount, set by the system (e.g. reservation amount minus a commission fee, if any), via the Account Validation and Payment Processing server (4), logs the transaction data in the Transaction Database server (6) and notifies the departing driver to release the parking space. Next, it deletes the requests of both drivers from the Pending Requests Database (9). Similarly, Figure 2 describes the process whereby a member driver, being ready to vacate his/her parking place, takes advantage of the invention disclose herein, to accommodate another nearby member driver that searches for a similar parking place and collaborate with him/her to hand it over.

The driver wishing to imminently vacate a parking space uses a Communication Device (7) to send via SMS, Internet, special software, etc., a request notifying of his/her imminent intention to vacate a parking space, with the following information:

1. Member ID

2. Vehicle ID, used to determine the size characteristics of the vehicle

3. Indent to vacate a parking space

4. Current location, sent automatically by the locate-aware Communication Device or is provided by the driver.

Alternatively, the Member ID and Vehicle ID may compose a unique ID.

The Communications Gateway (8) receives the request and checks it for its validity. It then stores it in the Pending Requests Database server (9) and also forwards it in the Parking Space Matching & Central Control server (10) where it is matched against the pending requests of drivers seeking a parking space. The matching criteria include the following:

1. The geographical distance between the driver departing from a parking space and the driver seeking a parking space. (It is also used to corroborate that the designated parking space is within walking distance of the target destination of the driver).

2. The ability of the driver seeking a parking space to reach the location of the vacating driver on time, by comparing the estimated time of arrival of the first driver against a reasonably short period of wait time (e.g. 2-3 minutes), set by the system, the second driver is asked to wait

3. Size of the vehicle or parking space (if known) of the departing driver against the size of the vehicle of the driver seeking a parking space In the event a request cannot be matched instantly, it remains as pending, for a reasonably short period of time, to be compared against new requests for parking space. In contrast, in case of successful pairing, both drivers receive at their Communication Devices instructions to collaborate. Specifically: o The driver that is about to depart, receives instructions with the estimated wait time (that cannot exceed the maximum reasonably short period of wait time, set by the system) together with information on how to uniquely identify the paired driver, e.g. via the vehicle's brand, color, last two letter or digit of the license plate or

VIN. o The driver seeking a parking space, receives instructions with the exact location of the parking space, the time until the space is reserved and information on how to uniquely identify the paired driver, e.g. via the vehicle's brand, color, last two letter or digit of the license plate or VIN. The driver that is about to depart, waits for the arrival of the paired driver so as to hand him/her over the parking place. The total wait time of the departing driver, counting from the moment the Communications Gateway receives the request notifying his/her imminent intention to vacate the parking space, cannot be longer than the reasonably short period of wait time, set by the system (e.g., 2-3 minutes), irrespectively of whether or not a matching request is found. In such a case, the departing driver is credited with the relinquishing amount.

Once the paired driver arrives at the designated location, the driver that is about to vacate the parking space sends to the Parking Matching and Central Control server (10), via the Communication Device (7) and the Communications Gateway (8), the confirmation code proving the arrival of the paired driver. The confirmation code is assembled by the driver that is about to vacate the parking space based on a predefined formatting and assembling scheme (e.g., received with the instructions or upon the driver's registration or introduction in the virtual community). For example, the code may be two or three specific letters or digits from the license place or VIN of the arrived driver's vehicle.

The Parking Space Matching and Central Control server (10) cross-checks the received confirmation code against the corresponding data maintained in the Member Database server (5) for the particular arriving vehicle. Next, it credits the departing driver's account for the relinquishing amount, set by the system (e.g. reservation amount minus a commission fee, if any), via the Account Validation and Payment Processing server (4), logs the transaction data in the Transaction Database server (6) and notifies the departing driver regarding the credit of his/her account and instructs him/her to release the parking space. At the same time, it deletes the requests of both drivers from the Pending Requests Database (9). It is noted that the crediting of the departing driver's account takes place after the successful identification of the paired driver, so as to motivate and forge the collaboration between the two drivers and the system. In this embodiment, the relinquishing amount set by the system is considered a refund to the amount that was debited to the driver when he/she had sent a request to occupy a parking space (minus a commission fee, if any). The same effect can be accomplished via the use of tokens, where a driver receives a token when offering a parking space and grants it when finding one, i.e., drivers need to have tokens to request help to find parking spaces; they collect them when they yield parking spaces to other member drivers.

In a second and extended embodiment of the invention, the driver proceeding to occupy a designated parking space can, depending on his/her need to occupy that specific parking place, offer to pay a premium in order to complement the set relinquishing amount credited to the departing driver, and ask for a heightened degree of collaboration of the departing driver.

In the second embodiment, if a driver realizes for various reasons (e.g. more difficult traffic conditions, missed a turn, etc.), it is difficult to reach the location of the designated parking space on time, he/she may request to extend the wait time of the paired driver by offering a premium, an extra payment amount, set by the system or the matched driver, to be credited to the paired driver, if he/she accepts. Upon acceptance, the requesting driver is debited the extra payment amount. Upon arrival of the driver to the designated parking space, the departing driver is credited the combined amount consisting of the set relinquishing amount plus the offered premium. This embodiment introduces and outlines a new market and supporting infrastructure to enable drivers to buy-and-sell time. In effect, drivers occupying parking spaces have the option to "sell" their waiting time to drivers seeking to occupy parking spaces. The infrastructure and systems supporting this embodiment is similar to the one described already, with the addition of the following communications:

1. Submit of a request by the driver proceeding to the designated parking space, via the Communication Device (7) and the Communications Gateway (8), asking for the extension of the matched driver's wait time. The request includes the updated location of the requesting driver and the selected, by the requesting driver, extra- priced wait-time extension option.

2. Forwarding of the above request to the Communication Device (7) of the waiting driver by the Communications Gateway (8), together with an updated estimate time of arrival of the driver seeking to occupy the parking space. 3. Send of notice accepting or rejecting the offer by the waiting driver via the

Communication Device (7) and the Communications Gateway (8).

4. Forwarding of the above notice to the Communication Device (7) of the requesting driver.

Additionally, the Parking Space Matching and Central Control server (10) is extended to include, in the instructions that are sent to the driver that requested a parking space, additional instructions on how to select from one or more extra-priced wait-time extension options, together with instructions on how to send the corresponding request to the paired driver with the designated parking space.

In yet another embodiment, the extra-priced wait-time extension options are set by the waiting drivers. In this case: o The Communication Device (7) is extended to allow the submit of wait-time extension options, o The Communications Gateway (8) is extended to receive and forward these options, o The Parking Matching Space and Central Control server (10) is extended to store them and use them (and hence bypass any other options set centrally).

In yet another embodiment, drivers are evaluated and rated by the system, i.e., Parking Space Matching and Central Control server (10), according to their good citizenship and their contribution in the well-functioning of the virtual community of member drivers. For example, drivers receive good ratings when they communicate their intent to vacate a parking place or when they promptly, accurately and properly communicate and handover their parking places. In this embodiment, drivers with higher ratings, stored in the Member Database server (5), receive a priority over other drivers with lower ratings when they seek to occupy a parking space. This rating method and system may be used separately or in conjunction with the crediting and debiting method and system of preceding embodiments. It should be noted that the preferred embodiment also describes a system for the central collection, management and communication of information pertaining to the supply and demand of parking spaces. The infrastructure and systems of this embodiment can be somewhat extended to also be used to collect and retain statistical data concerning the number of drivers and vehicles searching for and/or vacating parking spaces at any time, in every area, as well as data related to the time necessary for drivers to get to their designated parking spaces. Through the processing, analysis and comparison of such information against historical data and trends, it is possible to infer model and draw conclusions about traffic patterns, congestion points, alternative routes, etc., that can be further evaluated by members of the virtual community of drivers, or even the traffic police, local authorities, public transport experts, etc. To better support this, the embodiment is extended to not delete Pending Requests Database server's (9) data, but to maintain them at a replicate database and use them in conjunction with relevant data from the Member Database server (5) and the Transaction Database server (6). It should further be noted that the infrastructure and systems of the preferred embodiment enables drivers (members or not), people, authorities, etc., to communicate with member drivers in cases of urgent or not so urgent circumstances. Through the use of data maintained in the Member Database server (5) and the use of its communications facilities (i.e. the Communications Gateway (8) and the Communication Devices (7)) the embodiment facilitates the communication with member drivers if they obstruct the traffic or pedestrians (e.g., if vehicles are parked improperly), or if it is necessary to remove their vehicle from places which need to be vacated urgently (e.g., by the police, fire department, etc.), or where works have been scheduled (e.g., street cleaning, maintenance services etc.). For instance, one can send a notice to the driver of a vehicle that is obstructs traffic based on the license plate of that vehicle.

In such case, the embodiment describes a method and system that facilitate communication with drivers for reasons other than the search for parking spaces.

In yet another extension of the preferred embodiment, the Member Database server (5) also maintains the most recently known location of each member driver's vehicle. The extra information facilitates identifying the drivers that have parked at a specific street, or area or location, etc., and enables, through the Communications Gateway (8), the broadcasting of information to them if needed. For example, in a case of an emergency, it is possible the police, fire department, etc. to decide to broadcast an informing notice to vacate a specific street or area to all drivers parked there. Based on the information stored in the Member Database server (5), it is possible to locate all member drivers who, based on the most recent data, have parked at that specific street or area and send them the appropriate informing notice.

This capability can be further enhanced in yet another embodiment whereby the Communication Devices (7), specially if embedded in keys or key chains, or in special lock/unlock or other vehicle-activation devices or buttons or parts, with the capability to, at the discretion/consent of the user (through possibly an activation switch), transmit automatically and periodically to the Communications Gateway (8) the vehicle's coordinates, either continuously, or only when the vehicle is in operation, or when the user starts the vehicle, or when the user unlocks the doors, or through special user-operated switches. The preceding paragraphs presenting the preferred and alternative embodiments of this invention are not intended to be exhaustive or to limit the invention to the precise form disclosed above. While these embodiments and related examples described herein are for illustration purposes, various equivalent modifications are possible within the scope of this invention, as those skilled in the relevant art will recognize. For example, one may establish the logical and functional equivalency of alternative embodiments, indicatively based on object-oriented design, distributed systems design, service-oriented design, event-driven design or based on rules or business process automation and management tools.

Claims

CLAIMSWe claim:

1. A method for the central collection, management and communication of information about parking spaces, aiming at facilitating the collaboration between users that search to find, in real-time, a parking place when they have reached or are very close to their destination, with nearby users that are ready to vacate a parking space.

The method comprises of the following steps: a. Central collection of information from users regarding their imminent intention to vacate or occupy a parking space, whereby information contains their intention, their current location and their respective vehicle size. b. Central matching of the said location and vehicle size of a first user vacating a parking space with the said location and vehicle size of a second user seeking to occupy the parking space, based on the proximity of their said locations in space and time and the ability of the second user's said vehicle to fit in the space of the first user's said vehicle. c. Communication of instructions to the first user to wait and hold the parking space, for at least a reasonably short period of time set by the central system, until the arrival of the second user, together with information on how to uniquely recognize the second user. d. Communication of instructions to the second user with the said location of the first user, the remaining short period of time set by the central system during which the first user waits for the arrival of the second user, together with information on how to uniquely recognize the first user. e. Debit the second user with a reservation amount, set by the central system. f. Central collection of a confirmation code assembled and sent by the first user announcing the arrival of the second user and handover of the parking space from the first user to the second user. g. Credit the first user, upon receipt of valid said confirmation code or expiration of said reasonably short period of time, with a relinquishing amount that is set by the central system and is equal to the said reservation amount, minus relevant commission fees, if any.

2. The method of claim 1, wherein the code sent by the first user confirming the arrival of the second user is assembled by the first user, as per the central system's instructions, and contains specific information pertaining the second user's vehicle, including specific letters or digits of the second user's vehicle license plate, or vehicle registration number, or other vehicle-distinguishing characteristic.

3. The method of claim 1, wherein the second user requests a specific extension of the wait time of the first user by submitting one-of-possibly-many extra payment amount, to be credited to the first user, if the first user accepts. The second user is debited the said amount upon acceptance of the first user's request and the first user is credited the said amount, together with the relinquishing amount, when the first user confirms the arrival of the second user.

4. The method of claim 3, wherein the one or possibly many extra payment amounts are set by the central system.

5. The method of claim 3, wherein the one or possibly many extra payment amounts are set by the second user.

6. The method of claim 1, wherein the central system rates users according to a plurality of collaboration-related parameters, including whether or not they communicated to the central system their intention to vacate a parking space, their reliability, the correctness of the information they communicate to the central system.

7. The method of claim 1, wherein given the location of a parking space or a vehicle's distinctive characteristics, the central system can identify the user of the said parking space or vehicle and communicate to this user important information.

8. The method of claim 1 in combination with a data processing and analysis method, wherein the collected information is used to infer and improve upon traffic and parking patterns.

9. A system for the central collection, management and communication of information about parking spaces, aiming at facilitating the collaboration between users that search to find, in real-time, a parking place when they have reached or are very close to their destination, with nearby users that are ready to vacate a parking space. The system consists of a plurality of communication devices and logical interconnected computers as follows: a. A plurality of Communication Devices for the communication of users with a set of said computers described beneath. Indicative such devices are mobile phones, mobile computers, PDAs, (Personal Digital Assistants), special vehicle- mounted devices, devices than have been specially constructed to support this invention, location-aware mobile communication devices, which may or may not be equipped with software developed to facilitate and automate the communication between said users and the said computers of the said system.

These communication devices are used for the following: al. Send of membership registration requests a2. Send of requests to vacate / occupy a parking space a3. Receipt of instructions on how to vacate / occupy a parking space, or receipt of a notification of not finding an appropriate match a4. Send of confirmation code of arrival of user that requested to occupy the parking space. a5. Communication for corrections / clarifications / account, transaction status and updates. b. A Registration Gateway accepting membership registration requests, checking them for completeness and forwarding them to the Membership Registration Application server (described next) for further analysis and processing. Additionally, it responds with the resulting acceptance / rejection reports it receives from the Membership Registration Application server. c. A Membership Registration Application server that validates, if necessary, the membership registration data via the Account Validation and Payment Processing server (described below). Next, it generates a unique member ID for the each said user and a unique vehicle ID per registered vehicle (or a unique global ID per vehicle) and stores it, together with the said membership registration request data, in the Member Database server (described next). Additionally, it issues and forwards an acceptance / rejection report for each said membership registration request to the Registration Gateway. d. A Member Database server that maintains all data pertaining to the said users and said vehicles. e. A Communications Gateway capable of receiving / sending information from / to Communication Devices as said users seek to vacate or occupy a parking space. The Communications Gateway validates the incoming requests to vacate or occupy a parking space, generates a unique Request ID per request and stores it, together with data from the said incoming request, in the Pending Requests

Database (described below). Furthermore, it forwards to the Communication Devices the relevant instructions to help respective said users collaborate in vacating and occupying parking spaces. Furthermore, it forwards to the appropriate Communication Devices notifications of not finding an appropriate match. Furthermore, if forwards to the appropriate Communication Devices of said users about to vacate a parking space, expiration notifications of the reasonably short period of wait time. Additionally, it receives the confirmation code sent by said users vacating a parking space which announces the arrival of said users seeking to occupy that parking space and forwards it to the Parking Space Matching & Central Control server (described next). Additionally, it receives requests for corrections, clarifications and account and transactions status and sends to the Communication Devices of the respective said users the appropriate responses, as well as transaction and account updates. f. A Parking Space Matching & Central Control server for matching the requests of said users about to vacate a parking space and the requests of other said users seeking to imminently occupy one, based on their current geographic proximity, their estimated time proximity compared against a reasonably short wait time, and the size of their vehicles (to guarantee there is ample parking space). Furthermore, it determines the optimal matches, described as pairs of a first user vacating a parking space and a second user seeking to occupy a parking space, and formulates and forwards the relevant instructions to the Communications Gateway. Furthermore, it receives, via the Communications Gateway, the confirmation code assembled and sent by the first user and validates the correct handover of the parking space. Furthermore, it debits the account of the second user a parametrically-set reservation amount and credits the account of the first user a relinquishing amount that is equal to the said reservation amount, minus relevant commission fees, if any, via the Account Validation and Payment Processing server (described below), and records these transactions in the Transaction Database server (described below). Additionally, is generates and forwards to the Communications Gateway (for further forwarding) notification information pertaining to the credit and debit transactions of the first and second user respectively. Additionally, it removes the said matched requests from the Pending Requests Database (described next) unless they need to be kept for other reasons. g. A Pending Requests Database server for storing all requests received by the Communications Gateway, also forwarded to the Parking Space Matching &

Central Control server. Any said request that is not paired by the Parking Space

Matching & Central Control server, or has not expired, is maintained in this server awaiting to be compared against new incoming requests. Furthermore, it sets the expiration time, a reasonable short period of time, for each request pertaining to an imminent vacation of a parking space and forwards it to the

Communications Gateway (for further forwarding to the corresponding user).

Additionally, it removes the expired requests, credits the accounts of their respective users a said relinquishing amount that is equal to the said reservation amount, minus relevant commission fees, if any, via the Account Validation and Payment Processing server (described below), records these transactions in the

Transaction Database server (described next), and generates and forwards to the

Communications Gateway (for further forwarding) notification information pertaining to the particular credit transactions. h. A Transaction Database server for maintaining the transaction data of said users, including the said user-related data, said transaction type, association information with said requests, said transaction date and time and said transaction amount. i. An Account Validation and Payment Processing server for the validation of identification and payment account information of said users and the performance of debit and credit transactions, via direct or indirect connection to a Bank, or Interbank payments network, or a Telecommunication company, or an Internet Service Provider, or Telecommunication Service Provider.

10. The system of claim 8, wherein the Communication Devices are specially developed for use within this invention, either embedded in keys or key chains, or in special lock/unlock or other vehicle activation devices or buttons or parts, with the capability to, at the discretion/consent of the user (through possibly an activation switch), automatically and periodically transmit to the Communications Gateway the vehicle's coordinates, either continuously, or only when the vehicle is in operation, or when the user starts the vehicle, or when the user unlocks the doors, or through special user- operated switches.

11. The system of claim 8, wherein the Parking Space Matching & Central Control server formulates and sends instructions to the first user to assemble the confirmation code based on specific information pertaining the second user's vehicle, including specific letters or digits of the second user's vehicle license plate, or vehicle registration number, or other vehicle-distinguishing characteristic. Furthermore, the Matching Parking Space Request server validates the said confirmation code against the corresponding information pertaining the second user's vehicle that is recorded in the Member Database server.

12. The system of claim 8, wherein: a. The Communication Device also supports sending and receiving one of possibly-many-extra-priced wait-time extension offers to extend the wait time as well as the acceptance / rejection of the said offer. b. The Communications Gateway forwards the said extra-priced wait-time extension offer to the respective Communication devices and the Parking Space Matching & Central Control server. c. The Parking Space Matching & Central Control server formulates and sends instructions to the second user to consider selecting from one or more extra- priced wait-time extension options, set centrally, and then requesting the extension of the wait time from the first user. Furthermore, upon receipt of the acceptance offer by the first user, it debits the account of the second user the amount corresponding to the selected said extra-priced option. Additionally, when the first user confirms the arrival of the second user, it credits the account of the first user the same amount, together with the relinquishing amount.

13. The system of claim 8, wherein: a. The Communication Device also supports sending and receiving one of possibly-many extra-priced wait-time extension offers, defined by the first user, to extend the wait time as well as the acceptance / rejection of the said offer. b. The Communications Gateway forwards the said extra-priced wait-time extension offer to the respective Communication devices and the Parking Space Matching & Central Control server. c. The Parking Space Matching & Central Control server formulates and sends instructions to the second user to consider selecting from one or more extra- priced wait-time extensions offer to the first user, and then requesting the extension of the wait time from the first user. Furthermore, upon receipt of the acceptance offer by the first user, it debits the account of the second user the amount corresponding to the said extra-priced wait-time extension offer. Additionally, when the first user confirms the arrival of the second user, it credits the account of the first user the same amount, together with the relinquishing amount.

14. The system of claim 8, wherein: a. The Parking Space Matching & Central Control server evaluates and rates said users according to a plurality of collaboration-related parameters, including whether or not they communicated to the central system their intention to vacate a parking space, their reliability, the correctness of the information they communicate to the central system. Furthermore, it associates the said users' rating with the said users' priority when said users seek to occupy a parking space. b. The Transaction Database server also stores the rating the said users received in each transaction. c. The Member Database server also maintains the overall rating of said users

15. The system of claim 8, wherein the user of a particular parking space or vehicle can be identified and contacted based on the following: a. In case of a need to communicate information to said user that has parked at a specific location, the Transactions Database server maintains the most relevant data. Furthermore, the Member Database server can be extended to retain the most recently-known location of users, b. In case of need to communicate information to users that frequent at a specific location, the Member Database server maintains the most relevant data, c. In case of need to communicate information to users of a specific vehicle (e.g., based on license plates), the Member Database server maintains the most relevant data.

16. The system of claim 8, wherein the Pending Requests Database server's data are not deleted but maintained at a replicate database. These data, together with those from the Member Database server and the Transaction Database server are further processed and analyzed in order to infer and improve upon traffic and parking patterns.