A data transmission method, apparatus, device, medium and product

Abstract

A data transmission method, device, equipment, medium and product are disclosed. The method comprises: receiving handshake information request sent by a data receiver, and establishing a mapping relationship between handshake information and original information of data; generating lightweight data of the deterministic operating system according to the handshake information; sending the handshake information and the lightweight data to the data receiver, so that the data receiver analyzes the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data. Through the technical scheme of the present application, in the case that the data sender is deployed with a deterministic operating system, the running memory and transmission bandwidth required for data transmission are saved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communication technology, and in particular to a data transmission method, apparatus, device, medium and product. Background Technology

[0002] Trace tools are dynamic tracing tools built into the operating system kernel. They are used to monitor and analyze kernel behavior in real time, helping developers debug performance issues, understand code execution paths, or troubleshoot system anomalies. Trace tools generate data during application.

[0003] The existing Trace message format is as follows: Figure 1 As shown, the Trace message format includes: message type ID, name (the name of the trigger source), message content-1, message content-2, ... message content-n. Since the trigger source name is stored as a string, a single data message requires approximately 64 bytes of memory. Once the system is running, there will be a continuous stream of message records, requiring significant amounts of RAM and bandwidth during data transmission. Summary of the Invention

[0004] This invention provides a data transmission method, apparatus, device, medium, and product that saves the running memory and transmission bandwidth required for data transmission when the data sender has a deterministic operating system deployed on it.

[0005] According to one aspect of the present invention, a data transmission method is provided, performed by a data sender having a deterministic operating system deployed thereon, the data transmission method comprising:

[0006] Receive handshake information requests sent by the data receiver and establish a mapping relationship between the handshake information and the original data information;

[0007] Lightweight data for the deterministic operating system is generated based on the handshake information;

[0008] The handshake information and the lightweight data are sent to the data receiver so that the data receiver can parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

[0009] In some embodiments of the present invention, the handshake information includes: an event deterministic information identifier and event deterministic information;

[0010] The lightweight data for generating the deterministic operating system based on the handshake information includes:

[0011] Lightweight data is generated based on the event deterministic information identifier and the event content of the corresponding original information.

[0012] In some embodiments of the present invention, before sending the handshake information and lightweight data to the data receiver, the method further includes:

[0013] Get the target event type set;

[0014] Generate a handshake information set corresponding to each target event type in the target event type set, wherein the handshake information set includes at least two handshake information sets.

[0015] In some embodiments of the present invention, sending the handshake information to the data receiver includes:

[0016] Obtain the communication performance parameters of the data sender;

[0017] Based on the communication performance parameters of the data sender, the handshake information set corresponding to each target event type is split to obtain at least two sets of handshake information;

[0018] For any set of handshake information, the set of handshake information is sent as a single message frame to the data receiver.

[0019] In some embodiments of the present invention, the event deterministic information identifier includes: an event content identifier and an event type identifier, wherein the event type identifier includes: a task type identifier and an interruption type identifier.

[0020] According to one aspect of the present invention, a data transmission method is provided, performed by a data receiver, the data transmission method comprising:

[0021] A handshake information request is sent to the data sender so that the data sender can establish a mapping relationship between the handshake information and the original information of the data, wherein the data sender has a deterministic operating system deployed;

[0022] Receive handshake information sent by the data sender and lightweight data of the deterministic operating system, wherein the lightweight data is generated by the data sender based on the handshake information;

[0023] The lightweight data is parsed based on the mapping relationship established by the handshake information to obtain the original information of the data.

[0024] In some embodiments of the present invention, the handshake information includes: an event deterministic information identifier and event deterministic information, and the lightweight data includes: an event deterministic information identifier and the event content of the original information;

[0025] The lightweight data is parsed based on the mapping relationship established by the handshake information to obtain the original information of the data, including:

[0026] A mapping relationship between event deterministic information identifiers and event deterministic information is established based on the handshake information;

[0027] Based on the event deterministic information identifier in the lightweight data, the mapping relationship is queried to obtain the event deterministic information in the original information;

[0028] The original information of the data is determined based on the event content in the lightweight data and the event deterministic information in the original information.

[0029] In some embodiments of the present invention, the handshake information consists of at least two sets;

[0030] Before parsing the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data, the method further includes:

[0031] For any set of handshake information, after receiving the handshake information, a mapping relationship between event deterministic information identifiers and event deterministic information is established based on the set of handshake information.

[0032] In some embodiments of the present invention, sending a handshake information request to the data sender includes:

[0033] Upon receiving the trigger command, a handshake information request is sent to the data sender.

[0034] According to another aspect of the present invention, a data transmission apparatus is provided, configured in a data sender, the data sender having a deterministic operating system deployed thereon, the data transmission apparatus comprising:

[0035] The handshake information request receiving module is used to receive handshake information requests sent by the data receiver and establish a mapping relationship between the handshake information and the original information of the data.

[0036] A lightweight data determination module is used to generate lightweight data for the deterministic operating system based on the handshake information.

[0037] The handshake information and lightweight data sending module is used to send the handshake information and the lightweight data to the data receiver, so that the data receiver can parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

