Sharing management device and sharing system

Abstract

To more efficiently manage parking zones of a first parking lot.SOLUTION: A sharing management device executes a first setting process and a second setting process. In the first setting process, the sharing management device sets one of the parting zones of a second parking lot P2 so as not to be usable by another vehicle being a vehicle different from a use vehicle 50A. In the second setting process, the sharing management device sets parking zones of a first parking lot P1 so as to be usable by the different vehicle from the time the use vehicle 50A leaves for the second parking lot P2 until the use vehicle 50A arrives at the second parking lot P2.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a sharing management device and a sharing system. [Background technology]

[0002] Patent Document 1 describes a car sharing management device that determines whether or not a vehicle can be reserved based on the availability of parking spaces in a vehicle parking lot. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-159689 Summary of the Invention [Problem to be solved by the invention]

[0004] The car sharing management device described in Patent Document 1, when a reservation is made for a vehicle to move from a first parking lot to a second parking lot, will fulfill the reservation if there is an available parking space in the second parking lot. However, Patent Document 1 does not mention how to handle the availability of parking spaces in each parking lot while the vehicle is moving from the first parking lot to the second parking lot. Therefore, there is a need for management technology that allows for more efficient use of parking spaces in each parking lot while the vehicle is moving. [Means for solving the problem]

[0005] In order to solve the above problems, the present invention is a sharing management device that manages the sharing of parking spaces in a parking lot among users, and when a vehicle moving from a first parking lot to a second parking lot is defined as a user vehicle and a vehicle other than the user vehicle is defined as an other vehicle, the sharing management device executes a first setting process that sets the parking space in the second parking lot as unavailable to the other vehicle before the user vehicle departs for the second parking lot, and a second setting process that sets the parking space in the first parking lot as available to the other vehicle from the time the user vehicle departs for the second parking lot until the time the user vehicle arrives at the second parking lot.

[0006] According to the above configuration, the parking space in the first parking lot can be used by another vehicle by the time the vehicle arrives at the second parking lot. This increases the usage time of the parking space in the first parking lot. Therefore, the parking space in the first parking lot can be managed more efficiently. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a schematic diagram of a car sharing system. [Figure 2] FIG. 2 is an explanatory diagram showing the movement of a vehicle in use. [Figure 3] FIG. 3 is a flowchart showing a series of processes of the management program. DETAILED DESCRIPTION OF THE INVENTION

[0008] (One embodiment) A car sharing system to which a sharing system having a sharing management device is applied will be described below with reference to the drawings.

[0009] <Overview of the car sharing system> As shown in Fig. 1, a car sharing system 10 includes a plurality of client terminals 20 and a server 30. The server 30 is connected to the client terminals 20 via an external communication network 40. The external communication network 40 is, for example, a wireless communication network such as a mobile phone network. Therefore, the client terminals 20 and the server 30 can communicate information with each other via the external communication network 40.

[0010] The client terminal 20 is a so-called in-vehicle device that is attached to the vehicle 50. The client terminal 20 has a position information acquisition device 21 and a transmission device 22. The position information acquisition device 21 acquires position information PI indicating the position of the vehicle 50, for example, based on a signal from a Global Navigation Satellite System (GNSS). The position information PI indicates the latitude, longitude, and altitude of the vehicle 50. The transmission device 22 repeatedly transmits the position information PI of the vehicle 50 acquired by the position information acquisition device 21 to the server 30, for example, at one-minute intervals. The vehicle 50 is a target vehicle that can be shared by users in the car sharing system 10.

[0011] The server 30 has a transmission / reception device 31 and a sharing management device 32. The transmission / reception device 31 receives position information PI of the vehicle 50 transmitted from the transmission device 22 of the client terminal 20. In other words, the transmission / reception device 31 functions as a reception device that receives information transmitted from the transmission device 22 of the client terminal 20. In addition, the transmission / reception device 31 outputs the received position information PI of the vehicle 50 to the sharing management device 32.

