Automatic valet parking management system

Abstract

To improve convenience for a user of a vehicle arriving at a parking lot without a utilization reservation of automatic valet parking.SOLUTION: An automatic valet parking management system manages automatic valet parking in a parking lot. The automatic valet parking management system comprises one or more processors. The one or more processors determine whether or not utilization of automatic valet parking with a vehicle corresponding to the automatic valet parking is reversed when the vehicle arrives at the parking lot, retrieve availability information on reservations of parking frames in the parking lot when the utilization is not reserved, and notify a user of the vehicle of a utilization proposal of the automatic valet parking via a terminal device which is operated by the user when there is an available reservation of a parking lot.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to a technique for managing automated valet parking (AVP) in a parking lot. [Background technology]

[0002] Patent Document 1 discloses a parking control device that performs parking control to park a vehicle in a reserved parking area, which is a parking area for which an entry time has been reserved. When a reserved vehicle arrives at a parking lot before the reserved entry time, the parking control device determines whether parking is available in the reserved parking area. If the reserved parking area is not available, the parking control device parks the vehicle in a temporary parking area other than the reserved parking area if parking is available. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-201666 Summary of the Invention [Problem to be solved by the invention]

[0004] The technology described in Patent Document 1 is intended for reserved vehicles and does not assume that a vehicle compatible with automated valet parking (AVP) will arrive at an AVP-compatible parking lot without reserving AVP.

[0005] The present disclosure has been made in consideration of the above-mentioned problems, and its purpose is to improve the convenience of users of vehicles that arrive at a parking lot without making a reservation for automatic valet parking. [Means for solving the problem]

[0006] An automated valet parking management system according to the present disclosure manages automated valet parking in a parking lot. The automated valet parking management system includes one or more processors. When a vehicle capable of automated valet parking arrives at the parking lot, the one or more processors are configured to determine whether a reservation for automated valet parking has been made for the vehicle, search for available parking space reservations in the parking lot if a reservation for automated valet parking has not been made, and, if an available parking space is available, notify the user of a suggestion to use automated valet parking via a terminal device operated by the user of the vehicle. [Effects of the Invention]

[0007] According to the automated valet parking management system of the present disclosure, when a vehicle compatible with automated valet parking (AVP) arrives at a parking lot without making a prior reservation for the use of AVP, the automated valet parking management system automatically searches for available AVP parking space reservations. If there are available reservations, the automated valet parking management system notifies the user via a terminal device of a suggestion to use AVP. This eliminates the need for the user of a vehicle that has arrived at a parking lot and wishes to use AVP to perform reservation operations at the parking lot, including checking for available parking spaces. This improves convenience for users of vehicles that arrive at a parking lot without making a reservation for the use of AVP. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of the configuration of an automatic valet parking management system according to an embodiment. [Figure 2] 4 is a flowchart illustrating an example of processing by the automatic valet parking management system according to the embodiment. [Figure 3] FIG. 10 is a diagram showing an example of how usage suggestions are displayed on the screen of an HMI display mounted on a vehicle. [Figure 4] FIG. 10 is a diagram showing an example of how usage suggestions are displayed on the screen of a display of a user terminal. [Figure 5]10 is a flowchart illustrating another example of the processing of the automatic valet parking management system according to the embodiment. [Figure 6] 10 is a flowchart illustrating yet another example of the processing of the automatic valet parking management system according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0010] 1. Configuration of the automated valet parking management system 1 is a diagram illustrating an example of the configuration of an automated valet parking management system 100 according to an embodiment. The automated valet parking (AVP) management system 100 manages the AVP of a vehicle 10 in a parking lot 1.

