JP2020177265A - Distribution system, and distribution program - Google Patents

Abstract

To provide a distribution system and a distribution program capable of properly grasping congestion information on roads around event locations.SOLUTION: A distribution system comprises: event information DB 224 storing event information specifying an event to be held; an acquiring part 231 specifying a vehicle heading to an event specified with the event information and acquiring outward route information specifying an outward route of the specified vehicle; an estimation part 232 estimating congestion information which is congestion information on roads around an event location where the event specified with the event information stored in the event information DB 224 is held, and is information on congestion of vehicles departing from the event location on each of roads based on the outward route information acquired by the acquiring part 231; and a distribution part 233 distributing the congestion information estimated with the estimation part 232.SELECTED DRAWING: Figure 1

Description

The present invention relates to a distribution system and a distribution program.

Conventionally, a technique for estimating a traffic congestion condition on the return route based on data on the traffic volume on the outward route to a resort spot has been known (see, for example, Patent Document 1). In this conventional technique, for example, on a specific road such as an expressway connecting a recreational area and an urban area, an external factor (for example, an event, etc.) determines the mutual relationship between the traffic volume on the outward route and the traffic volume on the return route. ) Is also taken into consideration and generated as statistical data in advance, and when it is requested to provide the congestion status of the return route for the specific road, the information on the outbound route for the specific road and external factors can be used. Based on this, the congestion situation on the return trip was estimated.

Japanese Unexamined Patent Publication No. 2004-348598

By the way, for concerts and other various events, the end time is generally set to some extent, and after the event is over, you will be returning from the event venue almost all at once, and by the vehicle that will be returning. Congestion may be caused, and there was a request to grasp traffic congestion information for each road around the event venue. In particular, when the event venue is located in an urban area, congestion may become noticeable. Therefore, for example, in order to grasp the time to get out of the area around the event venue or to find a way out to avoid congestion, the event venue There was a relatively strong request to grasp traffic congestion information for each road in the vicinity.

However, when the technique of Patent Document 1 is applied, only the congestion situation of the return route for a specific predetermined road is estimated, so that the congestion information for each road around the event venue is appropriately grasped. There was room for improvement as it could not be possible.

The present invention has been made in view of the above, and an object of the present invention is to provide a distribution system and a distribution program capable of appropriately grasping traffic congestion information on each road around an event point.

In order to solve the above-mentioned problems and achieve the object, the distribution system according to the present invention has a storage means for storing event information for specifying an event to be held and the event information stored in the storage means. The acquisition means for identifying the vehicle heading for the event to be specified and acquiring the outbound route information for specifying the outbound route of the specified vehicle, and the storage means storing the outbound route information based on the outbound route information acquired by the acquisition means. An estimation means for estimating the congestion information, which is congestion information on each road around the event point, which is the event holding point specified by the event information, and is information on congestion caused by a vehicle away from the event point on each road. A delivery means for delivering the congestion information estimated by the estimation means is provided.

In addition, the distribution program according to the present invention identifies a vehicle heading for an event specified by the event information stored in a storage means for storing event information that specifies an event to be held, and the specified vehicle. Around the event point where the event information specified by the event information stored in the storage means is held based on the acquisition means for acquiring the outbound route information for specifying the outbound route and the outbound route information acquired by the acquisition means. The estimation means for estimating the congestion information, which is the congestion information on each road of the above, which is the information on the congestion caused by the vehicle away from the event point on each road, and the distribution means for delivering the congestion information estimated by the estimation means. To function as ,.

According to the distribution system and the distribution program according to the present invention, for example, the congestion information on each road around the event point is distributed by estimating the congestion information on each road around the event point based on the outbound route information. Therefore, it is possible to appropriately grasp the traffic congestion information on each road around the event point.

It is a block diagram which illustrates the navigation system which concerns on embodiment of this invention. It is a figure which illustrated the movement route information. It is a figure which illustrated the predicted movement route information. It is a figure which illustrated the event information. It is a figure which illustrated the parking information. It is a figure which exemplifies the predicted traffic jam information by road. It is the figure which illustrated the map around the event venue. It is a flowchart of the prediction movement route generation processing. It is a flowchart of the estimation process. It is a flowchart of a delivery process.

Hereinafter, the distribution system according to the present invention and the embodiment of the distribution program will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiments.

The distribution system according to the present invention is a system for distributing estimated congestion information, for example, a dedicated system for distributing estimated congestion information, or a computer used for general purposes (for example, a personal computer, a smartphone, etc.). It is a concept including a system realized by implementing a function of delivering estimated congestion information to a mobile terminal or the like. Further, the distribution system is a concept including, for example, a system realized by implementing a function of distributing estimated congestion information to a center device or the like that communicates with an in-vehicle device, and as an example. , A storage means, an acquisition means, an estimation means, and a delivery means.

Here, the "vehicle-mounted device" is a device mounted on a vehicle, and specifically, is a concept including an vehicle-mounted navigation device. The "center device" is a device that communicates with an in-vehicle device, and specifically, is a concept including a server device equipped with a predetermined computer.

The "storage means" is a means for storing event information that identifies an event to be held. The "acquisition means" is means for identifying a vehicle heading for an event to be specified by the event information stored in the storage means, and for specifying the outbound route of the specified vehicle. The "event" is an event or event, and is a concept including, for example, a concert, an exposition, a conference, or the like. Further, "toward an event" is a concept including, for example, going to the venue where the event is held or the vicinity of the venue for the purpose of participating in the event.

