Server device

JPWO2025004316A5Active Publication Date: 2025-07-18SUBARU CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2025529166
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-06-30
Filing Date
2023-06-30
Publication Date
2025-07-18
Estimated Expiration
2043-06-30

AI Technical Summary

Technical Problem

The scarcity of charging spots for electric vehicles, especially in remote areas, and the inefficiency of household chargers when not in use, along with challenges in coordinating private home charging spot usage, lead to inconvenience and underutilization of charging infrastructure.

Method used

A server device that facilitates the rental of private home chargers by matching user requests with available chargers through a registration and reservation system, ensuring efficient usage and payment processing, thereby utilizing private homes as charging spots and addressing the shortage of public charging infrastructure.

Benefits of technology

This solution enables the effective use of private home chargers, alleviates the shortage of charging spots for electric vehicles, and provides a secure and convenient charging solution for users while offering a business opportunity for providers, ensuring aligned interests and reduced inconvenience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025004316000001
    Figure 2025004316000001
Patent Text Reader

Abstract

This server device is provided with one or a plurality of processors and a storage medium that stores a program to be executed by the one or plurality of processors, said program including one or a plurality of instructions. The one or plurality of instructions cause the one or plurality of processors to perform: registration processing for registering information about providers who provide chargers at home, and information about users who wish to use chargers at other people's homes; reservation setting processing for, in response to a use request transmitted from a certain user terminal, extracting a provider who matches the use request from the registered information, causing the user terminal to present information about the extracted provider, and setting a reservation according to reservation decision information from the user terminal; and settlement processing regarding a user's use of the provider's charger to charge a vehicle on the basis of the set reservation.
Need to check novelty before this filing date? Find Prior Art

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] The following Patent Documents 1 and 2 disclose techniques for charging electric vehicles, which are intended to utilize home charging stations.

[0003] Patent Document 1: WO2011 / 115113 Patent Document 2: JP2019-221014A

