Vehicle, information processing method, and program

Abstract

To enhance the practicality of an electric-vehicle user.SOLUTION: In a case where an external charging-enabled vehicle has completed charging a driving battery in a given charging space, first information related to a first contact address of a user correlated with the vehicle is output via a given display device.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to charging electric vehicles. [Background technology]

[0002] Technologies have been proposed to shorten the waiting time for charging electric vehicles. In this regard, Patent Document 1 discloses a system that, when a vehicle remains parked in a charging space even after charging has been completed, sends a message to the user of the vehicle urging the vehicle to leave the charging space. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 5568772 Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure aims to improve convenience for users of electric vehicles. [Means for solving the problem]

[0005] A first aspect of the present disclosure is a vehicle capable of external charging, which has a control unit that outputs first information regarding the contact details of a first user associated with the vehicle via a specified display device when charging of the drive battery is completed in a specified charging space.

[0006] A second aspect of the present disclosure is an information processing method that causes a computer to execute the steps of reading the first information output by the vehicle and sending a request to move the vehicle to a first terminal associated with the first user based on the first information.

[0007] Furthermore, a third aspect of the present disclosure is an information processing method that causes a computer to execute the steps of reading first information output to a display device by a first vehicle, and sending a request to move the first vehicle to a first terminal associated with a user of the first vehicle based on the first information.

[0008] Another aspect of the present disclosure is a program for causing a computer to execute the above-described information processing method, or a computer-readable storage medium that non-temporarily stores the program. [Effects of the Invention]

[0009] According to the present disclosure, convenience for users of electric vehicles can be improved. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an overview of a vehicle system. [Figure 2] A diagram showing the relationship between charging space and evacuation space. [Figure 3] 1 is a diagram showing components of a vehicle 10 and an in-vehicle device 100. [Figure 4] 10 is an example of a contact image output by display device 150. [Figure 5] FIG. 2 is a diagram showing components of a mobile terminal 200. [Figure 6] FIG. 10 is a diagram illustrating information output by the mobile terminal 200A. [Figure 7] FIG. 2 is a diagram showing components of a server device 300. [Figure 8] 10 shows an example of terminal data stored in the server device 300. [Figure 9] 4 is a flowchart of a process executed by the in-vehicle device 100. [Figure 10] FIG. 10 is a sequence diagram of a process for evacuating a vehicle based on a movement request. [Figure 11] 10 is a flowchart of the process executed in step S25. [Figure 12] 1 is an example of an image output by the display device 150. [Figure 13] 10 shows a modified example of the image output by the display device 150. [Figure 14] FIG. 10 is a diagram showing components of a server device 300 according to a second embodiment. [Figure 15] FIG. 10 is a sequence diagram of processing according to the second embodiment. [Figure 16] 10 shows an example of a contact image according to the second embodiment. [Figure 17] 10 is an example of a screen presented to a second user. [Figure 18] 13 shows an example of a contact image according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] With the widespread use of electric vehicles, there is a demand for reducing waiting times for charging. Charging spots for electric vehicles are often installed in public facilities such as service areas. When charging at such locations, other users who wish to charge may have to wait their turn. However, once a driver leaves their vehicle, they are unable to determine the congestion status of the charging spot. In other words, a problem arises in that they are unable to determine whether they should immediately return to their vehicle after charging is complete in order to let others take their turn. The vehicle according to the present disclosure solves this problem.

[0012] One aspect of the present disclosure is a vehicle capable of external charging, which includes a control unit that, when charging of a drive battery is completed in a predetermined charging space, outputs first information related to contact information of a first user associated with the vehicle via a predetermined display device.

[0013] The first information is information for contacting a first user associated with the vehicle, typically a vehicle occupant (driver) of the vehicle. The first information may be obtained by encoding information using a predetermined procedure, such as a two-dimensional code. The first information may include, for example, an email address used by the first user, or a user identifier of a messenger application used by the first user. Furthermore, when contacting the first user via an external device, the first information may be an identifier issued by the external device (e.g., a vehicle identifier, a terminal identifier, a user identifier). The first information may be any data that can identify the mobile terminal owned by the first user.

[0014] When charging of the vehicle is completed, the control unit outputs the first information via a predetermined display device. The display device may be installed near the vehicle or on the vehicle itself. With this configuration, if the vehicle has finished charging but has not been moved, a message or the like requesting the first user to move the vehicle can be sent to the first user, allowing the first user to easily recognize that there is a queue at the charging facility.

