Vehicle bus testing method, system, medium and electronic device

CN122884826APending Publication Date: 2026-10-09SAIC GENERAL MOTORS +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610907165.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-06-23
Publication Date
2026-10-09

AI Technical Summary

Benefits of technology

[0022]根据本公开实施例,通过将测试任务配置数据和测试资源数据生成为测试任务,并通过第一通信模块和第二通信模块向总线仿真环境传递执行控制数据,可以使控制侧的数据处理过程与测试执行侧的测试运行过程通过执行控制数据进行衔接。通过将测试执行数据、测试用例标识数据和测试执行时间写入测试执行记录,可以为测试结果追踪、报告输出以及不同测试批次之间的数据查询提供数据基础。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122884826A_ABST
    Figure CN122884826A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a vehicle-mounted bus testing method, system, medium and electronic device. The testing method comprises: receiving testing task configuration data; generating a testing task based on the testing task configuration data and testing resource data; sending execution control data corresponding to the testing task to a second communication module through a first communication module, the execution control data being used to control the second communication module to control a bus simulation environment to run a testing case corresponding to testing case set data based on simulation running resources; receiving testing execution data, the testing execution data being data generated by the bus simulation environment running the testing case; and writing a testing execution record, the testing execution record comprising the testing execution data, corresponding testing case identification data and testing execution time.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of vehicles, and in particular to onboard bus testing methods, testing systems, non-transitory computer-readable storage media, and electronic devices. Background Technology

[0002] Testing of onboard electronic control units typically involves processing various types of test data, including those related to controller area networks (CLANs), local area networks (LANs), Ethernet, diagnostic protocols, refresh procedures, and secure access procedures. As the number of control units, communication links, and diagnostic functions in a vehicle's electrical and electronic architecture increases, the communication parameters, diagnostic parameters, test cases, test runtime resources, and test result records involved in the testing process also increase.

[0003] The content described herein is provided only as background information in connection with this disclosure and is not necessarily prior art. Summary of the Invention

[0004] According to one aspect of this disclosure, a method for testing an on-board bus is provided. The method includes: receiving test task configuration data, which includes communication parameters, diagnostic parameters, and test case set data for an electronic control unit under test (ECU). Based on the test task configuration data and test resource data, a test task is generated. The test resource data includes simulation runtime resources, a first parameter, and a second parameter. The simulation runtime resources are used to configure the test runtime state of the bus simulation environment. The first parameter indicates parameters that change with the test task, and the second parameter indicates parameters corresponding to the ECU under test or the simulation runtime resources. The method also includes: sending execution control data corresponding to the test task to a second communication module via a first communication module. The execution control data is used to enable the second communication module to control the bus simulation environment to run test cases corresponding to the test case set data based on the simulation runtime resources. The method further includes: receiving test execution data, which is data generated by the bus simulation environment running test cases. Finally, the method includes: writing a test execution record, which includes the test execution data, corresponding test case identification data, and test execution time.

[0005] In some embodiments, the first communication module is a communication client located on the control software side, and the second communication module is a communication server located on the test execution side. The first communication module and the second communication module transmit execution control data through a socket communication connection.

[0006] In some embodiments, the execution control data includes at least one of the following: control data for loading simulation runtime resources, control data for starting test scripts, control data for setting test parameters, control data for starting test runs, control data for stopping test runs, and control data for exporting test results.

[0007] In some embodiments, the test case identification data includes a test level field, a communication protocol field, a diagnostic protocol field, a functional domain field, a risk level field, and a test case number field.

[0008] In some embodiments, generating test tasks based on test task configuration data and test resource data includes: determining test cases corresponding to communication parameters or diagnostic parameters based on communication protocol fields or diagnostic protocol fields.

[0009] In some embodiments, generating a test task based on test task configuration data and test resource data includes: determining the execution order of test cases in the test task or the statistical category of test cases in the test report based on the risk level field.

[0010] In some embodiments, test execution data includes at least one of the following: test case running status, test pass results, test failure results, diagnostic response data, bus message data, message simulation data, response comparison results, error data, log file path, and test report file path.

[0011] In some embodiments, test execution records are located in a historical data structure, where the first dimension of the historical data structure corresponds to test case identification data and the second dimension of the historical data structure corresponds to the test execution time series.

[0012] In some embodiments, the test task corresponds to a functional module, which includes a security configuration module, a refresh module, or a diagnostic communication via Internet Protocol module. The execution control data is also used to call the functional module.

[0013] In some embodiments, the security configuration module is used to perform key injection, secure boot configuration data writing, security status query, or MCT verification.

[0014] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements an on-board bus testing method according to any embodiment of this disclosure.

[0015] According to another aspect of this disclosure, an on-board bus testing system is provided. The system includes a control device, a task processing module, a first communication module, a test execution device, and a data storage module. The control device receives test task configuration data, which includes communication parameters, diagnostic parameters, and test case set data for the electronic control unit under test (ECU). The task processing module generates test tasks based on the test task configuration data and test resource data. The test resource data includes simulation runtime resources, a first parameter, and a second parameter. The simulation runtime resources configure the test runtime state of the bus simulation environment. The first parameter indicates parameters that change with the test task, and the second parameter indicates parameters corresponding to the ECU under test or the simulation runtime resources. The first communication module sends execution control data corresponding to the test task to the second communication module. The test execution device includes the second communication module and the bus simulation environment. The second communication module controls the bus simulation environment to run test cases corresponding to the test case set data based on the simulation runtime resources, according to the execution control data. The data storage module writes test execution records, which include test execution data generated by the bus simulation environment running test cases, corresponding test case identification data, and test execution time.

[0016] In some embodiments, the system further includes a report output module for outputting a test report based on the test execution record.

[0017] In some embodiments, the report output module is used to output PDF or XML format reports.

[0018] In some embodiments, the system further includes a functional plug-in module, which includes at least one of a security configuration module, a refresh module, and a diagnostic communication via Internet Protocol module. The task processing module is also used to invoke the functional plug-in module according to the test task.

[0019] In some embodiments, the system further includes a hardware interface device connected between the electronic control unit under test and the bus analysis device. The hardware interface device includes at least one of a controller area network interface, a local area network interface, an Ethernet interface, a power control interface, a relay contact terminal, and a differential communication terminal.

[0020] In some embodiments, the hardware interface device is used for voltage programming control in the range of 0V to 18V.

[0021] According to another aspect of this disclosure, an electronic device is provided. The electronic device includes a processor and a memory, the memory storing a computer program that, when executed by the processor, implements an on-board bus testing method according to any embodiment of this disclosure.

