Information processing device

Abstract

To provide a technique capable of improving convenience for users who demand to charge their vehicles.SOLUTION: In an information processing device, a control unit receives a first request for information on a second vehicle having a power supply function from a first terminal corresponding to a first vehicle. The control unit 3 acquires a scheduled location and a scheduled time zone in which the second vehicle is to be parked. The control unit generates first information including the scheduled parking location and the scheduled parking time zone of the second vehicle, and transmits the generated first information to the first terminal.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device. [Background technology]

[0002] Patent Document 1 discloses a configuration for acquiring the current positions of multiple vehicles, searching for recommended locations for transferring energy between the multiple vehicles based on the current positions of the multiple vehicles, and providing the multiple vehicles with information about the searched recommended locations for transferring energy. Patent Document 2 discloses a configuration for transmitting a power supply request signal, including the current position of the vehicle, to other vehicles around the vehicle via vehicle-to-vehicle communication, requesting power supply to the vehicle's driving battery. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-167759 [Patent Document 2] Japanese Patent Application Laid-Open No. 2013-192285 Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present disclosure is to provide a technology that can improve convenience for users who wish to charge their vehicles. [Means for solving the problem]

[0005] The present disclosure can be understood as an information processing device. In this case, the information processing device includes, for example, receiving a first request for information on a second vehicle having a power supply function, the first request being transmitted from a first terminal corresponding to the first vehicle; Obtaining a planned parking position and a planned parking time period of the second vehicle; transmitting first information including the planned parking position and the planned parking time zone of the second vehicle to the first terminal; The control unit may be configured to execute the above.

[0006] The present disclosure can also be regarded as an information processing method in which a computer executes the processing of the information processing device described above, or as an information processing program for causing a computer to execute the information processing method described above, or as a non-transitory storage medium for storing the information processing program. [Effects of the Invention]