[0015] One aspect of the present disclosure is an information processing method that causes a computer to perform the steps of reading first information output by a vehicle and, based on the first information, sending a request to move the vehicle to a first terminal associated with the first user.

[0016] The first information may be visually read using a camera or the like. The movement request may be sent directly to the first user or the first terminal, or may be sent to the first user or the first terminal via an external device. The information may be transmitted indirectly to the terminal.

[0017] Specific embodiments of the present disclosure will be described below with reference to the accompanying drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, etc. described in each embodiment are not intended to limit the technical scope of the disclosure to those configurations.

[0018] (First embodiment) An overview of a vehicle system according to a first embodiment will be described with reference to FIG. The vehicle system according to this embodiment is a system used by a first user and a second user. The first user is a user who is charging an electric vehicle in a specified charging space. The second user is a user who is waiting for the first user to complete charging (i.e., waiting in line for the charging facility).

[0019] The vehicle system includes a vehicle 10, an in-vehicle device 100, a display device 150, a mobile terminal 200A, a mobile terminal 200B, and a server device 300. The vehicle 10 is a vehicle in which a first user rides, and includes the in-vehicle device 100 and the display device 150. The mobile terminal 200A is a mobile terminal owned by a first user, and the mobile terminal 200B is a mobile terminal owned by a second user.

[0020] Here, there is a case where the first user leaves the vehicle during charging and does not return even after charging is completed. To deal with this, when charging is completed, the vehicle 10 according to this embodiment uses a display device provided in the vehicle to output information (code) for contacting the first user. The second user reads the code using the mobile terminal 200B and transmits a request to move the vehicle to the server device 300. The server device 300 identifies the mobile terminal 200A carried by the first user based on the contents of the code, and transfers the request to move the vehicle to the mobile terminal 200A. This makes it possible to notify the first user that there is a queue at the charging facility.

[0021] Upon receiving the request, the first user issues an instruction to move the vehicle and transmits it to the server device 300. The server device 300 then forwards this instruction to the vehicle 10. Upon receiving the instruction, the vehicle 10 moves its own vehicle from the charging space to a predetermined evacuation space by autonomous driving. FIG. 2 is a diagram illustrating the positional relationship between the charging space and the evacuation space. As shown in the figure, the evacuation space is located near the charging space. When the vehicle 10 moves into the evacuation space, a subsequent user can use the charging facility. At this time, the subsequent user may request the second user to remove the charging plug.

[0022] Each component of the system will now be described. The vehicle 10 is a connected car that has a communication function with an external network. The vehicle 10 is also an electric vehicle that has a motor and can run on power from a drive battery. The vehicle 10 can be an electric vehicle or a plug-in hybrid vehicle.

[0023] The vehicle 10 includes an in-vehicle device 100 and a display device 150. The in-vehicle device 100 is an electronic control unit (also referred to as ECU) that controls charging and autonomous driving of the vehicle 10. The vehicle 10 is equipped with a plurality of electronic control The electronic control unit may be configured to include a computer that manages the electronic control units, and these components may be connected to each other via an in-vehicle network (e.g., a CAN bus).

[0024] 3 is a diagram showing the system configuration of the vehicle 10. The vehicle 10 includes an in-vehicle device 100 and and a display device 150.

[0025] The in-vehicle device 100 includes a processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), a main memory such as a RAM or a ROM, an EPROM or a disk drive, The system may be configured as a computer having an auxiliary storage device such as a hard drive or removable media, however, some or all of the functions may be realized by hardware circuits such as ASICs or FPGAs.

[0026] The in-vehicle device 100 includes a control unit 101 , a storage unit 102 , and a communication unit 103 . The control unit 101 is a computing unit (processor) that realizes various functions of the in-vehicle device 100 by executing predetermined programs. The control unit 101 has, as functional modules, a charging control unit 1011 and a driving control unit 1012. Each functional module may be realized by executing a program stored in the storage unit 102 by a CPU or the like.

[0027] The charging control unit 1011 manages the charging of the drive battery of the vehicle 10. Specifically, the charging control unit 1011 executes (1) a process of determining that charging using external power has been completed, and (2) a process of outputting an image including information for contacting the first user to the display device 150 when charging has been completed. Hereinafter, the information for contacting the first user will be referred to as "contact information," and the image including the contact information will be referred to as a "contact image." Examples of the contact information include an identifier of the vehicle 10, an identifier of the first user, and an identifier of the mobile terminal 200A possessed by the first user. These identifiers are managed by the system and do not constitute personal information of the first user. In this embodiment, the contact information is the identifier of the vehicle 10 managed by the system.