[0022] According to embodiments of this disclosure, by generating test tasks from test task configuration data and test resource data, and transmitting execution control data to the bus simulation environment through a first communication module and a second communication module, the data processing process on the control side and the test execution process on the test execution side can be connected through execution control data. By writing test execution data, test case identification data, and test execution time into the test execution record, a data foundation can be provided for test result tracking, report output, and data querying between different test batches. Attached Figure Description

[0023] Figure 1 This is a flowchart of a vehicle bus testing method provided in some embodiments of this disclosure.

[0024] Figure 2 This is a schematic diagram of the modules of an in-vehicle bus testing system provided in some embodiments of this disclosure.

[0025] Figure 3 This is a schematic diagram of the technical route of the vehicle bus testing system provided in some embodiments of this disclosure.

[0026] Figure 4 This is a schematic diagram of a hardware interface device provided in some embodiments of this disclosure.

[0027] Figure 5 This is a schematic diagram of the test case identification data structure provided in some embodiments of this disclosure.

[0028] Figure 6 This is a schematic diagram of test hardware connections provided in some embodiments of this disclosure.

[0029] Figure 7 This is a schematic diagram of the structure of an electronic device provided in some embodiments of this disclosure. Detailed Implementation

[0030] The following describes some of the various embodiments of this disclosure, intended to provide a basic understanding of this disclosure, and is not intended to identify key or decisive elements of this disclosure, nor to limit the scope of protection sought.

[0031] In this disclosure, unless the context clearly indicates otherwise, terms such as "first" and "second" are primarily used to distinguish different objects and do not necessarily indicate an order, priority, or quantity limitation between objects. For example, a first communication module and a second communication module can represent two different communication entities, communication processes, communication interfaces, or communication objects, and do not imply that they must operate sequentially in numerical order.

[0032] In this disclosure, the term "vehicle bus testing" can refer to communication testing, diagnostic testing, refresh testing, secure access testing, bus message testing, network management testing, or a combination thereof for vehicle electronic control units. The bus or network involved in vehicle bus testing may include Controller Area Network (CAN), Local Interconnect Network (LIN), Ethernet, Diagnostics over Internet Protocol (DoIP), or other buses or communication networks suitable for vehicle communication. Vehicle bus testing is not limited to a specific test tool or a specific communication protocol.

[0033] In this disclosure, the term "test task configuration data" can refer to the set of data used to form or trigger a test task. Test task configuration data may include communication parameters, diagnostic parameters, and test case set data for the electronic control unit under test (ECU). Communication parameters may include bus channel, communication address, baud rate, network address, communication protocol type, or a combination thereof. Diagnostic parameters may include diagnostic address, diagnostic service type, diagnostic session type, security access level, data identifier, routine identifier, or a combination thereof. Test case set data may indicate one or more test cases to be run, or it may indicate the test scope, test category, or test set associated with the test cases to be run.

[0034] In this disclosure, the term "test resource data" can refer to data, files, interfaces, scripts, parameters, or resource sets used to support the execution of test tasks. Test resource data may include simulation runtime resources, a first parameter, and a second parameter. Simulation runtime resources are used to configure the test runtime state of the bus simulation environment. Simulation runtime resources are not limited to project files, but may also include script files, configuration files, variable tables, channel configurations, message database files, test execution entry points, library files, test sequence files, diagnostic description files, or combinations thereof. In one specific embodiment, the bus simulation environment may be CANoe, and the simulation runtime resources may include CANoe project files, CAPL scripts, system variable configurations, communication channel configurations, diagnostic description files, or message database files. The first parameter may indicate parameters that change with the test task, such as the input value of this test, diagnostic request parameters, file path for writing, security access parameters, execution count, or test output path. The second parameter may indicate parameters corresponding to the electronic control unit under test (ECU) or simulation runtime resources, such as ECU model, communication channel, diagnostic address, network address, project path, project version, test script version, or resource version.

[0035] In this disclosure, the terms "first communication module" and "second communication module" refer to two data transmission entities that communicate with each other. The first communication module can be located on the control software side, task processing side, control device side, or user operation side; the second communication module can be located on the test execution side, bus simulation environment side, test execution device side, or server side. The first and second communication modules can transmit execution control data and test execution data through socket communication connections, application programming interface calls, shared memory, message queues, event listening, message listening, inter-process communication, or other data exchange methods. In one specific embodiment, the socket communication connection between the first and second communication modules can be implemented based on Socket.io to transmit execution control data, test status data, or test execution data between the control software side and the test execution side. The first and second communication modules are not limited to specific software names, product names, or communication library names.

[0036] In this disclosure, the term "test execution record" can refer to a data record used to solidify the results of one or more test executions. A test execution record may include test execution data, corresponding test case identification data, and test execution time. Test execution records can be stored in a database, history file, log file, matrix data structure, tabular data structure, key-value data structure, or other data structures that can be read by a processor. Test execution records can be used for test result querying, test report output, batch result comparison, failure result location, or test traceability.

[0037] The following provides exemplary descriptions of the vehicle bus testing methods, vehicle bus testing systems, electronic devices, non-transitory computer-readable storage media, and computer program products provided in this disclosure.

[0038] In some scenarios involving multiple vehicle models, multiple electronic control units, and multiple batches of testing, the lack of a unified data organization method for test task configuration data, test resource data, and test execution records can easily increase the amount of repetitive processing of test configurations and make the correlation between test execution data and test cases, test time, and test results unclear. Furthermore, the absence of a unified control entry point for data interaction between control software, bus simulation environment, test scripts, and hardware interfaces can also increase the processing burden of test process switching, result tracking, and test resource reuse.

[0039] Figure 1 This is a flowchart of an in-vehicle bus testing method provided in some embodiments of this disclosure. (See also...) Figure 1 The vehicle bus testing method may include the following steps.

[0040] In step S101, test task configuration data is received, which includes communication parameters, diagnostic parameters, and test case set data for the electronic control unit under test.

[0041] Test task configuration data can be received by the control device, test control software, task processing module, or other test management program. The electronic control unit (ECU) under test (DUT) can be a vehicle control unit, body controller, domain controller, battery management controller, powertrain controller, gateway controller, or other on-board electronic control unit. Communication parameters can be used to determine the communication link or communication method corresponding to the DUT. Diagnostic parameters can be used to determine the diagnostic communication process corresponding to the DUT. Test case set data can be used to indicate one or more test cases to be run.

[0042] In some embodiments, test task configuration data can be provided by a configuration interface, configuration file, database records, test plan file, test case management module, or external test management system. Test task configuration data may include the electronic control unit type, communication protocol type, diagnostic protocol type, test scope, test set, test execution conditions, test output path, or a combination thereof, corresponding to this test. In some embodiments, test task configuration data may also be imported from an external structured configuration file, which may include test parameters, test case selection information, or test execution conditions.

