Vehicle management system, vehicle management method, and vehicle management program

Abstract

To improve the quality and continuity of services provided by a vehicle management system.SOLUTION: A vehicle management system manages vehicles. The vehicle management system includes one or more processors. The one or more processors are configured to establish wireless communication with a target vehicle before or after the target vehicle is stopped at a stopping position, initiate handover processing to transfer authority to operate the target vehicle from a user of the target vehicle to the vehicle management system, execute presence confirmation processing to confirm that the user who has gotten off the target vehicle stopped at the stopping position exists within a predetermined range adjacent to the stopping position until the handover processing is completed, and notify the user of the completion if it is confirmed that the user exists within the predetermined range until completion.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to technology for managing vehicles. [Background technology]

[0002] Patent Document 1 discloses an automated parking system that includes a server. After accepting a reservation for parking an automated vehicle from a reserving user, the server transmits an authentication code to the reserving user. When the user then checks in using the authentication code in the parking lot, the server begins issuing automated valet parking instructions to the automated vehicle of the reserving user in the parking lot.

[0003] Furthermore, Patent Document 2 discloses a method for performing automated valet parking. This method includes a step of starting the automated valet parking. This step also includes a step of an infrastructure recognizing the driver and the vehicle of the vehicle. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-064117 [Patent Document 2] Japanese Patent Publication No. 2020-075717 Summary of the Invention [Problem to be solved by the invention]

[0005] Let's consider the "handover process" that transfers the authority to operate the target vehicle from the user of the target vehicle to the vehicle management system. Basically, once the handover process is complete, the vehicle management system is permitted to operate the target vehicle. However, there may be situations where it is not appropriate for the vehicle management system to operate the target vehicle as is. In such situations, the user must take additional steps to put the target vehicle into an appropriate state. However, if the user has already left the location, the additional steps cannot be taken immediately, and the target vehicle will end up in a state where it cannot be operated. If the target vehicle cannot be moved on its own and becomes stuck in place, the service provided by the vehicle management system will be stopped. [Means for solving the problem]

[0006] A vehicle management system according to the present disclosure manages vehicles. The vehicle management system includes one or more processors. The one or more processors are configured to establish wireless communication with a target vehicle before or after the target vehicle stops at a stop position, initiate a handover process that transfers authority to operate the target vehicle from the user of the target vehicle to the vehicle management system, execute a presence confirmation process that confirms that a user who has exited the target vehicle that has stopped at the stop position remains within a predetermined range adjacent to the stop position until the handover process is completed, and notify the user of the completion when it is confirmed that the user remains within the predetermined range until the handover process is completed.

[0007] A vehicle management method according to the present disclosure is a method for a computer to manage vehicles. The vehicle management 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 to transfer authority to operate the target vehicle from a user of the target vehicle to a vehicle management system; executing a presence confirmation process to confirm that a user who has exited the target vehicle stopped at the stop position remains within a predetermined range adjacent to the stop position until the handover process is completed; and notifying the user of the completion when it is confirmed that the user remains within the predetermined range until the handover process is completed.

[0008] A vehicle management program according to the present disclosure is executed by a computer that manages vehicles. The vehicle management program causes the computer to establish wireless communication with the target vehicle before or after the target vehicle stops at a stop position, initiate a handover process that transfers authority to operate the target vehicle from the user of the target vehicle to a vehicle management system, execute a presence confirmation process that confirms that a user who has exited the target vehicle that has stopped at the stop position remains within a predetermined range adjacent to the stop position until the handover process is completed, and notify the user of the completion when it is confirmed that the user remains within the predetermined range until the handover process is completed. [Effects of the Invention]