The "outward route information" is information for specifying the outbound route of the vehicle heading for the event, and is a concept including, for example, a travel history route which is a history of the destination and the traveled route.

The "estimating means" is traffic congestion information on each road around the event point, which is the event holding point specified by the event information stored in the storage means, based on the outbound route information acquired by the acquisition means. It is a means for estimating traffic congestion information, which is information on traffic congestion caused by vehicles away from the event point on each road. For example, based on the outbound route information acquired by the acquisition means, the return route information for specifying the return route of the vehicle is estimated and estimated. It is a concept including means for estimating traffic congestion information for each road around the event point based on the return route information, and traffic congestion information based on the outbound route information acquired by the acquisition means and other traffic information. It is a concept including means for estimating.

The “around the event point” is a concept including, for example, the area around the venue where the event is held (that is, the place where the event is held). The "traffic jam information" is the estimated traffic jam information, for example, the information for identifying the traffic jam on each road around the event point, which is the event holding point specified by the event information stored in the storage means. It is information that identifies traffic congestion that can be affected by vehicles away from the event point on each road. For example, information that can be obtained without considering other traffic information, or information that considers the other traffic information. It is a concept that includes information that can be obtained. The "return route information" is information for specifying the return route of the vehicle for which the outbound route information has been acquired, and is a concept including, for example, a planned travel route which is a planned travel route.

"Other traffic information" is traffic information other than the outbound route information acquired by the acquisition means, and is a concept including information distributed from an arbitrary distribution organization such as a road traffic information center, for example, as an example. , Current traffic information (for example, congestion degree of each road (number of vehicles per road), current accident, regulation, traffic closure, etc.), and predicted traffic information (for example, for each predicted road) It is a concept that includes the degree of traffic congestion (the number of vehicles on each road), predicted regulations, information on traffic closures, etc.).

The "delivery means" is a means for delivering the congestion information estimated by the estimation means. For example, it is determined whether or not the congestion caused by the event has started, and when it is determined that the congestion information has started, the congestion information is transmitted. It is a concept that includes means for distribution.

Then, in the embodiment shown below, a case where the distribution system is realized by the "center device" will be described.

In the following, a vehicle equipped with an in-vehicle device will be referred to as a "own vehicle". Further, the "own vehicle" is a concept including, for example, a four-wheeled vehicle, a two-wheeled vehicle, a bicycle, and the like, but the case where the own vehicle is a four-wheeled vehicle will be described below.

(Constitution)
First, the navigation system 100 according to the present embodiment will be described. FIG. 1 is a block diagram illustrating a navigation system according to an embodiment of the present invention. The navigation system 100 includes a distribution system, and includes, for example, an in-vehicle device 1 and a center device 2. Actually, the navigation system 100 includes a plurality of in-vehicle devices having the same configuration as the in-vehicle device 1, but here, for convenience of explanation, attention is paid to one in-vehicle device 1 unless otherwise specified. (The same applies to the processing described later).

(Configuration-In-vehicle device)
The in-vehicle device 1 includes, for example, a communication unit 11, a touch pad 12, a display 13, a speaker 14, a current position detection unit 15, a data recording unit 16, and a control unit 17.

(Configuration-In-vehicle device-Communication unit)
The communication unit 11 is a communication means for communicating with an external device via a network (not shown). The specific type and configuration of the communication unit 11 is arbitrary, and for example, a known mobile wireless communication means or a wireless communication means for a known VICS (registered trademark) system via FM multiplex broadcasting or a beacon can be used. Can be used.

(Configuration-In-vehicle device-Touch pad)
The touch pad 12 is an operation means for receiving various operation inputs from the user by being pressed by a user's finger or the like. The specific configuration of the touch pad 12 is arbitrary, but for example, a known one provided with an operation position detecting means by a resistance film method, a capacitance method, or the like can be used.

(Configuration-In-vehicle device-Display)
The display 13 is a display means for displaying various images under the control of the control unit 17. The specific configuration of the display 13 is arbitrary, but for example, a flat panel display such as a known liquid crystal display or an organic EL display can be used. The touch pad 12 and the display 13 may be integrally formed as a touch panel.

(Configuration-In-vehicle device-Speaker)
The speaker 14 is an audio output means that outputs various audios based on the control of the control unit 17. The specific mode of the voice output from the speaker 14 is arbitrary, and it is possible to output a synthetic voice generated as needed or a pre-recorded voice.

(Configuration-In-vehicle device-Current position detector)
The current position detection unit 15 is a current position acquisition means for acquiring the current position of the own vehicle. The current position detection unit 15 has a GPS, a gyro sensor, and a distance sensor (all not shown), and detects the current position (coordinates), orientation, and the like of the in-vehicle device 1 by a known method.

(Configuration-In-vehicle device-Data recording unit)
The data recording unit 16 is a recording means for recording a program and various data necessary for the operation of the in-vehicle device 1, and is configured by using, for example, a hard disk (not shown) as an external recording device. However, instead of or in combination with the hard disk, any other recording medium including a magnetic recording medium such as a magnetic disk or an optical recording medium such as a DVD or a Blu-ray disc can be used.

Further, the data recording unit 16 includes a map information database (hereinafter, the database is referred to as “DB”) 161.

