Management server, user terminal, parking lot sharing method, parking date and time determination method, parking lot sharing program, and parking date and time determination program

Abstract

To efficiently share and utilize a parking space of a parking lot.SOLUTION: The management server 100 includes the parking frame information terminal 122 that stores the parking frame IDs, the users, the use start dates, and the use date and time information in association with one another, the communication unit 130 receives the parking application information from the user-side storage device 200, the regular contract determination unit 111 determines whether the parking application information is the regular contract, the period determination unit 112 determines whether the parking application date is within the preferential application period, and the parking frame determination unit 113 determines whether the parking frame corresponding to the parking application information can be secured when it is determined that the parking application information is the regular contract and the parking application date is within the preferential application period. When it is determined that the parking frame corresponding to the parking application information can be secured, a parking frame storage part 114 stores the users, the use start date, and the use date information included in the parking application information in a parking frame information terminal 122 in association with the parking frame ID, and a communication part 130 transmits the propriety of securing the parking frame to a users' storage device 200.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a management server, a user terminal device, a parking lot sharing method, a parking date and time determination method, a parking lot sharing program, and a parking date and time determination program. [Background technology]

[0002] There are two ways to secure a parking space in a parking lot: a fixed-term contract, which continues unless the contract is cancelled, and hourly parking, which can be reserved or not, when there is space available in the parking lot. With a fixed-term contract, you can park in the parking space at any time, but contract holders rarely park all day, and there are many times when the space is not parked. In light of this situation, a technology has been disclosed that accepts registration of vacant times when a vehicle is not using the parking space from users with fixed-term contracts, publishes the vacant parking space times, and invites temporary use by the hour (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2003-016590 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the technology described in Patent Document 1 requires the contractor to rent a parking space for the entire time and then register the unused time, so unless the contractor registers, the contractor cannot use the available time and the parking space cannot be used efficiently.

[0005] The present invention has been made in consideration of the above, and aims to provide a management server, a user terminal device, a parking lot sharing method, a parking date and time determination method, a parking lot sharing program, and a parking date and time determination program that enable efficient sharing and utilization of parking spaces in a parking lot. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, the present invention is characterized by comprising a parking space information storage unit that stores a parking space ID that identifies a parking space, a user, a usage start date, and usage date and time information in association with each other, receives parking application information from the user terminal device, determines whether the parking application information is for a fixed-term contract, determines whether the parking application date on which the parking application information was received is within the priority application period, and if it is determined that the parking application information is for a fixed-term contract and the parking application date is within the priority application period, determines whether a parking space corresponding to the parking application information can be secured, and if it is determined that a parking space corresponding to the parking application information can be secured, stores the user, usage start date, and usage date and time information included in the parking application information in association with the parking space ID that identifies the parking space in the parking space information storage unit, and transmits whether the parking space can be secured to the user terminal device.

[0007] In another aspect of the present invention, the system includes a parking space information storage unit that stores a parking space ID that identifies a parking space, a user, a usage start date, and usage date and time information in association with each other, receives parking application information from a user terminal device, determines whether the parking application information is for a fixed-term contract, and if it determines that the parking application information is for a fixed-term contract, determines whether the parking application date, which is the day the parking application information was received, is within the primary application period, and if it determines that the parking application date is within the primary application period, stores the parking application information in the primary application information storage unit, matches the parking application information stored in the primary application information storage unit, and if a parking space corresponding to the parking application information is secured through matching, stores the user, usage start date, and usage date and time information included in the parking contract application information in the parking space information storage means in association with the parking space ID that identifies the parking space, and transmits whether the parking space was secured to the user terminal device. [Effects of the Invention]

[0008] According to the present invention configured as described above, it is possible to efficiently share and utilize parking spaces in a parking lot. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a configuration of a parking lot sharing system 10 according to a first embodiment. [Figure 2] 2 is an explanatory diagram showing an example of the data configuration of a parking lot information storage unit 121 and a parking space information storage unit 122. FIG. [Figure 3] 10 is a flowchart showing a parking lot sharing process executed by the management server 100 and the user terminal device 200. [Figure 4] FIG. 10 is an explanatory diagram showing the relationship between each user's parking application information, fixed-term contract application period, and fixed-term contract period. [Figure 5] 10 is a flowchart showing a parking space frame cancellation process procedure executed by the management server 100 and the user terminal device 200. [Figure 6] 10 is a flowchart showing a procedure of a fixed-term contract renewal process executed by the management server 100. [Figure 7] FIG. 10 is a block diagram showing a configuration of a parking lot sharing system 20 according to a second embodiment. [Figure 8] 10 is a flowchart showing a parking lot sharing process executed by the management server 300 and the user terminal device 200. [Figure 9] 10 is a flowchart showing a parking space matching process executed by the management server 300 and the user terminal device 200. [Figure 10] FIG. 10 is an explanatory diagram showing the relationship between each user's parking application information, application period, and fixed-term contract period. [Figure 11] FIG. 11 is an explanatory diagram showing the relationship between a beacon device 400 installed in a parking lot and a user terminal device 200 in the third embodiment. [Figure 12] FIG. 11 is a block diagram showing a configuration of user terminal information 200 included in the parking lot sharing system 10 according to the third embodiment. [Figure 13] 10 is a flowchart showing a parking start time determination process executed by the management server 100 and the user terminal device 200. [Figure 14]10 is a flowchart showing a parking end time determination process executed by the user terminal device 200. DETAILED DESCRIPTION OF THE INVENTION

[0010] Below, with reference to the accompanying drawings, examples of embodiments for implementing the management server, user terminal device, parking lot sharing method, parking date and time determination method, parking lot sharing program, and parking date and time determination program according to the present application will be described. The following explanations are examples of embodiments of the present application, and the management server, user terminal device, parking lot sharing method, parking date and time determination method, parking lot sharing program, and parking date and time determination program according to the present application are not limited to these examples.

[0011] Example 1 1 is a block diagram showing a configuration of a parking lot sharing system 10 according to Example 1. The parking lot sharing system 10 includes a management server 100 and user terminal devices 200-1 to 200-n (hereinafter referred to as user terminal devices 200).

[0012] The management server 100 is a server device that manages parking spaces in a parking lot based on parking application information, such as fixed-term contracts or spot reservations, received from a user terminal device 200. The user terminal device 200 is a computer operated by a user who wishes to use the parking lot, and may be a smartphone, tablet device, personal computer, or the like. The management server 100 and the user terminal device 200 are communicatively connected to each other via a network N, and transmit and receive data between the devices. The network N may be any communication network such as the Internet, an intranet, a LAN (Local Area Network), a VPN (Virtual Private Network), or a mobile communication network, or a combination thereof, and some or all of the network may be wired or wireless.

[0013] 1, the management server 100 includes a control unit 110, a storage unit 120, and a communication unit 130. The control unit 110 reads out programs and the like stored in the storage unit 120 and executes the read out programs to function as each unit of the management server 100, controlling each unit and transmitting data to each unit, etc. The control unit 110 functions as a fixed-term contract determination unit 111, a period determination unit 112, a parking space determination unit 113, a parking space storage unit 114, a fixed-term contract renewal unit 115, a reservation information generation unit 116, etc.

[0014] The storage unit 120 stores a parking lot information storage unit 121, a parking space information storage unit 122, and operation programs for controlling each unit, application programs, various control information, intermediate files, etc. (not shown).

[0015] FIG. 2 is an explanatory diagram showing an example of the data configuration of the parking lot information storage unit 121 and the parking space information storage unit 122. The parking lot information storage unit 121 stores information about parking lots. As shown in FIG. 2(a), the parking lot information storage unit 121 stores a parking lot ID, which is information identifying the parking lot, a beacon ID, which identifies a beacon device set in the parking lot, the parking lot name, the location, and other information. A beacon device is a device that emits light or radio waves called a beacon. The beacon device transmits a beacon signal including a beacon ID, which identifies the beacon, at a predetermined period. In addition, location information of the parking lot, etc. may be stored.

[0016] The parking space information storage unit 122 stores information indicating the reservation status of parking spaces. As shown in FIG. 2(b), the parking space information storage unit 122 stores a parking space ID, a parking space ID, a user, a usage start date, usage date and time information, and other information in association with each other. The parking space ID is information that identifies a parking space. A parking space indicates that a user can use any parking space in the parking lot; it does not have to be a predetermined parking space within the parking lot. For example, if a parking lot has five parking spaces and three parking spaces, a user who has reserved one parking space can park in any of the five parking spaces. In this way, by not fixing a parking space for each user, even if a user who has a fixed-term contract or a spot reservation exceeds their parking time, the excess time can be adjusted using two parking spaces other than the three parking spaces. Furthermore, by associating multiple parking space IDs with one parking space ID, multiple parking lots can be treated as a single parking lot and managed as parking spaces.

[0017] The user is information that uniquely identifies the user, such as the user name or user ID. The usage start date is the contract start date in the case of a fixed-term contract, and the usage date in the case of a spot reservation. Note that there may be multiple usage dates or a fixed period. In the case of a fixed-term contract, usage date and time information stores the weekday (weekday or holiday) on which parking is performed during the contract period, the day of the week, the parking start time and parking end time, etc. In the case of a spot reservation, the parking start time and parking end time for each usage date are stored. Other information stored in the case of a fixed-term contract is the contract period, for example, one month, three months, one year, etc. Note that the parking start time and parking end time for a fixed-term contract may be, for example, a predetermined time period (early morning (until 7:00), morning (7:00-12:00), afternoon (12:00-17:00), nighttime (from 17:00)), or a time convenient for the user, or a combination of both.

[0018] The communication unit 130 transmits and receives data between the user terminal device 200 and other devices via the network N. More specifically, the communication unit 130 receives parking application information from the user terminal device 200 and transmits to the information processing device 200 whether or not a parking space can be secured for the parking application information.

[0019] Next, the fixed-term contract determination unit 111, period determination unit 112, parking space determination unit 113, parking space storage unit 114, fixed-term contract renewal unit 115, and reservation information generation unit 116 that function in the control unit 110 of the management server 100 will be described.

[0020] The fixed-term contract determination unit 111 determines whether the parking application is for a fixed-term contract based on the parking application information received from the user terminal device 200. More specifically, the fixed-term contract determination unit 111 determines whether the parking application is for a fixed-term contract based on whether the parking application is for a fixed-term contract or a spot reservation included in the parking application information. The parking application information includes a parking lot ID that identifies the parking lot the user wishes to use, whether it is for a fixed-term contract or a spot reservation, the start date of use, and information on the date and time of use. Note that instead of the parking lot ID, an area including multiple parking lots may be specified.

[0021] The period determination unit 112 determines whether the parking application date is within the priority application period, the normal application period, or any other period based on the application date when the parking application information was received (hereinafter referred to as the parking application date) and the usage start date included in the parking application information. The period determination unit 112 determines whether the date when the cancellation information was received (hereinafter referred to as the cancellation application date) is within the renewal cancellation period.

[0022] The parking space determination unit 113 determines whether a parking space can be reserved based on the use start date and use date and time information included in the parking application information. More specifically, the parking space determination unit 113 determines whether a parking space can be reserved based on the use start date and use date and time information in the parking space information storage unit 122.

[0023] When the parking space storage unit 114 determines that a parking space corresponding to the parking application information can be secured, it stores the user, use start date, and use date and time information included in the parking application information in association with the parking space ID secured as the parking space in the parking space information storage unit 122. The parking space storage unit 114 deletes the user, use start date, and use date and time information associated with the parking space ID corresponding to the cancellation information from the parking space information storage unit 122.

[0024] If the fixed-term contract renewal unit 115 determines that the renewal / cancellation period for a parking space has elapsed, it updates the use start date for each parking space stored in the parking space information storage unit 122. If the fixed-term contract renewal unit 115 determines that the cancellation reception date is not within the renewal / cancellation period, it determines that the fixed-term contract cannot be canceled.

[0025] The reservation information generation unit 116 generates reservation information based on the usage start date and usage date and time information for each user stored in the parking space information storage unit 122. The reservation information includes a beacon ID that identifies a beacon device placed in the reserved parking lot, the reserved parking start date and time, the reserved parking end date and time, etc.

[0026] 3 is a flowchart showing the procedure of the parking lot sharing process executed by the management server 100 and the user terminal device 200. The parking lot sharing process executed in the parking lot sharing system 10 configured as described above will be explained.

[0027] The user terminal device 200 executes a user authentication process with the management server 100 (step S301). More specifically, the user terminal device 200 accepts input of a user ID, password, etc., registered in advance in the management server 100, and authenticates the user authentication information, such as the user ID and password, with the management server 100. The user terminal device 200 accepts input of parking application information (step S302). The parking application information includes the parking lot ID associated with the parking lot selected on the screen, whether it is a fixed-term contract or spot reservation, the start date of use, and information on the date and time of use. Whether it is a fixed-term contract or spot reservation is a selection between a fixed-term contract that is renewed every contract period (e.g., one month) or a spot reservation for one or several days.

[0028] If you select a fixed-term contract, enter the usage start date, usage date and time information, etc. The usage start date is the date when you start using the parking lot under the fixed-term contract, and is the base date for each period. The parking date and time information is information about the usage date and time during the fixed-term contract period, such as whether it is a weekday or holiday, the day of the week, the start time of parking, and the end time of parking. For example, it could be "weekdays Monday to Friday 12:00 to 17:00," and the time can be different for each day of the week.

[0029] If you select spot reservation, enter the date and time of use. The date of use is the date on which you will use the parking lot, and can be multiple dates. The time of use is from the start of parking to the end of parking. The time can be different for each day of use.

[0030] The user terminal device 200 transmits the parking application information input from the screen to the management server 100 (step S303).

[0031] The communication unit 130 of the management server 100 receives the parking application information. The fixed-term contract determination unit 111 determines whether the parking application information is a fixed-term contract (step S304). More specifically, the fixed-term contract determination unit 111 determines whether the parking application information is a fixed-term contract based on whether the parking application information is a fixed-term contract or a spot reservation.

[0032] If it is determined that the parking application information is a fixed-term contract (step S304: Yes), the period determination unit 112 determines whether the parking application date is within the priority application period (step S305). More specifically, the period determination unit 112 determines whether the parking application date is within the priority application period based on the usage start date.

[0033] Figure 4 is an explanatory diagram showing the relationship between each user's parking application information, the fixed-term contract application period, and the fixed-term contract period. As an example, the priority application period is set to one month before the start date of use until the start date of the fixed-term contract, i.e., one day two weeks before the start date of use, and the standard application period is set to two weeks before the start date of use until the start date of use. In addition, the fixed-term contract period is set to one month, and the period during which renewal and cancellation for the next month can be made is set to 15 days before the renewal date.

[0034] Figure 4(a) shows the case where user A applies for a one-month fixed-term contract on January 11th, with the start date of use being February 11th. In this case, the priority application period is from January 11th to January 27th, and the regular application period is from January 28th to February 11th, so the application date of January 11th is determined to be within the priority application period. The period during which renewal cancellation is possible in March is from January 28th to February 25th. The same determination is made for users B and C. The start date of use may be different for each user, as shown in Figures 4(a) to 4(c).

[0035] If it is determined that the parking application information is not a fixed-term contract (step S304: No) or if it is determined that the date of receipt of the parking application information is not within the priority application period (step S305: No), the period determination unit 112 determines whether the parking application date is within the normal application period (step S306).

[0036] If it is determined that the parking application date falls within the priority application period (step S305: Yes) or if it is determined that the parking application date falls within the normal application period (step S306: Yes), the parking frame determination unit 113 determines whether or not a parking frame can be reserved based on the usage start date and usage date and time information (step S307). More specifically, in the case of a fixed-term contract, the parking frame determination unit 113 refers to the parking frame information storage unit 122 to determine whether or not all parking frames that the user wishes to use from the usage start date to the usage end date can be reserved based on the weekday / holiday status, the day of the week, the parking start time, and the parking end time.

[0037] In Figure 4, for example, if all parking slots are available from February 11 onwards, users A and B can reserve all of the slots in order of application. User C, who applied on January 25, cannot reserve a parking slot because his / her application overlaps with user B's.

[0038] If user B applied on February 11th, which is within the regular application period, and users A and C applied as shown in Figure 4, user B would not be able to secure a parking space because it would overlap with user C's parking space. Furthermore, if user B applied on January 26th, which is within the priority application period, user B would also not be able to secure a parking space because he would be later than user C.

[0039] In the case of a spot reservation, the parking space determination unit 113 determines whether a parking space can be secured based on the date and time of use included in the parking application information by referring to the parking space information storage unit 122. In the case of a spot reservation, the application period may include the current day in addition to the normal application period.

[0040] If it is determined that a parking space can be reserved (step S307: Yes), the parking space storage unit 114 stores the reserved parking space in the parking space information storage unit 122 (step S308). If it is determined that the parking application date is not within the normal application period (step S306: No) or if it is determined that a parking space cannot be reserved (step S307: No), the parking space determination unit 113 determines that a parking space cannot be reserved (step S309). The communication unit 130 transmits whether a parking space can be reserved to the user terminal device 200 (step S310).

[0041] The user terminal device 200 receives the information on whether or not a parking space can be reserved from the management server 100, and displays the received information on whether or not a parking space can be reserved (step S311).

[0042] In this way, by dividing the period during which fixed-term contract applications can be made into a priority application period and a regular application period, it is possible to secure more parking spaces for fixed-term contracts. Also, by setting the priority application period and regular application period according to the start date of use, users can start using the parking lot from a date that is convenient for them.

[0043] 5 is a flowchart showing the procedure of the parking space slot cancellation process executed by the management server 100 and the user terminal device 200. The parking space slot cancellation process executed in the parking space sharing system 10 will be described.

[0044] The user terminal device 200 executes user authentication processing with the management server 100 (step S501). The user terminal device 200 accepts input of cancellation information (step S502). More specifically, the user accepts input of cancellation information by selecting a fixed-term contract or spot reservation displayed on the screen and instructing cancellation. The cancellation information includes at least the parking slot ID, whether the contract is a fixed-term contract or spot reservation, and the user. The user terminal device 200 transmits the cancellation information to the management server 100 (step S503).

[0045] The communication unit 130 of the management server 100 receives the cancellation information. The fixed-term contract determination unit 111 determines whether the cancellation information is for a fixed-term contract (step S504). If it is determined from the cancellation information that the contract is for a fixed-term contract (step S504: Yes), the period determination unit 112 determines whether the cancellation application date is within the renewal cancellation period (step S505). More specifically, the period determination unit 112 obtains the use start date associated with the parking space ID from the parking space information storage unit 122, and calculates the renewal cancellation period based on the obtained use start date. The period determination unit 112 determines whether the cancellation application date is within the renewal cancellation period based on the use start date.

[0046] If it is determined from the cancellation information that the contract is not a fixed-term contract (step S504: No) or if it is determined that the cancellation application date is within the renewal / cancellation period (step S505: Yes), the parking space storage unit 114 deletes the parking space corresponding to the cancellation information from the parking space information storage unit 122 (step S506). More specifically, the parking space storage unit 114 deletes the user, use start date, and use date / time information corresponding to the parking space ID included in the cancellation information from the parking space information storage unit 122. If it is determined that the cancellation application date is not within the renewal / cancellation period (step S505: No), the fixed-term contract renewal unit 115 determines that the fixed-term contract cannot be canceled (step S507). The communication unit 130 transmits whether the cancellation is possible to the user terminal device 200 (step S508).

[0047] The user terminal device 200 receives the cancellation permission / prohibition information from the management server 100 and displays the received cancellation permission / prohibition information (step S509).

[0048] In this way, a fixed-term contract can be canceled if the cancellation application date falls within the renewal / cancellation period, and a spot reservation can be canceled by deleting the parking slot when cancellation information is received. By specifying a renewal / cancellation period for a fixed-term contract, it is possible to accept applications for a new fixed-term contract after the renewal / cancellation period has expired, thereby minimizing vacant parking slots.

[0049] 6 is a flowchart showing the procedure of the fixed-term contract renewal process executed by the management server 100. The fixed-term contract renewal process executed in the parking lot sharing system 10 will be described.

[0050] The fixed-term contract renewal unit 115 of the management server 100 acquires the use start date from the parking space information storage unit 122 (step S601). The fixed-term contract renewal unit 115 calculates the renewal cancellation period based on the use start date (step S602). The fixed-term contract renewal unit 115 determines whether the renewal cancellation period has passed (step S603).

[0051] If it is determined that the renewal cancellation period has elapsed (step S603: Yes), the fixed-term contract renewal unit 115 updates the usage start date (step S604). If it is determined that the renewal cancellation period has not elapsed (step S603: No), the process ends.

[0052] In this way, by updating the usage start date to the next usage start date when the renewal cancellation period has passed, the fixed-term contract can be easily renewed.

[0053] <Example 2> In the above-mentioned Example 1, parking spaces were secured in the order in which the fixed-term contracts were accepted, but in Example 2, fixed-term contracts accepted during the initial application period are combined and matched to minimize the number of available parking spaces.

[0054] 7 is a block diagram showing the configuration of a parking lot sharing system 20 according to Example 2. The parking lot sharing system 20 includes a management server 300 and a user terminal device 200. In the management server 300, the components with the same reference numerals as those in Example 1 have almost the same functions and configurations as those in Example 1, and therefore their explanations are omitted and reference is made to the explanation of Example 1.

[0055] The management server 300 is a server device that manages parking spaces in a parking lot based on parking application information received from the user terminal device 200. As shown in Fig. 7, the management server 300 includes a control unit 310, a storage unit 320, and a communication unit 130. The control unit 310 functions as a fixed-term contract determination unit 111, a period determination unit 312, a parking space determination unit 313, a parking space storage unit 114, a fixed-term contract renewal unit 115, a reservation information generation unit 116, a parking space matching unit 317, etc.

[0056] The storage unit 320 stores a parking lot information storage unit 121, a parking space information storage unit 122, a primary application information storage unit 323, and operation programs for controlling each unit, application programs, various control information, intermediate files, etc. (not shown). The primary application information storage unit 323 stores parking application information received within a primary application period.

[0057] The period determination unit 312 determines whether the parking application date is within the primary application period, the secondary application period, or any other period. If the period determination unit 312 determines that the parking application date is within the primary application period, it stores the parking application information in the primary application storage unit 323. The period determination unit 312 determines whether it is the date for notifying whether or not a fixed-term contract is possible.

[0058] The parking space matching unit 317 acquires parking application information from the primary application information storage unit 323, and performs matching based on the acquired parking application information and information about parking spaces stored in the parking space information storage unit 122 so as to minimize the number of vacant parking spaces stored in the parking space information storage unit 122.

[0059] The parking space determination unit 313 determines whether a parking space can be secured in order of the parking application date based on the parking application information for fixed-term contract or spot reservation received from the user terminal device 200.

[0060] 8 is a flowchart showing the procedure of the parking lot sharing process executed by the management server 300 and the user terminal device 200. The parking lot sharing process executed in the parking lot sharing system 20 configured as described above will be described.

[0061] The user terminal device 200 executes user authentication processing with the management server 300 (step S801). The user terminal device 200 accepts input of parking application information (step S802). The user terminal device 200 transmits the parking application information accepted as input from the screen to the management server 300 (step S803).

[0062] The communication unit 130 of the management server 300 receives the parking application information from the user terminal device 200. The fixed-term contract determination unit 111 determines whether the parking application information is a fixed-term contract (step S804). If it is determined that the parking application information is a fixed-term contract (step S804: Yes), the period determination unit 312 determines whether the parking application date is within the primary application period (step S805). If it is determined that the parking application date is within the primary application period (step S805: Yes), the period determination unit 312 stores the parking application information in the primary application information storage unit 323 (step S806).

[0063] If it is determined that the parking application date is not within the primary application period (step S805: No), the period determination unit 312 determines whether the parking application date is within the secondary application period (step S807). If it is determined that the parking application date is within the secondary application period (step S807: Yes), the parking frame determination unit 313 determines whether a parking frame can be reserved based on the parking application information (step S808). If it is determined that a parking frame can be reserved based on the parking application information (step S808: Yes), the parking frame storage unit 114 stores the reserved parking frame in the parking frame information storage unit 122 (step S809). If it is determined that the parking application date is not within the secondary application period (step S807: No) or if it is determined that a parking frame cannot be reserved based on the parking application information (step S808: No), the parking frame determination unit 313 determines that a parking frame cannot be reserved (step S810).

[0064] If it is determined that the parking application information is not a fixed-term contract (step S804: No), the period determination unit 312 determines whether or not the application period for spot reservations is within (step S811). If it is determined that the application period for spot reservations is within (step S811: Yes), the parking frame determination unit 313 determines whether or not a parking frame can be reserved based on the parking application information (step S812). If it is determined that a parking frame can be reserved based on the parking application information (step S812: Yes), the parking frame storage unit 114 stores the reserved parking frame in the parking frame information storage unit 122 (step S813). If it is determined that the application period for spot reservations is not within (step S811: No) or if it is determined that a parking frame cannot be reserved (step S812: No), the parking frame determination unit 313 determines that a parking frame cannot be reserved (step S814). The communication unit 130 transmits to the user terminal device 200 the notification date of whether the fixed-term contract is possible or not if the contract is for a fixed-term contract and is within the primary application period, or transmits whether the parking space can be secured or not in other cases (step S815).

[0065] The user terminal device 200 receives the fixed-term contract availability notification date or the availability of a parking space from the management server 300, and displays the received fixed-term contract availability notification date or the availability of a parking space (step S816).

[0066] 9 is a flowchart showing the procedure of the parking space matching process executed by the management server 300 and the user terminal device 200. The parking space matching process executed in the parking lot sharing system 20 will be described.

[0067] The period determination unit 312 of the management server 300 determines whether it is the fixed-term contract availability notification date (step S901). If it is determined that it is not the fixed-term contract availability notification date (step S901: No), the processing ends. If it is determined that it is the fixed-term contract availability notification date (step S901: Yes), the parking space matching unit 317 acquires parking application information from the primary application information storage unit 323 (step S902). The parking space matching unit 317 matches a parking space based on the parking application information and the parking space information stored in the parking space information storage unit 122 (step S903).

[0068] Figure 10 is an explanatory diagram showing the relationship between each user's parking application information, application period, and fixed-term contract period. In the example shown in Figure 10, users A, B, and C have applied for monthly fixed-term contracts starting in February, with the primary application period being January 11th to January 17th, the secondary application period being January 18th to January 24th, and the notification date for whether the fixed-term contract will be accepted being January 25th.

[0069] If User A applies for a fixed-term contract from 5 PM on Friday to 7 AM on Monday, User B applies for a fixed-term contract from 12 PM to 5 PM on Monday and Wednesday, and User C applies for a fixed-term contract from 7 AM to 5 PM on Monday through Wednesday, then regardless of the order in which the application information of User A, User B, and User C is received within the primary application period, User A and User C will be deemed to have secured a parking space with the fewest available spaces.

[0070] The parking space determination unit 313 determines whether a parking space can be secured based on the parking application information through matching (step S904). If it is determined that a parking space can be secured based on the parking application information (step S904: Yes), the parking space storage unit 114 stores the secured parking space in the parking space information storage unit 122 (step S905). If a parking space cannot be secured (step S904: No), the parking space determination unit 313 determines that a parking space cannot be secured (step S906). The communication unit 130 transmits whether a parking space can be secured to the user terminal device 200 (step S907).

[0071] The user terminal device 200 receives the information on whether or not a parking space can be reserved from the management server 300, and displays the received information on whether or not a parking space can be reserved (step S908).

[0072] In this way, by providing a primary application period and a secondary application period, parking application information received during the primary application period is matched to minimize available parking spaces, and parking application information received during the secondary application period is reserved in order of the parking application date, thereby minimizing available parking spaces. Furthermore, because spot reservations are accepted after the secondary application period, parking spaces can be filled at any time even if a parking space becomes available under a fixed-term contract. Furthermore, if a parking space is available, parking on the day without a reservation can be made available, further filling up parking spaces. The fixed-term contract cancellation process and fixed-term contract renewal process are similar to those in Example 1, and therefore their explanation will be omitted here. Please refer to Figures 5 and 6 and the explanation of Example 1.

[0073] Example 3 In the third embodiment, a parking time calculation process will be described for the case where a user actually uses a parking lot after making a fixed-term contract or a spot reservation in the first and second embodiments described above. FIG. 11 is an explanatory diagram showing the relationship between a beacon device 400 and a user terminal device 200 installed in a parking lot in the third embodiment. The beacon device 400 is installed in the parking lot 11, and the beacon device 400 transmits a beacon signal. The beacon device 400 is placed so that the communication range of the beacon device 400 covers the entire parking lot 11, or so that the beacon signal can be received when the vehicle 12 or the user terminal device 200 enters or exits the parking lot 11. Note that the number of beacon devices 400 is not limited to one, and there may be multiple beacon devices 400.

[0074] Figure 11(a) shows when vehicle 12 enters parking lot 11. When entering, the user terminal device 200 carried by the user in vehicle 12 receives a beacon signal. Figure 11(b) shows the state when vehicle 12 is parked in parking lot 11. When parking, the user carries user terminal device 200 and moves away from vehicle 12, so user terminal device 200 does not receive a beacon signal. Figure 11(c) shows when vehicle 12 leaves parking lot 11. When leaving, the user's user terminal device 200 receives a beacon signal.

[0075] 12 is a block diagram showing the configuration of user terminal information 200 included in the parking lot sharing system 10 or 20 (hereinafter referred to as the parking lot sharing system 10, etc.) according to Example 3. As shown in FIG. 12, the user terminal information 200 includes a control unit 210, a storage unit 220, a communication unit 230, a short-range communication unit 240, and an operation display unit 250.

[0076] The control unit 210 reads out programs stored in the memory unit 220 and executes the read out programs to function as each unit of the user terminal information 200, controlling each unit and transmitting data to each unit, etc. The control unit 210 functions as a parking lot determination unit 211, a parking date and time determination unit 212, etc.

[0077] The memory unit 220 stores a reservation information memory unit 221, a parking date and time memory unit 222, and operation programs for controlling each unit, application programs, various control information, intermediate files, etc. (not shown). The reservation information memory unit 221 stores reservation information received from the management server 100 or 300 (hereinafter referred to as the management server 100, etc.). The reservation information includes a beacon ID that identifies a beacon device placed in a reserved parking lot, a reserved parking start date and time, a reserved parking end date and time, etc. The parking date and time memory unit 222 stores the parking start date and time when the vehicle actually entered the parking lot and the parking end date and time when the vehicle actually exited the parking lot, which correspond to the reserved parking start date and time and the reserved parking end date and time.

[0078] The communication unit 230 transmits and receives data to and from other devices such as the management server 100 via the network N. More specifically, the communication unit 230 receives reservation information from the management server 100 or the like, and stores the received reservation information in the reservation information storage unit 221. The communication unit 230 transmits the user and the parking start date and time, the parking end date and time, or the user and the overtime to the management server 100 or the like.

[0079] When the user terminal information 200 enters the communication range of the beacon device 400 installed in the parking lot and becomes communicable, the short-range communication unit 240 receives the beacon signal transmitted by the beacon device 400 and acquires the beacon ID included in the beacon signal.

[0080] The operation display unit 250 accepts operations on the user terminal information 200 and displays responses to the operations, characters, images, etc. The operation display unit 250 may be a touch panel or the like configured by superimposing a liquid crystal display and a touch sensor.

[0081] Next, the parking lot determination unit 211 and parking date and time determination unit 212 that function in the control unit 210 of the user terminal information 200 will be described.

[0082] The parking lot determination unit 211 determines whether the parking lot from which the user terminal device 200 received the beacon signal is a parking lot reserved under a fixed-term contract or spot reservation based on whether the beacon ID included in the beacon signal matches the beacon ID stored in the reservation information storage unit 221.

[0083] The parking date and time determination unit 212 determines whether the date and time of communication establishment with the beacon device 400 is before the parking start reservation date and time stored in the reservation information storage unit 221. If the parking date and time determination unit 212 determines that the communication establishment date and time is before the parking start reservation date and time, it sets the communication establishment date and time as the parking start date and time, and if it determines that the communication establishment date and time is not before the parking start reservation date and time, that is, the communication establishment date and time is after the parking start reservation date and time, it sets the parking start reservation date and time as the parking start date and time.

[0084] If the parking start date and time has been stored in the parking date and time storage unit 222, the parking date and time determination unit 212 determines whether the date and time of communication establishment with the beacon device 400 is later than the parking end reservation date and time stored in the reservation information storage unit 221. If the parking date and time determination unit 212 determines that the communication establishment date and time is later than the parking end reservation date and time, it sets the communication establishment date and time as the parking end date and time, and if it determines that the communication establishment date and time is not later than the parking end reservation date and time or is earlier than the parking end reservation date and time, it sets the parking end reservation date and time as the parking end date and time.

[0085] 13 is a flowchart showing the procedure of the parking start time determination process executed by the management server 100 and the user terminal device 200. The parking start time determination process executed by the parking lot sharing system 10 and the like will be described.

[0086] The period determination unit 112 of the management server 100 or the like determines whether or not it is a predetermined time (step S1301). The predetermined time is, for example, the day before the start date of use for each user. If it is determined that it is not a predetermined time (step S1301: No), the process returns to step S1301. If it is determined that it is a predetermined time (step S1301: Yes), the reservation information generation unit 116 generates reservation information (step S1302). The reservation information includes a beacon ID transmitted from a beacon device 400 installed in the parking lot reserved by the user, a parking start reservation date and time, and a parking end reservation date and time. More specifically, the reservation information generation unit 116 acquires a parking lot ID, a use start date, and use date and time information corresponding to the user from the parking space reservation information storage unit 122, and acquires a beacon ID associated with the acquired parking lot ID from the parking lot information storage unit 121. The reservation information generation unit 116 generates a parking start reservation date and time and a parking end reservation date and time based on the acquired use start date and use date and time information. For example, if the usage start date is "February 11, 2024" and the usage date and time information is "weekday Friday 12:00-17:00," reservation information is generated in which the parking start reservation date and time is February 16 (Friday) 12:00, the parking end reservation date and time is February 16 (Friday) 17:00, February 23 (Friday) is excluded because it is a national holiday, the parking start reservation date and time is March 1 (Friday) 12:00, the parking end reservation date and time is March 1 (Friday) 17:00, the parking start reservation date and time is March 8 (Friday) 12:00, and the parking end reservation date and time is March 8 (Friday) 17:00. The communication unit 130 transmits the reservation information to the user terminal device 200 (step S1303).

[0087] The communication unit 230 of the user terminal device 200 receives the reservation information from the management server 100 or the like and stores the reservation information in the reservation information storage unit 221 (step S1304). The short-range communication unit 240 determines whether or not a beacon signal has been received (step S1305). If it is determined that a beacon signal has not been received (step S1305: No), the process returns to step S1305. If it is determined that a beacon signal has been received (step S1305: Yes), the parking lot determination unit 211 determines whether or not the beacon ID included in the beacon signal matches the beacon ID stored in the reservation information storage unit 221 (step S1306).

[0088] If it is determined that the beacon ID included in the beacon signal matches the beacon ID stored in the reservation information storage unit 221 (step S1306: Yes), the parking date and time determination unit 212 determines whether the communication establishment date and time is before the parking start reservation date and time (step S1307). If it is determined that the communication establishment date and time is before the parking start reservation date and time (step S1307: Yes), that is, if an overtime occurs, the parking date and time determination unit 212 stores the communication establishment date and time as the parking start date and time in the parking date and time storage unit 222 (step S1308). Note that the difference between the parking start reservation date and time and the communication establishment date and time may be calculated as the overtime, and the calculated overtime may be stored in the parking date and time storage unit 222 in addition to or instead of the communication establishment date and time. A certain grace period may be set for the overtime. For example, if the communication establishment date and time is within 30 minutes before the parking start time, an overtime of 0 may be stored in the parking date and time storage unit 222. If it is determined that the communication establishment date and time is not before the parking start reservation date and time (step S1307: No), that is, if no overtime occurs, the parking date and time determination unit 212 stores the parking start reservation date and time as the parking start date and time in the parking date and time storage unit 222 (step S1309). Note that in addition to or instead of the parking start reservation date and time, an overtime of 0 may be stored in the parking date and time storage unit 222.

[0089] If it is determined that the beacon ID included in the beacon signal does not match the beacon ID stored in the storage unit (step S1306: No), i.e., if there is no reservation information, the parking date and time determination unit 212 stores the communication establishment date and time as the parking start date and time in the parking date and time storage unit 222 (step S1310). The communication unit 230 transmits the user and the parking start date and time to the management server 100, etc. (step S1311). Note that step S1311 is transmitted when the user terminal device 200 and the management server 100, etc., become able to communicate via the network N. The communication unit 230 may transmit the user, the parking start date and time, the parking end date and time, and / or the excess time all together after the usage period has elapsed.

[0090] 14 is a flowchart showing the procedure of the parking end time determination process executed by the user terminal device 200. The parking end time determination process executed in the parking lot sharing system 10 and the like will be described.

[0091] The short-range communication unit 240 determines whether a beacon signal has been received (step S1401). If it is determined that a beacon signal has not been received (step S1401: No), the process returns to step S1401. If it is determined that a beacon signal has been received (step S1401: Yes), the parking lot determination unit 211 determines whether the beacon ID included in the beacon signal matches the beacon ID stored in the reservation information storage unit 221 (step S1402). If it is determined that the beacon ID included in the beacon signal matches the beacon ID stored in the reservation information storage unit 221 (step S1402: Yes), the parking date and time determination unit 212 determines whether the parking start date and time has been stored in the parking date and time storage unit 222 (step S1403). If it is determined that the parking start date and time has not been stored in the parking date and time storage unit 222 (step S1403: No), parking has not started, so the parking start time determination process (step S1307 in FIG. 13) is executed.

[0092] If it is determined that the parking start date and time has been stored in the parking date and time storage unit 222 (step S1403: Yes), the parking date and time determination unit 212 determines whether the communication establishment date and time is later than the parking end reservation date and time (step S1404). If it is determined that the communication establishment date and time is later than the parking end reservation date and time (step S1404: Yes), that is, if an overtime occurs, the parking date and time determination unit 212 stores the communication establishment date and time as the parking end date and time in the parking date and time storage unit 222 (step S1405). Note that the difference between the parking end reservation date and time and the communication establishment date and time may be calculated as the overtime, and the calculated overtime may be stored in the parking date and time storage unit 222 in addition to or instead of the communication establishment date and time. A certain grace period may be provided for the overtime; for example, if the communication establishment date and time is within 30 minutes of the parking end time, an overtime of 0 may be stored in the parking date and time storage unit 222. If it is determined that the communication establishment date and time is not later than the reserved parking end date and time (step S1404: No), that is, if no overtime occurs, the reserved parking end date and time is stored as the parking end date and time in the parking date and time storage unit 222 (step S1406). Note that in addition to or instead of the reserved parking end date and time, an overtime of 0 may be stored in the parking date and time storage unit 222.

[0093] If it is determined that the beacon ID included in the beacon signal does not match the beacon ID stored in the reservation information storage unit 221 (step S1402: No), that is, if there is no reservation information, the parking date and time determination unit 212 determines whether the parking start date and time has been stored in the parking date and time storage unit 222 (step S1407).If it is determined that the parking start date and time has not been stored in the parking date and time storage unit 222 (step S1407: No), parking has not started, so the parking start time determination process (step S1310 in FIG. 13) is executed.

[0094] If it is determined that the parking start date and time has already been stored in the parking date and time storage unit 222 (step S1407: Yes), the communication establishment date and time is stored in the parking date and time storage unit 222 as the parking end date and time (step S1408). The communication unit 230 transmits the user and the parking end date and time to the management server 100, etc. (step S1409). Note that step S1409 is transmitted when the user terminal device 200 and the management server 100, etc., become able to communicate via the network N. The communication unit 230 may transmit the user, the parking start date and time, the parking end date and time, and / or the excess time all together after the usage period has elapsed.

[0095] The management server 100 etc. calculates the excess fee for each user based on the parking start date and time, parking end date and time, or excess time received from the user terminal device 200. The management server 100 etc. transmits the calculated excess fee to the user terminal device 200, and the user terminal device 200 settles the excess fee.

[0096] In this way, the user terminal device 200 receives reservation information from the management server 100, etc., and by comparing the reservation information with the communication establishment date and time when receiving a beacon signal, the user terminal device 200 can determine the parking start date and time and the parking end date and time without communicating with the management server 100, etc. This makes it possible to obtain the parking start date and time and / or the parking time exceeded even in environments where communication is difficult, such as when the parking lot is underground. Furthermore, even in the case of a fixed-term contract, it is possible to charge a fee for the excess parking time.

[0097] The hardware configuration of the management server 100, user terminal device 200, and management server 300 according to the above-described embodiments is a typical computer including one or more processors such as a CPU (Central Processing Unit), MPU (Micro-Processing Unit), or GPU (Graphics Processing Unit), and equipped with external storage devices such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), flash memory, and SSD (Solid State Drive), and a communication control device, etc. The above-described configuration and functions are realized by the CPU reading and running programs stored in the ROM, RAM, HDD, etc. The control unit may be an electronic circuit such as an ASIC (Application Specific Integrated Circuit) or PLD (Programmable Logic Device).

