EP3871134A1

EP3871134A1 - Method and device for testing a driver assistance system

Info

Publication number: EP3871134A1
Application number: EP19797196.3A
Authority: EP
Inventors: Emre Kaplan; Andrea LEITNER; Ahmetcan ERDOGAN; Markus NAGER
Original assignee: AVL List GmbH
Current assignee: AVL List GmbH
Priority date: 2018-10-24
Filing date: 2019-10-23
Publication date: 2021-09-01
Also published as: CN113168524A; KR20210078546A; AT521607B1; US20220048536A1; JP2022505759A; AT521607A4; WO2020083996A1; CN113168524B

Abstract

The invention relates to a method and to a device for testing a driver assistance system for a vehicle in a test environment. Traffic scenario descriptions are determined, which each characterize a certain traffic scenario and comprise at least one parameter, by means of which the traffic scenario in question can be adapted to constraints. The traffic scenario descriptions are stored in a traffic scenario file, in which the at least one parameter is stored in a predefined format. At least one traffic scenario description is selected on the basis of an input of a user and/or specified criteria. Furthermore, a test case is produced on the basis of the at least one selected traffic scenario description and at least one specified value for the at least one parameter. The test case corresponds to a specific realization of the traffic scenario characterized by the at least one selected traffic scenario description, with respect to the at least one specified value of the at least one parameter, and is suitable for producing a test environment in which a driver assistance system can be subjected to a test run. A test run can be carried out using the produced test case.

Description

METHOD AND DEVICE FOR TESTING ONE

DRIVER ASSISTANCE SYSTEM

The present invention relates to a method and a device for testing a driver assistance system for a vehicle in a test environment.

Modern vehicles are increasingly equipped with advanced driver assistance systems (ADAS), which support the driver in certain driving situations. Support ranges from the mere display of possibly relevant information (e.g. issuing a warning by a lane change assistant) to semi-autonomous interventions (e.g. regulation of the torque applied to the wheel axles by an anti-lock braking system) to fully autonomous interventions in the control of the vehicle (e.g. adaptive cruise control) thanks to an adaptive cruise control (ACC).

As a rule, the basis for such driver assistance systems is formed by sensor data, for example provided signals from ultrasound sensors, radar sensors or cameras, which can be used to determine the current driving situation and in response to this the function of the respective driver assistance system can be carried out. Particularly with driver assistance systems that (autonomously) intervene in the control of the vehicle, the current driving situation must be able to be classified in a highly reliable manner using the sensor data.

In general, certain rules or criteria associated with a driving situation are set up, and if they are fulfilled, it can be concluded that a known driving situation exists. Fulfilling the rule or criteria acts, for example, as a trigger for an action by the driver assistance system. For example, a traffic scenario in which a neighboring vehicle in front of the vehicle equipped with the driver assistance system (EGO vehicle) can cut into the same lane can be recognized by the fact that a sensor-detected transverse distance decreases perpendicular to the direction of travel to the neighboring vehicle and finally, at least essentially, assumes the value 0 if the neighboring vehicle is immediately in front of the EGO vehicle. In order to test such driver assistance systems, in particular their reaction in already known traffic scenarios, classified sensor data are generally provided with respect to a known traffic scenario and the driver assistance system to be tested is fed with these classified sensor data. In order to test the driver assistance system reliably, a large number of sensor data, which may also characterize slight variations in the traffic scenario, are generally required.

For this purpose, WO 2017/210222 A1 discloses the automatic generation of simulation scenarios for validating a driver assistance system. A large number of such simulation scenarios can be generated in particular by varying recorded scenarios, the variations being based on a data stream which is generated by isolating differences between similar recorded scenarios.

It is an object of the present invention to further improve the testing of driver assistance systems, in particular to simplify and / or make them more flexible.

This object is achieved by a method and a device for testing a driver assistance system for a vehicle in a test environment in accordance with the independent claims. Advantageous embodiments of the invention are the subject of the dependent claims.