[0038] In some embodiments of the present invention, the handshake information includes: an event deterministic information identifier and event deterministic information;

[0039] The lightweight data determination module is specifically used for:

[0040] Lightweight data is generated based on the event deterministic information identifier and the event content of the corresponding original information.

[0041] In some embodiments of the present invention, it further includes:

[0042] The target event type set acquisition module is used to acquire the target event type set before sending handshake information and lightweight data to the data receiver;

[0043] The handshake information set generation module is used to generate a handshake information set corresponding to each target event type in the target event type set, wherein the handshake information set includes at least two handshake information sets.

[0044] In some embodiments of the present invention, the handshake information and lightweight data transmission module is specifically used for:

[0045] Obtain the communication performance parameters of the data sender;

[0046] Based on the communication performance parameters of the data sender, the handshake information set corresponding to each target event type is split to obtain at least two sets of handshake information;

[0047] For any set of handshake information, the set of handshake information is sent as a single message frame to the data receiver.

[0048] In some embodiments of the present invention, the event deterministic information identifier includes: an event content identifier and an event type identifier, wherein the event type identifier includes: a task type identifier and an interruption type identifier.

[0049] According to another aspect of the present invention, a data transmission apparatus is provided, configured in a data receiver, the data transmission apparatus comprising:

[0050] The handshake information request sending module is used to send a handshake information request to the data sender so that the data sender can establish a mapping relationship between the handshake information and the original information of the data, wherein the data sender has a deterministic operating system deployed.

[0051] A handshake information and lightweight data receiving module is used to receive handshake information sent by the data sender and lightweight data of the deterministic operating system, wherein the lightweight data is generated by the data sender based on the handshake information;

[0052] The parsing module is used to parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

[0053] In some embodiments of the present invention, the handshake information includes: an event deterministic information identifier and event deterministic information, and the lightweight data includes: an event deterministic information identifier and the event content of the original information;

[0054] The parsing module is specifically used for:

[0055] A mapping relationship between event deterministic information identifiers and event deterministic information is established based on the handshake information;

[0056] Based on the event deterministic information identifier in the lightweight data, the mapping relationship is queried to obtain the event deterministic information in the original information;

[0057] The original information of the data is determined based on the event content in the lightweight data and the event deterministic information in the original information.

[0058] In some embodiments of the present invention, the handshake information consists of at least two sets;

[0059] Also includes:

[0060] The mapping relationship establishment module is used to parse the lightweight data based on the mapping relationship established based on the handshake information to obtain the original information of the data. Before that, for any set of handshake information, after receiving the handshake information, the module establishes a mapping relationship between the event deterministic information identifier and the event deterministic information based on the set of handshake information.

[0061] In some embodiments of the present invention, the handshake information request sending module has the function of:

[0062] Upon receiving the trigger command, a handshake information request is sent to the data sender.

[0063] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0064] At least one processor; and

[0065] A memory communicatively connected to the at least one processor; wherein,

[0066] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data transmission method described in any embodiment of the present invention.

[0067] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the data transmission method described in any embodiment of the present invention.

[0068] According to another aspect of the present invention, a computer program product is provided, which, when executed by a processor, implements the data transmission method as described in any of the embodiments of the present invention.

[0069] The technical solution of this embodiment receives a handshake information request sent by a data receiver and establishes a mapping relationship between the handshake information and the original information of the data; generates lightweight data of the deterministic operating system based on the handshake information; and sends the handshake information and the lightweight data to the data receiver, so that the data receiver can parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data. Generating lightweight data based on the handshake information first, and then sending the handshake information and lightweight data to the data receiver, can reduce the running memory and transmission bandwidth occupied by the data. After receiving the handshake information and lightweight data, the data receiver parses the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data. This ensures that the data receiver receives the original information of the data. Thus, it achieves the effect of saving the running memory and transmission bandwidth required for data transmission when the data sender has a deterministic operating system deployed.

[0070] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0071] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0072] Figure 1 This is a schematic diagram of the Trace message format in existing technology;

[0073] Figure 2 This is a flowchart of the first data transmission method in an embodiment of the present invention;

[0074] Figure 3 This is a flowchart of the second data transmission method in an embodiment of the present invention;

[0075] Figure 4 This is a flowchart of the third data transmission method in this embodiment of the invention;

[0076] Figure 5 This is a schematic diagram of the structure of the first data transmission device in an embodiment of the present invention;

[0077] Figure 6 This is a schematic diagram of the structure of the second data transmission device in an embodiment of the present invention;

[0078] Figure 7 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0079] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0080] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0081] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0082] Example 1

[0083] Figure 2 This is a flowchart of a first data transmission method provided in an embodiment of the present invention. This embodiment is applicable to data transmission situations. The method can be executed by the data transmission device in this embodiment, which is configured in the data sender. The data sender has a deterministic operating system deployed on it. The data transmission device can be implemented in software and / or hardware, such as... Figure 2 As shown, the method specifically includes the following steps:

[0084] S201. Receive the handshake information request sent by the data receiver and establish a mapping relationship between the handshake information and the original information of the data.

[0085] In this embodiment, the deterministic operating system is a system without dynamic task creation and deletion, or a system where threads that need to be observed and recorded as traces do not dynamically create or delete tasks. It should be noted that the deterministic operating system only creates tasks upon receiving a task creation instruction and deletes tasks upon receiving a task deletion instruction. Automatic task creation and deletion will not occur.

[0086] In this embodiment, the data can be monitoring data for an event. The original information of the data includes: event deterministic information and event content. For example, the original information of the data can include: event type identifier, event content, and event content identifier. The event content identifier can be the event name, which can be the name of the event triggering source. For task scheduling, the event name is the task name in the context of the task lifecycle; for interrupted events, the event name is the interrupt name.

[0087] In this embodiment, the handshake information request is a connection establishment signal initiated by the data receiver. Its purpose is to indicate to the data sender that it wishes to perform a handshake operation to begin specific communication. The handshake information request mainly contains fields indicating the purpose of the request and the receiver's basic information.

[0088] The handshake information refers to the information sent from the data sender to the data receiver during the handshake process. In this embodiment, the handshake information includes necessary information for project operation, so as to lightweight the original information based on the handshake information to obtain lightweight data.

[0089] In this embodiment, the mapping relationship between handshake information and the original data information can be a mapping relationship between handshake information and the event deterministic information of the data. It should be noted that establishing this mapping relationship between handshake information and the original data information is for lightweight data processing, thereby saving the runtime memory and bandwidth required for data transmission.

[0090] S202. Generate lightweight data for the deterministic operating system based on the handshake information.

[0091] In this embodiment, the lightweight data of the deterministic operating system can be generated based on the handshake information by: lightweighting the original information of the data based on the handshake information to obtain the lightweight data of the deterministic operating system.

[0092] In this embodiment, the handshake information may include: an event deterministic information identifier and event deterministic information, and the lightweight data may include: an event deterministic information identifier and the event content of the original information.

[0093] Optionally, the handshake information includes: an event deterministic information identifier and event deterministic information.

[0094] In this embodiment, the event deterministic information identifier may include: an event content identifier and an event type identifier. The event type identifier includes, but is not limited to: a task type identifier, an interruption type identifier, and a custom type identifier.

[0095] When the event type identifier is a task type identifier, the event deterministic information includes: task name, running core number, and task priority; when the event type identifier is an interrupt type identifier, the event deterministic information includes: interrupt callback function and interrupt priority.

[0096] The lightweight data for generating the deterministic operating system based on the handshake information includes:

[0097] Lightweight data is generated based on the event deterministic information identifier and the event content of the corresponding original information.

[0098] In this embodiment, the event deterministic information identifier is the event deterministic information identifier in the handshake information.

[0099] In this embodiment, the lightweight data includes: an event deterministic information identifier and the event content of the corresponding original information. It should be noted that the event content can be at least two parts.

[0100] In a specific example, during data transmission, all event deterministic information is replaced with event deterministic information identifiers. Lightweight data includes: a message type ID (event type identifier), a content ID (event content identifier), and at least two message contents (event contents).

[0101] Because deterministic operating systems lack dynamic task creation and deletion, their data contains event-specific information. If the original data is transmitted during data transfer, it results in a large amount of duplicate event-specific information. Furthermore, the significant runtime and bandwidth requirements of this event-specific information lead to substantial memory and bandwidth consumption during data transmission. The technical solution provided in this embodiment uses event-specific information and its identifier as handshake information. Based on this handshake information, the original data is lightweighted to obtain lightweight data, which is then sent to the data receiver. Since the lightweight data only includes the event-specific information identifier and the corresponding event content from the original information, duplicate transmission of event-specific information is avoided, thereby saving runtime and bandwidth required for data transmission and minimizing the impact on the original business operations.

[0102] Optionally, before sending the handshake information and lightweight data to the data recipient, the method further includes:

[0103] Get the target event type set.

[0104] In this embodiment, the target event type set can be a pre-defined set of event types to be monitored. The target event type set includes at least two target event types, which include, but are not limited to: task events, interruption events, and custom events.

[0105] Generate a set of handshake information corresponding to each target event type in the target event type set.

[0106] In this embodiment, the handshake information set includes at least two handshake information sets.

[0107] In this embodiment, the method for generating the handshake information set corresponding to each target event type in the target event type set can be as follows: for any target event type in the target event type set, generate the handshake information set corresponding to the target event type. It should be noted that the handshake information set may include at least one handshake information. If the handshake information set includes only one handshake information, the handshake information can be directly sent to the data receiver. If the handshake information set includes at least two handshake information, the handshake information set needs to be split based on the communication performance parameters of the data sender, and the split handshake information sets should be sent to the data receiver separately.

[0108] In a specific example, a set of target event types is predefined, and a handshake information set is generated for each target event type. The reason for being able to divide according to event type is that the information contained in each event type may differ. For example, for a task, the event deterministic information (information that remains unchanged during execution) may include: task name, task priority, task ID, running core number, etc. For an interrupt, the event deterministic information may include: interrupt callback function and interrupt priority, etc.

