Patent Application
20220068079
This invention relates to software related to parking management, and more specifically to parking management software.
It is known in the prior art to utilize a computer-implemented user interface to interact with a parking management system.
Prior art limits the types of available user interfaces by coupling some of the complexity of the environment with the user interface.
There are three important factors in modern parking systems that make it difficult to support additional user interfaces, for example, popular consumer navigation applications or in-vehicle software systems.
The first factor involves the application and calculation of parking policy to each parking location. Parking policy can vary dramatically from location to location, include both static and dynamic inputs, and may vary based on the vehicle attempting to park. For context, some example parking policies include:
The second factor involves the processing and settlement of funds across many parking operators based on the parking location where the parking session takes place. These integrations typically must be configured by the provider of the user interface when enabling each new parking operator.
The third factor involves supporting necessary downstream integrations, including integrations with parking enforcement software, financial reporting software, and data storage systems which vary from parking operator to parking operator; these systems may be managed by the parking operator or third-party vendors. These integrations are typically performed by the provider of each user interface when enabling each new parking operator.
The above-noted factors are addressed by aspects of the present invention, which describes a parking management system enabling a network-connected application, software application, or device to generate parking transactions across a plurality of parking operators.
The invention may be best understood by reference to the following description taken in conjunction with the accompanying drawing figures, in which:
Aspects of the present invention introduce features for software-based parking systems to reduce the complexity of supporting many different policy and environment configurations; this allows for a much larger group of user interfaces to provide parking payment functionality than is currently possible in existing solutions.
Now, referring to the drawings wherein identical reference numerals denote the same elements throughout the various views,
As used herein, the term “parking operator” or “facility operator” refers to an entity which controls physical access to a facility such as a parking space or parking lot. Typically, the parking operator or facility operator has legal ownership of or lease rights to the parking space or parking lot and is entitled to permit or deny access to the lot, collect fees for usage of the lot, and/or have unauthorized vehicles removed from the space or lot. A typical example of a parking operator could include a private parking company and/or a city in the case of a municipal parking lot.
A typical parking operator (shown schematically at reference 12 in
In the figures, operative connections between elements or entities are depicted in a single-line format. It will be understood that these are representative of suitable connections for the exchange of data (e.g. wired connections, wireless connections, and/or data networks).
The parking management system 10 includes a transaction database 20, a transaction processing module 22, a rate increment generator 24, and a parking location registry 26. It will be understood that the parking management system 10 may be hosted on one or more computer servers or individual user devices, which are connected to a wide area network. The parking management system 10 is depicted schematically in block diagram format as being hosted on a single computer server. It will be understood that multiple servers or groups of computer servers could be used.
The parking management system 10 is interoperable with one or more user interfaces 28. As used herein, the term “user interface” includes any device or combination of devices having one or more microprocessors operable to execute programmed instructions and supporting components such as an electrical power source (e.g. battery or AC power source), input/output devices (e.g. keyboard, touchscreen display, microphone, and/or speakers), and one or more transceivers operable to communicate data over various network protocols.
In one example, the user interface 28 can be implemented as firmware and/or software in a device such as a parking meter.
In another example, the user interface 28 can be implemented in a mobile computing device. Nonlimiting examples of commercially-available mobile computing devices include laptop computers, tablet computers, vehicle “infotainment” system (i.e. head unit), “smart watches”, and “smartphones”. The mobile computing device may be provisioned with a client software program (also referred to as a “client application” or “client app”) containing appropriate programming for interacting with the method described herein.
In another example, the user interface 28 can be implemented as software accessed through an Internet website (e.g. using an Internet browser program).
User interfaces 28 are able to look up parking locations for any location registered in the system 10, specifically by transmitting a request (1a) to the parking location registry 26, which returns the parking location information (1b). Parking operators may make changes to parking locations from time to time (such as adding or removing new locations, issuing new identifiers, or temporarily closing locations), and these changes are reflected in the system 10 and therefore all connected user interfaces 28 in real time.
Parking locations from any number of parking operators may be registered in the system 10, the locations being stored in the parking location registry 26. When ambiguous parking location identifiers are used, a variety of techniques may be used to determine which zone location a request may be referring to, including the user's location if provided by the user interface 28.
The system 10 provides access to pricing information in a form referred to as “rate increments.” The system 10 provides programmatic access to a series of “rate increments,” calculated by the system 10, specifically the increment generator 24, which describe the cost to park for a given duration based on the vehicle, time of day, local parking policy, local events, parking activity or congestion, and temporary rules/closures. The rate increments may be dependent on formulas or factors as described above. Given a request (2a) from a user interface 28 including a start time, vehicle information, and a parking location the system 10 can provide rate increments (2b) based on the desired parking duration. A visual representation of rate increments is provided in
Referring to
Leveraging rate increments ensures that any Internet-connected user interface 28 can display accurate price information in real time regardless of the parker, user interface 28, local regulations, or device that the application is running on; the complexities of generating the rate increments themselves are performed in the system 10 which allows for very “thin” user interfaces 28 that do not need to be aware of how the calculation was made, and may not have access to information from other clients (such as parking activity/congestion data).
Rate increment calculations based on many complex factors, including both static. e.g., flat cost per hour, or parking duration limits by license plate; or dynamic, e.g., fluctuating price based on nearby parking availability via variables provided at (5) from the transaction database 20. Cities, parking garage operators, and universities may have very diverse rate calculations; however, providing programmatic access to rate increments ensures that connected systems (i.e. user interfaces 28) do not need to be aware of or take additional steps to support this complexity.
User interfaces 28 can complete a transaction by submitting a request (3) to an integrated transaction processing module 22; this module ensures that funds are properly processed and delivered (7) to the parking operator's designed bank account 14, and that support operations (refunds, voids, and other payment-related operations) are available for all transactions regardless of the user interface 28 used to generate the transaction. Stated another way, the user interface 28 does is not required to be programmed to interface with the bank account 14.
When applied to many cities, the parking management system 10 also ensures that funds are routed to the correct bank account 14 at (7) based on the owner of the parking location specified when the transaction was processed. User interfaces 28 do not need to concern themselves with the proper routing of funds.
When a transaction (3) is performed in the transaction processing module 22, data is also generated that can be provided to a variety of internal and external systems, and is routed based on the owner of the parking location. For example, transaction information (4) can be stored in the transaction database 20. In all cases, parking session data is transmitted in real time to enforcement systems at (8) so ensure that parking enforcement officers have access to an up-to-date record of all valid parking sessions; no new integrations or training are required when new user interfaces 28 are added to a parking operator's environment as all parking session data is transmitted through a single flow to the parking enforcement system 16.
In some cases, parking session data may be used in the calculation of rate increments for future transactions; this can enable certain municipal policies that may price based on dynamic signals like parking activity in nearby parking locations (again, summarized for easy consumption by user interfaces 28 via the rate increments).
In some cases, parking session data may be submitted (9) to storage systems 18 maintained by the parking operator 12 or other third parties. The system 10 can provide real-time parking session information from all integrated user interfaces 28 to these storage systems in a consistent format.
The system 10 can support a registry of parking locations from any number of parking operators. These locations are provided to user interfaces 28 via a programmatic interface (1b), but are also used for routing funds, enforcement system integrations, and increment generation when applicable.
By populating the parking location registry 26 with parking locations from multiple operators, user interfaces 28 can leverage the same integration to access parking information and perform parking transactions in any number of locations, regardless of the inputs required to generate the pricing policy (via rate increments), details of how payments are processed, or what additional technologies or services may be active in the environment.
Taken holistically, the system 10 provides a uniform transactional interface that allows for any system, from popular consumer applications, in-dash vehicle systems, commodity hardware devices, autonomous vehicles, and other user interfaces 28 to retrieve parking information and complete parking transactions in any number of parking environments regardless of the policy active in each environment.
Similarly, each parking operator is able to coordinate all user interfaces 28 through the system 10 without regard for the details of each interface (device type, feature set, hardware specifications, etc.).
The parking management system 10 has several advantages over prior art systems. The system reduces the complexity of supporting many different policy an environment configurations; this allows for a much larger group of user interfaces to provide parking payment functionality than is currently possible in existing solutions.
The parking management system 10 provides a method for decoupling environmental details from the user interface 28. As a result, a variety of user interfaces become available that are not possible to support in the prior art.
Leveraging rate increments ensures that any Internet-connected user interface 28 can display accurate price information in real time regardless of the parker or user interface.
The parking management system 10 does not require specialized knowledge or technical effort to support additional parking operators (cities, universities, parking garage operators), regardless of the local policy that drives the pricing or availability of parking spaces. Any number of internet-connected applications, software applications, and devices may utilize the invention to generate parking transactions with no incremental complexity.
Similarly, the parking management system 10 also allows parking operators to manage policies, generate reports, and configure funds flow through a single system regardless of how many end user interfaces may be active in their environment.
With the parking management system 10, providers of user interfaces are not required to make any operator-specific configurations when the system is in use.
The foregoing has described a system for parking management. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive.
Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.
The invention is not restricted to the details of the foregoing embodiment(s). The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.
| Number | Date | Country | |
|---|---|---|---|
| 63073114 | Sep 2020 | US |
