EP3343532B1 - Procédé de collecte de données de sonde et dispositif de collecte de données de sonde - Google Patents

Procédé de collecte de données de sonde et dispositif de collecte de données de sonde Download PDF

Info

Publication number
EP3343532B1
EP3343532B1 EP15902910.7A EP15902910A EP3343532B1 EP 3343532 B1 EP3343532 B1 EP 3343532B1 EP 15902910 A EP15902910 A EP 15902910A EP 3343532 B1 EP3343532 B1 EP 3343532B1
Authority
EP
European Patent Office
Prior art keywords
probe data
vehicles
vehicle
server
seconds
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP15902910.7A
Other languages
German (de)
English (en)
Other versions
EP3343532A1 (fr
EP3343532A4 (fr
Inventor
Masahide Nakamura
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nissan Motor Co Ltd
Original Assignee
Nissan Motor Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nissan Motor Co Ltd filed Critical Nissan Motor Co Ltd
Publication of EP3343532A1 publication Critical patent/EP3343532A1/fr
Publication of EP3343532A4 publication Critical patent/EP3343532A4/fr
Application granted granted Critical
Publication of EP3343532B1 publication Critical patent/EP3343532B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/065—Traffic control systems for road vehicles by counting the vehicles in a section of the road or in a parking area, i.e. comparing incoming count with outgoing count
    • 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
    • G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
    • G08G1/0112—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from the vehicle, e.g. floating car data [FCD]
    • 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
    • G08G1/0125—Traffic data processing
    • 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
    • G08G1/0125—Traffic data processing
    • G08G1/0133—Traffic data processing for classifying traffic situation
    • 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
    • G08G1/0137—Measuring and analyzing of parameters relative to traffic conditions for specific applications
    • G08G1/0141—Measuring and analyzing of parameters relative to traffic conditions for specific applications for traffic information dissemination
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/123—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams
    • G08G1/127—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams to a central station ; Indicators in a central station
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/123—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams
    • G08G1/127—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams to a central station ; Indicators in a central station
    • G08G1/13—Traffic control systems for road vehicles indicating the position of vehicles, e.g. scheduled vehicles; Managing passenger vehicles circulating according to a fixed timetable, e.g. buses, trains, trams to a central station ; Indicators in a central station the indicator being in the form of a map
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096708—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
    • G08G1/096716—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information does not generate an automatic action on the vehicle control
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/16—Anti-collision systems
    • G08G1/164—Centralised systems, e.g. external to vehicles
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1694—Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/30—TPC using constraints in the total amount of available transmission power
    • H04W52/34—TPC management, i.e. sharing limited amount of power among users or channels or data types, e.g. cell loading
    • H04W52/343—TPC management, i.e. sharing limited amount of power among users or channels or data types, e.g. cell loading taking into account loading or congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Definitions

  • the present invention relates to a probe data collection method and a probe data collection device in a probe data management system for the collection of probe data that are transmitted from a vehicle.
  • a probe data collection method in which it is determined whether probe data that are transmitted from a vehicle is real-time transmission data or non-real-time transmission data, and real-time transmission data are preferentially transmitted over non-real-time transmission data (for example, refer to Patent Document 1).
  • DE 199 56 682 A1 discloses a probe data collection method for a probe data management system having a server that receives probe data transmitted from vehicles, and a database that stores the probe data received by the server.
  • Patent Document 1 Japanese Laid-Open Patent Application No. 2006-65391
  • the type of probe data is determined on the vehicle side that transmits the data, and the transmission method is varied according to the determination result. Consequently, the timing for receiving data (the timing at which the data are transmitted) cannot be controlled on the server (center) side that receives the probe data, causing problems such as not being able to sufficiently secure the real-time nature of the probe data, and the communication load of the server becoming excessive.
  • an object of the present invention is to provide a probe data collection method and a probe data collection device that are capable of both ensuring the real-time nature of the collected probe data and reducing the communication load of the server.
  • the present invention provides a probe data collection method according to claim 1 and a probe data collection device according to claim 8.
  • the server calculates the correction values of the upload times of the probe data of the vehicles, in accordance with the total number of vehicles that transmitted probe data. Then, the correction values of the upload times are transmitted to the vehicles that transmitted the probe data.
  • the upload timing of each vehicle can thereby be controlled by the server according to the vehicle density.
  • the probe data reception timing of the server can be controlled, and it becomes possible to prevent both an occurrence of bias in the data reception intervals and the number of received pieces of data from becoming enormous. Then, it becomes possible to both ensure the real-time nature of the collected probe data and to reduce the communication load of the server.
  • Figure 1 is an overall system view illustrating a probe data management system provided with the probe data collection device according to the first embodiment. The overall system configuration of the embodiment will be described below based on Figure 1 .
  • the probe data management system 1 comprises a server 10 and a database 20, as illustrated in Figure 1 .
  • the server 10 is a computer that collects probe data from a large number of vehicles, and stores the collected probe data in a database in association with vehicle IDs.
  • This server 10 comprises a reception unit 11, a probe data collection controller 12, and a transmission unit 13, as illustrated in Figure 1 .
  • the reception unit 11 receives probe data and ignition signals (including start switch signals) that are transmitted from the large number of vehicles 30, and stores the received probe data in the database 20.
  • Vehicles 30 include, in addition to engine-equipped vehicles having only an engine as a traveling drive source and electrically driven vehicles (hybrid vehicles and electric vehicles) having a motor as a traveling drive source, trucks, buses, and motorcycles.
  • probe data include an identification number (vehicle ID) attached to each vehicle 30 and position information obtained from a GPS (Global Positioning System) mounted in each vehicle 30, and here, comprise at least point sequence data and trip data.
  • the point sequence data and the trip data are stored in the database 20 respectively associated with a vehicle ID.
  • the point sequence data are data transmitted from each vehicle 30 at set intervals (for example, 30 seconds) from ignition ON to ignition OFF, comprising the data transmission time, the data transmission position, and the travel distance.
  • the "data transmission position” is information indicating the position of the vehicle 30 (position information) when transmitting the data, and is indicated by latitude and longitude.
  • the "travel distance” is information indicating the distance from the position where the previous data were transmitted to the position where the current data were transmitted. Connecting the "data transmission positions" shown on the map in chronological order based on these point sequence data results in movement trajectory information as illustrated in Figure 2 .
  • the trip data are data that are transmitted from each vehicle 30 only once between ignition ON and ignition OFF, and comprise the departure time, the arrival time, the departure position, the arrival position, and the total travel distance.
  • the "departure time” is information indicating the time at which ignition ON was carried out.
  • the "arrival time” is information indicating the time at which ignition OFF was carried out.
  • the "departure position” is information indicating the vehicle position when ignition ON was carried out.
  • the "arrival position” is information indicating the vehicle position when ignition OFF was carried out.
  • the "departure position” and the “arrival position” are indicated by latitude and longitude.
  • the “total travel distance” is information indicating the distance from the position where ignition ON was carried out to the position where ignition OFF was carried out, and is the sum of the "travel distance” in the point sequence data.
  • the probe data collection controller 12 grasps the reception timing of the probe data in the reception unit 11. Then, in order to control this reception timing, a probe data collection control process, described later, is executed, to calculate correction values of the upload times of the probe data in vehicles 30 (A, B, C in Figure 1 ) that are present in a predetermined traveling area ⁇ (area surrounded by the broken line in Figure 1 ). The calculated correction values of the upload times of the probe data are output from the probe data collection controller 12 to the transmission unit 13.
  • the transmission unit 13 is an external communication mechanism that communicates with the vehicles 30 (A, B, C in Figure 1 ) that are present in the predetermined traveling area ⁇ specified by the probe data collection controller 12.
  • the correction values of the upload times output from the probe data collection controller 12 are transmitted to the vehicles 30 (A, B, C) within the predetermined traveling area ⁇ .
  • Each vehicle 30 comprises a data transmission unit that transmits probe data to the reception unit 11 of the server 10, and a data reception unit that receives the correction values of the upload times from the transmission unit 13.
  • the vehicles 30 (A, B, C) within the predetermined traveling area ⁇ change the timings (upload times) of transmitting the probe data according to the correction values.
  • the database 20 is a memory capable of sending and receiving data to and from the server 10.
  • map data In addition to the probe data obtained from a plurality of vehicles 30, map data, user information including vehicle ID and User ID, and the like, are stored in this database 20.
  • Figure 3 is a flowchart illustrating the flow of a data collection control process that is executed in the first embodiment. The configuration of the data collection control process according to the first embodiment will be described below based on Figure 3 .
  • Step S1 vehicles that are in an ignition ON state are detected, and the process proceeds to Step S2.
  • an ignition ON state is determined when there is an input of an ignition signal from a vehicle 30 to the reception unit 11.
  • Step S2 following the detection of ignition ON vehicles in Step S1, it is determined whether or not there is a vehicle in the ignition ON state. In the case of YES (ignition ON vehicles present), the process proceeds to Step S3, and if NO (ignition ON vehicles absent), the process returns to Step S1.
  • Step S3 following the determination that ignition ON vehicles are present in Step S2, the vehicle IDs of the vehicles (ignition ON vehicles) detected in Step S2 are verified against User IDs that are stored in the database 20 in advance, and the process proceeds to Step S4.
  • Step S4 following the verification of the vehicle IDs in Step S3, the current positions of the vehicles detected in Step S2 (ignition ON vehicles) are detected for each vehicle, and the process proceeds to Step S5.
  • the current position information is detected based on the data transmission position information included in the point sequence data of the probe data.
  • this detection of the current position is executed for all vehicles detected in Step S2.
  • this current position information may include the traveling direction of the vehicles that are traveling.
  • Step S5 following the detection of the current positions of the vehicles in Step S4, the upload times of the vehicles detected in Step S2 (ignition ON vehicles) are detected for each vehicle, and the process proceeds to Step S6.
  • upload times are times indicating the timings at which probe data are transmitted from the vehicles 30, and are, for example, information such as "00 seconds and 30 seconds every minute” or "00 seconds -> 35 seconds -> 10 seconds -> 45 seconds -> 20 seconds -> 55 seconds -> 30 seconds "
  • This upload time information is detected based on the data transmission time information included in the point sequence data of the probe data.
  • this detection of the upload times is executed for all vehicles detected in Step S2.
  • Step S6 following the detection of the upload times in Step S5, the traveling areas in which the vehicles detected in Step S2 (ignition ON vehicles) are present are classified for each vehicle based on the current position of each vehicle detected in Step S4, and the process proceeds to Step S7.
  • "traveling areas” are individual areas obtained by partitioning an area from which the server 10 can receive probe data into a plurality of areas, and are arbitrarily set in advance. These traveling areas are, for example, areas along a specific lane, areas along the up lane of a specific lane, or the like. In addition, traveling areas may be partitioned based on links, intersections, etc., that are set on a lane. Then, the classification of these traveling areas is carried out based on the current position information detected in Step S4 and the traveling area sections that are set in advance. In addition, this classification of the traveling areas is executed for all vehicles detected in Step S2.
  • Step S7 following the classification of the traveling areas in Step S6, a predetermined area is arbitrarily selected from the plurality of traveling areas that are set in advance, and the process proceeds to Step S8.
  • the selection of the traveling area may be carried out according to an order that is set in advance, or may be carried out based on a condition that is arbitrarily set.
  • Step S8 following the selection of the traveling area in Step S7, the total number of vehicles 30 that are present within the selected traveling area is detected, and the process proceeds to Step S9.
  • the detection of the total number of vehicles within the traveling area is carried out based on the current position information detected in Step S4 and the information on the traveling areas in which the vehicles are present classified in Step S6.
  • Step S9 following the detection of the total number of vehicles in Step S8, it is determined whether or not the total number of vehicles within the predetermined traveling area detected in Step S8 is equal to or greater than a predetermined value Th, which is set in advance.
  • a predetermined value Th which is set in advance.
  • the process proceeds to Step S10, and if NO (less than the predetermined value Th), the process proceeds to Step S11.
  • the "predetermined value Th" is the number of cars at which the communication load of the server 10 is thought to become excessive.
  • the number of pieces of received probe data increases as the total number of vehicles within the traveling area increases, and the real-time nature of the probe data is improved.
  • the "predetermined value Th" described above is a value that is set based on the boundary between the securing of real-time nature and an excessive communication load.
  • Step S10 following the determination that the total number of vehicles is equal to or greater than the predetermined value Th in Step S9, thinning correction is carried out with respect to the respective upload times of the vehicles 30 that are present within the selected traveling area, and the process proceeds to Step S12.
  • “thinning correction” means to calculate a correction value for reducing the number of probe data received by the reception unit 11 of the server 10 during a predetermined period, and, in this case, one of "transmission interval extension correction,” “transmission data number reduction correction,” and “data transmission vehicle reduction correction” is carried out in accordance with the total number of vehicles.
  • the first threshold value Th1 and the second threshold value Th2, described later, are arbitrarily set.
  • the “transmission interval extension correction” is to calculate a correction value to extend the upload interval of the probe data by each vehicle 30, and is carried out when the total number of vehicles within the predetermined traveling area is relatively small, even if equal to or greater than the predetermined value Th (when the total number of vehicles is less than a first threshold value Th1 (> Th)). That is, in this "transmission interval extension correction,” in which probe data are being transmitted from each vehicle 30 at 30-second intervals, the upload interval is corrected to 40 seconds for a certain vehicle X, while the upload interval is corrected to 35 seconds for a different vehicle Y. In this "transmission interval extension correction,” it is not necessary to extend the upload interval of all vehicles, and it is not necessary to carry out an extension of the upload interval depending on the vehicle.
  • the "transmission data number reduction correction” is to calculate a correction value to reduce the number of uploads of the probe data within a predetermined time by each vehicle 30, and is carried out when the total number of vehicles within the predetermined traveling area is equal to or greater than the predetermined value Th but is relatively small (when the total number of vehicles is equal to or greater than the first threshold value Th1 and less than a second threshold value Th2 (> Th1)).
  • transmission data number reduction correction in which probe data are being transmitted from each vehicle 30 at 30-second intervals, a certain vehicle M is corrected to transmit at 60-second intervals (that is, the number of uploads is halved compared to before correction), and a different vehicle N is corrected to transmit at 90-second intervals (the number of uploads is set to 1/3 compared to before correction).
  • transmission data number reduction correction it is not necessary to reduce the number of uploads of all vehicles, and it is not necessary to carry out a reduction in the number of uploads depending on the vehicle.
  • the "data transmission vehicle reduction correction” is to calculate a correction value to reduce the number of vehicles that transmit probe data, and is carried out when the total number of vehicles within the predetermined traveling area is equal to or greater than the predetermined value Th, and is relatively large (when the total number of vehicles is equal to or greater than the second threshold value Th2). That is, in this "data transmission vehicle reduction correction,” in which all vehicles 30 within the predetermined traveling area ⁇ are transmitting probe data, a correction is made such that only half of the vehicles 30 present within the traveling area ⁇ transmit probe data. In this "data transmission vehicle reduction correction," the number of vehicles for stopping data transmission is arbitrarily set.
  • Step S11 following the determination that the total number of vehicles is less than the predetermined value Th in Step S9, an equalization correction is carried out with respect to the respective upload times of the vehicles 30 that are present within the selected traveling area, and the process proceeds to Step S12.
  • equalization correction is a correction to calculate correction values for offsetting the upload times without changing the upload intervals of the probe data and dispersing the reception intervals of the probe data by the server 10, and is specifically carried out by calculating correction values of upload times that make the reception intervals of the probe data by the server 10 constant.
  • the upload times of a certain vehicle P are "20 seconds and 50 seconds every minute” and the upload times of a different vehicle Q are "25 seconds and 55 seconds every minute.”
  • probe data are transmitted from the vehicle P at 20 seconds every minute and at 50 seconds every minute, and probe data are transmitted from vehicle Q at 25 seconds every minute and at 55 seconds every minute.
  • Step S12 after calculating correction values of the upload times in Step S10 or Step S11, the correction values of the upload times for each vehicle 30 are respectively transmitted to the vehicles 30 that are present within the selected traveling area, and the process proceeds to Step S13.
  • Step S13 following the transmission of the correction values of the upload times in Step S12, it is determined whether or not the correction of the upload times of the vehicles 30 that are present in each traveling area has been completed for all traveling areas that are set in advance. In the case of YES (correction complete), the process proceeds to RETURN, and if NO (correction incomplete), the process returns to StepS7.
  • the "upload time correction action,” the “transmission interval extension correction action,” the “transmission data number reduction correction action,” the “data transmission vehicle reduction correction action,” and the “equalization correction action” will be separately described regarding the actions of the probe data collection device according to the first embodiment.
  • probe data are collected by receiving probe data transmitted from vehicles 30 that are present around the server 10 of the probe data management system 1 and storing the probe data in a database 20.
  • each vehicle 30 when entering an ignition ON state, each vehicle 30 continues to transmit probe data to the server 10 at a preset timing (for example, at 30-second intervals) until an ignition OFF state is reached. That is, in each vehicle 30, the upload times are set based on the time at which the host vehicle reaches the ignition ON state, and probe data are transmitted when it becomes the set upload time.
  • the server 10 which receives the probe data, receives the probe data when the vehicles 30 transmit the probe data; therefore, the reception timing of probe data by the server 10 is dependent on the ignition ON time of each vehicle 30 and the total number of vehicles 30 that transmit probe data. That is, if a plurality of vehicles 30 reaches the ignition ON state in succession, the server 10 would receive the probe data continuously over a short period of time, then after a certain period of waiting time, the server would continuously receive probe data again, creating a bias in the reception timings of the probe data. In addition, if the total number of vehicles 30 that transmit probe data is small, or the data transmission frequency in each vehicle 30 is low, the amount of probe data that can be collected in the server 10 becomes small. In these cases, probe data cannot be appropriately collected in chronological order, and there arises a problem in that the real-time nature of the data cannot be ensured.
  • the server 10 calculates the correction values of the upload times of the probe data of the vehicles 30, and the timings at which the server 10 receives the probe data are controlled. An increase in the number of pieces of data and bias in the reception timings of the probe data are thereby suppressed, to both ensure the real-time nature and reduce the communication load.
  • Step S1 -> Step S2 -> Step S3 such that vehicles in the ignition ON state are detected, and the vehicle IDs of the detected ignition ON vehicles are verified against User IDs.
  • Step S4 -> Step S5 -> Step S6 such that the current position and the upload time is detected for each vehicle 30, and the traveling areas in which the vehicles 30 are present are classified for each vehicle 30.
  • Step S7 when the classification of the traveling areas is completed for all vehicles 30 that are in the ignition ON state, the process proceeds to Step S7, and a predetermined traveling area is arbitrarily selected.
  • Step S8 the total number of vehicles 30 that are present within the traveling area is detected, and the correction values of the upload times are calculated according to the total number of vehicles within the traveling area. That is, if the total number of vehicles within the traveling area is equal to or greater than the predetermined value Th, the process proceeds from Step S9 -> Step S10, and a "thinning correction" for reducing the number of pieces of probe data received by the reception unit 11 of the server 10 during a predetermined period is executed.
  • Step S9 if the total number of vehicles within the traveling area is less than the predetermined value Th, the process proceeds from Step S9 -> Step S11, and an "equalization correction" is executed whereby the upload times are offset without changing the upload intervals of the probe data, and the reception intervals of the probe data by the server 10 is dispersed. Then, when the correction values of the upload times for each vehicle 30 are calculated, these correction values of the upload times are transmitted to each of the vehicles 30 that are present within the selected traveling area.
  • the upload times of the vehicles 30 will be controlled by the server 10, and biases in the reception timings of the probe data and increases in the number of receptions of the probe data in the server 10 will be eliminated. It thereby becomes possible to both ensure the real-time nature of the probe data and reduce the communication load of the server 10.
  • an area from which the server 10 can receive probe data is partitioned into a plurality of traveling areas, and correction values corresponding to the total number of vehicles that are present within the traveling areas are calculated for each of the traveling areas. Accordingly, the reception timings of probe data are controlled for each of the limited partitions, and it becomes possible to facilitate the calculation of the correction values of the upload times. It is thereby possible to promptly correct the upload times with respect to changes in the total number of vehicles, and to appropriately control the reception timings of the probe data.
  • the method of correcting the upload times is changed according to the total number of vehicles that are present within the selected traveling area. That is, if the total number of vehicles within the traveling area is equal to or greater than the predetermined value Th, a "thinning correction" for reducing the number of pieces of probe data received by the server during a predetermined period is executed. In addition, if the total number of vehicles within the traveling area is less than the predetermined value Th, an "equalization correction" is executed whereby the upload times are offset without changing the upload intervals of the probe data, and the reception intervals of the probe data by the server 10 are dispersed.
  • Figure 4A is an explanatory view illustrating the transmission and reception timings of probe data before carrying out a transmission interval extension correction
  • Figure 4B is an explanatory view illustrating the transmission and reception timings of probe data when executing the transmission interval extension correction with respect to the transmission and reception timings shown in Figure 4A .
  • the transmission interval extension correction action of the first embodiment will be described below, based on Figure 4A and Figure 4B .
  • a "transmission interval extension correction” is carried out whereby the upload intervals of each vehicle 30 are increased.
  • the vehicles A, B, C are respectively transmitting probe data every 30 seconds, based on the time at which the respective host vehicle reached an ignition ON state; for example, it is assumed that the upload times of vehicle A are "00 seconds and 30 seconds every minute," the upload times of vehicle B are "03 seconds and 33 seconds every minute,” and the upload times of vehicle C are "28 seconds and 58 seconds every minute.”
  • reception of probe data is repeated in the server 10 at timings of 58 seconds (vehicle C) -> 00 seconds (vehicle A) -> 03 seconds (vehicle B) -> (25-second gap) -> 28 seconds (vehicle C) -> 30 seconds (vehicle A) -> 33 seconds (vehicle B) -> (25-second gap) -> 58 seconds (vehicle C) -> 00 seconds (vehicle A) ...
  • a "transmission interval extension correction” is executed to calculate correction values such that the upload interval of vehicle A is set to 35 seconds, the upload interval of vehicle B is set to 40 seconds, and the upload interval of vehicle C is set to 32 seconds.
  • the upload times of vehicle A are thereby corrected to "35 seconds -> 10 seconds -> 45 seconds -> 20 seconds "
  • the upload times of vehicle B are corrected to "43 seconds -> 23 seconds -> 03 seconds ...
  • the upload times of vehicle C are corrected to "30 seconds -> 02 seconds -> 34 seconds -> 06 seconds ... "
  • the server 10 receives probe data at 30 seconds (vehicle C) -> 35 seconds (vehicle A) -> 43 seconds (vehicle B) -> 02 seconds (vehicle C) -> 10 seconds (vehicle A) -> 23 seconds (vehicle B) -> 34 seconds (vehicle C) -> 45 seconds (vehicle A)...
  • Figure 5A is an explanatory view illustrating the transmission and reception timings of probe data before carrying out a transmission data number reduction correction
  • Figure 5B is an explanatory view illustrating the transmission and reception timings of probe data when executing the transmission data number reduction correction with respect to the transmission and reception timings shown in Figure 5A .
  • the transmission data number reduction correction action of the first embodiment will be described below, based on Figure 5A and Figure 5B .
  • a "transmission data number reduction correction” is carried out whereby the number of uploads by each vehicle 30 within a predetermined time is reduced.
  • the vehicles A, B, C, D, E are respectively transmitting probe data every 30 seconds, based on the time at which the respective host vehicle reached an ignition ON state; for example, it is assumed that the upload times of vehicle A are "00 seconds and 30 seconds every minute,” the upload times of vehicle B are “07 seconds and 37 seconds every minute,” the upload times of vehicle C are "15 seconds and 45 seconds every minute,” the upload times of vehicle D are "22 seconds and 52 seconds every minute,” and the upload times of vehicle E are "10 seconds and 40 seconds every minute.” In this case, reception of probe data is repeated in the server 10 at timings of 30 seconds (vehicle A) -> 37 seconds (vehicle B) -> 40 seconds (vehicle E) -> 45 seconds (vehicle C) -> 52 seconds (vehicle D) -> 00 seconds (vehicle A) -> 07 seconds (ve
  • a "transmission data number reduction correction” is executed to set the number of times of transmission of probe data to be carried out in one minute by each of the vehicles A, B, C, D, E to one. That is, a correction value is calculated to set the upload interval of each of the vehicles A, B, C, D, E to 60 seconds.
  • the upload time of vehicle A is corrected to "00 seconds every minute”
  • the upload time of vehicle B is corrected to "37 seconds every minute”
  • the upload time of vehicle C is corrected to "15 seconds every minute”
  • the upload time of vehicle D is corrected to "22 seconds every minute”
  • the upload time of vehicle E is corrected to "40 seconds every minute.”
  • the server 10 receives probe data at 00 seconds (vehicle A) -> 15 seconds (vehicle C) -> 22 seconds (vehicle D) -> 37 seconds (vehicle B) -> 40 seconds (vehicle E) -> 00 seconds (vehicle A) ... every minute.
  • Figure 6A is an explanatory view illustrating the transmission and reception timings of probe data before carrying out a data transmission vehicle reduction correction
  • Figure 6B is an explanatory view illustrating the transmission and reception timings of probe data when executing the data transmission vehicle reduction correction with respect to the transmission and reception timings shown in Figure 6A .
  • the data transmission vehicle reduction correction action of the first embodiment will be described below, based on Figure 6A and Figure 6B .
  • a "data transmission vehicle reduction correction” is carried out whereby the number of vehicles that transmit probe data is reduced.
  • the vehicles A-H are respectively transmitting probe data every 30 seconds, based on the time at which the respective host vehicle reached an ignition ON state; and the upload times of each vehicle shall be as follows.
  • reception of probe data is repeated in the server 10 at timings of 20 seconds (vehicle H) -> 22 seconds (vehicle C) -> 28 seconds (vehicle D) -> 30 seconds (vehicle A) -> 33 seconds (vehicle B and vehicle G) -> 37 seconds (vehicle E) -> 45 seconds (vehicle F) -> 50 seconds (vehicle H) -> 52 seconds (vehicle C) -> 58 seconds (vehicle D) -> 00 seconds (vehicle A) -> 03 seconds (vehicle B and vehicle G) -> 07 seconds (vehicle E) -> 15 seconds (vehicle F) -> 20 seconds (vehicle H) ... every minute, as illustrated in Figure 6A . Consequently, the amount of probe data received by the server 10 becomes extremely large, the communication load of the server 10 becomes excessive, and it becomes difficult to carry out appropriate information processing.
  • a "data transmission vehicle reduction correction” is executed to calculate correction values for stopping the transmission of probe data for vehicle B, vehicle D, vehicle G, and vehicle H. That is, the vehicles that transmit probe data will become vehicle A, vehicle C, vehicle E, and vehicle F, thereby halving the number of vehicles that transmit probe data. As a result, the upload times of vehicle B, vehicle D, vehicle G, and vehicle H are respectively corrected to "zero (none)."
  • the server 10 receives probe data at 00 seconds (vehicle A) -> 07 seconds (vehicle E) -> 15 seconds (vehicle F) -> 22 seconds (vehicle C) -> 30 seconds (vehicle A) -> 37 seconds (vehicle E) -> 45 seconds (vehicle F) -> 52 seconds (vehicle C) -> 00 seconds (vehicle A) ... every minute.
  • Figure 7A is an explanatory view illustrating the transmission and reception timings of probe data before carrying out an equalization correction
  • Figure 7B is an explanatory view illustrating the transmission and reception timings of probe data when executing equalization correction with respect to the transmission and reception timings shown in Figure 7A .
  • the equalization correction action of the first embodiment will be described below, based on Figure 7A and Figure 7B .
  • an "equalization correction” is executed whereby the upload times are offset without changing the upload intervals in each vehicle 30, and the reception intervals of the probe data by the server 10 is dispersed and correction values of upload times that make the reception intervals of the probe data by the server 10 constant are calculated.
  • the vehicles A, B are respectively transmitting probe data every 30 seconds, based on the time at which the respective host vehicle reached an ignition ON state; for example, it is assumed that the upload times of vehicle A are "00 seconds and 30 seconds every minute," and the upload times of vehicle B are "03 seconds and 33 seconds every minute.” In this case, reception of probe data is repeated in the server 10 at timings of 00 seconds (vehicle A) -> 03 seconds (vehicle B) -> (27-second gap) -> 30 seconds (vehicle A) -> 33 seconds (vehicle B) -> (27-second gap) -> 00 seconds (vehicle A) ...
  • an “equalization correction” is executed to offset the upload times of the vehicles A, B such that the reception intervals of the probe data in the server 10 become uniform. That is, a correction value of 12 seconds to be added for correction is calculated such that the upload times of vehicle A are maintained at "00 seconds and 30 seconds every minute,” while the upload times of vehicle B become “15 seconds and 45 seconds every minute.” As a result, the upload times of vehicle B are corrected to "15 seconds and 45 seconds every minute.”
  • the server 10 receives probe data at 00 seconds (vehicle A) -> 15 seconds (vehicle B) -> 30 seconds (vehicle A) -> 45 seconds (vehicle B) -> 00 seconds (vehicle A) ...
  • the server 10 is receiving probe data at biased timings, it becomes possible to uniformly differ the reception timings of the probe data by the server 10. Then, biased idle times will not occur at the time of receiving probe data, and it becomes possible to ensure the real-time nature of the probe data. Moreover, in this equalization correction, the number of pieces of probe data that are received by the server 10 within a predetermined time (for example, one minute) can be maintained at the same number as before correction. It is thereby possible to appropriately receive probe data that are transmitted from each vehicle 30 without waste, even if the total number of vehicles 30 that are present within the predetermined traveling area is relatively small.
  • the average reception interval in the server 10 is obtained (for example, 15 seconds, if the upload interval is 30 seconds and there are two vehicles).
  • the upload times of one vehicle for example, vehicle A
  • the necessary offset time of the upload times of another vehicle for example, vehicle B
  • This offset time becomes the "correction value.”
  • probe data collection method and the probe data collection device of the present invention were described above based on the first embodiment, but specific configurations thereof are not limited to this first embodiment, and various modifications and additions to the design can be made without departing from the scope of the invention according to the appended claims.
  • the upload intervals of all vehicles A-C that are present within a predetermined traveling area are extended.
  • the number of uploads of all vehicles A-E that are present within a predetermined traveling area are halved.
  • the number of uploads to be reduced may be a reduction of 1/3 or a reduction of 1/4. That is, it is sufficient if the setting of the number of uploads to be reduced during a predetermined time is carried out such that the reception timings in the server 10 becomes appropriate, based on the upload times of the vehicles A-E that are present within the traveling area before correction and the reception timings of the probe data in the server 10.
  • the transmission of probe data is stopped with respect to arbitrarily selected vehicles (B, D, G, H) from among the vehicles A-H that are present within a predetermined traveling area.
  • the selection of vehicles to stop the transmission of probe data is carried out such that the reception timings in the server 10 becomes appropriate, based on the upload times of the vehicles A-H that are present within the traveling area before correction and the reception timings of the probe data in the server 10.
  • the present invention is not limited thereto; it is sufficient if the upload times are offset without changing the upload intervals in the vehicles A, B that are present within the traveling area and the reception intervals of the probe data by the server 10 are dispersed, but it is not necessary for the reception intervals of the probe data to be strictly uniform. That is, it is sufficient to eliminate extreme bias in the reception intervals of the probe data by the server 10 by offsetting the upload times.
  • correction values of the upload times of the vehicles 30 are calculated for each of a plurality of traveling areas that are obtained by partitioning an area from which the server 10 can receive probe data into a plurality of traveling areas.
  • calculation of the correction values of the upload times may be carried out for all of the areas from which the server 10 can receive probe data. That is, in the present invention, it is sufficient if the server 10 calculates the correction values of the upload times based on the number of vehicles that transmitted probe data and the upload times for each of the vehicles, and if the reception timings of the probe data can be dynamically controlled.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Chemical & Material Sciences (AREA)
  • Analytical Chemistry (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Traffic Control Systems (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)

Claims (8)

  1. Procédé de collecte de données de sonde pour un système de gestion de données de sonde (1) doté d'un serveur (10) recevant des données de sonde transmises par des véhicules (30), et d'une base de données (20) stockant les données de sonde reçues par le serveur, caractérisé par
    la détection (S8) par le serveur d'un nombre total de véhicules ayant transmis les données de sonde et présents à l'intérieur d'une zone sélectionnée, et du temps de chargement des données de sonde pour chacun des véhicules sur la base des données de sonde reçues, le temps de chargement étant un temps de transmission des données de sonde par le véhicule,
    pour chacun des véhicules, le calcul (S10, S11) par le serveur d'une valeur de correction du temps de chargement si le nombre total de véhicules à l'intérieur de la zone sélectionnée est supérieur ou égal à une valeur définie, et en outre sur la base du temps de chargement détecté, et la transmission (S12) par le serveur des valeurs de correction calculées pour les véhicules respectifs.
  2. Procédé de collecte de données de sonde selon la revendication 1, où
    les données de sonde comprennent des informations de position, le serveur (10)
    classant (S6) les zones de déplacement où les véhicules (30) sont présents sur la base des données de sonde reçues, et sélectionnant (S7) une zone parmi la pluralité de zones de déplacement préalablement définies.
  3. Procédé de collecte de données de sonde selon la revendication 1 ou la revendication 2, où
    lors du calcul(S10, S11) de la valeur de correction, le serveur (10)
    exécute (S10) une correction réductrice pour diminuer un nombre d'éléments des données de sonde reçues par le serveur pendant une durée déterminée, en détectant le nombre total de véhicules (30) égal ou supérieur à une valeur définie préalablement, et
    exécute (S11) une correction égalisatrice où les temps de chargement sont décalés sans changer les intervalles de chargement des données de sonde, pour disperser des intervalles de réception des données de sonde par le serveur en détectant un nombre total de véhicules inférieur à la valeur définie.
  4. Procédé de collecte de données de sonde selon la
    revendication 3, où
    le serveur (10) exécute (S10) la correction réductrice en accroissant les intervalles de chargement des données de sonde par les véhicules (30).
  5. Procédé de collecte de données de sonde selon la
    revendication 3, où
    le serveur (10) exécute (S10) la correction réductrice en diminuant un nombre de chargements des données de sonde par les véhicules (30).
  6. Procédé de collecte de données de sonde selon la
    revendication 3, où
    le serveur (10) exécute (S10) la correction réductrice en diminuant un nombre de véhicules (30) transmettant les données de sonde.
  7. Procédé de collecte de données de sonde selon l'une des revendications 3 à 6, où
    le serveur (10) exécute (S11) la correction égalisatrice en calculant les valeurs de correction des temps de chargements donnant les intervalles de réception des données de sonde par le serveur constant.
  8. Dispositif de collecte de données de sonde dans un système de gestion de données de sonde (1), comprenant :
    un serveur (10) recevant des données de sonde transmises par des véhicules (30); et une base de données (20) stockant les données de sonde reçues par le serveur,
    caractérisé en ce que
    le serveur comprend un contrôleur de collecte (12) de données de sonde prévu pour
    détecter un nombre total de véhicules ayant transmis les données de sonde et présents à l'intérieur d'une zone sélectionnée, et le temps de chargement des données de sonde pour chacun des véhicules sur la base des données de sonde reçues, le temps de chargement étant un temps de transmission des données de sonde par le véhicule,
    pour chacun des véhicules, calculer une valeur de correction du temps de chargement si le nombre total de véhicules à l'intérieur de la zone sélectionnée est supérieur ou égal à une valeur définie, et en outre sur la base du temps de chargement détecté pour chacun des véhicules, et
    transmettre les valeurs de correction calculées pour les véhicules respectifs.
EP15902910.7A 2015-08-28 2015-08-28 Procédé de collecte de données de sonde et dispositif de collecte de données de sonde Active EP3343532B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/074453 WO2017037784A1 (fr) 2015-08-28 2015-08-28 Procédé de collecte de données de sonde et dispositif de collecte de données de sonde

Publications (3)

Publication Number Publication Date
EP3343532A1 EP3343532A1 (fr) 2018-07-04
EP3343532A4 EP3343532A4 (fr) 2018-09-19
EP3343532B1 true EP3343532B1 (fr) 2020-10-28

Family

ID=58187124

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15902910.7A Active EP3343532B1 (fr) 2015-08-28 2015-08-28 Procédé de collecte de données de sonde et dispositif de collecte de données de sonde

Country Status (10)

Country Link
US (1) US10096241B2 (fr)
EP (1) EP3343532B1 (fr)
JP (1) JP6323614B2 (fr)
KR (1) KR101928715B1 (fr)
CN (1) CN107924612A (fr)
BR (1) BR112018003599A2 (fr)
CA (1) CA2997047C (fr)
MX (1) MX365927B (fr)
RU (1) RU2684977C1 (fr)
WO (1) WO2017037784A1 (fr)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6905685B2 (ja) * 2017-10-26 2021-07-21 トヨタ自動車株式会社 情報管理装置及びプログラム
DE112018007629B4 (de) 2018-07-04 2022-02-24 Mitsubishi Electric Corporation Informationsversandsteuervorrichtung, server,informationsversandsteuersystem und informationsversandsteuerverfahren
DE102018214224B3 (de) * 2018-08-23 2019-12-19 Audi Ag Verfahren zur Steuerung von Erfassungseinrichtungen von Fahrzeugen einer Fahrzeugflotte durch eine zentrale Steuereinheit, um einen Datenbestand an Messdaten zu beschaffen
US11074812B2 (en) 2018-11-29 2021-07-27 Here Global B.V. Method, apparatus, and computer program product for reducing redundant data uploads
JPWO2020137950A1 (ja) * 2018-12-28 2021-11-11 パイオニア株式会社 移動体管理装置、制御方法、プログラム及び記憶媒体
CN114008409A (zh) * 2019-06-12 2022-02-01 株式会社电装 地图数据生成装置
JP7247859B2 (ja) * 2019-10-25 2023-03-29 トヨタ自動車株式会社 検査用データ収集システム、および、検査用データ収集方法
CN111339498B (zh) * 2020-03-17 2022-11-15 厦门市环境监测站(厦门市机动车排气检测中心) 一种荧光溶解有机质数据的快速校正方法及***
JP7470539B2 (ja) 2020-03-18 2024-04-18 日立建機株式会社 施工履歴情報管理システム
CN111752918B (zh) * 2020-05-15 2023-12-22 南京国电南自维美德自动化有限公司 一种历史数据交互***及其配置方法
US11617074B2 (en) * 2020-06-15 2023-03-28 Toyota Motor North America, Inc. Secure boundary area communication systems and methods
US11527153B1 (en) 2021-06-01 2022-12-13 Geotab Inc. Systems for analyzing vehicle traffic between geographic regions
US11335142B1 (en) 2021-06-01 2022-05-17 Geotab Inc. Systems for analyzing vehicle journeys
US11862011B2 (en) 2021-06-01 2024-01-02 Geotab Inc. Methods for analyzing vehicle traffic between geographic regions
JP2024061319A (ja) 2022-10-21 2024-05-07 富士通株式会社 アップロード頻度決定方法、アップロード頻度決定プログラム

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19513640C2 (de) * 1994-11-28 1997-08-07 Mannesmann Ag Verfahren zur Reduzierung einer aus den Fahrzeugen einer Fahrzeugflotte zu übertragenden Datenmenge
JPH1063997A (ja) 1996-08-23 1998-03-06 Mitsubishi Denki Eng Kk 移動体管理装置
JP3227489B2 (ja) * 1998-04-23 2001-11-12 国土交通省土木研究所長 ダイナミックにチャネルを配分する車両通信システムおよび方法
DE19956682B4 (de) 1999-11-25 2004-07-15 Daimlerchrysler Ag Verfahren zur Steuerung der Übertragungszeitpunkte von Daten, die Ereignisse betreffen, die durch Fahrzeuge detektiert werden
JP2002074591A (ja) 2000-09-01 2002-03-15 Fujitsu Ltd 位置情報通知装置
SE0201404D0 (sv) * 2002-05-06 2002-05-06 Pilotfish Networks Ab Method and apparatus providing information transfer
US7246007B2 (en) 2004-03-24 2007-07-17 General Motors Corporation System and method of communicating traffic information
JP4259430B2 (ja) 2004-08-24 2009-04-30 株式会社デンソー 車両情報送信装置および車両
EA009778B1 (ru) * 2007-01-18 2008-04-28 Совместное Белорусско-Российское Предприятие "Технотон" Закрытое Акционерное Общество Способ и система сбора эксплуатационных данных с транспортных средств для автотракторных парков
US8340718B2 (en) * 2007-12-20 2012-12-25 Telecom Italia S.P.A. Method and system for estimating road traffic
US8494709B2 (en) 2008-02-25 2013-07-23 Mitsubishi Electric Corporation On-vehicle communication device
JP2010263410A (ja) 2009-05-07 2010-11-18 Renesas Electronics Corp 車両通信装置
RU104356U1 (ru) * 2010-11-23 2011-05-10 Юрий Владимирович Леонов Автоматизированная система глобальной безопасности дорожного движения, мониторинга дорожной обстановки, дорожной ситуации, режимов работы всех бортовых систем и узлов автомобиля, сбора, обработки, передачи полученной информации от одних автомобилей к другим автомобилям и специальным государственным службам средствами связи и навигации

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP3343532A1 (fr) 2018-07-04
JP6323614B2 (ja) 2018-05-16
EP3343532A4 (fr) 2018-09-19
US20180225962A1 (en) 2018-08-09
US10096241B2 (en) 2018-10-09
KR101928715B1 (ko) 2018-12-12
JPWO2017037784A1 (ja) 2018-06-07
MX2018002139A (es) 2018-06-18
CN107924612A (zh) 2018-04-17
BR112018003599A2 (pt) 2018-09-25
WO2017037784A1 (fr) 2017-03-09
CA2997047A1 (fr) 2017-03-09
MX365927B (es) 2019-06-20
CA2997047C (fr) 2019-08-13
KR20180030222A (ko) 2018-03-21
RU2684977C1 (ru) 2019-04-16

Similar Documents

Publication Publication Date Title
EP3343532B1 (fr) Procédé de collecte de données de sonde et dispositif de collecte de données de sonde
US11630998B2 (en) Systems and methods for automatically training neural networks
CN108349496B (zh) 用于确定在两个车辆之间的用于车辆的更换车道的交通空隙的方法和控制***
US10964216B2 (en) Method for providing information about a vehicle's anticipated driving intention
CN110809790B (zh) 车辆用信息存储方法、车辆的行驶控制方法、以及车辆用信息存储装置
JP5673646B2 (ja) 周辺車両認識装置
US8989915B2 (en) Vehicular wireless communication apparatus and communication system
CN108966145B (zh) 使用v2x通信来跟踪肇事逃逸犯罪者
KR20180042344A (ko) 예상 주행 의도에 관한 정보를 제공하기 위한 장치, 방법 및 컴퓨터 프로그램
JP2016051467A (ja) 適合化予測のために広域的シーンコンテクストを使用する方法およびシステム並びに対応するプログラム、該システムを備えた乗り物
US11738776B2 (en) Perception performance evaluation of a vehicle ADAS or ADS
US20200307580A1 (en) Proactive message transmitter identification system
US20210370984A1 (en) System and method for estimating take-over time
US10803683B2 (en) Information processing device, information processing method, computer program product, and moving object
EP2492163B1 (fr) Système et procédé d'évaluation de commande de file d'attente
US11877217B2 (en) Message processing for wireless messages based on value of information
US20200406896A1 (en) Driving assist apparatus, driving assist method and program therefor
US10448344B2 (en) Communication apparatus and communication system
CN114360289A (zh) 用于车辆的辅助***、相应的方法、车辆和存储介质
CN111427063A (zh) 一种移动装置通行控制方法、装置、设备、***及介质
CN115662186A (zh) 基于人工智能的车辆避障方法以及***
CN114596727A (zh) 用于车辆的辅助方法、***、相应的车辆和存储介质
WO2023244994A1 (fr) Procédé de détection d'une collision imminente d'un véhicule

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180316

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20180821

RIC1 Information provided on ipc code assigned before grant

Ipc: G08G 1/13 20060101ALI20180813BHEP

Ipc: G08G 1/01 20060101AFI20180813BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190724

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200515

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1328998

Country of ref document: AT

Kind code of ref document: T

Effective date: 20201115

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015061333

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1328998

Country of ref document: AT

Kind code of ref document: T

Effective date: 20201028

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20201028

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210129

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210128

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210301

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210128

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210228

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015061333

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20210729

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210228

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210828

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210828

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20150828

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028

REG Reference to a national code

Ref country code: DE

Ref legal event code: R084

Ref document number: 602015061333

Country of ref document: DE

REG Reference to a national code

Ref country code: GB

Ref legal event code: 746

Effective date: 20230926

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230720

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230720

Year of fee payment: 9

Ref country code: DE

Payment date: 20230720

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201028