A first aspect of the invention relates to a, in particular computer-aided, method for testing a driver assistance system for a vehicle in a test environment, comprising the following working steps: (i) determining traffic scenario descriptions, each of which describes a specific traffic scenario, in particular a cut-in maneuver or a cut-out maneuver, characterize and have at least one parameter by means of which the respective traffic scenario can be adapted to boundary conditions, the traffic scenario descriptions preferably, in particular in each case, being stored in a traffic scenario file in which the at least one parameter is stored in a predetermined, in particular generic, format; (ii) Selecting at least one traffic scenario description based on an input by a user, in particular an indication of the at least one parameter or at least one value or entered by the user Range of values for the at least one parameter and / or of predetermined criteria; and (iii) generating a test case on the basis of the at least one selected traffic scenario description and at least one predetermined value, in particular entered by the user, for the at least one parameter and preferably further traffic scenario descriptions, the test case having a concrete implementation of the traffic scenario characterized by the at least one selected traffic scenario description and preferably further traffic scenarios in relation to the at least one predetermined value of the at least one parameter corresponds and is suitable for generating a test environment in which a driver assistance system can be subjected to a test run.

A boundary condition in the sense of the invention is, in particular, a traffic situation, weather, an initial speed of the vehicle with the driver assistance system to be tested (hereinafter: test vehicle) and / or other road users, a road geometry or a course of the road, a distance from the test vehicle one or more other road users, a configuration of the test vehicle and / or other road users such as a load, for example a trailer, and / or the like. A boundary condition can in particular be any conceivable factor that influences the control of the vehicle equipped with the driver assistance system by the driver assistance system.

A test case in the sense of the invention is in particular a script, e.g. a sequence of actions by road users, which enables testing of a driver assistance system. A test case can be, for example, a script, on the basis of which a simulation for testing the driver assistance system can be carried out.

A test environment in the sense of the invention is, in particular, the content of a simulation that generates a concrete (virtual) implementation of a traffic scenario. In other words, a test environment can be, for example, a simulated environment of the test vehicle, in which at least other road users, possibly also the test vehicle itself, move in a predefined manner, in particular carry out predetermined actions. A predetermined format in the sense of the invention is in particular a predefined (data) structure. A predetermined format can, for example, correspond to a certain scheme, for example a certain arrangement or sequence of several parameters and / or a certain coding of the at least one parameter in the traffic scenario file. It is conceivable, for example, that several parameters are stored in a table, in particular in a two- or three-dimensional, possibly also multidimensional, matrix.

Determining traffic scenario descriptions within the meaning of the invention is in particular capturing, e.g. when performing real or simulated tests. Determining traffic scenario descriptions can also be reading in, e.g. from databases and / or the like.

The invention is based in particular on the approach to select at least one traffic scenario description from preferably a plurality of traffic scenario descriptions, each characterizing a particular traffic scenario and preferably in a predetermined, in particular generic, format, and on the basis thereof at least one test case to generate a test environment that is suitable for testing a driver assistance system. The traffic scenarios characterized by the traffic scenario descriptions preferably correspond to specific traffic scenarios such as cut-in maneuvers (single-maneuvers) or a cut-out maneuvers (maneuvering out). The traffic scenario descriptions preferably describe the respective traffic scenario in a general, generic form, however, without the traffic scenario descriptions specifying a specific execution of these maneuvers. The test case, on the other hand, preferably corresponds to a concrete implementation of the traffic scenario, which is characterized by the at least one selected description of the traffic scenario.

Both the at least one traffic scenario description can be selected on the basis of a user input, for example by specifying at least one parameter or entered values or value ranges for one or more parameters which adapt, in particular, define boundary conditions of the traffic scenarios, and the at least one test case who has at least one selected traffic scenario description are generated. The parameters can serve, for example, as variables in the traffic scenarios.

For example, the user can input that the test vehicle, i.e. the vehicle equipped with the driver assistance system, drives straight ahead in a first lane at a speed selected by the user and is overtaken by another vehicle in an adjacent second lane, the other vehicle being in the first lane at a distance selected by the user from the test vehicle reevers. Based on these inputs, a database with traffic scenario files stored therein, which contain the traffic scenario descriptions in the specified format, can be searched in the following in order to select traffic scenario descriptions with which the specific traffic scenario characterized by the user input can be implemented. The parameters and / or boundary conditions entered by the user can then, like values in a mathematical function, be inserted into the at least one selected traffic scenario description in order to generate at least one test case with which a simulation is carried out and the driver assistance system is thereby tested can be.

