A data transmission method and apparatus

Abstract

The application discloses a data transmission method and device, relates to the technical field of communication, and is used for solving the problem of how to realize real-time sending of data measurement (or diagnosis) results by a lower machine. The method comprises the following steps: firstly, a diagnosis device sends first transmission mode indication information used for instructing a measurement device to enter a first transmission mode, wherein the measurement device needs to send target measurement data corresponding to a target event to the diagnosis device once every time the target event is completed in the first transmission mode. Then, the diagnosis device receives the target measurement data sent from the measurement device.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data transmission method and apparatus. Background Technology

[0002] With the development of autonomous driving, the interaction between the host computer and the slave computer (e.g., the onboard computer (electronic control unit, ECU)) is no longer limited to debugging and maintenance. The host computer can also control vehicle behavior (e.g., in an emergency, an administrator can remotely drive the vehicle). To improve the accuracy of the host computer's vehicle control, developers need to use host computer tools to observe the data measurement (or diagnostic) results of the slave computer in real time, so as to continuously improve the predictive algorithm and enhance the accuracy of the host computer's vehicle control.

[0003] However, currently, the lower-level device can only send data measurement results to the upper-level device actively (e.g., sending data measurement (or diagnostic) results to the upper-level device after receiving a diagnostic request message) or periodically (e.g., sending data measurement results to the upper-level device every 20ms). The lower-level device's active or periodic sending methods do not allow developers to observe the lower-level device's data measurement (or diagnostic) results in real time, significantly impacting the accuracy of the prediction algorithm.

[0004] Therefore, how the lower-level machine can transmit data measurement (or diagnostic) results in real time is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] This application provides a data transmission method and apparatus to solve the problem of how a lower-level machine can transmit data measurement (or diagnostic) results in real time. To achieve the above objective, this application adopts the following technical solution:

[0006] In a first aspect, this application provides a data transmission method, comprising: first, a diagnostic device sending first transmission mode indication information to a measuring device to instruct the measuring device to enter a first transmission mode, wherein, in the first transmission mode, the measuring device needs to send target measurement data corresponding to the target event to the diagnostic device once after completing each target event. Then, the diagnostic device receives the target measurement data sent from the measuring device.

[0007] As can be seen, in this application, the diagnostic device (host computer) sends a first transmission mode indication message to the measuring device (slave computer), causing the measuring device to enter the first transmission mode. After entering this transmission mode, the measuring device sends target measurement data (e.g., measurement result or diagnostic result) corresponding to the target event to the diagnostic device every time a target event (e.g., measurement or diagnosis) is completed. This enables the slave computer (measuring device) to send data measurement (or diagnostic) results to the host computer in real time.

[0008] In one possible design, the aforementioned first transmission mode indication information is carried in the diagnostic request message.

[0009] In another possible design, the diagnostic request message also includes target event indication information, which indicates the target event. This allows for flexible adjustment of the target event by setting the target event indication information, enabling the lower-level machine to complete various events and return corresponding data.

[0010] In another possible design, the target event includes at least one event that meets preset conditions, and the diagnostic request message also includes the preset conditions. This allows the lower-level machine to return data only when the preset conditions are met, eliminating unimportant data, reducing data interaction, and improving the interaction efficiency between the lower-level and upper-level machines.

[0011] In another possible design, the diagnostic request message also includes data indication information, which indicates the target measurement data. This allows the lower-level machine to upload only the target measurement data corresponding to the target event after completing the target event, rather than all data related to the target event. This further eliminates unimportant data, reduces data interaction, and improves the interaction efficiency between the lower-level and upper-level machines.

[0012] In another possible design, the diagnostic request message includes a first field carrying service description information, which is used to indicate the test service provided by the measuring device. The first field includes a first subfield carrying service indication information and a second subfield carrying first transmission mode indication information. The service indication information is used to instruct the measuring device to enter a first reporting mode, wherein the measuring device periodically reports measurement data to the diagnostic device in the first reporting mode.

[0013] In another possible implementation, the diagnostic device can display the target measurement data on a screen. This allows technicians to observe the measurement (or diagnostic) results and improve the measurement (or diagnostic) algorithm, thereby enhancing the accuracy of the data measurement (or diagnosis).

[0014] Secondly, this application also provides a data transmission method, which includes: first, a measuring device receiving first transmission mode indication information sent by a diagnostic device; then, the measuring device entering the first transmission mode; and next, in the first transmission mode, the measuring device sending target measurement data corresponding to the target event to the diagnostic device once each target event is completed.

[0015] In one possible design, the aforementioned first transmission mode indication information is carried in the diagnostic request message.

[0016] In another possible design, the diagnostic request message also includes target event indication information, which indicates the target event. This allows for flexible adjustment of the target event by setting the target event indication information, enabling the lower-level machine to complete various events and return corresponding data.

[0017] In another possible design, the target event includes at least one event that meets preset conditions, and the diagnostic request message also includes the preset conditions. This allows the lower-level machine to return data only when the preset conditions are met, eliminating unimportant data, reducing data interaction, and improving the interaction efficiency between the lower-level and upper-level machines.

[0018] In another possible design, the diagnostic request message also includes data indication information, which indicates the target measurement data. This allows the lower-level machine to upload only the target measurement data corresponding to the target event after completing the target event, rather than all data related to the target event. This further eliminates unimportant data, reduces data interaction, and improves the interaction efficiency between the lower-level and upper-level machines.

[0019] In another possible design, the diagnostic request message includes a first field carrying service description information, which is used to indicate the test service provided by the measuring device. The first field includes a first subfield carrying service indication information and a second subfield carrying first transmission mode indication information. The service indication information is used to instruct the measuring device to enter a first reporting mode, wherein the measuring device periodically reports measurement data to the diagnostic device in the first reporting mode.

[0020] Thirdly, this application also provides a data transmission apparatus for performing the methods described in the foregoing aspects or any possible implementation thereof. Specifically, the data transmission apparatus may include units for performing the methods described in the foregoing aspects or any possible implementation thereof.

[0021] Optionally, the data transmission device can be the diagnostic device or measuring device described above.

[0022] Fourthly, this application also provides a data transmission apparatus, comprising: a memory, at least one processor, a transceiver, and instructions stored in the memory and executable on the processor. Furthermore, the memory, the processor, and the communication interface communicate with each other via an internal connection path. The at least one processor executes the instructions to cause the data transmission apparatus to implement the methods described in the foregoing aspects or any possible implementation thereof.