[0011] Vehicle 10 is a vehicle that supports AVP in parking lot 1. Vehicle 10 can travel automatically at least within parking lot 1 without any driving operation by a driver. More specifically, vehicle 10 is equipped with a recognition sensor (e.g., a camera) for recognizing the surrounding situation. Vehicle 10 travels automatically within parking lot 1 while recognizing the surrounding situation using the recognition sensor. Vehicle 10 may also be an autonomous vehicle that can travel automatically outside parking lot 1. Vehicle 10 is also equipped with an HMI (Human Machine Interface) 12 as an interface with a user (passenger) of vehicle 10. HMI 12 is, for example, a touch panel. HMI 12 may include a speaker. HMI 12 corresponds to an example of a "terminal device" according to the present disclosure.

[0012] The parking lot 1 includes a drop-off area 2, a pick-up area 3, an aisle 4, and multiple parking spaces 5. A vehicle 10 entering the parking lot 1 stops in the drop-off area 2, where the user disembarks from the vehicle 10. On the other hand, a vehicle 10 leaving the parking lot 1 stops in the pick-up area 3, where the user boards the vehicle 10. The drop-off area 2 can also be called the pick-up area, and the pick-up area 3 can also be called the exit area. The aisle 4 is the area in which the vehicle 10 travels. The parking spaces 5 are spaces in which the vehicle 10 is parked. For example, the parking spaces 5 are separated by demarcation lines. The parking lot 1 may be an AVP-only parking lot that is only for AVP vehicles 10, or it may be a parking lot that can also be used by AVP vehicles 10 that do not use the AVP function and vehicles that do not have the AVP function.

[0013] In the example shown in FIG. 1, the AVP management system 100 includes one or more infrastructure sensors 20 (hereinafter simply referred to as "infrastructure sensors 20"), a local management device 30, and a management server 40. The local management device (or simply "management device") 30 is installed in a parking lot 1. The management server (cloud) 40 manages multiple parking lots 1. In the example of the AVP management system 100, various processes related to the management of AVPs, which will be described later, are executed by cooperation between the management device 30 and the cloud 40.

[0014] The infrastructure sensor 20 includes, for example, a camera, and recognizes the situation in the parking lot 1. More specifically, the infrastructure sensor 20 recognizes the situation around the vehicle 10 in the parking lot 1 (for example, obstacles such as pedestrians and other vehicles). The infrastructure sensor 20 also recognizes available parking spaces 5. Information acquired by the infrastructure sensor 20 is transmitted to the local management device 30. The infrastructure sensor 20 corresponds to an example of a "recognition sensor" according to the present disclosure.

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

[0016] The processor 34 executes various processes related to the management of AVPs. Examples of the processor 34 include a CPU, a GPU, an ASIC, and an FPGA. The processor 34 can also be called circuitry or processing circuitry. Circuitry is hardware programmed to realize a described function, or hardware that executes a function. The storage device 36 stores various information. Examples of the storage device 36 include volatile memory, non-volatile memory, HDD, and SSD. The functions of the management device 30 may be realized by cooperation between the processor 34, which executes a 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 be provided via a network.

[0017] The management server (cloud) 40 includes a communication device 42, one or more processors 44 (hereinafter simply referred to as processor 44), and one or more storage devices 46 (hereinafter simply 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) carried by the user of the vehicle 10, and corresponds to another example of a "terminal device" according to the present disclosure.

[0018] The processor 44 executes various processes related to the management of AVP. Examples of the processor 44 include a CPU, a GPU, an ASIC, and an FPGA. The processor 44 can also be called circuitry or processing circuitry. Circuitry is hardware programmed to realize a described function, or hardware that executes a function. The storage device 46 stores various information. Examples of the storage device 46 include a volatile memory, a non-volatile memory, an HDD, and an SSD. The functions of the cloud 40 may be realized by cooperation between the processor 44, which executes a 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 be provided via a network.

[0019] The AVP management system 100 executes "various processes related to AVP management" as follows, for example, through cooperation between the management device 30 and the cloud 40.

[0020] The cloud 40 manages information (user information) about each user of the AVP service (AVP service). The user information includes pre-registered membership information of each user and the following reservation information:

[0021] When a user X reserves an AVP, the user X operates the user terminal 50 to input the user X's ID information (identification information), desired parking lot 1, desired date of use, desired use time (scheduled entry time and scheduled exit time), etc. The user terminal 50 transmits reservation information including the input information to the cloud 40 (AVP management system 100). The storage device 46 of the cloud 40 stores the latest information on available parking spaces 5 obtained from the management device 30. Upon receiving the reservation information from the user X, the cloud 40 performs reservation processing based on the reservation information if there is an available parking space 5 (more specifically, a parking space 5 for an AVP) available for reservation in the parking lot 1. The reservation processing includes allocating the available parking space 5 to the vehicle 10, i.e., reserving the parking space 5 for the vehicle 10. Then, upon completion of the reservation processing, the cloud 40 transmits a reservation completion notification to the user terminal 50. Note that the "terminal device" used for reservation described here may be the HMI 12.

[0022] 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 time, the management device 30 performs processing to identify the arriving vehicle 10. Specifically, the management device 30 recognizes the license plate number of the vehicle 10 using, for example, the infrastructure sensor 20. The license plate number corresponds to an example of identification information of the vehicle 10. The management device 30 transmits information indicating the arrival of the vehicle 10 together with the identification information to the cloud 40. The storage device 46 of the cloud 40 stores identification information of each vehicle 10 that uses the AVP service. The cloud 40 identifies the vehicle 10 that has arrived at the drop-off area 2, for example, by comparing the identification information received from the management device 30 with the identification information stored in the storage device 46. Then, the cloud 40 identifies the user of the identified vehicle 10 based on the user information.

[0023] Then, the cloud 40 determines whether the arriving vehicle 10 is a vehicle with a reservation for AVP use based on the reservation information. The cloud 40 also executes a process to request consent from the user X for the AVP management system 100 to remotely operate the vehicle 10 in order to park the vehicle 10 with a reservation for AVP use. When the cloud 40 receives information indicating consent from the user X (for example, a request to start AVP) via the user terminal 50 or the HMI 12, the authority to operate the vehicle 10 is transferred from the user X to the AVP management system 100. The AVP management system 100 performs a warehousing process for the vehicle 10.

[0024] The entry process includes processing related to parking control of the vehicle 10 to park the vehicle 10 in the reserved parking space 5. In the parking control, the management device 30 acquires information indicating the situation around the vehicle 10 in the parking lot 1 (e.g., obstacles such as pedestrians and other vehicles) from the infrastructure sensor 20. Then, based on the information, the management device 30 generates a target driving route from the drop-off area (entry area) 2 to the parking space 5 assigned to the vehicle 10. Then, the management device 30 communicates with the vehicle 10 and remotely controls the vehicle 10 to travel along the generated target driving route. Alternatively, in another example of parking control, the AVP management system 100 may transmit information about the target driving route to the vehicle 10 along with information about the parking space 5 assigned to the vehicle 10 and map information about the parking lot 1. Then, the vehicle 10 may automatically travel along the received target driving route using a recognition sensor such as a camera mounted on the vehicle 10.

[0025] The management device 30 uses the infrastructure sensor 20 to detect that parking of the vehicle 10 is complete. Alternatively, once parking is complete, the vehicle 10 may notify the management device 30 that parking is complete. After parking is complete, the management device 30 communicates with the vehicle 10 and stops the operation of the vehicle 10 (powers off). The cloud 40 acquires information indicating that parking of the vehicle 10 is complete from the management device 30 and stores information about the parking space 5 of the vehicle 10 in association with the user X.

