JP7792838B2 - Parking location guidance system, server, vehicle-mounted device, and parking location guidance method - Google Patents

Description

This disclosure relates to a parking location guidance system, a server, an in-vehicle device, and a parking location guidance method.

Patent Document 1 describes the following parking lot guidance system. Specifically, in the parking lot guidance system described in Patent Document 1, information on available parking locations and a map of the parking lot interior is transmitted from a management center to an on-board information processing device. The on-board information processing device then displays a guide for the vehicle based on the parking lot map and vehicle position information, guiding the driver to the parking location. In this configuration, the on-board information processing device determines the route to the parking location based on the parking lot map and vehicle position information.

International Publication No. 2020/054354

However, the parking lot guidance system described in Patent Document 1 has an issue in that, because the onboard information processing device determines the route to the parking location, it may not be able to determine the route appropriately if, for example, the conditions in the parking lot change.

This disclosure has been made to solve the above-mentioned problems, and aims to provide a parking location guidance system, server, in-vehicle device, and parking location guidance method that can appropriately determine the route to a parking location.

In order to solve the above problems, the parking location guidance system disclosed herein is a parking location guidance system comprising a server and an in-vehicle device, wherein the server comprises a parking location determination unit that determines a parking location for a target vehicle, a route determination unit that determines a route for the target vehicle to reach the parking location, and a first communication unit that transmits information indicating the route to the in-vehicle device, and the in-vehicle device comprises a second communication unit that receives the information indicating the route and a guidance information determination unit that determines guidance information to be output based on the route and the vehicle's position.

The server according to the present disclosure is a server of a parking location guidance system that includes a server and an in-vehicle device, wherein the server includes a parking location determination unit that determines the parking location of a target vehicle, a route determination unit that determines the route the target vehicle will take to reach the parking location, and a first communication unit that transmits information indicating the route to the in-vehicle device, and the in-vehicle device includes a second communication unit that receives the information indicating the route and a guidance information determination unit that determines guidance information to be output based on the route and the vehicle's position.

The vehicle-mounted device disclosed herein is an vehicle-mounted device of a parking location guidance system that includes a server and a vehicle-mounted device, wherein the server includes a parking location determination unit that determines a parking location for a target vehicle, a route determination unit that determines a route for the target vehicle to reach the parking location, and a first communication unit that transmits information indicating the route to the vehicle-mounted device, and the vehicle-mounted device includes a second communication unit that receives information indicating the route, and a guidance information determination unit that determines guidance information to be output based on the route and the vehicle's position.

The parking location guidance method disclosed herein is a parking location guidance method using a server and an in-vehicle device, and includes the steps of: determining, in the server, the parking location of a target vehicle; determining a route for the target vehicle to reach the parking location; transmitting information indicating the route to the in-vehicle device; receiving, in the in-vehicle device, the information indicating the route; and determining guidance information to be output based on the route and the vehicle's position.

The parking location guidance system, server, vehicle-mounted device, and parking location guidance method disclosed herein make it possible to appropriately determine the route to the parking location.

FIG. 1 is a schematic diagram for explaining the functions of a parking lot management system according to an embodiment of the present disclosure. 1 is a block diagram illustrating an example of a mechanical configuration of a parking location guidance system according to an embodiment of the present disclosure. FIG. 1 is a plan view schematically illustrating an example of a parking lot for explaining an example of the operation of a parking location guidance system according to an embodiment of the present disclosure. FIG. 10 is a flowchart for explaining an example of the operation of the parking location guidance system according to an embodiment of the present disclosure. 10 is a flowchart for explaining an example of the operation of the parking location guidance system according to an embodiment of the present disclosure. 1 is a plan view schematically illustrating an example of a parking lot for explaining an example of the operation of a parking location guidance system according to an embodiment of the present disclosure. FIG. 1 is a plan view schematically illustrating an example of a parking lot for explaining an example of the operation of a parking location guidance system according to an embodiment of the present disclosure. FIG. 1 is a plan view schematically illustrating an example of a parking lot for explaining an example of the operation of a parking location guidance system according to an embodiment of the present disclosure. FIG. 1 is a plan view schematically illustrating an example of a parking lot for explaining an example of the operation of a parking location guidance system according to an embodiment of the present disclosure. FIG. 1 is a plan view schematically illustrating an example of a parking lot for explaining an example of the operation of a parking location guidance system according to an embodiment of the present disclosure. FIG. 1 is a plan view schematically illustrating an example of a parking lot for explaining an example of the operation of a parking location guidance system according to an embodiment of the present disclosure. FIG. 1 is a plan view schematically illustrating an example of a parking lot for explaining an example of the operation of a parking location guidance system according to an embodiment of the present disclosure. FIG. FIG. 1 is a schematic block diagram illustrating the configuration of a computer according to at least one embodiment.

Embodiments of the parking location guidance system, server, in-vehicle device, and parking location guidance method of the present disclosure will be described below with reference to the drawings. FIG. 1 is a schematic diagram illustrating the functions of a parking lot management system according to an embodiment of the present disclosure. FIG. 2 is a block diagram illustrating an example mechanical configuration of a parking location guidance system according to an embodiment of the present disclosure. FIG. 3 is a plan view schematically illustrating an example parking lot for explaining an example operation of a parking location guidance system according to an embodiment of the present disclosure. FIGS. 4 and 5 are flowcharts illustrating an example operation of a parking location guidance system according to an embodiment of the present disclosure. FIGS. 6 to 12 are plan views schematically illustrating an example parking lot for explaining an example operation of a parking location guidance system according to an embodiment of the present disclosure. Note that the same reference numerals are used in each drawing for identical or corresponding components, and descriptions thereof will be omitted as appropriate.

