Information processing device

Abstract

To provide a technology enabling grasping a time estimated to require parking to a parking lot in visiting a destination.SOLUTION: A control unit of an information processing device collects parking completion times having been taken respectively by a plurality of first vehicles from entering a prescribed range of a target destination to completing parking in a parking lot of a target destination in visiting the target destination in the past. The control unit of the information processing device determines a time estimated to be taken by a second vehicle from entering the prescribed range of the target destination to completing parking in the parking lot in accordance with the collected parking completion times of the respective first vehicles. The control unit of the information processing device stores the determined estimated time.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device. [Background technology]

[0002] Patent Document 1 discloses an information processing device. The information processing device disclosed in Patent Document 1 acquires the number of passing vehicles from sensors placed at the entrances and exits of sections within a parking lot. The information processing device calculates the number of vehicles remaining in the aisles within the section based on the number of passing vehicles. The information processing device then notifies at least one of the full or empty status of the section and the number of available parking spaces, as well as the number of remaining vehicles, to vehicles in the parking lot and vehicles attempting to enter the parking lot. [Prior art documents] [Patent documents]

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

[0004] The present disclosure aims to provide a technology that makes it possible to know the estimated time required to park in a parking lot when visiting a destination. [Means for solving the problem]

[0005] The information processing device according to the present disclosure includes: Collecting parking completion times taken by each of a plurality of first vehicles from entering a predetermined range of the target destination to completing parking in a parking lot of the target destination when the first vehicles have previously visited the target destination; Determining an estimated time required for a second vehicle to complete parking at the parking lot after entering the predetermined range of the target destination according to the collected parking completion time of each first vehicle; storing the determined estimated time; The controller is configured to: [Effects of the Invention]

[0006] The present disclosure makes it possible to know the estimated time required to park in a parking lot when visiting a destination. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing a schematic configuration of a navigation system. [Figure 2] FIG. 2 is a block diagram illustrating an example of a functional configuration of the server. [Figure 3] FIG. 3 is a diagram showing an example of a table configuration of facility information stored in the facility information database. [Figure 4] FIG. 4 is a diagram showing an example of a table configuration of estimated time information held in the estimated time information database. [Figure 5] FIG. 5 is a flowchart of a first process executed by the control unit of the server. [Figure 6] FIG. 6 is a flowchart of the second process executed by the control unit of the server. DETAILED DESCRIPTION OF THE INVENTION

[0008] When a vehicle moves to a destination, it may take time to park in a parking lot even though the vehicle has approached the destination. This creates a problem in that it is impossible to predict the time it will take to actually park the vehicle in the parking lot after the vehicle has approached the destination. The information processing device according to the present disclosure solves such a problem.

[0009] Here, it can be assumed that the time it took for a vehicle to enter a predetermined area of the destination and park in a parking lot when it visited the destination in the past is the same time now. Therefore, by understanding the time it took for multiple vehicles to enter a predetermined area and park in a parking lot when they visited the destination in the past, it is possible to estimate the time it takes for a general vehicle to approach a destination and park in a parking lot in the present.

[0010] Therefore, a control unit of an information processing device according to the present disclosure collects parking completion times measured from the time a plurality of first vehicles entered a predetermined range of the target destination until parking in the parking lot of the target destination was completed when the first vehicles previously visited the target destination. The control unit of the information processing device determines an estimated time required for a second vehicle from the time the second vehicle entered a predetermined range of the target destination until parking in the parking lot was completed, based on the collected parking completion times of each first vehicle. The control unit of the information processing device then stores the estimated time. Here, the first vehicle is a vehicle that has previously visited the target destination and is the vehicle for which parking completion times are to be collected. The second vehicle is a vehicle that may visit the target destination in the future.

[0011] As described above, the information processing device determines and stores the estimated time based on the parking completion time of each first vehicle. This makes it possible to know the estimated time required to park in a parking lot when visiting a target destination.

[0012] Specific embodiments of the present disclosure will be described below with reference to the accompanying drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, etc. described in each embodiment are not intended to limit the technical scope of the disclosure to those configurations.