[0109] The technical solution provided in this embodiment can improve the accuracy of the generated handshake information by generating a corresponding handshake information set for each target event type in the target event type set, since the event deterministic information content contained in each event type may differ.

[0110] Optionally, sending the handshake information to the data receiver includes:

[0111] Obtain the communication performance parameters of the data sender.

[0112] In this embodiment, the communication performance-related parameter can be the size of a single transmitted message. For example, if the data sender is a microcontroller unit (MCU), then the communication performance-related parameter of the data sender can be the size of a single transmitted message by the MCU.

[0113] Based on the communication performance parameters of the data sender, the handshake information set corresponding to each target event type is split to obtain at least two sets of handshake information.

[0114] In this embodiment, the handshake information set corresponding to each target event type is split according to the communication performance parameters of the data sender to obtain at least two sets of handshake information corresponding to each target event type.

[0115] For any set of handshake information, the set of handshake information is sent as a single message frame to the data receiver.

[0116] In a specific example, if a single message frame can only hold n handshake messages, and there are a total of m handshake messages (m is greater than n), then the m handshake messages are split into groups of n and sent separately.

[0117] It should be noted that since the handshake information in each frame is complete, the data receiver directly reads the handshake information in the frame after receiving it, and establishes a mapping by reading one piece of handshake information.

[0118] The technical solution provided in this embodiment, since the data sender has a limited single transmission message size, needs to split the handshake information set to obtain at least two sets of handshake information, and then send one set of handshake information as a frame message to the data receiver. This can adapt to the data sender's transmission limitations and enhance the stability of the data sender.

[0119] Optionally, the event deterministic information identifier includes: event content identifier and event type identifier, and the event type identifier includes: task type identifier and interruption type identifier.

[0120] In this embodiment, the event content identifier can be the event name, which can be the name of the event triggering source. For task scheduling and the task lifecycle, the event name is the task name; for interruption events, the event name is the interruption name.

[0121] S203. The handshake information and the lightweight data are sent to the data receiver so that the data receiver can parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

[0122] In this embodiment, the lightweight data can be at least two, and the handshake information can be at least two.

[0123] In this embodiment, the order in which the handshake information and lightweight data are sent can be either first the handshake information and then the lightweight data, or first the lightweight data and then the handshake information, or they can be sent intermittently. For example, after sending a handshake information, a lightweight data is sent, and then another handshake information is sent, and so on. This embodiment of the invention does not limit this.

[0124] In this embodiment, the data receiver parses the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data in the following ways: establishing a mapping relationship between event deterministic information identifiers and event deterministic information based on the handshake information; querying the mapping relationship according to the event deterministic information identifiers in the lightweight data to obtain the event deterministic information in the original information; and determining the original information of the data based on the event content in the lightweight data and the event deterministic information in the original information.

[0125] The technical solution of this embodiment receives a handshake information request sent by a data receiver and establishes a mapping relationship between the handshake information and the original information of the data; generates lightweight data of the deterministic operating system based on the handshake information; and sends the handshake information and the lightweight data to the data receiver, so that the data receiver can parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data. Generating lightweight data based on the handshake information first, and then sending the handshake information and lightweight data to the data receiver, reduces the amount of running memory and transmission bandwidth occupied by the data. After receiving the handshake information and lightweight data, the data receiver parses the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data. This ensures that the data receiver receives the original information of the data. It solves the problem that directly sending the original information of the data consumes a lot of resources due to the limited resources of the data sender. Therefore, it achieves the effect of no increase in hardware costs or at least no increase in resource consumption when the data sender has a deterministic operating system deployed, saving the running memory and transmission bandwidth required for data transmission and reducing the impact on the original business.

[0126] Example 2

[0127] Figure 3 This is a flowchart of the second data transmission method in this embodiment of the invention. This embodiment is applicable to data transmission situations. This method can be executed by the data transmission device in this embodiment of the invention. This device is configured in the data receiver, and the data transmission device can be implemented in software and / or hardware. Figure 3As shown, the method specifically includes the following steps:

[0128] S301. Send a handshake information request to the data sender so that the data sender can establish a mapping relationship between the handshake information and the original information of the data.

[0129] In this embodiment, the data sender deploys a deterministic operating system. A deterministic operating system is a system without dynamic task creation and deletion.

[0130] In this embodiment, the original information of the data includes: event deterministic information and event content. For example, the original information of the data may include: event type identifier, event content, and event content identifier. The event content identifier can be the event name, which can be the name of the event triggering source. For task scheduling, the event name is the task name in the context of the task lifecycle; for interrupted events, the event name is the interrupt name.

[0131] In this embodiment, the handshake information request is a connection establishment signal initiated by the data receiver. Its purpose is to indicate to the data sender that it wishes to perform a handshake operation to begin specific communication. The handshake information request mainly contains fields indicating the purpose of the request and the receiver's basic information.

[0132] The handshake information refers to the information sent from the data sender to the data receiver during the handshake process. In this embodiment, the handshake information includes necessary information for project operation, so as to lightweight the original information based on the handshake information to obtain lightweight data.