[0098] The programs that run on the management server 100, the user terminal device 200, and the management server 300 may be stored on a computer connected to a network such as the Internet and provided by downloading via the network, or may be recorded in an installable or executable file format on a computer-readable recording medium such as a CD-ROM, DVD, USB memory, or SD card and provided. Furthermore, the programs that realize the above-mentioned functions and processes may be provided in the form of an API (Application Programming Interface), SaaS (Software as a Service), or cloud computing.

[0099] The present invention is not limited to the above-described embodiments, and does not necessarily have to be physically configured as shown in the drawings. Furthermore, the present invention can be configured by functionally or physically dividing, integrating, replacing, modifying, or deleting all or part of the components described in the embodiments in any unit depending on various loads, usage conditions, etc. [Explanation of symbols]

[0100] 100... Management server, 110... Control unit, 111... Fixed-term contract determination unit, 112... Period determination unit, 113... Parking space determination unit, 114... Parking space storage unit, 115... Fixed-term contract renewal unit, 116... Reservation information generation unit, 120... Memory unit, 121... Parking lot information memory unit, 122... Parking space information memory unit, 130... Communication unit, 200... User terminal device, 210... Control unit, 211... Parking lot determination unit, 212... Parking date and time determination unit, 220... Memory unit, 221... Reservation information memory unit, 222... Parking date and time information memory unit, 300... Management server, 310... Control unit, 312... Period determination unit, 313... Parking space determination unit, 317... Parking space matching unit, 320... Memory unit, 323... Primary application information memory unit, 324... Secondary application information memory unit, 400... Beacon device