[0023] Optionally, the data transmission device can be the diagnostic device or measuring device described above.

[0024] Fifthly, this application also provides a computer-readable storage medium for storing a computer program that includes methods for implementing the foregoing aspects or any possible implementation thereof.

[0025] Sixthly, this application also provides a computer program product containing instructions that, when run on a computer, cause the computer to implement the methods described in the above aspects or any possible implementation thereof.

[0026] In a seventh aspect, this application also provides a chip device, including: an input interface, an output interface, and at least one processor. Optionally, the chip device further includes a memory. The at least one processor is used to execute code in the memory, and when the at least one processor executes the code, the chip device implements the methods described in the foregoing aspects or any possible implementation thereof.

[0027] Optionally, the data transmission device may be a chip device or integrated circuit in the aforementioned diagnostic or measuring device.

[0028] Eighthly, this application also provides a diagnostic system, including at least one of the diagnostic or measuring devices described in the fourth aspect above; or, including at least one of the chip devices or integrated circuits described in the diagnostic or measuring devices described in the seventh aspect above.

[0029] The data transmission method, data transmission device, computer storage medium, computer program product, chip, and diagnostic system provided in this embodiment are all used to execute the data transmission method provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the data transmission method provided above, and will not be repeated here. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1a This is a schematic diagram of a diagnostic request format provided in an embodiment of this application;

[0032] Figure 1b This is a schematic diagram illustrating another diagnostic request format provided in an embodiment of this application;

[0033] Figure 1c This is a schematic diagram of a diagnostic response format provided in an embodiment of this application;

[0034] Figure 1d This is a schematic diagram illustrating another diagnostic response format provided in an embodiment of this application;

[0035] Figure 1e This is a schematic diagram illustrating yet another diagnostic request format provided in an embodiment of this application;

[0036] Figure 1f This is a schematic diagram illustrating yet another diagnostic request format provided in an embodiment of this application;

[0037] Figure 2a A schematic diagram illustrating the interaction process between a host computer and a slave computer, provided as an embodiment of this application;

[0038] Figure 2b A schematic diagram illustrating another interaction process between a host computer and a slave computer, provided as an embodiment of this application;

[0039] Figure 3a A schematic diagram illustrating a data transmission scenario provided in an embodiment of this application;

[0040] Figure 3b A schematic diagram illustrating another data transmission scenario provided in an embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the structure of the diagnostic system provided in the embodiments of this application;

[0042] Figure 5 This is a schematic diagram of the structure of a standard architecture diagnostic instrument provided in an embodiment of this application;

[0043] Figure 6 A flowchart illustrating the data transmission method provided in an embodiment of this application;

[0044] Figure 7 A schematic diagram of the structure of a data transmission device provided in an embodiment of this application;

[0045] Figure 8 This is another schematic diagram of the data transmission device provided in the embodiments of this application;

[0046] Figure 9This is another schematic diagram of the data transmission apparatus provided in the embodiments of this application;

[0047] Figure 10 This is a schematic diagram of a chip structure provided in an embodiment of this application. Detailed Implementation

[0048] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0049] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0050] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0051] Furthermore, the terms “comprising” and “having”, and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus.

[0052] It should be noted that in the description of the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0053] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0054] First, some of the terms used in this application will be explained to facilitate understanding by those skilled in the art.

[0055] The Unified Diagnostic Service (UDS) protocol, or ISO 14229, is an application layer protocol and a standardized standard for diagnostic services. It standardizes the definition of all diagnostic commands, such as the message formats for diagnostic requests and responses. The UDS protocol can be implemented on top of various protocols. For example, ISO 14229-5 defines its implementation on the Internet Protocol (IP) (DoIP), and ISO 14229-3 defines its implementation on a Controller Area Network (CAN) bus. The following is a brief explanation of the diagnostic request and response formats defined by the UDS protocol.

[0056] UDS defines a unified format for diagnostic requests and responses for different diagnostic functions. Diagnostic request formats can be divided into two categories: one format includes a sub-function, and the other format does not, such as... Figure 1a and Figure 1b As shown. Please see below. Figure 1c The image shows the format of a diagnostic response for a diagnostic request that includes a sub-function. Please refer to [link to relevant documentation]. Figure 1d The image shows the diagnostic response format for diagnostic requests that do not contain sub-functions.

[0057] For example, for service identifier (SID) = 0x19, ReadDTCInformation is used to read diagnostic trouble code (DTC) information, and its format is as follows: Figure 1eAs shown. The sub-function, 0x06, `reportDTCExtDataRecordByDTCNumber`, is used to read a specific DTC and its associated "environmental data." In this case, the parameter is 4 bytes. The first three bytes identify the DTC to be read, and the fourth byte identifies the range of "environmental data" to be read. UDS specifies using FF to represent reading all "environmental data." Manufacturers can define other values ​​to represent the range of "environmental data" to be read according to their actual needs. Common "environmental data" includes DTC status, priority, occurrence count, aging counter, timestamp, mileage, etc.

[0058] It should be noted that the SID described in the embodiments of this application can also be referred to as Service ID.

[0059] For example, for SID = 0x2A, ReadDataByPeriodicIdentifier is used to periodically read the data identifier (DID) information, and its format is as follows: Figure 1f As shown. The values ​​and meanings of TransmissionMode are as follows: sendAtSlowRate: 0x01, commands the ECU to send a response to the Tester in low-rate mode. For example, every 1000ms. sendAtMediumRate: 0x02, commands the ECU to send a response to the Tester in medium-rate mode. For example, every 300ms. sendAtFastRate: 0x03, commands the ECU to send a response to the Tester in high-rate mode. For example, every 25ms. stopSending: 0x04, commands the ECU to stop sending responses. The values ​​and meanings of Parameter are as follows: Parameter is a set of DIDs, each DID being 1 byte long; DID is the Data ID that needs to be reported periodically (or stopped reporting).

[0060] For ease of description and brevity, this application embodiment only uses SID=0x2A as an example. SID=0x2A in this application embodiment is only an example. SID in this application embodiment can also be other values ​​(e.g., 0x19, 0x35, 0x22, etc.). When SID is other values, data transmission can also be performed by referring to the data transmission method provided in this application embodiment. This application embodiment does not limit this.

[0061] Currently, with the development of autonomous driving, the interaction between the host computer and the slave computer (e.g., ECU) is no longer limited to debugging and maintenance, but can also control vehicle behavior through the host computer (e.g., in an emergency, the administrator can remotely drive the vehicle).

