Parking rights trading system and parking rights trading program

Abstract

To provide a parking rights trading system and parking rights trading program, which allow, for example, a parking lot operator to consider reasonable parking fees by conducting parking rights trading.SOLUTION: A system for trading the rights to use parking lots PA is provided, the system comprising a sell order reception unit 10 configured to receive sell orders including parking lot usage fee information from multiple business operators BP, a buy order reception unit 20 configured to receive buy orders including requested conditions for parking lots from users US, and a trading unit 50 configured to execute a trade based on matching between a sell order condition and a buy order condition.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a parking right trading system and a parking right trading program for trading parking rights when using a parking lot. [Background technology]

[0002] For example, parking lot reservation systems that accept and manage reservations for using parking lots and act as intermediaries and coordinators between the parking lot operators and parking lot users are known (see Patent Documents 1 and 2).

[0003] However, in the above-mentioned Patent Documents 1 and 2, although intermediation and adjustment are performed when reserving parking spaces, the system does not base sales transactions on, for example, parking fees. Therefore, it is not necessarily clear to operators whether, for example, dynamic pricing can be used to conduct transactions at fair prices while increasing profits. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2018-156197 [Patent Document 2] Japanese Patent Application Publication No. 2018-92209 Summary of the Invention

[0005] The present invention has been made in consideration of the above points, and aims to provide a parking right trading system and a parking right trading program that enable parking lot operators to, for example, consider appropriate parking fees by conducting transactions for the purchase and sale of parking rights.

[0006] The parking right trading system for achieving the above-mentioned objective is a parking right trading system for trading the buying and selling of parking lot usage rights, and is equipped with a sell order receiving unit that receives sell orders including parking lot usage fee information from multiple businesses, a buy order receiving unit that receives buy orders including desired parking lot conditions from users, and a trading unit that executes the transaction based on a match between the sell order conditions and the buy order conditions.

[0007] In the parking rights trading system, the trading section executes transactions based on the match between the conditions of the sell order and the buy order, allowing, for example, a parking lot operator to confirm whether their sell order, i.e., the fee structure for parking lot use that they have set, is in line with the market price.

[0008] In a specific aspect of the present invention, a desired conditions disclosure unit is provided that compiles the desired conditions received by the purchase order receiving unit into a database and makes it public. In this case, parking lot operators can consider appropriate parking fees based on the disclosed desired conditions. Furthermore, parking lot users can place orders at appropriate prices that meet their desired conditions.

[0009] In another aspect of the present invention, a fee information disclosure unit is provided that compiles fee information received by the sell order receiving unit into a database and makes it public. In this case, parking lot operators can determine appropriate parking fees based on the disclosed fee information. Furthermore, parking lot users can place orders at appropriate prices that meet their desired conditions.

[0010] In yet another aspect of the present invention, the sell order receiving unit receives a request to change the fee information, which makes it possible to change the set fee structure for using the parking lot.

[0011] In yet another aspect of the present invention, the purchase order receiving unit receives desired conditions including any one of a time period for using the parking lot, a geographical area, and a desired price range, which enables the parking lot operator to set prices according to the time period for using the parking lot, the geographical area, or the desired price range.

[0012] In yet another aspect of the present invention, the buy order receiving unit receives buy orders for parking fees at limit prices and at market prices, making it possible to receive orders according to the user's need for parking space use.

[0013] In yet another aspect of the present invention, the transaction unit extracts the parking lot with the lowest price information from among the parking lots that meet the desired conditions, thereby making the optimal selection for the user and identifying the appropriate market price standard.

[0014] In yet another aspect of the present invention, a resale acceptance unit is provided that accepts the resale of the usage right for which a transaction has been concluded in the transaction unit, which further broadens the manner in which the parking right can be traded.

[0015] The parking right trading program for achieving the above object is a parking right trading program for trading the buying and selling of parking lot usage rights, accepting selling orders including parking lot usage fee information from multiple businesses, accepting buying orders including desired parking lot conditions from users, and executing the transaction based on a match between the conditions of the selling order and the conditions of the buying order.