[0013] <Embodiment> (System Overview) A navigation system 1 in this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing a schematic configuration of the navigation system 1. The navigation system 1 is configured to include a plurality of in-vehicle devices 100 and a server 200. In the navigation system 1, the plurality of in-vehicle devices 100 and the server 200 are connected to each other via a network N1. The network N1 may be, for example, a WAN (Wide Area Network), which is a global public communication network such as the Internet, or a telephone communication network such as a mobile phone.

[0014] (In-vehicle device) The in-vehicle device 100 is a device mounted on the vehicle 10. The in-vehicle device 100 outputs various pieces of information to the user of the vehicle 10 (displaying information on a display, outputting audio, etc.). The in-vehicle device 100 is, for example, a car navigation system. The user of the vehicle 10 inputs information about a facility at the destination (for example, the facility name, etc.) to the in-vehicle device 100. The in-vehicle device 100 transmits destination information indicating the current position (starting point) and destination of the vehicle 10 to the server 200 via the network N1.

[0015] The in-vehicle device 100 also acquires the current position of the vehicle 10 from a GPS sensor of the vehicle 10. The in-vehicle device 100 transmits the acquired position information indicating the current position of the vehicle 10 to the server 200 in real time via the network N1. The operating status of the engine or motor is acquired from an electronic control unit (ECU) that controls the running of the vehicle 10. The in-vehicle device 100 transmits the acquired operating information indicating the operating status of the engine or motor to the server 200 in real time via the network N1.

[0016] The in-vehicle device 100 receives notification information from the server 200 via the network N1. Here, the notification information is information for notifying the user of the vehicle 10 of the estimated time (hereinafter, sometimes referred to as "estimated time") that will be required from when the vehicle 10 enters the premises of the facility that is the destination until when the vehicle 10 is parked in the facility's parking lot. The in-vehicle device 100 outputs the notification information to the user of the vehicle 10, so that the user of the vehicle 10 can know the estimated time. Details of the notification information will be described later.

[0017] Furthermore, the vehicle 10 of the user who plans to visit the destination may be referred to as vehicle 10A to be distinguished from other vehicles 10. Furthermore, the in-vehicle device 100 mounted on the vehicle 10A may be referred to as in-vehicle device 100A to be distinguished from other in-vehicle devices 100.

[0018] (server) The server 200 is a server device for supporting the user of the vehicle 10. The server 200 receives destination information from the in-vehicle device 100A via the network N1. At this time, a parking lot at the destination of the user of the vehicle 10A may be crowded. In this case, even though the vehicle 10A has entered the premises of the facility (hereinafter, may be simply referred to as the "destination") that is the destination of the user of the vehicle 10A, it may take time to park the vehicle 10A in a parking lot provided on the premises of the destination. This causes a problem in that it is not possible to predict the time it will take for the user of the vehicle 10A to actually park the vehicle 10A in the parking lot after entering the premises of the destination.

[0019] On the other hand, it can be assumed that the average time taken from when multiple vehicles 10 visited the destination in the past to when they entered the destination site and when they parked in the parking lot is equivalent to the time taken from when vehicle 10A currently enters the destination site and when it parks in the parking lot. Therefore, server 200 can calculate the estimated time by grasping the time taken from when each vehicle 10 visited the destination in the past to when it entered the destination site and when it parked in the parking lot.

[0020] Therefore, the server 200 acquires the time taken from when each of the multiple vehicles 10 entered the designated area until parking in the designated parking lot when the vehicle 10 visited the destination in the past (hereinafter, this may be referred to as the "parking completion time"). Here, the destination site is designated as the designated area. The designated parking lot is a parking lot provided on the destination site. The server 200 then calculates an estimated time according to the parking completion time for each of the multiple vehicles 10, and outputs (transmits) notification information to the in-vehicle device 100A. Details of how the server 200 calculates the estimated time will be described later.