[0062] Taking the interaction between the host computer and the slave computer as an example of "obstacle trajectory prediction," the accuracy of the real-time obstacle trajectory prediction results directly affects the control commands for the vehicle. Therefore, as developers, we need to use host computer tools to observe the calculation results (i.e., trajectory coordinates) in real time to continuously improve the prediction algorithm. Whether the calculation results are uniform over time and whether they are reported in real time directly affects the work's effectiveness. In the above scenario, the developer expects: on the slave computer, when the result res_12 is obtained at 12ms, res_12 should be immediately sent to the host computer for display; on the slave computer, when the result res_17 is obtained at 17ms, res_17 should be immediately sent to the host computer for display; on the slave computer, when the result res_20 is obtained at 20ms, res_20 should be immediately sent to the host computer for display.

[0063] Currently, the interaction process between the host computer and the slave computer in the UDS protocol can be divided into two categories: such as Figure 2a The question and answer shown and such Figure 2b The example shows multiple answers to a single question.

[0064] In a question-and-answer format, the host computer sends a request, and the slave computer responds. In the UDS protocol, specific SIDs include: 0x19 (ReadDTCInformation), 0x35 (RequestUpload), and 0x22 (ReadDataByIdentifier). This interaction method requires the aforementioned active query, which cannot meet the above expectations.

[0065] For a request-multiple-response mechanism, the host computer sends a request, and the slave computer responds. In the UDS protocol, the specific SID is, for example, 0x2A (ReadDataByPeriodicIdentifier service).

[0066] For 0x2A service: The lower-level device (ECU) can periodically report data to the upper-level device (or Tester). There are three modes for ECU data transmission:

[0067] Low rate mode sendAtSlowRate (e.g., period of 1 second).

[0068] Medium rate mode sendAtMediumRate (e.g., period 300ms).

[0069] High-rate mode sendAtFastRate (e.g., period 25ms).

[0070] The data transmission cycle is predefined by the supplier on the lower-level machine side. Simultaneously, the maximumNumberOfResponsesToSend number of response messages is set.

[0071] In a scenario where the reporting period is 20ms and the 0x2A service of the UDS protocol is used, the lower-level device sends res_12, res_17, and res_20 to the upper-level device for display at 20ms. In this method, the transmission of res_12 and res_17 both have delays of 8ms and 3ms respectively, and these delays are not fixed. Therefore, the periodic mode (0x2A service in the UDS protocol) cannot support real-time reporting of data from the lower-level device.

[0072] For example, refer to Figure 3a As shown, the periodic mode (0x2A service in the UDS protocol) measures only a single (group) of data. If multiple (groups) of data are generated within a period, they need to be accumulated together and reported at a specific point in time.

[0073] For example, refer to Figure 3b As shown, multiple (groups) of data are measured using the periodic mode (0x2A service in the UDS protocol). Assume that when the operator detects an anomaly in the data star, a command needs to be issued to retrieve the data point. In actual operation, if the data star and data point occur in the same period, because the data star is reported in the first period, the operator can only issue a command to retrieve the data point after the report is submitted, while the data point can only be viewed in the next period.

[0074] In summary, in the UDS protocol, the lower-level machine periodically reports data to the upper-level machine using an upper-level machine (question) and lower-level machine (response) approach. This approach cannot support the lower-level machine to report the measurement results in real time, and the measurement results cannot be uniform over time.

[0075] While maintaining compatibility with existing implementations of the UDS protocol, this application proposes a data transmission method to address the aforementioned problems. This data transmission method is applicable to diagnostic systems. Figure 4 This illustrates one form in which the diagnostic system exists. For example... Figure 4 As shown, the diagnostic system may include a host computer 100 and a slave computer 200. The host computer 100 and the slave computer 200 can communicate with each other. For example, the slave computer 200 can send measurement data to the host computer 100, and the host computer can perform diagnostics based on the measurement data sent by the slave computer.

[0076] It is worth mentioning that the above-mentioned diagnostic system can also be called a testing system.

[0077] Optionally, the host computer 100 and the slave computer 200 can communicate via wired or wireless means, and this embodiment of the application does not limit this.

[0078] In one possible implementation, the host computer 100 and the slave computer 200 can communicate via a wired connection.

[0079] For example, the above-mentioned wired method can achieve communication through a data cable connection or through an internal bus connection.

[0080] In another possible implementation, the host computer 100 and the slave computer 200 can communicate wirelessly.

[0081] For example, the wireless method described above can be to achieve communication through a communication network.

[0082] Optionally, the aforementioned communication network may be Ethernet, radio access network (RAN), wireless local area network (WLAN), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., and this application embodiment does not limit it.

[0083] Optionally, the host computer 100 described above can take many forms, and this application embodiment does not limit this.

[0084] In one possible implementation, the host computer 100 can be a standalone device.

[0085] In another possible implementation, the host computer 100 can be integrated into other devices as a functional module or chip device.

[0086] It should be noted that the host computer 100 in this embodiment is a diagnostic instrument only as an example. The host computer 100 in this embodiment can also be other devices, and this embodiment does not limit it.

[0087] The aforementioned diagnostic instrument, also known as an automotive diagnostic instrument, is a professional instrument specifically designed for vehicle inspection. It detects vehicle performance and faults, making it an essential tool for vehicle testing. Diagnostic instruments can perform vehicle diagnostics through developed diagnostic software, presenting various diagnostic results in a graphical interface. Therefore, any device with diagnostic software installed can be understood as a diagnostic instrument. Examples of diagnostic instruments include personal computers (PCs), tablets, or dedicated devices with diagnostic software installed. Figure 5 It is a standard architecture diagnostic instrument developed by the Association for Standardization of Automation and Measuring Systems (ASAM). For example... Figure 5 As shown, the diagnostic tool includes an application layer, a diagnostic server API (D-Server API), a D-Server, a diagnostic protocol data unit API (D-PDU API), a vehicle communication interface (VCI), and an open diagnostic data exchange (ODX) interface. The application layer implements upper-level diagnostic functions, such as fault reading in the diagnostic tool, key matching in offline equipment, or test cases in testing equipment. The D-Server API is the interface between the application layer and the D-Server, defined by ISO standards. The D-PDU API is the interface between the MVCI-RTE and the VCI, also defined by ISO standards. The VCI is the hardware interface between the on-board diagnostic system (e.g., ECU) and external vehicle devices, enabling data transmission between different signal carriers. The display typically includes a user interface for displaying diagnostic results. The diagnostic file is an ODX file. ODX is a standardized diagnostic file format. With it, when diagnosing different vehicles or different ECUs, you only need to load the ODX file adapted to that vehicle model or ECU, without needing to make any changes to the diagnostic tool. Another important function of ODX is that it unifies the format of diagnostic files, so no format conversion is required when diagnostic files are transferred and exchanged between departments such as R&D, testing, production, and after-sales.