First Embodiment
(Parking lot management system)
FIG. 1 illustrates an example of a function of a parking lot management system 100 including a parking location guidance system 5 according to an embodiment of the present disclosure. The parking lot management system 100, for example, manages the usage status of parking spaces in a parking lot and manages various information related to one or more vehicles parked in the parking lot. In the example shown in FIG. 1 , the parking lot management system 100 includes a parking lot server 1, an in-vehicle device 2, and a mobile terminal 3. The parking lot server 1 is an example configuration of a server according to the present disclosure. The in-vehicle device 2 is an information processing device with a communication function mounted on a vehicle. The mobile terminal 3 is an information processing device with a communication function, such as a smartphone carried by a user such as a driver of the vehicle. The parking lot server 1 and the in-vehicle device 2 are wirelessly connected using, for example, a dedicated short-range communications (DSRC) line or a public communication line. The parking lot server 1 and the mobile terminal 3 are wirelessly connected using, for example, a public communication network, a wireless local area network, or the like. The vehicle-mounted device 2 and the mobile terminal 3 are wirelessly connected using, for example, a short-distance communication line, a wireless local area communication line, or the like.

The parking lot server 1 is configured, for example, using a computer and its peripheral devices. The parking lot server 1 has the following functions. Specifically, the parking lot server 1 has a contract management function F11, a recommended parking space setting function F12, an in-vehicle device detection function F13, an in-parking lot route provision function F14, a parking fee provision service function F15, and an exit charging function F16. Some or all of these functions can be provided, for example, as a cloud service. The functions of the parking lot server 1 can also be applied to one or more parking lots.

As described above, the in-vehicle device 2 is an information processing device with communication capabilities mounted on the vehicle, and is configured, for example, using one or more computers and their peripheral devices and circuits. In addition to wireless communication capabilities, the in-vehicle device 2 may also have functions such as measuring the vehicle's position, direction of travel, speed, etc., inputting user operations, outputting information to the user, and billing functions using cash cards or prepaid cards. The in-vehicle device 2 may be configured, for example, as a terminal for a toll road billing system. Alternatively, the in-vehicle device 2 may be configured, for example, such that some or all of its components are included in an electronic control unit or navigation device mounted on the vehicle. Alternatively, the in-vehicle device 2 may be configured to utilize, for example, the functions of the electronic control unit or navigation device, such as measuring the vehicle's position, direction of travel, speed, etc., a display, touch panel, and voice operation functions. In this case, the in-vehicle device 2 does not necessarily have to have functions such as measuring the vehicle's position, direction of travel, speed, etc., input devices such as a touch panel or microphone, or output devices such as a display or speaker. In the example shown in Figure 1, the vehicle-mounted device 2 has a parking lot entry function F21, an in-parking lot route reception waiting function F22, and a billing processing function F23.

In addition, the mobile terminal 3 implements a parking account management function F31 and a fee confirmation function F32, for example, by installing a specific app.

The contract management function F11 works in conjunction with the parking lot account management function F31 to register and manage user attributes and attributes (attribute information) of vehicles, onboard devices, communication units, etc. User attributes include, for example, information indicating whether the user is a contract holder for monthly parking space use, information indicating whether the user is a registered member of a facility operated by the parking lot operator or an affiliated facility, etc. Vehicle attributes include, for example, information indicating whether the vehicle is a vehicle for physically disabled passengers, whether the vehicle uses an external charger to charge the onboard battery (and the corresponding charging standard), whether the vehicle is permitted to park in a parking space allocated only to designated registered vehicles, the license plate marking, whether the vehicle is a commercial vehicle, etc. The attributes of the onboard device 2 include the onboard device ID, etc. The attributes of the communication unit include, for example, the telephone number, address, and unique identification code of the communication terminal. The contract management function F11 manages information indicating attributes by linking it to, for example, the ID (identification code; hereinafter also referred to as the onboard device ID) of the onboard device 2, the vehicle's license plate marking, etc. Note that each attribute does not need to be registered in advance using the contract management function F11; instead, for example, the user may register it in the vehicle-mounted device 2, and the parking lot server 1 may receive it from the vehicle-mounted device 2 that has entered the parking lot.

The recommended parking space setting function F12 sets a recommended parking space for the target vehicle (hereinafter referred to as the target vehicle) based on the ID of the on-board device 2 detected by the on-board device detection function F13, the attribute information described above, the vehicle's positioning information obtained from the on-board device 2, the parking lot usage status (vacant parking space information), etc. The recommended parking space can be, for example, a single parking space (a parking space for one vehicle), or multiple parking spaces or an area including multiple parking spaces. In this embodiment, one or more parking spaces or areas are collectively referred to as a parking location. The recommended parking space setting function F12 repeatedly sets the parking position for the target vehicle until the guidance for the target vehicle is completed (e.g., until the target vehicle is parked). Normally, a parking position once set is not changed. However, the parking position may be changed, for example, if another vehicle has parked there, or if the set parking position becomes unusable due to an obstacle, etc. Therefore, the recommended parking space setting function F12 repeatedly sets the parking position for the target vehicle. The parking lot server 1 can set the position of obstacles, for example, in response to input operations by the operator.

