JP2022061160A - Parking lot usage information detection system - Google Patents

Abstract

To provide a parking lot usage information detection system capable of detecting the level of aversion of a user to using a type of an entrance or exit of a parking lot.SOLUTION: A parking lot usage information detection system provided herein is configured to: acquire at least one of opening/closing of a door, change in shift position, and vehicle stop time at an entrance or exit of a parking lot as vehicle behavior in the parking lot; detect a level of aversion of a user driving a vehicle to using the type of the entrance or exit of the parking lot on the basis of the acquired information; and provide various assistance using the detected level of aversion of the user to the use.SELECTED DRAWING: Figure 5

Description

The present invention relates to a parking lot usage information detection system that detects a user's weakness in using a parking lot type based on information acquired from a vehicle.

When the user moves by car, the information about the parking lot where the car is parked is important information for the user. On the other hand, there are various types (types, structures, types) of parking lots, and depending on the type, use by a specific user may be avoided. Therefore, in order to provide information on parking lots with appropriate contents, it is necessary for the device side that provides information on the types of parking lots that are easy to use and the types of parking lots that are difficult to use for each user. For example, Japanese Patent Application Laid-Open No. 2019-15992 collects the number of forward parkings, the number of backward parkings, the number of turns to the right, the number of turns to the left, etc. A technique has been proposed for identifying and providing parking lots that are easy for users to use and parking lots that are difficult to use.

Japanese Unexamined Patent Publication No. 2019-15992 (page 5-6)

In Patent Document 1 above, on the device side that provides information, it is determined that a parking lot in which a user can easily perform a parking operation with respect to a parking space provided in the parking lot is a parking lot that is easy for the user to use. On the other hand, it is determined that a parking lot that is difficult for the user to perform a parking operation is a parking lot that is difficult for the user to use. For example, a user who often turns back when parking in a left turn is judged to be not good at parking in a left turn, and a parking lot having a parking space capable of parking in a right turn is set as a parking lot that is easy for the user to use. ..

However, the ease of use of the parking lot by the user is not determined only by the ease of parking operation in the parking space, and there are also large factors related to the entrance and exit of the parking lot. For example, in a parking lot where tickets must be issued or settled at the entrance or exit, it is necessary to move the car in one direction at the entrance or exit, but some users are not good at moving such vehicles in one direction. be. The above-mentioned Patent Document 1 does not have a means for grasping the degree of weakness of the user with respect to the types of entrances and exits of such parking lots, and cannot provide appropriate information to the users.

The present invention has been made to solve the above-mentioned conventional problems, and the user uses the parking lot for the type of entrance or exit based on the information on the behavior of the vehicle in the parking lot obtained from the vehicle. It is an object of the present invention to provide a parking lot usage information detection system that makes it possible to detect the degree of weakness in the parking lot.

