1. Patent Search
  2. Details

METHOD, DEVICE AND ARRANGEMENT FOR TRACKING MOVING OBJECTS

20230139242 · 2023-05-04

    Inventors

    Cpc classification

    International classification

    Abstract

    In order, when tracking moving objects, to be able to track the path of the objects without using object-identifying information, e.g. GPS information of the object or other individual identifiers by means which an object can be basically identified, or if the objects continue to change their respective identity, it is proposed how a statement can be made about the successful tracking with respect to at least some of the object group along the tracking route on the basis of the acquisition of information, taking place along a tracking route repeatedly, particularly at different locations at different times, with non-object-identifying parameter data which is emitted by the moving objects, at regular time intervals, by object-group-specific considerations of the acquired parameter data, of group-specific data profiles, acquired from these considerations, and a data profile similarity comparison, and tracking information is generated, and otherwise no such statement is possible and the generation of the tracking information does not occur.

    Claims

    1. A method for tracking moving objects, in which a) a multiplicity of objects move in an area along a tracking route in a defined direction of movement, b) the objects emit information with data relating to a plurality of non-object-identifying information parameters, at regular intervals of time, and c) with respect to the objects, the information emitted is captured with the non-object-identifying parameter data repeatedly, at different locations at different times, wherein d) first information is captured with first parameter data from a first group of the objects, which comprises at least one object, with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”, in a first information capture region along the tracking route and for the defined direction of movement, e) a data profile specific to the first group, including at least one of a group footprint and a group stamp of the object group, is generated from the captured first parameter data, and f) the data profile specific to the first group is provided for data evaluation based on a similarity comparison of data profiles, g) second information is respectively captured with second parameter data from a second group of the objects, which comprises at least one object, with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”, in at least one further, second information capture region spaced apart from the first information capture region along the tracking route at regular intervals of time or for a calculated time window after the capture in the first information capture region for the defined direction of movement for each interval of time or for each time window, h) a data profile specific to the second group is respectively generated from the respectively captured second parameter data, and i) the respectively generated data profile specific to the second group is provided for the data evaluation based on the data profile similarity comparison, j) each data profile specific to the second group is compared with the data profile specific to the first group during the data evaluation using parameter data, k) if it is determined, during the data profile similarity comparison carried out in each case, that the correlation between the first parameter data and the second parameter data is so great that the parameter data at least partially correspond, a statement can be made on the successful tracking of at least some of the objects captured in the first group along the tracking route between the two information capture regions and an item of tracking information generated, otherwise such a statement is not possible and the tracking information is not generated.

    2. The tracking method as claimed in claim 1, wherein method steps a) to f) or method steps a) to c) and g) to i) are carried out in a first device and method steps j) and k) are carried out in a second device.

    3. The tracking method as claimed in claim 1, wherein method steps a) to f) or method steps a) to c) and g) to i) and method steps j) and k) are carried out in a single device.

    4. The tracking method as claimed in claim 1, wherein the objects moving along the tracking route in space are motor vehicles driving on a road.

    5. The tracking method as claimed in claim 4, wherein the information with the non-object-identifying parameter data is an ITS status message containing data relating to a plurality of vehicle-specific, vehicle-characteristic message parameters.

    6. The tracking method as claimed in claim 5, wherein the ITS status message is a “cooperative awareness message <CAM>” according to the ETSI standard “ETSI TS 102 637-2” or a “basic safety message <BSM>” according to the SAE standard “SAE J2735”.

    7. The tracking method as claimed in claim 6, wherein the following vehicle-specific, vehicle-characteristic message parameters are used in the “cooperative awareness message <CAM>”: type of different vehicles belonging to the road users, for example bus, automobile, motorcycle, etc., in the group; time stamp of vehicles belonging to the road users in the group should be close in terms of time; position of different vehicles belonging to the road users in the group should be adjacent; direction of vehicles belonging to the road users in the group should be the same; speed of vehicles belonging to the road users in the group should be comparable; length of different vehicles belonging to the road users is used as a group identifying feature; width of different vehicles belonging to the road users is used as a group identifying feature; issuing authority of the cryptographic certificates for the signature of the status messages; certificate hierarchy for validating the certificate for the signature of the status messages; repetition rate of the change of the parameters.

    8. The tracking method as claimed in claim 1, wherein the tracking information is transmitted to a central monitoring entity, and, in this respect, is used to broadcast traffic messages or is used for cooperative ITS traffic systems or traffic telematics systems.

    9. A dev ice for tracking moving objects, characterized by tracking means which can be used to carry out method steps a) to f) or method steps a) to c) and g) to i) and method steps j) and k) as claimed in claim 1.

    10. An arrangement for tracking moving objects in which a) a multiplicity of objects move in an area along a tracking route in a defined direction of movement, b) the objects emit information with data relating to a plurality of non-object-identifying information parameters, at regular intervals of time, wherein the arrangement comprises c) at least two information capture dev ices which capture the information emitted by the moving objects with the non-object-identifying parameter data, at different locations at different times, further wherein, the at least two information capture devices comprise: d) a first information capture device d1) which captures first information with first parameter data from a first group of the objects, which comprises at least one object with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”, in a first information capture region along the tracking route for the defined direction of movement and d2) is designed in such a manner that a data profile specific to the first group, including at least one of a group footprint or a group stamp of the object group, can be generated from the captured first parameter data, e) a first communication interface which is connected to the first information capture device and provides the data profile specific to the first group and received from the first information capture dev ice for data evaluation based on a similarity comparison of data profiles, f) at least one second information capture device f1) which respectively captures second information with second parameter data from a second group of the objects, which comprises at least one object, with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”, in a further, second information capture region spaced apart from the first information capture region along the tracking route for the defined direction of movement at regular intervals of time or for a calculated time window after the capture in the first information capture region for each interval of time or for each time window, and f2) is designed in such a manner that a second data profile specific to the second group can be generated from the respectively captured second parameter data, g) a second communication interface which is connected to the second information capture device and provides the data profile specific to the second group and received from the second information capture device for the data evaluation based on the data profile similarity comparison, h) an evaluation device which is connected to the first communication interface and to the second communication interface and is designed in such a manner that h1) each data profile specific to the second group and provided by the second communication device is compared with the data profile specific to the first group and provided by the first communication device using parameter data, h2) if it is determined, during the data profile similarity comparison respectively carried out, that the correlation between the first parameter data and the second parameter data is so great that the parameter data at least partially correspond, a statement can be made on the successful tracking of at least some of the objects captured in the first group along the tracking route between the two information capture regions and an item of tracking information can be generated, otherwise such a statement is not possible and the tracking information is not generated.

    11. The tracking arrangement as claimed in claim 10, wherein arrangement features a) to e) with respect to the concrete elements stated therein or arrangement features a) to c) and f) to g) with respect to the concrete elements stated therein are contained in a first device and arrangement features h) to h2) with respect to the concrete elements stated therein are contained in a second device.

    12. The tracking arrangement as claimed in claim 10, wherein arrangement features a) to e) with respect to the concrete elements stated therein or arrangement features a) to c) and f) to g) with respect to the concrete elements stated therein and arrangement features h) to h2) with respect to the concrete elements stated therein are contained in a single device.

    13. The tracking arrangement as claimed in claim 10, wherein the objects moving along the tracking route in space are motor vehicles driving on a road.

    14. The tracking arrangement as claimed in claim 13, wherein the information with the non-object-identifying parameter data is an ITS status message containing data relating to a plurality of vehicle-specific, vehicle-characteristic message parameters.

    15. The tracking arrangement as claimed in claim 14, wherein the ITS status message is a “cooperative awareness message <CAM>” according to the ETSI standard “ETSI TS 102 637-2” or a “basic safety message <BSM>” according to the SAE standard “SAE J2735”.

    16. The tracking arrangement as claimed in claim 15, wherein the “cooperative awareness message <CAM>” has the following vehicle-specific, vehicle-characteristic message parameters: type of different vehicles belonging to the road users, for example bus, automobile, motorcycle, etc., in the group; time stamp of vehicles belonging to the road users in the group should be close in terms of time; position of different vehicles belonging to the road users in the group should be adjacent; direction of vehicles belonging to the road users in the group should be the same; speed of vehicles belonging to the road users in the group should be comparable; length of different vehicles belonging to the road users is used as a group identifying feature; width of different vehicles belonging to the road users is used as a group identifying feature; issuing authority of the cryptographic certificates for the signature of the status messages; certificate hierarchy for validating the certificate for the signature of the status messages; repetition rate of the change of the parameters.

    17. The tracking arrangement as claimed in claim 10, wherein for the purpose of transmitting the tracking information, the evaluation device is connected to a central monitoring entity, with the result that this can be used, as a result, to broadcast traffic messages or can be used for cooperative ITS traffic systems or traffic telematics systems.

    Description

    BRIEF DESCRIPTION

    [0039] Some of the embodiments will be described in detail, with references to the following Figures, wherein like designations denote like members, wherein:

    [0040] FIG. 1 shows a prior art cooperative ITS scenario with respect to a road VKS, a section of which is illustrated and which is in the preferred form of a freeway, on which a vehicle FZ drives past a stationary road devices SV in the form of a “roadside units” RSU′ in a direction of movement (direction of travel) BWR at different times t1, t2, t3,

    [0041] FIG. 2 shows, proceeding from the ITS scenario illustrated in FIG. 1, a first expanded cooperative ITS scenario for tracking at least one vehicle from a multiplicity of vehicles moving on the road or the freeway, in which a statement for tracking is obtained in a central unit,

    [0042] FIG. 3 shows, proceeding from the ITS scenario illustrated in FIG. 1, a second expanded cooperative ITS scenario for tracking at least one vehicle from a multiplicity of vehicles moving on the road or the freeway, in which a statement for tracking is obtained in a local unit; and

    [0043] FIG. 4 shows, on the basis of the expanded cooperative ITS scenario for tracking according to FIG. 2, the influence of dynamically changing affiliations of vehicles driving on the route or the freeway to the first group with respect to the first “roadside unit” having the first information capture region and to the second group with respect to the first “roadside unit” having the first information capture region on the similarity comparison (correlation check) to be carried out during the vehicle tracking according to FIG. 2.

    DETAILED DESCRIPTION

    [0044] Proceeding from the ITS scenario illustrated in FIG. 1, FIG. 2 shows a first expanded cooperative ITS scenario for tracking at least one vehicle from a multiplicity of vehicles FZ1, FZ2, FZ3 moving on the road or the freeway VKS, in which a statement for tracking is obtained in a central unit.

    [0045] In this expanded cooperative scenario, three vehicles—a first vehicle FZ1, a second vehicle FZ2 and a third vehicle FZ3—which are all trucks, for example, according to FIG. 2, but any other vehicle type, for example automobile, bus, motorcycle, bicycle, etc. would be possible, are moving at an approximately comparable speed on the road or the freeway VKS in the direction of movement BWR. In this case, this convoy of trucks respectively drives past a stationary modified road device SV in the form of a modified “roadside unit” RSU at times t1, t2. This vehicle convoy formed from the vehicles FZ1, FZ2, FZ3 therefore passes a first modified “roadside unit” RSU1 at the time t1 and a second modified “roadside unit” RSU2 at the time t2. The road device SV or the “roadside unit” RSU1, RSU2 can again be any desired technical system which belongs to the traffic infrastructure, controls the traffic and/or provides information on the traffic and/or an electronic device which is configured for this purpose and is preferably capable of V2X communication, as already mentioned above. The road devices SV or the “roadside units” RSU1, RSU2 are passed by the vehicle convoy in this case along a first tracking route SVS1 of the road VKS.

    [0046] The first tracking route SVS1 is also, at the same time, a capture route because each vehicle FZ1, FZ2, FZ3 in the convoy preferably transmits or emits an item of information IF.sub.FZ1, IF.sub.FZ2, IF.sub.FZ3 corresponding to the vehicle at regular intervals of time, for example every 100 ms, via a radio signal which needs to be captured. For this purpose, each vehicle FZ1, FZ2, FZ3 has an information transmitting device ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 corresponding to the vehicle which is preferably in the form of the V2X communication unit and is also again integrated in the on-board electronics of the vehicle (for example if the vehicle is a “non-legacy vehicle”) or else is in the form of a vehicle-independent separate device (for example if the vehicle is a “legacy vehicle”). Each item of information of this information IF.sub.FZ1, IF.sub.FZ2, IF.sub.FZ3 corresponding to the vehicle contains a multiplicity of parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 which accordingly correspond to the vehicle and belong to information parameters according to the following tables for FIG. 2 (Table-1-FIG. 2, Table-2-FIG. 2, Table-3-FIG. 2).

    [0047] Table-1-FIG. 2 shows the information IF.sub.FZ1 emitted by the vehicle FZ1 with the associated parameter data PD.sub.FZ1, whereas Table-2-FIG. 2 shows the information IF.sub.FZ2 emitted by the vehicle FZ2 with the associated parameter data PD.sub.FZ2 and Table-3-FIG. 2 shows the information IF.sub.FZ3 emitted by the vehicle FZ3 with the associated parameter data FD.sub.FZ3.

    TABLE-US-00002 TABLE 1 FIG. 2 Information (IF.sub.FZ1, t1, IF.sub.FZ1, t2) emitted at times (t1, t2) with Information (IF.sub.FZ1) emitted by the vehicle (FZ1) with parameter data (PD.sub.FZ1, t1, PD.sub.FZ1, t2) data relating to information parameters (PD.sub.FZ1) t1 t2 (Pseudonymous) identifier ID =370988 =440066 (Pseudonymous) information certificate ID =C5e4Jx1 =77gh07 Certificate authority =certauth155 =certauth155 Position (WGS84) =Lat: XX.xxx(t1)/ =Lat: XX.xxx(t2)/ Lon: YY.yyy(t1) Lon: YY.yyy(t2) Time stamp =dd.MM.yyyy(t1)/ =dd.MM.yyyy(t2)/ HH:mm:ss(t1) HH:mm:ss(t2) Type =Truck =Truck Direction of travel =west =west Speed =110 km/h =105 km/h Length =17.00 m =17.00 m Width =2.50 m =2.50 m Optional parameters =... =...

    TABLE-US-00003 TABLE 2 FIG. 2 Information (IF.sub.FZ2, t1, IF.sub.FZ2, t2) emitted at times (t1, t2) with Information (IF.sub.FZ2) emitted by the vehicle (FZ2) with parameter data (PD.sub.FZ2, t1, PD.sub.FZ2, t2) data relating to information parameters (PD.sub.FZ2) t1 t2 (Pseudonymous) identifier ID =59780 =123456 (Pseudonymous) information certificate ID =mk982 =an761 Certificate authority =certauth105 =certauth105 Position (WGS84) =Lat: XX.xxx(t1)/ =Lat: XX.xxx(t2)/ Lon: YY.yyy(t1) Lon: YY.yyy(t2) Time stamp =dd.MM.yyyy(t1)/ =dd.MM.yyyy(t2)/ HH:mm:ss(t1) HH:mm:ss(t2) Type =Truck =Truck Direction of travel =west =west Speed =112 km/h =107 km/h Length =12.50 m =12.50 m Width =2.60 m =2.60 m Optional parameters =... =...

    TABLE-US-00004 TABLE 3 FIG. 2 Information (IF.sub.FZ3, t1, IF.sub.FZ3, t2) emitted at times (t1, t2) with Information (IF.sub.FZ3) emitted by the vehicle (FZ3) with parameter data (PD.sub.FZ3, t1, PD.sub.FZ3, t2) data relating to information parameters (PD.sub.FZ3) t1 t2 (Pseudonymous) identifier ID =54510 =456789 (Pseudonymous) information certificate ID =1w389 =3o7hj Certificate authority =eurp2491 =eurp2491 Position (WGS84) =Lat: XX.xxx(t1)/ =Lat: XX.xxx(t2)/ Lon: YY.yyy(t1) Lon: YY.yyy(t2) Time stamp =dd.MM.yyyy(t1)/ =dd.MM.yyyy(t2)/ HH:mm:ss(t1) HH:mm:ss(t2) Type =Truck =Truck Direction of travel =west =west Speed =114 km/h =103 km/h Length =14.10 m =14.10 m Width =2.45 m =2.45 m Optional parameters =... =...

    [0048] In the case of the information parameters contained in the tables and the parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 corresponding to the vehicle, a distinction is again made between

    (i) information parameters and associated parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 which are used to uniquely identify the respective information transmitting device ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 corresponding to the vehicle as the transmission source of the information IF.sub.FZ1, IF.sub.FZ2, IF.sub.FZ3 and therefore ultimately also the respective vehicle FZ1, FZ2, FZ3 and the data values of which, as already stated above, are continuously changed at regular intervals of time (for example in the region of approximately 1 minute) for anonymization purposes—these information parameters and parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 are referred to below as object-identifying information parameters and parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3—and
    (ii) information parameters and associated parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 which are used to characterize, indicate, type, etc., but not uniquely identify, the respective vehicle FZ1, FZ2, FZ3 in which the information transmitting device ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 corresponding to the vehicle is situated as the transmission source of the information IF.sub.FZ1, IF.sub.FZ2, IF.sub.FZ3 and the data values of which are not changed—these information parameters and parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 are referred to below as non-object-identifying information parameters and parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3

    [0049] In said tables, Table-1-FIG. 2 to Table-3-FIG. 2, the object-identifying information parameters and parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 are again indicated with gray shading, whereas the non-object-identifying information parameters and parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 again do not have any background shading (for example with respect to a gray scale and/or pattern) (white background in said tables). Said tables each illustrate how the object-identifying parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 at the time t2 have changed in comparison with the object-identifying parameter data PD.sub.FZ1, PD.sub.FZ2, PD.sub.FZ3 at the time t1.

    [0050] The number of information parameters (both with respect to the object-identifying parameters and with respect to the non-object-identifying parameters) respectively contained in the table is fundamentally open and can be increased or decreased in an arbitrary manner as required. In the present case, the parameters decisive for the exemplary embodiment are stated.

    [0051] The meaning of these stated parameters and their data values are generally known and therefore do not require any further explanation at this point. When selecting the parameters, it should be taken into account (criteria catalog) that, for example, preferably [0052] different vehicle types of the road users, for example bus, automobile, motorcycle, etc., are captured; [0053] the time stamp of the captured vehicles belonging to the road users should be as close as possible in terms of time; [0054] the position of the captured different vehicles belonging to the road users should be as adjacent as possible; [0055] the direction of the captured vehicles belonging to the road users should be as identical as possible; [0056] the speed of the captured vehicles belonging to the road users should be as comparable as possible; [0057] the length of the captured different vehicles belonging to the road users should be used as a (group) identifying feature; [0058] the width of different vehicles belonging to the road users should be used as a (group) identifying feature; [0059] the issuing authority of the cryptographic certificates is used for the signature of the status messages; [0060] certificate hierarchy for validating the certificate is used for the signature of the status messages; [0061] repetition rate of the change of the parameters is used.

    [0062] If the vehicles FZ1, FZ2, FZ3 in the convoy having the information transmitting devices ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 corresponding to the vehicle and emitting the information IF.sub.FZ1, IF.sub.FZ2, IF.sub.FZ3 corresponding to the vehicle are in a first information capture region IEB1 of a first information capture device IEE1 of the modified first “roadside unit” RSU1, information IF.sub.FZ1,t1, IF.sub.FZ2,t1, IF.sub.FZ3,t1 emitted by the information transmitting devices ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 of the vehicles FZ1, FZ2, FZ3 at the time t1 is captured by the first information capture device IEE1 with parameter data PD.sub.FZ1,t1, PD.sub.FZ2,t1, PD.sub.FZ3,t1. In a similar manner to the information capture region IEB in FIG. 1, the first information capture region IEB1 reaches its maximum extent when the information IF.sub.FZ1, IF.sub.FZ2, IF.sub.FZ3 emitted by the information transmitting device ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 can no longer be received by the first information capture device IEE1.

    [0063] In order to be able to now track at least one vehicle in the vehicle convoy FZ1, FZ2, FZ3 in the expanded cooperative ITS scenario, in contrast to the cooperative ITS scenario explained above on the basis of FIG. 1, first information IF1 with first parameter data PD1 from the maximum quantity of information predefined at the time t1 by the information IF.sub.FZ1,t1, IF.sub.FZ2,t1, IF.sub.FZ3,t1 with the parameter data PD.sub.FZ1,t1, PD.sub.FZ2,t1, PD.sub.FZ3,t1 is captured from a first group GR1 of the vehicles FZ1, FZ2, FZ3, which comprises at least one vehicle, but preferably a plurality of vehicles with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”. When taking into account or stipulating the number of vehicles in the first group GR1, the criteria catalog mentioned above should be used when selecting the parameters.

    [0064] In the present case, at the time t1 according to FIG. 2, the three vehicles FZ1, FZ2, FZ3 form the first group GR1 even if the vehicle type is the same contrary to the criteria catalog because, for example, the speed of the vehicles is comparable and the prerequisite that the time stamps of the captured vehicles are close in terms of time and the position of the captured vehicles is adjacent is present (as illustrated in principle in FIG. 2). The information IF.sub.FZ1,t1, IF.sub.FZ2,t1, IF.sub.FZ3,t1 emitted by the vehicles FZ1, FZ2, FZ3 at the time t1 with the parameter data PD.sub.FZ1,t1, PD.sub.FZ2,t1, PD.sub.FZ3,t1 is the first information IF1 with the first parameter data PD1 as a result of the capture affiliation of said vehicles to the first group GR1 at the time t1.

    [0065] For the further performance of the tracking, the first information capture device IEE1 is now designed, preferably using generally conventional data processing means (for example a hardware unit based on a microprocessor and a memory component and program modules which can be operated and executed as software on the hardware unit), in such a manner that a data profile DP.sub.GR1 specific to the first group, in particular a group footprint or a group stamp of the vehicle group, is generated from the captured first parameter data PD1.

    [0066] This data profile DP.sub.GR1 specific to the first group is then forwarded in the modified first “roadside unit” RSU1 from the first information capture device IEE1 to a first communication interface KSS1 which is connected to the first information capture device IEE1 and provides the data profile DP.sub.GR1 specific to the first group and received from the first information capture device IEE1 for data evaluation based on a similarity comparison of data profiles. How, when and where this data profile similarity comparison takes place is explained further below in connection with the description of FIG. 2.

    [0067] In the interim, while the first data profile is generated and forwarded as described, the vehicle convoy moves further along the first tracking route SVS1 on the road or the freeway VKS. Since the vehicles FZ1, FZ2, FZ3 in the convoy are moving at a comparable speed and if one of the vehicles does not leave the road or the freeway VKS—for example for a stop at a gas station or a rest area or else to continue the journey on another road—or one of the vehicles does not inevitably leave the convoy as a result of a vehicle defect, for example engine damage, and does not drive at the edge of the road (on the shoulder in the case of the freeway) and stop, it can be assumed that the vehicle convoy is also still moving together on the road or the freeway VKS along the first tracking route SVS1.

    [0068] In the expanded cooperative ITS scenario illustrated in FIG. 2, in addition to the capture time t1, there is also a further time or a further point, the capture time t2 with the modified second “roadside unit” RSU2, for tracking the at least one vehicle in the vehicle convoy FZ1, FZ2, FZ3 along the first tracking route SVS1.

    [0069] If the convoy with the vehicles FZ1, FZ2, FZ3 now approaches the second “roadside unit” RSU2 and all vehicles (owing to the comparable speed) having the information transmitting device ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 corresponding to the vehicle and emitting the information IF.sub.FZ1, IF.sub.FZ2, IF.sub.FZ3 corresponding to the vehicle are finally in a second information capture region IEB2 of a second information capture device IEE2 of the second “roadside unit” RSU2, information IF.sub.FZ1,t2, IF.sub.FZ1,t2, IF.sub.FZ3,t2 emitted by the information transmitting devices ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 of the vehicles FZ1, FZ2, FZ3 at the time t2 is captured by the second information capture device IEE2 with parameter data PD.sub.FZ1,t2, PD.sub.FZ2,t2, PD.sub.FZ3,t2. The “roadside units” RSU1, RSU2 with the two information capture regions IEB1, IEB2 are arranged in a manner separated from one another by an arbitrarily selectable distance. In a similar manner to the information capture region IEB in FIG. 1 and the first information capture region IEB1, the second information capture region IEB2 also again reaches its maximum extent when the information IF.sub.FZ1, IF.sub.FZ2, IF.sub.FZ3 emitted by the information transmitting device ISE.sub.FZ1, ISE.sub.FZ2, ISE.sub.FZ3 can no longer be received by the second information capture device IEE2.

    [0070] Like the first information capture device IEE1, the second information capture device IEE2 captures second information IF2 with second parameter data PD2 from the maximum quantity of information predefined at the time t2 by the information IF.sub.FZ1,t2, IF.sub.FZ2,t2, IF.sub.FZ3,t2 with the parameter data PD.sub.FZ1,t2, PD.sub.FZ2,t2, PD.sub.FZ3,t2 from a second group GR2 of the vehicles FZ1, FZ2, FZ3, which again comprises at least one vehicle, but preferably again a plurality of vehicles with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”, at regular intervals of time or for a calculated time window—for example by means of the calculation according to the formula s=v*t (distance equals speed times time), where s=distance between RSU1 and RSU2 and v=speed of the vehicle convoy according to the tables (cf. Table-1-FIG. 2 to Table-3-FIG. 2), the time t and by considering “±t” to be the time window—after capturing the first vehicle group GR1 in the first information capture region IEB1 for each interval of time or for each time window. When taking into account or stipulating the number of vehicles in the second group GR2, said criteria catalog should again be used when selecting the parameters.

    [0071] In the present case, at the time t2 according to FIG. 2, the three vehicles FZ1, FZ2, FZ3 again form the second group GR2 even if the vehicle type is the same contrary to the criteria catalog because, for example, the speed of the vehicles is comparable and the prerequisite that the time stamps of the captured vehicles are close in terms of time and the position of the captured vehicles is adjacent is present (as illustrated in principle in FIG. 2). The information IF.sub.FZ1,t2, IF.sub.FZ2,t2, IF.sub.FZ3,t2 emitted by the vehicles FZ1, FZ2, FZ3 at the time t2 with the parameter data PD.sub.FZ1,t2, PD.sub.FZ2,t2, PD.sub.FZ3,t2 is the second information IF2 with the second parameter data PD2 as a result of the capture affiliation of said vehicles to the second group GR2 at the time t2.

    [0072] During the further performance of the tracking, the second information capture device IEE2—like the first information capture device IEE1—is designed, preferably again using generally conventional data processing means (for example a hardware unit based on a microprocessor and a memory component and program modules which can be operated and executed as software on the hardware unit), in such a manner that a data profile DP.sub.GR2 specific to the second group, in particular a group footprint or a group stamp of the vehicle group, is generated from the captured second parameter data PD2.

    [0073] This data profile DP.sub.GR2 specific to the second group is then forwarded in the modified second “roadside unit” RSU2 from the second information capture device IEE2 to a second communication interface KSS2 which is connected to the second information capture device IEE2 and provides the data profile DP.sub.GR2 specific to the second group and received from the second information capture device IEE2 for data evaluation based on a similarity comparison of data profiles.

    [0074] Two comparable variables, the two data profiles DP.sub.GR1, DP.sub.GR2, are now available for this data profile similarity comparison. The first data profile DP.sub.GR1 is thus supplied by the first communication interface KSS1 in the first “roadside unit” RSU1, and the second data profile DP.sub.GR2 is supplied by the second communication interface KSS2 in the second “roadside unit” RSU2, to a central unit in the form of an evaluation device AWE. The communication interfaces KSS1, KSS2 are connected to the evaluation device AWE for this purpose, wherein the connection may be wireless or wired, for example.

    [0075] In order to perform the data profile similarity comparison, the evaluation device AWE is now designed, preferably using generally conventional means for the data-processing-based comparison of two variables (for example a hardware unit based on a microprocessor and a memory component and program modules which can be operated and executed as software on the hardware unit), in such a manner that the data profile DP.sub.GR2 specific to the second group and provided by the second communication device KSS2 is compared with the data profile DP.sub.GR1 specific to the first group and provided by the first communication device KSS1 using parameter data, in particular from a combination of the parameter data PD1, PD2 within the groups GR1, GR2.

    [0076] If the data profile similarity comparison carried out in the evaluation device AWE reveals that the correlation between the first parameter data PD1 and the second parameter data PD2 is so great that the parameter data PD1, PD2 at least partially correspond, a statement can be made on the successful tracking of the vehicles FZ1, FZ2, FZ3 captured in the first group GR1 along the first tracking route SVS1 between the two information capture regions IEB1, IEB2. In this case, the evaluation device AWE produces or generates an item of tracking information SVI and forwards this information to a central monitoring entity ZÜI which is preferably in the form of a traffic control center and to which the evaluation device AWE is connected, for example in a wireless or wired manner. Otherwise, if the correspondence between the parameter data PD1, PD2 is not so great, such a statement is not possible and the tracking information SVI is not generated.

    [0077] The tracking information SVI can preferably be used in the traffic control center or the central monitoring entity ZÜI to broadcast traffic messages or can be used for cooperative ITS traffic systems or traffic telematics systems.

    [0078] Proceeding from the ITS scenario illustrated in FIG. 1, FIG. 3 shows a second expanded cooperative ITS scenario for tracking at least one vehicle from a multiplicity of vehicles FZ4 . . . FZ10 moving on the road or the freeway VKS, in which a statement for tracking is obtained in a local unit.

    [0079] In contrast to the scenario according to FIG. 2, seven vehicles—a fourth vehicle FZ4, a fifth vehicle FZ5, a sixth vehicle FZ6, a seventh vehicle FZ7, an eighth vehicle FZ8, a ninth vehicle FZ9 and a tenth vehicle FZ10—which are buses or automobiles, for example, according to FIG. 3, but any other vehicle type, for example truck, motorcycle, bicycle, etc. would also again be possible, are moving at a different speed on the road or the freeway VKS in the direction of movement BWR in this second expanded cooperative scenario. In this case, vehicle convoys having a sometimes different number of automobiles and buses in each vehicle convoy respectively drive past a stationary modified road device SV in the form of a modified “roadside unit” RSU at times t1, t2, t3. A first vehicle convoy comprising three automobiles and one bus, the bus FZ4 and the automobiles FZ5, FZ6, FZ7, therefore again passes the first modified “roadside unit” RSU1 at the time t1, a second vehicle convoy comprising three automobiles, the automobiles FZ6, FZ7, FZ8, again passes the second modified “roadside unit” RSU2 at the time t2, and a third vehicle convoy comprising three automobiles and one bus, the bus FZ9 and the automobiles FZ6, FZ7, FZ10, passes a third modified “roadside unit” RSU3 at the time t3. The road device SV or the “roadside unit” RSU1, RSU2, RSU3 can again be any desired technical system which belongs to the traffic infrastructure, controls the traffic and/or provides information on the traffic and/or an electronic device which is configured for this purpose and is preferably capable of V2X communication, as already mentioned above. The road devices SV or the “roadside units” RSU1, RSU2, RSU3 are passed by the three vehicle convoys in this case along a second tracking route SVS2 of the road VKS.

    [0080] The second tracking route SVS2 is also, at the same time, a capture route because each vehicle FZ4 . . . FZ10 in the three vehicle convoys preferably transmits or emits an item of information IF.sub.FZ4 . . . IF.sub.FZ10 corresponding to the vehicle at regular intervals of time, for example every 100 ms, via a radio signal which needs to be captured. For this purpose, each vehicle FZ4 . . . FZ10 has an information transmitting device ISE.sub.FZ4 . . . ISE.sub.FZ10 corresponding to the vehicle which is preferably in the form of the V2X communication unit and is also again integrated in the on-board electronics of the vehicle (for example if the vehicle is a “non-legacy vehicle”) or else is in the form of a vehicle-independent separate device (for example if the vehicle is a “legacy vehicle”). Each item of information of this information IF.sub.FZ4 . . . IF.sub.FZ10 corresponding to the vehicle contains a multiplicity of parameter data PD.sub.FZ4 . . . PD.sub.FZ10 which accordingly correspond to the vehicle and belong to information parameters according to the following tables for FIG. 3 (Table-1-FIG. 3 to Table-7-FIG. 3).

    [0081] Table-1-FIG. 3 shows the information IF.sub.FZ4 emitted by the vehicle FZ4 with the associated parameter data PD.sub.FZ4, Table-2-FIG. 3 shows the information IF.sub.FZ5 emitted by the vehicle FZ5 with the associated parameter data PD.sub.FZ5, Table-3-FIG. 3 shows the information IF.sub.FZ6 emitted by the vehicle FZ6 with the associated parameter data PD.sub.FZ6, Table-4-FIG. 3 shows the information IF.sub.FZ7 emitted by the vehicle FZ7 with the associated parameter data PD.sub.FZ7, Table-5-FIG. 3 shows the information IF.sub.FZ5 emitted by the vehicle FZ8 with the associated parameter data PD.sub.FZ8, Table-6-FIG. 3 shows the information IF.sub.FZ9 emitted by the vehicle FZ9 with the associated parameter data PD.sub.FZ9, and Table-7-FIG. 3 shows the information IF.sub.FZ10 emitted by the vehicle FZ10 with the associated parameter data PD.sub.FZ10.

    TABLE-US-00005 TABLE 1 FIG. 3 Information (IF.sub.FZ4, t1, IF.sub.FZ4, t2, IF.sub.FZ4, t3) emitted at times (t1, t2, t3) Information (IF.sub.FZ4) emitted by the vehicle (FZ4) with with parameter data (PD.sub.FZ4, t1, PD.sub.FZ4, t2, PD.sub.FZ4, t3) data relating to information parameters (PD.sub.FZ4) t1 t2 t3 (Pseudonymous) identifier ID =100555 (Pseudonymous) information certificate ID =Kv87xc34 Certificate authority =certauth212 Position (WGS84) =Lat: XX.xxx(t1)/ Lon: YY.yyy(t1) Time stamp =dd.MM.yyyy(t1)/ HH:mm:ss(t1) Type =Bus Direction of travel =west Speed =120 km/h Length =7.20 m Width =2.35 m Optional parameters =...

    TABLE-US-00006 TABLE 2 FIG. 3 Information (IF.sub.FZ5, t1, IF.sub.FZ5, t2, IF.sub.FZ5, t3) emitted at times (t1, t2, t3) Information (IF.sub.FZ5) emitted by the vehicle (FZ5) with with parameter data (PD.sub.FZ5, t1, PD.sub.FZ5, t2, PD.sub.FZ5, t3) data relating to information parameters (PD.sub.FZ5) t1 t2 t3 (Pseudonymous) identifier ID =15060607 (Pseudonymous) information certificate ID =Fr94Le97 Certificate authority =certauth358 Position (WGS84) =Lat: XX.xxx(t1)/ Lon: YY.yyy(t1) Time stamp =dd.MM.yyyy(t1)/ HH:mm:ss(t1) Type =Automobile Direction of travel =west Speed =124 km/h Length =3.55 m Width =1.90 m Optional parameters =...

    TABLE-US-00007 TABLE 3 FIG. 3 Information (IF.sub.FZ6, t1, IF.sub.FZ6, t2, IF.sub.FZ6, t3) emitted at times (t1, t2, t3) with Information (IF.sub.FZ6) emitted by the vehicle (FZ6) with parameter data (PD.sub.FZ6, t1, PD.sub.FZ6, t2, PD.sub.FZ6, t3) data relating to information parameters (PD.sub.FZ6) t1 t2 t3 (Pseudonymous) identifier ID =477300 =13579 =13579 (Pseudonymous) information certificate ID =6p248 =7my035 =7my035 Certificate authority =eurp4711 =eurp4711 =eurp4711 Position (WGS84) =Lat: XX.xxx(t1)/ =Lat: XX.xxx(t2)/ =Lat: XX.xxx(t3)/ Lon: YY.yyy(t1) Lon: YY.yyy(t2) Lon: YY.yyy(t3) Time stamp =dd.MM.yyyy(t1)/ =dd.MM.yyyy(t2)/ =dd.MM.yyyy(t3)/ HH:mm:ss(t1) HH:mm:ss(t2) HH:mm:ss(t3) Type =Automobile =Automobile =Automobile Direction of travel =west =west =west Speed =150 km/h =165 km/h =148 km/h Length =4.10 m =4.10 m =4.10 m Width =2.05 m =2.05 m =2.05 m Optional parameters =... =... =...

    TABLE-US-00008 TABLE 4 FIG. 3 Information (IF.sub.FZ7, t1, IF.sub.FZ7, t2, IF.sub.FZ7, t3) emitted at times (t1, t2, t3) with Information (IF.sub.FZ7) emitted by the vehicle (FZ7) with parameter data (PD.sub.FZ7, t1, PD.sub.FZ7, t2, PD.sub.FZ7, t3) data relating to information parameters (PD.sub.FZ7) t1 t2 t3 (Pseudonymous) identifier ID =94633 =382323 =998111 (Pseudonymous) information =QK92 =I85r3 =2m1073 certificate ID Certificate authority =eurp2700 =eurp2700 =eurp2700 Position (WGS84) =Lat: XX.xxx(t1)/ =Lat: XX.xxx(t2)/ =Lat: XX.xxx(t3)/ Lon: YY.yyy(t1) Lon: YY.yyy(t2) Lon: YY.yyy(t3) Time stamp =dd.MM.yyyy(t1)/ =dd.MM.yyyy(t2)/ =dd.MM.yyyy(t3)/ HH:mm:ss(t1) HH:mm:ss(t2) HH:mm:ss(t3) Type =Automobile =Automobile =Automobile Direction of travel =west =west =west Speed =153 km/h =168 km/h =153 km/h Length =4.40 m =4.40 m =4.40 m Width =2.15 m =2.15 m =2.15 m Optional parameters =... =... =...

    TABLE-US-00009 TABLE 5 FIG. 3 Information (IF.sub.FZ8, t2, IF.sub.FZ8, t3, IF.sub.FZ8, t3) emitted at times (t1, t2, t3) Information (IF.sub.FZ8) emitted by the vehicle (FZ8) with with parameter data (PD.sub.FZ8, t1, PD.sub.FZ8, t2, PD.sub.FZ8, t3) data relating to information parameters (PD.sub.FZ8) t1 t2 t3 (Pseudonymous) identifier ID =28112203 (Pseudonymous) information =Ho57Mo61 certificate ID Certificate authority =certauth358 Position (WGS84) =Lat: XX.xxx(t2)/ Lon: YY.yyy(t2) Time stamp =dd.MM.yyyy(t2)/ HH:mm:ss(t2) Type =Automobile Direction of travel =west Speed =126 km/h Length =3.70 m Width =1.95 m Optional parameters =...

    TABLE-US-00010 TABLE 6 FIG. 3 Information (IF.sub.FZ9, t1, IF.sub.FZ9, t2, IF.sub.FZ9, t3) emitted at times (t1, t2, t3) with Information (IF.sub.FZ9) emitted by the vehicle (FZ9) with parameter data (PD.sub.FZ9, t1, PD.sub.FZ9, t2, PD.sub.FZ9, t3) data relating to information parameters (PD.sub.FZ9) t1 t2 t3 (Pseudonymous) identifier ID =70608090 (Pseudonymous) information =Jw65yd23 certificate ID Certificate authority =certauth321 Position (WGS84) =Lat: XX.xxx(t3)/ Lon: YY.yyy(t3) Time stamp =dd.MM.yyyy(t3)/ HH:mm:ss(t3) Type =Bus Direction of travel =west Speed =118 km/h Length =7.50 m Width =2.30 m Optional parameters =...

    TABLE-US-00011 TABLE 7 FIG. 3 Information (IF.sub.FZ10, t1, IF.sub.FZ10, t2, IF.sub.FZ10, t3) emitted at times (t1, t2, t3) Information (IF.sub.FZ10) emitted by the vehicle (FZ10) with with parameter data (PD.sub.FZ10, t1, PD.sub.FZ10, t2, PD.sub.FZ10, t3) data relating to information parameters (PD.sub.FZ10) t1 t2 t3 (Pseudonymous) identifier ID =542684 (Pseudonymous) information =Hw57Sie86 certificate ID Certificate authority =eurp46668 Position (WGS84) =Lat: XX.xxx(t3)/ Lon: YY.yyy(t3) Time stamp =dd.MM.yyyy(t3)/ HH:mm:ss(t3) Type =Automobile Direction of travel =west Speed =122 km/h Length =3.45 m Width =1.90 m Optional parameters =...

    [0082] In the case of the information parameters contained in the tables and the parameter data PD.sub.FZ4 . . . PD.sub.FZ10 corresponding to the vehicle, a distinction is again made between

    (i) information parameters and associated parameter data PD.sub.FZ4 . . . PD.sub.FZ10 which are used to uniquely identify the respective information transmitting device ISE.sub.FZ4 . . . ISE.sub.FZ10 corresponding to the vehicle as the transmission source of the information IF.sub.FZ4 . . . IF.sub.FZ10 and therefore ultimately also the respective vehicle FZ4 . . . FZ10 and the data values of which, as already stated above, are continuously changed at regular intervals of time (for example in the region of approximately 1 minute) for anonymization purposes—these information parameters and parameter data PD.sub.FZ4 . . . PD.sub.FZ10 are referred to below as object-identifying information parameters and parameter data PD.sub.FZ4 . . . PD.sub.FZ10—and
    (ii) information parameters and associated parameter data PD.sub.FZ4 . . . PD.sub.FZ10 which are used to characterize, indicate, type, etc., but not uniquely identify, the respective vehicle FZ4 . . . FZ10 in which the information transmitting device ISE.sub.FZ4 . . . ISE.sub.FZ10 corresponding to the vehicle is situated as the transmission source of the information IF.sub.FZ4 . . . IF.sub.FZ10 and the data values of which are not changed—these information parameters and parameter data PD.sub.FZ4 . . . PD.sub.FZ10 are referred to below as non-object-identifying information parameters and parameter data PD.sub.FZ4 . . . PD.sub.FZ10.

    [0083] In said tables, Table-1-FIG. 3 to Table-7-FIG. 3, the object-identifying information parameters and parameter data PD.sub.FZ4 . . . PD.sub.FZ10 are again indicated with gray shading, whereas the non-object-identifying information parameters and parameter data PD.sub.FZ4 . . . PD.sub.FZ10 again do not have any background shading (for example with respect to a gray scale and/or pattern) (white background in said tables). Said tables each illustrate how the object-identifying parameter data PD.sub.FZ4 . . . PD.sub.FZ10 at the respective times t2, t3 have changed in comparison with the object-identifying parameter data PD.sub.FZ4 . . . PD.sub.FZ10 at the time t1.

    [0084] The number of information parameters (both with respect to the object-identifying parameters and with respect to the non-object-identifying parameters) respectively contained in the table is fundamentally open and can be increased or decreased in an arbitrary manner again as required. In the present case, the parameters decisive for the exemplary embodiment are stated. The meaning of these stated parameters and their data values are again generally known and therefore do not require any further explanation at this point. When selecting the parameters, it should again be taken into account (criteria catalog) that, for example, preferably [0085] different vehicle types of the road users, for example bus, automobile, motorcycle, etc., are captured; [0086] the time stamp of the captured vehicles belonging to the road users should be as close as possible in terms of time; [0087] the position of the captured different vehicles belonging to the road users should be as adjacent as possible; [0088] the direction of the captured vehicles belonging to the road users should be as identical as possible; [0089] the speed of the captured vehicles belonging to the road users should be as comparable as possible; [0090] the length of the captured different vehicles belonging to the road users should be used as a (group) identifying feature; [0091] the width of different vehicles belonging to the road users should be used as a (group) identifying feature; [0092] the issuing authority of the cryptographic certificates is used for the signature of the status messages; [0093] certificate hierarchy for validating the certificate is used for the signature of the status messages; [0094] repetition rate of the change of the parameters is used.

    [0095] If the vehicles FZ4, FZ5, FZ6, FZ7 in the first vehicle convoy having the information transmitting devices ISE.sub.FZ4, ISE.sub.FZ5, ISE.sub.FZ6, ISE.sub.FZ7 corresponding to the vehicle and emitting the information IF.sub.FZ4, IF.sub.FZ5, IF.sub.FZ6, IF.sub.FZ7 corresponding to the vehicle are in the first information capture region IEB1 of the first information capture device IEE1 of the modified first “roadside unit” RSU1, information IF.sub.FZ4,t1, IF.sub.FZ5,t1, IF.sub.FZ6,t1, IF.sub.FZ7,t1 emitted by the information transmitting devices ISE.sub.FZ4, ISE.sub.FZ5, ISE.sub.FZ6, ISE.sub.FZ7 of the vehicles FZ4, FZ5, FZ6, FZ7 at the time t1 is captured by the first information capture device IEE1 with parameter data PD.sub.FZ4,t1, PD.sub.FZ5,t1, PD.sub.FZ6,t1, PD.sub.FZ7,t1. In a similar manner to the information capture region IEB in FIG. 1, the first information capture region IEB1 again reaches its maximum extent when the information IF.sub.FZ4, IF.sub.FZ5, IF.sub.FZ6, IF.sub.FZ7 emitted by the information transmitting device ISE.sub.FZ4, ISE.sub.FZ5, ISE.sub.FZ6, ISE.sub.FZ7 can no longer be received by the first information capture device IEE1.

    [0096] In order to also be able to now again track at least one vehicle in the first vehicle convoy FZ4, FZ5, FZ6, FZ7 in the second expanded cooperative ITS scenario, in contrast to the cooperative ITS scenario explained above on the basis of FIG. 1, the first information IF1 with the first parameter data PD1 from the maximum quantity of information predefined at the time t1 by the information IF.sub.FZ4,t1, IF.sub.FZ5,t1, IF.sub.FZ6,t1, IF.sub.FZ7,t1 with the parameter data PD.sub.FZ4,t1, PD.sub.FZ5,t1, PD.sub.FZ6,t1, PD.sub.FL7,t1 is captured from a first group GR1 of the vehicles FZ6, FZ7 in the first vehicle convoy FZ4, FZ5, FZ6, FZ7, which comprises at least one vehicle, but preferably a plurality of vehicles with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”. When taking into account or stipulating the number of vehicles in the first group GR1, the criteria catalog mentioned above should be used when selecting the parameters.

    [0097] In the present case, at the time t1 according to FIG. 3, the two vehicles FZ6, FZ7 form the first group GR1 because, even though the vehicle type is also the same here contrary to the criteria catalog, for example, the speed of said vehicles is comparable and the prerequisite that the time stamps of said vehicles are close in terms of time and the position of the captured vehicles is adjacent is present (as illustrated in principle in FIG. 3). The information IF.sub.FZ6,t1, IF.sub.FZ7,t1 emitted by the vehicles FZ6, FZ7 at the time t1 with the parameter data PD.sub.FZ6,t1, PD.sub.FZ7,t1 is the first information IF1 with the first parameter data PD1 as a result of the capture affiliation of said vehicles to the first group GR1 at the time t1.

    [0098] For the further performance of the tracking, the first information capture device IEE1 is now again designed, preferably using generally conventional data processing means (for example a hardware unit based on a microprocessor and a memory component and program modules which can be operated and executed as software on the hardware unit), in such a manner that the data profile DP.sub.GR1 specific to the first group, in particular the group footprint or the group stamp of the vehicle group, is again generated from the captured first parameter data PD1.

    [0099] This data profile DP.sub.GR1 specific to the first group is then again forwarded in the modified first “roadside unit” RSU1 from the first information capture device IEE1 to the first communication interface KSS1 which is connected to the first information capture device IEE1 and provides the data profile DP.sub.GR1 specific to the first group and received from the first information capture device IEE1 for data evaluation based on a similarity comparison of data profiles. How, when and where this data profile similarity comparison takes place is explained further below in connection with the description of FIG. 3.

    [0100] In the interim, while the first data profile is generated and forwarded as described, the first vehicle convoy FZ4, FZ5, FZ6, FZ7 moves further along the second tracking route SVS2 on the road or the freeway VKS. Since the vehicles FZ4, FZ5, FZ6, FZ7 in the convoy are moving at a different speed, however, the first vehicle convoy will come apart along the second tracking route SVS2 and will be reduced to the vehicles at a comparable speed. These are the vehicles FZ6, FZ7 which, as a sub-convoy of the first vehicle convoy, form the first group GR1. It can therefore be assumed that, if one of these vehicles does not leave the road or the freeway VKS—for example for a stop at a gas station or a rest area or else to continue the journey on another road—or one of the vehicles does not inevitably leave the convoy as a result of a vehicle defect, for example engine damage, and does not drive at the edge of the road (on the shoulder in the case of the freeway) and stop, the vehicle sub-convoy is also still moving together on the road or the freeway VKS along the second tracking route SVS2.

    [0101] In the second expanded cooperative ITS scenario illustrated in FIG. 3, in addition to the capture time t1, there is also at least one further time or a further point, the capture time t2 with the modified second “roadside unit” RSU2 and the capture time t3 with the modified second “roadside unit” RSU3, for tracking the at least one vehicle in the vehicle sub-convoy FZ6, FZ7 along the second tracking route SVS2.

    [0102] If the sub-convoy with the vehicles FZ6, FZ7 now approaches the second “roadside unit” RSU2 and if, in addition to the two vehicles FZ6, FZ7 mentioned, also the vehicle FZ8 having the information transmitting devices ISE.sub.FZ6, ISE.sub.FZ7, ISE.sub.FZ8 corresponding to the vehicle and emitting the information IF.sub.FZ6, IF.sub.FZ7, IF.sub.FZ5 corresponding to the vehicle are finally in the second information capture region IEB2 of the second information capture device IEE2 of the second “roadside unit” RSU2 for the second vehicle convoy, information IF.sub.FZ6,t2, IF.sub.FZ7,t2, IF.sub.FZ8,t2 emitted by the information transmitting devices ISE.sub.FZ6, ISE.sub.FZ7, ISE.sub.FZ8 of the vehicles FZ6, FZ7, FZ8 at the time t2 is captured by the second information capture device IEE2 with parameter data PD.sub.FZ6,t2, PD.sub.FZ7,t2, PD.sub.FZ8,t2. The “roadside units” RSU1, RSU2 with the two information capture regions IEB1, IEB2 are again arranged in a manner separated from one another by an arbitrarily selectable distance. In a similar manner to the information capture region IEB in FIG. 1 and the first information capture region IEB1, the second information capture region IEB2 also again reaches its maximum extent when the information IF.sub.FZ6, IF.sub.FZ7, IF.sub.FZ8 emitted by the information transmitting device ISE.sub.FZ6, ISE.sub.FZ7, ISE.sub.FZ8 can no longer be received by the second information capture device IEE2.

    [0103] Like the first information capture device IEE1, the second information capture device IEE2 again captures second information IF2 with second parameter data PD2 from the maximum quantity of information predefined at the time t2 by the information IF.sub.FZ6,t2, IF.sub.FZ7,t2, IF.sub.FZ8,t2 with the parameter data PD.sub.FZ6,t2, PD.sub.FZ7,t2, PD.sub.FZ8,t2 from a second group GR2 of the vehicles FZ6, FZ7 in the second vehicle convoy FZ6, FZ7, FZ8, which again comprises at least one vehicle, but preferably again a plurality of vehicles with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”, at regular intervals of time or for a calculated time window—for example by means of the calculation according to the formula s=v*t (distance equals speed times time), where s=distance between RSU1 and RSU2 and v=speed of the vehicle convoy according to the tables (cf. Table-1-FIG. 3 to Table-7-FIG. 3), the time t and by considering “±t” to be the time window—after capturing the first vehicle group GR1 in the first information capture region IEB1 for each interval of time or for each time window. When taking into account or stipulating the number of vehicles in the second group GR2, said criteria catalog should again be used when selecting the parameters.

    [0104] In the present case, at the time t2 according to FIG. 3, the two vehicles FZ6, FZ7 also form the second group GR2 because, even though the vehicle type is the same contrary to the criteria catalog, for example, the speed of said vehicles is comparable and the prerequisite that the time stamps of said vehicles are close in terms of time and the position of the captured vehicles is adjacent is present (as illustrated in principle in FIG. 3). The information IF.sub.FZ6,t2, IF.sub.FZ7,t2 emitted by the vehicles FZ6, FZ7 at the time t2 with the parameter data PD.sub.FZ6,t2, PD.sub.FZ7,t2 is the second information IF2 with the second parameter data PD2 as a result of the capture affiliation of said vehicles to the second group GR2 at the time t2.

    [0105] During the further performance of the tracking, the second information capture device IEE2—like the first information capture device IEE1—is again designed, preferably again using generally conventional data processing means (for example a hardware unit based on a microprocessor and a memory component and program modules which can be operated and executed as software on the hardware unit), in such a manner that the data profile DP.sub.GR2 specific to the second group, in particular the group footprint or the group stamp of the vehicle group, is generated from the captured second parameter data PD2.

    [0106] This data profile DP.sub.GR2 specific to the second group is then again forwarded in the modified second “roadside unit” RSU2 from the second information capture device IEE2 to the second communication interface KSS2 which is connected to the second information capture device IEE2 and provides the data profile DP.sub.GR2 specific to the second group and received from the second information capture device IEE2 for data evaluation based on a similarity comparison of data profiles.

    [0107] With respect to the expanded cooperative ITS scenario, illustrated in FIG. 3, for tracking the at least one vehicle in the vehicle sub-convoy FZ6, FZ7 along the second tracking route SVS2, there is now also the capture time t3 with the modified second “roadside unit” RSU3.

    [0108] If the sub-convoy having the vehicles FZ6, FZ7 now approaches the third “roadside unit” RSU3 and if, in addition to these two vehicles FZ6, FZ7, also the vehicles FZ9, FZ10 having the information transmitting devices ISE.sub.FZ6, ISE.sub.FZ7, ISE.sub.FZ9, ISE.sub.FZ10 corresponding to the vehicle and emitting the information IF.sub.FZ6, IF.sub.FZ7, IF.sub.FZ9, IF.sub.FZ10 corresponding to the vehicle are finally in a third information capture region IEB3 of a third information capture device IEE3 of the third “roadside unit” RSU3 for the third vehicle convoy, information IF.sub.FZ6,t3, IF.sub.FZ7,t3, IF.sub.FZ9,t3, IF.sub.FZ10,t3 emitted by the information transmitting devices ISE.sub.FZ6, ISE.sub.FZ7, ISE.sub.FZ9, ISE.sub.FZ10 of the vehicles FZ6, FZ7, FZ9, FZ10 at the time t3 is captured by the third information capture device IEE3 with parameter data PD.sub.FZ6,t3, PD.sub.FZ7,t3, PD.sub.FZ9,t3, PD.sub.FZ10,t3.

    [0109] Since the vehicle tracking is based on a similarity comparison and the data captured at two measurement points are always compared with one another for this purpose, the third information capture region IEB3 with the third information capture device IEE3 with respect to this comparison is a further second information capture region IEB2 with a further second information capture device IEE2 which captures further second information IF2 with further second parameter data PD2 for a further second group GR2 of vehicles. Against this background, the following statements which relate to the capture of information at the third time t3 should be categorized.

    [0110] The “roadside units” RSU1, RSU2, RSU3 with the respective two information capture regions IEB1, IEB2 are again arranged in a manner separated from one another by an arbitrarily selectable distance. In a similar manner to the information capture region IEB in FIG. 1, the first information capture region IEB1 and the second information capture region IEB2, the further second information capture region IEB2 (IEB3) again also reaches its maximum extent when the information IF.sub.FZ6, IF.sub.FZ7, IF.sub.FZ9, IF.sub.FZ10 emitted by the information transmitting device ISE.sub.FZ6, ISE.sub.FZ7, ISE.sub.FZ9, ISE.sub.FZ10 can no longer be received by the further second information capture device IEE2 (IEE3).

    [0111] Like the first information capture device IEE1 and the second information capture device IEE2, the further second information capture device IEE2 again captures further second information IF2 with further second parameter data PD2 from the maximum quantity of information predefined at the time t3 by the information IF.sub.FZ6,t3, IF.sub.FZ7,t3, IF.sub.FZ10,t3, IF.sub.FZ9,t3 with the parameter data PD.sub.FZ6,t3, PD.sub.FZ7,t3, PD.sub.FZ9,t3, PD.sub.FZ10,t3 from a further second group GR2 of the vehicles FZ6, FZ7 in the third vehicle convoy FZ6, FZ7, FZ9, FZ10, which again comprises at least one vehicle, but preferably again a plurality of vehicles with the proviso “The greater the number of groups, the easier the correlation of the different parameter data from the information capture region”, at regular intervals of time or for a calculated time window—for example by means of the calculation according to the formula s=v*t (distance equals speed times time), where s=distance between RSU1 and RSU2 and v=speed of the vehicle convoy according to the tables (cf. Table-1-FIG. 3 to Table-7-FIG. 3), the time t and by considering “±t” to be the time window—after capturing the first vehicle group GR1 in the first information capture region IEB1 for each interval of time or for each time window. When taking into account or stipulating the number of vehicles in the further second group GR2, said criteria catalog should again be used when selecting the parameters.

    [0112] In the present case, at the time t3 according to FIG. 3, the two vehicles FZ6, FZ7 also form the further second group GR2 because, even though the vehicle type is the same contrary to the criteria catalog, for example, the speed of said vehicles is still comparable and the prerequisite that the time stamps of said vehicles are close in terms of time and the position of the captured vehicles is adjacent is present (as illustrated in principle in FIG. 3). The information IF.sub.FZ6,t3, IF.sub.FZ7,t3 emitted by the vehicles FZ6, FZ7 at the time t3 with the parameter data PD.sub.FZ6,t3, PD.sub.FZ7,t3 is the further second information IF2 with the further second parameter data PD2 as a result of the capture affiliation of said vehicles to the further second group GR2 at the time t3.

    [0113] During the further performance of the tracking, the further second information capture device IEE2—like the first information capture device IEE1 and the second information capture device IEE2—is also again designed, preferably again using generally conventional data processing means (for example a hardware unit based on a microprocessor and a memory component and program modules which can be operated and executed as software on the hardware unit), in such a manner that the further data profile DP.sub.GR2 specific to the second group, in particular the group footprint or the group stamp of the vehicle group, is generated from the captured further second parameter data PD2.

    [0114] This further data profile DP.sub.GR2 specific to the second group is then again forwarded in the modified third “roadside unit” RSU3 from the further second information capture device IEE2 to a third communication interface KSS3 which, by definition, is a further second communication interface KSS2 which is connected to the further second information capture device IEE2 and provides the further data profile DP.sub.GR2 specific to the second group and received from the further second information capture device IEE2 for data evaluation based on a similarity comparison of data profiles.

    [0115] Before it is now stated what happens then with the two data profiles DP.sub.GR2, DP.sub.GR1, it is noted at this point that, as an alternative to the second information capture region IEB2 described above at the time t2, the further second information capture region IEB3 at the time t3, with the modifications described above, can be used to generate the data profile DP.sub.GR2 specific to the second group.

    [0116] In addition, it is also possible (in a modification of the previous description in which the first information capture region IEB1 is present at the time t1 and the second information capture region IEB2 is present at the time t2) for the first information capture region IEB1 to be used at the time t2 to generate the data profile DP.sub.GR1 specific to the first group and for the second information capture region IEB2 to be used at the time t3 to generate the data profile DP.sub.GR2 specific to the second group with the corresponding modifications resulting from FIG. 3.

    [0117] Irrespective of what is captured at what time, there are now two comparable variables, the two data profiles DP.sub.GR1, DP.sub.GR2, for the data profile similarity comparison discussed. If this data profile similarity comparison is now intended to be carried out in a decentralized manner, that is to say locally, in contrast to the situation according to FIG. 2, there are two options provided that a central unit in the form of an evaluation device AWE is included in the first “roadside unit” RSU1, in the second “roadside unit” RSU2 and in the third “roadside unit” RSU3 for the data profile similarity comparison to be carried out.

    [0118] One option is for the first data profile DP.sub.GR1 to be transmitted, via the first communication interface KSS1 in the first “roadside unit” RSU1, to the second communication interface KSS2 in the second “roadside unit” RSU2 or to the further second communication interface KSS2 in the third “roadside unit” RSU3 by means of a wireless or wired connection, for example, and for the second communication interface KSS2 in the second “roadside unit” RSU2 to then supply the two data profiles DP.sub.GR1, DP.sub.GR2 to the evaluation device AWE in the second “roadside unit” RSU2 for the data profile similarity comparison to be carried out or else for the further second communication interface KSS2 in the third “roadside unit” RSU3 to then supply the two data profiles DP.sub.GR1, DP.sub.GR2 to the evaluation device AWE in the third “roadside unit” RSU3 for the data profile similarity comparison to be carried out.

    [0119] The other option is for the second data profile DP.sub.GR2 to be transmitted, via the second communication interface KSS2 in the second “roadside unit” RSU2, or else for the further second data profile DP.sub.GR2 to be transmitted, via the further second communication interface KSS2 in the third “roadside unit” RSU3, to the first communication interface KSS1 in the first “roadside unit” RSU1 in each case via a wireless or wired connection, for example, and for the first communication interface KSS1 to then supply the two data profiles DP.sub.GR1, DP.sub.GR2 to the evaluation device AWE in the first “roadside unit” RSU1 for the data profile similarity comparison to be carried out.

    [0120] Irrespective of which option ultimately takes effect, the evaluation device AWE is again designed, preferably again using generally conventional means for the data-processing-based comparison of two variables (for example a hardware unit based on a microprocessor and a memory component and program modules which can be operated and executed as software on the hardware unit), for carrying out the data profile similarity comparison in such a manner that the provided data profile DP.sub.GR2 specific to the second group is compared with the provided data profile DP.sub.GR1 specific to the first group using parameter data, in particular from a combination of the parameter data PD1, PD2 within the groups GR1, GR2.

    [0121] If the data profile similarity comparison carried out in the evaluation device AWE again reveals that the correlation between the first parameter data PD1 and the second parameter data PD2 is so great that the parameter data PD1, PD2 at least partially correspond, a statement can be made on the successful tracking of the vehicles FZ1, FZ2, FZ3 captured in the first group GR1 along the first tracking route SVS1 between the two information capture regions IEB1, IEB2. In this case, the respective evaluation device AWE in the first “roadside unit” RSU1, in the second “roadside unit” RSU2 or in the third “roadside unit” RSU3 produces or generates the tracking information SVI and forwards this information to the central monitoring entity ZÜI which is preferably in the form of a traffic control center and to which the evaluation device AWE is connected, for example in a wireless or wired manner. Otherwise, if the correspondence between the parameter data PD1, PD2 is not so great, such a statement is not possible and the tracking information SVI is not generated.

    [0122] The tracking information SVI can then again preferably be used in the traffic control center or the central monitoring entity ZÜI to broadcast traffic messages or can be used for cooperative ITS traffic systems or traffic telematics systems.

    [0123] On the basis of the expanded cooperative ITS scenario for tracking according to FIG. 2, FIG. 4 shows the influence of dynamically changing affiliations of nine vehicles FZ01 . . . FZ09—a first vehicle FZ01, a second vehicle FZ02, a third vehicle FZ03, a fourth vehicle FZ04, a fifth vehicle FZ05, a sixth vehicle FZ06, a seventh vehicle FZ07, an eighth vehicle FZ08 and a ninth vehicle FZ09—driving on the route or the freeway VKS in the direction of movement BWR to the first group GR1 with respect to the first “roadside unit” with the first information capture region IEB1.sub.RSU1 and to the second group GR2 with respect to the second “roadside unit” with the second information capture region IEB2.sub.RSU2 on the similarity comparison (correlation check) to be carried out during the vehicle tracking according to FIG. 2.

    [0124] With respect to the first “roadside unit” with the first information capture region IEB1.sub.RSU1, the vehicles FZ5, FZ6, FZ8, FZ9 belong to the first group GR1 at an nth time t.sub.n, the vehicles FZ2, FZ4, FZ5, FZ6, FZ7 belong to the first group GR1 at an (n+1)th time t.sub.n+1, and the vehicles FZ1, FZ2, FZ3, FZ4 belong to the first group GR1 at an (n+2)th time t.sub.n+2.

    [0125] With respect to the second “roadside unit” with the second information capture region IEB2.sub.RSU2, the vehicles FZ6, FZ7, FZ8 belong to the second group GR2 at an mth time t.sub.m, and the vehicles FZ2, FZ4, FZ5, FZ7 belong to the second group GR2 at an (m+1)th time t.sub.m+1.

    [0126] If the correlation check between the first group GR1 and the second group GR2 is now carried out at the respective times, the following correlation values KW result:

    GR1(t.SUB.n.)=FZ5, FZ6, FZ8, FZ9

    [0127] with}=>KW=50%

    GR2(t.SUB.m.)=FZ6, FZ7, FZ8

    GR1(t.SUB.n.)=FZ5, FZ6, FZ8, FZ9

    [0128] with}=>KW=25%

    GR2(t.SUB.m+1.)=FZ2, FZ4, FZ5, FZ7

    GR1(t.SUB.n+1.)=FZ2, FZ4, FZ5, FZ6, FZ7

    [0129] with}=>KW=40%

    GR2(t.SUB.m.)=FZ6, FZ7, FZ8

    GR1(t.SUB.n+1.)=FZ2, FZ4, FZ5, FZ6, FZ7

    [0130] with}=>KW=80%

    GR2(t.SUB.m+1.)=FZ2, FZ4, FZ5, FZ7

    GR1(t.SUB.n+2.)=FZ1, FZ2, FZ3, FZ4

    [0131] with}=>KW=0%

    GR2(t.SUB.m.)=FZ6, FZ7, FZ8

    GR1(t.SUB.n+2.)=FZ1, FZ2, FZ3, FZ4

    [0132] with}=>KW=50%

    GR2(t.SUB.m+1.)=FZ2, FZ4, FZ5, FZ7

    [0133] Although the invention has been illustrated and described in greater detail with reference to the preferred exemplary embodiment, the invention is not limited to the examples disclosed, and further variations can be inferred by a person skilled in the art, without departing from the scope of protection of the invention.

    [0134] For the sake of clarity, it is to be understood that the use of “a” or “an” throughout this application does not exclude a plurality, and “comprising” does not exclude other steps or elements.