[0012] The sharing management device 32 is a device that manages the sharing of parking spaces in a parking lot among users. The sharing management device 32 has a CPU 33, which is an execution device, a peripheral circuit 34, a ROM 35, a storage device 36, and a bus 37. The bus 37 connects the CPU 33, the peripheral circuit 34, the ROM 35, and the storage device 36 so that they can communicate with each other. The peripheral circuit 34 includes a circuit that generates a clock signal that defines internal operation, a power supply circuit, a reset circuit, etc. The ROM 35 pre-stores programs that enable the CPU 33 to execute various controls. Specifically, the ROM 35 stores a management program PR. The CPU 33 executes the various programs stored in the ROM 35. The processes defined in the management program PR will be described later.

[0013] The storage device 36 stores reservation information IR for multiple vehicles 50 used in the car sharing system 10. Specifically, the storage device 36 stores, as the reservation information IR, information indicating whether each vehicle 50 is in a reserved state. Furthermore, for a vehicle 50 that is in a reserved state, the storage device 36 stores, as the reservation information IR, information indicating the parking lot from which the vehicle departs and the parking lot from which the vehicle arrives.

[0014] The storage device 36 stores parking lot information IP for multiple parking lots used in the car sharing system 10. A parking lot has one or more parking spaces. The storage device 36 stores, as the parking lot information IP, information indicating whether each parking space in the parking lot is available for use. The storage device 36 also stores, as the parking lot information IP, the number of parking spaces available in the parking lot.

[0015] The storage device 36 stores geofence information IG that indicates the geofence for each parking lot. A geofence is set as a range that includes one parking lot but excludes the other parking lots among multiple parking lots. Note that the geofences are set so that they do not overlap.

[0016] When a reservation request for a vehicle 50 is received from a user, the CPU 33 of the sharing management device 32 executes the management program PR. The reservation request from the user is made by the user operating the operation terminal 60. When the operation terminal 60 is operated, a signal indicating the reservation request is sent from the operation terminal 60 to the server 30 via the external communication network 40. Then, when the server 30 receives the signal indicating the reservation request, the CPU 33 executes the management program PR, assuming that the reservation request has been received. The operation terminal 60 is, for example, a smartphone.

[0017] When reserving a vehicle 50, the signal indicating the reservation request includes information indicating the parking lot from which the vehicle departs and the parking lot to which the vehicle arrives. Hereinafter, as shown in FIG. 2, of the multiple parking lots, the parking lot from which the vehicle departs will be referred to as the first parking lot P1, and the parking lot to which the vehicle arrives will be referred to as the second parking lot P2. Furthermore, of the multiple vehicles 50, the vehicle 50 moving from the first parking lot P1 to the second parking lot P2 will be referred to as the vehicle 50A to be used. Furthermore, of the multiple vehicles 50, a vehicle 50 other than the vehicle 50A to be used will be referred to as a different vehicle.

[0018] In the following description, setting a parking space to be usable means storing the parking space information IP of the parking space in the storage device 36 as a state indicating that the parking space is usable. Setting a parking space to be unusable means storing the parking space information IP of the parking space in the storage device 36 as a state indicating that the parking space is unusable.

[0019] As shown in FIG. 3, when the CPU 33 starts a series of processes of the management program PR, it first performs the process of step S11. In step S11, the CPU 33 determines whether there is an available vehicle 50 in the first parking lot P1. Specifically, the CPU 33 references the reservation information IR in the storage device 36 and determines whether an unreserved vehicle 50 is parked in the first parking lot P1. If an unreserved vehicle 50 is parked in the first parking lot P1, the CPU 33 determines that there is an available vehicle 50A in the first parking lot P1. On the other hand, if there is no unreserved vehicle 50 parked in the first parking lot P1, the CPU 33 determines that there is no available vehicle 50A in the first parking lot P1. If it determines that there is no available vehicle 50A in the first parking lot P1 (S11: NO), the CPU 33 transmits a signal to the user's operation terminal 60 indicating that the reservation is not possible. The CPU 33 then terminates the series of processes. On the other hand, if there is an available vehicle 50A in the first parking lot P1 (S11: YES), the CPU 33 proceeds to step S12.