Because at least one traffic scenario description, in particular from a large number of traffic scenario descriptions, can be selected by the user input, it is possible to dispense with a possibly complex, scenario- or maneuver-specific preparation of data records for generating test environments. According to the invention, test runs for testing a driver assistance system can therefore be carried out particularly easily and quickly and / or in large numbers. In particular, because the traffic scenario descriptions can be stored in a predetermined, preferably generic, format, access to a wide range of traffic scenarios is made possible.

Overall, the invention makes it possible to further improve the testing of driver assistance systems, in particular to simplify them and / or to make them more flexible.

Preferred embodiments of the invention and their further developments are described below, each of which, unless expressly excluded, can be combined as desired with one another and with the aspects of the invention described below.

In a preferred embodiment, the method further comprises the following step: performing a test run using the test case generated. As a result, the driver assistance system can be tested in a reliable manner, in particular on the basis of a specifically adapted traffic scenario.

In a further preferred embodiment, the method also has the following work steps: (i) determining at least one data set which characterizes at least one, in particular real, traffic scenario; and (ii) identifying at least one parameter in the at least one determined data set, by means of which the respective traffic scenario can be adapted to boundary conditions, in particular an initial speed of an EGO vehicle, to which the traffic scenario relates. An EGO vehicle in the sense of the invention is in particular a vehicle from the point of view of which the, in particular real, traffic scenario is running.

The identification of at least one parameter in the at least one data record allows, in a particularly reliable manner, subsequently to select at least one traffic scenario description from a multiplicity of traffic scenario descriptions based on the user input. In particular, at least one traffic scenario can thus be selected based on the identified parameter, e.g. all traffic scenario descriptions that characterize a traffic scenario corresponding to a determined data set and therefore also have the identified parameter. In other words, the number of possible traffic scenarios relevant for testing the driver assistance system can be increased in this way.

The at least one data record is preferably determined on the basis of a sensor data stream that is generated, for example, by a sensor device for detecting the (real) vehicle environment of the EGO vehicle, in particular extracted from the sensor data stream. The sensor data stream can be processed, for example, in such a way that the vehicle environment of the EGO vehicle is classified, that is to say, for example, objects such as other road users, traffic signs, obstacles and / or the like are identified and labeled. The at least one data record can then be generated from the processed sensor data stream. With In other words, the at least one determined data record is preferably based on prepared sensor data that was generated when a real vehicle environment was detected and that contains additional meta information, ie information derived from raw data and therefore going beyond the pure physical information contained in the sensor data stream. This meta information in particular allows the identification of the at least one parameter, by means of which the respective traffic scenario can be adapted to boundary conditions.

In a further preferred embodiment, the identification of the at least one parameter is carried out by means of a comparison of a classified vehicle environment in chronologically successive scenes of the at least one traffic scenario characterized by the at least one determined data record. A classified vehicle environment in the sense of the invention is in particular a description of the vehicle environment of a vehicle that goes beyond pure physical information. The classified vehicle environment, which is preferably characterized by the data set provided, can in particular contain meta information which makes the classified vehicle environment comparable at different times. The classified vehicle environment preferably contains meta information, on the basis of which in individual scenes of the at least one traffic scenario characterized and characterized by the at least one determined data record, objects can be identified and labeled, e.g. whose positions, their speed, their configuration and / or the like are comparable to one another in the successive scenes. As a result, the at least one parameter can be identified in a particularly reliable and / or automated manner.

The states of the elements of the vehicle environment, ie, for example, the objects identified in the vehicle environment, such as other road users, are preferably derived from the classified vehicle environment in each scene of the at least one traffic scenario characterized by the at least one determined data set and compared with one another in chronologically successive scenes , especially subtracted from each other. A state of an element of the vehicle environment in the sense of the invention contains in particular at least one physical variable that characterizes the element, in particular relative to the EGO vehicle, for example the speed of the element, the position of the element, the configuration of the element and / or similar. If the state of an element changes in the successive scenes, the at least one parameter is preferably identified as the physical variable that causes the change in the state. As a result, the at least one parameter can be identified particularly easily.

For example, the speed and size of another road user can be taken from the classified vehicle environment in a first scene and compared with the speed or size of this road user in a subsequent second scene. The speed of the road user will usually change in the course of the traffic scenario and can therefore be identified as a parameter. In contrast, the size of the road user usually does not change and is therefore not identified as a parameter.