[0009] According to the present disclosure, even if the target vehicle is not in an appropriate state when the handover process is completed, it is possible to promptly request a user who has already been confirmed to be within a predetermined range (i.e., near the target vehicle) to take additional measures to bring the target vehicle into an appropriate state. This leads to the prevention of situations in which the target vehicle becomes stuck in place without being able to be operated. This is desirable from the perspective of the quality and continuity of the service provided by the vehicle management system. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a conceptual diagram for explaining an overview of a vehicle management system according to an embodiment; [Figure 2] 1 is a block diagram showing an example of the configuration of a vehicle management system according to an embodiment; [Figure 3] FIG. 10 is a conceptual diagram for explaining a solution to the problem regarding handover processing. [Figure 4] 4 is a flowchart illustrating an example of processing executed in the vehicle management system according to the embodiment. [Figure 5] FIG. 10 is a conceptual diagram for explaining a first example of the existence confirmation process. [Figure 6]10 is a flowchart showing an example of the flow of an existence confirmation process according to the first example. [Figure 7] FIG. 10 is a conceptual diagram for explaining a second example of the existence confirmation process. [Figure 8] 10 is a flowchart showing an example of the flow of an existence confirmation process according to the second example. [Figure 9] FIG. 10 is a conceptual diagram for explaining a third example of the existence confirmation process. [Figure 10] 10 is a flowchart showing an example of the flow of an existence confirmation process according to a third example. [Figure 11] FIG. 10 is a conceptual diagram for explaining a fourth example of the existence confirmation process. [Figure 12] 10 is a flowchart showing an example of the flow of an existence confirmation process according to a fourth example. [Figure 13] 10 is a flowchart showing an example of a processing flow when a combination of multiple types of existence confirmation processing is used. [Figure 14] 10 is a flowchart showing an example of the flow of first and second existence confirmation processes according to the first combination example. [Figure 15] 10 is a flowchart showing an example of the flow of first and second existence confirmation processes according to a second combination example. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] 1. Overview of Vehicle Management System FIG. 1 is a conceptual diagram for explaining an overview of a vehicle management system 100 according to an embodiment. The vehicle management system 100 manages a 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 automated driving (unmanned driving) of the vehicle 10 within a "predetermined area." In the example shown in FIG. 1, the predetermined area is a parking lot 1. In this example, the vehicle management system 100 corresponds to an automated valet parking management system that manages automated valet parking (AVP) of the vehicle 10 in the parking lot 1. Note that the predetermined area is not limited to the parking lot 1, and may be, for example, an area within a factory. The following description will be given taking the parking lot 1 as an example of a predetermined area.

[0013] Vehicle 10 is configured to be able to execute AVP in parking lot 1. Vehicle 10 can travel automatically at least within parking lot 1 without being driven by a driver. More specifically, the automatic travel of vehicle 10 within parking lot 1 is controlled by, for example, a vehicle management system 100 that uses infrastructure cameras 110. Alternatively, the automatic travel may be controlled by, for example, cooperation between vehicle management system 100 and a control system of vehicle 10. Note that vehicle 10 may also be an automatically driven vehicle that can travel automatically outside parking lot 1.

[0014] The parking lot 1 includes a drop-off area 2, a boarding area 3, an aisle 4, and multiple parking spaces 5. A vehicle 10 entering the parking lot 1 stops at a stopping position 6 in the drop-off area 2, where the user disembarks from the vehicle 10. The stopping position 6 provided in the drop-off area 2 corresponds to an example of a "stopping position" according to the present disclosure. On the other hand, a vehicle 10 leaving the parking lot 1 stops at a boarding area 3, where the user boards the vehicle 10. The drop-off area 2 can also be called the entry area, and the boarding area 3 can also be called the exit area. The aisle 4 is the area in which the vehicle 10 travels. The parking space 5 is the space in which the vehicle 10 is parked.

[0015] The vehicle management system 100 is capable of communicating with the vehicles 10 and manages the vehicles 10. For example, the vehicle management system 100 uses an infrastructure camera 110 to grasp the position and status 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 movement instructions (e.g., entry instructions, exit instructions) to the vehicle 10 in the parking lot 1. The vehicle management system 100 may provide map information of the parking lot 1 to the vehicle 10. For example, the vehicle management system 100 generates a target route for the vehicle 10 in the parking lot 1 and remotely controls the vehicle 10 in the parking lot 1. The vehicle management system 100 may also provide information on the generated target route to the vehicle 10.

[0016] The vehicle management system 100 also manages information relating to users of the automated valet parking service (AVP service). The vehicle management system 100 is capable of communicating with a user terminal 200 operated by a user.

[0017] An example of the flow when a user X uses the AVP service will be described below. Member information of the user X is registered in the vehicle management system 100 in advance.

[0018] First, user X makes a reservation for an AVP. For example, user X operates the user terminal 200 to input information such as user X's ID information, desired parking lot 1, desired date of use, and desired time of use. The user terminal 200 transmits reservation information including the input information to the vehicle management system 100. The vehicle management system 100 performs reservation processing based on the reservation information and transmits a reservation completion notification to the user terminal 200. The vehicle management system 100 also issues authentication information according to the reservation information. The authentication information is, for example, a reservation code such as a QR (Quick Response) code (registered trademark). More specifically, the vehicle management system 100 transmits the generated authentication information to the user terminal 200. The user terminal 200 receives the authentication information and stores the received authentication information.

