JP2022157811A - Congestion determination device, congestion determination method, and program - Google Patents

Abstract

To provide a congestion determination device, a congestion determination method, and a program that can accurately determine the occurrence of congestion on a toll road based on the driving time of a vehicle that has actually been driven from a starting point of the road to the destination point.SOLUTION: A congestion determination device includes: a vehicle identification information acquisition unit that acquires vehicle identification information that can identify each of a plurality of vehicles passing on a toll road from each of a plurality of roadside devices installed on the toll road; and a determination unit for determining, based on the vehicle identification information acquired by the vehicle identification information acquisition unit, whether or not congestion occurs on the toll road.SELECTED DRAWING: Figure 4

Description

The present disclosure relates to a congestion determination device, a congestion determination method, and a program.

In Patent Document 1, a roadside device is provided on the side of a road on which a vehicle travels, and the roadside device receives a signal from the vehicle a plurality of times within a range in which it can communicate with the vehicle, thereby determining the moving speed of the vehicle. It discloses that it calculates Patent Document 1 discloses a technique for determining that traffic congestion is occurring when the moving speed of a vehicle is slower than a predetermined speed.

JP 2009-169674 A

However, with the technology disclosed in Patent Document 1, although it is possible to determine whether or not a traffic jam occurs at a specific point on the road, the vehicle cannot move from the starting point to the destination point on the road. However, it is not possible to know how long it will take. Further, in the technology disclosed in Patent Document 1, in order to know whether or not there is traffic congestion on the entire road, it is necessary to install a large number of roadside devices at predetermined intervals on the entire road. There is

The present disclosure has been made in order to solve the above problems, and is to accurately determine the occurrence of traffic congestion on a toll road based on the travel time of a vehicle that actually traveled from a starting point to a destination point on the road. It is an object of the present invention to provide a traffic jam determination device, a traffic jam determination method, and a program.

In order to solve the above problems, the traffic congestion determination device according to the present disclosure provides vehicle identification information capable of identifying each of a plurality of vehicles traveling on the toll road from each of a plurality of roadside devices installed on the toll road. A vehicle identification information acquiring unit for acquiring; and a determining unit for determining whether or not the toll road is congested based on the vehicle identification information acquired by the vehicle identification information acquiring unit.

Further, in order to solve the above problems, a congestion determination method according to the present disclosure provides a vehicle identification method capable of identifying each of a plurality of vehicles traveling on a toll road from each of a plurality of roadside devices installed on the toll road. The method includes a vehicle identification information acquisition step of acquiring information, and a determination step of determining whether or not the toll road is congested based on the vehicle identification information acquired in the vehicle identification information acquisition step.

Further, in order to solve the above problems, a program according to the present disclosure causes a computer of a congestion determination device to detect each of a plurality of vehicles traveling on the toll road from each of a plurality of roadside devices installed on the toll road. a vehicle identification information acquisition step of acquiring identifiable vehicle identification information; and a determination step of determining whether or not the toll road is congested based on the vehicle identification information acquired in the vehicle identification information acquisition step. , is executed.

Advantageous Effects of Invention According to the present disclosure, it is possible to accurately determine the occurrence of congestion on a toll road based on the travel time of a vehicle that actually traveled from a starting point to a destination point on the road.

1 is a schematic diagram showing the configuration of a congestion determination system according to a first embodiment of the present disclosure; FIG. 1 is a schematic block diagram showing the configuration of a roadside device according to a first embodiment of the present disclosure; FIG. It is a figure which shows an example of the vehicle information which the roadside apparatus which concerns on 1st Embodiment of this indication produces|generates. 1 is a schematic block diagram showing the configuration of a congestion determination device according to a first embodiment of the present disclosure; FIG. It is a figure which shows an example of the traffic congestion information which the congestion determination apparatus which concerns on 1st Embodiment of this indication produces|generates. It is a figure which shows an example of the all-vehicles information which the congestion determination apparatus which concerns on 1st Embodiment of this indication memorize|stores. It is a figure which shows an example of the congestion determination information which the congestion determination apparatus which concerns on 1st Embodiment of this indication memorize|stores. FIG. 4 is a sequence diagram showing processing of the congestion determination system according to the first embodiment of the present disclosure; 4 is a flowchart showing processing of the roadside device according to the first embodiment of the present disclosure; 4 is a flow chart showing processing of the traffic jam determination device according to the first embodiment of the present disclosure; FIG. 3 is a schematic block diagram showing the configuration of a traffic jam determination device according to a second embodiment of the present disclosure; FIG. FIG. 11 is a schematic block diagram showing the configuration of a traffic jam determination device according to a third embodiment of the present disclosure; FIG. 11 is a schematic block diagram showing the configuration of a traffic jam determination device according to a fourth embodiment of the present disclosure; FIG. 11 is a schematic block diagram showing the configuration of a traffic congestion determination device according to a fifth embodiment of the present disclosure; FIG. 11 is a schematic block diagram showing the configuration of a congestion determination device according to a sixth embodiment of the present disclosure; FIG. 11 is a schematic block diagram showing the configuration of a congestion determination device according to a seventh embodiment of the present disclosure;

<First Embodiment>
A congestion determination system according to a first embodiment of the present disclosure will be described below with reference to FIGS. 1 to 10. FIG.

