Automatic valet parking management system

Abstract

An automatic valet parking management system that manages automatic valet parking in a parking lot is provided with one or more processors. The one or more processors are configured to, when a vehicle corresponding to automatic valet parking arrives at the parking lot, determine whether the vehicle has made a use reservation of automatic valet parking, retrieve vacancy information of a reservation of a parking frame of the parking lot if the use reservation is not made, and, if the reservation of the parking frame is vacant, determine whether the vehicle has made a use reservation of automatic valet parking. A user is notified of a use suggestion for automatic valet parking via a terminal device operated by the user of a vehicle.

Description

Technical Field

[0001] The present disclosure relates to a technology for managing Automated Valet Parking (AVP) in a parking lot. Background Art

[0002] Japanese Patent Application Laid-Open No. 2020-201666 discloses a parking control device that performs parking control to park a vehicle in a parking area with a reserved entry time, namely, a reserved parking area. If a vehicle with a reserved entry time arrives at the parking lot before the reserved entry time, the parking control device determines whether parking is available in the reserved parking area. If the result indicates that parking is not available in the reserved parking area, the parking control device parks the vehicle in the temporary parking area if parking is available in a temporary parking area different from the reserved parking area. Summary of the Invention

[0003] The technology described in Japanese Patent Application Laid-Open No. 2020-201666 targets vehicles that have made reservations and does not envision a situation where a vehicle supporting automatic valet parking (AVP) arrives at a parking lot supporting AVP without making a reservation for use of AVP.

[0004] The present disclosure has been made in view of the above-mentioned problems, and an object of the present disclosure is to improve the convenience for a user of a vehicle that arrives at a parking lot without making a reservation for use of automatic valet parking.

[0005] The automatic valet parking management system according to the present disclosure manages automatic valet parking in a parking lot. The automated valet parking management system includes one or more processors. One or more processors are configured as: When a vehicle that supports automatic valet parking arrives at a parking lot, it is determined whether the vehicle has made a reservation for automatic valet parking. If no reservation has been made, the vacancy information of the reserved parking space in the parking lot is retrieved. When there is a vacancy in the reserved parking frame, a user is notified of a recommendation to use the automatic valet parking via a terminal device operated by the user of the vehicle.

[0006] According to the automated valet parking management system of the present disclosure, when a vehicle corresponding to automated valet parking (AVP) arrives at a parking lot without a prior reservation for AVP use, the automated valet parking management system automatically retrieves information about available parking spaces for the AVP. If a space is available, the automated valet parking management system notifies the user via a terminal device of a recommendation to use the AVP. Consequently, if a user of a vehicle arriving at the parking lot wishes to use the AVP, the user does not need to perform reservation operations, including confirming the availability of a parking space, at the parking lot. This improves convenience for users of vehicles arriving at the parking lot without an AVP reservation. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which like reference numerals represent like parts, and in which: Figure 1 This is a diagram schematically showing an example of the configuration of an automatic valet parking management system according to the embodiment. Figure 2 This is a flowchart illustrating an example of processing of the automatic valet parking management system according to the embodiment. Figure 3 This is a diagram showing a display example of usage advice on a display screen of an HMI mounted on a vehicle. Figure 4 This is a diagram showing a display example of usage advice on a display screen of a user terminal. Figure 5 This is a flowchart illustrating another example of the processing of the automatic valet parking management system according to the embodiment. Figure 6 This is a flowchart illustrating another example of the processing of the automatic valet parking management system according to the embodiment. DETAILED DESCRIPTION

[0008] Embodiments of the present disclosure will be described with reference to the accompanying drawings. 1. Composition of the Automatic Valet Parking Management System

[0009] Figure 1 1 is a diagram schematically showing an example of a configuration of an automatic valet parking management system 100 according to the embodiment. The automatic valet parking (AVP) management system 100 manages the AVP of the vehicle 10 in the parking lot 1 .