[0088] Optionally, the aforementioned lower-level machine 200 can take many forms, and this application embodiment does not limit this.

[0089] In one possible implementation, the lower-level machine 200 can be a standalone device.

[0090] In another possible implementation, the lower-level machine 200 can be integrated into other devices as a functional module or chip device.

[0091] It should be noted that the lower-level machine 200 in this embodiment is an ECU only as an example. The lower-level machine 200 in this embodiment can also be other devices, and this embodiment does not limit it.

[0092] In one possible implementation, the host computer 100 is a diagnostic tool, and the slave computer 200 is an ECU. The diagnostic tool issues a request, and the ECU provides a response. In this communication process, the diagnostic tool (client, host computer) and the ECU (server, slave computer) play the roles of client and server in computer network communication, respectively.

[0093] It should be noted that the diagnostic system (testing system) provided in this application is applicable to scenarios including but not limited to the diagnosis, debugging and testing of ECUs in systems such as automotive diagnostic systems, distributed energy systems, and industrial control systems.

[0094] Figure 6 This illustration shows a schematic flowchart of a data transmission method provided in an embodiment of this application. This method can be applied to, for example... Figure 4 The diagnostic system shown. (As shown) Figure 6 As shown, the method includes:

[0095] S601, The diagnostic device sends a first transmission mode indication message to the measuring device.

[0096] Accordingly, the measuring device receives the first transmission mode indication information sent by the diagnostic device.

[0097] The first transmission mode indication information is used to instruct the measuring device to enter the first transmission mode. In the first transmission mode, the measuring device needs to send the target measurement data corresponding to each target event to the diagnostic device after completing one target event.

[0098] It should be noted that prior to S601, there was a communication link between the diagnostic device and the measuring device.

[0099] In one possible implementation, the diagnostic device can correspond to Figure 4 The host computer 100 in the middle. This measuring device corresponds to... Figure 4 The lower-level machine 200.

[0100] In one possible implementation, the diagnostic request message includes the first transmission mode indication information.

[0101] For example, the first transmission mode indication information can be carried in, such as Figure 1f The TransmissionMode in the diagnostic request message shown can be used as an example. For instance, a TransmissionMode value of 0x05 can be used to characterize the first transmission mode indication information. Of course, other values ​​of TransmissionMode can also be used to characterize the first transmission mode indication information, such as 0x06, 0x07, etc. Alternatively, other fields can be used to characterize the first transmission mode indication information; this embodiment of the application does not limit this approach.

[0102] In one possible implementation, the diagnostic request message also includes target event indication information, which is used to indicate the target event.

[0103] For example, target event indication information can be represented by an event ID. Target event indication information can be carried in, for example... Figure 1f The diagnostic request message parameters shown include different event ID values, each representing a different event. For example, an event ID of 3 indicates measuring vehicle speed, while an event ID of 5 indicates measuring engine speed.

[0104] Optionally, the target event may include at least one event that satisfies a preset condition, and the diagnostic request message may also include the preset condition.

[0105] For example, preset conditions can be carried out in, such as Figure 1fThe parameters of the diagnostic request message shown are as follows. An event can correspond to one preset condition or multiple preset conditions. This application embodiment does not limit this. For example, the event is uploading vehicle speed. The preset conditions may include preset condition 1 (vehicle speed greater than 100 km / h) and preset condition 2 (vehicle speed less than 30 km / h). Then the corresponding target events include uploading vehicle speed when the vehicle speed is greater than 100 km / h and uploading vehicle speed when the vehicle speed is less than 30 km / h. It is worth mentioning that the above is an example of using any one of the multiple preset conditions of an event as the target event. In practical applications, all or some of the preset conditions that are satisfied can also be used as the target event, and this application embodiment does not limit this. For example, event A includes preset condition 1, preset condition 2, preset condition 3, and preset condition 4. You can use the simultaneous fulfillment of preset conditions 1, 2, 3 and 4 as the target event, or you can use the simultaneous fulfillment of preset conditions 1, 2, 3 or 4 as the target event.

[0106] Of course, the number of preset conditions corresponding to an event can also be zero (i.e., there are no corresponding preset conditions). In this case, once the requested target event occurs on the lower-level machine side, it will be reported immediately (reporting the target measurement data corresponding to the target event).

[0107] In one possible implementation, the diagnostic request message also includes data indication information that indicates the target measurement data.

[0108] For example, data indication information can be carried in, such as Figure 1f The diagnostic request message parameters show that data indication information can be represented by a DID. Different DIDs can represent different data. For example, a DID value of 3 represents the vehicle's speed. A DID value of 5 represents the vehicle's engine speed.

[0109] It is worth mentioning that the target measurement data can be all the data in the data corresponding to the target event (for example, the target event is to measure the operating parameters of the car (such as vehicle speed, engine speed, remaining battery power, mileage, etc.), and the target measurement data is the operating parameters of the car), or it can be a part of the data in the data corresponding to the target event (for example, the target event is to measure the operating parameters of the car, and the target measurement data is the remaining battery power of the car). This application does not limit it in this way.

[0110] In one possible implementation, the diagnostic request message also includes constraints on the first transmission mode, and the measuring device exits the first transmission mode and stops reporting measurement data to the diagnostic device after the constraints are met.

[0111] For example, the constraint can be a duration constraint. The duration of the constraint can be 30 minutes, 60 minutes, 90 minutes, etc., and this embodiment does not limit it.

[0112] For example, the constraint can be a limit on the number of response messages. The number of response messages can be 20, 50, 100, etc., and this embodiment does not limit this.

[0113] For example, the constraints can be default constraints. That is, after receiving a diagnostic request message carrying default constraints from the diagnostic device, the measuring device will exit the first transmission mode and stop reporting measurement data to the diagnostic device once the pre-configured default constraints are met. The default constraints can be a limit on the number of response messages, a duration constraint, or other constraints. The default constraints can be pre-configured in the `maximumNumberOfResponsesToSend` parameter of the measuring device.

