METHOD FOR EXECUTING A DRIVING TASK IN A DECENTRALIZED CONTROL UNIT SYSTEM, AND DECENTRALIZED CONTROL UNIT SYSTEM
20230166747 · 2023-06-01
Inventors
Cpc classification
G07C5/02
PHYSICS
B60R16/0231
PERFORMING OPERATIONS; TRANSPORTING
B60W2050/0006
PERFORMING OPERATIONS; TRANSPORTING
International classification
B60W50/02
PERFORMING OPERATIONS; TRANSPORTING
B60R16/023
PERFORMING OPERATIONS; TRANSPORTING
Abstract
A method for executing a driving task in a decentralized control unit system and a decentralized control unit system are provided. The control unit system includes at least two control units that are designed as senders, and at least one control unit that is designed as a receiver. The at least two senders and the at least one receiver in each case have activity states and operating states. The two senders and the receiver in each case check their own activity states. The two senders’ own activity states are compared to the receiver’s own activity state. An evaluation of operating states is carried out if the two senders’ and the receiver’s own activity states are in each case error-free. The driving task is executed if one of the two senders and the receiver in each case has a dynamic operating state.
Claims
1. A method for executing a driving task in a decentralized control unit system, wherein, for executing the driving task, the decentralized control unit system includes at least two control units that are configured as senders, and at least one control unit that is configured as a receiver, each of the at least two senders and the at least one receiver having activity states and operating states, the method comprising the following steps: in a first step, checking, by each of the at least two senders and the at least one receiver, its own activity state; in a second step, comparing in each case the at least two senders’ own activity states to the at least one receiver’s own activity state; in a third step, carrying out an evaluation of operating states when the at least two senders’ own activity states and the at least one receiver’s own activity state is error-free in each case; and in a fourth step, executing the driving task when one of the at least two senders and the at least one receiver each has a dynamic operating state.
2. The method as recited in claim 1, wherein during the checking of the own activity states in the first step, it is checked in each case whether a voltage drop and/or a deviation is detected at the at least two senders and/or at the at least one receiver, wherein: the own activity state of the at least two senders and/or of the at least one receiver in each case containing errors when a voltage drop and/or a deviation is detected at the at least two senders and/or at the at least one receiver, and the own activity state of the at least two senders and/or of the at least one receiver in each case being error-free when no voltage drop and/or no deviation is detected at the at least two senders and/or at the at least one receiver.
3. The method as recited in claim 2, wherein, when an own activity state of the at least two senders and/or of the at least one receiver is identified as containing errors, in each case an error response for an affected sender and/or for an affected receiver is triggered in the second step, the error response being in the form of a substitute response and/or in the form of an error message, wherein the substitute response includes that the affected sender and/or the affected receiver remain disregarded for the third step, and only the operating states of one of the at least two senders and/or of the at least one receiver, whose own activity states in each case has been identified as error-free in the first step, being evaluated.
4. The method as recited in claim 1, wherein each of the operating states of the at least two senders and/or of the at least one receiver corresponds to at least one and/or a combination of the following states: operational, non-operational, initialization, delay, preprocessing, shutdown, dynamic, static, and wherein the dynamic operating state corresponds to the “dynamic” state.
5. The method as recited in claim 1, wherein the checking and comparing of the own activity states in the first and second steps is periodically repeated.
6. The method as recited in claim 5, wherein the checking and comparing of the own activity states in the first and second steps is implemented using a matrix.
7. A decentralized control unit system, wherein for executing a driving task, the decentralized control unit system includes at least two control units that are configured as senders and at least one control unit that is configured as a receiver, the at least two senders and the at least one receiver being communicatively linked to one another, each of the at least two senders and the at least one receiver having activity states and operating states, wherein: each of the at least two senders and the at least one receiver being configured to check its own activity state, the at least one receiver is configured to compare the own activity state of the at least one receiver in each case to the own activity states of the at least two senders, the at least one receiver is configured to carry out an evaluation of operating states when the own activity states of the at least two senders and the own activity state of the at least one receiver is in each case error-free, and the at least one receiver is configured to execute the driving task when one of the at least two senders and the at least one receiver each has a dynamic operating state.
8. The decentralized control unit system as recited in claim 7, wherein the at least two senders and/or the at least one receiver is configured, in each case during checking of its own activity state, to check whether a voltage drop and/or a deviation are/is present at the at least two senders and/or at the at least one receiver, wherein: the own activity state of the at least two senders and/or of the at least one receiver in each case containing errors when a voltage drop and/or a deviation is present at the at least two senders and/or at the at least one receiver, and the own activity state of the at least two senders and/or of the at least one receiver in each case being error-free when no voltage drop and/or no deviation is present at the at least two senders and/or at the at least one receiver.
9. The decentralized control unit system as recited in claim 8, wherein when the at least two senders and/or the at least one receiver in each case identifies its own activity state as containing errors, the at least one receiver in each case triggers an error response for an affected sender and/or for an affected receiver, wherein: the error response is in the form of a substitute response and/or in the form of an error message, the substitute response including that the affected sender and/or the affected receiver remain disregarded, and only the operating state of one of the at least two senders and/or of the at least one receiver, whose own activity state in each case has been identified as error-free, being evaluated.
10. A non-transitory machine-readable memory medium on which are stored a computer program for executing a driving task in a decentralized control unit system, wherein, for executing the driving task, the decentralized control unit system includes at least two control units that are configured as senders, and at least one control unit that is configured as a receiver, each of the at least two senders and the at least one receiver having activity states and operating states, the computer program, when executed by a computer, causing the computer to perform the following steps: in a first step, checking, by each of the at least two senders and the at least one receiver, its own activity state; in a second step, comparing in each case the at least two senders’ own activity states to the at least one receiver’s own activity state; in a third step, carrying out an evaluation of operating states when the at least two senders’ own activity states and the at least one receiver’s own activity state is error-free in each case; and in a fourth step, executing the driving task when one of the at least two senders and the at least one receiver each has a dynamic operating state.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0025]
[0026]
[0027]
[0028]
[0029]
[0030]
[0031]
[0032]
DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS
[0033] It is pointed out that the figures are merely schematic and not true to scale. In this sense, components and elements shown in the figures may be illustrated in an overly large scale or in reduced scale for better understanding. In addition, it is pointed out that the reference numerals in the figures have been selected to be unchanged when elements and/or components having an identical design are involved.
[0034]
[0035] The activity states may, for example, reflect present own state estimations of the individual control units, and the operating states may correspond to dynamic evaluations of changes in the own states due to obtained activity states of other control units and/or obtained sensor information and its interpretation, in each case during ongoing vehicle operation. Examples of possible operating states are in particular: operational, non-operational, initialization, delay, preprocessing, shutdown, dynamic, and static. A dynamic operating state may in particular correspond to the “dynamic” state. Further dynamic operating states such as “operational,” etc., are possible. The at least two senders 405, 410 and/or receiver 420 may in each case have one of the stated operating states and/or a combination of various stated operating states. In particular for a combination of various types of operating states, it is necessary to carry out an evaluation to allow data to be correctly interpreted and for suitable measures to be deduced, for example generating a wait instruction if a sender 405 only has the “initialization” operating state (i.e., apparently is not yet ready for a data exchange, or the like), but receiver 420 already has the “dynamic” state, i.e., a dynamic operating state, on the basis of which the driving task could be executed.
[0036] A first step 105 of method 100 in
[0037] Since the operating states may be different as explained above, and for example an initialization (static operating state) may likewise also already indicate complete operational readiness (dynamic operating state), the evaluation by receiver 420 in third step 115 is essential for the correct interpretation of the results. Receiver 420 executes the driving task in fourth step 120 only when dynamic operating states are present. For this purpose, generally one of the at least two senders 405, 410 (or at best, both senders 405, 410) as well as receiver 420 in each case have a dynamic operating state. Fourth step 120 may also include ascertaining a dynamic value contribution of senders 405, 410 to the overall computation result. For example, a contribution quantity for the driving task may be defined for each sender 405, 410. This contribution may be checked centrally by a receiver 420, for example as soon as data may be fused or also compared. The execution of the driving task may include, for example, a fusion and/or a comparison and/or a plausibility check of data of individual senders 405, 410 or of receiver 420.
[0038]
[0039]
[0040]
[0041]
[0042]
[0043] A first sender 525 may represent a braking unit (brake or braking functionality), for example, a second sender 530 may represent a steering unit (steering or steering functionality), and a third sender 535 may represent a drive unit (drive or drive functionality). Third sender 535 includes, for example, a first through third sensor unit 540, 545, 550 as a drive unit, second sender 530 includes, for example, a fourth through sixth sensor unit 555, 560, 565 as a steering unit, for example, and first sender 525 includes a seventh through ninth sensor unit 570, 575, 580 as a braking unit, for example. The individual sensor units may each be typical sensor units or sensors for a drive unit, a steering unit, and a braking unit. First through third senders 525, 530, 535 may also be designed in each case as receivers for the stated sensor units, as indicated by the arrows, which correspond to information interactions or communicative links. Here as well, a bidirectional communication may also be possible in addition to the illustrated unidirectional communication. This applies for all interactions between the illustrated components in
[0044] Control unit system 500 also includes a tenth through fourteenth sensor unit 581, 583, 585, 587, 589, it being possible, for example, for tenth sensor unit 581 to be designed as an ultrasonic sensor unit or ultrasonic sensor, for eleventh sensor unit 583 to be designed, for example, as a video sensor unit or video sensor or camera, etc., which may record video sequences, for twelfth sensor unit 585 to be designed, for example, as a cloud-based sensor unit (or cloud-based information source) that includes cloud-based information, for thirteenth sensor unit 587 to be designed as a LIDAR sensor unit or as a LIDAR sensor, for example, and for fourteenth sensor unit 589 to be designed as a radar sensor unit or radar sensor, for example. Stated tenth through fourteenth sensor unit 581, 583, 585, 587, 589, in each case as a sender, for example, may transfer information, such as the above-mentioned own activity states, etc., to first receiver 505. In addition, first through nth receivers 505, 510, 515, 520 may in each case check their own activity states and exchange this information with one another according to the above method steps.
[0045] At the same time, for example eleventh sensor unit 581, twelfth sensor unit 583, and fourteenth sensor unit 589 may in each case also represent a receiver for the information of seventh sensor unit 570 (for eleventh sensor unit 583 and fourteenth sensor unit 589 as senders in each case, for example) and for the information of third sensor unit 550 (for twelfth sensor unit 583 as sender, for example). The plurality of sensor units may be necessary for control unit system 500, for example due to redundancy with an increasing level or an increasing advanced driver assistance system (ADAS) level on the way to an autonomous vehicle. For each communication interaction or information interaction, in each case the own activity states may be initially checked and compared if the own activity states are in each case error-free, and the computation may be continued; i.e., the evaluation of the individual operating states, in particular the individual combinations of the different operating states, may be carried out as described above.
[0046]
[0047] The implementation of provided method 100, 200, 300 may take place, for example, based on the following pseudocode, which includes excerpts for two different scenarios with response options that may be implemented with the aid of arbitrary programming language. Further scenarios are possible. The programming may preferably take place in C or C++.
Scenario 1
[0048] receiver == activity state is error-free (“activity”/“in spec” via continuous monitoring) && [0049] sender 1 - n == activity state is error-free/“in spec” (via continuous monitoring) && [0050] sender 1 - (n - 1) == activity state is error-free/“in spec” (via continuous monitoring)
Case 1:
[0051] receiver == activity state is error-free (activity/in spec) && “dynamic” operating state && [0052] sender 1 == activity state is error-free (activity/in spec) && “initialization” operating state
Result:
[0053] sender 1 wait to proceed, system may be operational, but content not yet fully available
Case 2:
[0054] receiver == activity state is error-free (activity/in spec) && “dynamic” operating state && [0055] sender 1 == activity state is error-free (activity/in spec) && “dynamic” operating state
Result:
[0056] sender 1 can proceed, system is operational and “healthy”
Scenario 2
[0057] receiver == activity state is error-free (“activity”/“in spec” via continuous monitoring) && [0058] sender 1 - n == activity state is error-free (“activity”/“in spec” via continuous monitoring) && [0059] sender 1 - (n - 1) == activity state contains errors (“not active”/“not in spec” via continuous monitoring)
Case 1:
[0060] receiver == activity state is error-free (activity/in spec) && “dynamic” operating state && [0061] sender 1 == activity state contains errors (“not active”/“not in spec”) && “dynamic” operating state
Result:
[0062] sender 1 debouncing and error response (substitute response and/or error message)
[0063] The pseudocode may, for example, be extended to all combinations that are illustrated in matrix 403 in
[0064] In other words, the pseudocode may be expressed as follows: If an error-free activity state has been ascertained in the continuous monitoring for the further processing of the data (in each case by the two senders and the receiver), during dynamic operation it may then be further ascertained which dynamic state combination the control units, i.e., the two senders and the receiver, are in relative to one another. The further processing of the computation may thus be correctly interpreted. During the dynamic operation, it is important that the activity state estimation is sufficiently expanded by dynamically special states, referred to above as operating states.
[0065] The check must be able to discern that various combinations are present between the operating states. Due to different electrical connections in the vehicle for the control unit system, the sender may have an “initialization” operating state, while the receiver may already have the “dynamic” or “operational” operating state. This combination must result in a “wait” operation on the receiver or the executing control unit, since, although no error-containing activity states are present and therefore the data of the sender may be trusted, the “functional” driving task is not yet executable due to the “initialization” operating state.
[0066] For the processing of the results, a dynamic value contribution of the senders to the overall computation result may then be ascertained. For example, a contribution quantity for the dynamic driving task may be defined for each sender. This contribution is centrally checked, for example by a central control unit in
[0067] The present invention has been described in detail using preferred exemplary embodiments. Instead of the described exemplary embodiments, further exemplary embodiments are possible which may include further modifications or combinations of described features. For this reason, the present invention is not limited by the provided examples, since other variations may be derived therefrom by those skilled in the art without departing from the scope of protection of the present invention.