[0010] The vehicle 10 is a vehicle corresponding to the AVP in the parking lot 1. The vehicle 10 is capable of automatically driving at least within the parking lot 1 without relying on the driving operation performed by the driver. In more detail, the vehicle 10 is equipped with an identification sensor (such as a camera) for identifying the surrounding conditions. The vehicle 10 automatically drives within the parking lot 1 while using the identification sensor to identify the surrounding conditions. The vehicle 10 may also be an autonomous driving vehicle that can also automatically drive outside the parking lot 1. In addition, the vehicle 10 is equipped with a Human Machine Interface (HMI) 12 as an interface with the user (passenger) of the vehicle 10. The HMI 12 is, for example, a touch panel. The HMI 12 may also include a speaker. The HMI 12 is equivalent to an example of a "terminal device" involved in the present disclosure.

[0011] Parking lot 1 includes a disembarkation area 2, a boarding area 3, an aisle 4, and a plurality of parking frames 5. Vehicles 10 entering parking lot 1 stop in disembarkation area 2, where users disembark from vehicles 10. Meanwhile, vehicles 10 exiting parking lot 1 stop in boarding area 3, where users board vehicles 10. The disembarkation area 2 may also be referred to as an entry area, and the boarding area 3 as an exit area. The aisle 4 is the area where vehicles 10 travel. The parking frames 5 are spaces where vehicles 10 are parked. For example, the parking frames 5 are divided by demarcation lines. Alternatively, parking lot 1 may be an AVP-only parking lot for AVP vehicles 10, or it may be a parking lot that can also be used by AVP vehicles 10 and vehicles that do not utilize the AVP function.

[0012] exist Figure 1 In the example shown, AVP management system 100 includes one or more infrastructure sensors 20 (hereinafter referred to as "infrastructure sensors 20"), a local management device 30, and a management server 40. Local management device (or simply "management device") 30 is installed in parking lot 1. Management server (cloud) 40 manages multiple parking lots 1. In the example of AVP management system 100, various processes related to AVP management, described below, are executed through collaboration between management device 30 and cloud 40.

[0013] Infrastructure sensor 20, which includes, for example, a camera, recognizes the conditions of parking lot 1. More specifically, infrastructure sensor 20 recognizes the conditions surrounding vehicle 10 within parking lot 1 (e.g., obstacles such as pedestrians and other vehicles). Infrastructure sensor 20 also recognizes the availability of parking spaces 5. Information acquired by infrastructure sensor 20 is transmitted to local management device 30. Infrastructure sensor 20 is an example of a "recognition sensor" as used herein.

[0014] The local management device 30 includes a communication device 32, one or more processors 34 (hereinafter referred to as processors 34), and one or more storage devices 36 (hereinafter referred to as storage devices 36). The communication device 32 communicates with the vehicle 10 and the management server 40 via a communication network.

[0015] The processor 34 performs various processes related to the management of the AVP. Examples of the processor 34 include a CPU, a GPU, an ASIC, and an FPGA. The processor 34 may also be referred to as circuitry or processing circuitry. Circuitry is hardware programmed to implement the described functions or hardware that performs functions. The storage device 36 stores various information. Examples of the storage device 36 include a volatile memory, a non-volatile memory, an HDD, an SSD, and the like. The functions of the management device 30 may also be implemented by collaborating with the processor 34 that executes the first management program and the storage device 36. The first management program is stored in the storage device 36. Alternatively, the first management program may be recorded on a computer-readable recording medium. The first management program may also be provided via a network.

[0016] The management server (cloud) 40 includes a communication device 42, one or more processors 44 (hereinafter referred to as processors 44), and one or more storage devices 46 (hereinafter referred to as storage devices 46). The communication device 42 communicates with the vehicle 10, the management device 30, and a user terminal 50 via a communication network. The user terminal 50 is a terminal (e.g., a smartphone) held by the user of the vehicle 10 and is another example of a "terminal device" as used herein.