[0026] The process of leaving the vehicle 10 from the parking lot 1 is executed, for example, as follows. That is, in response to a request for leaving from a user X operating the user terminal 50, the cloud 40 executes a process of requesting consent from the user X for the AVP management system 100 to remotely operate the vehicle 10 in order to leave the vehicle 10. When the cloud 40 receives information indicating consent from the user X via the user terminal 50 (for example, a request to start leaving the vehicle 10), the AVP management system 100 communicates with the vehicle 10 and starts the vehicle 10 (powers on). Then, in the leaving process, the management device 30 generates a target driving route from the parking space 5 to the boarding area (leaving area) 3 based on information from the infrastructure sensor 20, for example, as in the case of the entering process. Then, for example, the management device 30 communicates with the vehicle 10 and remotely controls the vehicle 10 to travel according to the generated target driving route. When the vehicle 10 arrives at and stops in the boarding area 3, the authority to operate the vehicle 10 is transferred from the AVP management system 100 to the user X. After the passengers including the user X get into the vehicle 10, the vehicle 10 departs for the next destination.

[0027] 2. Measures for vehicles arriving without a reservation using AVP To use the AVP service, a reservation is required to secure a parking space. Therefore, if an AVP-compatible vehicle arrives at an AVP-compatible parking lot without a reservation, the following problem will arise unless special consideration is given. That is, the user of the arriving vehicle must personally perform the reservation procedure, including checking for available parking spaces, in the parking lot's drop-off area (entry area). This may cause inconvenience to the user regarding the use of AVP. It may also lead to congestion in the drop-off area. Furthermore, if the parking lot where the user arrives allows both AVP-based parking and user-driven parking, the user may park by driving themselves, even if they intend to use the AVP service, without realizing that AVP is available.

[0028] Therefore, when a vehicle 10 that supports AVP arrives at the drop-off area 2 of the parking lot 1, the AVP management system 100 according to this embodiment determines whether or not a reservation for use of the AVP has been made for the vehicle 10. If a reservation for use has not been made, the cloud 40 searches for available parking space information for parking spaces 5 in the parking lot 1. The parking space 5 for which available information is searched is a parking space that can be used by the AVP. If there is an available parking space 5, the cloud 40 notifies the user of a suggestion to use the AVP via a "terminal device." The terminal device used to notify the suggestion is at least one of the HMI 12 and the user terminal 50.

[0029] 2-1. Example of AVP management system processing 2 is a flowchart showing an example of processing performed by 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.

[0030] In step S100, the management device 30 (processor 34) determines whether the AVP-compatible vehicle 10 has arrived at the AVP-compatible parking lot 1. More specifically, the management device 30 determines whether the vehicle 10 has arrived at the parking lot 1, for example, using the infrastructure sensor 20. As a result, if the vehicle 10 has arrived at the parking lot 1 (step S100; Yes), the process proceeds to step S102.

[0031] In step S102, the cloud 40 (processor 44) determines whether or not there is a reservation for use of the AVP by the vehicle 10. This determination is made based on the reservation information stored in the storage device 46. As a result, if there is a reservation for use of the AVP (step S102; Yes), the process proceeds to S112. On the other hand, if there is no reservation for use of the AVP (step S102; No), the process proceeds to step S104.

[0032] In step S104, the cloud 40 determines whether there is a vacant parking slot 5 available for reservation for the AVP. That is, the cloud 40 autonomously searches for vacant information on the parking slot 5 available for the AVP. This determination (search) is performed based on the vacant information on the parking slot 5 stored in the storage device 46. As a result, if there is no vacant parking slot 5 available for reservation for the AVP (step S104; No), the process proceeds to END. On the other hand, if there is a vacant parking slot 5 available for reservation for the AVP (step S104; Yes), the process proceeds to step S106.

[0033] In step S106, the cloud 40 notifies the user of the vehicle 10 of the "usage suggestion" of the AVP. This notification is executed to the "terminal device," i.e., at least one of the HMI 12 and the user terminal 50. The notification of the usage suggestion is performed by displaying the usage suggestion on the display of the terminal device, as exemplified with reference to the following FIGS. 3 and 4. Alternatively, the notification of the usage suggestion may be performed by audio using the speaker of the terminal device instead of or in addition to displaying the usage suggestion on the display.