(Configuration-In-vehicle device-Data recording unit-Map information DB)
The map information DB 161 is a map information storage means for storing map information. Here, "map information" is information for presenting a map to a user, and specifically, it is necessary for identifying various positions including roads, road intersections, road structures, facilities, and the like. Information such as node data (for example, node ID, coordinates, etc.) for each node set on the road and link data (for example, link ID, link name, connection node ID) for each link set on the road. , Road coordinates, road type (eg, narrow streets, general roads, major national roads, and highways, etc.), road width, number of lanes, etc.), feature data (eg, traffic lights, road signs, guard rails, facilities (location of parking lots, etc.) (Including coordinates as an example), etc.), topographical data, etc. are included. Then, such map information is recorded by an arbitrary method, but for example, it is recorded by inputting it through a predetermined recording medium, or information distributed from a distribution center (not shown) is received. (The same applies to the map information of the map information DB 221 described later).

(Configuration-In-vehicle device-Control unit)
The control unit 17 is a control means for controlling the in-vehicle device 1. Specifically, the CPU, various programs interpreted and executed on the CPU (basic control programs such as the OS, and specific functions started on the OS). A computer configured with an internal memory such as a RAM for storing programs and various data). In particular, the program according to the embodiment is installed in the in-vehicle device 1 via an arbitrary recording medium or network to substantially configure each part of the control unit 17. The processing performed by each unit of the control unit 17 will be described later.

(Configuration-Center device)
The center device 2 is a distribution system, and includes, for example, a communication unit 21, a data recording unit 22, and a control unit 23.

(Configuration-Center device-Communication unit)
The communication unit 21 is a communication means for communicating with an external device (for example, an in-vehicle device 1 or the like) via a network (not shown). The specific type and configuration of the communication unit 21 is arbitrary, but can be configured in the same manner as the communication unit 11 of the in-vehicle device 1, for example.

(Configuration-Center device-Data recording unit)
The data recording unit 22 is a recording means for recording a program and various data necessary for the operation of the center device 2, and can be configured in the same manner as the data recording unit 16 of the in-vehicle device 1, for example.

In addition, the data recording unit 22 includes map information DB221, movement route information DB222, predicted movement route information DB223, event information DB224, parking lot information DB225, and road-specific predicted congestion information DB226.

(Configuration-Center device-Data recording unit-Map information DB)
The map information DB 221 is a map information storage means for storing map information, and for example, stores the same information as the map information DB 161 of the in-vehicle device 1.

