Vehicle management system, vehicle management method, and computer-readable recording medium

Abstract

The invention relates to a vehicle management system, a vehicle management method, and a computer-readable recording medium. The present disclosure improves the quality and persistence of a service performed by a vehicle management system. The vehicle management system manages the vehicle. The vehicle management system is provided with one or more processors. The one or more processors are configured to: establish wireless communication with the target vehicle before or after the target vehicle is stopped at the stop position, and start handover processing, which is a process of transferring an authority to operate the target vehicle from a user of the target vehicle to the vehicle management system; executing presence confirmation processing for confirming the presence of a user after getting off the target vehicle stopped at the stop position within a predetermined range adjacent to the stop position until the handover processing is completed; and notifying the user that the handover process is completed when it is confirmed that the user is within the predetermined range until the handover process is completed.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a technology of managing a vehicle. BACKGROUND

[0002] Patent Literature 1 discloses an automatic parking system having a server. The server transmits an authentication code to a reservation user after receiving a reservation for entry into a parking lot of an automatic driving vehicle from the reservation user. Thereafter, in a case where entry into the parking lot using the authentication code is performed within the parking lot, the server starts an instruction for automatic valet parking for the automatic driving vehicle of the reservation user within the parking lot.

[0003] Further, Patent Literature 2 discloses a method of performing automatic valet parking. The method includes a step of starting automatic valet parking. Also, the step includes a step of an infrastructure identifying a driver of a vehicle and the vehicle.

[0004] PRIOR ART DOCUMENTS

[0005] PATENT LITERATURE

[0006] Patent Literature 1: Japanese Patent Application Publication No. 2021-064117

[0007] Patent Literature 2: Japanese Patent Application Publication No. 2020-075717

[0008] Consideration is given to “handover processing” of transferring a right to operate a target vehicle from a user of the target vehicle to a vehicle management system. Basically, if the handover processing is completed, the vehicle management system is allowed to operate the target vehicle. However, a situation is also considered in which the vehicle management system is not suitable to directly operate the target vehicle. In such a situation, the user is required to implement additional measures for bringing the target vehicle into an appropriate state. However, if the user has already left the place, a state is entered in which the additional measures cannot be immediately implemented, and the operation of the target vehicle cannot be performed. When the target vehicle cannot be arbitrarily moved and thus the target vehicle is stuck at the place, a service by the vehicle management system is stopped. SUMMARY

[0009] The vehicle management system of the present disclosure manages vehicles. The vehicle management system has one or more processors. The one or more processors are configured to: establish wireless communication with the target vehicle before or after the target vehicle stops at the stop position, and start a handover process, wherein the handover process is a process of transferring the authority to operate the target vehicle from the user of the target vehicle to the vehicle management system; perform an existence confirmation process, wherein the existence confirmation process is a process of confirming that the user who gets off the target vehicle that stops at the stop position is present in a specified range adjacent to the stop position until the handover process is completed; and in the case where it is confirmed that the user is present in the specified range until the handover process is completed, notify the user that the handover process is completed.

[0010] The vehicle management method disclosed herein is a method for managing vehicles using a computer. The method includes: establishing wireless communication with a target vehicle before or after the target vehicle stops at a stop position and initiating a handover process, wherein the handover process is a process for transferring authority to operate the target vehicle from a user of the target vehicle to a vehicle management system; performing a presence confirmation process, wherein the presence confirmation process is a process for confirming that a user who has disembarked from the target vehicle at the stop position is present within a specified range adjacent to the stop position until the handover process is completed; and, upon confirming that the user has been present within the specified range until the handover process is completed, notifying the user of the completion of the handover process.

[0011] A computer-readable recording medium disclosed herein stores a vehicle management program executed by a computer for managing vehicles. The vehicle management program causes the computer to: establish wireless communication with a target vehicle before or after the target vehicle stops at a stop position and initiate a handover process, wherein the handover process is a process for transferring authority to operate the target vehicle from a user of the target vehicle to the vehicle management system; execute a presence confirmation process, wherein the presence confirmation process is a process for confirming that a user, after getting off the target vehicle at the stop position, is present within a specified range adjacent to the stop position until the handover process is completed; and, if the user is confirmed to be present within the specified range until the handover process is completed, notify the user of the completion of the handover process.

[0012] Effects of the Invention

[0013] According to the present disclosure, even if the target vehicle is not in a suitable state when the handover process is completed, the user whose presence has been confirmed to be within the specified range (i.e., near the target vehicle) can be promptly instructed to implement additional measures to restore the target vehicle to a suitable state. This prevents the target vehicle from being stranded in a state where it cannot be operated. This is ideal from the perspective of the quality and continuity of the services provided by the vehicle management system. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 This is a conceptual diagram for explaining the outline of the vehicle management system according to the embodiment.

[0015] Figure 2 This is a block diagram showing a configuration example of a vehicle management system according to an embodiment.

[0016] Figure 3 This is a conceptual diagram for explaining countermeasures to problems related to handover processing.

[0017] Figure 4 This is a flowchart showing an example of processing executed in the vehicle management system according to the embodiment.

[0018] Figure 5 This is a conceptual diagram for explaining a first example of the existence confirmation process.