The on-board device detection function F13 works in conjunction with the parking lot entry function F21 to detect the on-board device 2 of a vehicle that has entered the parking lot, for example, using short-range communication, and receives the on-board device ID, vehicle positioning information, specified attribute information (also known as attributes), etc. from the detected on-board device 2. The on-board device detection function F13 stores the detection time (entry time), on-board device ID, and attributes in a specified memory area (specified database), etc. In this case, the on-board device detection function F13 may, for example, store the license plate marking read by a license plate reader, etc., linked to the on-board device ID. The on-board device detection function F13 also transmits a map of the parking lot (MAP) to the detected on-board device 2. The parking lot entry function F21 stores the received parking lot map in a specified memory area.

The on-site route providing function F14 works in conjunction with the on-site route reception waiting function F22 to search for (search for) a route to move the target vehicle from its current location to the set parking location and transmit the optimal route to the vehicle-mounted device 2. The on-site route providing function F14 repeatedly performs route searches at predetermined intervals. The on-site route providing function F14 also changes the optimal route if it detects a change in the parking location or the route conditions, such as when the parking location is changed during guidance or when an obstacle appears on the route to the parking location. If the on-site route providing function F14 changes the optimal route, it provides the changed route to the on-site route reception waiting function F22. Meanwhile, the on-site route reception waiting function F22 determines guidance information based on the route and vehicle position received from the on-site route providing function F14 and outputs it to a specified output destination. The guidance information is, for example, turn-by-turn information indicating the direction of travel at corners (including intersections), straight roads, etc., using arrow icons, synthesized voice, etc. Furthermore, if the route is changed, the parking lot route reception waiting function F22 determines whether to accept the changed route. The parking lot route reception waiting function F22 can determine whether to accept the changed route, for example, by displaying the route before and after the change on a parking lot map and allowing the driver to choose whether to accept the changed route. Alternatively, the parking lot route reception waiting function F22 can determine to reject acceptance if, for example, the distance to the next corner would be shorter than the distance that allows for a safe turn if the changed route were accepted. If the changed route is rejected, the parking lot route provision function F14 searches for a new route and provides the changed route to the parking lot route reception waiting function F22.

The parking fee provision service function F15 works in conjunction with the fee confirmation function F32, and when a fee confirmation request is received from the fee confirmation function F32, it calculates, for example, the current parking fee for the vehicle and sends the calculation result to the fee confirmation function F32.

The exit charging function F16 works in conjunction with the charging processing function F23 to detect the onboard unit 2 of a vehicle attempting to leave (exit) the parking lot, for example, using short-range communication, and executes the specified charging process. The exit charging function F16 calculates the parking fee from the time of entry to the current time, for example, and charges the fee using the charging function of the onboard unit 2, for example.

(Parking location guidance system)
In this embodiment, the parking location guidance system 5 is configured by the functions F12 to F13 and F21 to F22, which are enclosed by two-dot chain lines among the functions shown in Fig. 1, and the parking lot server 1 and the vehicle-mounted device 2 that implement these functions. The parking location guidance system 5 will be described below with reference to Figs. 1 to 12.

Figure 2 is a block diagram showing an example of the functional configuration of the parking lot server 1 and the vehicle-mounted device 2. The parking lot server 1 and the vehicle-mounted device 2 are equipped with the components shown in Figure 2 as functional components configured as a combination of hardware such as a computer and its peripheral devices and software such as a program executed by the computer, or as hardware alone.

The parking lot server 1 includes a communication unit 11 and a processing unit 12. The communication unit 11 includes a short-range communication unit 111 and a network communication unit 112. The processing unit 12 includes an in-vehicle device detection and registration unit 121, a parking position determination unit 122, and a route determination unit 123.

The vehicle-mounted device 2 includes a communication unit 21, a positioning unit 22, a display input unit 23, a sound input/output unit 24, and a processing unit 25. The communication unit 21 includes a short-range communication unit 211 and a network communication unit 212. The processing unit 25 includes a parking lot entry processing unit 251 and a guidance information determination unit 252.

In the parking lot server 1, the short-range communication unit 111 communicates with the short-range communication unit 211 of the vehicle-mounted device 2, for example, using short-range communication antennas (not shown) installed near the entrance 201 and exit 202 of the parking lot 200 shown in Figure 3.

The parking lot 200 shown in Figure 3 has multiple parking spaces 203 and a roadway 204. The roadway 204 includes a straight section 205 and a corner (including an intersection) 206. Figure 3 also shows examples of guidance information (arrow 401 for guidance information for going straight, arrow 402 for guidance information for a right turn, and arrow 403 for guidance information for a left turn) displayed on the roadway 204 on the display input unit 23 of the vehicle-mounted device 2. In the following explanation of the operation example, a case where the target vehicle 301 is guided to a parking space 203a (also referred to as a recommended parking position 203a or parking position 203a) will be used as an example.