(Configuration-Center device-Data recording unit-Movement route information DB)
The movement route information DB 222 is a movement route information storage means for storing the movement route information. The "movement route information" is information including the above-mentioned outbound route information, and is, for example, information for specifying the history of the route on which the vehicle has traveled. FIG. 2 is a diagram illustrating movement route information. As shown in FIG. 2, the movement route information is configured by associating the item "vehicle ID", the item "destination information", and the item "movement route identification information" with the information corresponding to each item. ing. Here, the information corresponding to the item "vehicle ID" is vehicle identification information that uniquely identifies the vehicle (hereinafter, "identification information" is referred to as "ID") (in FIG. 2, the in-vehicle device 1 of FIG. 1 is shown. "ID001" for identifying other in-vehicle devices (not shown, "ID002", etc.). The information corresponding to the item "destination information" is the destination information that specifies the destination set in the vehicle (in FIG. 2, it is the coordinates on the map specified by the map information of the map information DB221. "(X11, Y11)" etc.). The notation of coordinates here is for convenience. The information corresponding to the item "Movement route identification information" is the movement route identification information for specifying the history of the route traveled by the vehicle (in FIG. 2, the route is specified by the link ID of the map information of the map information DB221. "LID001, LID002 ..., LID101, ...", etc.). Regarding this "LID001, LID002 ..., LID101, ...", for example, it is specified that the road traveled in the order of the road with link ID001, the road with link ID002, and the like. The specific storage method of such movement route information is arbitrary, but it is stored, for example, by executing the predicted movement route generation process described later (the same applies to the predicted movement route information).

(Configuration-Center device-Data recording unit-Predicted movement route information DB)
The predicted movement route information DB 223 is a predictive movement route information storage means for storing the predicted movement route information. The "predicted movement route information" is the above-mentioned return route information. FIG. 3 is a diagram illustrating predicted movement route information. As shown in FIG. 3, the predicted movement route information is configured by, for example, the item "vehicle ID" and the item "predicted movement route specific information" and the information corresponding to each item are associated with each other. Here, the information corresponding to the item "vehicle ID" is the same as the information having the same name in FIG. The information corresponding to the item "predicted travel route identification information" is the predicted travel route identification information that identifies the route to be traveled (in FIG. 3, the route is specified by the link ID of the map information of the map information DB221. "LID9011, LID902, ...", etc.). Regarding the "LID9011, LID902, ...", For example, a route traveling in the order of the road of the link ID 901, the road of the link ID 902, or the like is specified.

(Configuration-Center device-Data recording unit-Event information DB)
The event information DB 224 is the above-mentioned storage means, and specifically, is an event information storage means for storing event information. The "event information" is information that identifies the event to be held. FIG. 4 is a diagram illustrating event information. As shown in FIG. 4, the event information includes, for example, the item "event ID", the item "content information", the item "event position information", the item "time information", and the item "capacity information". The corresponding information is associated with each other. Here, the information corresponding to the item "event ID" is an event ID that uniquely identifies the event (in FIG. 4, "IDe001" or the like). The information corresponding to the item "content information" is the content information that specifies the content of the event (in FIG. 4, it is the type of event, such as "concert"). The information corresponding to the item "event position information" is the event position information that specifies the position where the event is held (event holding point) (in FIG. 4, the map information of the map information DB221 is the coordinates on the map specified. Yes, "(X10, Y10)" etc.). The information corresponding to the item "time information" is time information for specifying the time of the event (in FIG. 4, it is information for specifying the start time and end time of the event, and the start time is "18:00". “Start 1800, end: 2100”, etc., which specifies that the end time is “21:00”). The information corresponding to the item "capacity information" is the capacity information that specifies the capacity of the venue where the event is held or the event itself (in FIG. 4, "1000" that specifies 1000 people, etc.). The specific storage method of such event information is arbitrary, but it is stored, for example, by receiving information delivered from an external server that delivers information about the event.

(Configuration-Center device-Data recording unit-Parking lot information DB)
The parking lot information DB 225 is a parking lot information storage means for storing parking lot information. "Parking lot information" is information that identifies the state of the parking lot. FIG. 5 is a diagram illustrating parking information. As shown in FIG. 5, for example, the parking lot information correlates the item "parking lot ID", the item "parking lot position information", and the item "number of units information" with the information corresponding to each item. It is configured. Here, the information corresponding to the item "parking lot ID" is a parking lot ID that uniquely identifies the parking lot (in FIG. 5, "IDp001" or the like). The information corresponding to the item "parking lot position information" is the parking lot position information that specifies the position of the parking lot (in FIG. 5, it is the coordinates on the map specified by the map information of the map information DB221, and "(X11). , Y11) "etc.). The information corresponding to the item "number information" is the number information for specifying the number of vehicles parked in the parking lot (in FIG. 5, "100" for specifying 100 vehicles, etc.). The specific storage method of such parking lot information is arbitrary, but it is stored, for example, by receiving information distributed from an external server that distributes information about the parking lot.

(Configuration-Center device-Data recording unit-Forecast congestion information DB by road)
The road-specific predicted congestion information DB 226 is a road-specific predicted congestion information storage means for storing road-specific predicted congestion information. "Forecast traffic jam information by road" is traffic jam information by road around the event point. FIG. 6 is a diagram illustrating predicted traffic congestion information for each road. As shown in FIG. 6, the road-specific forecast congestion information is configured by, for example, the item "link ID" and the item "congestion degree information" and the information corresponding to each item are associated with each other. Here, the information corresponding to the item "link ID" is a link ID that identifies the road (in FIG. 6, it is a link ID of the map information of the map information DB 221, such as "LID901" and "LID902"). The information corresponding to the item "congestion degree information" is the congestion degree information for specifying the degree of congestion (in FIG. 6, it is the number of vehicles, "80" for specifying 80 vehicles, and "80" for specifying 30 vehicles. 30 "etc.). The specific storage method of such road-specific predicted congestion information is arbitrary, but it is stored, for example, by executing an estimation process described later.

(Configuration-Center device-Control unit)
The control unit 23 is a control means for controlling the center device 2, and can be configured in the same manner as the control unit 17 of the in-vehicle device 1, for example. The control unit 23 includes, for example, a acquisition unit 231, an estimation unit 232, and a distribution unit 233 in terms of functional concept. The acquisition unit 231 is an acquisition means for identifying a vehicle heading for an event specified by the event information stored in the event information DB 224 and acquiring outbound route information for specifying the outbound route of the specified vehicle. The estimation unit 232 is congestion information on each road around the event point, which is the event holding point specified by the event information stored in the event information DB 224, based on the outbound route information acquired by the acquisition unit 231. It is an estimation means for estimating traffic congestion information, which is information on traffic congestion caused by vehicles away from the event point on each road. The distribution unit 233 is a distribution means for distributing the congestion information estimated by the estimation unit 232. Each process performed by the control unit 23 will be described later.

(processing)
Next, the predicted movement route generation processing, the estimation processing, and the distribution processing executed by the navigation system 100 configured in this way will be described. FIG. 7 is a diagram illustrating a map around the event venue. For each process here, a case where information on traffic congestion around the event venue E1 in FIG. 7 is distributed will be described as appropriate. The event held at the event venue E1 in FIG. 7 is an event of "event ID" = "IDe001" in the event information of FIG. 4, that is, the position of the event venue E1 is "(X10, Y10)". Also, it will be described that the parking lot P1 of FIG. 7 is a parking lot adjacent to the event venue E1 and is a parking lot of "parking lot ID" = "IDp001" in the parking lot information of FIG. Further, the link ID of the road R1 around the event venue E1 in FIG. 7 is "LID901", the link ID of the road R2 is "ID902", and the link ID of the road R3 is "ID903". I will explain it as a thing.

(Processing-Predicted movement route generation process)
First, the predicted movement route generation process will be described. FIG. 8 is a flowchart of the predicted movement route generation process (steps are abbreviated as “S” in the following description of each process). The predicted movement route generation process is generally a process executed by the center device 2 and is a process for generating predicted movement route information. The timing of executing this predicted movement route generation process is arbitrary, but for example, it will be described from the point where the execution is started, assuming that the center device 2 is repeatedly started and the execution is started after the power is turned on (estimation process). , And the delivery process).

In SA1 of FIG. 8, the acquisition unit 231 of the center device 2 receives the movement route information. Specifically, although it is optional, for example, each in-vehicle device of the navigation system 100 (including the in-vehicle device 1 in FIG. 1 and the in-vehicle device (not shown)) has its own vehicle ID and a destination set to itself. It is assumed that the destination information for specifying the position of the vehicle and the movement route identification information for specifying the history of the traveled route are periodically transmitted to the center device 2, and the acquisition unit of the center device 2 The 231 receives and acquires the information transmitted from each of the vehicle-mounted devices as the movement route information, and records the received and acquired movement route information in the movement route information DB 222.

Here, for example, the in-vehicle device 1 of FIG. 1 has "vehicle ID" = "ID001", "destination information" = "(X11, Y11)", and "movement route identification information" = "LID001, LID002, ... When "..., LID101, ..." Is transmitted to the center device 2, the acquisition unit 231 of the center device 2 receives and acquires this information as movement route information, and moves the information at the top of FIG. Record in the route information DB 222.

In SA2 of FIG. 8, the acquisition unit 231 of the center device 2 acquires event information and parking lot information. Specifically, although it is arbitrary, for example, the event information of FIG. 4 and the parking lot information of FIG. 5 are acquired. Here, for example, the information of FIGS. 4 and 5 is acquired.

In SA3 of FIG. 8, the acquisition unit 231 of the center device 2 determines whether or not the destination of the vehicle equipped with the in-vehicle device corresponding to the movement route information received in SA1 is around the position where the event is held. By doing so, the vehicle heading for the event is identified. Specifically, although it is arbitrary, for example, the destination information received and recorded by SA1 is acquired, the event position information of the event information of FIG. 4 acquired by SA2 is acquired, and the event position information is acquired by SA2. The parking lot position information that specifies the vicinity of the position specified by the above-mentioned event position information in the parking lot position information of the parking lot information of FIG. 5 is acquired, and the destination information matches the event position information or the parking lot position information. Judgment is made based on whether or not to do so. In addition, "around the position specified by the event position information" is a concept including, for example, within a predetermined radius (for example, 100 m to 150 m, etc.) with reference to the position specified by the event position information. Then, when the destination information does not match either the event location information or the parking lot location information (that is, the destination information does not match the event location information and the destination information does not match the parking lot location information. Case), it is determined that the destination is not around the position where the event is held (NO of SA3), it is specified that the vehicle subject to the determination is not the vehicle heading for the event, and then the process is terminated. If the destination information matches the event location information or the parking lot location information, it is determined that the destination is around the location where the event is held (YES in SA3), and the vehicle subject to the determination is determined. After identifying that the vehicle is heading for the event, we will move to SA4.

Here, for example, the "destination information" = "(X11, Y11)" received in SA1 is stationed adjacent to the event venue E1 in FIG. 7 where the event of "event ID" = "IDe001" in FIG. 4 is held. Since it matches the "parking lot position information" = "(X11, Y11)" in FIG. 5, which specifies the position of the parking lot P1, the destination of the own vehicle, which is a vehicle equipped with the in-vehicle device 1, is the position where the event is held. Determined to be in the vicinity of (that is, identify that the vehicle is heading for the event).

In SA4 of FIG. 8, the control unit 23 of the center device 2 is identified by SA3 as a vehicle whose destination is determined to be around the position where the event is held (that is, a vehicle heading for the event). Predicted travel route information for the vehicle) is estimated and created. Specifically, although it is arbitrary, for example, the acquisition unit 231 acquires and estimates the movement route information (that is, the movement route information of the vehicle identified as the vehicle heading for the event) received and recorded by the SA1. The unit 232 creates the predicted movement route information based on the movement route information acquired by the acquisition unit 231 and records the created predicted movement route information in the predicted movement route information DB 223. The creation method here is arbitrary, but for example, the movement route identification information in FIG. 2 of the movement route information received and recorded by SA1 is information for specifying the outbound route to the vicinity of the position where the event is held. As a matter of fact, the return route corresponding to this outbound route is an arbitrary method (for example, a method in which the same route as the outbound route is regarded as the inbound route, or the position of the destination of the outbound route is the starting point and any method on the departure point side of the outbound route. A method of estimating by a route search method using the position as a destination, etc.) and creating predicted movement route information that specifies the estimated return route will be used. The travel route information here corresponds to "outward route information", and the predicted travel route information corresponds to "return route information".