[0019] Figure 6 This is a flowchart showing an example of the flow of the existence confirmation process of the first example.

[0020] Figure 7 This is a conceptual diagram for explaining a second example of the existence confirmation process.

[0021] Figure 8 This is a flowchart showing an example of the flow of the existence confirmation process of the second example.

[0022] Figure 9 This is a conceptual diagram for explaining a third example of the existence confirmation process.

[0023] Figure 10 This is a flowchart showing an example of the flow of the existence confirmation process of the third example.

[0024] Figure 11 This is a conceptual diagram for explaining a fourth example of the existence confirmation process.

[0025] Figure 12 This is a flowchart showing an example of the flow of the existence confirmation process of the fourth example.

[0026] Figure 13 This is a flowchart showing an example of the flow of processing when a combination of multiple types of existence confirmation processing is used.

[0027] Figure 14 This is a flowchart showing an example of the flow of the first existence confirmation process and the second existence confirmation process in the first combination example.

[0028] Figure 15This is a flowchart showing an example of the flow of the first existence confirmation process and the second existence confirmation process in the second combination example.

[0029] Description of Reference Numerals

[0030] 1: Parking lot; 2: Get-off location; 6: Stopping location; 7: Specified range; 10: Vehicle (target vehicle); 12: On-board camera; 100: Vehicle management system; 110: Infrastructure camera; 120: Management device; 130: Communication device; 140: Processor; 150: Storage device; 200: User terminal; 210: Display. DETAILED DESCRIPTION

[0031] Embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0032] 1. Overview of Vehicle Management System

[0033] Figure 1 This is a conceptual diagram for explaining the outline of the vehicle management system 100 of the embodiment. The vehicle management system 100 manages the vehicle 10. The vehicle 10 is a "target vehicle" managed by the vehicle management system 100. More specifically, the vehicle management system 100 manages the automatic driving (unmanned driving) of the vehicle 10 within the "prescribed area". Figure 1 In the example shown, the designated area is parking lot 1. In this example, vehicle management system 100 functions as an automated valet parking (AVP) management system that manages automated valet parking (AVP) for vehicle 10 in parking lot 1. It should be noted that the designated area is not limited to parking lot 1 and may also be, for example, an area within a factory. The following description uses parking lot 1 as an example of the designated area.

[0034] Vehicle 10 is configured to perform AVP in parking lot 1. Vehicle 10 is capable of autonomous driving, at least within parking lot 1, independent of driver control. More specifically, the autonomous driving of vehicle 10 within parking lot 1 is controlled, for example, by vehicle management system 100 utilizing infrastructure cameras 110. Alternatively, autonomous driving may be controlled through collaboration between vehicle management system 100 and the control system of vehicle 10. It should be noted that vehicle 10 may also be an autonomous vehicle capable of autonomous driving outside of parking lot 1.

[0035] The parking lot 1 includes a drop-off place 2, a pick-up place 3, a passageway 4, and a plurality of parking spaces 5. A vehicle 10 that is to be parked in the parking lot 1 stops at a stop position 6 of the drop-off place 2, where a user gets off from the vehicle 10. The stop position 6 of the drop-off place 2 provided is an example of the "stop position" of the present disclosure. On the other hand, a vehicle 10 that is to be picked up from the parking lot 1 stops at the pick-up place 3, where a user gets on the vehicle 10. The drop-off place 2 can also be referred to as a parking-in place, and the pick-up place 3 can also be referred to as a parking-out place. The passageway 4 is an area where the vehicle 10 travels. The parking space 5 is a space where the vehicle 10 is parked.

[0036] The vehicle management system 100 can communicate with the vehicle 10 and manage the vehicle 10. For example, the vehicle management system 100 uses the infrastructure camera 110 to grasp the position and state of each vehicle 10 in the parking lot 1. The vehicle management system 100 assigns a parking space 5 to the vehicle 10. The vehicle management system 100 issues a movement instruction (for example, a parking-in instruction, a parking-out instruction) to the vehicle 10 in the parking lot 1. The vehicle management system 100 can also provide the vehicle 10 with map information of the parking lot 1. The vehicle management system 100, for example, generates a target route of the vehicle 10 in the parking lot 1 and remotely operates the vehicle 10 in the parking lot 1. Further, the vehicle management system 100 can also provide the vehicle 10 with information of the generated target route.

[0037] Further, the vehicle management system 100 manages information related to a user of an automated valet parking service (AVP service). The vehicle management system 100 can communicate with a user terminal 200 operated by the user.

[0038] Hereinafter, an example of a flow when a certain user X uses the AVP service will be described. The user X's membership information is registered in advance in the vehicle management system 100.

[0039] First, the user X makes a reservation for the AVP. For example, the user X operates the user terminal 200 and inputs information such as the user X's ID information, a desired parking lot 1, a desired use date, and a desired use time. The user terminal 200 transmits reservation information including the input information to the vehicle management system 100. The vehicle management system 100 performs a reservation process based on the reservation information and transmits a reservation completion notification to the user terminal 200. Further, the vehicle management system 100 issues authentication information corresponding to the reservation information. The authentication information is, for example, a reservation code such as a QR (Quick Response) code (registered trademark). In more detail, the vehicle management system 100 transmits the generated authentication information to the user terminal 200. The user terminal 200 receives the authentication information and holds the received authentication information.