The network communication unit 112 shown in FIG. 1 communicates with the network communication unit 212 via the network 4. The network 4 includes, for example, a public communication network. The network communication unit 112 is an example configuration of the first communication unit according to the present disclosure, and transmits information indicating the route of the target vehicle to the vehicle-mounted device 2.

The vehicle-mounted device detection and registration unit 121 is a functional component that implements the vehicle-mounted device detection function F13. The parking position determination unit 122 is a functional component that implements the recommended parking space setting function F12. The parking position determination unit 122 determines the parking position of the target vehicle. The parking position determination unit 122 determines the parking position of the target vehicle based on at least one of the following attributes of the target vehicle: whether the vehicle is a vehicle carrying a physically disabled person, whether the vehicle is a vehicle that externally charges its onboard storage battery as a power source for driving the vehicle, or whether the vehicle is permitted to park in a parking position allocated only to specified registered vehicles. The route determination unit 123 is a functional component that implements the in-parking lot route provision function F14. The route determination unit 123 determines the route the target vehicle will take to reach the parking position. The configurations and operations of the vehicle-mounted device detection and registration unit 121, the parking position determination unit 122, and the route determination unit 123 will be described later with reference to the flowcharts shown in Figures 4 and 5.

In the vehicle-mounted device 2, the short-range communication unit 211 communicates with the short-range communication unit 111 of the parking lot server 1 via short-range communication antennas (not shown) installed near the entrance 201 and exit 202 of the parking lot 200 shown in Figure 3.

The network communication unit 212 communicates with the network communication unit 112 via the network 4. The network communication unit 212 is an example configuration of a second communication unit according to the present disclosure, and receives information indicating the route of the target vehicle.

The positioning unit 22 measures the position, direction of travel, and speed of the vehicle equipped with the on-board device 2 at a predetermined interval, for example, using GNSS (Global Navigation Satellite System). In this embodiment, information representing at least one of the position (coordinates), direction of travel (direction of position change), and vehicle speed (change in position over time) is referred to as positioning information. However, there are no limitations on the positioning method. The positioning unit 22 may acquire positioning information by, for example, combining positioning using GNSS with positioning using the results of vehicle speed pulse acquisition or detection results from a gyro sensor, acceleration sensor, etc.

The display/input unit 23 includes a touch panel, for example, a touchpad and a display integrated together, and displays images and acquires input operations according to instructions from the processing unit 25.

The sound input/output unit 24 includes a microphone and a speaker, and, for example, detects voices uttered by the driver or the like and outputs a synthesized voice signal in accordance with instructions from the processing unit 25. The sound input/output unit 24 may also include a voice recognition function and the like, and may have the ability to perform interactive operations with the driver or the like.

The parking lot entry processing unit 251 is a functional component that implements the parking lot entry function F21. The guidance information determination unit 252 is a functional component that implements the parking lot route reception waiting function F22. The guidance information determination unit 252 determines the guidance information to be output based on the vehicle's route and vehicle position received from the parking lot server 1. In addition, if the route is changed, the guidance information determination unit 252 determines whether to accept the changed route. For example, the guidance information determination unit 252 determines whether to accept the changed route based on the safety level of traveling based on the changed route. The parking lot entry processing unit 251 and the guidance information determination unit 252 will be described later with reference to the flowcharts shown in Figures 4 and 5.

(In-vehicle device detection function and parking lot entry function)
Next, the in-vehicle device detection function F13 and the parking lot entry function F21 will be described with reference to Figure 4. In Figure 4, the processes of steps S101 to S108 correspond to the in-vehicle device detection function F13 executed by the in-vehicle device detection and registration unit 121. Furthermore, the processes of steps S201 to S205 correspond to the parking lot entry function F21 executed by the parking lot entry processing unit 251. Note that the processes of steps S101 and S102 are executed continuously while the parking lot is in operation. The processes of steps S104 and S105 or the processes of S104 to S108 are executed when the in-vehicle device 2 is detected.

In the process shown in FIG. 4, the vehicle-mounted device detection and registration unit 121 repeatedly transmits a signal (hereinafter referred to as a scan signal) from the short-range communication unit 111 to scan for the vehicle-mounted device 2 (steps S101 to S102). The vehicle-mounted device detection and registration unit 121 repeatedly scans for the vehicle-mounted device 2 using the short-range communication unit 111 until the vehicle-mounted device 2 enters the communication range. In the example shown in FIG. 4, the vehicle-mounted device 2 does not respond to the scan in step S101 or the scan in step S102 because it is not within the communication range.

When the vehicle 301 enters before the scan in step S103, the parking lot entry processing unit 251 in the in-vehicle device 2 recognizes that the short-range communication unit 211 has received a scan signal (step S201). Next, the parking lot entry processing unit 251 determines whether the received signal is a scan from the legitimate parking lot server 1 (step S202). If it is a scan from the legitimate parking lot server 1 (step S202: YES), the parking lot entry processing unit 251 acquires positioning information from the positioning unit 22 (step S203). Thereafter (or before and after), the parking lot entry processing unit 251 repeatedly acquires positioning information from the positioning unit 22 at regular time intervals. Next, the parking lot entry processing unit 251 transmits the in-vehicle device ID, positioning information, and attributes from the short-range communication unit 211 (step S204). On the other hand, if the scan was not from a legitimate parking lot server 1 (step S202: NO), the parking lot entry processing unit 251 receives the scan signal (step S201) and determines its authenticity (step S202) again.

