Internet of vehicles communication method, apparatus, device, medium and program product
By acquiring and sending data quality levels and security certificates, the problem of false alarms and missed alarms in the judgment of abnormal behavior of aftermarket vehicle-mounted equipment has been solved, and refined judgment of abnormal behavior and data quality assurance have been achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- DATANG GOHIGH INTELLIGENT & CONNECTED TECH (CHONGQING) CO LTD
- Filing Date
- 2024-12-17
- Publication Date
- 2026-06-19
Smart Images
Figure CN122248414A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of vehicle networking technology, and in particular to a vehicle networking communication method, device, equipment, medium, and program product. Background Technology
[0002] With the widespread acceptance of Cellular Vehicle-to-Everything (C-V2X) technology in the automotive industry, several automakers have already released C-V2X-equipped mass-produced models. However, relying solely on pre-installed vehicles with C-V2X devices results in a low penetration rate and slow growth, leading to a less satisfying user experience. Therefore, to increase C-V2X penetration, the industry is actively promoting the installation of C-V2X devices in aftermarket vehicles (existing vehicles).
[0003] Existing basic safety messages (BSMs) for aftermarket automotive devices require verification through secure signatures and protocol consistency checks. However, this method only verifies the authenticity of the message's source and cannot determine whether the aftermarket device exhibits other abnormal behavior, easily leading to false positives and false negatives. Therefore, given the current aggressive push for aftermarket automotive devices, a more refined method for determining whether these devices exhibit abnormal behavior is urgently needed. Summary of the Invention
[0004] The purpose of this invention is to provide a vehicle-to-everything (V2X) communication method, device, equipment, medium, and program product to solve the problem of determining whether there is abnormal behavior in vehicle-mounted equipment in the prior art.
[0005] To achieve the above objectives, the present invention is implemented as follows:
[0006] In a first aspect, embodiments of the present invention provide a vehicle-to-everything (V2X) communication method, applied to a first in-vehicle device, the method comprising:
[0007] Obtain the data quality level of the first vehicle-mounted device, and obtain the security certificate related to the data quality level;
[0008] Based on the data quality level, a basic security message is generated;
[0009] Send the basic security message, which carries the security certificate.
[0010] In a second aspect, embodiments of the present invention provide a vehicle-to-everything (V2X) communication method applied to a second vehicle-mounted device, the method comprising:
[0011] Receive a basic security message sent by a first vehicle-mounted device, the basic security message carrying a security certificate related to the data quality level of the first vehicle-mounted device;
[0012] Based on the security certificate, obtain the data quality level of the first vehicle-mounted device;
[0013] Based on the basic security messages and the data quality level, determine whether the first vehicle-mounted device exhibits abnormal behavior.
[0014] Thirdly, embodiments of the present invention provide a vehicle-to-everything (V2X) communication device applied to a first in-vehicle device, the device comprising:
[0015] The first acquisition module is used to acquire the data quality level of the first vehicle-mounted device and to acquire the security certificate related to the data quality level.
[0016] The generation module is used to generate basic security messages based on the data quality level.
[0017] A sending module is used to send the basic security message, which carries the security certificate.
[0018] Fourthly, embodiments of the present invention provide a vehicle-to-everything (V2X) communication device applied to a second vehicle-mounted device, the device comprising:
[0019] A receiving module is used to receive a basic security message sent by a first vehicle-mounted device, the basic security message carrying a security certificate related to the data quality level of the first vehicle-mounted device;
[0020] The second acquisition module is used to acquire the data quality level of the first vehicle-mounted device based on the security certificate;
[0021] The judgment module is used to determine whether the first vehicle-mounted device has abnormal behavior based on the basic security message and the data quality level.
[0022] Fifthly, embodiments of the present invention provide a vehicle-to-everything (V2X) communication device, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, it implements the V2X communication method as described in the first aspect, or implements the V2X communication method as described in the second aspect.
[0023] In a sixth aspect, embodiments of the present invention provide a readable storage medium storing a program that, when executed by a processor, implements the vehicle-to-everything (V2X) communication method as described in the first aspect, or implements the V2X communication method as described in the second aspect.
[0024] In a seventh aspect, embodiments of the present invention provide a computer program product, including computer instructions, which, when executed by a processor, implement the vehicle-to-everything (V2X) communication method as described in the first aspect, or implement the V2X communication method as described in the second aspect.
[0025] The beneficial effects of the above-described technical solution of the present invention are as follows:
[0026] In this embodiment of the invention, a first vehicle-mounted device acquires its own data quality level and a security certificate associated with that data quality level; generates a basic security message based on the data quality level; and sends the basic security message, which carries the security certificate. Thus, a second vehicle-mounted device receiving the basic security message from the first vehicle-mounted device can fully determine whether the first vehicle-mounted device exhibits abnormal behavior based on the basic security message and the data quality level, avoiding false alarms and missed alarms regarding abnormal behavior. Attached Figure Description
[0027] Figure 1 This is a flowchart illustrating the vehicle-to-everything (V2X) communication method according to one embodiment of the present invention;
[0028] Figure 2 This is a flowchart illustrating the vehicle-to-everything (V2X) communication method according to another embodiment of the present invention;
[0029] Figure 3 This is a schematic diagram of the vehicle-to-everything (V2X) communication device according to one embodiment of the present invention;
[0030] Figure 4 This is a schematic diagram of the vehicle-to-everything (V2X) communication device according to another embodiment of the present invention;
[0031] Figure 5 This is a hardware block diagram of the vehicle-to-everything (V2X) communication device according to an embodiment of the present invention. Detailed Implementation
[0032] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.
[0033] In various embodiments of the present invention, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
[0034] In addition, the terms "system" and "network" are often used interchangeably in this article.
[0035] The terms "first," "second," etc., used in the specification and claims of this invention are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0036] See Figure 1 , Figure 1 This is a flowchart illustrating a vehicle-to-everything (V2X) communication method according to one embodiment of the present invention, as shown below. Figure 1 As shown, the method is applied to a first vehicle-mounted device, which includes an on-board unit (OBU). It should be noted that, preferably, the first vehicle-mounted device is an aftermarket vehicle-mounted device.
[0037] Furthermore, the method includes the following steps:
[0038] S101, obtain the data quality level of the first vehicle-mounted device, and obtain the security certificate related to the data quality level.
[0039] In this embodiment of the invention, the data quality level of the first vehicle-mounted device is used to indicate the data quality of the first vehicle-mounted device. By indicating the data quality of the first vehicle-mounted device, the second vehicle-mounted device that receives the data from the first vehicle-mounted device can detect whether the data sent by the first vehicle-mounted device meets its corresponding data quality, and thus determine whether the first vehicle-mounted device has abnormal behavior.
[0040] In one embodiment, optionally, obtaining the data quality level of the first vehicle-mounted device includes:
[0041] Based on the device information of the first vehicle-mounted device, the data quality level of the first vehicle-mounted device is obtained; wherein, the device information of the first vehicle-mounted device includes one or more of the following:
[0042] Installation method information; functional requirements information; performance requirements information; equipment capability information.
[0043] It should be noted that the device information of the first vehicle-mounted device specifically includes: the connection status of the first vehicle-mounted device with the vehicle controller area network (CAN) bus; and the position calibration status of the antenna location point and the vehicle's geometric center point.
[0044] In this embodiment of the invention, the data quality level of the vehicle-mounted device is divided into N (N≥2) data quality levels, which are described here as N=3. These are data quality level A, data quality level B, and data quality level C, which will be referred to as level A, level B, and level C in the following text. Level A is higher than or equal to level B, and level B is higher than level C. The device information corresponding to each data quality level is described below.
[0045] Level A: The on-board equipment can connect to the vehicle's CAN bus; the antenna location and the vehicle's geometric center point have been calibrated. It should be noted that if the data quality level of the first on-board equipment is Level A, then the data quality of the first on-board equipment is essentially the same as that of the pre-installed on-board equipment.
[0046] Level B: The onboard equipment cannot connect to the vehicle's CAN bus; the antenna location and vehicle geometric center point have been calibrated.
[0047] Level C: The onboard equipment cannot connect to the vehicle's CAN bus; the antenna location point and the vehicle's geometric center point have not been calibrated.
[0048] Optionally, the security certificate includes one or more of the following:
[0049] Application ID (AID) is used to indicate the type of the first in-vehicle device;
[0050] Service Specific Permissions (SSP) are used to indicate the data quality level of the first onboard device.
[0051] It should be noted that the security certificate uses AID combined with SSP to represent different data quality levels of in-vehicle devices, and the security certificate includes the fields shown in Table 1 below.
[0052]
[0053] Table 1: Examples of Security Certificates
[0054] Optionally, the first on-board device obtains a security certificate related to the data quality level from a security certificate management authority.
[0055] S102, Generate a basic security message based on the data quality level.
[0056] In one implementation, optionally, a basic security message is generated based on the data quality level, including:
[0057] Obtain the message field population requirements related to the data quality level;
[0058] Generate a basic security message based on the message field population requirements.
[0059] In this embodiment of the invention, the first vehicle-mounted device can obtain message field filling requirements related to the data quality level from a third-party platform, and generate basic security messages according to the message field filling requirements. The third-party platform includes, but is not limited to, security certificate management agencies and aftermarket vehicle-mounted device level certification agencies.
[0060] Optionally, the message field filling requirement is used to indicate the message fields included in the basic security message, and to indicate the values of the message fields.
[0061] It should be noted that the higher the data quality level, the more message fields the basic security message indicated by the message field filling requirement includes, and the more possible values of the message fields.
[0062] Optionally, the message field includes one or more of the following:
[0063] The integration degree field between the first vehicle-mounted device and the vehicle; the capability confidence field of the first vehicle-mounted device; and the integration degree field between the first vehicle-mounted device and the vehicle-mounted sensors.
[0064] It should be noted that the higher the data quality level of the first vehicle-mounted device, the higher the integration degree between the first vehicle-mounted device and the vehicle in the message fields included in the basic security message indicated by the message field filling requirement, the higher the capability confidence of the first vehicle-mounted device, and the higher the integration degree between the first vehicle-mounted device and the vehicle-mounted sensors.
[0065] It should also be noted that the message field filling requirements are used to indicate whether the aforementioned fields corresponding to different data quality levels are mandatory, optional, or not required. For example, some fields are defined as mandatory for high data quality levels, while those for low quality levels are defined as optional or not required. The message field filling requirements are also used to indicate the values and upper / lower value ranges of the aforementioned fields corresponding to different data quality levels. For example, some fields are defined as taking invalid values for low data quality levels; the same field may have different value range requirements for different data quality levels.
[0066] Optionally, the integration degree field between the first in-vehicle device and the vehicle includes, but is not limited to, one or more of the following:
[0067] Vehicle gear position field; vehicle steering wheel angle field; vehicle braking system status field; vehicle event flag field; vehicle lights status field around the vehicle body.
[0068] Optionally, the capability confidence field of the first vehicle-mounted device includes, but is not limited to, one or more of the following:
[0069] Position confidence field; speed confidence field; heading angle confidence field; steering wheel angle confidence field.
[0070] Optionally, the integration degree field of the first vehicle-mounted device and the vehicle-mounted sensor includes, but is not limited to, one or more of the following:
[0071] Obstacle information fields (e.g., fallen rocks, debris, dead branches, etc.); traffic incident information fields (e.g., driving against traffic, speeding, collision accidents, etc.); traffic participant information fields (e.g., pedestrians, bicycles, motor vehicles, etc.).
[0072] The message field filling requirements are shown in Table 2 below.
[0073]
[0074]
[0075]
[0076] Table 2: Example of message field population requirements
[0077] S103, send the basic security message, which carries the security certificate.
[0078] Optionally, the first vehicle-mounted device broadcasts the basic security messages.
[0079] Optionally, the first vehicle-mounted device periodically sends the basic security message.
[0080] Optionally, the basic security message may also carry message field population requirements related to the data quality level.
[0081] See Figure 2 , Figure 2 This is a flowchart illustrating another embodiment of the vehicle-to-everything (V2X) communication method of the present invention, as shown below. Figure 2 As shown, the method is applied to a second vehicle-mounted device, which includes an OBU. The second vehicle-mounted device can be a pre-installed vehicle-mounted device or an aftermarket vehicle-mounted device.
[0082] Furthermore, the method includes the following steps:
[0083] S201, Receive a basic security message sent by a first vehicle-mounted device, the basic security message carrying a security certificate related to the data quality level of the first vehicle-mounted device.
[0084] Optionally, the security certificate includes one or more of the following:
[0085] AID is used to indicate the type of the first vehicle-mounted device;
[0086] SSP is used to indicate the data quality level of the first on-board device.
[0087] It is understandable that the security certificate uses AID combined with SSP to represent different data quality levels of in-vehicle devices.
[0088] S202, Based on the security certificate, obtain the data quality level of the first vehicle-mounted device.
[0089] In this embodiment of the invention, the second vehicle-mounted device receives the basic security message, parses the security certificate carried in the basic security message, and obtains the data quality level of the first vehicle-mounted device.
[0090] S203, based on the basic security message and the data quality level, determine whether the first vehicle-mounted device has abnormal behavior.
[0091] In one implementation, optionally, determining whether the first vehicle-mounted device exhibits abnormal behavior based on the basic security message and the data quality level includes:
[0092] Obtain the message field population requirements related to the data quality level;
[0093] Based on the basic security message and the message field filling requirements, determine whether the first vehicle-mounted device exhibits abnormal behavior.
[0094] In this embodiment of the invention, the second vehicle-mounted device may obtain message field filling requirements related to the data quality level from a third-party platform, or the second vehicle-mounted device may obtain message field filling requirements related to the data quality level from the basic security message.
[0095] Optionally, the message field filling requirement is used to indicate the message fields included in the basic security message, and to indicate the values of the message fields.
[0096] Optionally, the message field includes one or more of the following:
[0097] The integration degree field between the first vehicle-mounted device and the vehicle; the capability confidence field of the first vehicle-mounted device; and the integration degree field between the first vehicle-mounted device and the vehicle-mounted sensors.
[0098] Optionally, the integration degree field between the first in-vehicle device and the vehicle includes, but is not limited to, one or more of the following:
[0099] Vehicle gear position field; vehicle steering wheel angle field; vehicle braking system status field; vehicle event flag field; vehicle lights status field around the vehicle body.
[0100] Optionally, the capability confidence field of the first vehicle-mounted device includes, but is not limited to, one or more of the following:
[0101] Position confidence field; speed confidence field; heading angle confidence field; steering wheel angle confidence field.
[0102] Optionally, the integration degree field of the first vehicle-mounted device and the vehicle-mounted sensor includes, but is not limited to, one or more of the following:
[0103] Obstacle information fields (e.g., fallen rocks, debris, dead branches, etc.); traffic incident information fields (e.g., driving against traffic, speeding, collision accidents, etc.); traffic participant information fields (e.g., pedestrians, bicycles, motor vehicles, etc.).
[0104] Furthermore, the second vehicle-mounted device analyzes whether the message fields related to the data quality level in the basic security message meet the message field filling requirements. If they do not meet the requirements, it is determined that the first vehicle-mounted device has abnormal behavior; otherwise, it is determined that the first vehicle-mounted device does not have abnormal behavior.
[0105] In one implementation, optionally, determining whether the first vehicle-mounted device exhibits abnormal behavior based on the basic security message and the message field filling requirements includes:
[0106] If the basic security message does not include the message field indicated by the message field filling requirement, then it is determined that the first vehicle-mounted device has abnormal behavior;
[0107] If the basic security message includes a message field for which the message field filling requirement is not indicated, then it is determined that the first vehicle-mounted device has abnormal behavior;
[0108] If the value of the message field in the basic security message does not meet the value of the message field indicated by the message field filling requirement, then it is determined that the first vehicle-mounted device has abnormal behavior.
[0109] It should be noted that if the basic security message contains a data quality level field for the first vehicle-mounted device that cannot be obtained, for example, if the basic security message is filled with an unselected field, then it is determined that the first vehicle-mounted device has abnormal behavior.
[0110] If the basic security message does not carry the field that the data quality level of the first vehicle device must send, that is, the basic security message does not fill in the required field, then it is determined that the first vehicle device has abnormal behavior.
[0111] If the basic security message does not fill in the value of the message field corresponding to the data quality level of the first vehicle device according to the message field filling requirements, for example, the value of the message field in the basic security message should be an invalid value, or if it is not an invalid value; or, the value of the message field in the basic security message exceeds the value range indicated by the message field filling requirements, then it is determined that the first vehicle device has abnormal behavior.
[0112] In one embodiment, optionally, when it is determined that the first vehicle-mounted device exhibits abnormal behavior, the method further includes:
[0113] Report the abnormal behavior of the first on-board device to the abnormal behavior management agency.
[0114] In this embodiment of the invention, when the second vehicle-mounted device reports the abnormal behavior of the first vehicle-mounted device to the abnormal behavior management agency, it needs to provide relevant evidence of the abnormal behavior. The evidence of the abnormal behavior includes, but is not limited to: the identity information of the first vehicle-mounted device; a security certificate related to the data quality level of the first vehicle-mounted device; and message field filling requirements related to the data quality level of the first vehicle-mounted device.
[0115] The following specific examples illustrate the vehicle-to-everything (V2X) communication method described in the embodiments of the present invention.
[0116] The second vehicle-mounted device, based on the security certificate related to the data quality level of the first vehicle-mounted device carried in the basic security message sent by the first vehicle-mounted device, obtains the data quality level of the first vehicle-mounted device as meeting one of the following three conditions:
[0117] Scenario 1: The data quality level of the first vehicle-mounted device is Level A;
[0118] Scenario 2: The data quality level of the first vehicle-mounted device is Level B;
[0119] Scenario 3: The data quality level of the first vehicle-mounted device is level C;
[0120] Furthermore, the second vehicle-mounted device parses the basic security messages to determine whether the first vehicle-mounted device exhibits any abnormal behavior.
[0121] If scenario 1 is met, the second vehicle-mounted device, based on the basic security message and the message field filling requirements related to the data quality level, determines that the first vehicle-mounted device exhibits abnormal behavior in the following situations:
[0122] The basic security message does not carry the required message fields corresponding to Level A, that is, the values of one or more fields in Table 2, namely DE_TransmissionState, DE_SteeringWheelAngle, DE_BrakePedalStatus, DE_BrakeAppliedStatus, DE_TractionControlStatus, DE_VehicleEventFlags, DE_ExteriorLights, and DE_PositionConfidence, are not filled;
[0123] In the basic security messages, the message fields corresponding to level A were not filled according to the values indicated by the message field filling requirements. For example, in Table 2, the value of DE_TransmissionState is 9, which is not within the specified value range; the value of DE_StabilityControlStatus is 5, which is not within the specified value range; and the value of DE_PositionConfidence is 5, which is not within the specified value range.
[0124] If scenario 2 is met, the second vehicle-mounted device, based on the basic security message and the message field filling requirements related to the data quality level, determines that the first vehicle-mounted device exhibits abnormal behavior in the following situations:
[0125] The basic security message contains message fields that are not available in Level B, namely the values of DE_VehicleEventFlags and / or DE_ExteriorLights in Table 2.
[0126] In the basic security message, the message fields corresponding to level B that are not filled according to the values indicated by the message field filling requirements, such as one or more of the fields in Table 2, namely DE_TransmissionState, DE_BrakePedalStatus, DE_AuxiliaryBrakeStatus, DE_PositionConfidence, DE_SpeedConfidence, and DE_SteeringWheelAngleConfidence, are not invalid values; the value of DE_SpeedConfidence is 3, which is not within the specified value range.
[0127] If scenario 3 is met, the second vehicle-mounted device, based on the basic security message and the message field filling requirements related to the data quality level, determines that the first vehicle-mounted device exhibits abnormal behavior in the following situations:
[0128] The basic security message carries message fields that cannot be obtained at level C, namely the values of DE_VehicleEventFlags and / or DE_ExteriorLights in Table 2.
[0129] In the basic security message, the message fields corresponding to level C that are not filled according to the values indicated by the message field filling requirements, such as one or more of the following fields in Table 2: DE_TransmissionState, DE_BrakePedalStatus, DE_AuxiliaryBrakeStatus, DE_PositionConfidence, DE_SpeedConfidence, and DE_SteeringWheelAngleConfidence, have non-invalid values; the value of DE_PositionConfidence is 20, which is not within the specified value range; the value of DE_SpeedConfidence is 9, which is not within the specified value range.
[0130] Therefore, existing technologies lack methods for determining whether in-vehicle devices exhibit abnormal behavior and do not consider the differences in data quality between aftermarket in-vehicle devices. For example, some devices can integrate in-vehicle networks to obtain data such as gear position, steering wheel angle, headlights, and brake status, while others cannot. Some devices can integrate in-vehicle sensors to obtain perception data such as obstacles, traffic events, and traffic participants, while others cannot. Devices with high data quality levels must provide high-precision data (position, speed, acceleration, heading angle, etc.), while devices with low data quality levels only need to provide low-precision data. In the vehicle-to-everything (V2X) communication method described in this invention, in one aspect, the message fields of basic safety messages sent by first in-vehicle devices (aftermarket in-vehicle devices) with different data quality levels have different message field filling requirements. For example, some fields are defined as mandatory for high data quality levels, while those for low data quality levels are defined as optional or not required; some fields are defined as taking invalid values for low data quality levels; the same field has different value range requirements for different data quality levels, etc. Furthermore, when the same message field value corresponds to different data quality levels, some may be judged as abnormal behavior, while others may be judged as normal behavior.
[0131] On the other hand, the second vehicle-mounted device (receiver) uses the security certificate related to the data quality level of the aftermarket vehicle-mounted device carried in the basic security message, combined with the message fields associated with the data quality level, to comprehensively determine whether the sender has abnormal behavior and whether it has triggered abnormal behavior reporting.
[0132] In summary, the embodiments of this invention fully consider the differences between different data quality levels of aftermarket vehicle-mounted devices, and provide a refined scheme for judging abnormal behavior of aftermarket vehicle-mounted devices, which can avoid false alarms and missed alarms. Furthermore, the embodiments of this invention facilitate real-time monitoring of messages sent by aftermarket vehicle-mounted devices by market participants, ensuring the data quality of aftermarket vehicle-mounted devices and preventing security incidents caused by the recipient using incorrect data.
[0133] like Figure 3 As shown, embodiments of the present invention also provide a vehicle-to-everything (V2X) communication device applied to a first in-vehicle device, the device comprising:
[0134] The first acquisition module 301 is used to acquire the data quality level of the first vehicle-mounted device and to acquire the security certificate related to the data quality level.
[0135] The generation module 302 is used to generate a basic security message based on the data quality level;
[0136] The sending module 303 is used to send the basic security message, which carries the security certificate.
[0137] Optionally, in the aforementioned vehicle-to-everything (V2X) communication device, the first acquisition module 301 is specifically used for:
[0138] Based on the device information of the first vehicle-mounted device, the data quality level of the first vehicle-mounted device is obtained; wherein, the device information of the first vehicle-mounted device includes one or more of the following:
[0139] Installation method information; functional requirements information; performance requirements information; equipment capability information.
[0140] Optionally, in the aforementioned vehicle-to-everything (V2X) communication device, the security certificate includes one or more of the following:
[0141] Application identifier, used to indicate the type of the first vehicle-mounted device;
[0142] A service-specific license used to indicate the data quality level of the first onboard device.
[0143] Optionally, in the aforementioned vehicle-to-everything (V2X) communication device, the generation module 302 is specifically used for:
[0144] Obtain the message field population requirements related to the data quality level;
[0145] Generate a basic security message based on the message field population requirements.
[0146] Optionally, in the vehicle-to-everything (V2X) communication device, the message field filling requirement is used to indicate the message fields included in the basic security message, and to indicate the values of the message fields.
[0147] Optionally, in the vehicle-to-everything (V2X) communication device, the message field includes one or more of the following:
[0148] The integration degree field between the first vehicle-mounted device and the vehicle; the capability confidence field of the first vehicle-mounted device; and the integration degree field between the first vehicle-mounted device and the vehicle-mounted sensors.
[0149] Optionally, in the vehicle-to-everything (V2X) communication device, the integration degree field between the first in-vehicle device and the vehicle includes one or more of the following:
[0150] Vehicle gear position field; Vehicle steering wheel angle field; Vehicle braking system status field; Vehicle event flag field; Vehicle light status field.
[0151] Optionally, in the vehicle-to-everything (V2X) communication device, the capability confidence field of the first on-board device includes one or more of the following:
[0152] Position confidence field; speed confidence field; heading angle confidence field; steering wheel angle confidence field.
[0153] Optionally, in the vehicle-to-everything (V2X) communication device, the integration degree field of the first vehicle-mounted device and the vehicle-mounted sensor includes one or more of the following:
[0154] Obstacle information field; Traffic incident information field; Traffic participant information field.
[0155] The vehicle-to-everything (V2X) communication device provided in this embodiment of the invention can execute the above-described V2X communication method embodiment. Its implementation principle and technical effects are similar, and will not be repeated here.
[0156] like Figure 4 As shown, embodiments of the present invention also provide a vehicle-to-everything (V2X) communication device applied to a second vehicle-mounted device, the device comprising:
[0157] A receiving module is used to receive a basic security message sent by a first vehicle-mounted device, the basic security message carrying a security certificate related to the data quality level of the first vehicle-mounted device;
[0158] The second acquisition module is used to acquire the data quality level of the first vehicle-mounted device based on the security certificate;
[0159] The judgment module is used to determine whether the first vehicle-mounted device has abnormal behavior based on the basic security message and the data quality level.
[0160] Optionally, in the aforementioned vehicle-to-everything (V2X) communication device, wherein,
[0161] Optionally, the vehicle-to-everything (V2X) communication device further includes:
[0162] The reporting module is used to report abnormal behaviors of the first vehicle-mounted device to the abnormal behavior management agency.
[0163] Optionally, in the aforementioned vehicle-to-everything (V2X) communication device, the security certificate includes one or more of the following:
[0164] Application identifier, used to indicate the type of the first vehicle-mounted device;
[0165] A service-specific license used to indicate the data quality level of the first onboard device.
[0166] Optionally, in the aforementioned vehicle-to-everything (V2X) communication device, the determination module 403 includes:
[0167] The acquisition unit is used to acquire the message field filling requirements related to the data quality level;
[0168] The judgment unit is used to determine whether the first vehicle-mounted device has abnormal behavior based on the basic security message and the message field filling requirements.
[0169] Optionally, in the vehicle-to-everything (V2X) communication device, the message field filling requirement is used to indicate the message fields included in the basic security message, and to indicate the values of the message fields.
[0170] Optionally, in the vehicle-to-everything (V2X) communication device, the message field includes one or more of the following:
[0171] The integration degree field between the first vehicle-mounted device and the vehicle; the capability confidence field of the first vehicle-mounted device; and the integration degree field between the first vehicle-mounted device and the vehicle-mounted sensors.
[0172] Optionally, in the aforementioned vehicle-to-everything (V2X) communication device, the determining unit is specifically used for:
[0173] If the basic security message does not include the message field indicated by the message field filling requirement, then it is determined that the first vehicle-mounted device has abnormal behavior;
[0174] If the basic security message includes a message field for which the message field filling requirement is not indicated, then it is determined that the first vehicle-mounted device has abnormal behavior;
[0175] If the value of the message field in the basic security message does not meet the value of the message field indicated by the message field filling requirement, then it is determined that the first vehicle-mounted device has abnormal behavior.
[0176] Optionally, in the vehicle-to-everything (V2X) communication device, the integration degree field between the first in-vehicle device and the vehicle includes one or more of the following:
[0177] Vehicle gear position field; Vehicle steering wheel angle field; Vehicle braking system status field; Vehicle event flag field; Vehicle light status field.
[0178] Optionally, in the vehicle-to-everything (V2X) communication device, the capability confidence field of the first on-board device includes one or more of the following:
[0179] Position confidence field; speed confidence field; heading angle confidence field; steering wheel angle confidence field.
[0180] Optionally, in the vehicle-to-everything (V2X) communication device, the integration degree field of the first vehicle-mounted device and the vehicle-mounted sensor includes one or more of the following:
[0181] Obstacle information field; Traffic incident information field; Traffic participant information field.
[0182] The vehicle-to-everything (V2X) communication device provided in this embodiment of the invention can execute the above-described V2X communication method embodiment. Its implementation principle and technical effects are similar, and will not be repeated here.
[0183] like Figure 5 As shown, this embodiment of the invention provides a vehicle-to-everything (V2X) communication device, including: a processor 501; and a memory 502 connected to the processor 501 via a bus interface. The memory 502 is used to store programs and data used by the processor 501 when performing operations, and the processor 501 calls and executes the programs and data stored in the memory 502.
[0184] The vehicle-to-everything (V2X) communication device is either the first in-vehicle device or the second in-vehicle device.
[0185] When the vehicle network communication device is the first on-board device, the transceiver 503, under the control of the processor 501, performs the following steps:
[0186] Obtain the data quality level of the first vehicle-mounted device, and obtain the security certificate related to the data quality level;
[0187] Processor 501 reads the program from memory 502 and performs the following steps:
[0188] Based on the data quality level, a basic security message is generated;
[0189] Transceiver 503 is also used, under the control of processor 501, to perform the following steps:
[0190] Send the basic security message, which carries the security certificate.
[0191] Among them, Figure 5 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 501) and memory (memory 502). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 503 can be multiple elements, including transmitters and transceivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, the user interface 504 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.
[0192] The processor 501 is responsible for managing the bus architecture and general processing, while the memory 902 can store the data used by the processor 501 when performing operations.
[0193] Optionally, the processor 501 is specifically used to read the program from the memory 502 and perform the following steps:
[0194] Based on the device information of the first vehicle-mounted device, the data quality level of the first vehicle-mounted device is obtained; wherein, the device information of the first vehicle-mounted device includes one or more of the following:
[0195] Installation method information; functional requirements information; performance requirements information; equipment capability information.
[0196] Optionally, the security certificate includes one or more of the following:
[0197] Application identifier, used to indicate the type of the first vehicle-mounted device;
[0198] A service-specific license used to indicate the data quality level of the first onboard device.
[0199] Optionally, the processor 501 is specifically used to read the program from the memory 502 and perform the following steps:
[0200] Obtain the message field population requirements related to the data quality level;
[0201] Generate a basic security message based on the message field population requirements.
[0202] Optionally, the message field filling requirement is used to indicate the message fields included in the basic security message, and to indicate the values of the message fields.
[0203] Optionally, the message field includes one or more of the following:
[0204] The integration degree field between the first vehicle-mounted device and the vehicle; the capability confidence field of the first vehicle-mounted device; and the integration degree field between the first vehicle-mounted device and the vehicle-mounted sensors.
[0205] Optionally, the integration degree field between the first in-vehicle device and the vehicle includes one or more of the following:
[0206] Vehicle gear position field; Vehicle steering wheel angle field; Vehicle braking system status field; Vehicle event flag field; Vehicle light status field.
[0207] Optionally, the capability confidence field of the first vehicle-mounted device includes one or more of the following:
[0208] Position confidence field; speed confidence field; heading angle confidence field; steering wheel angle confidence field.
[0209] Optionally, the integration degree field of the first vehicle-mounted device and the vehicle-mounted sensor includes one or more of the following:
[0210] Obstacle information field; Traffic incident information field; Traffic participant information field.
[0211] Alternatively, when the vehicle network communication device is the second on-board device, the transceiver 503, under the control of the processor 501, performs the following steps:
[0212] Receive a basic security message sent by a first vehicle-mounted device, the basic security message carrying a security certificate related to the data quality level of the first vehicle-mounted device;
[0213] Processor 501 reads the program from memory 502 and performs the following steps:
[0214] Based on the security certificate, obtain the data quality level of the first vehicle-mounted device;
[0215] Based on the basic security messages and the data quality level, determine whether the first vehicle-mounted device exhibits abnormal behavior.
[0216] Optionally, the transceiver 503 is also configured to perform the following steps under the control of the processor 501:
[0217] Report the abnormal behavior of the first on-board device to the abnormal behavior management agency.
[0218] Optionally, the security certificate includes one or more of the following:
[0219] Application identifier, used to indicate the type of the first vehicle-mounted device;
[0220] A service-specific license used to indicate the data quality level of the first onboard device.
[0221] Optionally, the processor 501 is specifically used to read the program from the memory 502 and perform the following steps:
[0222] Obtain the message field population requirements related to the data quality level;
[0223] Based on the basic security message and the message field filling requirements, determine whether the first vehicle-mounted device exhibits abnormal behavior.
[0224] Optionally, the message field filling requirement is used to indicate the message fields included in the basic security message, and to indicate the values of the message fields.
[0225] Optionally, the message field includes one or more of the following:
[0226] The integration degree field between the first vehicle-mounted device and the vehicle; the capability confidence field of the first vehicle-mounted device; and the integration degree field between the first vehicle-mounted device and the vehicle-mounted sensors.
[0227] Optionally, the processor 501 is specifically used to read the program from the memory 502 and perform the following steps:
[0228] If the basic security message does not include the message field indicated by the message field filling requirement, then it is determined that the first vehicle-mounted device has abnormal behavior;
[0229] If the basic security message includes a message field for which the message field filling requirement is not indicated, then it is determined that the first vehicle-mounted device has abnormal behavior;
[0230] If the value of the message field in the basic security message does not meet the value of the message field indicated by the message field filling requirement, then it is determined that the first vehicle-mounted device has abnormal behavior.
[0231] Optionally, the integration degree field between the first in-vehicle device and the vehicle includes one or more of the following:
[0232] Vehicle gear position field; Vehicle steering wheel angle field; Vehicle braking system status field; Vehicle event flag field; Vehicle light status field.
[0233] Optionally, the capability confidence field of the first vehicle-mounted device includes one or more of the following:
[0234] Position confidence field; speed confidence field; heading angle confidence field; steering wheel angle confidence field.
[0235] Optionally, the integration degree field of the first vehicle-mounted device and the vehicle-mounted sensor includes one or more of the following:
[0236] Obstacle information field; Traffic incident information field; Traffic participant information field.
[0237] A specific embodiment of the present invention also provides a computer-readable storage medium storing a computer program thereon. When the program is executed by a processor, it implements the steps in the above-described vehicle network communication method and achieves the same technical effect. To avoid repetition, it will not be described again here.
[0238] In addition, embodiments of the present invention also provide a computer program product, including computer instructions, which, when executed by a processor, implement the above-described... Figure 1 or Figure 2The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.
[0239] In the several embodiments provided by this invention, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between devices or units, and may be electrical, mechanical, or other forms.
[0240] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can be physically comprised separately, or two or more units can be integrated into one unit. The integrated unit described above can be implemented in hardware or in the form of hardware plus software functional units.
[0241] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions that cause a computer device (which may be a personal computer, server, or network device, etc.) to execute some steps of the transmission and reception methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0242] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.
Claims
1. A vehicle-to-everything (V2X) communication method, characterized in that, Applied to a first vehicle-mounted device, the method includes: Obtain the data quality level of the first vehicle-mounted device, and obtain the security certificate related to the data quality level; Based on the data quality level, a basic security message is generated; Send the basic security message, which carries the security certificate.
2. The vehicle-to-everything (V2X) communication method according to claim 1, characterized in that, Obtaining the data quality level of the first vehicle-mounted device includes: Based on the device information of the first vehicle-mounted device, the data quality level of the first vehicle-mounted device is obtained; wherein, the device information of the first vehicle-mounted device includes one or more of the following: Installation method information; functional requirements information; performance requirements information; equipment capability information.
3. The vehicle-to-everything (V2X) communication method according to claim 1, characterized in that, The security certificate includes one or more of the following: Application identifier, used to indicate the type of the first vehicle-mounted device; A service-specific license used to indicate the data quality level of the first onboard device.
4. The vehicle-to-everything (V2X) communication method according to claim 1, characterized in that, Based on the data quality level, a basic security message is generated, including: Obtain the message field population requirements related to the data quality level; Generate a basic security message based on the message field population requirements.
5. The vehicle-to-everything (V2X) communication method according to claim 4, characterized in that, The message field filling requirement is used to indicate the message fields included in the basic security message, and to indicate the values of the message fields.
6. The vehicle-to-everything (V2X) communication method according to claim 5, characterized in that, The message fields include one or more of the following: The integration degree field between the first vehicle-mounted device and the vehicle; the capability confidence field of the first vehicle-mounted device; and the integration degree field between the first vehicle-mounted device and the vehicle-mounted sensors.
7. The vehicle-to-everything (V2X) communication method according to claim 6, characterized in that, The integration degree field between the first in-vehicle device and the vehicle includes one or more of the following: Vehicle gear position field; Vehicle steering wheel angle field; Vehicle braking system status field; Vehicle event flag field; Vehicle light status field.
8. The vehicle-to-everything (V2X) communication method according to claim 6, characterized in that, The capability confidence field of the first vehicle-mounted device includes one or more of the following: Position confidence field; speed confidence field; heading angle confidence field; steering wheel angle confidence field.
9. The vehicle-to-everything (V2X) communication method according to claim 6, characterized in that, The integration degree field of the first vehicle-mounted device and vehicle-mounted sensors includes one or more of the following: Obstacle information field; Traffic incident information field; Traffic participant information field.
10. A vehicle-to-everything (V2X) communication method, characterized in that, Applied to a second vehicle-mounted device, the method includes: Receive a basic security message sent by a first vehicle-mounted device, the basic security message carrying a security certificate related to the data quality level of the first vehicle-mounted device; Based on the security certificate, obtain the data quality level of the first vehicle-mounted device; Based on the basic security messages and the data quality level, determine whether the first vehicle-mounted device exhibits abnormal behavior.
11. The vehicle-to-everything (V2X) communication method according to claim 10, characterized in that, If it is determined that the first vehicle-mounted device exhibits abnormal behavior, the method further includes: Report the abnormal behavior of the first on-board device to the abnormal behavior management agency.
12. The vehicle-to-everything (V2X) communication method according to claim 10, characterized in that, The security certificate includes one or more of the following: Application identifier, used to indicate the type of the first vehicle-mounted device; A service-specific license used to indicate the data quality level of the first onboard device.
13. The vehicle-to-everything (V2X) communication method according to claim 10, characterized in that, Based on the basic security messages and the data quality level, determine whether the first vehicle-mounted device exhibits abnormal behavior, including: Obtain the message field population requirements related to the data quality level; Based on the basic security message and the message field filling requirements, determine whether the first vehicle-mounted device exhibits abnormal behavior.
14. The vehicle-to-everything (V2X) communication method according to claim 13, characterized in that, The message field filling requirement is used to indicate the message fields included in the basic security message, and to indicate the values of the message fields.
15. The vehicle-to-everything (V2X) communication method according to claim 14, characterized in that, The message fields include one or more of the following: The integration degree field between the first vehicle-mounted device and the vehicle; the capability confidence field of the first vehicle-mounted device; and the integration degree field between the first vehicle-mounted device and the vehicle-mounted sensors.
16. The vehicle-to-everything (V2X) communication method according to claim 14, characterized in that, Based on the basic security message and the message field filling requirements, determine whether the first vehicle-mounted device exhibits abnormal behavior, including: If the basic security message does not include the message field indicated by the message field filling requirement, then it is determined that the first vehicle-mounted device has abnormal behavior; If the basic security message includes a message field for which the message field filling requirement is not indicated, then it is determined that the first vehicle-mounted device has abnormal behavior; If the value of the message field in the basic security message does not meet the value of the message field indicated by the message field filling requirement, then it is determined that the first vehicle-mounted device has abnormal behavior.
17. The vehicle-to-everything (V2X) communication method according to claim 15, characterized in that, The integration degree field between the first in-vehicle device and the vehicle includes one or more of the following: Vehicle gear position field; Vehicle steering wheel angle field; Vehicle braking system status field; Vehicle event flag field; Vehicle light status field.
18. The vehicle-to-everything (V2X) communication method according to claim 15, characterized in that, The capability confidence field of the first vehicle-mounted device includes one or more of the following: Position confidence field; speed confidence field; heading angle confidence field; steering wheel angle confidence field.
19. The vehicle-to-everything (V2X) communication method according to claim 15, characterized in that, The integration degree field of the first vehicle-mounted device and vehicle-mounted sensors includes one or more of the following: Obstacle information field; Traffic incident information field; Traffic participant information field.
20. A vehicle-to-everything (V2X) communication device, characterized in that, Applied to a first vehicle-mounted device, the device includes: The first acquisition module is used to acquire the data quality level of the first vehicle-mounted device and to acquire the security certificate related to the data quality level. The generation module is used to generate basic security messages based on the data quality level. A sending module is used to send the basic security message, which carries the security certificate.
21. A vehicle-to-everything (V2X) communication device, characterized in that, Applied to a second vehicle-mounted device, the device includes: A receiving module is used to receive a basic security message sent by a first vehicle-mounted device, the basic security message carrying a security certificate related to the data quality level of the first vehicle-mounted device; The second acquisition module is used to acquire the data quality level of the first vehicle-mounted device based on the security certificate; The judgment module is used to determine whether the first vehicle-mounted device has abnormal behavior based on the basic security message and the data quality level.
22. A vehicle-to-everything (V2X) communication device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the vehicle-to-everything (V2X) communication method as described in any one of claims 1 to 9, or implements the V2X communication method as described in any one of claims 10 to 19.
23. A readable storage medium, characterized in that, The readable storage medium stores a program that, when executed by a processor, implements the vehicle-to-everything (V2X) communication method as described in any one of claims 1 to 9, or implements the V2X communication method as described in any one of claims 10 to 19.
24. A computer program product, characterized in that, It includes computer instructions, which, when executed by a processor, implement the vehicle-to-everything (V2X) communication method as described in any one of claims 1 to 9, or implement the V2X communication method as described in any one of claims 10 to 19.