Data transmission method, device, equipment, medium, vehicle and system
By adding functional safety identifiers and objects to data transmission, the method ensures secure and authentic data communication, addressing the lack of safety mechanisms in DDS and enhancing data transmission security.
Patent Information
- Application Number
- CN202310798931.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-30
- Publication Date
- 2024-12-31
AI Technical Summary
Data Distribution Service (DDS) lacks a functional safety mechanism, limiting its use in scenarios requiring secure data transmission, and existing solutions do not meet functional safety communication requirements.
Incorporating a functional safety identifier and object into data transmission to enable safety checks, ensuring secure data transmission by adding a functional safety identifier to a preset position of the data and creating a functional safety object to verify data integrity and source authenticity during transmission.
Enhances data transmission security by meeting functional safety communication requirements with minimal resource overhead through the use of functional safety identifiers and objects, improving data integrity and authenticity verification.
Smart Images
Figure CN119232413A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of data transmission, and in particular to a data transmission method, device, equipment, medium, vehicle and system. Background Art
[0002] Data Distribution Service (DDS) is a new generation of distributed real-time communication middleware protocol. It adopts a publish / subscribe architecture, provides data-centric connection services and functions between the operating system and applications, and provides rich quality of service (QoS) strategies to ensure real-time, efficient and flexible data distribution, which can meet the needs of various distributed real-time communication applications.
[0003] However, since the data distribution service itself does not have a functional safety mechanism and cannot meet the functional safety communication requirements of data, the security of data transmission is low, resulting in the data distribution service only being used for non-functional safety communication services, which limits the use scenarios of the data distribution service. Summary of the invention
[0004] In order to solve the above technical problems, the present disclosure provides a data transmission method, device, equipment, medium, vehicle and system.
[0005] A first aspect of the present disclosure provides a data transmission method, the method comprising:
[0006] In response to a functional safety implementation requirement of the first data, adding a functional safety identifier to a preset position of the first data to obtain second data;
[0007] Creating a functional safety object in the second data to obtain target data;
[0008] The target data is sent to the subscriber so that the subscriber can perform safety detection on the target data based on the functional safety identifier and functional safety object in the target data to determine whether the target data is safe.
[0009] A second aspect of the present disclosure provides a data transmission method, the method comprising:
[0010] Receive target data sent by the publisher;
[0011] Based on the functional safety identification and functional safety objects in the target data, the target data is security checked to determine whether the target data is safe.
[0012] A third aspect of the present disclosure provides a data transmission device, including:
[0013] An adding module, configured to add a functional safety identifier to a preset position of the first data in response to a functional safety implementation requirement of the first data, so as to obtain second data;
[0014] A creation module, used for creating a functional safety object in the second data to obtain target data;
[0015] The sending module is used to send the target data to the subscriber, so that the subscriber can perform safety detection on the target data based on the functional safety identifier and functional safety object in the target data to determine whether the target data is safe.
[0016] A fourth aspect of the present disclosure provides a data transmission device, including:
[0017] A receiving module, used for receiving target data sent by the publisher;
[0018] The detection module is used to perform safety detection on the target data based on the functional safety identification and functional safety objects in the target data to determine whether the target data is safe.
[0019] A fifth aspect of the present disclosure provides a computer device, including a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the above-mentioned data transmission method can be implemented.
[0020] A sixth aspect of the present disclosure provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the above-mentioned data transmission method can be implemented.
[0021] The seventh aspect of the present disclosure provides a vehicle, including the data transmission device of the third aspect or the fourth aspect or the computer device of the fifth aspect or the computer-readable storage medium of the sixth aspect, which can implement the above-mentioned data transmission method.
[0022] An eighth aspect of the present disclosure provides a data transmission system, including a publisher and a subscriber, the data transmission system including:
[0023] The publisher is used to respond to the functional safety implementation requirements of the first data, add a functional safety identifier to a preset position of the first data, obtain the second data, create a functional safety object in the second data, obtain the target data, and send the target data to the subscriber;
[0024] The subscriber receives the target data sent by the publisher and performs security checks on the target data based on the functional safety identifier and functional safety object in the target data to determine whether the target data is safe.
[0025] Compared with the prior art, the technical solution provided by the present invention has the following advantages:
[0026] The present invention obtains second data by adding a functional safety identifier at a preset position of the first data in response to the functional safety implementation requirements of the first data; creates a functional safety object in the second data to obtain target data; and sends the target data to the subscriber, so that the subscriber can perform a security check on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe. The functional safety identifier and the functional safety object can be added to the data, and during the transmission of the data, the security of the data is determined based on the functional safety identifier and the functional safety object, thereby meeting the functional safety communication requirements of the data and improving the security of data transmission. In addition, only the functional safety identifier and the functional safety object need to be added to the data for functional safety certification, and the resource overhead is relatively small. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0028] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0029] Figure 1 is a flow chart of a data transmission method provided by an embodiment of the present disclosure;
[0030] Figure 2 is a flow chart of another data transmission method provided by an embodiment of the present disclosure;
[0031] Figure 3 is a flow chart of another data transmission method provided by an embodiment of the present disclosure;
[0032] Figure 4 is a flow chart of another data transmission method provided by an embodiment of the present disclosure;
[0033] Figure 5 is a flow chart of another data transmission method provided by an embodiment of the present disclosure;
[0034] Figure 6 is a structural schematic diagram of a data transmission device provided by an embodiment of the present disclosure;
[0035] Figure 7 is a structural schematic diagram of another data transmission device provided by an embodiment of the present disclosure;
[0036] Figure 8It is a structural diagram of a computer device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION
[0037] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.
[0038] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.
[0039] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.
[0040] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
[0041] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0042] In response to the defects of related technologies in data transmission, the embodiments of the present disclosure provide a data transmission method, apparatus, equipment, medium, vehicle and system, which can add functional safety identification and functional safety objects to the data. During the data transmission process, the security of the data is determined based on the functional safety identification and functional safety objects, and the functional safety communication requirements of the data are met, thereby improving the security of data transmission. In addition, only the functional safety identification and functional safety objects need to be added to the data for functional safety certification, and the resource overhead is small.
[0043] The data transmission method provided by the embodiments of the present disclosure may be executed by a computer device, which may be understood as any device with processing and computing capabilities, and may include but is not limited to mobile terminals such as smart phones, laptops, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), vehicle equipment, wearable devices, etc., as well as fixed electronic devices such as digital TVs, desktop computers, smart home devices, etc.
[0044] The data transmission method provided by the embodiment of the present disclosure can be applied to a data transmission system, which includes a publisher, a publisher protocol stack, a subscriber, and a subscriber protocol stack. The publisher can be understood as the data sending end, such as an application; the publisher protocol stack can be understood as the publisher's data distribution service protocol stack; the subscriber can be understood as the data receiving end, such as an application; the subscriber protocol stack can be understood as the subscriber's data distribution service protocol stack. The data transmission system can be a data transmission distribution service (DDS) system.
[0045] The data transmission method provided by the embodiment of the present disclosure can be used for communication security between different domains and intra-domain communication security within a smart car.
[0046] In order to better understand the inventive concept of the embodiments of the present disclosure, the technical solutions of the embodiments of the present disclosure are described below in conjunction with exemplary embodiments.
[0047] Figure 1 1 is a flow chart of a data transmission method provided by an embodiment of the present disclosure. The method can be executed by a computer device, in which case the computer device serves as the publisher of the data. Figure 1 As shown, the data transmission method provided in this embodiment includes the following steps:
[0048] Step 110: In response to the functional safety implementation requirement of the first data, a functional safety identifier is added to a preset position of the first data to obtain second data.
[0049] In the embodiment of the present disclosure, the first data can be understood as the data to be sent by the publisher. If there is a functional safety implementation requirement for the first data, the publisher can respond to the functional safety implementation requirement of the first data by adding a functional safety identifier to a preset position of the first data, obtain the second data, and send the second data to the publisher's protocol stack. The functional safety identifier can be understood as an identifier that the data needs functional safety implementation.
[0050] In some embodiments, the publisher may obtain a target sending sequence number of the first data; determine the target sending sequence number as a functional safety identifier, add the functional safety identifier to a preset position of the first data, and obtain the second data.
[0051] The sending sequence number can be understood as the sequence number of the data sent by the publisher, which can be achieved by adding a counter in the data writing object (Data Writer). The sending sequence number of the data is determined based on the counting function of the counter. For example, when the publisher does not send data, the value of the counter can be initialized to 0, that is, the sequence number of the data sent by the publisher is 0. If the first data is the data sent by the publisher for the first time, the value of the counter can be updated to 1, that is, the target sending sequence number of the first data is determined to be 1. The value of the counter increases monotonically throughout the life cycle of the publisher. If the counting function of the counter is not enabled, the value of the counter can be initialized to a preset value, which is different from the sending sequence number and can be set as needed. For example, the preset value can be 0xFFFFFFFF.
[0052] Step 120: Create a functional safety object in the second data to obtain target data.
[0053] In the embodiment of the present disclosure, after receiving the second data, the publisher protocol stack in the publisher may create a functional safety object in the second data to obtain the target data.
[0054] For example, the writer function of the data writer object (Data Writer) can be overloaded, and functional safety object creation logic can be added to the function.
[0055] Among them, the functional safety object can be understood as data for realizing functional safety. The functional safety object may include items such as data checksum, source identification, transmission cycle, and sending sequence number. The items of the functional safety object can be set as needed and are not limited here.
[0056] Among them, the checksum of the data can be understood as the accumulation of the number of bits of the data transmitted, which can be used to indicate the integrity of the data. The checksum of the data can be used by the data receiver to verify whether the complete data has been received. When the data transmission is completed, the receiver can judge whether all the data has been received based on the checksum. If the checksum matches, it means that the data transmission has been completed and the data received by the receiver is complete data. The calculation method of the checksum can refer to the relevant technology and will not be repeated here.
[0057] The source identifier of the data can be understood as a unique identifier of the data source, which may include a host identifier, application identifier, instance identifier, etc. indicating the data source.
[0058] The data transmission cycle can be understood as the duration of data transmission and the duration of data reception. In normal transmission, the publisher should send data within the transmission cycle, and the subscriber should receive data within the transmission cycle. For example, the data transmission cycle can be achieved through the deadline policy in the Quality of Service (QoS) policy.
[0059] Step 130: Send the target data to the subscriber, so that the subscriber can perform a safety check on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe.
[0060] In an embodiment of the present disclosure, the publisher protocol stack in the publisher can send target data to the subscriber. After receiving the target data, the subscriber protocol stack in the subscriber can parse the target data to obtain the functional safety identifier and functional safety object in the target data, and then perform a safety check on the target data based on the functional safety identifier and functional safety object in the target data to determine whether the target data is safe.
[0061] In an embodiment of the present disclosure, a functional safety identifier is added to a preset position of the first data in response to a functional safety implementation requirement of the first data to obtain second data; a functional safety object is created in the second data to obtain target data; and the target data is sent to a subscriber so that the subscriber can perform a security check on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe. The functional safety identifier and the functional safety object can be added to the data, and during the transmission of the data, the security of the data is determined based on the functional safety identifier and the functional safety object, thereby meeting the functional safety communication requirements of the data and improving the security of data transmission. In addition, only the functional safety identifier and the functional safety object need to be added to the data for functional safety certification, and resource overhead is relatively small.
[0062] Figure 2 1 is a flow chart of a data transmission method provided by an embodiment of the present disclosure. The method can be executed by a computer device, in which case the computer device serves as the publisher of the data. Figure 2 As shown, the data transmission method provided in this embodiment includes the following steps:
[0063] Step 210: In response to the functional safety implementation requirement of the first data, a functional safety identifier is added to a preset position of the first data to obtain second data.
[0064] The contents of the embodiment of the present disclosure may refer to the contents of the above step 110 and will not be repeated here.
[0065] Step 220: Calculate the target checksum of the second data, and obtain the target source identifier and target transmission period of the second data.
[0066] In the disclosed embodiments, the checksum of data can be understood as the accumulation of the number of bits of data transmission, which can be used to indicate the integrity of data. The checksum of data can be used by the data receiver to verify whether complete data has been received. When data transmission is completed, the receiver can determine whether all data has been received based on the checksum. If the checksum matches, it means that the data transmission has been completed and the data received by the receiver is complete data. The calculation method of the checksum can refer to the relevant technology and will not be repeated here.
[0067] The source identifier of the data can be understood as a unique identifier of the data source, which may include a host identifier, application identifier, instance identifier, etc. indicating the data source.
[0068] The data transmission cycle can be understood as the duration of data sending and data receiving. During normal transmission, the publisher should send data within the transmission cycle, and the subscriber should receive data within the transmission cycle.
[0069] In an embodiment of the present disclosure, a publisher protocol stack in a publisher may calculate a target checksum of the second data based on the second data, and obtain a target source identifier and a target transmission period of the second data from a quality of service (QoS) profile of the second data.
[0070] Step 230: increment the current data sending sequence number to obtain the target sending sequence number corresponding to the second data.
[0071] In the disclosed embodiment, a data sending sequence number is set in the publisher protocol stack in the publisher. When the publisher protocol stack does not send data, the data sending sequence number is 0. Each time the publisher protocol stack sends data, the data sending sequence number is incremented.
[0072] In the disclosed embodiment, the publisher protocol stack in the publisher may increment the current data sending sequence number to obtain a target sending sequence number corresponding to the second data.
[0073] Step 240: construct a functional safety object based on at least one of a target checksum, a target source identifier, a target transmission period, and a target sending sequence number.
[0074] In an embodiment of the present disclosure, after obtaining the target checksum, target source identifier, target transmission cycle and target sending sequence number of the second data, the publisher protocol stack in the publisher can construct a functional safety object based on the target checksum, target source identifier, target transmission cycle and target sending sequence number.
[0075] Step 250: Add the functional safety object to the second data to obtain target data.
[0076] In the embodiment of the present disclosure, after constructing the functional safety object, the publisher may add the functional safety object to the second data to obtain the target data.
[0077] Step 260: Send the target data to the subscriber, so that the subscriber can perform a safety check on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe.
[0078] The contents of the embodiment of the present disclosure may refer to the contents of the above step 130 and will not be repeated here.
[0079] Therefore, functional safety identification and functional safety objects can be added to the data. During the data transmission process, the security of the data can be determined based on the functional safety identification and functional safety objects, so the functional safety communication requirements of the data can be met, the security of data transmission is improved, and only the functional safety identification and functional safety objects need to be added to the data for functional safety certification, with less resource overhead.
[0080] Figure 3 1 is a flow chart of a data transmission method provided by an embodiment of the present disclosure. The method can be executed by a computer device, in which case the computer device serves as the publisher of the data. Figure 3 As shown, the data transmission method provided in this embodiment includes the following steps:
[0081] Step 310: Obtain a service quality configuration file of the first data.
[0082] In the embodiment of the present disclosure, the quality of service (QoS) configuration file of the first data may be understood as a quality requirement file of the user for the transmission of the first data.
[0083] In the embodiment of the present disclosure, the publisher may obtain a service quality configuration file of the first data.
[0084] Step 320 , determine whether there is a functional safety label in the service quality configuration file and the functional safety label includes a safety requirement identifier. If so, execute steps 330 - 360 ; otherwise, execute step 370 .
[0085] In the embodiment of the present disclosure, the publisher may determine whether there is a functional safety label in the service quality configuration file and whether the functional safety label includes a safety requirement identifier.
[0086] For example, a functional safety tag could be<function_safety> true< / function_safety> ,<function_safety> false< / function_safety> The functional safety label can be set as needed and is not limited here. Among them, "true" is the safety requirement mark, and "false" is the non-safety requirement mark.
[0087] Step 330: If yes, determine that the first data has functional safety implementation requirements.
[0088] In the embodiment of the present disclosure, if there is a functional safety tag in the service quality configuration file and the functional safety tag includes a security requirement identifier, the publisher may determine that there is a functional safety implementation requirement for the first data.
[0089] Step 340: In response to the functional safety implementation requirement of the first data, a functional safety identifier is added to a preset position of the first data to obtain second data.
[0090] Step 350: In response to the functional safety identifier in the second data, create a functional safety object in the second data to obtain target data.
[0091] Step 360: Send the target data to the subscriber, so that the subscriber can perform a safety check on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe.
[0092] Steps 340-360 in the embodiment of the present disclosure may refer to the contents of the above-mentioned steps 110-130, which will not be repeated here.
[0093] Step 370: Otherwise, determine that the first data does not have any functional safety implementation requirements.
[0094] In the embodiment of the present disclosure, if there is no functional safety label in the service quality configuration file or the functional safety label does not include a safety requirement identifier, the publisher may determine that there is no functional safety implementation requirement for the first data.
[0095] Therefore, the functional safety implementation requirements can be flexibly configured according to the needs of data transmission. When there are functional safety implementation requirements in the data, functional safety identifiers and functional safety objects can be added to the data. During the data transmission process, the security of the data is determined based on the functional safety identifiers and functional safety objects to meet the functional safety communication requirements of the data, thereby improving the security of data transmission. In addition, only the functional safety identifiers and functional safety objects need to be added to the data for functional safety certification, with less resource overhead.
[0096] In some embodiments of the present disclosure, after sending target data to a subscriber, the publisher may obtain a target transmission period of the target data, and if the target data is not successfully sent within the target transmission period, a first alarm message may be issued, and the first alarm message may include a target data sending timeout. Thus, the publisher may be informed of the data sending timeout in a timely manner, thereby improving the security of data transmission.
[0097] The publisher protocol stack in the publisher may obtain the target transmission period of the target data from the service quality configuration file of the target data.
[0098] Figure 4 1 is a flow chart of a data transmission method provided by an embodiment of the present disclosure. The method can be executed by a computer device, in which case the computer device serves as a data subscriber. Figure 4 As shown, the data transmission method provided in this embodiment includes the following steps:
[0099] Step 410: Receive target data sent by the publisher.
[0100] In the embodiment of the present disclosure, the subscriber protocol stack in the subscriber can receive the target data sent by the publisher.
[0101] Step 420: Based on the functional safety identifier and the functional safety object in the target data, perform a safety check on the target data to determine whether the target data is safe.
[0102] In the embodiment of the present disclosure, the subscriber protocol stack in the subscriber can perform a security check on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe.
[0103] Specifically, when both the functional safety identification and the functional safety object in the target data meet the preset requirements, the target data is determined to be safe; when any one of the functional safety identification and the functional safety object in the target data does not meet the preset requirements, the target data is determined to be unsafe. The preset requirements can be set as needed and are not limited here.
[0104] Therefore, during the data transmission process, the security of the data can be determined based on the functional safety identification and functional safety objects in the data, thereby meeting the functional safety communication requirements of the data and improving the security of data transmission. In addition, only the functional safety identification and functional safety objects need to be added to the data for functional safety certification, with less resource overhead.
[0105] Figure 5 1 is a flow chart of a data transmission method provided by an embodiment of the present disclosure. The method can be executed by a computer device, in which case the computer device serves as a data subscriber. Figure 5As shown, the data transmission method provided in this embodiment includes the following steps:
[0106] Step 510: Receive target data sent by the publisher.
[0107] Step 520 , determine whether there is a functional safety identifier in the target data, if so, execute steps 530 - 580 , otherwise execute step 590 .
[0108] In the embodiment of the present disclosure, after receiving the target data, the subscriber protocol stack in the subscriber may determine whether there is a functional safety identifier in the target data.
[0109] Step 530: If the functional safety identifier exists in the target data, the functional safety object of the target data is parsed to obtain the target checksum, target source identifier, target transmission period and target sending sequence number of the target data.
[0110] In an embodiment of the present disclosure, if there is a functional safety identifier in the target data, the subscriber protocol stack in the subscriber can parse the functional safety object of the target data to obtain the target checksum, target source identifier, target transmission cycle and target sending sequence number of the target data.
[0111] Step 540: increment the current data receiving sequence number to obtain the target receiving sequence number corresponding to the target data, and calculate the checksum to be verified of the target data.
[0112] In the disclosed embodiment, a data receiving sequence number is set in the subscriber protocol stack in the subscriber. When the subscriber protocol stack does not receive data, the data receiving sequence number is 0. Each time the subscriber protocol stack receives data, the data receiving sequence number is incremented.
[0113] Among them, the receiving sequence number can be understood as the sequence number of the data received by the subscriber, which can be achieved by adding a counter in the data reading object (Data Reader). The receiving sequence number of the data is determined based on the counting function of the counter. For example, when the subscriber does not receive the data, the value of the counter can be initialized to 0, that is, the sequence number of the data received by the subscriber is 0. If the target data is the data received by the subscriber for the first time, the value of the counter can be updated to 1, that is, the target receiving sequence number corresponding to the target data is determined to be 1. The value of the counter increases monotonically throughout the life cycle of the subscriber. If the counting function of the counter is not enabled, the value of the counter can be initialized to a preset value. The preset value is different from the sending sequence number and can be set as needed. For example, the preset value can be 0xFFFFFFFF.
[0114] In the disclosed embodiment, after receiving the target data, the subscriber protocol stack in the subscriber can increment the current data reception sequence number in the subscriber protocol stack to obtain the target reception sequence number corresponding to the target data, and calculate the checksum to be verified of the target data. The calculation method of the checksum can refer to the relevant technology and will not be repeated here.
[0115] Step 550, determine whether the target receiving sequence number is the same as the target sending sequence number, whether the checksum to be verified is the same as the target checksum, whether the target source identifier belongs to the source identifier in the preset whitelist, and whether the target data is received within the target transmission cycle. If so, execute step 560, otherwise, execute steps 570-580.
[0116] In the embodiment of the present disclosure, the preset whitelist (safety-peer-list) can be understood as a pre-set identifier of a safe data source. For example, the construction of the preset whitelist can be achieved by configuring a QoS profile.
[0117] In the disclosed embodiment, the subscriber protocol stack can determine whether the target receiving sequence number is the same as the target sending sequence number, whether the checksum to be verified is the same as the target checksum, whether the target source identifier belongs to the source identifier in the preset whitelist, and whether the target data is received within the target transmission cycle.
[0118] Step 560: When the target receiving sequence number is the same as the target sending sequence number, the checksum to be verified is the same as the target checksum, the target source identifier belongs to the source identifier in the preset whitelist, and the target data is received within the target transmission period, the target data is determined to be safe.
[0119] In the disclosed embodiment, when the target receiving sequence number is the same as the target sending sequence number, the checksum to be verified is the same as the target checksum, the target source identifier belongs to the source identifier in the preset whitelist, and the target data is received within the target transmission cycle, the subscriber protocol stack in the subscriber can determine that the target data is safe. When determining that the target data is safe, the subscriber protocol stack sends the target data to the subscriber.
[0120] Specifically, if the target receiving sequence number is the same as the target sending sequence number, it means that the target data received by the subscriber protocol stack in the subscriber is a correct information sequence; if the to-be-verified checksum of the target data is the same as the target checksum, it means that the subscriber protocol stack in the subscriber has received the complete target data; if the target source identifier belongs to the source identifier in the preset whitelist, it means that the source of the target data is safe; if the target data is received within the target transmission cycle, it means that the subscriber protocol stack in the subscriber has received the target data on time.
[0121] Step 570: If any of the following conditions is not met: the target receiving sequence number is the same as the target sending sequence number, the checksum to be verified is the same as the target checksum, the target source identifier belongs to the source identifier in the preset whitelist, and the target data is received within the target transmission period, it is determined that the target data is not safe.
[0122] In the embodiment of the present disclosure, when any of the following conditions is not met: the target receiving sequence number is the same as the target sending sequence number, the checksum to be verified is the same as the target checksum, the target source identifier belongs to the source identifier in the preset whitelist, and the target data is received within the target transmission cycle, the subscriber protocol stack in the subscriber can determine that the target data is unsafe.
[0123] Specifically, if the target receiving sequence number is different from the target sending sequence number, it means that the target data received by the subscriber protocol stack in the subscriber is an incorrect information sequence, and there may be functional safety problems such as information duplication or information loss; if the to-be-verified checksum of the target data is different from the target checksum, it means that the target data received by the subscriber protocol stack in the subscriber is incomplete, and there may be functional safety problems such as information insertion or information corruption; if the target source identifier does not belong to the source identifier in the preset whitelist, it means that the source of the target data is not safe, and there may be functional safety problems such as disguise / impersonation or incorrect information addressing; if the target data is not received within the target transmission cycle, it means that the subscriber protocol stack in the subscriber did not receive the target data on time, and there may be functional safety problems such as information delay or information loss.
[0124] Step 580: When it is determined that the target data is not safe, a second warning message is issued, where the second warning message includes the target data being not safe and / or the reason why the target data is not safe.
[0125] In the embodiment of the present disclosure, when it is determined that the target data is unsafe, the subscriber protocol stack in the subscriber may generate a second warning message and send the second warning message, and the second warning message may include the target data is unsafe and / or the reason why the target data is unsafe. For example, the second warning message may be sent to the subscriber based on a preset callback interface, and the callback interface may be on_function_safety_ret.
[0126] Therefore, when it is determined that the target data is not secure, an alarm message indicating that the target data is not secure and / or the reason why the target data is not secure can be issued, thereby improving the security of data transmission.
[0127] Step 590: If the functional safety identifier does not exist in the target data, it is determined that the target data does not have a functional safety implementation requirement.
[0128] In the embodiment of the present disclosure, if the functional safety identifier does not exist in the target data, the subscriber protocol stack in the subscriber may determine that the target data does not have a functional safety implementation requirement.
[0129] Therefore, functional safety identification and functional safety objects can be added to the data. During the data transmission process, the security of the data can be determined based on the functional safety identification and functional safety objects, so the functional safety communication requirements of the data can be met, the security of data transmission is improved, and only the functional safety identification and functional safety objects need to be added to the data for functional safety certification, with less resource overhead.
[0130] Figure 6 is a schematic diagram of the structure of a data transmission device provided by an embodiment of the present disclosure, and the device can be understood as the above-mentioned computer device or some functional modules in the above-mentioned computer device. Figure 6 As shown, the data transmission device 600 includes:
[0131] An adding module 610 is used to add a functional safety identifier to a preset position of the first data in response to a functional safety implementation requirement of the first data to obtain second data;
[0132] A creation module 620, configured to create a functional safety object in the second data to obtain target data;
[0133] The sending module 630 is used to send the target data to the subscriber, so that the subscriber can perform safety detection on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe.
[0134] Optionally, the creation module 620 includes:
[0135] A calculation submodule, used to calculate a target checksum of the second data, and obtain a target source identifier and a target transmission period of the second data;
[0136] A first incrementing submodule, used to increment the current data sending sequence number to obtain a target sending sequence number corresponding to the second data;
[0137] A construction submodule for constructing a functional safety object based on a target checksum, a target source identifier, a target transmission period, and a target send sequence number;
[0138] The adding submodule is used to add the functional safety object to the second data to obtain the target data.
[0139] Optionally, the data transmission device 600 includes:
[0140] A first acquisition module, used to acquire a service quality configuration file of the first data;
[0141] A determination module, used to determine whether there is a functional safety label in the service quality configuration file and whether the functional safety label includes a preset safety identifier;
[0142] A first determination module, configured to determine if, if so, whether there is a functional safety implementation requirement for the first data;
[0143] The second determination module is used to determine that the first data does not have any functional safety implementation requirements.
[0144] Optionally, the data transmission device 600 includes:
[0145] A second acquisition module is used to acquire a target transmission period of target data;
[0146] The first alarm module is used to issue a first alarm message if the target data is not successfully sent within the target transmission period, and the first alarm message includes a target data sending timeout.
[0147] The data transmission device provided by the embodiment of the present disclosure can achieve the above Figure 1-Figure 3 The execution method and beneficial effects of the method in any embodiment are similar and will not be described in detail here.
[0148] Figure 7 is a schematic diagram of the structure of a data transmission device provided by an embodiment of the present disclosure, and the device can be understood as the above-mentioned computer device or some functional modules in the above-mentioned computer device. Figure 7 As shown, the data transmission device 700 includes:
[0149] Receiving module 710, used to receive target data sent by the publisher;
[0150] The detection module 720 is used to perform a safety detection on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe.
[0151] Optionally, the detection module 720 includes:
[0152] A first determination submodule is used to determine the safety of the target data when both the functional safety identifier and the functional safety object in the target data meet the preset requirements;
[0153] The second determination submodule is used to determine that the target data is unsafe when any one of the functional safety identifier and the functional safety object in the target data does not meet the preset requirements.
[0154] Optionally, the detection module 720 includes:
[0155] The first judgment submodule is used to judge whether there is a functional safety mark in the target data;
[0156] A parsing submodule, for parsing the functional safety object of the target data, if any, to obtain a target checksum, a target source identifier, a target transmission period, and a target sending sequence number of the target data;
[0157] The second incrementing submodule is used to increment the current data receiving sequence number to obtain the target receiving sequence number corresponding to the target data, and calculate the checksum to be verified of the target data;
[0158] The second judgment submodule is used to judge whether the target receiving sequence number is the same as the target sending sequence number, whether the checksum to be verified is the same as the target checksum, whether the target source identifier belongs to the source identifier in the preset whitelist, and whether the target data is received within the target transmission period;
[0159] The third determination submodule is used to determine that the target data is safe when the target receiving sequence number is the same as the target sending sequence number, the to-be-verified checksum is the same as the target checksum, the target source identifier belongs to the source identifier in the preset whitelist, and the target data is received within the target transmission period.
[0160] The fourth determination submodule is used to determine that the target data is unsafe when any of the following items is not met: the target receiving sequence number is the same as the target sending sequence number, the checksum to be verified is the same as the target checksum, the target source identifier belongs to the source identifier in the preset whitelist, and the target data is received within the target transmission cycle.
[0161] Optionally, the detection module 720 includes:
[0162] The fifth determination submodule is used to determine that the target data does not have a functional safety implementation requirement if the functional safety identifier does not exist in the target data.
[0163] Optionally, the data transmission device 700 includes:
[0164] The second alarm module is used to issue a second alarm message when it is determined that the target data is not safe, and the second alarm message includes the target data being not safe and / or the reason why the target data is not safe.
[0165] The data transmission device provided by the embodiment of the present disclosure can achieve the above Figure 4-Figure 5 The execution method and beneficial effects of the method in any embodiment are similar and will not be described in detail here.
[0166] The embodiments of the present disclosure also provide a computer device, which includes a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method of any of the above embodiments can be implemented, and its execution method and beneficial effects are similar and will not be repeated here.
[0167] Figure 8 is a schematic diagram of the structure of a computer device provided by an embodiment of the present disclosure, such as Figure 8As shown, the computer device 800 may include a processor 810 and a memory 820, wherein the memory 820 stores a computer program 821, and when the computer program 821 is executed by the processor 810, the method provided by any of the above embodiments can be implemented, and its execution method and beneficial effects are similar and will not be repeated here.
[0168] Of course, to simplify, Figure 8 Only some of the components related to the present invention in the computer device 800 are shown, and components such as a bus, an input / output interface, an input device, and an output device are omitted. In addition, according to specific application conditions, the computer device 800 may also include any other appropriate components.
[0169] An embodiment of the present disclosure provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method of any of the above embodiments can be implemented. The execution method and beneficial effects are similar and will not be repeated here.
[0170] The above-mentioned computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.
[0171] The computer program may be written in any combination of one or more programming languages to write program codes for performing the operations of the disclosed embodiments, including object-oriented programming languages such as Java, C++, etc., and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer device, partially on the user's device, as a separate software package, partially on the user's computer device and partially on a remote computer device, or entirely on a remote computer device or server.
[0172] An embodiment of the present disclosure provides a vehicle, which includes the above-mentioned data transmission device or the above-mentioned computer device or the above-mentioned computer-readable storage medium, and can implement the method of any of the above-mentioned embodiments. The execution method and beneficial effects are similar and will not be repeated here.
[0173] The embodiment of the present disclosure provides a data transmission system, which includes a publisher and a subscriber;
[0174] The publisher is used to respond to the functional safety implementation requirements of the first data, add a functional safety identifier to a preset position of the first data, obtain the second data, create a functional safety object in the second data, obtain the target data, and send the target data to the subscriber;
[0175] The subscriber receives the target data sent by the publisher and performs security checks on the target data based on the functional safety identifier and functional safety object in the target data to determine whether the target data is safe.
[0176] The data transmission system may be a data distribution service (DDS) system.
[0177] Therefore, the data transmission system can implement the method of any of the above embodiments, and its execution method and beneficial effects are similar, which will not be repeated here.
[0178] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.
[0179] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.
[0180] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A data transmission method, characterized in that: include: In response to a functional safety implementation requirement of the first data, adding a functional safety identifier to a preset position of the first data to obtain second data; Creating a functional safety object in the second data to obtain target data; The target data is sent to a subscriber, so that the subscriber can perform a safety check on the target data based on a functional safety identifier and a functional safety object in the target data to determine whether the target data is safe.
2. The method according to claim 1, characterized in that The step of creating a functional safety object in the second data to obtain target data includes: Calculating a target checksum of the second data, and obtaining a target source identifier and a target transmission period of the second data; Incrementing the current data sending sequence number to obtain a target sending sequence number corresponding to the second data; constructing a functional safety object based on the target checksum, the target source identifier, the target transmission period, and the target transmission sequence number; The functional safety object is added to the second data to obtain target data.
3. The method according to claim 1, characterized in that The step of adding a functional safety mark to a preset position of the first data to obtain the second data includes: Obtaining a target sending sequence number of the first data; The target sending sequence number is determined as a functional safety identifier, and the functional safety identifier is added to a preset position of the first data to obtain second data.
4. The method according to claim 1, characterized in that: In response to the functional safety implementation requirement of the first data, before adding the functional safety mark to the preset position of the first data, the method further includes: Obtaining a quality of service profile of the first data; Determining whether there is a functional safety label in the quality of service configuration file and the functional safety label includes a preset safety identifier; If so, it is determined that the first data has functional safety implementation requirements; Otherwise, it is determined that there is no functional safety implementation requirement for the first data.
5. The method according to claim 1, characterized in that After sending the target data to the subscriber, the method further includes: Acquire a target transmission period of the target data; If the target data is not successfully sent within the target transmission period, a first alarm message is issued, wherein the first alarm message includes a timeout for sending the target data.
6. A data transmission method, characterized in that: include: Receive target data sent by the publisher; Based on the functional safety identifier and the functional safety object in the target data, a safety check is performed on the target data to determine whether the target data is safe.
7. The method according to claim 6, characterized in that The performing safety detection on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe includes: When both the functional safety identifier and the functional safety object in the target data meet preset requirements, determining that the target data is safe; When any one of the functional safety identifier and the functional safety object in the target data does not meet the preset requirement, it is determined that the target data is unsafe.
8. The method according to claim 6, characterized in that The performing safety detection on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe includes: Determining whether there is a functional safety identifier in the target data; If it exists, parse the functional safety object of the target data to obtain the target checksum, target source identifier, target transmission period and target sending sequence number of the target data; Incrementing the current data receiving sequence number to obtain the target receiving sequence number corresponding to the target data, and calculating the checksum to be verified of the target data; Determine whether the target receiving sequence number is the same as the target sending sequence number, whether the to-be-verified checksum is the same as the target checksum, whether the target source identifier belongs to a source identifier in a preset whitelist, and whether the target data is received within the target transmission period; When the target receiving sequence number is the same as the target sending sequence number, the to-be-verified checksum is the same as the target checksum, the target source identifier belongs to the source identifier in the preset whitelist, and the target data is received within the target transmission period, the target data is determined to be safe; When any of the following conditions is not met: the target receiving sequence number is the same as the target sending sequence number, the checksum to be verified is the same as the target checksum, the target source identifier belongs to the source identifier in the preset whitelist, and the target data is received within the target transmission cycle, the target data is determined to be unsafe.
9. The method according to claim 8, characterized in that After determining whether the target data contains a functional safety identifier, the method further includes: If the functional safety identifier does not exist in the target data, it is determined that the target data does not have a functional safety implementation requirement.
10. The method according to claim 6, characterized in that After determining whether the target data is safe, the method further includes: When it is determined that the target data is not secure, a second warning message is issued, wherein the second warning message includes the target data being not secure and / or a reason why the target data is not secure.
11. A data transmission device, characterized in that: include: an adding module, configured to add a functional safety identifier to a preset position of the first data in response to a functional safety implementation requirement of the first data, so as to obtain second data; A creation module, used to create a functional safety object in the second data to obtain target data; The sending module is used to send the target data to the subscriber, so that the subscriber can perform safety detection on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe.
12. A data transmission device, characterized in that: include: A receiving module, used for receiving target data sent by the publisher; The detection module is used to perform a safety detection on the target data based on the functional safety identifier and the functional safety object in the target data to determine whether the target data is safe.
13. A computer device, characterized in that: include: A memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the data transmission method according to any one of claims 1 to 10 is implemented.
14. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the data transmission method according to any one of claims 1 to 10 is implemented.
15. A vehicle, characterized in that: It comprises the data transmission device as claimed in claim 11 or 12 or the computer device as claimed in claim 13 or the computer-readable storage medium as claimed in claim 14.
16. A data transmission system, characterized in that: Including a publisher and a subscriber, the data transmission system includes: The publisher is used to respond to the functional safety implementation requirements of the first data, add a functional safety identifier to a preset position of the first data, obtain second data, create a functional safety object in the second data, obtain target data, and send the target data to the subscriber; The subscriber is used to receive target data sent by the publisher; based on the functional safety identifier and functional safety object in the target data, perform security detection on the target data to determine whether the target data is safe.