[0028] 4 shows an example of a contact image in this embodiment. By encoding the contact information, a two-dimensional code as shown in the figure is obtained. In this embodiment, the charging control unit 1011 outputs a contact image including such a two-dimensional code via the display device 150 when charging of the vehicle 10 is completed. Mobile terminal 200B carried by the second user reads such a two-dimensional code and transmits the obtained contact information to server device 300. As a result, server device 300 can notify mobile terminal 200A carried by the first user that charging has been completed and that there is a queue at the charging facility. This operation will be described later together with an explanation of mobile terminal 200. The contact information image shown in FIG. 4 may be stored in the storage unit 102, which will be described later.

[0029] The driving control unit 1012 executes a remote parking function, which is a function that automatically controls the throttle and steering of the vehicle to park the vehicle in a predetermined parking space. The driving control unit 1012 generates commands (e.g., forward / reverse commands, steering commands) for parking the vehicle in a designated parking space based on sensor data acquired from multiple sensors possessed by the vehicle 10, and transmits the commands to the ECU that manages the driving of the vehicle 10.

[0030] The driving control unit 1012 is configured to be operable in two modes. The first mode is a mode in which the vehicle is parked with a parking space designated by the user as the target. For example, the user of the vehicle uses the mobile terminal 200 to designate the location of the parking space where the vehicle is to be parked. The designation of the location may be performed on an image (for example, a panoramic image generated based on an image acquired by an on-board camera). The vehicle determines a trajectory for parking into the designated parking space, and, based on the movement instruction received from the mobile terminal 200, Move slowly while controlling the steering.

[0031] The second mode is a mode in which the vehicle moves autonomously from the charging space to the evacuation space. In the second mode, the mobile terminal 200A transmits a movement instruction to the vehicle 10 from a remote location. The travel control unit 1012 automatically recognizes the evacuation space using an on-board camera or the like, determines a trajectory, and then controls the movement of the vehicle. This allows the vehicle to move unmanned from the charging space.

[0032] The storage unit 102 is a memory device including a main storage device and an auxiliary storage device. The auxiliary storage device stores an operating system (OS), various programs, various tables, etc., and by loading the programs stored therein into the main storage device and executing them, various functions that meet predetermined purposes, as will be described later, can be realized. The storage unit 102 also stores a contact image output by the charging control unit 1011. As described above, the contact image includes an identifier for identifying the first user (or the vehicle 10 used by the first user or the mobile terminal 200 possessed by the first user).

[0033] The communication unit 103 is a communication interface for connecting the in-vehicle device 100 to a network. The in-vehicle device 100 can connect to two types of networks: an external network (e.g., a mobile communication network) and an internal network (e.g., a Controller Area Network). The communication unit 103 may be configured to include a network interface board for connecting to both networks and a wireless communication interface.

[0034] The display device 150 is a display device unit having a screen. The display device 150 is disposed, for example, with its display surface facing the outside of the vehicle. This allows any information to be displayed to people outside the vehicle. The display device 150 can be configured using a liquid crystal display, an organic EL display, an LED matrix, a projector, or the like. Display device 150 may be disposed inside the vehicle or embedded in a part of the body. When display device 150 is a part of the body, display device 150 may be disposed, for example, on the left side, right side, rear of the vehicle, etc. Display device 150 may also be disposed near a charging port. When the display device 150 is installed inside a vehicle, an image may be displayed through a window glass (for example, a side window, a rear window, etc.). Also, if an image can be projected onto a window glass, the image may be projected onto any window.

[0035] Next, the mobile terminal 200 will be described. The mobile terminal 200 is a mobile terminal used by a user associated with the vehicle 10 (typically, a passenger of the vehicle 10). The mobile terminal 200 is, for example, a personal computer, a smartphone, a mobile phone, a tablet computer, a personal information terminal, or the like. In this embodiment, it is assumed that both the first user and the second user possess a mobile terminal 200. The former is referred to as mobile terminal 200A, and the latter is referred to as mobile terminal 200B.

[0036] FIG. 5 is a diagram showing the system configuration of the mobile terminal 200. As shown in FIG. The mobile terminal 200 includes a control unit 201 , a storage unit 202 , a communication unit 203 , an input / output unit 204 , and a camera 205 .