[0043] By organizing communication parameters, diagnostic parameters, and test case set data into test task configuration data, the communication configuration, diagnostic configuration, and test case scope of the electronic control unit under test can be called in the same data object, which helps to reduce the repeated entry or conversion of configuration data between different test stages.

[0044] In step S102, a test task is generated based on the test task configuration data and test resource data. The test resource data includes simulation runtime resources, a first parameter, and a second parameter. The simulation runtime resources are used to configure the test runtime state of the bus simulation environment. The first parameter indicates the parameters that change with the test task, and the second parameter indicates the parameters corresponding to the electronic control unit under test or the simulation runtime resources.

[0045] Generating test tasks may involve binding test task configuration data with test resource data to form a data object that can be recognized or executed by the test execution device. A test task may include a test task identifier, test case set data, simulation runtime resources, first parameters, second parameters, execution control data generation rules, test output location, task status, or a combination thereof.

[0046] Simulation runtime resources can be used to put the bus simulation environment into the running state corresponding to the current test. For example, simulation runtime resources can be used to configure bus channels, load test scripts, configure diagnostic descriptions, configure message databases, configure simulation nodes, configure test sequences, or configure execution entry points. The first parameter can change depending on the test task; for example, it can indicate the input value of the current test, diagnostic request parameters, file path, security access parameters, execution count, or test output path. The second parameter can have a relatively stable correspondence with the electronic control unit under test (ECU) or simulation runtime resources; for example, it can indicate the ECU model, communication channel, diagnostic address, network address, project path, project version, test script version, or resource version.

[0047] By generating test tasks based on test task configuration data and test resource data, the test object parameters, test cases, and runtime resources required for a single test can be associated, facilitating subsequent test execution by running tests according to a unified task object. By distinguishing between the first and second parameters, parameters that change with the test task can be maintained separately from relatively fixed electronic control unit or runtime resource parameters, reducing the risk of parameter misuse during configuration reuse.

[0048] In step S103, the execution control data corresponding to the test task is sent from the first communication module to the second communication module. The execution control data is used to enable the second communication module to control the bus simulation environment to run the test cases corresponding to the test case set data based on the simulation runtime resources.

[0049] Execution control data can be generated by the task processing module based on the test task. This execution control data may include control data for loading simulation runtime resources, starting test scripts, setting test parameters, initiating test runs, stopping test runs, exporting test results, or combinations thereof. The first communication module can send the execution control data to the second communication module. The second communication module can then control the bus simulation environment to run corresponding test cases based on the execution control data. In one specific embodiment, the bus simulation environment can be CANoe, and the execution control data can be used to trigger CANoe project loading, CAPL script startup, system variable setting, measurement initiation, measurement stoppage, or diagnostic report export.

[0050] In some embodiments, the first communication module can be a communication client located on the control software side, and the second communication module can be a communication server located on the test execution side. The first and second communication modules can transmit execution control data through socket communication connections, application programming interface calls, shared memory, message queues, event listening, message listening, inter-process communication, or other data exchange methods. Socket.io can be used as an example of a data communication method within the main control software or on the user interface side, for example, it can be used to transmit test status data, interface update data, or execution status data between UI Front, UI BackEnd, TaskCenter, MySQLDB, or backend services. Socket.io does not constitute the only limitation on the communication method between the first and second communication modules.

[0051] Transmitting execution control data via the first and second communication modules allows the control side and the test execution side to connect through a data interface, eliminating the need to integrate the user interface, task processing, and bus emulation environment into the same program logic. This helps reduce the coupling between the control-side program and the test execution side's operating environment and facilitates the replacement or expansion of different bus emulation environments, communication services, or test execution interfaces. Furthermore, when the control side calls the bus emulation environment via standardized execution control data, and the hardware side performs physical connection adaptation via hardware interface devices, the control software, test scripts, and hardware interfaces can be maintained separately. This reduces adjustments to other parts when changing the electronic control unit under test, test scripts, or hardware wiring methods.

[0052] In step S104, test execution data is received, which is the data generated by running test cases in the bus emulation environment.

[0053] Test execution data may include test case running status, test pass results, test failure results, diagnostic response data, bus message data, error data, log file path, test report file path, or a combination thereof. In some embodiments, test execution data may also include message simulation data or response comparison results. Test execution data may be transmitted back in real time during test case execution or after one or more test cases have been completed.

[0054] In some embodiments, when running test cases, the bus simulation environment can configure communication channels, run test scripts, send diagnostic requests, receive diagnostic responses, record bus messages, or output test running status based on simulation runtime resources. Test execution data can be sent from the second communication module to the first communication module, or it can be written to the data storage module and then read by the control device.

[0055] By receiving test execution data, the operating status, diagnostic responses, bus messages, and error data generated by the test execution side can be returned to the control side or data storage side, which facilitates subsequent test result recording, report output, or failure item location.

[0056] In step S105, a test execution record is written, which includes test execution data, corresponding test case identification data, and test execution time.

[0057] Test execution logs associate data generated during a test execution with corresponding test case identifiers and execution times. Test case identifiers identify specific test cases. Execution times identify test batches, execution times, or time sequences. By writing to test execution logs, a queryable correspondence can be established between test execution data and test cases, test batches, and test times.

[0058] In some embodiments, test execution records may reside in a historical data structure. The first dimension of the historical data structure may correspond to test case identification data, and the second dimension may correspond to a test execution time sequence. The cells corresponding to the first and second dimensions may store test execution data, test pass results, test failure results, error data, log file paths, test report file paths, or combinations thereof.

[0059] By writing test execution data, test case identification data, and test execution time into the test execution record, the execution results of the same test case at different test times can be associated and saved. This makes it easy to query historical test results by test case or test batch, and also makes it easier to locate the corresponding test case and execution time when a test fails.

[0060] In some embodiments, test case identification data may include a test level field, a communication protocol field, a diagnostic protocol field, a functional domain field, a risk level field, and a test case number field. The test level field may indicate test depth, test phase, or test category. The communication protocol field may indicate the communication protocol involved in the test case. The diagnostic protocol field may indicate the diagnostic protocol involved in the test case. The functional domain field may indicate the functional domain to which the test case belongs. The risk level field may indicate the risk level corresponding to the test case. The test case number field may indicate the sequence number or unique identifier of the test case.

[0061] By setting multiple fields in the test case identification data, test cases can be identified not only by a single sequence number, but also organized by dimensions such as communication protocol, diagnostic protocol, functional domain, or risk level. This facilitates the selection of test cases according to different protocol types or functional domains, and also makes it easier to categorize and search by different fields in test reports or historical records.