[0020] In step S12, the CPU 33 refers to the parking lot information IP in the storage device 36 and determines whether there is an available parking space in the second parking lot P2. Specifically, when the number of available parking spaces in the second parking lot P2 is one or more, the CPU 33 determines that a parking space in the second parking lot P2 is available for use by the vehicle 50A. When there is no available parking space in the second parking lot P2 (S12: NO), the CPU 33 sends a signal to the user's operation terminal 60 indicating that a reservation is not possible. Thereafter, the CPU 33 ends the series of processes. On the other hand, when there is an available parking space in the second parking lot P2 (S12: YES), the CPU 33 proceeds to step S13.

[0021] In step S13, the CPU 33 performs a reservation process to reserve the vehicle 50A. In step S13, if the determinations in steps S11 and S12 are affirmative, the vehicle 50A is reserved. That is, the reservation process reserves the vehicle 50A on the condition that an available vehicle 50 exists in the first parking lot P1 and that a parking slot available for the vehicle 50A exists in the second parking lot P2. The CPU 33 also prevents the vehicle 50A from being reserved by anyone other than the user who requested the reservation. That is, the CPU 33 sets the vehicle 50A as a reserved vehicle 50. The CPU 33 then proceeds to step S14. For example, the CPU 33 storing information including the identification information of the reservation currently being processed, the reservation information IR, and the identification information of the vehicle 50A, the user, and the vehicle 50A in the storage device 36 is an example of an operation performed in the reservation process. In addition, reserving a vehicle means reserving the vehicle 50A for the user before the user begins using the vehicle 50A so that no one other than the user can use the vehicle 50A when the user uses the vehicle 50A.

[0022] In step S14, the CPU 33 performs a first setting process. In the first setting process, the CPU 33 sets one of the parking slots in the second parking lot P2 as unavailable for use by a vehicle other than the user vehicle 50A. Specifically, the CPU 33 updates the number of available parking slots in the second parking lot P2 in the parking lot information IP stored in the storage device 36 by decrementing it by one. As a result, the CPU 33 makes one of the parking slots in the second parking lot P2 available for use when the user vehicle 50A arrives at the second parking lot P2. The CPU 33 then proceeds to step S15.

[0023] In step S15, the CPU 33 notifies the user that the reservation for the vehicle 50A has been completed. Specifically, the CPU 33 notifies the user's operation terminal 60 from the transmission / reception device 31. Thereafter, the CPU 33 advances the process to step S16.

[0024] In step S16, the CPU 33 determines whether the vehicle 50A has departed. Specifically, the CPU 33 determines that the vehicle 50A has departed when the position of the vehicle 50A has changed, by referring to the position information PI of the vehicle 50A sent from the client terminal 20. If the vehicle 50A has not departed (S16: NO), the CPU 33 repeats the process of step S16. On the other hand, if the vehicle 50A has departed (S16: YES), the CPU 33 proceeds to step S17.

[0025] In step S17, the CPU 33 determines whether the user vehicle 50A has moved from within the range of the first geofence G1 to outside the range. Specifically, the CPU 33 makes this determination based on the position information PI of the user vehicle 50A sent from the client terminal 20. When the position of the user vehicle 50A is located outside the range of the first geofence G1, the CPU 33 determines that the user vehicle 50A has moved from within the range of the first geofence G1 to outside the range. When the user vehicle 50A has not moved outside the range of the first geofence G1 (S17: NO), the CPU 33 repeats the processing of step S17. On the other hand, when the user vehicle 50A has moved outside the range of the first geofence G1 (S17: YES), the CPU 33 proceeds to the processing of step S18. Note that the first geofence G1 is a geofence that includes the entire area of the first parking lot P1 but does not include the area of the second parking lot P2.