[0016] In the parking rights trading program, transactions are executed based on the match between the conditions of the selling order and the conditions of the buying order, so that, for example, a parking lot operator can confirm whether their selling order, i.e., the fee structure for parking lot use that they have set, is in line with the market price. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a conceptual diagram showing an overview of a transaction regarding parking lot use that employs the parking right trading system according to the first embodiment. [Figure 2] 1 is a block diagram showing an outline of the configuration of a parking right trading system. [Figure 3] FIG. 2 is a block diagram illustrating an example of the configuration of a trading unit. [Figure 4]10A and 10B are data diagrams showing information managed in a transaction management database. [Figure 5] FIG. 1 is a conceptual diagram showing an example of a parking lot using a parking rights trading system. [Figure 6] FIG. 10 is a conceptual diagram showing another example of a parking lot using the parking rights trading system. [Figure 7] 10A to 10G are diagrams for explaining terminal operations by a parking lot user when acquiring parking rights. [Figure 8] 10A and 10B are conceptual diagrams showing an example of transaction details to be made public. [Figure 9] 10A is a graph showing the transaction status of parking rights, and FIG. 10B is a diagram showing the difference in transaction between limit orders and market orders in the situation of FIG. 10A. [Figure 10] 10(A) to 10(F) are diagrams for explaining terminal operations for acquiring a parking right using the parking right trading system according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0018] [First embodiment] An example of a parking right trading system according to the first embodiment will be described below with reference to Fig. 1 etc. Fig. 1 is a conceptual diagram showing an overview of a transaction related to parking lot usage that employs a parking right trading system 100 according to this embodiment. As shown in the figure, the parking right trading system 100 is a system that functions as a platform (usage right trading platform) for effecting the buying and selling of parking lot usage rights (parking rights) by acting as an intermediary between multiple businesses BP that manage parking lots and users US of the parking lots.

[0019] In the example shown in Figure 1, each business operator BP accesses a parking rights trading system 100 configured by a cloud (e.g., a system provided by a cloud-type server) CS via a business operator server SS to transmit information about the fee structure of the parking lot they operate (fee structure information), information about available parking spaces, etc. The cloud CS accepts such information from multiple business operators BP as sell orders and stores it in a list or database.

[0020] Meanwhile, parking lot users US can place various orders for parking lot use by accessing the cloud CS via various terminal devices (user terminals TI), such as their smartphones (SM). In other words, the cloud CS extracts parking lots that match the user US's order from various information received from multiple businesses (BP), provides the extracted information to the user US, and accepts purchase orders. In this case, it is assumed that an app for accessing the cloud CS is installed on the user terminal TI (such as a general-purpose smartphone SM), or that the cloud CS website is accessed from a browser.

[0021] Generally, when using a parking lot, a user US makes a reservation or a business accepts reservations. In this case, the user US selects which parking lot to use and pays (settles) the fee determined for each parking lot. In contrast, in this embodiment, the user US places a buy order to acquire a parking right. A buy order can be either a limit order or a market order for the parking fee. When purchasing a parking right, the user US places a buy order specifying, for example, the time of use, geographic area, and desired price range. Therefore, for example, when a market order is placed, the cloud CS constituting the parking right trading system 100 checks whether there are any (matching) options among multiple business operators BP that satisfy various conditions other than the parking fee. From the available options, i.e., among the parking lots that satisfy the desired conditions, the parking lot with the lowest price information (parking fee) is extracted and the transaction for that option is immediately executed.

[0022] On the other hand, if an order is placed at a limit price, Cloud CS checks whether there are any parking spaces that meet the conditions and are being offered for sale at or below the limit price, and if there are, it executes the transaction immediately, just as in the case of a market order (if there are multiple parking spaces, it executes the transaction for the parking space with the lowest price), and if there are no parking spaces, it monitors price fluctuations and waits until one is offered for sale at or below the limit price.