[0034] FIG. 3 shows an example of a usage suggestion displayed on the screen 12a of the display of the HMI 12 mounted on the vehicle 10. In this example, the usage suggestion includes the characters "XX Airport P1" as an example of the name of the parking lot 1, as well as a message "AVP is 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, a message "A parking space for AVP is available." In this example, the usage suggestion includes a message "Do you want to make a reservation?" as an example of "information for confirming whether or not the user intends to use the AVP," a display of a "reservation button," and a display C of a "close screen button." Note that, instead of the display C of the "close screen button," for example, a button with the characters "Do not reserve" may be displayed. In an example of a usage suggestion using only audio, the "information for confirming whether or not the user intends to use the AVP" may include only the message "Do you want to make a reservation?"

[0035] FIG. 4 shows an example of a usage suggestion displayed on the screen 50a of the display of the user terminal 50. In this example, as in the example displayed on the HMI 12, the usage suggestion includes the text "XX Airport P1" and a message such as "AVP is available" as an example of "information indicating that parking slots 5 are available for reservation." Alternatively, the "information indicating that parking slots 5 are available for reservation" may include, for example, a message such as "A parking slot for AVP is available." In this example, the usage suggestion includes, as an example of "information for confirming the user's intention to use the AVP," a message such as "Do you want to make a reservation?", a display of a "reservation button," and a display C of a "close screen button." Note that, instead of the display C of the "close screen button," a button with the text "Do not make a reservation" may be displayed. In the example of a usage suggestion using only audio, the "information for confirming the user's intention to use the AVP" may include, for example, only the message "Do you want to make a reservation?"

[0036] In step S108 following step S106, the cloud 40 determines whether the user of the vehicle 10 intends to use the AVP. This determination is made based on the user's response to the usage suggestion. Specifically, for example, if the user operates the HMI 12 or the user terminal 50 and touches the "reserve button," the cloud 40 determines that the user intends to use the AVP. As a result, the process proceeds to step S110. On the other hand, for example, if the user operates the HMI 12 or the user terminal 50 and touches the "close screen button" or the "button with the text 'do not reserve'," the cloud 40 determines that the user does not intend to use the AVP. As a result, the process proceeds to END. In addition, the "terminal device," such as the HMI 12 and the user terminal 50, may have a voice recognition function. The terminal device may then use the voice recognition function to receive the user's response to the usage suggestion.

[0037] In step S110, the cloud 40 executes a process for reserving the use of the AVP. This process includes allocating a parking slot 5 for an available AVP to the vehicle 10, that is, reserving the parking slot 5 for the vehicle 10. Then, the process proceeds to step S112.

[0038] In step S112, the management device 30 starts the parking control described above to park the vehicle 10 in the reserved parking slot 5. Thereafter, the process proceeds to step S114.

[0039] In step S114, the management device 30 uses information from the infrastructure sensor 20, etc. to determine whether or not the entry of the vehicle 10 has been completed, in other words, whether or not the parking of the vehicle 10 has been completed in the reserved parking space 5. As a result, if the entry has been completed (step S114; Yes), the process proceeds to step S116.

[0040] In step S116, the cloud 40 sets the status of the AVP service for the vehicle 10 that has completed entering the warehouse to "waiting for release." After that, the process proceeds to END.

[0041] 2-2.Effects As described above, according to this embodiment, when an AVP-compatible vehicle 10 arrives at the drop-off area 2 of the parking lot 1 without making a prior reservation for the use of AVP, the AVP management system 100 automatically searches for available reservation information for AVP-compatible parking spaces 5. If there are available reservations, the AVP management system 100 notifies the user via a terminal device such as the HMI 12 of a suggestion to use the AVP. This eliminates the need for the user of the vehicle 10 who has arrived at the parking lot 1 to personally perform a reservation operation, including checking the availability of a parking space 5, in the parking lot 1 (more specifically, the drop-off area 2). In other words, the operations that the user of the vehicle 10 who has arrived at the parking lot 1 without making a reservation for the use of AVP must perform to start using the AVP are simplified. This improves the user's convenience in using the AVP service.