FIG. 1 is a schematic diagram showing the configuration of a congestion determination system 100 according to the first embodiment. The congestion determination system 100 determines whether or not there is congestion on the toll road 10 on which vehicles C1, C2, etc. pass. The toll road 10 is, for example, an expressway on which a toll must be paid for each predetermined section when a vehicle travels there. In Japan, vehicles are categorized into five categories: light/two-wheeled vehicles, ordinary vehicles, medium-sized vehicles, large vehicles, and extra-large vehicles. Here, the case where the vehicle C1 is a "regular vehicle" and the vehicle C2 is an "extra-large vehicle" will be described.

The toll road 10 is provided with an entrance G1, a tollgate G2, an exit G3, and an exit G4. Here, a case will be described where the vehicle C1 gets on the toll road 10 from the entrance G1, passes through the tollgate G2, and exits the toll road 10 at the exit G3. Also, a case where the vehicle C1 gets on the toll road 10 from the entrance G1, passes through the tollgate G2, and exits the toll road 10 at the exit G4 will be described.

A traffic jam determination system 100 shown in FIG. The roadside device 200a is installed at the entrance G1 of the toll road 10, acquires vehicle information from vehicles passing through the entrance G1, and transmits the acquired vehicle information to the congestion determination device 300a by wireless communication. The road device 200b is installed at the tollgate G2 of the toll road 10, acquires vehicle information from vehicles passing through the tollgate G2, and transmits the acquired vehicle information to the congestion determination device 300a by wireless communication.

The roadside device 200c is installed at the exit G3 of the toll road 10, acquires vehicle information from vehicles passing through the exit G3, and transmits the acquired vehicle information to the congestion determination device 300a by wireless communication. The roadside device 200d is installed at the exit G4 of the toll road 10, acquires vehicle information from vehicles passing through the exit G4, and transmits the acquired vehicle information to the congestion determination device 300a by wireless communication.

The congestion determination device 300a is configured by a PC (Personal Computer) or the like. The congestion determination device 300a is communicatively connected to roadside devices 200a, 200b, 200c, and 200d via a local network constructed by a company that provides services for the toll road 10. FIG. The congestion determination device 300a acquires vehicle information from each of the roadside devices 200a, 200b, 200c, and 200d, generates congestion status information based on the vehicle information, and sends the generated congestion status information to the cloud server 400. Send.

The cloud server 400 is configured by a PC or the like. The cloud server 400 is connected to the congestion determination device 300a via a public communication network 20 such as the Internet. The cloud server 400 stores traffic congestion information received from the traffic congestion determination device 300a, and provides the traffic congestion information to the user in response to a request from the user.

FIG. 2 is a schematic block diagram showing the configuration of the roadside device 200a (FIG. 1) according to the first embodiment. The construction of the roadside devices 200b, 200c, and 200d shown in FIG. 1 is the same as that of the roadside device 200a, so the description of the construction of the roadside devices 200b, 200c, and 200d is omitted.

The roadside device 200 a includes a control unit 201 , a sensor 202 , an imaging unit 203 , a clock 204 , a detection time storage unit 205 and a communication interface 206 . The control unit 201 is configured by a CPU (Central Processing Unit) and the like. The control unit 201 includes a vehicle detection unit 2011 , a vehicle information generation unit 2012 and a vehicle information transmission unit 2013 . The vehicle detection unit 2011 uses the sensor 202 to detect whether or not a vehicle exists within a predetermined range (for example, within 3 m) of the roadside device 200a. The vehicle information generator 2012 generates vehicle information.

FIG. 3 is a diagram showing an example of vehicle information Z1 generated by the vehicle information generator 2012 of the roadside device 200a according to the first embodiment. In the vehicle information Z1, vehicle identification information (for example, 1000004), vehicle detection time (for example, 09:00:00 on December 04, 2020), and roadside device identification information (for example, 200001) are associated. ing. The vehicle identification information is information of the number written on the license plate of the vehicle detected by the vehicle detection unit 2011 . The vehicle detection time is the time when the vehicle is detected by the vehicle detection unit 2011 . The roadside device identification information is information for identifying the roadside device 200a from the other roadside devices 200b and 200c.

Returning to the description of FIG. 2, the vehicle information transmission unit 2013 transmits the vehicle information Z1 (see FIG. 3) generated by the vehicle information generation unit 2012 to the congestion determination device 300a via the communication interface 206. FIG.

The sensor 202 is an optical sensor and optically detects a vehicle passing through the entrance G1 of the toll road 10 . The photographing unit 203 is a high-definition camera, and photographs an image including the license plate of a vehicle passing through the entrance G1 of the toll road 10 . A clock 204 measures the current time. The detection time storage unit 205 is a RAM (Random Access Memory) or the like, and stores the time when the vehicle detection unit 2011 detects the vehicle using the clock 204 . The communication interface 206 is an antenna or the like, and is used when the roadside device 200a communicates with the congestion determination device 300a.

FIG. 4 is a schematic block diagram showing the configuration of the congestion determination device 300a (FIG. 1) according to the first embodiment. The traffic congestion determination device 300 a includes a control section 301 , an all vehicle information storage section 302 , a traffic congestion determination information storage section 303 , a congestion status information storage section 304 and a communication interface 305 . The control unit 301 includes a vehicle identification information acquisition unit 3011 , a determination unit 3012 , a traffic congestion information generation unit 3013 and a traffic congestion information transmission unit 3014 .

The vehicle identification information acquisition unit 3011 acquires vehicle information Z1 from each of the roadside devices 200a, 200b, 200c, and 200d installed on the toll road 10 via the communication interface 305, as shown in FIG. The determination unit 3012 determines whether or not the toll road 10 is congested based on the all-vehicle information stored in the all-vehicle information storage unit 302 . The congestion information generation unit 3013 generates congestion information indicating the congestion status of the toll road 10 .