In a further preferred embodiment, the method further comprises the following step: generating at least one traffic scenario description on the basis of the determined data record or the determined data records, the traffic scenario description characterizing the determined traffic scenario and the at least one identified parameter in the predetermined format is filed. The storage of the at least one identified parameter in the specific format, in particular in a traffic scenario file, corresponds in a preferred manner to the generation of a standardized format or a standardized traffic scenario description. In other words, by storing the at least one identified parameter in the specific format, a standardized definition of the at least one corresponding traffic scenario, which is characterized by the at least one determined data record, is stored. The at least one data record extracted from a sensor data stream can thereby be provided in particular in a generic form as a description of the traffic scenario and subsequently selected to generate at least one test case.

In a further preferred embodiment, the method also has the following work step: storing the generated traffic scenario description, in particular the traffic scenario file, in a traffic scenario database, wherein further traffic scenario files are also stored in the traffic scenario database. This traffic scenario database is preferably set up as a No-SQL database and contains a standardized definition of the at least one link. reverse scenarios that are characterized by the at least one determined data set. By storing the generated traffic scenario description in the database, the generation of test cases can be based on a large number of, in particular real, traffic scenarios.

In a further preferred embodiment, the method further comprises at least one of the following work steps: (i) determining the predetermined values from a test run database; and / or (ii) determining the predetermined values from a user input, in particular via a user interface. For example, at least one value or range of values for the at least one parameter, which e.g. has proven to be useful in previous tests of a driver assistance system, read from the test run database and used to generate the at least one test case. Alternatively or additionally, a user can specify at least one value or range of values for the at least one parameter when inputting a user, in particular when inputting to select at least one traffic scenario description. As a result, test cases can be generated automatically and quickly and / or the user can be given a high degree of control over the generation of the test cases and thus over the checking of the driver assistance system.

A second aspect of the invention relates to a device for testing a driver assistance system for a vehicle in a test environment, which has a means for determining traffic scenario descriptions, wherein the traffic scenario descriptions preferably each have a specific traffic scenario, in particular a cut-in maneuver or a cut-out maneuver, characterize it and have at least one parameter by means of which the respective traffic scenario can be adapted to boundary conditions. The means for determining traffic scenario descriptions is also preferably set up to store the traffic scenario descriptions, in particular in each case, in a traffic scenario file in which the at least one parameter is stored in a predetermined, in particular generic, format. The means for determining traffic scenario descriptions can in particular be set up as an interface or sensor device. In addition, the device preferably has a means for selecting at least one traffic scenario description on the basis of an input from a user and / or predefined criteria, the means for selecting at least one traffic scenario description in particular as a first module a data processing device, for example as appropriate software. In addition, the device preferably has a means for generating a test case on the basis of the at least one selected traffic scenario description and at least one predetermined value for the at least one parameter and preferably further traffic scenario descriptions, the test case with a concrete implementation of the the at least one selected traffic scenario description characterized traffic scenarios and preferably further traffic scenarios corresponding to the at least one predetermined value of the at least one parameter and is suitable for generating a test environment in which a driver assistance system can be subjected to a test run. The means for generating the test case can in particular be set up as a second module of the data processing device, for example as appropriate software.

A means within the meaning of the present invention can be designed in terms of hardware and / or software, in particular one that is data or signal linked, preferably digital, processing, in particular microprocessor unit (CPU) or a, preferably with a memory and / or bus system Have module of such and / or one or more programs or program modules. The CPU can be designed to process commands implemented as a program stored in a memory system, to detect input signals from a data bus and / or to output signals to a data bus. A storage system can have one or more, in particular different, storage media, in particular optical, magnetic, solid-state and / or other non-volatile media. The program can be designed in such a way that it embodies or is capable of executing the methods described here, so that the CPU can carry out the steps of such methods and thus in particular can control and / or monitor a reciprocating piston engine.

In a preferred embodiment, the device has a traffic scenario database in which traffic scenario descriptions are or are stored in the form of traffic scenario files, each of which has at least one parameter present in a predetermined, in particular generic, format, by means of which a through the respective traffic scenario description characterized traffic scenario can be adapted to boundary conditions. In a further preferred embodiment, the device also has an input device by means of which a user can make an input for selecting at least one traffic scenario description, in particular from traffic scenario descriptions stored in the traffic scenario database.

In a further preferred embodiment, the device has a simulation device which is set up to carry out a test run using the test case generated. For this purpose, the simulation device can have, for example, a simulation environment such as MATLAB / Simulink, IPG CarMaker, PreScan, SUMO SCANer or Virtual Test Drive (VTD).