[0042] Furthermore, the spontaneous search for vacant information and usage suggestion by the AVP management system 100 according to this embodiment allows a user to quickly reserve an AVP in the drop-off area 2, compared to an example in which the user himself performs the reservation operation, including checking the availability of parking spaces 5, in the parking lot 1 (drop-off area 2). This makes it possible to prevent congestion in the drop-off area 2 caused by the arrival of vehicles 10 without reservations.

[0043] Furthermore, if the parking lot 1 where the user arrives allows both parking using AVP and parking by the user's own driving, the above-mentioned usage suggestion can also have the following effect. That is, if the user has the intention to use the AVP service but is unaware that AVP is available in the parking lot 1, the usage suggestion can make the user aware that AVP is available. This leads to increased use of AVP. And, if the AVP service is provided for a fee, it leads to increased revenue for the AVP service provider.

[0044] 2-3. Examples of restrictions on notification of proposed use As described above, the "usage suggestion" according to this embodiment leads to improved user convenience regarding the use of AVP. On the other hand, some users may find it annoying to receive notifications of usage suggestions. More specifically, for example, if the parking lot 1 where the user arrives allows both parking using AVP and parking by the user's own driving, some users may wish to drive and park the vehicle 10 themselves. Therefore, notifications of the "usage suggestion" may be limited as follows.

[0045] 2-3-1. First concrete example 5 is a flowchart showing another example of the processing of the AVP management system 100 according to the embodiment. This flowchart differs from the flowchart shown in FIG. 2 in that the processing of steps S200 and S202 is added.

[0046] In FIG. 5, if the user does not intend to use AVP (step S108; No), that is, if a response rejecting the usage proposal is received from the user via a terminal device (e.g., user terminal 50), the process proceeds to step S200. In step S200, cloud 40 stores the user's rejection of this usage proposal as a history in storage device 46. This rejection history is one of the above-mentioned user information stored for each user. Thereafter, the process proceeds to END.

[0047] 5, if there is a vacant parking slot 5 reserved for AVP (step S104; Yes), the process proceeds to step S202. In step S202, the cloud 40 determines, based on the user information stored in the storage device 46, whether or not the user who is the target of the process of the currently executed flowchart has a history of rejecting a usage suggestion. This determination is made based on the user information stored in the storage device 46.

[0048] If there is no history of rejection of the use proposal (step S202; No), the process proceeds to step S106, where the use proposal is notified. On the other hand, if there is a history of rejection of the use proposal (step S202; Yes), the process proceeds to END. In other words, the cloud 40 does not notify the user of the vehicle 10 that has just arrived at the parking lot 1 of the use proposal.

[0049] According to the first specific example described above, if the vehicle 10 carrying the user who rejected the usage suggestion arrives again at the same parking lot 1 without reserving the use of AVP, the cloud 40 will not notify the user of the usage suggestion even if there is a vacant parking slot 5 for AVP. In this way, according to the first specific example, it is possible to improve the convenience for users regarding the use of the AVP service while also taking into consideration users who do not want usage suggestions.

[0050] In addition, the vehicle 10 that a user rides in when using an AVP-enabled parking lot 1 is not always the same. Therefore, the restriction on usage suggestions for a user who has rejected a usage suggestion may, for example, apply only to the vehicle 10 that the user was actually riding in when the user rejected the usage suggestion. Alternatively, the restriction may apply to all vehicles 10 in which the user rides, not just the vehicle 10 that the user was actually riding in when the user rejected the usage suggestion.