[0023] As described above, the cloud CS constituting the parking right trading system 100 is a system that accepts sell orders including parking lot usage fee information from multiple businesses BP, and buy orders including desired parking lot conditions from users US, and executes the transaction based on a match between the sell order conditions and the buy order conditions. When the sell order and buy order conditions match, the cloud CS executes the transaction and transmits the resulting contract information to the business server SS and the user terminal TI.

[0024] In addition, it is assumed here that the business operator BP and the user US have appropriately completed pre-registration as a prerequisite for conducting the above-mentioned transactions, and that various payment processes associated with buying and selling are possible, for example, on the web.

[0025] In the illustrated example of the configuration on the provider BP side, a provider server SS for accessing the cloud CS manages the various information sent to the cloud CS and is connected to a payment machine (site management device) CM that is installed at the business site (local) BL where the parking lot is located and manages the parking lot. In this case, the provider server SS communicates with the payment machine CM to obtain information (usage information) indicating the usage status of the payment machine CM and transmits contract information (parking usage transaction results) obtained as a result of communication with the cloud CS as, for example, reservation application information for the local parking lot.

[0026] With the above-described configuration, the parking rights trading system 100 functions as a system that mediates the buying and selling of parking rights based on the contents of the sales orders submitted for parking lots at each business location (local) BL.

[0027] In the above example, the parking right trading system 100 is shown as being configured using a cloud CS, but this is not limited to this, and the parking right trading system 100 can be configured in various ways, such as by installing a physical (fixed) server.

[0028] In addition, although the above description states that the parking right trading system 100 is configured using the cloud CS, it may also be understood that the parking right trading system 100 is configured to include, for example, the operator server SS and part of the smartphone SM (user terminal TI).

[0029] An example of the configuration of the parking right trading system 100 will be described below with reference to Fig. 2. In this embodiment, as shown in the figure, the parking right trading system 100 includes a sell order receiving unit 10, a buy order receiving unit 20, and a trading unit 50 to trade the sale and purchase of parking lot usage rights.

[0030] The sell order receiving unit 10 is an interface unit for receiving sell orders including parking lot usage fee information from multiple business operators BP (see FIG. 1). In this embodiment, the sell order receiving unit 10 receives sell orders from each business operator server SS for parking lots PA under the management of each business operator server SS. The sell order receiving unit 10 also receives requests for changes to fee information. In other words, each business operator BP can change the contents of the sell order as appropriate depending on sales of its own parking lot usage.

[0031] The purchase order receiving unit 20 is an interface unit for receiving a purchase order including desired conditions for a parking lot from a user US. In this embodiment, the purchase order receiving unit 20 receives a purchase order (desired conditions) from a user US via a user terminal TI such as a smartphone SM owned by the user US. The contents of the purchase order can also be changed as appropriate.

[0032] The trading unit 50, which is comprised of, for example, a CPU and various storage devices, first analyzes sell orders for multiple parking lots PA received from multiple service provider servers SS via the sell order receiving unit 10. Specifically, the trading unit 50 extracts various information, such as the location of the parking lot, the fee structure, the parking period, and the parking fee fluctuations for each period, and then organizes this information into a database (systematized). The trading unit 50 then analyzes the desired conditions of buy orders received from user terminals TI via the buy order receiving unit 20, compares them with the databased sell orders, extracts those that match the conditions, and executes a transaction based on the match. In this case, as the above transactions are executed, the service provider BP (see FIG. 1) of each parking lot PA can monitor sales and confirm whether its sell orders, i.e., the parking fee structure it has set, are in line with the market price.

[0033] In particular, in this embodiment, the fee information etc. received by the sell order receiving unit 10 and the desired conditions received by the buy order receiving unit 20 are compiled into a database and made public, so that the operator BP of each parking lot PA (see FIG. 1) can consider the appropriate price for the parking fee that he or she has set based on the published desired conditions and fee information. Also, the parking lot user US (see FIG. 1) can place an order at an appropriate price that meets his or her desired conditions.