[0062] In some embodiments, generating a test task based on test task configuration data and test resource data may include: determining test cases corresponding to communication parameters or diagnostic parameters based on communication protocol fields or diagnostic protocol fields. For example, when communication parameters indicate that the electronic control unit under test (ECU) communicates via a controller local area network (Controller Area Network), test cases corresponding to the Controller Area Network can be determined based on the communication protocol field. When diagnostic parameters indicate that the ECU under test uses a specific diagnostic protocol, test cases corresponding to the same diagnostic protocol can be determined based on the diagnostic protocol field.

[0063] By determining test cases based on communication protocol fields or diagnostic protocol fields, the test case selection process can be matched with the actual communication and diagnostic parameters of the electronic control unit under test, which helps to reduce the occurrence of mismatched test cases being added to the test task.

[0064] In some embodiments, generating a test task based on test task configuration data and test resource data may include: determining the execution order of test cases in the test task or the statistical category of test cases in the test report based on a risk level field. For example, test cases with higher risk levels can be set to run earlier in the test order, or test results can be categorized and statistically analyzed in the test report according to the risk level field.

[0065] By determining the execution order or statistical category based on the risk level field, test cases with higher risk levels can obtain corresponding execution priorities in test tasks, or form corresponding statistical dimensions in test reports, which facilitates the identification of key test items.

[0066] In some embodiments, test tasks may correspond to functional modules. Functional modules may include a security configuration module, a refresh module, or a diagnostic communication over Internet Protocol (TCP) module. Execution control data may also be used to invoke functional modules. The security configuration module may be used to perform tasks related to secure access, secure configuration, key injection, secure boot configuration, or secure status query. The security configuration module may also be used to perform MCT verification, which can be used to verify the authentication results of the electronic control unit under test (ECU) during secure access, message authentication, or secure communication processes. The refresh module may be used to perform tasks related to refreshing, flashing, or updating the program of the ECU. The diagnostic communication over Internet Protocol (TCP) module may be used to perform communication tasks based on the diagnostic communication over Internet Protocol (TCP).

[0067] By enabling the test task to correspond to the security configuration module, refresh module, or diagnostic communication via Internet Protocol module, functions such as secure access, refresh, and diagnostic communication via Internet Protocol can be incorporated into the test task as callable test capabilities, facilitating the expansion of different types of vehicle-mounted test tasks without changing the main test process.

[0068] Furthermore, in some cases, a test environment fingerprint can be generated based on the version identifier of the simulation runtime resources, the first parameter, the second parameter, the channel status of the hardware interface device, and historical test execution records. When the test environment fingerprint differs from the historical baseline fingerprint, verification cases are inserted into the test task. In other words, a test environment fingerprint corresponding to the current test task can be generated after the test task is generated but before the execution control data is sent. The test environment fingerprint can be generated based on the version identifier of the simulation runtime resources, the test script version, the first parameter, the second parameter, the channel status of the hardware interface device, the functional module version, and historical test execution records. The task processing module can compare the test environment fingerprint with the historical baseline fingerprint; when they differ, channel verification cases, resource loading verification cases, or security access pre-check cases are inserted, and the verification results are written to the test execution record. In this way, deviations in results caused by changes in the test environment can be identified before the formal execution of test cases.

[0069] Figure 2 This is a schematic diagram of a vehicle bus testing system provided in some embodiments of this disclosure. (Reference) Figure 2 The vehicle bus test system 200 can be represented by a system frame, and this system frame can include five module frames: a control device 210, a task processing module 220, a first communication module 230, a test execution device 240, and a data storage module 250. Figure 2 This diagram illustrates the main functional units of the vehicle bus test system 200 from a modular perspective. Figure 2 The position and arrangement of the module boxes are only used to illustrate the logical relationship between the modules and do not constitute a limitation on the physical location, deployment method or execution order of the modules.

[0070] Control device 210 can be used to receive test task configuration data. The test task configuration data may include communication parameters, diagnostic parameters, and test case set data for the electronic control unit under test. Control device 210 may include control software, a control terminal, a control PC, a test control server, or other data processing equipment capable of receiving test configurations and initiating test tasks. Figure 2 In the diagram, the control device 210 is shown as a module within the system 200, representing the configuration entry point for the test task configuration data to enter the system 200.

[0071] The task processing module 220 can be used to generate test tasks based on test task configuration data and test resource data. Test resource data may include simulation runtime resources, a first parameter, and a second parameter. Simulation runtime resources can be used to configure the test runtime state of the bus simulation environment. The first parameter can indicate parameters that change with the test task. The second parameter can indicate parameters corresponding to the electronic control unit under test (ECU) or simulation runtime resources. Figure 2 In the diagram, the task processing module 220 is shown as a module block within the system 200, used to represent the processing unit that organizes test task configuration data and test resource data into test tasks.

[0072] The first communication module 230 can be used to send execution control data corresponding to the test task to the second communication module. The execution control data can be used to enable the test execution side control bus simulation environment to run the test cases corresponding to the test case set data based on the simulation runtime resources. Figure 2 In the diagram, the first communication module 230 is shown as a module within the system 200, representing a data interaction unit for transmitting execution control data between the control side and the test execution side. The second communication module can be part of the test execution device 240. Figure 2 It will not be drawn separately in the diagram, but can also be shown as an independent module in other embodiments.

[0073] The test execution device 240 can be used to run test cases based on execution control data. The test execution device 240 may include a second communication module and a bus emulation environment. The second communication module can receive execution control data from the first communication module 230, and the bus emulation environment can run test cases corresponding to the test case set data based on simulation runtime resources. Figure 2 In the diagram, the test execution device 240 is shown as a module within the system 200, used to summarize the second communication module, the bus simulation environment, and test execution-related functions.

[0074] The data storage module 250 can be used to write test execution records. The test execution records may include test execution data generated by running test cases in the bus emulation environment, corresponding test case identification data, and test execution time. The data storage module 250 can be a database, file system, log system, history module, or other data storage structure capable of storing test execution records. Figure 2 In the diagram, the data storage module 250 is shown as a module within the system 200, serving as a recording unit for representing data such as test execution data, test case identification data, and test execution time.

[0075] Combined with the preceding text Figure 1 The details in the described method embodiments are applicable to all situations where there is no conflict. Figure 2The vehicle bus test system 200 is shown. Accordingly, Figure 2 The control device 210, task processing module 220, first communication module 230, test execution device 240, and data storage module 250 shown can be implemented through software, hardware, or a combination of software and hardware. The report output module, function plug-in module, hardware interface device, bus analysis device, electronic control unit under test, and more specific main control software structure can be combined with… Figures 3 to 7 Further explanation is needed, without necessarily including everything. Figure 2 .