[0114] In one possible implementation, the diagnostic request message includes a first field carrying service description information, which is used to indicate the test service provided by the measuring device. The first field includes a first subfield carrying service indication information and a second subfield carrying first transmission mode indication information. The service indication information is used to instruct the measuring device to enter a first reporting mode, wherein the measuring device periodically reports measurement data to the diagnostic device in the first reporting mode.

[0115] In one possible implementation, the first field is as follows: Figure 1f As shown, the first field includes a first subfield (SID field) carrying service indication information and a second subfield (TransmissionMode field) carrying first transmission mode indication information. When the value of the first subfield (SID field) is 0x2A and the value of the second subfield (TransmissionMode field) is 0x05, it is used to instruct the lower-level computer (ECU) to send the target measurement data corresponding to the target event to the upper-level computer after each target event is completed. That is, after receiving a request message with the value of the first subfield (SID) being 0x2A and the value of the second subfield (TransmissionMode) being 0x05, the measuring device enters the first transmission mode.

[0116] In the prior art, the SID field in the diagnostic request message takes the value 0x2A, and the TransmissionMode field in the diagnostic request message represents different transmission modes when it takes different values.

[0117] Specifically, when the TransmissionMode field is set to 0x01, it instructs the lower-level device (ECU) to send a response to the upper-level device (Tester) in low-rate mode (sendAtSlowRate). For example, it sends a response every 1000ms.

[0118] The TransmissionMode field, with a value of 0x02, instructs the lower-level device (ECU) to send a response to the upper-level device (Tester) in medium-rate mode (sendAtMediumRate). For example, it sends a response every 300ms.

[0119] The TransmissionMode field, with a value of 0x03, instructs the lower-level ECU to send a response to the upper-level ECU (Tester) in high-rate mode (sendAtFastRate). For example, it sends a response every 25ms.

[0120] The TransmissionMode field has a value of 0x04, which is used to command the lower-level computer (ECU) to stop sending responses (stopSending).

[0121] In one possible implementation, the first field may also include a third subfield, which is used to carry target event indication information, preset conditions, data indication information, and constraints.

[0122] For example, such as Figure 1f As shown, the third subfield can be Figure 1f The parameter field in the file.

[0123] In one possible implementation, after receiving a diagnostic request message from the diagnostic device, the measuring device needs to perform a validity check on the message (e.g., parameter validity check and transmission mode validity check).

[0124] For example, when the measuring device receives a diagnostic request message from the diagnostic device and the SID in the diagnostic request message is 0x2A, it performs parameter validity judgment and transmission mode validity judgment. If the parameter validity judgment and transmission mode validity judgment are passed, it enters the corresponding transmission mode according to the value of the TransmissionMode field.

[0125] For example, when the measuring device receives a diagnostic request message from the diagnostic device and the diagnostic request message contains SID=0x2A, it performs parameter validity checks and transmission mode validity checks. If the parameter validity checks or transmission mode validity checks fail, it sends a failure response to the diagnostic device.

[0126] S602. The measuring device enters the first transmission mode based on the first transmission mode indication information.

[0127] The first transmission mode can also be called the event mode (SendAtEvent).

[0128] S603. In the first transmission mode, the measuring device sends the target measurement data corresponding to the target event to the diagnostic device once after completing each target event.

[0129] Accordingly, the diagnostic device receives target measurement data sent from the measuring device.

[0130] In one possible implementation, after receiving the target measurement data sent from the measuring device, the diagnostic device can also perform user interface (UI) processing on the target measurement data and display it on the interface of the diagnostic device.

[0131] For example, the diagnostic device is a host computer, the measuring device is an ECU, and the application scenario is a scenario that requires real-time measurement of data and / or status on the ECU. When the ECU enters the first transmission mode, that is, after the developer or system user can obtain various data and / or status in the ECU in real time, they can further analyze the data (debugging and testing work) or issue control operations to the vehicle (such as remote driving).

[0132] For example, for Figure 3a In the scenario shown, the target event can be set as reporting the data generated by the measurement. This way, every time the measuring device generates new data, it sends it to the diagnostic device, allowing the measuring device to report the measurement results in real time. Correspondingly, the user can view the data reported by the measuring device in real time through the diagnostic device.

[0133] For example, for Figure 3bIn the scenario shown, the target event can be set to report the data stars and data points generated by the measurement. This way, whenever the measuring device generates a new data star or data point, it will send it to the diagnostic device. Assuming that when the operator detects an anomaly in the data star, there's no need to issue a command to retrieve the data point; instead, the measuring device will automatically and in real-time upload the data point, allowing the operator to view and address it promptly, thereby improving the user experience.

[0134] For example, in an obstacle trajectory prediction scenario, the target event can be set to upload the calculation result. This way, the measuring device will immediately report and upload the calculation result to the diagnostic device after each calculation. For instance, when the measuring device obtains the calculation result res_12 in the 12ms, it will immediately send the calculation result res_12 to the diagnostic device. Correspondingly, the diagnostic device will immediately receive the calculation result res_12 sent by the measuring device. This allows developers to observe the calculation results (i.e., trajectory coordinates) in real time, enabling continuous improvement of the prediction algorithm, thereby increasing its accuracy and enhancing the user experience.

[0135] In one possible implementation, the diagnostic request message carries a duration constraint, so the measuring device will automatically exit the first transmission mode after a certain period of time. For example, the measuring device may exit the first transmission mode after 60 minutes and stop sending the target measurement data corresponding to the target event to the diagnostic device. Alternatively, the measuring device may exit the first transmission mode upon receiving a stop command (a diagnostic request message carrying the stop command). For example, the measuring device may exit the first transmission mode upon receiving a diagnostic request message with SID = 0x2A and TransmissionMode value of 0x04.

[0136] In another possible implementation, the diagnostic request message carries a constraint on the number of response messages. Therefore, after entering the first transmission mode, the measuring device sends a certain number of response messages and then exits the first transmission mode. For example, the measuring device might exit the first transmission mode and stop sending response messages to the diagnostic device after sending 50 response messages.

[0137] In another possible implementation, the diagnostic request message carries default constraints. After the measuring device enters the first transmission mode and meets the pre-configured default conditions, it will exit the first transmission mode and stop reporting measurement data to the diagnostic device.

