Server device

Abstract

A server device according to the present invention comprises one or more processors and a storage medium in which a program to be executed by the one or more processors is stored, wherein the program includes one or more commands. The commands cause the one or more processors to perform: a process for giving, to a vehicle that can autonomously travel and that belongs to a provider who provides, to a user, a charger installed in a parking lot for provider's own use, an instruction to move to a prescribed waiting position in accordance with alighting of a passenger from the vehicle of the provider, when the vehicle of the provider returns to the parking lot while the parking lot is occupied by a vehicle of the user; a process for giving, to the vehicle of the provider, an instruction to move from the waiting position to the parking lot in response to detection of exit of the vehicle of the user from the parking lot; and a process for transmitting a return notification to the provider in response to return of the vehicle of the provider to the parking lot.

Description

Server device

[0001] The present invention relates to a server device and to a technology for providing charging spots to users of electric vehicles and the like.

[0002] Japanese Patent Application Laid-Open No. 2003-144992 (Patent Document 1) below describes a method for charging electric vehicles, in which charging facilities at a home, such as a private home, are made available to other users.

[0003] Japanese Patent Application Laid-Open No. 2019-185308

[0004] While electric vehicles have become increasingly popular in recent years, situations can arise where there is no place to charge (charging spot) when the remaining charge runs low while out and about. For example, it is expected that there will be fewer charging stations in mountainous areas far from urban areas. On the other hand, for households that have charging spots (chargers) installed at home, the charger will go unused while the vehicle is out and about, resulting in a lower charger utilization rate. Furthermore, if someone else uses a home charger, the parking space will be occupied, and if the lender returns before the charging is complete, the lender may not be able to park. For these reasons, coordinating usage when using a private home as a charging spot is difficult. This is particularly difficult when the charger provider returns home while someone else is charging.

[0005] Therefore, the present invention provides a technique for adjusting when a provider of a rental charger for a private home returns home.

[0006] A server device according to one embodiment of the present invention comprises one or more processors and a storage medium storing a program executed by the one or more processors, the program including one or more instructions that cause the one or more processors to execute the following processes: when an autonomously driven provider vehicle of a provider that has provided a user with a charger installed in a parking lot for personal use returns to the parking lot and the parking lot is occupied by the user vehicle, instructing the provider vehicle to move to a predetermined waiting location in response to an occupant disembarking from the provider vehicle; instructing the provider vehicle to move from the waiting location to the parking lot in response to detecting the user vehicle's exit from the parking lot; and instructing the provider vehicle to move from the waiting location to the parking lot in response to the provider vehicle's return to the parking lot.

[0007] According to the present invention, when a private home or the like is used as a charging spot, if the provider returns earlier than the scheduled date and time, or if the provider returns on the scheduled date and time but the user is charging, etc., it is possible to prevent the provider from experiencing any inconvenience.

[0008] 1 is an explanatory diagram of a system configuration of an embodiment of the present invention; FIG. 2 is a block diagram of an information processing device that is a server device or the like of an embodiment; FIG. 3 is a block diagram of a vehicle configuration of an embodiment; FIG. 4 is an explanatory diagram of a procedure for a charger rental service of an embodiment; FIG. 5 is an explanatory diagram of a functional configuration of a server device of an embodiment; FIG. 6 is an explanatory diagram of a functional configuration of a user terminal of an embodiment; FIG. 7 is an explanatory diagram of a functional configuration of a provider terminal of an embodiment; FIG. 8 is a flowchart of a first processing example of an embodiment; FIG. 9 is a flowchart of a first processing example of an embodiment; FIG. 10 is a flowchart of a second processing example of an embodiment; FIG. 11 is a flowchart of a third processing example of an embodiment; and FIG. 12 is a flowchart of a fourth processing example of an embodiment.

[0009] <System Configuration> Figure 1 shows the system configuration for a charger rental service in one embodiment. This system allows coordination between charger providers and users who wish to rent a charger. In this system, a system management server device 1 (hereinafter referred to as "server device 1"), a user terminal 21, and a provider terminal 51 are configured to be able to communicate via a network 100.

[0010] A user is a person who has registered as a user for the charger rental service provided by the server device 1. By registering as a user, a person who wants to use the charger rental service can use other people's chargers 53, for example, for a fee. The vehicle used by the user is shown as user vehicle 2R.

[0011] A provider is a person who is willing to lend the charger 53 installed in the parking lot 52 that he or she uses to others and has registered as a provider with the charger rental service provided by the server device 1. By becoming a registered provider, the person can receive compensation in return for allowing others to use the charger 53. The vehicle used by the provider is shown as a provider vehicle 2S.

[0012] The user terminal 21 is an information processing device used by a user, and is a terminal device that can communicate with at least the server device 1 via the network 100. For example, the user terminal 21 may be an information processing device in the vehicle 2R, or may be an information processing device such as a smartphone, personal computer, or tablet device carried by the user.

[0013] Users using these user terminals 21 can enjoy the services provided by this system by, for example, browsing websites provided by the server device 1 or launching application programs using the user terminals 21 .

[0014] The provider terminal 51 is an information processing device used by the provider, and is a terminal device capable of communicating with at least the server device 1 via the network 100. For example, it may be a personal computer in the provider's residence 3 or the like, or an information processing device built into the charger 53. Furthermore, a smartphone or tablet device carried by the provider may serve as the provider terminal 51. Furthermore, an information processing device in the provider vehicle 2S used by the provider may serve as the provider terminal 51. An information processing device built into the residence 3 or the charger 53 and a smartphone or tablet device carried by the provider may be synchronized and used together as the provider terminal 51. Furthermore, a smartphone or tablet device carried by the provider may be used as a user interface device for the provider of the provider terminal 51 built into the residence 3 or the charger 53.

[0015] The provider terminal 51 performs processes such as transmitting provided information to the server device 1 according to the provider's convenience and transmitting information regarding the rental operation of the charger 53 to the server device 1. Therefore, the provider terminal 51 may be any information processing device capable of performing these processes, and the specific form is not important. Also, for example, a smartphone used by the provider and an information processing device in the charger 53 may function as the provider terminal 51 in cooperation with each other.