Here, for example, "movement route identification information" = "LID001, LID002, ..., LID101, ..." Of the information at the top of FIG. 2 received and recorded by SA1, is "LID101, ..." It is assumed that the information specifies the outbound route to the parking lot P1 in FIG. 7 around the position where the event of "event ID" = "IDe001" is held, the inbound route corresponding to this outbound route is estimated, and the estimated return route is estimated. "Predicted movement route identification information" = "LID9011, LID902, ..." Is generated as the information to be specified, and after associating with the "vehicle ID" = "ID001" corresponding to the above-mentioned outbound route, the most of FIG. Create and record the information in the upper row. This completes the predicted movement route generation process.

(Processing-estimation processing)
Next, the estimation process will be described. FIG. 9 is a flowchart of the estimation process. The estimation process is generally a process executed by the center device 2 and is a process for generating predicted congestion information for each road.

In SB1 of FIG. 9, the estimation unit 232 of the center device 2 acquires the predicted movement route information. Specifically, although it is arbitrary, for example, the predicted movement route information DB 223 of FIG. 1 is accessed to acquire the predicted movement route information of FIG.

In SB2 of FIG. 9, the estimation unit 232 of the center device 2 creates and stores the predicted traffic congestion information for each road based on the predicted movement route information acquired by SA1. Specifically, although it is arbitrary, for example, in the predicted movement route specification information of FIG. 3, pay attention to the fact that the link ID of the roads to be sequentially traveled is specified when moving away from the vicinity of the position where the event is held. Then, the link IDs of the roads around the position where the event is held are acquired, and the number of vehicle IDs (that is, the number of vehicles) associated with each acquired link ID is calculated as the road corresponding to the link ID. It is counted as the degree of congestion due to vehicles that pass through and away from the event point, the number of counted vehicle IDs is estimated as the degree of congestion on the road corresponding to the link ID, and road prediction congestion information corresponding to the estimation result is created and stored. To do.

