Information management system and information management method
The information management system addresses the inefficiency of long-term charging station reservations by enabling concurrent vehicle and charging device use, enhancing utilization and power management.
Patent Information
- Application Number
- JP2022185737
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-11-21
- Publication Date
- 2026-01-21
- Estimated Expiration
- 2042-11-21
AI Technical Summary
Users who reserve a vehicle charging station for extended periods leave it unutilized, preventing others from using it during that time, leading to inefficiencies in charging station usage.
An information management system that allows temporary use authority to be granted to borrowers of an electric vehicle during reserved charging times, enabling the vehicle and charging device to be used concurrently, with options for shared use or power supply/demand adjustment.
Effectively utilizes charging stations by allowing borrowers to use the vehicle during charging, optimizing station usage and balancing power supply and demand.
Smart Images

Figure 0007803253000001 
Figure 0007803253000002 
Figure 0007803253000003
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to information management systems. [Background technology]
[0002] When charging a vehicle's onboard power storage device using a charging station installed in a facility separate from the vehicle's home, the waiting time until charging is completed can be effectively utilized by using services provided in the vicinity of the charging station. For this reason, it is common to make a reservation for use of a charging station with consideration given to the use of such services.
[0003] For example, International Publication No. 2020 / 194456 (Patent Document 1) discloses a technology in which, when a user's candidate destination is recognized, available services at the candidate destination are extracted and candidate destination information including these services is transmitted to the user terminal. This allows the user to select available services to use while waiting at the destination, thereby helping to make effective use of waiting time. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] International Publication No. 2020 / 194456 Summary of the Invention [Problem to be solved by the invention]
[0005] A user who has made a reservation to use a charging station as described above may use another service, or may connect their vehicle to the reserved charging station at an airport or the like and then depart for a trip, leaving the charging station occupied for an extended period of time. As a result, other users cannot use the charging station during the occupied period, and the charging station may not be utilized effectively.
[0006] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide an information management system and an information management method that make effective use of a vehicle and a charging device when the charging device that charges a storage device installed in the vehicle is occupied for a long period of time. [Means for solving the problem]
[0007] According to an aspect of the present disclosure, there is provided an information management system including a server that manages reservation information for reserving the use of a charging device capable of charging an electric vehicle equipped with a power storage device, and the server receives information for temporarily granting use authority to a borrower who will borrow the electric vehicle during the reserved time.
[0008] In this way, when a reservation is made for use of a charging device, information for temporarily granting use authority to the borrower of the electric vehicle is received by the server, so that the borrower can use the electric vehicle during the period of use of the charging device, and the charging device can be used while the borrower is using the electric vehicle, so that the vehicle and charging device can be used effectively when a reservation is made for long-term use of the charging device.
[0009] In one embodiment, the server sets a set period within the reserved usage period of the charging device as a first period during which the borrower can use the electric vehicle.
[0010] In this way, the first period is set within the usage period of the charging device, so the borrower can use the electric vehicle during the first period, and the charging device can be used while the borrower is using the electric vehicle. Therefore, when a reservation for long-term use of the charging device is made, the vehicle and the charging device can be used effectively.
[0011] In one embodiment, the server sets the set period within the usage period of the reserved charging device as either a first period during which the borrower can use the electric vehicle or a second period during which adjustment of power supply and demand is performed.
[0012] In this way, when the first period is set as the set period, the borrower can use the electric vehicle during the first period, and the charging device can be used while the borrower is using the electric vehicle. Furthermore, when the second period is set as the set period, the electric vehicle can be used to adjust power supply and demand, thereby achieving a balance between power supply and demand.
[0013] In one embodiment, the information management system further includes a terminal capable of communicating with the server. When reserving use of the charging device, the terminal transmits to the server a digital key that enables the server to borrow the electric vehicle for a set period that is set within the usage period of the charging device.
[0014] In this way, when the use of the charging device is reserved, a digital key is transmitted from the terminal to the server, thereby allowing the borrower to use the electric vehicle during the period in which the charging device is used.
[0015] In one embodiment, the server acquires from the electric vehicle at least one of information on the usage history of the electric vehicle and the state of the electric vehicle during the period in which the charging device is used, and sets a charging schedule for the power storage device using the acquired information.
[0016] In this way, the charging schedule for the power storage device is set using the usage history of the electric vehicle or information on the state of the electric vehicle during the period in which the charging device is used, so that the state of the power storage device can be set to a predetermined state (for example, a fully charged state) at the end of the period in which the charging device is used.
[0017] According to another aspect of the present disclosure, there is provided an information management system including a terminal that notifies a user of an electric vehicle of reservation information for reserving the use of a charging device capable of charging an electric vehicle equipped with a power storage device, and the terminal transmits information for temporarily granting use authority to the borrower of the electric vehicle during the reserved time.
[0018] In this way, information is transmitted to temporarily grant the borrower of the electric vehicle permission to use the vehicle during the reserved time, allowing the borrower to use the electric vehicle during the period in which the charging device is being used, and the charging device can be used while the borrower is using the electric vehicle, allowing the vehicle and charging device to be used effectively when a reservation is made for long-term use of the charging device.
[0019] An information management method according to yet another aspect of the present disclosure includes the steps of managing reservation information for reserving the use of a charging device capable of charging an electric vehicle equipped with a power storage device, and receiving information for temporarily granting use authority to a borrower who borrows the electric vehicle during the reserved time.
[0020] An information management method according to yet another aspect of the present disclosure includes the steps of notifying a user of an electric vehicle of reservation information for reserving the use of a charging device capable of charging an electric vehicle equipped with a power storage device, and transmitting information for temporarily granting use authority to a borrower who borrows the electric vehicle during the reserved time. [Effects of the Invention]
[0021] According to the present disclosure, it is possible to provide an information management system and an information management method that make effective use of a vehicle and a charging device when the charging device that charges a power storage device mounted on the vehicle is occupied for a long period of time. [Brief explanation of the drawings]
[0022] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of an information management system. [Figure 2] 10 is a flowchart illustrating an example of processing executed by the first terminal. [Figure 3] 10 is a flowchart illustrating an example of a process executed by the management server for registering reservation information. [Figure 4]10 is a flowchart illustrating an example of a process for making a reservation for shared use, which is executed by the management server. [Figure 5] 10 is a flowchart illustrating an example of a process executed by the management server for transmitting a time-limited digital key. [Figure 6] 10 is a flowchart illustrating an example of a process executed by the management server for setting participating vehicles in a DR request. [Figure 7] 10 is a flowchart illustrating an example of a process executed by the management server for setting a charging schedule. [Figure 8] 10 is a flowchart illustrating an example of a process for setting a parking fee, which is executed by the management server. [Figure 9] 10 is a timing chart illustrating an example of the operation of the management server when only shared use is permitted. DETAILED DESCRIPTION OF THE INVENTION
[0023] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and description thereof will not be repeated.
[0024] 1 is a diagram illustrating an example of the configuration of an information management system 1. As shown in FIG. 1, in this embodiment, the information management system 1 includes a vehicle 2, a communication network 6, a base station 7, a management server 100, a first terminal 200, a second terminal 202, and a charging / discharging station 300.
[0025] Vehicle 2 may be, for example, a vehicle powered by an engine, an electric vehicle powered by an electric motor, or a hybrid vehicle equipped with an engine and an electric motor and using at least one of them as a power source. For ease of explanation, Fig. 1 shows only one vehicle 2 as the vehicle managed by management server 100, but the number of vehicles managed by management server 100 is not limited to one, and may be two or more.
[0026] The information management system 1 is configured to acquire and provide predetermined information from a vehicle 2 configured to be able to communicate with the management server 100, and manage the acquired information and the provided information.
[0027] The management server 100 includes a control device 11, a communication device 13, and a storage device 15. The control device 11, the communication device 13, and the storage device 15 are connected to each other via a communication bus 14 so that they can communicate with each other.
[0028] The control device 11 includes a processor 11a that executes programs such as a CPU (Central Processing Unit), a memory 11b (e.g., ROM (Read Only Memory) and RAM (Random Access Memory)), and an input / output port (not shown) for inputting and outputting various signals. The various controls performed by the control device 11 are software processes, that is, programs stored in the memory 11b are read out by the CPU 11a. The various controls performed by the control device 11 can also be realized by a general-purpose computer (not shown) executing programs stored in a storage medium. The various controls performed by the control device 11 are not limited to software processes and may be processed by dedicated hardware (electronic circuits).
[0029] The storage device 15 stores predetermined information related to the vehicle 2 configured to be able to communicate with the management server 100. The predetermined information includes, for example, information related to the control program of the vehicle 2 (described later) and information for identifying the vehicle 2 (hereinafter referred to as a vehicle ID). The vehicle ID is unique information set for each vehicle. The management server 100 can identify the source or destination vehicle by the vehicle ID.
[0030] The communication device 13 realizes two-way communication between the control device 11 and the communication network 6. The management server 100 can communicate with a vehicle 2 equipped with a communication device 30 via a base station 7 provided on the communication network 6 using the communication device 13. Furthermore, the management server 100 can communicate with a first terminal 200 or a second terminal 202 via the base station 7 provided on the communication network 6 using the communication device 13.
[0031] The first terminal 200 is, for example, a portable terminal such as a smartphone, a tablet terminal, or a wearable device owned by a user of the vehicle 2. The first terminal 200 includes a control device 200a having a processor such as a CPU that executes programs and a memory, a communication device 200b configured to be able to communicate with the management server 100 via the base station 7, and a user interface (hereinafter referred to as UI) 200c. The control device 200a, the communication device 200b, and the UI 200c include, for example, a display device that displays predetermined information and a touch panel that accepts user operations. The first terminal 200 stores information about a digital key for unlocking the doors of the vehicle 2 and operating the vehicle 2 in association with the vehicle ID of the vehicle 2. For example, the user performs a predetermined operation on the first terminal 200 near the vehicle 2, whereby the digital key of the first terminal 200 is authenticated in the vehicle 2, and the doors of the vehicle 2 are unlocked and operations such as driving are permitted.
[0032] The management server 100 stores, for example, identification information (for example, a telephone number or a MAC (Media Access Control) address) for identifying the first terminal 200 and the vehicle ID of the vehicle 2 in association with each other.
[0033] The second terminal 202 is a portable terminal such as a smartphone, tablet terminal, or wearable device owned by a user who uses a vehicle rental service such as a car rental or car sharing service. The second terminal 202 is a computer having a processor that executes a program such as a CPU (not shown), a memory, and an input / output interface. The second terminal 202 is configured to be able to communicate with the management server 100 via the base station 7. The second terminal 202 has a configuration similar to that of the first terminal 200. Therefore, detailed description thereof will not be repeated.
[0034] The charging / discharging station 300 is provided, for example, in at least one of a plurality of parking spaces provided in a parking lot of a facility such as an airport, and one charging / discharging station 300 is shown as a representative example in FIG.
[0035] A power line (not shown) that is connected to a power grid is connected to the charging / discharging stand 300. One end of a cable 302 is connected to the charging / discharging stand 300. A connector 304 is connected to the other end of the cable 302. The connector 304 has a structure that allows it to be connected to the inlet 40 of the vehicle 2. FIG. 1 shows the case where the connector 304 is connected to the inlet 40 of the vehicle 2.
[0036] When connector 304 is connected to inlet 40, power can be exchanged between charging / discharging stand 300 and power storage device 20 of vehicle 2. Charging / discharging stand 300 includes, for example, a control device and a communication device (neither of which are shown), and is configured to be able to communicate with management server 100 via base station 7 and communication network 6.
[0037] The information management system 1 further includes an aggregator server 102. The aggregator server 102 is, for example, a server owned by a business operator of a lower-level aggregator (resource aggregator). The lower-level aggregator is a business operator that controls small-scale power generation facilities including the charging and discharging stations 300 via the management server 100 in response to requests for power supply and demand adjustment (hereinafter also referred to as DR (Demand Response) requests) from a higher level (for example, a higher-level aggregator (aggregation coordinator) or a power transmission and distribution business operator (power company)). The aggregator server 102 adjusts supply and demand using the small-scale power generation facilities in the power grid that are the target of supply and demand adjustment in accordance with the DR request, and provides incentives corresponding to the contributions made to the owners of each small-scale power generation facility.
[0038] Next, a specific configuration of the vehicle 2 will be described. The vehicle 2 includes drive wheels and driven wheels. When the drive wheels are rotated by the operation of the drive source, a drive force acts on the vehicle 2, causing the vehicle 2 to travel.
[0039] The vehicle 2 further includes an ECU (Electronic Control Unit) 10, a power storage device 20, a communication device 30 configured by a DCM (Data Communication Module) or the like, an inlet 40, and a navigation system 60.
[0040] The ECU 10 is a computer having a processor 10a that executes programs such as a CPU, a memory 10b, and an input / output interface (not shown). The ECU 10 includes various control programs for controlling various actuators mounted on the vehicle 2. The various control programs include, for example, at least one of a control program for steering control, a drive control, and a braking control. The various control programs may include, for example, a program for executing a driving assistance system having a function related to driving assistance for the vehicle 2.
[0041] The power storage device 20 is a rechargeable DC power supply, and is formed by, for example, a secondary battery such as a nickel-metal hydride battery or a lithium-ion battery containing a solid or liquid electrolyte, or a capacitor.
[0042] The communication device 30 is configured to be able to perform two-way communication with the management server 100 via the communication network 6 and the base station 7 .
[0043] The navigation system 60 includes, for example, a position detection device that identifies the position of the vehicle 2 using a GPS (Global Positioning System) satellite or a wireless LAN (Local Area Network), a database that stores map information and driving history, and a control device using a CPU or the like (none of which are shown). The navigation system 60 identifies a driving route on a map from the current position of the vehicle 2 to a destination, and provides guidance to guide the vehicle 2 to the destination while traveling along the driving route. The navigation system 60 displays map information and guidance information on a touch panel display (not shown), identifies a destination input by the user through operation of the touch panel by the user, and displays multiple options for driving routes to the identified destination. Furthermore, the navigation system 60 stores driving history (driving time, power consumption, driving distance, etc.) during driving in a database or the like.
[0044] A user of vehicle 2 having the above-described configuration may charge power storage device 20 mounted on vehicle 2 using charging / discharging station 300 installed in a facility other than the user's home. In this case, the user can effectively use the waiting time until charging is completed by using a service provided in the vicinity of charging / discharging station 300.
[0045] For example, if charging / discharging stand 300 is installed in a parking lot at an airport or the like, a user can park vehicle 2 in the parking lot, connect to charging / discharging stand 300, and then use the facilities of the airport to effectively utilize the waiting time until charging of power storage device 20 is completed. Alternatively, a user can park vehicle 2 in the parking lot, connect to charging / discharging stand 300, travel by plane from the airport, and complete charging of power storage device 20 by the time they return to the airport, thereby avoiding the waiting time for charging. For this reason, reservations for use of charging / discharging stand 300 are made in consideration of the use of these services.
[0046] If a user who has made a reservation to use such charging / discharging station 300 uses another service, or if the user connects vehicle 2 to the reserved charging / discharging station 300 at an airport or the like and then departs for a trip, charging / discharging station 300 will be occupied for an extended period of time. Therefore, there is a possibility that other users will not be able to use charging / discharging station 300 during the occupied period.
[0047] Therefore, in this embodiment, the information management system 1 including the management server 100 and the first terminal 200 has the following features: The first terminal 200 transmits information to the management server 100 (and ultimately to the second terminal 202) for temporarily granting use authority to the borrower who will borrow the vehicle 2 during the reserved time. The management server 100 receives information from the first terminal 200 for temporarily granting use authority to the borrower who will borrow the vehicle 2 during the reserved time.
[0048] In this way, the borrower of vehicle 2 can use vehicle 2 during the usage period of charging / discharging station 300, and charging / discharging station 300 can be used while the borrower is using vehicle 2, so vehicle 2 and charging / discharging station 300 can be used effectively when a reservation is made for long-term use of the charging device.
[0049] An example of processing executed by the first terminal 200 (specifically, the control device 200a) will be described below with reference to Fig. 2. Fig. 2 is a flowchart showing an example of processing executed by the first terminal 200. The processing shown in this flowchart is repeatedly executed by the control device 200a of the first terminal 200 at predetermined control intervals.
[0050] In step (hereinafter, step will be abbreviated as S) 100, the first terminal 200 determines whether or not to start reservation processing. The reservation processing is processing in which the user of the vehicle 2 makes a reservation for use of the charging / discharging station 300 using the first terminal 200. For example, the first terminal 200 determines to start reservation processing when an operation to start reservation processing is received via the UI 200c while an app for enabling the reservation processing is running. If it is determined to start reservation processing (YES in S100), the processing proceeds to S102.
[0051] In S102, the first terminal 200 determines whether or not it has accepted the planned date and time when use of the charging / discharging stand 300 will begin (hereinafter referred to as the start date and time) and the planned date and time when use of the charging / discharging stand 300 will end (hereinafter referred to as the end date and time). For example, when the reservation process starts, the first terminal 200 displays on the UI 200c a display that allows the start date and time and the end date and time to be input. The first terminal 200 determines whether or not the start date and time and the end date and time have been input via the UI 200c. For example, when the user inputs the start date and time and the end date and time using the touch panel of the UI 200c, the first terminal 200 determines that it has accepted the start date and time and the end date and time. If it is determined that the start date and time and the end date and time have been accepted (YES in S102), the process proceeds to S104.
[0052] In S104, the first terminal 200 determines whether or not the vehicle 2 parked in the parking space corresponding to the charging / discharging station 300 is permitted to be used as a car share or rental car (hereinafter referred to as shared use) during the usage period of the charging / discharging station 300. For example, the first terminal 200 displays an item that allows the user to select whether or not to permit shared use, in addition to input items for the start date and time and the end date and time, on a screen that is displayed at the start of the reservation process. The first terminal 200 determines whether or not shared use is permitted using the selection state of the item. If it is determined that shared use is permitted (YES in S104), the process proceeds to S106.
[0053] In S106, the first terminal 200 issues a time-limited digital key. The digital key functions, for example, through an application running on the first terminal 200. When authentication is performed using the digital key during communication between the first terminal 200 and the vehicle 2, the first terminal 200 is permitted to lock and unlock the doors of the vehicle 2 and operate the vehicle 2 (hereinafter, simply referred to as "use"). The time-limited digital key has some of the authority to use the vehicle 2 that the above-mentioned digital key has. Specifically, the function of the time-limited digital key is limited to a predetermined period as a digital key. The first terminal 200 generates a time-limited digital key that permits use of the vehicle 2 for a usage period, for example, from a start date and time to an end date and time. Then, the process proceeds to S108. Note that the process also proceeds to S108 if it is determined that shared use is not permitted (NO in S104).
[0054] In S108, the first terminal 200 determines whether or not use of the vehicle 2 as a small-scale power source facility used in a VPP (Virtual Power Plant) during the usage period of the charging / discharging station 300 (hereinafter referred to as VPP use) is permitted. For example, the first terminal 200 displays an item that allows the user to select whether or not to permit VPP use on a screen displayed at the start of the reservation process, in addition to input items for the start date and time and end date and time. The first terminal 200 determines whether or not VPP use is permitted based on the selection state of the item. If it is determined that VPP use is permitted (YES in S108), the process proceeds to S110.
[0055] In S110, the first terminal 200 generates information indicating that VPP use is permitted (hereinafter referred to as VPP permission information). Thereafter, the process proceeds to S112.
[0056] In S112, the first terminal 200 transmits reservation information to the management server 100. The reservation information includes input information consisting of a start date and time and an end date and time. Furthermore, if shared use is permitted, the reservation information further includes information about a time-limited digital key. If VPP use is permitted, the reservation information further includes VPP permission information. Thereafter, the process proceeds to S114. Note that the process also proceeds to S114 if it is determined that VPP is not permitted (NO in S108).
[0057] In S114, first terminal 200 determines whether to receive reservation completion information from management server 100. The reservation completion information includes information indicating that registration of the reservation has been completed in management server 100. If it is determined that reservation completion information will be received from management server 100 (YES in S114), the process proceeds to S116.
[0058] In S116, first terminal 200 notifies the user that the reservation has been completed. Specifically, first terminal 200 may display information indicating the completion of the reservation using the display device of UI 200c, or may notify the user of the completion of the reservation using a voice or notification sound from the speaker of UI 200c. This process then ends. If it is determined that the reservation completion information has not been received (NO in S114), the process proceeds to S118.
[0059] In S118, first terminal 200 determines whether or not to receive reservation impossible information from management server 100. The reservation impossible information includes information indicating that the reservation was not accepted. If it is determined that reservation impossible information will be received from management server 100 (YES in S118), the process proceeds to S120.
[0060] In S120, first terminal 200 notifies the user that the reservation is not possible. Specifically, first terminal 200 may display information indicating that the reservation is not possible using the display device of UI 200c, or may notify the user of the information indicating that the reservation is not possible using voice or a notification sound from the speaker of UI 200c. This process then ends. If it is determined that the reservation is not possible information has not been received (NO in S118), the process returns to S114. If it is determined that the reservation process is not to be started (NO in S100), the process ends. If it is determined that the start date and time and the end date and time have not been accepted (NO in S102), the process returns to S102.
[0061] Next, an example of a process for registering reservation information executed by the management server 100 (specifically, the control device 11) will be described with reference to Fig. 3. Fig. 3 is a flowchart showing an example of a process for registering reservation information executed by the management server 100. The process shown in this flowchart is repeatedly executed by the control device 11 of the management server 100 at predetermined control intervals.
[0062] In S200, management server 100 determines whether to receive reservation information from first terminal 200. The reservation information is as described above, and therefore detailed description thereof will not be repeated. If it is determined that reservation information will be received from first terminal 200 (YES in S200), the process proceeds to S202.
[0063] In S202, management server 100 determines whether a reservation is possible using the input information included in the reservation information. Management server 100 determines that a reservation is possible if there are available reservations during the scheduled usage period (parking usage period) from the start date and time to the end date and time included in the input information (i.e., there are no other usage reservations for the charging / discharging station 300). Note that, if there are multiple charging / discharging stations 300, management server 100 may determine that a reservation is possible if there are available reservations during the scheduled usage period at at least one of the charging / discharging stations 300. If it is determined that a reservation is possible (YES in S202), the process proceeds to S204.
[0064] In S204, management server 100 registers the reservation information in storage device 15. Thereafter, the process proceeds to S208. If it is determined that reservation is not possible (NO in S202), the process proceeds to S206.
[0065] In S206, management server 100 transmits reservation impossible information to first terminal 200. The reservation impossible information is as described above, and therefore detailed description thereof will not be repeated. Thereafter, the process ends.
[0066] In S208, management server 100 transmits reservation completion information to first terminal 200. The reservation completion information is as described above, and therefore detailed description thereof will not be repeated. Thereafter, the process proceeds to S210.
[0067] In S210, the management server 100 determines whether or not shared use of the vehicle 2 is permitted. If the received reservation information includes a time-limited digital key, the management server 100 determines that shared use of the vehicle 2 is permitted. If it is determined that shared use of the vehicle 2 is permitted (YES in S210), the process proceeds to S212.
[0068] In S212, the management server 100 determines whether or not vehicle 2 is permitted to use the VPP. If the received reservation information includes VPP permission information, the management server 100 determines that vehicle 2 is permitted to use the VPP. If it is determined that vehicle 2 is permitted to use the VPP (YES in S212), the process proceeds to S216. If it is determined that vehicle 2 is not permitted to use the VPP for sharing (NO in S210), the process proceeds to S214.
[0069] In S214, management server 100 determines whether or not VPP use is permitted for vehicle 2. The method for determining whether or not VPP use is permitted is the same as the method for determining in the processing of S212, and therefore detailed description thereof will not be repeated. If it is determined that VPP use is permitted (YES in S214), processing proceeds to S220.
[0070] In S216, the management server 100 determines whether shared use of the vehicle 2 is prioritized over VPP use. The management server 100 determines whether shared use is prioritized over VPP use using the status, specifications, etc. of the vehicle 2.
[0071] For example, if the full charge capacity of the power storage device 20 mounted on the vehicle 2 is determined to be greater than a threshold value and therefore suitable for VPP use, the management server 100 may determine that VPP use is prioritized over shared use, and if the full charge capacity of the power storage device 20 is equal to or less than the threshold value, the management server 100 may determine that shared use is prioritized over VPP use. Note that the management server 100 may obtain the full charge capacity of the power storage device 20 via the first terminal 200, or may obtain the full charge capacity of the power storage device 20 by communicating with the vehicle 2.
[0072] Alternatively, the management server 100 may determine that VPP usage is prioritized over shared usage when the distance from the pre-registered user's home (or the location of the vehicle 2 or the first terminal 200) to the charging / discharging station 300 is greater than a threshold value, since the SOC will be consumed upon arrival at the charging / discharging station 300. Alternatively, the management server 100 may determine that shared usage is prioritized over VPP usage when the distance is equal to or less than the threshold value. The management server 100 may acquire information about the specifications and status of the vehicle 2 from the first terminal 200 or the vehicle 2, or the reservation information may include such information. Alternatively, the management server 100 may determine that VPP usage is prioritized over shared usage when the usage period of the charging / discharging station 300 is shorter than the lower limit of the period during which shared usage is available, and may determine that shared usage is prioritized over VPP usage when the usage period is equal to or greater than the lower limit. If it is determined that shared usage is prioritized over VPP usage (YES in S216), the process proceeds to S218. If it is determined in S212 that VPP use is not permitted (NO in S212), the process proceeds to S218.
[0073] In S218, management server 100 registers vehicle 2 as a vehicle eligible for rental. Management server 100 sets a portion of the usage period of charging / discharging station 300 between the reserved start date and time and the reserved end date and time as a sharing period for vehicle 2. The sharing period is set within the usage period, excluding at least the charging guaranteed period set immediately before the end date and time. The charging guaranteed period may include a predetermined period during which the power storage device 20 of vehicle 2 can be reliably charged to a fully charged state. The sharing period may also be set to a period excluding the charging guaranteed period for sharing use set immediately after the start date and time. The processing then ends. If it is determined that sharing use does not have priority over VPP use (NO in S216), the processing proceeds to S220.
[0074] In S220, the management server 100 registers the vehicle as a VPP eligible vehicle. In the process described later with reference to FIG. 6, the management server 100 registers the vehicle 2 as a selection candidate (i.e., a VPP eligible vehicle) for participating in a DR request in response to a DR request from the aggregator server 102. The process then ends. Note that if it is determined that reservation information has not been received (NO in S200), the process then ends. Furthermore, if neither shared use nor VPP use is permitted (NO in S210 and NO in S214), the process then ends.
[0075] Next, a process for reserving shared use, which is executed by the management server 100 (specifically, the control device 11), will be described with reference to Fig. 4. Fig. 4 is a flowchart showing an example of a process for reserving shared use, which is executed by the management server 100. The process shown in this flowchart is repeatedly executed by the control device 11 of the management server 100 at predetermined control intervals.
[0076] In S300, the management server 100 determines whether or not request information for reserving a shared use has been received from the second terminal 202. The request information includes a rental start date and time when the rental of the vehicle 2 will begin and a rental end date and time. The request information may also include information such as the destination when the vehicle 2 is rented. A user of the shared use (hereinafter referred to as the borrower) inputs information including the rental start date and time and the rental end date and time while an app for performing the shared use is running on the second terminal 202. The second terminal 202 generates request information using the input information and transmits the generated request information to the management server 100. If it is determined that request information has been received from the second terminal 202 (YES in S300), the process proceeds to S302.
[0077] In S302, the management server 100 executes a matching process. The matching process includes a process of selecting a vehicle that satisfies the conditions included in the request information from multiple rental vehicles. The management server 100 selects a vehicle that can be rented from the multiple rental vehicles during at least the desired rental period from the rental start date and time to the rental end date and time. When there are multiple selection candidates, the management server 100 selects one vehicle according to a predetermined priority order. The priority order may be set, for example, so that vehicles that use the charging / discharging station 300 have a higher selection priority. The process then proceeds to S304.
[0078] In S304, management server 100 transmits the matching result (i.e., the vehicle selected by the matching process) to second terminal 202. Thereafter, the process proceeds to S306.
[0079] In S306, the management server 100 determines whether to receive confirmation information from the second terminal 202. The confirmation information includes information indicating that the vehicle selected based on the matching result has been confirmed as the rental vehicle by the borrower. If it is determined that the confirmation information has been received (YES in S306), the process proceeds to S310. If it is determined that the confirmation information has not been received (NO in S306), the process proceeds to S308.
[0080] In S308, the management server 100 determines whether or not there is a re-matching request to request re-execution of the matching process. The management server 100 determines that there is a re-matching request when it receives a re-matching request from the second terminal 202. If it is determined that there is a re-matching request (YES in S308), the process returns to S302. If it is determined that there is no re-matching request (NO in S308), the process returns to S306.
[0081] In S310, management server 100 registers reservation information for shared use. Management server 100 stores, for example, information about the selected vehicle and information about the desired rental period for the selected vehicle as reservation information in storage device 15. Thereafter, the process proceeds to S312.
[0082] In S312, management server 100 transmits a reservation completion notification to second terminal 202. Thereafter, the process ends. If it is determined that the request information has not been received (NO in S300), this process ends.
[0083] Next, an example of a process for transmitting a time-limited digital key executed by the management server 100 (specifically, the control device 11) will be described with reference to Fig. 5. Fig. 5 is a flowchart showing an example of a process for transmitting a time-limited digital key executed by the management server 100. The process shown in this flowchart is repeatedly executed by the control device 11 of the management server 100 at predetermined control intervals.
[0084] In S400, management server 100 acquires reservation information for shared use. The reservation information for shared use has been described above, and detailed description thereof will not be repeated. If the reservation information is stored in storage device 15, management server 100 acquires the reservation information by reading it from storage device 15. Thereafter, processing proceeds to S402.
[0085] In S402, management server 100 determines whether the conditions for transmitting the time-limited digital key are met. The conditions for transmitting the time-limited digital key may include, for example, a condition that a predetermined period of time has passed since the rental start date and time of the selected vehicle, or a condition that the distance between the location of second terminal 202 and the selected vehicle is less than or equal to a threshold, or a condition that the desired rental period for the selected vehicle is still in progress. If it is determined that the conditions for transmitting the time-limited digital key are met (YES in S402), the process proceeds to S404.
[0086] In S404, the management server 100 transmits the time-limited digital key to the second terminal 202. If it is determined that the reservation information has not been acquired (NO in S400), this process is terminated. Furthermore, if it is determined that the conditions for transmitting the time-limited digital key are not met (NO in S402), the process returns to S402.
[0087] Next, an example of a process for setting participating vehicles in a DR request, which is executed by the management server 100 (specifically, the control device 11), will be described with reference to Fig. 6. Fig. 6 is a flowchart showing an example of a process for setting participating vehicles in a DR request, which is executed by the management server 100. The process shown in this flowchart is repeatedly executed by the control device 11 of the management server 100 at predetermined control intervals.
[0088] In S500, the management server 100 determines whether or not there is a DR request. For example, when the management server 100 receives information indicating a DR request from the aggregator server 102, the management server 100 determines that there is a DR request.
[0089] The aggregator server 102 transmits a DR request to small-scale power generation facilities including the management server 100, for example, in accordance with the difference between the amount of power that can be supplied in the power grid that is the target of supply and demand adjustment and the predicted value of the amount of power demand in the power grid. For example, when a period is predicted in which the amount of power that can be supplied in the power grid will be greater than the amount of power demand, the aggregator server 102 issues an upward DR request to increase the amount of demand during that period. For example, when a period is predicted in which the amount of power that can be supplied in the power grid will be less than the amount of power demand, the aggregator server 102 issues a downward DR request to decrease the amount of demand during that period. The aggregator server 102 transmits the DR request amount along with the upward or downward DR request to each small-scale power generation facility. If it is determined that a DR request exists (YES in S500), the process proceeds to S502.
[0090] In S502, the management server 100 sets participating vehicles. The management server 100 sets participating vehicles from among multiple VPP eligible vehicles that are connected to the charging / discharging station 300 and are permitted to use the VPP. For example, if the DR request is an upward DR request, the management server 100 may set as participating vehicles those vehicles with the lowest SOC of the installed power storage device among the multiple VPP eligible vehicles. Alternatively, if the DR request is a downward DR request, the management server 100 may set as participating vehicles those vehicles with the highest SOC of the installed power storage device among the multiple VPP eligible vehicles. Alternatively, the management server 100 may set all VPP eligible vehicles as participating vehicles. Then, the process proceeds to S504.
[0091] In S504, management server 100 sets an allocation of charge / discharge amounts for each participating vehicle. Management server 100 sets the allocation of charge / discharge amounts based on, for example, the current SOC and full charge capacity of each participating vehicle. Thereafter, the process proceeds to S506.
[0092] In S506, management server 100 sets a charge / discharge schedule for each participating vehicle. The charge / discharge schedule includes, for example, information on the time periods for charging / discharging and the charge / discharge power required to implement the charge / discharge amount assigned to each participating vehicle. The charge / discharge schedule is set for each participating vehicle.
[0093] In S508, the management server 100 transmits the set charge / discharge schedule to the corresponding participating vehicles or the charging / discharge stations to which the participating vehicles are connected. Each participating vehicle controls the charge / discharge of the power storage device in accordance with the received charge / discharge schedule. Thereafter, the process ends. Note that if it is determined that there is no DR request (NO in S500), this process ends.
[0094] Next, an example of a process for setting a charging schedule executed by the management server 100 (specifically, the control device 11) will be described with reference to Fig. 7. Fig. 7 is a flowchart showing an example of a process for setting a charging schedule executed by the management server 100. The process shown in this flowchart is repeatedly executed by the control device 11 of the management server 100 at predetermined control intervals.
[0095] In S600, management server 100 determines whether the shared use has ended. For example, management server 100 may determine that the shared use has ended when it receives information from second terminal 202 that the shared use has ended and the vehicle that is the subject of the shared use is connected to charging / discharging station 300. For example, the borrower parks the borrowed vehicle in the parking space where it was parked at the start of the shared use, connects connector 304 of charging / discharging station 300 to inlet 40, and then performs an operation on second terminal 202 to end the shared use. At this time, second terminal 202 transmits information to management server 100 that the shared use has ended in response to the operation. Meanwhile, charging / discharging station 300 obtains information (vehicle ID) of connected vehicle 2 when connector 304 is connected to inlet 40 of vehicle 2, and transmits information indicating that vehicle 2 is connected to charging / discharging station 300 and the driving history of vehicle 2 to management server 100. The information may be transmitted from the vehicle 2 to the management server 100, or may be transmitted to the management server 100 via the second terminal 202.
[0096] In S602, the management server 100 sets a fee for shared use (hereinafter referred to as a rental fee). The management server 100 may set the rental fee using, for example, the driving history of the vehicle 2. The management server 100 may set the rental fee using, for example, the distance driven during the shared use period and the rental fee per unit distance. Alternatively, the management server 100 may set the rental fee using, for example, the driving time during the shared use period and the rental fee per unit time. Alternatively, the management server 100 may set the rental fee using, for example, the shared use period and the rental fee per unit time. Thereafter, the process proceeds to S604.
[0097] In S604, management server 100 executes the settlement process. For example, if the borrower has registered a payment method such as a credit card or other electronic payment method, management server 100 executes the settlement process using the registered payment method. Then, the process proceeds to S606.
[0098] In S606, management server 100 acquires the SOC of the vehicle that is the target of shared use. Management server 100 acquires the SOC of the vehicle using the driving history of vehicle 2 acquired via charging / discharging station 300. Thereafter, the process proceeds to S608.
[0099] In S608, management server 100 sets a charging schedule for the vehicle that is the target of shared use. Management server 100 sets the date and time when charging should start (hereinafter referred to as the charging start date and time) so that the power storage device installed in the vehicle that is the target of shared use will be in a predetermined charged state (for example, fully charged) at the end date and time. For example, if the vehicle is scheduled to be used as a reserved VPP for the next shared use, management server 100 sets the charging start date and time so that the vehicle will be in a predetermined charged state at the start date and time of shared use or the start date and time of use as a VPP.
[0100] In S610, management server 100 determines whether the current date and time has passed the charging start date and time. If it is determined that the current date and time has passed the charging start date and time (YES in S610), the process proceeds to S612.
[0101] In S612, management server 100 outputs a command to execute charge control to charging / discharging station 300 to which the vehicle eligible for shared use is connected. Charging / discharging station 300 receives the command to execute charge control from management server 100 and charges the power storage device mounted on the connected vehicle. Management server 100 may also output a command to execute charge control to the vehicle eligible for shared use. The process then ends. If it is determined that the shared use has not ended (NO in S600), the process ends. If it is determined that the current date and time has not passed the charging start date and time (NO in S610), the process returns to S610.
[0102] Next, an example of a process for setting a parking fee executed by the management server 100 (specifically, the control device 11) will be described with reference to Fig. 8. Fig. 8 is a flowchart showing an example of a process for setting a parking fee executed by the management server 100. The process shown in this flowchart is repeatedly executed by the control device 11 of the management server 100 at predetermined control intervals.
[0103] In S700, management server 100 determines whether the parking use has ended. Management server 100 may determine that the parking use has ended, for example, when it receives information from first terminal 200 that the parking use has ended and the connection between the vehicle that is the subject of the parking use and charging / discharging station 300 is released. The owner of the vehicle, for example, performs an operation to release the parking use on first terminal 200. At this time, first terminal 200 transmits information to management server 100 that the parking use has ended in response to the operation. Meanwhile, when connector 304 is removed from inlet 40 of the vehicle, charging / discharging station 300 transmits information to management server 100 indicating that the connection between the vehicle that is the subject of the parking use and charging / discharging station 300 has been released. Note that this information may be transmitted from vehicle 2 to management server 100, or may be transmitted to management server 100 via first terminal 200. If it is determined that the parking use has ended (YES in S700), the process proceeds to S702.
[0104] In S702, management server 100 identifies the vehicle that will end its parking use. Management server 100 may identify the vehicle that will end its parking use, for example, by acquiring a vehicle ID from first terminal 200. Thereafter, the process proceeds to S704.
[0105] In S704, management server 100 acquires the usage history of the shared use. Management server 100 reads the shared use period, mileage, driving time, rental fee, etc. when the identified vehicle was used for shared use from storage device 15 and acquires this information as the usage history of the shared use. Management server 100 may acquire this information from the identified vehicle, or may acquire it from the vehicle via first terminal 200.
[0106] At S706, management server 100 acquires the usage history of VPP usage. Management server 100 reads from storage device 15 information such as the charge / discharge period, charge amount, and discharge amount when the identified vehicle used the VPP, and acquires this information as the usage history of VPP usage. Management server 100 may acquire this information from the identified vehicle, or may acquire it from the vehicle via first terminal 200.
[0107] In S708, if the vehicle that has finished parking use was set as a rental vehicle, the management server 100 cancels the setting as a rental vehicle, and if it was set as a VPP eligible vehicle, it cancels the setting as a VPP eligible vehicle. By canceling the setting as a rental vehicle, for example, the vehicle is excluded from selection candidates during matching processing. Furthermore, by canceling the setting as a VPP eligible vehicle, the vehicle is excluded from selection candidates when setting participating vehicles in response to a DR request. Then, processing proceeds to S710.
[0108] At S710, management server 100 sets the parking fee. Management server 100 sets the parking fee using, for example, the usage period, the usage history of shared use during the usage period, the usage history of VPP use during the usage period, and the amount of charge due to charging performed before the end of usage. Management server 100 sets the base parking fee based on, for example, the usage period. Management server 100 sets the reduced fee using the usage period of shared use and mileage, etc. Management server 100 sets the reduced fee using the usage period of VPP use, the amount of charge or discharge, the contribution level, etc. Management server 100 sets the increased fee using the amount of charge performed before the end of usage. Management server 100 sets the final parking fee based on the base parking fee, the reduced fee, and the increased fee.
[0109] In S712, management server 100 notifies the set parking fee to first terminal 200 of the user who owns the vehicle whose use has been terminated.
[0110] In S714, management server 100 executes the settlement process. If the parking lot user has registered a payment method such as credit card payment or other electronic payment method in advance, management server 100 executes the settlement process using the registered payment method. The process then ends. Note that if it is determined that parking usage has not ended (NO in S700), this process ends.
[0111] An example of the operation of the management server 100 based on the above-described structure and flowchart will now be described.
[0112] <When only shared use is permitted> Fig. 9 is a timing chart for explaining an example of the operation of the management server 100 when only shared use is permitted. Fig. 9 shows the parking use period, sharing period, charging guaranteed period, shared use period, and charging period. These periods are set by the operations of the management server 100, the first terminal 200, and the second terminal 202, as described below.
[0113] That is, when the user of vehicle 2 operates the first terminal 200 and launches an app for reserving a parking space, and the reservation process begins (YES in S100), the start date and time and the end date and time are accepted (S102). At this time, it is assumed that permission for only shared use is selected. When the start date and time and the end date and time are accepted as input information (YES in S102), and if shared use is permitted (YES in S104), a time-limited digital key is issued (S106). On the other hand, because VPP use is not permitted (NO in S108), VPP permission information is not generated, and reservation information including the input information and the time-limited digital key is sent to the management server 100 (S112).
[0114] In management server 100, the reservation information is received (YES in S200), and if it is determined that reservation is possible (YES in S202), the reservation information is registered (S204).
[0115] At this time, as shown in (A) of Figure 9, a reservation is made for a planned period of use of the parking lot, with time t(0) as the start date and time and time t(6) as the end date and time. Once the reservation information is registered, reservation completion information is sent to the first terminal 200 (S208).
[0116] When the reservation completion information is received at first terminal 200 (YES at S114), the UI 200c is notified that the reservation has been completed (S116).
[0117] In the management server 100, after the reservation completion information is transmitted, if shared use of the vehicle 2 is permitted (YES in S210) but VPP use is not permitted (NO in S212), the vehicle 2 is registered as a rental vehicle (S218). At this time, as shown in FIG. 9(B), the sharing period of the registered rental vehicle is set within the parking lot usage period. More specifically, the sharing period is set to a period beginning at time t(1), a predetermined time after the start date and time t(0) of the parking usage period, and ending at time t(4), which is the length of the charging assurance period prior to the end date and time t(6) of the parking usage period.
[0118] Therefore, when the borrower transmits request information to reserve a shared use using the second terminal 202 and the request information is received by the management server 100 (YES in S300), a matching process is executed to extract selection candidates from multiple rental vehicles (S302). The matching results obtained by the matching process are transmitted to the second terminal 202 (S304).
[0119] Then, when confirmation information indicating that the shared use has been confirmed using the selection candidates included in the matching result is received from the second terminal 202 (YES in S306), reservation information for the shared use is registered and a reservation completion notification is sent to the second terminal 202.
[0120] For example, as shown in (C) of Figure 9, assume that the borrower's desired shared usage period is a period in which the usage start date and time is time t(2), which is later than time t(1), and the usage end date and time is time t(3), which is earlier than time t(4).
[0121] When the management server 100 acquires reservation information for shared use (YES in S400), it determines whether the conditions for transmitting a time-limited digital key are met (S402). If the transmission conditions are met, for example, because the period from the current date and time to the borrowing start date and time is shorter than a threshold value (YES in S402), the time-limited digital key is transmitted to the second terminal 202 (S404). By transmitting the time-limited digital key to the second terminal 202, the borrower, who is the owner of the second terminal 202, can use the vehicle 2 parked in the parking lot.
[0122] After the borrower uses vehicle 2, he or she parks the vehicle in the parking lot at time t(3), connects connector 304 to inlet 40, and when the shared use ends (YES in S600), the rental fee for the shared use is set (S602) and the settlement process is executed (S604).
[0123] At this time, the SOC of the power storage device 20 mounted on the vehicle 2 is acquired (S606), and a charging schedule is set (S608). That is, the management server 100 calculates the amount of power corresponding to the difference between the SOC corresponding to a predetermined state of charge of the power storage device 20 mounted on the vehicle 2 and the current SOC. Then, the charging start date and time t(5) is set so that charging of the calculated amount of power will be completed at time t(6).
[0124] When the time reaches t(5) (YES in S610), a command to execute charge control is output (S612), and the power storage device 20 mounted on the vehicle 2 is charged. When the time reaches t(6), the power storage device mounted on the vehicle 2 reaches a predetermined charge state. At this time, if the owner of the vehicle 2 performs an operation to end the parking use (YES in S700), the vehicle 2 whose parking use is to be ended is specified in the management server 100 (S702). Then, the usage history of the shared use of the specified vehicle 2 is acquired (S704), and the usage history of the VPP (no VPP use) is acquired (S706).
[0125] Then, the setting of the vehicle to be lent is canceled (S708), and the parking fee is set (S710). Thereafter, the set parking fee is notified to the first terminal 200 (S712), and the settlement process is executed (S714).
[0126] <When VPP use is permitted> When only VPP use is permitted, the VPP available period is set instead of the shareable period in FIG. 9, and the VPP use period is set instead of the share use period. The VPP available period and the VPP use period are set as follows. For other periods, since they are set as described using FIG. 9, detailed description thereof will not be repeated.
[0127] For example, when a user reserves the use of a parking lot and share use is not permitted (NO in S104), and only VPP use is permitted (YES in S108), VPP use permission information is generated without issuing a time-limited digital key (S110). Therefore, in addition to the input information, the VPP use permission information is transmitted to the management server 100 as reservation information (S112).
[0128] In this case, the reservation information is received (YES in S200), reservations are possible (YES in S202), and the reservation information is registered (S204), and reservation completion information is transmitted (S208). Then, since sharing is not permitted (NO in S210) and VPP use is permitted (YES in S214), the vehicle is registered as a VPP eligible vehicle (S220). For VPP eligible vehicles, a VPP available period is set instead of the sharing available period shown in FIG. 9B.
[0129] Therefore, when a DR request is made (YES in S500), when the participating vehicles are set (S502), if the DR request period is included in the VPP possible period, vehicle 2 is extracted as a selection candidate. An allocation of charge / discharge power amount is set for each participating vehicle (S504), and a charge / discharge schedule for achieving the allocated charge / discharge power amount is set (S506). Then, the charge schedule is transmitted to charging / discharging stand 300 (S508). As a result, charge / discharge control is performed using power storage device 20 mounted on vehicle 2 during the DR request period, which contributes to adjusting the supply and demand of electricity.
[0130] If both shared use and VPP use are permitted (YES in S210 and YES in S212), it is determined whether shared use is given priority (S216).
[0131] For example, if the full charge capacity of the power storage device 20 mounted on the vehicle 2 is greater than the threshold value, it is determined that VPP use is prioritized (NO in S216), and the vehicle is registered as a VPP eligible vehicle (S220). On the other hand, if the full charge capacity of the power storage device 20 mounted on the vehicle 2 is equal to or less than the threshold value, it is determined that shared use is prioritized (YES in S216), and the vehicle is registered as a rental eligible vehicle (S218).
[0132] As described above, the information management system 1 according to the present embodiment allows a user other than the user who owns the vehicle 2 to use the vehicle 2 during the usage period of the charging / discharging station 300, and also allows the charging / discharging station 300 to be used while the user is using the vehicle 2, thereby enabling effective use of the vehicle 2 and the charging / discharging station 300 when a reservation is made for long-term use of the charging / discharging station 300. Therefore, it is possible to provide an information management system and information management method that make effective use of the vehicle and the charging device when the charging device that charges the power storage device mounted on the vehicle is occupied for a long period of time.
[0133] Furthermore, a set period within the reserved usage period of the charging device is set as the period during which the borrower can use the vehicle 2, so the borrower can use the vehicle 2 during that period, and the charging / discharging stand 300 can be used while the borrower is using the vehicle 2. Therefore, when a reservation is made for long-term use of the charging / discharging stand 300, the vehicle 2 and the charging / discharging stand 300 can be used effectively.
[0134] Furthermore, if a period during the usage period during which the borrower can use the vehicle 2 is set, the borrower can be allowed to use the vehicle 2 during that period, and the charging and discharging station can be used while the borrower is using the vehicle 2. Furthermore, if a period during the usage period during which adjustments to power supply and demand are made is set, the vehicle 2 can be used to adjust power supply and demand, thereby achieving a balance in power supply and demand on the power grid.
[0135] Furthermore, the borrower can be given temporary use authority using a time-limited digital key, so that the borrower can use the vehicle 2 during the period of use of the charging / discharging station 300.
[0136] Furthermore, by setting a charge ensuring period before the end of the use period, it is possible to bring the power storage device 20 of the vehicle 2 into a predetermined charge state (fully charged state) at the end of the use period.
[0137] Modifications will be described below. In the above-described embodiment, an example was described in which processing is performed by one processor and one memory in the first terminal 200, but the processing of the flowchart shown in Figure 2 may also be performed by one or more processors reading and executing programs stored in one or more memories.
[0138] In the above-described embodiment, an example has been described in which processing is executed by one processor 11a and one memory 11b in the control device 11 of the management server 100, but the processing of the flowcharts shown in Figures 3 to 8 may also be executed by one or more processors reading and executing programs stored in one or more memories.
[0139] Furthermore, in the above-described embodiment, a case where vehicle 2 is set as either a rental vehicle or a VPP eligible vehicle during the parking lot usage period has been described as an example. However, during the usage period, a vehicle may be set as a rental vehicle and then as a VPP eligible vehicle, or may be set as a VPP eligible vehicle and then as a rental vehicle. For example, a vehicle may be set as a rental vehicle and then as a VPP eligible vehicle if the SOC of power storage device 20 falls within a predetermined first range suitable for VPP usage after shared use. Alternatively, a vehicle may be set as a VPP eligible vehicle and then as a rental vehicle if the SOC of power storage device 20 falls within a predetermined second range (different from the first range) suitable for shared use after VPP use.
[0140] The above-described modifications may be implemented in whole or in part in appropriate combination. The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]
[0141] 1 information management system, 2 vehicle, 6 communication network, 7 base station, 10 ECU, 10a, 11a processor, 10b, 11b memory, 11, 200a control device, 13, 30, 200b communication device, 14 communication bus, 15 storage device, 20 power storage device, 40 inlet, 60 navigation system, 100 management server, 102 aggregator server, 200 first terminal, 200c UI, 202 second terminal, 300 charging / discharging stand, 302 cable, 304 connector.
Claims
1. a server that manages reservation information for reserving the use of a charging device that can charge an electric vehicle equipped with a power storage device; The server receiving information for temporarily granting a right of use to a borrower who will borrow the electric vehicle during the reserved time; An information management system that uses the state of charge of the storage device or the distance from the location of the electric vehicle to the charging device to determine whether to prioritize VPP use as a small-scale power source facility or shared use as a car share or rental car over the other.
2. The information management system according to claim 1 , wherein the server sets a set period that is set within a reserved usage period of the charging device as a first period during which the borrower is allowed to use the electric vehicle.
3. 2. The information management system according to claim 1, wherein the server sets the set period within the reserved usage period of the charging device as either a first period during which the borrower can use the electric vehicle or a second period during which adjustment of power supply and demand is performed.
4. The information management system further includes a terminal capable of communicating with the server, 2. The information management system according to claim 1, wherein, when reserving use of the charging device, the terminal transmits to the server a digital key that enables the server to borrow the electric vehicle for a set period that is set within a usage period of the charging device.
5. 2. The information management system according to claim 1, wherein the server acquires, from the electric vehicle, information on at least one of a usage history of the electric vehicle and a state of the electric vehicle during a period in which the charging device is used, and sets a charging schedule for the power storage device using the acquired information.
6. The information management system according to claim 1 , wherein the server receives information for temporarily granting use authority to a borrower who is other than the owner of the electric vehicle and who borrows the electric vehicle during a reserved time.
7. a terminal that notifies a user of an electric vehicle of reservation information for reserving use of a charging device that can charge an electric vehicle equipped with a power storage device, the terminal transmits information for temporarily granting a right of use to a borrower who will borrow the electric vehicle during the reserved time; An information management system that uses the state of charge of the storage device or the distance from the location of the electric vehicle to the charging device to determine whether to prioritize VPP use as a small-scale power source facility or shared use as a car share or rental car over the other.
8. An information management method executed by a server, comprising: a step in which the server manages reservation information for reserving the use of a charging device capable of charging an electric vehicle equipped with a power storage device; receiving information by the server for temporarily granting a right of use to a borrower who will borrow the electric vehicle during a reserved time; an information management method including a step in which the server determines whether to prioritize VPP use as a small-scale power supply facility or shared use as a car share or rental car over the other, using the state of charge of the storage device or the distance from the position of the electric vehicle to the charging device.
9. An information management method executed by a terminal, comprising: a step in which the terminal notifies a user of the electric vehicle of reservation information for reserving use of a charging device capable of charging the electric vehicle equipped with a power storage device; a step of transmitting information from the terminal for temporarily granting a right of use to a borrower who will borrow the electric vehicle during the reserved time; an information management method including a step in which the terminal determines whether to prioritize VPP use as a small-scale power supply facility or shared use as a car share or rental car over the other, using the charge state of the power storage device or the distance from the position of the electric vehicle to the charging device.
Citation Information
Patent Citations
Battery charging system of vehicle
JP2006074867A
Information processing device
JP2022132951A
Vehicle management system
WO2019130930A1
Information provision system and information provision method
WO2020194456A1