[0017] The processor 44 performs various processes related to the management of the AVP. Examples of the processor 44 include a CPU, a GPU, an ASIC, and an FPGA. The processor 44 may also be referred to as circuitry or processing circuitry. Circuitry is hardware programmed to implement the described functions or hardware that performs the functions. The storage device 46 stores various information. Examples of the storage device 46 include volatile memory, non-volatile memory, HDD, and SSD. The functions of the cloud 40 may also be implemented by collaborating with the processor 44 that executes the second management program and the storage device 46. The second management program is stored in the storage device 46. Alternatively, the second management program may be recorded on a computer-readable recording medium. The second management program may also be provided via a network.

[0018] The AVP management system 100 executes “various processes related to AVP management” as described below, for example, through the cooperation of the management device 30 and the cloud 40 .

[0019] The cloud 40 manages information (user information) related to each user of the AVP service (AVP service). The user information includes membership information and next reservation information of each user registered in advance.

[0020] When a user X makes an AVP reservation, he or she operates a user terminal 50 and enters user X's ID information (identification information), the desired parking lot 1, the desired date of use, the desired time of use (scheduled check-in and check-out times), and other information. The user terminal 50 transmits reservation information including the input information to the cloud 40 (AVP management system 100). The cloud 40's storage device 46 stores the latest available parking space information obtained from the management device 30. Upon receiving the reservation information from user X, the cloud 40 performs a reservation process based on the reservation information if a parking space 5 in the parking lot 1 (more specifically, a parking space 5 for the AVP) is available. This reservation process involves allocating the available parking space 5 to the vehicle 10, i.e., reserving the parking space 5 for the vehicle 10. Upon completion of the reservation process, the cloud 40 transmits a reservation completion notification to the user terminal 50. The "terminal device" used for reservations described herein may also be the HMI 12.

[0021] When a vehicle 10 carrying user X arrives at the drop-off area 2 of the parking lot 1, the management device 30 detects the arrival of the vehicle 10 using the infrastructure sensor 20. At this point, the management device 30 performs processing to identify the arrived vehicle 10. Specifically, the management device 30 uses the infrastructure sensor 20, for example, to identify the license plate number of the vehicle 10. The license plate number is an example of identification information for the vehicle 10. The management device 30 transmits information indicating the arrival of the vehicle 10 along with the identification information to the cloud 40. The storage device 46 of the cloud 40 stores the identification information of each vehicle 10 using the AVP service. The cloud 40 identifies the vehicle 10 that has arrived at the drop-off area 2 by, for example, comparing the identification information received from the management device 30 with the identification information stored in the storage device 46. The cloud 40 then identifies the user of the identified vehicle 10 based on the user information.

[0022] Based on this, the cloud 40 determines whether the arriving vehicle 10 has an AVP reservation based on the reservation information. Furthermore, the cloud 40 executes a process requesting user X's consent for remote operation of the vehicle 10 by the AVP management system 100 for parking the vehicle 10 with the AVP reservation. When the cloud 40 receives information indicating user X's consent (e.g., a request to start AVP) via the user terminal 50 or the HMI 12, the operation authority for the vehicle 10 is transferred from user X to the AVP management system 100. The AVP management system 100 then performs parking processing related to the vehicle 10.

[0023] The parking process includes processing related to parking control of the vehicle 10 for parking the vehicle 10 in the reserved parking box 5. During parking control, the management device 30 obtains information from the infrastructure sensor 20 indicating the conditions surrounding the vehicle 10 in the parking lot 1 (e.g., obstacles such as pedestrians and other vehicles). Based on this information, the management device 30 generates a target driving path from the unloading area (parking area) 2 to the parking box 5 assigned to the vehicle 10. The management device 30 then communicates with the vehicle 10 and remotely controls the vehicle 10 to drive along the generated target driving path. Alternatively, in another example of parking control, the AVP management system 100 may also transmit the target driving path information to the vehicle 10 along with the information about the parking box 5 assigned to the vehicle 10 and the map information of the parking lot 1. The vehicle 10 may then use recognition sensors such as cameras mounted on the vehicle 10 to automatically drive along the received target driving path.