[0037] The control unit 201 is a calculation device that controls the mobile terminal 200. The control unit 201 can be realized by a calculation processing device such as a CPU. The control unit 201 is configured to have three functional modules: a request sending unit 2011, a request receiving unit 2012, and a vehicle control unit 2013. Each functional module may be realized by executing a stored program by a CPU.

[0038] The request transmission unit 2011 transmits data (hereinafter, a movement request) requesting the server device 300 to move the vehicle 10 parked in a specified charging space. Specifically, the request transmission unit 2011 reads a contact image output by the vehicle 10 via the camera 205 (described later) and obtains contact information by decoding a two-dimensional code included in the contact image. The contact information includes an identifier for the vehicle 10. The request transmission unit 2011 then transmits a movement request including the obtained contact information to the server device 300, requesting the server device 300 to move the vehicle 10. The request transmission unit 2011 functions when the mobile terminal 200 is used by a second user.

[0039] The request receiving unit 2012 receives a movement request from the server device 300. The movement request is transmitted by the request transmitting unit 2011. When the request receiving unit 2012 receives the movement request, it notifies the first user via an interface such as an image or a sound. The request receiving unit 2012 may output a screen such as that shown in FIG. 6 via the input / output unit 204, for example. The request receiving unit 2012 may also emit a sound, activate a vibrator, or the like. The request receiving unit 2012 functions when the mobile terminal 200 is used by the first user.

[0040] When instructed by the first user, the vehicle control unit 2013 generates an instruction (hereinafter, a movement instruction) to cause the vehicle 10 to move autonomously away from the charging space. In this embodiment, when the first user taps the button 601 shown in FIG. 6, the vehicle control unit 2013 generates the movement instruction. The movement instruction includes an identifier of the vehicle 10 (on-board device 100). The generated movement instruction is transmitted to the on-board device 100 (travel control unit 1012) via the server device 300. This allows the vehicle 10 to move autonomously from the charging space to the evacuation space.

[0041] The storage unit 202 is configured to include a main storage device and an auxiliary storage device. The main storage device is a memory in which programs executed by the control unit 201 and data used by the control programs are expanded. The auxiliary storage device is a device in which programs executed by the control unit 201 and data used by the control programs are stored. The auxiliary storage device may store programs executed by the control unit 201 packaged as applications. It may also store an operating system for executing these applications. The programs stored in the auxiliary storage device are loaded into the main storage device and executed by the control unit 201, thereby performing the processing described below.

[0042] The main memory may include RAM (Random Access Memory) and ROM (Read Only Memory). The auxiliary memory may include EPROM (Erasable Programmable ROM) and hard disk. It may also include a disk drive (HDD, Hard Disk Drive). may include removable media, i.e., portable recording media.

[0043] The communication unit 203 is a wireless communication interface for connecting the mobile terminal 200 to a network. The communication unit 203 is configured to be able to communicate with the server device 300 via, for example, a wireless LAN or a mobile communication service such as 3G, LTE, or 5G.

[0044] The input / output unit 204 is a unit that accepts input operations performed by the user and presents information to the user. In this embodiment, it is made up of a single touch panel display. That is, it is made up of a liquid crystal display and its control means, and a touch panel and its control means. The camera 205 is an optical unit that includes an image sensor for capturing images.

[0045] Next, the server device 300 will be described. Server device 300 is a computer that mediates communication between mobile terminals 200A and 200B. Server device 300 holds contact information and information linking the contact information with the first user (mobile terminal 200A), and when it receives a movement request from a second user (mobile terminal 200B), it forwards the request to the first user (mobile terminal 200A). Furthermore, the server device 300 has a function of mediating communication between the mobile terminal 200A and the vehicle 10 (on-vehicle device 100). When the server device 300 receives a movement instruction from the mobile terminal 200A, it transfers the instruction to the corresponding vehicle 10 (on-vehicle device 100).

[0046] FIG. 7 is a diagram showing in detail the components of the server device 300 included in the vehicle system according to this embodiment.

[0047] The server device 300 can be configured as a general-purpose computer. That is, the server device 300 can be configured as a computer having a processor such as a CPU or GPU, a main memory such as a RAM or ROM, and an auxiliary memory such as an EPROM, a hard disk drive, or removable media. The auxiliary memory stores an operating system (OS), various programs, various tables, etc., and the programs stored therein are loaded into a working area of the main memory and executed. By controlling each component through the execution of the programs, various functions consistent with a predetermined purpose can be realized, as described below. However, some or all of the functions may be realized by hardware circuits such as ASICs or FPGAs.