[0019] The entry (check-in) of the vehicle 10 into the parking lot 1 is as follows: The vehicle 10 carrying the user X arrives at the drop-off point 2 of the parking lot 1 and stops at the stop position 6. At the drop-off point 2, the user X (and other passengers, if any) get out of the vehicle 10.

[0020] When the vehicle 10 enters the parking lot 1, the vehicle management system 100 executes a "handover process" that transfers 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 executes a warehousing process for the vehicle 10. The warehousing process includes a process related to the automatic driving of the vehicle 10 toward the parking slot 5 assigned to the vehicle 10.

[0021] 2. Example of vehicle management system configuration 2 is a block diagram showing an example of the configuration of a vehicle management system 100 according to an embodiment. The vehicle management system 100 includes one or more infrastructure cameras 110 (hereinafter simply referred to as “infrastructure cameras 110”) and a management device 120.

[0022] The infrastructure cameras 110 are installed in various locations in the parking lot 1 and recognize the situation in the parking lot 1, including the drop-off area 2 and the pick-up area 3. Information acquired by the infrastructure cameras 110 is transmitted to the management device 120.

[0023] The management device 120 manages the vehicle 10 (target vehicle). The management device 120 is installed in, for example, a parking lot 1. Alternatively, the management device 120 may be, for example, a management server (cloud) that manages multiple parking lots 1. Alternatively, the management device 120 may be a combination of a local management device installed in the parking lot 1 and a management server.

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

[0025] The processor 140 executes various processes related to the management of the vehicle 10. Examples of the processor 140 include a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), and a field-programmable gate array (FPGA). The processor 140 can also be called a "circuitry" or a "processing circuitry." The "circuitry" is hardware that is programmed to realize a described function, or hardware that executes a function. The storage device 150 stores various types of information. Examples of the storage device 150 include a volatile memory, a non-volatile memory, a hard disk drive (HDD), and a solid state drive (SSD). The processor 140 reads various types of information from the storage device 150 and stores various types of information in the storage device 150.

[0026] The storage device 150 also stores information such as parking lot map information, parking lot usage information, and vehicle management information. The parking lot map information is map information of the parking lot 1. The parking lot usage information indicates the usage status (availability) of the drop-off area 2, the pick-up area 3, and the parking spaces 5 within the parking lot 1. The vehicle management information is information for managing the vehicle 10 that is the target of the AVP. For example, the vehicle management information includes a vehicle ID, user information, entry / exit time information, and location information. Each vehicle 10 is associated with the vehicle ID, user information, entry / exit time information, and location information. The vehicle ID is identification information for the vehicle 10. The user information is information about the user who uses the vehicle 10. The entry / exit time information is information about the entry / exit time of the vehicle 10. The location information indicates the location of the vehicle 10 within the parking lot 1.

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

[0028] 3. Transfer of operation authority In order for the vehicle management system 100 to start automatic driving of the vehicle 10 (target vehicle), it is necessary to transfer the authority to operate the vehicle 10 (operation authority) from the user to the vehicle management system 100. The process executed by the vehicle management system 100 (processor 140) to transfer the operation authority includes the above-mentioned handover process (authority transfer process).

[0029] 3-1.Handover processing The handover process includes a process for establishing wireless communication with the vehicle 10 and a process for identifying the vehicle 10 as a target vehicle (vehicle identification process). Identification (authentication) of the target vehicle is necessary to confirm that the vehicle 10 that is about to receive the provision of the automated driving service is the vehicle 10 of a legitimate user (target vehicle).

[0030] The vehicle management system 100 starts the handover process, for example, after the vehicle 10 stops at the stop position 6 (see FIG. 1 ) at the drop-off area 2. More specifically, the vehicle management system 100 starts the handover process after recognizing, for example, using the infrastructure camera 110, that the user has gotten off the vehicle 10. Note that the handover process may be started before the vehicle 10 (target vehicle) stops at the stop position 6, rather than after the vehicle 10 (target vehicle) stops at the stop position 6. More specifically, the vehicle management system 100 may start the handover process when the vehicle 10 is traveling in a predetermined zone located just before the stop position 6.