[0016] The server device 1 is a server device of a company or the like that operates a charger rental service, and is composed of one or more information processing devices. The server device 1 is also accessible to a storage device 5. The storage device 5 contains a provider registration database 6 for registering providers and a user registration database 7 for registering users.

[0017] The server device 1 communicates with the user terminal 21 and the provider terminal 51, and provides a matching service by coordinating between the user and provider to ensure charging takes place at the location and date and time desired by the user. This allows users to charge their vehicle 2R even in areas where there are not many charging stations. Providers are also rewarded for lending chargers, which provides a simple business opportunity for providers.

[0018] A charger 53 is installed in the parking lot 52 at the provider's residence 3. Normally, the provider vehicle 2S is parked in the parking lot 52 and is charged using the charger 53. In the charger rental service of this embodiment, when the provider goes out in the provider vehicle 2S and the parking lot 52 and charger 53 are not in use, the user can charge the user vehicle 2R.

[0019] The charger 53 is provided with a panel 55 as a display and operation panel, which allows the user to, for example, operate the charger or provide usage guidance. The user charges the battery by connecting the gun 54 to a connector 67 (see FIG. 3 ), which is the charging port of the user's vehicle 2R. The charger 53 is provided with a measurement circuit therein that measures the amount of charge, and the measurement information of the amount of charge obtained by this measurement circuit can be acquired by the provider terminal 51.

[0020] This example also shows an example in which a camera 59 is installed in the parking lot 52. The camera 59 can capture, for example, the license plate and body of the user's vehicle 2R, as well as the charging status. The provider terminal 51 can obtain information about the user's vehicle 2R, such as the vehicle license plate and model, from the video captured by the camera 59. Alternatively, the provider terminal 51 may transmit the video data itself to the server device 1, so that the vehicle license plate, model, and the like can be detected on the server device 1 side. The provider terminal 51 and the server device 1 can also confirm the user's vehicle 2R entering and exiting the parking lot 52 from the video captured by the camera 59.

[0021] In the figure, the charger 53 is shown as being installed in the parking lot 52 of the residence 3, but the residence 3 can be any type, such as a detached house or an apartment building. The parking lot 52 may also be located away from the residence 3 and be a parking lot where the provider normally parks. In this embodiment, the charger 53 that is the target of the charger rental service is a parking lot 52 used by the provider, such as a parking lot on the premises of the residence 3 that serves as the provider's home, or a parking lot that is separate from the provider's home but owned or rented by the provider. The charger 53 is also a charger owned or rented by the provider and is normally used by the provider or their family, etc. However, the above is an example in which the provider is an individual. It is also assumed that the provider in this embodiment is a company, organization, etc., and the parking lot or charger of the company, etc. may be the parking lot 52 or charger 55 in FIG. 1 .

[0022] Furthermore, when a charger rental service is implemented, a waiting location 58 for the provider vehicle 2S is set. For example, this is a location where the provider vehicle 2S can be temporarily parked if the user vehicle 2R is still occupying the parking lot 52 when the provider returns home (when the provider vehicle 2S returns to the parking lot 52). This waiting location 58 can be determined by the provider, for example, within the premises of or in the vicinity of the residence 3, and location information and the like can be registered in the server device 1.

[0023] <Configuration of Information Processing Apparatus> FIG. 2 shows an example of the configuration of an information processing apparatus 30 that can be used as the server apparatus 1, the user terminal 21, or the provider terminal 51.

[0024] The information processing device 30 is configured to include a CPU (Central Processing Unit) 31, a ROM (Read Only Memory) 32, a RAM (Random Access Memory) 33, a bus 34, an input / output interface 35, an input unit 36, an output unit 37, a memory unit 38, a communication unit 39, a media drive 40, etc.

[0025] The CPU 31 executes various processes in accordance with programs stored in the ROM 32 or programs loaded from the storage unit 38 into the RAM 33. The RAM 33 also stores data and the like necessary for the CPU 31 to execute various processes.

[0026] The CPU 31, ROM 32, and RAM 33 are interconnected via a bus 34. An input / output interface 35 is also connected to the bus 34.

[0027] The input / output interface 35 is connected to an input unit 36, an output unit 37, a storage unit 38, a communication unit 39, and a media drive 40. The input unit 36 ​​is composed of a keyboard, a mouse, a touch panel, a microphone, etc. The output unit 37 is composed of a display such as an LCD (Liquid Crystal Display) or an organic EL (Electro Luminescence) panel, a speaker, etc.

[0028] The storage unit 38 is configured by a hard disk drive (HDD), a flash memory device, etc. When the information processing device 30 having this configuration is applied as the server device 1, the storage unit 38 may configure a database that stores registration information, etc.

[0029] The communication unit 39 performs communication processing and inter-device communication via a communication network. A removable medium 41, such as a semiconductor memory card, is inserted into the media drive 40, and information is written to and read from the removable medium 41.

[0030] In the information processing device 30, data and programs are uploaded and downloaded through communication by the communication unit 39. Data and programs can also be transferred via removable media 41. The CPU 31 performs processing operations based on various programs, thereby executing the information processing and communication required for the server device 1, the user terminal 21, or the provider terminal 51.

[0031] <Vehicle Configuration> Incidentally, a system within a vehicle may be used as the user terminal 21 or the provider terminal 51. Fig. 3 shows an example of a configuration for functioning as the user terminal 21 or the provider terminal 51, along with the charging-related configuration of the vehicle 2. Note that the vehicle 2 collectively refers to the provider vehicle 2S and the user vehicle 2R.

[0032] The vehicle 2 includes a control device 61 , an on-board battery 62 , a PCU (Power Control Unit) 63 , a motor 64 , an operation unit 65 , a display unit 66 , a connector unit 67 , and a communication unit 68 .

[0033] 3 shows only a portion of the configuration of the vehicle 2, and the vehicle 2 is also equipped with a map locator, various sensors for driving, communication devices, etc., which are not shown.