[0040] The vehicle 10 enters the parking lot 1 (enters the parking lot) as follows. The vehicle 10 on which the user X is seated arrives at the drop-off place 2 of the parking lot 1 and stops at the stop position 6. At the drop-off place 2, the user X gets off the vehicle 10 (if there are other passengers, the other passengers also get off the vehicle 10).

[0041] When the vehicle 10 enters the parking lot 1, the vehicle management system 100 performs a "handover process", which is a process of transferring the authority to operate the vehicle 10 (target vehicle) from the user X of the vehicle 10 to the vehicle management system 100. Details of the handover process will be described later. When the handover process is completed, the authority to operate the vehicle 10 is transferred from the user X to the vehicle management system 100. The vehicle management system 100 performs an entry process related to the vehicle 10. The entry process includes a process related to automatic travel of the vehicle 10 to the parking stall 5 assigned to the vehicle 10.

[0042] 2. Configuration example of vehicle management system

[0043] Figure 2 is a block diagram that shows a configuration example of the vehicle management system 100 according to the embodiment. The vehicle management system 100 includes a management device 120 and one or more infrastructure cameras 110 (hereinafter, simply referred to as "infrastructure camera 110").

[0044] The infrastructure camera 110 is provided at various places of the parking lot 1 and discriminates the situation of the parking lot 1 including the drop-off place 2 and the pick-up place 3. Information obtained by the infrastructure camera 110 is transmitted to the management device 120.

[0045] The management device 120 manages the vehicle 10 (target vehicle). The management device 120 is provided at the parking lot 1, for example. Alternatively, the management device 120 can be a management server (cloud) that manages a plurality of parking lots 1, for example. Alternatively, the management device 120 can be a combination of a management server and a local management device provided at the parking lot 1.

[0046] The management device 120 includes a communication device 130, one or more processors 140 (hereinafter, simply referred to as "processor 140"), and one or more storage devices 150 (hereinafter, simply referred to as "storage device 150"). The communication device 130 communicates with the vehicle 10, the infrastructure camera 110, and the user terminal 200 via a communication network, respectively.

[0047] The processor 140 performs various processes relating to the management of the vehicle 10. As the processor 140, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or the like is exemplified. The processor 140 can also be referred to as a "circuitry" or a "processing circuitry". The "circuitry" is hardware that is programmed in a manner to realize the recited functions or hardware that executes the functions. The storage 150 stores various information. As the storage 150, a volatile memory, a non-volatile memory, an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like is exemplified. The processor 140 reads out various information from the storage 150, and stores various information in the storage 150, in addition.

[0048] Further, in the storage 150, information such as parking lot map information, parking lot utilization information, and vehicle management information is stored. The parking lot map information is map information of the parking lot 1. The parking lot utilization information indicates utilization conditions (free conditions) of the drop-off place 2, the pick-up place 3, and the parking frame 5 in the parking lot 1. The vehicle management information is information for managing the vehicles 10 that are the objects of the AVP. For example, the vehicle management information includes a vehicle ID, user information, entry / exit time information, and position information. The vehicle ID, the user information, the entry / exit time information, and the position information are associated with each vehicle 10. The vehicle ID is identification information of the vehicle 10. The user information is information related to a user who utilizes the vehicle 10. The entry / exit time information is information related to the entry / exit time of the vehicle 10. The position information indicates the position of the vehicle 10 in the parking lot 1.

[0049] The function of the management device 120 can also be realized by the cooperation of the storage 150 and the processor 140 that executes a vehicle management program. The vehicle management program is a computer program for managing the AVP. The vehicle management program is stored in the storage 150. Alternatively, the vehicle management program can also be recorded on a computer-readable recording medium. The vehicle management program can also be provided via a network.

[0050] 3. Transfer of operation authority

[0051] In order to start the automatic travel of the vehicle 10 (target vehicle) by the vehicle management system 100, it is necessary to transfer the authority to operate the vehicle 10 (operation authority) from the user to the vehicle management system 100. The processing performed by the vehicle management system 100 (the processor 140) for the transfer of the operation authority includes the handover processing (authority transfer processing) described above.

[0052] 3-1. Handover Processing

[0053] The handover processing includes processing for establishing wireless communication with the vehicle 10 and processing for identifying the vehicle 10 as a target vehicle (vehicle identification processing). The identification (authentication) of the target vehicle requires that the vehicle 10 that is to receive the provision of the automatic travel service be a vehicle 10 of a regular user (target vehicle).

[0054] The vehicle management system 100 starts the handover processing, for example, after the vehicle 10 stops at the stop position 6 (refer to FIG. 1) of the drop-off location 2. Figure 1 In more detail, the vehicle management system 100 starts the handover processing, for example, after recognizing that the user has gotten off the vehicle 10 using the infrastructure camera 110. Note that the handover processing can also be started not after the vehicle 10 (target vehicle) stops at the stop position 6 but before the vehicle 10 stops at the stop position 6. In more detail, the vehicle management system 100 can also start the handover processing while the vehicle 10 is traveling in a prescribed zone in front of the stop position 6.