[0026] In step S18, the CPU 33 performs a second setting process. In the second setting process, the CPU 33 sets one of the parking spaces in the first parking lot P1 to be available for use by another vehicle. Specifically, the CPU 33 updates the number of available parking spaces in the first parking lot P1 in the parking lot information IP stored in the storage device 36 by increasing it by one. As a result, the CPU 33 makes one of the parking spaces in the first parking lot P1 available for use by another vehicle. The CPU 33 then proceeds to step S19.

[0027] In step S19, the CPU 33 determines whether the user vehicle 50A has arrived at the second parking lot P2. The CPU 33 determines that the user vehicle 50A has arrived at the second parking lot P2 when the following two conditions are met. The first condition is that the position of the user vehicle 50A is located within the range of the second geofence G2. Specifically, the CPU 33 determines that the first condition is met when the position of the user vehicle 50A is located within the range of the second geofence G2, with reference to the position information PI of the user vehicle 50A sent from the client terminal 20. Note that the second geofence G2 is a geofence that includes the entire area of the second parking lot P2 and does not overlap with the first geofence G1.

[0028] The second condition is that a signal indicating that the use of the vehicle 50A has ended is received from the user's operation terminal 60. Specifically, the CPU 33 determines that the second condition is met when the transceiver 31 receives a signal indicating that the use of the vehicle 50A has ended from the operation terminal 60. When these two conditions are met simultaneously, the CPU 33 determines that the vehicle 50A has arrived at the second parking lot P2. In other words, the CPU 33 determines that the vehicle 50A has arrived at the second parking lot P2 when the vehicle 50A is located within the range of the second geofence G2 and receives a signal indicating that the use of the vehicle 50A has ended.

[0029] If the vehicle 50A has not arrived at the second parking lot P2 (S19: NO), the CPU 33 repeats the process of step S19. On the other hand, if the vehicle 50A has arrived at the second parking lot P2 (S19: YES), the CPU 33 updates the reservation information IR so that the reservation status of the vehicle 50A is not reserved. Thereafter, the CPU 33 ends the series of processes.

[0030] As described above, when the determinations in steps S16 and S17 are affirmative, the CPU 33 performs the second setting process in step S18. Therefore, in the second setting process, the CPU 33 sets one of the parking spaces in the first parking lot P1 to be available for use by another vehicle when the user vehicle 50A moves from within the range of the first geofence G1 to outside the range after the user vehicle 50A departs for the second parking lot P2. Therefore, by the second setting process, the parking lot information IP of one of the parking spaces in the first parking lot P1 is rewritten from a state indicating that it is unavailable for use by another vehicle to a state indicating that it is available for use.

[0031] Furthermore, before step S19, a second setting process of step S18 is performed. After a positive determination is made in step S17, the user vehicle 50A is located outside the range of the first geofence G1 and outside the range of the second geofence G2 until a positive determination is made in step S19. Therefore, in the second setting process, the CPU 33 sets one of the parking slots in the first parking lot P1 as available for use by another vehicle by rewriting the parking lot information IP before the user vehicle 50A arrives at the second parking lot P2.

[0032] (Operation of the embodiment) As shown in FIG. 2, the process of the vehicle 50A moving from the first parking lot P1 to the second parking lot P2 when the vehicle 50A has been reserved will be described. When the vehicle 50A has been reserved, the vehicle 50A is present in one of the parking slots in the first parking lot P1. Therefore, the parking slot in the first parking lot P1 where the vehicle 50A is present is unavailable for use by another vehicle. Furthermore, when the vehicle 50A has been reserved, no other vehicle is present in one of the parking slots in the second parking lot P2. Therefore, the parking lot information IP for one of the parking slots in the second parking lot P2 indicates that the vehicle 50A is available for use.