[0133] In this embodiment, the mapping relationship between handshake information and the original data information can be a mapping relationship between handshake information and the event deterministic information of the data. It should be noted that establishing this mapping relationship between handshake information and the original data information is for lightweight data processing, thereby saving the runtime memory and bandwidth required for data transmission.

[0134] Optionally, a handshake information request may be sent to the data sender, including:

[0135] Upon receiving the trigger command, a handshake information request is sent to the data sender.

[0136] In this embodiment, the trigger command can be generated after touching a preset control (physical or virtual), or after detecting preset voice information or gesture information. This embodiment of the invention does not impose any restrictions on this.

[0137] In this embodiment, the trigger command can be manually triggered by staff when a problem needs to be analyzed; or it can be automatically triggered by pre-setting trigger conditions, and generating a trigger command after the trigger conditions are met.

[0138] The technical solution provided in this embodiment sends a handshake information request to the data sender after receiving the trigger command, which enables more targeted data transmission.

[0139] S302. Receive handshake information sent by the data sender and lightweight data of the deterministic operating system, wherein the lightweight data is generated by the data sender based on the handshake information.

[0140] In this embodiment, the lightweight data of the deterministic operating system can be generated based on the handshake information by: lightweighting the original information of the data according to the handshake information to obtain the lightweight data of the deterministic operating system. Alternatively, the lightweight data can be generated based on the event deterministic information identifier and the corresponding event content of the original information.

[0141] In this embodiment, the handshake information may include: an event deterministic information identifier and event deterministic information, and the lightweight data may include: an event deterministic information identifier and the event content of the original information.

[0142] S303. Based on the mapping relationship established by the handshake information, the lightweight data is parsed to obtain the original information of the data.

[0143] In this embodiment, the lightweight data can be at least two types, and the handshake information can be at least two types. The original information of the data includes: event deterministic information and event content.

[0144] In this embodiment, the method for parsing the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data can be as follows: establish a mapping relationship between event deterministic information identifiers and event deterministic information based on the handshake information; query the mapping relationship according to the event deterministic information identifiers in the lightweight data to obtain the event deterministic information in the original information; and determine the original information of the data based on the event content in the lightweight data and the event deterministic information in the original information.

[0145] Optionally, the handshake information includes: an event deterministic information identifier and event deterministic information, and the lightweight data includes: an event deterministic information identifier and the event content of the original information.

[0146] In this embodiment, the event deterministic information identifier includes: an event content identifier and an event type identifier. The event type identifier includes, but is not limited to: a task type identifier, an interruption type identifier, and a custom type identifier.

[0147] When the event type identifier is a task type identifier, the event deterministic information includes: task name, running core number, and task priority; when the event type identifier is an interrupt type identifier, the event deterministic information includes: interrupt callback function and interrupt priority.

[0148] The lightweight data is parsed based on the mapping relationship established by the handshake information to obtain the original information of the data, including:

[0149] A mapping relationship between event deterministic information identifiers and event deterministic information is established based on the handshake information.

[0150] In this embodiment, the mapping relationship between the event deterministic information identifier and the event deterministic information can be: an event deterministic information identifier and the event deterministic information corresponding to the event deterministic information identifier. For example, the mapping relationship between the event deterministic information identifier and the event deterministic information can include: event deterministic information identifier A1, corresponding to event deterministic information X1; event deterministic information identifier A2, corresponding to event deterministic information X2; and event deterministic information identifier A3, corresponding to event deterministic information X3.

[0151] In this embodiment, the mapping relationship between event deterministic information identifier and event deterministic information based on the handshake information can be established as follows: based on the event deterministic information identifier and event deterministic information in the handshake information, a mapping relationship between event deterministic information identifier and event deterministic information is established.

[0152] In a specific example, if the handshake information includes: event deterministic information identifier A1 and event deterministic information X1, then the mapping relationship between the event deterministic information identifier and the event deterministic information is: event deterministic information identifier A1 corresponds to event deterministic information X1.

[0153] In another specific example, the host computer (data receiver) establishes a mapping between event deterministic information identifiers and event deterministic information based on the handshake information. The event deterministic information identifiers include: content ID and handshake type ID; a mapping is established between the handshake type ID and the content name; and a mapping is established between the content ID and the content verification number, as well as other information.

[0154] The mapping relationship is queried based on the event deterministic information identifier in the lightweight data to obtain the event deterministic information in the original information.

[0155] In this embodiment, lightweight data includes: event deterministic information identifier and event content.

[0156] In this embodiment, the method of obtaining the event deterministic information in the original information by querying the mapping relationship based on the event deterministic information identifier in the lightweight data can be as follows: query the mapping relationship based on the event deterministic information identifier in the lightweight data to obtain the event deterministic information corresponding to the event deterministic information identifier, and use the event deterministic information corresponding to the event deterministic information identifier as the event deterministic information in the original information.