[0055] The vehicle identification processing is started, for example, in response to the transmission of the handover request from the vehicle management system 100 to the vehicle 10. The method of the vehicle identification processing is not particularly limited. For example, the vehicle identification processing can be performed using the following action of the vehicle 10. That is, in the example of the vehicle identification processing using the action, the vehicle management system 100 instructs the execution of a prescribed action to the vehicle 10 on the basis of the establishment of the wireless communication with the vehicle 10. If the vehicle 10 is a regular target vehicle, the vehicle 10 is expected to execute the prescribed action as instructed. After the instruction is performed, the vehicle management system 100 discriminates the action executed by the vehicle 10 using a sensor such as the infrastructure camera 110. Also, in the case where the discriminated action coincides with the expected action, the vehicle management system 100 identifies the vehicle 10 that has executed the discriminated action as the target vehicle. The prescribed action can be either a visible action that can be visually sensed, or an audible action that can be aurally sensed. As examples of the visible action, the lighting or blinking of the headlamp or the brake lamp, the blinking of the direction indicator, the operation of the wiper, or the opening and closing of the door or the window are cited. Further, as examples of the audible action, the sounding of the horn or the start of the engine (revving) are cited. The visible action or the audible action is executed in accordance with an action pattern designated by the vehicle management system 100. Further, the instruction of the vehicle management system 100 can also contain a request to repeat a certain action pattern. In the example using the audible action, the vehicle management system 100 can also be provided with a microphone for sensing the audible action.

[0056] 3-2. Problem

[0057] Basically, if the handover processing is completed, the vehicle management system 100 is allowed to operate the vehicle 10 (target vehicle). However, a situation is also considered in which the vehicle management system 100 is not suitable for directly operating the vehicle 10 (for example: the window of the vehicle 10 is open, the SOC (State Of Charge) remaining in the vehicle 10 is small, etc.). In such a situation, the user X is required to implement an additional measure for bringing the vehicle 10 into an appropriate state. However, the handover processing takes a certain degree of time, and therefore the user X can have moved to a place away from the stop position 6 of the vehicle 10 at the time when the handover processing is completed. In particular, in the case where the vehicle 10 executes a prescribed action in the vehicle identification processing, time is taken. If the user X has moved away from the stop position 6 of the vehicle 10, a state is entered in which the additional measure for bringing the vehicle 10 into an appropriate state cannot be immediately implemented, and the operation of the vehicle 10 cannot be performed. When the vehicle 10 cannot be freely moved and therefore the vehicle 10 is stranded, the service by the vehicle management system 100 is stopped.

[0058] 3-3. Countermeasures

[0059] Figure 3 is a conceptual diagram for describing a countermeasure against a problem related to handover processing. In view of the above problem, the processor 140 of the vehicle management system 100 of the present embodiment, while executing handover processing, also executes the following "existence confirmation processing". As shown in Figure 3 , the existence confirmation processing is processing of confirming the presence of the user X in the prescribed range 7 adjoining the stop position 6 until the handover processing is completed after the user X has gotten off the vehicle 10 (target vehicle) stopped at the stop position 6. Also, in the case where it is confirmed in the existence confirmation processing that the user X is present in the prescribed range 7 until the handover processing is completed, the processor 140 notifies the user X that the handover processing is completed.

[0060] Figure 4 is a flowchart showing one example of processing executed in the vehicle management system 100 of the present embodiment.

[0061] In step S100, the processor 140 determines whether or not the start timing of handover processing has come. Specifically, in the example where handover processing is started after the vehicle 10 is stopped at the stop position 6, the determination in step S100 is made, for example, on the basis of whether or not it is recognized by the infrastructure camera 110 that the user has gotten off the vehicle 10. On the other hand, in the example where handover processing is started before the vehicle 10 is stopped at the stop position 6, the determination in step S100 is made, for example, on the basis of whether or not the vehicle 10 has entered a prescribed authority transfer area having a certain range just before the stop position 6. In the case where the processor 140 determines that the start timing of handover processing has come (step S100: YES), the processing proceeds to step S102.

[0062] In step S102, the processor 140 starts handover processing. The handover processing includes processing for establishing wireless communication with the vehicle 10 and vehicle identification processing.

[0063] In step S104 following step S102, the processor 140 executes (starts) existence confirmation processing. Details of the existence confirmation processing will be described later. Thereafter, the processing proceeds to step S106. Note that it is also possible that, while the existence confirmation processing is being executed, the processor 140 also notifies the user X via the user terminal 200 of a request that the user X not move away from the vicinity of the vehicle 10 until the handover processing is completed after the user X has gotten off the vehicle 10.

[0064] In step S106, the processor 140 determines whether the presence of the user X in the prescribed range 7 until the handover processing is completed is confirmed. In a case where the result thereof is that the presence of the user X until the handover processing is completed is confirmed through the presence confirmation processing (step S106: YES), the processor 140 notifies the user X that the handover processing is completed (step S108). Specifically, for the notification, the processor 140 can transmit, for example, information indicating that the handover processing is completed to the user terminal 200. Alternatively, the processor 140 can also notify the user X that the handover processing is completed, for example, by using a notification device such as a speaker provided at the drop-off location 2. Further, in a case where the presence of the user until the handover processing is completed is confirmed, the processor 140 ends the presence confirmation processing. On the other hand, in a case where the presence of the user X until the handover processing is completed cannot be confirmed through the presence confirmation processing (step S106: NO), the processing proceeds to "END".

