METHOD AND ELECTRONIC VEHICLE SYSTEM FOR PROCESSING V2X MESSAGES
20230094360 · 2023-03-30
Inventors
Cpc classification
H04W4/021
ELECTRICITY
International classification
H04W4/021
ELECTRICITY
Abstract
A method for processing V2X messages by an electronic vehicle system, including receiving a V2X message by a verification device of a V2X communication device, determining whether the V2X message should be verified by the verification device and if no verification of the V2X message is to be carried out: forwarding the unverified V2X message or at least a part of the message content of the unverified V2X message to a processing device, wherein the processing device determines whether an action should be initiated on the basis of the part of the message content; verifying the V2X message if it is determined that an action should be initiated. The disclosure also relates to a corresponding electronic vehicle system and a vehicle, including the vehicle system.
Claims
1. A method for processing V2X messages by an electronic vehicle system, the method comprising: receiving a V2X message by a verification device of a V2X communication device; and determining whether the V2X message should be verified by the verification device and if no verification of the V2X message is to be carried out: forwarding the unverified V2X message or at least a part of the message content of the unverified V2X message to a processing device, wherein the processing device determines whether an action should be initiated on the basis of the part of the message content; verifying the V2X message if it is determined that an action should be initiated.
2. The method as claimed in claim 1, wherein the verification of the V2X message is carried out by the verification device or by the processing device, wherein the processing device issues an instruction signal for the verification to the verification device if the verification is carried out by the verification device.
3. The method as claimed in claim 1, wherein the determination by the verification device as to whether the V2X message should be verified depends on a value describing the computational load of the verification device, wherein the received V2X message is verified by the verification device if a value describing the computational load of the verification device is below a first threshold value and at least one further criterion is used by the verification device for determining whether the V2X message should be verified, if the value describing the calculation load of the verification device is above a second threshold value.
4. The method as claimed in claim 3, wherein the value describing the computational load is represented by the computational load of the verification device as such and/or by a rate of received V2X messages and/or a temperature of the verification device.
5. The method as claimed in claim 4, wherein the rate of received V2X messages is stored in a data memory on a location-specific basis and is retrieved from the data memory depending on a determined location of the electronic vehicle system executing the method.
6. The method as claimed in claim 5, wherein a location-dependent determination of the rate of received V2X messages is performed, wherein the rate determined on a location-specific basis is stored in the data memory.
7. The method as claimed in claim 1, wherein the result of determining whether the V2X message should be verified depends on a cryptographic algorithm used and/or a curve used and/or a key length used for the V2X message.
8. The method as claimed in claim 7, wherein, as a result of determining whether the V2X message should be verified, the received V2X message will not be verified if, taking into account the available resources of the verification device, its cryptographic algorithm and/or curve and/or key length does not allow verification of the V2X message by the verification device within a period of time equal to or less than a time threshold.
9. The method as claimed in claim 7, wherein the V2X message is assigned to one of at least two classes depending on the cryptographic algorithm and/or curve and/or key length used, wherein in the case of assignment to a first class, the result of determining whether the V2X message should be verified is that no verification will be carried out.
10. The method as claimed in claim 1, wherein a first received V2X message of a respective sender is always verified without exception.
11. The method as claimed in claim 1, wherein the verification device issues status information for describing a current verification status of the received message and/or for describing a current verification scheme for receipt by the processing device.
12. The method as claimed in claim 1, wherein the verification device issues latency information for describing an estimated verification time of the unverified V2X message for receipt by the processing device.
13. The method as claimed in claim 1, wherein the latency information is used in determining whether an action should be initiated.
14. An electronic vehicle system for processing V2X messages, comprising a verification device for verifying a received V2X message and a processing device for processing the V2X message and/or a message content that the received V2X message comprises, wherein the electronic vehicle system is configured to execute a method as claimed in claim 1.
15. A vehicle, comprising an electronic vehicle system as claimed in claim 14.
16. The method as claimed in claim 8, wherein the V2X message is assigned to one of at least two classes depending on the cryptographic algorithm and/or curve and/or key length used, wherein in the case of assignment to a first class, the result of determining whether the V2X message should be verified is that no verification will be carried out. 3.
17. The method as claimed in claim 2, wherein the determination by the verification device as to whether the V2X message should be verified depends on a value describing the computational load of the verification device, wherein the received V2X message is verified by the verification device if a value describing the computational load of the verification device is below a first threshold value and at least one further criterion is used by the verification device for determining whether the V2X message should be verified, if the value describing the calculation load of the verification device is above a second threshold value.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0054] Several embodiments of the invention are specified in the dependent claims. Further possible embodiments also emerge from the following description of exemplary embodiments on the basis of figures.
[0055] In the figures:
[0056]
[0057]
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0058]
[0059] On the other hand, if in step 108 it is determined that no action should be initiated, the V2X message is discarded (step 112). Alternatively, it may be planned to use the message content of the unverified V2X message only for non-safety-critical uses.
[0060]
[0061] The processing device 220 is designed, for example, as an electronic control unit of a driving assistance system and/or a (partially) autonomous driving system. The determination of whether an action should be initiated can therefore result, for example, from requirements to avoid a safety-critical traffic situation, such as a collision with another road user. Accordingly, the initiation of an action may consist of an intervention in the dynamics of the vehicle 230 by engagement of the brakes, for which the processing device 220 can be designed, by way of example, to output a signal 226 for changing the dynamic response to an electronic control device 228 for brake activation.
[0062] If it is found in the course of the proceedings that a feature or a group of features is not absolutely necessary, then the applicant aspires right now to a wording of at least one independent claim that no longer has the feature or the group of features. This may be, for example, a subcombination of a claim present on the filing date or a subcombination of a claim present on the filing date that is restricted by further features. Claims or combinations of features of this kind requiring rewording are intended to be understood as also covered by the disclosure of this application.
[0063] It should also be pointed out that refinements, features and variants of the invention which are described in the various embodiments or exemplary embodiments and/or shown in the figures can be combined with one another in any desired manner. Single or multiple features are interchangeable with one another in any desired manner. Combinations of features arising therefrom are intended to be understood as also covered by the disclosure of this application.
[0064] Back-references in dependent claims are not intended to be understood as a relinquishment of the attainment of independent substantive protection for the features of the back-referenced dependent claims. These features may also be combined with other features in any desired manner.
[0065] Features which are only disclosed in the description or features which are only disclosed in the description or in a claim in conjunction with other features may in principle be of independent significance essential to aspects of the invention. They may therefore also be individually included in claims for the purpose of delimitation from the prior art.
[0066] In general, it should be pointed out that vehicle-to-X communication is understood to mean in particular a direct communication between vehicles and/or between vehicles and infrastructure devices. For example, it may thus include vehicle-to-vehicle communication or vehicle-to-infrastructure communication. Where this application refers to a communication between vehicles, said communication can fundamentally take place as part of a vehicle-to-vehicle communication, for example, which is typically effected without switching by a mobile radio network or a similar external infrastructure and which must therefore be distinguished from other solutions based on a mobile radio network, for example. For example, a vehicle-to-X communication can be performed using IEEE 802.11p or IEEE 1609.4, SAE 2735, SAE 2945, and ETSI ITS-G5 standards. In addition, new standards are currently being written at 3GPP for C-V2X or LTE-V2X or 5G V2X. A vehicle-to-X communication can also be referred to as C2X communication or V2X communication. The sub-domains can be referred to as C2C (car-to-car), V2V (vehicle-to-vehicle) or C2I (car-to-infrastructure), V2I (vehicle-to-infrastructure). However, an aspect of the invention explicitly does not exclude vehicle-to-X communication with switching via a mobile radio network, for example. In no case is there a restriction to the explicitly mentioned communication technologies.