Meanwhile, in the parking lot server 1, the on-board device detection and registration unit 121 checks the information indicating the on-board device ID, positioning information, and attributes received by the short-range communication unit 111, and identifies the location of the target vehicle 301 (step S104). Next, the on-board device detection and registration unit 121 determines whether the vehicle is within a specified range (step S105). Here, the specified range is a predetermined range within which it can be confirmed that the vehicle is inside the parking lot 200. In step S105, the on-board device detection and registration unit 121 determines whether the vehicle is within the specified range based on the previously known position of the entrance 201 of the parking lot 200, the distance from the vehicle position measured by the on-board device 2, and the direction of travel of the vehicle. This makes it possible to determine whether the target vehicle 301 has entered the parking lot 200 or is simply passing nearby. If the vehicle is not within the specified range (step S105: NO), the on-board device detection and registration unit 121 performs on-board device scanning again (step S103).

If the vehicle is within the specified range (Step S105: YES), the in-vehicle device detection and registration unit 121 registers the in-vehicle device ID in a specified database, etc. (Step S106). Next, the in-vehicle device detection and registration unit 121 registers the in-vehicle device ID as a chargeable and guidance target, and the parking lot server 1 begins calculating the parking fee (Step S107). Next, the in-vehicle device detection and registration unit 121 transmits a parking lot interior map (Step S108). In Step S108, the in-vehicle device detection and registration unit 121 transmits information indicating the parking lot interior map from the network communication unit 112 to the network communication unit 212 of the in-vehicle device 2. Alternatively, in Step S108, the in-vehicle device detection and registration unit 121 transmits information indicating the parking lot interior map from the short-range communication unit 111 to the short-range communication unit 211 of the in-vehicle device 2. Meanwhile, in the in-vehicle device 2, the parking lot entry processing unit 251 registers the parking lot map received by the communication unit 21 in a specified memory area (Step S205).

Through the process shown in Figure 4, the parking lot server 1 registers the vehicle-mounted device 2 of the vehicle 301 as a guidance target, and the vehicle-mounted device 2 obtains information showing a map of the parking lot 200.

(Recommended parking space setting function, facility route provision function, and facility route guidance waiting function)
Next, the recommended parking section setting function F12, the on-site route providing function F14, and the on-site route guidance waiting function F22 will be described with reference to FIG. 5 . In FIG. 5 , for example, steps S301 to S305 correspond to the recommended parking section setting function F12 executed by the parking position determining unit 122. Furthermore, for example, steps S307 to S312 correspond to the on-site route providing function F14 executed by the route determining unit 123. Furthermore, for example, steps S401 to S411 correspond to the on-site route guidance waiting function F12 executed by the guidance information determining unit 252. Note that the two connectors A shown in FIG. 5 are connected to each other. Furthermore, the processing shown in FIG. 5 is executed for each target vehicle. If there are multiple target vehicles, the processing of steps S301 to S312 shown in FIG. 5 is executed in parallel multiple times, the number of times corresponding to the number of target vehicles.

In the process shown in FIG. 5, in the parking lot server 1, the parking position determination unit 122 first uses the network communication unit 112 to inquire about the position of the vehicle-mounted device 2 to the network communication unit 212 (vehicle-mounted device position inquiry) (step S301). In the vehicle-mounted device 2, the guidance information determination unit 252 recognizes that the network communication unit 212 has received the vehicle-mounted device position inquiry (step S401). Next, the guidance information determination unit 252 transmits positioning information from the network communication unit 212 to the network communication unit 112 (step S402). Next, the parking position determination unit 122 links the vehicle-mounted device ID with the received positioning information (target vehicle position) (step S302). Next, the parking position determination unit 122 derives the congestion rate within the parking lot for each area (step S303). Here, an area is a division of the parking lot, and each area includes multiple parking spaces. In a flat parking lot, an area is set for each fixed area, for example, and in a multi-story parking lot, each floor is an area, for example. However, depending on the parking lot, it may not be necessary to set an area. Meanwhile, in the vehicle-mounted device 2, the guidance information determination unit 252 repeatedly acquires positioning information at regular intervals (step S403).

Next, the parking position determination unit 122 checks the contract information from the onboard device ID, determines whether the vehicle is a specific vehicle, and sets the contract category, for example (step S304). In step S304, the parking position determination unit 122, for example, compares the onboard device ID with a contract list of monthly contracts and members, etc., and if there is a match, validates the contract category as "member." Furthermore, for example, if the attributes indicate that the vehicle is permitted to park in a disabled area, the parking position determination unit 122 validates the contract category as "disabled." Furthermore, for example, if the attributes indicate that the vehicle matches the specifications of the charging area within the facility, the parking position determination unit 122 validates the contract category as "EV (electric vehicle)." Furthermore, for example, the parking position determination unit 122 compares the onboard device ID with a list for business vehicles, and if there is a match, validates the contract category as "business." Furthermore, for example, if the vehicle does not fall under any of the above categories, the parking position determination unit 122 does not set the contract category information (it treats the vehicle as a general user for parking lot management purposes).