[0065] 4. Details of the Presence Confirmation Processing

[0066] Next, the first to fourth examples of the presence confirmation processing are sequentially described.

[0067] 4-1. First Example (Tracking)

[0068] Figure 5 is a conceptual diagram for describing the first example of the presence confirmation processing. In the first example, Figure 2 The infrastructure camera 110 illustrated in FIG. 10 includes at least one infrastructure camera 110 that includes at least a part of the prescribed range 7 adjoining the stop position 6 in the field of view. The at least one infrastructure camera 110 is provided, for example, at the drop-off location 2.

[0069] In the first example, the presence confirmation processing includes acquiring an image I1 captured by the above-described at least one infrastructure camera 110. Further, the presence confirmation processing includes performing tracking of the user X after the user X gets off the vehicle 10 (the subject vehicle) on the basis of the acquired image I1, thereby confirming the presence of the user X in the prescribed range 7 until the handover processing is completed. More specifically, the processor 140 senses the user X after the user X gets off the vehicle 10 on the basis of the image I1, and performs tracking of the user X. The tracking can be performed, for example, by using a Person ReID (Re-Identification) technique. Note that, for the acquisition of the image I1, a camera (a vehicle-mounted camera) 12 (refer to FIG. 1) mounted on the vehicle 10 in such a manner as to recognize the situation around the vehicle 10 can also be used instead of the infrastructure camera 110. Figure 11

[0070] Figure 6 ​This is a flowchart showing an example of the process of the existence confirmation process of the first example. Figure 6 The processing shown reflects the characteristics of the first example and more specifically shows Figure 4 The processing of steps S104 and S106 in .

[0071] exist Figure 6 In step S200 following step S102, the processor 140 acquires an image I1 captured by at least one infrastructure camera 110. The acquired image I1 is stored in the storage device 150. Thereafter, the process proceeds to step S202.

[0072] In step S202, processor 140 determines whether user X is detected within the predetermined range 7 included in image I1 acquired in step S200. If user X is detected (step S202: Yes), processing proceeds to step S204. On the other hand, if user X is not detected (step S202: No), processing proceeds to "End." Note that processing may also proceed to "End" if user X is not detected multiple times as determined in step S202.

[0073] In step S204, the processor 140 determines whether the handover process has been completed. If the result is that the handover process has not been completed (step S204: No), the process returns to step S200. That is, the processor 140 obtains a new image I1 and continues tracking the user X. On the other hand, if the handover process has been completed (step S204: Yes), the process proceeds to step S108 (see Figure 4 ). In addition, the processor 140 ends the existence confirmation process.

[0074] 4-2. Second Example (Near Field Communication)

[0075] Figure 7 In the second example, the predetermined range 7 corresponds to the communication range of short-range communication (eg, Bluetooth (registered trademark)) between the vehicle 10 (target vehicle) and the user terminal 200 of the user X.

[0076] In the second example, the presence confirmation process includes confirming that the short-range communication between the vehicle 10 (target vehicle) and the user terminal 200 is continuing, thereby confirming that the user X is within the predetermined range 7 until the handover process is completed.

[0077] Figure 8 This is a flowchart showing an example of the process of the existence confirmation processing of the second example. Figure 8The illustrated process reflects the features of the second example and more specifically represents the process of steps S104 and S106 in Figure 4

[0078] In Figure 8 , in step S300 following step S102, the processor 140 instructs the vehicle 10 and the user terminal 200 to perform close proximity communication between the two. This instruction is performed, for example, when it is recognized using the infrastructure camera 110 that the user X has gotten off the vehicle 10. Alternatively, the instruction can also be performed before getting off.

[0079] In step S302 following step S300, the processor 140 determines whether the close proximity communication between the vehicle 10 and the user terminal 200 is continuing. Information indicating whether the close proximity communication is continuing can be acquired, for example, from the vehicle 10 or the user terminal 200, and the determination is made based on the acquired information.

[0080] In the case where the close proximity communication is continuing (step S302: YES), the processor 140 determines whether the handover process has been completed (step S304). In the case where the result is that the handover process has not been completed (step S304: NO), the process returns to step S302. That is, the processor 140 continues the confirmation that the close proximity communication is continuing. On the other hand, in the case where the handover process has been completed (step S304: YES), the process proceeds to step S108 (refer to Figure 4 ). Further, the processor 140 ends the presence confirmation process.

[0081] On the other hand, in the case where the close proximity communication is not continuing (step S302: NO), the process proceeds to "END". Note that, in the case where it is determined in step S302 that the close proximity communication is not continuing, the processor 140 can repeatedly perform the determination of step S302 during a prescribed time from the time of interruption of the close proximity communication. Also, in the case where the prescribed time has been reached from the time of interruption of the close proximity communication, the process proceeds to "END".

[0082] 4-3. Third Example (Confirmation of Code Using Infrastructure Camera)