[0021] The server 200 is configured to include a computer having a processor 210, a main memory 220, an auxiliary memory 230, and a communication interface (communication I / F) 240. The processor 210 is, for example, a CPU (Central Processing Unit) or a DSP (Digital Signal Processor). The main memory 220 is, for example, a RAM (Random Access Memory). The auxiliary memory 230 is, for example, a ROM (Read Only Memory). The auxiliary memory 230 is, for example, a HDD (Hard Disk Drive) or a disc recording medium such as a CD-ROM, a DVD disc, or a Blu-ray disc. The auxiliary memory 230 may also be a removable medium (portable storage medium). Examples of removable media include a USB memory or an SD card. The communication I / F 240 is, for example, a LAN (Local Area Network) interface. It is an interface board or a wireless communication circuit for wireless communication.

[0022] In the server 200, the auxiliary storage unit 230 stores an operating system (OS), various programs, various information tables, and the like. In addition, in the server 200, the processor 210 loads the programs stored in the auxiliary storage unit 230 into the main storage unit 220 and executes them, thereby realizing various functions as described below. However, some or all of the functions of the server 200 may be realized by hardware circuits such as ASIC or FPGA. Note that the server 200 does not necessarily have to be realized by a single physical configuration, and may be composed of multiple computers that cooperate with each other. Note that, like the server 200, the in-vehicle device 100 also includes a computer.

[0023] (Functional configuration) Next, the functional configuration of the server 200 that constitutes the navigation system 1 will be described with reference to Fig. 2 to Fig. 4. Fig. 2 is a block diagram that schematically shows an example of the functional configuration of the server 200. The server 200 includes a control unit 201, a communication unit 202, a facility information database 203 (facility information DB203), and an estimated time information database 204 (estimated time information DB204).

[0024] The control unit 201 has a function of performing arithmetic processing for controlling the server 200. The control unit 201 can be realized by the processor 210 in the server 200. The communication unit 202 has a function of connecting the server 200 to the network N1. The communication unit 202 can be realized by the communication I / F 240 in the server 200.

[0025] The facility information DB 203 has a function of storing facility information. The facility information includes information indicating the designated range of each facility and the designated parking lot of each facility. The facility information also includes information related to the parking completion time when each of multiple vehicles 10 visited each facility in the past. The facility information DB 203 can be realized by the auxiliary storage unit 230 in the server 200. FIG. 3 is a diagram showing an example of a table configuration of facility information stored in the facility information DB 203.

[0026] 3, the facility information includes a facility ID field, a designated range field, a parking lot ID field, a vehicle ID field, an entry time field, a parking time field, a parking completion time field, and a congestion level field. The facility ID field stores an identifier (facility ID) for identifying a facility visited by the vehicle 10. The designated range field stores information indicating a designated range associated with the facility of the corresponding facility ID. In other words, the designated range field stores information indicating the range of the premises of the facility of the corresponding facility ID.

[0027] The parking lot ID field stores an identifier (parking lot ID) for identifying a designated parking lot associated with the facility of the corresponding facility ID. Here, there may be multiple designated parking lots associated with the facility. In other words, if there are multiple designated parking lots on the premises of the facility, such as a first parking lot and a second parking lot, multiple parking lot IDs are stored in the parking lot ID field. The vehicle ID field stores an identifier for identifying the vehicle 10 parked in the designated parking lot of the corresponding parking lot ID.

[0028] The entry time field stores information indicating the time (entry time) when the vehicle with the corresponding vehicle ID entered the designated range (facility site) designated in the corresponding designated range field. The parking time field stores the time (parking time) when the vehicle 10 with the corresponding vehicle ID parked in the designated parking lot with the corresponding parking lot ID.

[0029] Here, the control unit 201 receives position information and operation information from the in-vehicle device 100 in real time via the communication unit 202. Therefore, the control unit 201 can identify the time when the vehicle 10 entered the designated area by referring to the position information. Furthermore, the control unit 201 can determine whether the vehicle 10 has parked in a parking lot by referring to the position information and the operation information. Specifically, the control unit 201 determines that the vehicle 10 is located at the designated parking lot when it determines that the vehicle 10 is located at the designated parking lot by referring to the position information, and when it determines that the engine or motor of the vehicle 10 has stopped operating by referring to the operation information. When the control unit 201 determines that the vehicle 10 has parked in the designated parking lot, it identifies the time when the engine or motor stopped as the parking time.