FIG. 5 is a diagram showing an example of the congestion status information Z2 generated by the congestion determination device 300a according to the first embodiment. In the traffic congestion information Z2, the starting point (for example, entrance G1), the destination point (for example, exit G3), the average required time calculation date and time (for example, 09:00 on December 4, 2020), and the average required time (for example, 25 minutes) is associated with a traffic jam situation (for example, slightly congested). The starting point indicates the entrance G1 through which the vehicle passes first in the section of the toll road 10 where it is determined whether or not there is traffic congestion.

The arrival point indicates the exit G3 through which the vehicle passes last in the section of the toll road 10 where it is determined whether or not there is traffic congestion. The average required time calculation date and time indicates the time at which the traffic congestion situation calculated every predetermined time (every 5 minutes in FIG. 5) was calculated. The average required time is calculated by the traffic congestion determination device 300a and indicates how long it is expected to take to travel by vehicle from the departure point to the destination point. The congestion status indicates the degree of congestion on the toll road 10, and is classified into no congestion, slightly congested, congested, and severely congested.

FIG. 5 shows information about whether or not there is a traffic jam between the starting point, the entrance G1, and the destination, the exit G3, at predetermined time intervals (that is, every five minutes). The traffic congestion information Z2 shown in FIG. 5 may be generated, for example, every minute or every ten minutes. In addition to the congestion situation between the entrance G1 and the exit G3, the congestion situation between the entrance G1 and the exit G4, the congestion situation between the entrance G1 and the toll gate G2, and the traffic congestion situation between the toll gate G2 and the destination D3 , or between the tollgate G2 and the arrival point D4.

Returning to the description of FIG. 4 , the traffic congestion information transmission unit 3014 transmits the traffic congestion information ( FIG. 5 ) stored in the traffic congestion information storage unit 304 to the cloud server 400 via the communication interface 305 .

The all vehicle information storage unit 302 is composed of a RAM or the like, and the vehicle identification information acquisition unit 3011 stores all vehicle information generated based on the vehicle information Z1 (FIG. 3) acquired from each of the roadside devices 200a, 200b, 200c, and 200d. Vehicle information Z3 is stored.

FIG. 6 is a diagram showing an example of the all-vehicle information Z3 stored by the congestion determination device 300a according to the first embodiment. In the all vehicle information Z3, vehicle identification information, departure point, vehicle detection time, and running time are stored in association with each other. The vehicle identification information is identification information of a vehicle that has passed through both the entrance G1 and the exit G3 of the toll road 10, and is included in both the vehicle information Z1 (FIG. 3) transmitted from the roadside device 200a and the roadside device 200c. Information.

The starting point indicates the starting point of the section on the toll road 10 where it is determined whether or not there is traffic congestion. The arrival point indicates the end point of the section for which it is determined whether or not there is traffic congestion on the toll road 10 . The vehicle detection time is the time when the vehicle is detected at the exit G3, which is the arrival point, and is specified based on the vehicle information Z1 (FIG. 3) transmitted from the roadside device 200c.

Returning to FIG. 4, the congestion determination information storage unit 303 is configured by a RAM or the like, and stores congestion determination information used when determining whether or not there is congestion on the toll road 10 .

FIG. 7 is a diagram showing an example of the congestion determination information Z4 stored by the congestion determination device 300a according to the first embodiment. The congestion determination information Z4 is pre-stored in the congestion determination information storage unit 303 before the congestion determination processing by the congestion determination device 300a is started. In all vehicle information Z4, starting point (eg, entrance G1), arrival point (eg, exit G3), distance (eg, 20 km), normal required time (eg, 15 minutes), no congestion (eg, less than 20 minutes) , slightly congested (for example, 20 minutes or more and less than 30 minutes), traffic congestion (for example, 30 minutes or more and less than 60 minutes), and severe traffic congestion (60 minutes or more) are associated and stored.

The starting point indicates the starting point of the section on the toll road 10 where it is determined whether or not there is traffic congestion. The arrival point indicates the end point of the section to be determined whether or not the toll road 10 is congested. The distance indicates how many kilometers there is from the starting point to the destination point. The normal required time indicates how long it takes to travel by vehicle from the starting point to the destination point when there is no traffic jam.

Assuming that the time required for the vehicle to move from the departure point G1 to the destination exit G3 is X minutes, the determining unit 3012 (FIG. 4) outputs the congestion determination information Z4 shown in FIG. By referring to, if X minutes is less than 20 minutes, it is determined that there is no congestion, if it is 20 minutes or more and less than 30 minutes, it is determined that there is traffic congestion, and if it is 30 minutes or more and less than 60 minutes If there is, it is determined as a traffic jam, and if it is 60 minutes or more, it is determined as a heavy traffic jam.

Returning to FIG. 4, the communication interface 305 is configured by a communication device for wireless communication or wired communication, and is used when communicating with the roadside devices 200a, 200b, 200c, and 200d, cloud servers, and the like.

FIG. 8 is a sequence diagram showing the processing of the congestion determination system 100 (FIG. 1) according to the first embodiment. When the roadside device 200a detects a vehicle passing through the entrance G1 where the roadside device 200a is installed, the roadside device 200a acquires vehicle information (FIG. 3) from the vehicle and transmits the vehicle information to the congestion determination device 300a (step S101). When the road device 200b detects a vehicle passing through the toll booth G2 where the road device 200b is installed, the road device 200b acquires vehicle information from the vehicle and transmits the vehicle information to the congestion determination device 300a (step S102).