[0034] Furthermore, the sell order receiving unit 10 is configured to receive requests for changes to fee information, which allows the operator BP (see Figure 1) to change the parking lot usage fee structure that has been set, thereby enabling dynamic pricing to be used to increase profits while conducting transactions at fair prices.

[0035] An example of the configuration of the trading unit 50 having the above-described configuration will be described below with reference to the block diagram shown in Figure 3. As shown in the figure, in this example, the trading unit 50 includes a parking right trading program 51 that is made up of various programs for parking right trading, and a data storage unit 52 that stores various data for parking right trading.

[0036] The parking right trading program 51 is composed of a sell order program SO, a buy order program BO, a transaction execution program TE, a desired conditions disclosure program CD, and a fee information disclosure program PD for trading the sale and purchase of parking lot usage rights.

[0037] The data storage unit 52 also includes a transaction management database MD, a desired conditions disclosure database OD1, and a fee information disclosure database OD2.

[0038] Of the parking right trading program 51, the sell order program SO is a program for performing the analysis processing for the sell orders described above. That is, the sell order program SO analyzes information such as fee information as sell orders for multiple parking lots PA received via the sell order receiving unit 10 (see FIG. 2). Note that the sell order program SO includes a change receiving program CRs to accept and respond to changes to the content of sell orders from the business operator BP. That is, the change receiving program CRs performs processing such as rewriting the content of the analysis results in the sell order program SO in response to changes to the content of sell orders received by the sell order receiving unit 10.

[0039] Of the parking right trading program 51, the buy order program BO is a program for performing the analysis processing for the buy order described above. That is, the buy order program BO analyzes information (including whether it is a market order or a limit order) related to various desired conditions received as a buy order via the buy order receiving unit 20 (see FIG. 2). Note that the buy order program BO also includes a change receiving program CRb to accept and respond to changes to the buy order content from the user US. That is, the change receiving program CRb performs processing such as rewriting the content of the analysis results in the buy order program BO in response to changes to the buy order content received by the buy order receiving unit 20.

[0040] The transaction execution program TE in the parking right transaction program 51 extracts sell order details that meet the desired conditions based on the results of analysis by the sell order program SO and the buy order program BO, provides them to the user US, accepts the user US's intention to purchase, performs the necessary settlement processing, etc., and records the details of the rights (obligations) that have arisen. In this way, a transaction related to parking rights is executed. Once the transaction is executed, the confirmed contract information is notified to the seller and buyer.

[0041] The various data handled by the sell order program SO, buy order program BO, and transaction execution program TE are stored in a transaction management database MD. The transaction management database MD contains information such as that shown in Figures 4(A) and 4(B).

[0042] Figure 4(A) is a data diagram showing a series of data related to multiple business operators BP (see Figure 1). This data includes, as a premise, a business operator ID (business operator registration number) identifying each business operator BP, various information (business operator information) such as the business operator's name and address, notification destinations for notification of contract information, and information related to the attributes of the parking lots, such as the location of the parking lots to be handled (parking lot information). Furthermore, the data stores the sell order content for each parking lot as a result of analysis by the sell order program SO. Furthermore, the data stores a change history, including changes to the sell order content handled by the change acceptance program CRs of the sell order program SO, and the current transaction status as a result of the transaction being executed based on the transaction execution program TE.

[0043] Figure 4(B) is a data diagram showing a series of data related to user US (see Figure 1). Such data includes, as a premise, a business ID (business registration number) that identifies each user US, various information (user information) including the user's name and payment method, and a notification destination to which contract information and the like are notified. In addition to this, the data also stores the desired conditions (including the success or failure of the transaction) that are the result of analysis in the purchase order program BO, and the parking rights that arise when a transaction is executed based on the transaction execution program TE, as well as a usage right ID for identifying these, and the content of the rights corresponding to the usage right ID, along with a change history of the content of the rights.