[0083] Figure 9 is a conceptual diagram for explaining a third example of the presence confirmation process. As with the first example, in the third example, Figure 2 ​The illustrated infrastructure camera 110 also includes at least one infrastructure camera 110 that includes at least a portion of the prescribed range 7 that adjoins the stop position 6 in the angle of view. This at least one infrastructure camera 110 is disposed at the drop-off location 2. For example, at the time of reservation of the AVP, a prescribed code (e.g., a QR code or the like) is transmitted from the vehicle management system 100 to the user terminal 200. Note that the transmission of the prescribed code from the vehicle management system 100 can also be performed after the vehicle 10 arrives at the parking lot 1, for example.

[0084] In the third example, the presence confirmation process includes acquiring an image I1 captured by the at least one infrastructure camera 110 described above. Further, the presence confirmation process includes, after the handover process is completed, requesting the user X to cause the infrastructure camera 110 to read the prescribed code displayed on the user terminal 200 of the user X. Moreover, the presence confirmation process includes confirming that the prescribed code is displayed on the user terminal 200 based on the image I1.

[0085] Figure 10 is a flowchart that represents one example of a flow of the presence confirmation process of the third example. Note that the process of Figure 10 the illustrated process reflects the features of the third example and more specifically represents the process of steps S104 and S106 in Figure 4 .

[0086] In Figure 10 , after step S102, the processor 140 determines whether the handover process has been completed (step S400). In the case where the result is that the handover process has been completed (step S400: YES), the process proceeds to step S402.

[0087] In step S402, the processor 140 requests the user X to display a prescribed code on the display 210 of the user terminal 200 via the user terminal 200 (refer to Figure 9 ), and presents the prescribed code to the infrastructure camera 110 to cause the infrastructure camera 110 to read the displayed prescribed code. Thereafter, the process proceeds to step S404.

[0088] In step S404, the processor 140 acquires an image I1 captured by the at least one infrastructure camera 110 described above. The acquired image I1 is stored in the storage device 150. Thereafter, the process proceeds to step S406.

[0089] In step S406, the processor 140 determines whether the prescribed code is displayed on the user terminal 200 based on the image I1 captured by the infrastructure camera 110. In the case where the result is that the display of the prescribed code is confirmed (step S406: YES), the process proceeds to step S108 (refer to Figure 4). That is, in a case where the display of the prescribed code is confirmed, it is determined that the user X exists in the prescribed range 7 until the handover processing is completed. Further, the processor 140 ends the existence confirmation processing.

[0090] On the other hand, in a case where the display of the prescribed code is not confirmed (step S406: No), the processing proceeds to "End". Note that, in a case where the display of the prescribed code is not confirmed, the processor 140 can repeatedly execute the processing of steps S402 to S406 for a prescribed number of times or for a prescribed time.

[0091] 4-4. Fourth example (confirmation of code with vehicle-mounted camera)

[0092] Figure 11 is a conceptual diagram for explaining a fourth example of existence confirmation processing. The fourth example differs from the third example in that a camera (vehicle-mounted camera) 12 mounted on a vehicle 10 (target vehicle) is used instead of the infrastructure camera 110 in order to read the prescribed code displayed on the user terminal 200.

[0093] Figure 12 is a flowchart showing one example of a flow of the existence confirmation processing of the fourth example. Note that, by the processing shown in Figure 12 , the features of the fourth example are reflected, and more specifically, the processing of steps S104 and S106 in Figure 4 is shown.

[0094] In Figure 12 , after step S102, the processor 140 determines whether the handover processing has been completed (step S500). In a case where the result thereof is that the handover processing has been completed (step S500: Yes), the processing proceeds to step S502.

[0095] In step S502, the processor 140 requests the user X via the user terminal 200 to display the prescribed code on the display 210 of the user terminal 200, and to present the prescribed code to the vehicle-mounted camera 12, so that the vehicle-mounted camera 12 reads the displayed prescribed code. Thereafter, the processing proceeds to step S504.

[0096] In step S504, the processor 140 communicates with the vehicle 10 in order to acquire the image I2 captured by the vehicle-mounted camera 12, and causes the vehicle-mounted camera 12 of the vehicle 10 whose handover processing has been completed to remotely work. The acquired image I2 is stored in the storage device of the vehicle 10. Thereafter, the processing proceeds to step S506. Note that, the vehicle 10 can also have a control device that has been programmed in advance instead of performing the processing of step S504, so as to acquire the image I2 to read the prescribed code presented to the vehicle-mounted camera 12.

[0097] In step S506, the processor 140 determines whether a predetermined code is displayed on the user terminal 200 based on the image I2 transmitted from the vehicle 10. If the predetermined code is displayed (step S506: Yes), the process proceeds to step S108 (see Figure 4 ). That is, when the display of the predetermined code is confirmed, it is determined that the user X exists in the predetermined range 7 until the handover process is completed. In addition, the processor 140 ends the presence confirmation process.

[0098] On the other hand, if the display of the specified code is not confirmed (step S506: No), the process proceeds to "End". It should be noted that, if the display of the specified code is not confirmed, the processor 140 may repeatedly perform the processes of steps S502 to S506 a specified number of times or for a specified time.

[0099] 4-5. Combination of multiple existence confirmation processes