[0031] The vehicle identification process is started, for example, when a handover request is transmitted from the vehicle management system 100 to the vehicle 10. The method of the vehicle identification process is not particularly limited. For example, the vehicle identification process may be performed using the following action of the vehicle 10. That is, in an example of the vehicle identification process using an action, the vehicle management system 100 establishes wireless communication with the vehicle 10 and then instructs the vehicle 10 to perform a predetermined action. If the vehicle 10 is a legitimate target vehicle, the vehicle 10 is expected to perform the predetermined action in accordance with the instruction. After issuing the instruction, the vehicle management system 100 recognizes the action performed by the vehicle 10 using a sensor such as the infrastructure camera 110. Then, if the recognized action matches the expected action, the vehicle management system 100 identifies the vehicle 10 that performed the recognized action as a target vehicle. The predetermined action may be a visible action that can be detected visually, or an audible action that can be detected auditorily. Examples of visible actions include turning on or blinking headlights or brake lights, flashing turn signals, operating windshield wipers, or opening or closing a door or window. Examples of audible actions include honking the horn or starting the engine. The visible or audible action is performed in a specified operation pattern by the vehicle management system 100. The instructions of the vehicle management system 100 may also include a request to repeat a certain operation pattern. In examples using audible actions, the vehicle management system 100 may include a microphone for detecting the audible action.

[0032] 3-2.Challenges Basically, once the handover process is complete, the vehicle management system 100 is permitted to operate the vehicle 10 (target vehicle). However, there may be situations where it is not appropriate for the vehicle management system 100 to operate the vehicle 10 as is (e.g., when a window of the vehicle 10 is open, when the vehicle 10 has a low SOC (State of Charge), etc.). In such situations, the user X must take additional steps to restore the vehicle 10 to an appropriate state. However, because the handover process takes some time, it is possible that the user X has already moved far away from the parking position 6 of the vehicle 10 by the time the handover process is completed. This is particularly time-consuming when the vehicle 10 executes a predetermined action in the vehicle identification process. If the user X has already moved far away from the parking position 6 of the vehicle 10, the user X will not be able to immediately perform additional steps to restore the vehicle 10 to an appropriate state, and will be unable to operate the vehicle 10. If the user X is unable to move the vehicle 10 independently and the vehicle 10 becomes stuck, the service provided by the vehicle management system 100 will be stopped.

[0033] Countermeasures 3 is a conceptual diagram for explaining a countermeasure to the problems related to the handover process. In view of the above-mentioned problems, the processor 140 of the vehicle management system 100 according to this embodiment executes the following "presence confirmation process" in addition to the handover process. The presence confirmation process is a process for confirming that the user X who has got off the vehicle 10 (target vehicle) stopped at the stop position 6 at the drop-off point 2, as shown in FIG. 3, is present within a predetermined range 7 adjacent to the stop position 6 until the handover process is completed. Then, when it is confirmed in the presence confirmation process that the user X is present within the predetermined range 7 until the handover process is completed, the processor 140 notifies the user X of the completion of the handover process.

[0034] FIG. 4 is a flowchart showing an example of processing executed in the vehicle management system 100 according to the embodiment.

[0035] In step S100, processor 140 determines whether or not the timing to start the handover process has arrived. Specifically, in an example in which the handover process is started after vehicle 10 has stopped at stop position 6, the determination in step S100 is made, for example, based on whether or not infrastructure camera 110 has recognized that the user has gotten out of vehicle 10. On the other hand, in an example in which the handover process is started before vehicle 10 has stopped at stop position 6, the determination in step S100 is made, for example, based on whether or not vehicle 10 has entered a predetermined authority transfer zone having a certain range just before stop position 6. If processor 140 determines that the timing to start the handover process has arrived (step S100; Yes), the process proceeds to step S102.

[0036] In step S102, the processor 140 starts a handover process, which includes a process for establishing wireless communication with the vehicle 10 and a vehicle identification process.

[0037] In step S104 following step S102, the processor 140 executes (starts) a presence confirmation process. Details of the presence confirmation process will be described later. Thereafter, the process proceeds to step S106. In addition to executing the presence confirmation process, the processor 140 may notify the user X via the user terminal 200 of a request that the user X not leave the vicinity of the vehicle 10 after getting off the vehicle 10 until the handover process is completed.

[0038] In step S106, the processor 140 determines whether it has been confirmed that the user X is present within the predetermined range 7 until the completion of the handover process. As a result, if it has been confirmed that the presence of the user X has been present through the presence confirmation process until the completion of the handover process (step S106; Yes), the processor 140 notifies the user X of the completion of the handover process (step S108). Specifically, for this notification, the processor 140 may, for example, transmit information indicating the completion of the handover process to the user terminal 200. Alternatively, the processor 140 may, for example, notify the user X of the completion of the handover process using a notification device such as a speaker installed at the drop-off point 2. Furthermore, if it has been confirmed that the user's presence has been present until the completion of the handover process, the processor 140 ends the presence confirmation process. On the other hand, if it has not been confirmed that the presence of the user X has been present through the presence confirmation process until the completion of the handover process (step S106; No), the process proceeds to "END".

[0039] 4. Details of existence confirmation process Next, first to fourth examples of the existence confirmation process will be explained in order.