[0044] 4(A) and 4(B) is not all of the information (data) stored in the transaction management database MD, but only desired conditions and parking information that do not contain personal information are made public, and are compiled into a database to enable extraction of statistical data, and are stored in the desired conditions disclosure database OD1 and the fee information disclosure database OD2. In other words, the data stored in the transaction management database MD is managed within the transaction department 50 without being released (disclosed) to the outside.

[0045] Hereinafter, with reference to Fig. 5 etc., a description will be given of a parking lot PA using the parking right trading system 100 as described above. In the example conceptually shown in Fig. 5, it is assumed that there are separate businesses BP operating multiple parking lots PA (five parking lots A to E) around an airport AR, and that these businesses are registered with the parking right trading system 100, and that users US are able to acquire parking rights using their own user terminals TI (smartphones SM). In the example shown, information about each parking lot PA is transmitted and received to the parking right trading system 100 via a business server SS.

[0046] In the figure, among the multiple parking lots PA, parking lots A and B are located within a 10-minute walk from the airport AR, while parking lot C is located within a 15-minute walk, but is more than 10 minutes away. Meanwhile, parking lots D and E are located farther from the airport AR than parking lots A through C, and are not within walking distance, but are located near the shuttle bus SH terminal BS that leads to the airport AR. In this case, users US whose destination is the airport AR are likely to select a parking lot based on the parking fee of each parking lot PA, as well as locational factors, such as the distance from the airport AR and whether or not a shuttle bus SH is available. In this case, demand for parking lots is also likely to fluctuate depending on the arrival and departure times of flights at the airport AR.

[0047] In another example shown in FIG. 6, there are several potential destination facilities SI (three facilities SIα to SIγ) around multiple parking lots PA (five parking lots A to E). Specifically, of the multiple parking lots PA, parking lot A is located midway between pier WH (facility SIα) and station ST (facility SIβ), about a 10-minute walk from either. Parking lot B is located midway between station ST and baseball park BB (facility SIγ), about a 10-minute walk from either. Meanwhile, parking lot C is the closest parking lot to pier WH (facility SIα) but is far from the other facilities SIβ and SIγ. Parking lot D is the closest parking lot to station ST (facility SIβ) but is far from the other facilities SIα and SIγ. Parking lot E is the closest parking lot to baseball park BB (facility SIγ) but is far from the other facilities SIα and SIβ. In such a case, it is thought that the demand for each parking lot PA will fluctuate greatly depending on the time of events occurring at each of the facilities SIα to SIγ (ship and train arrival and departure times, game start times).

[0048] Under the various circumstances described above, by using the parking right trading system 100, each business operator BP can make various changes in response to fluctuations in demand, such as the number of parking spaces and fee structure accepted via the parking right trading system 100. In particular, in this embodiment, by disclosing the user's desired conditions and fee information for nearby parking lots, it becomes possible to obtain information that can serve as a guide for setting appropriate prices for one's own parking lot.

[0049] On the other hand, by making the above various information public, users US of each parking lot PA can also determine whether their purchase price is appropriate. For example, when placing a buy order at a limit price, they can obtain information that will serve as a guideline for determining whether they are likely to be able to purchase at the set price.

[0050] An example of terminal operation (operation of the smartphone SM) by the user US will be described below with reference to Fig. 7. As shown in Fig. 7(A) and other figures, the description will be given assuming that various operations are performed on the screen GG of the smartphone SM.