[0138] In one possible implementation, the response message (i.e., the message carrying the target measurement data corresponding to the target event) may include key data elements: timestamp (fixed length), PDID (fixed length), and Content (variable length, defined as needed). The timestamp represents the actual time the event (target event) occurred. Content is a detailed description of the target event. For example, data such as acceleration at a speed greater than 100 km / h or remaining battery power. PDID is the event ID mentioned above, which will not be elaborated further here.

[0139] As can be seen from S601-S603 above, in this embodiment, the diagnostic device (host computer) sends a first transmission mode indication information to the measuring device (slave computer), causing the measuring device to enter the first transmission mode. After entering this transmission mode, the measuring device sends target measurement data (e.g., measurement result or diagnostic result) corresponding to the target event to the diagnostic device every time a target event (e.g., measurement or diagnosis) is completed. This enables the slave computer (measuring device) to send data measurement (or diagnostic) results in real time, solving the problem of how the slave computer can achieve real-time sending of data measurement (or diagnostic) results.

[0140] The above combination Figure 6 The data transmission method provided in the embodiments of this application has been introduced. The following will be combined with… Figures 7 to 9 A data transmission apparatus for performing the above method is introduced.

[0141] It should be noted that the data transmission device can be the diagnostic device in the above method embodiments, capable of executing the methods performed by the diagnostic device in the above method; or, the data transmission device can be the measuring device in the above method embodiments, capable of executing the methods performed by the measuring device in the above method.

[0142] It is understood that, in order to achieve the above-mentioned functions, the data transmission device includes hardware and / or software modules that perform the respective functions. Based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0143] This embodiment can divide the data transmission device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0144] When dividing each function into modules according to its corresponding function. Figure 7 A schematic diagram of a possible composition of the data transmission device involved in the above embodiments is shown, such as... Figure 7 As shown, the device 700 may include a transceiver unit 701 and a processing unit 702.

[0145] The processing unit 702 can control the transceiver unit 701 to implement the methods performed by the diagnostic device or measuring device in the above method embodiments, and / or other processes used in the technology described herein.

[0146] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0147] When using integrated units, device 700 may include a processing unit, a storage unit, and a communication unit. The processing unit can be used to control and manage the operation of device 700, for example, to support device 700 in executing the steps performed by the aforementioned units. The storage unit can be used to support device 700 in executing stored program code and data. The communication unit can be used to support communication between device 700 and other devices.

[0148] The processing unit can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination of functions that implement computing capabilities, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc. The storage unit can be a memory. The communication unit can specifically be a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip, or other devices that interact with other electronic devices.

[0149] In one possible implementation, the data transmission device involved in this embodiment can be a device with... Figure 8 The device 800 shown is a schematic diagram of a diagnostic or measuring device. The device 800 includes a processor 801 and a transceiver 802, which communicate with each other through an internal connection path. Figure 7 The related functions implemented by the processing unit 702 can be implemented by the processor 801, and the related functions implemented by the transceiver unit 701 can be implemented by the processor 801 controlling the transceiver 802.

[0150] Optionally, the device 800 may also include a memory 803, and the processor 801, the transceiver 802 and the memory 803 communicate with each other through an internal connection path. Figure 7 The related functions implemented by the storage unit in the memory can be implemented by the memory 803.

[0151] In one possible implementation, Figure 9 Another schematic block diagram of a data transmission apparatus provided in an embodiment of this application is shown. This data transmission apparatus can be a diagnostic device as described in the above method embodiments, capable of executing the methods implemented by the diagnostic device in the above method; or, the data transmission apparatus can be a measuring device as described in the above method embodiments, capable of executing the methods implemented by the measuring device in the above method.

[0152] like Figure 9 As shown, the data transmission device 900 may include at least one of the following: a processor 910, an external memory interface 920, an internal memory 921, a universal serial bus (USB) interface 930, a charging management module 940, a power management module 941, a battery 942, an antenna 1, an antenna 2, a mobile communication module 950, a wireless communication module 960, an audio module 970, a speaker 970A, a receiver 970B, a microphone 970C, a headphone jack 970D, a sensor module 980, a button 990, a motor 991, an indicator 992, a camera 993, a display screen 994, and a subscriber identification module (SIM) card interface 995.

[0153] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the data transmission device 900. In other embodiments of this application, the data transmission device 900 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0154] Processor 910 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), baseband processors, and / or neural network processing units (NPUs). Different processing units may be independent components or integrated into one or more processors. In some embodiments, data transmission device 900 may also include one or more processors 910. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution. In other embodiments, processor 910 may also include a memory for storing instructions and data. For example, the memory in processor 910 may be a cache memory. This memory can store instructions or data that the processor 910 has recently used or is recurring. If the processor 910 needs to use the instruction or data again, it can directly retrieve it from the aforementioned memory. This avoids repeated accesses, reduces the waiting time of the processor 910, and thus improves the efficiency of the data transmission device 900 in processing data or executing instructions.

[0155] In some embodiments, the processor 910 may include one or more interfaces. These interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM card interface, and / or a USB interface, etc. The USB interface 930 is a USB standard-compliant interface, specifically a Mini USB interface, a Micro USB interface, a USB Type-C interface, etc. The USB interface 930 can be used to connect a charger to charge the data transmission device 900, and can also be used for data transmission between the data transmission device 900 and peripheral devices. The USB interface 930 can also be used to connect headphones for audio playback.

[0156] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the data transmission device 900. In other embodiments of this application, the data transmission device 900 may also employ different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0157] The charging management module 940 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 940 receives charging input from the wired charger via a USB interface 930. In some wireless charging embodiments, the charging management module 940 receives wireless charging input via the wireless charging coil of the data transmission device 900. While charging the battery 942, the charging management module 940 can also supply power to the data transmission device 900 via the power management module 941.

[0158] The power management module 941 connects the battery 942, the charging management module 940, and the processor 910. The power management module 941 receives input from the battery 942 and / or the charging management module 940, providing power to the processor 910, internal memory 921, external memory, display 994, camera 993, and wireless communication module 960. The power management module 941 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 941 may also be located within the processor 910. In other embodiments, the power management module 941 and the charging management module 940 may be housed in the same device.

[0159] The wireless communication function of the data transmission device 900 can be implemented through antenna 1, antenna 2, mobile communication module 950, wireless communication module 960, modem processor, and baseband processor.

[0160] Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the data transmission device 900 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0161] The mobile communication module 950 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the data transmission device 900. The mobile communication module 950 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 950 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 950 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 950 may be housed in the processor 910. In some embodiments, at least some functional modules of the mobile communication module 950 and at least some modules of the processor 910 may be housed in the same device.

