Vehicle detection systems and methods of operation thereof
Abstract
A parking management system and methods of operation are disclosed. In one variation, a computer-implemented method comprises receiving positional data concerning a listing location from a listing client device; establishing a radius boundary based on the positional data; filtering one or more databases using the radius boundary to determine an amount of parking spaces listed and the amount of parking spaces reserved within a preset time period; calculating a location-specific transaction rate using the amount of parking spaces listed, the amount of parking spaces reserved, and the preset time period; determining a recommended listing price based on the location-specific transaction rate; and transmitting the recommended listing price to the listing client device.
Claims
exact text as granted — not AI-modified1 . (canceled)
2 . A parking management system comprising:
a memory; and one or more processors coupled to the memory, the one or more processors being configured to:
receive parking location data relating to a parking location from a listing client device;
determine a radius boundary based on the parking location data, wherein the radius boundary is centered on the parking location;
determine a number of listings within the radius boundary;
determine a recommended listing price for the parking location based on the parking location data and one or more parameters including the number of listings within the radius boundary; and
transmit a signal including the recommended listing price to the listing client device.
3 . The parking management system of claim 2 , wherein the parking location data received from the listing client device includes at least one of a type of the parking location, a size of the parking location, an availability time period of the parking location, a preferred listing price, and a distance to an event venue.
4 . The parking management system of claim 2 , wherein the one or more parameters include at least one of a number of available listings, a number of occupied listings, and an average listing price of the listings within the radius boundary.
5 . The parking management system of claim 2 , wherein determining the radius boundary is based on a size of a geographic region in which the parking location is located.
6 . The parking management system of claim 2 , wherein the one or more processors are configured to:
adjust the radius boundary based on the number of listings within the radius boundary.
7 . The parking management system of claim 2 , wherein the one or more processors are configured to:
adjust the radius boundary based on a time of day, a day of week or month, a season, or a combination thereof.
8 . The parking management system of claim 2 , wherein the one or more processors are configured to:
determine a recommended availability time for the parking location; and transmit the signal including the recommended availability time to the listing client device.
9 . The parking management system of claim 2 , wherein the one or more processors are configured to:
determine that the number of listings within the radius boundary is below a listing threshold; and transmit an alert signal to the listing client device to list the parking location for rent.
10 . The parking management system of claim 2 , wherein the one or more processors are configured to:
determine a recommended penalty rate for the parking location, wherein the recommended penalty rate is charged when a use time of the parking location exceeds a reservation time period.
11 . The parking management system of claim 2 , wherein determining the recommended listing price includes:
determining a transaction rate for the listings within the radius boundary, wherein the transaction rate is the number of the listings within the radius boundary divided by a predetermined time period.
12 . A method comprising:
receiving parking location data relating to a parking location from a listing client device; determining a radius boundary based on the parking location data, wherein the radius boundary is centered on the parking location; determining a number of listings within the radius boundary; determining a recommended listing price for the parking location based on the parking location data and one or more parameters including the number of listings within the radius boundary; and transmitting a signal including the recommended listing price to the listing client device.
13 . The method of claim 12 , wherein the parking location data received from the listing client device includes at least one of a type of the parking location, a size of the parking location, an availability time period of the parking location, a preferred listing price, and a distance to an event venue.
14 . The method of claim 12 , wherein the one or more parameters include at least one of a number of available listings, a number of occupied listings, and an average listing price of the listings within the radius boundary.
15 . The method of claim 12 , wherein determining the radius boundary is based on a size of a geographic region in which the parking location is located.
16 . The method of claim 12 , further comprising:
adjusting the radius boundary based on the number of listings within the radius boundary.
17 . The method of claim 12 , further comprising:
adjusting the radius boundary based on a time of day, a day of week or month, a season, or a combination thereof.
18 . The method of claim 12 , further comprising:
determining a recommended availability time for the parking location; and transmitting the signal including the recommended availability time to the listing client device.
19 . The method of claim 12 , further comprising:
determining that the number of listings within the radius boundary is below a listing threshold; and transmitting an alert signal to the listing client device to list the parking location for rent.
20 . The method of claim 12 , further comprising:
determining a recommended penalty rate for the parking location, wherein the recommended penalty rate is charged when a use time of the parking location exceeds a reservation time period.
21 . A non-transitory computer-readable medium having stored thereon instructions which, when executed by one or more processors, cause the one or more processors to:
receive parking location data relating to a parking location from a listing client device; determine a radius boundary based on the parking location data, wherein the radius boundary is centered on the parking location; determine a number of listings within the radius boundary; determine a recommended listing price for the parking location based on the parking location data and one or more parameters including the number of listings within the radius boundary; and transmit a signal including the recommended listing price to the listing client device.Join the waitlist — get patent alerts
Track US2023066666A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.