[0100] It is also possible to combine two or more of the first to fourth examples above. Specifically, for example, Figure 13 As shown, the presence confirmation process may also include a "first presence confirmation process" and a "second presence confirmation process" which is executed when the presence of the user X cannot be confirmed by the first presence confirmation process.

[0101] Figure 13 1 is a flowchart showing an example of a process flow when a combination of multiple existence confirmation processes is used. More specifically, here, as an example of multiple existence confirmation processes, a combination of a first existence confirmation process and a second existence confirmation process is used. Figure 13 The processing of the flowchart shown is similar to that of Figure 4 The processing of the flowchart shown is different.

[0102] exist Figure 13 In step S600 following step S102, processor 140 executes (starts) a first existence confirmation process. The first existence confirmation process is any one of the first to fourth examples described above. Thereafter, the process proceeds to step S602.

[0103] In step S602, the processor 140 determines whether or not a situation in which the presence of the user X cannot be confirmed by the first presence confirmation processing has occurred. As the situation, for example, a situation in which the communication related to the execution of the first presence confirmation processing is poor is corresponded. In a case where as a result of the determination, the situation has occurred (step S602: YES), that is, in a case where the first presence confirmation processing is not effective, the process proceeds to step S604. On the other hand, in a case where the situation has not occurred (step S602: NO), the process proceeds to step S106.

[0104] In step S604, the processor 140 ends the first presence confirmation processing, and instead executes (starts) the second presence confirmation processing. The second presence confirmation processing is another one of the first to fourth examples described above. Thereafter, the process proceeds to step S106.

[0105] 4-5-1. First combination example

[0106] In the first combination example, the first presence confirmation processing is the presence confirmation processing (tracking) of the first example described above. Also, the second presence confirmation processing is the presence confirmation processing (confirmation of the code with the infrastructure camera) of the third example. Alternatively, the second presence confirmation processing can be the presence confirmation processing (confirmation of the code with the vehicle-mounted camera) of the fourth example.

[0107] Figure 14 is a flowchart showing one example of the flow of the first presence confirmation processing and the second presence confirmation processing of the first combination example. Note that the process shown in Figure 14 reflects the features of the first combination example, and more specifically shows the processes of steps S600 to S604 and step S106 in Figure 13 .

[0108] In the first combination example, in Figure 14 , after step S102, the processes of steps S200 to S204 are executed in order, similarly to the process shown in Figure 6 . However, in the first combination example, in a case where the user X is not sensed (step S202: NO), the process proceeds to step S400. Then, the processes of steps S400 to S406 are executed in order, similarly to the process shown in Figure 14 . Figure 10

[0109] In addition to this, in a case where the second presence confirmation processing is the presence confirmation processing (confirmation of the code with the vehicle-mounted camera) of the fourth example, in Figure 14 , the processes of steps S500 to S506 are executed (see Figure 12 ) instead of the processes of steps S400 to S406.

[0110] 4-5-2. Second combination example​

[0111] In the second combination example, the first presence confirmation process is the presence confirmation process (proximity communication) of the above-described second example. Also, the second presence confirmation process is the presence confirmation process (confirmation of the code with the infrastructure camera) of the third example. Alternatively, the second presence confirmation process can be the presence confirmation process (confirmation of the code with the on-vehicle camera) of the fourth example.

[0112] Figure 15 is a flowchart showing one example of the flow of the first presence confirmation process and the second presence confirmation process of the second combination example. Note that the process shown in Figure 15 reflects the features of the second combination example, and more specifically shows the processes of steps S600 to S604 and step S106 in Figure 13 .

[0113] In the second combination example, in Figure 15 , after step S102, the processes of step S300, step S302, and step S304 are executed in this order, as with the processes shown in Figure 8 . However, in the second combination example, in Figure 15 , in the case where the proximity communication is not continued (step S302: No), the process proceeds to step S400. Then, the processes of step S400 to step S406 are executed in this order, as with the processes shown in Figure 10 .

[0114] In addition, in the example where the second presence confirmation process is the presence confirmation process (confirmation of the code with the on-vehicle camera) of the fourth example, in Figure 15 , the processes of step S500 to step S506 (see Figure 12 ) are executed instead of the processes of step S400 to step S406.

[0115] 5. Effects

[0116] As described above, according to the present embodiment, the "presence confirmation process" is executed, which is a process of confirming the presence of the user who has gotten off from the vehicle 10 (the subject vehicle) in the prescribed range 7 adjoining the stop position 6 until the handover process is completed. Even if it is assumed that the vehicle 10 is not in an appropriate state at the time when the handover process is completed, the implementation of the additional measure for bringing the vehicle 10 into an appropriate state can be promptly (smoothly) entrusted to the user who has been confirmed to be present in the prescribed range 7 (i.e., in the vicinity of the vehicle 10). This leads to the suppression of the occurrence of a situation where the vehicle 10 is stranded in place in a state where the vehicle 10 cannot be operated. This is desirable from the viewpoint of the quality and continuity of the service by the vehicle management system 100.

[0117] In addition, each of the first and second examples (near field communication) of the presence confirmation process automatically performs presence confirmation without requiring user intervention (e.g., the user presenting a predetermined code to the camera). Therefore, the first and second examples are easier for the user to use than the third and fourth examples, which require the user to cause the camera (the infrastructure camera 110 or the vehicle-mounted camera 12) to read a predetermined code.