The features and advantages described in relation to the first aspect of the invention and its advantageous embodiment also apply, at least where it makes technical sense, to the second aspect of the invention and its advantageous embodiment, and vice versa.

Further features, advantages and possible applications of the invention will become apparent from the following description in connection with the figures, in which the same reference numerals are used for the same or corresponding elements of the invention. At least partially, they show schematically:

1 shows a preferred embodiment of a device according to the invention;

2 shows a preferred embodiment of a method according to the invention; and

3 shows an example of a traffic scenario description.

FIG. 1 shows a preferred embodiment of a device 100 according to the invention for testing a driver assistance system for a vehicle in a test environment. The device 100 has a traffic scenario database 2 with traffic scenario descriptions stored therein, each of which characterizes a specific traffic scenario, an input device 3 for selecting at least one of the traffic scenario descriptions stored in the traffic scenario database 2, and a data processing device 4 for creating a test case which, with a concrete realization of the traffic scenario selected by the at least one Description characterized traffic scenarios corresponds, based on the at least one selected traffic scenario description and a simulation device 5 for performing a test run using the test case generated, in particular a test environment generated based on the test case.

The traffic scenario descriptions preferably characterize a specific traffic scenario, for example a cut-in maneuver or a cut-out maneuver, in a generic manner. In other words, the traffic scenario descriptions preferably each represent a traffic scenario, in particular at least one concrete driving maneuver of a vehicle involved in the traffic scenario, in an abstract form.

The traffic scenario descriptions are preferably stored in the traffic scenario database 2 in the form of traffic scenario files. Because of the preferred generic character of the traffic scenario descriptions, the traffic scenario files can be stored in a predetermined, in particular generic, format, regardless of the (specific) traffic scenario characterized in each case. This enables or at least simplifies, for example, an identification and / or a parameterization of the traffic scenario characterized by the respective traffic scenario description.

For this purpose, the traffic scenario descriptions stored in the traffic scenario database 2 can have, for example, at least one parameter, for example speeds and / or positions of the traffic participants contained in the traffic scenario, with which the respective traffic scenario can be adapted to boundary conditions. The at least one parameter is preferably contained in the traffic scenario files. In particular, the predefined format of the traffic scenario files can correspond to the predefined format of the at least one parameter with which the at least one parameter is stored in the traffic scenario file. In other words, the predetermined format of the traffic scenario files can be predetermined or formed by the structure with which the at least one parameter is stored in the traffic scenario database 2. This enables the parameterization of the traffic scenarios. At least one traffic scenario description can also be selected via the at least one parameter contained in the traffic scenario files. For example, a user can use the input device 3 to specify or specify at least one parameter which is to be taken into account when creating test cases. In particular, it is conceivable for the user to enter at least one value or range of values for the at least one parameter via the input device 3, so that those traffic scenario descriptions which have the corresponding parameter or in which the corresponding one can be selected can be selected in the database Parameter can take the entered value or range of values.

For this purpose, the input device 3 can have, for example, a graphical user interface, in which the user can provide information on the selection of the at least one traffic scenario description, in particular the at least one parameter. The input device 3 thus preferably serves as a user interface.

The data processing device 4 is preferably set up to take into account at least one predefined value for the at least one parameter for generating the test case on the basis of the at least one selected traffic scenario description, the at least one predefined value being provided, for example, by the input device 3 can. By specifying at least one value for the at least one parameter, the traffic scenario characterized by the selected, preferably generic or abstract, traffic scenario description can be concretized, so that the test case preferably corresponds to a specific implementation of the traffic scenario.

Based on the test case generated by the data processing device 4, the simulation device 5 can preferably generate a test environment in which a driver assistance system can be subjected to a test run. For example, on the basis of the test case generated, the simulation device 5 can simulate a virtual, in particular dynamic, vehicle environment in which the reaction of the driver assistance system is tested in the traffic scenario specified by the test case. The parameterization of the traffic scenarios, each of which is characterized by a description of the traffic scenario, allows the driver to be tested accordingly. assistance systems under different conditions, for example in different weather conditions, on different road segments, at different vehicle speeds, with or without a trailer and / or the like.