[0157] In a specific example, the mapping relationship between event deterministic information identifiers and event deterministic information includes: event deterministic information identifier A1 corresponds to event deterministic information X1; event deterministic information identifier A2 corresponds to event deterministic information X2; and event deterministic information identifier A3 corresponds to event deterministic information X3. Lightweight data includes event deterministic information identifier A1 and event content. Based on event deterministic information identifier A1, the mapping relationship is queried to obtain event deterministic information identifier A1, corresponding to event deterministic information X1. Event deterministic information X1 is then used as the event deterministic information in the original information.

[0158] The original information of the data is determined based on the event content in the lightweight data and the event deterministic information in the original information.

[0159] In this embodiment, the original information of the data can be determined by summarizing the event content in the lightweight data and the event deterministic information in the original information to obtain the original information of the data.

[0160] In a specific example, the lightweight data includes: event content Y and event deterministic information identifier A1. The mapping relationship between event deterministic information identifiers and event deterministic information is as follows: event deterministic information identifier A1 corresponds to event deterministic information X1; event deterministic information identifier A2 corresponds to event deterministic information X2; and event deterministic information identifier A3 corresponds to event deterministic information X3. Based on the event deterministic information identifier A1, the mapping relationship is queried to obtain event deterministic information identifier A1, which corresponds to event deterministic information X1. Event deterministic information X1 is used as the event deterministic information in the original information. The original information of the data includes: event deterministic information X1 and event content Y.

[0161] The technical solution provided in this embodiment involves the data receiver establishing a mapping relationship between event deterministic information identifiers and event deterministic information based on the handshake information. Then, according to the mapping relationship, the event deterministic information corresponding to the event deterministic information identifier in the lightweight data is determined. Finally, based on the event content in the lightweight data and the event deterministic information in the original information, the original information of the data can be obtained. The data receiver can reconstruct the lightweight data based on the received handshake information to obtain the original data information. This allows for the reconstruction of the original data information even with lightweight data transmission, saving the required runtime memory and bandwidth for data transmission while ensuring the data receiver receives complete data.

[0162] Optionally, the handshake information consists of at least two sets;

[0163] Before parsing the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data, the method further includes:

[0164] For any set of handshake information, after receiving the handshake information, a mapping relationship between event deterministic information identifiers and event deterministic information is established based on the set of handshake information.

[0165] In this embodiment, the handshake information can be at least two sets. After receiving one set of handshake information, the data receiver establishes a mapping relationship between the event deterministic information identifier and the event deterministic information based on that set of handshake information. It should be noted that each set of handshake information is a message frame. That is, after receiving a message frame, the data receiver establishes a mapping relationship between the event deterministic information identifier and the event deterministic information based on the handshake information in the message.

[0166] In a specific example, if a message frame includes three handshake messages, the data receiver, after receiving the three handshake messages, establishes a mapping relationship between the event deterministic information identifier and the event deterministic information based on the three handshake messages.

[0167] The technical solution provided in this embodiment, after receiving a set of handshake information, establishes a mapping relationship between event deterministic information identifiers and event deterministic information based on the set of handshake information, which can improve the efficiency of establishing the mapping relationship and further improve the efficiency of the data receiver in parsing lightweight data.

[0168] In a specific example, the data sender can be an MCU (Microcontroller Unit Operating System). The Microcontroller Unit Operating System (MCU OS) is the operating system running on the MCU, used to manage and control the MCU's hardware resources, providing a runtime environment and various services for applications, enabling developers to more easily and efficiently develop embedded applications. The MCU OS is a deterministic operating system. The MCU OS can also be a vehicle control OS, a software operating system used to control automotive electronic systems. It is the core and software stack of the in-vehicle intelligent computing platform, running on the resource-constrained MCUs within various control units of the vehicle. The data receiver can be a host computer. For example... Figure 4 As shown, the host computer sends a handshake information request to the MCU. The MCU, based on the trace content (raw data information) it needs to record, internally encapsulates the handshake information (splitting the data according to the size of a single transmission message). Since the size of a single transmission message is one handshake message, n handshake messages are sent to the host computer as a single frame. The host computer establishes a corresponding mapping relationship based on the received handshake information. The MCU continuously sends lightweight data to the host computer based on the MCU OS's operating status. The host computer combines the lightweight data and the corresponding mapping relationship to parse the lightweight data and obtain the raw data information. The handshake information includes: an event deterministic information identifier and event deterministic information. The event deterministic information identifier includes: a handshake type ID and a content ID. The event deterministic information corresponding to the handshake type ID includes the content name, and the event deterministic information corresponding to the content ID includes: the content verification number and other information. The handshake information is set up so that in subsequent lightweight data, only the event deterministic information identifier can represent the event deterministic information.

[0169] The technical solution of this embodiment sends a handshake information request to the data sender, enabling the data sender to establish a mapping relationship between the handshake information and the original data information. The data sender deploys a deterministic operating system. The receiver receives the handshake information sent by the data sender and lightweight data from the deterministic operating system, where the lightweight data is generated by the data sender based on the handshake information. The lightweight data is parsed based on the mapping relationship established by the handshake information to obtain the original data information. This approach enables the data sender to perform lightweight processing on the original data based on the handshake information, and the data receiver to restore the original data based on the handshake information. Even with a deterministic operating system deployed on the data sender, this ensures that the data receiver receives complete data while saving the required memory and bandwidth for data transmission.