Claims

1. A management server connected to a user terminal device operated by a user via a network, a parking space information storage means for storing a parking space ID for identifying a parking space, a user, a use start date, and use date and time information in association with each other; a receiving means for receiving parking application information from the user terminal device; a fixed-term contract determination means for determining whether the parking application information is a fixed-term contract; a period determination means for determining whether the parking application date, which is the date on which the parking application information is received, is within a priority application period; a parking space determination means for determining whether a parking space corresponding to the parking application information can be secured when it is determined that the parking application information is a fixed-term contract and the parking application date is within the priority application period; a parking space storage means for storing, in the parking space information storage means, information on the user, the start date of use, and the date and time of use included in the parking application information in association with a parking space ID that identifies the parking space when it is determined that a parking space corresponding to the parking application information can be secured; a transmission means for transmitting to the user terminal device whether or not a parking space can be secured, the information being determined by the parking space determination means; A management server comprising:

2. The period determination means determines whether the parking application date is within a normal application period after the priority application period, 2. The management server according to claim 1, wherein the parking space determination means determines whether a parking space corresponding to the parking application information can be secured when it determines that the parking application date is within the normal application period.

3. A management server connected to a user terminal device operated by a user via a network, a parking space information storage means for storing a parking space ID for identifying a parking space, a user, a use start date, and use date and time information in association with each other; a receiving means for receiving parking application information from the user terminal device; a fixed-term contract determination means for determining whether the parking application information is a fixed-term contract; a period determination means for determining whether the parking application date, which is the date on which the parking application information is received, is within a primary application period when the parking application information is determined to be a fixed-term contract; application information storage means for storing the parking application information in a primary application information storage unit when it is determined that the parking application date is within the primary application period; a parking space matching means for matching the parking application information stored in the primary application information storage unit; a parking space storage means for storing, in the parking space information storage means, information on the user, the start date of use, and the date and time of use included in the parking contract application information in association with a parking space ID that identifies the parking space when a parking space corresponding to the parking application information is secured by matching in the parking space matching means; A transmission means for transmitting the availability of the parking space to the user terminal device; A management server comprising:

4. the period determination means determines whether the parking application date is within a secondary application period after the primary application period; The management server according to claim 3, wherein the application information storage means is provided with a parking space determination means that, when it is determined that the parking application date is within the secondary application period, determines whether a parking space corresponding to the parking application information can be secured in order of the parking application date.

5. A user terminal device that communicates with a beacon device installed in a parking lot, a receiving means for receiving reservation information from the management server, the reservation information including a beacon ID for identifying a beacon device installed in the reserved parking lot, a parking start reservation date and time, and a parking end reservation date and time, and storing the received reservation information in a reservation information storage unit; a short-range communication means for receiving a beacon signal from the beacon device; a parking lot determination means for determining whether the parking lot is a reserved parking lot based on whether a beacon ID included in the beacon signal matches the beacon ID stored in the reservation information storage unit; When the parking lot determination means determines that the parking lot is the reserved parking lot, it determines whether the communication establishment date and time with the beacon device is before the parking start reservation date and time stored in the reservation information storage unit, If it is determined that the communication establishment date and time is before the parking start reservation date and time, the communication establishment date and time is set as the parking start date and time; a parking date and time determination means for determining, when it is determined that the communication establishment date and time is not before the reserved parking start date and time, that the reserved parking start date and time is set as the parking start date and time; A user terminal device comprising:

6. When the parking lot determination means determines that the parking lot is the reserved parking lot, the parking date and time determination means determines whether the communication establishment date and time with the beacon device is later than the parking end reservation date and time stored in the reservation information storage unit, If it is determined that the communication establishment date and time is later than the parking end reservation date and time, the communication establishment date and time is set as the parking end date and time; 6. The user terminal device according to claim 5, wherein, when it is determined that the communication establishment date and time is not later than the reserved parking end date and time, the reserved parking end date and time is set as the parking end date and time.

7. A parking space sharing method executed by a computer having a parking space information storage unit that connects to a user terminal device operated by a user via a network and stores a parking space ID that identifies a parking space, a user, a usage start date, and usage date and time information in association with each other, a receiving step of receiving parking application information from the user terminal device; a fixed-term contract determination step for determining whether the parking application information is a fixed-term contract; a period determination step of determining whether the parking application date, which is the date on which the parking application information is received, is within a priority application period; a parking space determination step of determining whether a parking space corresponding to the parking application information can be secured when it is determined that the parking application information is a fixed-term contract and the parking application date is within the priority application period; a parking space storage step of storing, in the parking space information storage unit, user, use start date, and use date and time information included in the parking application information in association with a parking space ID that identifies the parking space, when it is determined that a parking space corresponding to the parking application information can be secured; a transmission step of transmitting to the user terminal device whether or not the parking space can be secured, the transmission step being determined by the parking space determination step; Parking sharing methods including.