Here, for example, in the predicted movement route information of FIG. 3, the vehicle ID corresponding to "predicted movement route identification information" = "LID9011, LID902, ..." Is other than the illustrated "ID001" and "ID003". 28 vehicles are stored in the vehicle, and the vehicle ID corresponding to "predicted movement route identification information" = "LID9011, LID903, ..." (That is, information including "LID901" but not "LID902") , The case where 50 pieces are stored will be described as an example. In this case, the number of vehicle IDs corresponding to "link ID" = "LID901" is 80 (that is, "ID001", "ID003", 28 vehicle IDs (not shown), and 50 vehicles (not shown). (Total of IDs), and the number of vehicle IDs corresponding to "link ID" = "LID902" is 30 (that is, the total of "ID001", "ID003", and 28 (not shown)), so that "LID901" The congestion level of the road R1 in FIG. 7 which is the road of "LID902" is estimated to be "80", and the congestion degree of the road R2 of FIG. 7 which is the road of "LID902" is estimated to be "30". Based on these estimation results, the information in the uppermost row and the second row in FIG. 6 is created and stored. Actually, the road R3 and other roads in FIG. 7 are also processed, but since this process is the same as the above process, the description thereof will be omitted. This ends the estimation process.

(Processing-Distribution processing)
Next, the delivery process will be described. FIG. 10 is a flowchart of the distribution process. The distribution process is generally a process executed by the center device 2 and is a process of distributing dedicated traffic information at the time of an event. The "event-dedicated traffic information" is traffic congestion information obtained in consideration of the other traffic information described above. Specifically, the road-specific traffic congestion information created in SB2 of FIG. 9 and other traffic. Information about traffic congestion based on information.

In SC1 of FIG. 10, the distribution unit 233 of the center device 2 determines whether or not to distribute the dedicated traffic information at the time of the event. Specifically, although it is optional, for example, there is a possibility that traffic congestion may occur due to a vehicle leaving the venue of the event after the event, but the event is generally as shown in the time information of FIG. , Although the end time is set, there is a fact that the event does not end on time, so the judgment is made as follows in consideration of this situation. Specifically, it is assumed that the number information of the parking lot information in FIG. 5 is configured to be updated to the latest information at predetermined time (for example, 30 seconds to 1 minute, etc.) intervals, and when the number information decreases. In addition, the following processing is performed as it is determined that the congestion caused by the event will start. More specifically, paying attention to the event position information in FIG. 4 and the parking lot position information in FIG. 5, in FIG. 5, the parking lot ID of the parking lot around the venue where the event is held is specified and the specified parking lot is specified. It is determined whether or not the number of vehicles specified by the number information corresponding to the parking lot ID has decreased. Then, if the number of vehicles has not decreased by a predetermined number or more (for example, 10 to 15 vehicles) within a predetermined time (for example, within 5 minutes), the number of vehicles has not decreased, so that the event is held. After determining that the resulting congestion has not started, it is determined that the event-specific traffic information will not be delivered (SC1 NO), and SC1 is repeated until it is determined that the event-specific traffic information will be distributed. Run. In addition, when the number of vehicles decreases by more than the specified number within a predetermined time, it is determined that the number of vehicles has decreased, and after determining that the traffic congestion due to the event has started, the traffic dedicated to the event It is determined that the information is to be delivered (YES of SC1), and the process proceeds to SC2.

Here, for example, regarding the parking lot P1 around the event venue E1 in FIG. 7, if the number information in FIG. 5 decreases by 20 in 5 minutes, it is determined that the number of vehicles has decreased, which is caused by the event. After determining that the traffic jam has started, it is determined that the exclusive traffic information at the time of the event will be delivered.

In SC2 of FIG. 10, the estimation unit 232 of the center device 2 estimates and creates the traffic information dedicated to the event. Specifically, it is optional, but for example, first, after referring to the parking lot position information in FIG. 5 and the map information in the map information DB 161 in FIG. 1, it is determined that the number of vehicles is decreasing in SC1. Identify the link ID of the road around the parking lot (that is, the road around the location where the event is held), refer to the predicted congestion information for each road in FIG. 6, and refer to the congestion degree corresponding to the identified link ID. Get information. Next, other traffic information distributed from any distribution agency such as the road traffic information center (not shown) (for example, the link of each current road where the number of vehicles due to traffic congestion caused by the event is not considered. The number of vehicles for each ID) is acquired. Next, for each of the above-mentioned specified link IDs, the number of vehicles specified by the above-mentioned acquired congestion degree information and the number of vehicles in other traffic information are added, and the result of the addition corresponds to the link ID. The attached information is estimated and created as traffic information dedicated to the event.

Here, for example, 100 vehicles are distributed as other traffic information of the road R1 of "LID901" in FIG. 7 from an arbitrary distribution organization such as a road traffic information center (not shown), and the road R2 of "LID902" An example will be described in which 200 vehicles are delivered as other traffic information. In this case, by adding 80 vehicles specified by "congestion degree information" = "80" of "link ID" = "LID901" in FIG. 6 and 100 vehicles as other traffic information of the above-mentioned road R1. As the traffic information of the road R1, information in which "LID901" and "180" for identifying 180 vehicles are associated is created, and "link ID" in FIG. 6 = "congestion degree information" of "LID902" = "30". By adding 30 vehicles specified in "" and 200 vehicles as other traffic information on the road R2 described above, "LID902" and "230" specifying 230 vehicles are associated with each other as traffic information on the road R2. Information is created, and the same processing is performed for the other roads in FIG. 7, and each of the created information is estimated and created as traffic information dedicated to the event.

In SC3 of FIG. 10, the distribution unit 233 of the center device 2 distributes the traffic information dedicated to the event. Specifically, although it is arbitrary, for example, the event-dedicated traffic information created by SC2 is acquired, and the acquired event-dedicated traffic information is transmitted to each in-vehicle device of the navigation system 100 via the communication unit 21. To deliver. Here, for example, the information in which the above-mentioned "LID901" and "180" are associated with each other, the information in which "LID902" and "230" are associated with each other, and the like are used as the traffic information dedicated to the event, and each of the navigation systems 100. Deliver to in-vehicle devices. Subsequent processing on the vehicle-mounted device side is optional, but for example, each vehicle-mounted device receives the delivered event-time dedicated traffic information and provides guidance based on the received event-time dedicated traffic information. This ends the distribution process.

(Effect of embodiment)
As described above, according to the present embodiment, by estimating the traffic congestion information on each road around the event point based on the outbound route information, for example, the traffic congestion information on each road around the event point can be distributed. , It becomes possible to appropriately grasp the traffic congestion information on each road around the event point.

Further, by estimating the return route information and estimating the congestion information for each road based on the estimated return route information, for example, it is possible to improve the estimation accuracy of the congestion information.

In addition, by delivering the traffic jam information when the traffic jam caused by the event starts, it is possible to deliver the traffic jam information at an appropriate timing related to the end of the event (for example, the timing when the event ends). It becomes.

Further, by estimating the traffic jam information based on the outbound route information and other traffic information, for example, the traffic jam information can be estimated in consideration of other traffic information, so that the estimation accuracy of the traffic jam information can be improved. Is possible.

[Modified example with respect to the embodiment]
Although the embodiments according to the present invention have been described above, the specific configuration and means of the present invention may be arbitrarily modified and improved within the scope of the technical idea of the present invention described in the claims. Can be done. Hereinafter, such a modification will be described.

(About the problem to be solved and the effect of the invention)
First, the problem to be solved by the invention and the effect of the invention are not limited to the above-mentioned contents, and may differ depending on the implementation environment and the details of the configuration of the invention, and only a part of the above-mentioned problems. May be resolved or only some of the effects described above may be achieved.

(About distribution and integration)
Further, each of the above-mentioned electrical components is a functional concept, and does not necessarily have to be physically configured as shown in the figure. That is, the specific form of distribution or integration of each part is not limited to the one shown in the figure, and all or part of the parts may be functionally or physically dispersed or integrated in arbitrary units according to various loads and usage conditions. Can be configured. Further, the "device" in the present application is not limited to a device composed of a single device, but includes a device composed of a plurality of devices. For example, the center device 2 is provided with at least a part of the functions of the vehicle-mounted device 1, and then the vehicle-mounted device 1 and the center device 2 communicate with each other to perform the same processing as in the embodiment. You may. On the contrary, at least a part of the functions of the center device 2 may be provided in the in-vehicle device 1.

(About shape, numerical value, structure, time series)
With respect to the components illustrated in the embodiments and drawings, the shapes, numerical values, or the interrelationships of the structures or time series of the plurality of components shall be arbitrarily modified and improved within the scope of the technical idea of the present invention. Can be done.

(About the timing of delivering exclusive traffic information at the time of the event)
Further, in the above embodiment, in SC1 of FIG. 10, whether or not to distribute the exclusive traffic information at the time of the event by paying attention to the number of vehicles parked in the parking lot around the position where the event is held. The case of determining is described, but the present invention is not limited to this. For example, paying attention to the event end time of the time information in FIG. 4, it may be determined that the event is to be delivered when the event end time arrives. Alternatively, it may be determined that the information specifying that the event has ended is transmitted from the event operator side to the center device 2 side, and when this information is received, it is to be distributed.

(Information that identifies the time)
Further, the travel route information in FIG. 2 is associated with the time when the travel route information is stored, or each link ID in the travel route identification information and the time when the link ID is traveled are associated with each other and stored. Therefore, it may be configured to pay attention to these times and perform appropriate processing.

[Part of the features and effects of the embodiment]
Finally, some of the features and effects of the embodiments described so far are illustrated below. However, the features and effects of the embodiments are not limited to the following contents, and only a part of the following effects can be achieved by having only a part of the following features, or other than the following features. By having the characteristics, it may exert other effects other than the following effects.

The distribution system according to one aspect 1 of the embodiment identifies a storage means for storing event information that specifies an event to be held and a vehicle heading for an event that the event information stored in the storage means specifies. An event specified by the event information stored in the storage means is held based on the acquisition means for acquiring the outbound route information for specifying the outbound route of the specified vehicle and the outbound route information acquired by the acquisition means. Congestion information on each road around the event point, which is a point, and is information on traffic congestion caused by a vehicle away from the event point on each road. An estimation means for estimating the congestion information, and the congestion information estimated by the estimation means. It is provided with a delivery means for delivering the above.

According to the distribution system according to the above aspect 1, by estimating the congestion information on each road around the event point based on the outbound route information, for example, the congestion information on each road around the event point can be distributed. , It becomes possible to appropriately grasp the traffic congestion information on each road around the event point.

The distribution system according to the other aspect 2 of the embodiment is the distribution system according to the aspect 1, wherein the estimation means is the return route information that identifies the return route of the vehicle based on the outward route information acquired by the acquisition means. Is estimated, and the congestion information for each road around the event point is estimated based on the estimated return route information.

According to the distribution system according to the above aspect 2, by estimating the return route information and estimating the congestion information for each road based on the estimated return route information, for example, it is possible to improve the estimation accuracy of the congestion information. ..

In the distribution system according to the other aspect 3 of the embodiment, in the distribution system according to the aspect 1 or 2, the distribution means determines whether or not the congestion caused by the event has started, and determines that the congestion has started. If so, the traffic jam information is delivered.

According to the distribution system according to the above aspect 3, by distributing the congestion information when the congestion caused by the event starts, for example, an appropriate timing related to the end of the event (for example, the timing when the event ends, or the timing when the event ends, or Congestion information can be delivered at the timing immediately before the end of the event, etc.).

The distribution system according to the other aspect 4 of the embodiment is the distribution system according to any one of the aspects 1 to 3, wherein the estimation means includes the outbound route information acquired by the acquisition means and other traffic information. Based on this, the traffic jam information is estimated.

According to the distribution system according to the above aspect 4, by estimating the traffic jam information based on the outbound route information and other traffic information, for example, the traffic jam information can be estimated in consideration of other traffic information. It is possible to improve the estimation accuracy of traffic congestion information.

The distribution program according to the other aspect 5 of the embodiment identifies the vehicle heading for the event specified by the event information stored in the storage means for storing the event information specifying the event to be held by the computer. At the holding point of the event specified by the event information stored in the storage means based on the acquisition means for acquiring the outbound route information for specifying the outbound route of the specified vehicle and the outbound route information acquired by the acquisition means. Congestion information on each road around a certain event point, which is information on traffic congestion caused by vehicles away from the event point on each road, and an estimation means for estimating the congestion information, and the congestion information estimated by the estimation means are distributed. It functions as a delivery means to be used.

According to the distribution program according to the above aspect 5, by estimating the congestion information on each road around the event point based on the outbound route information, for example, the congestion information on each road around the event point can be distributed. , It becomes possible to appropriately grasp the traffic congestion information on each road around the event point.

1 In-vehicle device 2 Center device 11 Communication unit 12 Touch pad 13 Display 14 Speaker 15 Current position detection unit 16 Data recording unit 161 Map information DB
17 Control unit 21 Communication unit 22 Data recording unit 23 Control unit 100 Navigation system 221 Map information DB
222 Travel route information DB
223 Predicted movement route information DB
224 Event information DB
225 Parking Information DB
226 Forecast congestion information by road 231 Acquisition part 232 Estimation part 233 Distribution part E1 Event venue P1 Parking lot R1 Road R2 Road R3 Road

Claims (5)

A storage means for storing event information that identifies the event to be held, and
An acquisition means for identifying a vehicle heading for an event specified by the event information stored in the storage means and acquiring outbound route information for specifying the outbound route of the specified vehicle.
Based on the outbound route information acquired by the acquisition means, the event information stored in the storage means is congestion information on each road around the event point, which is the holding point of the event specified, in each road. An estimation means for estimating the traffic jam information, which is information on traffic jams caused by vehicles away from the event point, and
A delivery means for delivering the congestion information estimated by the estimation means, and
Delivery system with. The estimation means estimates the return route information that identifies the return route of the vehicle based on the outbound route information acquired by the acquisition means, and based on the estimated return route information, the congestion information for each road around the event point. To estimate,
The delivery system according to claim 1. The distribution means determines whether or not the traffic jam caused by the event has started, and if it determines that the traffic jam has started, the traffic jam information is delivered.
The delivery system according to claim 1 or 2. The estimation means estimates the traffic congestion information based on the outbound route information acquired by the acquisition means and other traffic information.
The distribution system according to any one of claims 1 to 3. Computer,
An acquisition means for identifying a vehicle heading for an event specified by the event information stored in a storage means for storing event information for specifying an event to be held and acquiring outbound route information for specifying the outbound route of the specified vehicle. ,
Based on the outbound route information acquired by the acquisition means, the event information stored in the storage means is congestion information on each road around the event point, which is the holding point of the event specified, in each road. An estimation means for estimating the traffic jam information, which is information on traffic jams caused by vehicles away from the event point, and
A delivery means for delivering the congestion information estimated by the estimation means, and
A delivery program that functions as.

Images