[0170] Example 3

[0171] Figure 5 This is a schematic diagram of the structure of a first data transmission device in an embodiment of the present invention. This embodiment is applicable to data transmission scenarios. The device is configured in the data sender, which has a deterministic operating system deployed thereon. The data transmission device can be implemented in software and / or hardware, such as... Figure 5 As shown, the data transmission device specifically includes: a handshake information request receiving module 501, a lightweight data determination module 502, and a handshake information and lightweight data sending module 503.

[0172] The handshake information request receiving module is used to receive handshake information requests sent by the data receiver and establish a mapping relationship between the handshake information and the original information of the data.

[0173] A lightweight data determination module is used to generate lightweight data for the deterministic operating system based on the handshake information.

[0174] The handshake information and lightweight data sending module is used to send the handshake information and the lightweight data to the data receiver, so that the data receiver can parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

[0175] Optionally, the handshake information includes: an event deterministic information identifier and event deterministic information;

[0176] The lightweight data determination module is specifically used for:

[0177] Lightweight data is generated based on the event deterministic information identifier and the event content of the corresponding original information.

[0178] Optional, also includes:

[0179] The target event type set acquisition module is used to acquire the target event type set before sending handshake information and lightweight data to the data receiver;

[0180] The handshake information set generation module is used to generate a handshake information set corresponding to each target event type in the target event type set, wherein the handshake information set includes at least two handshake information sets.

[0181] Optionally, the handshake information and lightweight data transmission module is specifically used for:

[0182] Obtain the communication performance parameters of the data sender;

[0183] Based on the communication performance parameters of the data sender, the handshake information set corresponding to each target event type is split to obtain at least two sets of handshake information;

[0184] For any set of handshake information, the set of handshake information is sent as a single message frame to the data receiver.

[0185] Optionally, the event deterministic information identifier includes: event content identifier and event type identifier, and the event type identifier includes: task type identifier and interruption type identifier.

[0186] The above-mentioned products can execute the data transmission method provided in any embodiment of the present invention, and have the corresponding functional modules and beneficial effects of the execution method.

[0187] Example 4

[0188] Figure 6 This is a schematic diagram of a second data transmission device in an embodiment of the present invention. This embodiment is applicable to data transmission scenarios. The device can be implemented using software and / or hardware, and is configured in the data receiver, such as... Figure 6 As shown, the data transmission device specifically includes: a handshake information request sending module 601, a handshake information and lightweight data receiving module 602, and a parsing module 603.

[0189] The handshake information request sending module is used to send a handshake information request to the data sender so that the data sender can establish a mapping relationship between the handshake information and the original information of the data. The data sender has a deterministic operating system deployed.

[0190] A handshake information and lightweight data receiving module is used to receive handshake information sent by the data sender and lightweight data of the deterministic operating system, wherein the lightweight data is generated by the data sender based on the handshake information;

[0191] The parsing module is used to parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

[0192] Optionally, the handshake information includes: an event deterministic information identifier and event deterministic information, and the lightweight data includes: an event deterministic information identifier and the event content of the original information;

[0193] The parsing module is specifically used for:

[0194] A mapping relationship between event deterministic information identifiers and event deterministic information is established based on the handshake information;

[0195] Based on the event deterministic information identifier in the lightweight data, the mapping relationship is queried to obtain the event deterministic information in the original information;

[0196] The original information of the data is determined based on the event content in the lightweight data and the event deterministic information in the original information.

[0197] Optionally, the handshake information consists of at least two sets;

[0198] Also includes:

[0199] The mapping relationship establishment module is used to parse the lightweight data based on the mapping relationship established based on the handshake information to obtain the original information of the data. Before that, for any set of handshake information, after receiving the handshake information, the module establishes a mapping relationship between the event deterministic information identifier and the event deterministic information based on the set of handshake information.

[0200] Optionally, the handshake information request sending module has the following functions:

[0201] Upon receiving the trigger command, a handshake information request is sent to the data sender.

[0202] The above-mentioned products can execute the data transmission method provided in any embodiment of the present invention, and have the corresponding functional modules and beneficial effects of the execution method.

[0203] Example 5

[0204] Figure 7 A schematic diagram of an electronic device 60 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0205] like Figure 7As shown, the electronic device 60 includes at least one processor 61 and a memory, such as a read-only memory (ROM) 62 and a random access memory (RAM) 63, communicatively connected to the at least one processor 61. The memory stores computer programs executable by the at least one processor. The processor 61 can perform various appropriate actions and processes based on the computer program stored in the ROM 62 or loaded into the RAM 63 from storage unit 68. The RAM 63 may also store various programs and data required for the operation of the electronic device 60. The processor 61, ROM 62, and RAM 63 are interconnected via a bus 64. An input / output (I / O) interface 65 is also connected to the bus 64.