[0048] The server device 300 includes a control unit 301 , a storage unit 302 , and a communication unit 303 . The control unit 301 is an arithmetic unit that controls the server device 300. The control unit 301 can be realized by an arithmetic processing unit such as a CPU. The control unit 301 is configured to have a relay unit 3011 as a functional module. The functional module may be realized by executing a stored program by a CPU.

[0049] First, relay unit 3011 executes a process of transferring a movement request received from mobile terminal 200B to mobile terminal 200A. As described above, the movement request includes contact information. Relay unit 3011 identifies mobile terminal 200A owned by the first user based on the contact information included in the movement request, and transfers the movement request to the identified mobile terminal 200A. Information linking the contact information with the first user (mobile terminal 200A) may be stored in the storage unit 302, which will be described later.

[0050] Secondly, the relay unit 3011 executes a process of transferring the movement instruction received from the mobile terminal 200A to the vehicle 10 (on-board device 100). As described above, the movement instruction includes an identifier of the vehicle 10 (on-board device 100). Based on this, the relay unit 3011 identifies the target vehicle 10 and transfers the movement instruction to the on-board device 100 installed in the identified vehicle 10.

[0051] The storage unit 302 is configured to include a main storage device and an auxiliary storage device. The main storage device is a memory in which the programs executed by the control unit 301 and the data used by the control programs are expanded. The auxiliary storage device is a device in which the programs executed by the control unit 301 and the data used by the control programs are stored.

[0052] Furthermore, storage unit 302 stores terminal data 302A. The terminal data 302A links contact information with the mobile terminal 200A owned by the first user. In this embodiment, the contact information is the identifier of the vehicle 10. That is, the terminal data 302A is data that associates the identifier of the vehicle 10 with the identifier of the mobile terminal 200A carried by the first user. Fig. 8 shows an example of the terminal data 302A.

[0053] The communication unit 303 is a communication interface for connecting the server device 300 to a network. The communication unit 303 includes, for example, a network interface board and a wireless communication interface for wireless communication.

[0054] 3, 5, and 7 are merely examples, and all or part of the illustrated functions may be performed using dedicated circuits. Furthermore, programs may be stored or executed using a combination of main and auxiliary storage devices other than those illustrated.

[0055] Next, the processes executed by each device included in the vehicle system will be described in detail. 9 is a flowchart of processing executed by the in-vehicle device 100. The illustrated processing is repeatedly executed by the control unit 101 (charging control unit 1011) while the driving battery of the vehicle 10 is being externally charged.

[0056] In step S11, charging status information is acquired. The charging status information is, for example, a value representing the SoC (State of Charge) of the driving battery of the vehicle 10. Good too.

[0057] In step S12, it is determined whether charging of the vehicle 10 is complete. For example, if the SoC exceeds a predetermined value, this step is determined to be positive. The predetermined value may differ depending on the charging mode. For example, if rapid charging is being performed, charging may be determined to be complete when the SoC exceeds 80%, and if normal charging is being performed, charging may be determined to be complete when the SoC reaches 100%. If the determination in this step is affirmative, the process proceeds to step S13. If the determination in this step is negative, the process returns to step S11. In step S13, a predetermined contact image is output to display device 150. As described above, the contact image includes a two-dimensional code obtained by encoding information about the first user's contact information.

[0058] Next, a process in which the second user reads the contact image and requests the vehicle to move will be described. Fig. 10 is a sequence diagram of the process executed by the mobile terminals 200A and 200B, the server device 300, and the in-vehicle device 100.

[0059] First, in step S21, the second user uses mobile terminal 200B to read the contact image output on display device 150. The image is read by request sending unit 2011 using camera 205. The image may also be read via application software running on mobile terminal 200. The request sending unit 2011 detects the two-dimensional code from the scanned image and decodes it. This acquires the contact information. The request sending unit 2011 generates a travel request including the contact information and sends it to the server device 300.

[0060] The server device 300, which has received the movement request, identifies the mobile terminal 200A possessed by the first user based on the contact information (step S22). Specifically, the server device 300 identifies the identifier of the vehicle 10 indicated by the contact information, and identifies the identifier of the mobile terminal 200A corresponding to the vehicle 10. This process can be performed by referring to the terminal data 302A. The server device 300 (relay unit 3011) transfers the movement request to the identified mobile terminal 200A.