[0076] For details regarding the specific processing, optional configurations, data types, communication methods, test execution methods, test recording methods, and the technical effects that can be achieved by each module in the vehicle bus test system 200, please refer to the descriptions of the various embodiments of the vehicle bus test method above. Where there is no conflict, the various embodiments of the vehicle bus test method above can be applied equally, similarly, or adaptively to the vehicle bus test system 200. To avoid repetition, they will not be described again here.

[0077] Figure 3 This is a schematic diagram illustrating the technical approach of an in-vehicle bus testing system provided in some embodiments of this disclosure. (Reference) Figure 3 A vehicle bus testing system can include a hardware side, a laptop side, an overall software side, and a main control software side. The hardware side can include the electronic control unit (ECU) under test, an adapter box, a bus emulation device (such as a Canoe device), and an Ethernet interface device. The ECU under test can be connected to the adapter box. Both the Canoe device and the Ethernet interface device can be connected to the adapter box. Figure 3 The arrow between the Canoe device and the adapter box indicates that the Canoe device communicates with the ECU under test via the adapter box through a bus; the arrow between the Ethernet interface device and the adapter box indicates that the Ethernet interface device communicates with the ECU under test via Ethernet or diagnostic communication via Internet Protocol through the adapter box; the arrow between the adapter box and the ECU under test indicates the test connection or signal transfer relationship between the two.

[0078] refer to Figure 3 The laptop can run the overall software. This overall software can include the Canoe environment and the main control software. The Canoe environment can include Canoe, ComServer, user execution modules, and TP (Transmission Terminal) sets. Canoe can communicate with Canoe devices on the hardware side. ComServer can reside within the Canoe environment and can communicate with ComClient in the main control software. Figure 3The connection between the Canoe device and the ComServer indicates that the Canoe environment interacts with the Canoe device through the ComServer or related communication links, thereby accessing the electronic control unit (ECU) under test via the Canoe device.

[0079] refer to Figure 3 In the Canoe environment, user-executed modules can correspond to TP sets. A TP set can include one or more test cases, test steps, or test sequences. Figure 3 The connecting line extending to the right of the TP set indicates that the TP set can be used in conjunction with project files, dynamic parameters, static parameters, or test execution-related data on the main control software side. Through the user execution module and the TP set, test cases can be run in the Canoe environment according to the corresponding test flow.

[0080] refer to Figure 3 The main control software can include backend services and a UI front. Backend services may include components such as ComClient, TaskCenter, SocketIO, MySQLDB, UI BackEnd, CANoeHandle, EthHandle, and DLL wrappers. The UI front can reside on the main control software side and connect to the engineers. Figure 3 The arrow between the engineer and the UI Front indicates that the engineer can input test configurations, trigger test runs, view test status, or view test results through the UI Front.

[0081] refer to Figure 3 ComClient can be used as a communication client on the control software side and can communicate with ComServer in the Canoe environment. Figure 3 The ComClient internally includes processing items such as process startup, device connection, project loading, CAPL startup, and test report output. Device connection can be used to connect to Canoe devices, Ethernet interface devices, or other test communication devices. Project loading can be used to load Canoe project files or other simulation runtime resources. CAPL startup can be used to launch CAPL scripts within the Canoe environment. Test report output can be used to output test results or report data after the test run.

[0082] refer to Figure 3The ComClient section includes settings for project files, dynamic parameters, and static parameters. Project files serve as an example of simulation runtime resources. Dynamic parameters serve as an example of the first set of parameters, indicating parameters that change as the test task progresses. Static parameters serve as an example of the second set of parameters, indicating parameters corresponding to the electronic control unit (ECU) under test or the simulation runtime resource. Figure 3 The connection relationships between ComClient, project files, dynamic parameters, and static parameters indicate that the main control software can call or pass project files, dynamic parameters, and static parameters when executing test tasks.

[0083] refer to Figure 3 CANoeHandle can be used as an example of a handle in a bus emulation environment. Figure 3 The CANoeHandle is linked to project files, dynamic parameters, and TaskCenter. Based on... Figure 3 As shown in the connection relationship, CANOEHandle can be used to encapsulate or call operations related to Canoe, such as project loading, measurement startup, variable reading and writing, CAPL script startup, test running, or report export. Figure 3 The arrow pointing upwards from TaskCenter to CANoeHandle is labeled with "Canoe". This arrow indicates that TaskCenter can access Canoe-related capabilities through CANoeHandle.

[0084] refer to Figure 3 TaskCenter can be seen as an example of a task processing module. Located in the main control software, TaskCenter is connected to objects such as CANoeHandle, EthHandle, SocketIO, MySQLDB, and DLL wrappers. TaskCenter can be used to organize test tasks, schedule test execution, receive or write task data, and generate test tasks based on project files, dynamic parameters, static parameters, and test case sets. Figure 3 The connection between TaskCenter and MySQLDB can represent the transfer of test tasks, test resource data, test execution data, or test execution records between TaskCenter and MySQLDB. Figure 3 The connection between TaskCenter and SocketIO indicates that TaskCenter can pass test status or execution data to the user interface or backend service via SocketIO.

[0085] refer to Figure 3The main control software includes MySQLDB. MySQLDB can serve as an example of a data storage module or database, used to store test task configuration data, test resource data, test execution data, test execution records, test reports, historical results, or data required for user interface display. Figure 3 The connection between MySQLDB and TaskCenter can represent the transfer of task data or execution records between the task processing module and the database. Figure 3 The connection between MySQLDB and the UI BackEnd can mean that the user interface backend can read or write test configurations, historical results, or report data from the database.

[0086] refer to Figure 3 The main control software includes SocketIO. SocketIO can be used to transfer state data, execution control data, test execution data, or UI update data between TaskCenter, UIBackEnd, UI Front, or other backend services. Figure 3 The code also uses the term "Socket.io" to label several communication connections. The upper "Socket.io" connection line indicates data communication between ComClient and the UI Front, while the lower "Socket.io" connection line indicates data communication between TaskCenter, MySQLDB, or the UI BackEnd. In one specific implementation, the socket communication connection between the first and second communication modules can be based on "Socket.io," and test status or user interface data can also be passed between the UI BackEnd and UIFront via "Socket.io."

[0087] refer to Figure 3 The UI Front acts as the user interface front-end, while the UI BackEnd acts as the user interface back-end. There is a connection between the UI Front and UI BackEnd, and also between the UI BackEnd and MySQL Database. Engineers can use the UI Front to configure test tasks, view test execution status, query test execution records, or view test reports. The arrows between the UI Front and UI BackEnd indicate the transfer of data between the front-end page, test status data, or report display data. The arrows between the UI BackEnd and MySQL Database indicate data reading or writing between the back-end and the database.