[0051] First, Figure 7(A) shows a situation in which a user US selects to purchase a new parking right (a parking lot usage right) by, for example, launching a dedicated app to acquire the right. When such a selection is made, an image prompting the user to select the desired conditions, such as the area (geographical range) of the parking lot, the time of use, and the desired price range, is displayed on the screen GG, as shown in Figure 7(B). For example, if the user selects the area (geographical range) of the parking lot around a certain airport (XX Airport) as shown in Figure 7(C), the situation around the airport AR, as described with reference to Figure 5, is assumed. As desired conditions, options based on the walking time and whether or not a shuttle bus is available are displayed, and the user US can select the option that best suits their needs. Furthermore, as shown in Figure 7(D), the user selects the date and time of use as appropriate. Here, the desired price range can be as shown in Figure 7(E). In other words, the user can choose whether to place an order at a specified price, i.e., a limit order, or a market order without specifying a price. For example, when placing a market order, if there are offers that meet the conditions other than price, the lowest priced offer is selected, and a display such as that shown in Figure 7(F) is displayed, allowing the purchase procedure (execution of the transaction). On the other hand, when placing a limit order, if there are offers that meet the conditions, the lowest priced offer is selected, as in the case of a market order, and the purchase procedure (execution of the transaction) is allowed. However, if there are offers that meet the conditions other than price but are priced below the limit price, a display such as that shown in Figure 7(G) is displayed. The example shown in the figure shows the difference between the limit price and the current lowest price. In this case, the user US must decide whether to maintain the limit price set by the user and wait until a price below the limit price is found, or to change the limit price. In such cases, the user US is expected to refer to publicly available information to determine whether the limit price is reasonable.

[0052] Looking at the above-described aspects from another perspective, it can also be said that the buy order receiving unit 20 receives desired conditions including any of the time of parking lot use, geographical area, and desired price range in the parking right trading system 100. Furthermore, it can also be said that the buy order receiving unit 20 receives limit orders and market orders for parking fees.

[0053] An example of the transaction details to be made public will be explained below with reference to Figure 8 etc. Here, it is assumed that the business operator BP and the user US access the parking right trading system 100 via the business operator server SS and the user terminal TI (smartphone SM), and at this time, the business operator BP and the user US appropriately set search conditions such as location (geographical range) and time, thereby obtaining various information stored in the desired conditions disclosure database OD1 and the fee information disclosure database OD2 (see Figure 3).

[0054] FIG. 8(A) shows an example of a data table that can be obtained based on various data stored in the desired conditions disclosure database OD1. Specifically, data table DA1 shows, for example, the number of deals concluded and the number of views during a specified period in the vicinity of an airport, as shown in FIG. 5, broken down by the time required to reach the airport AR. From this information, each business operator BP can determine the level of demand for each parking lot location during the relevant period. Furthermore, data tables DA2 and DA3 show, for example, the number of deals concluded and the number of views at different times (X o'clock and Y o'clock) on the same day (month and day) for baseball park BB, as shown in FIG. 6, broken down by the time required to reach baseball park BB. From this information, each business operator BP can confirm changes in demand over time.

[0055] Figure 8(B) shows an example of a data table that can be obtained based on various data stored in the fee information disclosure database OD2. Specifically, data AD specifies the location and the time required to get to that location (the location conditions of the parking lot), and also indicates information on the lowest parking fee among the contracted rates when a specified period is specified. Each business operator BP can use the above information to, for example, consider the appropriateness of the price it has set.

[0056] The above information makes it possible to grasp market trends from a multifaceted perspective. Also, knowing this information allows users US to find the right price for their desired products.

[0057] For example, Figure 9(A) is a graph showing the status of parking rights transactions, showing changes over time when the location and other conditions of the parking lot, such as those shown in Figure 8(B), are fixed. Such graphs can be created based on various data stored in the desired conditions disclosure database OD1 and the fee information disclosure database OD2. Specifically, the horizontal axis represents time, and the vertical axis represents price (parking fee) or number of transactions. Histogram H1 shows the time-series changes in the lowest price (parking fee) among parking lots that meet the location and other conditions, and curve C1 shows the time-series changes in the number of transactions. It is expected that each business operator BP will change the price settings for their own parking lot while users US will set or change their desired conditions. In other words, each business operator BP and user US can identify trends and set prices by observing the frequency of transactions and the resulting price fluctuations.