[0061] In step S23, the mobile terminal 200A (request receiving unit 2012) notifies the first user by image and / or sound. The notification may be continued until a response is received from the first user. If the first user responds to move the vehicle 10, the process proceeds to step S24, where the mobile terminal 200A (vehicle control unit 2013) generates a movement instruction. The movement instruction includes an identifier of the target vehicle 10. The movement instruction is transmitted to the target vehicle 10 (in-vehicle device 100) via the server device 300.

[0062] In step S25, the in-vehicle device 100 (travel control unit 1012) responds to the movement instruction and causes the vehicle 10 to move autonomously.

[0063] FIG. 11 is a flowchart showing in detail the processing performed by the driving control unit 1012 in step S25. First, in step S251, a request to unplug the charging plug is output via the display device 150. In order to move the vehicle 10 after charging is complete, the charging plug must be unplugged. Therefore, the driving control unit 1012 outputs an image including text such as the example shown in FIG. 12(A) via the display device 150. This makes it possible to request a person (typically a second user) in the vicinity of the vehicle 10 to unplug the charging plug. Such an image may be stored in the storage unit 102. Note that if the vehicle 10 has a function to lock the charging plug while charging, the charging plug may be unlocked at this timing. Furthermore, if the vehicle 10 has an audio output device, a sound may be played to notify the user that a request has been made.

[0064] In this example, the request to unplug the charging plug is output via vehicle 10 (display device 150), but the request to unplug the charging plug may be output by mobile terminal 200B. In this case, server device 300 may transmit data to mobile terminal 200B notifying that removal of the charging plug is permitted at the same time as transferring the movement command to in-vehicle device 100. In response to this, mobile terminal 200 may output a notification message (or image) such as that shown in FIG. 12(B). In this case, the processing of step S251 can be omitted.

[0065] Next, in step S252, it is determined whether the charging plug has been unplugged from the vehicle 10. Whether the charging plug has been unplugged can be determined, for example, based on CAN data flowing through the in-vehicle network. If the charging plug has been unplugged, the process proceeds to step S253. If the charging plug has not been unplugged, the process waits for a predetermined time and then repeats the same process.

[0066] In step S253, the driving control unit 1012 recognizes the location of the evacuation space and generates a travel route from the charging space to the evacuation space. The location of the evacuation space may be recognized based on an image captured by an on-board camera. For example, if a line indicating the route from the charging space to the evacuation space or a marker indicating the location of the evacuation space is provided on the road surface, the driving control unit 1012 can generate a travel route from the charging space to the evacuation space by image recognition of these. Furthermore, if the on-board device 100 previously stores data regarding the location of the evacuation space, the location of the evacuation space may be recognized by referring to the data.

[0067] In step S254, the vehicle 10 starts autonomous movement. The autonomous movement can be performed by a known technique. The traveling control unit 1012 receives data from sensors (e.g., LiDAR, radar, image sensor, etc.) provided in the vehicle 10, and determines whether the vehicle 10 is autonomous or not based on the received data. The driving control unit 1012 controls autonomous movement. The driving control unit 1012 can receive sensor data from these sensors via the in-vehicle network.

[0068] In step S255, it is determined whether the evacuation of the vehicle has been completed. If the evacuation of the vehicle has been completed, the process ends. If the evacuation of the vehicle has not been completed, the in-vehicle device 100 waits for a predetermined time and then repeats the same process. Note that when the evacuation of the vehicle has been completed, the in-vehicle device 100 may notify the mobile terminal 200A of this fact via the server device 300.

[0069] As described above, the vehicle 10 according to the first embodiment outputs information about the first user's contact information to the outside of the vehicle when charging of the drive battery is completed. The information is read by the mobile terminal 200B carried by the second user, and a travel request is generated. Furthermore, the mobile terminal 200A that receives the travel route communicates with the vehicle 10, thereby autonomously evacuating the vehicle. This configuration, first, makes it possible to notify the first user that there is a waiting list for charging equipment. Second, in the case where the first user cannot immediately return to the vehicle, it makes it possible to evacuate the vehicle unmanned.

[0070] (Modification of the first embodiment) In the first embodiment, the vehicle 10 is caused to move autonomously based on the operation of the first user. However, if the charging facility can be made available, the vehicle itself does not necessarily have to be moved. For example, if the second user can start charging by simply replacing the charging plug, the first user may be asked "whether or not to allow the replacement of the charging plug," and based on the result, guidance may be output on the display device 150. For example, the image shown in FIG. 13 may be output to request the second user to remove the charging plug.

[0071] (Second embodiment) In the first embodiment, the first user and the second user possess the same mobile terminal 200. In contrast, in the second embodiment, the second user uses a general-purpose computer.