[0033] Let us assume that after the user vehicle 50A departs from the first parking lot P1, the user vehicle 50A moves from within the range of the first geofence G1 to outside the range. At this time, the CPU 33 of the sharing management device 32 sets the parking lot information IP of the parking space in the first parking lot P1 to be available for use by other vehicles through the second setting process.

[0034] Therefore, when the user vehicle 50A departs from the first parking lot P1 and arrives at the second parking lot P2, it can use the parking slot in the second parking lot P2. On the other hand, when the user vehicle 50A moves out of the range of the first geofence G1, that is, between the time when the user vehicle 50A departs from the first parking lot P1 and the time when the user vehicle 50A arrives at the second parking lot P2, another vehicle can use the parking slot in the first parking lot P1 that was used by the user vehicle 50A.

[0035] (Effects of the embodiment) (1) According to the above embodiment, one of the parking spaces in the first parking lot P1 is managed so that it can be used by another vehicle before the user vehicle 50A arrives at the second parking lot P2. In other words, the sharing management device 32 can shorten the period during which one user vehicle 50A reserves two parking spaces. Therefore, the parking spaces in the first parking lot P1 can be managed more efficiently.

[0036] (2) If a parking slot in the first parking lot P1 can be set as available for another vehicle, the earlier the setting is made, the more effectively the parking slot in the first parking lot P1 can be used. Therefore, by setting a parking slot in the first parking lot P1 as available for another vehicle when the user vehicle 50A departs for the second parking lot P2, the parking slot in the first parking lot P1 can be used by another vehicle sooner. However, in this case, when the user returns to the first parking lot P1 for some reason, such as to retrieve something they left behind, there may be a situation where there is no parking slot available and the user vehicle 50A cannot be parked.

[0037] In the above embodiment, the parking space in the first parking lot P1 is set as available for use by another vehicle on the condition that the user vehicle 50A has moved out of the range of the first geofence G1. In other words, if the user vehicle 50A has traveled a considerable distance and there is a high possibility that the user vehicle 50A will not return to the first parking lot P1, the parking space in the first parking lot P1 is set as available for use by another vehicle. Therefore, as described above, it is unlikely that a situation will occur in which there are no parking spaces available when the user returns to the first parking lot P1.

[0038] (3) According to the above embodiment, the sharing management device 32 manages not only the parking spaces in each parking lot, but also the vehicles 50 used in the car sharing system 10. When the sharing management device 32 receives a reservation request for the vehicle 50A, it performs a reservation process to reserve the vehicle 50A. In the reservation process, the CPU 33 of the sharing management device 32 reserves the vehicle 50A on the condition that the vehicle 50A is present in the first parking lot P1 and that a parking space available for the vehicle 50A is present in the second parking lot P2. Therefore, when the vehicle 50A arrives at the second parking lot P2, the vehicle 50A can use a parking space in the second parking lot P2. This prevents the vehicle 50A from being unable to use a parking space in the second parking lot P2 when the vehicle 50A arrives at the second parking lot P2.

[0039] (4) According to the above embodiment, in the car sharing system 10, the sharing management device 32 determines whether the user vehicle 50A has moved outside the range of the first geofence G1 based on the position information PI of the user vehicle 50A received from the client terminal 20. Therefore, no special device is required to determine the positional relationship between the user vehicle 50A and the first parking lot P1.

[0040] (Other embodiments) The above embodiment can be modified as follows: The above embodiment and the following modifications can be combined with each other within the scope of technical compatibility.

[0041] <Client terminal> The client terminal 20 is not limited to an in-vehicle device. For example, if the operation terminal 60 has a location information acquisition device 21 and a transmission device 22, the client terminal 20 may be the user's operation terminal 60. If the user carries the operation terminal 60, the location of the operation terminal 60 can be considered to be the location of the vehicle 50A to be used. Furthermore, the client terminal 20 does not have to be a single device, but may be a combination of multiple independent devices. For example, the client terminal 20 may be configured with a location information acquisition device 21 mounted on the vehicle 50 and a transmission device 22 included in the operation terminal 60. In this modified example, it is sufficient that the location information acquisition device 21 and the transmission device 22 are able to communicate with each other via short-range wireless communication or the like.