[0058] Hereinafter, referring to FIG. 9(B), the trading differences between the case of the order price and the case of the market order when it fluctuates as shown in FIG. 9(A) will be described. As shown in the figure, at time T1, when a buy order is applied, if it is an order at the market price, the price P1, which is the lowest price at that time, is used as the contract price (market order contract price), and the transaction is concluded at approximately the same time as the application time T1. That is, the application time T1 ≈ the market order transaction conclusion time. On the other hand, if it is assumed that the order is placed at a limit price. Also, let the limit price in this case be P2, and assume that P2 < P1. In this case, at the time of the application time T1, the transaction will not be concluded. In the example shown in the figure, at the time of time T2 (> T1), for the first time, the lowest price P3 becomes P3 < P2, and the transaction is concluded at this time. That is, time T2 becomes the limit order transaction conclusion time, and the price P3 (< P2 < P1) becomes the limit order contract price. Thus, in the aspect of this embodiment, on both the side of the parking lot operator and the user side, while varying the price, according to the balance of demand and supply, various aspects can be adopted. In addition, in the above, for example, the operator may vary not only the price but also the number of available parking spaces for sale.

[0059] As described above, the parking right trading system 100 according to this embodiment is a system for trading the right to use the parking lot PA, and includes a sell order receiving unit 10 that receives sell orders including the fee information for using the parking lot from a plurality of operators BP, a buy order receiving unit 20 that receives buy orders including the desired conditions of the parking lot from the user US, and a trading unit 50 that executes a transaction based on the matching of the conditions of the sell order and the conditions of the buy order. In this case, in the trading unit 50, by executing a transaction based on the matching of the conditions of the sell order and the conditions of the buy order, for example, the operator BP of the parking lot PA can confirm whether its own sell order, that is, the set parking lot usage fee system, etc. is in line with the market.

[0060] 〔Second Embodiment〕 The following describes the parking right trading system according to the second embodiment. This embodiment is a modified version of the parking right trading system 100 according to the first embodiment, and is similar to the first embodiment except that purchased rights can be resold or transferred. Therefore, detailed explanations of each component will be omitted, and reference will be made to matters related to the first embodiment as necessary.

[0061] FIG. 10 is a diagram for explaining terminal operations for acquiring a parking right using the parking right trading system 100 according to this embodiment, and corresponds to FIG.

[0062] As shown in FIG. 10(A), in addition to purchasing a parking right (a parking lot usage right), an option is provided for reselling the purchased right. That is, if resale is selected as shown in FIG. 10(B), an image prompting the user to enter the usage right ID for the purchased right is displayed on screen GG as shown in FIG. 10(C). Once the usage right ID is entered, an image prompting the user to set a resale price is displayed on screen GG as shown in FIG. 10(D). Once the resale price is set, this becomes a new sell order, so to speak, and the user US who purchased the right becomes a business BP. However, in this case, with regard to the subsequent completion of the sale, the parking right trading system 100 acts as an intermediary in the transaction between the user US, who now serves as a business BP, and the new, different user US.

[0063] Alternatively, instead of or similar to the resale described above, transfers may be made between users US as shown in Figures 10(E) and 10(F). That is, when a user US who has purchased a parking right selects transfer as shown in Figure 10(E) to transfer it to another user US, an image prompting the user ID of the transferee is displayed on screen GG as shown in Figure 10(F). Once the user ID is entered, the parking right is transferred to the other user US whose user ID has been entered. In this case, the parking right trading system 100 will make necessary rewrites to the various data shown in Figures 4(A) and 4(B), for example.

[0064] In this case, for example, in the trading unit 50 shown in Figure 3, each unit constituting the parking right trading program 51 functions as a resale acceptance unit that accepts the resale of the parking lot usage right (parking right) for which a transaction has been concluded.

[0065] In this embodiment, the business operator BP can also check whether its own selling order, i.e., the set fee structure for parking lot use, etc., is in line with the market price. In particular, this embodiment can further expand the trading modes of parking rights.

[0066] 〔others〕 The present invention is not limited to the above-described embodiment, and can be embodied in various forms without departing from the spirit and scope of the present invention.

[0067] For example, the content that can be made public in the above is merely an example, and the scope of what can be made public can be changed as appropriate and can take various forms. The scope of what can be made public may also be different for the business operator BP and the user US. The information to be handled, such as various IDs, is also not limited to the above-mentioned one form and can take various forms.