FIG. 2 shows a preferred embodiment of a method 1 according to the invention for testing a driver assistance system for a vehicle in a test environment 6. In a method step S1, a sensor data stream 7 generated when a real vehicle environment is detected by means of a sensor device is preferably processed. The sensor data stream 7 can in particular be prepared in such a way that parameterizable data records, each characterizing at least one traffic scenario, can be generated and stored in a database 2 as, in particular, generic traffic scenario descriptions. In the following, these traffic scenario descriptions serve as the basis for the generation of at least one test case with which the test environment 6 can be generated for testing the driver assistance system.

The sensor data stream 7 is preferably processed in method step S1, in particular analyzed, e.g. by the vehicle environment mapped by the sensor data stream 7 is classified. For example, elements of the vehicle environment can be identified and labeled in individual snapshots of the vehicle environment obtained by sensor data fusion, which correspond to individual scenes of a real (specific) traffic scenario. Thus, so-called. Meta information, which goes beyond the pure physical information due to the sensory detection of the vehicle environment, is preferably generated. For example, object lists of objects recognized in the vehicle environment, such as other road users or traffic signs, can be generated in this frame. Such processing of the sensor data stream 7 can be implemented, for example, by a rule-based approach in which predetermined events are recognized and marked.

In other words, an environment model is preferably generated on the basis of the sensor data stream 7, which, for example, represents the objects around the EGO vehicle equipped with the sensor device.

In a further method step S2a, on the basis of the sensor data stream 7 processed in this way, in particular from the meta-information generated in the process, such as an object list, at least one data record that contains at least one characterized, determined traffic scenario. For example, processed sensor data corresponding to individual traffic scenarios, which are identified, for example, by recognized predetermined events, can be selectively extracted from the sensor data stream 7. This can also be called scenario mining.

In a further method step S2b, at least one parameter is preferably identified for the at least one determined data set, by means of which the at least one traffic scenario characterized by the at least one determined data set is based on boundary conditions, such as weather conditions, a speed of the EGO vehicle and / or the like , can be adjusted. In other words, the at least one traffic scenario characterized by the at least one determined data record can be parameterized.

The identification of the at least one parameter can be achieved, for example, by using the classified vehicle environment, i.e. the at least one data record, the states of elements of the vehicle environment, for example of recognized objects such as other road users, are determined and compared with one another in successive scenes of the traffic scenario characterized by the at least one data record. In this case, a state of an element of the vehicle environment can be defined, for example, by physical variables such as a speed, position, configuration and / or the like. In a preferred manner, at least one parameter is identified in particular when a change in a state of an element occurs in the temporally successive scenes of the traffic scenario, for example a change in speed or position.

Since the traffic scenario description is preferably defined by the data set determined in method step S2a and the at least one parameter identified in method step S2b, method steps S2a and S2b can also be understood as determining traffic scenario descriptions and summarized in a method step S2c will. As an alternative or in addition, such traffic scenario descriptions can also be determined in some other way, for example from other databases such as NCAP, DVP and / or accident databases (not shown).

In a further method step S3, the at least one data record with the at least one traffic scenario parameterized in this way as, in particular generic, Traffic scenario description stored in a traffic scenario file and stored in the traffic scenario database 2. In particular, the at least one identified parameter can be stored in a predetermined, in particular generic, format in the traffic scenario file.

In a further method step S4, at least one of the traffic scenario descriptions ascertained and stored in the traffic scenario database 2 can then be selected by inputting a user, for example via an input device 3. E.g. the user can specify at least one parameter with which the traffic scenarios characterized by the traffic scenario descriptions can be adapted to boundary conditions.

The at least one traffic scenario description that is relevant or selected with regard to the user input is made available to a data processing device that, based on this traffic scenario description and at least one value, in particular by the user input, for the at least one parameter in a further method step S6 at least one test case is generated which corresponds to a concrete implementation of the traffic scenario characterized by the at least one selected traffic scenario description. The at least one test case generated can be used to generate a test environment for testing the driver assistance system.

The user can influence, in particular configure, the test of the driver assistance system via his input, for example by specifying boundary conditions for the traffic scenario characterized by the at least one traffic scenario description, in particular the course of the traffic scenario, e.g. resolving a traffic situation, specified. For this, the user can e.g. select appropriate parameters on the basis of which the at least one test case is created. It is particularly conceivable that the user directly selects relevant traffic scenario descriptions and, e.g. by specifying at least one value or range of values of a corresponding parameter.