[0042] <Sharing management device> The server 30 may have a vehicle management device that manages the vehicles 50, separate from the sharing management device 32. In this case, the sharing management device 32 may execute the first setting process of step S14 and the second setting process of step S17, while the vehicle management device may execute the processes of the other steps.

[0043] The sharing management device 32 may be configured as a circuit including one or more processors that execute various processes according to a computer program (software). The sharing management device 32 may also be configured as a circuit including one or more dedicated hardware circuits, such as an application-specific integrated circuit (ASIC), that execute at least some of the various processes, or a combination thereof. The processor includes a CPU and memory such as RAM and ROM. The memory stores program code or instructions configured to cause the CPU to execute processes. The memory, i.e., computer-readable medium, includes any available medium that can be accessed by a general-purpose or dedicated computer. The same applies to other devices.

[0044] <Second setting process> The CPU 33 of the sharing management device 32 may execute the second setting process from the time when the user vehicle 50A departs for the second parking lot P2 until the time when the user vehicle 50A arrives at the second parking lot P2. For example, after determining in step S16 that the user vehicle 50A has departed, the CPU 33 may execute the second setting process by skipping step S17 and proceeding to step S18.

[0045] Alternatively, for example, instead of the processing of step S17, the CPU 33 may determine whether or not a certain amount of time has elapsed since the departure of the user vehicle 50A. In this case, the CPU 33 may execute the second setting process when the certain amount of time has elapsed. Alternatively, for example, instead of the processing of step S17, the CPU 33 may determine whether or not the user vehicle 50A has traveled a certain distance or more since the departure of the user vehicle 50A. In this case, the CPU 33 may execute the second setting process when the user vehicle 50A has traveled a certain distance or more. In these modified examples, the storage device 36 does not need to store the geofence information IG.

[0046] The CPU 33 may determine the timing of performing the second setting process without relying on the position information PI of the user vehicle 50A. For example, if a short-range wireless communication device is installed in an area including the first parking lot P1 and the short-range wireless communication device and the client terminal 20 are able to communicate with each other, the following may be done. First, when the client terminal 20 is no longer able to communicate with the short-range wireless communication device, the client terminal 20 transmits a signal to the server 30 indicating that the client terminal 20 is no longer able to communicate with the short-range wireless communication device. When the transmission / reception device 31 of the server 30 receives the signal, the sharing management device 32 performs the second setting process.

[0047] Also, for example, if the first parking lot P1 is equipped with a communication device capable of communicating with the server 30 via the external communication network 40, and a detection device that detects the entry and exit of the vehicle 50 into the first parking lot P1, the following procedure may be performed. First, the detection device detects that the user vehicle 50A has left the first parking lot P1. When the user vehicle 50A leaves the first parking lot P1, the communication device transmits a signal to the server 30 indicating that the user vehicle 50A is departing. When the server 30 receives this signal, the sharing management device 32 determines that the user vehicle 50A has departed for the second parking lot P2 and also from the first parking lot P1. Thereafter, the sharing management device 32 performs a second setting process.

[0048] The CPU 33 may determine whether the vehicle 50A has departed without relying on the position information PI of the vehicle 50A. For example, when the user operates the operation terminal 60 to start using the vehicle 50A, the CPU 33 may determine that the vehicle 50A has departed. Specifically, the CPU 33 may determine that the vehicle 50A has departed by acquiring a signal based on the operation from the operation terminal 60. Furthermore, the CPU 33 may determine that the vehicle 50A has departed when the power switch of the vehicle 50A is operated to turn on the power of the vehicle 50A. Specifically, the CPU 33 may determine that the vehicle 50A has departed by acquiring a signal indicating that the power of the vehicle 50A has turned on from the client terminal 20.