In order to achieve the above object, the parking lot usage information detection system according to the present invention has an information acquisition means for acquiring the behavior of the vehicle in the parking lot and an entrance to the parking lot or a parking lot based on the information acquired by the information acquisition means. It has a user information detecting means for detecting the degree of weakness of use of the user who gets on the vehicle with respect to the type related to the exit.
Further, the "degree of weakness of user's use" also corresponds to the ease of parking when the user parks in the parking lot (the degree of difficulty of use by the user's subjectivity). That is, a parking lot of a type that the user is not good at is a parking lot that is easy for the user to park, and a parking lot of a type that the user is not good at is a parking lot that is difficult for the user to park.

According to the parking lot usage information detection system according to the present invention having the above configuration, the user's use for the type related to the entrance or exit of the parking lot is based on the information on the behavior of the vehicle in the parking lot acquired from the vehicle. It is possible to detect the degree of weakness. As a result, it becomes possible to provide various kinds of support such as providing information on a parking lot suitable for the user, for example, to a user who moves by car.

It is a schematic block diagram which showed the parking lot use information detection system which concerns on this embodiment. It is a block diagram which showed the structure of the parking lot use information detection system which concerns on this embodiment. It is a figure which showed an example of the probe information stored in the probe information DB. It is a figure which showed an example of the parking lot behavior information stored in the parking lot behavior history DB. It is a figure which showed an example of the user information stored in the user information DB. It is a figure which showed an example of the parking lot type information stored in the parking lot type DB. It is a block diagram which shows typically the control system of the navigation apparatus which concerns on this embodiment. It is a flowchart of the user information detection processing program which concerns on this embodiment. It is a flowchart of the sub-processing program of the 1st weakness degree detection processing which concerns on this embodiment. It is a flowchart of the sub-processing program of the 2nd weakness degree detection processing which concerns on this embodiment. It is a flowchart of the sub-processing program of the 3rd weakness degree detection processing which concerns on this embodiment. It is a figure which showed an example of a ticket-issuing type parking lot. It is a flowchart of the parking lot type detection processing program which concerns on this embodiment. It is a flowchart of the information provision processing program which concerns on this embodiment. It is a figure which showed the guide example of the search result of a parking lot.

Hereinafter, the parking lot usage information detection system according to the present invention will be described in detail with reference to the drawings based on an embodiment embodied. First, a schematic configuration of the parking lot usage information detection system 1 according to the present embodiment will be described with reference to FIGS. 1 and 2. FIG. 1 is a schematic configuration diagram showing a parking lot usage information detection system 1 according to the present embodiment. FIG. 2 is a block diagram showing the configuration of the parking lot usage information detection system 1 according to the present embodiment.

As shown in FIG. 1, the parking lot usage information detection system 1 according to the present embodiment has a server device (parking lot usage information detection device) 3 included in the probe center 2 and a communication (guidance) terminal mounted on the vehicle 4. It basically has a navigation device 5 and the like. Further, the server device 3 and the navigation device 5 are configured to be able to send and receive electronic data to and from each other via the communication network 6. Instead of the navigation device 5, for example, another on-board unit included in the vehicle 4 or a vehicle control ECU for controlling the vehicle 4 may be used. Further, as described later, a communication terminal other than the navigation device (for example, a mobile phone, a smartphone, a tablet terminal, a personal computer, etc.) is used in the parking lot usage information detection system 1 as a target for providing the information generated by the server device 3. It may be further included.

Here, the parking lot usage information detection system 1 according to the present embodiment constitutes a so-called probe car system. Here, the probe car system is a system that collects information using the vehicle 4 as a sensor. Specifically, the vehicle 4 transmits speed data, steering operation, shift position, and other operating conditions of each system to the probe center 2 together with GPS position information via a communication device mounted on the vehicle 4 in advance. A system that reuses the collected data as various information on the center side.

The server device 3 included in the probe center 2 appropriately collects and accumulates probe information (material information) including the current time and travel information from each vehicle 4 traveling nationwide, and variously collects the accumulated probe information. Support information (for example, the degree of weakness of the user's use for the type of parking lot, information on the type of parking lot, accident information, traffic jam information, travel time, etc.) is generated, and the generated support information is distributed to the navigation device 5. It is an information management server that performs various processes using support information. In particular, in the present embodiment, the server device 3 collects information about the behavior of the vehicle 4 in the parking lot from each vehicle 4, and analyzes the collected information to collect the information of the user who is the occupant of each vehicle. Generate user information that specifies the degree of weakness in use for the type of parking lot. Furthermore, by collecting information on the behavior of the vehicle 4 in the parking lot from each vehicle 4 and combining the collected information with the map information, the type of the entrance or exit of each parking lot nationwide can be specified. Generate parking lot type information. Further, the server device 3 performs processing related to facility search and route search using the map information provided in the server device 3 based on the request from the navigation device 5, and in that case, particularly when providing parking information. , Perform processing using the above user information and parking lot type information. For example, parking lots other than the types of parking lots that users are not good at using are preferentially provided as search results.

On the other hand, the navigation device 5 is mounted on the vehicle 4 and displays a map around the position of the own vehicle based on the stored map data, displays the current position of the vehicle on the map image, and sets a guide route. It is an in-vehicle device that provides movement guidance along the route. In addition, the navigation device 5 also provides information on the parking lot in consideration of user information. The details of the navigation device 5 will be described later.

In addition, the communication network 6 includes a large number of base stations located all over the country and a communication company that manages and controls each base station, and the base stations and the communication companies are connected to each other by wire (optical fiber, ISDN, etc.) or wirelessly. It is configured by connecting. Here, the base station has a transceiver (transmitter / receiver) and an antenna for communicating with the navigation device 5. Then, while the base station performs wireless communication between communication companies, it becomes the terminal of the communication network network 6 and relays the communication of the navigation device 5 within the range (cell) of the radio wave of the base station to the server device 3. Has a role to play.

Subsequently, the configuration of the server device 3 included in the parking lot usage information detection system 1 will be described in more detail with reference to FIG.

As shown in FIG. 2, the server device 3 includes a server control unit 11, a probe information DB 12 as an information recording means connected to the server control unit 11, a parking lot behavior history DB 13, a user information DB 14, and a parking lot type. It basically has a DB 15, a server-side map DB 16, and a center communication device 17.

The server control unit 11 is a control unit (MCU, MPU, etc.) that controls the entire server device 3, and is used as a calculation device, a CPU 21 as a control device, and a working memory when the CPU 21 performs various calculation processes. In addition to the RAM 22 and the control program, the ROM 23 in which the user information detection processing program (see FIG. 8), the parking lot type detection processing program (see FIG. 13), the information provision processing program (see FIG. 14), etc., which will be described later, are recorded. , It is provided with an internal storage device such as a flash memory 24 for storing a program read from the ROM 23. The server control unit 11 has various means as a processing algorithm together with the ECU of the navigation device 5 described later. For example, the information acquisition means acquires the behavior of the vehicle in the parking lot. The user information detecting means detects the degree of weakness of the user who gets on the vehicle for the type related to the entrance or exit of the parking lot based on the information acquired by the information acquisition means.

Further, the probe information DB 12 is a storage means for cumulatively storing probe information collected from each vehicle 4 traveling nationwide. In the present embodiment, the probe information collected from the vehicle 4 includes, in particular, (a) the date and time and (b) the area code of the area where the vehicle 4 travels at that date and time, and (c) the link where the vehicle 4 travels. (D) Traveling direction (forward or reverse) of vehicle 4, (e) mileage from link start point (end point), (f) vehicle speed of vehicle 4, (g) shift position of vehicle 4, (h) vehicle The open / closed state of the door of 4 and (i) the open / closed state of the window of the vehicle 4 are included.

The "link start point" and "link end point" are attributes set for both ends (nodes) of the link without depending on the traveling direction of the vehicle. The traveling direction of the vehicle is defined as the direction in which the vehicle enters the link from the start point of the link and exits from the end point of the link as "forward direction", and the direction in which the vehicle enters the link from the end point of the link and exits from the start point of the link is defined as "reverse direction".

However, the probe information does not necessarily include all the information related to the above (a) to (i), and information other than the above (a) to (i) (for example, brake operation amount, yaw rate, acceleration, drive recorder image, etc.) The configuration may include steering angle, etc.).

FIG. 3 is a diagram showing an example of probe information stored in the probe information DB 12. As shown in FIG. 3, the probe information includes a vehicle ID that identifies the source vehicle, information related to the above (a) to (i), and the like. For example, the probe information shown in FIG. 3 shows that the vehicle 4 with the ID “A” is traveling in the positive direction of the link with the ID “100001” in the area code “11” at 9:00:00 on March 2. It is remembered that the car stopped at .80 at a point 40m away from the starting point of the link, then the shift position was changed from "D" to "P", and the driver's seat window was opened. Further, it is remembered that the window was closed at 9:00: 14.50, the shift position was changed from "P" to "D", and the vehicle started running again. Similarly, other probe information is also stored. In the example shown in FIG. 3, probe information is collected from the vehicle at intervals of 200 msec, but the interval of collecting probe information may be shorter or longer than the interval of 200 msec.

Further, the parking lot behavior history DB 13 is generated based on the probe information of the vehicle located near the entrance and exit of the parking lot, among the probe information stored in the probe information DB 12, and is generated based on the probe information of the vehicle located near the entrance and exit of the parking lot. It is a storage means for storing the behavior of the vehicle near the exit and exit. The stored behavior of the vehicle includes identification information (for example, ID, name, position coordinates, etc.) of the parking lot where the vehicle enters or exits, the behavior related to the stop of the vehicle, and the behavior related to the change of the shift position. , The behavior related to the opening and closing of the door of the vehicle and the behavior related to the opening and closing of the window of the vehicle.

FIG. 4 is a diagram showing an example of information stored in the parking lot behavior history DB 13 (hereinafter referred to as parking lot behavior history information). As shown in FIG. 4, the parking lot behavior history information shows the behavior of the vehicle near the entrance and exit of the parking lot, the date and time when the vehicle enters or exits the parking lot, and the parking lot where the vehicle enters or exits. Identification ID, whether the vehicle is stopped, the stop time if the vehicle is stopped, whether the shift position is displaced to R, the distance retracted if the shift position is displaced to R, and the opening and closing of the vehicle door. The presence / absence of the vehicle, the type of the opened / closed door when the vehicle was opened / closed, the opening time, the opening angle, and the presence / absence of the opening / closing of the vehicle window and the type of the opened window when the vehicle was opened / closed are stored.

For example, in the example shown in FIG. 4, the vehicle with ID "A" stops for 14 seconds at the entrance or exit of the parking lot with ID "10101" at 9:00:00.80 on March 2. It is remembered that the driver's seat window was opened while the vehicle was stopped. Similarly, other stop history information is also stored. Then, the server control unit 11 detects the degree of weakness of the user for the type of parking lot by using the parking lot behavior history information shown in FIG. 4 as described later. Furthermore, the type of entrance or exit of each parking lot nationwide is also detected. The map information contained in the server device 3 stores information for specifying the position of the parking lot and the positions of the entrance and exit of the parking lot in advance, and includes the vehicle position information and the map information included in the probe information. By using, the probe information of the vehicle located near the entrance and exit of the parking lot can be extracted, and the parking lot where the vehicle enters or exits can be specified by the server device 3. However, the information that identifies the position of the parking lot and the positions of the entrance and exit of the parking lot may be generated based on the probe information collected from each vehicle instead of being stored in the map information in advance. ..

On the other hand, the user information DB 14 is a storage means for cumulatively storing probe statistical information generated by analyzing the parking lot behavior history information stored in the parking lot behavior history DB 13. In particular, in the present embodiment, by analyzing the parking lot behavior history information, the degree of weakness of use for the type of parking lot of the user who rides in each vehicle that is the transmission source of the probe information is detected, and the detected parking lot of the user. Information on the degree of weakness in use for each type (hereinafter referred to as user information) is generated as probe statistical information. The "degree of weakness of user's use" also corresponds to the ease of parking when the user parks in the parking lot (the degree of difficulty of use by the user's subjectivity). That is, a parking lot of a type that the user is not good at is a parking lot that is easy for the user to park, and a parking lot of a type that the user is not good at is a parking lot that is difficult for the user to park. The details of the method of detecting the degree of weakness of use for the type of parking lot of the user will be described later.

FIG. 5 is a diagram showing an example of user information stored in the user information DB 14. As shown in FIG. 5, the user information includes information that specifies the date and time when the parking lot behavior history information is analyzed (statistics) and information that specifies the degree of weakness of the user who gets on each vehicle for the type of parking lot. include. Here, in the present embodiment, it is particularly difficult to use the parking lot (hereinafter referred to as a ticket-issuing parking lot) in which a ticket-issuing machine or a payment machine is installed to be used while the user is in the vehicle at the entrance or exit. Specify the degree. In addition, it is specified in three stages of "high (very weak)", "medium (slightly weak)", and "low (not weak)" in descending order of weakness. For example, in the example shown in FIG. 5, the user of the vehicle with ID "A" is not good at the ticket-issuing parking lot, and the user of the vehicle with ID "B" is not very good at the ticket-issuing parking lot. It shows that the users of the vehicle are not good at ticket-issuing parking lots.

On the other hand, the parking lot type DB 15 is a storage means for cumulatively storing probe statistical information generated by analyzing the parking lot behavior history information stored in the parking lot behavior history DB 13. In particular, in the present embodiment, by analyzing the parking lot behavior history information, information on the type of each parking lot used by each vehicle that is the source of the probe information (hereinafter referred to as parking lot type information) is generated as probe statistical information. do. Here, in the present embodiment, the type of parking lot is classified according to the installation status of the ticket issuing machine or the checkout machine used by the user while the user is in the vehicle at the entrance or exit, and more specifically. "Ticket-issuing parking lot that is a parking lot where a ticket-issuing machine or checkout machine is installed that the user uses while the user is in the vehicle at the entrance or exit" or "The user is in the vehicle at the entrance and exit" It is divided into two types: parking lots that are not equipped with ticket-issuing machines or checkout machines (hereinafter referred to as non-ticket-issuing parking lots).

FIG. 6 is a diagram showing an example of parking lot type information stored in the parking lot type DB 15. As shown in FIG. 6, the parking lot type information includes information for specifying the date and time when statistics were performed and information for specifying the parking lot type for each parking lot nationwide. As described above, the types of parking lots are basically classified into two types, "ticket-issuing type parking lots" and "non-ticket-issuing type parking lots", but they may be classified in more detail. However, parking lots for which the type of parking lot cannot be determined due to lack of data are also included.

Then, the server device 3 can grasp the type of each parking lot nationwide by the parking lot type information stored in the parking lot type DB 15. As a result, for example, when the server device 3 searches for a parking lot based on a request from a user, it is possible to provide information in consideration of the type of parking lot. For example, it is possible to preferentially provide a non-ticketing type parking lot as a search result to a user who is not good at using the ticketing type parking lot.

On the other hand, the server-side map DB 16 is a storage means for storing server-side map information, which is the latest version of map information registered based on external input data and input operations. Here, the server-side map information is composed of various information necessary for route search, route guidance, and map display, including the road network. For example, network data including nodes and links indicating a road network, link data related to roads (links), node data related to node points, intersection data related to each intersection, point data related to points such as facilities, and map display for displaying a map. It consists of data, search data for searching a route, search data for searching a point, and the like. In addition, as point data, especially for parking lots, information for specifying the positions of entrances and exits of parking lots is also included.

Further, the center communication device 17 is a communication device for communicating with an external traffic information center such as a vehicle 4 or a VICS (registered trademark: Vehicle Information and Communication System) center via a communication network 6. In the present embodiment, probe information and information on parking lot search results are transmitted to and received from each vehicle 4 via the center communication device 17.

Next, a schematic configuration of the navigation device 5 mounted on the vehicle 4 will be described with reference to FIG. 7. FIG. 7 is a block diagram showing the navigation device 5 according to the present embodiment.

As shown in FIG. 7, the navigation device 5 according to the present embodiment includes a current position detection unit 31 that detects the current position of the vehicle on which the navigation device 5 is mounted, a data recording unit 32 in which various data are recorded, and a data recording unit 32. A navigation ECU 33 that performs various arithmetic processes based on the input information, an operation unit 34 that accepts operations from the user, a liquid crystal display 35 that displays a map around the vehicle, traffic information, etc. to the user, and a route. It has a speaker 36 that outputs voice guidance regarding guidance, a DVD drive 37 that reads a DVD as a storage medium, and a communication module 38 that communicates between an information center such as a probe center 2 and a VICS center. Further, the navigation device 5 is also connected to various sensors and cameras mounted on the vehicle 4 via an in-vehicle network such as CAN. The sensors and cameras mounted on the vehicle 4 include a vehicle speed sensor 39, a shift lever sensor 40, a door open / close sensor 41, and a window open / close sensor 42.

Hereinafter, each component of the navigation device 5 will be described in order.
The current position detection unit 31 includes a GPS 43, a yaw rate sensor 44, and the like, and can detect the current position, direction, and the like of the vehicle. Further, by acquiring the detection results of the vehicle speed sensor 39 and various sensors installed in other vehicles, it is possible to detect the current position, orientation, etc. of the current vehicle with higher accuracy.

Further, the data recording unit 32 reads a hard disk (not shown) as an external storage device and a recording medium, a map information DB 45, a travel history DB 46, a predetermined program, etc. recorded on the hard disk, and stores predetermined data on the hard disk. It is equipped with a recording head (not shown) that is a driver for writing. The data recording unit 32 may be configured by a flash memory, a memory card, an optical disk such as a CD or a DVD, instead of the hard disk. Further, the map information DB 45 and the travel history DB 46 may be stored in an external server and acquired by the navigation device 5 by communication.

Here, the map information DB 45 is, for example, link data related to a road (link), node data related to a node point, search data used for processing related to route search or change, facility data related to a facility, and a map for displaying a map. It is a storage means in which display data, intersection data for each intersection, search data for searching a point, and the like are stored.

Further, the travel history DB 46 is a storage means for accumulating and storing the travel information (vehicle behavior) of the vehicle 4. In this embodiment, as the travel information stored in the travel history DB 46, the detection results of various sensors such as the vehicle speed sensor 39, the shift lever sensor 40, the door open / close sensor 41, the window open / close sensor 42, GPS43, and the yaw rate sensor 44 are particularly used. include. The travel information stored in the travel history DB 46 is transmitted to the server device 3 as probe information at any time.

On the other hand, the navigation ECU (electronic control unit) 33 is an electronic control unit that controls the entire navigation device 5, a CPU 51 as a calculation device and a control device, and a working memory for the CPU 51 to perform various calculation processes. The RAM 52 that stores the route data when the route is searched, the control program, and the ROM 53 and ROM 53 that record the information provision processing program (see FIG. 14) described later are read. It is provided with an internal storage device such as a flash memory 54 for storing the program. The navigation ECU 33 has various means as a processing algorithm. For example, the parking lot information providing means searches for a parking lot corresponding to a predetermined search condition and provides the user with information on the searched parking lot.

The operation unit 34 is operated when inputting a departure point as a travel start point and a destination as a travel end point, and is composed of a plurality of operation switches (not shown) such as various keys and buttons. Then, the navigation ECU 33 controls to execute the corresponding various operations based on the switch signal output by pressing each switch or the like. The operation unit 34 can also be configured by a touch panel provided on the front surface of the liquid crystal display 35. It can also be configured by a microphone and a voice recognition device.

In addition, the liquid crystal display 35 has a map image including roads, traffic information, operation guidance, operation menus, key guidance, guidance information along the guidance route (scheduled travel route), news, weather forecast, time, mail, and television. Programs etc. are displayed. Further, in the present embodiment, particularly when the user searches for a facility such as a parking lot, the search result of the facility delivered from the server device 3 is also displayed. A HUD or HMD may be used instead of the liquid crystal display 35.

Further, the speaker 36 outputs voice guidance for guiding the travel along the guidance route (scheduled travel route) and traffic information guidance based on the instruction from the navigation ECU 33.

Further, the DVD drive 37 is a drive capable of reading data recorded on a recording medium such as a DVD or a CD. Then, based on the read data, music or video is played back, the map information DB 45 is updated, and the like. A card slot for reading / writing a memory card may be provided instead of the DVD drive 37.

Further, the communication module 38 is a communication device for receiving traffic information or the like transmitted from a traffic information center, for example, a VICS center or another external center, and corresponds to, for example, a mobile phone or a DCM. It also includes a vehicle-to-vehicle communication device that communicates between vehicles and a road-to-vehicle communication device that communicates with a roadside unit. It is also used to send and receive probe information and distribution information to and from the server device 3.

Further, the vehicle speed sensor 39 is a sensor for detecting the moving distance and the vehicle speed of the vehicle, generates a pulse according to the rotation of the drive wheel of the vehicle, and outputs the pulse signal to the navigation ECU 33. Then, the navigation ECU 33 calculates the vehicle speed and the moving distance of the vehicle by counting the generated pulses.

Further, the shift lever sensor 40 is built in the shift lever (not shown), and the shift positions are "P (parking)", "N (neutral)", "R (reverse)", "D (drive)", and so on. It is possible to detect which position is "2 (second)" or "L (low)".

Further, the door open / close sensor 41 is arranged for each door provided in the vehicle, for example, and is a sensor for detecting whether each door is in an open state or a closed state. In particular, in the present embodiment, a plurality of door opening / closing sensors 41 provided in the vehicle and the types of doors (driver's seat, passenger seat, rear seat left, rear seat right) for detecting opening / closing by the sensors are linked in advance and opened. Alternatively, it is possible to detect the type of closed door. Furthermore, the opening / closing angle can also be detected.

Further, the window open / close sensor 42 is arranged for each window provided in the vehicle, for example, and is a sensor for detecting whether each window is in an open state or a closed state. In particular, in the present embodiment, a plurality of window opening / closing sensors 42 provided in the vehicle and the types of windows (driver's seat, passenger seat, rear seat left, rear seat right) for detecting opening / closing by the sensors are linked in advance and opened. Alternatively, it is possible to detect the type of closed window.

Subsequently, a user information detection processing program executed by the server device 3 included in the parking lot usage information detection system 1 having the above configuration will be described with reference to FIG. FIG. 8 is a flowchart of the user information detection processing program according to the present embodiment. Here, the user information detection processing program is executed after a predetermined time (for example, 24 hours) has elapsed from the time when the program was executed last time, and is used for the type of parking lot of the user based on the probe information transmitted from each vehicle 4. It is a program that detects the degree of weakness of. The programs shown in the flowcharts of FIGS. 8 to 11 below are stored in the RAM 22, ROM 23, and the like included in the server device 3, and are executed by the CPU 21.

The processing of the following steps (hereinafter abbreviated as S) 1 and subsequent steps is executed in a loop for each vehicle that is the source of probe information nationwide, and is repeated until the processing for all vehicles is completed.

First, in S1, the CPU 21 extracts the probe information of the vehicle to be processed from the probe information (FIG. 3) currently stored in the probe information DB 12 (in the probe information DB 12 from the time when the previous program is executed). Only the stored probe information may be targeted). As shown in FIG. 3, the probe information includes (a) the date and time, (b) the area code of the area where the vehicle 4 travels at that date and time, (c) the link where the vehicle 4 travels, and (d) the traveling direction of the vehicle 4. (Forward or reverse direction), (e) Distance traveled from the link start point (end point), (f) Vehicle speed, (g) Vehicle 4 shift position, (h) Vehicle 4 door open / closed state, ( i) The open / closed state of the window of the vehicle 4 is included. Probe information is periodically collected from each vehicle 4 traveling nationwide. For example, in the example shown in FIG. 3, probe information is repeatedly collected from the vehicle at intervals of 200 msec. However, it is not always necessary to collect probe information at intervals of 200 msec. For example, the probe information to be transmitted in the navigation device 5 may be stored in the flash memory 54 or the like, and the probe information within a predetermined period may be collectively transmitted to the server device 3.

Next, in S2, the CPU 21 further extracts the probe information of the vehicle located near the entrance and exit of the parking lot from the probe information extracted in S1. The map information contained in the server device 3 stores information for specifying the positions of the entrance and exit of the parking lot in advance, and is parked by using the vehicle position information and the map information included in the probe information. It is possible to extract probe information of vehicles located near the entrance and exit of the parking lot. Further, the information for specifying the position of the parking lot and the positions of the entrance and exit of the parking lot may be generated based on the probe information collected from each vehicle instead of being stored in the map information in advance. ..

Subsequently, in S3, the CPU 21 generates parking lot behavior history information indicating the behavior of the vehicle in the vicinity of the entrance and exit of the parking lot, based on the probe information extracted in S2. As shown in FIG. 4, the parking lot behavior history information shows the behavior of the vehicle near the entrance and exit of the parking lot, the date and time when the vehicle entered or exited the parking lot, and the parking lot where the vehicle entered or exited. The identification ID of the parking lot, whether the vehicle is stopped, the stop time if the vehicle is stopped, whether the shift position is displaced to R, the distance retracted if the shift position is displaced to R, and the distance of the vehicle door. It includes the presence / absence of opening / closing, the type of door opened / closed when opened / closed, the opening time, the opening angle, and the presence / absence of opening / closing of the vehicle window and the type of the opened window when opened / closed.

After that, in S4, the CPU 21 determines whether or not the vehicle to be processed is a left-hand drive vehicle. Information for identifying whether the vehicle is a right-hand drive vehicle or a left-hand drive vehicle is transmitted to the server device 3 together with probe information.

Then, when it is determined that the vehicle to be processed is a left-hand drive vehicle (S4: YES), the process proceeds to S5. On the other hand, when it is determined that the vehicle to be processed is a right-hand drive vehicle (S4: NO), the process proceeds to S6.

In S5, the CPU 21 sets the door opening / closing time and the stop time to be excluded from the elements to be determined for the user's weakness degree in the weakness degree detection process (S6) described later. Details will be described later.

Next, in S6, the CPU 21 executes the weakness detection process (FIGS. 9 to 11) described later based on the parking lot behavior history information generated in S3. Here, the weakness detection process is a process of detecting the "weakness of use for the type of parking lot" of the user who gets on the vehicle to be processed. In particular, in the present embodiment, the degree of weakness in use for "a ticket-issuing parking lot in which a ticket-issuing machine or a payment machine is installed, which is used by the user while the user is in the vehicle at the entrance or exit" is specified.

After that, in S7, the CPU 21 associates the user information that specifies the "difficulty of using the parking lot type" of the user who gets on the vehicle to be processed detected in S6 with the vehicle ID (or user ID). Is stored in the user information DB 14.

Then, by executing the processes of S1 to S7 for all the vehicles that are the transmission sources of the probe information nationwide, the user information DB 14 is provided with "use for the type of parking lot" for each user as shown in FIG. User information that specifies "the degree of weakness" will be stored.

Next, the sub-processing of the weakness detection process executed in S6 will be described with reference to FIGS. 9 to 11. 9 to 11 are flowcharts of the sub-processing program of the weakness detection process. Here, as the sub-processing of the weakness degree detection processing, the first weakness degree detection processing sub-processing program shown in FIG. 9, the second weakness degree detection processing sub-processing program shown in FIG. 10, and the second Any program of the sub-processing program of the weakness detection processing of 3 may be executed. Further, it may be possible to execute a plurality of programs and detect the "degree of weakness of use for the type of parking lot" of the user who gets on the vehicle to be processed in an integrated manner.

First, a sub-processing program for the first weakness detection process shown in FIG. 9 will be described.
In S11, the CPU 21 enters or exits the parking lot (regardless of which parking lot, the same applies to the following steps) for the vehicle to be processed based on the parking lot behavior history information generated in S3. The frequency of opening and closing the door is calculated in. Specifically, the ratio of the number of times the door is opened and closed to the number of times the vehicle stops at the entrance or exit of the parking lot is calculated. The door is basically the door of the driver's seat, but doors other than the driver's seat may also be included in the target. Here, when the vehicle stops at the entrance or exit of the parking lot, as shown in FIG. 12, the ticket issuing machine 63 or the checkout machine used by the user in the vehicle at the entrance 61 or the exit 62. It shows the situation of using the parking lot where 64 is installed. Therefore, in S11, when entering or exiting the parking lot where the ticket issuing machine 63 or the checkout machine 64 is installed as shown in FIG. 12, the frequency (ratio) of the user opening the door from the stopped vehicle and getting off is determined. Shows. Here, it is considered that the reason why the user gets off the vehicle at the entrance 61 or the exit 62 is that the vehicle could not sufficiently approach the ticket issuing machine 63 or the checkout machine 64.

Next, in S12, the CPU 21 calculates the frequency with which the vehicle to be processed shifts the shift position to "R" at the entrance or exit of the parking lot based on the parking lot behavior history information generated in S3. .. Specifically, the ratio of the number of times the shift position is displaced to "R" is calculated with respect to the number of times the vehicle has stopped at the entrance or exit of the parking lot. Here, when the vehicle stops at the entrance or exit of the parking lot, as shown in FIG. 12, the ticket issuing machine 63 or the checkout machine used by the user in the vehicle at the entrance 61 or the exit 62. It shows the situation of using the parking lot where 64 is installed. Therefore, in S12, the frequency (ratio) at which the user retracts the once stopped vehicle when entering or leaving the parking lot where the ticket issuing machine 63 or the checkout machine 64 is installed as shown in FIG. 12 is shown. There is. Here, it is considered that the reason why the user retracts the vehicle at the entrance 61 or the exit 62 is that the vehicle could not be correctly stopped at a position where the user can operate the ticket issuing machine 63 or the checkout machine 64 from the window.

Further, in S13, the CPU 21 calculates the frequency with which the vehicle to be processed exceeds the threshold value at the entrance or exit of the parking lot based on the parking lot behavior history information generated in S3. .. Specifically, the ratio of the number of times the vehicle has stopped at the entrance or exit of the parking lot to the number of times the vehicle has stopped at or above the threshold value is calculated. The threshold value can be set as appropriate, but is set to, for example, 10 seconds. Here, when the vehicle stops at the entrance or exit of the parking lot, as shown in FIG. 12, the ticket issuing machine 63 or the checkout machine used by the user in the vehicle at the entrance 61 or the exit 62. It shows the situation of using the parking lot where 64 is installed. Therefore, in S13, the frequency (ratio) of the user stopping the vehicle for a long time when entering or leaving the parking lot where the ticket issuing machine 63 or the checkout machine 64 is installed as shown in FIG. 12 is shown. .. Here, as a factor for the user to stop the vehicle at the entrance 61 and the exit 62 for a long time, the user can stop the vehicle so that the ticket issuing machine 63 and the checkout machine 64 are located near the window of the driver's seat of the vehicle. It is possible that it was not.

In S11 to S13, the ratio of the number of times the vehicle is opened and closed to the number of times the vehicle is stopped at the entrance or exit of the parking lot, the ratio of the number of times the shift position is displaced to "R", and the stop time are equal to or greater than the threshold value. The ratio of the number of times the vehicle has become is calculated, but the ratio of the number of times the vehicle opens and closes the door to the number of times the vehicle opens the window at the entrance or exit of the parking lot, and the shift position is displaced to "R". The ratio of the number of times and the ratio of the number of times the stop time exceeds the threshold value may be calculated respectively. Even when the vehicle opens the window at the entrance or exit of the parking lot, as shown in FIG. 12, the ticket issuing machine 63 or the checkout machine 64 used by the user in the vehicle at the entrance 61 or the exit 62. Will indicate the situation of using the parking lot where is installed.

After that, in S14, the CPU 21 determines whether or not the total of the frequencies (ratio) calculated in S11 to S13 is equal to or higher than the first threshold value. The first threshold value can be set as appropriate, but is set to, for example, 20%. The value to be determined in S14 is not the total of the frequencies (ratio) calculated in S11 to S13, but may be the average value of each frequency (ratio), or may be the minimum value or the maximum value.

Then, when it is determined that the total of each frequency (ratio) calculated in S11 to S13 is equal to or higher than the first threshold value (S14: YES), the process proceeds to S15. On the other hand, when it is determined that the total of each frequency (ratio) calculated in S11 to S13 is less than the first threshold value (S14: NO), the process proceeds to S16.

In S15, the CPU 21 very much provides a "ticket-issuing parking lot in which a ticket-issuing machine or a payment machine is installed, which is used by the user who is a occupant of the vehicle to be processed while the user is in the vehicle at the entrance or exit." It is determined that the vehicle is not good at it, and "high (very weak)" is detected as the degree of weakness for the ticket-issuing parking lot. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

On the other hand, in S16, the CPU 21 determines whether or not the total of the frequencies (ratio) calculated in S11 to S13 is equal to or higher than the second threshold value lower than the first threshold value. The second threshold value can be set as appropriate, but is set to, for example, 10%. The value to be determined in S16 is not the total of the frequencies (ratio) calculated in S11 to S13, but may be the average value of each frequency (ratio), or may be the minimum value or the maximum value.

Then, when it is determined that the total of each frequency (ratio) calculated in S11 to S13 is equal to or higher than the second threshold value (S16: YES), the process proceeds to S17. On the other hand, when it is determined that the total of each frequency (ratio) calculated in S11 to S13 is less than the second threshold value (S16: NO), the process proceeds to S18.

In S17, the CPU 21 is a little weak at "a ticket-issuing parking lot in which a ticket-issuing machine or a payment machine is installed, which is used by the user while the user is in the vehicle at the entrance or exit" by the user who is the occupant of the vehicle to be processed. It is determined that the parking lot is not good at issuing tickets, and "medium (slightly weak)" is detected. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

In S18, the CPU 21 is not good at "a ticket-issuing parking lot where a ticket-issuing machine or a payment machine is installed, which is used by the user while the user is in the vehicle at the entrance or exit" by the user who is the occupant of the vehicle to be processed. It is determined that there is no parking lot, and "low (not weak)" is detected as the degree of weakness for the ticket-issuing parking lot. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

Further, when the vehicle to be processed is a left-hand drive vehicle, the setting is made to exclude the opening / closing and the stop time of the door from the element to be determined the degree of weakness of the user (S5). , It is determined whether or not the frequency (ratio) calculated in S12 is equal to or higher than the first threshold value or the second threshold value. At that time, it is desirable to change the threshold value as appropriate for the case of a right-hand drive vehicle.

Next, a sub-processing program for the second weakness detection process shown in FIG. 10 will be described.
In S21, the CPU 21 identifies the behavior of the vehicle to be processed opening and closing the door at the entrance or exit of the parking lot based on the parking lot behavior history information generated in S3. Specifically, the timing (time) of opening and closing the door at the entrance or exit of the parking lot is specified. The door is basically the door of the driver's seat, but doors other than the driver's seat may also be included in the target. The timing specified in S21 is the timing when the user opens the door from the stopped vehicle and gets off when entering or exiting the parking lot where the ticket issuing machine 63 or the checkout machine 64 is installed as shown in FIG. Is shown. Here, it is considered that the reason why the user gets off the vehicle at the entrance 61 or the exit 62 is that the vehicle could not sufficiently approach the ticket issuing machine 63 or the checkout machine 64.

Next, in S22, the CPU 21 specifies an action in which the vehicle to be processed shifts the shift position to "R" at the entrance or exit of the parking lot based on the parking lot behavior history information generated in S3. .. Specifically, the timing (time) at which the shift position is displaced to "R" at the entrance or exit of the parking lot is specified. The timing specified in S22 indicates the timing at which the user retracts the once stopped vehicle when entering or exiting the parking lot where the ticket issuing machine 63 or the checkout machine 64 is installed as shown in FIG. ing. Here, it is considered that the reason why the user retracts the vehicle at the entrance 61 or the exit 62 is that the vehicle could not be correctly stopped at a position where the user can operate the ticket issuing machine 63 or the checkout machine 64 from the window.

Further, in S23, the CPU 21 specifies an action in which the vehicle to be processed has a stop time of the vehicle equal to or longer than the threshold value at the entrance or exit of the parking lot based on the parking lot behavior history information generated in S3. .. Specifically, the timing (time) at which the vehicle is stopped at the entrance or exit of the parking lot by a threshold value or more is specified. The threshold value can be set as appropriate, but is set to, for example, 10 seconds. The timing specified in S23 indicates the timing at which the user stops the vehicle for a long time when entering or exiting the parking lot where the ticket issuing machine 63 or the checkout machine 64 is installed as shown in FIG. There is. Here, as a factor for the user to stop the vehicle at the entrance 61 and the exit 62 for a long time, the user can stop the vehicle so that the ticket issuing machine 63 and the checkout machine 64 are located near the window of the driver's seat of the vehicle. It is possible that it was not.

After that, in S24, the CPU 21 determines whether or not each of the actions specified in S21 to S23 has occurred in duplicate. It should be noted that the overlapping occurrences do not have to occur at the timing when the actions completely match, and it is sufficient that at least a part of the overlapping timings occur. Further, if the actions occur while the same vehicle is stopped, it is desirable to consider that the actions occur in duplicate even if the timings of the actions are different.

Then, when it is determined that two or more of the actions specified in S21 to S23 have occurred in duplicate (S24: YES), the process proceeds to S25. On the other hand, when it is determined that two or more of the actions specified in S21 to S23 do not occur in duplicate (S24: NO), the process proceeds to S26.

In S25, the CPU 21 very much provides a "ticket-issuing parking lot in which a ticket-issuing machine or a payment machine is installed, which is used by the user who is a occupant of the vehicle to be processed while the user is in the vehicle at the entrance or exit." It is determined that the vehicle is not good at it, and "high (very weak)" is detected as the degree of weakness for the ticket-issuing parking lot. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

On the other hand, in S26, the CPU 21 determines whether or not it can be specified that any of the actions has occurred in S21 to S23.

Then, when it is determined that any of the actions has occurred in S21 to S23 (S26: YES), the process proceeds to S27. On the other hand, when it is determined in S21 to S23 that the occurrence of any of the actions could not be identified (S26: NO), the process proceeds to S28.

In S27, the CPU 21 is a little weak at "a ticket-issuing parking lot where a ticket-issuing machine or a payment machine is installed, which is used by the user while the user is in the vehicle at the entrance or exit" by the user who is the occupant of the vehicle to be processed. It is determined that the parking lot is not good at issuing tickets, and "medium (slightly weak)" is detected. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

In S28, the CPU 21 is not good at "a ticket-issuing parking lot where a ticket-issuing machine or a payment machine is installed, which is used by the user while the user is in the vehicle at the entrance or exit" by the user who is the occupant of the vehicle to be processed. It is determined that there is no parking lot, and "low (not weak)" is detected as the degree of weakness for the ticket-issuing parking lot. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

Further, when the vehicle to be processed is a left-hand drive vehicle, the setting is made to exclude the opening / closing and the stop time of the door from the element to be determined the degree of weakness of the user (S5), so that the determination in S24 is made. Instead of doing so, it is determined whether or not it was possible to identify that the action of S22 has occurred in S26.

Next, a sub-processing program for the third weakness detection process shown in FIG. 11 will be described.
In S31, the CPU 21 targets the behavior of the vehicle to be processed opening and closing the door at the entrance or exit of the parking lot based on the parking lot behavior history information generated in S3, and the average time of the door opening time. (Average opening time) and the average angle of opening angle (average opening angle) are calculated respectively. The door is basically the door of the driver's seat, but doors other than the driver's seat may also be included in the target. Here, the reason why the user opens the door at the entrance or exit is that the vehicle cannot sufficiently approach the ticket issuing machine or the checkout machine and the user opens the door from the stopped vehicle and gets off. Can be estimated. It can be estimated that the longer the door opening time, the longer the distance from the vehicle to the ticket issuing machine or the checkout machine. Similarly, it can be estimated that the larger the door opening angle, the longer the distance from the vehicle to the ticket issuing machine or checkout machine.

Next, in S32, the CPU 21 targets the behavior in which the vehicle to be processed shifts the shift position to "R" at the entrance or exit of the parking lot based on the parking lot behavior history information generated in S3. , The average distance of the vehicle's retreat distance after that (average retreat distance) is calculated. Here, the reason why the user shifts the shift position to "R" at the entrance or exit is that the vehicle could not be stopped correctly at a position where the user can operate the ticket issuing machine or the checkout machine from the window. Can be estimated. Then, it can be estimated that the longer the retreat distance of the vehicle after that, the larger the deviation of the stop position.

Subsequently, in S33, the CPU 21 targets the behavior in which the vehicle to be processed stops the vehicle at the entrance or exit of the parking lot based on the parking lot behavior history information generated in S3, and determines the stop time of the vehicle. Calculate the average time (average stop time). Here, the reason why the user stops the vehicle for a long time at the entrance or exit is that the user could not stop the vehicle so that the ticket issuing machine or the checkout machine is located near the window of the driver's seat of the vehicle. It can be presumed to be a factor. Then, it can be estimated that the longer the stop time is, the larger the deviation of the stop position is.

In S31 to S33, the average value of the door opening time, opening angle, retreat distance, and stopping time is calculated, but the median value or the mode value may be used. Further, the maximum value may be calculated.

After that, in S34, the CPU 21 determines whether or not any of the values calculated in S31 to S33 is equal to or higher than the first threshold value. The first threshold can be set as appropriate, but for example, the average opening time of the door is 10 seconds, the average opening angle of the door is 60 degrees, the average retreat distance is 1 m, and the average stop time is 30 seconds. do.

Then, when it is determined that any of the values calculated in S31 to S33 is equal to or higher than the first threshold value (S34: YES), the process proceeds to S35. On the other hand, when it is determined that all of the values calculated in S31 to S33 are less than the first threshold value (S34: NO), the process proceeds to S36.

In S35, the CPU 21 very much provides a "ticket-issuing parking lot in which a ticket-issuing machine or a payment machine is installed, which is used by the user who is a occupant of the vehicle to be processed while the user is in the vehicle at the entrance or exit." It is determined that the vehicle is not good at it, and "high (very weak)" is detected as the degree of weakness for the ticket-issuing parking lot. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

On the other hand, in S36, the CPU 21 determines whether or not any of the values calculated in S31 to S33 is equal to or higher than the second threshold value lower than the first threshold value. The second threshold can be set as appropriate, but for example, the average opening time of the door is 5 seconds, the average opening angle of the door is 30 degrees, the average retreat distance is 0.5 m, and the average stop time is 20. Let it be seconds.

Then, when it is determined that any of the values calculated in S31 to S33 is equal to or higher than the second threshold value (S36: YES), the process proceeds to S37. On the other hand, when it is determined that all of the values calculated in S31 to S33 are less than the second threshold value (S36: NO), the process proceeds to S38.

In S37, the CPU 21 is a little weak at "a ticket-issuing parking lot where a ticket-issuing machine or a payment machine is installed, which is used by the user while the user is in the vehicle at the entrance or exit" by the user who is the occupant of the vehicle to be processed. It is determined that the parking lot is not good at issuing tickets, and "medium (slightly weak)" is detected. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

In S38, the CPU 21 is not good at "a ticket-issuing parking lot where a ticket-issuing machine or a payment machine is installed, which is used by the user while the user is in the vehicle at the entrance or exit" by the user who is the occupant of the vehicle to be processed. It is determined that there is no parking lot, and "low (not weak)" is detected as the degree of weakness for the ticket-issuing parking lot. After that, the process proceeds to S7, and the user information that specifies the degree of weakness for the detected ticket-issuing parking lot is linked to the vehicle ID (or user ID) and stored in the user information DB 14.

Further, when the vehicle to be processed is a left-hand drive vehicle, the setting is made to exclude the opening / closing and the stop time of the door from the element to be determined the degree of weakness of the user (S5). , It is determined whether or not the first threshold value or the second threshold value or more is targeted only for the average retreat distance calculated in S32.

Subsequently, a parking lot type detection processing program executed by the server device 3 included in the parking lot usage information detection system 1 having the above configuration will be described with reference to FIG. FIG. 13 is a flowchart of the parking lot type detection processing program according to the present embodiment. Here, the parking lot type detection processing program is executed after a predetermined time (for example, 24 hours) has elapsed from the time when the program was executed last time, and based on the probe information transmitted from each vehicle 4, the parking lot type in the whole country. Is a program to detect. The program shown in the flowchart in FIG. 13 below is stored in the RAM 22, ROM 23, or the like included in the server device 3, and is executed by the CPU 21.

The following processing after S41 is executed in a loop for each parking lot in the whole country, and is repeated until the processing for all parking lots is completed.

First, in S41, the CPU 21 uses the behavior of each vehicle in the parking lot to be processed in the latest parking lot behavior history information (FIG. 4) generated by the user information detection processing program (FIGS. 8 to 11) described above. The parking lot behavior history information indicating is extracted. As shown in FIG. 4, the parking lot behavior history information shows the behavior of the vehicle near the entrance and exit of the parking lot, the date and time when the vehicle entered or exited the parking lot, and the parking lot where the vehicle entered or exited. The identification ID of the parking lot, whether the vehicle is stopped, the stop time if the vehicle is stopped, whether the shift position is displaced to R, the distance retracted if the shift position is displaced to R, and the distance of the vehicle door. It includes the presence / absence of opening / closing, the type of door opened / closed when it was opened / closed, the opening time, the opening angle, and the presence / absence of opening / closing of the vehicle window and the type of the opened window when it was opened / closed.

After that, in S42, whether or not the CPU 21 exhibits the behavior of opening the window at at least one of the entrance and exit of the parking lot to be processed, based on the parking lot behavior history information extracted in S41. To judge. When the history of the behavior of a plurality of vehicles is stored in the parking lot to be processed, the behavior of vehicles having a predetermined ratio or more (for example, 90% or more) opening the window at at least one of the entrance and exit. It is desirable to determine whether or not it indicates.

Then, when it is determined that the vehicle exhibits the behavior of opening the window at at least one of the entrance and exit of the parking lot to be processed (S42: YES), the process proceeds to S43. On the other hand, when it is determined that the vehicle does not show the behavior of opening the window at the entrance and exit of the parking lot to be processed (S42: NO), the process proceeds to S44.

In S43, as shown in FIG. 12, the CPU 21 describes the parking lot to be processed as "a ticket-issuing parking lot in which a ticket-issuing machine or a checkout machine to be used while the user is in the vehicle at the entrance or exit" is installed. Detects that it is a parking lot. As a ticket-issuing parking lot, as shown in FIG. 12, there are parking lots with a ticketing machine 63 at the entrance 61 and a checkout machine 64 at the exit 62, and there are parking lots with only a checkout machine at the entrance. If there is, there is a parking lot where only the checkout machine exists at the exit. It is possible to classify these types according to the position where the window is opened, but in this embodiment, the parking lot is collectively a ticket-issuing type parking lot.

On the other hand, in S44, the CPU 21 uses the parking lot to be processed as "a non-ticketing type parking lot that is a parking lot in which a ticketing machine or a payment machine is not installed, which is used while the user is in the vehicle at the entrance and exit". Is detected. The non-ticketing type parking lot is basically a parking lot other than the ticketing type parking lot. After that, it shifts to S45.

In S45, the CPU 21 stores the parking lot type information that specifies the type of the parking lot to be processed detected in S43 in the parking lot type DB 15 in association with the parking lot ID. If the parking lot type information already associated with the parking lot to be processed exists in the parking lot type DB 15, the content of the parking lot type information may be changed to a new content based on the detection result this time. And update.

Then, by executing the processes of S41 to S47 for parking lots nationwide, the parking lot type DB 15 has parking lot type information that specifies the parking lot type for each parking lot nationwide as shown in FIG. Will be stored.

Subsequently, the information provision processing program executed by the server device 3 and the navigation device 5 of the parking lot usage information detection system 1 having the above configuration will be described with reference to FIG. FIG. 14 is a flowchart of the information provision processing program according to the present embodiment. Here, the information provision processing program is executed when a predetermined operation for searching a parking lot is received in the navigation device 5, and the user information detection processing program (FIG. 8) and the parking lot type detection processing program (FIG. 8) described above are executed. This is a program that searches for parking lots that meet the conditions using the detection results shown in FIG. 13) and provides the search results. The program shown in the flowchart in FIG. 14 below is stored in the RAM 52 or ROM 53 included in the navigation device 5, the RAM 22 or the ROM 23 included in the server device 3, and is executed by the CPU 21 or the CPU 51. Further, the following information provision processing program may be executed by a communication terminal other than the navigation device 5 (for example, a mobile phone, a smartphone, a tablet terminal, a personal computer, etc.) instead of the navigation device 5.

First, the information provision processing program executed by the navigation device 5 will be described.
In S51, the CPU 51 transmits a parking lot search request to the server device 3. The parking lot search request includes a terminal ID that identifies the navigation device 5 that is the source of the parking lot search request, and a parking lot search condition. Here, the parking lot search condition is, for example, the coordinates of the user's current position when searching for a parking lot around the user's current position, and is specified when searching for a parking lot around a specific point such as a destination. Use the coordinates of the point.

Next, in S52, the CPU 51 receives information regarding the parking lot search result searched by the server device 3 in response to the parking lot search request. The parking lot search result includes, for example, a parking lot ID, a name, position coordinates, a usage fee, vacancy information, and the like corresponding to the search conditions. In the search for parking lots by the server device 3, as will be described later, the search is performed preferentially for parking lots other than the types of parking lots that the user is not good at using (S62 to S67). In the present embodiment, the user information detection processing program (FIG. 8) described above specifies the degree of weakness of the user in using the ticket-issuing parking lot. Therefore, for example, for a user who is not good at using the ticket-issuing parking lot. Priority is given to non-ticketing parking lots. Therefore, in S53 described later, parking lots other than the types of parking lots that the user is not good at using are preferentially provided as search results.

After that, in S53, the CPU 51 displays the parking lot search result received in S52 on the liquid crystal display 35. FIG. 15 is a diagram showing an example of a parking lot guidance screen 71 displayed on the liquid crystal display 35.

As shown in FIG. 15, the parking lot guidance screen 71 is composed of two display areas, a left screen 72 for displaying a map around the vehicle and a right screen 73 for displaying guidance information about the parking lot.
The left screen 72 is composed of a map image 74 around the vehicle, a vehicle position mark 75 indicating the current position of the vehicle, and facility marks 76 to 79 indicating the position of the parking lot.
Further, the right screen 73 is provided with information display spaces 81 to 84 for displaying detailed information about the parking lot on which the mark is displayed on the left screen 72. In each of the information display spaces 81 to 84, for example, the name of the parking lot, the position of the parking lot (distance from the current position of the vehicle), the usage fee, the availability, and the type of the parking lot are displayed. Further, in the information display spaces 81 to 84, for example, the parking lots in the vacant state are displayed with priority, and the guidance information is displayed in order from the parking lots having the shortest distance among the parking lots in the vacant state. Further, a process of setting the searched parking lot as the destination of the navigation device 5 may be performed.

Next, the information providing processing program executed in the server device 3 will be described.
First, in S61, the CPU 21 receives the parking lot search request transmitted from the navigation device 5. The parking lot search request includes a terminal ID that identifies the navigation device 5 that is the source of the parking lot search request, and a parking lot search condition.

After that, in S62, the CPU 21 refers to the user information (FIG. 5) stored in the user information DB 14 and acquires the degree of difficulty in using the ticket-issuing parking lot for the user of the navigation device 5 that is the transmission source of the parking lot search request. ..

Next, in S63, the CPU 21 determines whether or not the user of the navigation device 5 that is the transmission source of the parking lot search request is not good at using the ticket-issuing parking lot.

Then, when it is determined that the user of the navigation device 5 that is the source of the parking lot search request is not good at using the ticket-issuing parking lot (S63: YES), it is determined that the user is not good at using the ticket-issuing parking lot. Move to S64. On the other hand, when it is determined that the user of the navigation device 5 that is the source of the parking lot search request is not good at using the ticket-issuing parking lot other than "high (very weak)" (S63: NO). Will move to S65.

In S64, the CPU 21 refers to the parking lot type information (FIG. 6) stored in the parking lot type DB 15, and sets to exclude the ticket-issuing type parking lot from the search target. After that, the CPU 21 searches for a parking lot corresponding to the search condition by using the parking lot search condition and the map information included in the parking lot search request received in S61. For example, when the area around the user's current position is specified as the parking lot search condition, the parking lot within a predetermined distance (for example, within 5 km) from the user's current position is extracted. However, parking lots excluded from the search target will not be extracted even if the search conditions are met. If there are many applicable parking lots, only a predetermined number of parking lots may be extracted in order from the user's current position. After that, it shifts to S68.

On the other hand, in S65, the CPU 21 determines whether or not the user of the navigation device 5 that is the transmission source of the parking lot search request is not good at using the ticket-issuing parking lot.

Then, when it is determined that the user of the navigation device 5 that is the transmission source of the parking lot search request is not good at using the ticket-issuing parking lot (S65: YES), S66 Move to. On the other hand, when it is determined that the user of the navigation device 5 that is the sender of the parking lot search request is not good at using the ticket-issuing parking lot (S65: NO). Will move to S67.

In S66, the CPU 21 refers to the parking lot type information (FIG. 6) stored in the parking lot type DB 15, and sets to exclude the ticket-issuing type parking lot from the search target. After that, the CPU 21 searches for a parking lot corresponding to the search condition by using the parking lot search condition and the map information included in the parking lot search request received in S61. For example, when the area around the user's current position is specified as the parking lot search condition, the parking lot within a predetermined distance (for example, within 5 km) from the user's current position is extracted. However, parking lots excluded from the search target will not be extracted even if the search conditions are met. If there are many applicable parking lots, only a predetermined number of parking lots may be extracted in order from the user's current position.

As a result, if the number of parking lots corresponding to the search conditions is sufficient (for example, if there are three or more parking lots), the search is terminated and the process proceeds to S68. On the other hand, if the number of parking lots that meet the search conditions is not sufficient, the setting for excluding the ticket-issuing parking lot from the search target is canceled, and the parking lot is searched again including the ticket-issuing parking lot. After that, it shifts to S68.

On the other hand, in S67, the CPU 21 uses the parking lot search condition and the map information included in the parking lot search request received in S61 to target all parking lots regardless of the type of parking lot, and uses the search condition as the search condition. Search for the applicable parking lot. For example, when the area around the user's current position is specified as the parking lot search condition, the parking lot within a predetermined distance (for example, within 5 km) from the user's current position is extracted. If there are many applicable parking lots, only a predetermined number of parking lots may be extracted in order from the user's current position. After that, it shifts to S68.

Subsequently, in S68, the CPU 21 distributes the information regarding the parking lot searched in S64, S66, and S67 to the navigation device 5 for which the parking lot search request has been made. For example, the parking lot ID, name, position coordinates, usage fee, vacancy information, etc. are included. Then, in the navigation device 5 to which the information is distributed, the information regarding the parking lot distributed as described above is displayed on the liquid crystal display 35 (S53). If the search is performed in S66 and the searched parking lot includes both a non-ticketing type parking lot and a ticketing type parking lot, the non-ticketing type parking lot should be given priority over the ticketing type parking lot. It is desirable to set the priority information. As a result, it becomes possible to provide the user with information on the parking lot that meets the user's desired conditions, and the ticket-issuing parking lot is excluded from the provision target as much as possible, especially for users who are not good at using the ticket-issuing parking lot. By doing so, it becomes possible to reduce the burden related to the parking of the user.

As described in detail above, in the computer program executed by the parking lot usage information detection system 1, the server device 3, and the server device 3 according to the present embodiment, the behavior of the vehicle in the parking lot is acquired (S1, S2). Based on the acquired information, the degree of weakness of the user who gets on the vehicle for the type related to the entrance or exit of the parking lot is detected (S6), so that it is based on the information on the behavior of the vehicle in the parking lot acquired from the vehicle. Therefore, it is possible to detect the degree of weakness of the user's use for the type related to the entrance or exit of the parking lot. As a result, it becomes possible to provide various kinds of support such as providing information on a parking lot suitable for the user, for example, to a user who moves by car.
In addition, the type of parking lot entrance or exit is classified according to the installation status of the ticketing machine or checkout machine that the user uses while the user is in the vehicle at the entrance or exit. Alternatively, it is possible to detect whether or not the user is not good at a parking lot that requires an operation of moving the vehicle in one direction at the exit.
In addition, since at least one of the opening / closing of the door at the entrance or exit of the parking lot, the displacement of the shift position, and the stop time is acquired as the behavior of the vehicle in the parking lot (S1, S2), it is specific in the parking lot. Based on the behavior of the vehicle, it is possible to accurately detect the degree of weakness of the user's use for the type related to the entrance or exit of the parking lot.
In addition, when searching for a parking lot that meets a predetermined search condition and providing information on the searched parking lot to the user, the parking lot is searched for or information is provided using the degree of weakness of the user's use (S62). ~ S67) Therefore, it is possible to provide the user who moves by vehicle with information on the parking lot suitable for the user.

It should be noted that the present invention is not limited to the above-described embodiment, and it goes without saying that various improvements and modifications can be made without departing from the gist of the present invention.
For example, in the present embodiment, "the degree of weakness of the user for the type of parking lot" based on the information on the stop position and the opening / closing of the door collected from a plurality of vehicles traveling nationwide using the probe car system using the probe information. However, the probe car system is not essential. For example, it is possible for the navigation device 5 to detect the degree of weakness of the user of the own vehicle for the type of parking lot based on the past travel history of the own vehicle.

Further, in the present embodiment, based on the information on the stop position and the opening / closing of the door collected from a plurality of vehicles traveling nationwide using the probe car system using the probe information, "the type of each parking lot in the whole country (ticketing type parking). Whether it is a parking lot or a non-ticketing type parking lot) ”is detected, but the type of parking lot may be obtained by communication from a server that manages the parking lot. Further, the map information may include information on the type of parking lot in advance.

Further, in the present embodiment, the degree of difficulty in using the "ticket-issuing parking lot where the ticket-issuing machine or the payment machine is installed, which is used by the user while the user is in the vehicle at the entrance or the exit" is specified. If it is a type related to the entrance or exit of the parking lot, the degree of weakness in use for other types may be specified. For example, the degree of weakness in using the "parking lot with a gate installed at the entrance or exit" may be specified. In addition, the degree of weakness in using the "parking lot where a ticketing machine or a payment machine is installed, which is used while the user is in the vehicle at the entrance" may be specified. In addition, the degree of weakness in using the "parking lot in which the payment machine used by the user while riding in the vehicle at the exit" may be specified.

Further, in the present embodiment, as the behavior of the vehicle for detecting "the degree of weakness of the user's use for the type of parking lot", the door is opened / closed at the entrance or exit of the parking lot, the shift position is displaced, and the vehicle is stopped. Although the time is given, the behavior of other vehicles may be used. For example, the window opening time may be used.

Further, in the present embodiment, as "the degree of weakness of the user for the type of parking lot", the degree of weakness of the use for the ticket-issuing type parking lot is "high (very weak)", "medium (slightly weak)", and " Although it is specified in three stages of "low (not weak)", other methods may be used to specify the degree of weakness. For example, the degree of weakness may be specified by using a continuous amount (0 to 100).

Further, in the present embodiment, the parking lot is searched as a control (service provision to the user) using the detection result of "the degree of weakness of the user's use for the type of the parking lot", but other controls are used. You may go. For example, when a facility equipped with a parking lot of a type that the user is not good at is set as a destination, another parking lot around the destination may be guided as a candidate for use. In addition, when using a type of parking lot that the user is not good at, it is possible to notify in advance that the parking lot is difficult to use.

Further, in the present embodiment, the execution subject of the user information detection processing program shown in FIG. 8 is the server device 3, but the navigation device 5 may execute the program. In that case, if the "degree of weakness of the user's use for the type of parking lot" is detected by using only the driving history of the own vehicle without using the traveling history of another vehicle, the parking lot usage information detection system 1 can be used. The server device 3 is not an indispensable element, and the parking lot usage information detection system 1 can be configured only by the navigation device 5. Similarly, in the present embodiment, the execution subject of the parking lot type detection processing program shown in FIG. 13 is the server device 3, but the navigation device 5 may execute the program.

Further, as a means for guiding the information provided from the server device 3 in the information providing processing program shown in FIG. 14, another device having a traveling guidance function may be used instead of the navigation device 5. For example, an in-vehicle device other than the navigation device 5, a mobile phone, a smartphone, a tablet terminal, a personal computer, or the like is possible.

1 ... Parking lot usage information detection system, 2 ... Probe center, 3 ... Server device, 4 ... Vehicle, 5 ... Navigation device, 11 ... Server control unit, 12 ... Probe information DB, 13 ... Parking lot behavior history DB, 14 ... Parking lot difficulty DB, 15 ... Parking lot type DB, 21 ... CPU, 33 ... Navigation ECU, 51 ... CPU, 61 ... Entrance, 62 ... Exit, 63 ... Ticketing machine, 64 ... Payment machine

Claims (4)

Information acquisition means to acquire the behavior of the vehicle in the parking lot,
Parking lot usage information having a user information detecting means for detecting the degree of weakness of the user riding in the vehicle for the type related to the entrance or exit of the parking lot based on the information acquired by the information acquisition means. Detection system. The type related to the entrance or exit of the parking lot is described in claim 1, which is a type classified according to the installation status of the ticket issuing machine or the checkout machine used by the user while the user is in the vehicle at the entrance or exit. Parking lot usage information detection system. The information acquisition means according to claim 1 or 2, wherein at least one of the opening / closing of the door at the entrance or exit of the parking lot, the displacement of the shift position, and the stop time is acquired as the behavior of the vehicle in the parking lot. The parking lot usage information detection system described. It has a parking lot information providing means that searches for a parking lot that meets a predetermined search condition and provides the user with information about the searched parking lot.
The station according to any one of claims 1 to 3, wherein the parking lot information providing means searches for a parking lot or provides information by using the degree of weakness of the user detected by the user information detecting means. Parking lot usage information detection system.

Images