[0030] Therefore, the control unit 201 stores the vehicle ID of the vehicle 10 in a vehicle ID field corresponding to the parking lot ID of the designated parking lot where the vehicle 10 is parked. The control unit 201 also stores the identified entry time in an entry time field corresponding to the parking lot ID of the designated parking lot where the vehicle 10 is parked. The control unit 201 also stores the identified parking time in a parking time field corresponding to the parking lot ID of the designated parking lot where the vehicle 10 is parked.

[0031] The parking completion time field stores the time (length of time) from the corresponding entry time to the corresponding parking time as the parking completion time. The control unit 201 calculates the time difference between the corresponding parking time and the corresponding entry time as the parking completion time. Then, the control unit 201 stores the calculated parking completion time in the parking completion time field.

[0032] The congestion level field stores a level (congestion level) that indicates the congestion status of the specified range. The congestion level is divided into multiple levels, and the more congested the specified range is, the higher the level is set. In addition, the congestion level field stores the congestion level of the corresponding specified range from the corresponding entry time to the corresponding parking time.

[0033] Specifically, the congestion level field stores the congestion level of the designated range at the time when the vehicle 10 of the corresponding vehicle ID enters as the congestion level of the designated range. Note that the congestion level field may store, for example, the congestion level of the designated range at the time when the vehicle 10 of the corresponding vehicle ID parks as the congestion level of the designated range. Furthermore, the congestion level field may store, for example, the maximum congestion level from the time when the vehicle 10 of the corresponding vehicle ID enters to the time when it parks.

[0034] Here, the congestion level is determined, for example, by vehicle density. In this case, the control unit 201 identifies the number of vehicles present within a specified range from the current positions of the multiple vehicles (multiple vehicles 10). The control unit 201 calculates the vehicle density by dividing the number of vehicles present within the identified specified range by the area of the specified range. The control unit 201 calculates the vehicle density at the time the vehicle 10 enters, and stores the congestion level associated with the vehicle density in the congestion level field.

[0035] The congestion level does not have to be determined by the control unit 201 calculating the vehicle density. The congestion level may be determined by the control unit 201 acquiring the congestion degree or the like from an external server. The vehicle ID field may also include the vehicle ID of the vehicle 10A. In other words, the vehicle 10A may be a vehicle for which parking completion times have been collected in the past.

[0036] The control unit 201 can grasp the parking completion time when the vehicle 10 has visited each facility in the past by acquiring the facility information stored in the facility information DB 203. Therefore, the control unit 201 calculates the estimated time using the parking completion time for each facility.

[0037] In this embodiment, the control unit 201 calculates an estimated time for each congestion level. Specifically, the control unit 201 identifies congestion level fields in the facility information that store the same congestion level, and acquires all parking completion times corresponding to the identified congestion level fields. The control unit 201 then calculates the average value of the acquired parking completion times as the estimated time. Note that the control unit 201 performs this process for all congestion levels. In other words, the control unit 201 calculates an estimated time corresponding to each congestion level.

[0038] Here, there may be multiple designated parking lots for the facility that is the destination of vehicle 10. In this case, the user of vehicle 10A parks in one of the multiple designated parking lots. Therefore, control unit 201 acquires all parking completion times when vehicle 10 is parked in one of the multiple designated parking lots and calculates an estimated time. This makes it possible to calculate an estimated time corresponding to the parking completion time taken for multiple vehicles 10 to park in one of the multiple designated parking lots.

[0039] The control unit 201 stores the calculated estimated time in the estimated time information DB 204. Specifically, the control unit 201 associates the estimated time for each congestion level with the facility and stores the information in the estimated time information DB 204. The estimated time information DB 204 has a function of storing estimated time information. The estimated time information is information indicating the estimated time for each congestion level for each facility. FIG. 4 is a diagram showing an example of the table configuration of estimated time information stored in the estimated time information DB 204. As shown in FIG. 4, the estimated time information has a facility ID field, a congestion level field, and an estimated time field.