[0040] 4-1. First example (tracking) 5 is a conceptual diagram for explaining a first example of the presence confirmation process. In the first example, the infrastructure cameras 110 shown in FIG. 2 include at least one infrastructure camera 110 whose angle of view includes at least a part of the predetermined range 7 adjacent to the stop position 6. The at least one infrastructure camera 110 is installed, for example, at a drop-off area 2.

[0041] In a first example, the presence confirmation process includes acquiring an image I1 captured by at least one infrastructure camera 110. The presence confirmation process also includes tracking the user X after getting off the vehicle 10 (target vehicle) based on the acquired image I1, thereby confirming that the user X remains within the predetermined range 7 until the completion of the handover process. More specifically, the processor 140 detects the user X who has gotten off the vehicle 10 based on the image I1, and tracks the user X. This tracking can be performed using, for example, person re-identification (Person ReID (Re-Identification)) technology. Note that, to acquire the image I1, a camera (on-board camera) 12 (see FIG. 11 ) mounted on the vehicle 10 to recognize the situation around the vehicle 10 may be used instead of the infrastructure camera 110.

[0042] Fig. 6 is a flowchart showing an example of the flow of the existence confirmation process according to the first example. Note that, by the process shown in Fig. 6, the processes of steps S104 and S106 in Fig. 4 are more specifically expressed while reflecting the features of the first example.

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

[0044] In step S202, the processor 140 determines whether or not the user X is detected within the predetermined range 7 included in the image I1 acquired in step S200. As a result, if the user X is detected (step S202; Yes), the process proceeds to step S204. On the other hand, if the user X is not detected (step S202; No), the process proceeds to "END". Note that the process may also proceed to "END" if the determination in step S202 indicates that the user X is not detected multiple times in a row.

[0045] In step S204, the processor 140 determines whether the handover process has been completed. As a result, if the handover process has not yet been completed (step S204; No), the process returns to step S200. That is, the processor 140 acquires 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 FIG. 4). In addition, the processor 140 ends the presence confirmation process.

[0046] 4-2. Second example (short-range communication) 7 is a conceptual diagram for explaining a second example of the presence confirmation process. In the second example, the predetermined range 7 corresponds to the communication range of short-range communication (e.g., Bluetooth (registered trademark)) between the vehicle 10 (target vehicle) and the user terminal 200 of the user X.

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

[0048] Fig. 8 is a flowchart showing an example of the flow of the existence confirmation process according to the second example. Note that, by the process shown in Fig. 8, the processes of steps S104 and S106 in Fig. 4 are more specifically expressed while reflecting the features of the second example.

[0049] 8, in step S300 following step S102, the processor 140 instructs the vehicle 10 and the user terminal 200 to perform short-range communication therebetween. This instruction is executed, for example, when it is recognized using the infrastructure camera 110 that the user X has gotten off the vehicle 10. Alternatively, the instruction may be executed before the user X gets off the vehicle.

[0050] In step S302 following step S300, the processor 140 determines whether or not short-range communication is continuing between the vehicle 10 and the user terminal 200. This determination can be made, for example, based on information indicating whether or not the short-range communication is continuing, obtained from the vehicle 10 or the user terminal 200.

[0051] If the short-range communication is continuing (step S302; Yes), processor 140 determines whether the handover process is completed (step S304). As a result, if the handover process is not yet completed (step S304; No), the process returns to step S302. That is, processor 140 continues to check whether the short-range communication is continuing. On the other hand, if the handover process is completed (step S304; Yes), the process proceeds to step S108 (see FIG. 4). Furthermore, processor 140 ends the presence confirmation process.

[0052] On the other hand, if the short-range communication is not continuing (step S302; No), the process proceeds to "END". If it is determined in step S302 that the short-range communication is not continuing, the processor 140 may repeatedly execute the determination in step S302 while the interruption time of the short-range communication has not reached the predetermined time. Then, if the interruption time has reached the predetermined time, the process may proceed to "END".

[0053] 4-3. Third example (check the code with an infrastructure camera) FIG. 9 is a conceptual diagram for explaining a third example of the presence confirmation process. As in the first example, in the third example, the infrastructure cameras 110 shown in FIG. 2 include at least one infrastructure camera 110 whose angle of view includes at least a part of the predetermined range 7 adjacent to the stopping position 6. The at least one infrastructure camera 110 is installed at the drop-off location 2. For example, when reserving an AVP, a predetermined code (e.g., a reservation code such as a QR code) is transmitted from the vehicle management system 100 to the user terminal 200. Note that the transmission of the predetermined code from the vehicle management system 100 may be performed, for example, after the vehicle 10 arrives at the parking lot 1.