[0034] The control device 61 is configured with a CPU, memory, etc., and performs overall control of the vehicle 2. The control device 61 may be provided as a single unit, or may be configured with multiple ECUs (Electronic Control Units). The multiple ECUs may include, for example, a battery control ECU that controls charging of the on-board battery 62, a display control ECU that controls display of display devices (including meters, etc.) provided in the vehicle 2, an airbag control ECU, an air conditioning control ECU, and so on.

[0035] In this embodiment, the vehicle 2 (at least the provider vehicle 2S) is an automobile that travels autonomously. Therefore, the vehicle 2 is also equipped with an information processing device necessary for autonomous driving. For example, the control device 61 may also include an autonomous driving ECU that determines a driving route and performs control according to the external environment, a driving control ECU that controls driving and stopping by a motor according to instructions from the autonomous driving ECU, and a steering control ECU that controls steering according to instructions from the autonomous driving ECU. Although not shown, the vehicle 2 is also equipped with devices that sense the surroundings, such as cameras and sensors, and devices that detect map information, road information, current location information, etc., for autonomous driving control.

[0036] The autonomous driving is performed, for example, in response to a destination specification operation by the occupant, but in this embodiment, it is also performed in response to a destination specification command from the server device 1. For example, the provider vehicle 2S autonomously drives to a destination, for example, the waiting area 58 or the home parking lot 52, in response to receiving a movement instruction from the server device 1 via the communication unit 68. Alternatively, if the provider's smartphone or the like serves as the provider terminal 51, the movement instruction from the server device 1 may be received by the communication unit 68 via the provider terminal 51. In this case, the provider vehicle 2S also autonomously drives, for example, to the waiting area 58 or the home parking lot 52 in response to the movement instruction. Furthermore, autonomous driving also includes autonomous driving for parking, for example, so-called "parallel parking" or "perpendicular parking."

[0037] The control device 61 realizes various functions by executing various programs stored in a memory etc. Therefore, the control device 61 can have a configuration equivalent to that shown in FIG.

[0038] The on-board battery 62 is a high-voltage battery used to drive the vehicle 2. The on-board battery 62 supplies power used to drive the wheels, power used to operate the air conditioning equipment, and power used to operate other equipment of the vehicle 2. Fig. 3 shows the power supply from the on-board battery 62 used to drive the wheels and power supply to the display unit 66, and does not show the power supply used to operate the other units.

[0039] The vehicle battery 62 is charged by the current supplied from the PCU 63. The vehicle battery 62 supplies the PCU 63 with a power supply voltage for driving the motor 64.

[0040] The PCU 63 is configured to include an inverter, a DC / DC converter, and the like for driving the motor 64. The PCU 63 generates an AC current for driving the motor 64 based on the supplied power supply voltage, and supplies the AC current to the motor 64. The PCU 63 controls the torque of the motor 64 by controlling the AC current. The PCU 63 may also be provided with a regenerative braking function to optimize energy efficiency by utilizing regenerative energy.

[0041] The motor 64 is configured as a motor generator having a power generating function, and drives the wheels based on the supplied AC current.

[0042] The operation unit 65 includes, for example, various types of buttons, levers, and other operators arranged in front of the driver's seat of the vehicle 2. The operation unit 65 may also include an MFD (Multi Function Display) with a touch panel function, a display unit of a navigation device, or the like.

[0043] The display unit 66 comprehensively represents, for example, an MFD installed in front of the driver and other display devices for presenting information to the driver. The display unit 66 displays information based on detection signals detected by various sensors equipped in the vehicle 2. The display unit 66 appropriately displays various information such as the total mileage of the vehicle, outside temperature, and instantaneous fuel consumption. The display unit 66 can also display map information, extracted route information, and the like. The display unit 66 can also be configured to display a screen for the charger rental service of this embodiment.

[0044] The connector unit 67 has a structure into which a charging plug (gun 54) provided in charging equipment such as the charger 53 can be inserted. The connector unit 67 outputs AC voltage supplied via the inserted charging plug to the PCU 63. The PCU 63 is provided with an AC / DC converter and supplies the converted DC voltage to the on-board battery 62, thereby charging the on-board battery 62.

[0045] The communication unit 68 is configured as a wireless communication device, and is configured to communicate with the server device 1 via the network 100, for example.

[0046] <Outline of Charger Rental Service> The following describes the general flow of the charger rental service provided by the server device 1. The service, including the actions of the user and provider, is implemented in the steps (ST1) to (ST11) shown in FIG.

[0047] (ST1) A user who wishes to become a provider registers a rentable charger 53 in the server device 1 using the provider terminal 51. Specifically, information such as the provider's personal information, information for settlement, location information of the parking lot 52 and waiting area 58, model and specifications of the charger 53, etc. is registered. (ST2) A user who wishes to become a user registers user information (vehicle information, personal information, etc.) in the server device 1 using the user terminal 21.

[0048] (ST3) At any time, the provider transmits provision information, including information on the date and time when the charger 53 is available for rental, to the server device 1 using the provider terminal 51. The provision information is information that tells the server device 1 that the provider is available to provide the parking lot 52 to others between a certain date and time.

[0049] (ST4) At any time, the user sends a request to use a charger 53 to the server device 1 using the user terminal 21. The request includes information such as the desired area and date and time of use. In response to the user's request, the server device 1 selects a provider whose provided information matches the area and date and time, from among the providers whose provided information has been received, and provides the user with a list of chargers 53 available for rental. The user selects the charger 53 they want to use and performs a confirmation operation to reserve use on the server device 1. The server device 1 sets the reservation in response to the confirmation operation.

[0050] (ST5) The user's vehicle 2R moves to the parking lot 52 where the charger 53 is installed on the reserved date and time. (ST6) When using the charger 53, the user is authenticated by the user terminal 21, the provider terminal 51, or both. The authentication result is also shared with the server device 1. (ST7) Charging is performed. At this time, the provider terminal 51 also measures the amount of charge. (ST8) After charging is completed, the fee is settled between the user terminal 21 and the server device 1. (ST9) The user sends evaluation information of the provider using the user terminal 21 (or a device such as a smartphone that functions as a user interface device for the user terminal 21). (ST10) The provider sends the user's evaluation to the server device 1 using the provider terminal 51. (ST11) The server device 1 grants a reward to the provider.