[0040] The facility ID field stores a facility ID for identifying a facility. Here, the facility ID stored in the estimated time information is the same as the facility ID stored in the facility ID field of the facility information held in the facility information DB 203. The congestion level field stores the congestion level within the specified range of the facility with the corresponding facility ID. The estimated time field stores the estimated time corresponding to each congestion level.

[0041] The control unit 201 can grasp the estimated time at each congestion level in each facility by acquiring the estimated time information stored in the estimated time information DB 204.

[0042] The control unit 201 receives destination information from the in-vehicle device 100A via the communication unit 202. Then, the control unit 201 calculates the time when the vehicle 10A is expected to enter a predetermined range (hereinafter, may be referred to as "estimated arrival time"). For example, the control unit 201 refers to the current position of the vehicle 10A and identifies the time when the vehicle 10A starts moving after receiving the destination information from the in-vehicle device 100A as the departure time. Then, the control unit 201 calculates the time when the vehicle 10A is expected to enter the predetermined range (estimated entry time) from the position of the vehicle 10A at the departure time and the departure time.

[0043] Furthermore, the control unit 201 references the facility information stored in the facility information DB 203 to estimate the congestion level at the predicted entry time. Specifically, the control unit 201 references the entry time field and the congestion level field in the facility information to acquire the congestion levels when the vehicle 10 previously entered the designated area during the same time period as the predicted entry time. Here, the time period is set at, for example, one-hour intervals. The control unit 201 determines, for example, the most frequent value of the acquired congestion levels as the congestion level to be estimated at the predicted entry time.

[0044] Note that the control unit 201 may estimate the congestion level at the predicted entry time using a method other than the above. For example, the control unit 201 may determine the congestion level at the predicted entry time by acquiring the degree of congestion estimated at the predicted entry time from an external server.

[0045] Furthermore, in this embodiment, the server 200 determines the congestion level at the predicted entry time based on the congestion level when the vehicle 10 previously entered the designated area during the same time period as the predicted entry time. However, the server 200 may also determine the congestion level at the predicted entry time based on the congestion level when the vehicle 10 entered the designated area on the same day of the week as the day of the week to which the predicted entry time belongs. Furthermore, the time when the vehicle 10A enters the designated area may fall during a predetermined period such as a tourist season. In such a case, the server 200 may determine the congestion level at the predicted entry time based on the congestion level when the vehicle 10 entered the designated area during a period corresponding to the predetermined period in the past.

[0046] Then, the control unit 201 refers to the estimated time information stored in the estimated time information DB 204, and determines the estimated time corresponding to the congestion level estimated at the predicted entry time as the estimated time to be notified to the user of the vehicle 10A. The control unit 201 outputs (transmits) notification information for notifying the user of the vehicle 10A of the estimated time to the in-vehicle device 100A via the communication unit 202. At this time, the control unit 201 refers to the position information of the vehicle 10A, and transmits the notification information to the in-vehicle device 100A at the timing when the vehicle 10A enters the premises of the destination (designated range). In this way, the in-vehicle device 100A can notify the user of the vehicle 10A of the estimated time at the timing when the vehicle 10A enters the premises of the destination.

[0047] (First process) Next, a first process executed by the control unit 201 of the server 200 in the navigation system 1 will be described with reference to Fig. 5. Fig. 5 is a flowchart of the first process executed by the control unit 201. The first process is a process for updating facility information and calculating an estimated time. Execution of the first process starts when the control unit 201 receives destination information from the in-vehicle device 100.

[0048] In the first process, first, in S101, the destination information received from the in-vehicle device 100 is referenced, and the destination of the user of the vehicle 10 is acquired. Next, in S102, the facility information held in the facility information DB 203 is referenced, and a specified range (range of the destination site) associated with the destination of the user of the vehicle 10 is identified. Next, in S103, acquisition of the current position of the vehicle 10 is started. That is, the control unit 201 references the position information of the vehicle 10 received in real time, and starts monitoring the current position of the vehicle 10.