[0206] Multiple components in electronic device 60 are connected to I / O interface 65, including: input unit 66, such as keyboard, mouse, etc.; output unit 67, such as various types of monitors, speakers, etc.; storage unit 68, such as disk, optical disk, etc.; and communication unit 69, such as network card, modem, wireless transceiver, etc. Communication unit 69 allows electronic device 60 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0207] Processor 61 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 61 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 61 performs the various methods and processes described above, such as data transfer methods.

[0208] In some embodiments, the data transfer method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 68. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 60 via ROM 62 and / or communication unit 69. When the computer program is loaded into RAM 63 and executed by processor 61, one or at least two steps of the data transfer method described above may be performed. Alternatively, in other embodiments, processor 61 may be configured to perform the data transfer method by any other suitable means (e.g., by means of firmware).

[0209] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0210] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0211] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0212] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0213] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0214] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0215] In one embodiment, the present invention further includes a computer program product, which includes a computer program that, when executed by a processor, implements the data transmission method of any embodiment of the present invention.

[0216] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0217] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0218] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data transmission method, characterized by, The data transmission method, executed by the data sender which has a deterministic operating system deployed, includes: Receive handshake information requests sent by the data receiver and establish a mapping relationship between the handshake information and the original data information; Lightweight data for the deterministic operating system is generated based on the handshake information; The handshake information and the lightweight data are sent to the data receiver so that the data receiver can parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

2. The method according to claim 1, characterized in that, The handshake information includes: an event deterministic information identifier and event deterministic information; The lightweight data for generating the deterministic operating system based on the handshake information includes: Lightweight data is generated based on the event deterministic information identifier and the event content of the corresponding original information.

3. The method according to claim 1 or 2, characterized in that, Before sending the handshake information and lightweight data to the data recipient, the process also includes: Get the target event type set; Generate a handshake information set corresponding to each target event type in the target event type set, wherein the handshake information set includes at least two handshake information sets.

4. The method according to claim 3, characterized in that, Sending the handshake information to the data receiver includes: Obtain the communication performance parameters of the data sender; Based on the communication performance parameters of the data sender, the handshake information set corresponding to each target event type is split to obtain at least two sets of handshake information; For any set of handshake information, the set of handshake information is sent as a single message frame to the data receiver.

5. The method according to any one of claims 2-4, characterized in that, The event deterministic information identifiers include: event content identifier and event type identifier. The event type identifiers include: task type identifier and interruption type identifier.

6. A data transmission method, characterized in that, The data transmission method, performed by the data receiver, includes: A handshake information request is sent to the data sender so that the data sender can establish a mapping relationship between the handshake information and the original information of the data, wherein the data sender has a deterministic operating system deployed; Receive handshake information sent by the data sender and lightweight data of the deterministic operating system, wherein the lightweight data is generated by the data sender based on the handshake information; The lightweight data is parsed based on the mapping relationship established by the handshake information to obtain the original information of the data.

7. The method according to claim 6, characterized in that, The handshake information includes: an event deterministic information identifier and event deterministic information; the lightweight data includes: an event deterministic information identifier and the event content of the original information. The lightweight data is parsed based on the mapping relationship established by the handshake information to obtain the original information of the data, including: A mapping relationship between event deterministic information identifiers and event deterministic information is established based on the handshake information; Based on the event deterministic information identifier in the lightweight data, the mapping relationship is queried to obtain the event deterministic information in the original information; The original information of the data is determined based on the event content in the lightweight data and the event deterministic information in the original information.

8. The method according to claim 6 or 7, characterized in that, The handshake information consists of at least two sets; Before parsing the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data, the method further includes: For any set of handshake information, after receiving the handshake information, a mapping relationship between event deterministic information identifiers and event deterministic information is established based on the set of handshake information.

9. The method according to any one of claims 6-8, characterized in that, Send a handshake information request to the data sender, including: Upon receiving the trigger command, a handshake information request is sent to the data sender.

10. A data transmission device, characterized in that, Configured in the data sender, which has a deterministic operating system deployed thereon, the data transmission device includes: The handshake information request receiving module is used to receive handshake information requests sent by the data receiver and establish a mapping relationship between the handshake information and the original information of the data. A lightweight data determination module is used to generate lightweight data for the deterministic operating system based on the handshake information. The handshake information and lightweight data sending module is used to send the handshake information and the lightweight data to the data receiver, so that the data receiver can parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

11. A data transmission device, characterized in that, Configured in the data receiver, the data transmission device includes: The handshake information request sending module is used to send a handshake information request to the data sender so that the data sender can establish a mapping relationship between the handshake information and the original information of the data, wherein the data sender has a deterministic operating system deployed. A handshake information and lightweight data receiving module is used to receive handshake information sent by the data sender and lightweight data of the deterministic operating system, wherein the lightweight data is generated by the data sender based on the handshake information; The parsing module is used to parse the lightweight data based on the mapping relationship established by the handshake information to obtain the original information of the data.

12. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data transmission method according to any one of claims 1-9.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to execute the data transmission method according to any one of claims 1-9.

14. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the data transmission method according to any one of claims 1-9.

Images