Data recharging method, detection rack, equipment and computer readable storage medium
By using communication protocols in the intelligent driving software bench to receive and process real vehicle data from the external domain and simulate the formation of backfilling data on the industrial control machine, the resource consumption and cost problems caused by access to multiple controllers in the prior art are solved. It realizes efficient data recharge of intelligent driving software.
Patent Information
- Application Number
- CN202411184945.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-27
- Publication Date
- 2024-12-03
AI Technical Summary
The existing intelligent driving software bench requires multiple controllers and sensors to access to simulate full-link data recharge, resulting in high resource consumption and high cost.
Receive external real-vehicle data through communication protocol, add time stamps and data IDs, and send them to the industrial control machine. The industrial control machine forms simulated real-vehicle receiving data based on these data and sends it back to the domain controller to be tested to realize full-link data back Drink.
This reduces the number of equipment on the bench, reduces resource consumption and cost, and realizes full-link data recharge of multiple sensors and controllers.
Smart Images

Figure CN119065979A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of intelligent driving technology, and in particular to a data re-injection method, a detection bench, a device and a computer-readable storage medium. Background Art
[0002] With the rapid development of the field of intelligent driving, the iteration speed of intelligent driving software and vehicle models equipped with intelligent driving software has accelerated, and the pace of version updates of controllers, sensors, and corresponding software has also accelerated; in order to improve the efficiency of controller software development, reduce labor and equipment costs during software testing, and quickly locate bugs in the software, it is necessary to conduct bench stability testing and functional testing when the software is released.
[0003] In the real car scenario, the intelligent driving software runs in an intelligent driving controller, which interacts with multiple other controllers or sensors. In related technologies, when the intelligent driving controller is bench tested, the source data of the real car is generally recorded from the sensor end or other controllers of the real car, and then the source data measured on the real car is input into the corresponding sensor or controller on the bench, and then enters the intelligent driving controller where the intelligent driving software is located through the data stream to realize data re-injection.
[0004] However, since the data link of the actual vehicle is long, the test bench needs to be connected to multiple controllers and sensors to simulate the reinjection of the entire link, which consumes a lot of resources and has high deployment costs for a large number of test benches.
[0005] Therefore, it is necessary to design a new data re-injection method to overcome the above problems. Summary of the invention
[0006] The present application provides a data reinjection method, a detection stand, a device and a computer-readable storage medium, which can solve the technical problems existing in the related art that the stand needs to be connected to multiple controllers and sensors to simulate full-link reinjection, which consumes a lot of resources and is costly.
[0007] In a first aspect, an embodiment of the present application provides a data re-injection method, the data re-injection method comprising:
[0008] Receive external real vehicle data through communication protocol;
[0009] Adding a timestamp and a data ID to the external domain real vehicle data to obtain first data, wherein the data ID corresponds to a service corresponding to the external domain real vehicle data;
[0010] Sending the plurality of the first data to an industrial computer;
[0011] The data re-injection is completed by receiving the re-injection data from the industrial computer, wherein the re-injection data is simulated real vehicle receiving data formed by the industrial computer according to the plurality of the first data and the corresponding timestamps and data IDs.
[0012] In combination with the first aspect, in one implementation, the receiving of external domain real vehicle data through a communication protocol includes:
[0013] Receive external controller data and sensor data encapsulated through communication protocols.
[0014] In combination with the first aspect, in one implementation, the adding of a timestamp and a data ID to the external domain real vehicle data to obtain the first data, wherein the data ID corresponds to a service corresponding to the external domain real vehicle data, includes:
[0015] Obtain the time of receiving the external domain real vehicle data and remove the data header of the external domain real vehicle data;
[0016] A timestamp of the receiving time and a data ID are added to the external domain real vehicle data to obtain first data, and the data ID corresponds to the service corresponding to the external domain real vehicle data.
[0017] In combination with the first aspect, in one implementation, sending the plurality of first data to an industrial computer includes:
[0018] storing a plurality of the first data in a memory;
[0019] The plurality of first data stored in the memory are periodically sent to the industrial computer.
[0020] In combination with the first aspect, in one implementation, before receiving the recharge data from the industrial computer to complete the data recharge, the industrial computer further performs the following steps:
[0021] receiving a plurality of the first data, and parsing out a plurality of data IDs of the first data;
[0022] According to the pre-stored correspondence between the data ID and the service, the method of corresponding service of each of the first data is called, and a plurality of re-injection data is formed based on the plurality of first data.
[0023] In combination with the first aspect, in one implementation, the industrial computer further performs the following steps:
[0024] Parsing out multiple timestamps of the first data;
[0025] The backfill data is sent to the domain controller to be tested in sequence according to the order of the timestamps.
[0026] In combination with the first aspect, in one implementation, the refill data is sent to the domain controller to be tested in sequence according to the order of the timestamps and the time intervals between the timestamps.
[0027] In the second aspect, an embodiment of the present application provides a detection bench, which includes a domain controller to be tested and an industrial computer, wherein the domain controller to be tested is used to receive external domain real vehicle data through a communication protocol; add a timestamp and a data ID to the external domain real vehicle data to obtain first data, and the data ID corresponds to the service corresponding to the external domain real vehicle data; send multiple first data to the industrial computer; the industrial computer is used to receive multiple first data, and form re-injection data according to the correspondence between the first data and the pre-stored data ID and the service, and send the re-injection data to the domain controller to be tested; the domain controller to be tested is also used to receive the re-injection data from the industrial computer to complete data re-injection.
[0028] In a third aspect, an embodiment of the present application provides a data reinjection device, which includes a processor, a memory, and a data reinjection program stored in the memory and executable by the processor, wherein when the data reinjection program is executed by the processor, the steps of the above-mentioned data reinjection method are implemented.
[0029] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a data re-injection program is stored, wherein when the data re-injection program is executed by a processor, the steps of the above-mentioned data re-injection method are implemented.
[0030] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:
[0031] The external domain real vehicle data is received through the communication protocol, and the domain controller to be tested adds a timestamp and data ID to the external domain real vehicle data and sends it to the industrial computer. The industrial computer can simulate the sending end according to the first data, timestamp and data ID sent, and send the feedback data to the domain controller to be tested, so that one domain controller to be tested and the industrial computer can complete the full-link data feedback of multiple sensors and controllers, which solves the technical problem in related technologies that the test bench needs to connect multiple controllers and sensors to simulate the full-link feedback, which consumes a lot of resources and is costly. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] Figure 1 This is a flow chart of an embodiment of the data re-injection method of the present application;
[0033] Figure 2 This is a flow chart of an industrial computer executing step 1 of an embodiment of the present application;
[0034] Figure 3 This is a schematic diagram of the structure of the test bench for this application;
[0035] Figure 4 This is a schematic diagram of the architecture of the test bench data re-injection for this application;
[0036] Figure 5 This is a schematic diagram of the communication protocol data structure in the embodiment of the present application;
[0037] Figure 6 This is a schematic diagram of the data structure of the first data in the embodiment of the present application;
[0038] Figure 7 This is a schematic diagram of the hardware structure of the data re-injection device involved in the embodiment of the present application. DETAILED DESCRIPTION
[0039] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0040] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.
[0041] In a first aspect, an embodiment of the present application provides a data re-injection method.
[0042] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the data re-injection method of this application. Figure 1 As shown, the data re-injection method includes:
[0043] S11: receiving external domain real vehicle data through a communication protocol.
[0044] In this step, it is preferred to use a general communication protocol, such as the DDS (Data Distribution Service) protocol. Of course, other protocols may also be used, without limitation. In step S11, the domain controller to be tested receives the external domain real vehicle data, and all the external domain real vehicle data required for re-injection are sent to the domain controller to be tested using the same set of general communication protocols. The external domain real vehicle data here may be obtained directly from the real vehicle or from other places, without limitation.
[0045] S12: Add a timestamp and a data ID to the external domain real vehicle data to obtain first data, where the data ID corresponds to a service corresponding to the external domain real vehicle data.
[0046] In step S12, after the domain controller to be tested receives the external domain real vehicle data, it records and processes the external domain real vehicle data, and adds a timestamp and data ID to obtain the first data. The data ID here can be, for example, hashid, which is the ID corresponding to each service in the communication protocol DDS, and hashid is mapped to the service. There are many services in this embodiment. For example, the hashids corresponding to the front corner radar and the rear corner radar are 03-80-9b-08 (hexadecimal) and 03-80-9c-08 (hexadecimal), respectively. Here is just one of the cases. If the vehicle model or hardware changes, the service may change.
[0047] S13: Sending the plurality of first data to the industrial computer. In this step, the domain controller to be tested sends the processed first data to the industrial computer.
[0048] S14: receiving the re-injection data from the industrial computer to complete the data re-injection, wherein the re-injection data is simulated real vehicle receiving data formed by the industrial computer according to the plurality of the first data and the corresponding timestamps and data IDs.
[0049] After step S13, the industrial computer receives multiple first data sent by the domain controller to be tested, and parses the multiple first data to parse out the data ID and timestamp, calls the method of the service corresponding to the data ID through the data ID, and forms simulated real vehicle reception data based on the first data and timestamp and sends it to the domain controller to be tested. In step S14, the domain controller to be tested receives the re-injected data from the industrial computer, and the playback of multiple controller or sensor data in the real vehicle scene can be completed through the industrial computer.
[0050] In this embodiment, the external domain real vehicle data are all sent to the domain controller to be tested using the same set of general communication protocols, and the domain controller to be tested adds a timestamp and a data ID to the external domain real vehicle data and sends it to the industrial computer. The industrial computer can form simulated real vehicle reception data according to the first data, timestamp and data ID sent by the domain controller to be tested, and simulate the external domain sending end to send the simulated real vehicle reception data to the domain controller to be tested, thereby realizing full-link data re-injection of multiple sensors and controllers by one domain controller to be tested and the industrial computer, that is, the test bench only needs at least one domain controller to be tested and the industrial computer to realize full-link data re-injection, and there is no need to set up multiple sensors or controllers for receiving corresponding source data on the test bench as in the related art, which greatly reduces the number of devices on the test bench, can reduce resource consumption and reduce costs, and solves the technical problem that the test bench needs multiple controllers and sensors to be connected to simulate full-link re-injection in the related art, which consumes a lot of resources and is costly.
[0051] Furthermore, in one embodiment, in step S11, the receiving of external domain real vehicle data through the communication protocol may include: receiving external controller data and sensor data encapsulated through the communication protocol. In this embodiment, the domain controller to be tested carried by the intelligent driving software is generally directly connected to multiple sensors and external controllers in the real vehicle, and receives all data from multiple sensors and external controllers to realize the control of intelligent driving, such as automatic parking, cruise control, etc.; in this embodiment, all external controller data and sensor data on the real vehicle needed by the domain controller to be tested are encapsulated through the communication protocol, and the service encapsulation interface of the communication protocol can split a large amount of data into specific data structures for sending and receiving.
[0052] Further, in one embodiment, in step S12, the adding of a timestamp and a data ID to the external domain real vehicle data to obtain the first data, wherein the data ID corresponds to a service corresponding to the external domain real vehicle data, includes:
[0053] S121: Obtain the time of receiving the external domain real vehicle data and remove the data header of the external domain real vehicle data.
[0054] S122: Add a timestamp of the receiving time and a data ID to the external domain real vehicle data to obtain first data, wherein the data ID corresponds to a service corresponding to the external domain real vehicle data.
[0055] For details, see Figure 5 The data structure of the general communication protocol is shown, including the data header, data and timestamp. Figure 6The data structure of the first data after being processed by the domain controller to be tested is shown. After being processed by the domain controller to be tested, the data header is removed, the data part is taken out without processing, and the timestamp (timestamp) when the domain controller to be tested receives each external domain real vehicle data and the data ID corresponding to each external domain real vehicle data are added; the data header is used for communication. After the first communication, the data header is removed. When the data forwarded subsequently communicates again, the called service will re-encapsulate a data header. Among them, Figure 5 The timestamp in the message refers to the time when the peer calls the service to send data to the domain controller to be tested. Figure 6 The timestamp in is the time when the domain controller under test receives the data and removes the data header for encapsulation. Figure 3 As shown, in this embodiment, the domain controller to be tested includes a data communication module, which receives the external domain real vehicle data and performs the above-mentioned processing on the received external domain real vehicle data to form the first data.
[0056] When the domain controller to be tested in this embodiment receives each external domain real vehicle data, it will record the time when each external domain real vehicle data is received, and encapsulate the timestamp when each external domain real vehicle data is received into the data structure of the corresponding first data, so that the subsequent industrial computer can sort them according to the time when each external domain real vehicle data is received, and send the feedback data to the domain controller to be tested in chronological order; and the data ID is also encapsulated into the data structure of the corresponding first data, so that the subsequent industrial computer can find the corresponding service according to the data ID of each first data.
[0057] Further, in one embodiment, in step S13, sending the plurality of the first data to the industrial computer may include:
[0058] S131: Storing the plurality of first data in a memory.
[0059] S132: Periodically sending the plurality of first data stored in the memory to the industrial computer.
[0060] See also Figure 3As shown, in this embodiment, the domain controller to be tested also includes a shared memory. After the data communication module processes the external domain real vehicle data to form the first data, the first data will be stored in the shared memory and published in the domain using the shared memory method. The downstream application can use the data from the shared memory for the realization of the function. The data communication module is essentially to isolate the remaining modules in the domain controller to be tested from the communication outside the domain, that is, the data outside the domain enters the domain controller to be tested and is received by the data communication module, and then the data is processed and placed in the shared memory with a specific data structure. The domain controller to be tested may also include a refill communication module, which can read the first data from the shared memory, and the refill communication module communicates with the industrial computer, and can periodically send multiple first data to the industrial computer. In this embodiment, multiple first data stored in the memory are periodically sent to the industrial computer, mainly to facilitate the judgment of whether they are sent normally. Under the working conditions of the real vehicle, the amount of data in the cycle will fluctuate up and down under a certain value. If there is an abnormal situation, it will be more obvious. Secondly, there is optimization in resources. If it is an event type, it will be called every time data enters, and the triggering frequency is too high.
[0061] In the real car scenario, the full data link is that the data from the external domain (including all data from other controllers and sensors directly connected to the controller equipped with the intelligent driving software) is sent to the controller equipped with the intelligent driving software through a general communication protocol, and is received and processed by the data communication module therein. The processed data is published in the domain using shared memory, and downstream applications take data from the shared memory for function implementation. In this embodiment, the domain controller to be tested also has an application module, see Figure 4 As shown, the industrial computer sends the feedback data to the domain controller to be tested through the general communication protocol. The data communication module in the domain controller to be tested receives the feedback data and sends it to the shared memory after parsing and processing the data. The application module reads the feedback data from the shared memory to collect information about the vehicle body and surrounding scenes, and can control different functions such as automatic parking and cruise control according to the algorithm.
[0062] Further, in one embodiment, see Figure 2 As shown, before receiving the re-injection data from the industrial computer and completing the data re-injection, the industrial computer also performs the following steps:
[0063] S21: receiving a plurality of the first data, and parsing out a plurality of data IDs of the first data.
[0064] S22: According to the pre-stored correspondence between the data ID and the service, the method of corresponding service of each of the first data is called, and a plurality of re-injection data is formed based on the plurality of first data.
[0065] In this embodiment, the data ID for communication with the external domain is consistent with that actually used in the real vehicle. By configuring the configuration file of the industrial computer in advance, the data ID can be mapped to the sending method of the corresponding data structure. After receiving the first data on the industrial computer, the refill module running in the industrial computer can store the received first data in the form of a file. Since the data ID is encapsulated in the data structure of the first data, when the refill is started, the refill module will parse the data structure of the first data, take out the data ID of each first data, and call the corresponding service to transfer the data from the industrial computer to the domain controller to be tested. The data ID corresponds to the service method during communication. Through the method that different data corresponds to different services, the user only needs to call the corresponding interface and input the corresponding data structure. In this embodiment, the data ID is mapped to the service, and the data structure has been recorded in the domain controller to be tested, so the corresponding method can be called only through the data ID, and the input data structure can also be used directly, avoiding the need for different structures for data with different data structures.
[0066] Furthermore, in one embodiment, the industrial computer further performs the following steps:
[0067] S23: Parse and obtain multiple timestamps of the first data.
[0068] Among them, step S23 can be performed simultaneously with step S21, or the timestamp can be parsed before the data ID is parsed, or the timestamp can be parsed after the data ID is parsed.
[0069] S24: Sending the refill data to the domain controller to be tested in sequence according to the order of the timestamps.
[0070] In this embodiment, since multiple timestamps are recorded in the cycle of the domain controller to be tested, when it is received on the industrial computer, the industrial computer will parse the data structure, take out the timestamps for comparison and arrangement, and send the re-injected data in the order of the timestamps. Since in the actual vehicle working conditions, data from multiple controllers / sensors will enter the domain controller to be tested run by the intelligent driving software at the same time, and at the same time, the data of each sensor / controller will also have multiple service calls in the same time period, this embodiment sorts the timestamps and calls the interface in the order of the timestamps, in order to restore the data transmission in the actual vehicle scene. And in this embodiment, the industrial computer calls the simulated sending interface in the order of the timestamp arrangement, and the input parameters are data ID and data structure. Since a general communication protocol is used, the domain controller to be tested only perceives the service corresponding to the data ID, so the simulated service method can re-inject the communication of the external domain.
[0071] Preferably, in one embodiment, when sending the refill data to the domain controller to be tested, the refill data is sent to the domain controller to be tested in sequence according to the order of the timestamps and the time intervals of the timestamps. Since there may be a certain time interval between two adjacent timestamps, this embodiment not only sends the refill data in the order of the timestamps, but also sends it in the time interval of each timestamp, which can simulate the real vehicle scene more realistically.
[0072] By adopting the data re-injection method provided in the embodiment of the present application, when the software carried by the domain controller to be tested is iterated, the real vehicle scenario can be simulated and the stability tested in advance on the test bench through data re-injection, so as to discover the bugs in the software of the domain controller to be tested in advance, and avoid a large number of problems in the real vehicle test that lead to the failure to release the software on schedule; and by recording the received external domain real vehicle data on the domain controller to be tested, and then arranging it according to the timestamp of the recorded data, and finally simulating the external domain on the industrial computer to send the data to the domain controller to be tested, the full-link data re-injection is completed, and at the same time, the test bench only needs one domain controller to be tested and the industrial computer connected to the domain controller to be tested.
[0073] In a second aspect, an embodiment of the present application also provides a detection stand.
[0074] In one embodiment, referring to Figure 3 , Figure 3 This is a schematic diagram of the functional modules of an embodiment of the detection bench of the present application. Figure 3 As shown, the test bench includes a domain controller to be tested and an industrial computer, the domain controller to be tested is used to receive external domain real vehicle data through a communication protocol; add a timestamp and a data ID to the external domain real vehicle data to obtain first data, and the data ID corresponds to the service corresponding to the external domain real vehicle data; send multiple first data to the industrial computer; the industrial computer is used to receive multiple first data, and form re-injection data according to the correspondence between the first data and the pre-stored data ID and the service, and send the re-injection data to the domain controller to be tested; the domain controller to be tested is also used to receive the re-injection data from the industrial computer to complete data re-injection.
[0075] Furthermore, in one embodiment, the domain controller to be tested includes a data communication module, and the data communication module is used to receive external controller data and sensor data encapsulated by a communication protocol.
[0076] Furthermore, in one embodiment, after receiving the external domain real vehicle data, the data communication module processes the external domain real vehicle data, specifically obtaining the time of receiving the external domain real vehicle data and removing the data header of the external domain real vehicle data; and adding the timestamp of the receiving time and the data ID to the external domain real vehicle data to obtain the first data, and the data ID corresponds to the service corresponding to the external domain real vehicle data.
[0077] Furthermore, in one embodiment, the domain controller to be tested also includes a shared memory, the data communication module sends the first data to the shared memory, and stores multiple first data in the shared memory; the domain controller to be tested also includes a feedback communication module, the feedback communication module can read the first data from the shared memory, and the feedback communication module communicates with the industrial computer, and can periodically send multiple first data stored in the memory to the industrial computer.
[0078] In this embodiment, due to the use of a universal communication protocol, when this type of data is received by the data communication module in the domain controller to be tested equipped with the intelligent driving software, the data header will be removed, and the data structure will be serialized and periodically pushed into the domain through protobuf and the timestamp and data ID of the moment through shared memory, and then a feedback communication module will communicate with the industrial computer to transmit the data periodically.
[0079] Furthermore, in one embodiment, the industrial computer is also used to receive multiple first data, parse out multiple data IDs of the first data; and according to the correspondence between the pre-stored data ID and the service, call the method of each service corresponding to the first data to form multiple re-injection data based on the multiple first data.
[0080] Furthermore, in one embodiment, the industrial computer is further used to parse out multiple timestamps of the first data; and send the re-injection data to the domain controller to be tested in sequence according to the order of the timestamps.
[0081] Preferably, in one embodiment, the industrial computer is further used to send the re-injection data to the domain controller to be tested in sequence according to the order of the timestamps and the time intervals between the timestamps.
[0082] In this embodiment, the domain controller to be tested also has an application module, see Figure 4 As shown, the application module reads the feedback data from the shared memory to collect information about the vehicle body and surrounding scenes, and can control different functions such as automatic parking and cruise control according to the algorithm.
[0083] Among them, the functional implementation of each module in the above-mentioned detection stand corresponds to the various steps in the above-mentioned data re-injection method embodiment, and its functions and implementation processes are no longer repeated here.
[0084] In a third aspect, an embodiment of the present application provides a data re-injection device, which may be a device having a data processing function, such as a personal computer (PC), a laptop computer, or a server.
[0085] Reference Figure 7 , Figure 7 Schematic diagram of the hardware structure of the data recharging device involved in the embodiment of the present application. In the embodiment of the present application, the data recharging device may include a processor, a memory, a communication interface and a communication bus.
[0086] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.
[0087] The communication interface includes input / output (I / O) interface, physical interface and logical interface, etc., which are used to realize the interconnection of devices inside the data return device, and the interface used to realize the interconnection between the data return device and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.
[0088] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.
[0089] The processor may be a general-purpose processor, and the general-purpose processor may call the data recharge program stored in the memory and execute the data recharge method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the data recharge program is called may refer to the various embodiments of the data recharge method of the present application, and will not be repeated here.
[0090] Those skilled in the art will understand that Figure 7 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
[0091] In a fourth aspect, an embodiment of the present application also provides a readable storage medium.
[0092] The readable storage medium of the present application stores a data re-injection program, wherein when the data re-injection program is executed by a processor, the steps of the above-mentioned data re-injection method are implemented.
[0093] Among them, the method implemented when the data re-injection program is executed can refer to the various embodiments of the data re-injection method of the present application, and will not be repeated here.
[0094] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.
[0095] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.
[0096] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.
[0097] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or. For example, A / B can mean A or B. The “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.
[0098] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.
[0099] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.
[0100] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A data re-injection method, It is characterized in that The data recharging method comprises: Receive external real vehicle data through communication protocol; Adding a timestamp and a data ID to the external domain real vehicle data to obtain first data, wherein the data ID corresponds to a service corresponding to the external domain real vehicle data; Sending the plurality of the first data to an industrial computer; The data re-injection is completed by receiving the re-injection data from the industrial computer, wherein the re-injection data is simulated real vehicle receiving data formed by the industrial computer according to the plurality of the first data and the corresponding timestamps and data IDs.
2. The data re-injection method according to claim 1, It is characterized in that The receiving of external domain real vehicle data through the communication protocol includes: Receive external controller data and sensor data encapsulated through communication protocols.
3. The data re-injection method according to claim 1, It is characterized in that The step of adding a timestamp and a data ID to the external domain real vehicle data to obtain the first data, wherein the data ID corresponds to a service corresponding to the external domain real vehicle data, includes: Obtain the time of receiving the external domain real vehicle data and remove the data header of the external domain real vehicle data; A timestamp of the receiving time and a data ID are added to the external domain real vehicle data to obtain first data, and the data ID corresponds to the service corresponding to the external domain real vehicle data.
4. The data re-injection method according to claim 1, It is characterized in that The sending of the plurality of the first data to the industrial computer comprises: storing a plurality of the first data in a memory; The plurality of first data stored in the memory are periodically sent to the industrial computer.
5. The data re-injection method according to claim 1, It is characterized in that Before receiving the re-injection data from the industrial computer and completing the data re-injection, the industrial computer also performs the following steps: receiving a plurality of the first data, and parsing out a plurality of data IDs of the first data; According to the pre-stored correspondence between the data ID and the service, the method of corresponding service of each of the first data is called, and a plurality of re-injection data is formed based on the plurality of first data.
6. The data re-injection method as claimed in claim 5, It is characterized in that The industrial computer also performs the following steps: Parsing out multiple timestamps of the first data; The backfill data is sent to the domain controller to be tested in sequence according to the order of the timestamps.
7. The data re-injection method as claimed in claim 6, It is characterized in that According to the sequence of the timestamps and the time intervals between the timestamps, the backfill data is sent to the domain controller to be tested in sequence.
8. A test bench, comprising a domain controller to be tested and an industrial computer, Features: The domain controller to be tested is used to receive external domain real vehicle data through a communication protocol; add a timestamp and a data ID to the external domain real vehicle data to obtain first data, wherein the data ID corresponds to a service corresponding to the external domain real vehicle data; and send a plurality of the first data to an industrial computer; The industrial computer is used to receive the plurality of the first data, form the re-injection data according to the correspondence between the first data and the pre-stored data ID and the service, and send the re-injection data to the domain controller to be tested; The domain controller to be tested is also used to receive the re-injection data from the industrial computer to complete the data re-injection.
9. A data re-injection device, It is characterized in that The data refill device comprises a processor, a memory, and a data refill program stored in the memory and executable by the processor, wherein when the data refill program is executed by the processor, the steps of the data refill method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a data re-injection program, wherein when the data re-injection program is executed by a processor, the steps of the data re-injection method according to any one of claims 1 to 7 are implemented.