[0162] The wireless communication module 960 can provide wireless communication solutions for use on the data transmission device 900, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, or other possible general transmission technologies.

[0163] Optionally, the wireless communication module 960 may be one or more devices that integrate at least one communication processing module, wherein one communication processing module may correspond to one network interface, the network interface may be set in different service function modes, and the network interface set in different modes may establish a network connection corresponding to that mode.

[0164] The wireless communication module 960 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 910. The wireless communication module 960 can also receive signals to be transmitted from processor 910, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0165] The data transmission device 900 implements display functions through a GPU, a display screen 994, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 994 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. The processor 910 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0166] Display screen 994 is used to display images, videos, etc. Display screen 994 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, data transmission device 900 may include one or more display screens 994.

[0167] In some embodiments of this application, when the display panel uses materials such as OLED, AMOLED, and FLED, the above-mentioned Figure 9 The display screen 994 in the document can be bent. Here, "the display screen 994 can be bent" means that the display screen can be bent to any angle at any location and held at that angle. For example, the display screen 994 can be folded in half horizontally from the middle, or vertically from the middle. In this application, the bendable display screen is referred to as a foldable display screen. The touch display screen can be a single screen or a display screen composed of multiple screens pieced together; no limitation is made here.

[0168] The display screen 994 of the data transmission device 900 can be a flexible screen. Currently, flexible screens are attracting much attention due to their unique characteristics and enormous potential. Compared to traditional screens, flexible screens are highly flexible and bendable, providing users with new interaction methods based on their bendability, thus meeting more user needs for the data transmission device 900. For data transmission devices equipped with foldable displays, the foldable display can switch between a small screen in a folded state and a large screen in an unfolded state at any time. Therefore, users are increasingly using the split-screen function on data transmission devices equipped with foldable displays.

[0169] The data transmission device 900 can perform shooting functions through an ISP, camera 993, video codec, GPU, display screen 994, and application processor.

[0170] The ISP (Image Signal Processor) is used to process data fed back from the camera 993. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's image sensor. The light signal is converted into an electrical signal, and the image sensor transmits this electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimizations on image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be integrated into the camera 993.

[0171] Camera 993 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then transmitted to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the data transmission device 900 may include one or more cameras 993.

[0172] A digital signal processor (DSP) is used to process digital signals. Besides digital image signals, it can also process other digital signals. For example, when the data transmission device 900 selects a frequency, the DSP performs Fourier transforms on the frequency energy.

[0173] Video codecs are used to compress or decompress digital video. Data transmission device 900 can support one or more video codecs. Thus, data transmission device 900 can play or record video in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0174] An NPU (Neural Processing Unit) is a neural network (NN) computing processor that borrows from the structure of biological neural networks, such as the communication functions between neurons in the human brain, to rapidly process input information and continuously learn. NPUs can enable intelligent cognitive applications in data transmission devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0175] The external memory interface 920 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the data transfer device 900. The external memory card communicates with the processor 910 through the external memory interface 920 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0176] The internal memory 921 can be used to store one or more computer programs, which include instructions. The processor 910 can execute the instructions stored in the internal memory 921, thereby causing the data transmission device 900 to perform the screen-off display method provided in some embodiments of this application, as well as various applications and data processing. The internal memory 921 may include a program storage area and a data storage area. The program storage area may store the operating system; it may also store one or more applications (such as a gallery, contacts, etc.). The data storage area may store data created during the use of the data transmission device 900 (such as photos, contacts, etc.). Furthermore, the internal memory 921 may include high-speed random access memory and non-volatile memory, such as one or more disk storage components, flash memory components, universal flash storage (UFS), etc. In some embodiments, the processor 910 can execute instructions stored in the internal memory 921 and / or instructions stored in memory disposed in the processor 910, causing the data transmission device 900 to perform the screen-off display method provided in the embodiments of this application, as well as other applications and data processing. The data transmission device 900 can implement audio functions, such as music playback and recording, through an audio module 970, a speaker 970A, a receiver 970B, a microphone 970C, a headphone jack 970D, and an application processor.

[0177] The sensor module 980 may include a pressure sensor 980A, a gyroscope sensor 980B, a barometric pressure sensor 980C, a magnetic sensor 980D, an accelerometer sensor 980E, a distance sensor 980F, a proximity sensor 980G, a fingerprint sensor 980H, a temperature sensor 980J, a touch sensor 980K, an ambient light sensor 980L, a bone conduction sensor 980M, etc.

[0178] This application also provides a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the data transmission method in the above embodiments.

[0179] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the data transmission method described in the above embodiments.

[0180] This application also provides an apparatus, which may specifically be a chip, integrated circuit, component, or module. Specifically, the apparatus may include a connected processor and a memory for storing instructions, or the apparatus may include at least one processor for fetching instructions from external memory. When the apparatus is running, the processor can execute instructions to cause the chip to perform the data transmission methods in the above-described method embodiments.

[0181] Figure 10 A schematic diagram of a chip 1000 is shown. The chip 1000 includes one or more processors 1001 and interface circuits 1002. Optionally, the chip 1000 may also include a bus 1003.

[0182] The processor 1001 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method can be completed by the integrated logic circuitry in the processor 1001 or by software instructions.

[0183] Optionally, the processor 1001 described above may be a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. It can implement or execute the methods and steps disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0184] The interface circuit 1002 can be used to send or receive data, instructions or information. The processor 1001 can use the data, instructions or other information received by the interface circuit 1002 to process the data, instructions or other information, and can send the processed information out through the interface circuit 1002.

[0185] Optionally, the chip may also include memory, which may include read-only memory and random access memory, providing operation instructions and data to the processor. A portion of the memory may also include non-volatile random access memory (NVRAM).

[0186] Optionally, the memory stores executable software modules or data structures, and the processor can execute corresponding operations by calling the operation instructions stored in the memory (which may be stored in the operating system).

[0187] Optionally, the chip can be used in the diagnostic or measuring apparatus described in the embodiments of this application. Optionally, the interface circuit 1002 can be used to output the execution result of the processor 1001. For the data transmission methods provided in one or more embodiments of this application, please refer to the foregoing embodiments, which will not be repeated here.

[0188] It should be noted that the functions of the processor 1001 and the interface circuit 1002 can be implemented through hardware design, software design, or a combination of hardware and software; no restrictions are imposed here.