[0072] It is conceivable that the first user of the vehicle 10 has a mobile terminal on which dedicated application software for realizing the functions of the control unit 201 is installed. On the other hand, it is highly likely that the second user does not use such application software. Therefore, in the second embodiment, a movement request can be sent using a browser that is included as standard in the mobile terminal (for example, a smartphone).

[0073] In the second embodiment, the mobile terminal used by the second user is similar to that shown in FIG. 5, but differs from mobile terminal 200 in that it does not have functional modules corresponding to request sending unit 2011, request receiving unit 2012, and vehicle control unit 2013.

[0074] In the second embodiment, the server device 300 provides a web server function for generating a movement request. Fig. 14 is a system configuration diagram of the server device 300 in the second embodiment. In this embodiment, the server device 300 is configured to further include a web service unit 3012. The web service unit 3012 provides a web server function. Specifically, it accepts access from a mobile terminal used by a second user and generates a movement request based on the result of an interaction with the second user.

[0075] 15 is a sequence diagram of the processes executed by each device in the second embodiment. Note that processes similar to those in the first embodiment are indicated by dotted lines and will not be described again. The second embodiment is different in that the contact information is written in URL format and the second user can This embodiment differs from the first embodiment in that the web server provided by the server device 300 is accessed by reading L and activating a web browser. 16 is an example of a two-dimensional code in the second embodiment. As shown in the figure, the two-dimensional code includes the address of a web server provided by server device 300 and the identifier of the target vehicle. By accessing the web service using this URL, the identifier of the target vehicle can be passed to server device 300.

[0076] The web service unit 3012 provides a user interface screen such as that shown in Fig. 17 and interacts with the second user. When the second user indicates his / her intention to request a vehicle movement via the user interface screen, the web service unit 3012 generates a movement request and transmits it to the mobile terminal 200A. The subsequent processing is the same as in the first embodiment.

[0077] In this way, it is possible for the second user to use a general-purpose computer as the mobile terminal on which no specific application software is installed.

[0078] (Third embodiment) In the first embodiment, only contact information is included in the two-dimensional code, but in this form, if the two-dimensional code or URL is copied, there is a risk that a movement request may be issued at an inappropriate time. To address this issue, the third embodiment is an embodiment in which the server device 300 further includes information for authenticating the second user in the two-dimensional code.

[0079] In this embodiment, a token for preventing data reuse, such as time information, location information, or a one-time password, is included in the two-dimensional code. Fig. 18(A) shows an example of information included in the two-dimensional code in this embodiment. As shown in the figure, the two-dimensional code includes the token. In this embodiment, the server device 300 uses the token in step S22 (or S22A) to determine whether the movement request sent from the second user is valid.

[0080] For example, if the token is date and time information, the server device 300 may determine whether the token included in the travel request transmitted from the second user is consistent with the current date and time. Also, if the token is location information, the server device 300 may determine whether the token included in the travel request transmitted from the second user is consistent with location information of the vehicle 10. Note that the location information of the vehicle 10 may be received from the in-vehicle device 100. For example, if the in-vehicle device 100 has a function of periodically transmitting location information, the server device 300 may store this information and use it for matching.

[0081] Furthermore, if the token is a one-time password, the in-vehicle device 100 and the server device 300 may each have a function for generating a password based on current time information. The password may be, for example, a character string obtained by hashing the current time information. By comparing the token included in the movement request (i.e., the token generated by the in-vehicle device 100) with the token generated by the server device 300, it is possible to confirm that the two-dimensional code has not been reused.

[0082] This embodiment can also be applied to the second embodiment, in which case a two-dimensional code such as that shown in Fig. 18(B) can be used.

[0083] (Variation) The above-described embodiment is merely an example, and the present disclosure can be modified and implemented as appropriate within the scope that does not deviate from the gist of the disclosure. For example, the processes and means described in this disclosure can be freely combined and implemented as long as no technical contradiction occurs.

[0084] In addition, in the description of the embodiment, the vehicle 10 has the display device 150, but the display device does not necessarily have to be provided on the vehicle. For example, if a display device (signage) for guidance is provided at the charging facility, the in-vehicle device 100 may transmit a contact image to the display device by wireless communication or wired communication. In this embodiment, it is possible to prominently notify that charging has been completed or that a travel request can be sent.

[0085] Although the description of the embodiment has been given of a contact image including a two-dimensional code, the in-vehicle device 100 may present contact information using a method other than a two-dimensional code. For example, the in-vehicle device 100 may present contact information using a character string.