[0051] The order of (ST8), (ST9), (ST10), and (ST11) may be different from that described above. Also, (ST1), (ST2), (ST3), and (ST4) are sequentially performed between an unspecified number of users and the server device 1.

[0052] The functional configuration of the server device 1 for executing the charger rental service described above will be described. For example, the server device 1 having the configuration of the information processing device 30 shown in FIG. 2 realizes various functions by executing programs by the CPU 31. FIG. 5 shows an example of the functions of the CPU 31 related to the charger rental service of this embodiment.

[0053] The registration processing unit 1a is a function that performs processing related to the registration of users and providers. The server device 1 provides a charger rental service to users who have registered as users. The server device 1 also provides users with information on chargers 53 of users who have registered as providers and who meet the conditions. In other words, the registration processing unit 1a is a function that performs processing related to the above-mentioned (ST1) and (ST2).

[0054] The reservation setting processing unit 1b is a function that performs reservation setting processing for charger rental between the user and the provider. For this purpose, the reservation setting processing unit 1b processes information provided by the provider. The provided information includes date and time information at which the provider can provide the charger 53 and parking lot 52 to others. For example, the date and time information is information including the start date and time at which rental is available and the end date and time at which rental is available. The reservation setting processing unit 1b also accepts reservation requests from users and performs processing to introduce providers that meet the conditions. In other words, the reservation setting processing unit 1b is a function that performs processing related to the above-mentioned (ST3) and (ST4).

[0055] The charging and settlement management unit 1c has a function of managing the use of the charger 53 by the user, settling the charges from the user, and providing rewards to the provider. The charging and settlement management unit 1c also performs adjustment processing when a user and a provider overlap in the parking lot 52. Details of the adjustment processing will be described later. The charging and settlement management unit 1c has a function of performing the processing related to (ST6) to (ST11) above.

[0056] Next, the functional configuration of the user terminal 21 will be described. For example, the user terminal 21 having the configuration of the information processing device 30 in Fig. 2 or the user terminal 21 realized as the control device 61 in Fig. 3 realizes various functions by executing programs by the CPU 31. Fig. 6 shows an example of functions provided to the CPU 31 of the user terminal 21 in relation to the charger rental service of this embodiment.

[0057] The registration processing unit 21a has a function of performing processes such as a user interface for the user to register as a user and transmitting registration information to the server device 1. That is, the registration processing unit 21a has a function of performing processes related to the above-mentioned (ST2).

[0058] The reservation request processing unit 21b is a function that provides a user interface for users to make use requests and communicates with the server device 1. That is, the reservation request processing unit 21b is a function that performs the processing related to (ST4) above.

[0059] The charging execution processing unit 21c has a function of performing processes required when a user uses the charger 53 to charge, such as authentication processing and communication with the server device 1. That is, the charging execution processing unit 21c has a function of performing the processes related to (ST6), (ST8), and (ST9) described above.

[0060] Next, the functional configuration of the provider terminal 51 will be described. For example, the provider terminal 51 having the configuration of the information processing device 30 in Fig. 2 or the provider terminal 51 realized as the control device 61 in Fig. 3 realizes various functions by executing programs by the CPU 31. Fig. 7 shows an example of functions provided to the CPU 31 of the provider terminal 51 in relation to the charger rental service of this embodiment.

[0061] The registration processing unit 51a has a function of performing processes such as an interface for a provider to register as a provider and transmitting registration information to the server device 1. That is, the registration processing unit 51a has a function of performing processes related to the above-mentioned (ST1).

[0062] The provided information processing unit 51b has a function of performing a user interface and communication for transmitting provided information indicating the date and time when the provider is available for rental to the server device 1. That is, the provided information processing unit 51b has a function of performing the process related to (ST3) above.

[0063] The charging management unit 51c has a function of performing processes required for a user to charge using the charger 53, such as authentication processing, measurement of the amount of charge and the amount of power, processing related to settlement, and associated communication with the server device 1. In other words, the charging management unit 51c has a function of performing the processes related to (ST6), (ST7), (ST10), and (ST11) described above.

[0064] The following describes examples of processing executed by the server device 1. The first to fourth processing examples described below are adjustment processing performed when the user vehicle 2R occupies the parking lot 52 when the provider vehicle 2S attempts to return to the parking lot 52.

[0065] <First Processing Example> A first processing example by the server device 1 will be described with reference to Figures 8 and 9. In each flowchart, "C1", "C2", and "C3" indicate the connection relationships due to the separate drawings.

[0066] 8, the server device 1 determines whether the provider vehicle 2S will return to the parking lot 52. In other words, this is the case when the provider is returning home. When the return determination is made in step S101, the processing from step S102 onward is started.

[0067] The server device 1 may determine whether the provider vehicle 2S has returned automatically or in response to the provider's operation. For this automatic determination, the server device 1 may set checkpoints in advance, for example, near the parking lot 52. When registering in the above-mentioned (ST1), the provider may input places near the parking lot that the provider always passes through on the way home as checkpoints and have the checkpoints registered in the server device 1. Alternatively, the server device 1 may automatically set places on nearby roads as checkpoints based on the location information of the parking lot 52. The server device 1 then continuously receives location information of the provider vehicle 2S during the rental period. This allows the server device 1 to detect that the provider vehicle 2S has reached a checkpoint, i.e., that it is returning. An example of a determination in response to the provider's operation is when the provider performs an operation on the provider terminal 51 to indicate their intention to return when they arrive near the parking lot 52. The provider terminal 51 transmits this operation information to the server device 1, allowing the server device 1 to determine the return.

[0068] In step S102, the server device 1 determines whether the charger 53 is currently being rented. Even if the user is still within the rental time, charging may have already finished and the user's vehicle 2R may have left the parking lot 52. In this case, adjustment processing is not required, and the processing in Figures 8 and 9 ends.