[0068] In the above, the business operator prepares a business server SS and accesses the parking right trading system 100 or the cloud CS through this, but for example, data management etc. may all be managed by the parking right trading system 100 (cloud CS), and the business operator may only notify the current number of parking spaces and the fee schedule. Also, for example, it is conceivable that there is no business operator server SS, and the on-site payment machine CM communicates directly with the parking right trading system 100 (cloud CS).

[0069] Furthermore, among the above, for example, the options shown in Figures 7(A) and 10(A) include change and cancellation in addition to new purchase, etc. However, it is also possible to not provide these options, or to impose certain restrictions or additional fees when selecting these options. It is also possible to use an appropriate combination of the options exemplified in Figures 7(A), 10(A), and 10(E).

[0070] In addition, in the above, the user terminal TI is a general-purpose smartphone SM, but this is not limited to this, and various devices that can communicate with the parking right trading system 100 can be used as the user terminal TI. [Explanation of symbols]

[0071] 10...sell order reception unit, 20...order reception unit, 50...trading unit, 51...parking right trading program, 52...data storage unit, 100...parking right trading system, AD...data, AR...airport, BB...stadium, BL...business location (local), BO...order program, BP...business operator, BS...departure / arrival point, C1...curve, CD...desired conditions disclosure program, CM...adjustment machine (site management device), CRb...change reception program, CRs...change reception program, CS...cloud, DA1, DA2, DA3... Data table, GG...screen, H1...histogram, MD...database for transaction management, OD1...database for disclosing desired conditions, OD2...database for disclosing fare information, P1-P3...price, PA...parking lot, PD...fare information disclosure program, SH...shuttle bus, SI, SIα~SIγ...facilities, SM...smartphone, SO...sell order program, SS...operator server, ST...station, T1, T2...time, TE...transaction execution program, TI...user terminal, US...user, WH...pier

Claims

1. a selling order receiving unit that receives selling orders including parking lot usage fee information from a plurality of businesses when trading the right to use the parking lot; a purchase order receiving unit that receives a purchase order including desired conditions for the parking lot from a user; a trading unit that executes a transaction based on a match between the conditions of the sell order and the conditions of the buy order; Equipped with The transaction unit indicates to the operator the demand for parking lots for each location condition based on the fee information and the desired conditions, A parking rights trading system in which the trading section includes information on the number of transactions or number of views by travel time from the parking lot to the facility as target data to be presented to the business operator.

2. 2. The parking right trading system according to claim 1, wherein the target data presented to the business operator in the trading unit includes information on changes in demand over time.

3. The parking right trading system according to claim 1 , wherein the selling order receiving unit receives an application for changing the fee information.

4. 4. The parking right trading system according to claim 1, wherein the purchase order receiving unit receives the desired conditions including any one of the period of parking lot use, the geographical area, and the desired price range.

5. 5. The parking right trading system according to claim 1, wherein the buy order receiving unit receives the buy order for the parking fee either at a limit price or at a market price.

6. 6. The parking right trading system according to claim 1, wherein the trading unit extracts the parking lot whose fee information is the lowest among the parking lots that satisfy the desired conditions.

7. 7. The parking right trading system according to claim 1, further comprising a resale acceptance unit that accepts resale of the usage right that has been traded in the trading unit.

8. A method for providing a computer with a procedure for accepting selling orders including parking lot usage fee information from multiple businesses when conducting a sale transaction of parking lot usage rights; A procedure for accepting a purchase order from a user including desired conditions for the parking lot; executing a transaction based on a match between the terms of the sell order and the terms of the buy order; a procedure for indicating to a business operator the demand for parking spaces for each location condition based on the fee information and the desired conditions; A parking right trading program for executing A parking rights trading program that, in a procedure for showing to a business operator the demand for parking spaces based on their location conditions, includes information on the number of successful transactions or number of views based on the travel time required from the parking space to the facility as target data to be shown to the business operator.

Images