[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 charge is complete, the lender may not be able to park. For these reasons, coordinating usage when using private homes as charging spots is difficult.

[0005] Therefore, the present invention provides a technique for effectively utilizing chargers in private homes and facilitating adjustment.

[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 perform a registration process for registering information about providers who provide chargers installed in parking lots 52 for personal use and information about users who wish to use chargers installed in parking lots 52 used by others; a reservation setting process for extracting providers that match the usage request from the registered information in response to a usage request sent from a user terminal, presenting information about the extracted provider on the user terminal, and setting a reservation in accordance with the information from the user terminal; and a settlement process for charging a vehicle by a user using the provider's charger based on the set reservation.

[0007] According to the present invention, ordinary homes can be used as charging spots, thereby resolving the shortage of charging spots for electric vehicles. Furthermore, the server device matches the area and date and time of use between providers and users, eliminating the risk of inconvenience to providers.

[0008] FIG. 1 is an explanatory diagram of a system configuration according to 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 according to an embodiment. FIG. 3 is a block diagram of a vehicle configuration according to an embodiment. FIG. 4 is an explanatory diagram of a procedure for a charger rental service according to an embodiment. FIG. 5 is an explanatory diagram of a functional configuration of a server device according to an embodiment. FIG. 6 is an explanatory diagram of a functional configuration of a user terminal according to an embodiment. FIG. 7 is an explanatory diagram of a functional configuration of a provider terminal according to an embodiment. FIG. 8 is a flowchart of a registration process according to an embodiment. FIG. 9 is a flowchart of a reservation process according to an embodiment. FIG. 10 is an explanatory diagram of an example of a display when a reservation is made according to an embodiment. FIG. 11 is a flowchart of processing after charging is performed according to 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 with 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. A provider is a person who is willing to lend the charger 53 installed in the parking lot 52 that they use to other people and has registered as a provider with the charger rental service provided by the server device 1. By becoming a registered provider, they can receive compensation in return for allowing other people to use their charger 53.

[0011] 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 2, or may be an information processing device such as a smartphone, personal computer, or tablet device carried by the user.

[0012] 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 .

[0013] 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 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 a vehicle (not shown) 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.

[0014] The provider terminal 51 performs processing 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 and an information processing device in the charger 53 may function as the provider terminal 51 in cooperation with each other.

[0015] 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.

[0016] 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 so that charging can be performed at the location and date and time desired by the user. This allows users to charge their vehicles 2 even in areas where there are not many charging stations. In addition, the provider is rewarded for lending the charger. This also provides a simple business opportunity for the provider.

[0017] A charger 53 is installed in a parking lot 52 at the provider's residence 3. Normally, the provider's own vehicle is parked in the parking lot 52 and charged using the charger 53. The charger rental service of this embodiment allows users to charge their vehicles when the provider is out in their vehicle and the parking lot 52 and charger 53 are not in use.

[0018] 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 connects the gun 54 to a connector 67 (see FIG. 3 ), which is the charging port of the vehicle 2, to charge the battery. The charger 53 is provided with an internal measurement circuit that measures the amount of charge, and this measurement information on the amount of charge obtained by this measurement circuit can be acquired by the provider terminal 51.

[0019] 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 2, as well as the state of charging. The provider terminal 51 can obtain information about the vehicle 2, 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 server device 1 can detect the vehicle license plate, model, and so on.

[0020] 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 a separate location from the residence 3, where the provider normally parks. In this embodiment, the charger 53 covered by the charger rental service is a charger installed in a parking lot 52 used by the provider, such as a parking lot on the premises of the residence 3 as the provider's home, or a parking lot 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 possible for a company, organization, etc. to be the provider in this embodiment, and the parking lot or charger of the company, etc. may be the parking lot 52 or charger 55 in FIG. 1 .

[0021] <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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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.

[0028] 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.

[0029] <Vehicle Configuration> Incidentally, a system within the vehicle may be used as the user terminal 21 or the provider terminal 51. Figure 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.

[0030] 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 .

[0031] 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.

[0032] 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.

[0033] In this embodiment, it is also assumed that the vehicle 2 is an autonomous vehicle, and therefore the vehicle 2 is also equipped with information processing devices necessary for autonomous driving. For example, the control device 61 may 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

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

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] <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.

[0044] (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, 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.

[0045] (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.

[0046] (ST4) At any time, the user sends a request to use a charger 53 to the server device 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 area and date and time match those of the providers whose 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 the charger 53. The server device 1 sets the reservation in response to the confirmation operation.

[0047] (ST5) The user's vehicle 2 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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 when the provider can provide the charger 53 and parking lot 52 to others. For example, the date and time information includes the start date and time when rental is available and the end date and time when 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.

[0052] 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.

[0053] The server device 1 performs the processes shown in FIGS. 8, 9, and 12, which will be described later, using the functions of the registration processing unit 1a, the reservation setting processing unit 1b, and the charging and settlement management unit 1c.

[0054] 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.

[0055] The registration processing unit 21 a has a function of providing a user interface for users to register as users and performing processes such as transmitting registration information to the server device 1 .

[0056] The reservation request processing unit 21 b is a function that provides a user interface for users to make usage requests and communicates with the server device 1 .

[0057] The charging execution processing unit 21 c 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 .

[0058] The user terminal 21 performs the processes shown in FIGS. 8, 9, and 12, which will be described later, using the functions of the registration processing unit 21a, the reservation request processing unit 21b, and the charging execution processing unit 21c.

[0059] 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.

[0060] The registration processing unit 51 a has a function of providing an interface for a provider to register as a provider, and of transmitting registration information to the server device 1 .

[0061] 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 willing to rent the content to the server device 1.

[0062] The charging management unit 51c has a function of performing the necessary processing in response to a user using the charger 53 to charge, such as authentication processing, measurement of the amount of charge and power consumption, processing related to settlement, and communication with the server device 1 associated with these.

[0063] The provider terminal 51 performs the processes shown in FIGS. 8, 9, and 12, which will be described later, using the functions of the registration processing unit 51a, the provided information processing unit 51b, and the charging correspondence management unit 51c.

[0064] An example of processing performed by the server device 1, the user terminal 21, and the provider terminal 51 having the above functions will be described below.

[0065] 8 shows an example of the registration process performed in advance as the above-mentioned (ST1) and (ST2). This process is performed by the functions of the registration processing unit 1a of the server device 1, the registration processing unit 21a of the user terminal 21, and the registration processing unit 51a of the provider terminal 51.

[0066] In step S101, the provider terminal 51 transmits the registration information P11 to the server device 1. For example, a user who wants to become a provider operates the provider terminal 51 to input the necessary registration information and perform a transmission operation. In response to this, the provider terminal 51 transmits the registration information P11.

[0067] The provider's registration information P11 includes, for example, personal information such as name, address, email address, and account number for receiving rewards, as well as information about the parking lot 52 and information about the charger 53.

[0068] Possible information about the parking lot 52 includes the size of the parking lot 52, an access road to the parking lot 52, an image of the parking lot 52, the type of the parking lot 52, whether or not it has a ground or a roof, etc. Possible information about the charger 53 includes the type of the charger 53, the product name, model number, charging capacity, various specifications, the type and length of the gun 54, an image of the charger 53, etc.

[0069] When the server device 1 receives the registration information P11 containing some or all of these contents, it performs a registration process in the provider registration database 6 in the storage device 5 in step S201. As a result, the user who performed the registration operation is registered as a provider of the charger rental service. Note that the provider does not have to enter all of the registration information P11. For example, information about the charger may be entered by entering only the charger's product name, model number, etc., and the server device 1 may determine its specifications and register them in addition to the registration information P11.

[0070] In step S301, the user terminal 21 transmits the registration information Q11 to the server device 1. For example, a user who wishes to become a user operates the user terminal 21, inputs the necessary registration information, and performs a transmission operation. In response, the user terminal 21 transmits the registration information Q11.

[0071] The user's registration information Q11 includes, for example, personal information such as name, address, email address, and credit card number for payment of fees, as well as information about the vehicle.

[0072] The vehicle-related information may include the vehicle model, year, vehicle license plate number, vehicle color, etc. The registration information Q11 may also include the type, product name, model number, etc. of connectable chargers. Alternatively, the server device 1 may determine connectable chargers from the vehicle model information.

[0073] When the server device 1 receives the registration information Q11 including some or all of these contents, in step S202 it performs a registration process in the user registration database 7 in the storage device 5. As a result, the user who performed the registration operation is registered as a user.

[0074] As described above, the provider registration database 6 and the user registration database 7 are successively updated. Note that providers in the provider registration database 6 and users in the user registration database 7 input each other's evaluation information when renting. This input evaluation information is also successively added to and updated in the provider registration database 6 and the user registration database 7 by the server device 1.

[0075] Next, the processing related to the above (ST3) and (ST4), i.e., the processing up to the reservation of use, will be described with reference to Fig. 9. This processing is performed by the functions of the reservation setting processing unit 1b of the server device 1, the reservation request processing unit 21b of the user terminal 21, and the provided information processing unit 51b of the provider terminal 51.

[0076] In step S120, the provided information P21 is transmitted from the provider terminal 51 to the server device 1. For example, the provider inputs the provided information into the provider terminal 51 at any time, such as when the provider has decided to go out or when the provider is about to go out, and performs a transmission operation, thereby transmitting the provided information P21 to the server device 1. The provided information P21 is information including date and time information and provider identification information when the provider can provide the charger 53 and parking lot 52 to others. Note that the date and time information is information that indicates at least the start date and time when rental is available and the end date and time when rental is available.

[0077] When the server device 1 receives the provided information P21 including the date and time information and the provider identification information, it performs a process of entering the sender of the provided information P21 as a valid provider for the period indicated by the date and time information included in the provided information in step S220. Note that an unspecified number of providers may transmit provided information P21 including their own date and time information to the server device 1 at their own timing. Each time such transmission occurs, the server device 1 responds by performing the process of step S220.

[0078] In step S320, the user terminal 21 transmits a usage request Q21 to the server device 1. A user who wishes to rent a charger 53 operates the user terminal 21 and inputs predetermined data for the usage request, such as the area in which the user wishes to rent the charger 53, the rental start date and time, the charging time (the time during which charging will be performed), the target charging rate or charging power, and the current charging rate (SOC: State Of Charge).

[0079] When the control device 61 of the vehicle 2 functions as the user terminal 21, the control device 61 may detect the current charging rate of the on-board battery 62. When a smartphone or the like is the user terminal 21, the smartphone or the like may communicate with the vehicle 2 to obtain the current charging rate. Alternatively, the current charging rate may be input by the user looking at a display on the display unit 66 or the like of the vehicle 2 and roughly inputting a value such as "50%" or "30%." Furthermore, the target charging rate may be input by the user roughly specifying a value such as "80%" or "100%." ​​Alternatively, the user may input the charging power (W) as desired.

[0080] When a usage request Q21 containing some or all of the above information, such as the desired area, rental start date and time, charging time, target charging rate or charging power, and current charging rate, as well as the user's identification information, is sent from the user terminal 21, the server device 1 extracts candidates for the usage request Q21 in step S221.

[0081] For example, the server device 1 first accesses the user registration database 7 using the user's identification information to obtain vehicle information such as the model and year of the user's vehicle 2. If information on compatible chargers is available, that information is also obtained. Evaluation information about the user is also obtained.

[0082] The server device 1 first extracts providers whose provision information has been entered that match the area specified in the usage request Q21. Furthermore, by referencing the date and time information from among the providers whose area matches, the server device 1 extracts providers that include time slots that can accommodate the rental start date and time and charging time specified in the usage request Q21. The server device 1 can calculate the charging time, for example, using the target charging rate in the usage request Q21, the current charging rate, and the charging capacity of each charger 53 that has been entered as available for reservation. Therefore, providers that can rent a charger for the calculated charging time may be extracted.

[0083] Furthermore, if the providers entered as available for reservation include a provider of a charger 53 that cannot accommodate the vehicle type in the usage request Q21, or a provider of a parking lot 52 that the vehicle type in the usage request Q21 cannot enter due to vehicle width, height, etc., the server device 1 excludes that provider from the extraction targets. Also, if the access route to the parking lot 52 is too narrow for the vehicle type in the usage request Q21 to pass through, the server device 1 excludes that provider from the extraction targets.

[0084] Through these processes, the server device 1 can extract providers (parking lots 52 and chargers 53) that are available for rental in response to the usage request Q21. In this case, "available for rental" means that the charger 53 and parking lot 52 are available for use on the desired date and time (time zone), and that the charger 53, parking lot 52, and access route are compatible with the user's vehicle 2.

[0085] After extracting one or more providers who are available for rental, the server device 1 sets a presentation area in step S222. For example, if the area where the parking lot 52 of the provider who is available for rental is located is to be displayed as an area frame 72 on a map as shown in Figure 10, the range of the area frame 72 is set.

[0086] 10, for example, the location of the provider's parking lot 52 is roughly indicated by an area frame 72 in the map image 70, and specific locations are not displayed with pins or the like. This is to prevent the provider's residence 3 and parking lot 52 available for reservation from being specified. In other words, the reservation-available dates and times are dates and times when the provider is not at home, so from a security standpoint, the locations of the provider's residence 3 and parking lot 52 should not be made public without due consideration.

[0087] For this reason, the server device 1 sets the position and size of the area frame 72 based on the addresses of one or more extracted providers. For example, if multiple providers are extracted, the position and size of the area frame 72 are set to a range that includes all of those providers. However, it is preferable to set the area frame 72 to a wider range rather than the minimum range that actually includes the addresses, etc. of each provider. Furthermore, if only one provider is extracted, it is preferable to set the position and size of the area frame 72 so that the area frame 72 is not centered on the address of that provider (i.e., so that the address cannot be guessed from the area frame 72).

[0088] The area frame 72 is not limited to a circle, but may be a square or an irregular shape. Alternatively, it may be a frame along administrative boundaries such as a city, town, or village. The only requirement is that the user can confirm the area, but the user will not know the exact address of each provider.

[0089] Then, in step S223, the server device 1 transmits area information, including the setting of the area frame 72, and information on the candidate providers to the user terminal 21, so that a display such as that shown in Fig. 10 is displayed on the user terminal 21. In the example of Fig. 10, an area for provider information 71 for each provider that can rent a charger 53 is provided, and the necessary information is displayed. The server device 1 also transmits information on the candidate providers to the user terminal 21 in order to display the provider information 71.

[0090] Each provider information 71 displays information about the respective provider. Alternatively, an operation on the provider information 71 may open a detailed provider information screen to display more detailed information. In these cases, the following may be displayed: Evaluation information of the provider Model name, charging capacity, predicted charging time, etc. of the provider's charger 53 Type of the provider's parking lot 52 (paved, gravel, covered, etc.) Images of the charger 53 Images of the parking lot 52 Road conditions of the access road to the parking lot 52 (road width, whether paved, etc.)

[0091] For example, by presenting this information, it is possible to provide the user with the information necessary for making a selection while concealing the personal information of each provider candidate. In particular, the image of the parking lot 52 is useful for showing the parking lot status of the charging spot. Furthermore, the image of the charger 53 is useful for clarifying the type of charger. An image of the shape of the gun 54 or the connector may be presented so that the type of charger 53 can be identified. Furthermore, if a conversion cable is available, it is also preferable to present an image of the cable.

[0092] When presenting an image, it is desirable to use a mosaic process or other method to prevent the viewer from seeing anything other than the intended object, thereby ensuring the provider's security while allowing users to use the image as a reference when selecting a charging spot.

[0093] Here, the setting of the presentation area by the server device 1 in step S222 may reflect the evaluation information of the user who sent the use request Q21. For example, while the display would normally be as shown in Figure 10, for users with high ratings, the area frame 72 may be displayed in a smaller size as shown in Figure 11. For example, the position and size of the area frame 72 may be set to the minimum range that includes the addresses of multiple candidate providers. This allows users with high ratings to select providers from a clearer range.

[0094] Furthermore, the content displayed in the provider information 71 may be more detailed depending on the user's rating. For example, images of the charger 53 and parking lot 52 are not usually displayed, but for a user with a high rating, these may be displayed.

[0095] 10 or 11 to the user, and performs processing corresponding to the user's operation. For example, the user terminal 21 performs processing to display detailed information about the provider in response to the user's operation, and processing to accept a decision operation to select the provider.

[0096] Although not shown, the user may make a usage request again in a different area or at a different date and time, in which case the process returns to step S320. The user may also perform an operation to cancel the usage request, in which case the user terminal 21 notifies the server device 1 of the cancellation.

[0097] When the user performs an operation to select a provider, in step S322, the provider terminal 51 transmits decision operation information Q22 to the server device 1. In response to this, the server device 1 performs reservation setting processing in step S224. That is, for the current user, a provider is determined in accordance with the decision operation information Q22, and reservation setting information specifying the date and time, etc. is generated.

[0098] Then, in step S225, the server device 1 transmits reservation confirmation notifications R22 and R23 to the provider terminal 51 and the user terminal 21. The reservation confirmation notification R22 includes information about the reservation date and time and the user. Based on this, the provider terminal 51 presents information about the confirmed reservation. For example, the provider terminal 51 presents the provider with the user's name, date and time information including the charging start date and time and the charging end date and time, vehicle information, and the like. The provider terminal 51 also stores this information about the reservation.

[0099] The reservation confirmation notification R23 also includes the reservation date and time, location information of the provider's parking lot 52, access route information, and information about the charger 53. Based on this, the user terminal 21 presents information about the confirmed reservation. For example, the user terminal 21 presents the user with location information and access information of the parking lot 52, date and time information including the charging start date and time and charging end date and time, information about the parking lot, and the like. This allows the user to know the location of the provider's parking lot 52. Note that the user terminal 21 may automatically set the location information of the provider's parking lot 52 as a destination in a navigation system or an automatic driving control system.

[0100] 12 , the process from (ST5) to (ST11) above, that is, the process after the user's vehicle 2 arrives at the reserved parking lot 52, will be described. This process is performed by the functions of the charging / payment management unit 1c of the server device 1, the charging execution processing unit 21c of the user terminal 21, and the charging correspondence management unit 51c of the provider terminal 51.

[0101] The vehicle 2 of the user who made the reservation in the process of Figure 9 above enters the provider's parking lot 52 on the reserved date and time. At this time, authentication processing is performed. The authentication processing may be performed by the provider terminal 51 in step S130, by the user terminal 21 in step S330, or by both the provider terminal 51 and the user terminal 21.

[0102] In the case where the provider terminal 51 performs this authentication, for example, the camera 59 photographs the vehicle 2 entering the parking lot 52, and analyzes the vehicle license plate number, model, body color, etc. from the photographed image. If these match the vehicle license plate number, model, body color, etc. notified in the reservation confirmation notice R22, authentication can be established. The authentication result is transmitted from the provider terminal 51 to the server device 1 in step S131.

[0103] Alternatively, for example, the above-mentioned reservation decision notifications R22 and R23 may include information such as a reservation code, and when the user operates the panel 55 of the charger 53 and correctly enters the reservation code, the provider terminal 51 may determine that authentication has been established.

[0104] When the authentication process is performed at the provider terminal 51 as in the above example, the authentication result is transmitted from the provider terminal 51 to the server device 1 in step S131.

[0105] When the authentication process is performed by the user terminal 21, for example, the user may use the user terminal 21 to read a two-dimensional code or the like displayed on the charger 53 and transmit it to the server device 1. In this case, the determination of whether authentication is successful is made by the server device 1, and if authentication is successful, the server device 1 transmits a message indicating that authentication is successful to the user terminal 21 and the provider terminal 51. In this case, for example, the user terminal 21 performs a process of reading the two-dimensional code in step S330, and communicates with the server device 1 in step S331 to receive a result indicating whether authentication is successful or not.

[0106] There is also a method for authentication in which the provider terminal 51 and the user terminal 21 communicate with each other via wireless communication such as NFC (Near Field Communication). For example, the reservation decision notifications R22 and R23 include each other's authentication codes. Then, the provider terminal 51 and the user terminal 21 mutually confirm the authentication codes via wireless communication to perform authentication.

[0107] In response to the authentication being established through these authentication processes, the server device 1 starts charge start management in step S230. That is, it confirms that the user has arrived at the provider's parking lot 52 and is ready to charge.

[0108] In the parking lot 52, the user can attach the gun 54 of the charger 53 to the connector 67 of the vehicle 2 and start charging. If authentication is not successful, the provider terminal 51 may control the charger 53 so that it does not supply charging current even when the gun 54 is connected. Alternatively, the storage section for the gun 54 may be provided with a lockable lid that cannot be opened unless authentication is successful.

[0109] During charging, the provider terminal 51 performs charging processing in step S132. For example, it measures the amount of charge. For example, it monitors and stores the value of the wattmeter attached to the charger 53. The user terminal 21 also performs charging processing in step S332. For example, it counts the charging time and waits for the user to operate to end charging. The user terminal 21 may also communicate with the server device 1 sequentially to transmit a status of charging.

[0110] When charging is complete, the user operates the user terminal 21 to end charging. For example, a button to be operated when charging is complete is provided on the screen of the user terminal 21. When the user inputs charging completion into the user terminal 21, the user terminal 21 sends an end notification Q32 to the server device 1 in step S333. The provider terminal 51 also determines that charging is complete by confirming that the gun 54 of the charger 53 has been disconnected or stored. In this case, the provider terminal 51 sends an end notification P32 to the server device 1 in step S133. This end notification P32 also includes information about the amount of charge.

[0111] When the server device 1 receives the completion notifications P32 and Q32, it confirms in step S231 that charging via the current rental of the charger 53 has ended, and manages history information of the current charger rental, etc. For example, the server device 1 manages the user's identification information, the provider's identification information, the start and end date and time information of charging, the amount of charging, etc. as history information.

[0112] Thereafter, the server device 1 performs a settlement process in step S240, and the user terminal 21 performs a settlement process in step S340. For example, the server device 1 determines a fee according to the amount of charging this time, and generates settlement data using a payment method according to the payment information registered for the user. Then, a settlement notice R33 based on this is sent to the user terminal 21. The user terminal 21 performs a display process based on the settlement notice R33, and presents the fee for this charging to the user.

[0113] The server device 1 also performs a settlement process in step S250, and the provider terminal 51 also performs a settlement process in step S140. For example, the server device 1 determines the amount of money to be refunded to the provider based on the amount of charging this time, and generates settlement data for depositing the money into the provider's bank account, for example. The server device 1 then transmits a settlement notice R34 based on this to the provider terminal 51. The provider terminal 51 performs a display process based on the settlement notice R34, and indicates to the provider the amount to be transferred in response to this charging, the date and time of the transfer, etc.

[0114] Thereafter, the user and the provider can transmit evaluation information at any time. For example, in step S350, the user terminal 21 transmits evaluation information Q33 of the provider to the server device 1 in response to an operation by the user. The evaluation information content for the provider may include, for example, the condition of the parking lot 52, the surrounding environment, the condition of the access road, the condition of the charger 53, etc. Note that the user may transmit evaluation information of the provider to the server device 1, for example, while charging.

[0115] In step S260, the server device 1 performs a registration or update process for the evaluation information Q33 transmitted from the user terminal 21. That is, in the provider registration database 6, new registration of evaluation information or registration / addition / update of evaluation information is performed for the provider that is the subject of the received evaluation information Q33.

[0116] In step S150, the provider terminal 51 transmits the user's evaluation information R35 to the server device 1 in response to the provider's operation. The evaluation information for the user is sent by a provider who returns after the user has left, so it is expected that the evaluation information will include an evaluation of the condition of the parking lot 52 and the handling of the charger 53.

[0117] In step S261, the server device 1 performs a registration or update process for the evaluation information R35 transmitted from the provider terminal 51. That is, in the user registration database 7, new registration of evaluation information, registration addition, update, etc. of evaluation information is performed for the target user of the received evaluation information R35.

[0118] Such provider and user evaluation information is then presented when the user selects a provider, and the display format of the information when selecting a provider may be changed depending on the user's usage and the user's own evaluation.

[0119] Effects of the Embodiments The above-described embodiments provide the following effects. The server device 1 of the embodiment performs a registration process to register information about providers who offer chargers 53 installed in their own parking spaces 52 and information about users who wish to use chargers 53 installed in parking spaces 52 used by others (see FIG. 8 ). In response to a usage request Q21 sent from a user terminal 21, the server device 1 extracts providers matching the content of the usage request Q21 from the registered information, causes the user terminal 21 to present information about the extracted providers, and performs a reservation setting process to set up a reservation in accordance with the reservation confirmation information from the user terminal 21 (see FIG. 9 ). The server device 1 also performs a settlement process for the user's use of the provider's charger 53 based on the set reservation (see FIG. 12 ). By performing the above-described processes and implementing a charger rental service, the server device 1 can turn ordinary homes into charging spots, thereby resolving the shortage of charging spots for electric vehicles. Furthermore, providers can easily establish a business that allows others to use their chargers 53. This system aligns the interests of users and providers. In particular, the server device 1 matches the information provided by the provider, such as the available date and time, with the area and date and time that the user desires to use the service, thereby eliminating the risk of inconvenience to the provider.

[0120] Furthermore, when the server device 1 causes the user terminal 21 to present information about providers that match the usage request Q21, it presents the information in a manner that prevents the provider's home from being identified (see FIGS. 9, 10, and 11). By preventing the provider's home from being identified when the user selects a provider, it is possible to prevent the disclosure of information about residences where the provider will be absent during the relevant time period. This ensures the security of the provider.

[0121] In addition, the server device 1 executes a process for updating the user's evaluation information in response to receiving the user's evaluation information from the provider terminal 51 (step S261 in FIG. 12 ), and a process for changing the presentation format depending on the user's evaluation information when presenting information about providers matching the usage request Q21 on the user terminal 21 (steps S222 and S223 in FIG. 9 ). For example, while a display such as that shown in FIG. 10 is normally displayed, a display such as that shown in FIG. 11 is displayed for users with high ratings. This allows users with higher ratings to view more detailed information and select a provider. For example, narrowing the area frame 72 makes it easier to select a desired location. Furthermore, changing the content viewed depending on the rating can also promote improved user etiquette. Note that, for example, depending on the evaluation information, in addition to the size of the area frame 72, it is also possible to vary the display format, such as whether or not to display an image, or the level of detail of the charger 53 information.

[0122] Furthermore, the server device 1 receives provision information P21 including the date and time when the charger is available from the provider terminal 51, and executes a process (step S220 in FIG. 9 ) in which the provider related to the received provision information P21 is made a search target for a usage request. When the provider is able to lend a charger 53, the provider transmits provision information P21 including date and time information indicating the time period when the charger is available for lending (from the date and time when the charger is available to start lending to the date and time when the charger is available to end) from the provider terminal 51 to the server device 1. This makes the provider a search target when a user submits a usage request. In other words, the provider only needs to specify the date and time when the provider wishes to provide the charger, which saves time and effort. This is expected to result in more providers offering charging spots.

[0123] Furthermore, in response to receiving evaluation information about the provider from the user terminal 21, the server device 1 executes a process of updating the evaluation information about the provider (step S260 in FIG. 12 ), and a process of including the evaluation information about the provider in the presentation content when causing the user terminal 21 to present information about the provider that matches the use request Q21 (step S223 in FIG. 9 ). For example, displaying the evaluation information about each provider in the provider information 71 helps the user select a provider.

[0124] 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 70 Map image 71 Provider information 72 Area frame

Claims

1. One or more processors, and a storage medium storing a program executed by the one or more processors, comprising: the program includes one or more instructions, the one or more instructions cause the one or more processors to perform a registration process of registering information on one or more providers who provide chargers installed in a parking lot for personal use and information on one or more users who request the use of chargers installed in a parking lot used by others; in response to a usage request transmitted from a certain user terminal, extract a provider that matches the usage request from the registration information, and cause the information on the extracted provider to be presented on the user terminal together with an area display in a state where the provider's home cannot be specified on a map image, and perform a reservation setting process of setting a reservation according to the information from the user terminal; perform a settlement process for the user to charge the vehicle using the charger of the provider based on the set reservation; and execute, a server device.

2. The one or more instructions perform a process of updating the registered evaluation information about the user in response to receiving evaluation information about the user from the provider terminal; perform a process of making the presentation mode different according to the evaluation information of the user when presenting the information about the provider that matches the usage request on the user terminal; and cause the one or more processors to execute the server device according to Claim 1.

3. The one or more instructions cause the one or more processors to perform a process of setting, as a search target for the usage request, the provider related to the received provision information by receiving provision information including available dates and times from the provider terminal; the server device according to Claim 1 or Claim 2.

4. The one or more instructions perform a process of updating the registered evaluation information about the provider in response to receiving evaluation information about the provider from the user terminal; perform a process of including the evaluation information of the provider in the presentation content when presenting the information about the provider that matches the usage request on the user terminal; and cause the one or more processors to execute the server device according to Claim 1 or Claim 2.