[0088] refer to Figure 3The main control software also includes a DLL encapsulation. This DLL encapsulation can include a security layer, a refresh library, and a DoIP library. The security layer can be used to perform secure configuration, secure access, key injection, secure boot configuration, secure status query, or MCT verification. The refresh library can be used to perform electronic control unit refresh, flashing, or program updates. The DoIP library can be used to perform Ethernet-based diagnostic communication via Internet Protocol (IP).

[0089] Figure 3 The connections between the DLL encapsulation and the Canoe environment, TP collection, TaskCenter, or EthHandle indicate that the security layer, refresh library, or DoIP library can be invoked during test task execution. Specifically, TaskCenter can be used to generate test tasks, configure invocation parameters, or trigger execution flows; the TP collection, test scripts, or related handle objects in the Canoe environment can invoke the security layer, refresh library, or DoIP library in the DLL encapsulation during test execution. Therefore, TaskCenter does not need to directly execute the security algorithm or refresh algorithm, but can collaboratively complete security testing, refresh testing, or DoIP communication testing by executing control data, test scripts, handle objects, or the DLL encapsulation.

[0090] refer to Figure 3 EthHandle can be used as an example of an Ethernet handle. Figure 3 The arrow pointing downwards from TaskCenter to EthHandle is labeled Ethernet, indicating that TaskCenter can access Ethernet-related communication capabilities through EthHandle. EthHandle can be used to encapsulate Ethernet communication, diagnostic communication via Internet Protocol (IP) communication, or access operations to Ethernet interface devices. Figure 3 The Ethernet interface device connects to the hardware-side adapter box, thereby enabling EthHandle, DoIP library, and Ethernet interface device to work together to achieve Ethernet diagnostic communication with the electronic control unit (ECU) under test.

[0091] refer to Figure 3 The backend service can be used to transfer data between ComClient, SocketIO, TaskCenter, MySQLDB, UIBackEnd, and UI Front. Figure 3The connections related to backend services represent the transfer of control commands, test status, database records, and user interface data between different software modules. Through backend services, UIFront can avoid direct coupling with the Canoe environment or DLL encapsulation, instead invoking test execution capabilities via UI BackEnd, SocketIO, TaskCenter, ComClient, CANoeHandle, EthHandle, or DLL encapsulation. The connection between ComClient and ComServer represents the transfer of execution control data or test execution data between the main control software and the Canoe environment. The connection between ComServer and the Canoe (CANoe) device represents the Canoe environment accessing the Canoe device through ComServer or related communication objects. The connection between the Canoe device and the adapter box represents bus communication between the Canoe device and the ECU under test via the adapter box. The connection between the Ethernet interface device and the adapter box represents Ethernet communication or DoIP communication between the Ethernet interface device and the ECU under test via the adapter box. The connections between TaskCenter, SocketIO, MySQLDB, UI BackEnd, and UI Front can represent the transfer of test tasks, test execution status, history, and UI display data within the main control software.

[0092] In some embodiments, the main control software may also reserve an interface for communication with a cloud server to upload test records, synchronize test configurations, or receive test tasks.

[0093] pass Figure 3 The technical approach shown allows the main control software, Canoe environment, DLL encapsulation, and hardware to handle tasks such as configuration, test execution, feature expansion, and physical access, respectively. This enables the main control software to organize test tasks, control test execution, and record test results through objects such as TaskCenter, ComClient, ComServer, CANoeHandle, EthHandle, SocketIO, and MySQLDB. This helps reduce adjustments to other components when replacing the electronic control unit (ECU), adjusting test scripts, or changing hardware interfaces.

[0094] Figure 4 This is a schematic diagram of a hardware interface device provided in some embodiments of this disclosure. (See reference) Figure 4The hardware interface device may include a housing and multiple sets of connection terminals disposed on the housing. The multiple sets of connection terminals may include different connection areas indicated by A1 to A11 in the figure. Each connection area may include one or more terminals for connecting power lines, communication lines, control lines, diagnostic lines, test lines, or combinations thereof to the electronic control unit under test. Connection areas A1 to A5 may be used to provide multiple sets of universal connection terminals. Figure 4 The terminal blocks 1 to 9 can correspond to different test channels, different pin positions, or different signal paths. In some embodiments, the intersection of the connection areas A1 to A5 with the terminal blocks 1 to 9 can be used to form a multi-row, multi-column terminal matrix to accommodate the pin connections, signal transfers, or channel assignments of different electronic control units under test. The connection areas A6 and A7 can be used to provide differential communication terminals and ground terminals. The connection areas A8 to A11 can be used to provide relay contact terminals.

[0095] refer to Figure 4 The hardware interface device may include power terminals. These power terminals may include positive and negative power terminals, indicated by "+" and "-" in the figure. The positive and negative power terminals can be used to provide test power to the electronic control unit under test (ECU) or to connect to an external power control device. In some embodiments, the hardware interface device may support voltage programming control and be able to output a supply voltage in the range of 0V to 18V to perform tests on the ECU under test under power-on, power-off, undervoltage, overvoltage, or different voltage conditions. The power terminals may correspond to a power control interface.

[0096] refer to Figure 4 The hardware interface device may include differential communication terminals and a ground terminal. The differential communication terminals may include the receive positive terminal, receive negative terminal, transmit positive terminal, and transmit negative terminal, indicated by RX+, RX-, TX+, and TX- in the figure. The ground terminal may be represented by GND. The differential communication terminals can be used to transmit Ethernet communication signals, diagnostic communication via Internet Protocol (IP) signals, or other differential communication signals. The ground terminal can be used to provide a reference potential for differential communication or device connection.

[0097] refer to Figure 4 The hardware interface device may include relay contact terminals. Relay contact terminals may include normally open contacts, common contacts, and normally closed contacts, indicated by NO, COM, and NC in the figure. Relay contact terminals can be used to control the on / off state of power supply paths, communication paths, test paths, or fault simulation paths. Relay contact terminals can also be used to switch different connection states during testing. In some embodiments, relay contact terminals may cooperate with a power control interface or a channel control interface to switch one or more test channels in the terminal matrix.

[0098] Figure 4The connection areas, terminal rows and columns, and number of terminals described are merely examples and do not constitute a limitation on the number, arrangement, definition, or interface type of the hardware interface device. In other embodiments, the hardware interface device may adjust the number of terminals, connection areas, and terminal functions according to the interface definition of different electronic control units under test. The voltage range of 0V to 18V is also just a specific example; in other embodiments, the voltage output range may be adjusted according to the power supply requirements of the electronic control unit under test.