[0051] 2-3-2. Second specific example 6 is a flowchart showing yet another example of the processing of the AVP management system 100 according to the embodiment. This flowchart differs from the flowchart shown in FIG. 2 in that processing of step S300 is added.

[0052] In the second specific example, the "usage suggestion" notification has the following customization function. That is, the cloud 40 is configured so that a user who does not need the usage suggestion can turn off 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 above-mentioned 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 turns off the usage suggestion notification function, the cloud 40 updates the status information of the user to indicate that the usage suggestion notification function is off.

[0053] 6, if there is no reservation for use of the AVP (step S102; No), the process proceeds to S300. In step S300, the cloud 40 determines whether the user who is the target of the currently executed process of the flowchart has set the notification function of the usage suggestion to off. This determination is made based on the above-mentioned state information stored in the storage device 46.

[0054] If the usage suggestion notification function is on (step S300; Yes), the process proceeds to step S104, where it is determined whether or not there is a vacant parking slot 5 for the AVP. On the other hand, if the usage suggestion notification function is off (step S300; Yes), the process proceeds to END. In other words, the cloud 40 does not notify the user of the vehicle 10 that has arrived at the parking lot 1 this time of a usage suggestion, regardless of whether or not there is a vacant parking slot 5 for the AVP.

[0055] According to the second specific example described above, if the user has turned off the usage suggestion notification function, that is, if a request indicating that usage suggestion notifications are not required has been received in advance from the user via a terminal device (e.g., user terminal 50), the cloud 40 restricts usage suggestion notifications as follows: That is, for all parking lots 1 that provide AVP services through the AVP management system 100, the cloud 40 does not notify the user of usage suggestions when the vehicle 10 in which the user is riding arrives at the drop-off area 2 of the parking lot 1 without an AVP usage reservation. In this way, according to the second specific example, it is possible to improve user convenience regarding the use of the AVP service while also taking into consideration users who do not want usage suggestions.

[0056] In addition, the vehicle 10 that a user rides in when using an AVP-enabled parking lot 1 is not always the same. Therefore, the restriction on usage suggestions for a user who has turned off the usage suggestion notification function may be applied to, for example, all vehicles 10 in which the user rides. Alternatively, the restriction may be applied to a vehicle 10 specified by the user. [Explanation of symbols]

[0057] 1 Parking lot, 2 Drop-off area, 5 Parking space, 10 Vehicle, 12 HMI, 20 Infrastructure sensor, 30 Local management device, 40 Management server (cloud), 50 User terminal, 100 Automatic valet parking management system

Claims

1. An automatic valet parking management system that manages automatic valet parking in a parking lot, one or more processors; the one or more processors: When a vehicle compatible with the automated valet parking arrives at the parking lot, it is determined whether or not a reservation for the automated valet parking has been made for the vehicle; If the reservation has not been made, search for available parking space reservations in the parking lot; If there is a vacant parking space available, the user of the vehicle is notified of the proposal to use the automated valet parking via a terminal device operated by the user of the vehicle. It was configured as Automated valet parking management system.

2. 2. The automated valet parking management system according to claim 1, The usage suggestion includes information indicating that there is a vacant parking space available for reservation, and information for confirming whether or not the user intends to use the automated valet parking. Automated valet parking management system.

3. 3. The automated valet parking management system according to claim 1 or 2, When a response rejecting the use proposal is received from the user via the terminal device, the one or more processors do not notify the user of the use proposal even if the vehicle in which the user who rejected the use proposal is riding arrives again at the same parking lot without a reservation for the automatic valet parking. Automated valet parking management system.

4. 3. The automated valet parking management system according to claim 1 or 2, When a request indicating that notification of the usage suggestion is not required has been received in advance from the user via the terminal device, the one or more processors, for all parking lots that provide an automatic valet parking service by the automatic valet parking management system, do not notify the user of the usage suggestion when the vehicle in which the user is riding arrives at the parking lot without a reservation for automatic valet parking. Automated valet parking management system.

Images