Such modified traffic scenario descriptions can be carried out in a further method step S5, possibly together with generated test cases, in the traffic scenario database, where you can be selected at a later point in time, especially faster, to create test cases.

In a further method step S7, a test environment 6 for testing a driver assistance system, for example a virtual vehicle environment, is generated from the at least one test case generated by means of a simulation device 5. For this purpose, the simulation device 5 can have a simulation environment, such as MATLAB / Simulink, IPG CarMaker, PreScan, SUMO SCANer or Virtual Test Drive (VTD). The test environment 6 can be generated independently of the simulation environment used, since the traffic scenario descriptions in the traffic scenario database 2 are stored as traffic scenario files in a predetermined, in particular generic, format and, accordingly, the test cases in a standardized format, e.g. the OpenSCENARIO format, who can.

It is pointed out that the exemplary embodiments are merely examples which are not intended to restrict the scope of protection, the applications and the structure in any way. Rather, the person skilled in the art is given a guide for the implementation of at least one exemplary embodiment by the preceding description, wherein various changes, in particular with regard to the function and arrangement of the described components, can be carried out without leaving the scope of protection as it is results from the claims and these equivalent combinations of features.

Figure 3 shows an example of a traffic scenario description 1 1 in a schematic representation. Preferably, the traffic scenario description 12 shown corresponds to a general description of a specific traffic scenario, in particular a driving maneuver such as a cut-in maneuver in the example shown, in which an EGO vehicle 8 to which the traffic scenario relates , from a first lane 9a to a second, adjacent lane 9b behind a preceding vehicle 10, as indicated by the arrow. On the basis of a corresponding traffic scenario description 12, for example, a driver assistance system, for example adaptive cruise control (ACC), could be tested for its reaction during and / or after reeving. Such a traffic scenario description 12 characterizing a traffic scenario can be determined in various ways. For example, traffic scenario descriptions can be loaded from NCAP, DVP and / or accident databases. As an alternative or in addition, sensor data can be collected which characterize the traffic scenario, for example by carrying out corresponding simulations or the EGO vehicle 8 equipped with a sensor device for detecting the vehicle environment is taking a test drive and a section of a sensor data stream generated by the sensor device, which corresponds to the traffic scenario when sensor data is extracted.

With regard to the cut-in maneuver, the sensor data stream is distinguished, for example, by the fact that the vehicle 10 driving ahead is suddenly detected in the middle of a detection region 11 of a sensor unit of the sensor device, for example a LIDAR sensor, when the lanes 9a, 9b change . This event can therefore be interpreted as a trigger for the cut-in maneuver and, preferably together with other corresponding triggers, can be used to extract the sensor data from the sensor data stream.

On the basis of the sensor data extracted in this way, parameters are preferably identified in the following which determine the boundary conditions of the traffic scenario, for example the speed of the ego vehicle 8 and the vehicle 10 driving ahead, the distance of the ego vehicle 8 from the vehicle 10 driving ahead at the beginning and / or at the end of the cut-in maneuver, the lanes 9a, 9b and / or the like used by the vehicles 8, 10 each. The parameters identified in this way preferably determine how the cut-in maneuver proceeds.

The parameters can in particular be identified by comparing different states of the two vehicles 8, 10 which are defined by the parameters and which occur during the course of the traffic scenario, in particular at the beginning and at the end of the traffic scenario, in particular subtractively from one another here.

The parameters identified in this way are preferably stored at least as part of the traffic scenario description 12 in a traffic scenario file which, together with other traffic scenario files, for example from NCAP, DVP and / or accident Databases, which forms a traffic scenario database. The traffic scenario file is preferably provided with a marker (tag) which identifies the traffic scenario description 12 stored in the traffic scenario as corresponding to a cut-in maneuver.

To generate a test case, on the basis of which a test environment can be generated in which the driver assistance system of the EGO vehicle 8 (hereinafter referred to as test vehicle, since it is equipped with the driver assistance system to be tested) can be tested the traffic scenario description 12 of the cut-in maneuver, which was determined as described above, is selected, eg by a user input, by means of which all traffic scenario descriptions 12 identified with the corresponding marking are called up. Values for the parameters of the selected traffic scenario description 12 can e.g. also by user input or by retrieving from a parameter database. The cut-in maneuver characterized by the selected traffic scenario description 12 is then preferably matched to the parameters set by the parameters and / or others, e.g. Boundary conditions defined by the user input are adapted.