[0189] This application also provides a diagnostic service on a lower-level machine (e.g., an ECU), which provides an event-based data transmission interface in the 0x2A service for application software to use. Users can use the event-based data transmission interface in the 0x2A service to send data to the upper-level machine (Tester) through the application software.

[0190] It should be noted that this idea relies on the event mechanism provided by the ECU software platform. Autonomous driving platforms typically possess an event mechanism.

[0191] It should be noted that the data transmission method proposed in this application uses the same MVCI architecture as the existing standard MVCI architecture. However, in the specific processing, support for the event mode (first transmission mode) SendAtEven in the 0x2A service (periodic reporting service) is added. This is manifested in that during ODX parsing, the event mode and the response results to the event mode are supported and parsed according to the format defined by the developer.

[0192] In this embodiment, the data transmission device, computer storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0193] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0194] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0195] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0196] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0197] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0198] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0199] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0200] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data transmission method, characterized in that, include: A first transmission mode indication message is sent to the measuring device. This message instructs the measuring device to enter a first transmission mode. In this first transmission mode, the measuring device sends target measurement data corresponding to each target event to the diagnostic device after each target event is completed. The first transmission mode indication message is carried within a diagnostic request message. This message includes a first field carrying service description information, which indicates the test service provided by the measuring device. The first field includes a first subfield carrying service indication information and a second subfield carrying the first transmission mode indication message. This service indication information instructs the measuring device to enter a first reporting mode, in which the measuring device periodically reports measurement data to the diagnostic device. Receive the target measurement data sent from the measuring device.

2. The data transmission method according to claim 1, characterized in that, The diagnostic request message also includes target event indication information, which is used to indicate the target event.

3. The data transmission method according to claim 1 or 2, characterized in that, The target event includes at least one event that meets preset conditions, and the diagnostic request message also includes the preset conditions.

4. The data transmission method according to claim 1 or 2, characterized in that, The diagnostic request message also includes data indication information, which is used to indicate the target measurement data.

5. A data transmission method, characterized in that, include: The device receives a first transmission mode indication message from a diagnostic device. This first transmission mode indication message instructs the measuring device to enter a first transmission mode. In this first transmission mode, the measuring device needs to send target measurement data corresponding to each target event to the diagnostic device after completing it. The first transmission mode indication message is carried in a diagnostic request message. The diagnostic request message includes a first field carrying service description information, which indicates the test service provided by the measuring device. This first field includes a first subfield carrying service indication information and a second subfield carrying the first transmission mode indication message. The service indication information instructs the measuring device to enter a first reporting mode, in which the measuring device periodically reports measurement data to the diagnostic device. Based on the first transmission mode indication information, enter the first transmission mode; In the first transmission mode, once the target event is completed, the target measurement data is sent to the diagnostic device.

6. The data transmission method according to claim 5, characterized in that, The diagnostic request message also includes target event indication information, which is used to indicate the target event.

7. The data transmission method according to claim 5 or 6, characterized in that, The target event includes at least one event that meets preset conditions, and the diagnostic request message also includes the preset conditions.

8. The data transmission method according to claim 5 or 6, characterized in that, The diagnostic request message also includes data indication information, which is used to indicate the target measurement data.

9. A data transmission device, characterized in that, It includes a processor and a transceiver, wherein the processor and the transceiver are coupled; The processor controls the transceiver to send a first transmission mode indication information to the measuring device. This first transmission mode indication information instructs the measuring device to enter a first transmission mode. In this first transmission mode, the measuring device needs to send target measurement data corresponding to each target event to the diagnostic device after completing it. The first transmission mode indication information is carried in a diagnostic request message. This diagnostic request message includes a first field carrying service description information, which indicates the test service provided by the measuring device. The first field includes a first subfield carrying service indication information and a second subfield carrying the first transmission mode indication information. This service indication information instructs the measuring device to enter a first reporting mode, in which the measuring device periodically reports measurement data to the diagnostic device. The processor is also configured to control the transceiver to receive the target measurement data sent from the measuring device.

10. The data transmission apparatus according to claim 9, characterized in that, The diagnostic request message also includes target event indication information, which is used to indicate the target event.

11. The data transmission apparatus according to claim 9 or 10, characterized in that, The target event includes at least one event that meets preset conditions, and the diagnostic request message also includes the preset conditions.

12. The data transmission apparatus according to claim 9 or 10, characterized in that, The diagnostic request message also includes data indication information, which is used to indicate the target measurement data.

13. A data transmission device, characterized in that, It includes a processor and a transceiver, wherein the processor and the transceiver are coupled; The processor controls the transceiver to receive first transmission mode indication information sent by the diagnostic device. The first transmission mode indication information instructs the measuring device to enter a first transmission mode. In this first transmission mode, the measuring device needs to send target measurement data corresponding to the target event to the diagnostic device once after completing each target event. The first transmission mode indication information is carried in a diagnostic request message. The diagnostic request message includes a first field carrying service description information, which indicates the test service provided by the measuring device. The first field includes a first subfield carrying service indication information and a second subfield carrying the first transmission mode indication information. The service indication information instructs the measuring device to enter a first reporting mode. In this first reporting mode, the measuring device periodically reports measurement data to the diagnostic device. Based on the first transmission mode indication information, the device enters the first transmission mode. In this first transmission mode, it sends the target measurement data to the diagnostic device once after completing each target event.

14. The data transmission apparatus according to claim 13, characterized in that, The diagnostic request message also includes target event indication information, which is used to indicate the target event.

15. The data transmission apparatus according to claim 13 or 14, characterized in that, The target event includes at least one event that meets preset conditions, and the diagnostic request message also includes the preset conditions.

16. The data transmission apparatus according to claim 13 or 14, characterized in that, The diagnostic request message also includes data indication information, which is used to indicate the target measurement data.

17. A chip device comprising at least one processor and an interface circuit, the interface circuit being configured to provide the at least one processor with the transmission or reception of data, instructions, or information, characterized in that, When the at least one processor executes program code or instructions, it implements the method of any one of claims 1 to 4 or any one of claims 5 to 8.

18. A computer-readable storage medium for storing a computer program, characterized in that, The computer program includes instructions for implementing the method of any one of claims 1 to 4 or any one of claims 5 to 8.

19. A computer program product, the computer program product comprising instructions, characterized in that, When the instructions are executed on a computer or processor, the computer or processor performs the method of any one of claims 1 to 4 or any one of claims 5 to 8.

Images