8. A parking space sharing method executed by a computer having a parking space information storage unit that connects to a user terminal device operated by a user via a network and stores a parking space ID that identifies a parking space, a user, a usage start date, and usage date and time information in association with each other, a receiving step of receiving parking application information from the user terminal device; a fixed-term contract determination step for determining whether the parking application information is a fixed-term contract; a period determination step of determining whether the parking application date, which is the date on which the parking application information is received, is within a primary application period when the parking application information is determined to be a fixed-term contract; an application information storage step of storing the parking application information in a primary application information storage unit when it is determined that the parking application date is within the primary application period; a parking space matching step of matching the parking application information stored in the primary application information storage unit; a parking space storing step of storing, in the parking space information storage means, information on the user, the start date of use, and the date and time of use included in the parking contract application information in association with a parking space ID that identifies the parking space when a parking space corresponding to the parking application information is secured by matching in the parking space matching step; a transmission step of transmitting the availability of the parking space to the user terminal device; Parking sharing methods including.

9. A parking date and time determination method executed by a computer that communicates with a beacon device installed in a parking lot, comprising: a receiving step of receiving reservation information from the management server, the reservation information including a beacon ID for identifying a beacon device arranged in a reserved parking lot, a parking start reservation date and time, and a parking end reservation date and time associated with each other, and storing the received reservation information in a reservation information storage unit; a short-range communication step of receiving a beacon signal from the beacon device; a parking lot determination step of determining whether the parking lot is the reserved parking lot based on whether a beacon ID included in the beacon signal matches the beacon ID stored in the reservation information storage unit; If it is determined that the parking lot is the reserved parking lot by the parking lot determination step, it is determined whether the communication establishment date and time with the beacon device is before the parking start reservation date and time stored in the reservation information storage unit, If it is determined that the communication establishment date and time is before the parking start reservation date and time, the communication establishment date and time is set as the parking start date and time; a parking date and time determination step of determining, when it is determined that the communication establishment date and time is not before the parking start reservation date and time, the parking start reservation date and time as the parking start date and time; A method for determining parking date and time, including:

10. A parking lot sharing program that causes a computer to execute the parking lot sharing method according to claim 7 or 8.

11. 10. A parking date and time determination program that causes a computer to execute the parking date and time determination method according to claim 9.

Images