[0099] Figure 5 This is a schematic diagram of the test case identification data structure provided in some embodiments of this disclosure. (Reference) Figure 5 Test case identification data can include test level, communication protocol, diagnostic protocol, functional domain, test case risk level, and test case number. Figure 5 The example shown here uses a segmented encoding format to illustrate test case identification data. This segmented encoding format is only used to illustrate the relative relationships between different fields and does not constitute a limitation on field length, character type, or field value method.

[0100] refer to Figure 5 Test level can be used to indicate the test level or test phase to which a test case belongs. Communication protocol can be used to indicate the communication protocol corresponding to a test case. Diagnostic protocol can be used to indicate the diagnostic protocol corresponding to a test case. Functional domain can be used to indicate the functional domain to which a test case belongs. Test case risk level can be used to indicate the risk level corresponding to a test case. Test case number can be used to indicate the number of the test case in the corresponding test set.

[0101] refer to Figure 5 The test case identification data contains multiple fields that can be read or identified by the task processing module. The task processing module can determine the test cases corresponding to the communication or diagnostic parameters based on the communication or diagnostic protocol. The task processing module can also determine the execution order of test cases in the test task based on the test case risk level, or determine the statistical category of the test cases in the test report.

[0102] In some embodiments, the main control software can function as the main control console. The main control console may include a hardware management module, a test configuration module, a diagnostic control module, a security function module, and a reporting center module. These modules serve as functional areas within the main control console, respectively supporting hardware status processing, test configuration organization, diagnostic test execution, security test execution, and test result output.

[0103] The hardware management module can include channel status detection and 0-18V voltage programming control. Channel status detection can be used to check the availability of hardware interface devices, bus analysis equipment, bus emulation environments, or communication channels, and can generate error data, test execution status, or prompt messages when a channel is abnormal. The 0-18V voltage programming control can be used to configure the power supply voltage, power-on status, power-off status, or test power supply conditions of the electronic control unit under test (ECU) to support testing under different power supply conditions. If the specific hardware platform supports other voltage ranges, the voltage output range can also be adjusted according to the power supply requirements of the ECU under test.

[0104] The test configuration module can include ECU parameter loading, test case filtering, and risk level filtering. ECU parameter loading can be used to load the communication parameters, diagnostic parameters, power supply parameters, interface parameters, or other configuration data related to the ECU under test. Test case filtering can be used to determine the test cases to be run from a test case library or set based on test task configuration data, communication parameters, diagnostic parameters, test level, communication protocol, diagnostic protocol, or functional domain. Risk level filtering can be used to filter, sort, or classify test cases based on their corresponding risk levels, thereby determining the execution order in the test task or the statistical category in the test report.

[0105] The diagnostic control module can include multi-protocol diagnostics, message simulation, and response comparison. Multi-protocol diagnostics can support diagnostic requests, responses, session switching, or status queries under different diagnostic protocols. Message simulation can generate simulated diagnostic messages, bus messages, or response messages according to preset message formats, diagnostic protocols, or test cases. Response comparison can compare the diagnostic response data returned by the ECU under test with the expected response data to determine the pass / fail result or error data of the corresponding test case.

[0106] The security function module may include one-click key injection, security status detection, and MACT verification. One-click key injection can be used to trigger key injection or write security access-related configurations. Security status detection can be used to query the security status of the ECU under test, such as security access status, security configuration status, security startup status, or security function execution status. MACT verification can be used to verify the authentication results of the ECU under test during secure access, message authentication, or secure communication processes, and can write the MACT verification results to test execution data or test execution records. In some embodiments, the security function module can simulate the interaction process between a security server and the ECU under test to complete key injection, secure startup configuration data writing, or security status query.

[0107] The reporting center module can include real-time logging, matrix history recording, and PDF / XML reports. Real-time logging can record test status, diagnostic responses, bus messages, error data, or execution time during test execution. Matrix history recording can organize historical test data according to test case identification data and test execution time; for example, recording test execution results with test case identification data as one dimension and test execution time series as another. PDF / XML reports can output test reports based on test execution records. PDF reports can be used to present test conclusions, test case execution status, error data, diagnostic response data, or statistical results to engineers, while XML reports can be used for structured data exchange with external systems.

[0108] The terms and names used in the above module and function descriptions are primarily for illustrative purposes, illustrating one possible functional division method for the main control software, and do not constitute a limitation on module names, number of modules, module boundaries, software architecture, or implementation methods. In other embodiments, the above functions may be merged, split, renamed, or deployed in different software modules, hardware modules, or combined software and hardware modules; as long as the corresponding data reception, parameter loading, test case filtering, test execution, status recording, security function processing, or report output can be achieved, they are applicable to the relevant embodiments of this disclosure.

[0109] Figure 6 This is a schematic diagram of test hardware connections provided in some embodiments of this disclosure. (Reference) Figure 6 The vehicle control unit can be used as an example of an electronic control unit under test (ECU). The vehicle control unit can be connected to a hardware interface box, which can be connected to a bus analysis device, which can be connected to a control PC. The vehicle control unit can access the bus analysis device through the hardware interface box, and the control PC can initiate tests through the bus analysis device.

[0110] refer to Figure 6 A connection from the vehicle control unit to the hardware interface box indicates that the power, communication, diagnostic, or test lines of the vehicle control unit are connected to the hardware interface box. A connection from the hardware interface box to the bus analysis device indicates that the hardware interface box transfers the corresponding signals from the vehicle control unit to the bus analysis device. A connection from the bus analysis device to the control PC indicates that the bus analysis device and the control PC transmit bus data, diagnostic data, test control data, or test execution data.

[0111] refer to Figure 6The control PC can perform communication tests, diagnostic tests, refresh tests, or secure access tests with the vehicle control unit via a bus analysis device and a hardware interface box. The hardware interface box adapts the physical connection between the vehicle control unit and the bus analysis device. The bus analysis device carries the interface for bus communication, message transmission and reception, simulation access, or test execution. Therefore, the control PC does not need to be directly connected to the vehicle control unit; test data exchange and hardware access can be completed through the bus analysis device and the hardware interface box. By separating the data processing on the control software side, the communication execution on the bus analysis device side, and the physical wiring adaptation on the hardware interface box side, the control software, test scripts, and hardware interfaces can be relatively independent, facilitating the reuse of test task configuration data, test resource data, or test case set data when replacing the electronic control unit under test or adjusting hardware wiring.

[0112] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is also provided, which stores instructions and executes a vehicle bus testing method according to any embodiment of this disclosure when the instructions are run. The non-transitory computer-readable storage medium, memory, etc., referred to in this disclosure can be any available medium accessible by a general-purpose or special-purpose computer.