When the road device 200c detects a vehicle passing through the exit G3 where the road device 200c is installed, the road device 200c acquires vehicle information from the vehicle and transmits the vehicle information to the congestion determination device 300a (step S103). When the road device 200d detects a vehicle passing through the exit G4 where the road device 200d is installed, the road device 200d acquires vehicle information from the vehicle and transmits the vehicle information to the congestion determination device 300a (step S104).

In steps S101 to S104, the traffic congestion determination device 300a generates congestion status information Z2 (FIG. 5) based on the vehicle information (FIG. 3) received from each of the roadside devices 200a, 200b, 200c, and 200d, and transmits it to the cloud server. 400 (step S105). Before entering the toll road 10 with the vehicle, the driver of the vehicle that is going to use the toll road 10 uses a mobile terminal such as a smartphone owned by the driver to store the traffic congestion information (see FIG. 5) in the cloud server 400. ) is requested (step S106).

Upon receiving the transmission request from the mobile terminal in step S106, the cloud server 400 transmits traffic congestion information (FIG. 5) to the mobile terminal (step S107). As a result, the driver can know how long it takes to travel by vehicle from the starting point of the toll road 10 to the destination point before using the toll road 10.例文帳に追加

FIG. 9 is a flowchart showing processing of the roadside device 200a (FIG. 2) according to the first embodiment. The processing of the roadside devices 200b, 200c, and 200d is the same as that of the roadside device 200a, so the description of the processing of the roadside devices 200b, 200c, and 200d is omitted.

First, the vehicle detection unit 2011 of the roadside device 200a determines whether or not a vehicle has been detected (step S201). Specifically, the vehicle detection unit 2011 uses the sensor 202 to detect whether or not a vehicle has entered the entrance G1 of the toll road 10 on which the roadside device 200a is installed. If the vehicle detection unit 2011 has not detected a vehicle (NO in step S201), the process of step S201 is repeated. On the other hand, when the vehicle detection unit 2011 detects a vehicle (YES in step S201), the vehicle detection unit 2011 refers to the clock 204 to specify the time when the vehicle detection unit 2011 detects the vehicle, The time is stored in the detection time storage unit 205 (step S202).

Further, the vehicle detection unit 2011 uses the image capturing unit 203 to capture an image including the vehicle identification information (here, license plate) of the vehicle detected in step S201 (step S203). The vehicle detection unit 2011 acquires the vehicle identification information by specifying the vehicle identification information of the vehicle detected in step S201 by analyzing the image captured in step S2011 (step S204).

The vehicle information generation unit 2012 associates the image identification information acquired in step S204, the detection time stored in the detection time storage unit 205, and the identification information for distinguishing the roadside device 200a from other roadside devices. Then, vehicle information (FIG. 3) is generated (step S205). The vehicle information transmission unit 2013 transmits the vehicle information Z1 generated in step S205 to the congestion determination device 300a via the communication interface 206 (step S206).

FIG. 10 is a flow chart showing the processing of the congestion determination device 300a (FIG. 4) according to the first embodiment. Here, a case will be described where it is determined whether or not there is a traffic jam between the entrance G1 and the exit G3 of the toll road 10 shown in FIG. First, the vehicle identification information acquisition unit 3011 of the congestion determination device 300a receives vehicle information (FIG. 3) including vehicle identification information transmitted from each of the roadside devices 200a to 200d installed on the toll road 10 (step S301).

The determination unit 3012 generates all-vehicle information (FIG. 6) based on the vehicle information acquired in step S301, and stores it in the all-vehicle information storage unit 302 (step S302). Specifically, the determination unit 3012 combines the vehicle identification information included in the vehicle information (FIG. 3) received from the roadside device 200a installed at the entrance G1, which is the departure point, with the vehicle identification information installed at the exit G3, which is the arrival point. By collating the vehicle identification information contained in the vehicle information received from the roadside device 200c with the vehicle identification information contained in both vehicle information, the vehicle identification information contained in common in both vehicle information is extracted, and all vehicle information (Fig. 6) is extracted. ).

Further, here, since it is determined whether or not there is a traffic jam between the entrance G1 and the exit G3 of the toll road 10, the determination unit 3012 adds the entrance G1 information of the exit G3 is entered in the arrival point of all vehicle information (FIG. 6). Further, the determination unit 3012 writes the vehicle detection time included in the vehicle information received from the roadside device 200c installed at the exit G3 as the vehicle detection time of all vehicle information (FIG. 6).

Further, the determining unit 3012 determines that the same vehicle identification information received from the roadside device 200a installed at the entrance G1 is based on the vehicle detection time included in the vehicle information received from the roadside device 200c installed at the exit G3. The time obtained by subtracting the vehicle detection time included in the vehicle information is described as the running time of all vehicle information (FIG. 6). The travel time is the time required for passing through the roadside device 200a installed at the entrance G1 and passing through the roadside device 200c installed at the exit G3.

Based on the all-vehicle information stored in the all-vehicle information storage unit 302 in step S302, the determination unit 3012 moves from the entrance G1, which is the departure point, to the exit G3, which is the destination, at predetermined time intervals (here, every five minutes). Calculate the average required time required to move to (step S303). Specifically, the determining unit 3012 determines that the starting point is the entrance G1 and the arrival point is the exit G3 in the all-vehicle information (FIG. 6), and the vehicle detection time is from the current time. , extracts information up to 5 minutes before the current time, totals the traveling times of the extracted information, and divides by the number of extracted information to calculate the average travel time.