[0024] The management device 30 uses the infrastructure sensor 20 to detect that the vehicle 10 has completed parking. Alternatively, the vehicle 10 may notify the management device 30 of the completion of parking. After parking is complete, the management device 30 communicates with the vehicle 10 and stops the vehicle 10 (disconnects the power). The cloud 40, having received the information indicating the completion of parking for the vehicle 10 from the management device 30, stores the information about the parking frame 5 of the vehicle 10 in association with the user X.

[0025] The process of unloading a vehicle 10 from parking lot 1 is performed, for example, as follows. Specifically, in response to an unloading request from user X operating user terminal 50, cloud 40 executes a process requesting user X's consent for remote operation of vehicle 10 by the AVP management system 100. Upon receiving information indicating user X's consent (e.g., a request to initiate unloading of vehicle 10) via user terminal 50, cloud 40 communicates with vehicle 10 and starts vehicle 10 (powering on). Then, in the unloading process, management device 30 generates a target driving route from parking frame 5 to boarding area (unloading area) 3 based on information from infrastructure sensors 20, similar to the loading process. Management device 30 then communicates with vehicle 10, remotely controlling vehicle 10 to drive according to the generated target driving route. When vehicle 10 arrives at boarding area 3 and stops, the operating authority for vehicle 10 is transferred from AVP management system 100 to user X. After passengers including the user X board the vehicle 10 , the vehicle 10 departs toward the next destination. 2. Measures for vehicles arriving without an AVP reservation

[0026] In order to secure a parking frame, the use of the AVP service requires a reservation. Therefore, if a vehicle corresponding to the AVP arrives at a parking lot corresponding to the AVP without a reservation for the use of the AVP, the following issues will arise if no special consideration is given. That is, the user of the arrived vehicle needs to perform reservation operations including confirmation of the availability of the parking frame in the disembarkation area (entry area) of the parking lot. As a result, the use of the AVP may be inconvenient for the user. In addition, congestion may occur in the disembarkation area. Furthermore, sometimes the parking lot that the user arrives at is a parking lot where both parking using the AVP and parking based on user driving can be performed. In this case, even if the user intends to use the AVP service, he or she may not realize that the AVP can be used, and thus park by driving himself or herself.

[0027] Therefore, when a vehicle 10 corresponding to an AVP arrives at the drop-off area 2 of the parking lot 1, the AVP management system 100 according to this embodiment determines whether the vehicle 10 has made an AVP usage reservation. If no AVP usage reservation has been made, the cloud 40 searches for vacant parking spaces 5 in the parking lot 1. The parking spaces 5 for which vacant parking information is searched are those that can be used with the AVP. If a parking space 5 is available, the cloud 40 notifies the user of an AVP usage recommendation via a "terminal device." The terminal device used to notify the user of the usage recommendation is at least one of the HMI 12 and the user terminal 50. 2-1. Example of Processing by the AVP Management System

[0028] Figure 2 1 is a flowchart showing an example of processing of the AVP management system 100 according to the embodiment. This flowchart is executed by, for example, cooperation between the management device 30 and the cloud 40 that communicate with each other.

[0029] In S100, the management device 30 (processor 34) determines whether the vehicle 10 corresponding to the AVP has arrived at the parking lot 1 corresponding to the AVP. More specifically, the management device 30 uses, for example, the infrastructure sensor 20 to determine whether the vehicle 10 has arrived at the parking lot 1. If the result is that the vehicle 10 has arrived at the parking lot 1 (S100: Yes), the process proceeds to S102.

[0030] In S102, the cloud 40 (processor 44) determines whether the AVP usage of the vehicle 10 is reserved. This determination is made based on the reservation information stored in the storage device 46. If the result is that the AVP usage is reserved (S102: "Yes"), the process proceeds to S112. On the other hand, if the AVP usage is not reserved (S102: "No"), the process proceeds to S104.

[0031] In S104, the cloud 40 determines whether the AVP parking frame 5 reservation is available. Specifically, the cloud 40 autonomously searches for available parking frame 5 information. This determination (search) is performed based on the available parking frame 5 information stored in the storage device 46. If the result indicates that the AVP parking frame 5 reservation is not available (S104: No), the process ends. On the other hand, if the AVP parking frame 5 reservation is available (S104: Yes), the process proceeds to S106.