Next, the parking position determination unit 122 derives a recommended parking position from the vehicle's contract class set in step S304 (step S305). In step S305, the parking position determination unit 122 derives a recommended parking position from the vehicle's contract class, for example, as follows: That is, for example, if the contract class is "disabled," a disabled parking space is designated as the "recommended section." For example, if the contract class is "EV," a charging-compatible parking section is designated as the "recommended section." For example, if the overall congestion rate is low, a parking area near the store entrance is designated as the "recommended section." For example, if the overall congestion rate is high, an empty parking area is designated as the "recommended section." For example, if the overall congestion rate is neither high nor low, a relatively empty area is designated as the "recommended section" so that the parking rate is uniform. Then, the parking position determination unit 122 designates, for example, all parking sections 203 within the recommended section, or one or some parking sections 203 within the recommended section, as the recommended parking position 203a.

Next, the route determination unit 123 calculates the route scores for all routes within the facility (step S306) and derives the optimal route from the vehicle position to the recommended parking location (step S307).

Here, a specific example of the processing of steps S306 and S307 will be described with reference to Figures 3 and 6 to 10. In this example, a route is searched for to guide the target vehicle 301 shown in Figure 3 to the recommended parking position 203a. In this example, the route score is an index that indicates the congestion status of each road (passageway), and is assumed to be high if it is congested and low if it is not congested. Causes that increase the route score (causes of congestion) include the following:

(1) When the route is temporarily closed due to pylons or barrier roads (in this case, the B value described below will be very high). (2) A route where there are vehicles struggling to park (in this case, the B value will be high). (3) A route where congestion is occurring (in this case, the B value will be high). (4) A route that leads to an area that is being guided to many vehicles as a "recommended section" (in this case, the J value described below will be high). (5) A route with many turns (in this case, the C value described below will be high). (6) A long route (in this case, the total S value described below will be high).

S, C, J, and B values are defined as score values. Because the roads in a parking lot are arranged in a grid, the edges that make up each grid are called routes. The S value, denoted by Sn, indicates the distance traveled in a straight line. The C value, denoted by Cn, indicates the total number of turns made by the C values. The J value, denoted by Jn, indicates the number of vehicles recommended to use that route. The B value, denoted by Bn, indicates the status of obstacles on that route. Here, n indicates the score values of the S, C, J, and B values. n is a natural number. The total value of the S, C, J, and B values on a route is the route score. The B value may be set by, for example, the parking lot manager entering it into the parking lot server 1, or it may be set by, for example, image recognition of surveillance camera footage.

Let's consider a parking lot 200 as shown in Figure 3, and the case where a target vehicle 301 is guided from the location shown in the figure to the recommended parking position 203a, shown shaded. For this parking lot 200, the route scores are set as shown in Figure 6. Note that in Figures 6 to 10, score values are indicated by circles. In this case, the recommended route 501 would be as shown in Figure 7. In an actual parking lot, there may be parked vehicles or the road may be closed for some reason, resulting in a route score like that shown in Figure 8. In this case, the recommended route would be the route with a "route score of 11" that avoids congestion as shown in Figure 10, rather than the route with a "route score of 14" that waits for a parked vehicle 302 as shown in Figure 9.

The optimal route from the position of the target vehicle 301 to the recommended parking position 203a is then derived as follows. In this example, the route is derived based on the Dijkstra algorithm, with the S value, C value, J value, and B value weighted appropriately. The weighting is varied depending on the shape of the parking lot, the width of the road, etc. If psychological reactance (such as a route for making a U-turn) is taken into consideration, for example, another algorithm may be used.

Next, the route determination unit 123 uses the network communication unit 112 to provide the network communication unit 212 with the optimal route to the recommended parking location 203a (step S308). In the vehicle-mounted device 2, the guidance information determination unit 252 recognizes that the network communication unit 212 has received the optimal route to the recommended parking location 203a, and calculates a risk score from the vehicle's position and the optimal route (step S404).

When the vehicle-mounted device 2 receives a recommended route in the target vehicle 301, if the instructions change from the guidance given up until that point (for example, an instruction to go straight changes to an instruction to turn right or left), the driver may be unable to comply with the instructions or may engage in dangerous driving such as sudden steering or braking in order to comply with the instructions. To avoid this, if there is a change in the recommended route, the following elements are quantified and a risk score is derived. Note that if the guidance does not change even when the route is changed, the risk score is zero. Also, if the route does not change, the risk score is zero. Also, a high risk score means that the safety of driving based on the changed route is low.

The elements to be quantified are: (1) There is a change in the content of the current guidance (a right or left turn followed by a right or left turn in the opposite direction will have a very high score, going straight followed by a right or left turn will have a high score, and going straight followed by a right or left turn will have a low score). (2) The distance to the next intersection (a short distance will have a very high score, a long distance will have a low score).

Next, the guidance information determination unit 252 determines whether the risk score is less than a predetermined threshold (step S405). If the risk score is not less than the predetermined threshold (step S405: NO), the guidance information determination unit 252 causes the network communication unit 212 to request the network communication unit 112 to search for a new route (step S406) and executes the processing of step S401. If the risk score is less than the predetermined threshold (step S405: YES), the guidance information determination unit 252 derives route guidance from the route and the vehicle's position (step S407) and displays the route guidance (step S408).