Based on the average travel time calculated in step S303, the determination unit 3012 determines whether or not there is traffic congestion between the departure point entrance G1 and the arrival point exit G3 (step S304). ). Specifically, when the average required time calculated in step S303 is X minutes, the determination unit 3012 determines that the average required time X is , no traffic jam (less than 20 minutes), moderate traffic jam (20 minutes or more, less than 30 minutes), traffic jam (30 minutes or more, less than 60 minutes), severe traffic jam (60 minute or longer), the state of congestion between the entrance G1 and the exit G3 is determined.

The congestion information transmission unit 3014 transmits the congestion information (FIG. 5) generated in step S304 to the cloud server 400 via the communication interface 305 (step S305).

According to the first embodiment, the driver, who is about to drive on the toll road 10, uses his/her mobile phone to receive traffic congestion information updated at predetermined intervals from the cloud server 40 (FIG. 5). Based on the information obtained from the vehicle that actually traveled from the starting point to the destination point, it is possible to obtain approximately It can be known accurately in real time (here, every 5 minutes).

At present, traffic counters are installed every few kilometers along the expressway in order to determine the congestion situation on the expressway. . However, if the traffic congestion determination system 100 according to the first embodiment is used, there is no need to install a large number of traffic counters on the toll road 10, and the roadside devices 200a to 200d are connected to the entrance G1, tollgate G2, and exit G3 of the toll road 10. , and G4, it is possible to determine the congestion status of the toll road 10 without spending a lot of money.

<Second embodiment>
Next, a second embodiment will be described. Descriptions of portions of the congestion determination device according to the second embodiment that are the same as those of the congestion determination device 300a (FIG. 4) according to the first embodiment will be omitted. In the second embodiment, the roadside devices 200a to 200d include the vehicle identification information, the vehicle detection time, and the roadside device identification information included in the vehicle information Z1 shown in FIG. Send to

The vehicle type information indicates whether the vehicle detected by the roadside devices 200a to 200d belongs to any category of "compact/two-wheeled vehicle", "ordinary vehicle", "medium vehicle", "large vehicle", and "extra-large vehicle". The roadside devices 200a to 200d are mounted on vehicles passing through the entrance G1, toll gate G2, exits G3 and G4 of the toll road 10 on which they are installed (for example, a car navigation system). The vehicle type information is acquired by receiving the vehicle type information included in the signals exchanged when communicating with the charging devices provided at the entrance G1, the toll booth G2, and the exits G3 and G4.

FIG. 11 is a schematic block diagram showing the configuration of a congestion determination device 300b according to the second embodiment. A traffic congestion determination device 300b (FIG. 11) according to the second embodiment differs from the traffic congestion determination device 300a (FIG. 4) according to the first embodiment in that a vehicle type information acquisition unit 3020 is provided. The vehicle type information acquisition unit 3020 acquires vehicle type information included in the vehicle information transmitted from the roadside devices 200a to 200d.

The determination unit 3012 (FIG. 11) of the traffic congestion determination device 300b of the second embodiment also uses the vehicle type information acquired by the vehicle type information acquisition unit 3020 in the process of the traffic congestion determination device 300a shown in FIG. I do. Specifically, the determination unit 3012 (FIG. 11) of the second embodiment determines whether the section from the entrance G1, which is the departure point, to the exit G3, which is the destination, is congested for each category indicated by the vehicle type information. determine whether or not

In the second embodiment, traffic congestion information Z2 (FIG. 5) can be generated for each category specified by vehicle type information and transmitted to cloud server 400 (FIG. 1). Since the size and weight of vehicles differ greatly between ordinary vehicles and oversized vehicles, even when traveling in the same section (for example, the section from the entrance G1 to the exit G3 of the toll road 10), the travel time Differences may occur.

In the second embodiment, since the congestion status of the toll road 10 is determined for each vehicle type classification, the driver of the vehicle can acquire the traffic congestion information corresponding to the vehicle type classification of the vehicle to be driven. It is possible to accurately know how long it will take to move to the destination point, taking into account the vehicle type.

<Third Embodiment>
Next, a third embodiment will be described. Descriptions of portions of the congestion determination device according to the third embodiment that are the same as those of the congestion determination device 300a (FIG. 4) according to the first embodiment will be omitted.

FIG. 12 is a schematic block diagram showing the configuration of a congestion determination device 300c according to the third embodiment. A congestion determination device 300c (FIG. 12) according to the third embodiment differs from the congestion determination device 300a (FIG. 4) according to the first embodiment in that a congestion prediction unit 3030 is provided.

The congestion prediction unit 3030 of the third embodiment predicts congestion using the congestion information (FIG. 5) stored in the congestion information storage unit 304 (FIG. 12). Specifically, the congestion prediction unit 3030 extracts the congestion information (FIG. 5) stored in the congestion information storage unit 304 (FIG. 12) from a predetermined day of the week (eg, Sunday) and a predetermined time period (eg, , 17:00 to 20:00), in a predetermined section (for example, the section from the entrance G1 to the exit G3 of the toll road 10), if it is determined that traffic congestion will occur, it means that many traffic congestions have occurred so far. It transmits to the cloud server 400 the day of the week, the time period, and the section.

According to the third embodiment, future traffic jams are predicted based on past traffic jams based on information about vehicles that have actually traveled a predetermined section of the toll road 10, so more accurate traffic jam prediction is performed. be able to.

<Fourth Embodiment>
Next, a fourth embodiment will be described. Descriptions of portions of the congestion determination device according to the fourth embodiment that are the same as those of the congestion determination device 300a (FIG. 4) according to the first embodiment will be omitted.