[0007] According to the present disclosure, it is possible to provide a technology that can improve convenience for users who wish to charge their vehicles. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an overview of a system according to an embodiment. [Figure 2] FIG. 2 illustrates an example of a hardware configuration of a server according to an embodiment. [Figure 3] FIG. 2 is a block diagram illustrating an example of a functional configuration of a server according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of information stored in a parking management DB according to an embodiment. [Figure 5] 4 is a flowchart illustrating a processing routine executed by a server in the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] In the information processing device according to the present disclosure, the control unit receives a first request transmitted from a first terminal. The first terminal is, for example, a mobile terminal used by a user of the first vehicle, or an in-vehicle terminal mounted on the first vehicle. The first vehicle is, for example, a PHEV (Plug-in Hybrid Electric Vehicle (EV) or BEV (Battery Electric Vehicle), etc. is a signal requesting information about a second vehicle. The second vehicle is, for example, a PHEV or BEV with a power supply function. The information processing device according to the present disclosure is, for example, a server that communicates with the first terminal and the second terminal via a network.

[0010] When the control unit receives the first request, the control unit acquires the planned parking location and planned parking time zone of the second vehicle. The control unit transmits the acquired first information including the planned parking location and planned parking time zone to the first terminal. This allows the user of the first vehicle to know the planned parking location and planned parking time zone of the second vehicle through the first terminal. As a result, the user of the first vehicle can more accurately determine whether the battery of the first vehicle can be charged using the second vehicle.

[0011] Specific embodiments of the present disclosure will be described below with reference to the accompanying drawings. Unless otherwise specified, the hardware configurations, module configurations, functional configurations, and the like described in the following embodiments are not intended to limit the technical scope of the disclosure to those configurations alone.

[0012] <Embodiment> In this embodiment, an example will be described in which an information processing device according to the present disclosure is applied to a system for providing information on a vehicle having a power supply function.

[0013] (System Overview) Fig. 1 is a diagram showing an overview of a system in this embodiment. The system in this embodiment includes a first in-vehicle device 100 mounted on a first vehicle 10, a second in-vehicle device 200 mounted on a second vehicle 20, a server 300, and a user terminal 400. The first in-vehicle device 100, the second in-vehicle device 200, the server 300, and the user terminal 400 are connected via a network. Note that although the example shown in Fig. 1 shows only one second vehicle 20 (second in-vehicle device 200), multiple second vehicles 20 (second in-vehicle devices 200) are under the management of the server 300.

[0014] The first vehicle 10 is a vehicle whose drive battery can be charged by external power supply. The first vehicle 10 is, for example, a PHEV or BEV that runs on battery power as a drive source. The second vehicle 20 is a PHEV or BEV that runs on battery power as a drive source and has the function of supplying power to other vehicles. In this embodiment, an example will be described in which a company car is used as the second vehicle 20.

[0015] The first in-vehicle device 100 is a computer mounted on the first vehicle 10. The first in-vehicle device 100 in this embodiment has the function of a car navigation system. That is, the first in-vehicle device 100 accepts input of a departure point and a destination by a user of the first vehicle 10, and presents a planned driving route from the departure point to the destination to the user. The planned driving route is presented, for example, in the form of displaying the planned driving route on a map.

[0016] The first vehicle-mounted device 100 of this embodiment also has a function of displaying, when displaying the planned driving route of the first vehicle 10 on a map, information indicating the planned parking time period (planned parking start date and time and planned parking end date and time) of the second vehicle 20 and the remaining battery capacity at the planned parking position of the second vehicle 20 on the map. When the first vehicle 10 arrives at the destination, the first vehicle 10 transmits a first request to the server 300 to acquire the planned parking position, planned parking time zone, and remaining battery charge of the second vehicle 20. The first request is a signal requesting information about the second vehicle 20, and includes information about the planned driving route of the first vehicle 10.

[0017] The first in-vehicle device 100 of this embodiment also has a function of accepting a reservation from a user for battery charging from the second vehicle 20 to the first vehicle 10, and a function of transmitting a signal (second request) for requesting the accepted reservation to the server 300. The second request includes, for example, identification information (a vehicle ID, described later) of the second vehicle 20 for which the reservation is to be made.

[0018] When the server 300 of this embodiment receives a first request transmitted from the first in-vehicle device 100, it generates first information and transmits the generated first information to the first in-vehicle device 100. The first information includes a planned parking position, a parking time zone, and a remaining battery charge of the second vehicle 20. The remaining battery charge of the second vehicle 20 is acquired by the server 300 communicating with the second in-vehicle device 200.

[0019] Furthermore, when the server 300 of this embodiment receives a second request transmitted from the first in-vehicle device 100, it transmits reservation information to the user terminal 400 used by the user of the second vehicle 20. The reservation information includes information regarding a planned parking location and a planned parking time period when the second vehicle 20 is used to charge the battery of the first vehicle 10. Note that while the second vehicle 20 is being used to charge the battery of the first vehicle 10 (planned parking time period), the user of the second vehicle 20 will not be able to use the second vehicle 20. Therefore, it is conceivable that the user of the second vehicle 20 will have too much time on their hands. Therefore, the reservation information may include information regarding recommended spots (for example, tourist spots, amusement facilities, or restaurants) located near the planned parking location to be reserved. This allows the user of the second vehicle 20 to spend the time until the planned parking end date and time at the recommended spots.

[0020] The second in-vehicle device 200 is a computer mounted on the second vehicle 20. In this embodiment, the second in-vehicle device 200 has a function of acquiring the remaining battery charge of the second vehicle 20 in response to a request from the server 300 and transmitting the acquired remaining battery charge to the server 300.

[0021] The user terminal 400 has a function of presenting the reservation information to the user of the second vehicle 20 when the reservation information transmitted from the server 300 is received.

[0022] In this embodiment, the first in-vehicle device 100 corresponds to the "first terminal" according to the present disclosure. The user terminal 400 in this embodiment corresponds to the "second terminal" according to the present disclosure. The server 300 in this embodiment corresponds to the "information processing device" according to the present disclosure. Note that, instead of the first in-vehicle device 100, a mobile terminal (e.g., a smartphone or a tablet terminal) used by the user of the first vehicle 10 can also be used as the "first terminal" according to the present disclosure. In this case, it is sufficient that an application program for providing a car navigation service is installed on the mobile terminal.

[0023] (Server configuration) Fig. 2 is a diagram showing an example of the hardware configuration of the server 300 in this embodiment. As shown in Fig. 2, the server 300 in this embodiment is configured to include a processor 301, a main memory unit 302, an auxiliary memory unit 303, and a communication unit 304. Note that, in the example shown in Fig. 2, only the hardware configuration related to a service that provides information on vehicles having a power supply function is extracted and illustrated, but the server 300 may include other hardware configurations.

[0024] The processor 301 is an arithmetic processing device such as a CPU (Central Processing Unit) or a DSP (Digital Signal Processor). The program is loaded into the main memory 302 and executed, and the server 300 is controlled through this execution.

[0025] The main memory unit 302 includes semiconductor memories such as a RAM (Random Access Memory) and a ROM (Read Only Memory). The main memory unit 302 provides a storage area and a working area for loading programs stored in the auxiliary memory unit 303. The main memory unit 302 is also used as a buffer for arithmetic processing by the processor 301.

[0026] The auxiliary storage unit 303 is, for example, an EPROM (Erasable Programmable ROM) or The auxiliary storage unit 303 is a removable medium, i.e., a hard disk drive (DD). The auxiliary storage unit 303 may include a removable storage medium. The removable medium is, for example, a disk storage medium such as a USB (Universal Serial Bus) memory, a CD (Compact Disc), or a DVD (Digital Versatile Disc). The auxiliary storage unit 303 stores various programs and data used by the processor 301 when executing each program.

[0027] The programs stored in the auxiliary memory unit 303 include an OS (Operating System) as well as dedicated programs for causing the processor 301 to execute processing related to a service that provides information on vehicles with power supply capabilities.

[0028] The communication unit 304 is an interface for connecting the server 300 to a network. The network may be, for example, a WAN (Wide Area Network), which is a global public communication network such as the Internet, or other communication networks. For example, mobile communication systems such as LTE (Long Term Evolution), LTE-Advanced, 5G (5th Generation), and 6G (6th Generation), Wi-Fi (registered trademark), etc. The communication unit 304 connects to the network using a wireless communication method, a LAN (Local Area Network), etc. In this embodiment, the communication unit 304 communicates with the first in-vehicle device 100, the second in-vehicle device 200, and the user terminal 400 through the network. .

[0029] (Server functional configuration) The functional configuration of server 300 in this embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing an example of the functional configuration of server 300. As shown in Fig. 3, server 300 in this embodiment has, as its functional components, a control unit 310 and a parking management DB 320. Note that the functional components of server 300 are not limited to the example shown in Fig. 3, and components may be omitted, replaced, or added as appropriate.

[0030] Here, of the control unit 310 and the parking management DB 320, the parking management DB 320 will be described first. The parking management DB 320 stores information regarding the parking schedule of the second vehicle 20 for a predetermined period (for example, a period of several days to several weeks). The parking management DB 320 of this embodiment is a database that is constructed in the auxiliary storage unit 303 of the server 300 when the processor 301 of the server 300 executes a DBMS (Database Management System) program. In this case, the parking management DB 320 may be constructed as a relational database. The parking management DB 320 of this embodiment corresponds to the "first database" according to the present disclosure.

[0031] 4 is a diagram showing an example of information stored in the parking management DB 320 in this embodiment. As shown in FIG. 4, the parking management DB 320 in this embodiment stores a plurality of records (hereinafter referred to as "parking As shown in FIG. 4, each parking information record has fields such as a vehicle ID, appearance, and parking schedule.

[0032] The vehicle ID field stores information (vehicle ID) that allows the server 300 to identify each of the multiple second vehicles 20 under the management of the server 300. The appearance field stores information that indicates external characteristics (e.g., the character string on the vehicle registration plate, the vehicle model, and the body color) that allow a person other than the user of the second vehicle 20 (e.g., the user of the first vehicle 10) to identify each second vehicle 20.

[0033] In the parking schedule field, information indicating the parking schedule of each second vehicle 20 for a predetermined period is registered. In the example shown in FIG. 4, the parking schedule field is divided into subfields for location, time period, user, and reservation. In the location field, information indicating the location where each second vehicle 20 is scheduled to be parked (e.g., latitude and longitude, or address, etc.) is registered. In the time period field, the time period (scheduled parking start date and time and scheduled parking end date and time) when each second vehicle 20 is scheduled to be parked at the scheduled parking location is registered. In the user field, identification information of the user who will use each second vehicle 20 (e.g., a company employee who uses the second vehicle 20 as a company car) is registered. In this embodiment, information indicating the email address of the user terminal 400 of the user who will use each second vehicle 20 is registered in the user field. In the reservation field, information indicating whether or not the second vehicle 20 is reserved for use to charge the battery of another vehicle is registered. For example, for each second vehicle 20, a reserved parking schedule is registered as "Yes" in the reservation field, and an unreserved parking schedule is registered as "No" in the reservation field.

[0034] For the second vehicle 20 for which multiple parking schedules are set during a predetermined period, multiple parking schedule fields ("Parking Schedule 1" to "Parking Schedule N (N is a natural number)" in FIG. 4) are set. In this case, a user field is provided for each parking schedule because, for the second vehicle 20 used as a company car, the user (employee) who uses the second vehicle 20 may be different for each parking schedule.

[0035] Information indicating the parking schedule of the second vehicle 20 for a predetermined period (scheduled parking date and time, scheduled parking time zone, and email address of the user terminal 400) is provided periodically by the company or the like that uses the second vehicle 20 as a company car, and is registered in the parking management DB 320. Note that the configuration of the parking information record is not limited to the example shown in Fig. 4, and fields can be added, changed, or deleted as appropriate.

[0036] 3, the control unit 310 of the server 300 will now be described. The control unit 310 is realized by the processor 301 of the server 300 loading a dedicated program stored in the auxiliary storage unit 303 into the main storage unit 302 and executing the program. Note that the control unit 310 may also be realized by a hardware circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0037] The control unit 310 is triggered by the communication unit 304 receiving the first request to determine the second vehicle 20 that is the subject of the first information. First, the control unit 310 accesses the parking information record in the parking management DB 320 and determines whether "None" is registered in the reservation field of the parking schedule field. If "None" is registered in the reservation field, the control unit 310 determines whether a parking schedule for the current day (the day the first request was received or the planned day the first vehicle 10 is to move) is registered based on the information registered in the planned parking time zone field of the parking schedule field. In this case, if the planned parking time zone registered in the time zone field includes at least a part of the time zone of the current day, the control unit 310 determines that a parking schedule for the current day is registered. In addition, if "None" is registered in the time zone field, the control unit 310 determines that a parking schedule for the current day is registered. If the registered planned parking time zone does not include any time zone for the day, the control unit 310 determines that the parking schedule for the day is not registered. The determination of whether the parking schedule for the day is registered is performed for all parking information records registered in the parking management DB 320.

[0038] The control unit 310 excludes from the first information the second vehicle 20 for which "Yes" is registered in the reservation field and the second vehicle 20 for which no parking schedule for the day is registered. On the other hand, for the second vehicle 20 for which "No" is registered in the reservation field and for which a parking schedule for the day is registered, the control unit 310 calculates the planned length of time the vehicle will be parked at the planned parking location (first time length Tl1). In this case, the control unit 310 may calculate the length of time from the planned parking start date and time to the planned parking end date and time as the first time length Tl1. Alternatively, the control unit 310 may calculate the time length for the day from the planned parking start date and time to the planned parking end date and time as the first time length Tl1. The control unit 310 determines whether the calculated first time length Tl1 is equal to or greater than a predetermined time length Tlthre1. The predetermined time length Tlthre1 is, for example, the minimum charging time length (for example, about 3 hours) required to charge the battery of the first vehicle 10 using the second vehicle 20.

[0039] For a second vehicle 20 for which it is determined that the first time length Tl1 is less than the predetermined time length Tlthre1, the control unit 310 excludes the second vehicle 20 from the target of the first information. On the other hand, for a second vehicle 20 for which it is determined that the first time length Tl1 is equal to or greater than the predetermined time length Tlthre1, the control unit 310 calculates a distance (first distance L1) from the planned driving route of the first vehicle 10 to the planned parking position based on the information registered in the position field. The control unit 310 determines whether the calculated first distance L1 is within the predetermined distance Lthre1. The predetermined distance Lthre1 is, for example, a distance (e.g., several hundred meters to several kilometers) that is shorter than the distance that the first vehicle 10 can travel with the remaining battery charge even when the remaining battery charge of the first vehicle 10 has dropped to a predetermined threshold (e.g., the remaining battery charge at which a warning is output to prompt battery charging).

[0040] For a second vehicle 20 whose first distance L1 is determined to be greater than the predetermined distance Lthre1, the control unit 310 excludes it from the scope of the first information. On the other hand, for a second vehicle 20 whose first distance L1 is determined to be within the predetermined distance Lthre1, the control unit 310 determines it as a subject of the first information.

[0041] According to the above-mentioned method, among the multiple second vehicles 20 under the management of the server 300, the second vehicle 20 for which a parking schedule for the day has been set, the first time length Tl1 is equal to or greater than a predetermined time length Tlthre1, and the first distance length L1 is within the predetermined distance length Lthre1 is determined to be the target of the first information.

[0042] When the second vehicle 20 that is the subject of the first information is determined, the control unit 310 communicates with the second in-vehicle device 200 of the second vehicle 20 via the communication unit 304 to obtain the remaining battery charge.

[0043] The control unit 310 generates first information for the second vehicle 20 determined as the subject of the first information. The first information is information including the vehicle ID, parking schedule (planned parking location and planned parking time zone), and remaining battery charge of the second vehicle 20 determined as the subject of the first information. At this time, for the second vehicle 20 for which multiple parking schedules are registered in the parking management DB 320, only the parking schedule including the parking schedule for the day among the multiple parking schedules is included in the first information. The control unit 310 transmits the generated first information to the first in-vehicle device 100 via the communication unit 304. The first in-vehicle device 100 that has received the first information transmits the planned driving route of the first vehicle 10 and the planned parking schedule of the second vehicle 20. The location is displayed on the map. Furthermore, the first vehicle-mounted device 100 displays the planned parking time period and remaining battery charge of the second vehicle 20 at the planned parking location of the second vehicle 20 on the map.

[0044] Furthermore, when the communication unit 304 of the server 300 receives the second request, the control unit 310 transmits reservation information to the user terminal 400 used by the user of the second vehicle 20. The second request is a signal requesting a reservation for battery charging of the first vehicle 10 by the second vehicle 20, and includes the vehicle ID and parking schedule of the second vehicle 20 desired by the user. When the communication unit 304 receives such a second request, the control unit 310 accesses the parking management DB 320 using the vehicle ID included in the second request as an argument, and identifies a parking information record whose information registered in the vehicle ID field matches the vehicle ID included in the second request. The control unit 310 identifies a parking schedule field among the parking schedule fields registered in the identified parking information record in which information matching the parking schedule included in the second request is registered. The control unit 310 registers "Yes" in the reservation field of the identified parking schedule field. The control unit 310 also reads out information (email address) registered in the user field of the identified parking schedule field. The control unit 310 transmits the reservation information to the user terminal 400 having the read email address. The reservation information includes information about the planned parking location and planned parking time period when the second vehicle 20 is to be used to charge the battery of the first vehicle 10, as well as information about recommended spots located around the planned parking location.

[0045] After transmitting the reservation information to the user terminal 400, the control unit 310 may transmit information indicating that the reservation has been completed to the first in-vehicle device 100. The information indicating that the reservation has been completed may include information indicating the external characteristics of the second vehicle 20 to be reserved (information registered in the appearance field of the parking information record). This enables the user of the first vehicle 10 to identify the second vehicle 20 when arriving at the planned parking location of the second vehicle 20.

[0046] (Processing flow) Next, the flow of processing executed by server 300 in this embodiment will be described with reference to Fig. 5. Fig. 5 is a flowchart showing a processing routine executed by server 300 when triggered by communication unit 304 of server 300 receiving a first request. The processing routine in Fig. 5 is executed by processor 301 of server 300, but here the processing routine will be described assuming that a functional component (control unit 310) of server 300 is the executing unit.

[0047] 5, when communication unit 304 of server 300 receives a first request, the first request is passed from communication unit 304 to control unit 310. As a result, control unit 310 receives the first request through communication unit 304 (step S101). After completing the process of step S101, control unit 310 executes the process of step S102.

[0048] 5 are executed for all parking information records registered in the parking management DB 320. First, in step S102, the control unit 310 determines whether a valid parking schedule is registered in the target parking information record. A valid parking schedule is a parking schedule in which "None" is registered in the reservation field of the parking schedule field, and the planned parking time zone registered in the planned parking time zone field of the parking schedule field includes at least a part of the time zone of the day. If it is determined that a valid parking schedule is registered in the target parking information record (positive determination in step S102), the control unit 310 executes the process of step S103.

[0049] In step S103, the control unit 310 calculates a first time length Tl1 based on information registered in the time period field of the parking schedule field in which a valid parking schedule is registered. Specifically, the control unit 310 calculates the length of time from the scheduled parking start date and time to the scheduled parking end date and time as the first time length Tl1. Alternatively, the control unit 310 may calculate the length of time for the current day from the scheduled parking start date and time to the scheduled parking end date and time as the first time length Tl1. The control unit 310 determines whether the calculated first time length Tl1 is equal to or greater than a predetermined time length Tlthre1. If the first time length Tl1 is equal to or greater than the predetermined time length Tlthre1 (positive determination in step S103), the control unit 310 executes the process of step S104.

[0050] In step S104, the control unit 310 calculates a first distance L1 (the distance from the planned driving route of the first vehicle 10 to the planned parking position) based on the information registered in the position field of the parking schedule field in which a valid parking schedule is registered. The control unit 310 determines whether the calculated first distance L1 is within a predetermined distance Lthre1. If the first distance L1 is within the predetermined distance Lthre1 (positive determination in step S104), the control unit 310 executes the process of step S105.

[0051] In step S105, the control unit 310 determines the second vehicle 20 corresponding to the target parking information record as the target of the first information.

[0052] If a negative determination is made in any of steps S102-S104, the control unit 310 executes the process of step S106. In step S106, the control unit 310 determines that the second vehicle 20 corresponding to the target parking information record is not included in the first information.

[0053] After completing the process of step S105 or step S106, the control unit 310 executes the process of step S107. In step S107, the control unit 310 determines whether the process of steps S102-S106 has been executed for all parking information records registered in the parking management DB 320. If the process of steps S102-S106 has not been executed for all parking information records registered in the parking management DB 320 (negative determination in step S107), the control unit 310 executes the process of steps S102-S106 for the next target parking information record. Furthermore, if the process of steps S102-S106 has been executed for all parking information records registered in the parking management DB 320 (positive determination in step S107), the control unit 310 executes the process of step S108.

[0054] In step S108, the control unit 310 acquires the remaining battery charge of the second vehicle 20 determined as the subject of the first information in step S105 by communicating with the second in-vehicle device 200 of the second vehicle 20 via the communication unit 304. If there are multiple second vehicles 20 determined as the subject of the first information, the control unit 310 acquires the remaining battery charge for each of the multiple second vehicles 20. After completing the processing of step S108, the control unit 310 executes the processing of step S109.

[0055] In step S109, the control unit 310 generates first information for the second vehicle 20 determined as the subject of the first information in step S105. The first information is information including the vehicle ID, parking schedule (planned parking location and planned parking time period), and remaining battery charge of the second vehicle 20 determined as the subject of the first information. If there are multiple second vehicles 20 determined as the subject of the first information, the control unit 310 generates first information for each of the multiple second vehicles 20. Furthermore, for a second vehicle 20 for which multiple parking schedules are registered in the parking management DB 320, only the parking schedule that includes the parking schedule for the day among the multiple parking schedules is included in the first information. The control unit 3 After completing the process of step S109, the CPU 10 executes the process of step S110.

[0056] In step S110, the control unit 310 transmits the first information generated in step S109 to the first in-vehicle device 100 of the first vehicle 10 via the communication unit 304. After completing the process of step S110, the control unit 310 executes the process of step S111.

[0057] In step S111, the control unit 310 determines whether the communication unit 304 has received a second request from the first in-vehicle device 100. The second request is a signal requesting a reservation for battery charging of the first vehicle 10 by the second vehicle 20, and includes the vehicle ID and parking schedule of the second vehicle 20 desired by the user. If the communication unit 304 has not received the second request (negative determination in step S111), the control unit 310 waits for reception of the second request. Note that if the communication unit 304 does not receive the second request within a preset timeout time, the control unit 310 may terminate execution of this processing routine. On the other hand, if the communication unit 304 has received the second request (positive determination in step S111), the control unit 310 executes the processing of step S112.

[0058] In step S112, the control unit 310 accesses the parking management DB 320 using the vehicle ID included in the second request as an argument and identifies a parking information record whose vehicle ID field information matches the vehicle ID included in the second request. The control unit 310 identifies a parking schedule field in the identified parking information record that has information matching the parking schedule included in the second request registered therein. The control unit 310 registers "Yes" in the reservation field of the identified parking schedule field. The control unit 310 also reads information (email address) registered in the user field of the identified parking schedule field. The control unit 310 transmits reservation information to the user terminal 400 having the read email address. The reservation information includes information about the planned parking location and planned parking time period when the second vehicle 20 is used to charge the battery of the first vehicle 10, as well as information about recommended spots located near the planned parking location. After completing the process of step S112, the control unit 310 executes the process of step S113.

[0059] In step S113, the control unit 310 transmits information indicating that the reservation has been completed (reservation completion information) to the first in-vehicle device 100 of the first vehicle 10 via the communication unit 304. The reservation completion information may include information indicating the external characteristics of the second vehicle 20 to be reserved, in addition to the information indicating that the reservation has been completed. The information indicating the external characteristics of the second vehicle 20 to be reserved is, for example, information registered in the appearance field of the parking information record identified in step S112 (such as the character string on the vehicle registration plate, the vehicle model, and the body color). After completing the processing of step S113, the control unit 310 terminates the execution of this processing routine.

[0060] (Actions and Effects of the Embodiments) According to the embodiment described above, when the first in-vehicle device 100 displays the planned driving route of the first vehicle 10 on a map, it can display, at the planned parking position of the second vehicle 20 on the map, information indicating the planned parking time period of the second vehicle 20 (planned parking start date and time and planned parking end date and time) and the remaining battery charge of the second vehicle 20. This enables the user of the first vehicle 10 to more accurately determine whether the battery of the first vehicle 10 can be charged using the second vehicle 20 while traveling along the planned driving route, and which second vehicle 20 should be used to charge the battery of the first vehicle 10.

[0061] The second vehicle 20 displayed on the map by the first vehicle-mounted device 100 is located at the first time. The second vehicle 20 is limited to those whose first distance length L1 is equal to or less than the predetermined time length Tlthre1 and whose second distance length Tl1 is equal to or less than the predetermined distance length Lthre1. This makes it possible to prevent a situation in which the time available for charging the battery of the first vehicle 10 using the second vehicle 20 is insufficient, or the first vehicle 10 is unable to reach the planned parking position of the second vehicle 20.

[0062] Furthermore, the reservation information is notified to the user of the second vehicle 20 via the user terminal 400. This makes it possible to prevent the user of the second vehicle 20 from parking the second vehicle 20 in a location different from the planned parking position or from moving the second vehicle 20 during the planned parking time period.

[0063] Therefore, according to this embodiment, convenience for a user who wishes to charge the first vehicle 10 can be improved.

[0064] <Other> The above-described embodiment is merely an example, and the present disclosure may be modified and implemented as appropriate without departing from the spirit and scope of the present disclosure. Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by a single device. In a computer system, the hardware configuration for implementing each function can be flexibly changed. [Explanation of symbols]

[0065] 10 First car 20 Second vehicle 100 First in-vehicle device 200 Second in-vehicle device 300 servers 301 processor 302 Main memory 303 Auxiliary storage unit 304 Communications Department 310 Control Unit 320 Parking management DB 400 User Terminals

Claims

1. An information processing device comprising a first database and a control unit, the first database stores information indicating a parking schedule that associates a planned parking position and a planned parking time period of a second vehicle having a power supply function; The control unit receiving a first request for information about a second vehicle, the first request being sent from a first terminal corresponding to the first vehicle; determining, based on the information in the first database, whether or not information indicating a parking schedule for the day including the day on which the first request is received from the first terminal is stored in the first database; When information indicating a parking schedule for the current day, including the day on which the first request was received, is stored in the first database, acquiring a planned parking position and a planned parking time period for the second vehicle included in the information indicating the parking schedule for the current day; transmitting first information including the acquired planned parking position and planned parking time zone of the second vehicle to the first terminal; To execute Information processing device.

2. When information indicating a parking schedule for the current day, including the day on which the first request was received, is stored in the first database, the control unit further acquires a remaining battery charge of the second vehicle related to the information indicating the parking schedule for the current day, and includes the remaining battery charge in the first information. The information processing device according to claim 1 .

3. The control unit determining whether a first length of time, which is a length of time that the second vehicle is scheduled to be parked at the scheduled parking position, is equal to or greater than a predetermined length of time, based on information in the first database; transmitting the first information to the first terminal when it is determined that the first time length is equal to or greater than the predetermined time length; To execute The information processing device according to claim 1 .

4. The control unit acquiring a planned driving route of the first vehicle; determining whether a first distance, which is a distance from the planned driving route to the planned parking position, is within a predetermined distance, based on the planned driving route and information in the first database; transmitting the first information to the first terminal when it is determined that the first distance is within the predetermined distance; To execute The information processing device according to claim 1 .

5. The control unit receiving, from the first terminal, a reservation for power supply from the second vehicle to the first vehicle; transmitting information about the reservation to a second terminal used by a user of the second vehicle that is the subject of the reservation; transmitting information indicating that the reservation has been completed, the information including information indicating external characteristics of the second vehicle to be reserved, to the first terminal; To execute The information processing device according to claim 1 .

Images