Next, the guidance information determination unit 252 determines whether or not it is OK to end the guidance (step S409). The guidance may be ended when the target vehicle 301 reaches the recommended parking position 203a (or its vicinity), or when, for example, an attendant is guiding the vehicle near the recommended parking position 203a and the driver or other person performs an input operation to end the guidance. If it is OK to end the guidance (step S409: YES), the guidance information determination unit 252 displays the parking position (step S410) and causes the network communication unit 212 to notify the network communication unit 112 that the guidance has ended (step S411). If it is not OK to end the guidance (step S409: NO), the guidance information determination unit 252 executes the processing of step S401.

On the other hand, if the network communication unit 212 sends a request to re-search the route to the network communication unit 112 (step S406), the network communication unit 112 receives the request to re-search the route from the network communication unit 212 (step S309). Note that if a request to re-search the route is not sent, step S309 is omitted.

Next, the route determination unit 123 determines whether a route re-search request has been received (step S310). If a route re-search request has been received (step S310: YES), the route determination unit 123 executes the process of step S301. If a route re-search request has not been received (step S310: NO), the route determination unit 123 waits for a certain period of time (step S311) and then executes the process of step S301.

Furthermore, if the in-vehicle device 2 notifies that the guidance has ended (step S411), the route determination unit 123 removes the in-vehicle device ID of that in-vehicle device 2 from the list of route guidance targets (step S312).

11 and 12 show an example in which the route for the target vehicle 301 (target vehicle 301a) is changed from a route that goes straight through the intersection 206 to a route that turns left at the intersection 206. The example shown in FIG. 11 is a case in which the risk score is below the threshold value after the route is changed. The example shown in FIG. 12 is a case in which the risk score is equal to or greater than the threshold value after the route is changed. In FIGS. 11 and 12, the positions of the target vehicle 301 at the time the changed route was received are shown as target vehicle 301b and target vehicle 301c. Target vehicle 301c is closer to the intersection 206 than target vehicle 301b. As shown in FIGS. 11 and 12, guidance information G1 indicating going straight is displayed on the display input unit 23 of target vehicle 301a. In contrast, in the example shown in FIG. 11, guidance information G2 indicating a left turn is displayed on the display input unit 23 of target vehicle 301b. On the other hand, in the example shown in FIG. 12, guidance information G3 indicating going straight is displayed on the display input unit 23 of target vehicle 301c.

(Action and effect)
In the parking location guidance system 5, parking lot server 1, in-vehicle device 2, and parking location guidance method configured as described above, the parking lot server 1 determines the parking location of the target vehicle and the route to reach the parking location, and the in-vehicle device 2 determines the guidance information to be output based on the route determined by the parking lot server 1 and the vehicle's position. Therefore, according to the parking location guidance system 5, parking lot server 1, in-vehicle device 2, and parking location guidance method of the embodiment, the route to the parking location can be appropriately determined.

(Other embodiments)
The above describes in detail the embodiments of the present disclosure with reference to the drawings, but the specific configuration is not limited to this embodiment, and design changes and the like are also included within the scope that does not deviate from the gist of the present disclosure.

<Computer Configuration>
FIG. 13 is a schematic block diagram illustrating the configuration of a computer according to at least one embodiment.
The computer 90 includes a processor 91 , a main memory 92 , a storage 93 , and an interface 94 .
The parking lot server 1 and the vehicle-mounted device 2 described above are implemented in a computer 90. The operations of the above-mentioned processing units are stored in the form of a program in a storage 93. The processor 91 reads the program from the storage 93, loads it into the main memory 92, and executes the above-mentioned processing in accordance with the program. The processor 91 also allocates storage areas in the main memory 92 corresponding to the above-mentioned storage units in accordance with the program.

The program may be for realizing some of the functions to be performed by the computer 90. For example, the program may be combined with other programs already stored in storage or implemented in other devices to achieve the functions. In other embodiments, the computer may include a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to or instead of the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), and FPGA (Field Programmable Gate Array). In this case, some or all of the functions realized by the processor may be realized by the integrated circuit.

Examples of storage 93 include HDD (Hard Disk Drive), SSD (Solid State Drive), magnetic disk, magneto-optical disk, CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disc Read Only Memory), semiconductor memory, etc. Storage 93 may be internal media directly connected to the bus of computer 90, or external media connected to computer 90 via interface 94 or a communication line. Furthermore, if this program is distributed to computer 90 via a communication line, the computer 90 that receives the program may expand the program into main memory 92 and execute the above-mentioned processing. In at least one embodiment, storage 93 is a non-transitory, tangible storage medium.

<Additional Notes>
The parking location guidance system 5 described in each embodiment can be understood, for example, as follows.

(1) A parking location guidance system 5 according to a first aspect is a parking location guidance system 5 comprising a server (parking lot server 1) and an in-vehicle device 2, in which the server comprises a parking location determination unit 122 that determines a parking location (recommended parking location 204a) for a target vehicle 301, a route determination unit 123 that determines a route for the target vehicle to reach the parking location, and a first communication unit (communication unit 11) that transmits information indicating the route to the in-vehicle device, and the in-vehicle device comprises a second communication unit (communication unit 21) that receives information indicating the route and a guidance information determination unit 252 that determines guidance information to be output based on the route and the vehicle's position. According to this aspect and each of the following aspects, a route to a parking location can be appropriately determined.