[0054] In the third example, the presence confirmation process includes acquiring an image I1 captured by the at least one infrastructure camera 110. The presence confirmation process also includes requesting user X to have the infrastructure camera 110 read a predetermined code displayed on user X's user terminal 200 after the handover process is completed. The presence confirmation process further includes confirming, based on image I1, that the predetermined code is displayed on the user terminal 200.

[0055] Fig. 10 is a flowchart showing an example of the flow of the existence confirmation process according to the third example. Note that, by the process shown in Fig. 10, the processes of steps S104 and S106 in Fig. 4 are more specifically expressed while reflecting the features of the third example.

[0056] 10, after step S102, processor 140 determines whether or not the handover process is completed (step S400). As a result, if the handover process is completed (step S400; Yes), the process proceeds to step S402.

[0057] In step S402, the processor 140 displays a predetermined code on the display 210 (see FIG. 9) of the user terminal 200, and requests the user X via the user terminal 200 to hold the predetermined code over the infrastructure camera 110 so that the infrastructure camera 110 can read the displayed predetermined code. Then, the process proceeds to step S404.

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

[0059] In step S406, processor 140 determines whether a predetermined code is displayed on user terminal 200, based on image I1 captured by infrastructure camera 110. As a result, if the display of the predetermined code is confirmed (step S406; Yes), the process proceeds to step S108 (see FIG. 4). That is, if the display of the predetermined code is confirmed, it is determined that user X was present within predetermined range 7 until the completion of the handover process. Furthermore, processor 140 ends the presence confirmation process.

[0060] On the other hand, if the display of the predetermined code is not confirmed (step S406; No), the process proceeds to "END." Note that if the display of the predetermined code is not confirmed, processor 140 may repeatedly execute the processes of steps S402 to S406 a predetermined number of times or for a predetermined period of time.

[0061] 4-4. Fourth example (check the code with the in-car camera) 11 is a conceptual diagram for explaining a fourth example of the presence confirmation process. The fourth example differs from the third example in that a camera (on-board camera) 12 mounted on a vehicle 10 (target vehicle) is used instead of an infrastructure camera 110 to read a predetermined code displayed on a user terminal 200.

[0062] Fig. 12 is a flowchart showing an example of the flow of the existence confirmation process according to the fourth example. Note that, by the process shown in Fig. 12, the processes of steps S104 and S106 in Fig. 4 are more specifically expressed while reflecting the features of the fourth example.

[0063] 12, after step S102, processor 140 determines whether or not the handover process is completed (step S500). As a result, if the handover process is completed (step S500; Yes), the process proceeds to step S502.

[0064] In step S502, processor 140 displays a predetermined code on display 210 of user terminal 200 and requests user X via user terminal 200 to hold the displayed predetermined code over in-vehicle camera 12 so that in-vehicle camera 12 can read it. Then, processing proceeds to step S504.

[0065] In step S504, the processor 140 communicates with the vehicle 10 and remotely activates the on-board camera 12 of the vehicle 10 for which the handover process has been completed, in order to acquire image I2 captured by the on-board camera 12. The acquired image I2 is stored in a storage device of the vehicle 10. The process then proceeds to step S506. Note that instead of performing the process of step S504, the vehicle 10 may be provided with a control device that is pre-programmed to acquire image I2 in order to read a predetermined code held over the on-board camera 12.

[0066] In step S506, processor 140 determines whether a predetermined code is displayed on user terminal 200 based on image I2 transmitted from vehicle 10. As a result, if the display of the predetermined code is confirmed (step S506; Yes), the process proceeds to step S108 (see FIG. 4). That is, if the display of the predetermined code is confirmed, it is determined that user X was present within predetermined range 7 until the completion of handover processing. Furthermore, processor 140 ends the presence confirmation process.

[0067] On the other hand, if the display of the predetermined code is not confirmed (step S506; No), the process proceeds to "END." Note that if the display of the predetermined code is not confirmed, processor 140 may repeatedly execute the processes of steps S502 to S506 a predetermined number of times or for a predetermined period of time.

[0068] 4-5. Combining multiple types of existence confirmation processes A combination of two or more of the above-described first to fourth examples is also possible. Specifically, for example, the presence confirmation process may include a "first presence confirmation process" and a "second presence confirmation process" that is executed when the presence of user X cannot be confirmed by the first presence confirmation process, as shown in Fig. 13.