[0049] It is also assumed that the vehicle 50A may remain parked in the parking space in the first parking lot P1 for a while after an operation to start using the vehicle 50A is performed or after the power switch of the vehicle 50A is operated. For this reason, it may be determined that the vehicle 50A has departed when a predetermined time has elapsed since the operation to start using the vehicle 50A was performed or the power switch of the vehicle 50A was operated.

[0050] If the same parking lot as the first parking lot P1 is set as the second parking lot P2, the first setting process and the second setting process do not need to be performed. In other words, it is sufficient that the parking slot in the parking lot set as both the first parking lot P1 and the second parking lot P2 is always unavailable for use by other vehicles while it is being used by the vehicle 50A.

[0051] <Other> The vehicle 50A is not limited to a vehicle that is subject to sharing by a user. For example, the vehicle may be owned by a user, as long as a parking space in a parking lot is shared by multiple users. In this case, the user can operate the operation terminal 60 to check the availability of parking spaces in the second parking lot P2 before departing the vehicle 50A and request the server 30 to perform the second setting process.

[0052] The vehicle 50 is not limited to an automobile, but may be a bicycle. Also, the vehicle 50 is not limited to a four-wheeled vehicle, but may be, for example, a three-wheeled vehicle or a two-wheeled vehicle. There may be cases where a single site contains parking spaces for sharing and parking spaces that are not for sharing. In this case, the range of the geofence may be set to include all of the parking spaces for sharing that are managed by the sharing management device 32. In other words, the geofence may be set so that parking spaces that are not for sharing are not included. [Explanation of symbols]

[0053] 10...Sharing system 20...Client terminal 21...Location information acquisition device 22...Transmitter 30...Server 31...Transmitter / receiver 32...Sharing management device 33...CPU 34...Peripheral circuit 35...ROM 36...Storage device 37...Bus 40...External communication line network 50...Vehicle 50A...Vehicle in use 60...Operation terminal G1...First geofence G2...Second geofence IG...Geofence information IP...Parking lot information IR...Reservation information P1...First parking lot P2...Second parking lot PI...Location information

Claims

1. A sharing management device that manages parking spaces in a parking lot so that users can share them, A vehicle moving from the first parking lot to the second parking lot is a vehicle in use, When a vehicle other than the vehicle used is designated as a separate vehicle, a first setting process for setting a parking space in the second parking lot as unavailable for use by the other vehicle before the vehicle departs for the second parking lot; A process of determining whether the vehicle has departed for the second parking lot; After it is determined that the user vehicle has departed for the second parking lot, a process is performed to determine whether the user vehicle has moved from within a geofence that includes the first parking lot but does not include the second parking lot to outside the range; a second setting process for setting a parking slot in the first parking lot as available for use by the other vehicle from the time the vehicle departs for the second parking lot until the time the vehicle arrives at the second parking lot; After it is determined that the user vehicle has departed for the second parking lot, the second setting process is not executed until it is determined that the user vehicle has moved from within the range of the geofence to outside the range, and when it is determined that the user vehicle has moved from within the range of the geofence to outside the range, the second setting process is executed. Sharing management device.

2. The vehicle to be used is a target vehicle that is subject to sharing by the user, When a reservation request for the vehicle to be used to move from the first parking lot to the second parking lot is received, a reservation process is executed to reserve the vehicle to be used; The reservation process is a process of reserving the vehicle to be used on the condition that the vehicle to be used is present in the first parking lot and that a parking space available for the vehicle to be used is present in the second parking lot. The sharing management device according to claim 1 .

3. A system including a server having the sharing management device according to claim 1 and a client terminal capable of communicating with the server, the client terminal has a transmitting device that transmits the location information of the vehicle to the server; The server further includes a receiving device that receives the location information of the vehicle to be used transmitted from the transmitting device, The sharing management device determines whether the vehicle in use has moved from within the geofence to outside the geofence, based on the location information of the vehicle in use. Sharing system.

Images