[0113] This disclosure also provides an electronic device. The electronic device includes a memory and a processor. The memory stores instructions that, when executed by the processor, perform an on-board bus testing method according to any of the foregoing embodiments. Reference Figure 7 , Figure 7 A schematic diagram of an electronic device 700 is shown. The electronic device 700 may include a processor 702, a memory 704, a communication device 706, and a bus 708. The processor 702, memory 704, and communication device 706 can communicate with each other via the bus 708.

[0114] The processor 702 can be used to execute computer programs to implement the above-described vehicle bus testing method. The processor 702 may include a general-purpose processor, a special-purpose processor, a microprocessor, a digital signal processor, a programmable logic device, or other processing means capable of executing computer programs.

[0115] The memory 704 can be used to store computer programs, test task configuration data, communication parameters, diagnostic parameters, test case set data, test resource data, simulation runtime resources, first parameters, second parameters, test tasks, execution control data, test execution data, test execution records, test case identification data, test execution time, historical data structures, or test reports. The memory 704 may include volatile memory or non-volatile memory.

[0116] The communication device 706 can be used to receive or transmit data related to vehicle bus testing. For example, the communication device 706 can receive test task configuration data, test resource data, execution control data, or test execution data, and can also output test execution records, test reports, or execution control data. The communication device 706 can also communicate with the electronic control unit under test, hardware interface device, bus analysis equipment, test execution device, control device, or server through a vehicle communication interface, network interface, serial interface, controller area network interface, local area network interface, vehicle Ethernet interface, or other communication interface.

[0117] Bus 708 can be used to transmit data or control signals between processor 702, memory 704 and communication device 706.

[0118] In some embodiments, the electronic device 700 may further include an input device or an output device. The input device may include a keyboard, mouse, touchscreen, file reader interface, diagnostic interface, bus interface, test configuration import interface, or other input components. The output device may include a display screen, file output interface, communication output interface, report output interface, or other output components.

[0119] The technical features in the above embodiments can be combined arbitrarily, as long as the combination does not conflict. The above description is only a part of the embodiments of this disclosure and is not intended to limit this disclosure. For those skilled in the art, changes, substitutions or combinations can be made to the above embodiments without departing from the concept of this disclosure, and such changes, substitutions or combinations should all fall within the protection scope of this disclosure.

Claims

1. A method for testing an in-vehicle bus, characterized in that, include: Receive test task configuration data, which includes communication parameters, diagnostic parameters, and test case set data for the electronic control unit under test; Based on the test task configuration data and test resource data, a test task is generated. The test resource data includes simulation running resources, a first parameter, and a second parameter. The simulation running resources are used to configure the test running state of the bus simulation environment. The first parameter indicates the parameter that changes with the test task, and the second parameter indicates the parameter corresponding to the electronic control unit under test or the simulation running resources. The first communication module sends the execution control data corresponding to the test task to the second communication module. The execution control data is used to enable the second communication module to control the bus simulation environment to run the test cases corresponding to the test case set data based on the simulation running resources. Receive test execution data, which is the data generated by the bus emulation environment running the test cases; as well as Write the test execution record, which includes the test execution data, the corresponding test case identification data, and the test execution time.

2. The method according to claim 1, characterized in that, The first communication module is a communication client located on the control software side, and the second communication module is a communication server located on the test execution side. The first communication module and the second communication module transmit the execution control data through a socket communication connection.

3. The method according to claim 1, characterized in that, The execution control data includes at least one of the following: Control data for loading the simulation runtime resources, control data for starting the test script, control data for setting test parameters, control data for starting the test run, control data for stopping the test run, and control data for exporting the test results.

4. The method according to claim 1, characterized in that, The test case identification data includes test level field, communication protocol field, diagnostic protocol field, functional domain field, risk level field, and test case number field.

5. The method according to claim 4, characterized in that, A test task is generated based on the test task configuration data and test resource data, including: Based on the communication protocol field or the diagnostic protocol field, determine the test cases corresponding to the communication parameters or the diagnostic parameters.

6. The method according to claim 4, characterized in that, A test task is generated based on the test task configuration data and test resource data, including: Based on the risk level field, determine the execution order of the test cases in the test task or the statistical category of the test cases in the test report.

7. The method according to claim 1, characterized in that, The test execution data includes at least one of the following: Test case running status, test pass results, test failure results, diagnostic response data, bus message data, error data, log file path, and test report file path.

8. The method according to claim 1, characterized in that, The test execution record is located in a historical data structure. The first dimension of the historical data structure corresponds to the test case identification data, and the second dimension of the historical data structure corresponds to the test execution time sequence.

9. The method according to claim 1, characterized in that, The test task corresponds to a functional module, which includes a security configuration module, a refresh module, or a diagnostic communication via Internet Protocol module. The execution control data is also used to call the functional module.

10. A non-transitory computer-readable storage medium, characterized in that, It stores a computer program thereon, which, when executed by a processor, implements the method of any one of claims 1 to 9.

11. A vehicle-mounted bus testing system, characterized in that, include: A control device is used to receive test task configuration data, which includes communication parameters, diagnostic parameters, and test case set data for the electronic control unit under test. The task processing module is used to generate test tasks based on the test task configuration data and test resource data. The test resource data includes simulation running resources, a first parameter, and a second parameter. The simulation running resources are used to configure the test running state of the bus simulation environment. The first parameter indicates the parameter that changes with the test task, and the second parameter indicates the parameter corresponding to the electronic control unit under test or the simulation running resources. The first communication module is used to send the execution control data corresponding to the test task to the second communication module; The test execution device includes the second communication module and the bus simulation environment. The second communication module is used to control the bus simulation environment to run the test cases corresponding to the test case set data based on the simulation running resources, according to the execution control data. as well as The data storage module is used to write test execution records, which include test execution data generated by the bus simulation environment running the test cases, corresponding test case identification data, and test execution time.

12. The system according to claim 11, characterized in that, The system also includes a report output module, which is used to output a test report based on the test execution record.

13. The system according to claim 11, characterized in that, The system also includes a functional plug-in module, which includes at least one of a security configuration module, a refresh module, and a diagnostic communication via Internet Protocol module. The task processing module is also used to call the functional plug-in module according to the test task.

14. The system according to claim 11, characterized in that, The system also includes a hardware interface device, which is connected between the electronic control unit under test and the bus analysis device. The hardware interface device includes at least one of a controller local area network interface, a local area network interface, an Ethernet interface, a power control interface, a relay contact terminal, and a differential communication terminal.

15. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores a computer program that, when executed by the processor, implements the method of any one of claims 1 to 9.