For example, a value can be specified for the, in particular lateral, speed of the test vehicle 8, which value is lower than when the real cut-in maneuver was recorded. Accordingly, the implementation of the cut-in maneuver characterized by the test case proceeds more slowly or takes longer. In this way, at least one value or range of values can also be specified for other parameters in order to produce one or more implementations of the cut-in maneuver. Correspondingly, several different test cases can be generated easily and without great effort on the basis of the one traffic scenario description 12. Reference list

1 procedure

S1 -S7 process steps

2 Traffic scenario database

3 input device

4 data processing device

5 simulation device

6 test environment

7 sensor data stream

8 EGO vehicle or test vehicle

9a, 9b lane

10 other vehicle

11 Detection area

12 Description of the traffic scenario

100 device

Claims

1. Method (1) for testing a driver assistance system for a vehicle in one

Test environment (6), comprising the following steps:

- Determining (S2c) traffic scenario descriptions (12), each of which characterizes a specific traffic scenario, in particular a cut-in maneuver or a cut-out maneuver, and has at least one parameter by means of which the respective traffic scenario is adapted to boundary conditions can be, the traffic scenario descriptions (12) preferably, in particular in each case, being stored in a traffic scenario file, in which the at least one parameter is stored in a predetermined, in particular generic, format;

- Selections (S4) of at least one traffic scenario description (12) on the basis of an input from a user and / or of specified criteria; and

- Generation (S6) of a test case on the basis of the at least one selected traffic scenario description (12) and at least one predetermined value for the at least one parameter and preferably further traffic scenario descriptions, the test case with a concrete realization of the by the at least a selected traffic scenario description (1) characterizes traffic scenarios and, before further traffic scenarios, preferably corresponds to the at least one predetermined value of the at least one parameter and is suitable for generating a test environment (6) in which a driver assistance system is subjected to a test run can.

2. The method of claim 1, further comprising the following step:

- Carrying out (S7) a test run using the generated test case.

3. The method (1) according to claim 1 or 2, further comprising the following steps: - Determining (S2a) at least one data record that characterizes at least one, in particular real, traffic scenario; and

- Identifying (S2b) at least one parameter in the at least one determined data set, by means of which the respective traffic scenario can be adapted to boundary conditions, in particular an initial speed of a first-person vehicle, to which the traffic scenario relates.

4. The method according to claim 3, wherein the identification of the at least one parameter is carried out by comparing a classified vehicle environment in chronologically successive scenes of the at least one traffic scenario characterized by the at least one determined data record.

5. The method according to claim 3 or 4, further comprising the step:

- Generating at least one traffic scenario description (12) on the basis of the determined data record or the determined data records, the traffic scenario description (12) characterizing the determined traffic scenario and the at least one identified parameter being stored in the predetermined format.

6. The method according to any one of claims 1 to 5, further comprising the step of:

Filing (S3) of the generated traffic scenario description (12), in particular the traffic scenario file, in a traffic scenario database (2), further traffic scenario files also being stored in the traffic scenario database (2).

7. The method according to any one of claims 1 to 6, further comprising at least one of the following steps:

- Determining the specified values from a test run database; and or ~ Determining the specified values from a user input, in particular via a user interface.

8. Device (100) for testing a driver assistance system for a vehicle in a test environment (6), comprising:

- Means, in particular interface or sensor device, for determining traffic scenario descriptions (12), each of which characterize a specific traffic scenario, in particular a cut-in maneuver or a cut-out maneuver, and have at least one parameter by means of which the respective Traffic scenario can be adapted to boundary conditions, and preferably for storing the traffic scenario descriptions (12), in particular in each case, in a traffic scenario file in which the at least one parameter is stored in a predetermined, in particular special, generic format;

- Means, in particular a first module of a data processing device, for selecting at least one traffic scenario description (12) on the basis of an input from a user and / or predetermined criteria; and

- Means, in particular a second module of a data processing device, for generating a test fail based on the at least one selected traffic scenario description (12) and on at least one predetermined value for the at least one parameter and preferably further traffic scenario descriptions, the test case having a Concrete implementation of the traffic scenario characterized by the at least one selected traffic scenario description and preferably further traffic scenarios in relation to the at least one predetermined value of the at least one parameter corresponds and is suitable for generating a test environment (6) in which a driver assistance system is subjected to a test run can.