(2) The parking location guidance system 5 according to the second aspect is (1) the parking location guidance system 5, in which, when the route is changed, the guidance information determination unit 252 determines whether to accept the changed route. According to this aspect, the on-board device, which is able to grasp the actual situation within the parking lot, can determine whether to accept the changed route.

(3) A parking location guidance system 5 according to a third aspect is the parking location guidance system 5 according to (2), in which the guidance information determination unit 252 determines whether to accept the changed route based on the safety level of traveling based on the changed route. According to this aspect, a safe route can be selected.

(4) A parking location guidance system 5 according to a fourth aspect is the parking location guidance system 5 of any one of (1) to (3), in which the parking location determination unit 122 determines the parking location of the target vehicle according to attributes of the target vehicle, including at least one of the following: the vehicle is a vehicle that externally charges a storage battery installed as a power source for driving the vehicle, or the vehicle is permitted to park in a parking location allocated only to specified registered vehicles. According to this aspect, the parking location can be determined appropriately.

(5) A parking location guidance system 5 according to a fifth aspect is the parking location guidance system 5 of any one of (1) to (4), in which the parking location determination unit 122 repeatedly determines the parking location of the target vehicle and the route determination unit 123 repeatedly determines the route until guidance for the target vehicle is completed. This aspect makes it possible to appropriately respond to changes in the situation within the parking lot and with other vehicles.

1 Parking lot server 2 Vehicle-mounted device 5 Parking location guidance system 11 Communication unit 12 Processing unit 122 Parking location determination unit 123 Route determination unit 252 Guidance information determination unit

Claims (6)

A parking location guidance system including a server and an in-vehicle device,
The server:
a parking position determination unit that determines a parking position of a target vehicle;
a route determination unit that determines a route for the target vehicle to reach the parking position;
a first communication unit that transmits information indicating the route to the vehicle-mounted device;
The vehicle-mounted device,
a second communication unit that receives information indicating the route;
a guidance information determination unit that determines guidance information to be output based on the route and the vehicle's position,
when the route is changed, the guidance information determination unit calculates a risk score determined in correspondence with a combination of an instruction relating to a right turn, a left turn, or going straight before the change and an instruction relating to a right turn, a left turn, or going straight after the change, and determines whether to accept the changed route based on a comparison between the calculated risk score and a predetermined determination threshold value;
Parking location guidance system. The parking position determination unit determines the parking position of the target vehicle according to attributes of the target vehicle, including at least one of the following: the target vehicle is a vehicle that charges a storage battery mounted thereon from an external source as a power source for driving the vehicle; or the target vehicle is a vehicle that is permitted to park in a parking position allocated only to predetermined registered vehicles.
The parking location guidance system according to claim 1 . Until the guidance for the target vehicle is completed,
The parking position determination unit repeatedly determines the parking position of the target vehicle,
The route determination unit repeatedly determines the route.
3. The parking location guidance system according to claim 1 or 2 . A server of a parking location guidance system including a server and an in-vehicle device,
The server:
a parking position determination unit that determines a parking position of a target vehicle;
a route determination unit that determines a route for the target vehicle to reach the parking position;
a first communication unit that transmits information indicating the route to the vehicle-mounted device;
The vehicle-mounted device,
a second communication unit that receives information indicating the route;
a guidance information determination unit that determines guidance information to be output based on the route and the vehicle's position;
Equipped with
when the route is changed, the guidance information determination unit calculates a risk score determined in correspondence with a combination of an instruction relating to a right turn, a left turn, or going straight before the change and an instruction relating to a right turn, a left turn, or going straight after the change, and determines whether to accept the changed route based on a comparison between the calculated risk score and a predetermined determination threshold value;
server. A parking location guidance system including a server and an in-vehicle device,
The server:
a parking position determination unit that determines a parking position of a target vehicle;
a route determination unit that determines a route for the target vehicle to reach the parking position;
a first communication unit that transmits information indicating the route to the vehicle-mounted device;
The vehicle-mounted device,
a second communication unit that receives information indicating the route;
a guidance information determination unit that determines guidance information to be output based on the route and the vehicle's position;
Equipped with
when the route is changed, the guidance information determination unit calculates a risk score determined in correspondence with a combination of an instruction relating to a right turn, a left turn, or going straight before the change and an instruction relating to a right turn, a left turn, or going straight after the change, and determines whether to accept the changed route based on a comparison between the calculated risk score and a predetermined determination threshold value;
Onboard equipment. A parking location guidance method using a server and an in-vehicle device,
In the server,
determining a parking position of the target vehicle;
determining a route for the target vehicle to reach the parking position;
transmitting information indicating the route to the vehicle-mounted device;
In the in-vehicle device,
receiving information indicative of the route;
determining guidance information to be output based on the route and the vehicle position;
In the step of determining the guidance information , when the route is changed, a risk score is calculated corresponding to a combination of an instruction relating to a right turn, a left turn, or going straight before the change and an instruction relating to a right turn, a left turn, or going straight after the change, and whether or not to accept the changed route is determined based on a comparison between the calculated risk score and a predetermined determination threshold value.
Parking location guidance method.