[0069] During rental, that is, when the provider vehicle 2S returns, if the user vehicle 2R is still in the parking lot 52, the server device 1 determines in step S103 whether the provider vehicle 2S is in the waiting area 58 and the occupants have disembarked. For example, the server device 1 performs the disembarkation determination by receiving information on the disembarkation determination based on information from a seat sensor of the provider vehicle 2S, video from a camera inside the vehicle, or the like.

[0070] If the occupant, such as the provider, has disembarked at the waiting location 58, the server device 1 will not issue any particular instruction and will cause the provider vehicle 2S to wait at the waiting location 58. If the occupant has disembarked at a location other than the waiting location 58, the server device 1 will instruct the provider vehicle 2S in step S104 to automatically travel to the waiting location 58. As a result, the provider vehicle 2S will wait at the waiting location 58. In either case, the occupant can disembark and return home to the residence 3.

[0071] In step S110, the server device 1 determines whether the return is earlier than the scheduled date and time (rental end date and time). If the scheduled date and time has passed, the user's vehicle 2R should have already left the parking lot 52. In this case, in step S111, the server device 1 notifies the user terminal 21 of the provider's return. The user terminal 21 displays this notification, prompting the user to take appropriate action. For example, the user may perform an acknowledgement operation, terminate charging, and leave the user's vehicle 2R from the parking lot 52.

[0072] If consent information is received from the user vehicle 2R, the server device 1 proceeds from step S112 to step S135 and instructs the provider terminal 51 to stop the power supply within a predetermined time.

[0073] On the other hand, there may be cases where the user wishes to continue charging. In this case, the user can transmit a request to continue use from the user terminal 21 to the server device 1. When a request to continue use is received, the server device 1 checks the usage conditions in step S113. That is, the conditions are those that determine which vehicle will be given priority when the user's vehicle 2R and the provider's vehicle 2S collide in the parking lot 52. In addition to determining basic priority conditions based on pre-existing regulations, the provider may also set user priority, for example, when confirming a reservation. Furthermore, whether the current date and time is before or after the rental end date and time may be included in the determination conditions. The server device 1 determines which vehicle has priority in the current case based on the regulations, setting information for each reservation, etc.

[0074] If it is determined that the provider has priority in the current case, the server device 1 determines that the request for continued use cannot be accepted, and proceeds to step S135. In this case, charging is terminated, and the user's vehicle 2R is allowed to exit.

[0075] If it is determined that the user has priority in the current case, the server device 1 accepts the user's request to continue using the vehicle and allows the user to continue charging. However, since the user will continue the rental service after the scheduled departure date and time, the server device 1 increases the usage fee to be charged to the user under predetermined conditions in step S114.

[0076] Then, the server device 1 waits for the charging to be completed in step S115, and when the charging is completed, instructs the provider terminal 51 to stop the power supply in step S116.

[0077] Up to this point, we have considered the case where the provider vehicle 2S returns after the scheduled date and time, but the provider vehicle 2S may also return earlier than the scheduled date and time. In this case, the server device 1 proceeds from step S110 to step S120, sends a notification to the provider terminal 51 requesting a response on how to respond, and confirms the response information. For example, the user can choose to wait until charging is complete or to request the user to exit the parking lot 52.

[0078] Since the provider knows that the return will be earlier than planned, it is conceivable that the provider will wait until the scheduled date and time. In this case, the provider operates the provider terminal 51 to send a response to the server device 1 indicating that the provider will wait. In this case, the server device 1 proceeds from step S120 to step S121, and notifies the user terminal 21 that the provider has returned but will wait. Then, in step S115, the server device 1 waits for charging to be completed, and when charging is completed, in step S116, it instructs the provider terminal 51 to stop supplying power.

[0079] On the other hand, in step S120, the provider may, for some reason, want to have the user vehicle 2R exit earlier than planned. In this case, the provider operates the provider terminal 51 to send a response to the server device 1 requesting the user to exit. In this case, the server device 1 notifies the user terminal 21 in step S130 that the provider has requested the user to exit. In response to this notification, the user can either approve the request to exit or not approve it and send a response indicating that the user wishes to continue using the vehicle.

[0080] If the server device 1 receives information from the user terminal 21 indicating consent to the exit, the server device 1 proceeds from step S131 to step S134, where it performs a process to reduce the remuneration to the provider under predetermined conditions. This is to ensure that charging of the user's vehicle 2R is completed before the rental end date and time. In this case, the server device 1 may also simultaneously reduce the user's usage fee. Then, in step S135, the server device 1 instructs the provider terminal 51 to stop the power supply within a predetermined time. For example, the predetermined time may be set to about one minute, so that charging is completed immediately and the user is allowed to exit.

[0081] If in step S131 the server device 1 receives a response from the user terminal 21 indicating a desire to continue use until the scheduled date and time, the server device 1 checks the terms of use in step S132. That is, as in step S113 above, the server device 1 determines whether to prioritize the user or the provider in the current case. If it determines that provider priority is given, the server device 1 proceeds to step S134. In this case as well, even though provider priority was given, the rental could not be carried out as reserved, so processing is performed to reduce the provider's remuneration under specified conditions. Then, in step S135, the server device 1 instructs the provider terminal 51 to stop the power supply within a specified time.

[0082] If it is determined in step S132 that the user is given priority, the server device 1 proceeds to step S115 to wait for the charging to be completed, and when the charging is completed, in step S116 instructs the provider terminal 51 to stop the power supply.

[0083] In each of the above cases, the process proceeds to steps S115 and S116 if the provider vehicle 2S is to wait at the waiting location 58. However, the occupants, such as the provider, have already disembarked and returned to the residence 3. In this case, the server device 1 proceeds to step S161 in FIG. 9 as indicated by "C3." In step S161, the server device 1 confirms that the user vehicle 2R is leaving the parking lot 52. For example, the provider terminal 51 confirms the exit of the user vehicle 2R based on the image from the camera 59, and transmits information about the exit to the server device 1. This allows the server device 1 to confirm the exit of the user vehicle 2R. Alternatively, the provider terminal 51 may transmit the image from the camera 59 to the server device 1, and the server device 1 may determine the exit from the image.