[0049] Next, in S104, it is determined whether the current position of the vehicle 10 is within the designated range. If a negative determination is made in S104, the vehicle 10 has not entered the designated range and is moving toward the destination, so the processing of S104 is executed again. If a positive determination is made in S104, it is determined in S105 that the vehicle 10 has entered the designated range. Therefore, the entry time is acquired in S105.

[0050] Next, in S106, the current position and operation information of the vehicle 10 are referenced to determine whether parking of the vehicle 10 has been completed. If a negative determination is made in S106, parking of the vehicle 10 has not been completed, and the processing of S106 is executed again. If a positive determination is made in S106, the parking time is acquired in S107.

[0051] Next, in S108, the congestion level of the specified range at the entry time is acquired. Next, in S109, the facility information held in the facility information DB 203 is updated using the acquired entry time, parking time, and congestion level. Next, in S110, the updated facility information is referenced and an estimated time is calculated. Next, in S111, the estimated time information held in the estimated time information DB 204 is updated to save the calculated estimated time. Then, the first process ends.

[0052] (Second process) Next, the second process executed by the control unit 201 of the server 200 in the navigation system 1 will be described with reference to FIG. 6. FIG. 6 is a flowchart of the second process executed by the control unit 201. The second process is a process for transmitting notification information to the in-vehicle device 100A. Execution of the second process starts when the control unit 201 receives destination information from the vehicle 10A. Note that the second process may be executed in parallel with the first process. In other words, the first process may be executed in parallel with the second process, with the vehicle 10A being the target for collecting parking completion times.

[0053] In the second process, first, in S201, the destination of vehicle 10A is acquired from the destination information. Next, in S202, facility information held in facility information DB 203 is referenced, and a designated area associated with the destination of vehicle 10A is identified. Next, in S203, the estimated arrival time of vehicle 10A is acquired. Next, in S204, the facility information is referenced, and the congestion level in the designated area at the estimated arrival time of vehicle 10A is estimated. Next, in S205, an estimated time corresponding to the congestion level in the designated area predicted at the estimated arrival time of vehicle 10A is acquired from estimated time information held in estimated time information DB 204.

[0054] Next, in S206, it is determined whether the vehicle 10A has entered the designated range. If a negative determination is made in S206, the vehicle 10A has not entered the designated range, and therefore it is not time to transmit the notification information. Therefore, in this case, the processing of S206 is executed again. On the other hand, if a positive determination is made in S206, it is time to transmit the notification information, and therefore the notification information is transmitted to the in-vehicle device 100A in S207. Then, the second processing is terminated. Note that in this embodiment, the timing for transmitting the notification information is the timing when the vehicle 10A enters the designated range. However, the timing for transmitting the notification information is not limited to the timing when the vehicle 10A enters the designated range. The timing for transmitting the notification information may be any timing other than the timing when the vehicle 10A enters the designated range.

[0055] As described above, the navigation system 1 calculates and stores an estimated time based on the parking completion times when multiple vehicles 10 have previously visited the destination. The navigation system 1 also outputs notification information to the in-vehicle device 100A. At that time, the notification information output indicates an estimated time based on the estimated congestion level at the expected arrival time of the vehicle 10A at the destination.

[0056] In this case, there may be multiple designated parking lots for the facility. In this case, all of the parking completion times when vehicle 10 is parked in any of the multiple designated parking lots are acquired, and an estimated time is calculated. This allows the user of vehicle 10A to know the estimated time it will take to park in any of the multiple designated parking lots. In this way, the user of vehicle 10A can know the estimated time it will take to park in a parking lot when visiting a destination.

[0057] (Variation 1) In this embodiment, the server 200 calculates an estimated time according to the congestion level. However, the estimated time does not necessarily have to be according to the congestion level. The server 200, for example, acquires the parking completion time for a plurality of vehicles 10 that have visited a target facility from facility information stored in the facility information DB 203. The server 200 calculates the average value of the parking completion time for the acquired plurality of vehicles 10 (hereinafter, may be referred to as "average time value"). Then, the server 200 may calculate the average time value as the estimated time. This Even in this way, it becomes possible for the user of vehicle 10A to know the estimated time required for parking in a parking lot when visiting a destination.