[0069] Fig. 13 is a flowchart showing an example of a process flow when a combination of multiple types of presence confirmation processes is used. More specifically, here, a combination of first and second presence confirmation processes is used as an example of multiple types of presence confirmation processes. The process of the flowchart shown in Fig. 13 differs from the process of the flowchart shown in Fig. 4 in the following points.

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

[0071] In step S602, processor 140 determines whether a situation has occurred in which the presence of user X cannot be confirmed by the first presence confirmation process. For example, such a situation corresponds to a situation in which communication conditions related to the execution of the first presence confirmation process are poor. If such a situation has occurred (step S602; Yes), that is, if the first presence confirmation process is not effective, the process proceeds to step S604. On the other hand, if such a situation has not occurred (step S602; No), the process proceeds to step S106.

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

[0073] 4-5-1. First combination example In the first combination example, the first presence confirmation process is the presence confirmation process (tracking) according to the first example described above. The second presence confirmation process is the presence confirmation process according to the third example (checking the code with an infrastructure camera). Alternatively, the second presence confirmation process may be the presence confirmation process according to the fourth example (checking the code with an in-vehicle camera).

[0074] Fig. 14 is a flowchart showing an example of the flow of the first and second existence confirmation processes according to the first combination example. Note that, by the process shown in Fig. 14, the processes of steps S600 to S604 and S106 in Fig. 13 are expressed more specifically while reflecting the features of the first combination example.

[0075] In Fig. 14, after step S102, steps S200 to S204 are executed in order, similar to the process shown in Fig. 6. However, in Fig. 14, if user X is not detected (step S202; No), the process proceeds to step S400. Then, steps S400 to S406 are executed in order, similar to the process shown in Fig. 10.

[0076] In addition, in an example where the second presence confirmation process is the presence confirmation process according to the fourth example (checking the code with an on-board camera), the processes of steps S500 to S506 (see FIG. 12) are executed instead of the processes of steps S400 to S406 in FIG. 14.

[0077] 4-5-2. Second combination example In the second combination example, the first presence confirmation process is the presence confirmation process (near-field communication) according to the second example described above. The second presence confirmation process is the presence confirmation process (checking the code with an infrastructure camera) according to the third example. Alternatively, the second presence confirmation process may be the presence confirmation process (checking the code with an in-vehicle camera) according to the fourth example.

[0078] Fig. 15 is a flowchart showing an example of the flow of the first and second existence confirmation processes according to the second combination example. Note that, by the process shown in Fig. 15, the processes of steps S600 to S604 and S106 in Fig. 13 are expressed more specifically while reflecting the features of the second combination example.

[0079] In Fig. 15, after step S102, steps S300, S302, and S304 are executed in order, similar to the process shown in Fig. 8. However, in Fig. 15, if short-range communication is not continuing (step S302; No), the process proceeds to step S400. Then, steps S400 to S406 are executed in order, similar to the process shown in Fig. 10.

[0080] In addition, in an example where the second presence confirmation process is the presence confirmation process according to the fourth example (checking the code with an in-vehicle camera), the processes of steps S500 to S506 (see FIG. 12) are executed instead of the processes of steps S400 to S406 in FIG. 15.

[0081] 5.Effects As described above, according to this embodiment, a "presence confirmation process" is executed to confirm that a user who has exited the vehicle 10 (target vehicle) is present within the predetermined range 7 adjacent to the stopping position 6 until the handover process is completed. Even if the vehicle 10 is not in an appropriate state when the handover process is completed, it is possible to promptly (smoothly) request a user who has already been confirmed to be present within the predetermined range 7 (i.e., near the vehicle 10) to take additional measures to bring the vehicle 10 into an appropriate state. This leads to the prevention of situations in which the vehicle 10 becomes stuck on the spot without being able to operate it. This is desirable from the viewpoint of the quality and continuity of the services provided by the vehicle management system.

[0082] In addition, according to the first example (tracking) and the second example (short-range communication) of the presence confirmation process, the presence confirmation process is performed automatically without any user operation (e.g., the user holding a predetermined code over the camera). Therefore, the first or second example is easier for the user than the third and fourth examples, which require the user to have the camera (infrastructure camera 110 or in-vehicle camera 12) read the predetermined code.

[0083] Furthermore, it is also possible to combine two or more of the first to fourth examples, as illustrated with reference to Figures 13 to 15. By combining a plurality of types of presence confirmation processes, the accuracy of confirming the presence of a user is further improved.