FIG. 13 is a schematic block diagram showing the configuration of a congestion determination device 300d according to the fourth embodiment. A traffic congestion determination device 300d (FIG. 13) according to the fourth embodiment differs from the traffic congestion determination device 300a (FIG. 4) according to the first embodiment in that it includes a recommended information notification unit 3040. FIG.

The recommended information notification unit 3040 of the fourth embodiment uses the traffic congestion information (FIG. 5) stored in the traffic congestion information storage unit 304 (FIG. 13) to to notify recommended information. Specifically, the recommended information notifying unit 3040 refers to the traffic congestion information (FIG. 5) to determine whether a person is likely to experience traffic congestion at the same time on weekdays (for example, 7:00 to 8:00). When traveling on the same section of the toll road 10 that is not open (for example, the section from the entrance G1 to the exit G3 of the toll road 10), at 6:30 on weekdays, if there is a traffic jam, Messages are sent to people's mobile devices, such as "You shouldn't use the expressway because there's been traffic jams since the morning," or "Why don't you come to work at a different time (staggered commuting)?" Send a message.

According to the fourth embodiment, it is possible to notify each user of recommended information for avoiding traffic jams occurring on the toll road 10 based on the usage history of the toll road 10 by each user. Therefore, it is possible to reduce the probability that the user will be caught in a traffic jam on the toll road 10.例文帳に追加

<Fifth Embodiment>
Next, a fifth embodiment will be described. Descriptions of portions of the congestion determination device according to the fifth embodiment that are the same as the congestion determination device 300a (FIG. 4) according to the first embodiment will be omitted. In the fifth embodiment, the roadside devices 200a to 200d include the vehicle identification information, the vehicle detection time, and the roadside device identification information included in the vehicle information Z1 shown in FIG. Send to When the vehicle passes through the entrance G1, the toll gate G2, the exits G3 and G4 of the toll road 10, the toll information is collected by the driver of the vehicle through an electronic toll collection system (ETC). (Registered Trademark), also known as an "automatic toll collection system") or in cash.

FIG. 14 is a schematic block diagram showing the configuration of a congestion determination device 300e according to the fifth embodiment. A congestion determination device 300e (FIG. 14) according to the fifth embodiment differs from the congestion determination device 300a (FIG. 4) according to the first embodiment in that a toll information acquisition unit 3050 is provided. The toll information acquisition unit 3050 acquires toll information included in the vehicle information transmitted from the roadside devices 200a to 200d.

The determination unit 3012 (FIG. 14) of the toll information acquisition unit 3050 of the fifth embodiment also uses toll information acquired by the vehicle type information acquisition unit 3020 in the processing of the congestion determination device 300a shown in FIG. make a judgment. Specifically, the determination unit 3012 (FIG. 14) of the fifth embodiment determines whether the section from the entrance G1, which is the departure point, to the exit G3, which is the destination, is congested for each section indicated by the toll information. determine whether or not

In the fifth embodiment, traffic congestion information Z2 (FIG. 5) can be generated and transmitted to cloud server 400 (FIG. 1) for each section specified by toll information. Paying tolls in cash requires interaction with toll booth staff, and thus requires more money to travel the toll road 10 than paying tolls with an electronic toll collection system. It takes time.

In the fifth embodiment, since the congestion status of the toll road 10 is determined for each toll information, the driver of the vehicle can acquire the congestion status information corresponding to the payment method of the toll, and can obtain the congestion status information from the departure point to the destination. It is possible to accurately know how long it will take to move to a point, taking into consideration the payment method of the toll.

<Sixth Embodiment>
Next, a sixth embodiment will be described. Descriptions of portions of the congestion determination device according to the sixth embodiment that are the same as those of the congestion determination device 300a (FIG. 4) according to the first embodiment will be omitted.

FIG. 15 is a schematic block diagram showing the configuration of a congestion determination device 300f according to the sixth embodiment. A congestion determination device 300f (FIG. 15) according to the sixth embodiment differs from the congestion determination device 300a (FIG. 4) according to the first embodiment in that a discount information notification unit 3060 is provided.

The discount information notification unit 3060 of the sixth embodiment uses the traffic congestion information (FIG. 5) stored in the traffic congestion information storage unit 304 (FIG. 15) to to notify the discount information. Specifically, the discount information notification unit 3060 calculates the speed of the vehicle traveling from the entrance G1 to the exit G3 of the toll road 10 by referring to the traffic congestion information (FIG. 5). If the speed is within the range of 90% to 100% of the legal speed limit, the mobile terminal or the like held by the driver of the vehicle is notified of coupon information for discounting the toll.

According to the sixth embodiment, it is possible to identify a vehicle that has traveled a predetermined section of a toll road without exceeding the legal speed limit. By notifying discount information for discounting tolls, it can be expected that the number of vehicles traveling at the legal speed limit will increase.

<Seventh Embodiment>
Next, a seventh embodiment will be described. Descriptions of portions of the congestion determination device according to the seventh embodiment that are the same as those of the congestion determination device 300a (FIG. 4) according to the first embodiment will be omitted.

FIG. 16 is a schematic block diagram showing the configuration of a congestion determination device 300g according to the seventh embodiment. A congestion determination device 300g (FIG. 16) according to the seventh embodiment differs from the congestion determination device 300a (FIG. 4) according to the first embodiment in that a vehicle notification unit 3070 is provided.