[0058] (Variation 2) In this embodiment, the server 200 calculates the estimated time using the parking completion time associated with the congestion level. On the other hand, in this modified example, the server 200 calculates the estimated time according to the congestion level without using the parking completion time associated with the congestion level.

[0059] Specifically, the server 200 acquires the parking completion time of each vehicle 10 that visited the target facility from the facility information stored in the facility information DB 203. The server 200 calculates a time average value. Then, the server 200 calculates an estimated time according to the congestion level by adding a weight according to the congestion level to the time average value. The server 200 calculates an estimated time according to the congestion level, for example, by multiplying the time average value by a coefficient determined according to the congestion level. The server 200 may also calculate an estimated time according to the congestion level by adding a time determined according to the congestion level to the time average value. This also makes it possible for the user of the vehicle 10A to know the estimated time required to park in a parking lot when visiting a destination.

[0060] (Variation 3) In this embodiment, the designated range associated with the destination of vehicle 10 is the site of the destination. However, the designated range associated with the facility that is the destination of vehicle 10 does not necessarily have to be the site of the destination. The designated range associated with the facility that is the destination may be a predetermined range that includes the site of the destination. In this way, when the user of vehicle 10A visits the destination, it becomes possible to know the estimated time required from approaching the destination to parking in a parking lot.

[0061] In this case, the predetermined range includes roads and the like outside the destination. Therefore, the server 200 acquires the congestion level of the predetermined range, including the road congestion level, and calculates the estimated time according to the congestion level. This allows the user of the vehicle 10A to know the estimated time required to park in a parking lot near the destination when the area around the destination is congested.

[0062] Furthermore, the destination of vehicle 10 does not necessarily have to be a facility. In this case, the destination of vehicle 10 may be a predetermined area. Here, the predetermined area is, for example, an area defined by administrative divisions such as cities, wards, towns, and villages, or an area such as a tourist destination. In this case, the specified range is defined as the predetermined area or a predetermined range including the predetermined area. In this way, it is possible for the user of vehicle 10A to know the estimated time required for parking in a parking lot when visiting the predetermined area.

[0063] (Variation 4) In this embodiment, the server 200 calculates and stores an estimated time associated with the congestion level. Meanwhile, there is a case where the vehicle 10A visits the destination on a specific day of the week, time period, or season. In this case, it is assumed that the degree of congestion at the destination will differ depending on the attribute (day of the week, time period, or season) to which the timing when the vehicle 10A visits the destination belongs. Therefore, it is assumed that the time required for parking will differ depending on the attribute to which the timing when the vehicle 10A visits the destination belongs. Therefore, the server 200 calculates and stores an estimated time associated with the attribute to which the period belongs.

[0064] Specifically, the server 200 refers to the facility information stored in the facility information DB 203, and acquires the entry time and parking time of each vehicle 10. The server 200 then identifies a period attribute to which the period from when the vehicle 10A enters the designated area until when the vehicle 10A parks in the designated parking lot belongs. Here, the period attribute may be an attribute defined by a time period or a day of the week. The period attribute may also be an attribute defined by a specific period such as a tourist season. The server 200 then acquires the parking completion time when the vehicle 10A enters the designated area and parks in the designated parking lot for the same period attribute, and calculates the estimated time. This makes it possible to grasp the estimated time that varies depending on the period attribute to which the timing of the user of the vehicle 10A visiting the destination belongs.

[0065] Furthermore, even if the congestion level is the same, it is expected that the attributes of users visiting a destination will differ depending on the period attributes (time of day, day of the week, season). User attributes are defined, for example, by the length of time spent at a facility or driving skill. Here, it is expected that during a period when many users who stay at the facility for a short time visit, parking spaces will be more likely to be available even if the facility is crowded, compared to a period when many users who stay at the facility for a long time visit. Furthermore, during a period when many users with high driving skills visit, it is expected that the time required for parking and departing after parking will be shorter, and parking spaces will be more likely to be available, compared to a period when many users with low driving skills visit.