[0086] In addition, in the description of the embodiment, an identifier issued by the system is used as the contact information, but other information can also be used as the contact information. For example, the contact information can be an email address used by the first user, a user ID of a messenger application used by the first user, or the like. Any information can be used as the contact information as long as it can identify the mobile device owned by the first user. If the contact information is not managed by an external device, the second user can contact the first user directly without going through the external device (server device 300). Furthermore, if the server device 300 is not used, the mobile terminal 200A used by the first user may start autonomous movement by directly communicating with the vehicle 10 (in-vehicle device 100).

[0087] 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 (server configuration) by which each function is realized can be flexibly changed.

[0088] The present disclosure can also be realized by providing a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors in the computer read and execute the program. Such a computer program may be provided to the computer via a non-transitory computer-readable storage medium connectable to the computer's system bus or via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (e.g., a floppy disk, a hard disk drive (HDD), etc.), an optical disk (e.g., a CD-ROM, a DVD disk, a Blu-ray disk), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, or any type of medium suitable for storing electronic instructions. [Explanation of symbols]

[0089] 10. Vehicle 100...In-vehicle equipment 101, 201, 301...Control unit 102,202,302...Storage section 103,203,303···Communications Department 150...Display device 200 Mobile devices 204...Input / output section 205···Camera 300 Server device

Claims

1. A vehicle capable of external charging, When charging of the drive battery is completed in a predetermined charging space, first information related to contact information of a first user associated with the vehicle is output via a predetermined display device; When a movement instruction is received from a first terminal associated with the first user while the vehicle is parked in the charging space, the charging plug is unlocked and / or a notification that the charging plug can be removed is output via the display device. A vehicle having a control unit.

2. The first information is information about the first user's contact information encoded according to a predetermined procedure. The vehicle of claim 1 .

3. when the control unit receives the movement instruction from the first terminal while the vehicle is parked in the charging space, the control unit moves the vehicle to an evacuation space outside the charging space.

3. A vehicle according to claim 1 or 2.

4. the control unit recognizes, based on the sensor data, a line provided on a road surface indicating a route from the charging space to the evacuation space, or the evacuation space indicated by a marker indicating the location of the evacuation space.

4. The vehicle of claim 3.

5. the control unit starts moving the vehicle on the condition that the charging plug is removed.

5. A vehicle according to claim 3 or 4.

6. The display device is further provided with a display surface facing the outside of the vehicle. A vehicle according to any one of claims 1 to 5.

7. A computer comprising: The first information output by the vehicle according to any one of claims 1 to 6 is acquiring the image via a camera of the computer; transmitting a request to move the vehicle to a first terminal associated with the first user based on the first information; An information processing method that performs the above.

8. A computer comprising: acquiring first information outputted to a display device by a first vehicle via a camera of the computer; transmitting a request to move the first vehicle to a first terminal associated with a user of the first vehicle based on the first information; An information processing method that performs the above.

9. the first vehicle is a vehicle parked in a predetermined charging space, the first information is information that is output when charging of a drive battery of the first vehicle is completed; The information processing method according to claim 8.

10. The method further includes receiving notification data from the first terminal notifying that removal of the charging plug is permitted. The information processing method according to claim 9.

11. and when the notification data is received from the first terminal, outputting a guide indicating that the first vehicle will move from the charging space by removing the charging plug. The information processing method according to claim 10.

12. An information processing method for controlling a vehicle capable of external charging, comprising: outputting, via a predetermined display device, first information relating to contact points of a first user associated with the vehicle when charging of the drive battery is completed in a predetermined charging space; and when the vehicle receives a movement instruction from a first terminal associated with the first user while parked in the charging space, unlocking a charging plug and / or outputting a notification that the charging plug can be removed via the display device. Information processing methods.

13. The first information is information about the first user's contact information encoded according to a predetermined procedure. The information processing method according to claim 12.

14. and when the vehicle receives the movement instruction from the first terminal while parked in the charging space, moving the vehicle to an evacuation space outside the charging space.

14. The information processing method according to claim 12 or 13.

15. and further comprising a step of recognizing the evacuation space indicated by a line on a road surface indicating a route from the charging space to the evacuation space or a marker indicating the location of the evacuation space, based on the sensor data. The information processing method according to claim 14.

16. Starting the movement of the vehicle on the condition that the charging plug is removed.

16. The information processing method according to claim 14 or 15.

17. A program for causing a computer to execute the information processing method according to any one of claims 7 to 16.

Images