[0032] In S106, the cloud 40 notifies the user of the vehicle 10 of the "usage suggestion" of the AVP. This notification is performed on the "terminal device", that is, at least one of the HMI 12 and the user terminal 50. The notification of the usage suggestion is as follows Figure 3 and Figure 4 As shown in the example, the usage suggestion is displayed on the display of the terminal device. Alternatively, the usage suggestion may be notified by sound through the speaker of the terminal device instead of displaying it on the display, or by sound through the speaker of the terminal device in addition to displaying it on the display.

[0033] Figure 3 An example of a display of usage advice on the display screen 12a of the HMI 12 mounted on the vehicle 10 is shown. In this display example, the usage advice includes the text "XX Airport P1" as an example of the name of the parking lot 1, and the message "AVP available" as an example of "information indicating that a parking space 5 is available for reservation." Alternatively, the "information indicating that a parking space 5 is available for reservation" may include, for example, the message "Parking space for AVP available." Furthermore, in this display example, the usage advice includes the message "Do you want to make a reservation?", the display of a "Reserve button," and the display C of a "button to close the screen" as an example of "information for confirming the user's intention to use the AVP." Alternatively, the display C of the "button to close the screen" may be replaced with, for example, a button accompanied by the text "Do not reserve." Furthermore, in the example of usage advice based solely on voice, the "information for confirming the user's intention to use the AVP" may simply include, for example, the message "Do you want to make a reservation?"

[0034] Figure 4An example of a display of usage advice on screen 50a of the display of user terminal 50 is shown. In this display example, similar to the example of the display on HMI 12, the usage advice includes the text "XX Airport P1" and the message "AVP Available" as an example of "information indicating that a parking space 5 is available for reservation." Alternatively, the "information indicating that a parking space 5 is available for reservation" may include, for example, the message "Parking space for AVP Available." Furthermore, in this display example, the usage advice includes the message "Do you want to make a reservation?", the display of a "Reserve button," and the display C of a "Close screen button" as an example of "information for confirming the user's intention to use the AVP." Alternatively, instead of the display C of the "Close screen button," a button accompanied by the text "Do not reserve" may be displayed. Furthermore, in the example of usage advice based solely on voice, the "information for confirming the user's intention to use the AVP" may simply include, for example, the message "Do you want to make a reservation?"

[0035] In S108 following S106, the cloud 40 determines whether the user of the vehicle 10 intends to use the AVP. This determination is made based on the content of the user's answer to the usage suggestion. Specifically, for example, when the user operates the HMI 12 or the user terminal 50 and touches the "reservation button", the cloud 40 determines that the user intends to use the AVP. As a result, the processing enters S110. On the other hand, for example, when the user operates the HMI 12 or the user terminal 50 and touches the "button to close the screen" or the "button with the text "no reservation", the cloud 40 determines that the user does not intend to use the AVP. As a result, the processing enters the end. In addition, the "terminal device" such as the HMI 12 and the user terminal 50 may also have a voice recognition function. In addition, the terminal device can use the voice recognition function to accept the user's answer to the usage suggestion.

[0036] In S110, the cloud 40 executes processing related to reservation of use of the AVP. This processing includes allocating a vacant parking frame 5 for the AVP to the vehicle 10, that is, reserving the parking frame 5 for the vehicle 10. The process then proceeds to S112.

[0037] In S112, the management device 30 starts the above-mentioned parking control in order to park the vehicle 10 in the reserved parking frame 5. Then, the process proceeds to S114.

[0038] In S114, the management device 30 uses information from the infrastructure sensor 20 and the like to determine whether the parking of the vehicle 10 has been completed. In other words, it determines whether the vehicle 10 has been parked in the reserved parking space 5. If the result indicates that the parking has been completed (S114: YES), the process proceeds to S116.

[0039] In S116 , the cloud 40 sets the status of the AVP service for the vehicle 10 that has completed parking to “waiting for parking.” The process then ends. 2-2. Effect