[0084] After confirming the exit of the user vehicle 2R, the server device 1 checks in step S162 whether the automatic movement of the provider vehicle 2S from the waiting location 58 to the parking lot 52 is permitted. In particular, if the provider wants to return the vehicle to the parking lot 52 by himself, the server device 1 can set the automatic movement not to be permitted.

[0085] If automatic movement is permitted, the server device 1 proceeds to step S163 and transmits to the provider vehicle 2S an instruction to move to the parking lot 52. In response to this, the provider vehicle 2S will drive to the parking lot 52 by itself.

[0086] When the movement to the parking lot 52 is completed, the server device 1 transmits a return notification to the parking lot 52 to the provider terminal 51 (in this case, the provider's smartphone, etc.) in step S164. The return notification also includes information about the remaining charge of the provider vehicle 2S. For example, it may include information such as "charged 40%." In response to the return notification, the provider terminal 51 displays to the provider that the movement of the provider vehicle 2S has been completed and the remaining charge, and also displays a message recommending charging.

[0087] A situation in which the provider vehicle 2S has driven back to the parking lot 52 while the provider has already returned home may be one in which the provider, who is in the residence 3, is likely to forget to charge the provider vehicle 2S. Therefore, the server device 1 reminds the provider to charge the provider vehicle 2S. In particular, by displaying information about the remaining charge on the provider terminal 51, the provider can accurately determine whether or not it is actually advisable to charge the vehicle, and can go to the parking lot 52 to charge the vehicle if necessary.

[0088] On the other hand, if automatic movement is not permitted, the server device 1 proceeds from step S162 to step S165 and notifies the provider terminal 51 (such as the provider's smartphone) that a parking space 52 has become available. This allows the provider to head to the waiting area 58 at any time and return the provider vehicle 2S to the parking space 52 by self-propelled or manual driving. In this case, the provider can check the remaining charge and be aware of the need to charge the vehicle when returning to the parking space 52, so there is no need to issue a warning to charge the vehicle.

[0089] In the various cases described in FIG. 8 , the process proceeds to step S135 when the user stops charging and exits. In this case, the server device 1 proceeds to step S151 in FIG. 9 as indicated by "C2." In step S151, the server device 1 checks the charging status of the user's vehicle 2R. For example, the server device 1 receives information about the actual amount of charging by the charger 53 from the provider terminal 51 and compares this with the planned charging amount set at the time of reservation. The server device 1 then determines whether the difference between the actual charging amount and the planned charging amount is equal to or greater than a predetermined amount.

[0090] If the difference is less than the predetermined amount, the server device 1 confirms in step S155 that the user's vehicle 2R has exited the parking lot 52, and then ends the process.

[0091] If the difference is equal to or greater than a predetermined amount, the server device 1 transmits a proposal for a nearby charging spot to the user terminal 21 in step S152. The user checks the nearby charging spots using the user terminal 21 and responds whether or not to accept the proposal. If the server device 1 receives a response indicating that the user does not particularly need to accept the proposal, the server device 1 proceeds from step S153 to step S155. The server device 1 then confirms that the user's vehicle 2R has exited and ends the process.

[0092] If the server device 1 receives a response that the user accepts the proposal, the server device 1 proceeds from step S153 to step S154, performs a reservation process for a nearby charging spot, and transmits route guidance information to the user's vehicle 2R. This allows the user to charge at another charging spot. Then, in step S155, the server device 1 confirms that the user's vehicle 2R has exited, and ends the process.

[0093] According to the above first processing example, adjustment is made in the case where the user vehicle 2R is present in the parking lot 52 when the provider vehicle 2S is about to return.

[0094] <Second Processing Example> A second processing example will be described with reference to Fig. 10. Note that "C1", "C2", and "C3" in Fig. 10 proceed to Fig. 9. Note that the processing described in Fig. 9 is also performed in the second processing example, and in the third and fourth processing examples described below.

[0095] The second processing example is an example in which it is known in advance that the provider vehicle 2S will return earlier. When the server device 1 determines in step S201 that the provider vehicle 2S is currently being rented and when it determines in step S202 that the provider vehicle 2S will return earlier than the scheduled date and time, the server device 1 performs processing from step S203 onwards.

[0096] Note that the situation where it is known in advance that the provider will return early is assumed to be one in which, for example, the provider's activity schedule is changed and the provider terminal 51 (such as the provider's smartphone) notifies the server device 1 that the provider will return earlier than the rental end date and time.

[0097] When the notification is received, the server device 1 notifies the provider terminal 51 in step S203 to request a response on how to respond, and confirms the response information. For example, the provider can select whether to wait until charging is completed or to request the user to leave the parking lot 52.

[0098] If the provider chooses to wait until the scheduled date and time and operates the provider terminal 51 to send a response to the server device 1 indicating that he or she will wait, the server device 1 proceeds from step S203 to step S204 and notifies the user terminal 21 that the provider's return will be earlier but that he or she will wait.

[0099] Then, in step S220, the server device 1 monitors the return of the provider, and when the return is detected, in steps S221 and S222, the provider vehicle 2S is put into a waiting state at the waiting place 58. The occupants of the provider, etc., can get off the vehicle and go home. These steps S220, S221, and S222 are the same processes as steps S101, S103, and S104 in FIG. 8.

[0100] In step S223, the server device 1 waits for the charging of the user vehicle 2R to be completed, and when the charging is completed, in step S224, instructs the provider terminal 51 to stop the power supply. Thereafter, the server device 1 performs the processes from step S161 onwards in FIG.

[0101] In step S203, if the provider operates the provider terminal 51 to transmit a response to the server device 1 requesting the user vehicle 2R to exit, the server device 1 notifies the user terminal 21 in step S205 that the provider has requested the user to exit. In response, the user may transmit a response from the user terminal 21 indicating that the provider has requested the user to exit or that the user wishes to continue using the service.

[0102] If the server device 1 receives a response from the user terminal 21 in step S206 indicating that the user wishes to continue using the service until the scheduled date and time, the server device 1 checks the terms of use in step S207. If the server device 1 determines that the user is given priority, the server device 1 proceeds to the processing of step S220 and subsequent steps. In other words, the server device 1 performs the processing of steps S220 to S224 and step S161 and subsequent steps in FIG. 9.

[0103] If the server device 1 receives information from the user terminal 21 indicating consent to the withdrawal, the server device 1 proceeds from step S206 to step S208, and performs processing to reduce the reward for the provider under predetermined conditions. If the server device 1 determines in step S207 that priority is given to the provider, the server device 1 also proceeds to step S208.

[0104] Then, in step S209, the server device 1 instructs the provider terminal 51 to stop the power supply within a predetermined time. In this case, in the subsequent processing of step S151 and subsequent steps in FIG. 9 , another charging spot is suggested to the user for convenience. However, in this case, there may be some time until the provider vehicle 2S actually returns. Therefore, the predetermined time in this case may be the time until the predicted date and time when the provider vehicle 2S actually returns, and charging may be continued until that time. Alternatively, at this time, a return determination of the provider vehicle 2S may be performed as in step S220, and charging may be continued until return is detected.

[0105] After that, after actually stopping the power supply, the server device 1 performs the processes from step S151 onward in FIG.

[0106] By the above process, if it is known in advance that the return of the provider vehicle 2S will be earlier, adjustments can be made before the actual return time and a response to the user can be determined.

[0107] <Third Processing Example> A third processing example will be described with reference to Fig. 11. Note that "C1", "C2", and "C3" in Fig. 11 lead to Fig. 9. Note that the third processing example is also an example in which it is known in advance that the provider vehicle 2S will return early, and only the differences from Fig. 10 will be described.

[0108] The processing example in Fig. 11 differs in that the notification in step S204 in Fig. 10 is not performed, but is performed in steps S230 and S231. The notification in step S204 in Fig. 10 notifies the user that the return will be earlier even when the provider is willing to wait. This may cause the user to feel psychological pressure even though the charging is being performed as scheduled.

[0109] 11, the server device 1 waits in step S230 until the scheduled return date and time of the provider vehicle 2S, that is, the rental end date and time as originally reserved, and notifies the user when the scheduled date and time arrives in step S231. The server device 1 then performs steps S223 and S224 and the processes from step S161 onwards in FIG.

[0110] This prevents the user from feeling uneasy if the user can rent the item as reserved regardless of the provider's return.

[0111] <Fourth Processing Example> A fourth processing example will be described with reference to Fig. 12. Note that "C1", "C2" and "C3" in Fig. 12 proceed to Fig. 9.

[0112] The fourth processing example is a processing example that takes into consideration the case where the user's charging is not completed even after the scheduled date and time has passed. Charging may not be completed, for example, when the server device 1 is unable to accurately calculate the time required for charging and is unable to set a reservation for an appropriate charging time, when the user makes an operational error, or when there is a malfunction or problem with the performance of the charger 53. There may also be cases where the user leaves the vehicle 2R and does not return even after the scheduled date and time has passed.

[0113] When the server device 1 determines in step S301 that the vehicle is currently being rented and determines in step S302 that the provider vehicle 2S has returned, the server device 1 performs the processes in step S303 and thereafter.

[0114] In step S303, the server device 1 determines whether the user's vehicle 2R is still being charged after the scheduled rental end date and time has passed. If the charging has already finished, no adjustment process is necessary, and the processes in Figures 12 and 9 are terminated. In this case, "being charged" refers to a state in which the user's vehicle 2R has not yet left the parking lot.

[0115] If charging is in progress, the server device 1 notifies the provider that charging is in progress and determines whether the provider will wait in step S304. If the provider selects to wait until charging is complete and operates the provider terminal 51 to transmit a response to the server device 1 indicating that the provider will wait, the server device 1 proceeds from step S304 to step S305 and notifies the user terminal 21 that the provider has returned but will wait.

[0116] Then, in steps S320 and S321, the server device 1 causes the provider vehicle 2S to wait at the waiting area 58. The occupants can get off and go home. In step S322, the server device 1 waits for charging to be completed, and when charging is completed, in step S323, it instructs the provider terminal 51 to stop supplying power. Thereafter, the server device 1 performs the processes from step S161 onwards in FIG. 9 .

[0117] In step S304, if the provider operates the provider terminal 51 to transmit a response to the server device 1 requesting the user vehicle 2R to exit, the server device 1 notifies the user terminal 21 in step S306 that the provider has requested the user to exit. In response, the user may transmit a response from the user terminal 21 indicating that the provider has requested the user to exit or that the user wishes to continue using the service.

[0118] If in step S307 the server device 1 receives a response from the user terminal 21 indicating a desire to use the service beyond the scheduled time, the server device 1 checks the terms of use in step S308. If it determines that the user is given priority, the server device 1 increases the user's usage fee under predetermined conditions in step S309, and proceeds to step S320 and subsequent steps. This is because the user will be using the service beyond the scheduled date and time. However, if the reason for not being able to complete charging within the scheduled time lies on the server device 1 side or the charger 53 side, it is possible that the usage fee will not be increased.

[0119] If the server device 1 receives information from the user terminal 21 indicating consent to the exit, the server device 1 proceeds from step S307 to step S310. Also, if it determines in step S308 that the provider has priority, the server device 1 proceeds to step S310. In step S310, the server device 1 instructs the provider terminal 51 to stop the power supply within a predetermined time, and then proceeds to the processing of step S151 and subsequent steps in FIG. 9.

[0120] By the above processing, adjustments can be made in the event that charging of the user vehicle 2R does not finish within the scheduled time.

[0121] <Effects of the Embodiments> The above-described embodiments provide the following effects. When an autonomously driven provider vehicle 2S returns to a parking lot 52 and the parking lot 52 is occupied by a user vehicle 2R, the server device 1 of the embodiment performs a process of instructing the provider vehicle 2S to move to a predetermined waiting location 58 in response to an occupant disembarking from the provider vehicle 2S (step S104 in FIG. 8 , step S222 in FIGS. 10 and 11 , and step S321 in FIG. 12 ). Furthermore, upon detecting that the user vehicle 2R has exited the parking lot 52, the server device 1 performs a process of instructing the provider vehicle 2S to move from the waiting location 58 to the parking lot 52 (step S163 in FIG. 9 ). Furthermore, upon the return of the provider vehicle 2S to the parking lot 52, the server device 1 performs a process of transmitting a return notification to the provider (step S164 in FIG. 9 ). If the provider returns earlier than the scheduled date and time, or if the return date and time is as scheduled but the user is charging, the provider vehicle 2S cannot enter the parking lot 52, but by waiting in a nearby waiting area 58, the provider's occupants can disembark and go home. When the user vehicle 2R leaves the parking lot 52, the provider vehicle 2S drives itself into the parking lot 52. This prevents the provider from experiencing any inconvenience when subscribing to the charger rental service.

[0122] In the embodiment, the return notification in step S164 of Fig. 9 includes information indicating the remaining charge of the rechargeable battery of the provider vehicle 2S. After the user vehicle 2R leaves, the provider receives a notification via the provider terminal 51 as the provider vehicle 2S drives into the parking lot 52. The remaining charge is displayed, allowing the provider to determine whether charging is necessary. This helps the provider remember to go to the parking lot 52 and charge the provider vehicle 2S.

[0123] In the embodiment, the server device 1 performs a process of transmitting a provider return notification to the user terminal 21 in response to the return of the provider vehicle 2S when the parking lot 52 is occupied by the user vehicle 2R (step S111 in FIG. 8 , step S205 in FIGS. 10 and 11 , and step S306 in FIG. 12 ). The server device 1 also performs a process of increasing or decreasing the user's payment fee or the benefit to be provided to the provider depending on the relationship between the return date and time of the provider vehicle 2S and the scheduled charging end date and time, and whether the user vehicle 2R has left the parking lot 52 (steps S114 and S134 in FIG. 8 , step S208 in FIGS. 10 and 11 , and step S309 in FIG. 12 ). By learning of the provider's return, the user can decide whether to leave the user vehicle 2R from the parking lot 52 or continue charging. In this case, the server device 1 adjusts the user's payment amount and the provider's compensation, taking into account circumstances such as the provider's return earlier than planned, the user's charging exceeding the time limit, or the user's leaving even while charging. This allows for fair service to be provided to both parties.

[0124] In the embodiment, an example has been given in which the server device 1 transmits the provider return notification after the scheduled charging end date and time arrives when the provider vehicle 2S selects to wait until charging of the user vehicle 2R is completed (steps S230 and S231 in FIG. 11 ). If the provider returns early for personal reasons, the provider can select to wait until charging is completed. In this case, by not sending the provider return notification to the user until the scheduled charging end date and time (rental end), unnecessary psychological pressure on the user can be avoided.

[0125] In the embodiment, when the provider wishes to have the user's vehicle 2R exit the parking lot 52 and the user wishes to continue charging in the parking lot 52, the server device 1 determines which priority to give based on the terms of use (steps S113 and S132 in FIG. 8 , step S207 in FIGS. 10 and 11 , and step S308 in FIG. 12 ). The server device 1 then executes processing to either exit the user's vehicle 2R or continue charging based on the determination result. For example, the server device 1 may stop the power supply for a predetermined time or stop the power supply after waiting for charging to be completed. When the provider's request for parking and the user's request for continued charging overlap, the server device 1 determines whether to give priority to the user or the provider based on the terms of use and the situation, and selects whether to move the provider's vehicle 2S to the waiting area 58 or to stop charging the user's vehicle 2R. This allows both the user and the provider to be satisfied.

[0126] REFERENCE SIGNS LIST 1 System management server device (server device) 1a Registration processing unit 1b Reservation setting processing unit 1c Charging and settlement management unit 2 Vehicle 3 Residence 21 User terminal 30 Information processing device 51 Provider terminal 52 Parking lot 53 Charger 54 Gun 55 Panel 61 Control device 68 Communication unit

Claims

1. one or more processors; a storage medium storing a program to be executed by the one or more processors; The program includes one or more instructions, The one or more instructions may cause the one or more processors to: When an autonomously driven provider vehicle of a provider that has provided a user with a charger installed in a parking lot for personal use returns to the parking lot and the parking lot is occupied by a user vehicle, a process of instructing the provider vehicle to move to a predetermined waiting location in response to a passenger disembarking from the provider vehicle; a process of transmitting a provider return notification to a terminal used by a user in response to the return of the provider vehicle when the vehicle is occupied; a process of instructing the provider vehicle to move from the waiting location to the parking lot in response to detecting the user vehicle leaving the parking lot; a process of transmitting a return notification to a terminal used by the provider in response to the provider vehicle returning to the parking lot; a process of increasing or decreasing the fee paid by the user and / or the benefit provided to the provider depending on the relationship between the return date and time of the provider vehicle and the scheduled charging end date and time and whether the user vehicle has left; Run Server device.

2. The return notice shall include: The information indicating the remaining charge of the rechargeable battery of the provider vehicle is included. The server device according to claim 1 .

3. If the provider vehicle selects to wait until the charging of the user vehicle is completed, the provider return notification is transmitted after the scheduled charging completion date and time.

3. The server device according to claim 1.

4. one or more processors; a storage medium storing a program to be executed by the one or more processors; The program includes one or more instructions, The one or more instructions may cause the one or more processors to: When an autonomously driven provider vehicle of a provider that has provided a user with a charger installed in a parking lot for personal use returns to the parking lot and the parking lot is occupied by a user vehicle, a process of instructing the provider vehicle to move to a predetermined waiting location in response to a passenger disembarking from the provider vehicle; a process of instructing the provider vehicle to move from the waiting location to the parking lot in response to detecting the user vehicle leaving the parking lot; a process of transmitting a return notification to a terminal used by the provider in response to the provider vehicle returning to the parking lot; Execute When the provider desires for the user's vehicle to leave the parking lot and the user desires for the user's vehicle to continue charging in the parking lot, a determination is made as to which of the two is to be given priority in accordance with the conditions of use, and a process is executed to either allow the user's vehicle to leave or continue charging in accordance with the determination result. Server device.

Images