[0118] In addition, as referenced Figures 13-15 As shown in the examples, two or more of the first to fourth examples may be combined. By combining a plurality of presence confirmation processes, the accuracy of user presence confirmation can be further improved.

[0119] In addition, regarding a combination of multiple existence confirmation processes, the first existence confirmation process that is executed first can be called an existence confirmation process with a higher priority than the second existence confirmation process. Figure 14 In the first combination example shown, the first presence confirmation process is the first example (tracking). That is, a process that is automatically implemented without user operation is performed as the first presence confirmation process. As a result, multiple presence confirmation processes can be appropriately combined with consideration for user comfort. This is different from the second combination example (refer to Figure 15 ) is the same.

Claims

1. A vehicle management system that manages a vehicle, wherein the vehicle management system has one or more processors, the one or more processors are configured to: establish wireless communication with an object vehicle before or after the object vehicle stops at a stop position, and start handover processing that is processing of transferring an authority to operate the object vehicle from a user of the object vehicle to the vehicle management system; perform presence confirmation processing that is processing of confirming presence of the user in a prescribed range adjoining the stop position until the handover processing is completed after the user gets off the object vehicle that stops at the stop position; and in a case where it is confirmed that the user is present in the prescribed range until the handover processing is completed, notify the user that the handover processing is completed.

2. The vehicle management system according to claim 1, wherein the presence confirmation processing includes: acquiring an image captured by at least one camera that includes the prescribed range in a field of view angle; and based on the image, tracking the user after the user gets off the object vehicle, thereby confirming presence of the user in the prescribed range until the handover processing is completed.

3. The vehicle management system according to claim 1, wherein the prescribed range corresponds to a communicable range of near field communication between the object vehicle and a user terminal of the user, the presence confirmation processing includes: confirming that the near field communication between the object vehicle and the user terminal is continuing, thereby confirming presence of the user in the prescribed range until the handover processing is completed.

4. The vehicle management system according to claim 1, wherein the presence confirmation processing includes: acquiring an image captured by at least one camera that includes at least a part of the prescribed range in a field of view angle; after the handover processing is completed, requesting the user to cause the at least one camera to read a prescribed code displayed on a user terminal of the user; and based on the image, confirming that the prescribed code is displayed on the user terminal.

5. The vehicle management system according to claim 4, wherein the at least one camera includes at least one of an infrastructure camera and a vehicle-mounted camera mounted on the object vehicle.

6. The vehicle management system according to claim 1, wherein the presence confirmation processing includes: first presence confirmation processing; and second presence confirmation processing that is performed in a case where presence of the user is not confirmed by the first presence confirmation processing.

7. The vehicle management system according to claim 6, wherein the first presence confirmation processing includes: acquiring an image captured by at least one camera that includes the prescribed range in a field of view angle; and based on the image, tracking the user after the user gets off the object vehicle, thereby confirming presence of the user in the prescribed range until the handover processing is completed.

8. The vehicle management system according to claim 6, wherein the prescribed range corresponds to a communicable range of near field communication between the subject vehicle and a user terminal of the user, the first presence confirmation process includes confirming that the near field communication between the subject vehicle and the user terminal is being continuously performed, thereby confirming that the user is present in the prescribed range until the handover process is completed.

9. The vehicle management system according to any one of claims 6 to 8, wherein the second presence confirmation process includes: acquiring an image captured by at least one camera having at least one field of view that includes at least a portion of the prescribed range; after the handover process is completed, requesting the user to cause the at least one camera to read a prescribed code displayed on the user terminal of the user; and based on the image, confirming that the prescribed code is displayed on the user terminal.

10. The vehicle management system according to claim 1, wherein the subject vehicle is configured to be able to perform automatic valet parking in a parking lot, the stop position is a position at which the subject vehicle is to stop for entry into the parking lot.

11. A vehicle management method for computer management of a vehicle, wherein, the vehicle management method includes: establishing wireless communication with the subject vehicle before or after the subject vehicle stops at a stop position, and starting a handover process, wherein the handover process is a process of transferring a right to operate the subject vehicle from a user of the subject vehicle to a vehicle management system; performing a presence confirmation process, wherein the presence confirmation process is a process of confirming that the user who has gotten off the subject vehicle stopped at the stop position is present in a prescribed range adjacent to the stop position until the handover process is completed; and in a case where it is confirmed that the user is present in the prescribed range until the handover process is completed, notifying the user that the handover process is completed.

12. A computer-readable recording medium storing a vehicle management program executed by a computer that manages a vehicle, wherein the vehicle management program causes the computer to: establish wireless communication with the subject vehicle before or after the subject vehicle stops at a stop position, and start a handover process, wherein the handover process is a process of transferring a right to operate the subject vehicle from a user of the subject vehicle to a vehicle management system; perform a presence confirmation process, wherein the presence confirmation process is a process of confirming that the user who has gotten off the subject vehicle stopped at the stop position is present in a prescribed range adjacent to the stop position until the handover process is completed; and in a case where it is confirmed that the user is present in the prescribed range until the handover process is completed, notify the user that the handover process is completed.

Images