[0040] As described above, according to this embodiment, when a vehicle 10 corresponding to an AVP arrives at the drop-off area 2 of a parking lot 1 without a prior reservation for AVP use, the AVP management system 100 automatically retrieves information about available parking spaces 5 corresponding to the AVP. If a reservation is available, the AVP management system 100 notifies the user of a recommendation to use the AVP via a terminal device such as the HMI 12. Consequently, when a user of a vehicle 10 arriving at parking lot 1 wishes to use the AVP, the user does not need to perform reservation operations, including confirming the availability of parking spaces 5, in parking lot 1 (more specifically, the drop-off area 2). This simplifies the operations required for a user of a vehicle 10 arriving at parking lot 1 without an AVP reservation to begin using the AVP. Consequently, user convenience in using the AVP service is improved.

[0041] Furthermore, the spontaneous retrieval of vacancy information and use recommendations by the AVP management system 100 according to this embodiment allows for more rapid AVP reservations in the drop-off area 2, compared to an example where a user performs a reservation operation in the parking lot 1 (drop-off area 2), including confirming the availability of the parking frame 5. Consequently, congestion in the drop-off area 2 caused by the arrival of vehicles 10 without reservations can be reduced.

[0042] Furthermore, if the parking lot 1 that the user arrives at is one that allows both AVP parking and user-driven parking, the following effects can be achieved by providing the aforementioned usage suggestions. Specifically, if the user intends to use the AVP service but is unaware that AVP is available in that parking lot 1, the usage suggestion can help the user realize that AVP is available. This helps promote AVP usage. Furthermore, if the AVP service is provided for a fee, it can help increase the revenue of the AVP service provider. 2-3. Examples of restrictions on notifications using recommendations

[0043] As described above, the "usage suggestions" of this embodiment contribute to improving user convenience related to AVP usage. On the other hand, some users may find receiving notifications of usage suggestions annoying. More specifically, for example, if a user arrives at a parking lot 1 where both AVP parking and user-driven parking are possible, some users may wish to park their vehicle 10 themselves. Therefore, notifications of "usage suggestions" may be limited as follows. 2-3-1. First specific example

[0044] Figure 5 This is a flowchart showing another example of the processing of the AVP management system 100 according to the embodiment. This flowchart is similar to the above flowchart in that the processing of S200 and S202 is added. Figure 2 The flowchart shown is different.

[0045] exist Figure 5 If the user does not intend to use the AVP (S108: No), that is, if a user rejects the usage suggestion via the terminal device (e.g., user terminal 50), the process proceeds to S200. In S200, the cloud 40 stores the user's rejection of the usage suggestion as a history in the storage device 46. This rejection history is one of the aforementioned user information stored for each user. The process then ends.

[0046] In addition, Figure 5 If there is a vacant reservation for the AVP parking frame 5 (S104: Yes), the process proceeds to S202. In S202, the cloud 40 determines whether the user who is the subject of the process in the currently executing flowchart has a history of declining usage recommendations based on the user information stored in the storage device 46. This determination is performed based on the user information stored in the storage device 46.

[0047] If there is no history of declining the use recommendation (S202: No), the process proceeds to S106, where the use recommendation is notified. On the other hand, if there is a history of declining the use recommendation (S202: Yes), the process ends. In other words, the cloud 40 does not notify the user of the vehicle 10 that has recently arrived at the parking lot 1 of the use recommendation.

[0048] According to the first specific example described above, if a vehicle 10 boarded by a user who has previously declined a recommendation for use arrives again at the same parking lot 1 without an AVP reservation, the cloud 40 will not notify the user of the recommendation for use, even if a vacant parking space 5 for the AVP is available. Thus, according to the first specific example, user convenience related to the use of the AVP service can be improved while also taking into account users who do not wish to use the recommendation.