[0066] Therefore, even if the congestion level is the same, it is expected that the pace at which parking spaces become available will be shorter depending on the period attribute. Therefore, the server 200 may calculate an estimated time associated with the period attribute and the congestion level. Specifically, the server 200 obtains the parking completion time when the vehicle 10 enters the designated area and parks in the designated parking lot for each period attribute, for each congestion level, and calculates the estimated time. In this way, it is possible to grasp the estimated time that differs depending on the attribute to which the timing at which the user of the vehicle 10A will arrive at the destination belongs and the congestion level.

[0067] (Variation 5) In this embodiment, if there are multiple designated parking lots for a facility, all of the parking completion times when vehicle 10 parks in any of the multiple designated parking lots are acquired, and an estimated time is calculated. However, if there are multiple designated parking lots for a facility, the parking completion time may be acquired for each designated parking lot, and an estimated time may be calculated for each designated parking lot. In this case, the notification information includes the estimated time for each designated parking lot. This allows the user of vehicle 10A to know the estimated time for each designated parking lot and select a designated parking lot in which to park vehicle 10A.

[0068] (Variation 6) In this embodiment, the notification information is output (transmitted) to the in-vehicle device 100A. However, the notification information does not necessarily have to be output to an external device. Even in this case, the server 200 calculates the estimated time and then stores the estimated time in the estimated time information DB 204. This allows the administrator of the server 200 or the like to know the estimated time required to park in a parking lot when visiting a destination.

[0069] <Other embodiments> The above-described embodiment is merely an example, and the present disclosure may be modified as appropriate within the scope of the present disclosure. Furthermore, the processes and means described in the present disclosure may be freely combined and implemented as long as no technical contradiction occurs.

[0070] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by a single device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0071] The present disclosure can also be realized by providing a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors in the computer read and execute the program. Such a computer program may be provided to the computer via a non-transitory computer-readable storage medium connectable to the computer's system bus or via a network. Non-transitory computer-readable storage media include any type of medium suitable for storing electronic instructions, such as a magnetic disk (e.g., a floppy disk or a hard disk drive (HDD)), an optical disk (e.g., a CD-ROM, a DVD disk, or a Blu-ray disk), a read-only memory (ROM), a random-access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, or an optical card. [Explanation of symbols]

[0072] 1. Navigation system 10. Vehicle 100...In-vehicle equipment 200 Server 201 Control section 202··Communications Department 203 Facility Information DB 204··Estimated Time Information DB

Claims

1. collecting parking completion times taken by each of a plurality of first vehicles from entering a predetermined range of the target destination to completing parking in a parking lot of the target destination when the first vehicles have previously visited the target destination; Determining an estimated time required for a second vehicle to complete parking in the parking lot after entering the predetermined range of the target destination according to the collected parking completion time of each first vehicle; storing the determined estimated time; a controller configured to execute Information processing device.

2. The parking completion time is associated with a congestion state of the predetermined area from the time when each of the first vehicles enters the predetermined area to the time when parking in the parking lot is completed, acquiring the parking completion time includes acquiring the parking completion time associated with a predetermined congestion state; calculating the estimated time includes determining the estimated time in accordance with the parking completion time associated with the acquired predetermined congestion state; The information processing device according to claim 1 .

3. Determining the estimated time includes determining the estimated time according to the acquired parking completion time and a congestion state in the predetermined area. The information processing device according to claim 1 .

4. a period attribute that corresponds to a period from when each of the first vehicles enters the predetermined area to when the first vehicle completes parking in the parking lot; obtaining the parking completion time includes obtaining the parking completion time associated with a predetermined duration attribute; determining the estimated time includes determining the estimated time according to the parking completion time associated with the acquired predetermined period attribute; The information processing device according to claim 1 .

5. a plurality of parking lots are associated with the target destination; acquiring the parking completion time includes acquiring the parking completion time when each of the first vehicles is parked in any of the plurality of parking lots. The information processing device according to claim 1 .

Images