The vehicle notification unit 3070 of the seventh embodiment uses the traffic congestion information (FIG. 5) stored in the traffic congestion information storage unit 304 (FIG. 16) to send information to a portable terminal held by the driver of the vehicle. In response, the warning information is notified. Specifically, the discount information notification unit 3060 calculates the speed of the vehicle traveling from the entrance G1 to the exit G3 of the toll road 10 by referring to the traffic congestion information (FIG. 5). If the speed exceeds 120% of the legal speed limit, a warning message is sent to the mobile terminal or the like held by the driver of the vehicle to warn that the speed limit was exceeded. Here, the case where the warning information is notified to the driver who drives at an excessive speed has been described, but the notification is not limited to this, and may be reported to the police or the like.

According to the seventh embodiment, it is possible to identify a vehicle that has traveled a predetermined section of a toll road in excess of the legal speed limit, and to notify a driver who has driven at an excessive speed with warning information. Therefore, it can be expected that the number of vehicles that follow the legal speed limit will increase.

In the above-described first to seventh embodiments, the vehicle identification information for identifying the vehicles C1 and C2 is described as information written on the license plates attached to the vehicles C1 and C2, but is limited to this. not to be For example, as the vehicle identification information, information described on the license plate, on-board equipment identification information for identifying the on-board equipment mounted on the vehicles C1 and C2, the card number of the credit card inserted in the on-board equipment, the vehicle body or a captured image of the driver's face, or a combination thereof may be used as the vehicle identification information.

4 and 11 to 16, a program for realizing the function of each unit of the traffic jam determination devices 300a to 300g is recorded in a computer-readable recording medium, and the program recorded in the recording medium is transferred to a computer system. 4, 11 to 16 may be performed by loading and executing the program. It should be noted that the "computer system" referred to here includes hardware such as an OS and peripheral devices. Also, the "computer system" includes a WWW system provided with a home page providing environment (or display environment). The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. In addition, "computer-readable recording medium" means a volatile memory (RAM) inside a computer system that acts as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. , includes those that hold the program for a certain period of time.

<Appendix>
The congestion determination devices 300a to 300g described in each embodiment are grasped as follows, for example.

(1) The traffic congestion determination device 300a according to the first aspect is a vehicle capable of identifying each of the plurality of vehicles C1 traveling on the toll road 10 from each of the plurality of roadside devices 200a to 200d installed on the toll road 10. A vehicle identification information acquisition unit 3011 that acquires identification information, and a determination unit 3012 that determines whether or not there is congestion on the toll road 10 based on the vehicle identification information acquired by the vehicle identification information acquisition unit 3011. .

(2) In the traffic congestion determination device 300a according to the second aspect, the vehicle identification information acquisition unit 3011 obtains, as vehicle identification information, license plate information of a plurality of vehicles C1 and C2 traveling on the toll road 10, vehicle-mounted device identification information, card Acquire at least one of the number and the captured image.

(3) In the congestion determination device 300a according to the third aspect, the determination unit 3012 collates the vehicle identification information acquired from the plurality of roadside devices 200a to 200d.

(4) In the traffic congestion determination device 300a according to the fourth aspect, the determination unit 3012 determines whether the plurality of vehicles C1 and C2 are detected based on the time when the plurality of vehicles C1 and C2 pass through the plurality of roadside devices 200a to 200d. The travel time required to pass through the roadside devices 200a to 200d is calculated, and it is determined whether or not traffic congestion occurs based on the calculated travel time.

(5) In the traffic jam determination device 300a according to the fifth aspect, the determination unit 3012 determines, based on the vehicle identification information acquired by the vehicle identification information acquisition unit 3011, when the plurality of vehicles C1 and C2 are traveling on the toll road 10. The average required time is calculated, and based on the calculated average required time, it is determined whether or not there is a traffic jam.

(6) In the congestion determination device 300a according to the sixth aspect, the plurality of roadside devices 200a to 200d are connected to the entrance G1 of the toll road 10, the exits G3 and G4 of the toll road 10, and between the entrance G1 and the exits G3 and G4. and a toll gate G2 provided in .

(7) In the traffic jam determination device 300b according to the seventh aspect, the vehicle identification information acquisition unit 3011 further includes a vehicle type information acquisition unit 3020 that acquires vehicle type information for determining the vehicle types of the plurality of vehicles C1 and C2.

(8) The congestion determination device 300c according to the eighth aspect further includes a congestion prediction section 3030 that predicts congestion that will occur on the toll road 10 based on the determination result of the determination section 3012 .

(9) The traffic congestion determination device 300d according to the ninth aspect further includes a recommended information notification unit 3040 that notifies recommended information for avoiding traffic congestion based on the determination result of the determination unit 3012 .

(10) The congestion determination device 300e according to the tenth aspect further acquires information on the payment method of the toll required for the plurality of vehicles C1 and C2 to travel between the plurality of roadside devices 200a to 200d. An information acquisition unit 3050 is further provided.

(11) The traffic jam determination device 300e according to the eleventh aspect calculates the speed when the plurality of vehicles C1 and C2 pass through the toll road 10 based on the vehicle identification information acquired by the vehicle identification information acquisition unit 3011, It further includes a discount information notification unit 3060 that notifies discount information for discounting the toll necessary for the plurality of vehicles C1 and C2 to travel between the plurality of roadside devices 200a to 200d based on the calculated speed.

(12) The traffic jam determination device 300f according to the twelfth aspect calculates the speed when the plurality of vehicles C1 and C2 pass through the toll road 10 based on the vehicle identification information acquired by the vehicle identification information acquisition unit 3011, A vehicle notification unit 3070 is further provided for notifying a vehicle whose calculated speed satisfies a predetermined condition.

