A test synchronization method, device, equipment and storage medium
By synchronously sending test sequences and time publishing nodes between test terminals of on-board domain controllers, the problem of insufficient test time accuracy of on-board domain controllers in the existing technology is solved, and more efficient synchronous testing is achieved, and the test results are improved. accuracy.
Patent Information
- Application Number
- CN202111537596.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-15
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2041-12-15
AI Technical Summary
In the prior art, when testing on-board domain controllers in smart cars, the test process of the two different processors is independent, resulting in poor time accuracy of the test results.
By synchronously sending the test sequence and time publishing nodes between the first test terminal and the second test terminal, the second test terminal is caused to update its time according to the received time publishing node, and to the first processor according to the updated time A second processor of different types is tested, thereby enabling synchronous testing of the on-board domain controller.
The time accuracy of the test results is improved, and the synchronous testing of the vehicle-mounted domain controller is realized by the first test terminal and the second test terminal, saving labor costs and simplifying the test process.
Smart Images

Figure CN114490199B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of testing technology, and in particular to a test synchronization method, device, equipment and storage medium. Background Art
[0002] With the development of science and technology, all walks of life have higher and higher requirements for testing efficiency. In the field of smart cars, when testing the vehicle domain controller, two devices are usually used to test the two different processors in the vehicle domain controller. However, the test process of these two devices is relatively independent, resulting in poor time accuracy of the test results. Therefore, a solution is urgently needed. Summary of the invention
[0003] Embodiments of the present application provide a test synchronization method, apparatus, device, and storage medium for improving the time accuracy of test results obtained by testing a vehicle-mounted domain controller.
[0004] An embodiment of the present application also provides a test synchronization method, including: a first test terminal determines at least one first test sequence used to test a first processor in the vehicle-mounted domain controller; sends at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal, so that the second test terminal updates the time according to the time publishing node and tests a second processor of a different type from the first processor in the vehicle-mounted domain controller according to the updated time and the at least one first test sequence received.
[0005] Further optionally, the first test terminal and the second test terminal run different operating systems; the operating system run by the first test terminal is adapted to the first processor, and the operating system run by the second terminal is adapted to the second processor.
[0006] Further optionally, after sending at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having a different operating system from the first test terminal, it also includes: receiving first status data returned by the first processor, and synchronizing the first status data to the second test terminal.
[0007] Further optionally, sending at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having an operating system different from that of the first test terminal includes: synchronously sending the at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and the second test terminal through at least one of TCP, UDP and a designated serial port protocol.
[0008] An embodiment of the present application also provides a test synchronization method, which is applied to a vehicle-mounted domain controller, and the method includes: receiving at least one first test sequence sent by a first test terminal and a time publishing node corresponding to each of the at least one first test sequences; the at least one first test sequence is used to test a first processor in the vehicle-mounted domain controller; according to the time publishing node corresponding to each of the at least one first test sequence, the time of the second test terminal is updated; and according to the updated time and the at least one first test sequence received, a second processor of a type different from that of the first processor in the vehicle-mounted controller is tested.
[0009] Further optionally, testing the second processor according to the received at least one first test sequence includes: converting the at least one first test sequence to obtain at least one second test sequence adapted to the operating system running on the second test terminal; and sending the at least one second test sequence to the second processor.
[0010] Further optionally, after testing the second processor of a different type from the first processor in the vehicle controller, it also includes: receiving first status data sent by the first test terminal and returned by the first processor; converting the received first status data to obtain second status data adapted to the operating system running on the second test terminal, and outputting the second status data.
[0011] An embodiment of the present application also provides a test synchronization device for testing a vehicle-mounted domain controller, the device comprising: a determination module, used to determine at least one first test sequence used to test a first processor in the vehicle-mounted domain controller; a testing module, used to send at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal, so that the second test terminal updates the time according to the time publishing node and tests the second processor of a different type from the first processor in the vehicle-mounted domain controller according to the updated time and the received at least one first test sequence.
[0012] An embodiment of the present application also provides a test synchronization device for testing a vehicle-mounted domain controller, the device comprising: a receiving module, used to: receive at least one first test sequence sent by a first test terminal and a time publishing node corresponding to each of the at least one first test sequence; the at least one first test sequence is used to test a first processor in the vehicle-mounted domain controller; an updating module, used to: update the time of a second test terminal according to the time publishing node corresponding to each of the at least one first test sequence; a testing module, used to: test a second processor of a different type from the first processor in the vehicle-mounted controller according to the updated time and the at least one first test sequence received.
[0013] An embodiment of the present application also provides an electronic device, comprising: a memory and a processor; wherein the memory is used to: store one or more computer instructions; the processor is used to execute the one or more computer instructions, so as to: execute the steps in the test synchronization method.
[0014] An embodiment of the present application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor is caused to implement the steps in the test synchronization method.
[0015] The embodiment of the present application provides a test synchronization method, device, equipment and storage medium, in which the first test terminal can synchronously send at least one first test sequence and at least one time release node corresponding to each first test sequence to the first processor and the second test terminal; the second test terminal can update the time of the second test terminal according to the time release node corresponding to each of the at least one first test sequence received, and test the second processor according to the updated time and the at least one first test sequence received. Through this implementation, the time release node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle domain controller, thereby improving the time accuracy of the test results. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0017] Figure 1 A structural schematic diagram of a test synchronization system provided by an exemplary embodiment of the present application;
[0018] Figure 2 A schematic diagram of a practical application provided by an exemplary embodiment of the present application;
[0019] Figure 3 A schematic diagram of a test synchronization method provided by an exemplary embodiment of the present application;
[0020] Figure 4 A schematic diagram of a test synchronization method provided by an exemplary embodiment of the present application;
[0021] Figure 5 A schematic diagram of a test synchronization device provided for an exemplary embodiment of the present application;
[0022] Figure 6 A schematic diagram of a test synchronization device provided for an exemplary embodiment of the present application;
[0023] Figure 7 A schematic diagram of the structure of an electronic device provided as an exemplary embodiment of the present application. DETAILED DESCRIPTION
[0024] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. 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 making creative work are within the scope of protection of the present application.
[0025] In view of the prior art, two devices are usually used to independently test two different processors in the vehicle domain controller, resulting in low test efficiency. In some embodiments of the present application, a solution is provided, which includes a test synchronization system composed of a first test terminal and a second test terminal. In the test synchronization system, the first test terminal can synchronously send at least one first test sequence and at least one time release node corresponding to each first test sequence to the first processor and the second test terminal; the second test terminal can update the time of the second test terminal according to the time release node corresponding to each of the at least one first test sequence received, and test the second processor according to the updated time and the at least one first test sequence received. Through this implementation, the time release node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle domain controller, thereby improving the time accuracy of the test results. The following is a detailed description of the technical solutions provided by each embodiment of the present application in conjunction with the accompanying drawings.
[0026] Figure 1 A structural diagram of a test synchronization system provided by an exemplary embodiment of the present application is shown in FIG. Figure 1As shown, the test synchronization system 100 includes a first test terminal 10 and a second test terminal 20 .
[0027] The test synchronization system 100 is used to test a vehicle-mounted domain controller, which includes at least a first processor and a second processor of different types. The processors are defined by "first" and "second", and are only used to distinguish the two processors included in the vehicle-mounted domain controller. In some embodiments, the first processor included in the vehicle-mounted domain controller is an Arm Cortex-M7, and the second processor is an Arm Cortex-A53.
[0028] Among them, the first test terminal 10 and the second test terminal 20 can be implemented as a vehicle-mounted terminal, a computer, a tablet computer or other forms of host computer devices, which are not limited in this embodiment. The first test terminal 10 and the second test terminal 20 can run different operating systems. It should be noted that in the field of testing of vehicle-mounted domain controllers, specific development software or development environments are usually required to test the first processor and the second processor respectively, such as CANOE (CAN open environment, a bus development environment), etc., but some development software and development environments are not universal for all operating systems, or some development software and development environments cannot run efficiently in all operating systems. Therefore, in this embodiment, in order to facilitate efficient testing of the first processor and the second processor, an operating system adapted to the first processor can be run on the first test terminal 10, and an operating system adapted to the second processor can be run on the second terminal 20. For example, the first test terminal 10 needs to use software R1 to test the first processor, and software R1 can only run on the Windows operating system, or when software R1 works more efficiently on the Windows operating system, the Windows operating system can be run on the first test terminal 10. When the first test terminal 10 needs to use software R2 to test the first processor, and software R2 can only run on the Linux operating system, or software R2 works more efficiently on the Linux operating system, the Linux operating system can be run on the second test terminal 20 .
[0029] In the test synchronization system 100 , the first test terminal 10 is used to synchronously send at least one first test sequence and at least one time publishing node corresponding to each of the first test sequences to the first processor and the second test terminal 20 .
[0030] Among them, the test sequence can be a continuous level sequence, which is used to perform power on / off test on the vehicle domain controller; the test sequence can also be a sequence composed of multiple control signals sent by other controllers, which is used to perform response test on the vehicle controller, etc., which is not limited in this embodiment.
[0031] It should be noted that the term “first” is used to limit the test sequence, which is only used to distinguish the test sequence sent by the first test terminal 10 , and does not limit the sending order and quantity of the test sequence.
[0032] The time release node refers to the time point when the first test terminal 10 sends the test sequence to the first processor. When the first test terminal 10 sends at least one first test sequence to the first processor, the time point when the at least one first sequence is sent can be synchronously sent to the second test terminal 20 as a time release node. It should be noted that the above process can be performed once each time a test sequence is sent.
[0033] For example, the first test terminal 10 sends the first test sequence L1 to the first processor at 9:00:00 in the morning. At the same time, the time point 9:00:00 when the first test sequence L1 is sent can be used as the time release node J0, and the test sequence L1 and the time release node J0 are synchronously sent to the second test terminal 20. The first test terminal 10 sends the first test sequence L2 to the first processor at 9:01:00 in the morning. At the same time, the time point 9:01:00 when the first test sequence L2 is sent can be used as the time release node J1, and the test sequence L2 and the time release node J0 are synchronously sent to the second test terminal 20.
[0034] In the test synchronization system 100, the second test terminal 20 can update the time of the second test terminal 20 according to the time publishing node corresponding to each of the at least one first test sequence received, so that the time of the second test terminal 20 is the same as that of the first test terminal 10. Continuing with the above example, after receiving the time publishing node J0, the second test terminal can update its own time 9:00:02 to 9:00:00.
[0035] After updating the time, the second test terminal 20 can test the second processor according to the updated time and the received at least one first test sequence. For example, after the second test terminal 20 updates the time 9:00:02 to 9:00:00, it can test the second processor according to the at least one first test sequence at 9:00:00.
[0036] In this embodiment, the first test terminal 10 included in the test synchronization system can synchronously send at least one first test sequence and at least one time publishing node corresponding to each first test sequence to the first processor and the second test terminal 20; the second test terminal 20 included in the test synchronization system can update the time of the second test terminal 20 according to the time publishing node corresponding to each received at least one first test sequence, and test the second processor according to the updated time and the received at least one first test sequence. Through this implementation, the time publishing node and the test sequence can be synchronized between the first test terminal 10 and the second test terminal 20, so that the first test terminal 10 and the second test terminal 20 synchronously test the vehicle-mounted domain controller, thereby improving the time accuracy of the test results.
[0037] In some optional embodiments, the second test terminal 10 is specifically used to: convert at least one first test sequence to obtain at least one second test sequence adapted to the operating system running on the second test terminal 20, and send at least one second test sequence to the second processor. Since the operating systems running on the first test terminal 10 and the second test terminal 20 are different, and the first processor and the second processor are respectively applicable to different operating systems, the second test terminal 20 cannot directly use the first test sequence to test the second processor after receiving the first test sequence. Therefore, the second test terminal 20 can convert the first test sequence into a second test sequence adapted to the operating system running on the second test terminal 20. After the conversion, the second test sequence can be sent to the second processor to test the second processor. For example, the second test terminal 20 running the Linux operating system can convert the first test sequence J1 received from the first test terminal 10 running the Windows operating system into a second test sequence Z1 adapted to the Linux operating system, and send the second test sequence Z1 to the second processor to test the second processor.
[0038] Through this implementation, the same test content can be synchronized and the same content can be tested. Moreover, by means of test sequence conversion, there is no need to edit and develop the test sequence in the second test terminal 20, thereby realizing automatic testing and saving labor costs.
[0039] In some optional embodiments, the first test terminal 10 is further used to: receive first status data returned by the first processor, and synchronize the first status data to the second test terminal 20. The first status data may include: at least one of a test log and a processor status.
[0040] The test log is used to record the events and test results that occurred during the test process. The processor status may include: normal operation, pre-sleep, sleep or abnormal operation. Taking the power on and off of the first processor as an example, after the first test terminal 10 tests the first processor, the first status data returned by the first processor is the abnormally running processor status and test log, and the received status data is synchronized to the second test terminal 20. In this way, after the test is completed, the user can view the status data on any one of the first test terminal 10 and the second test terminal 20 to analyze the cause of the abnormal operation of the first processor based on the status data.
[0041] In some optional embodiments, the second test terminal 20 is further used to: convert the received first state data to obtain second state data adapted to the operating system running on the second test terminal 20, and output the second state data.
[0042] Optionally, maintenance can be performed for abnormal operation of the processor based on the status data. If the test results of the test sequence are inconsistent with the expected results, the processor can be further repaired or adjusted. For example, if a power-on sequence is sent to the processor, but the processor still sleeps, it means that the processor is abnormal at this time, and an error can be reported for inspection by the operation and maintenance personnel.
[0043] In some scenarios, since the operating systems running on the first test terminal and the second test terminal are different, there is a possibility that the first state data cannot be displayed on the second test terminal. Therefore, in some embodiments, the first state data can be converted into second state data that is compatible with the operating system running on the second test terminal. For example: the second test terminal running the Linux operating system converts the first state data K1 received from the first test terminal running the Windows operating system into the second state data Y1 that is compatible with the Linux operating system, and outputs the second state data Y1 so that the user can view the state data on the second test terminal.
[0044] In some optional embodiments, the first test terminal is specifically used to synchronously send at least one first test sequence and at least one time publishing node corresponding to each of the first test sequences to the first processor and the second test terminal 20 through at least one of TCP (Transmission Control Protocol), UDP (User Datagram Protocol) and a specified serial port protocol.
[0045] UDP is a connectionless transport layer protocol that provides a method for applications to send encapsulated IP data packets without establishing a connection. TCP is a connection-oriented, reliable, byte stream-based transport layer communication protocol. It is a transmission protocol specially designed to provide reliable end-to-end byte streams on unreliable Internet networks. The specified serial port protocol may include: RS232 or RS-232C serial port protocols, which can be selected according to actual needs.
[0046] The following will be combined Figure 2 The test synchronization system provided by the embodiment of the present application is further described in detail with reference to the actual application scenario. The XCU in the figure may include: an Arm Cortex-M7 processor and an Arm Cortex-A53 processor, hereinafter referred to as M core and A core, respectively.
[0047] In the first test terminal running Windows operating system, CANoe, python (a programming language) and data synchronization server program are run, etc. The first test terminal is connected to the M core using CAN (Controller Area Network) bus, and is connected to the second test terminal running Linux operating system using tcp / udp communication protocol.
[0048] In the second test terminal running the Linux operating system, run shell (a command parser), python, c / c++ (a programming language) and data synchronization client program, etc., use the tcp / udp communication protocol and RS232 serial port protocol to connect to the A core in the XCU, and use the tcp / udp communication protocol to connect to the first test terminal running the Windows operating system.
[0049] Among them, the data synchronization server in the first test terminal not only sends the test sequence to the M core in the XCU, but also acts as a time publishing node to synchronize its own system time to the XCU and the second test terminal to ensure time synchronization of all devices during the test.
[0050] The Linux system used by the second test terminal running the data synchronization client can more conveniently communicate and debug with the A core in the XCU. The data synchronization client uses the TCP / UDP communication protocol to communicate with the data synchronization server, which can ensure the real-time nature of the data and also ensure sufficient bandwidth for large data transmission.
[0051] In addition to the test synchronization system provided in the above embodiments, the embodiment of the present application also provides a test synchronization method, which will be described below in conjunction with the accompanying drawings.
[0052] Figure 3is a flow chart of a test synchronization method provided by an exemplary embodiment of the present application. When the method is executed on the first test terminal side, it may include the following steps: Figure 3 Steps shown:
[0053] Step 301: A first test terminal determines at least one first test sequence for testing a first processor in a vehicle-mounted domain controller.
[0054] Step 302: Send at least one first test sequence and at least one time publishing node corresponding to each of the first test sequences to the first processor and the second test terminal, so that the second test terminal updates the time according to the time publishing node and tests the second processor of the vehicle domain controller that is different from the first processor type according to the updated time and the received at least one first test sequence.
[0055] Through this implementation, the time publishing node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle-mounted domain controller, thereby improving the time accuracy of the test results.
[0056] Further optionally, the first test terminal and the second test terminal run different operating systems; the operating system run by the first test terminal is adapted to the first processor, and the operating system run by the second terminal is adapted to the second processor.
[0057] The processors are limited by "first" and "second" only to distinguish between two processors included in the vehicle domain controller. In some embodiments, the first processor included in the vehicle domain controller is Arm Cortex-M7, and the second processor is Arm Cortex-A53.
[0058] Among them, the first test terminal and the second test terminal can be implemented as a vehicle-mounted terminal, a computer, a tablet computer or other forms of host computer devices, which are not limited in this embodiment. The first test terminal and the second test terminal can run different operating systems. It should be noted that in the field of testing the vehicle-mounted domain controller, specific development software or development environment is usually required to test the first processor and the second processor respectively, such as CANOE (CAN open environment, a bus development environment), etc., but some development software and development environments are not universal for all operating systems, or some development software and development environments cannot run efficiently in all operating systems. Therefore, in this embodiment, in order to facilitate efficient testing of the first processor and the second processor, an operating system adapted to the first processor can be run on the first test terminal, and an operating system adapted to the second processor can be run on the second terminal. For example, the first test terminal needs to use software R1 to test the first processor, and software R1 can only run on the Windows operating system, or when software R1 works more efficiently on the Windows operating system, the Windows operating system can be run on the first test terminal. When the first test terminal needs to use software R2 to test the first processor, and software R2 can only run on the Linux operating system, or software R2 works more efficiently on the Linux operating system, the Linux operating system can be run on the second test terminal.
[0059] Further optionally, after sending at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having a different operating system from the first test terminal, the first status data returned by the first processor can be received and synchronized to the second test terminal.
[0060] The first status data may include at least one of a test log and a processor status.
[0061] Among them, the test log is used to record the events and test results that occurred during the test process. Among them, the processor status may include: normal operation, pre-sleep, sleep or abnormal operation, etc. Taking the power on and off of the first processor as an example, after the first test terminal tests the first processor, the first status data returned by the first processor received is the processor status and test log of abnormal operation, and these received status data are synchronized to the second test terminal. In this way, after the test is completed, the user can view the status data on any terminal of the first test terminal and the second test terminal to analyze the cause of the abnormal operation of the first processor based on the status data.
[0062] Further optionally, when the first test terminal synchronously sends at least one first test sequence and at least one time publishing node corresponding to each first test sequence to the first processor and the second test terminal, it can synchronously send at least one first test sequence and at least one time publishing node corresponding to each first test sequence to the first processor and the second test terminal through at least one of TCP, UDP and a specified serial port protocol.
[0063] UDP is a connectionless transport layer protocol that provides a method for applications to send encapsulated IP data packets without establishing a connection. TCP is a connection-oriented, reliable, byte stream-based transport layer communication protocol. It is a transmission protocol specially designed to provide reliable end-to-end byte streams on unreliable Internet networks. The specified serial port protocol may include: RS232 or RS-232C serial port protocols, which can be selected according to actual needs.
[0064] In this embodiment, the first test terminal can synchronously send at least one first test sequence and at least one time publishing node corresponding to each of the first test sequences to the first processor and the second test terminal. Through this implementation, the time publishing node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle-mounted domain controller, thereby improving the time accuracy of the test results.
[0065] The embodiment of the present application also provides a test synchronization method, which will be described below in conjunction with the accompanying drawings.
[0066] Figure 4 is a flow chart of a test synchronization method provided by an exemplary embodiment of the present application. When the method is executed on the first test terminal side, it may include the following steps: Figure 4 Steps shown:
[0067] Step 401: Receive at least one first test sequence sent by a first test terminal and a time publishing node corresponding to each of the at least one first test sequence; the at least one first test sequence is used to test a first processor in the vehicle-mounted domain controller.
[0068] Step 402: Update the time of the second test terminal according to the time publishing node corresponding to at least one first test sequence.
[0069] Step 403: Test a second processor in the vehicle controller that is different in type from the first processor according to the updated time and the received at least one first test sequence.
[0070] Through this implementation, the time publishing node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle-mounted domain controller, thereby improving the time accuracy of the test results.
[0071] In some optional embodiments, since the operating systems running on the first test terminal and the second test terminal are different, and the first processor and the second processor are respectively applicable to different operating systems, the second test terminal cannot directly use the first test sequence to test the second processor after receiving the first test sequence. Therefore, the second test terminal can convert the first test sequence into a second test sequence adapted to the operating system running on the second test terminal. After the conversion, the second test sequence can be sent to the second processor to test the second processor. For example, the second test terminal running the Linux operating system can convert the first test sequence J1 received from the first test terminal running the Windows operating system into a second test sequence Z1 adapted to the Linux operating system, and send the second test sequence Z1 to the second processor to test the second processor.
[0072] Through this implementation, the same test content can be synchronized and the same content can be tested. Moreover, by means of test sequence conversion, there is no need to edit and develop the test sequence in the second test terminal, thus achieving automatic testing and saving labor costs.
[0073] In some scenarios, since the operating systems running on the first test terminal and the second test terminal are different, there is a possibility that the first state data cannot be displayed on the second test terminal. Therefore, in some embodiments, after testing the second processor of a different type from the first processor in the vehicle controller, the second test terminal can receive the first state data sent by the first test terminal and returned by the first processor, and convert the first state data into second state data adapted to the operating system running on the second test terminal. After the conversion, the second state data can be output. For example: the second test terminal running the Linux operating system converts the first state data K1 received from the first test terminal running the Windows operating system into the second state data Y1 adapted to the Linux operating system, and outputs the second state data Y1 so that the user can view the state data on the second test terminal.
[0074] In this way, after the test is completed, the user can view the status data on any one of the first test terminal and the second test terminal to analyze the cause of the abnormal operation of the first processor according to the status data.
[0075] Further optionally, the operating system running on the first test terminal is adapted to the first processor, and the operating system running on the second terminal is adapted to the second processor.
[0076] In this embodiment, the second test terminal can update the time of the second test terminal according to the time publishing node corresponding to each of the at least one first test sequence received, and test the second processor according to the updated time and the at least one first test sequence received. Through this implementation, the time publishing node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle-mounted domain controller, thereby improving the time accuracy of the test results.
[0077] It should be noted that the execution subject of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution subject of step 11 to step 12 can be device A; for another example, the execution subject of step 11 can be device A, and the execution subject of step 12 can be device B; and so on.
[0078] In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations appearing in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this document or may be executed in parallel, and the sequence numbers of the operations, such as 11, 12, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel.
[0079] It should be noted that the descriptions such as “first” and “second” in this article are used to distinguish different messages, devices, modules, etc., and do not represent the order of precedence, nor do they limit “first” and “second” to different types.
[0080] The present application embodiment provides a test synchronization device, such as Figure 5 As shown, the test synchronization device includes: a determination module 501 and a test module 502.
[0081] Among them, the determination module 501 is used to: determine at least one first test sequence used to test the first processor in the vehicle domain controller; the testing module 502 is used to: send at least one first test sequence and the time publishing node corresponding to the at least one first test sequence to the first processor and the second test terminal, so that the second test terminal updates the time according to the time publishing node and tests the second processor of the vehicle domain controller that is different from the first processor type according to the updated time and the received at least one first test sequence.
[0082] The first test terminal and the second test terminal run different operating systems; the operating system run by the first test terminal is adapted to the first processor, and the operating system run by the second terminal is adapted to the second processor.
[0083] Further optionally, the test module 502 is also used to: after sending at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having a different operating system from the first test terminal, receive first status data returned by the first processor, and synchronize the first status data to the second test terminal.
[0084] Further optionally, when the test module 502 sends at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having a different operating system from the first test terminal, it is specifically used to: synchronously send the at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and the second test terminal through at least one of TCP, UDP and a specified serial port protocol.
[0085] In this embodiment, the first test terminal can synchronously send at least one first test sequence and at least one time publishing node corresponding to each of the first test sequences to the first processor and the second test terminal; thus, the second test terminal can update the time of the second test terminal according to the time publishing node corresponding to each of the at least one first test sequence received, and test the second processor according to the updated time and the at least one first test sequence received. Through this implementation, the time publishing node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle-mounted domain controller, thereby improving the time accuracy of the test results.
[0086] The present application embodiment provides a test synchronization device, such as Figure 6 As shown, the test synchronization device includes: a receiving module 601, an updating module 602 and a testing module 603.
[0087] Among them, the receiving module 601 is used to: receive at least one first test sequence sent by the first test terminal and the time publishing node corresponding to each of the at least one first test sequence; the at least one first test sequence is used to test the first processor in the vehicle domain controller; the updating module 602 is used to: update the time of the second test terminal according to the time publishing node corresponding to each of the at least one first test sequence; the testing module 603 is used to: test the second processor of a different type from the first processor in the vehicle controller according to the updated time and the at least one first test sequence received.
[0088] Further optionally, when testing the second processor according to the at least one first test sequence received, the test module 603 is specifically used to: convert the at least one first test sequence to obtain at least one second test sequence adapted to the operating system running on the second test terminal, and send the at least one second test sequence to the second processor.
[0089] Further optionally, after testing the second processor of a different type from the first processor in the vehicle controller, the receiving module 601 is also used to: receive the first status data sent by the first test terminal and returned by the first processor; convert the received first status data to obtain second status data adapted to the operating system running on the second test terminal, and output the second status data.
[0090] In this embodiment, the first test terminal can synchronously send at least one first test sequence and at least one time publishing node corresponding to each of the first test sequences to the first processor and the second test terminal; thus, the second test terminal can update the time of the second test terminal according to the time publishing node corresponding to each of the at least one first test sequence received, and test the second processor according to the updated time and the at least one first test sequence received. Through this implementation, the time publishing node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle-mounted domain controller, thereby improving the time accuracy of the test results.
[0091] Figure 7 is a schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. Figure 7 As shown, the electronic device includes: a memory 701 and a processor 702.
[0092] The memory 701 is used to store computer programs and can be configured to store various other data to support operations on the terminal device. Examples of such data include instructions for any application or method operating on the terminal device, contact data, phone book data, messages, pictures, videos, etc.
[0093] Among them, the memory 701 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.
[0094] In some embodiments, the processor 702 is coupled to the memory 701 and is used to execute a computer program in the memory 701 to: determine at least one first test sequence used to test a first processor in the vehicle domain controller; send at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and the second test terminal, so that the second test terminal updates the time according to the time publishing node and tests the second processor of a different type from the first processor in the vehicle domain controller according to the updated time and the received at least one first test sequence.
[0095] Further optionally, the first test terminal and the second test terminal run different operating systems; the operating system run by the first test terminal is adapted to the first processor, and the operating system run by the second terminal is adapted to the second processor.
[0096] Further optionally, after sending at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having a different operating system from the first test terminal, the processor 702 is also used to: receive first status data returned by the first processor, and synchronize the first status data to the second test terminal.
[0097] Further optionally, when the processor 702 sends at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having a different operating system from the first test terminal, the processor 702 is specifically used to: synchronously send at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and the second test terminal through at least one of TCP, UDP and a specified serial port protocol.
[0098] In other embodiments, the processor 702 is coupled to the memory 701 and is used to execute a computer program in the memory 701, so as to: receive at least one first test sequence sent by a first test terminal and a time publishing node corresponding to each of the at least one first test sequence; the at least one first test sequence is used to test the first processor in the vehicle domain controller; according to the time publishing node corresponding to each of the at least one first test sequence, the time of the second test terminal is updated; and according to the updated time and the at least one first test sequence received, a second processor of a different type from the first processor in the vehicle controller is tested.
[0099] Further optionally, when the processor 702 tests the second processor according to the updated time and at least one first test sequence received, it is specifically used to: convert at least one first test sequence to obtain at least one second test sequence adapted to the operating system running on the second test terminal, and send at least one second test sequence to the second processor.
[0100] Further optionally, after testing the second processor of a different type from the first processor in the vehicle controller, the processor 702 is also used to: convert the received first state data to obtain second state data adapted to the operating system running on the second test terminal, and output the second state data.
[0101] Above Figure 7 The memory in can be implemented by any type of volatile or non-volatile storage device or a combination of them, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.
[0102] Above Figure 7 The display 703 in the embodiment includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
[0103] Further, if Figure 7 As shown, the electronic device also includes other components such as a communication component 704 and a power supply component 705. Figure 7 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 7Components shown.
[0104] Above Figure 7 The communication component 704 in is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component can be implemented based on near field communication (NFC) technology, radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
[0105] The power supply component 705 provides power to various components of the device where the power supply component is located. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply component is located.
[0106] In this embodiment, the first test terminal can synchronously send at least one first test sequence and at least one time publishing node corresponding to each of the first test sequences to the first processor and the second test terminal; the second test terminal can update the time of the second test terminal according to the time publishing node corresponding to each of the at least one first test sequence received, and test the second processor according to the updated time and the at least one first test sequence received. Through this implementation, the time publishing node and the test sequence can be synchronized between the first test terminal and the second test terminal, so that the first test terminal and the second test terminal synchronously test the vehicle-mounted domain controller, thereby improving the time accuracy of the test results.
[0107] Accordingly, an embodiment of the present application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to implement the steps in the test synchronization method.
[0108] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0109] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0110] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0111] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0112] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0113] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0114] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0115] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0116] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims
1. A test synchronization method, applied to a vehicle-mounted domain controller, characterized in that: include: The first test terminal determines at least one first test sequence used to test the first processor in the vehicle-mounted domain controller; Sending at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and the second test terminal, so that the second test terminal updates the time according to the time publishing node and tests the second processor of a different type from the first processor in the vehicle domain controller according to the updated time and the at least one first test sequence received, and the updated time of the second test terminal is the same as that of the first test terminal; The first test terminal and the second test terminal run different operating systems; The operating system running on the first test terminal is adapted to the first processor, and the operating system running on the second test terminal is adapted to the second processor.
2. The method according to claim 1, characterized in that After sending at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having a different operating system from the first test terminal, the method further includes: The first state data returned by the first processor is received, and the first state data is synchronized to the second test terminal.
3. The method according to any one of claims 1 to 2, characterized in that: Sending at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to the first processor and a second test terminal having an operating system different from that of the first test terminal, includes: The at least one first test sequence and the time publishing node corresponding to each of the at least one first test sequence are synchronously sent to the first processor and the second test terminal through at least one of TCP, UDP and a designated serial port protocol.
4. A test synchronization method, applied to a vehicle-mounted domain controller, characterized in that: include: receiving at least one first test sequence sent by a first test terminal and a time publishing node corresponding to each of the at least one first test sequence; The at least one first test sequence is used to test the first processor in the vehicle-mounted domain controller; updating the time of the second test terminal according to the time publishing node corresponding to each of the at least one first test sequences, wherein the updated time of the second test terminal is the same as the time of the first test terminal; Testing a second processor of the vehicle domain controller that is different in type from the first processor according to the updated time and the received at least one first test sequence; The first test terminal and the second test terminal run different operating systems; The operating system running on the first test terminal is adapted to the first processor, and the operating system running on the second test terminal is adapted to the second processor.
5. The method according to claim 4, characterized in that Testing the second processor according to the received at least one first test sequence includes: Converting the at least one first test sequence to obtain at least one second test sequence adapted to the operating system running on the second test terminal; The at least one second test sequence is sent to the second processor.
6. The method according to claim 4 or 5, characterized in that: After testing a second processor in the vehicle domain controller that is different in type from the first processor, the method further includes: receiving first status data sent by the first test terminal and returned by the first processor; The received first state data is converted to obtain second state data adapted to the operating system running on the second test terminal, and the second state data is output.
7. A test synchronization device for testing a vehicle-mounted domain controller, characterized in that: The device comprises: A determination module, configured to: enable a first test terminal to determine at least one first test sequence for testing a first processor in the vehicle-mounted domain controller; A test module, configured to: send at least one first test sequence and a time publishing node corresponding to each of the at least one first test sequence to a first processor and a second test terminal, so that the second test terminal updates the time according to the time publishing node and tests a second processor of a different type from the first processor in the vehicle domain controller according to the updated time and the at least one first test sequence received, and the updated time of the second test terminal is the same as that of the first test terminal; The first test terminal and the second test terminal run different operating systems; the operating system run by the first test terminal is adapted to the first processor, and the operating system run by the second test terminal is adapted to the second processor.
8. A test synchronization device for testing a vehicle-mounted domain controller, characterized in that: The device comprises: A receiving module, configured to: receive at least one first test sequence sent by a first test terminal and a time publishing node corresponding to each of the at least one first test sequence; the at least one first test sequence is used to test the first processor in the vehicle-mounted domain controller; An updating module, configured to: update the time of the second test terminal according to the time publishing node corresponding to each of the at least one first test sequence, wherein the updated time of the second test terminal is the same as the time of the first test terminal; A testing module, configured to: test a second processor in the vehicle domain controller that is different in type from the first processor according to the updated time and the received at least one first test sequence; The first test terminal and the second test terminal run different operating systems; the operating system run by the first test terminal is adapted to the first processor, and the operating system run by the second test terminal is adapted to the second processor.
9. An electronic device, characterized in that: include: Memory and processor; Wherein, the memory is used to: store one or more computer instructions; The processor is used to execute the one or more computer instructions to: perform the steps in the method according to any one of claims 1-6.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processor is caused to implement the steps in the method according to any one of claims 1 to 6.
