WO2003107302A1 - ビーコンを用いたfcdシステムと装置 - Google Patents
ビーコンを用いたfcdシステムと装置 Download PDFInfo
- Publication number
- WO2003107302A1 WO2003107302A1 PCT/JP2003/007284 JP0307284W WO03107302A1 WO 2003107302 A1 WO2003107302 A1 WO 2003107302A1 JP 0307284 W JP0307284 W JP 0307284W WO 03107302 A1 WO03107302 A1 WO 03107302A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- vehicle
- beacon
- fcd
- travel
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/052—Detecting movement of traffic to be counted or controlled with provision for determining speed or overspeed
Definitions
- the present invention relates to a car data (FCD) system and a device for collecting data indicating a driving state from a vehicle and using the data for traffic information, and more particularly to a data collection through a beacon. It is. Background technology>
- the introduction of a system called a probe car (or floating car) that uses vehicles as sensors for collecting traffic information has been considered.
- the on-board FCD onboard the vehicle records data such as the running speed and position of the vehicle and sends it to the center, which analyzes the running locus data sent from each vehicle. Generate road traffic information on traffic flow and the like.
- beacons are installed on the road and provide VICS road traffic information to passing vehicles in a pinpoint manner.
- the beacon can perform two-way communication with the onboard equipment (data transfer rate l Mbps).
- optical beacons are collecting the following information using two-way communication.
- the distance between the beacons varies depending on the installation conditions, etc., but is about several hundred meters to several kilometers.
- the beacon 10 transmits the “beacon number” of the beacon 10 to the on-vehicle device, and the on-vehicle device stores this beacon number.
- the beacon 20 transmits the “beacon number” of the beacon 20 to the in-vehicle device, and the in-vehicle device stores this beacon number.
- optical beacons In this way, it is possible to collect travel time between beacons using optical beacons.
- the collection of travel time by optical beacons has the following problems.
- the present invention solves such a conventional problem, and provides an FCD system that can efficiently collect vehicle trajectory data by utilizing the characteristics of beacons and analyze detailed traffic conditions. It is also intended to provide a device that constitutes the system.
- the traveling locus data is collected from the in-vehicle device of the vehicle using the beacon.
- the downstream beacon collects travel trajectory data, calculates the travel distance of the vehicle from the upstream beacon to the downstream beacon based on the travel trajectory data, and calculates the travel distance and the upstream beacon from the downstream beacon. It is configured to compare the distance of the target road to the downstream beacon and determine whether or not to use the travel locus data of the vehicle for analyzing the traffic condition of the target road.
- the downstream beacon collects the traveling locus data, identifies the passing road section of the vehicle from the upstream beacon to the downstream beacon using the position data included in the traveling locus data, and includes the traveling locus data in the traveling locus data.
- the speed data measurement points in the passing road section are complemented and specified using the speed data obtained.
- the traveling locus data is collected by a downstream beacon, and the vehicle from the upstream beacon to the downstream beacon is collected based on the traveling locus data.
- the travel distance of the vehicle is compared with the distance of the target road from the upstream beacon to the downstream beacon, and the travel locus data of the vehicle is used for analyzing the traffic condition of the target road. It is configured to determine whether or not it is not.
- the traveling locus data is collected by the downstream beacon, and the passing road section from the upstream beacon to the downstream beacon is specified using the position data included in the traveling locus data.
- the speed data measurement points in the passage section are complemented and specified using the included speed data.
- the traveling locus data measured after passing through the upstream beacon is encoded and transmitted to the downstream beacon.
- FIG. 1 is a diagram showing a data transmission form in the FCD system according to the first embodiment of the present invention.
- FIG. 2 is a diagram illustrating a data structure of transmission data according to the first embodiment of the present invention.
- FIG. 3 is a diagram illustrating a data transmission form in the FCD system according to the second embodiment of the present invention.
- FIG. 4 is a block diagram showing a data structure of transmission data according to the third embodiment of the present invention.
- FIG. 5 is a diagram showing a configuration of the FCD system according to the third embodiment of the present invention.
- FIG. 6 is a diagram illustrating a data transmission form in the FCD system according to the fourth embodiment of the present invention.
- FIG. 7 is a diagram showing a data structure of encoding instruction data according to the fourth embodiment of the present invention.
- FIG. 8 is a diagram showing a quantization table used in the fourth embodiment of the present invention.
- FIG. 9 is a diagram showing a code table used in the fourth embodiment of the present invention.
- FIG. 10 is a diagram showing a data structure of travel locus data according to the fourth embodiment of the present invention.
- FIG. 11 is a block diagram showing a configuration of the FCD system according to the fourth embodiment of the present invention.
- FIG. 12 is a flow chart showing a procedure for generating encoding instruction data according to the fourth embodiment of the present invention.
- FIG. 13 is a flowchart showing an operation procedure of the FCD system according to the fourth embodiment of the present invention.
- FIG. 14 is a diagram illustrating a first configuration of the FCD system according to the fifth embodiment of the present invention.
- FIG. 15 is a diagram showing a second configuration of the FCD system according to the fifth embodiment of the present invention.
- FIG. 16 is a flowchart showing an operation procedure of the FCD system according to the fifth embodiment of the present invention.
- FIG. 17 is an explanatory diagram showing information collection using a conventional beacon.
- FIG. 18 is an explanatory diagram showing the problem of information collection by a conventional beacon. The symbols in the figure are as follows.
- the in-vehicle device measures “average speed” or “passing time” for each unit section in units of a certain distance, and uploads the measured data to a downstream beacon.
- upstream beacons 10 and downstream beacons 20 are installed in the target road section where traffic information is collected, and the distance between the beacons in the target road section is known. is there.
- the upstream beacon 10 uploads its own beacon number and the sampling interval of data measurement to the FCD vehicle of the passing vehicle.
- the upstream beacon 10 specifies the distance (for example, 150 m) of the unit section for measuring the average speed as the sampling interval.
- the space between the white circles is represented as a unit space.
- the in-vehicle unit averages the speed of the unit section every time it travels the specified distance (150 m).
- the traveling locus data including the recorded average speed information of each unit section and the beacon number of the upstream beacon 10 that passed last time is uploaded to the downstream beacon 20.
- the travel locus data sent from the on-board FCD to the downstream beacon 20 includes "the number of the last beacon passed", “sampling distance interval", "the last measurement point and the beacon gap point”.
- Offset distance distance between the final measurement point of speed (15 Om pitch) and the uploading point to the downstream beacon 20 (fraction less than 150 m)
- “Number of sampling points for speed information” Average speed per unit section ” is included. If there is sufficient transmission path capacity, “traveling distance from the last beacon passed” may be included in the traveling locus data. However, even if this is not included, the downstream beacon 20 will be calculated based on the “speed sampling distance interval”, “number of speed information sampling points”, and The distance traveled from the beacon that has been completed "can be calculated.
- the distance between the beacons in the target road section is known for the downstream beacon 20 or the center device connected to it.
- the distance and the "travel distance from the previous beacon" obtained from the travel locus data are calculated.
- the average speed of each unit section in the travel trajectory data of each vehicle is compared, and it is determined that the vehicle has stopped in the section where the average speed is abnormally slower than other sections.
- the remaining travel trajectory data excluding these data is statistically analyzed, and the density of traffic congestion in the target road section is analyzed from the average speed of each unit section.
- this system can accurately identify vehicles that have passed a detour or stopped vehicles. It is possible to accurately and in detail analyze the traffic condition of the target road section by excluding these data.
- the in-vehicle device may measure the “passing time” required for passing through the unit section instead of measuring the average speed in the unit section. The reason is that the downstream beacon 20 or the center device connected to the downstream beacon 20 can calculate the average speed of the unit section using the “passing time” and the “speed sampling distance interval”.
- the speed may be measured each time the vehicle travels in each unit section, and this speed may be included in the traveling locus data.
- 15 Om is exemplified as the “speed sampling distance interval”, but it may be set to about 50 to 30 Om.
- This sampling distance interval is shorter in urban areas where the distance between beacons is shorter, and longer in mountainous areas where the distance between beacons is longer. They can be collected and the beacon transmits the sampling interval instruction information to the vehicle, so that the unit section can be set according to the installation status of the beacon.
- the on-board machine may identify the traveling area and determine the sampling interval by itself.
- the download data in Fig. 2 (a) includes only the beacon number.
- the on-vehicle device measures “average speed” or “moving distance” per unit time in units of a fixed time, and uploads the measured data to a downstream beacon.
- the upstream beacon 10 sends its own beacon number and the unit time (approximately 2 to 30 seconds) as a sampling interval to the on-board FCD of the passing vehicle. to download.
- the onboard unit records the average speed every time the specified unit time elapses, and when it comes to the position of the downstream beacon 20, the "beacon number passed last time”, “speed sampling time interval”, “final measurement” Offset distance between point and beacon up point "Speed information
- the trajectory data including the data of “3/07284 sampling points” and “average speed per unit time” is uploaded to the downstream beacon 20.
- the downstream beacon 20 adds the “offset distance between the final measurement point and the beacon up point” to the cumulative value of (“speed sampling time interval” x “average speed per unit time”). By adding them, the “distance traveled since the last beacon passed” can be calculated.
- the downstream beacon 20 or the center device connected to the downstream beacon 20 includes the distance between the beacons in the target road section and the ⁇ travel distance from the last beacon passed through '' obtained from the travel locus data. Are compared to determine the vehicle that has passed through the detour, and the travel trajectory data of the relevant vehicle is excluded from the material for determining the traffic condition of the target road section.
- the average speed of each vehicle in the travel trajectory data for each unit time is compared, and in a section where the average speed is abnormally slower than other unit times, it is determined that the vehicle has stopped, and the data is determined. Is excluded from the material for judging the traffic condition of the target road section.
- the remaining trajectory data excluding these data is statistically analyzed, and from the average speed of each unit time, the density of traffic congestion in the target road section is analyzed.
- the “speed sampling time interval” can be changed as in the first embodiment.
- a method for reducing the data amount of the average speed, transit time, or travel distance data uploaded from the on-vehicle device to the beacon will be described.
- speed information is taken as an example.
- the amount of data is reduced by converting the speed information into statistically biased data and performing variable-length coding on the converted data using a code table. This technique is described in detail in Japanese Patent Application No. 2001-329242 previously proposed by the inventor of the present invention.
- the measured value is expressed as the difference from the previous measured value. In this way, when the vehicle passes through the target road section at a substantially uniform speed, the differential speed data concentrates around zero.
- the code table a small bit value is assigned to differential speed data having a high occurrence frequency near ⁇ 0, and a large bit value is assigned to the differential speed data having a low occurrence frequency. Then, the data amount can be reduced by performing variable length coding on the differential speed data using this code table. Also, at this time, the data amount can be further reduced by applying run-length coding to the same continuous value contained therein and performing run length compression.
- the velocity data is quantized before the velocity data is expressed as a difference, and the quantized value is expressed as a difference, the data amount can be further reduced.
- this speed data since it is necessary to grasp the traffic congestion state in detail at the center, it is finely quantized at a low speed and coarsely quantized as the speed increases.
- the upstream beacon or the center device connected to it downloads the encoding method, the quantization unit of speed information, and the code table to the in-vehicle device, and the in-vehicle device performs measurement.
- the speed data thus encoded is encoded by the specified encoding method and uploaded to the downstream beacon.
- Fig. 4 (a) shows the data downloaded from the upstream beacon 10 in this case
- Fig. 4 (b) shows the data structure of the data uploaded by the onboard unit to the downstream beacon 20 .
- Fig. 4 (a) contains the coding instruction data specifying the sampling interval, the quantization unit and the code table.
- Fig. 4 (b) shows the data obtained by coding the speed difference and the speed. The absolute speed of the final measurement point required to convert the difference into speed data is included.
- FIG. 5 is a block diagram showing the configuration of this system including an upstream beacon (or a center device connected thereto) 10, a downstream beacon (or a center device connected thereto) 20, and an FCD vehicle 50. I have.
- the upstream beacon (or the center device connected to it) 10 includes a traffic condition determination unit 11 that determines traffic conditions, and coding instruction data (sampling interval, quantization) according to various traffic conditions based on past travel locus data.
- An encoding instruction creating unit 12 for creating a unit and a code table), and an encoding instruction selecting unit 13 for downloading selected encoding instruction data to the in-vehicle device 50 of a passing vehicle.
- the traffic condition determination unit 11 includes a sensor processing unit 111 that processes sensor information of the traffic sensor 14 including the FCD, and a traffic condition determination unit 112 that determines a traffic condition from information of the traffic sensor.
- the encoding instruction creating unit 12 encodes the encoding instruction data (sampling interval, quantum interval) that can efficiently encode the speed data in the traffic situation of each pattern using the past traveling locus data 123 divided into traffic situation patterns.
- a code table calculating unit 121 for calculating the coding unit (code table) 122 is provided.
- the encoding instruction selecting unit 13 includes an encoding instruction selecting unit 131 that selects the encoding instruction data 122 according to the traffic condition determined by the traffic condition determining unit 112, and a beacon number management data.
- a beacon number / encoding instruction transmitting unit 133 that downloads the beacon number and the selected encoding instruction data managed by the data 134 to the on-board FCD device 50.
- the FCD on-board unit 50 also includes a data reception unit 51 that receives the encoding instruction data 52 from the upstream beacon 10, a default encoding instruction data 53 that the FCD on-board unit 50 holds in advance, and a speed sensor 60 detection.
- a running locus transmitting unit 57 for transmitting to the beacon 20 is provided.
- a downstream beacon (or a center device connected thereto) 20 includes a traveling locus receiving unit 21 for receiving traveling locus data from the FCD vehicle-mounted device 50 and a beacon indicating an installation position of the upstream beacon 10 and the downstream beacon 20.
- Installation position data 22 an encoded data decoding unit 24 for decoding the encoded traveling locus data, and a traveling route / stop for excluding traveling locus data of vehicles that have traveled or stopped outside the target road section.
- the vehicle includes a vehicle determination unit 26 and a traveling locus information utilization unit 25 that utilizes traveling locus data for analysis of traffic flow and the like.
- the functions of the respective components of the upstream beacon 10, the downstream beacon 20, and the on-board FCD device 50 can be realized by causing a computer incorporated in these devices to perform processing specified by a program.
- the traffic condition determination unit 11 of the upstream beacon 10 determines the traffic condition based on the sensor information of the traffic sensor 14 including the FCD, and transmits it to the coding instruction creation unit 12 and the coding instruction selection unit 13. I do.
- the encoding instruction creating unit 12 divides the past traveling locus data 123 into patterns according to the traffic situation transmitted from the traffic situation judging unit 11 at that time. Create encoding instruction data (sampling interval, quantization unit, code table) 122 for encoding speed data in traffic conditions.
- the encoding instruction selecting unit 13 matches the current traffic condition determined by the traffic condition determining unit 112 from the encoding instruction data 122 created in advance by the encoding instruction creating unit 12. 07284, and downloads it along with the beacon number to the FCD vehicle 50 of the passing vehicle.
- the selected encoding instruction data 122 is also transmitted to the downstream beacon 20.
- the FCD on-board unit 50 Upon receiving the beacon number and the encoded instruction data 52 from the upstream beacon 10, the FCD on-board unit 50 stores them, collects the speed data of the traveling vehicle detected by the speed sensor 60, and stores the traveling locus storage unit 54. To accumulate. Then, when it passes under the downstream-side beacon 20, the velocity data stored in the traveling locus accumulating portion 5 4, and coded using a coding instruction data 52 is uploaded to the downstream-side beacon 20. If no encoding instruction data is received from the upstream beacon 10, this encoding is performed using the default encoding instruction data 53.
- the downstream beacon 20 that has received the travel trajectory data decodes the encoded travel trajectory data using the code table notified from the upstream beacon 10 and obtains the The distance traveled after passing the upstream beacon 10 '' and the distance between the beacons managed by the beacon installation position data 22 are compared to determine whether the vehicle equipped with this FCD on-board device 50 has passed the target road section. Determine if you have passed the road. Travel trajectory data collected from vehicles that have passed the detour is excluded from the material used to determine the traffic situation in the target road section.
- the speed data of each unit section of the travel trajectory data is compared to identify the section where the vehicle has stopped, and the data of that section is also excluded from the material for judging the traffic condition of the target road section.
- the remaining data will be used to analyze traffic conditions in the target road section and use it for traffic information.
- the traveling locus data by encoding the traveling locus data, the amount of data to be uploaded from the on-board FCD device 50 to the downstream beacon 20 can be reduced, and the vehicle can pass under the downstream beacon 20 in a short time. Therefore, it is possible to transmit the traveling locus data without any trouble.
- the on-board FCD measures the position data along with the speed data Hire 84
- the FCD on-board unit measures the position information at the double circle point, and measures the speed information more densely than the position information at the double circle and white circle points.
- the FCD on-board unit uploads these measurement data to the downstream beacon 20 when passing below the downstream beacon 20.
- the downstream beacon 20 (or the center device connected to it) performs map matching using the intermittent position information included in the received travel trajectory data, and specifies the road on which the vehicle has passed. Then, the distance between the positions on the road is supplemented by using the speed information, the measurement point of the speed information and the speed at the point are specified, and the congestion state of the road is determined.
- position data has the disadvantage that the amount of information is larger than that of velocity data. Even if the position information is expressed in 3 m units (resolution is 3 m), for example, about 32 bits are required to represent the trajectory position. On the other hand, the speed information of a vehicle does not usually exceed 256 Km / h, so that it can be displayed in 8 bits, and the amount of information is relatively light.
- the number of position information is limited to a level that can provide sufficient position identification accuracy (the road correct answer rate by map matching). Completion can reduce the amount of travel trajectory data sent from the on-board FCD, and the beacon can obtain detailed information indicating the travel status.
- the measurement of the FCD car machine 50 is performed every time a fixed time elapses (fixed period method) or every time the vehicle travels a fixed distance (fixed distance interval method).
- PC Rank 84 In the case of the fixed period method, position information is measured at a long period (for example, 15 seconds to 60 seconds), and speed information is measured at a short period (for example, 2 seconds to 5 seconds).
- the fixed distance interval method In the case of the fixed distance interval method, the position information is measured every time a long distance (for example, 20 m) is moved, and the speed information is measured every time a short distance (for example, 20 m) is moved.
- the position information of each measurement point is represented by the distance L from the adjacent measurement point and the declination 0.
- the distance L is represented by the difference ⁇ L from the distance data of the adjacent position measurement point
- the declination ⁇ is expressed as a difference ⁇ ⁇ (or ⁇ as it is) from the declination of the adjacent position measurement point.
- a L 0, and the position can be represented only by the argument difference ⁇ ⁇ (or argument ⁇ ).
- the speed information V is represented by the speed difference A V from the speed at the adjacent speed measurement point.
- the data volume of these data will be further reduced by applying variable length coding and run length compression.
- the position information is represented by the distance L from the adjacent position measurement point or the declination ⁇
- the absolute position of the final point or the start point is converted to convert the position information into the absolute position information.
- the positions of the beacons are known, so there is no need for the FCD vehicles to upload absolute position information to the beacons. Therefore, it is possible to reduce the data amount of 32 bit X 2 + 9 to 8 bit by this amount alone.
- Figure 6 shows the measured data at the position measurement point (double circle) and the speed measurement point (white circle + double circle) in the case of the fixed period method. L becomes unnecessary.
- FIG. 7 shows an example of the encoding instruction data downloaded by the upstream beacon 10 to the on-board FCD.
- FIG. 10 shows data uploaded from the on-board FCD to the downstream beacon 20.
- the ID information of the vehicle equipped with the on-board FCD device the instruction number of the encoding method included in the encoding instruction data, the number of measurement points of 0, the encoded data of declination ⁇ , the speed of the final measurement position , ⁇ , the number of measurement points, and encoded data of the speed difference.
- FIG. 11 shows the configuration of this system in a block diagram.
- the configuration of the upstream beacon (or the center device connected thereto) 10 is substantially the same as that of the third embodiment (FIG. 5).
- the FCD on-board unit 50 includes an encoding instruction receiving unit 51 that receives the encoding instruction data 52 from the upstream beacon 10, a default encoding instruction data 53 previously held by the FCD on-board unit 50, a GPS antenna 58, The vehicle position determination unit 55 that measures the vehicle position using the jay mouth 59, the traveling locus storage unit 54 that accumulates measurement data of the vehicle position and the detection data of the speed sensor 60, and the traveling locus storage unit 54 An encoding processing unit 56 that encodes the accumulated measurement data using the encoding instruction data 52 or 53 and a traveling trajectory transmitting unit 57 that transmits traveling trajectory data to the downstream beacon 20 are provided.
- the downstream beacon (or a center device connected thereto) 20 includes a traveling locus receiving unit 21 that receives traveling locus data from the FCD on-board device 50 and a beacon indicating the installation positions of the upstream beacon 10 and the downstream beacon 20.
- Installation position data 22 a beacon information adding unit 23 for adding beacon position information to the traveling locus data
- an encoded data decoding unit 24 for decoding encoded traveling locus data
- a decrypted traveling locus A running locus information utilization unit 2 ⁇ that uses data for traffic flow analysis and the like is provided.
- FIG. 12 shows a processing procedure of the encoding instruction creation unit 12 of the center device (FCD collection device) 10 to which the upstream beacon is connected.
- the past trajectory and typical traffic conditions around the beacon N are collected (step 2), and the position is determined from the occurrence status of mismatching and the amount of information.
- the information sampling distance interval L is determined (step 3).
- the quantization unit of the speed information is determined from the traffic conditions and the amount of information (step 4).
- the sampling distance interval of the speed information is determined from the information amount (step 5).
- ⁇ ⁇ of each section is calculated, and the distribution of ⁇ ”is calculated to create a code table (step 6).
- AVi is calculated according to the statistical value calculation formula, and the distribution of is calculated to create a code table (step 7).
- the determined quantization unit, measurement interval, and contents of the code table are stored as the upstream beacon number transmission instruction (step 8). This process is performed for all beacons (steps 9 and 10).
- FIG. 13 shows the operation procedure of the upstream beacon (or the center device connected thereto) 10, the downstream beacon (or the center device connected thereto) 20, and the FCD vehicle-mounted device 50.
- the upstream beacon 10 collects the current traffic information (step 11), determines the quantization unit to be transmitted, the measurement interval, and the code table (step 12), and, together with the coding instruction number, displays the FCD onboard equipment 50 (Step 13).
- the FCD on-board unit 50 receives the code table (step 14), measures the current position-speed information according to the specified contents, and accumulates the traveling locus data (step 15).
- the traveling locus data position and speed
- the traveling locus data is encoded by referring to the code table (step 17), and the encoded instruction number and the traveling locus data are converted to the following. Transmit to the upstream beacon 20 (step 18).
- the downstream beacon 20 Upon receiving the travel locus data (step 19), the downstream beacon 20 adds the absolute latitude / longitude / absolute azimuth of the beacon position at which the information was received to the travel locus data (step 20).
- the position (L / ⁇ ) and velocity (V) are decoded with reference to the quantization unit, measurement interval, and code table (step 21).
- Step 24 performed map matching by using the position information to identify the road segment (Step-up 22), and interpolate between the identified road section at a speed information (step 2 3), generation of traffic information, Perform FCD information utilization processing such as storage (Step 24).
- the road on which the vehicle equipped with the on-board FCD is passed can be specified, and the data measured by the on-board FCD on this road can be used for analyzing the traffic situation.
- the center device connected to the upstream beacon creates a plurality of patterns based on the coding instruction contents.
- JP03 / 07284 If there is sufficient CPu power, the coding instruction content may be calculated in real time from the latest information.
- this on-board FCD device uses a plurality of encoding instruction data 52 in which a sampling interval, a quantization unit, and a code table are described, and uses the encoding instruction data 52.
- a code instruction selecting section 61 for selecting the encoding instruction data 52 is provided.
- the code instruction selecting section 61 selects the most suitable encoding instruction data 52 from the past running patterns (process A).
- the coding instruction selecting unit 61 may determine the coding instruction data 52 in consideration of the past uplink frequency (when the uplink frequency is high, a dense measurement is performed. The encoding instruction data 52 to be instructed is selected).
- the on-board FCD device 50 shown in FIG. 15 includes a plurality of encoding processing units 561 and 562 that perform encoding processing in parallel based on different encoding instruction data 521 and 522, and each encoding processing unit 561. , 562 are provided with an encoded information selecting section 62 for selecting encoded data to be transmitted from the encoded data.
- the encoding processing units 561 and 562 hold N pieces of encoding instruction data 521 and 522 In such a case, the data stored in the traveling locus storage unit 54 is coded based on each of the coding instruction data 521 and 522 to generate N kinds of coded data.
- the coded information selection unit 62 selects the most effective coded data that has a good balance between the information amount and the data size from the N types of coded data.
- the coded information selection unit 62 determines whether or not the coded information is effective coded information by, for example, the following method (process B).
- buffer capacity communication capacity
- the buffer capacity When “the buffer capacity has been reached”, it is desirable to send the travel trajectory information over the longest possible distance, so send the encoded trajectory information that can represent the longest distance within the specified data amount. If the buffer capacity has not been reached, we want to send as detailed information as possible, so we send the encoding trajectory information with the shortest sampling interval within the specified data amount.
- the FCD on-board unit can effectively transmit travel trajectory data encoded using the optimal code table.
- FIG. 16 shows a processing procedure of the FCD vehicle-mounted device 50 in this case.
- FCD vehicle unit 50 holds a plurality of code tables received (step 34), as specified contents, the current position - speed information is measured and accumulates traveling locus data (step 35).
- the processing A for selecting the optimal encoding instruction data is performed (step 37).
- the processing B for selecting effective coded data from data coded based on each coding instruction data is performed (step 38).
- Step 3 9 transmits the traveling locus data encoded instructions number and coding on the downstream side beacon 20 (Step 3 9), it clears the traveling locus buffer (step 40).
- the on-board FCD can automatically select the code table according to the driving situation. Also, in the encoded instruction data transmitted by the upstream beacon to the on-board FCD, the on-board FCD instructs to increase the information on the number of stops and the stop time, and blinker / hazard half-door warning / parking. It may be instructed to increase vehicle sensor information such as brakes. These information will be helpful when eliminating poor quality information that becomes noise in determining traffic conditions in the collected travel route data.
- the FCD system and its device of the present invention can efficiently collect travel trajectory data of a vehicle using a beacon and obtain highly accurate traffic information.
- the traveling locus data collection position is the fixed position of the beacon, the amount of data transmitted from the vehicle-mounted device to the beacon can be reduced.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Chemical & Material Sciences (AREA)
- Analytical Chemistry (AREA)
- Traffic Control Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2003242082A AU2003242082A1 (en) | 2002-06-14 | 2003-06-09 | Fcd system and device using beacon |
EP03736108A EP1533775A4 (en) | 2002-06-14 | 2003-06-09 | FCD SYSTEM AND DEVICE USING A BEACON |
US10/517,791 US20050171682A1 (en) | 2002-06-14 | 2003-06-09 | Fcd system and device using beacon |
KR10-2004-7020365A KR20050005560A (ko) | 2002-06-14 | 2003-06-09 | 비콘을 이용한 fcd 시스템과 장치 |
CA002489541A CA2489541A1 (en) | 2002-06-14 | 2003-06-09 | Fcd system using beacons and facilities |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2002174424A JP3748420B2 (ja) | 2002-06-14 | 2002-06-14 | ビーコンを用いたfcdシステムと装置 |
JP2002-174424 | 2002-06-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003107302A1 true WO2003107302A1 (ja) | 2003-12-24 |
Family
ID=29727970
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/007284 WO2003107302A1 (ja) | 2002-06-14 | 2003-06-09 | ビーコンを用いたfcdシステムと装置 |
Country Status (8)
Country | Link |
---|---|
US (1) | US20050171682A1 (ja) |
EP (1) | EP1533775A4 (ja) |
JP (1) | JP3748420B2 (ja) |
KR (1) | KR20050005560A (ja) |
CN (1) | CN1675664A (ja) |
AU (1) | AU2003242082A1 (ja) |
CA (1) | CA2489541A1 (ja) |
WO (1) | WO2003107302A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1605419A1 (en) * | 2003-03-17 | 2005-12-14 | Matsushita Electric Industrial Co., Ltd. | Method and device for transmitting a run trace in probe car system |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10323968B2 (en) * | 2007-05-28 | 2019-06-18 | Panasonic Intellectual Property Management Co., Ltd. | Method of recording physical quantity change history, program thereof, flow rate measurement apparatus and fluid supplying system |
CN100517411C (zh) * | 2007-09-18 | 2009-07-22 | 中国科学院软件研究所 | 一种基于网络受限移动对象数据库的交通流数据采集与分析方法 |
JP2011039704A (ja) * | 2009-08-07 | 2011-02-24 | Sumitomo Electric Ind Ltd | プローブ情報の処理装置、コンピュータプログラム及び路車間通信システム |
CN103000022B (zh) * | 2011-09-08 | 2015-04-08 | 北京掌城科技有限公司 | 一种实时交通信息生成方法 |
JP6521541B2 (ja) * | 2014-12-31 | 2019-05-29 | 華為技術有限公司Huawei Technologies Co.,Ltd. | Internet−of−vehicles通信方法および装置 |
JP6389154B2 (ja) * | 2015-08-25 | 2018-09-12 | 矢崎エナジーシステム株式会社 | 運行管理システム |
WO2017188020A1 (ja) * | 2016-04-28 | 2017-11-02 | 日本電気株式会社 | 管理システム、移動体、管理装置、速度通知方法、管理方法及びプログラムが記憶された記憶媒体 |
WO2021066784A1 (en) * | 2019-09-30 | 2021-04-08 | Siemens Mobility, Inc. | System and method for detecting speed anomalies in a connected vehicle infrastructure environment |
KR102609839B1 (ko) * | 2023-06-01 | 2023-12-05 | 클레온(주) | 전동청소차 운영 중앙 제어 시스템 |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS5631199A (en) * | 1979-08-24 | 1981-03-28 | Nippon Denso Co | Traffic control data conversion system |
JPS5837796A (ja) * | 1981-08-28 | 1983-03-05 | オムロン株式会社 | 旅行時間計測装置 |
JPH07262487A (ja) * | 1994-03-25 | 1995-10-13 | Hitachi Ltd | 道路区間旅行時間推定方法 |
JPH08329381A (ja) * | 1995-05-31 | 1996-12-13 | Matsushita Electric Ind Co Ltd | 起点・終点情報作成装置 |
JPH09115087A (ja) * | 1995-10-19 | 1997-05-02 | Mitsubishi Electric Corp | 交通所要時間算出装置 |
JP2000011290A (ja) * | 1998-06-22 | 2000-01-14 | Hitachi Ltd | 旅行時間・渋滞情報推定方法及び装置 |
JP2000194984A (ja) * | 1998-12-24 | 2000-07-14 | Nippon Telegr & Teleph Corp <Ntt> | 誘導車両数制御システム |
JP2000259978A (ja) * | 1999-03-12 | 2000-09-22 | Hitachi Ltd | 旅行時間情報処理装置 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5289183A (en) * | 1992-06-19 | 1994-02-22 | At/Comm Incorporated | Traffic monitoring and management method and apparatus |
ATE187835T1 (de) * | 1995-03-23 | 2000-01-15 | Deutsche Telekom Mobil | Verfahren und einrichtung zur ermittlung von dynamischen verkehrsinformationen |
DE19833614B4 (de) * | 1998-07-25 | 2009-12-10 | Bayerische Motoren Werke Aktiengesellschaft | Verfahren zur Verkehrsqualitätserkennung und Fahrzeug als Mittel dazu |
US6334086B1 (en) * | 2000-03-10 | 2001-12-25 | Rotis Inc. (Road Traffic Information Systems) | Method and apparatus for collecting traffic information |
WO2001069569A2 (en) * | 2000-03-15 | 2001-09-20 | Raytheon Company | Automatic incident detection |
-
2002
- 2002-06-14 JP JP2002174424A patent/JP3748420B2/ja not_active Expired - Lifetime
-
2003
- 2003-06-09 CN CNA038186624A patent/CN1675664A/zh active Pending
- 2003-06-09 WO PCT/JP2003/007284 patent/WO2003107302A1/ja not_active Application Discontinuation
- 2003-06-09 AU AU2003242082A patent/AU2003242082A1/en not_active Abandoned
- 2003-06-09 CA CA002489541A patent/CA2489541A1/en not_active Abandoned
- 2003-06-09 EP EP03736108A patent/EP1533775A4/en not_active Withdrawn
- 2003-06-09 US US10/517,791 patent/US20050171682A1/en not_active Abandoned
- 2003-06-09 KR KR10-2004-7020365A patent/KR20050005560A/ko not_active Application Discontinuation
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS5631199A (en) * | 1979-08-24 | 1981-03-28 | Nippon Denso Co | Traffic control data conversion system |
JPS5837796A (ja) * | 1981-08-28 | 1983-03-05 | オムロン株式会社 | 旅行時間計測装置 |
JPH07262487A (ja) * | 1994-03-25 | 1995-10-13 | Hitachi Ltd | 道路区間旅行時間推定方法 |
JPH08329381A (ja) * | 1995-05-31 | 1996-12-13 | Matsushita Electric Ind Co Ltd | 起点・終点情報作成装置 |
JPH09115087A (ja) * | 1995-10-19 | 1997-05-02 | Mitsubishi Electric Corp | 交通所要時間算出装置 |
JP2000011290A (ja) * | 1998-06-22 | 2000-01-14 | Hitachi Ltd | 旅行時間・渋滞情報推定方法及び装置 |
JP2000194984A (ja) * | 1998-12-24 | 2000-07-14 | Nippon Telegr & Teleph Corp <Ntt> | 誘導車両数制御システム |
JP2000259978A (ja) * | 1999-03-12 | 2000-09-22 | Hitachi Ltd | 旅行時間情報処理装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP1533775A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1605419A1 (en) * | 2003-03-17 | 2005-12-14 | Matsushita Electric Industrial Co., Ltd. | Method and device for transmitting a run trace in probe car system |
EP1605419A4 (en) * | 2003-03-17 | 2008-10-15 | Matsushita Electric Ind Co Ltd | METHOD AND DEVICE FOR TRANSMITTING ROUTE OF COURSE IN AUTOMOTIVE PROBE SYSTEM |
Also Published As
Publication number | Publication date |
---|---|
EP1533775A4 (en) | 2006-05-17 |
US20050171682A1 (en) | 2005-08-04 |
KR20050005560A (ko) | 2005-01-13 |
CA2489541A1 (en) | 2003-12-24 |
JP2004021517A (ja) | 2004-01-22 |
AU2003242082A1 (en) | 2003-12-31 |
CN1675664A (zh) | 2005-09-28 |
EP1533775A1 (en) | 2005-05-25 |
JP3748420B2 (ja) | 2006-02-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107784835B (zh) | 基于交通数据分析的交通状态模式预测系统及其预测方法 | |
US7680588B2 (en) | Traffic information management system | |
EP2142887B1 (en) | Selecting route according to traffic information | |
WO2004061394A1 (ja) | 交通情報提供システム、交通情報表現方法及び装置 | |
EP1566665A1 (en) | Apparatus and method for providing ambient parameter data and for determining weather information | |
US11740101B2 (en) | Method for characterising bends for warning drivers | |
US8260532B2 (en) | Traffic probe in-vehicle map-based process to reduce data communications and improve accuracy | |
JP2004280521A (ja) | プローブカーシステムでの走行軌跡の伝送方法と装置 | |
JP2006244265A (ja) | 交通情報生成装置及び交通情報生成方法、交通情報提供装置並びに交通情報配信システム | |
EP2617021A1 (en) | Improvements in or relating to portable processing devices | |
KR20140052953A (ko) | 운행의 예상된 평균 속도들을 생성하는 방법 | |
US20010014847A1 (en) | Apparatus and method monitoring traffic | |
KR20160125457A (ko) | 트래픽 혼잡 경고를 제공하기 위한 방법들 및 시스템들 | |
JP4233364B2 (ja) | 交通情報送信方法、交通情報送信システム及び装置 | |
WO2003107302A1 (ja) | ビーコンを用いたfcdシステムと装置 | |
WO2004097340A1 (ja) | ルート情報送信方法と装置 | |
JP2004342138A (ja) | ビーコンを用いたfcdシステムと装置 | |
JP2003203243A (ja) | 地図データの蓄積及び送信方法とそれを実施する装置 | |
JP2006344006A (ja) | 旅行時間推定システム、装置及び方法 | |
WO2005038742A1 (ja) | 交通情報の生成方法と装置 | |
CN102692233B (zh) | 可变信息标志应用系统、电子导航装置和方法 | |
JP2004318621A (ja) | 交通情報推定装置及び方法 | |
JP2006031422A (ja) | 交通情報生成装置及び交通情報生成方法、交通情報提供装置並びに交通情報配信システム | |
JP3874745B2 (ja) | 交通情報提供方法、交通情報提供システム及び装置 | |
JP2004342138A5 (ja) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2489541 Country of ref document: CA Ref document number: 1020047020365 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003736108 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1020047020365 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20038186624 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10517791 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 2003736108 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2003736108 Country of ref document: EP |