[0049] In addition, the vehicle 10 that a user takes when using the parking lot 1 corresponding to the AVP is not always the same. Therefore, restrictions on usage suggestions for users who have rejected usage suggestions may apply only to the vehicle 10 that the user actually boarded when rejecting the suggestion. Alternatively, the restrictions may apply not only to the vehicle 10 that the user actually boarded when rejecting the suggestion, but to all vehicles 10 that the user has boarded. 2-3-2. Second specific example

[0050] Figure 6 This is a flowchart showing another example of the processing of the AVP management system 100 according to the embodiment. Figure 2 The flowchart shown is different.

[0051] In the second specific example, the "Usage Suggestion" notification has a customizable function as described below. Specifically, the cloud 40 is configured so that users who deem usage suggestions unnecessary can disable the usage suggestion notification function by operating a terminal device such as the HMI 12 or the user terminal 50. In the second specific example, the aforementioned user information stored in the storage device 46 of the cloud 40 includes status information indicating the status (on or off) of the usage suggestion notification function. For example, if a user disables the usage suggestion notification function, the cloud 40 updates the user's status information to indicate that the usage suggestion notification function is disabled.

[0052] exist Figure 6 If there is no AVP usage reservation (S102: No), the process proceeds to S300. In S300, the cloud 40 determines whether the user who is the subject of the process in the currently executing flowchart has set the usage recommendation notification function to off. This determination is made based on the aforementioned status information stored in the storage device 46.

[0053] If the usage recommendation notification function is on (S300: No), the process proceeds to S104 to determine whether AVP parking frame 5 is available. On the other hand, if the usage recommendation notification function is off (S300: Yes), the process ends. In other words, regardless of whether AVP parking frame 5 is available, cloud 40 does not notify the user of vehicle 10 arriving at parking lot 1 of usage recommendations.

[0054] According to the second specific example described above, if the user has disabled the notification function for usage recommendations, that is, if the user has previously received a request from the user via a terminal device (e.g., user terminal 50) indicating that notification of usage recommendations is not desired, the cloud 40 restricts notification of usage recommendations as follows. Specifically, the cloud 40, targeting all parking lots 1 providing AVP services based on the AVP management system 100, does not notify the user of usage recommendations when the vehicle 10 boarding the user arrives at the drop-off area 2 of the parking lot 1 without an AVP usage reservation. Thus, according to the second specific example, user convenience related to the use of AVP services can be improved while also taking into account users who do not wish to use recommendations.

[0055] In addition, a user may not always use the same vehicle 10 when using the parking lot 1 corresponding to the AVP. Therefore, restrictions on usage suggestions for a user who has disabled the notification function for usage suggestions may apply to all vehicles 10 used by the user. Alternatively, the restrictions may apply to a vehicle 10 specified by the user.

Claims

1. An automatic valet parking management system that manages automatic valet parking in a parking lot. The automatic valet parking management system has one or more processors. The one or more processors are configured to: When a vehicle corresponding to the automatic valet parking system arrives at the parking lot, determining whether the vehicle has made a reservation for using the automatic valet parking system; If the use reservation has not been made, the vacancy information of the reserved parking frame of the parking lot is retrieved, When there is a vacancy in the reserved parking frame, a user of the vehicle is notified of a use recommendation for the automatic valet parking via a terminal device operated by the user.

2. The automatic valet parking management system according to claim 1, wherein: The usage suggestion includes information indicating that a reservation of the parking frame is available and information for confirming whether or not there is an intention of the user to use the automatic valet parking.

3. The automatic valet parking management system according to claim 1 or 2, wherein: When a response rejecting the usage suggestion is received from the user via the terminal device, Even if the vehicle boarded by the user who rejected the usage suggestion arrives at the same parking lot again without a reservation for the automatic valet parking, the one or more processors do not notify the user of the usage suggestion.

4. The automatic valet parking management system according to claim 1 or 2, wherein: In a case where a request indicating that the notification of the use recommendation is not required is received in advance from the user via the terminal device, the one or more processors do not notify the user of the use recommendation when the vehicle carrying the user arrives at the parking lot without a reservation for the use of the automatic valet parking service, targeting all parking lots that provide the automatic valet parking service based on the automatic valet parking management system.

Images