(13) The traffic jam determination method according to the thirteenth aspect is a vehicle capable of identifying each of the plurality of vehicles C1 and C2 traveling on the toll road 10 from each of the plurality of roadside devices 200a to 200d installed on the toll road 10. A vehicle identification information acquisition step S301 for acquiring identification information, and a determination step S304 for determining whether or not there is congestion on the toll road 10 based on the vehicle identification information acquired in the vehicle identification information acquisition step S301. .

(14) The program according to the fourteenth aspect is configured to cause the computer of the traffic congestion determination device 300a to transmit the plurality of vehicles C1 and C2 traveling on the toll road 10 from each of the plurality of roadside devices 200a to 200d installed on the toll road 10. A vehicle identification information acquisition step S301 for acquiring vehicle identification information capable of identifying each vehicle, and a determination to determine whether or not there is congestion on the toll road 10 based on the vehicle identification information acquired in the vehicle identification information acquisition step S301. Step S304 and are executed.

100 traffic congestion determination system 200a, 200b, 200c, 200d roadside device 201 control unit 202 sensor 203 imaging unit 204 clock 205 detection time storage unit 206 communication interface 300a to 300g traffic congestion determination device 300
301 control unit 301
302 All vehicle information storage unit 303 Congestion judgment information storage unit 304 Congestion condition information storage unit 305 Communication interface 400 Cloud server 2011 Vehicle detection unit 2012 Vehicle information generation unit 2013 Vehicle information transmission unit 3011 Vehicle identification information acquisition unit 3012 Judgment unit 3013 Congestion condition Information generation unit 3014 Congestion status information transmission unit 3020 Vehicle type information acquisition unit 3030 Congestion prediction unit 3040 Recommended information notification unit 3050 Toll information acquisition unit 3060 Discount information notification unit 3070 Vehicle notification unit

Claims (14)

a vehicle identification information acquisition unit configured to acquire vehicle identification information capable of identifying each of a plurality of vehicles traveling on the toll road from each of a plurality of roadside devices installed on the toll road;
a determination unit that determines whether or not there is congestion on the toll road based on the vehicle identification information acquired by the vehicle identification information acquisition unit;
Traffic congestion determination device. The vehicle identification information acquisition unit acquires at least one of license plate information, vehicle-mounted device identification information, card numbers, and captured images of a plurality of vehicles traveling on the toll road as the vehicle identification information.
The congestion determination device according to claim 1. The determination unit collates the vehicle identification information acquired from the plurality of roadside devices.
3. The traffic jam determination device according to claim 1 or 2. The determining unit calculates the travel time required for the plurality of vehicles to pass through the plurality of roadside devices based on the time when the plurality of vehicles passed through the plurality of roadside devices, and calculates Determining whether traffic congestion is occurring based on the travel time obtained,
The congestion determination device according to any one of claims 1 to 3. The determination unit calculates an average required time required for the plurality of vehicles to travel on the toll road based on the vehicle identification information acquired by the vehicle identification information acquisition unit, and calculates the calculated average required time 5. The traffic jam determination device according to any one of claims 1 to 4, wherein it is determined whether or not the traffic jam occurs based on. The plurality of roadside devices are provided at an entrance of the toll road, an exit of the toll road, and a toll booth provided between the entrance and the exit.
The congestion determination device according to any one of claims 1 to 5. The vehicle identification information acquisition unit further includes a vehicle type information acquisition unit that acquires vehicle type information for determining the vehicle type of the plurality of vehicles,
The congestion determination device according to any one of claims 1 to 6. Further comprising a congestion prediction unit that predicts the congestion that will occur on the toll road based on the determination result of the determination unit;
The congestion determination device according to any one of claims 1 to 7. Further comprising a recommended information notification unit that notifies recommended information for avoiding the congestion based on the determination result of the determination unit,
The congestion determination device according to any one of claims 1 to 8. The vehicle further comprises a toll information acquisition unit that further acquires toll payment method information required when the plurality of vehicles travel between the plurality of roadside devices,
The congestion determination device according to any one of claims 1 to 9. Based on the vehicle identification information acquired by the vehicle identification information acquisition unit, the speed when the plurality of vehicles pass through the toll road is calculated, and based on the calculated speed, the plurality of vehicles Further comprising a discount information notification unit that notifies discount information for discounting the toll required when traveling between a plurality of roadside devices,
The congestion determination device according to any one of claims 1 to 10. Based on the vehicle identification information acquired by the vehicle identification information acquisition unit, the speeds of the plurality of vehicles traveling on the toll road are calculated, and the vehicle that satisfies a predetermined condition for the calculated speed is notified of the vehicle. further comprising a notification unit;
The congestion determination device according to any one of claims 1 to 10. a vehicle identification information acquiring step of acquiring vehicle identification information capable of identifying each of a plurality of vehicles traveling on the toll road from each of a plurality of roadside devices installed on the toll road;
a determination step of determining whether or not the toll road is congested based on the vehicle identification information obtained in the vehicle identification information obtaining step;
Congestion judgment method having. In the computer of the traffic jam judgment device,
a vehicle identification information acquiring step of acquiring vehicle identification information capable of identifying each of a plurality of vehicles traveling on the toll road from each of a plurality of roadside devices installed on the toll road;
a determination step of determining whether or not the toll road is congested based on the vehicle identification information obtained in the vehicle identification information obtaining step;
program to run.

Images