[0084] In addition, with regard to the combination of multiple types of presence confirmation processes, the first presence confirmation process, which is executed primarily, can be said to be a presence confirmation process with a higher priority than the second presence confirmation process. In the first combination example shown in FIG. 14, the first presence confirmation process is the first example (tracking). That is, a process that is performed automatically without requiring user operation is executed as the first presence confirmation process. This makes it possible to appropriately combine multiple types of presence confirmation processes while taking user comfort into consideration. The same is true for the second combination example (see FIG. 15) in which the first presence confirmation process is the second example (near field communication). [Explanation of symbols]

[0085] 1 Parking lot, 2 Drop-off area, 6 Stop position, 7 Predetermined range, 10 Vehicle (target vehicle), 12 In-vehicle camera, 100 Vehicle management system, 110 Infrastructure camera, 120 Management device, 130 Communication device, 140 Processor, 150 Storage device, 200 User terminal, 210 Display

Claims

1. A vehicle management system for managing vehicles, one or more processors; the one or more processors: before or after the target vehicle stops at a stop position, establish wireless communication with the target vehicle, and start a handover process to transfer the authority to operate the target vehicle from the user of the target vehicle to the vehicle management system; performing a presence confirmation process to confirm that the user who has gotten out of the target vehicle that has stopped at the stop position is present within a predetermined range adjacent to the stop position until the handover process is completed; If it is confirmed that the user is within the predetermined range until the completion, the user is notified of the completion. It was configured as Vehicle management system.

2. The vehicle management system according to claim 1, The existence confirmation process includes: acquiring an image captured by at least one camera having an angle of view that includes the predetermined range; confirming that the user remains within the predetermined range until the completion by tracking the user after getting out of the target vehicle based on the image; Contains Vehicle management system.

3. The vehicle management system according to claim 1, the predetermined range corresponds to a communication range of short-range communication between the target vehicle and the user terminal of the user, The presence confirmation process includes confirming that the user is present within the predetermined range until the completion by confirming that the short-range communication between the target vehicle and the user terminal is continuing. Vehicle management system.

4. The vehicle management system according to claim 1, The existence confirmation process includes: acquiring an image captured by at least one camera having an angle of view that includes at least a part of the predetermined range; after said completion, requesting said user to have said at least one camera read a predetermined code displayed on said user's user terminal; confirming, based on the image, that the predetermined code is displayed on the user terminal; Contains Vehicle management system.

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

6. The vehicle management system according to claim 1, The existence confirmation process includes: a first existence confirmation process; a second presence confirmation process that is executed when the presence of the user cannot be confirmed by the first presence confirmation process; Contains Vehicle management system.

7. The vehicle management system according to claim 6, The first existence confirmation process includes: acquiring an image captured by at least one camera having an angle of view that includes the predetermined range; confirming that the user remains within the predetermined range until the completion by tracking the user after getting out of the target vehicle based on the image; Contains Vehicle management system.

8. The vehicle management system according to claim 6, the predetermined range corresponds to a communication range of short-range communication between the target vehicle and the user terminal of the user, The first presence confirmation process includes confirming that the user is present within the predetermined range until the completion by confirming that the short-range communication between the target vehicle and the user terminal is continuing. Vehicle management system.

9. 9. A vehicle management system according to claim 6, wherein: The second existence confirmation process includes: acquiring an image captured by at least one camera having an angle of view that includes at least a part of the predetermined range; after said completion, requesting said user to have said at least one camera read a predetermined code displayed on said user's user terminal; confirming, based on the image, that the predetermined code is displayed on the user terminal; Contains Vehicle management system.

10. The vehicle management system according to claim 1, The target vehicle is configured to be able to perform automated valet parking in a parking lot, The stop position is a position where the target vehicle entering the parking lot stops. Vehicle management system.

11. A vehicle management method for managing vehicles by a computer, comprising: Before or after the target vehicle stops at a stop position, establish wireless communication with the target vehicle and start a handover process to transfer the authority to operate the target vehicle from the user of the target vehicle to a vehicle management system; executing a presence confirmation process to confirm that the user who has gotten out of the target vehicle that has stopped at the stop position is present within a predetermined range adjacent to the stop position until the handover process is completed; notifying the user of the completion when it is determined that the user remains within the predetermined range until the completion; Contains Vehicle management methods.

12. A vehicle management program executed by a computer that manages vehicles, Before or after the target vehicle stops at a stop position, establish wireless communication with the target vehicle and start a handover process to transfer the authority to operate the target vehicle from the user of the target vehicle to a vehicle management system; executing a presence confirmation process to confirm that the user who has gotten out of the target vehicle that has stopped at the stop position is present within a predetermined range adjacent to the stop position until the handover process is completed; notifying the user of the completion when it is determined that the user remains within the predetermined range until the completion; causing the computer to execute Fleet management program.

Images